[SOLVED][Q] ART building bootloop - anyone else seen this? - One (M9) Q&A, Help & Troubleshooting

Hi, Ive not long had my m9. When i got it it updated straight away and got the charging bug.
Since then I have s-off'd and tried various roms with not too much luck.
I now have a bug that occurs when i flash a new rom. This has happened when i flashed 3 different roms. Leedroid, Viper and android revolution. the rom flashes ok, then starts to boot, and builds art. It then finishes building art and starts to complete the boot process, and then it reboots and tries to build art again.
I flash back to my stock backup and everything is fine again. (apart from the damned charging bug)
Has anyone else experienced something similar?? am i missing something??

Go in twrp and make factory reset

just tried that, didnt work

Did you update your firmware? if you're still on 1.x firmware, those 2.x roms will reboot.

yeah. have tried matching roms to firmware and still get the same result. trying viper one currently. in a massive bootloop again. It boots enough to say "nfc service has stopped working" and thats what made me think it might be firmware, but it seems to make no difference.

cant even adb whilst its booting.. getting waiting for device.

What version of twrp are you using?

2.8.6.1

philicibine said:
2.8.6.1
Click to expand...
Click to collapse
Update to 2.8.7.0 and see if it continues.

I've solved this, and my charging issue. Finally!!
I decided to flash the earliest ruu I could find and then let it do all of the ota updates itself.
I then rerooted, flashed updated firmware and am now running leedroid.
Thanks for the help guys.

Related

[Q] Back to stock, touchscreen does not work after OTA update

I did a restore of my One-X to stock rom according to this tutorial.
http://design-extreme.net/restore-ht...-to-stock-rom/
This all went well and without problems. The RUU I flashed is this one.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed
When I now startup the phone it all works perfect. Then the phone says there is an OTA (to 3.20 I believe)
I download and install the OTA and the phone restarts, but after restarts the phone's touchscreen does not work anymore.
I solved this for now by installing the 3.14RUU again, then it works again. But of course I would like to be able to install the OTA's
To me it sounds like a driver problem in the new version that prevents the touchscreen from working. Anyone have idea how to solve this?
I tried different boot.img after the OTA update but none of them solved the problem. Somebody here who has a good idea?
Xanion said:
I did a restore of my One-X to stock rom according to this tutorial.
http://design-extreme.net/restore-ht...-to-stock-rom/
This all went well and without problems. The RUU I flashed is this one.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed
When I now startup the phone it all works perfect. Then the phone says there is an OTA (to 3.20 I believe)
I download and install the OTA and the phone restarts, but after restarts the phone's touchscreen does not work anymore.
I solved this for now by installing the 3.14RUU again, then it works again. But of course I would like to be able to install the OTA's
To me it sounds like a driver problem in the new version that prevents the touchscreen from working. Anyone have idea how to solve this?
I tried different boot.img after the OTA update but none of them solved the problem. Somebody here who has a good idea?
Click to expand...
Click to collapse
Kicking my own question. No-One who has an idea or thought? I've tried everything I could think off and would appreciate some fresh thoughts.
I have almost the same problem now. I was running CWM 10.2 with the TWRP recovery and reverted back to stock using a backup from this thread: http://forum.xda-developers.com/showthread.php?t=1975140
The installation went fine, but touch isn't working anymore. What could be wrong? I would like to have my phone back to stock and use the OTA from HTC.

[Q] CM11 snapshot/nightly stuck at boot... now can not even rollback to 10.2

Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )
nabeelmoeen said:
Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )
Click to expand...
Click to collapse
Your HBOOT is to low you must to upgrade ti 1.39 or 1.72 but 1.31 is tooo low and for this the CM11 don't boot
Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version
nabeelmoeen said:
Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version
Click to expand...
Click to collapse
try restore stock and chek for update restore nandroid and see I am not sure J15 is only 1.31
Will give it a shot tonight and report back. ...what's grinding my gears is none of the other roms including jb ones I tried are working either
i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!
nabeelmoeen said:
i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!
Click to expand...
Click to collapse
is HBOOT still the same version or did you upgrade it?
I am curious about the order in which you did things. After formatting boot, system and cache partitions, did you flash the boot image again or did you do that prior to the formatting.
Thanks

System UI crashing on latest CM12 Nightlys

So I have CM12 installed, but when I go to flash the latest nightlys I keep getting System UI crashing. When I acknowledge it, the error will not go away. I have HBOOT 3.18 and radio 1.19 with TWRP 2.8.4.0. I've wiped everything I can think of save the internal and external SDCARDs. What am I doing wrong to not be able to flash the latest nightlys? Ive tried flashing on top of my current CM12, which was upgraded from CM11, and wiping clean. When I wiped clean everything was working great till the phone went to sleep. When I woke it up, same issues.
Yeah, I was having that issue as well. CM12 just isn't stable right now, at least for me. Everything lagged after having the phone on for about a half hour, took 4-5 seconds to do anything after selecting it... it was just a mess. Went back to stock.
Everything runs like a champ, I just cant flash the latest version. It seems that I'm the only one having this issue, or no one cares to help anyone anymore.
Tobb555 said:
Everything runs like a champ, I just cant flash the latest version. It seems that I'm the only one having this issue, or no one cares to help anyone anymore.
Click to expand...
Click to collapse
Okay, I have cleared off a bunch of crap off my phone and am willing to give CM12 a try just to see if you have the issue. Which CM12 version are you referring to?
Thanks for the help. Right now Im running version 12-20150128-NIGHTLY-m8. When I try to update to any of the latest versions Im getting the System UI crashes. It doesnt matter how many times I acknowledge it, it wont go away.

Boot loop issue when battery dies or on abrupt restart

I'm running stock 5.1.1 rooted. Whenever the battery dies on the tablet, it will go into a bootloop when I charge it and turn it back on (gets to Samsung logo with no start up music). So far, that only thing that seems to work is wiping data. Has anyone experienced something similar? Bad install maybe?
I've had the same thing happen to me last night. I tried everything and nothing worked. I had to restore a old back up i had with twrp and it started fine. Not sure what causes it though.
I've been having this problem for 6 months now. Let me try a custom rom.
dkb218 said:
I've been having this problem for 6 months now. Let me try a custom rom.
Click to expand...
Click to collapse
Update the twrp tp latest version.I had the ame problem with old twrp but now all is fine with 3.0.2.0.
mine just started doing this. i can boot into recovery but the touch screen doesn't respond. i can also get into odin. I believe i was running Rooted Stock 5.1.1. Should i just reflash (i was thinking of going custom like LineAge) or do i need to reflash stock rom? I was also reading about just flashing the PIT and EFS. i know it's a 3 year old tablet at this point, but it's been good to me and i'd like to increase my odds of bringing it back to life

Frequent freezes and hangs after rooting and installing twrp

So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
What model?(network)
aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.
ziggy71 said:
What model?(network)
Click to expand...
Click to collapse
Verizon SM-N910V retail
weard1212 said:
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.
Click to expand...
Click to collapse
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?
aclays said:
Verizon SM-N910V retail
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?
Click to expand...
Click to collapse
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.
ziggy71 said:
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.
Click to expand...
Click to collapse
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.
aclays said:
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.
Click to expand...
Click to collapse
So you are full stock? Does the update issue happen on the stock recovery?
ziggy71 said:
So you are full stock? Does the update issue happen on the stock recovery?
Click to expand...
Click to collapse
Yep it did. So I think I've actually fixed it now. I thought that flashing the full firmware would also flash the boot loader and modem, but I Odin'd both of those in and so far so good! It did the whole updating thing again just like before this time, but when it was done it actually loaded up recovery like it was supposed to. So at that point I wiped the cache, factory reset, then used Odin to flash in the boot loader and modem for CPF3 that I found in that thread.
I've been using my phone and installing things for a couple hours now and haven't had a single hang. Before I did this, it would hang very quickly. Maybe I'll get brave and try rooting and whatnot again later, but for now I'm just going to back off for a bit. Thanks for the help!
And so much for that. It was more stable than it had been in ages so I started installing all my apps and whatnot, now it's just as unstable as it used to be, just took a couple days to happen. I'm running out of ideas

Categories

Resources