Database Develop

[Q] Fastboot failure help needed

I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):

You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.

I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.

You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk

shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?

Yes you should be able too.
Sent from my XT1053 using Tapatalk

danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.

All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?

shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.

danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.

samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?

danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.

Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.

I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!

danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.

You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.

KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.

danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.

Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.

KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.

Root and BL help

Hi everyone
Okay so Im going to ask a couple of noob questions here. I have been doing a lot of searching on and off xda but I still have a few doubts about rooting/flasing/unlocking my moto x.
If these questions have been asked before I apologize.
First off, I know that my motoX is from ATT, so it has a locked bootloader, right?
And also that it is a 16GB version so is definitely not DE.
I came across a source where it said I can still root my X with a locked bootloader and that must enable me to flash custom roms. Is this true? (I am a little hesitant about trusting websites other than xda). Why do we even need to unlock the bootloader then? if flashing custom roms is a go with root.
My phone is currently on 4.2.2. How am i supposed to find out if this is the pre or post camera update?
I would really appreciate your replies here as I am holding back from updating to KitKat (I read bootloader cant be unlocked on 4.4). Thanks a lot!

See this thread...
http://forum.xda-developers.com/showthread.php?t=2826159
And you can not flash roms without a custom recovery. And you can't have a custom recovery without an unlocked bootloader.
Whatever you read on another site sounds plain wrong. So proceed with caution.
You can try the thread in general about the Chinese Middleman and see if you can unlock your bootloader for $45. That's your only hope at the moment.
Good luck!

alimzia said:
Hi everyone
Okay so Im going to ask a couple of noob questions here. I have been doing a lot of searching on and off xda but I still have a few doubts about rooting/flasing/unlocking my moto x.
If these questions have been asked before I apologize.
First off, I know that my motoX is from ATT, so it has a locked bootloader, right?
And also that it is a 16GB version so is definitely not DE.
I came across a source where it said I can still root my X with a locked bootloader and that must enable me to flash custom roms. Is this true? (I am a little hesitant about trusting websites other than xda). Why do we even need to unlock the bootloader then? if flashing custom roms is a go with root.
My phone is currently on 4.2.2. How am i supposed to find out if this is the pre or post camera update?
I would really appreciate your replies here as I am holding back from updating to KitKat (I read bootloader cant be unlocked on 4.4). Thanks a lot!
Click to expand...
Click to collapse
There is either a lot of misinformation, or misunderstanding, or both. My guess is a little of both.
What you have read about is using an exploit to root and disable write protection. This is VERY different from actually unlocking the bootloader. These exploits are temporary, and they do not allow you to flash custom roms. They only allow flashing "stock-based, safestrap-compatible" ROMs. While this can be useful, there is no comparison to unlocking the bootloader. Be careful to not confuse the two.
@KJ has pointed you in the right direction. I only wanted to clarify that what you are referring to is "write-protect disable", which again is very different from bootloader unlock. Follow his advice and read up so you can better understand. In the mean-time, don't accept any OTAs until you have decided which option is best for you.
Good Luck :good:

samwathegreat said:
There is either a lot of misinformation, or misunderstanding, or both. My guess is a little of both.
What you have read about is using an exploit to root and disable write protection. This is VERY different from actually unlocking the bootloader. These exploits are temporary, and they do not allow you to flash custom roms. They only allow flashing "stock-based, safestrap-compatible" ROMs. While this can be useful, there is no comparison to unlocking the bootloader. Be careful to not confuse the two.
@KJ has pointed you in the right direction. I only wanted to clarify that what you are referring to is "write-protect disable", which again is very different from bootloader unlock. Follow his advice and read up so you can better understand. In the mean-time, don't accept any OTAs until you have decided which option is best for you.
Good Luck :good:
Click to expand...
Click to collapse
Okay i just need root for using titanium backup. Just one question though before i go on with it. After rooting my device (currently 4.2.2) can i continue to get OTA updates? If so, till what version (4.4 max)?
Again thankyou for your replies. Appreciate it.

alimzia said:
Okay i just need root for using titanium backup. Just one question though before i go on with it. After rooting my device (currently 4.2.2) can i continue to get OTA updates? If so, till what version (4.4 max)?
Again thankyou for your replies. Appreciate it.
Click to expand...
Click to collapse
If you are now on 4.2.2, you're one of the lucky ones..... You can still use the slapmymoto method and get full root with write protection disabled!!
See that section in the one stop shop thread.
?
But you can't go higher than 4.4 to keep all that.

Hey Sam i know this is Off topic but tell me more about Republic wireless and why you like them im thinking of switching from big red

qweesy said:
Hey Sam i know this is Off topic but tell me more about Republic wireless and why you like them im thinking of switching from big red
Click to expand...
Click to collapse
Sent you a PM.

KJ said:
If you are now on 4.2.2, you're one of the lucky ones..... You can still use the slapmymoto method and get full root with write protection disabled!!
See that section in the one stop shop thread.
?
But you can't go higher than 4.4 to keep all that.
Click to expand...
Click to collapse
Okay, after rooting will i be able to receive OTA for 4.4? If so, will it still be write protection disabled?

alimzia said:
Okay, after rooting will i be able to receive OTA for 4.4? If so, will it still be write protection disabled?
Click to expand...
Click to collapse
You would have to read the slapmymoto thread, but I believe you would flash 4.4 with fastboot . And that's it. If you upgrade to 4.4.2 or higher, you will have write protection enabled again.

KJ said:
You would have to read the slapmymoto thread, but I believe you would flash 4.4 with fastboot . And that's it. If you upgrade to 4.4.2 or higher, you will have write protection enabled again.
Click to expand...
Click to collapse
Yeah I read that. It is a long method...
I dont know why write protection is so important, i dont know what it does. All I care about is root. If write protection doesn't matter to me just as much, should i rather just receive the OTA to 4.4 right now and THEN root my device? (I just need root privileges for titanium and xposed)
What would you recommend? Is write disabling write protection that important? Thanks again.
Isnt there a way to root directly from 4.4? (Wont slapmymoto work?)

alimzia said:
Yeah I read that. It is a long method...
I dont know why write protection is so important, i dont know what it does. All I care about is root. If write protection doesn't matter to me just as much, should i rather just receive the OTA to 4.4 right now and THEN root my device? (I just need root privileges for titanium and xposed)
What would you recommend? Is write disabling write protection that important? Thanks again.
Click to expand...
Click to collapse
Yes, it is that important. Without write protect disabled, you have to re-root after every reboot. Titanium backup won't work fully because all changes are reverted upon reboot. You will have a heck of a time getting xposed to word if you even can without it disabled.
Yes you can update to 4.4 but not higher. If you use safestrap, you can flash stock based Roms all the way up to 4.4.4. But your bootloader and partition table will remain on 4.4 - this allows you to keep root and write protect disabled.
Be very careful. If you update the bootloader or partition table past 4.4 there is no going back and you will lose the ability to disable write protect permanently.
Basically, without write protect disabled, anything you change gets reverted back upon reboot. You also lose root and have to re-root after every reboot... Not very useful...

alimzia said:
Yeah I read that. It is a long method...
I dont know why write protection is so important, i dont know what it does. All I care about is root. If write protection doesn't matter to me just as much, should i rather just receive the OTA to 4.4 right now and THEN root my device? (I just need root privileges for titanium and xposed)
What would you recommend? Is write disabling write protection that important? Thanks again.
Isnt there a way to root directly from 4.4? (Wont slapmymoto work?)
Click to expand...
Click to collapse
I'm not a slapmymoto expert, since I never needed it... But I believe you need to start on 4.2.2 with it. Then upgrade. Again... You'd need to read on it.
With write protection disabled you can store to the system then. Definitely needed for Xposed.
Trust me.... There's people with locked bootloaders on 4.4.2 and up that would kill to be able to use slapmymoto. ?

Alright thanks a lot guys. Ive made up my mind, going to go through with it, definitely need xposed!
Oh btw just out of curiosity, does Towel-pie-root work with 4.4?

alimzia said:
Alright thanks a lot guys. Ive made up my mind, going to go through with it, definitely need xposed!
Oh btw just out of curiosity, does Towel-pie-root work with 4.4?
Click to expand...
Click to collapse
I believe so.... But people have trouble with Xposed.
---------- Post added at 07:27 PM ---------- Previous post was at 07:26 PM ----------
Same thing too.... Even IF you get Xposed to work... All undone on a reboot or power down.

Will CM12 update radio/bootloader when they update to 5.1?

Title says it all. Will I get the new radio/bootloader when CM12 gets updated? The update includes the ability to use the 700Mhz TMobile freq as well as VoLTE.

They normally do, yes.

Custom ROMs do not provide bootloaders

rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
I didn't think so. I went ahead and restored back to stock and updated to 5.1 from the google factory images. I'll probably go back to CM when they update to 5.1.
Thanks!

rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
Cm does
Sent from my Nexus 6 using XDA Free mobile app

rootSU said:
Custom ROMs do not provide bootloaders
Click to expand...
Click to collapse
CM does. What they're currently doing is they are checking your bootloader version, and the ZIP refuses to flash if you're not on 5.1 bootloader (because downgrading the bootloader might be reason of all these bricks). If you are, then the ZIP flashes and writes bootloader (the version you already have) and radio again.
http://review.cyanogenmod.org/#/c/91181/

Tasssadar said:
CM does. What they're currently doing is they are checking your bootloader version, and the ZIP refuses to flash if you're not on 5.1 bootloader (because downgrading the bootloader might be reason of all these bricks). If you are, then the ZIP flashes and writes bootloader (the version you already have) and radio again.
http://review.cyanogenmod.org/#/c/91181/
Click to expand...
Click to collapse
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.

The issue with cm specifically is that the zip attempted to downgrade the bootloader which isn't possible. Bad things followed.
Sent from my Nexus 6 using XDA Free mobile app

akellar said:
The issue with cm specifically is that the zip attempted to downgrade the bootloader which isn't possible. Bad things followed.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah OK. I don't tend to read threads that have "cm" in the title so I've missed that.

rootSU said:
Ah OK. I don't tend to read threads that have "cm" in the title so I've missed that.
Click to expand...
Click to collapse
(looks at this thread title) Hmm...
Sent from my Nexus 6 using XDA Free mobile app

akellar said:
(looks at this thread title) Hmm...
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. "Tend" . This one piqued my interest as it was asking about the bootloaders though.

rootSU said:
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
Click to expand...
Click to collapse
No, we haven't locked our bootloaders. They have moved all nightlies except one left there. I think that explains sth. Thats how it happens to most of us i think. I never locked my BL, and that happens too. Maybe too soon to judge . Now all i got is a hard bricked phone.

randy6644 said:
No, we haven't locked our bootloaders. They have moved all nightlies except one left there. I think that explains sth. Thats how it happens to most of us i think. I never locked my BL, and that happens too. Maybe too soon to judge . Now all i got is a hard bricked phone.
Click to expand...
Click to collapse
To be hoinest I haven't been following CM specific bricks. That may indeed be what is happening to CM users. I was talking seemingly out of context about all the other threads where peiople had upgraded using fastboot then relocked their BL's

rootSU said:
To be hoinest I haven't been following CM specific bricks. That may indeed be what is happening to CM users. I was talking seemingly out of context about all the other threads where peiople had upgraded using fastboot then relocked their BL's
Click to expand...
Click to collapse
relocking bootloader leads to a bootloop , and it's nothing like a real hard brick like mine. So sad~

rootSU said:
OK I stand corrected, however, flashing CM will not upgrade the bootloader, which is what the OP asked.
The bricks mostly seem to occur for people who have locked their bootloader. They locked it then when android cannot boot, they cannot unlock it again. Most the threads I have seen have not involved anyone flashing older bootloaders yet they still have the problem. Whether, Android would boot for these people had they not locked it is uncertain. Its hard to say whether the OTA just didnt take and they didnt check it booted before locking the BL or whether the BL actually caused the loop once locked... But definitely people have this issue who have not attempted to downgrade.
One of the perks of using custom roms, I never update my bootloader.
Click to expand...
Click to collapse
but they will upgrade the bootloader to 5.1, which means those running 5.0.2 will upgrade.
Most bricks are happening because CM includes the bootloader and you cannot downgrade bootlodaers, if you tried in fastboot it will stop you from doing this. CM uses an old way of accomplishing this which force downgrades the bootloader and messes up the partitioning, resulting in a brick.
I have seen 3 or 4 cases in person from this, and those users never relocked their boot loader like you described.

Circaflex said:
but they will upgrade the bootloader to 5.1, which means those running 5.0.2 will upgrade.
Click to expand...
Click to collapse
Great. Got it. At some point in the future, cm "will" upgrade the bootloader but right now they will refuse to flash.
I'm safe. Haven't used cm since cm6.

Re locking boot loader.

Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!

H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.

Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?

H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.

you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.

simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.

danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.

Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6

Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.

H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.

cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.

-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.

Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6

Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?

H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.

Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?

alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.

Android N OTA Failed

Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?

wolfnumba1 said:
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
Click to expand...
Click to collapse
reboot into bootloader mode and flash that way. OTA is the worst way to update, IMO.

mikeprius said:
reboot into bootloader mode and flash that way. OTA is the worst way to update, IMO.
Click to expand...
Click to collapse
I can't flash images with a locked bootloader or is there a way around that?

wolfnumba1 said:
I can't flash images with a locked bootloader or is there a way around that?
Click to expand...
Click to collapse
the OTA wiped your custom recovery and didn't load the ROM properly !??!?!?! Yikes....................if your phone has stock recovery and the bootloader is locked then it is bricked and you need to send it in.

Device was completely stock, including recovery no custom recovery or root or anything.

That's strange....

mikeprius said:
That's strange....
Click to expand...
Click to collapse
Lol I know tell me about it.... I am going to see if motorola will send me a replacement but not to confident they will.

did you have root before taking the ota? anyways, sounds like you have the first N brick.

wolfnumba1 said:
Lol I know tell me about it.... I am going to see if motorola will send me a replacement but not to confident they will.
Click to expand...
Click to collapse
They may....I think the big question is if they still have any in stock......anyways, let us know what happens....that's a very unfortunate situation. The first thing I did when I got my phone was unlock the bootloader and I have not re-locked it since.

simms22 said:
did you have root before taking the ota? anyways, sounds like you have the first N brick.
Click to expand...
Click to collapse
No did not have root, was completely stock.

mikeprius said:
They may....I think the big question is if they still have any in stock......anyways, let us know what happens....that's a very unfortunate situation. The first thing I did when I got my phone was unlock the bootloader and I have not re-locked it since.
Click to expand...
Click to collapse
Yea sucks, device is out of warranty so I am SOL it seems. Lol I don't unlock because it breaks android pay and other security features which I did not want to disable.

wolfnumba1 said:
No did not have root, was completely stock.
Click to expand...
Click to collapse
yea, read. i was going to post when no one else posted, but had a customer walk in. by the time i posted it was too late :angel:

wolfnumba1 said:
Yea sucks, device is out of warranty so I am SOL it seems. Lol I don't unlock because it breaks android pay and other security features which I did not want to disable.
Click to expand...
Click to collapse
This is even more unfortunate. You can use Android Pay with an unlocked bootloader. I've flashed my phone back to stock images with the bootloader unlocked and Android Pay works. It's not contingent on a locked bootloader, only factory stock images.

mikeprius said:
This is even more unfortunate. You can use Android Pay with an unlocked bootloader. I've flashed my phone back to stock images with the bootloader unlocked and Android Pay works. It's not contingent on a locked bootloader, only factory stock images.
Click to expand...
Click to collapse
Oh weird, when you check off the allow oem unlock it says disabled security features, I wonder what that means then... yes it sucks, now a very nice looking paperweight lol

wolfnumba1 said:
Oh weird, when you check off the allow oem unlock it says disabled security features, I wonder what that means then... yes it sucks, now a very nice looking paperweight lol
Click to expand...
Click to collapse
That's just a general warning. No bearing on AP.......well you may be able to sell the phone as some people may buy it. I'm sure someone out there has a way to get it back, but I'm not sure how. I recall seeing a thread where someone in Cambodia did the same thing and he took it to a shop that was able to reverse it.....

mikeprius said:
That's just a general warning. No bearing on AP.......well you may be able to sell the phone as some people may buy it. I'm sure someone out there has a way to get it back, but I'm not sure how. I recall seeing a thread where someone in Cambodia did the same thing and he took it to a shop that was able to reverse it.....
Click to expand...
Click to collapse
Lol really? Recall where?

wolfnumba1 said:
Lol really? Recall where?
Click to expand...
Click to collapse
I can't find the thread, but I did find this one:
http://forum.xda-developers.com/nexus-6/help/nexus-6-bricked-november-security-ota-t3242773
It looks like you are not the first to be bricked with an OTA update. There should be a sticky about this issue moving forward.

mikeprius said:
I can't find the thread, but I did find this one:
http://forum.xda-developers.com/nexus-6/help/nexus-6-bricked-november-security-ota-t3242773
It looks like you are not the first to be bricked with an OTA update. There should be a sticky about this issue moving forward.
Click to expand...
Click to collapse
Lol so ****ty, looks like the phone is ****ed

wolfnumba1 said:
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
Click to expand...
Click to collapse
Count me in as one of the potentially many more that bricked his phone while trying out the Beta program via OTA...

sorry to tell you this , but with locked bootloader , your phone is hard bricked, no way to recover, only by sending it back to motorola or amazon if you bought from them. i sold about 100 pieces of nexus 6 to customers and my first advice to them is to check " Enable oem unlocking "
anyway email google and blame them for this and i am sure they will help