Database Develop

[Q] stuck on locked bootloader question

I have a nexus 6 with locked bootloader with 5.1 unable the check OEM unlock bla bla...
So... I was 3 days ago at a mobile repair service and i gave my nexus 6 for a repair...
They cant repair my phone.. They tried with 3 different engineers but non of them can repair it...
motorola will not replace your phone i asked them because i not updated with OTA...flash over usb errors
Not covered by the warranty...
So does anyone succeeded with this solution? On anyway ?? Anyhow?? For money or for free? I dont care .... Just please reply something ...Any working method? Please answer i really need my device... Thanks and sorry for my english. i think in this thread this is the main issue

necroside007 said:
I have a nexus 6 with locked bootloader with 5.1 unable the check OEM unlock bla bla...
So... I was 3 days ago at a mobile repair service and i gave my nexus 6 for a repair...
They cant repair my phone.. They tried with 3 different engineers but non of them can repair it...
motorola will not replace your phone i asked them because i not updated with OTA...flash over usb errors
Not covered by the warranty...
So does anyone succeeded with this solution? On anyway ?? Anyhow?? For money or for free? I dont care .... Just please reply something ...Any working method? Please answer i really need my device... Thanks and sorry for my english. i think in this thread this is the main issue
Click to expand...
Click to collapse
Ooooh... That's tough. The only place I've heard of any kind of fix is in this thread:
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
But, I don't think your situation applies... You're probably SOL.

There's no fix. You can try fastboot format cache and fastboot format userdata. If that doesn't work, there's no fix.

rootSU said:
There's no fix. You can try fastboot format cache and fastboot format userdata. If that doesn't work, there's no fix.
Click to expand...
Click to collapse
So i can throw away my phone?

necroside007 said:
So i can throw away my phone?
Click to expand...
Click to collapse
I wouldn't yet. Someone may eventually find a fix. But yes, you're going to need a new phone in the meantime.

Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.

jackpollard said:
Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.
Click to expand...
Click to collapse
This is a very good idea!

jackpollard said:
Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.
Click to expand...
Click to collapse
It does say in post 1 that he asked Motorola

I'm confused. What did u do to screw up your phone
sent from your moms phone

necroside007 said:
So i can throw away my phone?
Click to expand...
Click to collapse
Send it in for repair mate, off course its fixable in a servicecenter but not by us consumers.
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
93fuelslut said:
I'm confused. What did u do to screw up your phone
sent from your moms phone
Click to expand...
Click to collapse
He probably locked the bootloader and had oem-unlock disabled in developer options, and now he can`t flash anything and the phone has no OS.

rootSU said:
It does say in post 1 that he asked Motorola
Click to expand...
Click to collapse
"Hello Ms. Motorola, yes my mother called earlier today, she thought my N6 was in some sort of loop or something, man you know how moms can be. It just won't turn on, I have no idea why, I just know it was working great 1 minute and now, nothing. OK, where do I send it? Thanks"
The crap part would be if someone finds a fix after the phone is damaged. But, before you do anything, make the call.
I see many many threads regarding how to get free tethering, so I don't feel this is too out of place. Again, everyone has to work out for themselves whats right for them.

gee2012 said:
Send it in for repair mate, off course its fixable in a servicecenter but not by us consumers.
---------- Post added at 03:53 PM ---------- Previous post was at 03:52 PM ----------
He probably locked the bootloader and had oem-unlock disabled in developer options, and now he can`t flash anything and the phone has no OS.
Click to expand...
Click to collapse
I'm thinking abt getting a n6. Can u elaborate a little more? Wouldn't "unlocked disabled" mean locked, so that phrase would mean the same as a locked bootloader which he did?
sent from your moms phone

93fuelslut said:
I'm thinking abt getting a n6. Can u elaborate a little more? Wouldn't "unlocked disabled" mean locked, so that phrase would mean the same as a locked bootloader which he did?
sent from your moms phone
Click to expand...
Click to collapse
Since 5.1, you need "enable OEM unlock" set in settings to unlock the bootloader. If it is not set, you cannot unlock the bootloader. It only stays set until you boot up.
So some people update then immediately lock the bootloader. Then their phone won't boot so they cannot set "enable OEM unlock" so they're screwed.

rootSU said:
Since 5.1, you need "enable OEM unlock" set in settings to unlock the bootloader. If it is not set, you cannot unlock the bootloader. It only stays set until you boot up.
So some people update then immediately lock the bootloader. Then their phone won't boot so they cannot set "enable OEM unlock" so they're screwed.
Click to expand...
Click to collapse
So when I get my n6, I just need a laptop to root, and not to unlock boot loader? Since I can just go into settings and check "enable unlock bootloader?
sent from your moms phone

93fuelslut said:
So when I get my n6, I just need a laptop to root, and not to unlock boot loader? Since I can just go into settings and check "enable unlock bootloader?
sent from your moms phone
Click to expand...
Click to collapse
You have to enable oem-unlock after every boot, it will not stick after a reboot.

93fuelslut said:
So when I get my n6, I just need a laptop to root, and not to unlock boot loader? Since I can just go into settings and check "enable unlock bootloader?
sent from your moms phone
Click to expand...
Click to collapse
No. The "enable OEM unlock" setting allows you to boot to the bootloader, connect to a pc and use the "fastboot oem unlock" command to unlock the bootloader.

gee2012 said:
You have to enable oem-unlock after every boot, it will not stick after a reboot.
Click to expand...
Click to collapse
Is this the same with aosp ROMs?
What happens if I forget to check it after a reboot? Like if my ROM does a random reboot and I don't know about it
sent from your moms phone

93fuelslut said:
Is this the same with aosp ROMs?
What happens if I forget to check it after a reboot? Like if my ROM does a random reboot and I don't know about it
sent from your moms phone
Click to expand...
Click to collapse
I think we're confusing the issue. It doesn't need to stay ticked. All it stops you doing is unlocking the bootloader. Once the bootloader is unlocked, its unlocked.
The only reason you'll need to tick it is if you relocked the bootloader and then wanted to unlock it again. But this is dangerous because if your ROM breaks and you're locked, you cannot then unlock.

jackpollard said:
Just a random thought; so what is covered by warranty? Say an internal connection was to get detached and the phone just won't power up, I think that would probably be something they may honor and replace the phone. I would not go back to the same place you tried to have it fixed, I would contact Motorola direct.
Again just a thought without thinking through all the scenarios nor with any thought of the morality of it.
Click to expand...
Click to collapse
With OTA should be fine.. If something goes wrong during ota thats covered by warranty, but i was impatient to wait for it, so i did for my self over USB thats not covered by warranty like when u **** up something with root permissions.. This method is not the original updating method. but its a bit confusing because this was an official google suggested method (https://developers.google.com/android/nexus/images) Terms of use, i accepted hurray!

"Send it in for repair mate, off course its fixable in a servicecenter but not by us consumers."
I did it and they cant repair it.. No way to access to that software part

[Q] Thoughts on unlocking bootloader on locked nexus 6

I bought a nexus 6 and it is locked with the anti theft thing...cant get ahold of the seller and it doesnt show his info on the nexus at all. anyways does anyone have any thoughts on bypassing it ? I did try to sign into mine and it does sign and checks for update and then immediately signs out. Maybe a modified DNS server ? I also did try to reset it ..no lucky, also tried to flash android 5.0 but says boot loader needs to be unlocked. Is there a way to unlock boot loader without doing it in settings ? I did also try to fastboot oem unlock but says to do it in settings. I was thinking maybe modifying the stock image and go into the build prompt and change the value of the start up wizard to remove it but then the bootloader thing gets in the way. Someone help

jordy787 said:
I bought a nexus 6 and it is locked with the anti theft thing...cant get ahold of the seller and it doesnt show his info on the nexus at all. anyways does anyone have any thoughts on bypassing it ? I did try to sign into mine and it does sign and checks for update and then immediately signs out. Maybe a modified DNS server ? I also did try to reset it ..no lucky, also tried to flash android 5.0 but says boot loader needs to be unlocked. Is there a way to unlock boot loader without doing it in settings ? I did also try to fastboot oem unlock but says to do it in settings. I was thinking maybe modifying the stock image and go into the build prompt and change the value of the start up wizard to remove it but then the bootloader thing gets in the way. Someone help
Click to expand...
Click to collapse
Far as I know if it it is locked to his account there is no way without his password. If used paypal file with them to get money back.

prdog1 said:
Far as I know if it it is locked to his account there is no way without his password. If used paypal file with them to get money back.
Click to expand...
Click to collapse
my friend was the one who bought it , he sold it to me for $100. Maybe i should get it into a bootloop and then try to rma it ?

jordy787 said:
my friend was the one who bought it , he sold it to me for $100. Maybe i should get it into a bootloop and then try to rma it ?
Click to expand...
Click to collapse
Yea. It pretty much a paperweight as it is. Lot of people selling them and don't know they have to remove their Google account before resetting and selling.

prdog1 said:
Yea. It pretty much a paperweight as it is. Lot of people selling them and don't know they have to remove their Google account before resetting and selling.
Click to expand...
Click to collapse
Yup , i was also thinking maybe flashing a userdata.img from another phone ? Idk if the bootloader would stop me tho

jordy787 said:
Yup , i was also thinking maybe flashing a userdata.img from another phone ? Idk if the bootloader would stop me tho
Click to expand...
Click to collapse
Need to be unlocked. Can't unlock if can't get to settings. That the whole theory of the security. Need that password. If you even reset without deleting your account and change your password can't get back in for 3 days with your own account..

http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504

prdog1 said:
Need to be unlocked. Can't unlock if can't get to settings. That the whole theory of the security. Need that password. If you even reset without deleting your account and change your password can't get back in for 3 days with your own account..
Click to expand...
Click to collapse
in recovery there is apply update from adb which is adb sideload..Think i can sideload twrp?

jordy787 said:
in recovery there is apply update from adb which is adb sideload..Think i can sideload twrp?
Click to expand...
Click to collapse
Don't think stock recovery will let you flash recovery from within itself. Would lose adb as soon as tried I would think.

jordy787 said:
in recovery there is apply update from adb which is adb sideload..Think i can sideload twrp?
Click to expand...
Click to collapse
No.

I got into the browser ,YouTube and Facebook worked wonder if I can trick it and have a shortcut that brings me to the home screen ?

Help! Phone stuck at boot screen, power button only restarts phone!!

UPDATE:
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
so I received a new Nexus 6 device from T-Mobile for my girlfriend.
In our area unfortunately Wi-Fi calling is a must, so she went ahead and did both of the OTA updates. After doing the second update the phone was stuck optimizing apps, and then the screen wouldn't work...
So I then hooked the phone up to the PC and through ADB did the following commands
fastboot erase userdata
fastboot erase cache
That was supposedly the commands I had found on the internet to go ahead and factory reset the phone.
Now the phone is stuck at the balls swirling and it won't stop. Try and hold the power button down and the phone just restarts itself, won't shut down so I can't even get back into the recovery.
I tried to first load up a factory image before doing something silly like that but when I tried to run the command "fasboot oem unlock" it says I need to enable developer options in Android... which I couldn't get to anyways...
Can someone please help with this issue. Her old phone got stolen and now she has this one which is completely messed up.
Thank you for anyone who can help me!

none
You have to hold power and down on the bottom button, or since you have adb, you can do "adb reboot recovery". Push volume down first then power. After that you can enable MTP and toss a rom on the phone. Do a complete wipe with the exception of the internal storage ( I did storage one time accidentally, yuk) flash a ROM and you should be good

I can't even turn off the device at this point.... It is just stuck at the balls spinning and won't go any further.
When trying to shut the phone off the power button just restarts the phone, doesn't shut it down. Not sure what is going on.....

jwleonhart said:
I can't even turn off the device at this point.... It is just stuck at the balls spinning and won't go any further.
When trying to shut the phone off the power button just restarts the phone, doesn't shut it down. Not sure what is going on.....
Click to expand...
Click to collapse
It should shut down if hold the power button long enough. Takes like 20 seconds or so.

OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.

jwleonhart said:
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
Click to expand...
Click to collapse
As far as I know with stock recovery about all you can do is try to format cache and try to factory reset again. Otherwise will have to take back to T-Mobile and RMA. Make them update it. Lot of OTA updates have been failing.

I'm just curious to know if there is someway. Maybe I can force TWRP recovery or something like that on the phone by at least getting in the bootloader... There is a fix for bricking if it is like that.
Why the bootloader just doesn't come unlocked I will not understand. It would prevent motorola from having a heap of useless devices, as i'm sure probably even motorola themselves cannot fix the device.
Seems like a whole pile of sh*t if you ask me.
Anyone have any ideas? Worst part is T-Mobile won't ship a phone over the weekend either, so thats just 3 more days without a phone which is just wonderful.

jwleonhart said:
I'm just curious to know if there is someway. Maybe I can force TWRP recovery or something like that on the phone by at least getting in the bootloader... There is a fix for bricking if it is like that.
Why the bootloader just doesn't come unlocked I will not understand. It would prevent motorola from having a heap of useless devices, as i'm sure probably even motorola themselves cannot fix the device.
Seems like a whole pile of sh*t if you ask me.
Anyone have any ideas? Worst part is T-Mobile won't ship a phone over the weekend either, so thats just 3 more days without a phone which is just wonderful.
Click to expand...
Click to collapse
There is no way to flash a recovery without the bootloader unlocked. On these devices it is best to unlock bootloader first thing before trying to update so have some control if things go bad. Moto has the ability to reflash them like J-Tag. TMobile store may replace it.

Messed up part about T-Mobile is the fact this was an exchange for a stolen phone. They actually waived the insurance fee of $175 and the tax on the phone... which was extremely nice of them since I still owed about $350 on the LG G3 my girlfriend had.
So since the exchange was done over the phone or I should say since the new handset would bought over the phone the store won't replace it... it's weird they operate that way because the store should be able to replace anything that is sold via phone or internet and vice versa.

jwleonhart said:
Messed up part about T-Mobile is the fact this was an exchange for a stolen phone. They actually waived the insurance fee of $175 and the tax on the phone... which was extremely nice of them since I still owed about $350 on the LG G3 my girlfriend had.
So since the exchange was done over the phone or I should say since the new handset would bought over the phone the store won't replace it... it's weird they operate that way because the store should be able to replace anything that is sold via phone or internet and vice versa.
Click to expand...
Click to collapse
Yea. It a bad situation. We have seen a lot of them choke on the OTA flash. Best to unlock upfront and fastboot the updated factory image. You are always safe once it is unlocked.

Still begs the question as to why they don't just unlock the bootloader from the factory to avoid all this crap. I mean imagine how much money and time they would save if they just did it? I completely forgot about unlocking the bootloader even because I figured hey just OTA it and be done.... remember it's my girlfriend so I wasn't going to put some ROM on there that might have something broken or whatever... can't believe this **** though.

jwleonhart said:
Still begs the question as to why they don't just unlock the bootloader from the factory to avoid all this crap. I mean imagine how much money and time they would save if they just did it? I completely forgot about unlocking the bootloader even because I figured hey just OTA it and be done.... remember it's my girlfriend so I wasn't going to put some ROM on there that might have something broken or whatever... can't believe this **** though.
Click to expand...
Click to collapse
I understand. They look at unlocked bootloader as a security problem. It even tells you it disabled security when you flip the unlock switch. From the many OTAs we have seen brick it is best to just unlock even if running stock. Once it is up and running can always relock. Do not relock if have custom recovery or kernel tho. It will more than likely bootloop. I tried it for grins but made sure the unlock option was enabled and was able to unlock and reflash. Many have flashed new software and relocked before first boot to find out it bootloops and can't unlock again. Best to have TWRP so that if is locked have a adb/MTP option. We pretty much discourage OTA. I haven't tried but have seen a post that says must be locked to OTA. If that is the case you always have the chance of a bad OTA flash and end up same place you are now. With TWRP there are also OTA files that have been converted to flashable zip and can be flashed in recovery.

The strangest bootloader screen I have ever seen

Can someone explain this

bwtmanagement said:
Can someone explain this
Click to expand...
Click to collapse
I've not experienced this.
Are you rooted / bootloader unlocked?
Do you have any idea what caused it?
Were you able to recover?
If so, what did you have to do?

bwtmanagement said:
Can someone explain this
Click to expand...
Click to collapse
Did you do anything to the bootloader by flashing any files? Did you unlock the bootloader? If the answer is yes then you might have an issue with flashed files.
If no and you have not touched the device then you might have a rare error. If you have a carrier phone with Verizon you might want to try their "repair assistant" which is the same as what is mentioned on the phone screen. It seems to have a repair function. You will have to connect the phone via USB to your computer. Download the assistant from here. https://www.verizonwireless.com/support/knowledge-base-209211/
If you don't have a Verizon moto x4 or you have another carrier then either still give the software a shot or take it to a Motorola service centre.
Can pretty much confirm the same with an old moto z force post on the Lenovo forums. If you have Verizon downloading the software will solve the problem.

I know that I was trying to flash to stock and that was the result, rsd can see the device but when I flash it it says failed to switch to fastboot

Yea bootloader has been unlocked for weeks and started acting up and I was trying to clear it and start over and no I can't get it to flash spar_chunks

Any ideas

Notice you mentioned RSD failing to switch to fastboot... I assume you tried reflashing the GPT/bootloader directly from fastboot?
If you hit volume up/down from the screen you posted, does it go through the other fastboot screens?

No i get the quausb or whatever that is in my comp for deviecs now...and no screen mow and yes the parition was compermised by error on my part

Pixel 5 - Removal from Beta 13 - Corrupt Error

So.... I removed my Pixel 5 form the beta 13 program, selected update on the devices and had it download Android 12 a few weeks back. On reboot I get the "device is corrupt" error with visit the g.co/ABH link. If I hit the power button that error loops, and trying a hard / factory reset does nothing.
I tried several of the steps but since I cannot get into Dev mode to unlock the bootloader I'm kind of stuck.
The most I have been able to do is with the rescue tool, but that throws a "software on device is newer then this tool" error and wont go forward.
Any suggestions? Should I just send in to a repair shop? Or move on?

I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA

xunholyx said:
I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA
Click to expand...
Click to collapse
Tried both types of cables, no luck...

grmacd said:
Tried both types of cables, no luck...
Click to expand...
Click to collapse
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.

V0latyle said:
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.
Click to expand...
Click to collapse
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet

grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
Unfortunate and I feel for you.
It's generally advisable to always unlock the bootloader when running any kind of beta software, just because of this eventuality - if something goes wrong, you need to have a way to recover the device.

grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
You should be able to boot to recovery from the bootloader

I can boot to recovery, but the software wont sideload since the boot locker is locked.
My one hope is the fact Rescue mode on the web is throwing "software on the device older then this tool" so I am hoping once that gets a newer version I will be ok. So into the drawer it goes...

But you don't need an unlocked bootloader to sideload an OTA....

xunholyx said:
But you don't need an unlocked bootloader to sideload an OTA....
Click to expand...
Click to collapse
Ok... perhaps I will give it another try tomorrow.

grmacd said:
Ok... perhaps I will give it another try tomorrow.
Click to expand...
Click to collapse
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now

xunholyx said:
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now
Click to expand...
Click to collapse
So this AM I downloaded the newest ZIP file and followed the step on the site - after about 10 minutes presto the phone is back up and running with Android 13! Thanks for your help!