Related
My wife has the incredible 2 and it is rooted on the stock GB 2.3.3 rom. This morning she emails me and says her phone has a little android icon with an exclamation point... I had her pull the battery to try to reboot but it just goes back to that same screen.
Any ideas how we can boot back up into the ROM? I won't be able to physically touch her phone until i get home from work tonight but I thought if you all could give me some suggestions in the mean time that would be great, thanks!
Is she able to get into recovery? If so, then she should be able to wipe and flash something else. However, if she isn't (and she's unable to boot the rom) then she can load the ruu through the bootloader. I'm assuming she's s-off, though. Loading the ruu would return the phone to stock and then you can reroot it afterward. Weird, though. The android with the exclamation mark is stock recovery so it seems as if she doesn't have a custom recovery.Was clockwork ever flashed?
Edit: Actually instead of going back to stock just load the custom CWM that's in the development forum. With the flashed recovery she can clear dalvik and cache. Hope this somewhat helps!
Assuming she had CWM recovery flashed during the rooting process, get her to go into recovery and try wiping the dalvik and cache partitions. She may be able to boot after that.
If she doesn't have HTC Fast Boot feature turned off, she'll need to do a battery pull first to really shut the power off, replace the battery, then hold down the Down Volume button while powering on to get into recovery.
good luck
klm22 said:
Assuming she had CWM recovery flashed during the rooting process, get her to go into recovery and try wiping the dalvik and cache partitions. She may be able to boot after that.
If she doesn't have HTC Fast Boot feature turned off, she'll need to do a battery pull first to really shut the power off, replace the battery, then hold down the Down Volume button while powering on to get into recovery.
good luck
Click to expand...
Click to collapse
Holding power + volume down gets you into the bootloader. But from there she can get into recovery.
not sure how to fix but i know what the cause is
This seems to have been caused by the push of the new market. Mine did the exact same thing today... Pulled it out of my pocket to see it on a blue android with exclamation, basically the stock recovery screen. I think that the market app is trying to flash there, but since we have custom recoveries, it takes a crap.
all we need is to be able to somehow clear wherever the DL for the new market install is, or manually apply the market from recovery. however, I have NO idea how to do either.
*edit* So i rebooted into recovery (pull battery 30 sec, replace, hold down power + vol down until bootloader, then selected recovery) cleared cache, cleared dalvik (im thinking mostly for good measure, dont think this solved the problem), and then rebooted the phone. AS SOON as it was booted enough to interact with, i held down the power button, turned it to airplane mode. the clearing of the cache mustve dumped the file pushed earlier, because as soon as the phone fully booted i got a "OTA software update failure" message, telling me it couldnt connect to the update server (airplane mode had the antenna off).
hope it works for you, I think it worked for me here. i'll post updates if anything changes.
p.s. i recommend finding the .apk floating around for the new market, and adding it manually, so that this doesnt happen post-airplane mode
Conduitz said:
This seems to have been caused by the push of the new market. Mine did the exact same thing today... Pulled it out of my pocket to see it on a blue android with exclamation, basically the stock recovery screen. I think that the market app is trying to flash there, but since we have custom recoveries, it takes a crap.
all we need is to be able to somehow clear wherever the DL for the new market install is, or manually apply the market from recovery. however, I have NO idea how to do either.
*edit* So i rebooted into recovery (pull battery 30 sec, replace, hold down power + vol down until bootloader, then selected recovery) cleared cache, cleared dalvik (im thinking mostly for good measure, dont think this solved the problem), and then rebooted the phone. AS SOON as it was booted enough to interact with, i held down the power button, turned it to airplane mode. the clearing of the cache mustve dumped the file pushed earlier, because as soon as the phone fully booted i got a "OTA software update failure" message, telling me it couldnt connect to the update server (airplane mode had the antenna off).
hope it works for you, I think it worked for me here. i'll post updates if anything changes.
p.s. i recommend finding the .apk floating around for the new market, and adding it manually, so that this doesnt happen post-airplane mode
Click to expand...
Click to collapse
The android market has nothing to do with what you just said.
The OTA message you're getting is from HTC pushing an "Over the air" update. The market is supposed to be updated while you're in the market. Two completely different things and I doubt it's the cause of this issue. Otherwise we'd all be experiencing problems.
yeah CWM is on her phone. It was installed during the rooting process. I've been wanting to put a Sense 3.0 ROM on there... looks like this is the perfect opportunity!
Thanks for the tips!!
cowman4000 said:
yeah CWM is on her phone. It was installed during the rooting process. I've been wanting to put a Sense 3.0 ROM on there... looks like this is the perfect opportunity!
Thanks for the tips!!
Click to expand...
Click to collapse
No problem man. Good luck.
jrizk07 said:
The android market has nothing to do with what you just said.
The OTA message you're getting is from HTC pushing an "Over the air" update. The market is supposed to be updated while you're in the market. Two completely different things and I doubt it's the cause of this issue. Otherwise we'd all be experiencing problems.
Click to expand...
Click to collapse
I'd love a link to anything stating the market was supposed to update while in the market.
each phone company was responsible for their own compatible version of the new market, I believe I read the other day, which would be why HTC, not VERIZON, WHO PUSHES ALL OTHER OTAS TO YOUR PHONE (unless theyre not your service provider, of course) sent an OTA to the phone.
Not sure what other, if any, updates HTC had to send today to my handset, seeing as it has recieved both OTA's before (GB and fixes), and as soon as I installed the new market app manually, the OTA didnt prompt me to install on reboot as it had previously.
at any rate, what I did fixed it. Does the cause, theorized by someone who didnt make the phone or the software for it, or the root tool, or custom HBoot that it uses, really effing matter?
Conduitz said:
I'd love a link to anything stating the market was supposed to update while in the market.
each phone company was responsible for their own compatible version of the new market, I believe I read the other day, which would be why HTC, not VERIZON, WHO PUSHES ALL OTHER OTAS TO YOUR PHONE (unless theyre not your service provider, of course) sent an OTA to the phone.
Not sure what other, if any, updates HTC had to send today to my handset, seeing as it has recieved both OTA's before (GB and fixes), and as soon as I installed the new market app manually, the OTA didnt prompt me to install on reboot as it had previously.
at any rate, what I did fixed it. Does the cause, theorized by someone who didnt make the phone or the software for it, or the root tool, or custom HBoot that it uses, really effing matter?
Click to expand...
Click to collapse
I'm glad you got it fixed but yes it matters. You say now that you're theorizing but in other places you're stating that the market update IS the culprit.
Say you're not sure but here's what I did. Otherwise you start to get people thinking that the new market is the cause of their issues when it has not been verified.
My phone downloaded the new market, I didn't manually install it and I do not have the problem you're describing.
My Girlfriend is the exact same way, She doesn't like the new market and it got installed on her phone but it not once rebooted into stock recovery.
what then?
Conduitz said:
I'd love a link to anything stating the market was supposed to update while in the market.
each phone company was responsible for their own compatible version of the new market, I believe I read the other day, which would be why HTC, not VERIZON, WHO PUSHES ALL OTHER OTAS TO YOUR PHONE (unless theyre not your service provider, of course) sent an OTA to the phone.
Not sure what other, if any, updates HTC had to send today to my handset, seeing as it has recieved both OTA's before (GB and fixes), and as soon as I installed the new market app manually, the OTA didnt prompt me to install on reboot as it had previously.
at any rate, what I did fixed it. Does the cause, theorized by someone who didnt make the phone or the software for it, or the root tool, or custom HBoot that it uses, really effing matter?
Click to expand...
Click to collapse
chillax bro. What you did obviously fixed the issue. The market is pushed to phones (similar to that of OTAs); however, the market is "updated" when the user accesses the original installed market. There won't be any warning or anything before the new market is installed over the old one. Correct me if i'm wrong, but you stated that each phone company is responsible for their own compatible version of the market... I BELIEVE that is incorrect as each market works on ANY android powered device, regardless of phone company/manufacturer. I am nearly certain that the market is universal on android phones. Again, someone correct me if i'm wrong. Just trying to clear something up.
Conduitz said:
I'd love a link to anything stating the market was supposed to update while in the market.
each phone company was responsible for their own compatible version of the new market, I believe I read the other day, which would be why HTC, not VERIZON, WHO PUSHES ALL OTHER OTAS TO YOUR PHONE (unless theyre not your service provider, of course) sent an OTA to the phone.
Not sure what other, if any, updates HTC had to send today to my handset, seeing as it has recieved both OTA's before (GB and fixes), and as soon as I installed the new market app manually, the OTA didnt prompt me to install on reboot as it had previously.
at any rate, what I did fixed it. Does the cause, theorized by someone who didnt make the phone or the software for it, or the root tool, or custom HBoot that it uses, really effing matter?
Click to expand...
Click to collapse
http://www.google.com/support/androidmarket/bin/answer.py?hl=en&answer=190860
klarson said:
chillax bro. What you did obviously fixed the issue. The market is pushed to phones (similar to that of OTAs); however, the market is "updated" when the user accesses the original installed market. There won't be any warning or anything before the new market is installed over the old one. Correct me if i'm wrong, but you stated that each phone company is responsible for their own compatible version of the market... I BELIEVE that is incorrect as each market works on ANY android powered device, regardless of phone company/manufacturer. I am nearly certain that the market is universal on android phones. Again, someone correct me if i'm wrong. Just trying to clear something up.
Click to expand...
Click to collapse
Google pushes out all the market updates. It's the files on the ROM itself that tells what to show in the market, like how some phones have their own "carrier channel"?
I believe this is done via the build.prop file, I could be wrong on which file it is but what does and doesn't show up in the market is controlled by the phone, Not necessarily the carriers.
jrizk07 said:
Google pushes out all the market updates. It's the files on the ROM itself that tells what to show in the market, like how some phones have their own "carrier channel"?
I believe this is done via the build.prop file, I could be wrong on which file it is but what does and doesn't show up in the market is controlled by the phone, Not necessarily the carriers.
Click to expand...
Click to collapse
That's exactly what i thought. Thanks.
i only ever said "it seems that" the market is the culprit. best guess is that its rom to rom wether or not something is getting screwed up from the market update or whatever. Not sure. Maybe its not the market at all. I just saw the same issue i had posted, threw my theory and fix out there. worked for me, hoped it'd help the poster.
also, to acknowledge the link you provided, that I requested.... I stand corrected. I only know just enough to be dangerous with these things and always appreciate solid fact to add to my knowledge base.
Problem is from a failed ota push. Wipe cache and davlik. Reboot phone and rename /system/etc/security/otacerts.zip to something else.
Sent from my ADR6300 using XDA App
maniac2k said:
Problem is from a failed ota push. Wipe cache and davlik. Reboot phone and rename /system/etc/security/otacerts.zip to something else.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
This x2,
About once a week I would get a push to phone via OTA, causes the same exact problem your having. Renamed otacerts.zip with root explorer, have not had a problem since.
I just had the same issue with my phone after the newest OTA pushed (I should have rejected it). My phone wouldn't boot, I got the white triangle, yellow exclamation and blue android. I used Conduitz's fix and I am back in business!
Thanks to the forum (and Conduitz)!
Hey guys, I have had the same issue with the triangle/exclamation point and the blue android guy. I booted into recovery and cleared cache. Like many have said it fixed the issue, however I want to push the 2.3.4 update to my phone.
How do I get my phone to accept and install the update?
(I know I'll lose root, but it will take somebody about a day to get it back in this forum, so that's not a concern).
I can tell you that I used the market less than 5 min before doing the OTA. Directly after the OTA, the new market was present. If they are not including the new market with the OTA, it sure did happen nearly simultaneously, which is quite coincidental. I know what the Google link said, but it sure seemed like the new market came with the update.
Disclaimer: This worked on my phone. I am not responsible if your phone turns into an expensive brick.
I know this isn't quite the update everyone was waiting for I managed to pull the 2.3.6 OTA files. I also managed to figure out how to flash them. Turns out CWM 5 offers root adb access, everything we need to update and root this phone. Note I tried CWM 6 but it said "possible loss of root" so apparently CWM 6 likes to reside on an already rooted phone.
Note this is not the most elegant solution. The most elegant would be a signed update.zip. The second most elegant would be something flashable with CWM or Odin. Too bad I don't know how to do those. I do know how to do this.
The first thing to do is make sure you are on the AT&T stock firmware. It doesn't matter if you've already flashed something else. No need to wipe cache or factory reset or anything (although if you run into problems you should try to do that step). Download it from samfirmware.com. Flash it with Odin. This will put you on stock 2.3.5. Even if you were already on 2.3.6, or rooted, or on Rogers, this will work. After the flash, boot the phone normally, wait a minute or so, and shut it down.
Now for the fun part. AT&T will not push the OTA to a non AT&T customer. The flash will also not work with a modified phone (hence the reflash to stock). How to gain root access to manually flash the OTA? If we install root, it will not install. If we install CWM, we will not have the stock recovery which is required to process the OTA. So...
How about this? We install CWM 5. You can find it here http://forum.xda-developers.com/showthread.php?t=1458153
Then we adb into the phone, and push the OTA files, and then reflash the stock recovery over CWM, and then manually reboot into OTA mode. That sounds crazy... crazy enough to work.
After you've flashed CWM, reboot into it and make sure your phone is still connected to your computer. We won't actually be using CWM, just the root access it provides over adb. Unzip the two zip files below (why use external hosting, I can store zips up to 11 MB on here) into a folder and run fota.bat. Ooo and ahh over your Gingerbread.
But what about root? Well, I posted in another thread a complicated method for rooting 2.3.6 using the root access from CWM, but how about easy? Boot your phone into 2.3.6 and let it sit for a minute or so, and shut it down. Reboot into Odin mode, and reflash CWM over the stock recovery (again). Copy the Superuser zip from the folder you made earlier to your SD card. Flash this with CWM. This is the beta of Superuser 3.2, courtesy of Rom Manager. Download the stericson busybox app from the Market if you want busybox as well.
This was a fun way to kill a weekend
Throws a signature verification failed error.
Try again with the new method
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Why go to 2.3.6? It´s better than 2.3.5 customized?
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
AraDreamer said:
Better question: we're getting ICS within the month, so why bother with 2.3.6 when you can just upgrade to 4.x.x when it comes down?
-Ara
Click to expand...
Click to collapse
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
narume said:
Had a few mild scares. After flashing CWM on stock, it refused to boot into it but after 3 tries and my screen acting up upon boot, it finally booted into CWM. Launched the bat file and it went well. Upon booting up and entering the update process, it froze up at 74% and refused to continue. Rebooted the phone and it once again entered the update process and this time it managed to finish. Phone rebooted and after checking "About phone", my phone is on 2.3.6 stock. When you initially provided the OTA files and the sig check failed, I had a good feeling this would be the only other way to do it as I tried to sign it and it also failed. Thanks for taking the time to post all of this.
Click to expand...
Click to collapse
When I was testing this, I saw that behavior if you didn't completely boot up the phone between steps (ie, flash stock firmware, boot phone, flash CWM, boot phone). I don't know what would cause it otherwise. Glad to see your phone made it.
narume said:
Because there are some people who will want to stick with 2.3.5/6 . He made this so that those who do, can update to 2.3.6 even when they aren't with AT&T, almost hassle free.
Click to expand...
Click to collapse
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Nardholio said:
Actually I did it because I've owned this phone for exactly two weeks and discovered all the available ROMs are based on 2.3.5 even though 2.3.6 has been out since December. CWMR with root has been out since January, and since then nobody else has rooted 2.3.6 or found a way to flash it. And I thought, it couldn't be that hard? And even more amazed when I discovered CWMR comes with root out of the box, without even touching /system. The only other missing piece was the stock recovery, which also wasn't out in the wild. 3 birds for one stone
On a side note, if you want to do some cleaning after the OTA and you decide to root, you can delete /cache/fota and /data/fota safely.
Click to expand...
Click to collapse
Ah, I see. Well, still, being able to flash to 2.3.6 is nice because if anyone ever decides to stick with 2.3.6 they can easily flash the update now. Maybe more people like you will pop up and start pushing out more useful content like this for the Glide so it won't be a dead area of development anymore.
Ok, so I am not to sure exactley what I did. I accidental hit unroot in CWM. I have a recent titanium backup, but i suppose that will do me no good. I lost superuser permission to operate Titanium anyway. Also CMW as the app is useless to me now. I can boot into it using the volume down, home power option, but i can not get to anything there to restore it.
Do i need to re-root, or what direction should I be going in? All I am looking for is someone to point me in the proper direction, I feel horrible asking this here, as I normally know what I am doing.
Thanks for your help.
I am back to stock. Not rooted or anything, so there is one problem solved. I would like to OTA update, but it is saying i am up to date, and i am pretty sure 4.1.2 is not up to date. Oh well, im half way there.... i think...
sully42 said:
I am back to stock. Not rooted or anything, so there is one problem solved. I would like to OTA update, but it is saying i am up to date, and i am pretty sure 4.1.2 is not up to date. Oh well, im half way there.... i think...
Click to expand...
Click to collapse
You have options, OTA to 4.3 (just advance time/date 24 hours or whatever time it says to check again) You will have a locked bootloader and Knox *****ing at you if you install root.
Or you can flash this through ODIN or CWM, You get root and 4.3
http://forum.xda-developers.com/showthread.php?t=2589891
dicksteele said:
You have options, OTA to 4.3 (just advance time/date 24 hours or whatever time it says to check again) You will have a locked bootloader and Knox *****ing at you if you install root.
Or you can flash this through ODIN or CWM, You get root and 4.3
http://forum.xda-developers.com/showthread.php?t=2589891
Click to expand...
Click to collapse
Thanks! I got it to OTA to 4.3,I did not think about changing the clock, I ended up booting to CWM and factory resetting, then rebooted and it poped up with in 30 seconds that there was a software update.
I think I will flash that threw oden later. I was mostly freaking out because my phone was stuck between rooted, and not rooted. All sorts of apps where tweeking out on me. 4.3 is nice, but way to much junk installed by ATT.
cell carriers are the worst kind of people.
sully42 said:
Thanks! I got it to OTA to 4.3,I did not think about changing the clock, I ended up booting to CWM and factory resetting, then rebooted and it poped up with in 30 seconds that there was a software update.
I think I will flash that threw oden later. I was mostly freaking out because my phone was stuck between rooted, and not rooted. All sorts of apps where tweeking out on me. 4.3 is nice, but way to much junk installed by ATT.
cell carriers are the worst kind of people.
Click to expand...
Click to collapse
No worries. This just came out yesterday.
http://forum.xda-developers.com/showthread.php?t=2659569
A little of the crap removed. I'm running it, pretty smooth.
I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
ghettovirtuoso said:
I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
Click to expand...
Click to collapse
I'm having a very similar issue. Stock M8 running latest T-mobile firmware. Rooted. Flashed PhilzCWMtouch and now the phone reboots every 1-3 minutes. I flashed the original recovery via fastboot and it is still rebooting. Going to redownload the stock recovery and try flashing it again before I do a full restore. I really want to avoid that if possible.
cheasfridge said:
I'm having a very similar issue. Stock M8 running latest T-mobile firmware. Rooted. Flashed PhilzCWMtouch and now the phone reboots every 1-3 minutes. I flashed the original recovery via fastboot and it is still rebooting. Going to redownload the stock recovery and try flashing it again before I do a full restore. I really want to avoid that if possible.
Click to expand...
Click to collapse
Thanks for the reply, but I gave up last night trying to fix it from the current state. I restored a nandroid from the previous week and used titanium to infuse data into already installed apps and restore missing apps. I do hope you find success in getting your issue to stop. I haven't had problem using TWRP on this phone, maybe give that a try
ghettovirtuoso said:
Thanks for the reply, but I gave up last night trying to fix it from the current state. I restored a nandroid from the previous week and used titanium to infuse data into already installed apps and restore missing apps. I do hope you find success in getting your issue to stop. I haven't had problem using TWRP on this phone, maybe give that a try
Click to expand...
Click to collapse
I finally was able to fix it after flashing twrp and then doing a wipe from there. then updated superSU and everything seems fine now. sorry about the different accounts. I need to delete that other one.
Sent from my HTC One_M8 using Tapatalk
ghettovirtuoso said:
I've had my phone for about two months now without any issues. I have it rooted with the stock rom. Today I was getting a red wifi calling notification. When I finally went to check it, it was error that said cannot start so I turned it off and back on to see if that would resolve anything. Since then my phone has been constantly rebooting. It comes on and stays on for about two minutes before rebooting again. I've been able to reach the settings and turn wifi calling off but that hasn't helped. I want to try to maybe disable the app or whatever runs it and try clearing it's data, so my question finally is does anyone know which app I would be looking for under all apps so I could give that a try.
Click to expand...
Click to collapse
Lemme ask you......... did you root your phone BEFORE or AFTER receiving any OTAs?
I have T-Mobile and the M8 too. I rooted my phone AFTER getting the OTA, and I'm pretty sure that's what caused all hell to break loose. My phone wasn't like yours at first, for weeks it would randomly go into Recovery mode............ but then this past week it started doing that: constantly rebooting. I didn't have a backup that was pre-root, only post-root (rookie mistake lol), so having to replace it now. Using the post-root is just a temporary fix as it can still go back to non-stop reboot at anytime, but the new phone comes in Tuesday.
Please let me know.
Good luck! (Not sure if that's you in the other post that said it's been fixed).
Thank You,
RockStar2005
RockStar2005 said:
Lemme ask you......... did you root your phone BEFORE or AFTER receiving any OTAs?
I have T-Mobile and the M8 too. I rooted my phone AFTER getting the OTA, and I'm pretty sure that's what caused all hell to break loose. My phone wasn't like yours at first, for weeks it would randomly go into Recovery mode............ but then this past week it started doing that: constantly rebooting. I didn't have a backup that was pre-root, only post-root (rookie mistake lol), so having to replace it now. Using the post-root is just a temporary fix as it can still go back to non-stop reboot at anytime, but the new phone comes in Tuesday.
Please let me know.
Good luck! (Not sure if that's you in the other post that said it's been fixed).
Thank You,
RockStar2005
Click to expand...
Click to collapse
I rooted preOTAs. Pretty much as soon I got the phone. I have been unsuccessful in stopping the problem as of yet but am going to RUU in a few minutes. Prior to this I've only tried factory resets from within the OS and from the bootloader wiping everything including data and external sd. Hope this RUU provides me some peace.
ghettovirtuoso said:
I rooted preOTAs. Pretty much as soon I got the phone. I have been unsuccessful in stopping the problem as of yet but am going to RUU in a few minutes. Prior to this I've only tried factory resets from within the OS and from the bootloader wiping everything including data and external sd. Hope this RUU provides me some peace.
Click to expand...
Click to collapse
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
chattguy said:
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
Click to expand...
Click to collapse
I was having the same problems. I'm getting my replacement phone today. My current one is only working (for now) b/c I did a restore, but not far back enough for it to be working 100% right. I'm working with someone who might have a plan, so we'll see. He said he did everything, including root and S-OFF, and got Harman/Kardon sound too (on his non-Sprint phone). I'll post again here when I get more info. First gotta get my replacement phone. lol I had H/K but I think rooting it after the OTA messed it up, but we'll see. H/K did improve the sound, so I really want it back.
RockStar2005
chattguy said:
It almost seems like this (my) phone hates to be rooted. As soon as I restore to pre-root backup, it's fine. I hate not being rooted.
Software No: 1.57.531.7
It did the constant reboot (after about 1 minute of being loaded) with both stock, rooted and with Skydragon 2.3 rom. Very irritating. It seems to happen when I unplug it from the charger or pc, while rebooting.
Click to expand...
Click to collapse
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
ghettovirtuoso said:
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
Click to expand...
Click to collapse
Yeah man, I hope they come up with a fix for it, I don't want to be unrooted forever.
ghettovirtuoso said:
Mine too. I RUU'd back to stock and unlocked bootloader. Before anything else I made a backup. Rooted and the problem presented itself again. Restored backup but chose not to root and my phone has been fine thus far. Never used an android without root so this should be interesting.
Click to expand...
Click to collapse
He's working to help me out. Maybe he can fix your issue too? Still waiting for him to write me a guide for my specific issues, so can't verify anything, but sounds like he's helped a lot of ppl on here already. Check him out:
http://forum.xda-developers.com/showthread.php?t=2718130
Good luck!
RockStar2005
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
chattguy said:
Yeah man, I hope they come up with a fix for it, I don't want to be unrooted forever.
Click to expand...
Click to collapse
He's working to help me out. Maybe he can fix your issue too? Still waiting for him to write me a guide for my specific issues, so can't verify anything, but sounds like he's helped a lot of ppl on here already. Check him out:
http://forum.xda-developers.com/showthread.php?t=2718130
Good luck!
RockStar2005
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
Yes you can go to software number to get the info you need. To do an OTA you need a stock sense ROM (NO CHANGES TO ANY SYSTEM APPS) you then need to flash the correct recovery for your software number and [IMPORTANT] relock the bootloader. You then can reboot into your system and take the OTA while still being able to unlock the bootloader and flash a custom recovery afterwards.
No need to relock the bootloader for an ota. People should stop spreading that info
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
ericksonline said:
Hello all, this is my first post. I'm looking for a little clarification on which stock recovery I should use so I can do OTA updates.
First, a little background. This is the first device that I've ever unlocked and rooted. I did a lot of reading before I started, but sometimes you don't really learn until you get your hands dirty. I started with an AT&T HTC One M8. I used HTCdev to unlock the bootloader, then used TWRP recovery. After that, I used Hasoon2000's All-in-one-toolkit for the Perm Root. All went as expected. I then loaded the Xposed framework and tried a couple of things with it. Suddenly, my phone started re-booting every 30 seconds or so. After panicking a bit, I figured out that there was a problem with the SuperSU. I re-applied that and all has been happy again. Since then, I also tried to obtain S-Off using the firewater method, but it failed with the Whelp message so I still only have S-On. I've now uninstalled the Xposed framework and I want to revert back to a stock recovery so I can do future OTA updates.
When I use getvar all, my version-main is blank. From what I have read, this is a common problem so I'm not worried about it. But, isn't this the number that I need to determine which stock recovery to use? Is this the same number that shows up in the Settings->About->Software information->Software number? Does the cid have any determination in which stock recovery to use?
After I do find the correct stock recovery, it is my understanding that I just flash that back to the device and it should be safe for OTA updates in the future. Is this correct?
Sorry... I'm a little gun shy after my reboot problem and I'm just looking for a little confirmation that I'm understanding things correctly before pulling the trigger again.
Thanks!
Ron
Click to expand...
Click to collapse
ericksonline said:
Thanks for the replies!
Just to check my understanding, since I simply unlocked the bootloader, used the TWRP recovery, added SuperSU, installed then uninstalled Xposed framework, that means that I should still be on a stock sense ROM (with no changes to any system apps), right?
There is a lot to learn with all of this when you are first starting out. I'm reading a lot, but sometimes you do find conflicting information. I'd rather be a little cautious than do something stupid!
Thanks again!
Click to expand...
Click to collapse
Yup you're good ROM wise. Just flash the stock recovery and you should be good to go.
You can be unlock and have OTA.
You just need a stock recovery.
HTC ONE M8 fails to load up after failed software update
Hello guys, this is my first post. I really need your help as I'm at risk of loosing all my phone data. My phone internal memory had been exhausted and I bought an external SD card. I am unable to transfer data to the external SD card. I was doing a software update on my phone that failed to install, there was a warning sign on the phone screen for a few minutes then it try to power on but has failed, as it's seem to stuck on the screen that display htc powered by android. I tried the recovery holding down the power button and the column up button, the phone power off and back on but is still stuck on this screen (htc powered by android). I tried connecting the phone to my laptop to try and recover my data, but it's not mounting to the laptop. Please can someone help me. Thanks in advance.
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
jbarr3 said:
Similar to the post above ie rooted and kept on stock. Also loaded a few Xposed modules but when I connected to my wifi I had over 30 updates so loaded all of them and once loaded the old bootloop started. I restored my nandroid backup from TWRP (this is an essential backup) and I was back in action. Phew!!!! I no longer had Xposed. So I did the updates again and the same thing happened. I am now updating one at a time which is painful when you've got so many. I also tried wiping the caches but that didn't work.
I noticed there were a lot of HTC apps eg HTC sense input, service pack, blinkfeed etc. I also notice a super SU update. ericksonlines post above said he had a problem with superSU. What kind of problem? What does he mean by reapplying? Flashing from TWRP?
So the big question. Which app(s) update did the damage???
Any apps I shouldn't update eg HTCs?
Has this happened to anyone else? What did you then do? Is the new updated superSU the problem
Apologies for cross posting on an Australian site but I'm a bit frazzled with all of this.
Click to expand...
Click to collapse
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
ericksonline said:
Hello! It is possible that an update came through that caused my phone to start into the boot loop. I'm not sure because it worked fine for a few hours before the problem started happening all of the sudden. My guess is that something updated that broke SuperSU. As soon as something would try to use SuperSU (or maybe the rights granted by SuperSU), the phone would crash and reboot. To fix the problem, I rebooted into the bootloader (TWRP) and re-installed SuperSU from there. After I re-installed, everything began working nicely again. I have not had a problem since and the problem occurred a few months ago now. I have also recently updated to the new version of SuperSU with no problems at all.
I hope this helps!
Ron
Click to expand...
Click to collapse
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
jbarr3 said:
You're dead right Ron. Supersu was the culprit. Just simply updating from the playstore caused this. I restored an android backup which got me back. I went into the old SuperSu (V1.94) and clicked "clean up when updating from google play" or similar, did the update again (v 2.04 from google) and while this didn't cause rebooting, I couldn't install the binary. I chose "normal" (maybe I should have chosen TWRP) and it didn't work. So I flashed my old v1.94 from TWRP and that got me back. So some questions on updating SuperSu.
1. Is flashing the zip file through TWRP the best way to install a new version?
2. Should I delete or uninstall the old version or will flashing do that for me? Did you simply flash over the top of the other one?
3. Should I stick with 1.94, which works, or should I update to a new and improved version?
4. I think 2.16 is the latest. What version are you running, is it stable and do you recommend it ?
5. I assume I get the zip file from chainfire. They are way ahead of the google playstore for updates
Click to expand...
Click to collapse
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
ericksonline said:
I'm no expert, but I'm happy to share my experience. I do believe that flashing from TWRP is the best way to install. That is what I did to fix my reboot problems. I don't recall uninstalling the previous version in any way. I think the old file was still on there. I browsed to it in TWRP and installed it. I'm not sure what version I was on when I did this. Recently, a new update (2.16) was available that downloaded through the Play Store. When I went to update, it recommended that I use TWRP to install. I didn't go this route because I had already switched back to the default bootloader and didn't want to reinstall TWRP if I didn't have to. So, I just used the "normal" method. It updated successfully and I've had no problems. I am now running 2.16.
Click to expand...
Click to collapse
Thanks erick but given what's happened I don't think I'll ever update from the playstore again. I'll load 2.16 using TWRP and report back. I can't stress enough how important it is to have a nandroid backup. I reckon its the best reason to load a custom recovery. Its got me out of trouble twice now and gives me piece of mind. I've actually gone overboard on this and I have two backups on my phone which I have copied to my PC..
vm54 said:
You can be unlock and have OTA.
You just need a stock recovery.
Click to expand...
Click to collapse
And stock ROM.
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
jbarr3 said:
Updated to v 2.16. Piece of cake!!!
Loaded through TWRP, rebooted and that was it. It didn't even ask about installing the binary. Same binary I guess.
It worried me, however, when I saw over 700 pages on this version xda. Most with problems.
Click to expand...
Click to collapse
Awesome! I'm glad to hear that it worked!