For the last two days I tried to revert my HTC One V back to stock android. As in, the way I got it when I first booted it up. I experienced that this progress was pretty difficult. Maybe this was because I was used to the AOSP niceness of Google's LG NExus 4 or because HTC made it very hard to say the least to downgrade/upgrade to their own stock ROM.
I may not have the original sources for all files because I deleted some original .zip files and only have the extracted files.
First off, I wouldn't do any of this if you have important files on your device, I wiped everything from my phone a dozen of times in the process and it didn't care because I didn't had any important files on their.
Alright, so what we want to achieve is to get to the latest version of HTC's RUU version "2.22.401.7". The RUU I could find was "2.22.401.1" so we're gonna have to d/l some OTA's later on via our device if everything is set up.
So obviously everyone who is trying to revert back has somewhere unlocked their bootloader by doing
fastboot oem get_identifier_token
and
fastboot flash unlocktoken Unlock_code.bin
Please remember this: ANY RUU will fail every single time if your device is LOCKED. It will ONLY work if it's unlocked or relocked.
So first off what we gonna have to do is relock/unlock our device. You can relock your device by going into fastboot[1] mode and running the following command:
fastboot oem lock
Myself have expierenced an error that told me it "FAILED". Please reboot your bootload:
fastboot reboot-bootloader
And check the locked status at the top. If it says "RELOCKED", succes! If it didn't, retry the command above.
Next, we're relocked so we can run the RUU. Please look at the text file at the RUU source [2] for the download links. In this .zip file are the files inside the RUU wizard. You can run the wizard by executing "ARUWizard.exe" and you can view the contents of the actual ROM in "rom.zip extracted" and you can find the original ROM in "rom.zip". Since these are the files the wizard will be using (except rom.zip extracted folder) please do not touch them.
Alright, so we've got the extracted files of the RUU and we're ready to update. Please boot your phone in fastboot mode and connect it to your computer via USB. Now run the "ARUWizard.exe" file and let it update. I couldn't think of a situation where this could go wrong, so please ask below if you face any problems.
The wizard will flash stock radio, recovery andsystem.img (the actual ROM you all know) so by doing this you lose your custom revovery.
When your phone boots up you've gotta go through 3-4 updates till it's on "2.22.401.7".
I recommend not flashing a custom recovery right away because when you install/download OTA updates it isn't able to flash it right. In the meantime if you want root[3] use this command:
adb install -s supersu.apk
When you're on the latest version you have to unlock your bootloader, otherwise you cannot flash a custom recovery or kernel or whatever. You can do this via HTC[4]. I think there are enough guides on how to do this, but in short:
- create an account with an legitimate email address
- Select "all other supported devices" from the list
- follow on screen instructions.
Seriously everything is on there, HTC made it really easy.
If you want to install a custom recovery I recommend using TWRP[5]. Please flash TWRP by booting into fastboot and running the following command:
fastboot flash recovery twrp_recovery.img
Troubleshooting
There isn't really a lot that can go wrong if you do this. But when you're stuck on a screen or you think your device is "bricked" or stuck in a bootloop do these things:
- First off, hold the power and volume down button till the device goes down. If it's down, release the buttons and then hold the same buttons again till you're in bootloader
If that doesn't work do either of these commands (make sure your device is connected via USB, hehe)
Make sure fastboot and/or adb is working first:
fastboot devices
adb devices
If fastboot is working:
fastboot reboot-bootloader
If ADB is working:
adb reboot bootloader
adb reboot recovery
If you have any questions, please ask me. I did a dozen of things these two days, I may forgotten something because I did a crapload of things all at once.
Cheers!
Sources:
[1] http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930
[2] http://rg.to/file/aaca8c0c03e655d6df78242b4cea931b/hov.zip.html
http://ul.to/dfmg5dnw
https://mega.co.nz/#!wBcUiIxD!uIkyqZLgFErSItBTu3K7RY3eyUmXVUg60rcB-B-QRWE
Please request other providers below.
[3] http://download.chainfire.eu/supersu
[4] http://www.htcdev.com/bootloader
[5] http://techerrata.com/browse/twrp2/primou
tl;dr
unlock bootloader -> run RUU -> done
This is great and all, but is this for the PRIMO-C or U? US version? etc... etc..
Related
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
1. Download the correct RUU (ROM Update Utility) for your device from androidfiles.org. Make sure you download a Primo_C RUU for a CDMA device (no sim card) or a Primo_U RUU for a GSM device (uses a sim card)!! Also make sure you get the correct RUU for your carrier.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Hi
Thanks for that perfect decsription exactly when I needed it
I just had a weired effect with my new windows 7 laptop that I want to share.
I installed the USB drivers and "fastboot devices" showed my HTC fine
but even flashing the stock recovery image was not working.
So it was stucking in the "Sending" part and never continued.
I then moved to my old laptop with Vista did exactly the same things
and there it worked without problems.
I disabled virus scanner, checked for htsync and used the original USB cable
without success.
But now I know why I normally never touch Windows and only
work on linux
Regards
max
---------- Post added at 11:19 PM ---------- Previous post was at 10:33 PM ----------
Hi
CafeKampuchia said:
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Click to expand...
Click to collapse
I have done that now - compared to my first "try"
Regards
max
hi. thanks for the tips.
however when i do this, i get an error "FAILED <remote: signature verify fail>
Any suggestions?
ur RUU and CID is diff...
ryanlow134 said:
ur RUU and CID is diff...
Click to expand...
Click to collapse
and... how do i make them the same?
lcavada said:
and... how do i make them the same?
Click to expand...
Click to collapse
Use the correct RUU package for your device
regards
max
Another way of saying it is that you downloaded the wrong RUU for your device.
not working
it keeps on saying waiting for device n does not proceed further
i tried installing the drivers again but that doesnt help either
pls help me out
I use fastboot flasher for this.. this tool is good .
sush93 said:
it keeps on saying waiting for device n does not proceed further
i tried installing the drivers again but that doesnt help either
pls help me out
Click to expand...
Click to collapse
"Waiting for Device" at fastboot usually related to bootloader driver. You need Android USB Driver
See : http://developer.android.com/sdk/win-usb.html
Hi folks,
I've bought my One V in late may and I had 2.08 ROM.
Now I've tested some roms and I wanted to revert back to stock rom.
I've downloaded RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed, and got recovery_signed and boot_signed images. Then I've went to fastboot, did flash recovery and boot partitions, and oem locked bootloader. Afterwards I booted my phone and entered PIN. Then I fired up RUU*.exe file, and I have 155 error. What the heck? Something I missed?
greetings!
run the ruu in hboot..
Sent from my HTC One V
thevilish said:
Hi folks,
I've bought my One V in late may and I had 2.08 ROM.
Now I've tested some roms and I wanted to revert back to stock rom.
I've downloaded RUU_PRIMO_U_ICS_40A_HTC_Europe_2.08.401.2_Radio_20.72.30.0833U_3831.17.00.18_M_release_263376_signed, and got recovery_signed and boot_signed images. Then I've went to fastboot, did flash recovery and boot partitions, and oem locked bootloader. Afterwards I booted my phone and entered PIN. Then I fired up RUU*.exe file, and I have 155 error. What the heck? Something I missed?
greetings!
Click to expand...
Click to collapse
Flashing RUU to revert to stock
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
NOTE: There is no boot/reboot and enter pin in between.
paarthdesai said:
run the ruu in hboot..
Sent from my HTC One V
Click to expand...
Click to collapse
I've done this before and didn't succeeded, but now it works! Magic
Thanks a lot!
help
CafeKampuchia said:
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT/B] using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
Click to expand...
Click to collapse
PLEASE HELP!
The 5th point does not work for me. I can not run the code.
What can i do?
what do you mean by navigate to the folder where you installed sdk?
brandoncoronado said:
what do you mean by navigate to the folder where you installed sdk?
Click to expand...
Click to collapse
It means that if you installed SDK in c:/android, then u must type.in the command prompt: cd c:/android and hit enter
Cheers
Sent from my HTC One V using xda app-developers app
brandoncoronado said:
what do you mean by navigate to the folder where you installed sdk?
Click to expand...
Click to collapse
where the fastboot.exe is located and stock recovery must be in the same folder for the command to work
[ask] Error 155
hey guys, ive been reading all tutorial for reverting to stock RUU.
the first time i tried, it works prefectly.
then after a few weeks, i tried to revert to stock RUU, it failed .
it show error 155.
i already flash the boot , recovery that i found inside the stock RUU, also I've relock the phone.
but when i relock the phone, it show "info Lock successfully , status read failed no such file / directory"
when i enter bootloader, it show that my device already "relocked"
does the relocked proses is successfully ?
iam running PrimoU 2.09.707.1 with stock bootloader, CWM recovery, and rooted ..
I did exactly as it is mentioned but at the end where there is vertical progress bar it gives me an error of customer Id... Failed to update. What shud i do. How do I check what my customer Id is I can't Download it from play store coz can't boot into normal screen... How do I make ruu and cid same.
Sent from my Galaxy Nexus using xda app-developers app
I know the feeling! You're all excited because you just unlocked your One V's bootloader, flashed a recovery, and flashed a steamin' hot new ROM. You boot up for the first time and get ecstatic, the tension building as you put in your Gmail info. You finish the start up but OH NO!!! Your phone reboots! You blame yourself... you blame your cat... you blame your wife... you blame the war in the Middle East. You think, I must've done something wrong! Stupid, stupid, stupid! Don't fret! Take my experience with this quite seriously (despite the jokes). For 2 weeks, I retraced my steps and tried EVERYTHING! I thought it was just the ROM's problem, so I flashed one after another to the same end. Finally, I decided to post a new thread asking for help. Nothing became of the first thread, so I posted a second one. To my great relief, along trotted Curiousn00b. After shoving me in the correct direction, I figured out the rest. A big thanks by the way, Curiousn00b! The following is the method that I used to get my phone to finally run a ROM. Also, a thanks to CafeKampuchia for the quoted directions below.
A few things to make sure you have:
Windows (with Administrator's priveleges)
Fastboot installed and working
Your phone (duh!)
A USB cable
Time and patience
The following quote is from CafeKampuchia's thread over here.
Solution #1
CafeKampuchia said:
Here we go:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT/B] using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thus far you should have the stock recovery back and be bootlocked again. Now, back in fastboot mode, you should already be connected to your computer via USB (if you disconnected, just reconnect it and wait for "FASTBOOT" to change to "FASTBOOT USB")
Run this command:
Code:
fastboot oem rebootRUU
Next, start up the RUU program again and let it run through without interruption. After this process is done, the phone should boot up to the stock ROM. Let it do its thing, but this time don't do the OTA update. From here, just unlock the bootloader again, install your recovery of choice, and install your ROM of choice or reroot the stock ROM (I know some want to keep it stock).
As also pointed out by RoyalYeo, you can let HBOOT take care of the problem:
Solution #2
My hunch was correct, the .0928 Radio was causing the bootloop... I managed to flash the 521_2 radio, and now the Sick kernel is working and AOKP JB runs great.
Steps (on windoze):
1) Download the RUU
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Lemme know if you get it working...
Click to expand...
Click to collapse
My personal solution (Solution #1) is the more technical side of things and also exposes you to the nitty-gritty. Having said this, #1 is quite touchy because if you do something wrong, there is a good chance that you could... well uh, brick your phone to be quite honest. On the other hand, #1 requires no SD card (given the event that your SD card won't mount, your SD reader is broken, or you just plain don't have an SD card). Ultimately, the choice is up to you.
A note for Mods: I'm not sure if this technically falls under Development or Q&A (or both). If it can stay here in Development, I'll also post a thread in Q&A.
hello there,
So i've followed these instructions and I still get a bootloop... Occasionally when i flashed the MIUI.us rom it will get up to the start out screen... then restart... and do it repeatedly... but at the current moment... it's simply bootlooping on the MIUI logo. I've ran RUU approximately 20 times on this phone... i've tried different SD cards because something is recently they have been randomly disconnecting and not showing up... i Plugged my phone in and set it to Disk Drive mode, wrote files to it... and when i check on my phone... all the files are gone except for the original.. so i preceded to take the card out plug it into my computer and format there... i do that... and all the files show back up when i plug into my phone... ALL the original files that i just formatted... i don't know what steps to take next to get any of it working. I've tried flashing sick kernel and the MIUI rom and still nothing has worked... any assistence would be greatly appreciated, I'm tired of resetting my phone EVERY time i try and flash a new rom
I have a thread here but Everything i have tried there has failed to work but you could use some of the info from there to possibly diagnose?
http://forum.xda-developers.com/showthread.php?t=2013489
Thanks a million!
hello android geniuses first of sorry about this once my phone is working again i will not mess with it anymore
okay so i was feeling cool and rooted my htc one m7 from verizon then i turned s-off and unlocked bootloader
then i flashed a custom rom it was paranoid android everything worked except i wasnt getting any service on the phone so i was told to flash a verizon htc one rom so i went and flashed viper 6.2 but the phone got stuck in a bootloop so for some reason i thought that doing a factory reset/wipe from the recovery would fix it....it didnt and now i cant reflash the rom either....i tried to sideload but adb wont recognize my device while fastboot recognizes the phone adb wont
what am i to do?
Well im not sure of any other methods to try but i had loads of problems myself pushing files to the SDcard threw twrp and cwm recoveries, so the way I went about it was doing a decrypted RUU to return the phone to stock then once it loaded up in Android I pushed the Rom to the SDcard card then rebooted and started over.
Goto this thread http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
All the way at the bottom you should see some links for RUU's, I used the one labeled "1.10.605.15 Decrypted RUU" You will flash this the same way as you would a firmware update, if you dont know how thats done that post will explain it all. After you flash the RUU reboot and it should be back to the day you got it, but you will still be s-off, at that point just put a custom recovery back on and flash away, however that RUU will downgrade your firmware so you might wanna update your firmware after you get the phone booted up and your rom placed back on the sdcard
fLaWx said:
Well im not sure of any other methods to try but i had loads of problems myself pushing files to the SDcard threw twrp and cwm recoveries, so the way I went about it was doing a decrypted RUU to return the phone to stock then once it loaded up in Android I pushed the Rom to the SDcard card then rebooted and started over.
Goto this thread http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
All the way at the bottom you should see some links for RUU's, I used the one labeled "1.10.605.15 Decrypted RUU" You will flash this the same way as you would a firmware update, if you dont know how thats done that post will explain it all. After you flash the RUU reboot and it should be back to the day you got it, but you will still be s-off, at that point just put a custom recovery back on and flash away, however that RUU will downgrade your firmware so you might wanna update your firmware after you get the phone booted up and your rom placed back on the sdcard
Click to expand...
Click to collapse
What he said. Good post dude.
When you enabled adb sideload, what command did you use? Because you don't push files that way. You type "adb sideload Rom.zip", then it will send the file and after it sends immediately start the install. So you will need to wipe in recovery first to make sure it's clean.
Sent from my Lunar Ecliptic One.
i followed your steps i got to the part where fastboot asks to flush the zip again i typed "fastboot flash zip firmware.zip" and it said waiting for device and that never went away so i rebooted into bootloader and now fastboot wont recognize the device however if i go to device manager it says my htc is plugged but has a little yellow icon...the drivers are up to date this is driving me nuts i just want my phone to work
Ruu
sound like you may need to ruu back to total stock there are instruction on doing it here and I do not want to give you the wrong steps. found this but make sure you have the decrypted ruu
1. Download VZW RUU.zip from the following thread 1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/show....php?t=2428276)
2. Rename to "ruu.zip"
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I also use cut and paste when doing this as it stops my crappy spelling from getting in the way
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
quadracorn said:
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
Click to expand...
Click to collapse
You could always use a USB-OTG, place a rom on a flash drive and try to install that way. There may be a simpler way, but that's all i can think of for now.
i guess i have to order an otg cable....oh well...ill have to live without a phone a bit longer until cable shows up haha XD w
quadracorn said:
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
Click to expand...
Click to collapse
Does pc see device in computer?if so down load room onto pc place Rom on root of ad card or in download and reboot phone into recovery ahs flash zip..I also had problem where adb would not see devices cause I had miniadb and the full version of adb and it was a conflict,just my two cents
I don't know if this will help, but I had an issue of my devices not being found so I followed this guy's guide: http://zacktutorials.blogspot.com/2013/04/adb-is-not-recognized-as-internal-or.html
and was able to get my device recognized. Also which recovery are you using? I don't know if it's still an issue but when I was on viper I got stuck in a bootloop with TWRP so I switched to Philz.
If you're able to get into fastboot, follow post #4 http://forum.xda-developers.com/showthread.php?t=2677015 and basically start from the beginning.
Make sure you have the latest recovery, the latest firmware (radios and such), and the correct ROM..
good luck
bregga said:
sound like you may need to ruu back to total stock there are instruction on doing it here and I do not want to give you the wrong steps. found this but make sure you have the decrypted ruu
1. Download VZW RUU.zip from the following thread 1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/show....php?t=2428276)
2. Rename to "ruu.zip"
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I also use cut and paste when doing this as it stops my crappy spelling from getting in the way
Click to expand...
Click to collapse
Hi All,
Do you know is RUU 4.4 has surfaced? please help
I am posting this in the hopes it might help someone that has a similar problem. I personally went down a lot of wrong roads before stumbling across the answer. Maybe that is me but like many issues all the answers were here in XDA they were just a little hard to find. If you are facing this problem here they are in one place/
Initially I was faced with a non-charging, boot looped HOX International
Many thanks to [email protected]|-|oR, teemo, Thant who got me through this.
HOX International Endeavoru
S-On
HBOOT 0.95
Version-main 1.29.401.11
oem readcid H_Y13-2.17.401.2
Stuck in boot loop. Device would not charge, would only run when on usb and then only go to bootloader screen. After a few minutes connection and phone would die. This is the worst possible situation if you have anything more than this it will work as well
The phone was unlocked.
Should work on either Windows, Mac, Linux as long as you have adb and fastboot installed (I use Linux)
This can all be done without ever having a working phone until process is completed.
Step One - Install a recovery CWM 5.8.4.0
On your pc download 5.8.4.0 from http://forum.xda-developers.com/show...5#post24738635
Personally I renamed it to somethingeasy.
Open a terminal (in Linux as long as fastboot is in your path it doesn't matter, in Windows you will need to be in the directory that has fastboot) Now flash the recovery.
Code:
fastboot flash recovery somethingeasy.img
Make sure it completes with no errors. This is an old recovery and should not be a problem for the device.
This recovery will (among other things) give you the ability to mount the phone on your box easily so you can copy files over.
Step 2 - Give the phone a chance to charge
Reboot the phone into recovery (or the bootloader and select recovery) which will allow the battery to charge.
Step 3 - Find a file to update your HBOOT
The major issue here is HBOOT 0.95 since it won't allow you to do a native update in the phone OS from an OTA. For me it refused to accept anything I downloaded on the phone after I restored from a nandroid backup so I just skipped that step.
By going to http://forum.xda-developers.com/showthread.php?t=1957376
Then find a file that matches your realcid. In my case that was a H_Y13 with 401 file. As in x.xx.401.2
Download that file and put it in your fastboot directory.
Step 4 - Relock the phone
Boot the phone into the bootloader select fastboot usb. Open a terminal and type
Code:
fastboot oem lock
Step 5 - Follow the steps on http://forum.xda-developers.com/showthread.php?t=1957376
Follow the steps from thread above:
Rename the downloaded file to firmware.zip and open a terminal
Code:
fastboot oem rebootRUU
and wait for device to reboot. It will come up with an HTC screen, be patient
Code:
fastboot flash zip firmware.zip
and wait for process to complete, again be patient it will work as noted on the link above sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure (and in my case it did not and I had to flash twice)
Code:
fastboot flash zip firmware.zip
and wait for process to complete
Code:
fastboot reboot
Then find your original unlock code from HTC dev or just do the whole unlock http://www.htcdev.com/bootloader/ again from the HTC site
Step 6 Reflash the recovery from above
Next reflash the HOX recovery from above we called somethingeasy.img
Code:
fastboot flash recovery somethingeasy.img
Boot into recovery
Wiped system, data, cache
now follow the steps from http://forum.xda-developers.com/showthread.php?t=2630225 or whatever ROM you want. In my case my HBOOT was upgraded to 1.72, just in time to get ready for Lollipop. Hope this is of help to someone.
Hi guys! A couple months ago I flashed CM on my Desire 816, but I wasn't happy with it, so I restored my backup that I made before the flash. Now that the new update came out, I tried updating, but I can't, because I have a custom recovery (CWM). I followed theunlockr.com's guide to revert everything, but the RUU linked in that does not work for me, fastboot complains about signature verification. I bought my phone in Hungary, off contract, so I guess it's an EU version. I'm pretty much a noob, so if I missed giving some vital info, just ask. Please help! Thanks!
We need good boot.img
Okay guys, I managed to go back to stock and my phone is updating ATM. Here's how I did it, if anyone is in a similiar situation:
1. I had the OTA on my comp, copied it from phone. You'll need fastboot as well. Also, I had the stock ROM installed.
2. Unlock the bootloader. If you already rooted your phone, you know how to do it.
3. Unzip the OTA, if you did it, unzip the firmware.zip as well.
4. You'll find a recovery.img in that zip. Copy it next to fastboot.
5. Restart your phone, go into bootloader, select fastboot, plug your phone in your computer. (to do this, you'll need to turn fast booting off while you're phone's on, and I think you'll need USB Debugging on as wel, but you probably know all of this)
6. Hit up a command prompt in fastboot's folder. Type in "fastboot flash recovery recovery.img", without quotemarks
7. It should flash the stock recovery in a couple of seconds. *optional* Check recovery in hboot just to make sure.
8. While your phone is still in fastboot mode, type fastboot oem lock into the command prompt you opened in step 6.
9. Now that you have a stock recovery and you're bootloader's locked, your HTC should update properely
I'm not sure (cause I'm a noob), but I guess this should work in every region, because the stock recovery is from the update itself. Hope this'll help