Related
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Watercycle said:
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Click to expand...
Click to collapse
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
a.mcdear said:
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
Click to expand...
Click to collapse
unguarded or super user? and thank you i didn't know about that =)
Watercycle said:
unguarded or super user? and thank you i didn't know about that =)
Click to expand...
Click to collapse
Sueperuser not unguarded
this is the most rediculous process ever! (currently trying to wire trick) I'VE USED 2 DARN TYPES OF WIRE AND A PAPERCLIP AND NONE OF THEM DO ANYTHING
oh god, whew... i was running around the house making a wire out of everything...
but after trying the paperclip for like the 8th time (which took a half hour to find) it seems to have worked
S-off is the most stressful android activity ever >XO
thanks you two <3
You did use the ics jb hboot right? Make sure you can see the sd card? And don't unlock your phone again. You would need to s-on then s-off again for it to say locked. I just woke up and saw your new posts, its been a long day but I see you got help. Welcome to the club, glad it finally worked.
sent from my Clean Rezound
I used the Hboot that came with 3.14 Ruu, if S-off took the "relocked" away then i'm happy, if it didn't, oh well, but I was unlocked when I started the process =o
As long as you don't unlock it after s-off, it will be locked again ( although it says "juopunutbear" instead of "locked" if you're using their modified boot. Just flash a stock one and it will say locked)
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The patched hboot adds some advanced fast boot commands. However everything will work without the patched hboot. You don't need it its just nice to have
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
ericsignals said:
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
Click to expand...
Click to collapse
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Forgot to add that part when I typed the adb part ....thanks for correcting me.:thumbup:
Sent from my Rezound
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Watercycle said:
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Click to expand...
Click to collapse
Yes, but there are ways around that
I personally just package my own ph98img.zips if I need to flash a kernel or recovery after doing something dumb
Sent from my ADR6425LVW using Tapatalk 2
If you want to add the JB Hboot, it is very simple. You can go to their site and just download the most recent hboot. You must know if you are ICS or GB. But go here: http://unlimited.io/hboot-downloads/ and download the right one, either vigor ics or vigor gb. Put that in the folder where you had put the original controlbear program and follow these instructions:
To flash the JuopunutBear hboots
Put the phone in fastboot mode, connected to the pc and enter the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
Thats all there is to it and you can now benefit from the JB Hboot.
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Yes you need to be unlocked. It's part of the prerequisites. Please read then reread the thread in general "s-off with instructions...it's official". Understand how to avoid problems and fix them if they arise. It's very easy but it's like people half ass reading the instructions recently. Don't be that person.
sent from my Clean Rezound
th3rapist said:
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Click to expand...
Click to collapse
You have to unlock befor you s off, afterwards it's redundant to do so. But some people have
Sent from my ADR6425LVW using Tapatalk 2
doubleshot, ruby ICS, vigor ICS, holiday ICS, pyramid ICS?
which one? haha
I don't mind don't 1 more small flash that will probably be necessary in the future as long as it doesn't screw my current rom up
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.
Hey,
I have a Telus Amaze 4G and I have lost my radio. Phone says it has an unknown Baseband/IMEI. Not sure where I went wrong/ lost my radio but this is a run down of what I've done to my handset so far:
- Rooted
- Flashed CWM recovery.
- Flashed EnergyRom.
- Sent phone to HTC because of suspected warranty issue. (Wouldn't Charge)
- Phone returned un-repaired from HTC.
- Charged battery externally, phone finally booted.
- Replaced CWM with 4EXT.
- Ran the Telus GB RUU exe from windows.
- Did the OTA ICS from the phone.
- Attempted upgrade to SpeedRom, failed because the OTA had failed, didn't realize this until the next around, this is where I think it went wrong. Had done a full wipe of all partitions, except SD from 4EXT in the process.
- Re-applied original Telus GB RUU.
- Re-applied Telus ICS OTA. this is when I realized I had no radio. I had not put in my SIM-Card since the phone was returned from HTC so not exactly sure when it stopped working but the OTA had installed correctly this time.
- Re-rooted.
- Did the wire-trick and obtained S-OFF.
- Flashed the latests JP hboot.
- Used fastboot to flash several radio.img files from various TMO and Telus RUUs, nada.
- Flashed the T-Mobile ICS RUU via hboot, still no radio.
- Extracted the rom from the Telus GB RUU and applied that via hboot, still no radio.
The only thread I could find where someone had mentioned the missing baseband on an amaze 4g, the only suggested fix was to reflash a stock, GB rom but that didn't work. Now I am at a loss at to what I could try next.
Any suggestions would be greatly appreciated.
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Jay_Rulen said:
found this thread fro you maybe that will help you get a idea http://forum.xda-developers.com/showthread.php?t=1627565
Click to expand...
Click to collapse
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Dark Nightmare said:
He means the built in antenna radio software drivers. Your best call would be warranty replacement, probably a bad chipset issue.
Click to expand...
Click to collapse
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
inluck said:
Not cool.... so Telus/HTC already know that I've had third party software on my handset after I returned it the last time. If I was to reverse *everything* I've done, do you think I could get it back to a point in which they would still honor the warranty?
Thanks!
Click to expand...
Click to collapse
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
inluck said:
Okay, I can totally do all that. One last question though, when my phone was last returned to HTC, they discovered I had 3rd party software on the phone and refused to look at it any further, do you think this will have an effect on a second return?
Click to expand...
Click to collapse
I can't say, just keep your fingers crossed that it doesn't.
Dark Nightmare said:
You said you're s-off, rights? Flash a pure stock ruu, lock the bootloader via fastboot using the command fastboot oem lock. Check the bootloader to make sure it says locked, then in fastboot use the command fastboot OEM writesecureflag 3 to s-on. Once you're all done, give 'm a call again. Said it happened when you updated to ics or something.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
inluck said:
Know off the top of your head how to remove the *RELOCKED* from the bootloader?
Click to expand...
Click to collapse
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
How did you lock the bootloader? Manually or via hasoons tool? Did you s-on as yet or still s-off?
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
inluck said:
I had extracted the rom.zip from the Telus GB RUU and flashed it to the handset from hboot. This removed the jp hboot and put it back to stock.
I then booted into fastboot and issued these commands from the cli:
fastboot.exe oem lock
fastboot.exe oem writesecureflag 3
So to answer your questions, manually and I am now S-ON.
I get the feeling I need to issue those commands from the jp hboot instead of the stock. Am I right?
Click to expand...
Click to collapse
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Dark Nightmare said:
You should've made sure the bootloader said locked first -_-, oh well, unless you wanna s-off again, hope they don't make an issue out of it. Why did you put exe at the end of fastboot? You did it before s-on, it should say locked, odd.
Sent from an Amaaaaaazing place :-D
Click to expand...
Click to collapse
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
inluck said:
It said relocked, I wasn't sure at which point that was supposed to disappear/changed.
I'll S-OFF again once the thing gets another charge.
I have a feeling it was because I was in the stock GB hboot and not the modified jb hboot.
Don't want to leave anything for them to complain about.
Click to expand...
Click to collapse
It's not the hboot. I gotta find the s-on thread, since you have to be on a stock bootloader before you s-on. I probably missed something.
Sent from an Amaaaaaazing place :-D
http://forum.xda-developers.com/showthread.php?t=1647728
I just remembered another trick as well, when you s-off the device, it relock your bootloader but it says "locked" not relocked, therefore when you s-off, do not flash the jb hboot when they ask you if you wanna flash it, then simply s-on via the fastboot command, voila!
Sent from an Amaaaaaazing place :-D
Alright people, I need help. I have an HTC Rezound (obviously) for verizon. I want to go back to Complete Stock, (as if it were brand new).
It was unlocked using HTC devs method
Its rooted
It is s-on
The recovery file i used is : recovery-ra-vigor-3.16-gnm
I installed a custom rom: Business_ICS4.0.3_Sense3.6-v6.3
Android version 4.03.605.2
HTC Sense 3.6
How do i get my phone to be:
Completely stock
Stock rom
no root
Locked title in Hboot
fix the tampered title in hboot
Any help is much apreciated
Are you doing this to warranty it? It will say "relocked" when you are done. It hasn't been a problem for anyone in the past though, you should still be able to return it to Verizon.
Instructions on how to return to stock are here:
http://forum.xda-developers.com/showpost.php?p=38244272&postcount=10
You probably should use the latest official RUU (prior to the OTA they just rolled out a couple days ago) which is 3.14.605.12. The link I have is to an .exe file. You just connect your phone to your pc and then double click. It will take you through the steps.
Get it here:
http://androidfiles.org/ruu/?dir=Vigor
That will get you back to stock, unrooted and it will say "relocked".
There was a global leak that wasn't official. If you want to use that, get it here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
This is a zip file you put on your external sd card. Follow instructions in the first link I gave you.
THANK YOU
feralicious said:
Are you doing this to warranty it? It will say "relocked" when you are done. It hasn't been a problem for anyone in the past though, you should still be able to return it to Verizon.
Instructions on how to return to stock are here:
http://forum.xda-developers.com/showpost.php?p=38244272&postcount=10
You probably should use the latest OTA, prior to the one they just rolled out a couple days ago which is 3.14.605.12. The link I have is to an .exe file. You just connect your phone to your pc and then double click. It will take you through the steps.
Get it here:
http://androidfiles.org/ruu/?dir=Vigor
That will get you back to stock, unrooted and it will say "relocked".
There was a global leak that wasn't official. If you want to use that, get it here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
This is a zip file you put on your external sd card. Follow instructions in the first link I gave you.
Click to expand...
Click to collapse
Thank you so much it worked like a charm!!! You just saved me from a weeks worth of searching i did and a couple of headaches.. Thank you very much
You're welcome, glad it worked for you!
I noticed I typed the wrong thing when I said "latest OTA", I should have said "latest official RUU" (don't know what was going on in my head) so I'm going to edit that post to fix it for any future readers.
okay, im having the same problem, except im s-off. i need to send my rez back for warranty reasons, i have a custom rom, my h-boot says locked, s-off, 2.27.000. any help would be awsome! thanks!
motodanr1 said:
okay, im having the same problem, except im s-off. i need to send my rez back for warranty reasons, i have a custom rom, my h-boot says locked, s-off, 2.27.000. any help would be awsome! thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=
Sweet, thanks! When I click on the link I get "no thread specified" though ..?
Sent from my ADR6300 using xda app-developers app
Go into dev, sticky, roll up thread. Click on back to s-on link
Phaded said:
http://forum.xda-developers.com/showthread.php?t=
Click to expand...
Click to collapse
I was Tampered/Locked and s-off. I ran the 4.03.605.2 RUU twice then its said locked the tampered was removed. I used the mini-adb_vigor program to achieve S-ON. Open a Command prompt wtih admin privileges and enter these commands pressing enter after each one. Now I am completely back to Locked S-ON. Hope this helps.
cd c:\mini-adb_vigor
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
netookska05 said:
I was Tampered/Locked and s-off. I ran the 4.03.605.2 RUU twice then its said locked the tampered was removed. I used the mini-adb_vigor program to achieve S-ON. Open a Command prompt wtih admin privileges and enter these commands pressing enter after each one. Now I am completely back to Locked S-ON. Hope this helps.
cd c:\mini-adb_vigor
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Click to expand...
Click to collapse
Make sure to run this on a stock hboot or it will brick.
I am having a similar issue. I am rooted, I never relocked my bootloader, stock minus a few mods, but the ota update keeps failing. What do I need to do to be able to accept the update so it stops rebooting my phone?
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.