I just downgraded my phone from hboot 1.58 to 1.40. I put the PG86IMG_1.40hboot on my sd card and rebooted into the bootloader and it started applying the PG86IMG update (downgrade?) It worked, my hboot is now 1.40 but, when the phone reboots it is now in a bootloop. So here is where I'm stuck, every time I go into the bootloader it automatically starts applying the PG86IMG that I used before I can access my recovery to delete the file. Is there a way I can get into recovery so I can delete this or any other work around for me to use?
Thanks
If you have adb setup on your pc it is easy.
With phone powered off connect usb cable to pc. Charge light will come one for a moment then go out and come back on. Now use this command on your pc. Adb reboot recovery. You will boot directly into recovery.
Without adb you will need to use a card reader on a pc to remove the file.
Sent from my PC36100 using xda app-developers app
Thank you so much.
Related
//Header information
***UNLOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
eMMC-boot
Hey guys, I recently acquired an EVO 3D in a trade deal and even though I don't want it (I plan on selling it but the cash deal + EVO 3D was worthy), I ended up being hellbent on rooting it last night. Success. Great, I threw Cyanogenmod7 on there and realized I'll have to undo the root/ROM to sell it later. I used what I believe is referred to as the REVOLUTIONARY method (using HTCDev.com, some terminal commands on my Mac, etc.)
Anyhow, didn't think it would be hard to undo what I did and I guess I was wrong. Let me tell you what I've tried so far.
I've tried using the PG86IMG.zip flash and nothing. No option (VOL UP or VOL DOWN) to even TRY installing it. Just quickly flashes the green text "No Image!" under each category (it goes too fast for me to read it) and I'm back at the boot menu. I've tried using different copies of the PG86IMG.zip with the same results (latest site acquired from: Goo-inside me, or something like that).
I've also tried using the RUU*.exe method on a Windows 7 machine. I've installed the drivers, everything checks out just fine until it actually tried to update the ROM. What happens here is that the phone reboots (as expected) and though the splash screen is different (black background with silver/gray hTc logo, semi-reflected) from the usual splash screen (white background with hTc in green), nothing happens. The software on the Windows 7 machine says "Waiting for bootloader" - which never shows up. Then it quickly gives me an error stating that the USB cable between the PC and the phone needs to be checked. Of course, there's no disconnect anywhere in the cables.
Please help! I planned on selling this device but if it's stuck in Cyanogenmod7, especially with no Google apps (couldn't get Gapps*.zip to work but whatever, not really concerned about that right now), there's no way I could sell this thing. I'm fairly knowledgeable in the basics of these matters as I have a rooted EVO 4G as well.
Anyone wanna buy an EVO 3D? HAHA
you could always flash a stock rooted rom .
You've gotta relock through adb before running the RUU.exe; then it'll work.
Hit the thanks if I helped
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
zer0xity said:
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
Click to expand...
Click to collapse
It's because of the pg86img.zip you can delete/move it away from the root of your sd card and get back into recovery... but you shouldn't need to, follow these steps:
1) Turn off phone
2) Hold power+vol down
3) Choose fastboot
4) Plug into your PC if you're not already
5) When you see FASTBOOT USB on the phone screen go back to your command prompt where you have your adb.exe, fastboot.exe, etc.
6) Type: " fastboot oem lock "
7) Aaaand you're done w/ the relocking go crazy and run your RUU.exe, don't reboot the phone or anything just run your RUU while your phone's still in HBOOT.
Edit: Oh, the adb I was talking about would kind of make everything easier; in command prompt: adb reboot bootloader AND THEN fastboot oem lock
Two steps, mhm.
I'm on it! Standby...
Okay, the adb stuff - can I do that from terminal in Mac? I tried doing it while in the appropriate folder where all that adb stuff is and I typed: adb reboot bootloader (ERROR: command not found), then I tried just: reboot bootloader (not permitted). I did try: ./fastboot-mac oem lock (successful. header now says *** RELOCKED ***).
Tried the RUU*.exe stuff on the Windows machine while in that state and again an alleged problem with the USB connection...
Sounds like we're close?
BAM! Got it. You put me on the right track with that last post. RUU still wouldn't do the reversion even though I had some drivers installed on Windows so I had to find some other drivers (some HTC3*.exe file, 13MB) and ended up running those for it to recognize the phone.
+1 to you, sir. Thank you so much!
Glad it all turned out well.
EVO 3d cdma 1.4 s-off with cwm was running cyanogen 7. went into rom manager app and super user had an update. updated ok then froze and now stuck at HTC load screen.
1. with sd card containing PG86IMG.zip: regular power up - hangs on HTC screen
2 with sd card containing PG86IMG.zip: HBoot - device ask to update (yes) tries to update (1)bootloader ... sucesss i get an ok then when prompts me to reboot it hangs at HTC again.
3. no sd card: regular power up hangs at HTC
4. no sd card: hboot will not let me go into recovery or factory data reset, just short vibrate then fastboot screen
5. blank sd card: scrolls down no img or wrong PG86IMG then after will not go into recovery or factory data reset, short vibrate then fastboot screen.
*can not get to usb debugging stuck at HTC screen
*connect to computer phone: fastboot to fastboot usb
*@command prompt,
6.adb devices,reboot-bootloader,remount, etc - no devices found. guess usb debugging needs to be on.
7.fastboot devices - i get serial #
8.fastboot flash recovery recovery.img - gets FAILED (remote not allowed) ... tried different recoveries ... named/renamed all the same
9. fastboot erase cache ... ok
10. fastboot reboot-bootloader ... ok
any ideas what i should try next?
controlofsound said:
EVO 3d cdma 1.4 s-off with cwm was running cyanogen 7. went into rom manager app and super user had an update. updated ok then froze and now stuck at HTC load screen.
1. with sd card containing PG86IMG.zip: regular power up - hangs on HTC screen
2 with sd card containing PG86IMG.zip: HBoot - device ask to update (yes) tries to update (1)bootloader ... sucesss i get an ok then when prompts me to reboot it hangs at HTC again.
3. no sd card: regular power up hangs at HTC
4. no sd card: hboot will not let me go into recovery or factory data reset, just short vibrate then fastboot screen
5. blank sd card: scrolls down no img or wrong PG86IMG then after will not go into recovery or factory data reset, short vibrate then fastboot screen.
*can not get to usb debugging stuck at HTC screen
*connect to computer phone: fastboot to fastboot usb
*@command prompt,
6.adb devices,reboot-bootloader,remount, etc - no devices found. guess usb debugging needs to be on.
7.fastboot devices - i get serial #
8.fastboot flash recovery recovery.img - gets FAILED (remote not allowed) ... tried different recoveries ... named/renamed all the same
9. fastboot erase cache ... ok
10. fastboot reboot-bootloader ... ok
any ideas what i should try next?
Click to expand...
Click to collapse
Damn, that's wild. Just from updating superuser!
The next thing I would try is running an RUU with the phone in fastboot mode, or running an RUU as a PG86IMG.zip. Hopefully one of those will run.
Sent from my PG86100 using Tapatalk
progress. the latest RUU broke through.
seems like i am now unlocked 1.5 hboot s-off.
I think i will run stock til cm9 beta hits.
I'm glad it worked for you. Since you're still s off, you can downgrade your hboot back to 1.4 if you want to. No real reason to though, other than it won't say locked.
Sent from my PG86100 using Tapatalk
k2buckley said:
I'm glad it worked for you. Since you're still s off, you can downgrade your hboot back to 1.4 if you want to. No real reason to though, other than it won't say locked.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
have you tried a different cable?
I'm not sure if it's a good suggestion because your also having issues with RUU zips but its worth a try.
My phone froze during the soff procedure. Following the direction I excited bearcontrol and restarted it in hopes that it would try to continue from where it left off. Not the case.
I'm trying to adb amon ra now but my phone isn't showing up with ADB. It automatically boots to fastboot everytime I turn it on. I remember there was a way that I could flash amon without using fastboot flash recovery.... but I can't seem to find it.
My memory card needed to be formatted when I tried to add ph98img through a card reader. I followed the directions but for some reason it only reformatted at 128kb. This isn't big enough to hold anything.
phone won't boot passed fastboot at this point.
Suggestions?
flash the SD card in a pc untill it gets formated... also did u get s-off in your Hboot?
no fastboot
Try to replace your boot image with a PH98IMG file you can find here on xda.
That will allow you to boot your phone back to the rom you had before.
I'm having this exact problem, but further cannot access ANYTHING or charge
my phone with USB cable. Am desperate to flash something to get access to USB
again.
I tried reformatting the card in another phone but it's still formats to 128kb. I picked up a new sd card and will try that when I get home tonight.
No I did not get s-off...yet
memory card error
Your sdCard was partitioned to a small readable portion and the rest unavailable when trying the S-0ff.
You can put it into a computer and use a partitioning program to get
it all back. I just used a freeware program called Mini Tool Partition Wizard Home Edition, saw many others while searching.
I am still S-0n and HTC unlocked but can't run any PH98IMG's other than the
boot install that allowed the phone to start again. Also can't get into recovery or install another recovery. It just ignores the PH98IMG in hboot.
New memory card did the trick. I'm back up and running.
After attempting to S-Off the phone yesterday afternoon and failing (it is unlocked), I'm now stuck at the infamous JPbear screen with the green arrow. I've read pretty much every post I can find on recovering from it and still cannot get the phone to boot correctly.
I flashed the boot img for the rom I was running, I created my own PH98 file with the boot image and AmonRa, I've tried to flash a complete rooted Global stock rom, as well as attempting a full flash of the rom I was running. The PH files seem to process correctly but when done I get a messaging it is parsing the file but nothing happens afterwards. On reboot I get the white HTC screen then straight to the black JPBear screen. The phone also does not recognize that it is plugged into my laptop or a wall charger, there are no LED's lit. Without the USB I cannot relock the phone so I cannot flash back to a stock RUU. Fastboot\Min-ADB\Controlbear all fail as the phone is not recognized.
Are there any other things I can try before I give up. I'm not sure if the S-Off attempt may have damaged the USB or not but it definitely does not respond. I do have the extended warranty on the phone but returning it would be a last resort.
I apologize for asking the same questions as many others but I have not been able to find an answer despite searching for most of the night.
controlbear - r
Straight from the troubleshooting page: http://unlimited.io/jbtroubleshooting.htm
shrike1978 said:
controlbear - r
Does not work. I've read the troubleshooting page and tried everything I could find before posting. Controlbear returns an error it cannot find the phone and prompts me to install the drivers and reboot. Fastboot and mini-adb return similar results (phone is not detected).
Thanks for the input.
Click to expand...
Click to collapse
Did you try placing a rom on your sdcard and flashing it in recovery, or just simply placing a signed PH98IMG.zip on your sdcard (meaning the official update)?
brando56894 said:
Did you try placing a rom on your sdcard and flashing it in recovery, or just simply placing a signed PH98IMG.zip on your sdcard (meaning the official update)?
Click to expand...
Click to collapse
I did try a ROM but have no access to recovery. When I select it fro the hboot menu, the screen flashes for a second and then goes back to hboot. I cannot load the stock RUU because the bootloader is unlocked and I have read there is no way to relock it without working USB.
Thanks for the suggestions, I appreciate the imput.
control bear makes a back up before doing the wire trick. just restore the back up?
synisterwolf said:
control bear makes a back up before doing the wire trick. just restore the back up?
Click to expand...
Click to collapse
I tried that but no go. The main issue comes down to not getting the phone recognized by the laptop. The USB port on the phone does not recognize when it is plugged in (either to a PC or the wall charger). Controlbear or other utilities cannot find the phone so I cannot execute any commands. I've been searching for a strictly SD based solution but I am SOL.
Thanks though.
gskuse said:
I tried that but no go. The main issue comes down to not getting the phone recognized by the laptop. The USB port on the phone does not recognize when it is plugged in (either to a PC or the wall charger). Controlbear or other utilities cannot find the phone so I cannot execute any commands. I've been searching for a strictly SD based solution but I am SOL.
Thanks though.
Click to expand...
Click to collapse
Can you see hboot at all?
Sent from my iPhone...
synisterwolf said:
Can you see hboot at all?
Sent from my iPhone...
Click to expand...
Click to collapse
I can boot to hboot by using power and volume keys, but I have no recovery when I select that choice. If I choose Fastboot, it will try to load a PH image if present but when it completes it says "parsing file" and then goes back to the hboot menu.
gskuse said:
I can boot to hboot by using power and volume keys, but I have no recovery when I select that choice. If I choose Fastboot, it will try to load a PH image if present but when it completes it says "parsing file" and then goes back to the hboot menu.
Click to expand...
Click to collapse
if you can get to hboot then you should ruu. it will get your phone back to working order. just make sure you oem lock before doing it if you are s-on
synisterwolf said:
if you can get to hboot then you should ruu. it will get your phone back to working order. just make sure you oem lock before doing it if you are s-on
Click to expand...
Click to collapse
I cannot relock the bootloader without access to to the phone. The laptop does not see the phone when connected to it. I cannot run the relock tool. I think the port actually died. No LED when plugged in to a wall charger or laptop USB cable. I have not been able to locate a way to relock the bootloader using the SD card.
Thanks again.
gskuse said:
I cannot relock the bootloader without access to to the phone. The laptop does not see the phone when connected to it. I cannot run the relock tool. I think the port actually died. No LED when plugged in to a wall charger or laptop USB cable. I have not been able to locate a way to relock the bootloader using the SD card.
Thanks again.
Click to expand...
Click to collapse
idk how to help then. Im sorry. can you charge the phone in any way? if not then i would let it die and send it in as a warranty replacement.
synisterwolf said:
idk how to help then. Im sorry. can you charge the phone in any way? if not then i would let it die and send it in as a warranty replacement.
Click to expand...
Click to collapse
Nah no way to charge the battery. I have a VZW store near me and will take it there for a swap.
I really appreciate your help though.:good:
The only way to recover with the control bear program is to place all the files in its own folder and then CD to that folder and run from there.I had to recover my phone once. Took me a few minutes to wrap my mind around it. Just keep reading until it makes sense.
I have been following all the posts about rooting and I managed to soft-brick my phone. I was able to temp root the phone, but I could never get superCID because the modified CID would never take. I didn't get errors, it just didn't stick. Anyway, I flashed the recovery for 2.17, but my phone took an OTA update to 2.19 a few days ago, and now I am stuck on the main screen but without the sense unlock ring. The screen works, and I can access the phone's drive and sd card, and I can adb. The bootloader shows ****TAMPERED***** (been that way for a while), and Bootloader is LOCKED. FIREBALL PVT SHIP S-ON RL, HBOOT is 1.15.0000.
Any ideas to recover to a fully booted phone?
yes had the same thing happen to me. download the ruu exe. from here http://www.androidruu.com/?developer=Fireball i used 217.605.2 ruu. put phone in fastboot connect it to computer and run ruu exe. on ur computer
I followed your reply but am not having any success . . . yet.
I go through the RUU.exe screens where I verify that I want to "upgrade" from image version 2.19.605.2 to image version 2.17.605.2.
Then RUU.exe runs to the point where it tells me the process will take 10 minutes. It then gets to "waiting for bootloader........" and the phone looks like it is rebooting and a black "HTC" screen appears. Bootloader never appears. A Windows 8 Systray error message then appears saying "USB Device Not Recognized - The last USB device connected has lost communication with the computer [or something like that]" The RUU.exe program then states: "ERROR [171] USB Connection Error. Check the following: (1) phone is connected to USB cable; (2) PC is connected to USB cable" There is no further option than to EXIT the RUU.exe. (Yes, my cable is connected to a USB 2 port).
I tried to do this twice with the same error message and the same disappointing results. The phone stays locked on the black HTC screen and I need to pull the battery to change this locked state.
I have no trouble communicating with the phone with ADB and I have root (#) at ADB Shell. I JUST loose USB communications with the phone as soon as it goes tries to load bootloader. I originally tried to run RUU.exe the way you stated by putting the phone into fastboot and then running RUU.exe, but then the program would not find the phone. What am I missing here? I have HTC drivers loaded, but I keep getting the comm error. Any more ideas?
Maybe I need to flash a recovery for 2.19.605.2? Any idea where I might find that?
OK, not sure why I didn't do this sooner, but I did a factory reset from Bootloader and it seems I am back again running the 2.19.605.2. Not sure if I can root this new OTA version using the 2.17.605.2 procedures or not, but I may give this a break for a bit.
Yeah u can't downgrade to 2.17 if ur on 2.19
Sent from my XT1060 using xda app-developers app