Mine is a HTC EVO 3D rooted gsm device currently running on 3.28.720.1 firmware. I want to flash the cool ICS v14b for which I need to downgrade the firmware to 3.28.707.1. I successfully relocked the device by using the "fastboot oem lock" command. It even shows "RELOCKED".
But when I reboot into the bootloader after placing the pg86img.zip in the root folder , the status turns back to "UNLOCKED". How do I relock the device so that I can flash the pg86img.zip and then unlock the device followed by flashing the rom using 4xt recovery.
I unlocked the bootloader using htcdev method and mine is a s-on device.
Any help would be appreciated!
You can't downgrade if you are S-ON..
EDIT : I see you edited it yourself.
Related
Hello. I have a GSM Evo 3d, 1.53.0007 hboot (unlocked via HTC Dev), after that S-OFF via JBEAR, now I'm on stock hboot locked with S-OFF. After that I can't install 4Ext. When I use fastboot i got info remote: not allowed (I supose that this is because I'm S-ON). Can I flash 4Ext directly in hboot? Does any1 have this recovery as a PG86IMG.ZIP? Or is there any other way to flash it? Cheers
c000ler said:
Hello. I have a GSM Evo 3d, 1.53.0007 hboot (unlocked via HTC Dev), after that S-OFF via JBEAR, now I'm on stock hboot locked with S-OFF. After that I can't install 4Ext. When I use fastboot i got info remote: not allowed (I supose that this is because I'm S-ON). Can I flash 4Ext directly in hboot? Does any1 have this recovery as a PG86ING.ZIP? Or is there any other way to flash it? Cheers
Click to expand...
Click to collapse
JBear will leave the bootloader locked which will prevent most fastboot commands from running if you didn't choose the JuopunutBear bootloader when prompted by controlbear. If you don't have "JuopunutBear" at the top of your bootloader you can download the JBear custom bootloader for your phone and Android version (GB or ICS) from the unlimted.io website and install it using the instructions on that site, then you should be able to run the fastboot commands needed for flashing.
ramjet73
c000ler said:
Hello. I have a GSM Evo 3d, 1.53.0007 hboot (unlocked via HTC Dev), after that S-OFF via JBEAR, now I'm on stock hboot locked with S-OFF. After that I can't install 4Ext. When I use fastboot i got info remote: not allowed (I supose that this is because I'm S-ON). Can I flash 4Ext directly in hboot? Does any1 have this recovery as a PG86IMG.ZIP? Or is there any other way to flash it? Cheers
Click to expand...
Click to collapse
There's 2 simple ways to do this, depending on whether you want jb hboot or not.
Regardless of whether you want it or not, download the correct hboot for your device from here: http://unlimited.io/downloads/hboots/
If you want to change your hboot from ***LOCKED*** to =Juopunutbear= :
then rename your recovery image to "recovery.img" & drag-and-drop the recovery.img file onto jb_hboot.zip to add it to the zip
Then, use the commands given here to flash it: http://unlimited.io/jbhboots.htm
If you want to keep your hboot as ***LOCKED*** :
then rename your recovery image to "recovery.img" & drag-and-drop the recovery.img file onto jb_hboot.zip to add it to the zip
Open the jb_hboot.zip file & delete the .nb0 file that might have a long name (something like"hboot_....nb0"
Then, use the commands given here to flash it: http://unlimited.io/jbhboots.htm
I've flashed Jbear hboot, everything works like a charm. Restoring my backup now. Thanks for fast answers.
c000ler said:
I've flashed Jbear hboot, everything works like a charm. Restoring my backup now. Thanks for fast answers.
Click to expand...
Click to collapse
:good: And there's a button for thanks mate
Can I use the same method to flash only bootloader (official 1.53.0007). This is what i thought about: extract hboot from ruu (hboot_SHR_U_1.53.0007_20120522_signedbyaa.nb0), add this to archive with android-info.txt and then use the same commands when I was flashing jbear hboot? Can I downgrade bootloader to 1.49.0007 using this method and will this hboot work well with ICS?
I accidentally hit the factory reset option while in the bootloader. After this my phone would not boot past the HTC splash screen, and I couldn't boot into the recovery (it would just boot loop). So, I decided to reflash the RUU to get out of the loop, This worked fine except for the fact that now in the boot loader the "dirty racun" banner has been replaced with the "locked" banner and I can't install a custom recovery, when I type in the fastboot command to push a recovery I get an error saying it failed. Anyone have any ideas? I was going to redo the bootloader unlock script that team fireballas wrote but I couldn't log into htcdev.com to get the unlock.bin file. I also retried the rabies shot from unlimited.io but it said the racuns had already been released. It appears that I have s-off but the bootloader is locked again.
Sent from my KFTT using xda app-developers app
You need to download the eng hboot (dirtyracun) from unlimited io website and flash it you can easily do this through the bootloader by naming the zip PJ53IMG and booting into the boot loader or you can do it through fastboot.
I'm having trouble getting the ROM to work. Can I go from a 4.3JB ROM to it? I have s-off and unlocked. Nothing loads after bootloader screen
StlGucci said:
I'm having trouble getting the ROM to work. Can I go from a 4.3JB ROM to it? I have s-off and unlocked. Nothing loads after bootloader screen
Click to expand...
Click to collapse
you s on of s off???, if s on you need to flash boot.img when changing roms
I have s-off. And have twrp as recovery.
jose51197 said:
you s on of s off???, if s on you need to flash boot.img when changing roms
Click to expand...
Click to collapse
I'm guilty of just asking "are you s-off" too, but this isn't actually sufficient. Users need to be s-off AND either unlocked or using the engineered bootloader to be able to flash boot images through recovery. Some users might be s-off but have locked bootloaders and stock hboot if they ran an RUU at some point after going s-off. To the best of my knowledge, this tree summarizes what users can do in each state:
State of Phone: flashing capabilities
S-ON and Locked: none
S-ON and Unlocked: can flash recovery and boot images through fastboot only
S-OFF, Locked, and Stock HBOOT: can flash recovery and boot images through fastboot only (need to verify if this is even possible)
S-OFF, Locked, and Unlimited.io HBOOT: can flash recovery and boot images through either fastboot or recovery
S-OFF, Unlocked, and Stock HBOOT: can flash recovery and boot images through fastboot only (need to verify if flashing boot image through recovery is possible)
S-OFF, Unlocked, and Unlimited.io HBOOT: can flash recovery and boot images through either fastboot or recovery
mdmower said:
I'm guilty of just asking "are you s-off" too, but this isn't actually sufficient. Users need to be s-off AND either unlocked or using the engineered bootloader to be able to flash boot images through recovery. Some users might be s-off but have locked bootloaders and stock hboot if they ran an RUU at some point after going s-off. To the best of my knowledge, this tree summarizes what users can do in each state:
State of Phone: flashing capabilities
S-ON and Locked: none
S-ON and Unlocked: can flash recovery and boot images through fastboot only
S-OFF, Locked, and Stock HBOOT: can flash recovery and boot images through fastboot only (need to verify if this is even possible)
S-OFF, Locked, and Unlimited.io HBOOT: can flash recovery and boot images through either fastboot or recovery
S-OFF, Unlocked, and Stock HBOOT: can flash recovery and boot images through fastboot only (need to verify if flashing boot image through recovery is possible)
S-OFF, Unlocked, and Unlimited.io HBOOT: can flash recovery and boot images through either fastboot or recovery
Click to expand...
Click to collapse
I can confirm that stock hboot and s off flashes kernels fine for me, reason for me on stock hboot, most sense 5 ports end up killing my phone to a state where recovery is unreachable, this is my procedure if you wanna check:
I leave bootloader unlocked
Fastboot OEM rebootruu
Fastboot flash zip ruu.zip
Then fastboot reboot-bootloader
And finally fastboot flash recovery twrp.IMG
Then I restore nandroid
Sent from my ADR6410LVW using xda app-developers app
I think i got it figured out. My bad lol I think I was flashing gapps with it lol I'm so used to having to flash Gapps with JB ROMs.:good:
I tried flashing a new rom and it wouldnt boot. i then had to relock bootloader to run pj53img.zip but it wont read the file, it acts like my card isnt in there. is my phone now bricked?
Thanks for any help
I believe all you have to do is go to the unlimited.io website and re-download the hboot 1.15 file and reflash it using their instructions. This will unlock your bootloader again and allow you to reinstall a custom rom. You can go here http://unlimited.io/fireball.htm to do that. If you're using a windows pc you don't have to type the sudo before each fastboot command.
I am rooted with an unlocked bootloader (went from TWRP back to Stock recovery a few weeks ago). I was reading about the RUU, but someone said you need to be S-off to do it. Is this true? And if not, how can I use the RUU then?
need to know this too mine was rooted bootloader is unlocked but for some reason its s-on
I cannot use firewater cause my phone won't boot past htc logo and when I true ancestor thru twrp it says failed .
I'm pulling my hair out some one help
I don't think you need to be S-Off. But I think you do need to re-lock the bootloader though not sure on that.
relock the bootloader and flash stock recovery, then use the RUU if you want an easy way to relock the bootloader and flash the stock recovery use HTC One 2014 (M8) All-In-One Toolkit from here http://forum.xda-developers.com/showthread.php?t=2699065 by hasoon2000
or enter recovery , fastboot, then try running the RUU
fastboot oem lock will lock bootloader again...make sure you have stock recovery, you can boot into bootloader, connect via fastboot mode and run ruu from there