Related
I'm not entirely sure how to troubleshoot this problem, but here goes...
I was charging my phone and it just attempted to reboot itself. I saw it in the corner of my eye and figured "oh well, let it finish". It never finished, and it seems it won't get past the boot screen.
I entered Fastboot mode. Device is still locked. It also states that the charger is connected, regardless of whether it is or isn't. Additionally, I cannot access Recovery or Factory, instead receiving the following error:
No valid PIV block in SP for system
piv validation failed (system)
Boot up failed
Click to expand...
Click to collapse
Anyone know what's going on here? Did my phone really just brick itself?
Edit: I apologize if my first post goes against any of the rules here. I've searched for a similar thread, but mostly found cases in which people failed to root and are receiving this message. I have some minor experience with rooting a Motorola Droid, Verizon Droid Incredible 2 and a Nexus 10. I was hoping to do the same with this phone, but it came with 4.4.2 already installed.
Don't take my word for it, but if you Google no valid piv moto x....it doesn't look good.
Then again if you read through some of the stuff you find, even other phones with issue....perhaps you'll stumble on a fix.
Last moto x thread I read with that error was solved by a replacement unfortunately.
Hope you find a fix, or can send it in. Your warranty should be in tact if its locked and unrooted.
As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition
SymbioticGenius said:
As kj mentioned, seek a replacement under warranty. If you are really looking to fix yourself. Unlock the bootloader and flash the latest stock ROM via fastboot.
I'd only try that if you can't get a warranty replacement cause unlocking the boot loader will kill your warranty unless you have a Dev edition
Click to expand...
Click to collapse
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!
samwathegreat said:
He doesn't need to unlock his bootloader to try to fastboot flash the lastest stock rom...
The Stock rom will flash just fine even locked because it's signed with release keys.
Try it!
Click to expand...
Click to collapse
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?
ed0421 said:
Thanks! I was hesitant to flash anything on this phone because I read people who had 4.4.2 were at risk of bricking their phones... but now that you've said it, it feels so obvious. I'll give this a try. Is there a standard go-to place for the stock ROM?
Click to expand...
Click to collapse
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.
samwathegreat said:
You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0
If you were on 4.4.2 before you bricked MAKE SURE you flash the 4.4.2 rom, and not a previous version.
Also remember that aside from a BL unlock, there will be no way of obtaining ROOT after this.
Download the correct file for your carrier and try to flash with RSD lite. Let us know what happens.
EDIT:
You can find a great guide here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Now that guide was made before 4.4.2 so it doesn't warn you not to flash a previous version. You've been warned... If you flash a pre-4.4.2 rom, you'll likely be perma-bricked.
Anyways, try the RSD Lite method. PAY CLOSE ATTENTION TO STEP 4 - editing the xml file
If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.
Since you ARE able to get into fastboot mode, I'm hopeful that this may work for you.
And finally, if you have problems with RSD lite, make SURE you have the USB drivers installed, and try another USB port if necessary.
Good Luck.
Click to expand...
Click to collapse
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!
I didn't have the same issue but I did just RMA my X for another reason and got a brand new 2014 X, was expecting a refurbished phone and was surprised to get a new one. They shipped it next day air that same day which also surprised me.
ed0421 said:
Hey, thanks for the effort! Unfortunately, it looks like my phone is completely bricked. I tried with RSD Lite, after making sure to edit the XML, and it failed when trying to flash the first file. "Failed flashing process. 2/17 flash parition "gpt.bin" -> Phone returned FAIL."
Figured I'd try with fastboot, and no luck there either.
Code:
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.978s
Looks like I'm gonna have to use my warranty. Thanks for taking the time to reply, though!
Click to expand...
Click to collapse
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat
samwathegreat said:
Usually (not always) when it errors out on gpt.bin, its because you're trying to flash a pre-4.4.2 image.
Hate to ask, but are you absolutely sure you downloaded the 4.4.2 rom?
And when you tried the manual method....you are executing the commands one at a time, right? Which part does it fail on? Flashing recovery? Because I see an error right above it - something about failed to erase....but erase what?
Good luck with your exchange if you must send it back...
-samwathegreat
Click to expand...
Click to collapse
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated
ed0421 said:
100% certain I downloaded the 4.4.2 rom, unfortunately. Flashing manually, it fails from the very first flash attempt. Only setting the oem fb_mode_set goes through without failure. Thanks for your help throughout this whole ordeal, it's very much appreciated
Click to expand...
Click to collapse
Really dumb question but when flashing... Are you using the command fastboot or mfastboot?
I had all kinds of errors and thought I was bricked too until I used mfastboot. Then everything went perfect. Moto uses their own version of fastboot.exe that's included in the sbf/fxz or whatever they are called now. Even the XML file states fastboot as the command but never worked for me. Just a thought.
Hello everyone. I made a noob mistake of misreading something for the 4.4 downgrade root and thought it said 4.4.2. So i attempted to downgrade from 4.4.2 with the sbf now some settings are messed up. I heard that if it didnt brick during the downgrade attempt it might brick getting an ota. I was wondering if using the 4.4.2 sbf woukd work to fix this problem or if this might cause a brick. Im on a verizon moto x . so to sum up question would the 4.4.2 sbf brick or fix a botched downgrade from 4.4.2
caramelbear said:
Hello everyone. I made a noob mistake of misreading something for the 4.4 downgrade root and thought it said 4.4.2. So i attempted to downgrade from 4.4.2 with the sbf now some settings are messed up. I heard that if it didnt brick during the downgrade attempt it might brick getting an ota. I was wondering if using the 4.4.2 sbf woukd work to fix this problem or if this might cause a brick. Im on a verizon moto x . so to sum up question would the 4.4.2 sbf brick or fix a botched downgrade from 4.4.2
Click to expand...
Click to collapse
You can pretty much always sbf up/forward to a newer version, it's trying to go down/backwards to an older version that can get you in trouble.
caramelbear said:
Hello everyone. I made a noob mistake of misreading something for the 4.4 downgrade root and thought it said 4.4.2. So i attempted to downgrade from 4.4.2 with the sbf now some settings are messed up. I heard that if it didnt brick during the downgrade attempt it might brick getting an ota. I was wondering if using the 4.4.2 sbf woukd work to fix this problem or if this might cause a brick. Im on a verizon moto x . so to sum up question would the 4.4.2 sbf brick or fix a botched downgrade from 4.4.2
Click to expand...
Click to collapse
Using the SBF of 4.4.2 is the best option. But because of the changes to motoboot and GPT.Bin in 4.4.2, and the attempt to downgrade, in most cases you will need to do a little more than just using RSDLite to flash the 4.4.2 SBF.
Consider visiting -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and using option 5. To play it safe, you might want to add a mfastboot erase userdata between the mfastboot erase cache and mfastboot reboot at the bottom of the list of commands. This WILL reset your phone to factory defaults and erase apps/data/settings too.
Hi people. I neen your help for booting my phone.
I had Stock 4.4.2, Moto X with camera update and Locked Bootloader, today I stupidly flashed a ROM 4.4.4, I know I have to be on UB, but I forgot it, it was an impulse. I got an error in the flashing, then I tried to flash my sbf Stock Version, but now it says Downgraded security something with gpt and I cannot flash anything, I mean starts flahsing but in boot.img it got stucked, please if someone tried the same and could help me please.
Thanks in advance.
icerebro said:
Hi people. I neen your help for booting my phone.
I had Stock 4.4.2, Moto X with camera update and Locked Bootloader, today I stupidly flashed a ROM 4.4.4, I know I have to be on UB, but I forgot it, it was an impulse. I got an error in the flashing, then I tried to flash my sbf Stock Version, but now it says Downgraded security something with gpt and I cannot flash anything, I mean starts flahsing but in boot.img it got stucked, please if someone tried the same and could help me please.
Thanks in advance.
Click to expand...
Click to collapse
Without Bootloader unlocking how can u flash a rom to your device thats first Mistake ... I think u cant back to u r device...
icerebro said:
Hi people. I neen your help for booting my phone.
I had Stock 4.4.2, Moto X with camera update and Locked Bootloader, today I stupidly flashed a ROM 4.4.4, I know I have to be on UB, but I forgot it, it was an impulse. I got an error in the flashing, then I tried to flash my sbf Stock Version, but now it says Downgraded security something with gpt and I cannot flash anything, I mean starts flahsing but in boot.img it got stucked, please if someone tried the same and could help me please.
Thanks in advance.
Click to expand...
Click to collapse
Mahesh8348 said:
Without Bootloader unlocking how can u flash a rom to your device thats first Mistake ... I think u cant back to u r device...
Click to expand...
Click to collapse
Yep, you are stuck until the full 4.4.4 SBF is released for your carrier. Shouldn't have done that.
Who is your carrier? If it is AT&T, you are in luck! The 4.4.4 SBF was just released. If not....bummer - you will have to wait. Can't flash a ROM with a different CID with a locked BL.
I highly suggest you don't attempt to manually force the older rom. Really, beyond the fact that you flashed the wrong ROM, how did you miss all the warnings that downgrade = brick?
Tough situation to be in. Hopefully you have an AT&T unit. If so, we can help get you fixed up.
Well, I have solved it Unlocking my Bootloader and then reinstalling the rom 4.4.4 retail from Brazil. It works now.
I have a question, now I am in Brazil but I am from Perú, and when I try to change the APN for the one I use in Perú, it deletes itself, so I can not change the APN or create a new one because i can not save it. What is the problem in there?
My phone was Nextel operator, then I unlock it, never had a problem.
Hope your help.
Thanks!
Hi Guys,
I am in a bit of a problem. My Moto X has unlocked bootloader and rooted with custom recovery (twrp). So i can't update to 4.4.4 from OTA so i want to unroot and lock my bootloader (going back to everything stock).
I tried this method but it failed at first two steps.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
The firmware which i am trying to install is:
"Android 4.4.2 Blur_Version.161.44.32.ghost_sprint.Sprint.en.US ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml"
My fastboot/bootloader with the error i am getting along with My phone information is attached below.
Need your help what should i do now.
Usama Ahmed said:
Hi Guys,
I am in a bit of a problem. My Moto X has unlocked bootloader and rooted with custom recovery (twrp). So i can't update to 4.4.4 from OTA so i want to unroot and lock my bootloader (going back to everything stock).
I tried this method but it failed at first two steps.
The firmware which i am trying to install is:
"Android 4.4.2 Blur_Version.161.44.32.ghost_sprint.Sprint.en.US ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml"
My fastboot/bootloader with the error i am getting along with My phone information is attached below.
Need your help what should i do now.
Click to expand...
Click to collapse
You should NOT re-lock the bootloader. Leave it unlocked. The phone will update just fine with unlocked BL. Just flash back to stock (what ever version you have on the phone now), then take the new OTA update.
Afterwards you can re-root if you want to.
Once again: You do NOT need to lock the BL - for any reason.
EDIT: Just looked at your pictures. Your phone is in BAD shape -- you should have never attempted to downgrade. This will be difficult to recover. I suggest asking for help in the "debricking" thread in the General sub-forum.
Good Luck.
It looks to me like you WERE on the 4.4.4 or above bootloader, and you flashed just the 4.4.2 system and boot.img at some point. Now, going back to full 4.4.2, you have downgraded the Bootloader and partition table. That is a no-no.
samwathegreat said:
You should NOT re-lock the bootloader. Leave it unlocked. The phone will update just fine with unlocked BL. Just flash back to stock (what ever version you have on the phone now), then take the new OTA update.
Afterwards you can re-root if you want to.
Once again: You do NOT need to lock the BL - for any reason.
EDIT: Just looked at your pictures. Your phone is in BAD shape -- you should have never attempted to downgrade. This will be difficult to recover. I suggest asking for help in the "debricking" thread in the General sub-forum.
Good Luck.
It looks to me like you WERE on the 4.4.4 or above bootloader, and you flashed just the 4.4.2 system and boot.img at some point. Now, going back to full 4.4.2, you have downgraded the Bootloader and partition table. That is a no-no.
Click to expand...
Click to collapse
I have bought the phone in this shape so i don't know what the previous owner did to it. What if i use donot touch bootloader but just use Super SU (Full Unroot) option to unroot and flash stock recovery img from "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" file, then will i be able to install OTA update of 4.4.4?
Usama Ahmed said:
I have bought the phone in this shape so i don't know what the previous owner did to it. What if i use donot touch bootloader but just use Super SU (Full Unroot) option to unroot and flash stock recovery img from "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" file, then will i be able to install OTA update of 4.4.4?
Click to expand...
Click to collapse
Don't take the OTA. Just try to flash the full 4.4.4 SBF!
You can find the full 4.4.4 Sprint SBF at one of the links here: http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
samwathegreat said:
Don't take the OTA. Just try to flash the full 4.4.4 SBF!
You can find the full 4.4.4 Sprint SBF at one of the links here: http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
Click to expand...
Click to collapse
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.
Usama Ahmed said:
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.
Click to expand...
Click to collapse
The previous owner has left you with mismatched partitions. This state is known to be at risk of bricking....
Your safest option is to attempt to flash the 4.4.4 SBF (yes you linked the right file), but even this is not without risk. It might work perfectly fine, and you might end up having to de-brick it.
Wish I could give you a more definite answer, but anything other than flashing the full 4.4.4 SBF is very dangerous. Even flashing the entire 4.4.4 SBF has some risk.
Good Luck.
samwathegreat said:
The previous owner has left you with mismatched partitions. This state is known to be at risk of bricking....
Your safest option is to attempt to flash the 4.4.4 SBF (yes you linked the right file), but even this is not without risk. It might work perfectly fine, and you might end up having to de-brick it.
Wish I could give you a more definite answer, but anything other than flashing the full 4.4.4 SBF is very dangerous. Even flashing the entire 4.4.4 SBF has some risk.
Good Luck.
Click to expand...
Click to collapse
Thanks alot for your help. If you think there is even a slight chance of hard brick than i will stay with the current rom i have.
One last question, I you were in my position, would you go for flashing 4.4.4 SBF or would you just leave it as it is?
Usama Ahmed said:
Ok i am getting a little scared right now. I don't want to brick my device. I have found one firmware which i think should be okay to go with.
ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip
Do you think i should go with it? Is their any chance of getting bricked? I have posted my system information picture above so you can see if it will be compatible with it.
Click to expand...
Click to collapse
@samwathegreat is correct. You are trying to downgrade, hence the errors and problems. The key here is the screen shot of AP Fastboot, where the second line shows 30.B7 which is the bootloader for 4.4.4. So at this point, you only want to flash a 4.4.4 SBF, and never flash anything lower.
That does appear to be the correct 4.4.4 if you have a 2013 or First Gen... Sprint X.
I suggest you flash using mFastboot with the extra steps as listed in Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html However, if you are unsuccessful doing that, then you're going to need to visit the Unbricking thread and see if that can help you get fixed up.
KidJoe said:
@samwathegreat is correct. You are trying to downgrade, hence the errors and problems. The key here is the screen shot of AP Fastboot, where the second line shows 30.B7 which is the bootloader for 4.4.4. So at this point, you only want to flash a 4.4.4 SBF, and never flash anything lower.
That does appear to be the correct 4.4.4 if you have a 2013 or First Gen... Sprint X.
I suggest you flash using mFastboot with the extra steps as listed in Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html However, if you are unsuccessful doing that, then you're going to need to visit the Unbricking thread and see if that can help you get fixed up.
Click to expand...
Click to collapse
Hi KidJoe! Thanks for your reply. What can i post to confirm if i have chosen the right SBF for my phone (Yes it is Moto X First-Gen).
This is the file i am downloading right now. "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip"
And if i flash it with what you mentioned, is their a chance of bricking my device?
BTW i try to flash "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" with the same method you posted which resulted in error due to the problem you mentioned above.
Usama Ahmed said:
Hi KidJoe! Thanks for your reply. What can i post to confirm if i have chosen the right SBF for my phone (Yes it is Moto X First-Gen).
This is the file i am downloading right now. "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip"
And if i flash it with what you mentioned, is their a chance of bricking my device?
Click to expand...
Click to collapse
Your first screen shot in Post 1 shows your phone has 161.44.32.ghost_sprint.Sprint.en.US. In other words, Sprint rom. So you should be able to flash the Sprint 4.4.4 you found.
Ideally you want to look at the FINE PRINT on the bottom of the back of the phone. It will have a model, like XT1056, XT1060, XTT1049, XT1053, etc. The other option, if you have the original box, check the label on the end of it. If the IMEI number printed on the label, matches what phone shows in its menus, then that label on the box should also tell you the model (the box for my Verizon X has MOTXT1060DEV on the bar code label.), Since you got yours used, its VERY important you confirm that is the original box when trying to use the box to confirm the model number!
As for risks of bricking... well, that is an unknown. There have been MANY bricks caused when users got them selves into the situation your phone is in. There is no 100% risk free process to try and recover. And that is why there are so many warnings telling people to NOT DOWN GRADE!!!
What I'm suggesting has worked, but you are correct, there is still a chance to brick. Taking an OTA in the state your phone is in also has a risk of bricking. Anything you try and do at this point also have a risk of bricking.
Usama Ahmed said:
BTW i try to flash "ghost_sprint-user-4.4.2-KXA20.16-1.32-37-release-keys-cid9.xml" with the same method you posted which resulted in error due to the problem you mentioned above.
Click to expand...
Click to collapse
Yes. The phone will ERROR if you try to flash an older GPT.BIN which is what you are encountering. (bootloader version indicates you had 4.4.4 on your phone, including its GPT.BIN and Bootloader).
The problem is this...
The Phone's previous owner had a FULL 4.4.4 ROM flashed to the phone. They attempted to downgrade. Since GPT.BIN and MOTOBOOT.IMG can not be downgraded, they did only PARTS!! Now the phone has mismatched bootloader, partition table and other parts compared to the older "System" and such which are installed.
KidJoe said:
Your first screen shot in Post 1 shows your phone has 161.44.32.ghost_sprint.Sprint.en.US. In other words, Sprint rom. So you should be able to flash the Sprint 4.4.4 you found.
Ideally you want to look at the FINE PRINT on the bottom of the back of the phone. It will have a model, like XT1056, XT1060, XTT1049, XT1053, etc. The other option, if you have the original box, check the label on the end of it. If the IMEI number printed on the label, matches what phone shows in its menus, then that label on the box should also tell you the model (the box for my Verizon X has MOTXT1060DEV on the bar code label.), Since you got yours used, its VERY important you confirm that is the original box when trying to use the box to confirm the model number!
As for risks of bricking... well, that is an unknown. There have been MANY bricks caused when users got them selves into the situation your phone is in. There is no 100% risk free process to try and recover. And that is why there are so many warnings telling people to NOT DOWN GRADE!!!
What I'm suggesting has worked, but you are correct, there is still a chance to brick. Taking an OTA in the state your phone is in also has a risk of bricking. Anything you try and do at this point also have a risk of bricking.
Yes. The phone will ERROR if you try to flash an older GPT.BIN which is what you are encountering. (bootloader version indicates you had 4.4.4 on your phone, including its GPT.BIN and Bootloader).
The problem is this...
The Phone's previous owner had a FULL 4.4.4 ROM flashed to the phone. They attempted to downgrade. Since GPT.BIN and MOTOBOOT.IMG can not be downgraded, they did only PARTS!! Now the phone has mismatched bootloader, partition table and other parts compared to the older "System" and such which are installed.
Click to expand...
Click to collapse
The model no written on back is XT1056. Just to be sure i have also attached the picture below. I am currently downloading "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip".
Should i go for all these cmds?
mfastboot getvar max-download-size
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot reboot
Click to expand...
Click to collapse
Also in this process, is their chance of my phone dead?
Will these cmds also lock my bootloader or should i just leave it unlocked? As currently my phone has unlocked bootloader and is rooted.
A step by step (maximum safe steps) for flashing would be greatly appreciated.
Usama Ahmed said:
The model no written on back is XT1056. Just to be sure i have also attached the picture below. I am currently downloading "ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip".
Should i go for all these cmds?
Also in this process, is their chance of my phone dead?
Will these cmds also lock my bootloader or should i just leave it unlocked? As currently my phone has unlocked bootloader and is rooted.
A step by step (maximum safe steps) for flashing would be greatly appreciated.
Click to expand...
Click to collapse
XT1056 is Sprint. So ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip is the right ROM to use.
use EVERY COMMAND AS STATED in the link. If successful, all parts will be back in line, and consistent.
As I said, yes there is a chance you can brick your phone. Many other things can brick your phone while you are in this state too. There is no 100% "Safe" and "guaranteed to not brick your phone" process when you are in this state.
This process will NOT lock your bootloader. And samwathegreat already told you there is no need to re-lock it.
KidJoe said:
XT1056 is Sprint. So ghost_sprint-user-4.4.4-KXA21.12-L1.28-28-release-keys-cid9.xml.zip is the right ROM to use.
use EVERY COMMAND AS STATED in the link. If successful, all parts will be back in line, and consistent.
As I said, yes there is a chance you can brick your phone. Many other things can brick your phone while you are in this state too. There is no 100% "Safe" and "guaranteed to not brick your phone" process when you are in this state.
This process will NOT lock your bootloader. And samwathegreat already told you there is no need to re-lock it.
Click to expand...
Click to collapse
Ok then i will be trying it right now and see what happens.
Thanks alot to @samwathegreat and @KidJoe. I have successfully updated my Moto X to 4.4.4 KitKat. I hope it had solved mismatched bootloader, partition table and other parts as mentioned by @KidJoe.
Attachment of process is below.
Usama Ahmed said:
Thanks alot to @samwathegreat and @KidJoe. I have successfully updated my Moto X to 4.4.4 KitKat. I hope it had solved mismatched bootloader, partition table and other parts as mentioned by @KidJoe.
Attachment of process is below.
Click to expand...
Click to collapse
Screen shot starts when system.img is flashing, so as long as the commands above that were also done and didn't error out, you are good!
Excellent support here! @samwathegreat and @KidJoe are GREAT!
KidJoe said:
Screen shot starts when system.img is flashing, so as long as the commands above that were also done and didn't error out, you are good!
Click to expand...
Click to collapse
Sorry i didn't realize that. Yes everything part was flashed without error otherwise i wouldn't go further.
But i am in a new problem now. My sim card is not working now. It says "Your SIM card does not allow a connection to this network". If anyone can help regarding that or if i can flash something to make it work.
Usama Ahmed said:
But i am in a new problem now. My sim card is not working now. It says "Your SIM card does not allow a connection to this network". If anyone can help regarding that or if i can flash something to make it work.
Click to expand...
Click to collapse
it appears you're not using sprint as your carrier... So You may now have to run this process to SIM unlock -> http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155
KidJoe said:
it appears you're not using sprint as your carrier... So You may now have to run this process to SIM unlock -> http://forum.xda-developers.com/moto-x/general/guide-success-sim-unlock-sprint-xt1056-t2825155
Click to expand...
Click to collapse
Yes i am not using sprint as my carrier. Thanks alot for the help again. I will try this now and post the result.
Hey, i got the verizon dev edition with unlocked boktloader and root device i flash xt1052 rom to get the ota to 5.1
And aftet i flashed the baseband of 4.4.4 xt1060 to get my network work.
But now i want to get back to 4.4.4 of the verizon dev edition and i download tgz fille from the motorola site
And i wanted to flash it on rsd lite but i didnt have the xml fille there? So i dont know what to do now?
Ty for help
harel013 said:
Hey, i got the verizon dev edition with unlocked boktloader and root device i flash xt1052 rom to get the ota to 5.1
And aftet i flashed the baseband of 4.4.4 xt1060 to get my network work.
But now i want to get back to 4.4.4 of the verizon dev edition and i download tgz fille from the motorola site
And i wanted to flash it on rsd lite but i didnt have the xml fille there? So i dont know what to do now?
Ty for help
Click to expand...
Click to collapse
there is a high risk of bricking your device while downgrading http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
It's highly risky to downgrade but if you persist just make sure your bootloader and partition table is not the one that got upgtaded with the latest 5.1 rom. If it is the latest then don't do it.
Sent from my Moto X using Tapatalk
You can downgrade completely to 4.4.4.
But don't take OTA, your phone will brick.
The safest way in my opinion is (if you want to downgrade);
- Flash entire official firmware of XT1060 to your phone.
- DON'T TAKE OTA
- Wait for full firmware of XT1060(5.1)
- Flash full firmware of XT1060(5.1)
But if you want to play with 5.1, you can try this;
In my case, I have XT1056, and I wanted to play around with 5.1, so I converted from XT1056(4.4.4) to XT1053(4.4.4), then took OTA to XT1053 (5.1).
After that I tried AOSP but my bluetooth headset had a problem with phone function, then I decided to go back to official firmware again.
Since there is no Lollipop image for XT1053 or XT1056 now, I had to flash another variants like XT1052 and XT1058, but I got no signal.
I had to downgrade to XT1056(4.4.4) and using it for a day. After that I found out that file size of fsg.mbn differ by variants, then I downloaded XT1053(5.1 OTA) to get it.
I mixed up an entire XT1052(5.1 retail EN) with fsg.mbn from XT1053(5.1 OTA) and flashed them manually. Now my XT1056 works very well (with Xposed framework).
Keep in mind that YOU DO THIS ON YOUR OWN RISK.
ong14 said:
You can downgrade completely to 4.4.4.
But don't take OTA, your phone will brick.
The safest way in my opinion is (if you want to downgrade);
- Flash entire official firmware of XT1060 to your phone.
- DON'T TAKE OTA
- Wait for full firmware of XT1060(5.1)
- Flash full firmware of XT1060(5.1)
But if you want to play with 5.1, you can try this;
In my case, I have XT1056, and I wanted to play around with 5.1, so I converted from XT1056(4.4.4) to XT1053(4.4.4), then took OTA to XT1053 (5.1).
After that I tried AOSP but my bluetooth headset had a problem with phone function, then I decided to go back to official firmware again.
Since there is no Lollipop image for XT1053 or XT1056 now, I had to flash another variants like XT1052 and XT1058, but I got no signal.
I had to downgrade to XT1056(4.4.4) and using it for a day. After that I found out that file size of fsg.mbn differ by variants, then I downloaded XT1053(5.1 OTA) to get it.
I mixed up an entire XT1052(5.1 retail EN) with fsg.mbn from XT1053(5.1 OTA) and flashed them manually. Now my XT1056 works very well (with Xposed framework).
Keep in mind that YOU DO THIS ON YOUR OWN RISK.
Click to expand...
Click to collapse
My situation is same with you. My phone is xt1056 sprint. I converted to xt1053, and got ota to 5.1. But I don't like stock 5.1,there are some bug with graphic... I flashed and used customs Rom CM, PA,Carbon...some day. But now, I want to come back 4.4.4. Can you guide me more details?
I think if you flash complete 4.4.4 from 5.1, phone will bricked, because bootloader can not downgrade as someone said in high risk ...topic. Maybe you can flash 4.4.4 fw with edit xml to NOT flash motoboot and gpt....
Right ?
And last question, if there is a method to flash back 4.4.4, can I flash 4.4.4 xt1053 ? I don't want my phone have many bloatware sprint xt1056.
md07 said:
My situation is same with you. My phone is xt1056 sprint. I converted to xt1053, and got ota to 5.1. But I don't like stock 5.1,there are some bug with graphic... I flashed and used customs Rom CM, PA,Carbon...some day. But now, I want to come back 4.4.4. Can you guide me more details?
I think if you flash complete 4.4.4 from 5.1, phone will bricked, because bootloader can not downgrade as someone said in high risk ...topic. Maybe you can flash 4.4.4 fw with edit xml to NOT flash motoboot and gpt....
Right ?
And last question, if there is a method to flash back 4.4.4, can I flash 4.4.4 xt1053 ? I don't want my phone have many bloatware sprint xt1056.
Click to expand...
Click to collapse
You can flash back to 4.4.4 of XT1053 or XT1056 as you prefer, I think their radio are compatible.
But when 5.1 comes out, DON'T TAKE OTA. You have to wait for a full firmware to upgrade your phone.
I always use a manual flash method, so I don't have to edit an xml file.
When you downgrades, you will see a warning message, just ignore them.
ong14 said:
You can flash back to 4.4.4 of XT1053 or XT1056 as you prefer, I think their radio are compatible.
But when 5.1 comes out, DON'T TAKE OTA. You have to wait for a full firmware to upgrade your phone.
I always use a manual flash method, so I don't have to edit an xml file.
When you downgrades, you will see a warning message, just ignore them.
Click to expand...
Click to collapse
Do you use fastening to flash fw? And you flash all part inside fw? Include motorboat and got... ? After flash, do you make unlock network again ?
I used mfastboot to flash all CGs to my phone. But you may try to skip some CGs like KidJoe said.
Every time when you return to stock or do a hard reset, you have to do the SIM-unlock process again.
harel013 said:
Hey, i got the verizon dev edition with unlocked boktloader and root device i flash xt1052 rom to get the ota to 5.1
And aftet i flashed the baseband of 4.4.4 xt1060 to get my network work.
But now i want to get back to 4.4.4 of the verizon dev edition and i download tgz fille from the motorola site
And i wanted to flash it on rsd lite but i didnt have the xml fille there? So i dont know what to do now?
Ty for help
Click to expand...
Click to collapse
Moto is no longer including the XML to flash via RSDLite, but you could make your own if needed... instead they include a BATCH file which calls a copy of Moto's fastboot to flash it.
That being said... I WARN YOU!!! You will risk bricking your phone if you attempt to downgrade. While there is a slight chance the phone will not brick, we have enough who have bricked to say it is not safe!!
Some will say... "its ok, just skip motoboot.img and gpt.bin when flashing" that isn't safe either. If you later get prompted for and take an OTA update you'll again likely brick. Further when motoboot.img and GPT.BIN are missmatched from the rest of a STOCK Moto rom we've seen "bugs" or "issues" of things no working, like speaker phone, Settings -> Security menu, etc which are not a problem when all parts of your phone are consistent.
You're best bet... wait until a full 5.1 SBF for the Verizon XT1060 is either posted to Moto's web site of Dev Edition Images, or wait until a copy leaks... however, that too many also fail *IF* the GPT.BIN and components of motoboot.img are newer or different in the build you are running compared to what is made available as the XT1060 5.1 SBF.
KidJoe said:
Moto is no longer including the XML to flash via RSDLite, but you could make your own if needed... instead they include a BATCH file which calls a copy of Moto's fastboot to flash it.
That being said... I WARN YOU!!! You will risk bricking your phone if you attempt to downgrade. While there is a slight chance the phone will not brick, we have enough who have bricked to say it is not safe!!
Some will say... "its ok, just skip motoboot.img and gpt.bin when flashing" that isn't safe either. If you later get prompted for and take an OTA update you'll again likely brick. Further when motoboot.img and GPT.BIN are missmatched from the rest of a STOCK Moto rom we've seen "bugs" or "issues" of things no working, like speaker phone, Settings -> Security menu, etc which are not a problem when all parts of your phone are consistent.
You're best bet... wait until a full 5.1 SBF for the Verizon XT1060 is either posted to Moto's web site of Dev Edition Images, or wait until a copy leaks... however, that too many also fail *IF* the GPT.BIN and components of motoboot.img are newer or different in the build you are running compared to what is made available as the XT1060 5.1 SBF.
Click to expand...
Click to collapse
Yea i think i will wait for the full sbf 5.1 for verizon, i dont want to take the chance.
Thank you all for your help when the 5.1 update will come to the verizon you think?