Related
I recently went to change my ROM on my HTC amaze, but after I was finished installing it went to reboot and ever since no matter what I do, it just stays on the white htc screen. The only thing I can get to is into Recovery. I locked boot loader and unlocked it and after doing so I noticed it said S ON. How do I turn s off while stuck in recovery mode? Im using the ZurgRushTemp root but it says that I need my phone in usb debugging mode and I dont know how to do that in recovery mode. If I sound like a total idiot it's probably because I am. Previously I have unlocked boot loader and rooted my phone and downloaded other roms and it worked fine. I have no fricken clue what happened. Please help me.. How do I s off to install another rom while I can only get into recovery mode?
What recovery did you flash?
If its not 4EXT then you need to flash the kernel using fastboot.
Check out my hairless guinea pig
Double0EK said:
What recovery did you flash?
If its not 4EXT then you need to flash the kernel using fastboot.
Check out my hairless guinea pig
Click to expand...
Click to collapse
Im not quite sure what you mean by which recovery did I flash? Im using ClockworkMod Recovery v5.0.2.6 if that helps. What does it mean and how do I "flash the kernal using fastboot"?
ben200451 said:
Im not quite sure what you mean by which recovery did I flash? Im using ClockworkMod Recovery v5.0.2.6 if that helps. What does it mean and how do I "flash the kernal using fastboot"?
Click to expand...
Click to collapse
Alright slowly but surely I'm catching on to all this stuff.. I think. I found "Hasoon2000's HTC amaze all in one kit" on another fourm so im using that. So I want to flash a 4ext recovery? Then after that what? And do I want to flash it to stock telus kernal aswell? Goddamnit did I mess up big this time.
ben200451 said:
Alright slowly but surely I'm catching on to all this stuff.. I think. I found "Hasoon2000's HTC amaze all in one kit" on another fourm so im using that. So I want to flash a 4ext recovery? Then after that what? And do I want to flash it to stock telus kernal aswell? Goddamnit did I mess up big this time.
Click to expand...
Click to collapse
The bootloader screen reads
*** Unlocked ***
Ruby PVT SHIP S-ON RL
HBOOT-1.90.0006
eMMC-boot
just get the stock RUU for your phone. Re-lock your bootloader. Rename what you downloaded to PH85IMG.zip. place it in the root directory of your external SD card. reboot your phone into HBOOT and it should automatically flash the stock recovery and ROM. this WILL wipe your phone clean. then you can unlock the bootloader, root it, flash a custom recovery then a ROM of your choice.
NeoAndroid said:
just get the stock RUU for your phone. Re-lock your bootloader. Rename what you downloaded to PH85IMG.zip. place it in the root directory of your external SD card. reboot your phone into HBOOT and it should automatically flash the stock recovery and ROM. this WILL wipe your phone clean. then you can unlock the bootloader, root it, flash a custom recovery then a ROM of your choice.
Click to expand...
Click to collapse
What is PH85IMG.zip and where can I download it?
ben200451 said:
What is PH85IMG.zip and where can I download it?
Click to expand...
Click to collapse
Really?
If u don't know that, you've got some reading to do. Google it
_________________________
Am I on Candid Camera?
aha sorry I did, thanks for all the help. Well see if this works,
ben200451 said:
I recently went to change my ROM on my HTC amaze, but after I was finished installing it went to reboot and ever since no matter what I do, it just stays on the white htc screen. The only thing I can get to is into Recovery. I locked boot loader and unlocked it and after doing so I noticed it said S ON. How do I turn s off while stuck in recovery mode? Im using the ZurgRushTemp root but it says that I need my phone in usb debugging mode and I dont know how to do that in recovery mode. If I sound like a total idiot it's probably because I am. Previously I have unlocked boot loader and rooted my phone and downloaded other roms and it worked fine. I have no fricken clue what happened. Please help me.. How do I s off to install another rom while I can only get into recovery mode?
Click to expand...
Click to collapse
Unlocking the bootloader won't change your phone into s-off. So, what you see is correct.
Forget about ZergRush. It won't work, or necessary at all if you unlocked your bootloader, anyway.
Edit: I forgot to mention. Try 'adb logcat' to see if your phone even gets to the boot sequence. If you see your screen gets filled up with tons of stuff, hit control-c to stop it. Then enter adb logcat > logfile.txt to capture it. You can post it here for someone to take a look.
If you can get into bootloader and/or recovery, your phone isn't in a bad shape at all. If you can access your phone from a pc with adb or fastboot (which, you should have if you've unlocked your bootloader), there are things you can try.
1. boot your phone into recovery and see if you can access it through adb shell. Do you see a shell prompt ('$' or '#' sign)? On the phone, use the mount option to mount system and data partitions to see if they are mountable. You can use 'ls -l' on the shell prompt to look around, if you like.
2. If your phone is accessible, but not bootable, the first thing I would try is to flash a boot image. You probably have one sitting in the pc folder you used to unlock, or hanson's all-in-one tool has it.
3. If you flash a fresh boot image (kernel) and the phone still won't boot up, the next thing I would try is to restore from a nandroid backup. I'm sure you've made a backup before you started, right?
4. If the nandroid restore doesn't work, you can try flashing a stock rom like someone elese suggested. You just copy the zip file, which you download from the stock rom thread in the dev section, to the external sd card, rename it to PH85IMG.zip, and reboot your phone into the bootloader. The phone will detect the stock rom if it's there and asks you whether to install the update or not. Remember to download the correct file for your carrier.
5. If nothing works, come back here and post your result. I'm afraid your phone may have a corrupt nand memory...
I am having the problem I followed steps 1-5 of the post above.
using PH85IMG.zip in bootloader. It loades the image and checks. afterwards when it restarts it gets stuck on bootloader or HTC splash screen.
I am unlocked through HTC Dev
S-ON
rooted
on ext4 recovery
Sheng1988 said:
I am having the problem I followed steps 1-5 of the post above.
using PH85IMG.zip in bootloader. It loades the image and checks. afterwards when it restarts it gets stuck on bootloader or HTC splash screen.
I am unlocked through HTC Dev
S-ON
rooted
on ext4 recovery
Click to expand...
Click to collapse
What carrier are you on?
mobilicity phone but using on rogers.
also not sure if it matters
h.boot 1.93
Sheng1988 said:
mobilicity phone but using on rogers.
also not sure if it matters
h.boot 1.93
Click to expand...
Click to collapse
Were you on GB or ICS before this started happening? Or a custom ROM? Give me as much info as possible in one brief post.
original rom nandroid backup to sd card before flash
s-off through Juopunutbear
unlocked boot loader
ext4 recovery and rooted
flashed energy rom, wouldn't boot
tried to go back to stock but then internal sd card stopped working could not access anything except ext4 and fastboot
used PH85IMG.zip through bootloader still wouldn't boot
formatted internal sd card through ext4 (format everything including sd card)
re ran PH85IMG.zip in bootloader, everything checked out but could not pass htc screen
tried to relock bootloader got hard brick used unbricking project
S-ON
re-ran PH85IMG.zip still wouldn't boot past htc
unlocked bootloader through htc dev
ext4 recovery with all in one tool
rooted with tool
re-ran PH85IMG.zip and still won't get through htc screen
tried to flash kernel with all in one tool with boot img received from
OTA_RUBY_ICS_35_S_DAVE_CA_2.14.1800.6-1.45.1800.2_R_release_263099viknauioz1fkgotb
still stopped at htc screen
any help and all help is appreciated!
Sheng1988 said:
original rom nandroid backup to sd card before flash
s-off through Juopunutbear
unlocked boot loader
ext4 recovery and rooted
flashed energy rom, wouldn't boot
tried to go back to stock but then internal sd card stopped working could not access anything except ext4 and fastboot
used PH85IMG.zip through bootloader still wouldn't boot
formatted internal sd card through ext4 (format everything including sd card)
re ran PH85IMG.zip in bootloader, everything checked out but could not pass htc screen
tried to relock bootloader got hard brick used unbricking project
S-ON
re-ran PH85IMG.zip still wouldn't boot past htc
unlocked bootloader through htc dev
ext4 recovery with all in one tool
rooted with tool
re-ran PH85IMG.zip and still won't get through htc screen
tried to flash kernel with all in one tool with boot img received from
OTA_RUBY_ICS_35_S_DAVE_CA_2.14.1800.6-1.45.1800.2_R_release_263099viknauioz1fkgotb
still stopped at htc screen
any help and all help is appreciated!
Click to expand...
Click to collapse
You used the wrong image, went about using that ota file incorrectly as well, Oh boy, ite, let's keep our fingers crossed on this.
You said your hboot was 1.93.0002? Correct? If you're s-on, this may or may not work, lets hope it does, since's it practically your only hope, though I wonder what your cid currently is set to.
Since you did s-off, you should know how to use adb. Shut the phone off via battery pull, boot up into hboot then go into fastboot, using adb check your cid via this command: fastboot getvar cid
Let me know what it is when you're done, we'll work from there, hopefully we can get this done.
sorry, forgot to pull sd card so it ran the PH85IMG twice,
the cid is
11111111
Sheng1988 said:
sorry, forgot to pull sd card so it ran the PH85IMG twice,
the cid is
11111111
Click to expand...
Click to collapse
Cid is 11111111 and you're s-on? Lucky you, well download the mobilicity GB stock ruu exe file, reboot into fastboot and run the file to restore your phone to complete stock GB, hopefully it goes through, though I don't see why it wouldn't, if you're s-on, you'll have to relock your bootloader before doing this.
Thanks! hopefully it'll work
downloading the GB rom from
http://forum.xda-developers.com/showthread.php?p=27704071
going to relock bootloader with the amaze tool.
going to change the RUU to PH85IMG then pray it works!
I'll post an update in this thread, unfortunately the rom takes about 4 hours to download from file factory
Sheng1988 said:
Thanks! hopefully it'll work
downloading the GB rom from
http://forum.xda-developers.com/showthread.php?p=27704071
going to relock bootloader with the amaze tool.
going to change the RUU to PH85IMG then pray it works!
I'll post an update in this thread, unfortunately the rom takes about 4 hours to download from file factory
Click to expand...
Click to collapse
You can download the ruu from the ruu/ota thread in the same forum, the dev host upload by krook is much faster.
Do not change the name of that file, it's an exe file, you have to run it via a pc with your phone connected via usb cable in fastboot mode.
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
silenthatred said:
I was given a phone to try to resurrect from the dead. It powers on directly to the bootloader screen and does no more. I really know nothing about this phone model. Before I start, I want to know if it is even possible. The screen says the following:
*** LOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.57.0000
eMMC-boot
Apr 20 2012, 17:39:22
And then there are the normal bootloader options. Can this thing be saved?
Click to expand...
Click to collapse
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
silenthatred said:
Thanks, it does show fastboot usb...find your token? Not sure what that means. I'll search around a bit when I get home. My original Evo 4G I did root, but don't remember that part.
Click to expand...
Click to collapse
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
silenthatred said:
RUU.EXE finds it and then gets to the restarting into bootloader step and the phone restarts. Then it just saying waiting for bootloader until it times out, but the bootloader is up on the phone.
Click to expand...
Click to collapse
This happens sometimes if you have a custom bootloader installed when you flash the RUU. Just cancel the Windows task and restart it and you should be fine.
ramjet73
wloftus said:
if you can get to the bootloader screen and access the fastboot selection,plug it into a computer and get it to read fastbootusb then its fixable,first find your token and unlock the bootloader, then from there install a custom recovery , next copy the stock ROM over to your sdcard and boot into recovery... select install zip from sdcard and guide yourself to where the file is located ,select it and let it install... from there it should be able to reboot and boot up into the ROM
Click to expand...
Click to collapse
Unknownforce said:
You don't need to unlock the bootloader to fix it, and you shouldn't unlock it anyways, until you have it fully booted properly.
Run the RUU EXE from a PC for the 3.28 update (or whatever the later version is) while the phone is connected via fastboot USB mode, it will re-flash the ROM and should boot properly then.
Click to expand...
Click to collapse
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
silenthatred said:
Couple things since I have looked into this a little more. Despite it saying Sprint on the front, it is a Virgin Mobile phone. It has the OTA that came down on it, so I can't flash the older RUU. It says it is an older version. So it looks like unlocking the bootloader is my only option? Question is, how do I do that from the bootloader? I was able to get the token and have the unlock_code.bin file, but the instructions to flash it seem to rely on having a working ROM to complete it, which I don't have. The phone is stuck in a bootloader loop. S-OFF, I have the answer. But it is S-ON, so not sure what to do.
Click to expand...
Click to collapse
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
ramjet73 said:
You are right that the Virgin Mobile RUU can't be flashed when S-ON and the OTA has been installed unless you can flash a zip to downgrade your main version (mainver) and you have to be unlocked and rooted to do that.
Click to expand...
Click to collapse
Why is this? Is there not a full RUU for the latest version?
ramjet73 said:
The unlock_code.bin file is flashed via fastboot USB mode so it might work, but if you've tried that and it doesn't you may be able to use unknownforce's hboot downgrade method to get straight to S-OFF. I don't know of anyone that's done it on an Evo V 4G but it might work if you use the RUU zip file for that model.
ramjet73
Click to expand...
Click to collapse
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
silenthatred said:
It flashes unlock_code.bin to the phone successfully, but the next steps say to click yes on the screen to unlock on the phone. Can't access that without a working ROM. I'll try unknownforce's method when I get home, thanks for the help!
Click to expand...
Click to collapse
Does it still say ** LOCKED ** Or does it say ** UNLOCKED ** now?
Unknownforce said:
Why is this? Is there not a full RUU for the latest version?
Click to expand...
Click to collapse
No. Virgin Mobile released an OTA update in November but there's no RUU that corresponds to it available yet. Fortunately, the bootloader version didn't change so the original RUU can be flashed with S-ON if the mainver is set low, but you need to be unlocked and rooted already to flash the zip file that does that.
You still have to brick the device for this and I haven't been able to brick it without using a full RUU flash, which he apparently can't do?
Click to expand...
Click to collapse
That would be a problem for him then. I don't know of anyway to flash the RUU with S-ON after the OTA has been installed if the bootloader is actually locked and he can't unlock it.
ramjet73
Yeah, not looking good. Thanks for the help though!
VZW is sending me a refurb to replace a dead Rezound.
I have PH98IMG_ICS_3.14.605.12-shipped-rom.zip
for the RUU, OTA-ICS-Plus-DTa2sd-v.1.2.zip for the
rom, recovery-ra-vigor-3.16-gnm.img for recovery and
ControlBear_Release_0.5_Vigor_ICS_2.14.605.5_Win
for the s-off script.
I've got a nandroid backup and complete backup of
the internal /sdcard and external microsd card
including a TiBu of everything in both flashable
and database formats with a flashable TiBu
apk. :angel:
I know I have to
unlock boot loader
flash a recovery
install root
then run the s-off script and do the wire trick when prompted,
did I miss any steps?
After that I reflash the recovery and restore
the amonra backup, recopy the backup of
internal /sdcard and hopefully be back
where I was when the nandroid &
/sdcard backup was done?
I'd like to end up with s-off, Amonra recovery and
the custom ICS ROM I was on at last nandroid.
Do I need to reflash a bootloader / radio / boot
combo or does the s-off script do that?
I'm unsure what will be the refurb sometimes
I get ones with the original gingerbread and
sometimes whatever is the latest OTA.
Do I need to flash an ICS RUU that is compatible
with the rom I'm going to use before / after s-off?
Would that replace the s-off hboot with the stock one?
I guess maybe I should do the RUU then S-off?
fuzzynco said:
VZW is sending me a refurb to replace a dead Rezound.
I have PH98IMG_ICS_3.14.605.12-shipped-rom.zip
for the RUU, OTA-ICS-Plus-DTa2sd-v.1.2.zip for the
rom, recovery-ra-vigor-3.16-gnm.img for recovery and
ControlBear_Release_0.5_Vigor_ICS_2.14.605.5_Win
for the s-off script.
I've got a nandroid backup and complete backup of
the internal /sdcard and external microsd card
including a TiBu of everything in both flashable
and database formats with a flashable TiBu
apk. :angel:
I know I have to
unlock boot loader
flash a recovery
install root
then run the s-off script and do the wire trick when prompted,
did I miss any steps?
After that I reflash the recovery and restore
the amonra backup, recopy the backup of
internal /sdcard and hopefully be back
where I was when the nandroid &
/sdcard backup was done?
I'd like to end up with s-off, Amonra recovery and
the custom ICS ROM I was on at last nandroid.
Do I need to reflash a bootloader / radio / boot
combo or does the s-off script do that?
I'm unsure what will be the refurb sometimes
I get ones with the original gingerbread and
sometimes whatever is the latest OTA.
Do I need to flash an ICS RUU that is compatible
with the rom I'm going to use before / after s-off?
Would that replace the s-off hboot with the stock one?
I guess maybe I should do the RUU then S-off?
Click to expand...
Click to collapse
uhhhh, there are alot of questions. so im just going to reply with my thoughts than reply if you need more answers
You should Flash the latest RUU. if it already comes with it than just keep that one
install Amon Ra Recovery
do S-OFF, S-OFF will not touch your radio or boot but it may flash an hboot of 2.25 but if you want you can re flash your RUU after and wont lose or effect S-OFF
also when restoring your nandroid you only nee to restore the data folder to get everything back. so flash the rom zip in recovery than restore the data folder only and reboot. and things like music and pictures should be copied back to your sdcards
and as for ics RUU and rom compatibility, any ics RUU will work with your ics ROM. but always use the latest
BTW weird choice of rom, there are alot of new roms out that are awesome
PLEASE be sure that when you do Juopunut's S-OFF method you DO NOT USE the same SDCard where your Nandroid is, or you will most assuredly lose everything on that card. Use a different microsd card, or at least copy everything on your card to PC for safekeeping, then you can copy it back.
I'm not sure the Nandroid from the old phone will take on the new one because of the new device ID, but others may be able to help you get around that.
I just did this (for the 3rd time) but first I waited for the OTA firmware/radio update. Then, as you state, the method is: (1) htc.dev unlock bootloader; (2) flash Amon Ra recovery; (3) Root the device in recovery; (4) Nandroid backup (just in case): (5) insert different microsd card and run Juopunot S-OFF; (6) replace temp sdcard with your regular sdcard in the handset; (7) restore Nandroid (or old nandroid, if you can).
hgoldner said:
...
I'm not sure the Nandroid from the old phone will take on the new one because of the new device ID, but others may be able to help you get around that.
...
Click to expand...
Click to collapse
Yeah, in regards to the phone ID and nandroid, what you need to do is make a new nandroid on the new phone and it will make a folder with that phone's ID. Then copy your old nandroid into that folder so it will then see it and you can restore that old one from there.
hboot's and ROMs and fastboot Oh My
hgoldner said:
PLEASE be sure that when you do Juopunut's S-OFF
method you DO NOT USE the same SDCard where your Nandroid is, or you will
most assuredly lose everything on that card. Use a different microsd card, or at
least copy everything on your card to PC for safekeeping, then you can copy it
back.
.
Click to expand...
Click to collapse
The latest one, 0.5 I think, does attempt to preserve the sdcard's content,
but I always an empty 4gb just for that.
You were saying the latest stock hboot will still allow fastboot commands,
with s-off already done? I thought I need the patched JB (s-off) one for
ICS to have that work?
May I should look into a current ROM with the updated radios then?
fuzzynco said:
The latest one, 0.5 I think, does attempt to preserve the sdcard's content,
but I always an empty 4gb just for that.
You were saying the latest stock hboot will still allow fastboot commands,
with s-off already done? I thought I need the patched JB (s-off) one for
ICS to have that work?
May I should look into a current ROM with the updated radios then?
Click to expand...
Click to collapse
Nope. I flashed my own splash screen via fastboot usb right after getting S-OFF via Juopunut's ControlBear.
Dumped down the innertubes from my Transformer TF300T.
Wouldn't you be on Juopunut's hboot at that point?
I was asking if I used a later RUU, (overwriting the special
hboot with the newer stock one), would the unlocked fastboot
commands still work, even though its locked / s-off?
fuzzynco said:
Wouldn't you be on Juopunut's hboot at that point?
I was asking if I used a later RUU, (overwriting the special
hboot with the newer stock one), would the unlocked fastboot
commands still work, even though its locked / s-off?
Click to expand...
Click to collapse
Should. I just checked again and post ControlBear S-OFF I still have hboot v. 2.28 which is the new OTA firmware version.
Remember, you can obviously do fastboot usb on stock hboot, because that's how you unlock the bootloader.
My name's Harold and I'm a flashaholic.....
So are you saying all the patched & ENG hboots do differently
is cosmetics? (saying locked / no tampered warning (with a
possible custom title line) vs tampered and unlocked)?
fuzzynco said:
So are you saying all the patched & ENG hboots do differently
is cosmetics? (saying locked / no tampered warning (with a
possible custom title line) vs tampered and unlocked)?
Click to expand...
Click to collapse
Not sure. I know that my old Rezound had Juopunut's last hboot and said "locked" even though it was S-OFF and my current Rezound says "TAMPERED UNLOCKED" on stock hboot. It doesn't really matter. Both support fastboot usb, and I don't use it that much anyway. Only issue may be a mainver mismatch now, but as I intend to stay mostly stock, that doesn't matter to me.
Dumped down the innertubes from my Asus Transformer TF300T
fuzzynco said:
So are you saying all the patched & ENG hboots do differently
is cosmetics? (saying locked / no tampered warning (with a
possible custom title line) vs tampered and unlocked)?
Click to expand...
Click to collapse
hgoldner said:
Not sure. I know that my old Rezound had Juopunut's last hboot and said "locked" even though it was S-OFF and my current Rezound says "TAMPERED UNLOCKED" on stock hboot. It doesn't really matter. Both support fastboot usb, and I don't use it that much anyway. Only issue may be a mainver mismatch now, but as I intend to stay mostly stock, that doesn't matter to me.
Dumped down the innertubes from my Asus Transformer TF300T
Click to expand...
Click to collapse
My understanding is this:
When you s-off your phone will say locked.
Juopunut's hboot - no fastboot function
Eng hboot - fastboot function, which is why people flash this
Stock hboot - fastboot function (of course)
Tampered just means you have a custom recovery on it, but when you s-off the process replaces it, I don't know what it says instead, maybe Juopunut.
Tampered and unlocked is usually a phone that is s-on with a custom recovery (like mine), although some people who s-offed also unlocked again for some reason so theirs say unlocked. However, you don't have to unlock after you s-off.
feralicious said:
My understanding is this:
When you s-off your phone will say locked.
Juopunut's hboot - no fastboot function
Eng hboot - fastboot function, which is why people flash this
Stock hboot - fastboot function (of course)
Tampered just means you have a custom recovery on it, but when you s-off the process replaces it, I don't know what it says instead, maybe Juopunut.
Tampered and unlocked is usually a phone that is s-on with a custom recovery (like mine), although some people who s-offed also unlocked again for some reason so theirs say unlocked. However, you don't have to unlock after you s-off.
Click to expand...
Click to collapse
I think the last version of Juopunut restores both whatever recovery you had before you get S-OFF and possibly also your hboot. I definitely did *not* have "tampered* on my first two Rezounds after getting S-OFF, but they were on earlier hboot/RUU versions. This is the first time I ran it on a post "official" global OTA (with the 2.28 hboot), and now it says TAMPERED. I could probably flash an earlier hboot, but since I still have fastboot usb access (and used it to flash my own splash screen) it isn't necessary.
Can I use Juopunut's hboot (25) with the current firmware and
a rom expecting the current firmware, and AmonRa recovery?
I also use a custom splash (actually Juopunut's).
I like to clean look of locked and untampered
It does support most of fastboot command set,
I don't need the ENG specific subset anyway.
So, I have a dilemma. I am currently S-ON running TACHYON 1.2 (Android 4.3)
HBOOT 2.28.0000
Radio 2.23.10.0123/4
I updated the hboot and radio while S-ON. Now, I've decided I'd like to go S-OFF. According to JuopunutBear I need to be on a stock RUU for their S-OFF to work. I tried running the newest ICS RUU a few weeks ago and found that it would just error out when it was checking the file because the radios and hboot on the phone were newer than the ones on the RUU. Can I step backwards in HBOOT versions whlie S-ON or have I kind of screwed myself? Or is there a better option I haven't thought about?
Thanks
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Uzephi said:
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
It's a stock hboot, yes. But the RUU won't run because it is an older version hboot.
You need s-off to downgrade. Just install a stock based Rom that is rooted and run s-off procedure. You will have no issues. After s-off if you want, you can ruu
Sent from my DNA using my mind.
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
jeff925 said:
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
Click to expand...
Click to collapse
A stock rooted RUU would work. I was in your predicament once. First, do a nandroid backup then use this guide it'll get you to s-off. If you want to downgrade, then use this guide to accomplish this.
Thanks guys for the help. Installed the rom listed in the guide and it worked great. S-OFF now!! (Took me long enough...I've had the phone for 2 years!)
It installed JuopunutBear's hboot but whatever. I'd probably rather stick with a stock hboot but I can do that later.
Restored my nandroid backup and I'm back up and running like I never left.
Just flash this ROM and boot image, and you should be able to S-OFF, I can't remember if stock recovery is needed but that can be flashed separately as well if needed, but I don't think it is.
http://forum.xda-developers.com/showthread.php?t=2260154
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
jeff925 said:
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
Click to expand...
Click to collapse
In fastboot does it say s-off? Try manually flashing the boot.img by extracting it. If you haven't setup enviroment variable for fastboot put the boot.img in the same directory as fastboot.exe and use command prompt by typing
Code:
cd C:\Android\platform-tools (or wherever it is for you)
Then type
Code:
fastboot flash boot boot.img
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
You can unlock when S-OFF, but there is no reason to, you can get a PH98img.zip of CWM here: http://forum.xda-developers.com/showthread.php?t=1914215 or TWRP here: http://forum.xda-developers.com/showthread.php?t=1902381 and just copy it to your sd card (remember to name it exactly PH98IMG.zip, beware the Windoze "double zip" issue) then pop it in the phone, boot into Hboot with the USB disconnected and it should recognize it and flash either CWM or TWRP. from there you can flash ANYTHING you want, being S-OFF with custom recovery allows you to flash anything, no fastboot commands required.
Also, since you are S-OFF, your Hboot is mostly irrelevant, but should be the matching version to your radios... an engineered hboot (like Juopunutbears) would allow fastboot commands well locked, but fastboot isn't generally needed once S-OFF has been obtained...
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
4218kris said:
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
Click to expand...
Click to collapse
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
and what recovery problems are you having....flashing an hboot will not give you a recovery...and an ruu is an exe file not a ph98img file...those are OTA's.....if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
REV3NT3CH said:
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
Click to expand...
Click to collapse
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
that one or the this 2nd ph98img in my downgrade/upgrade guide work as well...that one is just radios and hboot....doesnt come with stock <3e> recovery
REV3NT3CH said:
if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
Click to expand...
Click to collapse
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
jrredho said:
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
Click to expand...
Click to collapse
when you boot into your bootloader...does your hboot now say S-OFF....if so i can give you everything you need and what id suggest doing just prior to doing it
REV3NT3CH said:
when you boot into your bootloader...does your hboot now say S-OFF..
Click to expand...
Click to collapse
Yes it does.
REV3NT3CH said:
.if so i can give you everything you need and what id suggest doing just prior to doing it
Click to expand...
Click to collapse
That would be fantastic!
Thanks,
John
I have a HTC desire 601 bought this Summer from Virgin Mobile USA, a CDMA based carrier using Sprint network. My son played with it yesterday and now it is bricked. A "HTC" log is shown up and frozen in the display, not able to shutdown the phone by pressing anything.
I asked my son what he did, but he didnt say anything as he is afraid of punishment
what I can do is try to remove the battery, then hold the volume down key and power key, then it brings up this screen:
***Tampered***
***Unlocked***
ZARA_C PVT SHIP S-ON RL
HBOOT-2.20.0000
RADIO-1.14.50.1003
OpenDSP-v16.2.0268.noBeats.0902
OS-1.10.652.9
eMMC-boot 1024MB
Oct 7 2013 18:39.56.0
HBOOT
<vol_up>to previewitem
<vol_down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
CLEAR storage
SIMLOCK
Image CRC
Show barcode
after I press "recovery", it enter this page::
Team Win Recovery project v2.7.1.1(kk)
Install Wipe
Backup Restore
Mount Settings
Advanced Reboot
what I want to to go back to the stock Virgin Mobile ROM. what should I do? thanks.
I'm assuming you don't have a backup... Try a factory reset from twrp, if that didn't help seek out a zara_cl backup
attrunner said:
I have a HTC desire 601 bought this Summer from Virgin Mobile USA, a CDMA based carrier using Sprint network. My son played with it yesterday and now it is bricked. A "HTC" log is shown up and frozen in the display, not able to shutdown the phone by pressing anything.
I asked my son what he did, but he didnt say anything as he is afraid of punishment
what I can do is try to remove the battery, then hold the volume down key and power key, then it brings up this screen:
***Tampered***
***Unlocked***
ZARA_C PVT SHIP S-ON RL
HBOOT-2.20.0000
RADIO-1.14.50.1003
OpenDSP-v16.2.0268.noBeats.0902
OS-1.10.652.9
eMMC-boot 1024MB
Oct 7 2013 18:39.56.0
HBOOT
<vol_up>to previewitem
<vol_down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
CLEAR storage
SIMLOCK
Image CRC
Show barcode
after I press "recovery", it enter this page::
Team Win Recovery project v2.7.1.1(kk)
Install Wipe
Backup Restore
Mount Settings
Advanced Reboot
what I want to to go back to the stock Virgin Mobile ROM. what should I do? thanks.
Click to expand...
Click to collapse
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive.
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
-Duir- said:
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive[/URL].
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
Click to expand...
Click to collapse
sir, can you show me where did you see it's Kitkat recovery on my device, and where did you see it's still Jelly bean? I am still leaning.
attrunner said:
sir, can you show me where did you see it's Kitkat recovery on my device, and where did you see it's still Jelly bean? I am still leaning.
Click to expand...
Click to collapse
Team Win Recovery project v2.7.1.1(kk)
^^where it says "kk" at the end means that is a kitkat recovery.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
Team Win Recovery project v2.7.1.1(kk)
^^where it says "kk" at the end means that is a kitkat recovery.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
where it shows it's jelly bean? thank you very much.
attrunner said:
where it shows it's jelly bean? thank you very much.
Click to expand...
Click to collapse
The OS version in your post is Jelly Bean.
-Duir- said:
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive.
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
Click to expand...
Click to collapse
sir, This is what I did:
1 I tried to use the RUU (file name RUU_ZARA_CL_JB422_SENSE50_Sprint_WWE_VM_1.10.652.9_Radio_1.14.50.1003_NV_SPCS_5.17_003_PRL55009_release_337148_signed_2.exe), but after the RUU erase data, and trying to send data, it has error message:
ERROR[155]: unknown error.
The ROM Update Utility can not update your Android phone.
Please get the correct ROM update utility and try again.
2 I tried different TWRP version as recovery, then use your RUU, all failed as step 1.
openrecovery-twrp-2.6.3.0-zaracl
openrecovery-twrp-2.7.0.0-zaracl
openrecovery-twrp-2.7.1.0-zaracl
3. I tried a stock ROM in Google dirve:
/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
I chose file JB_stock_system_dump.zip, tried to copy to external SD card and install from recovery, but failed.
So please help what should I try next. thank you very much
attrunner said:
sir, This is what I did:
1 I tried to use the RUU (file name RUU_ZARA_CL_JB422_SENSE50_Sprint_WWE_VM_1.10.652.9_Radio_1.14.50.1003_NV_SPCS_5.17_003_PRL55009_release_337148_signed_2.exe), but after the RUU erase data, and trying to send data, it has error message:
ERROR[155]: unknown error.
The ROM Update Utility can not update your Android phone.
Please get the correct ROM update utility and try again.
2 I tried different TWRP version as recovery, then use your RUU, all failed as step 1.
openrecovery-twrp-2.6.3.0-zaracl
openrecovery-twrp-2.7.0.0-zaracl
openrecovery-twrp-2.7.1.0-zaracl
3. I tried a stock ROM in Google dirve:
/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
I chose file JB_stock_system_dump.zip, tried to copy to external SD card and install from recovery, but failed.
So please help what should I try next. thank you very much
Click to expand...
Click to collapse
Lock the bootloader and then run it.
Also:
Custom recovery does not affect the RUU.
The system dump zip is literally that, a dump of the system partition. As such, it's not recovery flashable.
-Duir- said:
Lock the bootloader and then run it.
Also:
Custom recovery does not affect the RUU.
The system dump zip is literally that, a dump of the system partition. As such, it's not recovery flashable.
Click to expand...
Click to collapse
Don't lock the boot loader, that's not why the ruu is failing.
You need to change the mid first
mrplowdan said:
Don't lock the boot loader, that's not why the ruu is failing.
You need to change the mid first
Click to expand...
Click to collapse
That's exactly why it's failing. You need to be relocked to run the RUU.
-Duir- said:
That's exactly why it's failing. You need to be relocked to run the RUU.
Click to expand...
Click to collapse
Perhaps its different for the cl varient but for my ul, I'm 100% positive you don't need to be relocked. However, mid and cid must match the ruu.
*edit*
Also your hboot must be older or the same version as the ruu's hboot
mrplowdan said:
Perhaps its different for the cl varient but for my ul, I'm 100% positive you don't need to be relocked. However, mid and cid must match the ruu.
*edit*
Also your hboot must be older or the same version as the ruu's hboot
Click to expand...
Click to collapse
Well, they have the Virgin Mobile zara_cl variant which the RUU is made for, so the mid and cid shouldn't be an issue since they're S-ON and can't change it. Also, as stated their using 4.2.2. They still have the old firmware and partition layout which is why the version of twrp they installed won't work so hboot version is also not an issue. Also, it throws a different error if your device has a newer hboot than the RUU.
While it's not entirely outside the realm of possibility that something else could be causing the error, it's definitely not hboot version or mid/cid.
Were you S-OFF when you ran RUU on unlocked bootloader? I'm not sure of all the benefits of being S-OFF, but maybe one is being able to RUU with an unlocked bootloader. It makes perfect sense for an unlocked bootloader to throw an error since it can void your warranty and RUUs are generally ran by service techs.
But in all my experience the bootloader needs to be locked/relocked for the RUU to run.
-Duir- said:
... Were you S-OFF when you ran RUU on unlocked bootloader? I'm not sure of all the benefits of being S-OFF, but maybe one is being able to RUU with an unlocked bootloader. It makes perfect sense for an unlocked bootloader to throw an error since it can void your warranty and RUUs are generally ran by service techs.
But in all my experience the bootloader needs to be locked/relocked for the RUU to run.
Click to expand...
Click to collapse
I haven't tried running the ruu while s-on. I'm pretty sure the distinction is if your s-off you can flash ruu zips (which don't have the mid/cid requirements) after running fastboot oem rebootRUU as well as the standard exe RUUs, and if your s-on you can only run exe RUUs.
Hey, guys. I've finally made an account here after clumsily stepping into the world of custom ROMs. I recently got a Zara_CL on Virgin mobile and somehow wound up in the same position as the OP here. I never updated to KitKat due to the update failing with a custom recovery image. After unlocking the bootloader, I installed TWRP 2.7.1.1 and tried to flash InstertCoin yesterday without making a backup (couldn't mount certain partitions and now I know why ^_^). It took many hours to figure out what I did wrong and to make many plans of action to fix those mistakes.
I have re-locked my bootloader and the RUU has allowed me to get the stock Jellybean ROM back on my phone. I tried before while still unlocked and the RUU made no progress at all.
From what I've experienced, S-OFF and Unlocked are sort of interchangeable on a device in this stage of being cracked. One can flash recoveries with S-OFF and a locked loader, or with S-ON and an unlocked loader. I'm still learning after a few months and a successful root, s-off, and rom flash on an ancient EVO 3D. The high of that success drove me to buy this phone and try some magic on it, but my conjuration skills are quite unpolished.
To OP: Relock your bootloader with fastboot command "oem lock" and then run the RUU you found here. This should resurrect your handset flawlessly as it did in my situation. Don't punish your son, but teach him to be more careful. We both learned the hard way, but I guess I learned more quickly.
I had to always lock bootloader before running ruu. Would always get same error otherwise. This was for s-on. I can't remember my one experience running ruu while s-off.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
I had to always lock bootloader before running ruu. Would always get same error otherwise. This was for s-on. I can't remember my one experience running ruu while s-off.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
How to lock bootloader? I only know how to unlock.
Get into boot loader and type "oem lock" into adb/command prompt.
attrunner said:
How to lock bootloader? I only know how to unlock.
Click to expand...
Click to collapse
You're phone needs to be in fastboot mode.
You need adb on your computer and to run a command prompt from your adb folder. Plug your phone into the computer and from the command prompt type "fastboot oem lock" and press enter. You're bootloader will now be locked. If you get a message about too many flags or something and a security warning afterwards, don't worry, it worked.