Develop Bugs

How to Unroot/go back to STOCK after installing Rooted versions of 1.47/2.05

Pretty sure most people know how to do this but for some who are having issues with drivers n such this might help, wouldn't hurt imo.. I'm on Windows 7 Ultimate (x86)
*** Reportedly Will not work with Official OTA 1.47/2.05 Updates, only Rooted updates, I have not personally tried. The Wizards @ the dev forums are working on a fix: http://forum.xda-developers.com/showthread.php?t=714157 ***
The steps below worked for me. I had the latest clockwork recovery,Damage Control DC 3.2.2.1 deodexed and The latest rooted ota updates installed (EVO_1.47.651.1_De-odex'd_Rooted.zip, 2.05.00.06.10 update.zip)
Download and install HTC Sync Update http://www.htc.com/us/support/evo-sprint/downloads/ (if you already have it installed then click the repair option,
or better yet uninstall your current one even if it is the same one, reboot your computer and then install this one again, for good measure.)
1. I unplugged/plugged my phone into the computer a couple times,switched to htc sync mode when it asks what type of usb connection I wanted, to install more driver updates if any
and did 2 reboots on my computer to get all the drivers updated/installed and working as they should.
2. Turn off the phone, hold volume down and hold down power button to get to bootloader,
pressed Power button one more time to get to the menu where you can reboot bootloader,
rebooted bootloader once and twice BEFORE the unrooting process for good measure.
3. Download either one of the RUU Stock Roms, I would try RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe and then RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe if the first one fails.
http://shipped-roms.com/shipped/Supersonic/
Alternate Link http://tinyurl.com/2fq4dzk
4. Plug your phone into your computer, make sure ALL Drivers installed properly if any, you may already have drivers installed, but double check, switch to HTC Sync mode
and let it install any drivers, then turn off your phone and start it in bootloader (Hold Volume Down +Power button) Reboot your computer also
to make sure everything has been properly installed.
5. Then you can finally double click (right click run as admin imo) the RUU.exe and start the unrooting process, good luck!

I try it and it don't work. I mean yet it detect my ota version but after I click update than for a while it said that my phone is not plug from the computer. I'm running windows 7 ultimate 64bit, eva x58 core i7-920

Thanks for the write-up, does this take the phone completely back to out-of-the-box stock?

yang704 said:
I try it and it don't work. I mean yet it detect my ota version but after I click update than for a while it said that my phone is not plug from the computer. I'm running windows 7 ultimate 64bit, eva x58 core i7-920
Click to expand...
Click to collapse
Make sure your in HTC Sync mode or Disk Drive Mode on your phone, also try rebooting your computer & phone, plugging your phone into a different usb port, etc, have to tinker with it a bit.
jasongthang said:
Thanks for the write-up, does this take the phone completely back to out-of-the-box stock?
Click to expand...
Click to collapse
Yes.

Worked for me earlier today. Failed the first time, but i just ran it again and it went through. Thanks for the writeup!

Np glad I could help
Sirchuk said:
Worked for me earlier today. Failed the first time, but i just ran it again and it went through. Thanks for the writeup!
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

do you have to have either 1.47 or 2.05 to use this method, or will the rooted supersonic 1.32.651.1 be able to do it?
because I installed htc sync, set the phone to HTC Sync, but the phone says it cant find it on my computer.

jasongthang said:
do you have to have either 1.47 or 2.05 to use this method, or will the rooted supersonic 1.32.651.1 be able to do it?
because I installed htc sync, set the phone to HTC Sync, but the phone says it cant find it on my computer.
Click to expand...
Click to collapse
Yes it will work for that version, you only set HTC Sync mode up to install any missing drivers, then you switch back to disk drive mode if you want your computer to gain access to your phones SD card.

Tundricles said:
Yes it will work for that version, you only set HTC Sync mode up to install any missing drivers, then you switch back to disk drive mode if you want your computer to gain access to your phones SD card.
Click to expand...
Click to collapse
so are you saying the htc sync doesnt have to actually sync? the phone never finds the htc sync on the computer. But I can get the computer to see the phone and access the sd card no problem.

Thanks for the write-up it worked just like planned. And with so many people returning for some reason or another this is just what we need
Im returning one and buying another at bestbuy HEHE

so will this return the Evo to shipped stock rom IF i did the OTA update? and will i be able to root if i have the OTA update?
thanks

I had the .6 stock(not root)and OTA updated to 1.47,how can I go back to .6 stock,I ran the .6 RUU,but it said main version older and refused to downgrade,anyone knows how do I reload the .6 back?my EVO ever rooted.

As far as I've been able to find by SEARCHING the forums:
NO
Once you do the OTA update you can NOT go back or downgrade or uninstall it or whatever.
This method posted is for installing a ROOTED ota update. ie, it was hacked, and rooted prior to being installed. If you downloaded it from sprint on your phone and installed it, your are SOL for now.

Sirchuk said:
As far as I've been able to find by SEARCHING the forums:
NO
Once you do the OTA update you can NOT go back or downgrade or uninstall it or whatever.
This method posted is for installing a ROOTED ota update. ie, it was hacked, and rooted prior to being installed. If you downloaded it from sprint on your phone and installed it, your are SOL for now.
Click to expand...
Click to collapse
That sucks...oh well,thanks for the info.

They're working on a fix, but I wouldn't hold your breath. Most of the devs are taking the weekend off for one reason or another.
Here's the discussion thread:
http://forum.xda-developers.com/showthread.php?t=714157

jasongthang said:
so are you saying the htc sync doesnt have to actually sync? the phone never finds the htc sync on the computer. But I can get the computer to see the phone and access the sd card no problem.
Click to expand...
Click to collapse
Yes, sync be damned!

Thanks for the write up.
Couldnt get it to go. Tried EVERYthing mentioned. Keep running into Error 170 USB connection error. I did dl HTC sync and let all the drivers install and rebooted my PC. And the phone.
Also tried multiple USB ports.
Nada.

not sure if this is any help, but I think the person in this thread had that same error, I hate to have you dig through the thread but I want to say it was mentioned on one of the later pages. Not sure if this is applicable to what you are doing.
http://forum.xda-developers.com/showthread.php?t=723236

elegantai said:
not sure if this is any help, but I think the person in this thread had that same error, I hate to have you dig through the thread but I want to say it was mentioned on one of the later pages. Not sure if this is applicable to what you are doing.
http://forum.xda-developers.com/showthread.php?t=723236
Click to expand...
Click to collapse
Thanks but sadly I've been through all the steps mentioned in all those links.
My USB is fine as I have been using it without issue.
I definitely cannot flash the .1 or .6 RUU.
I tried liquid jesus's method and it would not go either.
I'm stumped

Have u tried to flash the ruu as a zip?

[Q] Some Things Not Working On Desire [Q]

Anyone that can help me with this one, can be my new bestfriend
After getting really really depressed over being on the Official HTC Sense ROM with my Desire, I decided to change to the Starburst ROM. As the new Unrevoked doesn't work with the latest official build of Froyo from HTC I always, always use this when I want to downgrade and root, to install new roms.
Normally, I will use the utility as indicated, everything will go smoothly, Eclair 2.1 will install, however normally my phone will be locked, and I will have to remove my SIM, update to 2.2, my phone will become Unlocked after updating, and I will root. However this time, when the utility copied a misc_partition or something like that to my SD Card, it came up with a load of write errors, saying there wasn't enough room on my SD Card, which I know is wrong as there is well above 6GB on there, and it's a Goldcard. One advantage of the utility is, if anything goes wrong you can press CRTL-C and the utility will stop with no changes made to your phone, however in my case this wasn't so. I stopped the utility, thinking if I continued due to the write error I would encounter some more errors, and I decided to do a complete wipe of my phone using the on-board Factory Reset in the Setting's menu. After doing this, I started to encounter some problems.
First of all, when the phone enters the setup wizard, it says I have 4 bars of signal, and a 3G connection. After around 15 seconds of being in the Wizard, I will suddenly loose all mobile connection. After completing the setup wizard, I will be prompted by a notice telling me I need to Insert an SD Card. Well my card is in there, and I know its working because after these problems I put it into my brothers phone, and formatted it, and it showed up as working just fine. If an LG POP can mount my phone, surely a frigging HTC Desire can?
I have noticed that if I remove my SD Card, then the problems with the Network will go away and I will be able to connect, however sometimes when I boot it my phone will connect to the Network for about 5 minutes with the SD inserted, then return back to Limited Service. *I have attached a picture of what I am seeing.* This is really annoying me, I am going to download the Froyo 2.2 ROM from Shipped-Roms as the SD Card seems to mount fine in HBoot. Please though, can anyone help me. Thanks.
*This is starting to become very annoying now, I have been working on this for several hours now, and I still have no fix or nothing. I can't exactly be patient and I don't mean to sound like a tech addict, but my world revolves around my phone, I use it for business ect. When I connect my phone to my computer, I get a message saying 'Install Drivers For Qualcomm CDMA Technologies MSM' I have heard of CDMA before, but I don't think my phone is CDMA? My phone was originally branded Orange in the UK? Anyone that can help, just please please help me!

Hi, sorry I can't help with your problem as it seems too complicated to me (noob here) but reading what you wrote sort of alarmed me as I've been reading/watching videos on rooting and I thought that unrevoked (latest version) worked on any desire. It says so on the unrevoked site but you wrote you can't do it on yours because of new build of froyo.
Don't understand that, I'm on vodafone and asked advice to a few people about rooting and nobody told that I couldn't use unrevoked. Are you sure you can't use it. How about you do a factory reset and reflash rom and see how it goes. I do hope you're wrong about unrevoked though as I'm about to use it any day now (building up the courage...) Hope you get your problem solved.

well try to reinstall whole software via pc ...............
but check download latest version of official rom
back up your data as ur whole system sofware will be replaced
and do format ur sd in pc ( not a quick format )
hopefully it might resolve ur issues ( otherwise it seems a hardware issue >>>>>)
and i am not responsible for any sim locking or data loss sort of problems

wilborama said:
Hi, sorry I can't help with your problem as it seems too complicated to me (noob here) but reading what you wrote sort of alarmed me as I've been reading/watching videos on rooting and I thought that unrevoked (latest version) worked on any desire. It says so on the unrevoked site but you wrote you can't do it on yours because of new build of froyo.
Don't understand that, I'm on vodafone and asked advice to a few people about rooting and nobody told that I couldn't use unrevoked. Are you sure you can't use it. How about you do a factory reset and reflash rom and see how it goes. I do hope you're wrong about unrevoked though as I'm about to use it any day now (building up the courage...) Hope you get your problem solved.
Click to expand...
Click to collapse
Basically on the latest Froyo build from HTC (2.29.405.5) if you use Unrevoked, everything will go fine until it boots out of the bootloader to the actual software. On reboot Unrevoked will say 'Waiting for system to Settle'. This will never dissappear and it will wait for the system to settle forever and ever. However becuase you are branded on Vodafone, the chances are you're not running Froyo build 2.29.405.5, but a slightly older one. This is because when HTC release an update the phone companies have to put their software onto it, the the 2.29.405.5 update was only 5Mb, barely enough for the companies to be even bothered messing around with, so chances are you WOULD be able to root anyway, thanks for commenting.
commando0 said:
well try to reinstall whole software via pc ...............
but check download latest version of official rom
back up your data as ur whole system sofware will be replaced
and do format ur sd in pc ( not a quick format )
hopefully it might resolve ur issues ( otherwise it seems a hardware issue >>>>>)
and i am not responsible for any sim locking or data loss sort of problems
Click to expand...
Click to collapse
Oh I know about data loss, Sim Locking and all that, been there, done that, got the T-Shirt, I've got a Utility on my computer that will unlock my phone and as for Data Loss, Google servers have it all
I've got a bit of an update though, I know your saying it's a hardware error but I think there are two key components here that aren't working.
- The SD Card
- The SIM Card
I have come to believe this, because I managed to use the PB99IMG file to update to the latest Froyo, and now my phone is saying there is an SD in there, but stats about the SD are unavailable in my phone, and also when trying to connect to the network, my phone will not connect to Orange. If I click on Manually Select, and I click on Orange, I get a message saying SIM won't allow connection to this network, if I do it with Automatic however, it just says unable to connect to the network at this time. I'm gutted I haven't been able to fix this yet, it's really annoying me because normally I would be able to sort this, been up all night trying to do it, any help is greatly appreciated.

2.29.405.5 roots absolute fine with unrEVOked - if it didn't I wouldn't be rooted!!

EddyOS said:
2.29.405.5 roots absolute fine with unrEVOked - if it didn't I wouldn't be rooted!!
Click to expand...
Click to collapse
Possibly a problem with my Device or HBoot? Could anyone point me to the correct RRU for me to reset my phone with? I am running the latest software version with a goldcard, the card won't mount when the phone is turned on, thanks.

This is for the 2.29.405.5 RUU
http://www.multiupload.com/LEJCW182AH

EddyOS said:
This is for the 2.29.405.5 RUU
http://www.multiupload.com/LEJCW182AH
Click to expand...
Click to collapse
Really appreciate it mate, thankyou
*Update, I flashed this RRU, it's not working though :/

When you say not working what do you mean? More info needed!
Also, edit the 'Qualcom CDAM' thingy, that means its trying to install modem drivers - sounds you USB-bricked the phone

EddyOS said:
When you say not working what do you mean? More info needed!
Also, edit the 'Qualcom CDAM' thingy, that means its trying to install modem drivers - sounds you USB-bricked the phone
Click to expand...
Click to collapse
Yeah it won't connect in any way USB wise, and when IS ay not working, the OS works fine, connects to the network for the first 5 minutes, SD card won't mount, then after 5 minutes I get locked out of the network, and if I try and connect I get a message saying my sim won't allow connection to Orange :/ Think you can help?

[ROM] Gingerbread for Incredible 2 is coming

RUU(full rom):
http://www.megaupload.com/?c=premium&l=1
It seems an offical version, but maybe a test one.
It includes many languages to select, e.g. Simple Chinese, English and so on..
Update before, you'd better make your phone S-off !!

Drool
Sent from my ADR6350 using Tapatalk

I've flashed this, with out root (Don't need it). Everything is pretty solid. There's a 5th metal skin i've seen included with the incredible S, The Get more htc widgets works, quadrant gives me a 1510 or so.
Anyone who has experienced the 'input lag', where typing to fast will cause the phone to lock up for a sec then spit out the text, should know that gingerbread fixes that.
The only issue I've seen so far is the vzw app crashes constantly if you update it. If you don't update it, it's fine, but you can't access usage info.
This is 2.3.3, so it doesn't have the updated Gtalk video chat, If you root, there should be a way to install it.

excuse me for being such a noob,
i admit. the force is not strong with this young padwon..
how do i go about flashing this update to my stock unrooted dinc2?
i remember how i flashed my OG D1 but was having some troubles with this new beast,
thanks for any advice in advance boys!

This would be done through fastboot... it will will recognize the leak as a real update and flash for you.
But in doing so, like it has been said in other posts: You will lose the capacity to root with Alpharex.

no renaming the file to update.zip or anything? nothings poping up through the fastboot screen other than the standard options

does it do a wipe or is it an actual update (No Data Loss)?

bigslam123 said:
does it do a wipe or is it an actual update (No Data Loss)?
Click to expand...
Click to collapse
The installer warns of a full data wipe, but i cannot get the ruu installer to find my phone connected to the system...anyone have any insight?

would it be possible to go back to froyo once s-off is released? i do want to check this out but not at the expense of not being ready for s-off once it is made public.

mikejaret said:
The installer warns of a full data wipe, but i cannot get the ruu installer to find my phone connected to the system...anyone have any insight?
Click to expand...
Click to collapse
This is what I did using win7 x64: *BECAUSE I DO NOT CARE FOR ROOT*
First, download the latest version on HTC sync... it has all the drivers you need, and takes care of error 171 (when the phone reboots and the RUU is waiting)
Next, enable USB debugging, this takes care of error 170. You can do this by going to menu>settings>applications>development
If you encounter any other errors, try running the RUU program as admin, and using vista sp2 compatablity mode.
Edit: also, no you don't have reboot into fastboot. The RUU program does some initial checks (software ver. battery %, other bs) then reboots the phone for you.
HTH

bigslam123 said:
does it do a wipe or is it an actual update (No Data Loss)?
Click to expand...
Click to collapse
YES. you lose all data (text, phone log, programs).
The programs reinstalls automagically for the most part though, since it's backed up with android market. I thought that wifi passwords would be backed up with this system as well (it does with CM7) but no dice.

cougar618 said:
This is what I did using win7 x64: *BECAUSE I DO NOT CARE FOR ROOT*
First, download the latest version on HTC sync... it has all the drivers you need, and takes care of error 171 (when the phone reboots and the RUU is waiting)
Next, enable USB debugging, this takes care of error 170. You can do this by going to menu>settings>applications>development
If you encounter any other errors, try running the RUU program as admin, and using vista sp2 compatablity mode.
Edit: also, no you don't have reboot into fastboot. The RUU program does some initial checks (software ver. battery %, other bs) then reboots the phone for you.
HTH
Click to expand...
Click to collapse
So grab the file.. Then what?
where does the file go? Assuming it's on the SD card? (Sorry, first HTC phone since G1) and then once the phone is detected and in USB debugging then what?

@cougar618, besides for that typing lag fix you mentioned, are there any other upgrades/changes that you noticed so far? i'm real curious and want to check this out but also so eager for root... AHHH!!!!

presence06 said:
So grab the file.. Then what?
where does the file go? Assuming it's on the SD card? (Sorry, first HTC phone since G1) and then once the phone is detected and in USB debugging then what?
Click to expand...
Click to collapse
You don't put it on your SD card. The File is actually an EXE file, you run it on your computer. .. it took me quite a while to figure that out when I had the OG inc lol. so dl the file, dl the HTC sync and install for the drivers, and run the RUU program that you dl.
For me, the Typing lag fix was the sole reason for me to install the GB update. asides from that, GPS seems to work much better, and it seems very stable. Batter life is not that geat, but it was not that great for me on froyo (I use my phone as an mp3 player, etc).
and a bit off topic, but I can't check partial wake usage on GB. Anyone with froyo able to? I tried with spare parts, and I know there's a code you can dial, but can't find it.

what's partial wake usage?

cougar618 said:
You don't put it on your SD card. The File is actually an EXE file, you run it on your computer. .. it took me quite a while to figure that out when I had the OG inc lol. so dl the file, dl the HTC sync and install for the drivers, and run the RUU program that you dl.
For me, the Typing lag fix was the sole reason for me to install the GB update. asides from that, GPS seems to work much better, and it seems very stable. Batter life is not that geat, but it was not that great for me on froyo (I use my phone as an mp3 player, etc).
and a bit off topic, but I can't check partial wake usage on GB. Anyone with froyo able to? I tried with spare parts, and I know there's a code you can dial, but can't find it.
Click to expand...
Click to collapse
Ok.
According to some including Droid Life, you need to be root to install the RUU? Is that true?

nope root not needed

presence06 said:
Ok.
According to some including Droid Life, you need to be root to install the RUU? Is that true?
Click to expand...
Click to collapse
False.
There are two files out there, one on this forum by jcase, for rooted users, and the official RUU from HTC, that removes the root exploit someone found. once rooted, you can do S-off, which allows for you to root the phone later.
As i've said, I don't care for root, so I just used the RUU from htc.
Please do some more research on this before trying anything...
Also, off topic again, partial wake usage is when the cpu is woken from sleep for an application, such as listening to music.

alright guys here we go.
i figured it out ! LOL
you must install the htc sync program so that your DINC2 and SYNC link up through your WINDOWS based pc.
after that you download the RUU in the original post,
run it and it will open on its own.
that is all you gotta do.
however,
I do not think there is a way to uniinstall this update and it has been mentioned that this build may NOT link to future ota's
can anyone provide more insight on the ota part?
I'm going to be one sad panda if i can't get any updates because i jumped the gun with this RUU

cougar618;15134771
Also said:
ahh.. icic.. hmm i didn't even know you could see a stat like that in froyo haha.
Click to expand...
Click to collapse

[TUT][CDMA]ROM randomly rebooting? Here are some fixes! (BACK IN BUSINESS!!! :D)

NOTE: This one's a big one if you can't tell! Everyone give a round of applause to simonsimons34 for tracking down the issue. What does this mean? Well, there may not be a need to ever downgrade using the RUU. If you go here (you really can't miss that big, bolded "here"), you will see that he determined the issue is caused by:
a bad battery driver function in the kernel
Click to expand...
Click to collapse
He also took the liberty of building a kernel compatible with 4.2 and putting in a commit for fixing the kernel to work with the newer radio at GitHub. Any ROM builders who see this, please do check it out. As far as everything goes, I haven't personally tested it but I do always encourage people to try it out. Simon has been a great supporter and kernel builder for our device so I have faith that he hath found the Holy Grail. 'Course my thread will have no more existential purpose, BUT it is a great resource so as it is, I will leave it up for the general perusal of the community. Have a great week everybody and I look forward to a new flood of development.
Exciting news y'all! This thread has been stickied! [Hopefully] this will allow continued support and growth of the thread. My personal philosophy is that anything I post shouldn't be locked down to what I know or believe in, so I encourage any reader to put forth their input. What does that mean? It means that if you have a suggestion, by all means inbox me your thoughts. I'm open to continual development of this tutorial through community teamwork. Have a good day everyone!
-------------------------------------------------------------------------------------------------------
Here are some common reasons why your phone will randomly reboot (bootloop). You should only use an RUU (the methods below the "=" signs) if NOTHING ELSE WORKS (because the RUU does a factory wipe of the phone).
Common Problems:
I switched from another ROM and now my phone keeps rebooting...
There are several factors in play here. The commonly accepted fix is backing up your data and doing a full wipe (cache, dalvik cache, system, data) followed by reflashing your ROM.
I upgraded my ROM from blah blah version to blah blah version (ex. 4.0.x to 4.1.x)...
This is because your old Ice Cream Sandwich system stuff may not be compatible with JellyBean (in the case of the example). Wipe system and the caches (dalvik & cache) followed by reflashing your ROM.
I upgraded my ROM (within the same version) and it keeps rebooting...
Every time I upgrade my ROM, I wipe cache. If something funky happens, just wipe system and reflash your ROM.
I flashed a ROM and it won't boot at all...
Either you flashed a ROM for a different device, you flashed a kernel for another device, OR you didn't flash a kernel at all. Make sure everything is for your phone (the HTC One V on Virgin Mobile is the CDMA version known as "PrimoC" whereas the GSM version is the "PrimoU").
=============================
NOTE: This guide is for the One V!
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.
NOTE ABOUT THE FOLLOWING PARAGRAPH: jmztaylor's site is now legally able to host the RUUs again so the download link is right here*
In support of jmztaylor and all of his work for this device, I have decided to also include his website in this thread... *here is the download directory for the HTC One (Primo) device RUUs. I'm not sure if this bug effects other Primo devices, so this especially pertains to the PrimoC (HTC One V CDMA). Thanks jmz for the tip!
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 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.

y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665

cybervibin said:
y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
Won't work if the ota is already applied from the factory.

cybervibin said:
y take a risk, avoid it in the first place, follow this guide
http://forum.xda-developers.com/showthread.php?t=1996665
Click to expand...
Click to collapse
You need to downgrade your radios or your guide will be useless no matter what, i followed this post i found on android forums and it worked
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

robaho said:
Won't work if the ota is already applied from the factory.
Click to expand...
Click to collapse
Or if you applied the OTA via the popup window saying, "Blah, blah, blah, new update available."

Thank you so much for this. I will try it when I get home. Ever since I applied that OTA battery update, I haven't been able to successfully run any other ROM that I have tried. Hopefully this will be the solution that I have been looking for.
Just out of curiosity though, I have a Nandroid backup of before I applied the OTA Rom. If I restore that backup, would that do the same thing as you provide here, or would I definitely have to go through this process?

Won't work. The radio partition cannot be backed up/restored unless you have an s-off device.

Why not point to htcruu.com no premium acct necessary or wait times
Sent from my One X using xda premium

Moved to General section.

I seem to have screwed up. Upon trying these instructions, I went with solution 2, relocked the bootloader, but before doing so, I didn't flash the stock recovery, and kept with CWM.
Now I can't boot into HBOOT or the fastboot, it just brings up a textured static screen. I'm assuming that is where I went wrong.
Is there a way to un-do this?
EDIT: Just kidding. It turns out I had fastboot checked, which is why I couldn't get it to boot into HBOOT.

mastertr said:
I seem to have screwed up. Upon trying these instructions, I went with solution 2, relocked the bootloader, but before doing so, I didn't flash the stock recovery, and kept with CWM.
Now I can't boot into HBOOT or the fastboot, it just brings up a textured static screen. I'm assuming that is where I went wrong.
Is there a way to un-do this?
EDIT: Just kidding. It turns out I had fastboot checked, which is why I couldn't get it to boot into HBOOT.
Click to expand...
Click to collapse
EDIT#2: I still wasn't able to escape the rebooting, even after doing this. I installed AOKP 10 and it stayed on the Initiating Swagger screen while rebooting every minute or so...

mastertr said:
EDIT#2: I still wasn't able to escape the rebooting, even after doing this. I installed AOKP 10 and it stayed on the Initiating Swagger screen while rebooting every minute or so...
Click to expand...
Click to collapse
Did you relock the bootloader before or after flashing PK76IMG.zip? This does make a difference. My suggestion is just to go back through and try again following everything to a tee. Doesn't always work the first time.

I went with your first solution this time and followed the directions step-by-step and it was a success. I am now running AOKP 10 without any boot loop. Thanks!

Bump

It worked thank you
thanks man followed your guide and boom everything went just fine.
1st i had 1 minute problem. now i dont have any.
i confirm that anybody having 1 minute problem can solve it with this tutorial:laugh::laugh::laugh::laugh::laugh:
thanks

Have a recently purchased HTC One V thanks to the recent $49 deals. Getting ready to root, from what I read there's a good chance I'll hit this bug and need the RUU for my device.
How do I know which one it is? I loaded both links, they seem to have files for different regions and/or carriers.
TIA

BobbaLouie said:
Have a recently purchased HTC One V thanks to the recent $49 deals. Getting ready to root, from what I read there's a good chance I'll hit this bug and need the RUU for my device.
How do I know which one it is? I loaded both links, they seem to have files for different regions and/or carriers.
TIA
Click to expand...
Click to collapse
check ur version
settigs->about >software version

Is the Sprint RUU the one that works on Virgin Mobile?

Euler MD said:
Is the Sprint RUU the one that works on Virgin Mobile?
Click to expand...
Click to collapse
Yes
Sent from my One V using xda app-developers app

Thankyou for this guide. Even though I followed the steps, it didn't work. Maybe it was just my luck but I'll try again soon.

Failed to init device after factory reset

Hi,
I'm having problem with my HTC M9 device after providing factory reset from recovery. So resetting finished successfully, and after booting phone and optimizing apps I see welcome message. After selecting network connection and connecting to WiFi (I don't have problems neither with WiFI nor with the HSPA connection), it's supposed to let me log in into my Google account. Instead it I see "Loading...", "Checking info" and than it returns to the WiFi page.
I was facing the same problem, when I was installing non-stock rom on Samsung device, when gapps were rather old version , so they couldn't connect to the google servers. But here I have stock rom, s-on, and phone is locked.
So I can't neither pass initialization nor skip it. So I'm wondering is there any method how to workaround this situation. Any help is appreciated.
Thanks in advance.

Have you tried setting up the phone without a sim card and without WI-FI being activated? This way you should be able to get trough the first initialization. You can retry connecting the phone with your google account afterwards.

Flippy498 said:
Have you tried setting up the phone without a sim card and without WI-FI being activated? This way you should be able to get trough the first initialization. You can retry connecting the phone with your google account afterwards.
Click to expand...
Click to collapse
Yep. The point is, that it doesn't have any "Skip" button. If I'm not connected to the network, Next button just stays inactive... And I even can.t get into the settings, as the status bar doesn't working...
I tried to upgrade to the 4.16.709.3 with adb sideload (as currently I have 3.36.709.3), but the upgrade failed. It seems, that I retrieved firmware for 64Gb version, as it failed with the partition mapping error.

What's your current firmware version? I always skip the Wi-Fi setup and never have a SIM inserted when I initialize my phone for the first time. It's always working without any problems on this phone.
Edit: I didn't see your edit while I was writing this post. You may have borked you firmware with that failed sideload. Please try to flash a RUU. This way your phone should get fixed.

Flippy498 said:
What's your current firmware version? I always skip the Wi-Fi setup and never have a SIM inserted when I initialize my phone for the first time. It's always working without any problems on this phone.
Edit: I didn't see your edit while I was writing this post. You may have borked you firmware with that failed sideload. Please try to flash a RUU. This way your phone should get fixed.
Click to expand...
Click to collapse
Just to clarify:
For flashing RUU do I need to get S-OFF/Unlocked bootloader? Or I just should find 3.36.709.3 firmware and flash it with fastboot/sideload?

Just take a look at the RUU section of the ReadMe thread. It should answer all you questions. (For foreshadowing some information: neither S-OFF nor an unlocked bootloader are needed as long as your firmware is still a 3.x one.)

Flippy498 said:
Just take a look at the RUU section of the ReadMe thread. It should answer all you questions. (For foreshadowing some information: neither S-OFF nor an unlocked bootloader are needed as long as your firmware is still a 3.x one.)
Click to expand...
Click to collapse
Thank you so much. Flashing RUU from SD card worked like a charm!
PS. After flashing RUU (and factory reset), I was able to install OTA update to 4.16.709.3. Before it, upgrade was failing on 25% with the red triangle, as it was reported many times at forums.