I've been considering unlocking the bootloader and know that it then displays the unlocked notification on the boot screen. If you need to take it back for some reason and relock the bootloader does the unlocked message still stay on the boot screen or does it go away as well?
Thanks
edozier said:
I've been considering unlocking the bootloader and know that it then displays the unlocked notification on the boot screen. If you need to take it back for some reason and relock the bootloader does the unlocked message still stay on the boot screen or does it go away as well?
Thanks
Click to expand...
Click to collapse
If you relock then the message will go away
Sent from my MB855 using xda premium
ianford10 said:
If you relock then the message will go away
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Sweet. Guess that means you really can go back to full stock. Relock bootloader then reflash stock sbf.
edozier said:
Sweet. Guess that means you really can go back to full stock. Relock bootloader then reflash stock sbf.
Click to expand...
Click to collapse
Indeed you can
Sent from my MB855 using xda premium
Related
My phone has had an issue of randomly shutting off for awhile now.
Even with every type of version and before I unlocked it.
It's currently on 2.3.4 Unlocked with the pudding ota.
What should I do? Is it necessary to remove all signs of unlocked when I send the phone back to Motorola after they will likely already send me a new phone to replace it?
If possible, I would recommend locking it back up and "unrooting" (if you are currently rooted)...
Sent from my GT-I9000 using XDA Premium App
I think its impossible to relock 'once unlocked always unlocked'
Sent from my MB860 using XDA App
Relocking Atrix
Javi97100 said:
I think its impossible to relock 'once unlocked always unlocked'
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I actually had to reset my phone and I returned it completely back to stock. The bootloader can be locked again. I completely unrooted and wiped my phone clean. Just flash back to the stock rom and factory data wipe. The unlocked message will go away and so will root.
14themoney24theshow said:
I actually had to reset my phone and I returned it completely back to stock. The bootloader can be locked again. I completely unrooted and wiped my phone clean. Just flash back to the stock rom and factory data wipe. The unlocked message will go away and so will root.
Click to expand...
Click to collapse
Wow that's interested, I didn't know that, thanks man
Sent from my MB860 using XDA App
We are attempting to unlock the bootloader of a device on factory stock 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US and need some help..
The sbf in this link is dead [UNLOCKED BOOTLOADER] released!!! 8/14/11{WILL KILL 4G}
Tried this guide: how to have unlocked fastboot without flashing. File flashes ok but "unlocked" does not display on top of the screen. Also attemped "fastboot oem unlock" but get error "infooem unlock is not implemented"
Any input on how to successfully get this device's bootloader unlocked would be very much appreciated!
Update.. Bootloader unlocked using pudding thread.. Thanks myself!!
Hey buddy... how did you unlocked boot loader.....
I got the same error....as u got....
Sent from my MB855 using xda app-developers app
We would all like to know how you pulled it off. Are you on ota 2.35? And if so, what steps did you take?
Sent from my Magical mopho using xda premium
JohnH4 said:
We would all like to know how you pulled it off. Are you on ota 2.35? And if so, what steps did you take?
Sent from my Magical mopho using xda premium
Click to expand...
Click to collapse
He's not on 2.3.5 ota. Sounds like he's on .4 or shipped .5.
Howeverrr, read motorolas latest post on unlocking the boot loader for photons....think you may find something rather interesting, I'm too lazy to go hunt down a link for you.
Sent from my Motorola Electrify using Tapatalk 2
We are flashing back to stock 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US and using this thread to unlock the bootloader.
After step 1 in the thread we usually get an error in RSD but we disregard it as instructed, finish the steps and it's successful every time.
I am just wondering if any one else has seen this I just busted out my old rezoned and went to flash the official ruu and my hboot says tampered Ive never unlocked or rooted this phone is the ***tampered*** from using the leaked ics img
tampered means that it was unlocked then relocked, i think.
I thought it was from flashing a custom recovery, either way not a big deal .
Sent from my ADR6425LVW using Tapatalk 2
Actually neither. When you flashed the leaked ICS RUU it changes your bootloader label to "tampered." You can get rid of it by s-offing.
Sent from my ADR6425LVW using xda app-developers app
Tampered means there is a custom recovery. For unlocked it displays locked unlocked or relocked.
Sent from my DROID RAZR using Tapatalk 2
mjh68 said:
I thought it was from flashing a custom recovery, either way not a big deal .
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Correct you get tampered when you flash a custom recovery, running a full ruu should remove it.. cuz it replaces the custom with stock recovery
Sent from my ADR6425LVW using xda app-developers app
+1 for it being due to a custom recovery. Relocking it and running an RUU will get rid of it, although it'll still say "relocked" instead of "locked"
scy1192 said:
+1 for it being due to a custom recovery. Relocking it and running an RUU will get rid of it, although it'll still say "relocked" instead of "locked"
Click to expand...
Click to collapse
But you can s-off and install a hex-edited HBOOT to one that says locked even if it's relocked.
Doesn't it also say "unlocked" underneath "tampered"? I don't think you can install a custom recovery without having unlocked the phone.
Or did you temp root?
OK so I used the bootloader to flash the 3 option in Haus's thread and every thing is working. But....
Now on the bootloader screen it says locked tampered then S-off.
I was told the locked was just wat it was saying and didn't matter.
So do I have a locked boot loader? And does that even matter for anything or was it just required to get root plus S-off?
Did I mess up getting the newest hboot from the firmware? I was told I needed it to run meanbean.
Sent from my EVO using xda app-developers app
I'm not sure what u flashed but it sounds like you flashed the whole thing which means you have stock recovery now. Either fastboot flash recovery image or download thru goo manager.
Once you have a custom recovery installed your all set. Don't worry about the locked on your bootloader
Sent from my EVO using xda premium
mainstang said:
OK so I used the bootloader to flash the 3 option in Haus's thread and every thing is working. But....
Now on the bootloader screen it says locked tampered then S-off.
I was told the locked was just wat it was saying and didn't matter.
So do I have a locked boot loader? And does that even matter for anything or was it just required to get root plus S-off?
Did I mess up getting the newest hboot from the firmware? I was told I needed it to run meanbean.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You should have flashed the first file the one with no kernel,hboot, or stock recovery that would have updated everything you needed to be updated
So did I mess anything up? I was able to flash mean bean without any issues.
Sent from my EVO using xda app-developers app
mainstang said:
So did I mess anything up? I was able to flash mean bean without any issues.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
No you just did the same as taking the OTA as far as I can tell. As long as everything is working you should be fine
I had a unlocked bootloader, rooted rezound running AOKP JB rom. Now after trying to flash a differnet kernel (stupid me) I can't get past the bootloader screen. I was able to relock my bootloader but now on Hboot screen it says ***tampered*** *****relocked**** and ****security warning**** I am completely stuck. Am I SOL or is there a chance to fix this? Any help would be greatly appreciated.
bluerez79 said:
I had a unlocked bootloader, rooted rezound running AOKP JB rom. Now after trying to flash a differnet kernel (stupid me) I can't get past the bootloader screen. I was able to relock my bootloader but now on Hboot screen it says ***tampered*** *****relocked**** and ****security warning**** I am completely stuck. Am I SOL or is there a chance to fix this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Get back into fastboot. Unlocked your phone. You can just go back and flash the boot.img that was on your original rom
Flyhalf205 said:
Get back into fastboot. Unlocked your phone. You can just go back and flash the boot.img that was on your original rom
Click to expand...
Click to collapse
I tried. I went through the htc.dev and it all went ok until i tried to submit it. It said "unlocking bootloader failed"
bluerez79 said:
I tried. I went through the htc.dev and it all went ok until i tried to submit it. It said "unlocking bootloader failed"
Click to expand...
Click to collapse
You s-on or s-off?
Might as well install the RUU again...
Flyhalf205 said:
You s-on or s-off?
Might as well install the RUU again...
Click to expand...
Click to collapse
S-on
Can I flash with a locked bootloader?
Sent from my Galaxy Nexus using xda app-developers app
bluerez79 said:
Can I flash with a locked bootloader?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You won't be able to flash a rom or kernel if your s-on and locked. The only thing you can do is try and unlock bootloader or run RUU and restart from scratch
I can't unlock boot loader. Went thru the process and it said the token was too long. So I guess I'll look for the RUU and give it a go.
Sent from my Galaxy Nexus using xda app-developers app
bluerez79 said:
I can't unlock boot loader. Went thru the process and it said the token was too long. So I guess I'll look for the RUU and give it a go.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
At what point did it say that? When you are trying to get it from the HTC site? If that's it you are just copying too much. Make sure you don't copy any extra characters at all.
If it's when you are flashing the unlock token bin file then I agree that you should just run the RUU and get back to fresh stock then try again.
Use the RUU that is the .12 version rather than the global leak, unless you have already run the global leak one, if you want to be able to take the newest OTA.
I tries to flash ruu from my pc. The command prompt said “access denied"
Sent from my Galaxy Nexus using xda app-developers app
And your bootloader is locked? You talked about getting the unlock token, did you unlock it again before RUUing?
It needs to be locked to run the RUU.
bluerez79 said:
I tries to flash ruu from my pc. The command prompt said “access denied"
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
How are you flashing it?
Fastboot flash and then the name of the ruu
Sent from my Galaxy Nexus using xda app-developers app
It was locked when I tried to flash ruu
Sent from my Galaxy Nexus using xda app-developers app
Try this:
fastboot oem rebootRUU
fastboot flash zip {nameofruu}.zip
Or place it on your sd card and flash it in hboot
If it's an exe file you need to double click on that on your pc while the phone is connected.