Well I unlocked my bootloader no problem, then i tried to flash a recovery to which i get the messages okay. After that I tried to boot into recovery via cmd with the command adb reboot recovery which worked and my device turned off, turned back on and for a split second had some red text under the HTC logo and immediatly started back up. I then tried to go to bootloader which I did via cmd and adb reboot Bootloader, and now above unlocked it says tempered. Please help me out with what I should do. Also there is no recovery option available. I was trying to flash TWRP.
The red text just tells you you're on an unlocked bootloader. And the tampered stamp stays there for all eternity after you've unlocked the bootloader.
Anyway you have nothing to worry about. It's just what happens when you unlock the bootloader.
Sent from my HTC One X using Tapatalk 2
Thank you sir just got into recovery I was really worried!
You CAN get rid of the tampered flag by relocking the bootloader and running a ruu. But your bootloader will say relocked in bright red still so it wouldnt matter. Just sayin'..
Yea no point of that
18th.abn said:
You CAN get rid of the tampered flag by relocking the bootloader and running a ruu. But your bootloader will say relocked in bright red still so it wouldnt matter. Just sayin'..
Click to expand...
Click to collapse
No one knows of a way to get rid of the "re-lock" and have it just say locked?
sixty_oz said:
No one knows of a way to get rid of the "re-lock" and have it just say locked?
Click to expand...
Click to collapse
Maybe I'm wrong, but I was under the impression that if you re-lock and run RUU, it changes back to original "Locked" state...
[deleted]
I'm pretty sure it stays as "Relocked" even with an RUU
You can only change that with S-OFF
Sent from my HTC One X using Tapatalk 2
[deleted]
Related
I'm looking to go back to stock so I can sell my device.
I mainly need to get stock recovery and stock software back on the phone.
Is it as simple as flashing a RUU? I know this will restore the stock software, but will it flash stock recovery too?
Also, is relocking the bootloader as simple as "fastboot oem lock"?
Thanks for the help.
The answer to your questions is yes.
Yep.
Relock the bootloader, run an RUU. You'll be good to go.
_MetalHead_ said:
Yep.
Relock the bootloader, run an RUU. You'll be good to go.
Click to expand...
Click to collapse
hi, I'm in the same position now, I want to sell my phone and need to lock the bootloader. I just want to be acting as meticulous as I can be since I've hard bricked a GNote before just because I didn't read the instructions carefully.
I've used the htcdev method to unlock the device. On the road the stock, what's next step I should take ? How do I re-lock the bootlader ?
Boot to recovery. Then run fastboot oem lock.
gunnyman said:
Boot to recovery. Then run fastboot oem lock.
Click to expand...
Click to collapse
After that, should I flash a stock ROM ? is that it ?
Yes
One thing to note when relocking the bootloader and I don't think it's normal but it happened to me, it may result in a bootloop that won't let you out of the hboot screen. It didn't happen to me the first couple of times I did it to return to stock, but the last 2 times I did after relocking the bootloader I had the tampered warning at the top which is normal, and then relocked, but below that it said security warning. I don't recall seeing that in the past which maybe it was normal, however I was stuck in an endless hboot loop. Trying to shutoff and restart the phone or go into recovery or any option other than fastboot really all resulted in the same thing. I would be returned to the hboot screen. If this happens just select fastboot and plug in the phone and run the ruu like normal.
like I said the first couple times I relocked it went off without a hitch but then that started happening so this is just a little tip should the same thing happen.
When you lock the bootloader with a custom recovery installed, that is the expected behavior.
That would explain it then, thanks gunny. The first couple of times I performed this I was just doing it to familiarize myself with the steps, you know, burn them into my thick skull. I hadn't actually put cwm or twrp on yet. I guess now I understand why it was different.
Just updating...
I was able to relock the bootloader and flash the run with no problems.
I'm assuming there's no way to ever get rid of the "tampered" banner on the top of the bootloader screen?
If you're stock unrooted tampered goes away.
provenflipper said:
Just updating...
I was able to relock the bootloader and flash the run with no problems.
I'm assuming there's no way to ever get rid of the "tampered" banner on the top of the bootloader screen?
Click to expand...
Click to collapse
gunnyman said:
If you're stock unrooted tampered goes away.
Click to expand...
Click to collapse
I'm sorry, I meant there's no way to make the "relocked" banner go away.
Unless we get s - off nope. It will say re locked
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
very simple to fix. The fact that you got to the "ready to unlock?" screen means the unlock token works.
go into settings on the phone go to power. Turn OFF fastboot.
Power off the phone completely.
Boot to bootloader
send the unlock.bin again
this time it will stick.
saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
Sometimes the phone can get confused about its locked state.
To fix:
-Force reboot the phone. Hold the power button for 10+ seconds until bottom lights flash and then stop.
-Boot in to bootloader
Now force the phone to lock even if you think it is locked already.
-fastboot oem lock
-fastboot flash unlocktoken Unlock_code.bin
Sending "fastboot oem lock" tends to get the phone back on the right track so it doesn't just keep rebooting in to a relocked state.
get into bootloader manually volume down + power.
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
yes root will happen.
unlock bootloader. Install twrp recovery. Flash the root package found here http://forum.xda-developers.com/showthread.php?t=1673935
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Ethere said:
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Click to expand...
Click to collapse
I think you may have to use fastboot flash recovery recovery.img because of the new limitations of the new HBOOT. It might be only for boot.imgs though
That worked rohan32 Thanks so much to both of you. Now I have an unlocked bootloader and TWRP installed. Going for root now. Thank you thank you thank you! You guys have saved me from wanting another phone!
[EDIT]Rooted as well. Again, thank you both so much!
thanks everyone i solved my problem.dint except quick replies from you guys.
Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
If you stay away from the AT&T cid you will be fine.
In theory things could change but at the moment so long as you have super cid prior to RUU flashing you will be fine.
OK I just got my AT&T HOX today and from what I've read hear there is no way to root it? Since I have 2.20.502.7 710RD but if I use super cid I can flash roms?
Without root you can't get super Cid
Please update the title and add "Resolved"
Sent from my HTC One XL using xda premium
I have previously rooted my device, but was bothered by the bootloader saying
Tampered
Unlocked
I then decided to restore it to factory/stock rom, which I was successful in doing, and bootloader is now relocked
I used Hasoon2000's toolkit and followed all the steps correctly, everything said it was successful but when i boot into bootloader says that it is still relocked
What could be causing this?
I'm running 2.20 btw, h-boot 1.14
htc one x evita AT&T
i am new to this as well but im pretty sure it will stay "relocked"
as you tampered with it already and there is no way of getting it back to normal (from what i read in the forums) more knowledgable people correct me if im wrong
i believe the only way to get it not to say relocked is with s-off
I think he's trying to unlock his bootloader again, not trying to get rid of the relocked message.
Sent from my HTC One XL
The only way to change that in the bootloader is to s-off then some other fun stuff.
Sent from my HOX w/CM10.1 4.2.2 s-off
ECEXCURSION said:
I think he's trying to unlock his bootloader again, not trying to get rid of the relocked message.
Sent from my HTC One XL
Click to expand...
Click to collapse
Yeah that's what I'm trying to do...
I just went through the toolkit process again, and same thing. still says relocked
Radio S-Off was mentioned, what are some of the basic steps required for that?
swagglikerichie said:
Yeah that's what I'm trying to do...
I just went through the toolkit process again, and same thing. still says relocked
Radio S-Off was mentioned, what are some of the basic steps required for that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=38174259
Sent from my HTC One XL
sorry i misread your post
Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?
mikel.canovas said:
Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?
Click to expand...
Click to collapse
Can you get to bootloader? Fastboot access? You were soff previously correct?
Sent from my One Xl using Tapatalk 2
jrior001 said:
Can you get to bootloader?
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel
mikel.canovas said:
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/evita
From twrp's site grap the 2.6.3 recovery.IMG and with phone in bootloader where you see "fastboot usb" type in cmd promt fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
And the fastboot reboot-bootloader
Then navigate and try to get to recovery again
If you get that far flash ROM again, just that for now and relax for a bit
Sent from my One Xl using Tapatalk 2
Getting an error after writing recovery. Saying FAILED (remote: not allowed)
mikel.canovas said:
Getting an error after writing recovery. Saying FAILED (remote: not allowed)
Click to expand...
Click to collapse
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2
jrior001 said:
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
No bootloader is "relocked". I was in fastboot when I ran the RUU since ADB is not being recognized when in bootloader. RUU was successful, didn't seem like anything went wrong
Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.
redpoint73 said:
Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.
Click to expand...
Click to collapse
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work
mikel.canovas said:
Bootloader says relocked.
Click to expand...
Click to collapse
You need to unlock bootloader again to flash TWRP.
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel
mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel
Click to expand...
Click to collapse
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2
mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Click to expand...
Click to collapse
Using the unlock token is known to sometimes fail and require repeated attempts, just keep trying.
Not sure why the RUU didn't work, that is weird.
jrior001 said:
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
I've done the RUU twice now. Same results. Was s-off with 2.14 hboot
mikel.canovas said:
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work
Click to expand...
Click to collapse
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita
timmaaa said:
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader
mikel.canovas said:
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader
Click to expand...
Click to collapse
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita
timmaaa said:
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita
Click to expand...
Click to collapse
Then why has it failed 3 times? RUU is reporting successful. So what's the error?
Which error code is it giving you?
Sent from my Evita
timmaaa said:
Which error code is it giving you?
Sent from my Evita
Click to expand...
Click to collapse
RUU gives no error. It shows that it's successful
OK, tried to root my HTC One X, got the HTCDev unlock, but could never get an S-OFF on 5.18 firmware. Did have a CID unlock, so set it back to OEM Relock, and have tried to RUU the exact firmware back. It says its sucsessful but get a loop condition, White HTC, then a strange black screen, when I get back to Bootloader and tried again, same result. Any ideas, attached are pic. of strange screen and Bootloader
mbardsley said:
OK, tried to root my HTC One X, got the HTCDev unlock, but could never get an S-OFF on 5.18 firmware. Did have a CID unlock, so set it back to OEM Relock, and have tried to RUU the exact firmware back. It says its sucsessful but get a loop condition, White HTC, then a strange black screen, when I get back to Bootloader and tried again, same result. Any ideas, attached are pic. of strange screen and Bootloader
Click to expand...
Click to collapse
What were you trying to do in the first place? When you say CID unlock do you mean bootloader unlock? I think you're a bit confused about what you've been doing. Why did you relock the bootloader? What is your CID currently? Do not attempt to run the RUU again until we can confirm what your CID is, you could brick your phone.
Sent from a crappy Samsung because my Evita died
Confirmed CID is showing all 11111111, bootloader screen now says ***TAMPERED*** then ***UNLOCKED*** and still has S-ON, and this was a 5.18, which I think was my mistake for trying. Cannot run RUU utility, it wont complete, can get into TWRP recovery 2.6.0.0 but not able to flash, or anything. At this time would love to be able to just flash back to my stock.
Flash a Sense ROM, get s-off, run the RUU.
Sent from a crappy Samsung because my Evita died
THANKS! That did the trick, I knew I was close, but thought I had to get S-OFF before a flash of ROM.