Can someone give direction on Re locking my bootloader? - T-Mobile LG G5 Questions & Answers

So I have not really been on here since last spring when the g5 was rooted, and once more in the early winter, to do Prime's upgrade to the h83020a.
When I did that upgrade, the 20a, I was just trying to bring the device back to a semi stock state, with locked bootloader, and no root.
It took away root, but the bootloader is still unlocked.
If I just wanted to relock the bootloader, what would I have to do if I am on 20a, no root? In the past I would just dive into the dev section, but I do not have a urge to become an 'expert' on the device, if I am giving it back to Tmob this week.
Can anyone point me to the thread, that would help me with the process of relocking the bootloader, without pooching the phone?
Thanks in advance

Tmobilesucksass said:
So I have not really been on here since last spring when the g5 was rooted, and once more in the early winter, to do Prime's upgrade to the h83020a.
When I did that upgrade, the 20a, I was just trying to bring the device back to a semi stock state, with locked bootloader, and no root.
It took away root, but the bootloader is still unlocked.
If I just wanted to relock the bootloader, what would I have to do if I am on 20a, no root? In the past I would just dive into the dev section, but I do not have a urge to become an 'expert' on the device, if I am giving it back to Tmob this week.
Can anyone point me to the thread, that would help me with the process of relocking the bootloader, without pooching the phone?
Thanks in advance
Click to expand...
Click to collapse
If you're running stock, unrooted Ron and haven't made any system changes, all you need to do is use ADB to boot to Fastboot mode:
Code:
ADB reboot bootloader
Once in Fastboot mode type:
Code:
Fastboot OEM lock
Then you will have a locked bootloader again. Just make sure you're running 100% stock first, because if not and you relock the bootloader it could brick it.

jeffsga88 said:
If you're running stock, unrooted Ron and haven't made any system changes, all you need to do is use ADB to boot to Fastboot mode:
Code:
ADB reboot bootloader
Once in Fastboot mode type:
Code:
Fastboot OEM lock
Then you will have a locked bootloader again. Just make sure you're running 100% stock first, because if not and you relock the bootloader it could brick it.
Click to expand...
Click to collapse
Thanks, man. 'Prime said the same thing. I had TWRP before 20a, so just to be sure, I'm going to reflash with LGUP, and than do the adb as he suggested, also.

Related

Going back to stock

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

[Q] Relock, RUU, Start Over?

Hi everyone,
I feel kind of bad for asking such a generic question like this, and I assure you that I have read around and done my research, but before I do potentially dangerous, irreversible, things to my device, I just want to make sure that I will perform the necessary steps correctly.
Basically, I have owned my HOX since launch date, and it came with either 1.73 or 1.85 base. As such, I rooted and unlocked the bootloader as soon as the exploits were available, and have been comfortably flashing ROMs and kernels every since. However, I have been experiencing some issues with data connectivity and stuff, issues that remain with any ROM, kernel, or radio that I flash. The details aren't important...
Now, I want to basically "start over" with my HOX. As if it was a brand new, unmodified, fresh device. So basically, unroot, relock bootloader, RUU, etc... And then start all over, root, unlock bootloader, install recovery, etc.....
Basically, what exact steps do I need to take to accomplish the "starting over"? As in the methods to use, the RUU to use, etc... ?
An outline of the steps, basically. My biggest fear is restoring to the wrong thing and losing my old HBOOT.
Again, I know this question probably gets asked often, but please bear with me through this.
I ruu'd my wife a and it was about 3 weeks before att sent her the next update lol. As long as you don't accept it you'll be fine. I'm sure you'd prolly root as soon as its finished anyway..
But you got it right. No need to unroot, just fire up fastboot and enter "fastboot oem lock". (Without quotes)
Figure out which ruu you need, most likely 1.85. Make sure you have the right HTC drivers updated, and make sure HTC sync is working right. Download ruu, which is an executable application, and run it. It should factory restore your phone like the day you bought it.
As far as restoring to the "bad" hboot, it shouldn't let you complete an ruu that's for another firmware other than what you had on it when you got root... So you'll be safe. Good luck bro, come back and let us know how it went :thumbup:
Sent from my One X using Tapatalk 2
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone?
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me?
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally?
And also, once I relock my boot loader, should I immediately RUU?
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
?
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU?
And after I relock the bootloader, will the phone reboot out of fastboot or anything? Or should I go immediately from the relock phase to the RUU phase?
Thanks
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Yep.. Run it from anywhere, as long as your computer recognizes your device let us know how it goes
Sent from my One X using Tapatalk 2
Ok, thanks a lot.
I don't have a PC with me right now (mac user) but once I get the opportunity I will go through with this. Thanks again!
Im hoping this thread may help me to solve my problem (I'm a total noob too lol)
I rooted and flashed a Rom on my HTC One S, and I had the same issues as OP
Im with Fido, but I was told that both Fido and Rogers use the same RUU
Trying to go back to stock, I relocked the bootloader.
1. then I ran the RUU (found a tutorial online), but I got an error message (155: wrong RUU or file cant be larger or something like that)
2. then I tried an alternative method : extract 2 files from the RUU, move them to another folder and from there run a cmd; didnt work either
(By the way, in method number 1, I also had to flash a recovery file (stock recovery) during the bootloader unlock process)
Did I do it the right way?
Can some Senior member give me a detailed step by step method?
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
Yeah.
954wrecker said:
Why do you keep posting HTC ONE S questions in our HTC ONE X forum? What is wrong with using the correct forum?
Click to expand...
Click to collapse
I did ???
Hey what do you know :laugh:
I have tried to do this multiple times, but no matter how many times a run the 2.2 exploit, and flash the unlock code bootloader continues to say relocked? any ideas
Yes, you need to check your pm. You need to hard reset the device. Hold power until device reboots, capacitive keys will flash during the process. Then run the unlock and you're device will unlock. I spent a full day to figure this out... Lol
Sent from my HTC One XL using Tapatalk 2
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Behemyth said:
anyone happen to have a link on how to reset your phone back to factory defaults? i've had too many issues with roms, and my wifi, and as i use it for work, i cant have this happening.
I didn't back up the factory ROM before i started flashing, does that mean im pretty much screwed?
I have Hboot 1.14
Click to expand...
Click to collapse
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
ECEXCURSION said:
If you want to reset to stock just run the ruu like the poster above is trying to do.
Sent from my HTC One XL
Click to expand...
Click to collapse
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Behemyth said:
Nobody answered his question about if he needs to find a RUU specific to his device. I've been looking and can't find an RUU specific to 1.14, and I dont want to chance bricking my device.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
scroll down to the stock ruu section and look up the firmware 2.2 not the hboot 1.14
Well, I'm the OP, and I ended up figuring out what RUU to use, which was 1.73. Basically, I ran 'fastboot oem lock' , then ran the RUU right afterwards, then booted up and ran the root exploit, rooted, and then ran 'fastboot oem unlock' using my old Unlock.bin file that I had from the very first time I unlocked the bootloader. From there, I installed a custom recovery and was good to go.
Yah, if your using 2.20 firmware, run the below link, works like a charm. Must make sure you re-lock the bootloader before, or it will error out. Just hold down the power button until it turns off if this happens.
possible brick
Skeeterdrums said:
So basically relock the bootloader with "fastboot oem lock" , and then RUU, and I have a fresh new phone? You got it.
And for determining which RUU I need, either 1.73 or 1.85, if I try running the wrong one, it will stop me? Yes, it'll throw an error when you try to go through the RUU install process.
And since I'm still on the older HBOOT with the older initial base, root and unlock the same way I did originally? Yes. This is a fresh phone install after you run the RUU (like the day you bought it).
And also, once I relock my boot loader, should I immediately RUU? Yes. There's not a lot else you really need to do (especially on bricked phones, not a lot you CAN do).
So a full outline would be:
Connect phone to computer ( with drivers and all)
Boot into fast boot
Relock bootloader with command
RUU
Let phone boot
Re-root
Re-unlock bootloader
Install recovery
Flash ROMS!
? - Yes, that's pretty much it.
And just because it's been forever since I've done it, what are the steps again for RUUing? Do I need to boot the phone into any special mode? Or I just connect the phone to the PC and run the RUU? - Connect to pc in fastboot usb and run it from there.
And after I relock the bootloader, will the phone reboot out of fastboot or anything? - Nope, it'll stay in fastboot unless you reboot it.
Or should I go immediately from the relock phase to the RUU phase? - That makes things a little faster
Click to expand...
Click to collapse
I did this, but my phone never boots. It just stays at the bootloader after i run the RUU. Any ideas? :/
Also, i get the "this build is for development purposes only" message under the HTC logo before the phone enters the bootloader.
EDIT: managed to get the bootloadr unlocked again via HTCDev.com and flashed recovery and ROM. Guess Im not starting fresh after all lol

Stock rom that doenst loose my bootloader unlock?

Hey guys i was just wondering if there was any way to flash back to stock without loosing my bootloader unlock?
the only way to re-lock the bootloader is by using the fastboot command for it.
This is an interesting question.
I am currently on the latest 4.4.4 and now I would like to try CM 12.x (5.1.).
In case I do not like 5.1, how do I get back to stock without losing the unlocked bootloader?
flashing back to stock will not relock your bootloader. the only way is by fastboot command. so if you an unlocked bootloader there is no need to worry about losing that. you will however lose root which is easy to get back.

bootloader relock

hello guys, im new here.
anybody tried relocking their bootloader by using this command?
fastboot oem lock
and does it work and restores warranty conditions?
That command has been tried since the original Moto G and no, contrary to what some people think you can't reset the internal unlock counter. They will always know you unlocked it. If nothing else, they know because you got the unlock code from them. I'm not sure why people overlook this clearly posted sentence when they request the unlock code from Motorola.
"Unless you have a Developer Edition device, once you get the unlock code, your device is no longer covered by the Motorola warranty; in other words, please don't blame us if things go wrong, even if they appear unrelated to unlocking the bootloader."
Sent from my SM-T530NU using Tapatalk
creative21 said:
hello guys, im new here.
anybody tried relocking their bootloader by using this command?
fastboot oem lock
and does it work and restores warranty conditions?
Click to expand...
Click to collapse
That command will lock your bootloader again. However, locking and unlocking will wipe your device.
Upon receiving your unlock code from Motorola, your warranty is void; regardless if you unlock it or not. The sheer act of asking for and receiving the code voids your warranty.
Of course, if there is a true hardware issue that is not caused by software tinkering, you can still use that piece of the warranty.
Sent from my MotoG3 using Tapatalk
nikon120 said:
That command will lock your bootloader again. However, locking and unlocking will wipe your device.
Upon receiving your unlock code from Motorola, your warranty is void; regardless if you unlock it or not. The sheer act of asking for and receiving the code voids your warranty.
Of course, if there is a true hardware issue that is not caused by software tinkering, you can still use that piece of the warranty.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
after relocking, warning bootlogo is removed or can be replaced?
creative21 said:
after relocking, warning bootlogo is removed or can be replaced?
Click to expand...
Click to collapse
I think I can be replaced !, I'm not sure!
I will test and send feedback!
Jeconias Santos said:
I think I can be replaced !, I'm not sure!
I will test and send feedback!
Click to expand...
Click to collapse
but I think after reflashing stock, boot logo will be return to normal.
I tried that command and relock the bootloader several times as i didnt got the same battery backup as stock... So my question is after relocking and flahing stock rom... Do i get the OTA? and will it get flashed sucessfully?
sagar27691 said:
I tried that command and relock the bootloader several times as i didnt got the same battery backup as stock... So my question is after relocking and flahing stock rom... Do i get the OTA? and will it get flashed sucessfully?
Click to expand...
Click to collapse
Yes you will be able to get over the air updates after relocking bootloader if necessary system apps and files are not modified.
If you are not able to get ota you could also flash stick firmware images.
Thanks man... I flashed the whole stock rom from xda here only...
Even though I've run the commands to re-lock, going into the fastboot (bootloader) mode shows it's unlocked.
Anyone figure out a way to actually re-lock it?
JWhipple said:
Even though I've run the commands to re-lock, going into the fastboot (bootloader) mode shows it's unlocked.
Anyone figure out a way to actually re-lock it?
Click to expand...
Click to collapse
No, once it's unlocked, the counter will always show an unlocked bootloader. Best you can do is hide the opening unlocked bootloader screen.
In the 1st Moto G i have sucessfully relocked the bootloader.
You can use the command 'fastboot oem lock begin', then flash all files from fastboot firmware changing the logo file to logo-mod.bin (File that have removed the unlocked warning image, because flashing custom logo.bin doesn't check crc or hash when relocking the bootloader), then finish with 'fastboot oem lock' command.
Example:
fastboot oem lock begin
fastboot flash partition gpt.bin
- - - rest of commands
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
I don't have tested because i don't have unlocked my g3 bootloader yet.
Just try
jmadotme said:
In the 1st Moto G i have sucessfully relocked the bootloader.
You can use the command 'fastboot oem lock begin', then flash all files from fastboot firmware changing the logo file to logo-mod.bin (File that have removed the unlocked warning image, because flashing custom logo.bin doesn't check crc or hash when relocking the bootloader), then finish with 'fastboot oem lock' command.
Example:
fastboot oem lock begin
fastboot flash partition gpt.bin
- - - rest of commands
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
I don't have tested because i don't have unlocked my g3 bootloader yet.
Just try
Click to expand...
Click to collapse
Been there, done that, got the T-Shirt, doesn't stop the banner from saying the bootloader is unlocked.
JWhipple said:
Been there, done that, got the T-Shirt, doesn't stop the banner from saying the bootloader is unlocked.
Click to expand...
Click to collapse
Have you flashed moded logo.bin?
I still don't understand the point of all this... why are people trying to go through all the work of relocking the bootloader?!?! There is ZERO benefit to it... your warranty is still void (you don't even have to unlock, just agree to the terms and get the unlock token), it doesn't enhance resale value, it doesn't change the performance, so why all the effort to try to do it?!?!
acejavelin said:
I still don't understand the point of all this... why are people trying to go through all the work of relocking the bootloader?!?! There is ZERO benefit to it... your warranty is still void (you don't even have to unlock, just agree to the terms and get the unlock token), it doesn't enhance resale value, it doesn't change the performance, so why all the effort to try to do it?!?!
Click to expand...
Click to collapse
to get the new official OTA... if bootloader is locked and have stock rom we are able to get the OTA and can flash successfully with it... though it shows bootloader unlocked warning.
sagar27691 said:
to get the new official OTA... if bootloader is locked and have stock rom we are able to get the OTA and can flash successfully with it... though it shows bootloader unlocked warning.[emoji14]
Click to expand...
Click to collapse
Hmm... Are you sure? If you are unlocked but otherwise pure stock, you should still get OTAs, if your not then they are most likely blocked server-side not client-side. In other words just accepting the T&C of a Motorola bootloader unlock could not only void your warranty, but also blacklist your IMEI from OTAs as well.
I could be wrong, but I think your "barking up the wrong tree" here... I can tell you for sure that Huawei does it this way since Lollipop, if you unlock the bootloader your IMEI is blacklisted server-side... They are very straightforward about it.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Hmm... Are you sure? If you are unlocked but otherwise pure stock, you should still get OTAs, if your not then they are most likely blocked server-side not client-side. In other words just accepting the T&C of a Motorola bootloader unlock could not only void your warranty, but also blacklist your IMEI from OTAs as well.
I could be wrong, but I think your "barking up the wrong tree" here... I can tell you for sure that Huawei does it this way since Lollipop, if you unlock the bootloader your IMEI is blacklisted server-side... They are very straightforward about it.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
not at all... already flashed official firmware 3 times after experiencing the less battery backup on custom roms. in this 3 times i flashed the modified bootlogo so didnt got the warning of bootloader unstlocked and not able to get the OTA but then again i flashed the official firmware 4th time and without that modified bootlogo in hope to get the latest OTA build no. LPI23.72-65 and it worked i got that update next day... and still its show bootloader unlocked warning... so that warnling doesn't affect the OTA is you have everything stock with locked bootloder.
Can anyone post a modified logo without the unlocked warning? My bootlock is relocked but i wanna get rid of this message. Thanks!
Just to clear up any confusion. There is no need to relock the bootloader. In fact it seems like a waste of time to me...
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91999/p/1449,8620
After I unlock my device bootloader, am I still eligible to receive software upgrades from Motorola?
Unlocking your bootloader does not affect your eligibility to receive over-the-air (OTA) upgrades from Motorola. Upgrade packages to new versions of Android will be pushed to all eligible devices, regardless of their bootloader locking status.
Click to expand...
Click to collapse

Few questions about relocking bootloader

I am considering relocking the bootloader for my HTC U12+. I unlocked it a long time ago (out of habit I guess). So my phone is completely running stock without any modifications. I want to relock the phone to get widewine back to L1, so I'll get Netflix updates and such.
A few questions about relocking that I couldn't find an answer to.
1. When I relock the bootloader will it do a factory reset to the phone? I'm asking because unlocking did.
2. If later on I decide to unlock the relocked bootloader again, do I have to get another unlock-code from HTC? Or is unlocking a relocked bootloader a simpler procedure?
So I decided to do the relocking. During the relocking procedure I was being told on the screen that the phone will be wiped if I continue. It remains to be seen how I'll unlock it later on if I want to.
lvl3 said:
I am considering relocking the bootloader for my HTC U12+. I unlocked it a long time ago (out of habit I guess). So my phone is completely running stock without any modifications. I want to relock the phone to get widewine back to L1, so I'll get Netflix updates and such.
A few questions about relocking that I couldn't find an answer to.
1. When I relock the bootloader will it do a factory reset to the phone? I'm asking because unlocking did.
2. If later on I decide to unlock the relocked bootloader again, do I have to get another unlock-code from HTC? Or is unlocking a relocked bootloader a simpler procedure?
Click to expand...
Click to collapse
2. You have to to go through the HTCDev website procedure (not sure if you can reuse the previous Unlock_code.bin file).
is it possible to get "locked bootloader" instead of "relocked bootloader" and get rid of system status modified?
maslaq said:
is it possible to get "locked bootloader" instead of "relocked bootloader" and get rid of system status modified?
Click to expand...
Click to collapse
No.

Categories

Resources