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.

[Q] Unroot fail, cannot access recovery. fastboot loop

Hey guys,
I've search through many forums for someone with similiar problems but to no avail.
I had my EVO rooted with unrevoked 3. I needed to have my phone repaired at the sprint store and since a rooted phone constitutes a voided warranty, I attempted to UN-root. I followed the DROID DEMO 2-STEP UNROOT to the tee.
After attempting to flash the pc36img, It gave me the error of :Main version older
Tried to flash the stock ruu image, wouldn't work either. Someone told me to remove the s-on image on my sd card and replace with s-off. I did that and it let me flash the pc36img, went through all the ok's and after complete and reboot, it boots to fastboot only. Also, I cannot get into recovery(triangle screen).
I downloaded android sdk with the usb drivers so I could flash the unrevoked recovery image through adb. When I go to command prompt to enter adb, the device is not found. Im guessing because USB DEBUGGING has to be enabled on the device. Since I cannot get into recovery nor boot my OS, is there any other method of forcing usb debugging on the device?
Or, If there something else I could do to get my evo to boot normally?
Any help would be definitely appreciated(A LOT!!!)
Im not really an expert(i know, why did I play around with something im not familiar with) So please bare with me. Thanks in advance!!

You're nowhere near bricked. Quickest solution would be to push Amon_RA over fastboot, then flash the same version or older ROM as the 2-step solution so you can actually use it.
If for some reason that gives you trouble, you're still S-OFF so just grab a rooted PC36IMG.ZIP and let the bootloader flash that one. Then you can still push Amon_RA through the OS using the Rom Manager (the one for clockwork, but which lets you flash alternate/Amon_RA recovery).
EDIT: I think the 1st method (fastboot commands) might only work on hboot 0.76 which you are probably not on. Use the 2nd method (ROM Manager), more info here: http://forum.xda-developers.com/showthread.php?t=744918

Thanks for your help! I guess I had a bad version of pc36img, I re-downloaded another version and it worked perfectly.
Thanks again, bro

S-OFF/root problems

I managed to root and install cm7rc1 with the newest radio and when i went back into fastboot, I noticed that S-ON was activated again. did a search and discovered that crazy HTC sets security and somehow i undid my S-OFF. I was going to use the .exploid root method but i can't write to the phone anymore. I think i still have clockworkmod recovery. so am i still rooted? can i even flash an OTA update. any suggestions? thanks.
(update: in my haste i forgot the search, i'll delete this if i find a solution)

To figure out if you still have root you can go into Terminal and type "su" if superuser comes up, you accept and it changes the symbol to a # then you're still root but you may not be S-OFF anymore.

First off if u just rooted it it will still have s on the only way to get soff is wilt the alpharev exploit and only way to lose soff is to reflash the hboot and cm7 does not do that so I think u never had soff unless u did the alpharev

After much reading I think I finally understand. I've been spoiled with the nexus one which obviously doesn't have this problem. This is my wife's phone. I thought that after rooting I would get s-off. Anyway, I guess without s-off I have to always update.zip into clockworkmod recovery to flash a cm rom? I am still unclear how to alpharev. Sounds like I need to burn a utility CD and then the app automatically forces s-off. Will need to read more. Thanks for the replies/help

Never got S-OFF and now I can't get get into recovery!

Ok here it is, My son Never go s-off and we somehow got a ROM to install, Magnolia_2_0_Final, this one. Now he had revolutionary on it and unlocked. The fun part is, now he can't get into recovery, it just goes to a white HTC screen. We have tried to relock the phone and go back, and tried to do all the tricks of the forums, we are still stuck. I would like for some detailed instructions on how we can get this back if at all. If you could help that would great. Thanks.

It will help if we had more detail on what you exactly have done and how you are doing it.
First with the phone on go to your settings. Look under "POWER" setting and disable fastboot.
Then I recommend pulling battery and reinsert battery. Hold volume down and power button to access hboot. The go to recovery through that.
If you have root access the down load Rom manager from market place and make sure you have recovery installed. If not download and flash from Rom manager. From the Rom manager app you can reboot into recovery.
Sent from my ADR6350 using xda premium

Recovery
We we have got into recovery and all is ok. We have updated SU and Clockworks. We are running Magnolia 2.0 *Sense 3.5, Android 2.3.5, Tweaks*, S-ON. The weird part is I have no idea how we got the rom on without S-OFF, but here we are. Now we have tried to just install the PH32IMG file and have had no luck with that. No matter what we have tried, all we get to is a loop of the boot screen.

Wait, did you unlock via HTC Unlock first? Either way, unzip the ROM zip, pull the boot image from it and follow the instructions in guide 6 in my sig to flash it in fastboot.

HTC Unlock
Yes we have it unlocked though HTC Unlock and still S-ON with the ROM. Now we just need to either be able to go back and get S-OFF so we can move forward. The problem is if we try to flash the zip from CWM, it doesn't work.

So you're going to need to go to htcdev.com and relock your bootloader. Then, follow attn1's guide to downgrade to 2.3.3, then run revolutionary. You can find guides for all of this online.

Won't turn back on after I relock it
The phone stays at the HBOOT screen and wont reset so I can't use adb devices at all because it won't see that it is plugged in. what do I do?

Coming from 2.3.5
Oh and I'm also coming from 2.3.5 if that makes any difference

I think you're gonna have to go back to S-ON a diff way. There's a thread in the general section on how. Follow it and then revolutionary s-off.

All Ideas have FAILED so far
Ok here it is, My son Never go s-off and we somehow got a ROM to install, Magnolia_2_0_Final, this one. Now he had revolutionary on it and unlocked. The fun part is, now he can't get into recovery, it just goes to a white HTC screen. We have tried to relock the phone and go back, and tried to do all the tricks of the forums, we are still stuck. I would like for some detailed instructions on how we can get this back if at all.
This is what I said to begin with. Now I thank anyone who could help in this situation. We can get into recovery, we have a rom with 2.3.5 sence 3.5, s-on, CWM, and we have tried all of the ideas so far. We need to know is there a better solution getting this phone back to stock and s-off.

[Q] State of root access, 4.3

Hey all,
I just wanted to pose a few questions. I've spent about 20 hours going through forums and articles to root my Verizon HTC One, and a heck of a lot of the information out there is very dated, and often contradictory. I've tried condensing it into a single procedure, but am having problems.
Here's the procedure for a brand new phone straight from a verizon store yesterday, running Android 4.3, with hboot 2.55, as I understand it; the information that I believe is now out of date, wrong, or not for 4.3/ 2.55; and the problem(s) I'm running into:
Procedure:
1) Unlock the bootloader and get s-off -- Firewater should be able to do this using the temproot method
2) Flash recovery mod, I was going to use CWM since it worked so nicely on my Incredible for 4 years -- this requires an unlocked bootloader and s-off, done the standard way via fastboot
3) Use CWM to flash superuser in recovery -- push the zip to sd, flash it from recovery
4) Happy times with my old set up back
Misinformation:
1) HTCdev -- no longer allowed for HTC One by Verizon, can't unlock bootloader this way. Renders a lot of the threads irrelevant now that this is not a valid route
2) rumrunner -- works for Android 2.2.4, not 2.3, and up to hboot 2.54
3) firewater "standard method" -- useless to anyone attempting to root a new device for the first time
4) "flash ARHD, then run firewater" -- again, not useful if you're trying to get CWM and SU on your phone for the first time
Problems:
1) The big one. Running temproot/ firewater, I acquire root access after running temproot, but when I run firewater after I get
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, hold power for 60 seconds !!
preparing, one moment
The first bottle is open
chugging..........
C:\adb>
Click to expand...
Click to collapse
with the adb shell crashing out, and my phone will freeze, requiring a hard reboot.
2) I got a few suggestions to use rumrunner (before I decided rumrunner was 2.2.4, from the sources I could find). The process would be going fairly smoothily, until it would crash with the error "looks like device is not rooted AND lacks an unsecure kernel. su or FU!!" I also once got an error about "unexpected process or ROM" but haven't been able to replicate it.
3) Found some advice for "flashing CWM without s-off"...that obviously didn't work, but I thought I might as well try
4) Not so much a problem as a concern...I'm a bit worried about my drivers. I think they are good and up to date, I got them from HTCsync, and have full adb and fastboot control to my device, but still...
The Jury
So, what's your take? Am I missing something obvious?

Update
atewsleybooth said:
So, what's your take? Am I missing something obvious?
Click to expand...
Click to collapse
Update
I tried going through the firewater procedure on OSX instead of Windows, with the exact same results (crashing out of adb shell). This leads me to believe that the problem is with the device, and not the computer. Does that sound right?
I switched cables, got one instance where I actually received "somebody pissed in the firewater reboot and try again." However, 2 reboots since with the same cable and port have both gone back to crashing out of the shell.

Rumrunnwr is only for 4.2.2. Firewater is for 4.3. You need to be complete stock and follow temproot method. Firewater was written for multiple devices so the whole HTC dev unlock and other methods won't work for the m7vzw. If you are on 4.4.2 then you are sol for now.

Gizmoe said:
Rumrunnwr is only for 4.2.2. Firewater is for 4.3. You need to be complete stock and follow temproot method. Firewater was written for multiple devices so the whole HTC dev unlock and other methods won't work for the m7vzw. If you are on 4.4.2 then you are sol for now.
Click to expand...
Click to collapse
I'm on full stock 4.3 device, running firewater using the temproot. I've made sure not to got to 4.4.2.

atewsleybooth said:
I'm on full stock 4.3 device, running firewater using the temproot. I've made sure not to got to 4.4.2.
Click to expand...
Click to collapse
Have u tried to factory reset the device?

Try redownloading the firewater file, mabey it was a bad download, or got corrupted somewhere along the way. If thays not the issue try below.
You shouldnt have to do this but its worth a shot. Once you aquire temp root, try pushing the su binary to /system/xbin, and the superuser.apk to /system/app. Then reboot the phone. This should technically give you root. Then try running firewater again to unlock and get s-off.

cmlusco said:
Try redownloading the firewater file, mabey it was a bad download, or got corrupted somewhere along the way. If thays not the issue try below.
You shouldnt have to do this but its worth a shot. Once you aquire temp root, try pushing the su binary to /system/xbin, and the superuser.apk to /system/app. Then reboot the phone. This should technically give you root. Then try running firewater again to unlock and get s-off.
Click to expand...
Click to collapse
I got it working. What I wound up doing was saying "No" to the first prompt from firewater, then restarting firewater, and saying "Yes." Twice this gave me "somebody pissed in the firewater," but on the third try, it went through. Not initiating firewater twice and canceling out of the first run would always crash my shell.
Go figure.

atewsleybooth said:
I got it working. What I wound up doing was saying "No" to the first prompt from firewater, then restarting firewater, and saying "Yes." Twice this gave me "somebody pissed in the firewater," but on the third try, it went through. Not initiating firewater twice and canceling out of the first run would always crash my shell.
Go figure.
Click to expand...
Click to collapse
Weird. Glad you got it to work though.