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 cannot get into regular bootloader. It just either sits and stalls, goes to HTC screen, or just straight to recovery. This has happened on and off before but I was always able to get it after a few tries. I've been trying for 2 days since the new ICS was released by Sprint but it's been no go.
I believe I have 1.5 Hboot, but I can't tell for sure because I can't access it. I had to take the long route when I had to root with the HTC unlock thing, etc.
I've tried to get to HBoot using QuickBoot app and using the menu option within TWRP 1.1 and now 2.2 (thought that might be the problem, but guess not)...still just stalls and nothing happens after reset
I've been using only rooted OTA's on my phone and only rooted for bloatware removal and wifi tether. No custom roms. No ICS leak.
The buttons of course work. As soon as I take my finger off of the Down volume button, the phone will activate and boot up normal in some cases.
I don't know if this is causing other issues with my phone as it self reboots or freezes a few times a week. I was looking forward to ICS update because I was hoping it would fix the reboots and freezing. Everything else works fine with the phone.
Any help would be greatly appreciated.
try "adb reboot bootloader" and see if your phone gets into bootloader.
mnomaanw said:
try "adb reboot bootloader" and see if your phone gets into bootloader.
Click to expand...
Click to collapse
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
brokenmouse said:
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
Click to expand...
Click to collapse
Look under settings/battery or power saver and uncheck fastboot?
Then you can actually get into hboot.
AFAIK, adb commands work in android, fastboot commands work in bootloader.
just make sure USB DEBUGGING is checked in settings.
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Click to expand...
Click to collapse
This caused a lot of trouble for me trying to flash MeanRom and Tribulattifather's ICS OTA with 4EXT because it kept trying to go into bootloader after the install to do the "smart install" or whatever. The phone would just black out upon reboot and sit there or if I tried doing bootloader manually, it would go straight to recovery again. I was up until 4 in the morning trying to get my phone to fully boot last night...never did.
Brought my phone to work today and left it off nearly all day. I thought I was seriously screwed and would have to do a RUU update/unbrick from work. Lo and behold it went into bootloader first try.
I'm restoring a backup now through TWRP 2.2 (because it doesn't have the smart install feature). We'll see if
What do you think is causing these problems? I don't want anything crazy...just a solid ICS rom or rooted OTA. Most ROMs I read suggest using 4EXT to flash, but I'm afraid of running into this again. Any suggestions or thoughts?
as mentioned above, installed the TWRP 2.2 from bootloader and restored a backup (that worked a long time ago). Now i'm having the same issue I had last night. It won't boot up at all except to recovery again.
For most people, being s-off is the best thing to do. S-on and ICS tend to bootloop. For some reason, 4ext and flash image GUI don't seem to work well in ICS either for some.
Have you tried flashing a GB ROM?
Save the Drama for your Mama with Tapatalk 2
I'm going to have to figure out how to get back to complete stock. Everytime I flash a rom...doesn't matter what it is, the phone will say the flash is done, then reboot to...NOTHING...just a black screen. I've let it sit and nothing happens.
Followed a guide on androidcentral that had a nice restore to stock guide. Did the RUU from my computer and now it's acting normal again. It must've been really messed up because when I had it talking to ADB and did the reboot reloader command (as someone stated), the screen was solid black, though the RUU still saw it.
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
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.
Hello,
This is an odd request, but I'm in need of some help with this HTC Rezound. A bit of background first. It's not mine. I'm a G2 user (rooted and I know my way around Android hacking). This phone belongs to a friend and despite having it rooted he knows nothing about how he got there or how to fix a problem. Currently it's stuck in a bootloop. He mailed the phone to me (we live 750 miles apart) and he's hoping I might be able to assist. I can get into recovery (I'm assuming it's a custom recovery - looks like ClockworkMod) and my hope was to flash a new ROM but he stupidly neglected to send the phone to me with an SD Card. I'm wondering if there's a way to get a ROM/gapps onto the phone (internal storage) and flash from there. I see there's an option for USB-MS toggle and I've tried playing around in the internal_sd area, and I can get a G: drive to appear when choosing this and connected via USB to my computer, but when I put the ROM/gapps on there I cannot seem to access it for flashing purposes.
Sorry for the long-winded description. But is this a simple solution? Do I just need to get a hold of an SD card and put the files needed on there for flashing? Or is there a way to flash the ROM directly from internal storage?
Thanks in advance for any help you might provide.
Could you post a "fastboot getvar all" ? Without the commas.
Also one thing I would do. Flash twrp 2.6.3.0 Then mount the phone. Push the ROM using a adb push. But first could you post a fastboot getvar all ?
Sent from my Rezound running Sense 5. S-OFF
pball52998 said:
Could you post a "fastboot getvar all" ? Without the commas.
Also one thing I would do. Flash twrp 2.6.3.0 Then mount the phone. Push the ROM using a adb push. But first could you post a fastboot getvar all ?
Sent from my Rezound running Sense 5. S-OFF
Click to expand...
Click to collapse
Sorry for my noobness, but I have no idea how to do that with this phone. I know nothing about HTC devices - never owned one before.
No problem at all man, we all start somewhere for every phone company.
Okay, pull the battery out. Put it back in, volume down, power button. It should show up a white screen. With I think like 5 options, I know the first two are: fastboot and recovery. When highlighted over fastboot, press power. Then will bring you to fastboot. It'll say in red letters "FASTBOOT USB" at the top. Plug it into the computer open a cmd prompt where you fastboot/adb also known as platform-tools is. Type fastboot getvar all
Sent from my Rezound running Sense 5. S-OFF
pball52998 said:
No problem at all man, we all start somewhere for every phone company.
Okay, pull the battery out. Put it back in, volume down, power button. It should show up a white screen. With I think like 5 options, I know the first two are: fastboot and recovery. When highlighted over fastboot, press power. Then will bring you to fastboot. It'll say in red letters "FASTBOOT USB" at the top. Plug it into the computer open a cmd prompt where you fastboot/adb also known as platform-tools is. Type fastboot getvar all
Sent from my Rezound running Sense 5. S-OFF
Click to expand...
Click to collapse
Thanks for the reply. My time messing with the phone is done for the night, but I'll give that a try tomorrow.
Okay sounds good
Sent from my crappy Jailbroken apple iPad.....
Freedoms just another word for nothing left to do... Nothin' ain't worth nothing but it's free.....
It should say something in the bootloader at the top like below:
***unlocked***
Pvt ship s-off (or s-on)
Hboot version # stuff here
Radio version # stuff here
Is it s-off or s-on?
If it's secure flag is still on, you would need to extract the boot.IMG from your ROM zip and do the following command after pushing and flashing the ROM in recovery. After you do flash the ROM, boot back into bootloader and into fastboot and type the following command in PC terminal
Fastboot flash boot boot.img
Sent from my Rezound
Uzephi said:
It should say something in the bootloader at the top like below:
***unlocked***
Pvt ship s-off (or s-on)
Hboot version # stuff here
Radio version # stuff here
Is it s-off or s-on?
If it's secure flag is still on, you would need to extract the boot.IMG from your ROM zip and do the following command after pushing and flashing the ROM in recovery. After you do flash the ROM, boot back into bootloader and into fastboot and type the following command in PC terminal
Fastboot flash boot boot.img
Sent from my Rezound
Click to expand...
Click to collapse
Yep, pretty much, what I was trying to get him through first was actually pushing a ROM to the phone, also the fastboot getvar all gives almost all info. But true with that, that's probably the MOST important part of rooting and ROMing HTC lol. Although he never stated what rom he has. Trying to get him through some basics of HTC too.
Sent from my Rezound running Sense 5. S-OFF
Yeah, just wanted to put that out there in case he found it how to flash a ROM without us, he will see that post to fix his boot loop (if s-on)
Sent from my Rezound
Thanks again for the replies everyone. Very helpful. As stated before, this is an odd situation because I know nothing about rooting/ROMs for HTC and this isn't my phone.
Anyway, a bit of where I'm at and some better info regarding the phone's situation. The phone, upon attempting to boot, would just bootloop. I don't remember exactly which ROM was on there as I've since done a factory reset, but needless to say it wasn't working. Also, I happened to track down an SD card from an old phone of mine and I used the USB-MS feature in recovery to put a ROM on there for flashing. Wiped everything as I would any other phone, flashed the ROM (which stated was successful) and upon a reboot the phone just hangs on the white HTC screen. Did a bit of digging and decided to try returning to stock (he doesn't care if this phone is still rooted, just wants it working). Found this link http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ and followed the instructions exactly. Update seemed to take just fine, but again a reboot just got me stuck on the white HTC screen.
I've yet to hook this up to try the fastboot getvar thing as the computer I'm using didn't have ADB installed and I didn't have the time to do so. In the meantime any additional suggestions?
I'm attaching a pic of the phone in hboot so you can see some info that might be helpful.
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Uzephi said:
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Click to expand...
Click to collapse
Thanks for this. I think I get what you're saying, but just for the sake of clarification, one more question regarding this process.
I extract the boot.IMG from my ROM of choice, flash the ROM/gapps as I would on any other device, then go back to fastboot and run the adb commands posted earlier? Correct?
Rodeojones said:
Thanks for this. I think I get what you're saying, but just for the sake of clarification, one more question regarding this process.
I extract the boot.IMG from my ROM of choice, flash the ROM/gapps as I would on any other device, then go back to fastboot and run the adb commands posted earlier? Correct?
Click to expand...
Click to collapse
Exactly. Be sure to do exactly that command not
Fastboot boot boot.img
If you forget to say flash boot, it will just temporarily boot that kernel/boot image and not flash it to the device. Then upon reboot you will be back at step one.
Sent from my Rezound
Uzephi said:
Exactly. Be sure to do exactly that command not
Fastboot boot boot.img
If you forget to say flash boot, it will just temporarily boot that kernel/boot image and not flash it to the device. Then upon reboot you will be back at step one.
Sent from my Rezound
Click to expand...
Click to collapse
Again, thank you. Going to give this a go after my son's t-ball game. I feel like more of a noob than when I rooted my OG Droid years ago.
@Uzephi, @pball52998, thank you to for your assistance. I felt like a total noob working on a phone that wasn't mine. But I've got it up and running again. My friend Jake will be very happy (I've also told him that this is the last ROM he will ever put on here unless he learns how to do everything I just did - he didn't even know what ADB was when I told him).
Rodeojones said:
@Uzephi, @pball52998, thank you to for your assistance. I felt like a total noob working on a phone that wasn't mine. But I've got it up and running again. My friend Jake will be very happy (I've also told him that this is the last ROM he will ever put on here unless he learns how to do everything I just did - he didn't even know what ADB was when I told him).
Click to expand...
Click to collapse
Wait! He has old HBOOT and Radios, the newest radio is 1.28 he has 1.21 I think I saw.... I would suggest s-off then RUU and doing a RUU.... Or if anyone has em, the HBOOT and Radios you can flash in recovery.
pball52998 said:
Wait! He has old HBOOT and Radios, the newest radio is 1.28 he has 1.21 I think I saw.... I would suggest s-off then RUU and doing a RUU.... Or if anyone has em, the HBOOT and Radios you can flash in recovery.
Click to expand...
Click to collapse
Flashing them in recovery would be great, if there's a link to download the files. But just to be clear, despite this phone finally booking up there's more I need to do to make it 100% usable?
It is 100% usable, but you will experience less overheats and better battery life with the new firmware. I know the hboot ph98img zip is somewhere in this forum for the updated hboot and radio (for that zip you would just put in root of external SD card and in hboot it will automatically flash)
Sent from my Rezound
Uzephi said:
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Click to expand...
Click to collapse
Hello, I have been preparing to RUU back to 4.03.605.2 and want to be sure of process. I read REV3NT3CH's post on downgrading, so I downloaded the latest 2 PH89IMGs via his instructions and here's where I stand:
S Off
Hboot 2.28
Radio 2.23.10.0123r/1.23.10.0124r
also running CleanRom 4.5
Can I just place PH89IMG on sdcard to RUU or am I missing a step? Thank you in advance
Just place it in the root of SD card and reboot to your boot loader
Sent from my Rezound