I just received my Nexus 5X today and it just so happens to be that it is, in fact, locked from the previous user. I'm afraid that factory resetting will result in the FRP locking me out completely. What can I do? I've tried contacting the seller, but I've received no reply
You could install an Custom Recovery (TWRP), format all partitions and then reflash the factory images, of course only if you have a unlocked bootloader
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.
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,
my mum locked her out on her Google Pixel 2 XL. She cannot remember even her email. I tried a factory reset at the stock recovery. But now the phone stuck at the FRP (Factory Reset Protection)
Bootloader is locked.
Is there any way to bypass the FRP or even boot into the phone ?
Please hlp.
Thanks
Not that I know of,
Androids are hellishly secure these days.
Try recovering the mail using phone number
Did not have entered phone number when registering.
Hello,
I'm in a rather peculiar situation. I bought a Nexus 5X from eBay recently (I know) which was advertised as having the common bootloop issue, of which I saw there seems to be a fix for. After receiving the phone I found that not only does it bootloop, but the bootloader is still locked and the previous owner has set up the phone and used a PIN lock on the lockscreen, leaving me unable to get into the settings to enable Developer settings and unlock the bootloader. Does anyone know of any kind of fix for this? Just to reiterate, I cannot flash any stock rom, and there is no custom recovery on the device. I am not new to unlocking bootloaders and flashing custom firmware, and I have contacted the previous owner to no avail. Any help in this issue would be greatly appreciated.
I have searched the forums but as my situation is compounded of multiple problems (locked BL, no custom recovery and PIN lock) I feel like I have hit a dead end.
I am with ya
I have the exact situation i would love to know if you have figured it out. i have two of them as a package deal from ebay. Both 5x.
advertised as bootloop. wont go past the google screen.. one them i actually got to fire up but then ran into the pin thing...
Can you get in fastboot mode ? If so, you can try flashing a custom recovery
I'm going to keep this short and sweet. I have a Sprint S9 SM-G960U and its activation locked and been factory reset. My friend gave me his old phone after he upgraded because he forgot the lock code and does not remember what google account was used to unlock the device after it was reset from the factory reset boot menu.
Is it possible to unlock the bootloader...if thats even needed, root the device, and flash a custom rom to get around this?
xVoidx said:
I'm going to keep this short and sweet. I have a Sprint S9 SM-G960U and its activation locked and been factory reset. My friend gave me his old phone after he upgraded because he forgot the lock code and does not remember what google account was used to unlock the device after it was reset from the factory reset boot menu.
Is it possible to unlock the bootloader...if thats even needed, root the device, and flash a custom rom to get around this?
Click to expand...
Click to collapse
AFAIK there is no reliable rooting / bootloader unlocking method available
Same question for a european SM-G960U (Snapdragon), where no "OEM unlock" option is available in Developers options.
I've just factory reset it, and am currently waiting for the tedious 7-day uptime period to pass, but am I keeping my hopes too up ??
Please share your results and whether or not it was successful. Thanks!
Well, no luck : no unlock option appeared, and the owner decided to get their device back, so I sadly don't have any result to contribue.
breversa said:
Well, no luck : no unlock option appeared, and the owner decided to get their device back, so I sadly don't have any result to contribue.
Click to expand...
Click to collapse
Bummer!!!