hi, I have done all I could find on this site and others to no avail. I would be so thankful if there is just one person out there who can help me get this done! I have htc evo 4g lte with hboot 1.19, 2.13.651.1 and all I have been trying to do is get root with superuser. i tried to unlock and s-off too just to see if i could get closer to superuser and i am so stuck. i have windows 8 x64 and windows 7 x32 available to use. help! please! thanks!
This is the guide I used before s-off was available through dirtyracuns. It's pretty straightforward. If you're bootloader is unlocked already then all you need to do it flash the superuser zip from the guide through recovery.
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
Sent from my EVO using xda app-developers app
I have nothing altered yet. i've tried that, and command prompt sat there forever waiting to see my device, which it never does. never got the token. also, in my device manager it doesn't read ADB Interface > My HTC-- it reads Android USB Devices > My HTC. not sure if that might be an indication of what is/isn't installed/configured [im]properly on my computer.
go here http://unlimited.io/dirtyracun.htm and follow the directions to a T on your win7x32 machine, you will be unlocked with s-off.
once you're done with that, go here http://teamw.in/project/twrp2/98 and download the openrecovery-twrp-2.3.1.0-jewel.img file to the RabiesShot_WIN folder that you just used to do your s-off (because the fastboot.exe is there, just use the command prompt from that folder like you did for the racun) and use the fastboot method (boot to bootloader, vol-dwn to fastboot, pwr, plug in usb, enter "fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img" command)
after that's done you can try to reboot to recovery, though mine always boots to system the first time after i've flashed recovery, to confirm it's there, or just let the phone boot to system, plug in your USB and download the CWM installable zip from the bottom of the OP in this thread http://forum.xda-developers.com/showthread.php?t=1538053 to your USB card someplace where you know you can find it.
then power off your phone, boot to the bootloader again, pwr-dwn to recovery, hit power button, welcome to TWRP, tap Install, browse the the zip you just saved, install, reboot to system, and you have root
dangle79 said:
go here http://unlimited.io/dirtyracun.htm and follow the directions to a T on your win7x32 machine, you will be unlocked with s-off.
once you're done with that, go here http://teamw.in/project/twrp2/98 and download the openrecovery-twrp-2.3.1.0-jewel.img file to the RabiesShot_WIN folder that you just used to do your s-off (because the fastboot.exe is there, just use the command prompt from that folder like you did for the racun) and use the fastboot method (boot to bootloader, vol-dwn to fastboot, pwr, plug in usb, enter "fastboot flash recovery openrecovery-twrp-2.3.1.0-jewel.img" command)
after that's done you can try to reboot to recovery, though mine always boots to system the first time after i've flashed recovery, to confirm it's there, or just let the phone boot to system, plug in your USB and download the CWM installable zip from the bottom of the OP in this thread http://forum.xda-developers.com/showthread.php?t=1538053 to your USB card someplace where you know you can find it.
then power off your phone, boot to the bootloader again, pwr-dwn to recovery, hit power button, welcome to TWRP, tap Install, browse the the zip you just saved, install, reboot to system, and you have root
Click to expand...
Click to collapse
Thanks, im gonna have to try that tomorrow when i get to my win7 x32. Miss my good ol' evo, she was always good to me.
well then.. its unlocked, s-on. the ruu.zip was carried out just fine. gonna do it again in case i messed up
emwarf said:
well then.. its unlocked, s-on. the ruu.zip was carried out just fine. gonna do it again in case i messed up
Click to expand...
Click to collapse
remember you want to be locked after step 6 before running the RUU
pay attention to step 9 if you get that error message just do what it says, hit the up arrow to start the RUU process again. ( i had to do it twice before it actually completed fully )
I was actually able to re-use my original unlock token for step 11 from when i'd unlocked before.
so you'll lock
run RUU (will see a lot of output if it actually finishes, i think i even booted to system once to confirm)
then you'll unlock
then run the rabiesshot, which does take a while to run through completely and your phone will restart at least a half dozen times. just watch the command window and it'll say when it's totally finished
dangle79 said:
remember you want to be locked after step 6 before running the RUU
pay attention to step 9 if you get that error message just do what it says, hit the up arrow to start the RUU process again. ( i had to do it twice before it actually completed fully )
I was actually able to re-use my original unlock token for step 11 from when i'd unlocked before.
so you'll lock
run RUU (will see a lot of output if it actually finishes, i think i even booted to system once to confirm)
then you'll unlock
then run the rabiesshot, which does take a while to run through completely and your phone will restart at least a half dozen times. just watch the command window and it'll say when it's totally finished
Click to expand...
Click to collapse
MONEY! this is great. got my beloved evo back. miss being rooted so much. I was stupid and renamed a file when I downloaded it so I could identify it more easily. just had to call it the new name instead. big help you are! id still be fighting to find some updated rooting stuff on the net, or id be remaining blind to some stupid fault of my own. thank you!
took me months to find this thread. thank you jeebus. VERY HELPFUL! perhaps even sticky-worthy to nubs like myself.
in the past, using various phones, every time I flashed CM it would install SU automatically (i think)... so can I skip that step, put the chosen CM stable build on the SD card and be done with it?
richard head said:
in the past, using various phones, every time I flashed CM it would install SU automatically (i think)... so can I skip that step, put the chosen CM stable build on the SD card and be done with it?
Click to expand...
Click to collapse
correct. cm is already a rooted rom.
I like this thread. I'm going to give it a try when I get my hands on a 32 bit windows 7 PC, since I have no idea how to use liveCD.
Related
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
glitch666 said:
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
Click to expand...
Click to collapse
Well, you didn't really say what "everything just fails" means. How about giving us an error message?
While you are at it, what version of recovery is on the phone - Amon_RA v1.6.2, or some version of Clockwork?.
Same deal for the bootloader - how about an exact version number - 1.49.0000, 1.47.0000, or other?
Because your phone is already "soft-bricked", and you got it for free, and because your recovery boots up, you can try flashing "ErisMTDNuke_v0.9.zip". You can find it at this post:
http://forum.xda-developers.com/showpost.php?p=11651122&postcount=21
It has an an assert() in it that tries to block it from running on ClockworkMod, but depending on what version of recovery you have, that may not matter. Let me know if you get any errors running it. If it runs, you should be back in business; it leaves the /system, /data, and "boot" partitions of the ROM blank, so you will need to flash a ROM afterwards. Also, if you have ClockworkMod recovery on the phone, you should consider getting it off of there, and putting one of the two Amon_RA recovery variants on there.
You might find the entire thread that contains the above post very useful, as it describes a method for installing the S-OFF bootloader using the "SoSickWiTiT" rooting method, as well as other tricks such as using fastboot to soft-load recoveries without writing them to flash; that full thread is here:
http://forum.xda-developers.com/showthread.php?p=11652502
Please provide full details on what works / doesn't work, particularly with "ErisMTDNuke_v0.9.zip" - it has only been used on 3 phones so far (worked on all three, though).
cheers
bftb0
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
glitch666 said:
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
Click to expand...
Click to collapse
OK, that is completely different. It is impossible to load a dev ROM using the stock recovery <2e>
Did you try the "wipe data/factory reset procedure" of the recovery menu, or have you already done that and then the phone hangs at the three droids?
bftb0
If the stock ( <2e> ) recovery factory reset does not work, then the method of last resort is going to be to try and get the S-OFF bootloader onto the phone using the "SoSickWiTiT" rooting method.
Generally what happens - if you have corrupted flash memory partitions - is that parts of this install will fail, but getting the engineering bootloader (1.49.2000 S-OFF) onto the phone will succeed - and from there you can leverage the behaviors of the S-OFF bootloader to get a custom recovery running (by using fastboot). Once that happens, you can run the ErisMTDNuke_v0.9.zip flash to erase the /system, /data, and "boot" partitions, so that a subsequent ROM flashing operation will succeed (probably, no guarantees).
The way the "SoSicWiTiT" rooting method works, you run the "Official 2.1 RUU" Utility on the PC - but just before it is ready to start writing to the phone (after it has unpacked all it's temporary files and installed drivers for you), you take the "Root PB00IMG.ZIP" file, rename it to "rom.zip", and replace the "rom.zip" file unpacked in the temporary file area of the RUU. This gets the S-OFF bootloader installed (at a minimum, possibly the whole rom if your problem is not flash memory page corruption).
The thread I mentioned above has more details; ask questions if you don't understand something.
bftb0
PS You should be doing all of these operations with a well charged battery - 100% is a good place to start. Don't let the phone sit in HBOOT or FASTBOOT mode for extended periods of time - the battery will discharge rapidly, even if the phone is plugged in to the charger.
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
glitch666 said:
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
Click to expand...
Click to collapse
OK. Good luck.
The Root PB00IMG.ZIP and the "Official 2.1 RUU" can be found here:
Consolidated HTC RUU, Leak, and OTA Downloads
Amon_RA's original (v1.6.2) recovery is located here
If you don't have a version of fastboot on your PC/workstation already, you can find different platform versions of it a short distance down the HTC's developer page for the ADP.
If you can get the S-OFF bootloader onto the phone, then you can flash Amon_RA's recovery from the PC with a single command:
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
If you don't already have USB drivers installed on your PC, the RUU utility should be able to do it for you automatically (although ymmv depending on your Xp/Vista/Win7/x32/x64 variety).
Let me know how things go.
bftb0
PS It is worth repeating - make sure your phone is well charged when you are doing any flashing.
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
glitch666 said:
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
Click to expand...
Click to collapse
Standing by.
No matter what the official 2.1 RUU gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things. Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
PS -
I might have mentioned it in that other thread, but anyway: the RUU utility will get the phone to cooperate if the phone is put into fastboot mode (or RUU mode). Normally it is expected that the phone will be booted normally when you start up the RUU... but that (obviously) isn't an option for a soft-bricked phone.
cheers
glitch666 said:
No matter what the official 2.1 ruu gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things.
Click to expand...
Click to collapse
Rats. Does that happen immediately after the RUU starts up, or only when you tell it to begin the flashing operation?
Here's another wild straw to grasp at.
If you plug the phone into your PC, and then cold-start it (normal boot), do you hear 2 USB sequences at about 5 and 9 seconds, respectively? If the kernel is alive, but looping on something.... and the prior user had USB debugging enabled, and it's a 2.1 ROM, we can probably still root it by hand across ADB.
does "adb devices" give you anything 15 or more seconds after boot-up, or does your (Windows) device manager indicate a "Composite Interface"?
bftb0
Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
Click to expand...
Click to collapse
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
No it goes all the way to the flashing processes after the phone goes into bootloader mode. then stops and gives me the error, now with adb when I turn the phone on I hear one chime and then get a device not recognized and no output from adb. Did you see my last post on the other page I edited it about the bootloaders, its says its going from 2.37.605.4 to 2.36.605.1. Sorry you posted before me so ignore this last tid bit.
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
I would think that you are starting the process with the phone in FASTBOOT mode, right?
bftb0 said:
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
Click to expand...
Click to collapse
I am not getting anything from adb.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
Click to expand...
Click to collapse
Yup it stayed the same.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
Click to expand...
Click to collapse
First I put the phone into fastboot mode, then fire up RUU and it kicks the phone to a black screen with an htc logo in the middle and trys to flash it(the RUU says its putting the phone into bootloader mode so I guess thats what its in when it restarts to the htc logo).
Don't Quote me but I know the Eris is Almost like my Hero, and with the Hero there's a way to Get it into the Fastboot I Think by Holding Volume Up and Powering on the Phone! Then you Should be Able to Run the Latest RUU for the Eris... Hopefully that will get you back Right!!
Good Luck!
Sent from my Hero using XDA App
I rooted my rezound and wanted to update my rezound to ics os I followed the step exactly but when I rebooted I got stuck on the white screen. I took out the sd card and deleted the zip file and download the file again put the sd card back into the rezound but same thing. Now I can't get back to old 2.3.4 os i was using before because the post said do a wipe all data can someone help me with this to get my phone back to working order. I don't care if it is android 2.3.4 or ics 4.0 plase help.
I would first delete the PHzip file so you can start over.
Are you able to get into fastboot?
If so, check what mainver you are on with the following command:
fastboot getvar all
Also, check if you can get into recovery. Do you have Amon Ra on there? Did you make a nandroid before trying to flash ICS? If you made a nandroid and can get into recovery then restore that. If you didn't make one make a mental note to always make one before you flash ANYTHING on your phone.
If you can't restore, after you get your mainver, try to run RUU to get you back to stock. You need to relock the phone before running this.
Use the file from here that corresponds to your mainver:
http://www.filefactory.com/f/c2e320ee1d5c7886/
(Link from this thread http://forum.xda-developers.com/showthread.php?t=1338916)
If your mainver is 3.xx then you are up to ICS and will need to find a thread about getting back from that mainver to stock. I know I've seen one or two.
I had that same screen after flashing my first ROM, and in my case it was that it couldn't install the lower mainver in the ROM kernel (most are 1.x) since I was already on 2.x from the OTA. You probably need a different kernel to flash that has your version. Look in Rezound Android Development for a thread titled [KERNEL] Assorted stock kernels, then get the one you need based on what you learn from the previous reply and flash in recovery.
Sent from my ADR6425LVW using XDA App
spitzaf said:
I had that same screen after flashing my first ROM, and in my case it was that it couldn't install the lower mainver in the ROM kernel (most are 1.x) since I was already on 2.x from the OTA. You probably need a different kernel to flash that has your version. Look in Rezound Android Development for a thread titled [KERNEL] Assorted stock kernels, then get the one you need based on what you learn from the previous reply and flash in recovery.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
This is the thread I believe:
http://forum.xda-developers.com/showthread.php?p=22076459
If just the kernel doesn't work, another thing you can try besides RUU is flashing a Stock OTA ROM. You can use con247's Stock OTA ROM instead of running the RUU.
http://forum.xda-developers.com/showthread.php?p=21880389
Here are the steps to take to accomplish that:
1) use Amon Ra to flash con's vigorStock OTA ROM. It will do its thing then reboot to hboot. I think it then asks you if you want to update. Don't do it yet.
2) At this point you want to relock. So go into fastboot on the phone. Using adb/fastboot type the following at the cmd prompt:
fastboot oem lock
3) Reboot phone and let it flash the PHzip file. It should reboot completely when it's finished.
4) delete the PHzip file using a file explorer app like ES File Explorer or Root Explorer.
5) get the phone back into fastboot. Unlock again using adb/fastboot. I don't remember the exact command but you can find that in the guide for unlocking.
6) reinstall su using Amon Ra.
Now you should be stock OTA rooted with the new goodies.
i can't even get into the command promt it scolls down really fast and closes. when i went to sdk manager all the 4.0.3 boxes were checked does that mean i hane ics 4.0.3?
Sorry yes i can get into fastboot iv'e tried everything i can search for. Am gonna try getting a different kernel for the 4.0.3 ics
Well i install a custom rom and kernel but before i installed i did a wipe and restore to factory and i wiped delvek and then sared the install of new kernel and custom rom. am i missing somgthing. If i were to try to back up android 2.3.4 from my girlfriend lg revolution would i be abould to exract only the android 2.3.4 and erase the lg and somehow get sense 3.5. I dont know am new to this. I rooted the phone fine with no prob and i thought that an update would be easy. I did have amon ra but now i cant locate it on my sd card. I even tried the PH98IMG.zip thing and that didnt work. I will try anything please help and dont give up on me. Oh and is there another way to get the command promt up.
Everything you need can be found in these Rezound forums.
So you can get into fastboot. That's good.
Do you still have your computer set up from when you unlocked the phone? If not, download the mini sdk that MrSmith317 made that I've attached and place that in the C: directory of your computer and name it something easy, mine is named android-flasher. Then just always keep it there as you will need to use it often when modding your phone.
1) get the sdk working on your computer
2) On your phone, do a battery pull, then boot it into fastboot and then connect it to your computer.
3) Type the following at your computer's cmd prompt:
fastboot getvar all
and find out what mainver you are on.
* If you are on a mainver that starts with 3.x then you cannot run the RUUs. I will try to find out what you should do in that case. If your mainver starts with 1.x or 2.x then continue onto step 4.
4) Relock your phone by typing the following:
fastboot oem lock
5) Download the RUU for your mainver to your computer. Use the file from here that corresponds to your mainver:
http://www.filefactory.com/f/c2e320ee1d5c7886/
This is an exe file so just run it on your pc with your phone attached. I know you need to be locked, I think you need HTC Sync installed, so if it's not working search for those answers, it will work, others have done it. Now you are back to stock.
5) Unlock your phone again using the same unlock bin file you got before by putting it in the same folder you are now using for sdk. Type the following command:
fastboot flash unlocktoken Unlock_code.bin
If you don't have it obtain a new one by following the same steps you did before to get it originally. Here is a guide for that:
http://forum.xda-developers.com/showpost.php?p=20780879&postcount=1
Now you should be stock and unlocked.
6) Flash Amon Ra in fastboot. Get the lateset version, 3.13. here:
http://www.mediafire.com/?chpoxzb8bl4nn2b
Type the following command to flash it:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Now you should have Amon Ra on your phone.
7) Root your phone by installing su using Amon Ra. Go to the developer menu and find the option in there.
Now you should be stock, unlocked and rooted.
8) MAKE A NANDROID BACK UP NOW AND LABEL IT.
9) Flash a new ROM.
*** If your mainver is 3.x try this thread to see if you can come up with a method to go back to stock. I haven't looked into this since I have not ventured into ICS land as of yet.
http://forum.xda-developers.com/showthread.php?t=1459347
There are also some threads about getting back to stock from ICS I think so here are my search results for "stock ics" in the thread title and you can probably find an answer in there somewhere.
Hope this helps you get back up and running.
OK nevermind I got it. I just download mik roms and the kernel right under ineffabilis rom and the link for the kernal is right under it. I had to do the steps twice but it work finally like at 430 in the morning. I turned off the computer and went to bed. The first thing I did when I woke up was check my phone and it was still working. Phone calls,text wifi pretty much all features are working. So i decided to write an update to let anybody know that if you have trouble fixing white htc screen dont worry it can be fixed. Am verying new to this and if I can fix this anyone can. I will check back on this post to see if any needs help. Thank you for the people who tried to help me in my post. Now I can be one of the people who help others now that I know who to root and fix the white sceen.
If you haven't done so, make a nandroid right now so you can always go back to that if anything gets messed up.
The "people" who tried to help you was me, so maybe you can hit my "thanks" button.
Just a detailed messages of What I did.
1) I erased any PH98IMG.zip or any other roms I download so the sdcard should have no roms,kernels or anything you downloaded to fix the white htc screen. What I did was use my girlfriend LG Revolution to insert my sdcard to erase any roms or whatever I tried to use to fix before.
2) put the sdcard back into the same phone and hold down the - volume and the power key to get to HBOOT screen. On this part I always did the battery pull but I left the back cover off up to you if you want to put it back on I guess it doesnt really matter and connect your phone to your computer.
3) Push the volume button down til you get to recovery and push the power button once to select recovery.
4) push the -volume til you get to USB-MS TOGGLE and push the power button once. Now go to USB-MS Toggle SDCard now your SDCard is read by your computer.
5) Now go to this website and dont read everything just use download link about half way down the web page. Ineffabilis V1.0 make sure to skip the ad first then the real download should pop up. Now click SAVEAS and when the files come up to choose where to save left click once to highlight your SDCard or removeable stroage and click save. Now do the same thing for the download right under Ineffabilis V1.0 named stock rooted kernel (flash in bootloader)
http://themikmik.com/showthread.php...-0-12-31-11-Sense-3-5-Beats-Tweaks-1-02-605-6
thank you so much guys from themikmik.com you saved my phone
6) After dowload is complete press power to disable USB-MS. Now push power once to return to recovery menu and disconnect your phone from the computer. Go down to wipe push power once to select. push power once on Wipe ALL data/factory reset and push power again to start the wipe. After that is done scoll down to Wipe Dalvik-cache after that is done go back to the recovery menu.
7) Now go to flash zip menu and push power once. Go to choose zip from sdcard now install the kernel and then the rom you downloaded.
9) once it is complete go to re boot system now and push the power button. and your done it will stay on the white screen for about 20 min and start up.
more info my s-on.
Just thought I would share this good luck.
bbarlow26 said:
OK nevermind I got it. I just download mik roms and the kernel right under ineffabilis rom and the link for the kernal is right under it. I had to do the steps twice but it work finally like at 430 in the morning. I turned off the computer and went to bed. The first thing I did when I woke up was check my phone and it was still working. Phone calls,text wifi pretty much all features are working. So i decided to write an update to let anybody know that if you have trouble fixing white htc screen dont worry it can be fixed. Am verying new to this and if I can fix this anyone can. I will check back on this post to see if any needs help. Thank you for the people who tried to help me in my post. Now I can be one of the people who help others now that I know who to root and fix the white sceen.
Click to expand...
Click to collapse
Also erase or rename the PH98IMG.zip file from the root directory of your SDCARD. It could save you some headaches in the future.
When I first got my Rezound months and months ago, I found and installed one of the stock, rooted ROMS on this site, and installed it.
Much to my annoyance, Verizon has been trying to push the latest update to my phone, so I came back to get the latest relevant ROM. I found http://forum.xda-developers.com/showthread.php?t=1835422 ("stock rooted deodexed 4.03.605.02") and flashed it from Recovery.
The problem is, whenever I try to boot the phone, it gets to the white screen with the green HTC logo, and just sits there. Did I miss a step or something? It's been a long while since I last flashed a ROM, and I'm sure I forgot something...
Thanks.
beleynn said:
When I first got my Rezound months and months ago, I found and installed one of the stock, rooted ROMS on this site, and installed it.
Much to my annoyance, Verizon has been trying to push the latest update to my phone, so I came back to get the latest relevant ROM. I found http://forum.xda-developers.com/showthread.php?t=1835422 ("stock rooted deodexed 4.03.605.02") and flashed it from Recovery.
The problem is, whenever I try to boot the phone, it gets to the white screen with the green HTC logo, and just sits there. Did I miss a step or something? It's been a long while since I last flashed a ROM, and I'm sure I forgot something...
Thanks.
Click to expand...
Click to collapse
looks like you tried to update to a ICS rom from a stock rom.
are you s-off or dev unlocked?
synisterwolf said:
looks like you tried to update to a ICS rom from a stock rom.
are you s-off or dev unlocked?
Click to expand...
Click to collapse
Dev unlocked.
beleynn said:
Dev unlocked.
Click to expand...
Click to collapse
you are going to need to re lock the bootloader and run the ruu.
this will wipe your internal sd card so please back it up
here are the steps:
1. back up rom
2. back up internal sd card
3. fastboot oem lock command
4. download the latest ruu
5. pull the zip out of it and name it PH98IMG.zip
6. place on root of external sd card
7. make sure you have 70% or more on the battery
8. boot into hboot and let it run.
8.1 first pass will be quick and it will ask you to reboot, say yes and grab a beer because the next part will take some time.
9. boot into stock rom
10. dev unlock and all that fun stuff again
synisterwolf said:
you are going to need to re lock the bootloader and run the ruu.
this will wipe your internal sd card so please back it up
here are the steps:
1. back up rom
2. back up internal sd card
3. fastboot oem lock command
4. download the latest ruu
5. pull the zip out of it and name it PH98IMG.zip
6. place on root of external sd card
7. make sure you have 70% or more on the battery
8. boot into hboot and let it run.
8.1 first pass will be quick and it will ask you to reboot, say yes and grab a beer because the next part will take some time.
9. boot into stock rom
10. dev unlock and all that fun stuff again
Click to expand...
Click to collapse
Thanks, but a few questions:
first, when I first got the phone and rooted it, S-Off wasn't available at the time (which is why I didn't do it then). Would it be better (and/or easier) to do that instead of dev unlock?
second, how do I "fastboot oem lock"? It's been months since I last flashed a ROM, and, as always, I forgot how to do these things.
Thanks again.
beleynn said:
Thanks, but a few questions:
first, when I first got the phone and rooted it, S-Off wasn't available at the time (which is why I didn't do it then). Would it be better (and/or easier) to do that instead of dev unlock?
second, how do I "fastboot oem lock"? It's been months since I last flashed a ROM, and, as always, I forgot how to do these things.
Thanks again.
Click to expand...
Click to collapse
s-off is a lot easier. i would recommend it. makes updating easy but you do run the risk of a brick so be careful
to re lock the bootloader you need to plug your phone into the pc.
make sure ADB debuging is on
then CD into your folder with ADB and Fastboot. (for me is C:\android )
then you type " fastboot oem lock"
you will see it say lock on top.
(if you are going to s-off then do not run this command. you need to be dev unlocked for s-off to work)
EDIT:
if you dont have ADB or Fastboot. i have a mini version for you to use. it will have everything needed to do this without having to download the whole android SDK link
synisterwolf said:
s-off is a lot easier. i would recommend it. makes updating easy but you do run the risk of a brick so be careful
to re lock the bootloader you need to plug your phone into the pc.
make sure ADB debuging is on
then CD into your folder with ADB and Fastboot. (for me is C:\android )
then you type " fastboot oem lock"
you will see it say lock on top.
(if you are going to s-off then do not run this command. you need to be dev unlocked for s-off to work)
EDIT:
if you dont have ADB or Fastboot. i have a mini version for you to use. it will have everything needed to do this without having to download the whole android SDK link
Click to expand...
Click to collapse
I *had* ADB, then I built a new PC, so thanks for the link.
Once I do S-Off, do I still follow the other steps except for 3?
synisterwolf said:
s-off is a lot easier. i would recommend it. makes updating easy but you do run the risk of a brick so be careful
to re lock the bootloader you need to plug your phone into the pc.
make sure ADB debuging is on
then CD into your folder with ADB and Fastboot. (for me is C:\android )
then you type " fastboot oem lock"
you will see it say lock on top.
(if you are going to s-off then do not run this command. you need to be dev unlocked for s-off to work)
EDIT:
if you dont have ADB or Fastboot. i have a mini version for you to use. it will have everything needed to do this without having to download the whole android SDK link
Click to expand...
Click to collapse
Ok, so I got to step 9 no problem (your ADB/Fastbook download was 1000x easier than downloading the whole damn package from Google).
Can I now just load up the rooted stock ROM I found earlier, or do I have to do the Dev unlock first?
beleynn said:
I *had* ADB, then I built a new PC, so thanks for the link.
Once I do S-Off, do I still follow the other steps except for 3?
Click to expand...
Click to collapse
If you are s-off you dont need to OEM lock the phone because s-off > dev unlock
so once you are s-off all you need to do is this:
1. download RUU of your choice
2. place on the root of the sd card
3. back up your internal sd because it will be wiped
4. make sure you have 70% battery or better
5. boot into hboot and let hboot take care of the rest.
5.1 first pass of the install will go quickly and ask for a reboot. it will boot back into hboot and continue the install.
6. boot into the stock rom once.
or if you want s-on
1. do the htc dev unlock fun
2. need to load up an engineering hboot to do fastboot commands.
once you have dev unlock then you can do recovery, then load any ICS rom that is meant for our phone. if you wanted to go back to GB you would need s-off so you can downgrade with a GB RUU. (but why would we want to go backwards. )
optional
if you want to install a recovery and you want to do it the fastboot way, you will need an engineering hboot which you can get from the s-off site
or
if you find a recovery that is in zip form just let hboot install it for you.
My phone is stuck in a bootloop at the white HTC screen. I am able to go to the HBOOT screen but I can't boot into recovery. Also, my phone doesn't show up when I plug it into the computer. It does say FASTBOOT USB though. Also, I have relocked the bootloader. I'm on Hboot 2.27. I have tried flashing the RUU but that hasn't done anything.
At this point I just want my phone working right now. I wouldn't mind losing root and doing a full reset if it meant my phone was working. Also I would like to point out that my phone won't charge its battery. I had to buy a new battery that has a charge on it to use my phone.
Thanks!
So you tried flashing an RUU through bootloader with a higher version than what you were on before, it flashed successfully, and it still won't boot? Did you try flashing the RUU twice? If not, try. If you have already, someone else will have to help you. You can also flash an RUU from your computer using fastboot if it's not working from the bootloader, but I'm not sure what the command would be. Just keep in mind that any device that fastboot recognizes is not at all bricked.
Did you try flashing a recovery in hboot?
Tyler 3 said:
My phone is stuck in a bootloop at the white HTC screen. I am able to go to the HBOOT screen but I can't boot into recovery. Also, my phone doesn't show up when I plug it into the computer. It does say FASTBOOT USB though. Also, I have relocked the bootloader. I'm on Hboot 2.27. I have tried flashing the RUU but that hasn't done anything.
At this point I just want my phone working right now. I wouldn't mind losing root and doing a full reset if it meant my phone was working. Also I would like to point out that my phone won't charge its battery. I had to buy a new battery that has a charge on it to use my phone.
Thanks!
Click to expand...
Click to collapse
Were you using clockwork mod recovery?
You need to flash the RUU twice, and that means that it will probably reboot itself back to hboot and then you have to select bootloader again maybe in order to let it see the RUU and continue, do NOT count this as the second RUU flash, even if it reboots a few times and you restart it or it restarts itself, let it update until you get to the screen that says update successful press power to reboot. Now press power and count that as the first time, let it reboot and then once it boots to the first screen you want to pull the battery and boot to hboot again and say yes to the update again and continue until it says update complete, press power to reboot and then let the phone boot and you can skip through the setup screens without signing in.
Now that the phone is booted, just run the command to unlock the bootloader. Your Unlock_code.bin file should still be in your fastboot folder so it only takes running the command "Fastboot flash unlocktoken Unlock_code.bin" in the command prompt. If your fastboot.exe is located inside the Platform-Tools folder, then back out to where you're looking at the Platform Tools folder, hold shift on your keyboard and right click on the folder, choose open command window here. Then type the command I put in quotes up above, and say yes to the unlock on your phone.
That's why you skipped through the setup earlier, no use in signing in until after you unlock because the unlock wipes the phone clean.
With your bootloader unlocked and phone working like it should, you will want to flash a custom recovery. DO NOT flash the official clockwork mod or you will have the battery problem you're currently experiencing. I would flash amon ra 3.15, because it just works, but if you want to use something else, use Fly Half's recoveries which are posted in the development section and do not update your recovery with rom manager, do not even get close enough to rom manager to let your phone smell the apk, it may get sick.
I am trying to update to a new ICS rom and was able to update the radio with the file PG05IMG.zip but unfortunately put it on the internal memory. The phone will no longer boot up. I can get into recovery but the phone immediately searches for the PG05IMG.zip file to update the radio and won't allow any other menu choices. Is there a way to delete the file? Is there a way to force the T-bolt into recovery? Or is there something of an .SBF file that I can flash using Odin or something.
Thanks for any help you can give.
I've never heard of someone putting the image on the system partition and it flashing. If it is still on the root of your SD card put the SD card in a reader and erase or rename the image.
Sent from my Nexus 7 using Tapatalk 2
Hate to say but I didn't have the sd card in the phone at the time so the file was placed onto the internal memory. The phone when connected does show in windows as being a cd drive but I cannot access it.
No you cant access system memory from a oc without using adb. Try using adb if it recognizes it and use adb pull PG05IMG.zip
Sent from my Nexus 7 using Tapatalk 2
don't suppose there is a quick and easy guide for the extreme noob?
Yea I'm not getting into how to install adb. It isn't hard but its to late for me to get on that right now. Google is your best friend here. Google how to setup adb for windows xx or Linux or whatever setup you have. Its fairly easy to do.
Sent from my Nexus 7 using Tapatalk 2
was able to delete the file. All's good in Thunderbolt land. Thanks for the assistance.
recovery tease
Ok here is the problem, rooted my tbolt after the recent update using revo.
I was able to keep "s-on" with root access etc. Had it good for about a month
then I tried to uninstall a program, it rebooted kinda funky and booted up
but without a lock screen. then it would run slow. at the time i was using smart laucher
and in my brilance I thought unistalling the laucher, it would go back to the htc sense
oem laucher....but then nothing...well not nothing, the status bar was there, so was the singal
strength, battery life. tried running recovery and my problem is, that I can get the bootloader
up but when I select recovery, I get the 2 arrowrs in a circle around a arrow pointing down
at the little phone there... then it turns to the red triangle with the "!".
tried several times. checked the sd card and removed the PG05img (whatever the zip image is),
finally tried the factory reset....just gives a long status bar, reboots after five minutes
get the thunderbolt screen to come up and it goes back to the black screen with the status
bar like above. Its like the system booted without touch screen or any type of laucher.
Now the other problem I have is usb doesn't recognize in my pc... I was bumed but
I do have a sd card reader and I have tried a few PG05IMG.zip files( the no_hboot and others)
but no good though. so far when using the fastboot method it finds the zip file tries to run an
sometimes it says in green writing, "no image found or wrong image" skips a line Parsing...
and depending on the zip file I have in root with my fingers crossed a blue status bar comes
up in the upper right corner....but still not able to get into recovery or activate the usb
to use the adb tools.
so heres what I have in bootloader:
MECHA XD SHIP S-ON
HBOOT-1.08.0000
MICROP-/
RADIO-2.03.00.0201r
eMMC-boot
Jun 28 2012, 14:56:09
and my options are
FASTBOOT
RECOVERY (doesn't work so far)
FACTORY RESET (still doesn't work)
SIMLOCK
HBOOT USB
IMAGE CRC
So anybody with clearly more knowledge than I have a way to flash an image that will repair
my recovery...or some how reenable the usb again so I can use the adb tools?
marcus_hogan81 said:
Ok here is the problem, rooted my tbolt after the recent update using revo.
I was able to keep "s-on" with root access etc. Had it good for about a month
then I tried to uninstall a program, it rebooted kinda funky and booted up
but without a lock screen. then it would run slow. at the time i was using smart laucher
and in my brilance I thought unistalling the laucher, it would go back to the htc sense
oem laucher....but then nothing...well not nothing, the status bar was there, so was the singal
strength, battery life. tried running recovery and my problem is, that I can get the bootloader
up but when I select recovery, I get the 2 arrowrs in a circle around a arrow pointing down
at the little phone there... then it turns to the red triangle with the "!".
tried several times. checked the sd card and removed the PG05img (whatever the zip image is),
finally tried the factory reset....just gives a long status bar, reboots after five minutes
get the thunderbolt screen to come up and it goes back to the black screen with the status
bar like above. Its like the system booted without touch screen or any type of laucher.
Now the other problem I have is usb doesn't recognize in my pc... I was bumed but
I do have a sd card reader and I have tried a few PG05IMG.zip files( the no_hboot and others)
but no good though. so far when using the fastboot method it finds the zip file tries to run an
sometimes it says in green writing, "no image found or wrong image" skips a line Parsing...
and depending on the zip file I have in root with my fingers crossed a blue status bar comes
up in the upper right corner....but still not able to get into recovery or activate the usb
to use the adb tools.
so heres what I have in bootloader:
MECHA XD SHIP S-ON
HBOOT-1.08.0000
MICROP-/
RADIO-2.03.00.0201r
eMMC-boot
Jun 28 2012, 14:56:09
and my options are
FASTBOOT
RECOVERY (doesn't work so far)
FACTORY RESET (still doesn't work)
SIMLOCK
HBOOT USB
IMAGE CRC
So anybody with clearly more knowledge than I have a way to flash an image that will repair
my recovery...or some how reenable the usb again so I can use the adb tools?
Click to expand...
Click to collapse
Is your bootloader locked or unlocked? Does it say some security warning?
It will be at the top when booting into the boot loader.
If its unlocked you can flash a recovery.
Sent from my Rezound using xda app-developers app
not sure if its a good thing or not but...
From what I've been reading on the forums so far an *****unlocked***** bootlaoder is a good thing
and somehow mine is. It would seem something did work when I rooted. I've been going through recovery options using the fastboot img method (still no usb help) I tried a cmw recovery img and got this error:
"Main Version is older!
Update Fail!
Press <POWER> to reboot"
:silly::silly::silly:
far as I know I am renaming the zip correctly and the hboot does try and read it.
at this point.. if there was a PG05IMG file I could use or make to flash back into the factory settings etc. I would do that and start over.
I just know if I get into recovery do a wipe and flash a new rom, could be ok. or at least get usb functioning so i can use adb. I was actually starting to enjoy the command line.
I also had a thought since the bootloader is unlocked but still has "S-ON" if that might be a issue with flashing a recovery?
You need to get s off first to flash PG05IMG files from fastboot
Sent from my ADR6400L using Tapatalk 2
try this to get full S-OFF and unlock
I believe they have it working on the latest ICS hboot as well
http://forum.xda-developers.com/showthread.php?t=1703455
success!
marcus_hogan81 said:
From what I've been reading on the forums so far an *****unlocked***** bootlaoder is a good thing
and somehow mine is. It would seem something did work when I rooted. I've been going through recovery options using the fastboot img method (still no usb help) I tried a cmw recovery img and got this error:
"Main Version is older!
Update Fail!
Press <POWER> to reboot"
:silly::silly::silly:
far as I know I am renaming the zip correctly and the hboot does try and read it.
at this point.. if there was a PG05IMG file I could use or make to flash back into the factory settings etc. I would do that and start over.
I just know if I get into recovery do a wipe and flash a new rom, could be ok. or at least get usb functioning so i can use adb. I was actually starting to enjoy the command line.
I also had a thought since the bootloader is unlocked but still has "S-ON" if that might be a issue with flashing a recovery?
Click to expand...
Click to collapse
Okay so after looking over at least 6 forms for androids, recovery, how to fastboot, flashing images etc. I came across a forum that had a step by step instruction on how to basically force usb to to work. it said it was a last resort if revo didn't give you recovery. from here: "naw forums search how to manually gain recovery.
"This should only be done if you cannot get revolutionary to successfully flash recovery for you.
1. download this pack
(sorry can't post links yet, I'm still noob)
2. extract it, so it is no longer zipped up
3. copy the unzipped folder, and paste it on the root of your c drive
4. plug your phone into your computer. turn it off. then hold volume down and the power button until you are in the bootloader. it should say revolutionary at the top. highlighted in red, it should say fastboot usb. if it says hboot, push the power button, and it should change to fastboot usb.
5. on your computer, click start, in the search bar if on win7 type cmd. if xp, click run, then type cmd
6. a command prompt should be opened. type..
cd c:\ThunderboltRecovery
(press enter)
7. then type
fastboot flash recovery recovery-clockwork-4.0.1.5-mecha.img
(press enter)
fastboot reboot
(press enter)
8. your phone should reboot, and you should have recovery!"
this method got the usb working some how (I say some how because adb wasn't working before) and basically forced a new recovery onto the bootloader, i was able to get in, wipe a few things, and about an 6 hours or so ( some of those downloads took FOREVER) i was flashed back to stock with full recovery and with superbackup all contacts and favorite apps came back.
One little hiccup not mention on that page. it maybe be common sense to the veteran user of android smart phones but when going back to stock, the radios ( your 4GLTE, gps etc) will not work properly, it will start off 4GLTE, then drop to 3G and then 1! I got my radio's from: teambamf.net and look for ics radio leaks. downloaded the radio zip, (this only took a minute) placed on sd card, renamed
PG05IMG (my favorite zip) and flashed using hboot. just followed the instructions and no more signal issues.
Thanks for the help. Good to know you aren't alone when something goes wrong.
You should now go grab the radios from our first official ics ota. They are much better than those leaked radios.
Sent from my ADR6400L using Tapatalk 2