A colleague of mine has an incredible that every few days reboots into a continuous boot loop. It takes removing the battery for it to boot normally, and then a few days later it does it again.
He has tried a reset, and it doesn't fix the problem. This is an unhacked unrooted stock Incredible with what ever updates came from Verizon/HTC over the air.
I'm wondering if it would help to reflash it to virgin stock in case something is corrupted. In fact its also possible that one of the HTC updates caused the problems, since it seems to have started about the time of an update.
I have a Samsung phone and am familiar with the procedure for Samsung (Kies, Odin, etc) but don't know what to tell him about HTC.
What is the procedure for reflashing to stock, and perhaps selecting a stock version older than the latest for HTC phones?
kmandel said:
A colleague of mine has an incredible that every few days reboots into a continuous boot loop. It takes removing the battery for it to boot normally, and then a few days later it does it again.
He has tried a reset, and it doesn't fix the problem. This is an unhacked unrooted stock Incredible with what ever updates came from Verizon/HTC over the air.
I'm wondering if it would help to reflash it to virgin stock in case something is corrupted. In fact its also possible that one of the HTC updates caused the problems, since it seems to have started about the time of an update.
I have a Samsung phone and am familiar with the procedure for Samsung (Kies, Odin, etc) but don't know what to tell him about HTC.
What is the procedure for reflashing to stock, and perhaps selecting a stock version older than the latest for HTC phones?
Click to expand...
Click to collapse
You can reflash the phone to stock with what incredible users call an ruu (rom update utility), however flashing older versions or downgrading the os is not allowed with s-on (security on). His best bet in my opinion would be to root and s-off the phone, and then flash a custom rom. However if hes not into all of that he can try to do an ruu and see if it fixes things. Doing so will wipe the phone compleetly and he will loose all of his apps and data. A pc running windows xp or newer is required.
1. Download the ruu http://dinc.does-it.net/Stock_Image...0_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, and place it somewhere on your pc.
2. Download and install HTC Sync http://dinc.does-it.net/HTC-Sync/3.0.5606/setup_3.0.5606.exe.
3. On the phone go to menu - settings - applications, uncheck fastboot if it is checked and then select development, and make sure usb debugging is checked.
4. Connect the phone to the pc with the usb cable, and wait for any drivers to install on the pc. The phone should be in charge only mode.
5. On the pc run the ruu file and follow the instructions it gives you.
If all goes well the phone will be like it just came from the factory. If doing all of this is to technical for him he can take it into a verizon store and they will do it for him at little or no charge.
cmlusco said:
If all goes well the phone will be like it just came from the factory. If doing all of this is to technical for him he can take it into a verizon store and they will do it for him at little or no charge.
Click to expand...
Click to collapse
Well not like it came from the factory originally. That would be Froyo, and this procedure would presumably get the last official (and maybe problem some Gingerbread). Is that right?
Also, I'm surprised to hear that a Verizon store could do a flash. My only experience is with T-mobile and they can't do any better than use the "factory reset" menu that just clears settings.
kmandel said:
Well not like it came from the factory originally. That would be Froyo, and this procedure would presumably get the last official (and maybe problem some Gingerbread). Is that right?
Also, I'm surprised to hear that a Verizon store could do a flash. My only experience is with T-mobile and they can't do any better than use the "factory reset" menu that just clears settings.
Click to expand...
Click to collapse
Well not like it originally came from the factory 2 years ago (with froyo), but if they were still selling them today or you get a replacement, that is how it would come from the factory. The last update 4.08.605.2 fixed all the major issues and shouldnt give any major trouble. The only other option would be to root.
Verizion is pretty good with customer service, you may have to find a knowledgable employee but they can do it for you.
We tried the "ruu" approach without success. The drivers installed on the PC, the phone goes into debug mode, and we can even run "adb" manually and talk to the phone. However, when either "ruu" or "Ht Sync" try to talk to the phone they just say the phone is not connected.
If we run the task manager on windows we can actually see "ruu" invoking "adb" and there is no long timeout. It appears that ruu just doesn't like the answers.
Again running adb manually for example with the shell option seems to do all you expect adb to do. This is with both the versions linked above and the updates they end up offering.
Any ideas?
OK, found a mistake. I didn't realize that to do the ruu flash I needed to turn off the phone and vol-down/power it into htboot mode.
With that done the update program sees the phone notices it has lastest firmware and offers to update it to the same version. I say yes, and the phone reboots and the PC tells me it will take 10 minutes to flash, then 2 seconds later tells me it succeeded and the phone reboots.
Obviously it did not flash anything. Am I missing something?
Also any pointers on how to flash an earlier stock rom (and where to find it)?
Related
i get a "can't connect to phone" error and a black screen with silver HTC letters on it on the screen of my phone when trying to flash the latest stock RUU. this is after the updater reboots the phone to try and flash.
i ran some root technique a couple days after i got my EVO (stood in line @ 5:30am to boot!). don't remember what it was though. toasts orig root i guess.
then it ran that sd card update (which didn't work for me). dunno if any of this matters, but wanted to provide back story.
why can't i flash??
Well depending on if you installed todays OTA update somehow changes my answer to your question.
For one if you did not install todays OTA update then the problem you are having is very commen and easily fixed. You'll notice that after it tells you there is no connection your phone should still be at the black screen with htc's logo. Without disconnecting or restarting your phone relaunch the RUU and go through it again. You should notice it will actually work the second time and eventually youll get a progress bar on your pc and eventually on the phone. This I am 90% certain should fix your problem. I've used the RUU numerous times and that has become standard procedure, although I don't understand why.
This will unroot your phone meaning you can then run unrooted or its now presentable if you have reason to take it in for replacement/warrenty issues.
But be warned! If you go back to stock in order to receive todays OTA update you will not be able to root your phone again using any current methods or files. Youll receive an error about the file being older than the new and wont be able to even partial root let alone get nand access.
On my end I unrooted today to test out the new features knowing full well I wouldn't be able to root again with the update installed. I figured I'd be able to use the RUU like you are because when it unroots a phone it takes it back to the default software from the day the phone was release but it was my luck that for whatever reason this new update effs up trying to use the RUU.
Is there a way to restore to factory settings that won't have the update installed or is it like how the 3GS was and once you upgrade thats it
Try flashing directly from the sd card, link is in my sig '(un)root'
-------------------------------------
Sent from my god phone.
aaaahhh. there it goes. thanks.
actually it was more i was having sd-card issues still. kept unmounting. rather happy w/ how the EVO works for now so rooting/modding isn't a priority. figured i'd reflash to see if it fixed the sd issue.
thanks!
Guys,
My Evo says Froyo 2.2 is avail for download when I check HTC Updates... I hit accept, it downloads, then asks if I want to install NOW... I HIT YES, and it takes me to the boot loader page, THEN DOES NOTHING.. It doesn't boot into recovery mode like it is supposed to, and it just sits on the Boot loader screen, NO TRIANGLE, NO BAR on the bottom showing the progress, IT JUST SITS THERE on the boot loader page with the 3 Androids on the bottom... I have already tried to hard reset the phone, BUT that didn't work... PLEASE HELP !!! Is there a way to HARD reset my EVO BACK to BEFORE ALL OF THE UPDATES??? IS THERE A WAY TO Force boot into recovery to apply the "update.zip" ??? Please advise...
Mine did'nt go no where near the bootloader screen...
I hit the download...then it just installed like any other app...except it brought me to a bar progress page a couple of times. Then the phone rebooted and whala...froyo.
I must say this...I was previosly rooted but unrooted to do it!!!
Are you rooted or unrooted to start off with?
Was rooted, but then I did the "update of June 29th" and ruined ALL of my fun... Is there even a way for me to root my phone now??? How do I get it to go into recovery?
Same issue
My EVO ISN'T ROOTED, and I'm having the same exact problem
You're hosed root wise until someone cracks the rom, if they crack the rom. Most likely you'll need to update to the official version once HTC releases an upgrade as they claimed they would eventually do on Twitter.
im not trying to root my phone, i just want froyo
right, I WAS rooted, the update in JUNE fixed that for me =(... NOW I just want FROYO which is available from Sprint/HTC OTA, it just wont install?????????? I think I can install it as an update.zip if I could get my phone into RECOVERY mode... When at the bootloader, if I hit Recovery, it just boots back to the BOOT LOADER????
I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
This is the route I took and was just like you...I had no probs this way!
This is a great recommendation, but I haven't done any ROOT or ROMing to my phone since I've owned it, I've stayed true to the true image they released, and I'm not comfortable downgrading it to some other image that wasn't on the phone. I attempted to do the instructions outlined and I was unable to get pas the stage of pushing the:
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
to the phone. It says USB error, and I have debugging mode enabled.
cardiox said:
I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/19278-how-unroot-return-stock.html
This is the route I took and was just like you...I had no probs this way!
Click to expand...
Click to collapse
I RE-Loaded this version, as the other "older" versions would not work (re-loaded, as this is what I already HAD on my phone)... It wiped the system, and ALL of my info/apps (make sure you back up) and then I was able to do the Froyo Update... YES !!!! Thanks...
http://shipped-roms.com/shipped/Sup...51.1_Radio_2.05.00.06.10_release_CL195459.exe
I did the same, thank you !
No prob...have fun!!!
Froyo Update Won't Install
To start off - I have never rooted my evo - my phone is running Android 2.1 update 1 supersonic - and I did not try to do the "pre-release" update put out by HTC. Since late last night, I have been trying to install Froyo through system updates (settings, system updates, htc software update). I am able to download the upgrade, which is about 80 MB, but for some reason the update will not install. When I click install now, my phone restarts in the bootloader. If I click on fastboot, it searches for an image on my SD card but can't find one. If I hit recovery, it just returns me to the main bootloader screen. The only thing I can do is reboot or shut down my phone. When my phone boots back up, it says the update is downloaded and ready to be installed. I have tried redownloading the update but the same thing happens. Any help would be appreciated, preferable without losing contacts and apps. I'm trying to save a factory reset for a last resort.
Thanks,
Nick
Nick,
Please read the earlier posts, and follow the link from Cardiox... He said the following...
"I would suggest using this unroot program and make sure you use the 1.47 one because there are 3 different roms. This is what I did as I had the june update as you. This will guarantee that you have the right stock rom and are not rooted. Then try the update again...
http://forum.androidcentral.com/htc-...urn-stock.html
This is the route I took and was just like you...I had no probs this way!"
Then read my posts, and you will see that I had the SAME problem you are having, and this worked for me... I posted the thread... It is pretty easy if you follow the instructions... Let me know if it works for you... Good luck !!!
wolverinexc said:
To start off - I have never rooted my evo - my phone is running Android 2.1 update 1 supersonic - and I did not try to do the "pre-release" update put out by HTC. Since late last night, I have been trying to install Froyo through system updates (settings, system updates, htc software update). I am able to download the upgrade, which is about 80 MB, but for some reason the update will not install. When I click install now, my phone restarts in the bootloader. If I click on fastboot, it searches for an image on my SD card but can't find one. If I hit recovery, it just returns me to the main bootloader screen. The only thing I can do is reboot or shut down my phone. When my phone boots back up, it says the update is downloaded and ready to be installed. I have tried redownloading the update but the same thing happens. Any help would be appreciated, preferable without losing contacts and apps. I'm trying to save a factory reset for a last resort.
Thanks,
Nick
Click to expand...
Click to collapse
I am not a genius by no means thus I am only sharing info that I have from personal trial and error. If you are going to a bootloader screen during this update process and your SD card is mounted then you most likely will need to bite the bullet and either do a factory reset or follow the link instructions so given. For some reason this update can not find the original factory code or RUU that it is trying to update. Sounds like your SD card is mounted but it can't find it...I would strongly consider just starting over with that link program. It does not root you it just puts you back square one with factory code. Then the update will have something to build off of...which you apparently don't have for whatever reason.
Ok, this is what I needed to know. I'm backing up my stuff with bitpim and will just do this. Thanks for all the help and the speedy responses!
-Nick
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.
Hey guys,
First off, I've searched far and wide for any help with my problem but it is such a peculiar situation that I have yet to find someone with a similar situation. I expect if I want to ever use my M8 again, I'll need to send it to HTC and pay a few hundred bucks to fix it. But maybe someone here will have an idea that I've missed.
Shortly after getting my M8, I unlocked my device, rooted it and installed a few roms. Everything was fine save for one major thing: no matter which PC I used (and I used MANY - 3 different windows destops, a windows desktop at the office and my Macbook Pro) the device was never able to mount and make the storage accessible. I knew at that point something at some point had gone wrong. I've long preferred to use a wireless file transfer app to send stuff to and from my phone so I wouldn't have to break out all my cables so I figured it wouldn't be a big deal. I'd make it work.
A few days ago, I decided to try a different rom than what I'd been using for months (HD Revolution - great rom!) and downloaded everything required. I booted to TWRP, wiped the usual stuff and flashed my rom. When I rebooted, I was continually met with a crash as soon as the phone started and was never able to get into the OS. No big deal - this has happened before with other devices, so I didn't sweat it. I simply powered down the phone and tried to get back to recovery. Here's where the problem really kicked in : when attempting to boot to recovery, my phone will bring up the Hboot screen but instantly try to select the first option, thus not allowing me to scroll down to "Recovery". No matter what I do, it brings up the white Hboot screen, automatically selects the first option, gives me some error (I'm at work so I don't have the device in front of me) and tries to boot to the OS. That takes us back to the automatic crash.
Now, I know usually the solution would involve USB and ADB, but like I mentioned at the start of my sad tale, connecting my phone to PC's results either in nothing (Mac) or a "the device has failed" message in Windows. I've tried removing all the phone drivers, reinstalling and using a few toolkit methods - the phone is just never ever detected.
So, that's it. I'm pretty much resigned to sending my phone in and the HTC folks quoted me about $200. I do have a functional phone at the moment so it isn't the worst situation in the world, but if I could fix this I'd be able to using it as my main device again or sell it for a good chunk of change - I just bought it in June.
Sorry for the long read!
As far as the storage issue, never seen that happen before so I'm not sure. When you plug it in to the computer does the phone ask if you want to connect it as a storage device etc?
The bootloader is a very peculiar problem. It almost sounds like you have an img file that its trying to read as soon as you boot into boot loader.
Try to install HTC sync. And make sure the computer has an internet connection when you plug it in via usb.
Try to flash stock recovery fw buddy
Maybe thats problem RUU
Cek mike blg to find all stock recovery fw
After that install custom recovery again
This sounds a little familiar.
In my experience I've found some firmware versions and ROMs very choppy.
I once had a problem with storage too, couldn't send anything over to my phone.
Fortunately I could access recovery, so used ADB sideload and installed another ROM. And went to another firmware and never looked back.
The last 401.6 firmware gave me all sorts of issue.
If you can access fastboot I'd also recommend new firmware 401.7 is working flawlessly for me with ARHD 21.
Sent from my HTC One_M8 using XDA Free mobile app
I would try putting one of the bootable ruus on your SD card so when it goes to your hboot, it'll read the RUU and install it
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Xavierc123 said:
Awesome, some interesting suggestions here. Would I be able to somehow update the firmware via an SD card without any input from a computer? I managed to get into Recovery last night somehow (maybe letting the battery totally drain and charging it for a while did something) but plugging in my phone when in recovery still won't mount the storage or be recognized by ADB. Would I somehow be able update my firmware from recovery without the need of ADB'ing from my desktop? I've been looking at ROM threads and stuff and noticed that almost every rom requires new firmware or WiFI/radios other stuff won't work....
I'm at work right now so I'll definitely research this in depth when I get home, but if you guys could guide me in the right direction, I'd really appreciate it and maybe buy ya' a beer.
Click to expand...
Click to collapse
Download a rom that can use the 2.xx firmware. Look around and you should be able to find the roms. There's still plenty out there. Here's a little suggestion, reflash TWRP (or other recovery) through fastboot than grab a SD card and place the rom into the SD card and install the rom using through the use of a SD card. Just remember to do a full wipe before that
I've had my M8 since about the end of 2014. Originally on Android 4, have since done OTA upgrades to 5 and 6 as they were flagged as available by my carrier (UK, O2).
I've never managed to get HTC Backup on my PC to recognise the phone, even with the original USB cable, so have never done a proper backup (Yes. I know). Fortunately for me, my Gmail contacts list was almost up to date, and apart from my calendar, that was the most important thing to save, so I've just had to grin and bear it.
Because of the lack of proper backup and therefore the facility to restore from one, I'd never done a factory reset after the various OS upgrades, which I've been told might have avoided my present situation, which is that I can't get any further than a bootloop situation. Other than that, I can get into recovery mode, but no further.
I've tried clearing the cache, I've tried a factory reset. Neither of those have got me anywhere.
I've no great desire (at present) to go fiddling with rooting or anything clever with the phone, I'd just like to get it working again. I've downloaded Android Studio to get the SDK for ADB but don't really know what I'm doing, and if I mess around without expert advice I could end up with a hard brick - which is why I'm here.
Can anyone give me some guidance about what I need to do to get my phone working again?
Thanks in advance...
Hi, I have the same problem, started a few days ago when I was trying to download VLC from the play store, the phone rebooted and said optimizing apps.... It has been in an optimizing apps bootloop since - it gets to the end, then says starting android then freezes and reboots, then starts again... I tried clearing the cache and doing the factory reset as well but nothing helps. We could really use some expert help on this :S
If a stock phone isn't booting, and factory reset doesn't help, the OS is possibly damaged or corrupted in some way; and needs to be restored.
If your version has RUU, you can try to run that.
If no RUU for your version, then probably your only choice is to unlock the bootloader, install custom recovery, so you can restore a stock TWRP backup from the following thread: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I am in a very similar situation, apparently because of a botched automatic system update, almost same symptoms as airick94. I haven't tried a factory reset yet though, because I want to try to recover what I can from the internal storage first. Can I do that through ADB even if my phone is not recognised as a device by the computer?