Develop Bugs

[Q] Fail-pu on HBOOT 2.02

Just wanted to get this out there. I have been trying to root all night with no luck. Hoping others with same issue will come for an offer help. Free evo accessory for anyone that can get this solved for me.

You need to provide a few more details what you've done to try and achieve root. What method did you try? What are seeing on the screen at the various steps.

I used the long method listed Here. If you're using the .exe file in the other thread, its not as reliable.

I am having the sane issue. I have tried regaw's method, the manual method listed in the hboot S-off thread, and the automated method in the other hboot thread. Everything works except flashing pc36img.zip....it throws the error he mentioned when updating radio v2, plus it throws fail-ic when trying to update bootloader (it does not say "bootloader skipped" as indicated it should in the guide). From this point forward, it will not boot past white HTC splash w/o running ruu. You can even do the rest of the guide and get a custom recovery flashed (i have done both amon-ra, and clockwork). After running ruu, S-off sticks (meaning unrevoked worked, I suppose), but you obviously don't have root. If you try to flash a custom Rom, even just a rooted version of the ruu, it throws a symlink error (something like E:fail can't symlink bin/lsmod....can't remember exact syntax, I posted it in another thread though, I'll see if u can find it). I have tried doing this from custom recovery and from toast's pc-based recovery. Is there a way for me to pull a log of what is happening when the pc36img has its errors? That may be the only way for me to give you more info than I have.

funnyrocket said:
Just wanted to get this out there. I have been trying to root all night with no luck. Hoping others with same issue will come for an offer help. Free evo accessory for anyone that can get this solved for me.
Click to expand...
Click to collapse
Look at this guys thread and also ask them to move your thread to the right forum so you can get the proper views and help
http://forum.xda-developers.com/showthread.php?t=831915

i followed the manual method, it failed with the radio pu, i completed the method, my phone would not boot it was stuck at the "htc evo" screen. So after some research I found the correct file to make my phone boot, The manual steps worked and i rotted my phone but i am unable to put a custom rom on
dl this file rename it pc36img and push it to you phone and reboot in the hboot and let it install it should pass you will have root access and clockworks custom recovery but until someone fixes the roms or gives a answer they wont work they will fail but you will have a phone and root admin.
http://forum.xda-developers.com/showthread.php?t=791019

flipper12 said:
You need to provide a few more details what you've done to try and achieve root. What method did you try? What are seeing on the screen at the various steps.
Click to expand...
Click to collapse
I used Method 3 from this zikronix's [TOOL][GUIDE] HBoot 2.02 S-OFF thread. Everything works great until I have to flash PC36IMG. It starts but gives the Radio-V2 Fail-PU and Bootloader-Fail-IC. The screen shows updated failed. Upon restart I'm at the red triangle boot screen. Can't do anything else from there.

kc_sheets said:
i followed the manual method, it failed with the radio pu, i completed the method, my phone would not boot it was stuck at the "htc evo" screen. So after some research I found the correct file to make my phone boot, The manual steps worked and i rotted my phone but i am unable to put a custom rom on
dl this file rename it pc36img and push it to you phone and reboot in the hboot and let it install it should pass you will have root access and clockworks custom recovery but until someone fixes the roms or gives a answer they wont work they will fail but you will have a phone and root admin.
I don't see what this will do for me since I don't have S-Off status yet. I can't get that far. Plus, this isn't a comeplete root. I have another Evo here that has the exact same specs, right down to Hardware 003 and I just did the Method 3 root and it went through with flying colors. So...
Click to expand...
Click to collapse

I think it is the bad blocks issue popping up again. I read about it in toast's root thread, I believe. If I am right, toast figured out a fix before. We may have to find a way to use his fix again. It was for a different bootloader, though. Might not work straight out of the box. I'm no dev, but this seems to me to be what is happening.

tejasrichard, i didnt know you got an Evo.
Come see us in #HTC-EVO on irc.freenode.net
Alot of devs hang out in irc so you guys might be able to get help there.

Use clockwork.
For some reason, amon ra doesn't work right away. You'll get fail-pu with it.

OtisFeelgood said:
tejasrichard, i didnt know you got an Evo.
Come see us in #HTC-EVO on irc.freenode.net
Alot of devs hang out in irc so you guys might be able to get help there.
Click to expand...
Click to collapse
Sup Otis! Yeah, I finally got my upgrade, lol! I'm a little late to the party, but better late than never, right? I'll stop by tomorrow and say hi (promised the missus some quality time tonight). I've got a few more things I want to try, but I'm betting whatever toast did b4 to get around the bad blocks will work again. Need to pm him and see what he thinks.

Rooting with Visonary 14 killed me phone

I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!

People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.

You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App

@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.

ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery

ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery

Anyone? Bueller?

cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.

This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.

[Q] Can I use Advanced Ace Hack Kit in recovery mode?

I have CWM installed, and i want to run the AAHK, because my phone wont load up, and maybe it will fix that.
If there is a method, someone please give me a short tutorial of it.

You are still running stock?
Don't run the hack kit if your phone isn't booting. First find out what's wrong with your cell phone. Google is a fantastic place to find answers, especially when the description of your issue is so vague.
On a second note, by asking for a tutorial it is evident you haven't used the search whether it be here in xda or google. Hence, my previous comment.
Once you have an idea of what is wrong with your cell, give a description of how the problem started, what you did to fix it and so on, then I'll be happy to help and so will others in the community.
Expand on what is going on.
Sent from a dream.

Gabouka said:
I have CWM installed, and i want to run the AAHK, because my phone wont load up, and maybe it will fix that.
If there is a method, someone please give me a short tutorial of it.
Click to expand...
Click to collapse
The hack kit wont solve that issue. If you have CWM installed then flash a custom ROM. If You are already S-OFF the Hack Kit will jam u up. If it Is a hardware issue then fix that first....it might be the volume rocker

My issue is that I am on S-ON, with custom recovery. The phone wont boot up, neither when I flash a custom rom, nor on a stock rom.
Stock roms doesn't want to install. The ruu installer says error 130. The current version of the rom on the phone is 3.13.0.0.

Hmm, seems like you're screwed buddy! I'm not too sure but maybe you can use ADB to recover it? Correct me if I'm wrong but I think that's the only way you'll fix your device
Sent from my Desire HD using Swype beta for Android!

Check this thread...http://www.androidcentral.com/gingerbread-update-htc-desire-now-available-ruu
do a google search for more info...

[Q] Bootloader - Bypassed when trying to flash Stock Image

Hi all, I followed Prototype7's method for gaining root and S-OFF via Tacoroot. I then proceeded to install Revolutionary with the CWM recovery.
I am now trying to go back to stock following CondemnedSoul's method, but whenever the PG32IMG.zip update installs, it skips [3] Bootloader and says "Bypassed". It also says "Bypassed" for [7] TP.
The update will say "Complete...", I can boot the phone once and use it normally, but every subsequent attempt to reboot the phone results in boot loops!
What am I doing wrong? Is there some way to flash the bootloader separately? Does my SD card need to be reformatted? Thanks in advance...

swenpro said:
Hi all, I followed Prototype7's method for gaining root and S-OFF via Tacoroot. I then proceeded to install Revolutionary with the CWM recovery.
I am now trying to go back to stock following CondemnedSoul's method, but whenever the PG32IMG.zip update installs, it skips [3] Bootloader and says "Bypassed". It also says "Bypassed" for [7] TP.
The update will say "Complete...", I can boot the phone once and use it normally, but every subsequent attempt to reboot the phone results in boot loops!
What am I doing wrong? Is there some way to flash the bootloader separately? Does my SD card need to be reformatted? Thanks in advance...
Click to expand...
Click to collapse
Did you flash a new radio? Can you tell us what radio you are on (settings > about phone > baseband version).

I did nothing more than the instructions given in the links I posted. To gain root via the tacoroot method I had to flash the 1.09.01.0312_vivow_Radio_PG32IMG.zip after flashing the initial RUU. But note that my radio and everything else, except the bootloader, was successfully updated using the stock image provided by CondemnedSoul.

swenpro said:
I did nothing more than the instructions given in the links I posted. To gain root via the tacoroot method I had to flash the 1.09.01.0312_vivow_Radio_PG32IMG.zip after flashing the initial RUU. But note that my radio and everything else, except the bootloader, was successfully updated using the stock image provided by CondemnedSoul.
Click to expand...
Click to collapse
I didn't use tacoroot (I rooted before it was needed), so I'm not 100% familiar with it. You'll probably have to wait for someone more familiar with it. I was just suggesting something that I've read about other users doing that tripped them up. Good luck with it, you shouldn't have to wait long for someone more helpful to come along.

Thanks for your effort.
Anyone able to help me on this?

Not sure what the [7] is, but the bootloader gets bypassed by Revolutionary's custom hboot so it can't be overwritten by an RUU or OTA, which is why you don't lose S-OFF unless you manually overwrite the hboot partition.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:49 AM ---------- Previous post was at 07:43 AM ----------
As for your issue, reflash the .0312 (or .0320, that's the one from the ICS leak) radio, the one from CS's image isn't an upgrade even though it probably is version .0622 or something like that, HTC has some weird version naming scheme that they don't even follow half the time.
Sent from my SCH-I535 using Tapatalk 2

prototype7 said:
Not sure what the [7] is, but the bootloader gets bypassed by Revolutionary's custom hboot so it can't be overwritten by an RUU or OTA, which is why you don't lose S-OFF unless you manually overwrite the hboot partition.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:49 AM ---------- Previous post was at 07:43 AM ----------
As for your issue, reflash the .0312 (or .0320, that's the one from the ICS leak) radio, the one from CS's image isn't an upgrade even though it probably is version .0622 or something like that, HTC has some weird version naming scheme that they don't even follow half the time.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! Flashing the new radio (.0312) seems to have fixed the problem, so far no bootlooping anymore.
By the way, I was on a .1111 radio after flashing the stock image. I would have wrote that sooner, but did not know until I had reflashed the phone once again where I could look at the baseband version, since it was bootlooping.
This is not a necessity, but... I was wondering how a person would flash the stock bootloader and turn it back to S-ON? Just in case I decide to sell my phone in the future, it would be "all stock".

swenpro said:
Thank you! Flashing the new radio (.0312) seems to have fixed the problem, so far no bootlooping anymore.
By the way, I was on a .1111 radio after flashing the stock image. I would have wrote that sooner, but did not know until I had reflashed the phone once again where I could look at the baseband version, since it was bootlooping.
This is not a necessity, but... I was wondering how a person would flash the stock bootloader and turn it back to S-ON? Just in case I decide to sell my phone in the future, it would be "all stock".
Click to expand...
Click to collapse
There's a guide in the general section, basically you have to flash the RUU, then extract the hboot and manually write it to the partition, it's fairly easy to do, easier than rooting it.
Sent from my SCH-I535 using Tapatalk 2

Thanks again! There are so many sections to this forum I had never noticed that sticky. Appreciate the help.

My silly n00b Question(s)
prototype7 said:
There's a guide in the general section, basically you have to flash the RUU, then extract the hboot and manually write it to the partition, it's fairly easy to do, easier than rooting it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Ok, i can't figure out what a sticky is, nevermind where to find the one you reference... Sorry.
I love XDA, it helped me root my dInc2 replacement, and that one's replacement (both after the previous phone's charge port died), and i just love it, BUT i've never had to use it except these two times, so i haven't figured out the forum stuff - like stickies - especially since i usually use NoScript normally and i don't really understand the general vs Q&A distinctions between groups of threads...
In any case - i haven't been able to find the sticky you referenced, and my searches have failed to find recent instructions regarding manually flashing the Hboot -- everything i found had download links that didn't work, except CS's stock ROM (as mentioned by the OP in this thread) - and now i've got that installed on my phone-to-send-back, so i've have successfully returned the ROM to a stock 2.3.4 GB using CS's post here on XDA, and from what i can tell/remember, flashing the HBOOT to stock (.97) will put it back exactly how it was when i got it last year - as i had to downgrade the OS but i don't think i had to touch the HBOOT (i got this phone in late March 2012)
So i'm now trying to rectify the issue that i don't know where to get the Hboot to manually flash, and, even if i had the file, i haven't found out if there is a ADB over TCP-IP that works when your USB/charge port has basically disconnected itself from the motherboard.
I was hoping that someone here might be able to help me either find the hboot file or extract what i need from CondemnedSoul's RUU (as seems to be described in prototype7's post), and give me the commands i need to do the manual flash...
If i could also get ADB over TCPIP advice, that would be awesome, but the former would be a good start...
Verizon has started to nag me for not returning the old phone sooner...
Thank you!
Also - thanks to Prototype7 for his awesome guide to s-off methods/rooting the Dinc2 -- was a life-saver for rooting the new phone so i could make use of my clockworkrecovery backup... (after some boot-looping horror, when i got an error during the update of the radio using the tacoroot method -- i restarted again from a different windows machine and it worked fine - i think the issue was the drivers on the other machine -- i'd used it to root the earlier phone, and i think it had weird drivers or something)

wntrequinx said:
Ok, i can't figure out what a sticky is, nevermind where to find the one you reference... Sorry.
I love XDA, it helped me root my dInc2 replacement, and that one's replacement (both after the previous phone's charge port died), and i just love it, BUT i've never had to use it except these two times, so i haven't figured out the forum stuff - like stickies - especially since i usually use NoScript normally and i don't really understand the general vs Q&A distinctions between groups of threads...
In any case - i haven't been able to find the sticky you referenced, and my searches have failed to find recent instructions regarding manually flashing the Hboot -- everything i found had download links that didn't work, except CS's stock ROM (as mentioned by the OP in this thread) - and now i've got that installed on my phone-to-send-back, so i've have successfully returned the ROM to a stock 2.3.4 GB using CS's post here on XDA, and from what i can tell/remember, flashing the HBOOT to stock (.97) will put it back exactly how it was when i got it last year - as i had to downgrade the OS but i don't think i had to touch the HBOOT (i got this phone in late March 2012)
So i'm now trying to rectify the issue that i don't know where to get the Hboot to manually flash, and, even if i had the file, i haven't found out if there is a ADB over TCP-IP that works when your USB/charge port has basically disconnected itself from the motherboard.
I was hoping that someone here might be able to help me either find the hboot file or extract what i need from CondemnedSoul's RUU (as seems to be described in prototype7's post), and give me the commands i need to do the manual flash...
If i could also get ADB over TCPIP advice, that would be awesome, but the former would be a good start...
Verizon has started to nag me for not returning the old phone sooner...
Thank you!
Click to expand...
Click to collapse
This is the guide I was referencing: http://forum.xda-developers.com/showthread.php?t=1466295
For ADB over TCPIP, I use ADBWireless off the market, but instead of using the adb connect command with the info it shows, use your phone's IP address shown under About phone>Status (I think that's where it is).

prototype7 said:
This is the guide I was referencing: http://forum.xda-developers.com/showthread.php?t=1466295
For ADB over TCPIP, I use ADBWireless off the market, but instead of using the adb connect command with the info it shows, use your phone's IP address shown under About phone>Status (I think that's where it is).
Click to expand...
Click to collapse
YOU ROCK. - thanks for the quick reply.
I read the guide you referenced - but the links are down, so i'll add a reply and see if that thread's OP can re-upload. If that seems to still be the correct way to un-root/S-on, then i'll see what i can do..
I had a bunch of questions, but i think I figured out the answers... i just need to go home from work and actually try out following those directions...

wntrequinx said:
YOU ROCK. - thanks for the quick reply.
I read the guide you referenced - but the links are down, so i'll add a reply and see if that thread's OP can re-upload. If that seems to still be the correct way to un-root/S-on, then i'll see what i can do..
I had a bunch of questions, but i think I figured out the answers... i just need to go home from work and actually try out following those directions...
Click to expand...
Click to collapse
See my reply in that thread, gave you updated links.

I need help!

Hi guys! So last night I tried to root and flash my Desire HD but something went wrong and it wouldn't go past the splashscreen. I could still get into the bootloader though. I used the AAHK to root it but it failed everytime and after trying some different things something went wrong. So after a lot of frustration I went to bed, and after waking up this morning I found out it wouldn't start at all. How can that be? Nothing changed.
My CID is VODAPE17. I tried to flash Sabsa Prime.
What do I do now?
Thanks in advance.

You do need help. Posting threads in the Development Section is forbidden, unless it's a new ROM.
Mods move, then I'll try to help.

Thread Moved​
Please do not post question threads in a development section.​

b3rnd.bj said:
Hi guys! So last night I tried to root and flash my Desire HD but something went wrong and it wouldn't go past the splashscreen. I could still get into the bootloader though. I used the AAHK to root it but it failed everytime and after trying some different things something went wrong. So after a lot of frustration I went to bed, and after waking up this morning I found out it wouldn't start at all. How can that be? Nothing changed.
My CID is VODAPE17. I tried to flash Sabsa Prime.
What do I do now?
Thanks in advance.
Click to expand...
Click to collapse
maybe you can read...and ask for help being a bit more precise. How did you try to flash a custom rom without being S-OFF or with an unlocked bootloader?
Why the AAHK failed? let me tell you that the Hack Kit works flawlessly unless you do not accomplish the requirements for it to work, so what is probably failing is you.
If you want to get help, be precise about what the Hack Kit session says, and what you did to your cell to end up like this.

glevitan said:
maybe you can read...and ask for help being a bit more precise. How did you try to flash a custom rom without being S-OFF or with an unlocked bootloader?
Why the AAHK failed? let me tell you that the Hack Kit works flawlessly unless you do not accomplish the requirements for it to work, so what is probably failing is you.
If you want to get help, be precise about what the Hack Kit session says, and what you did to your cell to end up like this.
Click to expand...
Click to collapse
I don't know what it said, just that it didn't work. It didn't turn S-off, it didn't install CWM, it did nothing. And then I couldn't get past the splashscreen. It now won't connect with AAHK, so I can't check what error I got. I think my pc had a hiccup when installing a new radio.
I can get into bootloader again, my volume buttons are messed up so I couldn't press it correctly.
I guess I have to flash a RUU with a goldcard right? But when I put my SD in my girlfriend's Galaxy s2 the Goldcard Helper App only shows MMC0 and MMC1. Not MMC2, which I need. Do I need another DHD for it to work? I thought the CID was memory card specific in this case.