Jump to content
PaulOBrien

Beta 13: MoDaCo.SWITCH HTC One support topic

Recommended Posts

Further is there anyone having issues with b12 bootloops that has never tried a 4.3 sense rom on their One?

Only ever had stock and ota and Switch

Share this post


Link to post
Share on other sites

I'm not experiencing bootloops and

- syncing contacts with Google

- have a SIM PIN code

- baseband 4A.14.3250.13_10.33.1150.01L

- never used a 4.3 Sense ROM

- forgot to disable fastboot before switching, and fastboot has remained on

Share this post


Link to post
Share on other sites

CID: VODAP203 (obtained with CIDgetter cause do not appears on the bootloader since unlocked)

Hboot: 1.54.0000

OS: 2.24.163.2

Never used a 4.3 sense ROM too

Have a SIM pin code too

Share this post


Link to post
Share on other sites

and you are having issues with b12?

Berrrr ya could say that seeing as its damn near bricked my device Hahahahaha

No Fear I'm all good just frustrated

Share this post


Link to post
Share on other sites

If you are having the bootloop problem, please...

  • Reboot to recovery
  • Do the following in adb shell: 'mount /system && df -h|grep system'

...and post the output.

P

Share this post


Link to post
Share on other sites

Okay, so this is the first time for me using pastebin, hope it's ok :)

Wiped, installed beta 12 and s-on package. In Sense disabled fastboot and enables wifi, that's all. Rebooted into GPe, enabled Wifi and set up my google account. Then booted back into Sense, and back to GPe. I was able to boot into Gpe, but I kept getting an error message saying com.android.phone stopped working, see: http://pastebin.com/sPsf2AHj

Next, I booted back into Sense, that didn't work: http://pastebin.com/n393mxXX

Hope this helps! It's different than what I experienced last time, don't know why. Will try to recreate that as well. Tnx.

Share this post


Link to post
Share on other sites

If you are having the bootloop problem, please...

  • Reboot to recovery
  • Do the following in adb shell: 'mount /system && df -h|grep system'

...and post the output.

P

C:\Program Files\Minimal ADB and Fastboot>adb devices

List of devices attached

HT36AW902384 recovery

C:\Program Files\Minimal ADB and Fastboot>adb shell

~ # ←[6nmount /system && df -h|grep system

mount /system && df -h|grep system

Filesystem Size Used Available Use% Mounted on

1.8G 1.7G 40.4M 98% /system

~ # ←[6n mount /system && df -h|grep system

mount /system && df -h|grep system

mount: mounting /dev/block/mmcblk0p35 on /system failed: Device or resource busy

~ # ←[6nmount /system && df -h|grep system

mount /system && df -h|grep system

mount: mounting /dev/block/mmcblk0p35 on /system failed: Device or resource busy

~ # ←[6nmount /system && df -h|grep system

mount /system && df -h|grep system

mount: mounting /dev/block/mmcblk0p35 on /system failed: Device or resource busy

Share this post


Link to post
Share on other sites

If you are having the bootloop problem, please...

  • Reboot to recovery
  • Do the following in adb shell: 'mount /system && df -h|grep system'

...and post the output.

P

Filesystem Size Used Available Use% Mounted on

1.8G 1.8G 24.1M 99% /system

booted into recovery when trying to get into Sense.

Share this post


Link to post
Share on other sites

Filesystem Size Used Available Use% Mounted on

1.8G 1.7G 40.4M 98% /system

All normal there.

Okay, so this is the first time for me using pastebin, hope it's ok :)

Wiped, installed beta 12 and s-on package. In Sense disabled fastboot and enables wifi, that's all. Rebooted into GPe, enabled Wifi and set up my google account. Then booted back into Sense, and back to GPe. I was able to boot into Gpe, but I kept getting an error message saying com.android.phone stopped working, see: http://pastebin.com/sPsf2AHj

Next, I booted back into Sense, that didn't work: http://pastebin.com/n393mxXX

Hope this helps! It's different than what I experienced last time, don't know why. Will try to recreate that as well. Tnx.

Thanks, i'll have a look at that!

P

Share this post


Link to post
Share on other sites

Okay, so this is the first time for me using pastebin, hope it's ok :)

Wiped, installed beta 12 and s-on package. In Sense disabled fastboot and enables wifi, that's all. Rebooted into GPe, enabled Wifi and set up my google account. Then booted back into Sense, and back to GPe. I was able to boot into Gpe, but I kept getting an error message saying com.android.phone stopped working, see: http://pastebin.com/sPsf2AHj

Next, I booted back into Sense, that didn't work: http://pastebin.com/n393mxXX

Hope this helps! It's different than what I experienced last time, don't know why. Will try to recreate that as well. Tnx.

Thanks, this is super-helpful! Both of these logcats are siloing issues - data problems causing a bootloop. Are you s-on or s-off?

P

Share this post


Link to post
Share on other sites

Thanks, this is super-helpful! Both of these logcats are siloing issues - data problems causing a bootloop. Are you s-on or s-off?

P

No problem :) I'm S-on and was running stock 401.8.

Share this post


Link to post
Share on other sites

No problem :) I'm S-on and was running stock 401.8.

This definitely points to an issue that could affect S-ON users, but it's unlikely the same problem would affect S-OFF users?

P

Share this post


Link to post
Share on other sites

Paul, latest logcat. I reinstalled like I did before: http://www.modaco.com/topic/363797-beta-12-modacoswitch-htc-one-support-topic/page__st__1580#entry2154986

Bootloop upon starting GPe, logcat: http://pastebin.com/HN9fL63H

Right now I have to restore my backup, but if you need additional information, please let me know and I can try asap. Thanks for looking into it.

Share this post


Link to post
Share on other sites

Paul, latest logcat. I reinstalled like I did before: http://www.modaco.com/topic/363797-beta-12-modacoswitch-htc-one-support-topic/page__st__1580#entry2154986

Bootloop upon starting GPe, logcat: http://pastebin.com/HN9fL63H

Right now I have to restore my backup, but if you need additional information, please let me know and I can try asap. Thanks for looking into it.

This again is a siloing failure. I'm preparing a hotfix to test now.

P

Share this post


Link to post
Share on other sites

com.android.phone this is the exact error message I got too, Paul do you need more logs or you assume this is ok with that one ?

The cause will be the same. Watch this space, i'm working to track it down! :)

P

Share this post


Link to post
Share on other sites

A quick heads up that i've found the problem, but not what's causing it. I'm working on it. Updates will be posted here in due course!

P

  • Upvote 1

Share this post


Link to post
Share on other sites

Yes After days with problem and coulden`t get switch to work! but now when i installed beta 12 with S-ON support package! Could i switch with out any problems!! :3 I LOVE it! just need to see after some switches if it still works or its start too bootloop? But SO far so good! GREAT WORK PaulOBrien! :3!!!

Share this post


Link to post
Share on other sites

I'm pretty confident i've found the issue and i'm testing the fix now.

It affects quite a few things actually (siloing, boot time, the package delete feature amongst others) so it's quite a biggie. ;)

P

Share this post


Link to post
Share on other sites
I'm pretty confident i've found the issue and i'm testing the fix now.

It affects quite a few things actually (siloing, boot time, the package delete feature amongst others) so it's quite a biggie. ;)

P

Great to hear and good to know that a fix is possibly coming soon. Waiting eagerly here (:

Share this post


Link to post
Share on other sites

Right folks!

Beta 13 is now available for testing here (flash on top of Beta 12) - DOWNLOAD (ROMraid)

Hopefully this will resolve the issues everyone has been having! Let me know...!

P

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.