I have a Rezound on RezRom (latest). The phone is s-off... I can't believe I got through that with my old eyes and limited tech ability...
I got a new phone, and want to give the Rezound to my daughter. What would be the right thing to flash to make her stock, and able to receive updates? I don't care if the phone stays s-off or goes back to s-on-- she'll never use that feature anyhow.
I'm guessing I can just run this: RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed.exe and all will be back to stock, the updates will work, the phone will be erased and probably s-on again.
If someone can point me in the right direction, I'd appreciate it. (So would she... she's still rocking an OG droid!)
Thanks much in advance for any help!
Cheers,
SteveRN
S-OFF will remain after RUU but there's a thread about returning to S-ON but make sure it's after the RUU or you'll brick your phone beyond repair.
Sent from my ADR6425LVW
Running that ruu will get you completely back to stock with the exception of s-off. If you want to set it back to s-on there's simply a fast boot command you need to run. There are a few threads around here that talk about it if that's the way you want to go.
Sent from my ADR6425LVW using XDA
Here's the thread for s-on btw.
http://forum.xda-developers.com/showthread.php?t=1612937
Sent from my ADR6425LVW using XDA
Many thanks to you all. (of course I hit the button) ;-)
I'll run the RUU and leave it S-off. As long as it's on the upgrade path I'm a happy camper... and If I ever need to flash something for her, I can.
If it breaks or anything I'll be able to s-on it I suppose, she would only send it in through me anyway... (yeesh... kids )
Still stuck trying to flash stock back to my S-Off rezound...
Uh oh. Still stuck. I run the RUU i listed above and it errors out.
I boot the phone into the latest RezRom (ics) and run the RUU; the RUU gets to the part where it says "ok, say ok to flash this" and then it comes up "unknown error".
Am I supposed to start this up while the phone is in recovery? or is there a zip I can flash like a ph98img.zip that would take me to stock, even if it's s-off stock?
Argh.
RezRom still boots up fine. I can reboot into TWRP as well.
Help! (I need a clue....)
try preforming a factory reset in bootloader then try the ruu again
steven.rn said:
I have a Rezound on RezRom (latest). The phone is s-off... I can't believe I got through that with my old eyes and limited tech ability...
I got a new phone, and want to give the Rezound to my daughter. What would be the right thing to flash to make her stock, and able to receive updates? I don't care if the phone stays s-off or goes back to s-on-- she'll never use that feature anyhow.
I'm guessing I can just run this: RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed.exe and all will be back to stock, the updates will work, the phone will be erased and probably s-on again.
If someone can point me in the right direction, I'd appreciate it. (So would she... she's still rocking an OG droid!)
Thanks much in advance for any help!
Cheers,
SteveRN
Click to expand...
Click to collapse
Ignore this post.......
Sent from my MB870 using Xparent Cyan Tapatalk 2
dogredwing1 said:
try preforming a factory reset in bootloader then try the ruu again
Click to expand...
Click to collapse
Thanks bud... that didn't work either.
When I run adb devices, I see the rezound listed... I'm still thinking there is a zip i could flash from twrp, but I don't know where to find a stock zip that I could rename to ph98img.zip for that.
I am a bit mystified why the RUU won't run.
the hboot is 2.25, could that be it?
steven.rn said:
Thanks bud... that didn't work either.
When I run adb devices, I see the rezound listed... I'm still thinking there is a zip i could flash from twrp, but I don't know where to find a stock zip that I could rename to ph98img.zip for that.
I am a bit mystified why the RUU won't run.
the hboot is 2.25, could that be it?
Click to expand...
Click to collapse
Does it say unlocked at the top by any chance? In hboot that is?
If so you run, "fastboot OEM lock" while in fastboot. Then run the ruu.
Sent from my ADR6425LVW using XDA
nosympathy said:
Does it say unlocked at the top by any chance? In hboot that is?
If so you run, "fastboot OEM lock" while in fastboot. Then run the ruu.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
It says "locked" but I do remember unlocking it before s-off. I'll chase that down a bit, I think you have something here. I'll let you know in a bit
nosympathy said:
Does it say unlocked at the top by any chance? In hboot that is?
If so you run, "fastboot OEM lock" while in fastboot. Then run the ruu.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
What ended up working was booting the phone into fastboot and then running the RUU. I didn't know you had to do that.... I don't know if I was just clueless on this one or if things are different with an S-Off phone.
Thanks, Dr. No
steven.rn said:
What ended up working was booting the phone into fastboot and then running the RUU. I didn't know you had to do that.... I don't know if I was just clueless on this one or if things are different with an S-Off phone.
Thanks, Dr. No
Click to expand...
Click to collapse
glad it worked out, second recommendation was going to be pulling the rom.zip file from the ruu.exe and running that through hboot itself.
Related
Before I begin, I've read through a lot of threads on different forums and have yet to find a solution (that's working for me.)
I could never get my device to S-OFF so simply dropped the task. Not in too big of a rush right now. That being said, I'd like to go back to GB for a bit just to try a few things out.
I never flashed the ICS firmware, therefor I've had to use the old firmware patches. So, I tried running the RUU for GB and it only encountered error after error and my phone stayed at the black HTC screen. Any ideas?
Phone works just fine, just rebooted while I was typing this post and went straight into my ROM.
Only way I found is S-off'd, I had to go back to GB after ICS since it came on the phone I bought and needed to return it. Everyone told me I had to S-Off then RUU
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Downgrading radios when s-on could very well hard brick your phone. I strongly recommend that you s-off first.
Sent from my ADR6425LVW using Tapatalk 2
Abu-7abash said:
Downgrading radios when s-on could very well hard brick your phone. I strongly recommend that you s-off first.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You can't downgrade with s on....
Sent from my Rezound
ericsignals said:
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Click to expand...
Click to collapse
ericsignals said:
You can't downgrade with s on....
Sent from my Rezound
Click to expand...
Click to collapse
Are you even the same guy?
Sent from my ADR6425LVW using Tapatalk 2
Pick a Gingerbread based rom and flash. Try out Chingy's Ineffabilis gingerbread.
Chyrux said:
I never flashed the ICS firmware, therefor I've had to use the old firmware patches.
Click to expand...
Click to collapse
Wish you guys would read.
Abu-7abash said:
Are you even the same guy?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
If you never ran an ics ruu you still were on gb firmware....so you can run a gb ruu. When you run the same ruu that's not downgrading....sheesh :rolleyes . And its probably the easiest way to get back to a working phone if you are lost and don't really know what you are doing.
Sent from my Rezound
ericsignals said:
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Click to expand...
Click to collapse
Tried that. RUU said "Could not update your phone at this time."
I came from stock GB originally in...April. Is there a specific RUU for that?
I've never used RUU's before so I'm lost.
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Chyrux said:
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Click to expand...
Click to collapse
Still only a soft brick. Would suggest trying the other of the two GB RUU .exe version packages if you only tried one of them, just a suggestion until someone else can help you and diagnose.
http://forum.xda-developers.com/showthread.php?p=19756694
Chyrux said:
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Click to expand...
Click to collapse
If you can get to hboot It's not bricked. Which ruu were you trying
pwned3 said:
If you can get to hboot It's not bricked. Which ruu were you trying
Click to expand...
Click to collapse
RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed
Try running that one again. It should work. You have to run it twice anyway
pwned3 said:
Try running that one again. It should work. You have to run it twice anyway
Click to expand...
Click to collapse
Tried. It's stuck on the "Verifying the information on your PDA Phone...Please wait..." screen.
EDIT: Nevermind, went into Fastboot, working now. Let you know how it goes. Thanks for the help so far.
I'm getting a bootloader version error. An ICS RUU should fix this, right? Granted, I know that means I can't go back until I S-Off, but I'd rather that than have a soft bricked phone
I am in the same boat - S-ON. I flashed Scott's ICS Rooted Stock Rom, along with the GB Patch. I downloaded the PH98IMG.zip and HBOOT doesn't recognize it. Trying the exe may resolve this?
Issue resolved thanks to dsb in the IRC channel. For some reason, I thought I had to throw the unlock.bin on my SD card to unlock.
And to the guy above me, try pushing it through adb. Extract the ROM, find the boot.img, throw it into your ADB directory.
adb reboot bootloader
(make sure you're in fastboot USB)
fastboot flash boot boot.img
Chyrux said:
Issue resolved thanks to dsb in the IRC channel. For some reason, I thought I had to throw the unlock.bin on my SD card to unlock.
And to the guy above me, try pushing it through adb. Extract the ROM, find the boot.img, throw it into your ADB directory.
adb reboot bootloader
(make sure you're in fastboot USB)
fastboot flash boot boot.img
Click to expand...
Click to collapse
Hate to ask you this, but would you mind giving me a step by step on what you did to get back to GB?
Thanks -Kim
print.logic said:
Hate to ask you this, but would you mind giving me a step by step on what you did to get back to GB?
Thanks -Kim
Click to expand...
Click to collapse
With the new leak out, I haven't. However, I can still help.
Make sure there is no P98IMG file on your SD card.
1. Download the mainver fix from this post http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4
2. Drop GB ROM of your choice onto SD card.
3. Flash the fix in recovery and reboot into bootloader.
4. Relock your phone by going into adb and typing in fastboot oem lock
5. Run GB RUU of your choice.
6. Use the HTCDev unlock on your bootloader
7. Download a recovery and push it to your phone by typing in fastboot flash recovery recovery.img
8. Boot into recovery, flash ROM, enjoy.
so i got s off and updated ruu and flashed amonra 3.15 and now when i try to boot into recovery from fast boot it goes to a screen with a phone and a trianble with a red exclamation point in it??? please help i need my phone tomorrow for work. i knew i should have waited for the weekend...... Thanks,
Jake
What hboot are you on?
Sent from my evolving Rezound.
LunaticSerenade said:
What hboot are you on?
Sent from my evolving Rezound.
Click to expand...
Click to collapse
i flashed junoperbears.. 2.25
and now after installing busy box and super user i am getting no service.... FML!
its also saying parsing image when i boot into bootloader....
jski711 said:
its also saying parsing image when i boot into bootloader....
Click to expand...
Click to collapse
You have a PH98IMG on your SD Card. Plug it into your PC and erase it, then you'll get into recovery.
As far as service, what ROM are you on?
Sent from my evolving Rezound.
i did delete and it did the same thing. it was the stock ruu i couldn't get into recovery to flash a rom. i am going to redo the ruu update and see if that helps. any other info would be great! damnit 5:15 am is coming fast. LOL
Its only 1 where I am lol.
Which RUU are you running?
Run the exe, then I would say just S-Off. Then you can flash whatever you want.
Sent from my evolving Rezound.
LunaticSerenade said:
Its only 1 where I am lol.
Which RUU are you running?
Run the exe, then I would say just S-Off. Then you can flash whatever you want.
Sent from my evolving Rezound.
Click to expand...
Click to collapse
i am s off.. now im confused. lol RUU 3.14.605.5
just reflashed RUU and at least i get service now. im still getting the same error when trying to go from fastboot to recovery..... WTF. i guess i'll just run this stock until i figure it out. not sure what happened though..
Flash this:
http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/[ICS][2.25][JB][5-7]PH98IMG.zip
Then boot fastboot and flash Amon-Ra.
Then flash the ICS ROM of your choice.
Should be good to go.
Sent from my evolving Rezound.
do i flash in bootloader? thanks for the help!
LunaticSerenade said:
Flash this:
http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/[ICS][2.25][JB][5-7]PH98IMG.zip
Then boot fastboot and flash Amon-Ra.
Then flash the ICS ROM of your choice.
Should be good to go.
Sent from my evolving Rezound.
Click to expand...
Click to collapse
when i try to flash amonra from the all in one toolkit (ya i don't understand adb yet) it just says it failed and thats it.
jski711 said:
when i try to flash amonra from the all in one toolkit (ya i don't understand adb yet) it just says it failed and thats it.
Click to expand...
Click to collapse
Do you have adb installed? At first glance it seems rough, but its really not that bad.
Sent from my evolving Rezound.
ya i can get to the command prompts but i just don't understand what to do from there.
Gotcha.
Boot to hboot on your phone, then make sure it says 'fastboot'
Plug it into your PC, and run fastboot devices.
If it returns with a serial number, you're good to go. Let me know how that fares.
Sent from my evolving Rezound.
i think i might have got it thanks to you... i'll let you know momentarily
AND IM BACK IN THE GAME!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! LUNATIC YOU ARE AWESOME!!!!!! Thanks a lot, its hard to find people like you on these boards sometimes!!
No worries! I remember stumbling through it...it was not fun.
Of course, I was too thick headed to ask questions...
Glad it works though!
this has already been answered but it wouldn't go to your recovery because a RUU is a full stock image of the phone.
So your recovery was erased and the stock one was placed on.
That's like the definition of an RUU it makes EVERYTHING stock.
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
rezin said:
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
Click to expand...
Click to collapse
Tampered is normal. Did you try flashing it with a ph98img, or as an .exe
It happens after you unlock and install a custom recovery I believe. Are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
big_mike_2k6 said:
And are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Yeah make sure your bootloader is relocked
i was in the middle of doing s-off when the phone froze and corrupted the mem card...so i tried redoing the whole process over and i havent been able to get past the hboot...im still unlocked and have access to recovery and hboot but i cant flash a rom and boot into it...i cant run an ruu but the phone is not technically bricked...its an odd predicament...i just flashed a rom and i still cant get it to get past the hboot
Have you tried re-locking the bootloader and then run the ruu?
Sent from my ADR6425LVW using Tapatalk 2
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
rezin said:
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
Click to expand...
Click to collapse
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
synisterwolf said:
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
Click to expand...
Click to collapse
Yeah I already got it up n running...between being unlocked and having a slightly dead battery I wasn't even being given the option to run an ruu...its running now but I still need to do s-off again, and of course my sd card is corrupted so ill work on that tonight
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
willdo7474 said:
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
Click to expand...
Click to collapse
Hey, I didn't have to do this, but if you noticed, controlbear makes backup copies of stuff like boot.img (forget what else) and puts them on your computer. If you crap out you ought to be able to fastboot flash boot [bootimgfilename.img] and be able to boot up your phone. I saw where one person did this to get going again after a failed soff.
Yeah well happened in my case is that I was already s-offed and then I flashed the ruu to go back to stock...then I relocked my phone cuz I'm having an issue with one of the pins on phone (the terminal that connects to battery).so I was gonna get it exchanged, I wanted it to look absolutely stock...so the "relocked" status wasn't good enough, so someone suggested doing s-off again so it will show locked in hboot...well that's where everything went wrong, the phone froze at the wire trick and then the entire memory card was corrupted which is normal...so when I went to redo the whole s-off procedure again I kept rebooting into the blank screen with the arrow...could not get past that, so I resorted to putting my real sd card in...I had no backups for that card cuz that one has my actual personal stuff so I figures it'd be ok since I used a spare to do s-off anyway...well upon powering on the phone it was also corrupted...so Ive actually given up on s-off and getting my phone restored and replaced for a while...I don't know why s-off has always given me problems I've watched and read every vid or post about s-off and am in no way tech illiterate but I've always had problems with s-off (i lost all my pics and documents the first time I did s-off even thought I backed everything up cuz the only way to get it right was to eliminate every file in the folder and rerun it again cuz it didn't back up my sd correctly If at all)...its beyond infuriating
well that didnt last long...i just unlocked and s-offed my phone again, only to be returned to s-on and fully locked (indistinguishable from brand new in box), as i originally intended...im gonna miss this particular phone but it has to be done
i have rezound that someone gave me and its not booting up. s-on, rooted, bootloader unlocked but its stuck at the htc screen. anyone know how i can return this back to stock without s-off or how i can get s-off without being booted up. i can get into recovery and bootloader but flashing firmware or another rom didnt work.
anyone have any ideas?
i dont know whether its on gb or ics. he just gave it to me like this.
vegandroid said:
i have rezound that someone gave me and its not booting up. s-on, rooted, bootloader unlocked but its stuck at the htc screen. anyone know how i can return this back to stock without s-off or how i can get s-off without being booted up. i can get into recovery and bootloader but flashing firmware or another rom didnt work.
anyone have any ideas?
i dont know whether its on gb or ics. he just gave it to me like this.
Click to expand...
Click to collapse
Go to the bootloader screen and tell us what hboot and radio versions you have.
Hboot 2.21 is gingerbread.
2.25 is the first ICS OTA.
2.27 is the global update.
Did you run an RUU?
That should work.
Sent from my Rezound
wlmeng11 said:
Go to the bootloader screen and tell us what hboot and radio versions you have.
Hboot 2.21 is gingerbread.
2.25 is the first ICS OTA.
2.27 is the global update.
Did you run an RUU?
That should work.
Sent from my Rezound
Click to expand...
Click to collapse
hboot 2.11
it doesnt tell me which radio...
vegandroid said:
hboot 2.11
it doesnt tell me which radio...
Click to expand...
Click to collapse
Baseband is radio.
Anyway, that means you are on Gingerbread.
So you can either flash the GB RUU, or upgrade with the ICS RUU.
Sent from my Rezound
wlmeng11 said:
Baseband is radio.
Anyway, that means you are on Gingerbread.
So you can either flash the GB RUU, or upgrade with the ICS RUU.
Sent from my Rezound
Click to expand...
Click to collapse
im looking for a combo that i can flash with nils business 4.0.3.. what could i flash thatll get my booted up? thank you for your help.
vegandroid said:
im looking for a combo that i can flash with nils business 4.0.3.. what could i flash thatll get my booted up? thank you for your help.
Click to expand...
Click to collapse
Since that's an ICS rom, you should flash the 3.14.605.12 RUU.
Sent from my Rezound
wlmeng11 said:
Since that's an ICS rom, you should flash the 3.14.605.12 RUU.
Sent from my Rezound
Click to expand...
Click to collapse
i have tried finding things and have flash a few ruu's but cant find anything thatll work with s-on.. do you know a combo that would work with it?
vegandroid said:
i have tried finding things and have flash a few ruu's but cant find anything thatll work with s-on.. do you know a combo that would work with it?
Click to expand...
Click to collapse
All RUUs work s-on.
Only flashing hboot/radio individually requires s-off, and downgrading RUUs.
Sent from my Rezound
Need to lock the boot loader before running the ruu if you're s-on.
Sent from my ADR6425LVW using Tapatalk 2
This is the process I've used from what I've read here many times.
Place the PH98 file of the RUU on your ext SD card.
Relocking the bootloader always has started the flash process for me but if it doesn't.
Pull the battery.
Boot into bootloader.
Let the RUU flash.
Let the phone boot but don't set anything up.
Shut down the phone and pull the battery.
Reboot into bootloader again.
Flash the RUU a second time.
Boot the phone.
Delete the PH98 file off your ext SD card.
Power down and pull the battery.
Boot back into the bootloader and do a factory reset.
Reboot again and enjoy.
Sent from my ADR6425LVW using xda app-developers app
wlmeng11 said:
All RUUs work s-on.
Only flashing hboot/radio individually requires s-off, and downgrading RUUs.
Sent from my Rezound
Click to expand...
Click to collapse
mjones73 said:
Need to lock the boot loader before running the ruu if you're s-on.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
LOBBS said:
This is the process I've used from what I've read here many times.
Place the PH98 file of the RUU on your ext SD card.
Relocking the bootloader always has started the flash process for me but if it doesn't.
Pull the battery.
Boot into bootloader.
Let the RUU flash.
Let the phone boot but don't set anything up.
Shut down the phone and pull the battery.
Reboot into bootloader again.
Flash the RUU a second time.
Boot the phone.
Delete the PH98 file off your ext SD card.
Power down and pull the battery.
Boot back into the bootloader and do a factory reset.
Reboot again and enjoy.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
THANK YOU!!!! Thanks all around! I am proficient in adb and rooting and unlocking bootloaders but what ive come to realize about htc is the whole s-off/s-on crap. as soon as i relocked the bootlooader and flashed the ruu already on my sd card i was able to get booted back up. im running a s3 as my my driver and dont really have to deal with radios and hboot, but when i had my thunderbolt it really started to bring back memories. thanks for the help guys!
Dudes,
Too many dead pixels dying on my phone and ATT is sending me another replacement device through warranty. I RUU'd and brought everything back to normal from the CID, hboot, radio, and back to s-on but I cannot get my bootloader to show "Locked". It just shows relocked. Im certain I cannot send it back to them saying relocked. Ive searched and maybe im not searching good enough. Care to share some commands?
"fastboot oem lock" only relocks it.
I restored the phone to 3.17 firmware and RUU but before I update it to the 4.3 id like it to show locked. Any help is appreciated.
Edit: Nevermind I found my answer. Read that this was not possible.
kennypow3rs said:
Dudes,
Too many dead pixels dying on my phone and ATT is sending me another replacement device through warranty. I RUU'd and brought everything back to normal from the CID, hboot, radio, and back to s-on but I cannot get my bootloader to show "Locked". It just shows relocked. Im certain I cannot send it back to them saying relocked. Ive searched and maybe im not searching good enough. Care to share some commands?
"fastboot oem lock" only relocks it.
I restored the phone to 3.17 firmware and RUU but before I update it to the 4.3 id like it to show locked. Any help is appreciated.
Edit: Nevermind I found my answer. Read that this was not possible.
Click to expand...
Click to collapse
If you're s-off it is totally possible there's a command for it built right in to revone.
Sent from my HTC One using Tapatalk
to my knowledge any htc device no longer show "locked" after you unlocked it the first time..it will always show relocked when locked again..
Nick281051 said:
If you're s-off it is totally possible there's a command for it built right in to revone.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Too bad i found this out after i s-on'd the phone again lol. So now im in the process of unlocking with rumrunner, then re s-off, then try to "lock" it again. Thanks for the replies guys
kennypow3rs said:
Too bad i found this out after i s-on'd the phone again lol. So now im in the process of unlocking with rumrunner, then re s-off, then try to "lock" it again. Thanks for the replies guys
Click to expand...
Click to collapse
No problem lol good luck
Sent from my HTC One using Tapatalk
Nick281051 said:
No problem lol good luck
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ok now I have some problems. I unlocked again, s-off'd and then tried to "lock" and s-on again. Something went wrong and now I have a message in hboot that says "security warning" and tampared over the words "locked". I doesnt boot to the rom again just goes to recovery im guessing with the phone and the red triangle. lol Pain in the butt.
To be honest I have no clue how to fix that lol I haven't tried to lock it yet
Sent from my HTC One using Tapatalk
Nick281051 said:
To be honest I have no clue how to fix that lol I haven't tried to lock it yet
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Theres no rom on the phone now lol.Gotta figure this out! Thanks for your help dude!
Run a ruu that will fix it tampered will be gone too
Sent from my HTC One using Tapatalk
So right now it's unlocked with tampered above an s-off. Is it wise to lock bootloader first before I run ruu? Which order should I go? I know s-on is last for sure...
Sent from my HTC One using Tapatalk
For anyone that's searching for this exact issue ill share what i did to get my phone completely back to stock. I did search the forum but the info was all over the place and in my opinion it was as clear as "I" needed it to be hence me creating a thread for something so simple. Ok as follows here is what I did step by step.
First I had to make sure I installed HTC sync of course. At the moment my firmware was 3.57 and I downloaded the 3.17 RUU.exe from HTC.com
Your firmware *HBOOT* and the RUU you download have to match or you will get errors. Well, least I did.
Make sure you download some type of toolkit it would make life a lot easier. I used this one it worked like a charm!
At the moment, my phone is bootloader unlocked and s-off fyi.
Next, Use the tool to "lock" your bootloader first not "re-lock" just "lock". If you're having issues push revone again and follow commands on toolbox.
Now, check hboot to see if it shows "locked" if it has tampered above locked that's ok the RUU will take care of that.
Run, the RUU, make sure usb debugging on and htc sync already installed. Let it run.
After its done, start up phone again, turn off fastboot under "power" and turn usb debugging on again.
Start up toolkit, look to the right and it will say "s-on" device. You can only s-on after you've ran the RUU and are on stock hboot and rom.
Check Hboot again and it should read "Locked" and now "s-on".
Phone now ready to send back for warranty or etc.
Hope this helps anyone that searches. I found a few thread via google and they helped out a bunch.