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!
Related
if I have already upgraded to kit kat 4.4.2? I take it that since the 4.4.2 OTA hasn't been pushed for my Verizon Dev Ed device, that the factory images I have been given by Motorola are for 4.4.
But once the 4.4.2 OTA is pushed, the factory images I have now would be out of date because those are for 4.4., right? Then will Motorola release 4.4.2 factory images later?
Also, what does it mean when in bootloader mode it says Device is UNLOCKED. Status Code: 3. What is the status code 3?
Cozume said:
if I have already upgraded to kit kat 4.4.2? I take it that since the 4.4.2 OTA hasn't been pushed for my Verizon Dev Ed device, that the factory images I have been given by Motorola are for 4.4.
But once the 4.4.2 OTA is pushed, the factory images I have now would be out of date because those are for 4.4., right? Then will Motorola release 4.4.2 factory images later?
I have a verizon unlocked dev ed. Also, what does it mean when in bootloader mode it says Devide is UNLOCKED. Status Code: 3. What is the status code 3?
Click to expand...
Click to collapse
It gives you the stock recovery, the stock system image with all the applications, and the ability to update over the air (OTA). People re-flash the factory images either when they think they messed up their phone, or when they want the latest update via OTA instead of waiting for a SBF package. In short, it returns the phone to the default/non modded status.
I am fairly certain that a SBF will be made for 4.4.2, it just is taking a bit longer this time, maybe they are busy, especially since there is no new updates around the corner any time soon. Since you have already updated to 4.4.2 (like myself) there is no way to go back to stock unless you have made a recovery image in TWRP/CWM. Then all you have to do to update, is reflash the stock recovery image and then you can take a system OTA.
The bootloader on this phone cannot be downgraded, due to the eFuse system incorporated into it. If you attempt to load a lower bootloader in RSD Lite, it will simply fail to install and nothing else bad will happen, however, if you force the bootloader overwrite then you have a nice new paperweight (aka hard brick), because this trips the eFuse.
Status code 3 is basically the computer flag telling the future firmware updates that your bootloader has already been unlocked, so if you update using that same carrier/firmware, you don't lose your unlocked bootloader status. Another reason why you need to simply stick with your own firmware. As there have been reports that loading another regions/phones firmware can lock your bootloader again because the flag isn't there.
mastarifla said:
In short, it returns the phone to the default/non modded status.
Click to expand...
Click to collapse
It restores everything I modded? I erased the clogo.bin file and then I think I flashed with some other bin file to clogo and of course, didn't save a backup. Now I can't get the Kit Kat easter egg when I tap the build version so clearly it has something to do with the clogo file I messed with. I can live without the easter egg, but I don't want to brick my device. So I guess I should just flash the factory images and see what happens.
mastarifla said:
The bootloader on this phone cannot be downgraded, due to the eFuse system incorporated into it. If you attempt to load a lower bootloader in RSD Lite, it will simply fail to install and nothing else bad will happen, however, if you force the bootloader overwrite then you have a nice new paperweight (aka hard brick), because this trips the eFuse.
Click to expand...
Click to collapse
and even if your bootloader is unlocked, you have a hard brick and there is no way to correct that?
mastarifla said:
Status code 3 is basically the computer flag telling the future firmware updates that your bootloader has already been unlocked, so if you update using that same carrier/firmware, you don't lose your unlocked bootloader status. Another reason why you need to simply stick with your own firmware. As there have been reports that loading another regions/phones firmware can lock your bootloader again because the flag isn't there.
Click to expand...
Click to collapse
If my bootloader were to ever get locked again, can't I use the same 20 digit unlock key that Motorola emailed me to unlock it?
Many thanks again, and sorry I cannot hit the thanks button until tomorrow!
Cozume said:
It restores everything I modded? I erased the clogo.bin file and then I think I flashed with some other bin file to clogo and of course, didn't save a backup. Now I can't get the Kit Kat easter egg when I tap the build version so clearly it has something to do with the clogo file I messed with. I can live without the easter egg, but I don't want to brick my device. So I guess I should just flash the factory images and see what happens.
Click to expand...
Click to collapse
If you are already on 4.4.2 then you can flash the 4.4.2 "factory image" when it is released and it should be fine/back to normal.
Cozume said:
and even if your bootloader is unlocked, you have a hard brick and there is no way to correct that?
Click to expand...
Click to collapse
Correct, all the phones have the same eFuse system, even the developer phones. This "supposedly" prevents people from screwing up their phones more. (Personally I think it's silly, but I also have a Nexus, so it doesn't bother me).
Cozume said:
If my bootloader were to ever get locked again, can't I use the same 20 digit unlock key that Motorola emailed me to unlock it?
Many thanks again, and sorry I cannot hit the thanks button until tomorrow!
Click to expand...
Click to collapse
You should be able to (if you still have your IMEI), however there are reports that some people are losing their IMEI too, if this gets lost and there is no way to recover it then you are out of luck, because in order to unlock the bootloader it has to verify that the code works for your IMEI (which is carrier specific).
mastarifla said:
Correct, all the phones have the same eFuse system, even the developer phones. This "supposedly" prevents people from screwing up their phones more. (Personally I think it's silly, but I also have a Nexus, so it doesn't bother me).
Click to expand...
Click to collapse
It seems like the eFuse is the cause of people screwing up their phones. I suppose they do these sorts of things to satisfy potential corporate customers who want secure devices for their corporate communications.
mastarifla said:
You should be able to (if you still have your IMEI), however there are reports that some people are losing their IMEI too, if this gets lost and there is no way to recover it then you are out of luck, because in order to unlock the bootloader it has to verify that the code works for your IMEI (which is carrier specific).
Click to expand...
Click to collapse
Wow, that is awful but can't an IMEI be restored somehow if you know what it is? I not only have my box, Verizon has all my IMEI's stored on their system.
Cozume said:
It seems like the eFuse is the cause of people screwing up their phones. I suppose they do these sorts of things to satisfy potential corporate customers who want secure devices for their corporate communications.
Click to expand...
Click to collapse
Sadly corporate security is much less of a concern to them and actually something else entirely (see Samsung's encryption protocol for enterprise - SAFE). Motorola doesn't want to bother with supporting people on lower firmwares, and this prevents them from having to worry about it because they will always require you to be on the latest firmware for support, this eFuse system basically prevents people from using exploits in previous versions of the system (aka getting root on a non-unlocked phone, etc).
Cozume said:
Wow, that is awful but can't an IMEI be restored somehow if you know what it is? I not only have my box, Verizon has all my IMEI's stored on their system.
Click to expand...
Click to collapse
If you have your EFS files backed up then you are okay, you can just restore it and you are good to go again. However, the IMEI is a secure file, so you cant make a new one if its gone (nor can your cell company), this system in effect prevents people stealing phones and changing the IMEI in order to not be blacklisted. This system is in place for a very good reason, while not perfect (try selling a used phone to someone who understands this), its the best deterrent against theft currently available.
mastarifla said:
If you have your ESF files backed up then you are okay, you can just restore it and you are good to go again.
Click to expand...
Click to collapse
If I do a nandroid backup does it back those files up? if not, what can I use to back them up?
Also, I will have to come back tomorrow and the next day to hit the thanks button because I will use up all my thanks again tomorrow on you, lol!
Cozume said:
If I do a nandroid backup does it back those files up? if not, what can I use to back them up?
Also, I will have to come back tomorrow and the next day to hit the thanks button because I will use up all my thanks again tomorrow on you, lol!
Click to expand...
Click to collapse
There are tools available to backup your EFS partition in case a nandroid doesn't work correctly. Some CWM/TWRP versions do EFS partition backups, some don't, be sure to read through the threads and make sure. Asking a question goes a long way.
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.
Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Resurrecting A Bricked Moto X
drvoje said:
Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Is there any way to try to delete chache or factory reset before flashing to stock rom
drvoje said:
Is there any way to try to delete chache or factory reset before flashing to custom rom
Click to expand...
Click to collapse
If its not the developer edition for Verizon, the bootloader is likely locked, so you can NOT flash custom roms (unless you, or a previous owner, got a bootloader unlock code from the China Middleman and used it)
Did you buy the phone used, or new? If used, then it is possible that it was rooted using RockMyMoto, SlapMyMoto or the like... and the boot loop while trying to install an update could be due to that. If so, erasing cache will stop the boot loop. This can be done from stock recovery, or when in Bootloader/FastbootAP mode.
How to Boot into recovery -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
If that doesn't work, try bootloader/fastboot....
How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup -> http://mark.cdmaforums.com/ADB.htm
How to boot the phone into fastboot mode -> http://mark.cdmaforums.com/MotoX-BootloaderMode.htm
from your PC, do a mfastboot erase cache
to reboot the phone, mfastboot reboot
Optionally, you could do a mfastboot erase userdata before rebooting, to remove all data, apps, etc.
If erasing cache fixes the boot loop, you might just want to try using RSDLite and reflashing the STOCK rom, recovery, etc. (Download the Verizon 4.4.4 SBF from -> http://sbf.droid-developers.org/phone.php?device=0 then follow -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 ) It would undo anything that was done to root your device, and put you back to factory fresh. The only reason not to, would be if you care about rooting and disabling write protection..
With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader).
Once your phone is on 4.4.2 or above, you can't properly downgrade the ROM, bootloader and gpt.bin to use the exploits used by SlapMyMoto/MotoWpNoMo. There is a TowelPieRoot which is a temp root that works on 4.4.2. Temp root in the fact that it doesn't survive power off/on, so it needs to be redone each time. Also it doesn't disable write protection, so any changes made to /system or the like are also lost at power off/on (aka hard boot).
Once on 4.4.4, you can't properly downgrade the ROM, bootloader and gpt.bin, and there are no exploits to root, and no way to disable write protection.
If you can use the China Middleman thread to get a bootloader unlock code, then you don't need to worry about the exploits, and you can then root and disable write protection just as if you had a developer edition. Also JCASE may be updating their Sunshine tool to use the exploit found by Dan Rosenberg to unlock the bootloader on the Moto X, but there is no exact date yet of when it will be available (so far "next few weeks" has been said, but nothing more specific), and there is discussion around will it work for those who took the 4.4.4 update or not (no confirmation yet either way).
KidJoe;55503494
If that doesn't work said:
[*]How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup ->
[*]How to boot the phone into fastboot mode ->
[*]from your PC, do a mfastboot erase cache
[*]to reboot the phone, mfastboot reboot
[/list]
Click to expand...
Click to collapse
did this with mfastboot image and worked like charm
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
and tnx for the help again mate
drvoje said:
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
Click to expand...
Click to collapse
You said its a verizon phone, but not the developer edition..
So at this point, the only way to unlock the bootloader is the China Middleman thread (in the general section). When JCASE updates Sunshine for the X (in the coming week or two), you can try that.
Otherwise, there isn't anything you can do.
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
drvoje said:
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
Click to expand...
Click to collapse
THe best depends on what you want to do.
Like I said before. IF you have 4.4 (aka 4.4.0) on the phone, and NEVER had anything newer on there (not 4.4.2 or 4.4.4), then stay there, look at SlapMyMoto and MotoWpNoMo to root and disable write protection.
Once you get 4.4.2 on there, you can root, but its temp root, and write protection can NOT be disabled.
4.4.4 you can't root.
Other than that, I can't say I really find too much difference. The camera is better in 4.4.4, but the battery isn't performing as well lately (could be a recent app update).
can i do this on my phone now - without fear of bricking it:
from my pc to run mfastboot again
then to clear chache
then to delete all user data
then to use rsd lite and flash Android 4.4
Blur_Version.140.45.5.ghost_verizon.Verizon.en.US even i alrdy have 4.4 now?
..because i dont know what is done to my phone before and i want to make sure its like "new" device
i know i can not downgrade, but can i flash same frimware? just to make sure thats all stock again
bdw Im stll unable to enter recovery after fastboot :/ is it that because of locked bootloeader? or because it was rooted with any method? i cant find superuser
and then to wait for solution to unlock bootleader?
Thanks in advance
You can always re-flash the same rom that is on your phone.
You just never want to down grade, or flash something older than what is on your phone.
As for not being able to enter Stock Recovery... early versions of the RockMyMoto and such did a trick which made it so that when you picked boot to recovery, it booted to regular system with write protection disabled. If that was used on your phone before you purchased it, that could be the issue. Using RSDLite and flashing back to 100% stock will undo that.
But You never answered if you got the phone new or used.
IF new, then you have some other issue (either you're not doing it right, or there is something wrong with the phone).
If used, you don't know what was done before you received it. Someone might have rooted, etc.. then just removed SuperSU to appear non-rooted when selling, rather than flashing back to stock.
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i made this screenshots, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
drvoje said:
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i found this screenshot in phone, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
Click to expand...
Click to collapse
If you mean you don't see a SuperSU icon in the app drawer, then they probably un-installed SuperSU before selling it rather than completely unrooting. If you mean you have an icon in the app drawer, but don't see it to uninstall under Settings -> Apps.. I don't know why that would be.
drvoje said:
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
Click to expand...
Click to collapse
Yes, that could be what happened to you. There are many reports of locked bootloader users who used those older root processes who then upgraded using the OTA from 4.4 to 4.4.2 that encountered bootloops and other issues. It was often recomended to reflash to 100% stock.
And what I meant is that if you are on 4.4 (aka 4.4.0) with all its parts, it is vulnerable and the older exploits can still be used to root and disable write protection without unlocking your bootloader. Search for SlapMyMoto for more details. Some people tried to be cute and mix/match parts which caused issues. Mostly the issues around downgrading are caused by GPT.BIN and Motoboot.IMG parts, their versions, if they've been upgraded and no longer match the rest of the rom on the phone, etc. (and that is a LONG story...)
drvoje said:
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
Click to expand...
Click to collapse
You can TRY using something like LTE On/Off to open the hidden menu and set for GSM Auto (PRL) or LTE GSM Auto(PRL). I'm not sure which would work best.
Oh, and as for unlocking the bootloader, I've mentioned the China Middleman and JCASE's Sunshine so there are the links to read up if you want to do it.
The China Middleman is just like if you got the code directly from Moto. I don't know what the Jcase tool is like yet.
thanks again!
so i dont see a SuperSU icon in the app drawer - uninstalled probably and that is why i can not enter stock recovery
I am still on android 4.4 didnt do anything yet...
what u recommend me to do? to rsd lite it to 4.4 again? right?
than i will root my device
and about bootloader, my device is 9.2013, so i will wait JCASE's Sunshine and support him
ps. wiget works gr8 :good:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Now you can update to 4.4.4,whichever methods you want, and still root it. Done. ?
drvoje said:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Click to expand...
Click to collapse
Follow [mention]@KJ[/mention] 's advice and update to 4.4.4, and follow the Dev Edition or Unlocked Bootloader guides to rooting (flash the latest TWRP and root.)
In addition to completing the poll, please leave more specific information if you can - i.e., bricked downgrading from Lollipop to Kit Kat, took an OTA without flashing back to stock, was able to recover by doing xyz, was not able to recover, screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD, had to do a warranty replacement, etc.
Edited - if you could post a follow up post with specifics after you vote, that would be great.
To the person who bricked after taking an OTA - did you not flash back to stock first? Or had you upgraded, then flashed backed to stock on a lower version (downgraded) and then took the OTA? What versions were you upgrading b/t?
To the person who bricked when they were downgrading - did you try to downgrade the bootloader? What versions were your downgrading b/t?
JulesJam said:
In addition to completing the poll, please leave more specific information if you can - i.e., bricked downgrading from Lollipop to Kit Kat, took an OTA without flashing back to stock, was able to recover by doing xyz, was not able to recover, screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD, had to do a warranty replacement, etc.
Click to expand...
Click to collapse
You should add "I'm too lazy to read." as an option in your poll.
badams1 said:
You should add "I'm too lazy to read." as an option in your poll.
Click to expand...
Click to collapse
I don't think that is the problem here. Motorola has not told anyone not to attempt to downgrade the bootloader and supposedly mfastboot will prevent a bootloader from being downgraded. Moreover, supposedly checks were put in the OTA script that would just cause it to fail if you were not entirely stock when you took the OTA. But obviously, people are still bricking downgrading and taking OTAs so somehow either fastboot or mfastboot is not preventing bricks and likewise the OTA script hasn't been perfected to prevent bricks.
At the end of the day, the real problem is in designing an OS that will brick if the BL is downgraded. They do that so that if they patch security holes in the bootloader, you can't then go back to an insecure earlier version. It is fine to block downgrades, but terrible that it bricks the phone.
Also, as far as not reading, I posted a warning post about the risks of downgrading the bootloader or partition table and lots of people are posting on that thread disputing that. So people don't know what to think.
bump
bump.
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
r4ph431 said:
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
Click to expand...
Click to collapse
There is no way to unbrick it.
r4ph431 said:
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
Click to expand...
Click to collapse
This has to go back to motorola and get a warranty replacement. It could be fixed if they would release a couple of files to us but they haven't so far.
r4ph431 said:
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
Click to expand...
Click to collapse
Was it an actual XT1095 or a converted one? Which 5.1 where you on the original or the current or did you attempt the Brazilian? was your bootloader 60.14 or 60.16 ? did you fastboot flash partition gpt.bin and
fastboot flash motoboot motoboot.img ? If so did they not fail? and lastly you didn't attempt to lock your bootloader after the downgrade? for some reason people are trying this and even though it doesn't appear to be doing anything it just might causing an issue. There is no reason to attempt to relock your boot loader on the XT1095 it's the pure edition and warranty is not voided. When did it go black ? Was it during the 5.0 upgrade or after the reboot?
Try this site
http://www.usoftsmartphone.com/t300062.html
wolfu11 said:
Was it an actual XT1095 or a converted one? Which 5.1 where you on the original or the current or did you attempt the Brazilian? was your bootloader 60.14 or 60.16 ? did you fastboot flash partition gpt.bin and
fastboot flash motoboot motoboot.img ? If so did they not fail? and lastly you didn't attempt to lock your bootloader after the downgrade? for some reason people are trying this and even though it doesn't appear to be doing anything it just might causing an issue. There is no reason to attempt to relock your boot loader on the XT1095 it's the pure edition and warranty is not voided. When did it go black ? Was it during the 5.0 upgrade or after the reboot?
Click to expand...
Click to collapse
It is a converted xt1092, the germen variant. I converted it and after this i flashed the offical US 5.1 OTA (from here). After this i got a bootloop due to a problem with xposed and root.
So as stupid as i was,i just reflashed all the 4.4 files (xt1095 variant, with adb/fastboot from the sdk) with the motoboot and the gpt.bin, because i had them downloaded on my pc. After this i could boot again. Then I tried to take the OTA to 5.0 .11 . After this the device tried to reboot, but never booted and was hard bricked.
To the other questions, i dont know the version of my bootloader and i didnt tried to relock it.
r4ph431 said:
It is a converted xt1092, the germen variant. I converted it and after this i flashed the offical US 5.1 OTA (from here). After this i got a bootloop due to a problem with xposed and root.
So as stupid as i was,i just reflashed all the 4.4 files (xt1095 variant) with the motoboot and the gpt.bin, because i had them downloaded on my pc. After this i could boot again. Then I tried to take the OTA to 5.0 .11 . After this the device tried to reboot, but never booted and was hard bricked.
To the other questions, i dont know the version of my bootloader and i didnt tried to relock it.
Click to expand...
Click to collapse
I'd give this site a try since you're already bricked.
http://www.usoftsmartphone.com/t300062.html
wolfu11 said:
Try this site
http://www.usoftsmartphone.com/t300062.html
Click to expand...
Click to collapse
Thanks i gone try this as soon as i am home from work and then report back if it helped.
r4ph431 said:
Thanks i gone try this as soon as i am home from work and then report back if it helped.
Click to expand...
Click to collapse
That site is a site that just repeats XDA posts and the post quoted to you was deleted by the author b/c the files that were posted were for a Snapdragon 400 (MSM8626). I don't know what those files will do to your device.
This was the original thread on XDA:
http://forum.xda-developers.com/moto-x-2014/general/guide-unbrick-hard-bricked-moto-x-2nd-t2966017
Same here
r4ph431 said:
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
Click to expand...
Click to collapse
I have the same problem dude. ¿any progress?
r4ph431 said:
I downgraded from 5.1 on my XT1095 to 4.4 and then took the OTA to 5.0, this bricked it. Wasnt able to unbrick it until now. Screen is black, can't get into bootloader mode, device only recognized as QHSUSB_DLOAD.
Anyone an idee how to unbrick?
Click to expand...
Click to collapse
Why don't you get a warranty replacement? The XT1095 is covered by the warranty even if you unlock the bootloader.
JulesJam said:
Why don't you get a warranty replacement? The XT1095 is covered by the warranty even if you unlock the bootloader.
Click to expand...
Click to collapse
Its a converted xt1092(see me second answer) so its not covered.
Besides that motorola support told me it isnt covered under the support, not even on the xt1095. They stated it is against their tos and they wont repair it, not even when you pay them.
Sent from my D6603 using Tapatalk
r4ph431 said:
Its a converted xt1092(see me second answer) so its not covered.
Besides that motorola support told me it isnt covered under the support, not even on the xt1095. They stated it is against their tos and they wont repair it, not even when you pay them.
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
That's not true in the US. In the US, the XT1095 gets warranty replacements no matter whether you unlocked or rooted.
Idk about Europe but I thought you had stronger consumer protection laws over there than we have here. I would look into it and not take No for an answer until you are sure that their policy is in-line with your consumer protection laws.
New hope here
JulesJam said:
That's not true in the US. In the US, the XT1095 gets warranty replacements no matter whether you unlocked or rooted.
Idk about Europe but I thought you had stronger consumer protection laws over there than we have here. I would look into it and not take No for an answer until you are sure that their policy is in-line with your consumer protection laws.
Click to expand...
Click to collapse
Im so glad to know that, i have a Moto XT1095 with unlocked bootloader, so today i contact the customer service via chat, they tried to helpe solve the problem, and when nothing gets better, the lady on the chat asked my IMEI, then she told me that it was still under warranty coverage, so i give her my shipping address, and now just waiting for a prepaid label to send my device for a "like new" replacement.
"Hi Ezequiel,
This is Jess from Motorola Chat Support. This is just a follow up email regarding your concern with us with reference number: 150606-001922. I just want to verify your shipping address for me to be able to process the replacement for you. Please provide me your complete shipping address. Feel free to respond to this email. Please let us know so that we can continue process your replacement.
Please feel free to chat back if you have further questions; we are open 24/7 to assist you. You may also call our Motorola Android Customer Service Department at 1-800-734-5870 during Mondays to Fridays 8am till 11pm and Saturdays and Sundays 10am till 7pm CST.
Thank you for choosing Motorola and have a nice day!"
ZekeMV said:
Im so glad to know that, i have a Moto XT1095 with unlocked bootloader, so today i contact the customer service via chat, they tried to helpe solve the problem, and when nothing gets better, the lady on the chat asked my IMEI, then she told me that it was still under warranty coverage, so i give her my shipping address, and now just waiting for a prepaid label to send my device for a "like new" replacement.
Click to expand...
Click to collapse
Good news!!!
JulesJam said:
Good news!!!
Click to expand...
Click to collapse
Thanks for this thread btw. I just bricked my device doing the same thing (5.1 OTA back to 4.4.4 factory image, black screen no bootloader/no response, QHSUSB_DLOAD shows up in device manager) and realized after finding this that that was the cause of the issue. I called customer support and will be receiving a replacement this week. It's not too bad b/c my usb port was starting to get janky so I was thinking of getting an RMA anyway so I would have had to spend the $25 on the advance RMA anyway (I really can't wait 2 weeks+ without a phone).
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.
Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk
SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.
TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.