Bootloader to show "Locked" - AT&T HTC One (M7)

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.

Related

Bootloader is LOCKED please help

I flashed the newest RUU and now my bootloader is highlighted in pink and says LOCKED.
Sooo how do I unlock it since I cannot flash anything in Bootloader now??
flooritnfly said:
I flashed the newest RUU and now my bootloader is highlighted in pink and says LOCKED.
Sooo how do I unlock it since I cannot flash anything in Bootloader now??
Click to expand...
Click to collapse
not "security warning"?
loonatik78 said:
not "security warning"?
Click to expand...
Click to collapse
Nope. It is highlighted in pink and says LOCKED.
I see nothing that says "Security Warning" anywhere.
I just flashed this RUU: http://forum.xda-developers.com/showthread.php?t=1225752&highlight=2.11.605.0
and while it was updating in Bootloader it locked it.
flooritnfly said:
Nope. It is highlighted in pink and says LOCKED.
I see nothing that says "Security Warning" anywhere.
I just flashed this RUU: http://forum.xda-developers.com/showthread.php?t=1225752&highlight=2.11.605.0
and while it was updating in Bootloader it locked it.
Click to expand...
Click to collapse
I searched for that all over. couldn't find anything like it. Ever tried IRC? There's usually some fairly knowledgeable folks there who might be of help. The network is andirc.net, channel #thunderbolt.
Somebody please save me.....I just don't understand how I can fix it when all the "fixes"require flashing something.... But my bootloader is locked so I cannot flash anything
Sent from my ADR6400L using XDA App
If anyone comes up with the solution PLEASE post it, I have the same problem. thanks.
WOW! Revolutionary Finally worked on my phone!! Now instead of a Pink **LOCKED** I have a nice pink --REVOLUTIONARY--!! So...I suggest trying REVOLUTIONARY!!
The pink locked is because the newest RUU has an hboot with support for official unlocking through HTC. Not that we will ever see that or need it. Like you said Revolutionary will s-off that hboot no problem. Just thought I would shed some light on the pink "locked" deal.
Sent from my HTC Thunderbolt
JBO1018 said:
The pink locked is because the newest RUU has an hboot with support for official unlocking through HTC. Not that we will ever see that or need it. Like you said Revolutionary will s-off that hboot no problem. Just thought I would shed some light on the pink "locked" deal.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
So tell me exactly what I do please...
Sent from my ADR6400L using XDA App
1. follow link below
2. Get s-off
3. Flash ROM
4. ???
5. Profit
http://revolutionary.io
Sent from my HTC Thunderbolt
Umm...I downloaded the revolutionary.zip and ran the app on my PC and nothing happens....it just hangs at "waiting for device" even with my phone connected.....
Could you spare 4 minutes and be a bit more specific?
flooritnfly said:
Umm...I downloaded the revolutionary.zip and ran the app on my PC and nothing happens....it just hangs at "waiting for device" even with my phone connected.....
Could you spare 4 minutes and be a bit more specific?
Click to expand...
Click to collapse
you may need htc sync and the android sdk installed first. also make sure usb debugging is on under your phone settings.
you didnt read their page,you need the drivers they have listed,unistall anything you already installed,install the drivers from their page and it will see your phone,but if you would have read the instructions you would have known that, never mind you guys never learn even on the post with the ruu it says it will lock your bootloader,so why flash it,oh sorry you would have had to read that also!
Sent from my ADR6400L using xda premium
Finally got it.....did the EXACT same thing I did before and it worked the 2nd time......whatever.

HTC Unlock tool OTA 2.17.651.5

Hey everyone, I am unable to unlock my bootloader after accepting this OTA. I just got an EVO 3D yesterday and I updated it as soon as I got it. I first checked to see if it was an HBOOT below 1.5, it wasn't so I went ahead and updated. However when i get to step 12 i believe on the htc dev site, I flash the unlock_code.bin and nothing happens just sits there. I read around and found people saying you need to take the 2.08 RUU, I tried that and when it gets to the black HTC screen I get an error 140. I was so excited to get this phone and already downloaded the rom i wanted before owning it. If someone can please help me out I would appreciate it. Thanks
No one? Dam..
Sent from my PG86100 using XDA App
majid25 said:
No one? Dam..
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Did you try factory reset or battery pull then give it another go? Also did you follow all the steps anyways give her another go.
frustrated
majid25 said:
Hey everyone, I am unable to unlock my bootloader after accepting this OTA. I just got an EVO 3D yesterday and I updated it as soon as I got it. I first checked to see if it was an HBOOT below 1.5, it wasn't so I went ahead and updated. However when i get to step 12 i believe on the htc dev site, I flash the unlock_code.bin and nothing happens just sits there. I read around and found people saying you need to take the 2.08 RUU, I tried that and when it gets to the black HTC screen I get an error 140. I was so excited to get this phone and already downloaded the rom i wanted before owning it. If someone can please help me out I would appreciate it. Thanks
Click to expand...
Click to collapse
Same here.
The same RUU I used to revert to the .2sw update to unlock two other evo3d's with hboot 1.5, will not work. Im unbelievably frustrated right now as Ive been sitting at this computer for over three hours. Please, if you find a way to downgrade your software, please let me know. thanks
not sure why you wanted to be on hboot 1.50. but shouldnt be a problem to unlock the bootloader, since it was just minor updates and still on hboot 1.50. id just try doing the process again.
i unlocked mine with unlock_code.bin that i used when i rooted my evo 3d for 1st time.....it worked fine.
Tried 5 times and failed..
Sent from my PG86100 using XDA App
evoRomz said:
not sure why you wanted to be on hboot 1.50. but shouldnt be a problem to unlock the bootloader, since it was just minor updates and still on hboot 1.50. id just try doing the process again.
Click to expand...
Click to collapse
I didn't want to be on hboot 1.5, I wanted to be below it. But when I first got my phone I checked the bootloader and was already at 1.5. If it was below that I would've been rooted right now...
to be a bit more clear it was hboot 1.5 with an OTA 2.08 when I first received the phone.
Sent from my PG86100 using XDA App
majid25 said:
I didn't want to be on hboot 1.5, I wanted to be below it. But when I first got my phone I checked the bootloader and was already at 1.5. If it was below that I would've been rooted right now...
to be a bit more clear it was hboot 1.5 with an OTA 2.08 when I first received the phone.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
1st Check you bootloader .What it says at the top .(locked/unlocked/relocked) if it says unlocked you do not need unlock_code.bin.
Try these from step 13:
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/
You can flash another recovery in step 18 .....
mnomaanw said:
1st Check you bootloader .What it says at the
http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/
Click to expand...
Click to collapse
That's the guide I used to HTC Unlock. Video helped. There is a post somewhere about needing to Re-flash the stock RUU.exe or Ruu.zip (renamed to PG86IMG.zip) to get the phone past the "nothing happens" step where you're supposed to get the "unlock" option screen on the phone. I haven't seen the 651.5 released as a complete RUU, but you could probably flash the 651.3 RUU, finish the HTC unlock and then run the 651.5 update. Heck, the unlock would probably work after the update, idk for sure.
I have some links and my issue with this below.
SOLVED-Stock Hboot1.50 HTC Unlock/ RUU 651.3 flash problems (1-14-12) http://forum.sdx-developers.com/?topic=18852.0
Evo3d Useful Links(md5's): http://forum.sdx-developers.com/?topic=18827.0
Edit: Here's where I saw the info about flashing the RUU to get a good unlock:
(XDA) JTniggle's [GUIDE] HTC Unlock Hboot 1.50 + TWRP Recovery + Root + Flash!! [9.11.11] (All via ADB)
http://forum.xda-developers.com/showthread.php?t=1239821
Says locked.
mpgrimm2 said:
That's the guide I used to HTC Unlock. Video helped. There is a post somewhere about needing to Re-flash the stock RUU.exe or Ruu.zip (renamed to PG86IMG.zip) to get the phone past the "nothing happens" step where you're supposed to get the "unlock" option screen on the phone. I haven't seen the 651.5 released as a complete RUU, but you could probably flash the 651.3 RUU, finish the HTC unlock and then run the 651.5 update. Heck, the unlock would probably work after the update, idk for sure.
I have some links and my issue with this below.
SOLVED-Stock Hboot1.50 HTC Unlock/ RUU 651.3 flash problems (1-14-12) http://forum.sdx-developers.com/?topic=18852.0
Evo3d Useful Links(md5's): http://forum.sdx-developers.com/?topic=18827.0
Edit: Here's where I saw the info about flashing the RUU to get a good unlock:
(XDA) JTniggle's [GUIDE] HTC Unlock Hboot 1.50 + TWRP Recovery + Root + Flash!! [9.11.11] (All via ADB)
http://forum.xda-developers.com/showthread.php?t=1239821
Click to expand...
Click to collapse
Thank your for all the help. However I tried doing what is said in these links, I ran the 2.08.651.3 RUU and at the black HTC screen I get the error 140. Can I downgrade OTA's or no? Cuz that what it looks like I have to do here.
majid25 said:
Thank your for all the help. However I tried doing what is said in these links, I ran the 2.08.651.3 RUU and at the black HTC screen I get the error 140. Can I downgrade OTA's or no? Cuz that what it looks like I have to do here.
Click to expand...
Click to collapse
I could before the .5 update. Had to get a new phone last night and it will not downgrade to the .2 software so I can then unlock. Frustrating to say the least. Actually, I'm pissed about it.
Sent from my Google Nexus S 4G via XDA Premium
How did you get a new phone, through Sprint? And yea this sucks, hope there is a solution soon I've been posting everywhere like an idiot haha
majid25 said:
How did you get a new phone, through Sprint? And yea this sucks, hope there is a solution soon I've been posting everywhere like an idiot haha
Click to expand...
Click to collapse
Yeah, returned it. Dead pixel. Now I'm stuck with this bs bloat on here cause I can't downgrade and unlock.
Sent from my Google Nexus S 4G via XDA Premium
Edit: I cant even get a damn temp root! Stuff is pissing me off. Bout to go iphone so I dont have to nerd it up and waste my damn time, which isnt even that valuable.
I say you try to just wait it out a bit. Give it a week...but don't go iPhone!!!
majid25 said:
I say you try to just wait it out a bit. Give it a week...but don't go iPhone!!!
Click to expand...
Click to collapse
At the rate devs are dropping off, a week is an eternity. And I'm new to the evo3d. Sad face.
Sent from my Google Nexus S 4G via XDA Premium
tailsthecat3 said:
Yeah, returned it. Dead pixel. Now I'm stuck with this bs bloat on here cause I can't downgrade and unlock.
Sent from my Google Nexus S 4G via XDA Premium
Edit: I cant even get a damn temp root! Stuff is pissing me off. Bout to go iphone so I dont have to nerd it up and waste my damn time, which isnt even that valuable.
Click to expand...
Click to collapse
What method did you try for temp root?
Crackanug said:
What method did you try for temp root?
Click to expand...
Click to collapse
Frevo.
Sent from my Google Nexus S 4G via XDA Premium
tailsthecat3 said:
Frevo.
Sent from my Google Nexus S 4G via XDA Premium
Click to expand...
Click to collapse
I have some tools and files for you to use that will give you temp root and allow a downgrade to 2.08.651.2 rom, hboot will still be 1.50 though. However from there you should be able to unlock via HTCdev method. I gotta upload the files and write the code which I will post up here in a second. I hope you are ok with using adb and fastboot.

[Q] S-off phone going to my kid; what to flash?

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.

Ruu help.

I going to get a replacement from Verizon and I need to revert my phone back to stock. Right now I'm s on and my boot says tampered and unlocked how can I get back to stock. Will an ruu work?
If you look for the hboots thread in the dev section, there is a modified one that will say 'locked'. You just need to download it and flash. I believe you may actually have to re s-off temporarily to flash it though. Could be wrong
wildstang83 said:
If you look for the hboots thread in the dev section, there is a modified one that will say 'locked'. You just need to download it and flash. I believe you may actually have to re s-off temporarily to flash it though. Could be wrong
Click to expand...
Click to collapse
Could I just not flash the ruu I have on my SD card? Or would I have to soff for that?
Sent from my Rezound using XDA
You can, but it wouldn't do any good as the ruu would not clear the tampered, unlocked message. This is why you need the modified hboot I mentioned. It has the message modified that has the correct message of 'locked'.
Grab the one called 'locked'
http://forum.xda-developers.com/showthread.php?t=1853871
Remember, I believe you may have to be s-off, you might brick if not.
USE THIS
erisboxx said:
I going to get a replacement from Verizon and I need to revert my phone back to stock. Right now I'm s on and my boot says tampered and unlocked how can I get back to stock. Will an ruu work?
Click to expand...
Click to collapse
Use this to relock http://forum.xda-developers.com/showthread.php?t=1504824:D
But play it smart dont brick it if you think you need to do something before hitting re-lock then do it!!!
lpcar04 said:
Use this to relock http://forum.xda-developers.com/showthread.php?t=1504824:D
But play it smart dont brick it if you think you need to do something before hitting re-lock then do it!!!
Click to expand...
Click to collapse
But I'm trying to make it look completely stock won't it show "relocked"?
Sent from my Rezound using XDA
lpcar04 said:
Use this to relock http://forum.xda-developers.com/showthread.php?t=1504824:D
But play it smart dont brick it if you think you need to do something before hitting re-lock then do it!!!
Click to expand...
Click to collapse
Why would he use that? It won't do what he needs to do. Seriously now, we appreciate your effort to help, but please don't add confusion to a simple task especially after I've taken the time to tell eris exactly what he needed to do..
And you do need to s-off then flash the hex edited hboot.. all you need is for that phone to stay locked and be on a stock Rom and your good. Verizon doesn't usually check as long as you went thru the trouble shooting process with them over the phone and theyll send you a new one in the mail and you'll ship the old one back. They can't technically send you a phone and then charge you for the old one (if it is ***tampered***) cuz they wouldn't have done the proper trouble shooting before sending you a new phone. For all they know you got your phone that way.
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
famouscollin said:
And you do need to s-off then flash the hex edited hboot.. all you need is for that phone to stay locked and be on a stock Rom and your good. Verizon doesn't usually check as long as you went thru the trouble shooting process with them over the phone and theyll send you a new one in the mail and you'll ship the old one back. They can't technically send you a phone and then charge you for the old one (if it is ***tampered***) cuz they wouldn't have done the proper trouble shooting before sending you a new phone. For all they know you got your phone that way.
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
Click to expand...
Click to collapse
Can you point me in the direction for a "stock rom"?
Sent from my Rezound using XDA
erisboxx said:
Can you point me in the direction for a "stock rom"?
Sent from my Rezound using XDA
Click to expand...
Click to collapse
heres the latest ruu.. itll give you stock EVERYTHING http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ lock your bootloader, relock your bootlader, run the ruu, twice, i think after it still says relocked (havent done it myself in a while) if so s-off from there, then flash the hex edited hboot..

*security warning* Stuck in bootloader

I've done a bunch of searching on this and finally gave up and decided to ask it here because I can't find anywhere with actual info on it... I was trying to ruu back to the 2.13 base and then reroot from scratch with the new radios but ended up getting stuck in the bootloader with **TAMPERED** **RELOCKED** and **Security Warning** as the headers. It won't let me reboot, it won't let me into recovery, and I'm getting frustrated ... I still have access to fastboot but I'm useless with commands so I haven't been able to fix it. Any help?
Basically, here's the whole details.
I'm on hboot 1.15 s-on, dev-unlocked using regaw's rooting+unlocking tool. The phone had the 2.13 deodexed running, got it from here http://forum.xda-developers.com/showthread.php?t=1860728
Had twrp 2.X (the version before the latest) installed
I tried running the latest ruu.exe on my computer but it kept failing so I looked it up and assumed it must be because I was dev-unlocked.
Went into the bootloader>fastboot and locked it with fastboot oem lock
The phone rebooted into bootloader with the ** Security Warning** header and now I'm stuck...
I would try the downgrade thread.. It's pretty easy and I believe it can be done from bootloader. Then instead of going thru all that hassle, use one of the radio upgrades from captain throw back on themikmik. Just my opinion. Worst that could happen is it doesn't work. Anyone else have feedback on this??
Sent from my EVO using xda premium
sparytrainor said:
I would try the downgrade thread.. It's pretty easy and I believe it can be done from bootloader. Then instead of going thru all that hassle, use one of the radio upgrades from captain throw back on themikmik. Just my opinion. Worst that could happen is it doesn't work. Anyone else have feedback on this??
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I think I figured it out.. I dug a little deeper into some other threads I found on it from people who've done this before. One of them managed to fix it by running the RUU from the bootloader. It took me a bit to realize it had to be in fastboot (facepalm) for it to run. It failed the first time but it looks like its working this time. :good:
Good luck to ya. I hope it works out.. I would still recommend using the hacked upgrades for radios and such.
Sent from my EVO using xda premium
Do you know with the security warning will cause running an RUU to fail?
rubyknight said:
I think I figured it out.. I dug a little deeper into some other threads I found on it from people who've done this before. One of them managed to fix it by running the RUU from the bootloader. It took me a bit to realize it had to be in fastboot (facepalm) for it to run. It failed the first time but it looks like its working this time. :good:
Click to expand...
Click to collapse
I'm in the same boat as you were - can you point me to where/how you got the RUU to run? I've got exactly the same situation, but my RUU (2.13) won't run, either in fastboot or the bootloader.

Categories

Resources