ive re locked my bootloader but when i try to update it just goes to the hboot screen and at the top it says RELOCKED and underneath that it says Security Warning!!!!!
Any ideas please
mimicuk said:
ive re locked my bootloader but when i try to update it just goes to the hboot screen and at the top it says RELOCKED and underneath that it says Security Warning!!!!!
Any ideas please
Click to expand...
Click to collapse
It does that when you have re-locked the bootloader with a custom ROM or even a rooted stock ROM I think.
that might be something like on the Samsung phones with the triangle and exclamation point. i guess it's a double notice for HTC returns to know it was unlocked.
mimicuk said:
ive re locked my bootloader but when i try to update it just goes to the hboot screen and at the top it says RELOCKED and underneath that it says Security Warning!!!!!
Any ideas please
Click to expand...
Click to collapse
You need to do the process of going back to completely stock.
Flash stock recovery, then re-lock bootloader, then flash the RUU you are currently on. Cannot be an older version as Hboot changed. At least from 1.26 to 1.28 base.
Or if you want to just be able to boot again, you need to unlock bootloader again
mimicuk said:
ive re locked my bootloader but when i try to update it just goes to the hboot screen and at the top it says RELOCKED and underneath that it says Security Warning!!!!!
Any ideas please
Click to expand...
Click to collapse
I ran into this problem when I tried flashing the 1.29 OTA update today. The device would boot directly into hboot with RELOCKED and SECURITY WARNING at the top, and the only way to render it usable was to re-unlock the bootloader.
After flashing the boot image (I'd dumped a copy the day I got my phone), it booted normally, although it still said RELOCKED in hboot. If I remember correctly, the boot image can be extracted from the appropriate RUU, and I've also uploaded the copy I had (from 1.28.720.10) here: dl [dot] dropbox [dot] com/u/24520454/stockboot.img
Related
phone was given to me with damaged wifi functionality (listed ERROR instead of ON or OFF) found directions suggesting a rom flash to fix it... well.. things have gone down hill.
now stuck at HTC Whitescreen.
Bootloader Display..
*** UNLOCKED ***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.1111
eMMC-boot
July 18 2011,12:39:36
Recovery is CWM 4.0.0.4
last flash is 6.01.605.05_VZW_OTA-full-odex.zip
Flashed system and boot from that file (extracted boot.img).
I tried this, but suspected it wouldn't work as I can't get past the white HTC logo http://forum.xda-developers.com/showthread.php?t=1298990
Oddly I did end up seeing a BLACK screen HTC emblazoned across it. However after it finished I'm back to the white HTC screen hang.
HBOOT is still .98 so it seems to have had no appreciable effect.
Nova5 said:
I tried this, but suspected it wouldn't work as I can't get past the white HTC logo http://forum.xda-developers.com/showthread.php?t=1298990
Oddly I did end up seeing a BLACK screen HTC emblazoned across it. However after it finished I'm back to the white HTC screen hang.
HBOOT is still .98 so it seems to have had no appreciable effect.
Click to expand...
Click to collapse
It looks like it was unlocked using HTC Dev. You can't downgrade if you are unlocked already. Re-lock the phone (not sure how to do this, as I never did it this way), and then downgrade and S-Off. That is going to be your best option.
kubes069 said:
It looks like it was unlocked using HTC Dev. You can't downgrade if you are unlocked already. Re-lock the phone (not sure how to do this, as I never did it this way), and then downgrade and S-Off. That is going to be your best option.
Click to expand...
Click to collapse
Ahh, need to relock to downgrade? I missed that bit somewhere. Thanks. will try that then run the downgrade path again.
No luck.. Bootloader then shows
***Relocked***
*Security Warning*
Will not proceed past bootloader. So the ADB commands error out with "Error: device not found". I can't get into CWM recovery with a locked bootloader to allow ADB commands to work.
perplexing..
In addition when unlocked, in CWM I cannot mount System. Is that normal?
Nova5 said:
No luck.. Bootloader then shows
***Relocked***
*Security Warning*
Will not proceed past bootloader. So the ADB commands error out with "Error: device not found". I can't get into CWM recovery with a locked bootloader to allow ADB commands to work.
perplexing..
In addition when unlocked, in CWM I cannot mount System. Is that normal?
Click to expand...
Click to collapse
You might need to try the Taco Root Method.
http://forum.xda-developers.com/showthread.php?t=1751796
You can 100% do it. I never did it this way, but there is many others on this site that have been successful with this method.
A little back and forth play with the locked/unlocked status finally got it all working. Had to Unlock, enter CWM, format system, data, cache, , pull a boot.img from a zip file, flash that, reboot back to Fastboot, into recovery, mount system, data, cache, run the ADB section of the commands, reboot again into fastboot, relock (reboots on its own).. stick a RUU onto the microSD and slide that in. fail.. np, try another, and another. Finally found one it took and updated. Unbricked, Wifi is alive.
Downgrade may be possible at this point but probably not really worth it.
Hello, i have unlocked bootloader of my HTC One X with CID _032.
I have tried one Custom Rom with JellyBean and after i have returned on custom ICS Rom.
Now, when i try to upgrade phone with official OTA upgrade, the phone stuck on fastboot screen.
Bootloader is relocked.
Any idea to upgrade the phone with official OTA upgrade?
1) you need to be on a stock ROM to apply the upgrade (it won't work if you're on a custom ICS ROM as it sounds like you are).
2) you need to be on a stock recovery to apply the upgrade (it won't work if you're on cwm/twrp as it sounds like you might be).
There's plenty of "how to return to stock" threads around if either of the above apply.
I have relocked the bootloader and i am returned on stock recovery...
But when i reboot to install update, the phone stuck on fastboot screen, and i see on up "bootloader relocked-security warning"
What is the problem?
Deadoc3 said:
I have relocked the bootloader and i am returned on stock recovery...
But when i reboot to install update, the phone stuck on fastboot screen, and i see on up "bootloader relocked-security warning"
What is the problem?
Click to expand...
Click to collapse
The "bootloader relocked security warning" message is normal, it will always show that when the bootloader has been unlocked then locked again. That's nothing to worry about.
You are running a stock ROM yes?
Hello, just a quick question. I had my One rooted, s-off, and unlocked when my microphone went. So I relocked, s-on, and flashed an RUU via http://forum.xda-developers.com/showthread.php?t=2475216. Just making sure that before I pack it in the box, there is nothing else that could trip the people at Verizon that I had messed with my phone. I took the OTAs up to 4.3. I'm just paranoid about info not matching up such as the baseband version and build number etc. Thanks
Does the bootloader say locked or relocked? Locked is good relocked not so much. Other than that you should be fine. Ruu's wipe everything and install it all fresh, including the firmware (baseband, hboot, recovery, etc), so everything will match up.
In the bootloader I have "Locked" also s-on. I noticed though with the refurbished phone I received (not happy about having to get refurbished but thats besides the point) the CID number shows in the bootloader screen whereas on my original phone it is not displayed. Not sure if I even need to be this worried, but I'm just paranoid. Thanks
Are both phones on the same hboot version? I dont remember if it showed in older hboots or not. Either way i wouldn't worry, locked and s-on is all you need.
No they weren't. I'm just going to stop worrying too much about it. Thanks
If i send my phone back to verizon do i have to be on the original ROM? i understand that i need to lock my bootloader and have s-on, but what about the software itself?
It can be on stock rom/firmware of any version. Just no custom roms or anything.
Just to confirm, if I have a phone that is S-OFF, unlocked:
1. Do I need to lock the bootloader before flashing an RUU?
2. Does flashing an RUU revert the phone to S-ON?
3. Does anything special otherwise need to be done to the phone prior to flashing the RUU?
Thanks so much in advance.
I also have to return a phone to VZW due to a hardware issue (the autofocus issue finally too much for me to bear).
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Fantastically clear, Clumsco, thanks! Three quick additional questions
1. is there any advantage to flashing the signed RUU, and adding danger by locking the bootloader beforehand? In your links below your signature is a path to both decrypted and signed versions of the latest RUUs. So I thought to ask before going with one or the other. If there is no advantage then I guess the decrypted version would be the safer bet, right?
2. Is there a danger that locking after the RUU will result in a "relocked" versus the desired "Locked" status?
3. Will the RUU flash wipe my /sdcard area? If so I'll back everything up before embarking on this.
I VERY much appreciate the help. I ran rumrunner several months back and have forgotten a lot of the nuances. Thanks for the quick primer!
cmlusco said:
You only need to relock the bootloader if using a signed ruu. A decrypted ruu does not need it locked.
Flashing an ruu will not remove s-off or relock the bootloader. You can do it before or after, but i sugest after, that way if something goes wrong durring the ruu, you still have options.
Once you do the ruu you will be stock. So the only thing you would have to do is relock and go s-on.
Click to expand...
Click to collapse
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Thanks, everything worked. For future knowledge, can you flash signed RUU's with an S-ON device?
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
cmlusco said:
Yes and no. You can flash a signed ruu if s-on, but not one that is an older version than currently on the phone. It has to be the same or a newer version. This is an issue if your on kitkat, as we do not currently have a kk ruu available.
Click to expand...
Click to collapse
I'm trying to learn here too, that is dependent on the hboot correct? So if you were to downgrade your hboot via the thread somewhere in the VZW HTC One forum, you should be able to flash any RUU right?
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Your responses are clear and helpful. Thanks a bunch!
cmlusco said:
Technically yes, although as far as i know there is no way to do so while s-on and locked. In order to downgrade hboot you would need to have the bootloader unlocked. Since verizon does not let us use htcdev to unlock, it would be virtually imposible.
Click to expand...
Click to collapse
cmlusco said:
There is no difference between a signed and decrypted ruu other than what their names suggest. Ones signed ones not, both do the exact same thing to the phone.
You can lock the bootloader first. As long as you still have s-off, you have a saftey net. As long as your s-off you can change it to say what ever you want it to say. Locked, relocked, or unlocked.
Yes the ruu will wipe everything.
You will want to back up your sd.
Do the ruu.
Take the ota to kitkat.
Lock the bootloader.
Go s-on.
Click to expand...
Click to collapse
My phone is current S-Off and relocked, how can I change it to unlocked?
Thank you.
UPDATE: Nevermind, I got it here: http://forum.xda-developers.com/showthread.php?t=2470340
Hello,
my HTC 10 has CID 034. I kept S-ON, unlocked bootloader, installed TWRP, then LineageOS 14.1.
Then I wanted to revert back to stock. I tried several things, among them I think I downloaded file from this thread - RUU Zip (Stock Signed) - 1.90.401.5 and tried flashing with "fastboot oem rebootRUU" + "fastboot flash zip firmware.zip", but received errors and gave up. Now I think it was lower version (1.90.401.5) then I should have tried to flash (in download mode I saw 2.41.401.4).
Later I found official RUU.exe in this thread, flashing goes without problems, but when I reboot to bootloader, it still shows "System status: Modified".
Does anyone have any suggestions what I should do to return to status "Official" ?
Thank you in advance.
https://r.tapatalk.com/shareLink?ur...share_tid=3386456&share_fid=3793&share_type=t
[GUIDE] Safely set your bootloader back to "LOCKED" from "UNLOCKED" or "RELOCKED"
Read this. S-off should clear system status. RUU could never do that on HTC phones
Thank you for your reply.
So, you're saying I should turn the phone into S-OFF state and software status will be Official after I reflash with RUU? I'm sorry I'm new at this and it isn't very clear to me from the thread.
Thank you.
Can't seem to find any into on relocking the bootloader with S-on
other than HTC has disabled the oem lock in 7.0
So is there anyway I can downgrade to with a TWRP backup, flash a stock recovery file relock the bootloader and then run the latest RUU to update everything or do I need S-off to downgrade the bootloader to relock?
It's not for a warranty claim, I just want to use Android pay since it works with my bank now.
I'm assuming a ***RELOCKED*** flag would pass it's security check?
I don't have sunshine since I never went S-off.
Vonrottes said:
Can't seem to find any into on relocking the bootloader with S-on
other than HTC has disabled the oem lock in 7.0
So is there anyway I can downgrade to with a TWRP backup, flash a stock recovery file relock the bootloader and then run the latest RUU to update everything or do I need S-off to downgrade the bootloader to relock?
It's not for a warranty claim, I just want to use Android pay since it works with my bank now.
I'm assuming a ***RELOCKED*** flag would pass it's security check?
I don't have sunshine since I never went S-off.
Click to expand...
Click to collapse
You may want to look into flashing a custom kernel, like ElementalX. Hides the bootloader unlocked status from safetynet. You'd also need to have an untouched system partition as well for Android Pay to work.
You can simply relock the bootloader, no need to downgrade. But you will have to flash a RUU >= your current version. Done it several times, it works
The command world be "fastboot oem lock". Phone needs to be in download mode, obviously...
Relock flag passes safetynet, yes.
bopsch said:
You can simply relock the bootloader, no need to downgrade. But you will have to flash a RUU >= your current version. Done it several times, it works
The command world be "fastboot oem lock". Phone needs to be in download mode, obviously...
Relock flag passes safetynet, yes.
Click to expand...
Click to collapse
You sure?
I've tried it 3 times with a 2.41 RUU the command does what it should, but reboot still shows unlocked.
Vonrottes said:
You sure?
I've tried it 3 times with a 2.41 RUU the command does what it should, but reboot still shows unlocked.
Click to expand...
Click to collapse
Enable OEM unlocking option in developer options from settings. Then the command.
A breadcrumb for anybody on the same trail...
If your bootloader status is still "unlocked" even after flashing a stock RUU and passing a seemingly successful "fastboot oem lock", try removing your SD card and "fastboot oem lock" again. After a load of messing around this immediately allowed me to gain "Relocked".
I loved my HTC10 in it's heyday but I'm so over all these HTC quirks