I recently got a new motherboard installed to my Nexus 5X by LG due to the recent bootloop related to TWRP and Android N. My problem is that after unlocking bootloader, and doing the mandatory device wipe that comes with it, the bootloader gets reverted to locked state when I restart my device. I've tried multiple cables, USB ports, fastboot binaries, but nothing seems to make the device behave any differently. I am able to flash things in fastboot mode after unlocking the device as long as I don't restart the device. TWRP installs just fine, but obviously throws a bunch of errors because I cannot enter recovery mode without restaring (which gets the bootloader locked again). Is there any tricks I could try, or is it my NAND that is acting up as it seems to revert to previous state on power loss? As far as I can tell, the rest of the memory chip is working just fine, /sdcard does not lose any data when restarting etc. I was able to install Nougat on the device by flashing factory images.
I have not bought my device from Google and thus it is covered only by LG's limited warranty, which probably means that this is something they will not repair as unlocking the bootloader probably voids their warranty in any case. Am I just out of luck?
neree said:
I recently got a new motherboard installed to my Nexus 5X by LG due to the recent bootloop related to TWRP and Android N. My problem is that after unlocking bootloader, and doing the mandatory device wipe that comes with it, the bootloader gets reverted to locked state when I restart my device. I've tried multiple cables, USB ports, fastboot binaries, but nothing seems to make the device behave any differently. I am able to flash things in fastboot mode after unlocking the device as long as I don't restart the device. TWRP installs just fine, but obviously throws a bunch of errors because I cannot enter recovery mode without restaring (which gets the bootloader locked again). Is there any tricks I could try, or is it my NAND that is acting up as it seems to revert to previous state on power loss? As far as I can tell, the rest of the memory chip is working just fine, /sdcard does not lose any data when restarting etc. I was able to install Nougat on the device by flashing factory images.
I have not bought my device from Google and thus it is covered only by LG's limited warranty, which probably means that this is something they will not repair as unlocking the bootloader probably voids their warranty in any case. Am I just out of luck?
Click to expand...
Click to collapse
What TWRP errors are you getting? TWRP shouldn't care if your device is locked or not. It doesn't do its operations through the bootloader.
Also just as a sanity check, you enabled OEM unlocking under developer options and you did fastboot oem unlock (or equivalent) on the phone right?
sfhub said:
What TWRP errors are you getting? TWRP shouldn't care if your device is locked or not. It doesn't do its operations through the bootloader.
Also just as a sanity check, you enabled OEM unlocking under developer options and you did fastboot oem unlock (or equivalent) on the phone right?
Click to expand...
Click to collapse
For the TWRP errors I'll have to get back on when I get back home to my device. For the other part, yes I did enable the unlocking under dev options, and used fastboot flashing unlock (also tried fastboot oem unlock). They both do go through and wipe my device. The bootloader also stats that current state is unlocked after the wipe. However after restaring the device back to bootloader causes the state change back to locked.
Did you install the motherboard or did LG?
I think something didn't install correctly on your phone. There is probably somewhere on the phone where they store the persistent unlocked state of the bootloader and that isn't working.
If you are bold, you can try using LGUP and the TOT file to reinstall you phone (this is a more in-depth reinstall than just factory images)
However there is always the risk you make things worse on your phone than they currently are.
If you have 16GB then you need to install the Android N OTA afterwards to get the partition tables set correctly.
sfhub said:
Did you install the motherboard or did LG?
I think something didn't install correctly on your phone. There is probably somewhere on the phone where they store the persistent unlocked state of the bootloader and that isn't working.
If you are bold, you can try using LGUP and the TOT file to reinstall you phone (this is a more in-depth reinstall than just factory images)
However there is always the risk you make things worse on your phone than they currently are.
If you have 16GB then you need to install the Android N OTA afterwards to get the partition tables set correctly.
Click to expand...
Click to collapse
LG (or whatever company it is that does it for them here) installed the new board. I think I'll pass on doing the deeper installations for now as I'm currently trying to sell the device off to someone who wouldn't have any use to unlocked bootloader. Was just wondering if I completely missed something that might cause the device to do this so I could either use it again by myself or sell it as fully functioning Nexus device.
neree said:
I think I'll pass on doing the deeper installations for now as I'm currently trying to sell the device off to someone who wouldn't have any use to unlocked bootloader.
Click to expand...
Click to collapse
That's a good call. Actually I wouldn't mess around too much with the phone if you are going to sell it.
Just make sure you remove any pin/pattern/password from the phone and to be extra safe, remove your google account from the phone *PRIOR* to factory reset or you will run into Factory Reset Protection (FRP) where you will have to give the buyer your google account and password so they can do first install and switch to their own account.
Related
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
railpressureflip said:
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
Click to expand...
Click to collapse
you might be able to fastboot boot path/to/recovey.img like when you were flashing twrp but im not sure if that works on locked devices try it with a factory image with the recovery extracted and if that works you can sideload the full ota in recovery.
and possibly lgs flashtool can rewrite the phone with it locked but idk if there are imgs out there or if it works with pixel 2 xl
for next time never lock your phone on a custom rom really never relock once unlocked there is no need to and it only takes away your recovery options
railpressureflip said:
So long story short, my rom (nitrogenOS, great rom BTW) got corrupt (or so I thought) and I had to wipe all data to re-install it clean.
But now I'm in a position where my phone has no rom, no recovery (neither TWRP nor stock) and both my bootloader and bootloader critical are locked (Last time I had to lock and unlock them to prevent bootloop before flashing stock OS, I don't know why)
Now I can't boot into twrp or absolutely anything, and cannot unlock the bootloader either because it says "Flashing unlock is not allowed".
Is my device 100% unrecoverable?
Going to have to go back to JBHifi (Australia) and have them send it to google
Any thing I can still do to recover the device?!
Click to expand...
Click to collapse
How the heck did your bootloader get locked if you didn't do it yourself?? Do you get your phone ID displayed when you type in "fastboot devices" in bootloader mode???
You probably ended up switching slots when you reflashed. You need to use Deuces flashing script. Say yes to unlocking.
Try downloading and installing skipsoft tools. It might not see your device but try. If it doesn't see it, manually select your device. Have it install USB drivers. Restart skipsoft and see if it sees your device then. I got into a situation once where in fastboot it showed something like a corrupt bootloader and my computer could not see my device. After messing with the phone with skipsoft running, skipsoft could see it when my computer couldn't.
Let's tell my experience.
I had my Moto G6 Play for near two months. I've unlocked the Bootloader and attempted to root it but unsuccessful. So, I've rolled back to my stock rom via Fastboot (using the stock ROM linked in this forum). It worked fine after that.
Some days ago, the official Android Pie update has been available, so, I installed it via OTA. However, it failed. After trying installing again, the phone gone down and never powered on again (even entering the Recovery mode, even charging all the night).
Therefore, I left the device to the technical service, knowing the bootloader unlock voids the warranty.
Does this happened to someone else? In what scenarios?
Thanks for commenting.
Amitie10g said:
Let's tell my experience.
I had my Moto G6 Play for near two months. I've unlocked the Bootloader and attempted to root it but unsuccessful. So, I've rolled back to my stock rom via Fastboot (using the stock ROM linked in this forum). It worked fine after that.
Some days ago, the official Android Pie update has been available, so, I installed it via OTA. However, it failed. After trying installing again, the phone gone down and never powered on again (even entering the Recovery mode, even charging all the night).
Therefore, I left the device to the technical service, knowing the bootloader unlock voids the warranty.
Does this happened to someone else? In what scenarios?
Thanks for commenting.
Click to expand...
Click to collapse
1. Unlocking your bootloader does not void your warranty.
2. That's a recovery loop. It doesn't look like it, but it is.
3. How to fix that crap. -Flash stock firmware, wipe data, cache, and DDR through fastboot, then issue the command fastboot reboot. Let it encrypt, then you can boot into recovery normally. If you don't let it encrypt right after flashing stock firmware then you'll loop again.
Spaceminer said:
1. Unlocking your bootloader does not void your warranty.
2. That's a recovery loop. It doesn't look like it, but it is.
3. How to fix that crap. -Flash stock firmware, wipe data, cache, and DDR through fastboot, then issue the command fastboot reboot. Let it encrypt, then you can boot into recovery normally. If you don't let it encrypt right after flashing stock firmware then you'll loop again.
Click to expand...
Click to collapse
1.- Maybe, depending the country. So, the agent who attended me told me the warranty is void just when unlocking the Bootloader. Motorola's technical service will give the last word about that, as I have re-installed the stock rom.
2.- As I told, the phone don't seems to power on and no charging light. I've connected to the computer and it never identifies as anything than a brick.
3.- Per above, Fastboot won't recognize the device and unable to send commands to the device in any way. In other words, the device seems to be completely dead.
The vendor where I purchased the device just told me they will replace the device under the warranty.
So, I'll apply the updates via OTA and tell you the results, but I'll not unlock the bootloader, but backup upload the ROM via Fastboot and TWRP, and upload it.
I've finally gone to the vendor to retire the replacement device.
However, they don't have the Moto G6 Play available anymore. Instead, they gave me the Moto G6 (better device except for the battery) for free, as the failure has been covered under the warranty.
Advices:
Ask your vendor the repair costs for failures caused by failed firmware updates. I assume Motorola didn't checked even if the bootloader is unlocked (as the device seems to be completely dead), they just decided to replace the device.
Don't send the device to the technical service if it powers on and Fastboot is working unless you're prepared to pay the repairs.
Don't try to install the Android Pie update with the bootloader unlocked and firmware altered.
acutally, updating with unlocked bootloader causes nothing. that might have been a hardware problem of some source, idk...
---------- Post added at 09:45 PM ---------- Previous post was at 09:44 PM ----------
but unlocking the bootloader does void your warranty tho
Indeed the warranty is void after unlocking the bootloader, but Motorola haven't noticed (and even checked it) as the device completely died.
¿So, where is actually stored the Bootloader? In the Flash or a separated ROM chip. As a previous flashing attempt may caused failed write to key partitions.
Amitie10g said:
Indeed the warranty is void after unlocking the bootloader, but Motorola haven't noticed (and even checked it) as the device completely died.
¿So, where is actually stored the Bootloader? In the Flash or a separated ROM chip. As a previous flashing attempt may caused failed write to key partitions.
Click to expand...
Click to collapse
Not true. My bootloader is unlocked, and Motorola is well aware of that since I had to ask them for the key. Unlocking it by itself doesn't void it. It's what you do afterwards that might void it. Like running an over volted kernel and frying something. Check the screen shot. My warranty is still good until Aug of this year. And if I really wanted to I could just relock the bootloader before sending it in, which blows that theory out of the water.
i replaced one under warranty with no issue. with an unlocked boot loader. twice.
Hi,
I have recently bought a T-mobile version of OP7T. Even though T-Mobile unlocked the network permanently, I still didn't like T-mobile branding at the start, plus I wanted Stock OxygenOs. So what did I do?
(No root and No TWRP)
1. I've Unlocked the bootloader via the method in this post. Stage-1
2. I have flashed the stock rom which I downloaded from this post. Stage-2
3. Phone loads up perfectly fine and now I have stock OOS. to make sure everything is fine, I also did a factory reset and re-flashed the stock rom to make sure there's no track of previous roms.
4. I then wanted to relock the bootloader in order to keep my device safe and enjoy having a normal device like any others without the ugly message at the startup.
5. So I put it in fastboot mode and executed "fastboot flashing lock" or "fastboot oem lock" and it gave me the options and I locked the bootloader.
6. after this, I can't do anything else. it keeps showing me the page where it says Your device is corrupt. It can't be trusted and will not boot and in order to get rid of I need to keep unlocking the devices relfashing everything and the rest of the story.
I've read all the accurate and inaccurate infos on forums where another guy claims when he did turn everything to stock (recovery + rom + factory reset) things go back to normal and he's done. in my case it doesn't work.
Please help me, how I can be able to relock the bootloader without running into Your device is corrupt. It can't be trusted and will not boot.
Thanks.
First I think no help is stupid, since that is the regular way of doing it. Second you should have read extensively before doing what you did. T-mobile is very specific device. What he probably didn't mention is that you need the original rom t-mobile branded, since you need original software to be able to relock bootloader. I would recommend use msm- tool to recover you device. Read carefully and next time just be sure that what you are doing is informed.
I have unlocked the device and installed everything. the phone works like a charm.
My only problem is that I can't re-lock the bootloader.
bahadorkh said:
I have unlocked the device and installed everything. the phone works like a charm.
My only problem is that I can't re-lock the bootloader.
Click to expand...
Click to collapse
That was my point in order to relock your device you must have the original firmware that the phone came with if it's t-mobile. Installed in both slots. Then you can relock you device.
Please try this thread
[OP7T T-MOBILE][OOS 11.0.1.5 HD63CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
After the first boot you must update via OTA, then after the 7T reboots you can go back into the bootloader and relock it. I'm typing this message out on my T-Mobile 7T running the Global OOS 11 version. _ANY_ modification to the system whatsoever will cause the "Device is Corrupt" error, due to a mismatch of the keys used by OnePlus to sign the firmware. I've attached a screenshot of my "About phone" section as proof of the conversion, however, I can't show proof of my bootloader's state because I don't have access to a PC at the moment and *#*#7378423#*#* didn't work, neither did *#*#7378423*#*#. If I remember to the next time I'm near a PC I'll add proof of that too.
For further reading see::
1.) https://source.android.com/security/verifiedboot/boot-flow#locked-devices-with-custom-key-set
And
2.) https://source.android.com/security/verifiedboot/dm-verity
P.s. I do realize that I'm almost a year late to this discussion, but I thought knowing would/could still be useful to someone.
Hi there,
I'm interested in installing Lineage 18.1 on several flo Nexus 7s for my family, but I would like to lock the bootloader afterwards on each one. The reason I want to do this is because this device seems to erase all userdata if an unlock is issued, and I want to take advantage of that security feature. I successfully relocked the bootloader on the stock version of Marshmallow (6.0.1 I believe) after unlocking and installing SuperSU a long time ago by unlocking, 'fastboot boot'ing TWRP, installing SuperSU, and relocking. Presumably this worked because only the system partition was modified, and a check isn't done on the whole partition.
Now I'd like to upgrade to Lineage 18.1, but as this is more drastic, and involves repartitioning the flash, I searched around first about the risks but couldn't find a definitive answer for these devices. I've read about a lot of bricked phones of other brands when people have tried to relock the bootloader after installing custom ROMs. I'm not sure if that applies to this device. I'd prefer userdata was cleared rather than encrypting the whole device, as it is somewhat old, and I'd like to prevent 'fastboot boot'ing into a custom recovery without unlocking, as that might allow tampering of the other partitions, even if userdata was encrypted.
If this doesn't work and device is softbricked, but is recoverable, then it's not so much of a problem, but I'd prefer not to create a doorstop if someone else has tried it or knows if it's safe.
So, is it possible to safely issue the fastboot oem lock or fastboot flashing lock command after repartitioning, flashing Lineage, installing MindTheGapps and Magisk? And will the firmware still know how to properly erase userdata after reparitioning and flashing if it has moved? And if all else fails, is there a way of recovering from this type of brick?
Edit: Clarity.
The bootloader lock it is not an effective security feature...
SAFE UNLOCK
Unlock your device without data loss
Click to expand...
Click to collapse
Thanks for the reply!
Yup, I've heard that's the case.
However, I was under the impression that you had to unlock the bootloader in order to boot an alternative recovery. Since the bootloader forces the userdata to be cleared if you unlock, and the default recovery can't install anything, I thought that you may not be able to access the device without clearing userdata. I could also zero the recovery partition entirely, since Fastboot would allow me to boot recovery via USB if it the bootloader was unlocked. Basically I wanted to prevent easy access to userdata and encourage factory resetting the device if it got lost.
I am aware that even after a factory reset, it doesn't seem to properly erase the userdata (it seems like it is just a filesystem rebuild), so that's hardly great security since the eMMC could be read. Plus I wouldn't be surprised if some of the Qualcomm/factory tools allow you to get to the filesystem before the bootloader, however, again, I thought that the bootloader had to be zeroed for that to work, and the Qualcomm tools only allowed access if the onboard bootloader failed. Maybe I am wrong about that.
Do you have any other thoughts? For now I've left the devices unlocked as I don't want to risk bricking them. That was the main concern. I wanted to get rid of the unlocked padlock blatantly advertising the unlocked status before the bootloader was accessible, and if the device(s) were stolen then it is likely someone would just take the easy route and trash the data.
Qualcomm tool flashes a temporary, permissive bootloader, then RAM-booted TWRP patches a 'lock' byte and no user data is lost in the process. Just encrypt it.
Week ago I flashed the android 14 dev, don't liked it and yesterday flashed A13 (TQ1A.230205.002) with Android Flash Tool. Today I saw that I can't add my credit card to the Google Pay. I checked in settings and found out that my bootloader unlocked but the button is unavailable.
What can I do?
If your phone was rooted, then do a factory reset. Download and install the Google Platform tools, or if adb and fastboot drivers are installed system-wide, that's fine.
Connect phone to PC in fastboot mode
Enter the first command "fastboot devices"
Then type, "fastboot flashing unlock"
Confirm on your device to lock the bootloader
That's it. If you want a detailed guide, here are the instructions on how to unlock/relock the bootloader on a Pixel phone.
wrkadung said:
If your phone was rooted, then do a factory reset. Download and install the Google Platform tools, or if adb and fastboot drivers are installed system-wide, that's fine.
Connect phone to PC in fastboot mode
Enter the first command "fastboot devices"
Then type, "fastboot flashing unlock"
Confirm on your device to lock the bootloader
That's it. If you want a detailed guide, here are the instructions on how to unlock/relock the bootloader on a Pixel phone.
Click to expand...
Click to collapse
Locking with adb will erase all my data?
max_134 said:
Locking with adb will erase all my data?
Click to expand...
Click to collapse
Yes, of course! Unlocking and relocking will erase and factory reset your phone, I use Google One to take backups.
Alternatively, you can also use the Android flash tool, and it will automatically do it for you. You just have to follow the on-screen instructions, and it will ask for your confirmation to lock the bootloader, and you also get the option to wipe data (never tried unchecking the wipe data option).
Here is the video tutorial, if you need it.
EDIT: apologies for covering much of what has already been discussed by @wrkadung, got ninja'd a bit there...
I wouldn't risk locking the bootloader via platform-tools....so many instances from all the way back from the original Pixel has had countless members hard-brick their Pixel's relocking the bootloader.
The safest way to go about it is to use the Android Flash Tool to flash both slots and relock bootloader; most hard bricks happen when it's not flashed to both slots and/or the improper factory image is used...
But the OEM unlocking being greyed out is sometimes SOP after unlocking the bootloader. It's not really anything to be concerned about. If Wallet isn't working properly, it is doubtful it is simply having the unlocked bootloader; Wallet usually doesn't work when rooted than it is the fact of an unlocked bootloader. You should try Force Stop-ing and Clear Data Wallet first. Then even "uninstall updates" and/or revert to an older version before locking the bootloader. ESPECIALLY if you don't wish to wipe the device by relocking the bootloader...
max_134 said:
Week ago I flashed the android 14 dev, don't liked it and yesterday flashed A13 (TQ1A.230205.002) with Android Flash Tool. Today I saw that I can't add my credit card to the Google Pay. I checked in settings and found out that my bootloader unlocked but the button is unavailable.
What can I do?
Click to expand...
Click to collapse
Google pay will work with an unlocked bootloader.
simplepinoi177 said:
EDIT: apologies for covering much of what has already been discussed by @wrkadung, got ninja'd a bit there...
I wouldn't risk locking the bootloader via platform-tools....so many instances from all the way back from the original Pixel has had countless members hard-brick their Pixel's relocking the bootloader.
The safest way to go about it is to use the Android Flash Tool to flash both slots and relock bootloader; most hard bricks happen when it's not flashed to both slots and/or the improper factory image is used...
But the OEM unlocking being greyed out is sometimes SOP after unlocking the bootloader. It's not really anything to be concerned about. If Wallet isn't working properly, it is doubtful it is simply having the unlocked bootloader; Wallet usually doesn't work when rooted than it is the fact of an unlocked bootloader. You should try Force Stop-ing and Clear Data Wallet first. Then even "uninstall updates" and/or revert to an older version before locking the bootloader. ESPECIALLY if you don't wish to wipe the device by relocking the bootloader...
Click to expand...
Click to collapse
Yes, definitely, a stock factory image is required. Most people directly lock the bootloader on a rooted phone using adb & fastboot commands, which results in bricking the phone.
On stock firmware, it is working perfectly. Right now I am working on a video tutorial for Pixel 7 and it worked fine without any issues, it was just bootloader unlocked device (not rooted).