• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Help - I'm bricked

9to5cynic said:
Did you try this: http://androidforums.com/evo-4g-all-things-root/398795-boot-loop.html#post3097747

What I meant by try recovery again is try to re-root, and that should install a custom recovery for you. But I think granite took the cake on this issue.
Click to expand...

When I go into "recovery" I have four options (fastboot, reboot, reboot bootloader, and power down) so I am not able to wipe anything or install from SD card. Does this mean I should just reboot and be patient with the freaking WHITE screen?
 
heroparadigm said:
When I go into "recovery" I have four options (fastboot, reboot, reboot bootloader, and power down) so I am not able to wipe anything or install from SD card. Does this mean I should just reboot and be patient with the freaking WHITE screen?
Click to expand...

Hmm looks like you don't have a custom recovery. Never seen the 'reboot bootloader' before...

Try the revolutionary tool again. The one on your computer. When it asks you to install clockwork say yes. Then flash away.
 
bfrench1990 said:
Make sure you aren't unzipping the zip. Don't put it in any folders either, put it in the root of the SD card. When you boot your phone into the bootloader, it should scan for PC36IMG.zip and find it, then ask if you want to update. Do the action that corresponds with yes. If you are s-off, and your PC36IMG.zip is in the root of the SD card, it should all go according to plan. Worst case scenario, PC36IMG.zip is corrupted, in which case you can just download amon ra again.
Click to expand...

Here's my problem, it doesn't find the file when it does the scan and I have downloaded it from three different sources and they are all legit. It says no image file found as I've stated above. Yet, the zip file is on my SD card and I have already performed a hard reset...
 
9to5cynic said:
Hmm looks like you don't have a custom recovery. Never seen the 'reboot bootloader' before...

Try the revolutionary tool again. The one on your computer. When it asks you to install clockwork say yes. Then flash away.
Click to expand...

That's a good idea too. Revolutionary should give you an option to install a recovery called clockworkmod. Personally, it's not my cup of tea, but it will do until you can get rooted proper. Seriously check out amon ra, especially if you are into sense 3.0.
 
9to5cynic said:
Hmm looks like you don't have a custom recovery. Never seen the 'reboot bootloader' before...

Try the revolutionary tool again. The one on your computer. When it asks you to install clockwork say yes. Then flash away.
Click to expand...

How am I supposed to sync the "revolutionary tool" on my computer in the cmd window if I can't boot my phone? I'm in HBOOT now and it won't recognize my phone...it just says (in the cmd on the computer) "waiting for device..."
 
heroparadigm said:
How am I supposed to sync the "revolutionary tool" on my computer in the cmd window if I can't boot my phone? I'm in HBOOT now and it won't recognize my phone...
Click to expand...

adb should still work, go to revolutionary.io, do your beta key and all. run the tool and put your beta key in, and let it do its thing. it will tell you if it was successful or not.
 
Hmm.. do you have adb up and running. It seems like I read that (while difficult) it is possible to issue ADB commands from recovery. Which might mean you can issue the commands to get the custom recovery working. Though, the only one who I can think that might even know how to do that hasn't been on in quite some time....
 
bfrench1990 said:
adb should still work, go to revolutionary.io, do your beta key and all. run the tool and put your beta key in, and let it do its thing. it will tell you if it was successful or not.
Click to expand...

Forgive my ultra N00bne$$, but what is adb and where would you suggest I download it? Thanks man...please teach the student!

I figured out what adb is...sorry LOL
 
9to5cynic said:
Hmm.. do you have adb up and running. It seems like I read that (while difficult) it is possible to issue ADB commands from recovery. Which might mean you can issue the commands to get the custom recovery working. Though, the only one who I can think that might even know how to do that hasn't been on in quite some time....
Click to expand...

Fastboot (the command window tool) will recognise a device plugged in while on the bootloader.

EDIT: You can flash a recovery with fastboot. The command is like this

fastboot flash recovery (recovery path eg c:\recovery.img)

download amon ra, but get the IMG instead of the zip, and you should be good to go once you flash it via fastboot.
 
bfrench1990 said:
Fastboot (the command window tool) will recognise a device plugged in while on the bootloader.

EDIT: You can flash a recovery with fastboot. The command is like this

fastboot flash recovery (recovery path eg c:\recovery.img)

download amon ra, but get the IMG instead of the zip, and you should be good to go once you flash it via fastboot.
Click to expand...

K, I'm working on that now. Thanks
 
I flashed that Kings Shooter ROM & it nearly bricked my phone.....like yours, it was stuck on the white "HTC Evo 4G" screen...I ran REVOlution once again and it fixed it...not sure how the problem happened though...the ROM worked for about 2 hours...
but-if you can-run REVOlution & that should fix it for you...hopefully...:D
 
broad_st_bully said:
I flashed that Kings Shooter ROM & it nearly bricked my phone.....like yours, it was stuck on the white "HTC Evo 4G" screen...I ran REVOlution once again and it fixed it...not sure how the problem happened though...the ROM worked for about 2 hours...
but-if you can-run REVOlution & that should fix it for you...hopefully...:D
Click to expand...

You shouldn't have to run Revolutionary again once you have root. I don't think it actually will do anything to fix an issue. I have seen a battery pull solve boot issues on new flashes before. I would be interested to see if others have had issues fixed by rerunning it.
 
I did a battery pull & when I put it back in it went right back to the white screen....and stayed there for another 20 minutes....I couldn't get to the bootloader or recovery either....I guess that's why they call it "bricked".....but I ran REVOlution and everything was fixed immediately after....maybe I just got lucky there...
 
Xtremedays said:
You shouldn't have to run Revolutionary again once you have root. I don't think it actually will do anything to fix an issue. I have seen a battery pull solve boot issues on new flashes before. I would be interested to see if others have had issues fixed by rerunning it.
Click to expand...

Xtreme... do you think it might have something to do with the way Revolutionary connects to the phone? I have no idea how they are actually doing it, but perhaps it does something with ADB that has some kind of command to remount something or another...?

I'm grasping at straws here.
 
9to5cynic said:
Xtreme... do you think it might have something to do with the way Revolutionary connects to the phone? I have no idea how they are actually doing it, but perhaps it does something with ADB that has some kind of command to remount something or another...?

I'm grasping at straws here.
Click to expand...

Possibly.....thinking about it, revolutionary replaces the bootloader with its own version(thus the 6.16 from 2.16). Maybe it could be used to fix some of the bricked phones that get stuck in the middle of an RUU or when selecting recovery takes them back to fastboot. Something to keep in mind if we have another on here like that.
 
Xtremedays said:
Possibly.....thinking about it, revolutionary replaces the bootloader with its own version(thus the 6.16 from 2.16). Maybe it could be used to fix some of the bricked phones that get stuck in the middle of an RUU or when selecting recovery takes them back to fastboot. Something to keep in mind if we have another on here like that.
Click to expand...

that is what i was thinking as well. because the bootloader gets changed it might fix certain issues people may have. as long as they have the new hboot 6.16. i have no way to confirm this as the revolutionary dream team have not disclosed what the exploit is.
 
ocnbrze said:
that is what i was thinking as well. because the bootloader gets changed it might fix certain issues people may have. as long as they have the new hboot 6.16. i have no way to confirm this as the revolutionary dream team have not disclosed what the exploit is.
Click to expand...

Possibly suggest it if we have someone that can't get past the bootloader. If we can get a few fixed that way, then that should tell us something about what they did.
 
You must log in or register to reply here.
Back
Top Bottom