Related
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.
I have to return my old phone today and need to lock the bootloader back. I already did a factory reset which did not work. Could someone please give me the directions on how to relock it so I can get it sent off? Thanks.
Oaklands said:
I have to return my old phone today and need to lock the bootloader back. I already did a factory reset which did not work. Could someone please give me the directions on how to relock it so I can get it sent off? Thanks.
Click to expand...
Click to collapse
Haven't done it in a while but I'm sure it's the same. Go into fastboot and make sure the device is recognized with "fastboot devices" then " fastboot flashing lock " and it will wipe device and reboot.
bobby janow said:
Haven't done it in a while but I'm sure it's the same. Go into fastboot and make sure the device is recognized with "fastboot devices" then " fastboot flashing lock " and it will wipe device and reboot.
Click to expand...
Click to collapse
Thank you. I will give it a try.
That did not do it. What I tried was flashing the Raven Rom again with a standard flash-all.bat.
The bootloader was still locked then I ran the "fastboot flashing lock" command and it worked.
Oaklands said:
That did not do it. What I tried was flashing the Raven Rom again with a standard flash-all.bat.
The bootloader was still locked then I ran the "fastboot flashing lock" command and it worked.
Click to expand...
Click to collapse
Maybe this isn't up to date, then? Weird. Not so uncommon if it is out of date, but it's such a big thing I would expect it to be up to date. You're using the latest Platform Tools, correct? I'm confused because you start the first sentence "That did not do it" but then say "and it worked" at the end, so I'm missing something.
https://source.android.com/setup/build/running#relocking-the-bootloader
Re-locking the bootloader​To re-lock the bootloader:
For newer devices (2015 and higher):
fastboot flashing lock
For older devices (2014 and lower):
fastboot oem lock
Note: Re-locking the bootloading on a
Click to expand...
Click to collapse
You could also try the flashing tool from Google that makes it extremely easy. Before you flash you can choose to lock the bootloader as one fo the options. https://flash.android.com/welcome?continue=/back-to-public
liljq said:
You could also try the flashing tool from Google that makes it extremely easy. Before you flash you can choose to lock the bootloader as one fo the options. https://flash.android.com/welcome?continue=/back-to-public
Click to expand...
Click to collapse
This. Android Flash Tool is the #1 best option for returning to complete stock.
Select the "Wipe Device", "Lock Bootloader", and "Force flash all partitions" options. When the process completes, the device will be back to absolute factory.
roirraW edor ehT said:
Maybe this isn't up to date, then? Weird. Not so uncommon if it is out of date, but it's such a big thing I would expect it to be up to date. You're using the latest Platform Tools, correct? I'm confused because you start the first sentence "That did not do it" but then say "and it worked" at the end, so I'm missing something.
https://source.android.com/setup/build/running#relocking-the-bootloader
Click to expand...
Click to collapse
Just running the command he gave me did not work. The phone would not respond to locking the bootloader. I updated again using the standard .37 image with the -w command. The ran the "fastbopt flashing lock" command and it then responded fine.
V0latyle said:
This. Android Flash Tool is the #1 best option for returning to complete stock.
Select the "Wipe Device", "Lock Bootloader", and "Force flash all partitions" options. When the process completes, the device will be back to absolute factory.
Click to expand...
Click to collapse
I didn't know about this tool beforehand. I have unlocked and rooted a phone in a few years. It's like learning it all over again. I appreciate you letting me now about this.
Oaklands said:
I didn't know about this tool beforehand. I have unlocked and rooted a phone in a few years. It's like learning it all over again. I appreciate you letting me now about this.
Click to expand...
Click to collapse
This tool is specific to Pixel devices only and cannot be used with any other platform.
V0latyle said:
This. Android Flash Tool is the #1 best option for returning to complete stock.
Select the "Wipe Device", "Lock Bootloader", and "Force flash all partitions" options. When the process completes, the device will be back to absolute factory.
Click to expand...
Click to collapse
I concur!
Hello,
I did uninstall the magisk I had in my pixel 6 pro and now I don't have root, but now when I start the device I see lines at the boot about the fastboot so as I understand I should lock it for the OTA's of google, (is it right?)
So i saw here the command: fastboot flashing lock
or to use the google tool
https://flash.android.com/welcome?continue=/back-to-publicdoes the usage of the tool meaning that the device will be wiped? (I have the stock rom ->rooted -> uninstall magisk) and I want to be original with that stock to get updateds,
Thanks
I7210I said:
Hello,
I did uninstall the magisk I had in my pixel 6 pro and now I don't have root, but now when I start the device I see lines at the boot about the fastboot so as I understand I should lock it for the OTA's of google, (is it right?)
So i saw here the command: fastboot flashing lock
or to use the google tool
https://flash.android.com/welcome?continue=/back-to-publicdoes the usage of the tool meaning that the device will be wiped? (I have the stock rom ->rooted -> uninstall magisk) and I want to be original with that stock to get updateds,
Thanks
Click to expand...
Click to collapse
As you may know, even though you uninstalled Magisk and don't have root, you could still have modified partitions on the phone.
You can use:
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
(same as your link) but uncheck the option to wipe, then the phone won't be wiped.
Only then re-lock the bootloader.
roirraW edor ehT said:
As you may know, even though you uninstalled Magisk and don't have root, you could still have modified partitions on the phone.
You can use:
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
(same as your link) but uncheck the option to wipe, then the phone won't be wiped.
Only then re-lock the bootloader.
Click to expand...
Click to collapse
Thank you, the lock of the bootloader will be how?
And in that point i'm going back to the start right?
I7210I said:
Thank you, the lock of the bootloader will be how?
And in that point i'm going back to the start right?
Click to expand...
Click to collapse
You're welcome. I believe you have the lock command correct. See here -> Re-locking the bootloader
Keep in mind that when you do that, it will factory reset your device, and there's no way around that. Every single time you unlock the bootloader or lock it, it forces the phone to factory reset.
Also note that after re-locking the bootloader, you should toggle OEM unlocking in Developer options back to disabled.
roirraW edor ehT said:
You're welcome. I believe you have the lock command correct. See here -> Re-locking the bootloader
Keep in mind that when you do that, it will factory reset your device, and there's no way around that. Every single time you unlock the bootloader or lock it, it forces the phone to factory reset.
Also note that after re-locking the bootloader, you should toggle OEM unlocking in Developer options back to disabled.
Click to expand...
Click to collapse
and....when I will do factory reset = the device will be wiped , right? no way to do it without that
I7210I said:
and....when I will do factory reset = the device will be wiped , right? no way to do it without that
Click to expand...
Click to collapse
Correct.
Looks like @fil3s gave you some of this information in the separate thread you created here. Since I haven't used Official Google Android Flash Tool, I forgot that it appears there's an option right on that site to lock the bootloader. You should follow the directions that @fil3s gave you there, and yes, it will wipe. Factory Reset = Wipe
Ok no way so no way
Will do that
Thank you
I7210I said:
Hello,
I did uninstall the magisk I had in my pixel 6 pro and now I don't have root, but now when I start the device I see lines at the boot about the fastboot so as I understand I should lock it for the OTA's of google, (is it right?)
Click to expand...
Click to collapse
Everything @roirraW "edor" ehT said, but just to be clear, if you only have the bootloader unlocked but nothing else modified, you should still be able to take OTAs. You don't need a locked bootlaoder to take OTAs.
Lughnasadh said:
Everything @roirraW "edor" ehT said, but just to be clear, if you only have the bootloader unlocked but nothing else modified, you should still be able to take OTAs. You don't need a locked bootlaoder to take OTAs.
Click to expand...
Click to collapse
So I think I will leave it like this if I will still get the OTAs, there is no problem with that right?
Thanks
Hi guys,
Really odd one here. On my Dads Pixel 6 pro whenever he uses say a banking app that requires a fingerprint scan the popup isn't aligned the same as my pixel 6 pro. The words Touch the fingerprint sensor aren't there as well as the cancel button at the bottom left. The whole popup is lower than on my pixel.
This means the actual bit where you have to put the your finger is above the little finger print image.
This seems to be from the last update. Anyone got any suggestions?
Worth noting it is perfect on the main lockscreen but just not in apps that require a fingerprint.
Very odd!
I only checked one of my banking fingerprint logins and it worked completely normal. Has he tried turning it off and on again? (the phone)
Tried that. Reinstalled all banking apps.
Removed fingerprints , then re-added.
Thanks
jonahjones said:
Tried that. Reinstalled all banking apps.
Removed fingerprints , then re-added.
Thanks
Click to expand...
Click to collapse
Just to be clear, are you saying that what you did fixed the issue, or the apps are still having that problem?
You're welcome!
Edit: And it's more than one app, or just one particular?
It didn't fix the issue. All apps that allow you sign in with a fingerprint are impacted so seems to be OS level.
Very strange. Stock Android on the phone with the March update, no bootloader unlocked, no root, not opted in to one of the Android Developer Previews/Betas, correct?
roirraW edor ehT said:
Very strange. Stock Android on the phone with the March update, no bootloader unlocked, no root, not opted in to one of the Android Developer Previews/Betas, correct?
Click to expand...
Click to collapse
Yeah all stock with latest update. My Pixel 6 pro with the same banking apps is fine.
jonahjones said:
Yeah all stock with latest update. My Pixel 6 pro with the same banking apps is fine.
Click to expand...
Click to collapse
If OEM Unlocking is able to be toggled on the device (non-Verizon, and either Unlocked, or paid off T-Mobile contract - not sure about AT&T), then I would suggest the following with a full wipe. Making sure everything is backed up from the phone that your dad wants to keep first: Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
roirraW edor ehT said:
If OEM Unlocking is able to be toggled on the device (non-Verizon, and either Unlocked, or paid off T-Mobile contract - not sure about AT&T), then I would suggest the following with a full wipe. Making sure everything is backed up from the phone that your dad wants to keep first: Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
Click to expand...
Click to collapse
Thanks. It probably isn't worth the hassle of a full wipe.
IDK, but could it have anything to do if he has his UI set to 'large print' in system settings? Just a thought.
You know what I would try? Using the Android Flash Tool and reflashing the lastest FULL OTA and seeing if that fixes it. That way, NO WIPE!
thanks guys.
his display settings are default but I am going to get him to tweak those and hopefully that will cause the OS to rearrange the layout somehow.
I had originally thought it was because he uses the navigation buttons
jonahjones said:
thanks guys.
his display settings are default but I am going to get him to tweak those and hopefully that will cause the OS to rearrange the layout somehow.
I had originally thought it was because he uses the navigation buttons
Click to expand...
Click to collapse
I use navigation buttons and have no problem with banking apps or any app that uses the Fingerprint scanner. Maybe reflashing March with Android flash tool is worth a try. Without wiping or locking bootloader, of course.
Been a while since I mucked about with the firmware on phones. HTC Desire HD haha.
So using that tool allows you to not wipe the data?
Yes. Uncheck boxes "wipe" & "lock bootloader"
jonahjones said:
Been a while since I mucked about with the firmware on phones. HTC Desire HD haha.
So using that tool allows you to not wipe the data?
Click to expand...
Click to collapse
To add to what @jcp2 said, your bootloader must already be unlocked to use the flash tool. If it's not already unlocked, unlocking the bootloader forces the phone to be completely wiped as if it's brand new - albeit now it would have an unlocked bootloader.
That is on top of whether the phone is even bootloader unlockable.
Once you unlock the bootloader, the recommendation is to leave it unlocked, as if you lock it, it will once again completely wipe the phone.
roirraW edor ehT said:
To add to what @jcp2 said, your bootloader must already be unlocked to use the flash tool. If it's not already unlocked, unlocking the bootloader forces the phone to be completely wiped as if it's brand new - albeit now it would have an unlocked bootloader.
That is on top of whether the phone is even bootloader unlockable.
Once you unlock the bootloader, the recommendation is to leave it unlocked, as if you lock it, it will once again completely wipe the phone.
Click to expand...
Click to collapse
Thanks. I had completely forgotten about that bit
Hey everyone!
I was updating to the latest Android beta to try to get the Move to iOS app to work. The update seemingly went fine and I was using my phone (on reddit lol) and suddenly it powered off.
Now when it starts I get a black screen that asyas "Fastboot Mode". My phone isn't unlocked so I haven't done anything funky with the firmware.
I'm afraid I've lost everything on the phone
Here's a picture of what the phone shows:
https://imgur.com/oBpGFGX
Well, the fact you can boot into fastboot is good news
Before we talk about possible actions:
- what ROM exactly were you coming from ? Was that rooted or with a custom kernel ? Was the device unlocked ?
- what ROM exactly have you been flashing ? By using which method ? Any additional steps you did while/after flashing this ?
s3axel said:
Was the device unlocked ?
Click to expand...
Click to collapse
Besides @adamkparker's statement below, the screenshot shows the bootloader is locked, unfortunately.
adamkparker said:
My phone isn't unlocked so I haven't done anything funky with the firmware.
Click to expand...
Click to collapse
You should never install Betas without having the bootloader unlocked. Is OEM unlocking at least enabled in Developer Options (I know you can't get in there right now, but was it enabled before the phone stopped being able to boot to Android)? If OEM unlocking is enabled, even with the bootloader locked now, you can try Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
If OEM unlocking isn't enabled, there's probably nothing you can do to fix the phone - you'll have to RMA it.
Pretty sure he can sideload an ota if USB debugging was enabled. One user reported they were able to sideload with locked bootloader
fil3s said:
Pretty sure he can sideload an ota if USB debugging was enabled. One user reported they were able to sideload with locked bootloader
Click to expand...
Click to collapse
You can sideload OTA updateds without USB debugging enabled. It's really the only way forward for op.
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).