[Q] 12 Hours of Froyo Hell!! - Android Q&A, Help & Troubleshooting

Evening all,
I have been advised to post here on XDA from Android Forums. This is a copy of my initial post on there to explain the background to my issue.....
Hi there,
I have HTC Desire from O2 and after 12 hours of online searching and tweaking I'm hoping someone may be able to help.
I received the OTA upgrade yesterday which I accepted because I thought O2 might have it sorted by now. Obviously not. Anyway update ran with no interruption but then rebooted to a frozen O2 screen.
I searched the net and eventually found the guide to update the phone using the RUU Rom. I followed this to the letter and the installer for the RUU wouldnt't open. I then realised that Google Chrome hadn't fully downloaded the file (113mb not 171mb). I then used a download manager to ensure I had the full file. It then ran and seemed to be working... until 80% in when I get ERROR 110 File Open.... please use a complete RUU. I downloaded it several more times in various ways but still same result. By this point my phone was pretty much bricked.
I had black screen with silver HTC logo in the middle and 4 exclamation marks in the corners.... this remained whilst the phone was plugged in and the buttons in any combination did nothing. When i removed the USB cable i got a white boot screen with RUU highlighted in orange and again.... buttons do nothing. Every time I ran the RUU file it brought up a green bar as if it was making progress but then errors at the same point every time. (Error 110 use complete RUU... file seems to be complete now at 171mb)
I tried it on two computers, one win7 and the other vista. The vista machine doesn't even see the phone, it gives a USB error before the update begins.
At 2am I used the SDK download and typed the following at command prompt.... "fastboot oem boot".... phone instantly boots into O2 Froyo and works fine. If i then unplug the phone, turn it off and on again.... i get the black HTC screen again, back to square one.
At the moment I have fastbooted it so its working and have used the goldcard tool to obtain the CID and created the .img file.
I don't know what to do from here!!.... the update obviously hasn't FULLY worked but it must have completed enough for the thing to fastboot and seems to have full functionality (calls, wireless, network etc)
I don't really want to void the warranty but O2's only option is to send it off for 14 days to have an engineer tell me its buggered and send a replacement.
Any advice is appreciated.
Rich.
A couple of helpful guys on there have tried to advise me but without success. They suggested rooting etc but here is my problem.....
At the moment the phone seems to be working fine with Froyo... but the only way I can get my phone to start up is by plugging in and running "fastboot oem boot" from command prompt. If my phone is powered off and I turn it on in the normal way, I get the black screen with silver 'HTC' and triangles in 4 corners and all buttons do nothing!
I have tried fastboot command whilst holding down the volume keys etc and it just boots normally. Obviously something isn't right and I can't let my battery run down otherwise its useless until I can fastboot it again.
So this is preventing me from accessing any of the menu's required in the flash/root tutorials.
Can anyone help or do I just need to ensure I don't run the battery down?!?
Thanks in advance
Rich

if you have a goldcard already, have you tried flashing a diffrent ruu from fastboot? maybe just a generic htc one rather than the o2 one?

Hi,
Thanks for your reply.
Could you advise me which RUU would be the best to use?
I have looked through the list on shipped-roms website but apart from the obvious O2 ones, I don't understand which ones are which!
Thanks
Rich

Hi Rich,
I have exactly the same problem. Have you got any feedback about whether you have solved this issue?
Thanks!
Kelk
Edit:
I think I may have got it sorted. Downgrade to 2.1 as per:
hxxp://forum.xda-developers.com/showthread.php?t=768256
(replace xx to tt in link above)

Hi there,
I haven't solved my issue yet. At the moment I am using my phone on 2.2 but trying not let the battery run flat (I have to use fastboot from command prompt to get my phone to boot up)
Did the tutorial above work for you?
My issue is getting a working goldcard. I'm not sure whether mine has worked succesfully because when i've tried running the RUU of either the unbranded froyo update or even the O2 original, i get and error message and it doesn't work.
I followed the goldcard creation tutorial but I still get the CID error when trying to run the various RUU files.
I hope I can sort this soon because i've been close to throwing my phone out of the window several times!!
Cheers
Rich

Hi Rich,
Yes, the above tutorial worked for me. I think this is because it downgrades to a former version of HBOOT.

rich0684 said:
Hi there,
I haven't solved my issue yet. At the moment I am using my phone on 2.2 but trying not let the battery run flat (I have to use fastboot from command prompt to get my phone to boot up)
Did the tutorial above work for you?
My issue is getting a working goldcard. I'm not sure whether mine has worked succesfully because when i've tried running the RUU of either the unbranded froyo update or even the O2 original, i get and error message and it doesn't work.
I followed the goldcard creation tutorial but I still get the CID error when trying to run the various RUU files.
I hope I can sort this soon because i've been close to throwing my phone out of the window several times!!
Cheers
Rich
Click to expand...
Click to collapse
Use Goldcard + your shipped o2 ROM (ROM that came originally with ur phone 1st time). you can get the rom from HTC official website. enter your Serial Number t download (i recommend using Mozilla built in download manager, coz Google Chrome always give me Corrupted Download when downloading Large files)

Related

Flashing Issues

I recently flashed to the new AT&T Test ROM 5.08. Basically I want to flash an energy rom over the AT&T and am having issues. Any rom I try to flash will go the gray loading screen on the phone and then hang up and gives the error 260 connection lost. I tried running the Raphael custom RUU before flashing the energy rom and I get an error 240 trying to run the custom ruu. I tried running the raphael unsigned hardspl and that only takes me to the black screen. From the black screen I've tried running the custom ruu and energy rom and nothing happens. Can anyone help me because I'm tired of this rom and I can't get anywhere!
Power off your device, hold the Volume Down button (keep hodling it), turn the device back on.
You should see the TriColor BootLoader screen; it should halt with USB or SERIAL displayed on the bottom white portion of the screen. Note the information that appears on the screen and post the details. To return to normal device operation, remove the battery for 30 seconds and put it back in.
That should assist us in determining the next steps.
HTH,
Screen appears:
RAPH110
SPL-5.08.0000
PSOC-Raph STAGE-CVT V0x36
PCBID 0x00
RID 0x0
Serial
It would appear that the HardSPL did not "take" or hasn't been applied yet. Here's the link to the HardSPL thread and Wiki page:
http://forum.xda-developers.com/showthread.php?t=410150
http://wiki.xda-developers.com/index.php?pagename=Raphael_HardSPL
Once the HardSPL is applied, you should be able to flash custom ROM's to your device. If you need a "refresher" on flashing, have a look at this thread:
http://forum.xda-developers.com/showthread.php?t=448008
Lastly, although optional, you may want to consider performing a SIM unlock.
HTH,
It freezes the phone on the gray loading screen when trying to hardspl and then gives the 260 error code connection lost. I followed all the guides and nothing works (hence the point of starting the thread in the first place). I am a noob, but not a complete idiot that can't read guides. I understand if I can't hardspl, then I can't flash a rom. Well the hardspl does not work for me! I have tried the unsigned version which freezes the phone loses connection. I've tried the raphael wrapper which only takes me to the black screen and gives the error 240. From the black screen I cannot run spl or roms. I tried running stock spl's. I don't understand how the Test ROM flashed fine and now I can't flash anything.
The test rom worked fine because you don't need hard spl to flash it; it matched the carried id of your phone (CID). Hard spl CID-unlocks your phone, so you can flash non-ATT roms.
You should never try to flash a custom rom without hard spl. In the best case scenario, you'll be stonewalled. You need to use the wrapper that comes with the hard spl package to flash hard spl. Using any other wrapper is a waste of time. It says this clearly in the hard spl thread, where you should have posted your question. If you read the last 50 or so posts of that thread, you'll come across a post by Captain Throwback. He had some problems flashing H-spl, and he found some tricks to get it going. I suggest that you search the thread for his how-to. My guess is that you're forgetting something obvious, like turning off your anti-virus software or installing net framework 3.5 on your pc (if it isn't already there). You have to flash hard spl off of your pc, so don't even bother trying to flash it off your sd card. It's probably easier to do it off of XP than Vista.
I already tried the raphael wrapper as I stated twice. Raphael wrapper takes me to the black screen (where I read about the post by captain throwback). I followed everyones instructions that got it to work and still the same thing happens. The Wrapper only takes me to the black screen where I cannot do anything because the computer isn't synced with my Fuze and will not. Then the error 260 message comes up saying that there is no connection. Hence the point the wrapper won't work even with xp, antivirus turned off and 3.7 framework (even tried going back to 3.5 and same thing). I even tried doing everything at home on my vista notebook and the same things happen.
I already tried the raphael wrapper as I stated twice. Raphael wrapper takes me to the black screen (where I read about the post by captain throwback). I followed everyones instructions that got it to work and still the same thing happens. The Wrapper only takes me to the black screen where I cannot do anything because the computer isn't synced with my Fuze and will not. Then the error 260 message comes up saying that there is no connection. Hence the point the wrapper won't work even with xp, antivirus turned off and 3.7 framework (even tried going back to 3.5 and same thing). I even tried doing everything at home on my vista notebook and the same things happen.
Few questions:
1) Under usual conditions, does the device establish a connection via ActiveSync?
2) Does the problem occur in a new user profile /w Admin priviledges on your XP workstation where you establish a Guest connection via ActiveSync to the device?
3) Have you tried a Hard Reset on your device prior to flashing HardSPL?
4) Have you removed the SIM and any SD Card for the time being?
5) Are you able to successfully flash a non-test version of an official AT&T ROM to your device?
1. Yes alot. Only use it for transferring files and battery charging.
2. No, registered device in activesync with full administrative rights to my workstation. I don't have any problems with losing connection during file transfer, etc.
3. Yes, did a hard reset a couple weeks ago and same thing. Possibly going to try it today again because I installed a couple programs before attempting hardspl the last time.
4. I take them out when trying to flash
5. No, I'm stuck with the AT&T Test ROM. Have tried ones on here that are supposed to be stock AT&T ROMs and the same thing happens.
Your response to #5 concerns me; just to make sure I understand ... you are unable to flash an official ROM to your device?
Here's the link to the latest official AT&T FUZE ROM:
http://www.htc.com/us/SupportDownload.aspx?p_id=198&cat=2&dl_id=553
Springboard URL: http://www.wireless.att.com/answer-center/main.jsp?t=solutionTab&solutionId=KB95876
Download the ROM and try flashing it to your device; if it fails ... time to call AT&T, you have a problem with your device.
HTH,
bratch15 said:
Hence the point the wrapper won't work even with xp, antivirus turned off and 3.7 framework (even tried going back to 3.5 and same thing). I even tried doing everything at home on my vista notebook and the same things happen.
Click to expand...
Click to collapse
Is there a net framework 3.7 for pc's? Or are you talking about your phone? You need net framework 3.5 on your pc to run the flash. It won't work with 2.0. It doesn't matter which compact framework you have on the phone.
Did you already try putting your phone in Bootloader mode, and then connecting it to your PC? Does it load the Qualcomm CDMA Technologies/HTC/Pocket PC USB Sync driver? Did you make sure the SIM and SD cards were removed from your device? FYI - You HAVE to use the RUU that comes with HardSPL in order for it to flash successfully. If you've verified that your computer has installed the drivers, and then been unable to successfully complete HardSPL, I'm not sure what to tell you. Do you press "yes" on the Device when running the HardSPL RUU & you're prompted to run the program?
Those are all the suggestions I have.
Last night as I was driving home my phone kept disconnecting as it was charging. I finally found the answer! First time it ever did that. So its back to AT&T for a new one. Probably should have mentioned that the phone was submerged in the toilet (thank god before the #2) a couple months ago. The phone went crazy and started saying error messages with email and then lines going thru it. But after a couple days of drying it worked fine again.
THREAD CLOSED!!!!!
Always wanted to say that
bratch15 said:
THREAD CLOSED!!!!!
Click to expand...
Click to collapse
If you say so...

? Device not booting - flash rom without running windows mobile?

Hi all,
I've got a problem with my hermes phone which I can't solve by my own I think :
My device gets stucked while booting. It just shows a "htc smart mobility" screen and displays the various red numbers on the bottom for some seconds (as usual I think). But it's not going any further (waited for about 20 minutes).
I flashed the "Hermes.DarkVisions.v5.17.23017.Manila" rom over my exisisting "Schap's 4.22" rom a few hours before. The rom was running good. Then I executed the "kill em all" app by mistake, which can be found in the accessory folder as far as I can remember. Then the phone began to work very slowly so I decided to restart it. And now its not really working any more.
By connecting the phone with my pc and trying to flash a new rom, I get the RUU Error "200 INVALID UPDATE TOOL" - what does this mean? The auto detection of the current bootloader obviously doesn't work due to no running windows mobile.
Is there any chance to flash the phone without a running windows mobile? Or what else can I do to get the current rom "Dark Visions" running again?
Thanks a lot for your help,
Michael
Press The Power, The ok button (usually found on the left side) and The reset button using your pen until this rainbow coloured thing comes up.
Plug it into your USB and then reflash your ROM, also don't forget to upgrade your radio as you will need it to stabilize your custom ROM which you will find under wiki part of this forum. Just search "Hermes Radio" and click the first thing you see.
Now your device should be back to life again.
OK, so I've been reading the Common Upgrade Problems on the wiki, and I saw this:
Important : Windows VISTA users need to make a change to their system to successfully use many ROM packages. See Mr. Vanx's guide here.
Click to expand...
Click to collapse
Since Mr.Vanx's website was taken down, I ask you what are the changes i need to perform and if I need to apply them to Windows 7.
Best wishes!
Any help in here?
Please, i have the same trouble. I didn't work with Windows 7. Does Anyone know a solution?

[A] ruu error 110

I was attempting to install the stock radio for my htc evo 3D gsm on Rogers network. I had the right exe file and ran it on my computer and started the update. Everything worked until the last ~5% when it said image writing error and now my phone will only show the htc symbol with exclamation marks in all four corners. Please help me out here! I just got this phone
EDIT: this problem has been solved thanks to il dice and his possy. I shall now attempt to recall the steps to fix ruu error 110 on the evo 3D gsm
When your phone has the above problems (ruu failiure resulting in a black HTC screen with exclamations in all four corners) you need to:
1-make sure it is charged
2-plug it into a computer on which you have the android SDK or at least fastboot.
3-Hopefully you have a nandroid back up that you can pull off of your sd, put the recovery.IMG and boot.IMG from your back up in the same folder as fastboot.exe.
4-open up a command prompt and point it to the folder with all the goodies in it (cd *path to folder*)
5-type these commands into the computer:
fastboot flash recovery recovery.img
Fastboot boot recovery.img
6-If all goes as planned your phone will boot into recovery (clockworkmod, or whatever you had with your backup), from there you need to wipe. (LOLilduce)
7-select wipe data/factory reset, wipe cache and wipe dalvik
8-now you can flash a Rom from your sd card, so go ahead and do so
9-don't reboot from recovery, in my situation it just brings you back to the ruu error, erasing all your previous work. Instead type in the computer fastboot oem boot.
I do believe those are all the steps you need to take to get your phone back up and running.
Update: re running the ruu is how I fixed my phone, yet I had to use another computer. If this happens to you, download the ruu again and try it on a different machine.
CAUTION: Every time your phone turns off, you probably will have to do these steps again. I am working on a fix for this hopefully with the help of il duce again.
Update: re running the ruu is how I fixed my phone, yet I had to use another computer. If this happens to you, download the ruu again and try it on a different machine. My phone is now working completely fine.
Please leave comments if this helped you out. I know there isn't much info on this error because I couldn't find any.
Cheers!
jverm said:
I was attempting to install the stock radio for my htc evo 3D gsm on Rogers network. I had the right exe file and ran it on my computer and started the update. Everything worked until the last ~5% when it said image writing error and now my phone will only show the htc symbol with exclamation marks in all four corners. Please help me out here! I just got this phone
Click to expand...
Click to collapse
Have you tried to Boot into Recovery? If you Can't get into Recovery, see if you can get to Fastboot...
Nothing. Power and volume button only bring up the error screen.
Let the phone charge a few hours and try to run the .exe again.
Locked & Loaded
""shooter on Deck""
Most likely your briked if you where messing with the radios something ill never do
Sent from my PG86100 using xda premium
Chances are you are bricked, if you can't get into recovery or try the exe again. Errors when flashing radio's is very bad.
@OP - please check info from our discussion in my help thread. Was busy last night, but still want to help. I was curious about if you tried using wireless adb since you can't communicate via usb cord? Also, I was digging thru some links from a couple years ago becuz your issue sounded familiar. Good news is I found a thread WITH A POSSIBLE FIX just linked in help thread
@jverm when you get time, please post the various steps we took to unbrick you, with links to helpful threads and concise information. Put SOLVED in the thread title, and add some thread tags to the issues. This way hopefully someone in a similar situation can hopefully find this thread, and then also successfully revive their phone as you did. This is all I ask of you for my help and again really it was fun for me, so thanks.
The screen with four small triangles in the corners means you had an incomplete flash. Luckily you're not bricked but it will be stuck in RUU mode until you Redland it with a good RUU
edit: nm, just saw il Duce's post

[Q] Lg-P769 error

Well i have been looking all over for help with my phone. I have figured out that i tried to flash a rom without unlocking my bootloader. Well im running windows 8.1 and for some reason i couldnt get my computer to recognize the phone at all. After using 3 or 4 different guides i gave up for a few days so not to get too aggrivated. I mean its my own fault but my back up phone sucks lol. So i borrowed my wifes laptop running win 7. I Followed this guide androidforums.com/optimus-l9-all-things-root/807569-guide-security-error-fix.html. For the first time since i started trying to solve my issue everything seemed to work got the s/w screen to appear in reverse and using the cmd prompt that says wiating for device then starting the .bat file from the download it says on the bat cmd prompt that everything worked. well at the bottom its says done then comes up with C:\fastboot\yours. i have been browsing google but i havent been able to find what i am supossed to do with the yours file. i tried putting a kdz file into the file location and running it from that but no luck. after a few min the phone auto reboots and comes back with the security error screen and not the backwards one. i have tried doing the hard reset at the point but no luck. if someone could please help with what i need to do with the fastboot/yours area that would be awesome. Or at least point me in the right direction cuz google isnt wanting to be my friend with the searches.
Android noob in training:
Sobih
help
Well i have tried several times now with using my wifes windows 7 laptop. i can get everything to work with the screen coming up backwards and in the command prompts it says that the fastboot is done then loads the command fastboot/yours which with the file i downloaded that file was empty. really unsure on what i need to do at this point. from the guides i have read it seems that im at like a step or 2 from getting the phone to work but after 30 seconds while still plugged in it reboots and loads the secruity error screen. from what i have read i should be able to do a factory reset by holding the volume and home button and then pressing the power for 3 seconds but it just reboots into the error. any help would be much appreciated i really dont want to have to buy a new phone.
Seems like that guide is more for when flashing a recovery on the locked bootloader and things go wrong. It was suggested a few posts down on the first page of that guide that if your problem happened when you were trying to flash a rom you might want to follow this : http://androidforums.com/optimus-l9-all-things-root/792689-guide-unbrick-manual-update-updated.html or http://forum.xda-developers.com/showthread.php?t=2085344 (the xda one seems more complete) .
sigh
Well im still stuck on the security error screen. i got the phone to boot into the backwards fastboot screen 1 time and cant remember how to do it again. i can boot into the s/w upgrade mode. if i go to use the lg support tool being that im in the united stats my options is upgrade recovery or help. well if i go to upgrade recovery im told that my phone has the latest upgrade already. if i try and use the moduptest that come in a lot of the unbricking guides it makes me turn the internet back on even with having hte shttps and everything else that is listed in the various folders. i only have the omap44 on my device manager 1 time but there is also 2 lg mobile modems. im thinking my issue lies with the fact thta i dont have the adb file for the device manager. i have donwloaded and uninstalled various times but still no luck. i dont remeber how i got the phone to the backwards fastboot but i remember i was following a guide and the op had to open one file and while that one was stuck on "waiting for device" he opened another one becasue that was the only way he could get it to connect. Any help would be awesome. not trying to rely on everyone else but after several weeks trial and error im at my wits end with it.
thanks
sobih

Recovered my softbricked phone really easy way

Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
sethandian said:
Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
Click to expand...
Click to collapse
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
t5620 said:
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
Click to expand...
Click to collapse
Thanks for posting up the links.
sethandian said:
Here is where I was at, ready to throw away the phone I ruined.
Click to expand...
Click to collapse
As long as the screen comes on for this phone, its virtually always recoverable. There was never any reason to think you had to throw away the phone. Next time you are stuck, just ask for help here; as we are happy to help. You did the right thing in trying to find existing solutions. But it sounds like you did your due diligence searching and reading; and would have been justified starting a new thread and asking for help.
sethandian said:
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else.
Click to expand...
Click to collapse
That is precisely what the RUU does. Its a complete image, and handy for recovery purposes.
sethandian said:
I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. l
Click to expand...
Click to collapse
While the OTA has had some reports of causing battery issues, the RUU has not had any reports of such issue, and seems to be free of it.
sethandian said:
I am not sure a phone that is S-OFF would work but it doesnt hurt to try.
Click to expand...
Click to collapse
S-off does not affect whether or not the RUU will work, I don't know why folks keep saying or asking this. RUU will work whether S-on or S-off. The only difference, is that with S-on, you need to either have a LOCKED bootloader, or RELOCKED (relock it manually if you unlocked it).
Also, in general, S-off does not limit anything. It means "all security off" and enables more access, not the opposite. If anything, S-off enables more things than S-on.
Thanks for the all the info. The experience was a valuable teaching moment. Now back to playing around with the M8.

Categories

Resources