Database Develop

[Q] Am I screwed? Warranty with Motowpnomo

So a loong time ago I diabled write protection using Motowpnomo, slap, and whatever else it took (cant remember, it was a long time ago).
From what I remember, disabling write protection using motowpnomo was irreversable. That still seems to be the case from what I read in the forums. But I am trying to see what my next steps can be with my issue. FYI - Verizon told me that they could tell that my phone was rooted just from talking over the phone??!?! Weird FYI I disabled write protection a long time ago and then my phone had an OTA a few months ago that I accidentally installed. After the OTA my phone still worked properly and SU still worked. But that is the state that my phone is in right now. I have a Verizon Moto X with a locked boot loader. I am on 4.4.2 build kxa20.16-1.25.2
So Saturday my GPS stopped working. I'm not sure if its an app conflict or something else. If Verizon gives me the option to send it in for warranty, is there anything I can do to get the phone back to stock (or close to it) or re-enable write protection?
Also, will my phone still work right or be soft bricked if I just factory reset my phone using the phone itself? I would like to see if I factory data reset if the GPS issue goes away.

Yes. Verizon can tell if you rooted. Yes this can void the warranty. There is a clause in there about altering from manufacturer specs, etc... which they can try to use against you. There was argument about this in another thread, so I'm not going to get into that.
IF the root method you used replaced factory recovery, then doing a factory reset via the phone's menus likely wont work as it would reboot into recovery to try and wipe the phone. But you can try using mfastboot to erase data and cache.
As for returning the phone under warranty option, that is another matter. You can download the 4.4.2 SBF and use RSDLite to flash it. That will remove the effects of MotoWpNoMo, SlapMyMoto, RockMyMoto, PwnMyMoto, etc. And get you to a fresh out of the box state. It could fix your problem too.

KidJoe said:
Yes. Verizon can tell if you rooted. Yes this can void the warranty. There is a clause in there about altering from manufacturer specs, etc... which they can try to use against you. There was argument about this in another thread, so I'm not going to get into that.
IF the root method you used replaced factory recovery, then doing a factory reset via the phone's menus likely wont work as it would reboot into recovery to try and wipe the phone. But you can try using mfastboot to erase data and cache.
As for returning the phone under warranty option, that is another matter. You can download the 4.4.2 SBF and use RSDLite to flash it. That will remove the effects of MotoWpNoMo, SlapMyMoto, RockMyMoto, PwnMyMoto, etc. And get you to a fresh out of the box state. It could fix your problem too.
Click to expand...
Click to collapse
Mark, my brother dropped his moto x and broke the glass. It was running 4.4 rooted locked bootloader verizon phone. If I run 4.4 sbf http://sbf.droid-developers.org/phone.php?device=0 from the link, using rsdlite will that remove any indication it was rooted so it might be covered by the warrenty. and if i get a new phone with 4.4.2 or newer preinstalled, would I be able to run rsdlite and 4.4 sbf to get root again?
thanks

doitinthedirt said:
Mark, my brother dropped his moto x and broke the glass. It was running 4.4 rooted locked bootloader verizon phone. If I run 4.4 sbf http://sbf.droid-developers.org/phone.php?device=0 from the link, using rsdlite will that remove any indication it was rooted so it might be covered by the warrenty. and if i get a new phone with 4.4.2 or newer preinstalled, would I be able to run rsdlite and 4.4 sbf to get root again?
thanks
Click to expand...
Click to collapse
I should have been a little clearer. While flashing the SBF with RSDLite or mFastboot would remove any trace from the phone itself, that might not address what Verizon has in their system.
If Verizon has already noted the account that your phone is rooted, they may not accept warranty claim even if you unroot. I don't know their full policy. I don't know when they "check" if your phone is rooted. Is it an on-going "automatic" thing, or just a "when you call for issue with the phone" type of thing.
As for downgrading from 4.4.2... There are many posts already warning that once 4.4.2 is on the phone, DO NOT attempt to downgrade. There are many reports of bricks or other issues from downgrading to 4.4 and below when you have 4.4.2 already on the phone. Enough bricks, potential bricks, and other flaky issues that it is advised to NOT DOWNGRADE once 4.4.2 is on your phone.

KidJoe said:
I should have been a little clearer. While flashing the SBF with RSDLite or mFastboot would remove any trace from the phone itself, that might not address what Verizon has in their system.
If Verizon has already noted the account that your phone is rooted, they may not accept warranty claim even if you unroot. I don't know their full policy. I don't know when they "check" if your phone is rooted. Is it an on-going "automatic" thing, or just a "when you call for issue with the phone" type of thing.
As for downgrading from 4.4.2... There are many posts already warning that once 4.4.2 is on the phone, DO NOT attempt to downgrade. There are many reports of bricks or other issues from downgrading to 4.4 and below when you have 4.4.2 already on the phone. Enough bricks, potential bricks, and other flaky issues that it is advised to NOT DOWNGRADE once 4.4.2 is on your phone.
Click to expand...
Click to collapse
Thank you for the thorough and fast response.

doitinthedirt said:
If I run 4.4 sbf http://sbf.droid-developers.org/phone.php?device=0 from the link, using rsdlite will that remove any indication it was rooted so it might be covered by the warrenty.
thanks
Click to expand...
Click to collapse
Once you are rooted, they can tell. The phone's bootloader has an indication of root state.
If you see “qe 0/0″ you are running a device that has never been rooted.
If you see “qe 0/1″ you are running a device that was at one time rooted, but currently is not.
If you see “qe 1/1″ like in the picture above, you are running a device that is currently rooted.

mandrsn1 said:
Once you are rooted, they can tell. The phone's bootloader has an indication of root state.
If you see “qe 0/0″ you are running a device that has never been rooted.
If you see “qe 0/1″ you are running a device that was at one time rooted, but currently is not.
If you see “qe 1/1″ like in the picture above, you are running a device that is currently rooted.
Click to expand...
Click to collapse
What picture?

mandrsn1 said:
Once you are rooted, they can tell. The phone's bootloader has an indication of root state.
If you see “qe 0/0″ you are running a device that has never been rooted.
If you see “qe 0/1″ you are running a device that was at one time rooted, but currently is not.
If you see “qe 1/1″ like in the picture above, you are running a device that is currently rooted.
Click to expand...
Click to collapse
Yeah, what picture?
and my X doesn't show QE... it shows "Device is Unlocked. Satus Code: 3" for my unlocked bootloader. A default LOCKED bootloader would say "Device is LOCKED. Status Code: 0" And I think RELOCKED is status code 2.
But it doesn't show root status.
Are you thinking of Samsung maybe?

KidJoe said:
Yeah, what picture?
and my X doesn't show QE... it shows "Device is Unlocked. Satus Code: 3" for my unlocked bootloader. A default LOCKED bootloader would say "Device is LOCKED. Status Code: 0" And I think RELOCKED is status code 2.
But it doesn't show root status.
Are you thinking of Samsung maybe?
Click to expand...
Click to collapse
Oops. I meant stock recovery.
It looks like this: http://www.droid-life.com/wp-content/uploads/2012/08/rootcheck1.jpg

mandrsn1 said:
Oops. I meant stock recovery.
It looks like this: http://www.droid-life.com/wp-content/uploads/2012/08/rootcheck1.jpg
Click to expand...
Click to collapse
Ok, after flashing stock recovery back on, yes I do see qe 1/1 on my rooted Dev X.

KidJoe said:
Ok, after flashing stock recovery back on, yes I do see qe 1/1 on my rooted Dev X.
Click to expand...
Click to collapse
Right. Now if you SBF back to stock, it will go to 0/1. You cannot clear the second 1.

mandrsn1 said:
Right. Now if you SBF back to stock, it will go to 0/1. You cannot clear the second 1.
Click to expand...
Click to collapse
Interesting.. read this thread -> https://forums.motorola.com/posts/78f197711d
There is a post stating that the QE value changed to 1/1 on phones with the KitKat Update, even if you haven't rooted.

KidJoe said:
Interesting.. read this thread -> https://forums.motorola.com/posts/78f197711d
There is a post stating that the QE value changed to 1/1 on phones with the KitKat Update, even if you haven't rooted.
Click to expand...
Click to collapse
Yes, I was under the impression that these QE values were determined to be unrelated to rooting, since completely stock users who received OTAs are suddenly showing 1/1
https://forums.motorola.com/posts/759ad51d8f
http://forum.xda-developers.com/showthread.php?t=2649483
(This rather irritated user insists "qe values don't mean JACK for root")...although I don't know how much trust I would put into that having read the conversation.

samwathegreat said:
Yes, I was under the impression that these QE values were determined to be unrelated to rooting, since completely stock users who received OTAs are suddenly showing 1/1
https://forums.motorola.com/posts/759ad51d8f
http://forum.xda-developers.com/showthread.php?t=2649483
(This rather irritated user insists "qe values don't mean JACK for root")...although I don't know how much trust I would put into that having read the conversation.
Click to expand...
Click to collapse
OK. so my phone came with 4.4 and i rooted via slapmymoto.. so if I do the factory restore if that's an option? and than just ship it back to moto for the warranty replacement... wonder if that will work out or not?

doitinthedirt said:
OK. so my phone came with 4.4 and i rooted via slapmymoto.. so if I do the factory restore if that's an option? and than just ship it back to moto for the warranty replacement... wonder if that will work out or not?
Click to expand...
Click to collapse
I suggest you flash the entire 4.4.2 SBF first. The instructions are in the "Return to Stock" thread. I suggest the manual method. Everything you need is in that thread, including links to the SBF Files themselves. Be sure to flash the appropriate SBF for YOUR carrier.
These instructions assume that you intend to return the phone and no longer care about being able to root it. Flashing the 4.4.2 SBF WILL render your device 'unrootable' except for the partial-root "PIE".
This is your safest bet.
Good Luck
Also, may I ask what the problem with the device is? SBFing back to stock can fix many issues - of course hardware failures are the obvious exception here. Just curious...

samwathegreat said:
I suggest you flash the entire 4.4.2 SBF first. The instructions are in the "Return to Stock" thread. I suggest the manual method. Everything you need is in that thread, including links to the SBF Files themselves. Be sure to flash the appropriate SBF for YOUR carrier.
These instructions assume that you intend to return the phone and no longer care about being able to root it. Flashing the 4.4.2 SBF WILL render your device 'unrootable' except for the partial-root "PIE".
This is your safest bet.
Good Luck
Also, may I ask what the problem with the device is? SBFing back to stock can fix many issues - of course hardware failures are the obvious exception here. Just curious...
Click to expand...
Click to collapse
Mine works very nice... I bought two though and gave one to my brother... he dropped it and screen broke, gonna see if moto will work with fixing it or swapping up to a de version, thanks for the help!

XT1095 on 5.1 with 60.16 Bootloader - Need help Downgrading

I've read mixed things and dont' know what can and can't be done. I purchased an XT1095 from ebay that had device protection activated. The phone is running android 5.1 with the 60.16 bootloader. The phone has a locked bootloader. My thought is if I can downgrade to 5.0, it will let me start the phone without a google account, and then I can unlock it and go from there. Problem is, I haven't had any success yet. I can get the phone into fastboot and recovery mode, but I cannot get it to flash a lower version bootloader or system image (I get invalid preflash validation errors) and the system image says it's not signed properly. There's gotta be a way to downgrade it, but I can't find a solution. Any ideas?

darkprime said:
I've read mixed things and dont' know what can and can't be done. I purchased an XT1095 from ebay that had device protection activated. The phone is running android 5.1 with the 60.16 bootloader. The phone has a locked bootloader. My thought is if I can downgrade to 5.0, it will let me start the phone without a google account, and then I can unlock it and go from there. Problem is, I haven't had any success yet. I can get the phone into fastboot and recovery mode, but I cannot get it to flash a lower version bootloader or system image (I get invalid preflash validation errors) and the system image says it's not signed properly. There's gotta be a way to downgrade it, but I can't find a solution. Any ideas?
Click to expand...
Click to collapse
You wont be able to flash anything if your bootloader is locked...its an xt1095 unlock the bootloader. There are many posts on how to do this for the xt1095 you basically get a code from moto that you apply through adb fastboot. After you unlock bootloader you can flash stuff BUT NEVER EVER EVER EVER EVER try and downgrade the gpt or bootloader EVER. Just the system and boot images.
just to be sure you got it NEVER TRY TO DOWNGRADE THE BOOTLOADER OR GPT .

adm1jtg said:
You wont be able to flash anything if your bootloader is locked...its an xt1095 unlock the bootloader. There are many posts on how to do this for the xt1095 you basically get a code from moto that you apply through adb fastboot. After you unlock bootloader you can flash stuff BUT NEVER EVER EVER EVER EVER try and downgrade the gpt or bootloader EVER. Just the system and boot images.
just to be sure you got it NEVER TRY TO DOWNGRADE THE BOOTLOADER OR GPT .
Click to expand...
Click to collapse
I thought the system image is supposed to be flashable even when not locked. Motorola's instructions for returning something to stock has the bootloader and partition flashed - what's the point in doing that if you can't downgrade it?
Anyways, I have tried to unlock it, but since it is running android 5.1, it requires me to set the OEM Unlock option in Android Developer's Settings. Unfortunately, when the phone boots up, I cannot get into any settings without entering the google account information that was used to protect the phone in the first place. So I'm stuck - 5.1 won't let me get far enough to set the setting to unlock so I can't unlock bootloader to revert back to an earlier system version.

darkprime said:
I've read mixed things and dont' know what can and can't be done. I purchased an XT1095 from ebay that had device protection activated. The phone is running android 5.1 with the 60.16 bootloader. The phone has a locked bootloader. My thought is if I can downgrade to 5.0, it will let me start the phone without a google account, and then I can unlock it and go from there. Problem is, I haven't had any success yet. I can get the phone into fastboot and recovery mode, but I cannot get it to flash a lower version bootloader or system image (I get invalid preflash validation errors) and the system image says it's not signed properly. There's gotta be a way to downgrade it, but I can't find a solution. Any ideas?
Click to expand...
Click to collapse
Try flashing the 5.1 images. I don't know if that will work but it seems like it might since you're not technically downgrading which would require an unlocked bootloader. Just follow all the commands on Motorola's website.
Sent from my XT1095 using Tapatalk

There is nothing you can do. This is an anti-theft protection. You need to contact the seller and have him login to the account... then after that, the account can be removed. If the seller does not help you, then sorry to say but you have a paperweight because there is absolutely no way around this.
Sent from my XT1095 using Tapatalk

AGISCI said:
There is nothing you can do. This is an anti-theft protection. You need to contact the seller and have him login to the account... then after that, the account can be removed. If the seller does not help you, then sorry to say but you have a paperweight because there is absolutely no way around this.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Not quite...I got motorola to accept it under warranty to replace it. The IEMI says the phone was bought in Feb. 2015, so it still has a chunk of warranty left on it.

That surprises me... so if I steal a motorola phone that still has warranty they will send me a replacement that is unlocked just because it is under warranty? Seems like that is a huge problem.
Sent from my XT1095 using Tapatalk

AGISCI said:
That surprises me... so if I steal a motorola phone that still has warranty they will send me a replacement that is unlocked just because it is under warranty? Seems like that is a huge problem.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Is that really a huge problem? They will know who claimed the warranty and I'm sure can notice if anyone is abusing that. Not perfect, but not terrible either. Besides, when the phone is turned in for a warranty, how does Moto know that the reason it's locked out is not due to my own google account?

Supposedly the warranty is only with proof of purchase, which you don't have since you bought it from someone else on ebay. That is a big issue because that undermines the whole reason for having this option on the phone.
Sent from my XT1095 using Tapatalk

AGISCI said:
Supposedly the warranty is only with proof of purchase, which you don't have since you bought it from someone else on ebay. That is a big issue because that undermines the whole reason for having this option on the phone.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
The person on ebay ran a storefront and I have a receipt from it - I did buy it. The warranty doesn't say you can't buy it from a 3rd party, nor does it say you have to to be the first end-user.

darkprime said:
The person on ebay ran a storefront and I have a receipt from it - I did buy it. The warranty doesn't say you can't buy it from a 3rd party, nor does it say you have to to be the first end-user.
Click to expand...
Click to collapse
Mototola's warranty:
https://www.google.com/url?q=https:...6FUuSQ&usg=AFQjCNEGjgEU48cZkqSs2Y72u8W2SgI-mw
The very first thing it says is that it is for the first owner only and is non transferrable.
Sent from my XT1095 using Tapatalk

AGISCI said:
Mototola's warranty:
https://www.google.com/url?q=https:...6FUuSQ&usg=AFQjCNEGjgEU48cZkqSs2Y72u8W2SgI-mw
The very first thing it says is that it is for the first owner only and is non transferrable.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Ok, I stand corrected, but Moto doesn't know if I was the first end user or not. I'm sure I wasn't, but good businesses will honor warranties even when technically against the agreement, terms, or expiration.
Anyways, back on topic - if someone knows of something else I can try while I still have the phone, I would like to hear it.

XT1095 US Hard Brick

Long story short but I tried to revert back to stock in order to take the MM ota update but this resulted in me downgrading my bootloader and this hard bricked my phone.
I am aware of "blankflash" that can fix hard bricked 2013 versions of this phone but apparently there are no blankflash files which can restore this phone.
To my knowledge there is no other way to fix a hard bricked moto x 2014 (I really want to be wrong about this and would love if someone could provide info on how to fix).
I tried to contact moto support for a replacement but my device is 2 weeks out of warranty so no dice they will not help me and want me to pay $125 for a repair.
Is there anything I can do? Or should I start looking for a new phone....

madkapitolist said:
Long story short but I tried to revert back to stock in order to take the MM ota update but this resulted in me downgrading my bootloader and this hard bricked my phone.
I am aware of "blankflash" that can fix hard bricked 2013 versions of this phone but apparently there are no blankflash files which can restore this phone.
To my knowledge there is no other way to fix a hard bricked moto x 2014 (I really want to be wrong about this and would love if someone could provide info on how to fix).
I tried to contact moto support for a replacement but my device is 2 weeks out of warranty so no dice they will not help me and want me to pay $125 for a repair.
Is there anything I can do? Or should I start looking for a new phone....
Click to expand...
Click to collapse
Sorry, there is nothing you can do to fix a hard brick.
Sent from my XT1095 using Tapatalk

madkapitolist said:
Long story short but I tried to revert back to stock in order to take the MM ota update but this resulted in me downgrading my bootloader and this hard bricked my phone.
I am aware of "blankflash" that can fix hard bricked 2013 versions of this phone but apparently there are no blankflash files which can restore this phone.
To my knowledge there is no other way to fix a hard bricked moto x 2014 (I really want to be wrong about this and would love if someone could provide info on how to fix).
I tried to contact moto support for a replacement but my device is 2 weeks out of warranty so no dice they will not help me and want me to pay $125 for a repair.
Is there anything I can do? Or should I start looking for a new phone....
Click to expand...
Click to collapse
Was your bootloader unlocked? Can you boot to the bootloader?

rsa 329 said:
Was your bootloader unlocked? Can you boot to the bootloader?
Click to expand...
Click to collapse
Yes bootloader was unlocked, seems like the consensus is that its dead until moto releases the blankflash files for this phone. Oh well live and learn. I cannot boot into fastboot and adb does not detect the device.

madkapitolist said:
Yes bootloader was unlocked, seems like the consensus is that its dead until moto releases the blankflash files for this phone. Oh well live and learn. I cannot boot into fastboot and adb does not detect the device.
Click to expand...
Click to collapse
I also have a pure edition XT1095 with an unlocked bootloader and reflashed to stock to take the Marshmallow OTA and bricked my phone. I used the Multi Tool V4.1 which flashed my phone from 5.1 to 4.2.2. It booted fine and started the OTA of either 5.0 or 5.1 which was when everything went to hell. I can't get to recovery mode and I'm pretty pissed. I've ordered a Nexus 6P and have put Motorola on my short list of companies I will no longer do business with as they have the drivers and utilities to fix the phone but do not release them. Yeah, I'm guessing it had to do with the bootloader not being able to go back to 4.2.2 and don't need to hear that. The point is that it is a non-subsidized pure edition phone and an OTA should not be able to hard brick the phone.

RobbieDowie said:
I also have a pure edition XT1095 with an unlocked bootloader and reflashed to stock to take the Marshmallow OTA and bricked my phone. I used the Multi Tool V4.1 which flashed my phone from 5.1 to 4.2.2. It booted fine and started the OTA of either 5.0 or 5.1 which was when everything went to hell. I can't get to recovery mode and I'm pretty pissed. I've ordered a Nexus 6P and have put Motorola on my short list of companies I will no longer do business with as they have the drivers and utilities to fix the phone but do not release them. Yeah, I'm guessing it had to do with the bootloader not being able to go back to 4.2.2 and don't need to hear that. The point is that it is a non-subsidized pure edition phone and an OTA should not be able to hard brick the phone.
Click to expand...
Click to collapse
The xt1095 has a warranty, you can send it in for repair. As far as as downgrading, in the upgrade descriptions it clearly states you cannot downgrade to an earlier version. You ignored that message or didn't read it and flashed 4.4.4. That isn't motorola's fault. However the pure xt1095 does not lose it's warranty when you unlock the bootloader, so they will fix it if you contact them and send it in. They just don't give us the tools to fix it ourselves, but that does not mean you have no options.
Sent from my XT1095 using Tapatalk

AGISCI said:
The xt1095 has a warranty, you can send it in for repair. As far as as downgrading, in the upgrade descriptions it clearly states you cannot downgrade to an earlier version. You ignored that message or didn't read it and flashed 4.4.4. That isn't motorola's fault. However the pure xt1095 does not lose it's warranty when you unlock the bootloader, so they will fix it if you contact them and send it in. They just don't give us the tools to fix it ourselves, but that does not mean you have no options.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Seriously? First off, the phone is out of warranty. Secondly, I don't know what upgrade descriptions you're talking about. I didn't ignore anything. I used a tool I got from these forums that had no warning. This is an honest mistake I'll guarantee others will make and to suggest they are stupid is just rude. After it happened I guessed it was due to downgrading to 4.4.4 but by then it was too late. For the phone to be so fragile that you can brick it this way is ridiculous and unacceptable that there is a tool Motorola has that would fix it but they do not make available.
Thanks for the helpful feedback. I was trying to share but now see I was wasting my time.

You might want to join the conversation going on at reddit over here I think you can go back to 5.1 by flashing the whole 5.1 image via the bootloader (including erasing userdate and cache) - I say so because that is what I did but some people say it will not work and to be honest now I'm losing confidence in my memory.... Hope we could get more insight, or at least get the official 6.0 bootloader image from moto soon.

RobbieDowie said:
Seriously? First off, the phone is out of warranty. Secondly, I don't know what upgrade descriptions you're talking about. I didn't ignore anything. I used a tool I got from these forums that had no warning. This is an honest mistake I'll guarantee others will make and to suggest they are stupid is just rude. After it happened I guessed it was due to downgrading to 4.4.4 but by then it was too late. For the phone to be so fragile that you can brick it this way is ridiculous and unacceptable that there is a tool Motorola has that would fix it but they do not make available.
Thanks for the helpful feedback. I was trying to share but now see I was wasting my time.
Click to expand...
Click to collapse
Well....apparently you haven't read much more in this forum, this downgrading brick is common and its often asked by the other. You cant downgrade from lollipop to kitkat. So, if you had read more deeper in this forum, you could prevent this hard brick. And many member forget that this is not nexus device, and yes flashing or upgrading will have risk of hard brick.
Sent from my XT1095 using Tapatalk

bimasakti85 said:
Well....apparently you haven't read much more in this forum, this downgrading brick is common and its often asked by the other. You cant downgrade from lollipop to kitkat. So, if you had read more deeper in this forum, you could prevent this hard brick. And many member forget that this is not nexus device, and yes flashing or upgrading will have risk of hard brick.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I actually knew downgrading was a bad idea and didn't intend on doing it. I used the MOTO_X_2014_PURE_MULTI_TOOLV4.1 which I had used in the past but didn't remember it was going to flash back to 4.2.2. The instructions on the page just say FLASH BACK TO TOTAL STOCK UNRROOTED ROM AND RECOVER-FULL-WIPE. It doesn't say anything about going to 4.2.2. When it said it was downgrading when I ran it I thought "oh, oh" but it was too late. I was trying to provide information in this thread because I hoped it would be helpful, e.g. DON'T USE THE MULTI_TOOLV4.1!. I specifically said "I'm guessing it had to do with the bootloader not being able to go back to 4.2.2 and don't need to hear that" and what do I get? "...You ignored that message or didn't read it..." I'm already pretty grumpy about my mistake and bricking my phone and to get this kind of lashing isn't appreciated.

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

New update bootloops my phone, help please!

Hey guys, so my mom was using the Turbo yesterday when she was prompted to an update. Now according to a few searches there was a soak test out or something? Not sure, since I have the Turbo 2. But regardless, she went to apply the update and now that phone won't boot up. It lights up with the M logo screen and then goes to andy where he's got the rotating box in his belly, and underneath it says "Erasing...". I can't get to any of the other options from the screen where you hold Volume Down while powering up. All of the options lead to the same erasing screen. The phone will reboot after two or three minutes and go back to the same thing. Been doing this for hours. I have it sitting on a charger and will take a look at it when I come back from work but I'm wondering how to remedy this? I am familiar with RSD lite and can use it to flash the phone if I can figure out which files to use. Not familiar with ADB so if that's the route I have to go, I'd appreciate a write up on how to use it. Willing to install custom firmware if I have to as well. I just need to get the phone working asap. My mom works nights and she is currently phoneless, so this is a safety concern of mine.
Also that screen where you hold Volume Down, it says battery okay and all that but it says the phone software is modified. Not sure why, I know that she completely incapable of doing that. And I didn't modify anything when I had the phone. Not that is matters though, it's out of warranty so Verizon or Moto probably won't be too useful.
Any and all help appreciated. Currently not in the position to buy a new phone so I'd prefer fixing this one up if I can. Thanks!

Xelios029 said:
I am familiar with RSD lite and can use it to flash the phone if I can figure out which files to use.
Click to expand...
Click to collapse
Is the phone pure stock? You've never unlocked the bootloader via Sunshine nor installed TWRP custom recovery?
If so, then this is the full firmware version of the most recent update that you would flash via RSD.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
It should fix your phone -- but you will not be able to unlock the bootloader and install custom recovery because the update blocks Sunshine. If you had wanted an unlocked bootloader you should have done it before now.

Never, which is why I'm confused why it says software status modified. The sunshine and mofo mods were released after I upgraded to the turbo 2 so I never even had a chance. But thank you though! Really appreciate it, I was scared that some part of the memory had failed or something. My only question from here is how do I get the phone into the mode to required to RSD it? Because even if I select the bootloader option from that screen where you hold volume down while powering up, it goes to that erasing screen no matter what.
EDIT: Got home from work and downloaded all the files. RSD 6.1.5, Motorola Device Manager for the drivers, and the FXZ file. No dice. It won't recognize the device in RSD even though windows is making that sound when a device is connected. No luck on RSDLite 6.2.4 either.
EDIT2: Okay ugh, now I don't know what to do. Turns out RSD didnt detect it because the cable was not directly plugged into the motherboard. Took me a while to figure that out. So I got it detected and I flashed that file you put above and I'm still having the same problem. It reboots once everything is finished flashing and then goes back to the "Erasing..." screen.
EDIT3: SUCCESS!!! Thank you so much! I swear I was thinking I was going to have to replace the phone. Let it sit at the Erasing screen after flashing it for a bit and it eventually rebooted itself and started the Droid splash screen. What a huge relief! Hopefully these updates help with someone else who may run into the same problem.

Glad it worked for you!
And it helped you were persistent.

ChazzMatt said:
Glad it worked for you!
And it helped you were persistent.
Click to expand...
Click to collapse
Thanks again, much appreciated!

ChazzMatt said:
Is the phone pure stock? You've never unlocked the bootloader via Sunshine nor installed TWRP custom recovery?
If so, then this is the full firmware version of the most recent update that you would flash via RSD.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
It should fix your phone -- but you will not be able to unlock the bootloader and install custom recovery because the update blocks Sunshine. If you had wanted an unlocked bootloader you should have done it before now.
Click to expand...
Click to collapse
Do you think sunshine will update the unlock bootloader for MCG24.251-5-5[
Sent from my XT1254 using Tapatalk

KARIM9377 said:
Do you think sunshine will update the unlock bootloader for MCG24.251-5-5[
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
You have to ask them. I don't know. But we've been surprised before by their talent.

ChazzMatt said:
you have to ask them. I don't know. But we've been stories surprised before by their talent.
Click to expand...
Click to collapse
Yes I did I ask
*@beaups and he told me that they will try if they have time for it
Put I asking for is ? did Verizon black the patch that sunshine can unlock bootloader with it ?
I hope they don't and I hope sunshine will do it and update

KARIM9377 said:
Yes I did I ask
*@beaups and he told me that they will try if they have time for it
Put I asking for is ? did Verizon black the patch that sunshine can unlock bootloader with it ?
I hope they don't and I hope sunshine will do it and update
Click to expand...
Click to collapse
Every time Sunshine released an update to force unlock the Droid Turbo bootloader, Verizon releases an OTA "security update" to block it.
This next rant is not towards you but to other longtime Droid Turbo owners... (Like anyone who has owned a Droid Turbo for over two months. Anywhere from 2 months - 2 years.)
People just need to UNLOCK their bootloaders before taking any updates. NEVER, NEVER, NEVER take an OTA update. If there's anything worthwhile it will be posted HERE on XDA and you can flash it manually. Just unlock your bootloader and you don't have to worry about Verizon "blocking" Sunshine because your bootloader will already be unlocked!