Return Rooted 5.1 VZW to stock? - X 2014 Q&A, Help & Troubleshooting

I have a the VZW Moto X (2014) XT1096 which is BL unlocked and rooted.
I flashed the Google Dialer App the other day and like a moron did not rename the old dialer first in order to keep it. The Google Dialer is giving me fits - force closes, freezes and just generally being a pain in my ...
Any idea idea how I can restore my system to bone stock?

Here is the full 5.1 factory image:
http://www.filefactory.com/file/5hj...ZON_XT1096_5.1_LPE23.32-25-3_cid2_CFC.xml.zip
Extract the zip and flash the system image to get back to stock.
Sent from my XT1095 using Tapatalk

Thanks for the link - next stupid question.
What do you mean by flash? I am used to RSD like on past Moto phones but that doesn't appear to be the route here. So... Mind pointing me in the right direction?

HTC-OH_SNAP said:
Thanks for the link - next stupid question.
What do you mean by flash? I am used to RSD like on past Moto phones but that doesn't appear to be the route here. So... Mind pointing me in the right direction?
Click to expand...
Click to collapse
RSDLite will flash everything, system, modem, recovery, logo, etc. So yes that will work as well, just remember that RSDLite will erase your data, so backup first.
If you only want to flash just system, you can use fastboot instead of RSDLite. That will only flash the system, and you keep your data.

Related

Bricked? Say it ain't so.

So trying any and everything to remove safestrap and install the latest ota i think i wiped all my data and my system cause now i just sit on the blue motorola m forever. I have an at&t moto x. the only thing i can do is fastboot with vol down and after that none of those options bring me anywhere. am i completely f'd or is there some way to fix this? thanks for the help guys.
Rsdlite back to stock
Sent from my Nexus 7 using Tapatalk
zeer.row said:
So trying any and everything to remove safestrap and install the latest ota i think i wiped all my data and my system cause now i just sit on the blue motorola m forever. I have an at&t moto x. the only thing i can do is fastboot with vol down and after that none of those options bring me anywhere. am i completely f'd or is there some way to fix this? thanks for the help guys.
Click to expand...
Click to collapse
Do you have any experience with fastboot? If not, google how to download it for whatever type of computer you have. I'm on a linux machine so its pretty straight forward, but I think its easy on any machine. If you're on windows you'll need the motorola drivers as well. You'll also need a factory stock image for at&t moto x.
After that it's just a matter of flashing the image to your phone and starting over.
I'm sorry, forgot about the locked bootloader. Listen to the guy before me.
If there are any pictures or stuff like that on your phone, i'm afraid those will probably be lost.
I will try to find helpful links for all this stuff, but I just wanted to give you something to look for while I did that.
Anthony04x said:
Rsdlite back to stock
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
lnstalling rsdlite now. will update. thanks a ton.
Okay, got it.
1. Go here and download that (hopefully you're on a windows machine):
http://forum.xda-developers.com/showthread.php?t=1348587
2. then go here and download the AT&T one. The third one down is KitKat, so just go with that, since it's what you're trying to do anyway.
http://sbf.droid-developers.org/ghost_rcica/list.php
3. Make sure you have these drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
Now, go into RSDLite, click on load or open or whatever it says and go to the FXZ from step 2.
Click start.
Should be that easy, let me know if there are any hiccups.
thank you sooo much!
Hey no problem, we've all been there at some point. Did you get it working?
ps. Don't forget about that thank you button.
Sent from my XT1060
You can use the moto x toolkit here in this forum too. Install, open as administrator, install drivers from main menu, pick back to stock from main menu. Follow on screen instructions and it will do the rest from there
http://forum.xda-developers.com/showthread.php?t=2477132
This is in the completely wrong section. Needs to be moved to Q&A. Questions and help posts don't belong in a Development section.
Sent from my Nexus 5
Moto X was Bricked - Fixed - Thanks for the help
Thank you - it worked -
For some reason VZW wouldn't update my Moto X from 4.2.2 to Kit Kat. I bricked it trying. RSDLite fixed it with your instructions and now I'm on 4.4 Kit Kat.
Thanks!
JetOhmNet said:
Okay, got it.
1. Go here and download that (hopefully you're on a windows machine):
http://forum.xda-developers.com/showthread.php?t=1348587
2. then go here and download the AT&T one. The third one down is KitKat, so just go with that, since it's what you're trying to do anyway.
http://sbf.droid-developers.org/ghost_rcica/list.php
3. Make sure you have these drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
Now, go into RSDLite, click on load or open or whatever it says and go to the FXZ from step 2.
Click start.
Should be that easy, let me know if there are any hiccups.
Click to expand...
Click to collapse
OP - you can use my script here:
http://forum.xda-developers.com/showthread.php?t=2603051
choose Advanced Menu and then #2 - Flash Binaries (no wipe)
it uses the mfastboot method and may be able to save your data.

[Q] new OTA update bricked my phone

I need some help. My phone is capable of booting into fastboot mode, but doesn't seem to be able to boot normally.
I am seeing the android laying on it's side with a red triangle with an exclamation point, this keeps blinking on and off. I've tried using rsdlite as well as the flash back to stock options in the moto-x toolkit and nothing is working. I've also cleared the cache and userdata folders but nothing has worked.
Is there a way to fix this or will I need to send my phone back to motorola for a repair?
doctor_evil said:
I need some help. My phone is capable of booting into fastboot mode, but doesn't seem to be able to boot normally.
I am seeing the android laying on it's side with a red triangle with an exclamation point, this keeps blinking on and off. I've tried using rsdlite as well as the flash back to stock options in the moto-x toolkit and nothing is working. I've also cleared the cache and userdata folders but nothing has worked.
Is there a way to fix this or will I need to send my phone back to motorola for a repair?
Click to expand...
Click to collapse
In the fastboot screen whats version is your booloader ?
Sent on my Gummy running Lenoto X
looks to be the one that I shouldn't have installed the OTA update. why in the F would they send me an update that isn't compatible with my bootloader version?
Well they're getting it back for a repair, I didn't pay 399 for a developer edition phone just to have a dang paperweight because they sent me an incompatible OTA update.
doctor_evil said:
looks to be the one that I shouldn't have installed the OTA update. why in the F would they send me an update that isn't compatible with my bootloader version?
Well they're getting it back for a repair, I didn't pay 399 for a developer edition phone just to have a dang paperweight because they sent me an incompatible OTA update.
Click to expand...
Click to collapse
They didn't send you a incompatible boot loader, the ota's always come with a new boot loader, so what I like to know is, what version is your boot loader , its Motorola's fault that you accepted the ota while having a custom recovery, had you read my thread here http://forum.xda-developers.com/showthread.php?t=2639102
You wouldn't have any issues.
If you don't want my help, thats fine by me, getting tired of this ota crap anyways
Sent on my Gummy running Lenoto X
Clearly you don't really want us to help or you would have answered the previous posters question. You also gave no details into if you had rooted the phone or unlocked the bootloader.
From the bootloader screen select the "factory" option.
I may agree with the op here. Moto supplied me with a 4.4 version for my dev ed. If I take an update, have an issue and moto still only provides 4.4 sbf what a I supposed to do?
However, OP you do need to supply more information as we can only speculate as to what your issue is.
Sent from my SM-P600 using Tapatalk
edthesped said:
I may agree with the op here. Moto supplied me with a 4.4 version for my dev ed. If I take an update, have an issue and moto still only provides 4.4 sbf what a I supposed to do?
However, OP you do need to supply more information as we can only speculate as to what your issue is.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Its not moto's fault, its up to the user to make sure you read the sticky notes, read the threads and search, moto puts out the ota for unrooted users.
Sent on my Gummy running Lenoto X
flashallthetime said:
Its not moto's fault, its up to the user to make sure you read the sticky notes, read the threads and search, moto puts out the ota for unrooted users.
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
However I purchased a Dev Ed phone. Motorola supplied me with a recovery firmware to restore my device to stock. I therefore expect the Factory supplied firmware to not brick my phone. If Motorola makes changes in an update that would cause previous versions of their software to damage phones when used as supplied Motorola needs to bear some of the responsibility. They can build a failsafe into the update that would prevent an attempt of a downgrade, supply upgrades that can safely be downgraded, add some kind of notification or not market "Dev Ed" phones for mass consumption.
Sent from my SM-P600 using Tapatalk
But the update clearly and concisely says, YOU CANNOT roll back to a previous firmware after applying said update.
Onus is on the user at that point.
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Tx Redneck said:
But the update clearly and concisely says, YOU CANNOT roll back to a previous firmware after applying said update.
Onus is on the user at that point.
Click to expand...
Click to collapse
Does it? I never saw that going to 4.4. As long as they put a new sbf up all should be fine.
Sent from my SM-P600 using Tapatalk
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
doctor_evil said:
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Click to expand...
Click to collapse
Did you call Motorola?
Sent from my SM-P600 using Tapatalk
doctor_evil said:
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Click to expand...
Click to collapse
UPDATE:
I tried again to select the factory option in fastboot and unlike the previous times I had tried, this time seems to have fixed it. It booted up into Android OS. I think I'll try the OTA once again and see if this time is more successful, as if it screws up again I have a repair rma number and a fedex shipping label, but hopefully it does better this time.
doctor_evil said:
UPDATE:
I tried again to select the factory option in fastboot and unlike the previous times I had tried, this time seems to have fixed it. It booted up into Android OS. I think I'll try the OTA once again and see if this time is more successful, as if it screws up again I have a repair rma number and a fedex shipping label, but hopefully it does better this time.
Click to expand...
Click to collapse
ok OTA successful this time.
does anyone know if it's possible to boot the moto-x off a custom recovery using fastboot like we could for the galaxy nexus? I'd like to get root reinstalled but I don't want to mess with the current recovery, which should help I would think in regards to being able to install OTA updates without major issues.
doctor_evil said:
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Click to expand...
Click to collapse
Maybe try this out.. option 2 http://forum.xda-developers.com/showthread.php?t=2446515
doctor_evil said:
ok OTA successful this time.
does anyone know if it's possible to boot the moto-x off a custom recovery using fastboot like we could for the galaxy nexus? I'd like to get root reinstalled but I don't want to mess with the current recovery, which should help I would think in regards to being able to install OTA updates without major issues.
Click to expand...
Click to collapse
Unfortunately, I don't believe it's possible to fastboot boot recovery. It's how I did everything with my Galaxy Nexus and Nexus 7. I was disappointed to find out it isn't possible with the Moto X Dev edition even though I didn't buy one.
nhizzat said:
Unfortunately, I don't believe it's possible to fastboot boot recovery. It's how I did everything with my Galaxy Nexus and Nexus 7. I was disappointed to find out it isn't possible with the Moto X Dev edition even though I didn't buy one.
Click to expand...
Click to collapse
has anyone tried it with the google play edition of the moto-g? I'm wondering if there is a way to convert from a regular retail rom over to a GPE rom for the moto-x after google starts selling it. I remember reading about them going to sell a GPE of it. Hopefully the GPE rom would be friendlier than the retail rom
doctor_evil said:
I am seeing the android laying on it's side with a red triangle with an exclamation point, this keeps blinking on and off. I've tried using rsdlite as well as the flash back to stock options in the moto-x toolkit and nothing is working. I've also cleared the cache and userdata folders but nothing has worked.
Is there a way to fix this or will I need to send my phone back to motorola for a repair?
Click to expand...
Click to collapse
I know you have fixed this now, but if you see the android with the red triangle and ! use the key combination pwr & up vol. That gets you into stock recovery and from there you should be able to boot up.

How to flash a fresh stock Verizon 4.4

I have a Verizon DE moto x that has twrp recovery. My active display keeps getting stuck when I get a notification, so I think I need to flash (or however it must be done) a fresh rooted stock copy. Where can I find info on how to do this?
Sent from my XT1060
Since you aren't downgrading or anything, you won't have to worry about the bootloader, so just grab the Verizon 4.4 SBF and follow the instructions
mastarifla said:
Since you aren't downgrading or anything, you won't have to worry about the bootloader, so just grab the Verizon 4.4 SBF and follow the instructions
Click to expand...
Click to collapse
What is the difference between flashing firmware and flashing factory images?
Cozume said:
What is the difference between flashing firmware and flashing factory images?
Click to expand...
Click to collapse
As far as I know, the only verifiable "factory images" are the Developer Edition ones that Moto hosts on their personal website.
The SBF may/may not be official factory images. However, they are essentially accepted by the community as the next best thing, mainly because the zips follow the rules set by RSD Lite (Insider Moto Tool) and help prevent bad flashes/user error.
Flashing the SBF firmware manually (via fastboot commands) can raise a few problems of its own, if you don't know what you are doing you can cause serious damage to your device, which is why it is safer to use something like RSD Lite. If you are manually flashing, there is no "check" to verify that you installed them in the correct order or that you flashed all the files without missing anything. Therefore, it is much more risky, please know what you are doing if you plan on flashing this way.
mastarifla said:
As far as I know, the only verifiable "factory images" are the Developer Edition ones that Moto hosts on their personal website.
The SBF may/may not be official factory images. However, they are essentially accepted by the community as the next best thing, mainly because the zips follow the rules set by RSD Lite (Insider Moto Tool) and help prevent bad flashes/user error.
Flashing the SBF firmware manually (via fastboot commands) can raise a few problems of its own, if you don't know what you are doing you can cause serious damage to your device, which is why it is safer to use something like RSD Lite. If you are manually flashing, there is no "check" to verify that you installed them in the correct order or that you flashed all the files without missing anything. Therefore, it is much more risky, please know what you are doing if you plan on flashing this way.
Click to expand...
Click to collapse
Just to clarify. Using the rsd lite method will not mess with the boot loader nor the /media folder correct?
Sent from my XT1060
Swimboy46163 said:
Just to clarify. Using the rsd lite method will not mess with the boot loader nor the /media folder correct?
Sent from my XT1060
Click to expand...
Click to collapse
Depends on if you edit the xml file or not. The bootloader will be flashed by default and data will be wiped by default. It's been a while since I've used RSD but I think when it wipes /data it wipes everything (i.e. including /media). That being said, you could always take those steps out of the xml file.
piccit said:
Depends on if you edit the xml file or not. The bootloader will be flashed by default and data will be wiped by default. It's been a while since I've used RSD but I think when it wipes /data it wipes everything (i.e. including /media). That being said, you could always take those steps out of the xml file.
Click to expand...
Click to collapse
Will this work? http://www.youtube.com/watch?v=gDJvZe7_s0E
While yes it will work I would suggest learning HOW it works, take a look at the steps it goes through and see what is happening, don't rely on these kinds of tools, because they become useless if something bad happens. However, if you look at and modify the XML, it is literally only taking out a few lines of code, but if you want an automated version, then use the tool.
mastarifla said:
While yes it will work I would suggest learning HOW it works, take a look at the steps it goes through and see what is happening, don't rely on these kinds of tools, because they become useless if something bad happens. However, if you look at and modify the XML, it is literally only taking out a few lines of code, but if you want an automated version, then use the tool.
Click to expand...
Click to collapse
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Sent from my XT1060
Swimboy46163 said:
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Click to expand...
Click to collapse
I have a Windows 7 machine and I can never get adb to run in a command prompt, either. I have a driver problem.
I can only use mfastboot to do anything unless I can fix my driver problem.
Swimboy46163 said:
I can never get adb to run in command prompt. Mostly because windows is different from Mac.
Sent from my XT1060
Click to expand...
Click to collapse
There are a few tutorials for setting it up correctly, I'm not sure that you need the full SDK in order to do this, but I guess it's nice to have anyways. Try reading up a bit about it, I'm sure you can get it running in no time , after that you'll be much more familiar with these kinds of things.
OP, are you on 4.4? if so, then you don't have to worry about the bootloader. Just download the most current factory image from Motorola. The instructions for flashing the factory images are on their website. Go to www.motorola.com, go to the bottom of the page and click on "Developers". Its the same page you went to in order to get the bootloader unlock code. You have to request the factory image, and Motorola will email you a link, or there's several links to it floating around here.
The factory image will have the same bootlaoder version as you have installed as long as your are flashing the same OS version. It won't relock your bootloader, but you will lose root until you flash TWRP recovery. as far as the media partition, just back up your sdcard partition to your computer before flashing the factory image.
Here's the steps:
1. Plug your MX into the computer and back up all files you want to keep (photos, music, videos, downloads, etc...)
2. Download the 4.4 factory image from the source of your choice (If you don't get it from Motorola, make 100% sure you are downloading the correct file)
3. Make sure you have ADB and fastboot set up properly (and make sure you use the motorola fastboot (mfastboot.exe), bot the Google version)
4. Unzip the factory image and place all the files into the same folder as your adb and fastboot files.
5. Boot your MX into fastboot mode (power off, then hold all three buttons for approx 5 seconds and release)
6. Flash the files using mfastboot, and following the order provided in the included xml file.
7. Reboot.
8. Set your phone up and then restore the files you backed up to your computer
9. If you want root, then you will have to go back to fastboot and flash the TWRP recovery and let it install SuperSU.
10. Finally, PLEASE, make a nandroid back up once you have everything set up and before you make any alterations to it.
Thanks guys! The toolkit actually did the trick for me I was being lazy today lol
Sent from my XT1060 using Tapatalk
Swimboy46163 said:
Thanks guys! The toolkit actually did the trick for me I was being lazy today lol
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Thanks buddy for ruining it for everybody. If you would stop being on your rag and complaining like a girl none if this would have happened. Look at what you did little girl.
MOTO X Slapped

[Q] been out of the xda world for a while, need a couple questions awnsered

ok i had alot of bs happening in my life latly and just totally lost touch with this whole scene and im now having some tech issues and was hoping you guy would be kind enough to refreshify my memory and give me some updates.
so to my phone is a dev edition, Ultra Maxx but im running the VZW moto x factory images so that is why im posting here.
so whats been happening is my phone has been generally running slow and im getting really inconsistent battery life. what i was planing was to flash just to reflash the moto x firmware. im on straight 4.4 and now i see weve gotten 4.4.2 and 4.4.3 and im wondering what are the pros and cons were from a hack-ability stand point if any since im unlocked? also i use skvalex's call recorder and wondered if anyone is using it successfully on 4.4.2 or 4.4.3.
and im sure this is just me being a retard but i cant find motorolas factory image page? am i stupid or are they dicks and not doing it any more?
thanks in advance for the help and for patients with my reversion to a noob.
TheWhiteChallenger said:
ok i had alot of bs happening in my life latly and just totally lost touch with this whole scene and im now having some tech issues and was hoping you guy would be kind enough to refreshify my memory and give me some updates.
so to my phone is a dev edition, Ultra Maxx but im running the VZW moto x factory images so that is why im posting here.
so whats been happening is my phone has been generally running slow and im getting really inconsistent battery life. what i was planing was to flash just to reflash the moto x firmware. im on straight 4.4 and now i see weve gotten 4.4.2 and 4.4.3 and im wondering what are the pros and cons were from a hack-ability stand point if any since im unlocked? also i use skvalex's call recorder and wondered if anyone is using it successfully on 4.4.2 or 4.4.3.
and im sure this is just me being a retard but i cant find motorolas factory image page? am i stupid or are they dicks and not doing it any more?
thanks in advance for the help and for patients with my reversion to a noob.
Click to expand...
Click to collapse
Factory SBF images here: http://sbf.droid-developers.org/phone.php?device=0
Follow the instructions in the "Return to Stock" thread. I don't know about call recording, so can't advise on that.
I can tell you that if and when you upgrade to 4.4.2 or above, you can never go back to 4.4 - If you attempt to downgrade once on 4.4.2, you WILL brick your phone.
Good Luck
thank you i actually know about this site however im looking for the official motorola files specific to the dev editions,
ok i found it, this is what ive been looking for
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
also if you flash the imgs manually as opposed to rds lite and DO Not flash the bootloader you can go back.
so for example im on 4.4 su1 and flash the system.img from su2 i can go back to su1, because attemting to flash the su1 boot.im over the su2.img is what bricks you
TheWhiteChallenger said:
thank you i actually know about this site however im looking for the official motorola files specific to the dev editions,
ok i found it, this is what ive been looking for
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
also if you flash the imgs manually as opposed to rds lite and DO Not flash the bootloader you can go back.
so for example im on 4.4 su1 and flash the system.img from su2 i can go back to su1, because attemting to flash the su1 boot.im over the su2.img is what bricks you
Click to expand...
Click to collapse
The VZW XT1060 rom hosted at SBF Droid Dev.org and requestable as the XT1060 Dev Edition from Moto directly are the same. Verified if you unzip and do a file compare of the IMG and BIN files included. At one point the XML files differed slighty in that the DEV Ed SBF from Moto had an extra reboot in the XML while flashing, and the erase cache and erase userdata statements were included in one but not the other.
In the OP you mention you have a Ultra Maxx running the Moto X rom... so I don't know if the same conditions apply, but on a Real X... if you flash just downgrade just SYSTEM.IMG, you will have issues. For example Settings -> Security will kick you back out of that menu. Other problems might arise too. Also, while in this state of miss matched GPT.BIN and MOTOBOOT.IMG (bootloader) vs ROM version, should you take an OTA update best case it will fail, worst case it will brick.
KidJoe said:
The VZW XT1060 rom hosted at SBF Droid Dev.org and requestable as the XT1060 Dev Edition from Moto directly are the same. Verified if you unzip and do a file compare of the IMG and BIN files included. At one point the XML files differed slighty in that the DEV Ed SBF from Moto had an extra reboot in the XML while flashing, and the erase cache and erase userdata statements were included in one but not the other.
In the OP you mention you have a Ultra Maxx running the Moto X rom... so I don't know if the same conditions apply, but on a Real X... if you flash just downgrade just SYSTEM.IMG, you will have issues. For example Settings -> Security will kick you back out of that menu. Other problems might arise too. Also, while in this state of miss matched GPT.BIN and MOTOBOOT.IMG (bootloader) vs ROM version, should you take an OTA update best case it will fail, worst case it will brick.
Click to expand...
Click to collapse
thats interesting im not sure what would be diff but ive had no issues with mis match but thanks for the info

[Q] Deleted system partition

I was wiping data and cache on twrp and I accidentaly deleted the system partition. The thing is, I was in the 4.4.3 brazil retail stock rom and I can't find this firmware to flash with rsd. So, what should I do?
Guilhermewpds said:
I was wiping data and cache on twrp and I accidentaly deleted the system partition. The thing is, I was in the 4.4.3 brazil retail stock rom and I can't find this firmware to flash with rsd. So, what should I do?
Click to expand...
Click to collapse
Oh boy....this is a tricky one.
The full STOCK 4.4.3 SBF for the Brazil Retail Rom has not been 'leaked' yet....
Be VERY careful or you could end up with a brick.
Here are my suggested instructions, but DO NOT FOLLOW THEM until another user comments and verifies that I have given you the correct method -- we are in uncharted territory here.
I would suggest downloading the ENTIRE stock 4.4.2 Brazil Retail SBF, extracting it, and running JUST the following commands:
mfastboot flash system system.img
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot erase cache
mfastboot erase userdata
THEN, reboot, and accept the 4.4.3 OTA to get you back on track. This SHOULD work, but wait for another user to verify my suggestions.
The thing is, you cannot flash gpt.bin from the 4.4.2 ROM. Fortunately, the bootloader version did not change, so if we can get you safely booted into 4.4.2, you SHOULD be able to accept the OTA and be back to 4.4.3 without any mismatched partition tables or bootloader.
I hightly suggest making a backup afterwards, so you can restore if something like this happens again...
I also suggest (as you have seen) erasing all userdata (and cache) because it is unknown what problems might arise if you flash the 4.4.2 system.img with your existing userdata.
Unfortunately, this means you will need to set everything up from scratch, but --better safe than sorry--.
Good Luck with this, and one last time - please wait for another experienced user to verify my methods. I do NOT want to be responsible for you bricking your device...
EDIT: Still no reply/confirmation. @KidJoe , @KJ , what do you guys think??
@Guilhermewpds and @samwathegreat
I would be careful.
even though the bootloader did not change between 4.4.2 and 4.4.3, the GPT.BIN (partition table) did. So there could still be issues when trying to "downgrade"
My gut reaction would be, try to flash only the system.img from the 4.4.2 SBF along with erasing userdata and cache, and if it works to get the phone up and running, make sure to NOT take any OTAs. Stick on that until the 4.4.3 SBF leaks, and then flash the SBF to get back to 4.4.3 and bring everything back in line.
keep in mind that erasing userdata will wipe the data and apps you've added to the phone, so I would flash system.img, see if the phone boots, copy any data from it that you can, and then go back and use mfastboot to erase userdata and cache.
I forgot to mention, but i have an unlocked bootloader, so I believe I could, for instance, install a 4.4.3 rom too, couldn't I? I just want to know what is the less risky thing to do in this situation
Guilhermewpds said:
I forgot to mention, but i have an unlocked bootloader, so I believe I could, for instance, install a 4.4.3 rom too, couldn't I? I just want to know what is the less risky thing to do in this situation
Click to expand...
Click to collapse
Although I hate to say it, in this case the less risky method would be to download the entire 4.4.3 SBF for the T-Mobile XT1053, and flash the entire ROM using either fastboot, or RSD Lite.
This should get you up and running in NO time, with much less risk. If and when the Brazil 4.4.3 SBF is released, you can flash it back on, if you want.
---------- Post added at 10:33 AM ---------- Previous post was at 10:30 AM ----------
KidJoe said:
@Guilhermewpds and @samwathegreat
I would be careful.
even though the bootloader did not change between 4.4.2 and 4.4.3, the GPT.BIN (partition table) did. So there could still be issues when trying to "downgrade"
My gut reaction would be, try to flash only the system.img from the 4.4.2 SBF along with erasing userdata and cache, and if it works to get the phone up and running, make sure to NOT take any OTAs. Stick on that until the 4.4.3 SBF leaks, and then flash the SBF to get back to 4.4.3 and bring everything back in line.
keep in mind that erasing userdata will wipe the data and apps you've added to the phone, so I would flash system.img, see if the phone boots, copy any data from it that you can, and then go back and use mfastboot to erase userdata and cache.
Click to expand...
Click to collapse
So exactly the same as my suggestion, except NOT accepting the OTA. Thanks for the input
Guilhermewpds said:
I forgot to mention, but i have an unlocked bootloader, so I believe I could, for instance, install a 4.4.3 rom too, couldn't I? I just want to know what is the less risky thing to do in this situation
Click to expand...
Click to collapse
I usually don't recommend flashing a full ROM/SBF from another carrier and/or model X.. There are a bunch of caveats to keep in mind which makes it risky.
Since you mention you are Brazil, do you have an XT1052, XT1058 or XT1053? My guess is XT1058.
The Only 4.4.3 SBF out there right now appears to be the T-Mobile USA (same as GSM Dev Edition) 4.4.3. You could try it.
If you have an XT1053, its less risky to flash the T-Mo USA SBF, but if your X is an XT1052 or XT1058, then know that the modems will be different and would change the process of flashing the T-MO SBF, or you will lose support of some frequencies.
---------- Post added at 10:54 AM ---------- Previous post was at 10:46 AM ----------
samwathegreat said:
So exactly the same as my suggestion, except NOT accepting the OTA. Thanks for the input
Click to expand...
Click to collapse
Kind of. But I suggested backing up before doing the erase userdata and left off the erase modemst1 & modemst2 because I'm not sure it is really needed.
KidJoe said:
Kind of. But I suggested backing up before doing the erase userdata and left off the erase modemst1 & modemst2 because I'm not sure it is really needed.
Click to expand...
Click to collapse
Modemst1 / Modemst2 = baseband cache partitions. Probably NOT necessary, but definitely can't hurt.
What a tricky situation
I can't think of a way to to express in any more urgency how important it is to not downgrade.....it is already stickied at the top of almost every subforum on here.....I just hate to see these guys end up bricking such a great phone
EDIT: and yes, ALL Brazil Moto X's are XT1058
EDIT2: I also want to point out that although I would normally NEVER recommend flashing another carrier's ROM...I feel it is irresponsible to advise users at it is "perfectly safe", without providing any disclaimer. Think about @bernardomendez181 , who blames another user on this forum for his phone getting bricked. He was advised that it was perfectly safe, and didn't even say "do it at your own risk". That gentleman ended up with a brick, sadly
BUT, you are already in a pickle here. Seems to me that flashing a ROM with the same version of GPT.bin is less risky than having mismatched versions, etc.
Also, @KidJoe, I very much value your advice, which is why I asked for you comment in the first place. Your advice and solutions seem well-thought-out and methodical. I appreciate the contributions you make to our community.
So, with the XT1058 being my variant, what would you guys do in my situation: flash the T-Mobile SBF with/without the modems or downgrade to 4.4.2?
Guilhermewpds said:
So, with the XT1058 being my variant, what would you guys do in my situation: flash the T-Mobile SBF with/without the modems or downgrade to 4.4.2?
Click to expand...
Click to collapse
NEVER DOWNGRADE attempt to 4.4.2 (i.e. once you have 4.4.3 on your phone do NOT fully flash a 4.4.2 SBF on your phone.)
It would be a "no brainer" if the 4.4.3 SBF for your XT1058 and carrier was leaked. Just flash the System.img from your carrier's 4.4.3 SBF.
BUT Your situation is tricky. Brazil XT1058 with 4.4.3, and you need to re-flash, BUT there is no Brazil XT1058 SBF available yet.
I think @samwathegreat and I are both in agreement that anything you proceed with at this point (since the Brazil XT1058 4.4.3 SBF hasn't leaked) will be RISKY!!!
There is the potential to brick your phone in the process, or in the future (when taking an upgrade or flashing back to stock), or might end up just being unstable until you can flash with the proper SBF!
That being said, I think what samwathegreat suggested in Post #2 might be the best course of action, but do NOT take any OTAs, instead wait until the full XT1058 4.4.3 SBF for your carrier leaks, or 4.4.4 SBF should it leak, then flash it to get your files back in line and matched up again. And remember that the erase userdata statement will clear your apps, files, etc from the phone, so back up first if you can! You might find some things that don't work properly (like those with 4.4.2 who flashed 4.4 system.img found that their Settings ->Security menu stopped working)
Flashing only parts of an SBF will put your phone in a state with mismatched files (i.e. files from different versions), so its an undesirable state. Take an OTA, in this state, and you will most likely brick, or possibly get lucky and have the OTA fail its validation checks and not attempt to install.
And I can also agree with samwathegreat's EDIT2 in post #7, that flashing a ROM with with same version GPT.BIN might be less risky than flashing just system.img of an older version and running with mismatched files. However, I've seen people successfully run with a lower system.img and do a FULL SBF back to the current rom version when it was released without bricking.
Then again, another option is flash the system.img from the T-Mobile 4.4.3 SBF, and run with that ( i would still recommend erase cache and erase userdata, and do NOT take any OTA's), and again flash the Brazil XT1058 4.4.3 SBF (or 4.4.4 sbf) if/when it leaks.
So I followed @samwathegreat guide and could put it running again. Thank you so much! The only problem that I've found is that I can't turn wifi on. There's something I could do to fix it or I'll have to wait for the brazilian 4.4.3 SBF?
Guilhermewpds said:
So I followed @samwathegreat guide and could put it running again. Thank you so much! The only problem that I've found is that I can't turn wifi on. There's something I could do to fix it or I'll have to wait for the brazilian 4.4.3 SBF?
Click to expand...
Click to collapse
I seriously doubt that your WiFi not working is a result of what we have done.
I have a very strong idea on what the problem is.
Are you rooted? Please use a the app "Root Browser" to find your /persist folder.
What files are inside?
I have a suspicion that somehow you formatted your persist partition.
Your persist partition should have (among other folders) the following files inside:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
I bet that you are MISSING your WCNSS_qcom_wlan_nv.bin file!
Let me know if you are missing that file. If so, I will send you a copy and your WiFi should start working again immediately. You can NOT get the file from any of the STOCK firmwares or SBF files, because the /persist partition is SUPPOSED to remain untouched between flashes, and is never supposed to be deleted.
Please advise.
samwathegreat said:
I seriously doubt that your WiFi not working is a result of what we have done.
I have a very strong idea on what the problem is.
Are you rooted? Please use a the app "Root Browser" to find your /persist folder.
What files are inside?
I have a suspicion that somehow you formatted your persist partition.
Your persist partition should have (among other folders) the following files inside:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
I bet that you are MISSING your WCNSS_qcom_wlan_nv.bin file!
Let me know if you are missing that file. If so, I will send you a copy and your WiFi should start working again immediately. You can NOT get the file from any of the STOCK firmwares or SBF files, because the /persist partition is SUPPOSED to remain untouched between flashes, and is never supposed to be deleted.
Please advise.
Click to expand...
Click to collapse
Well, I just checked and I do have those files. Everytime I switch the wifi on it switches back to off.
Guilhermewpds said:
Well, I just checked and I do have those files. Everytime I switch the wifi on it switches back to off.
Click to expand...
Click to collapse
Bummer. The missing file results in the same issue. This is likely due to running mismatched versions.
There is a third option that I failed to consider earlier. If you can find someone willing, with a Brazil xt1058 on 4.4.3, you could have them do a factory reset, erase cache, then do a twrp backup of JUST /system
EDIT: upon further review, it shouldn't be necessary for the person who does this for you to reset and erase cache. JUST making a twrp backup of /system should suffice, IF that user has not modified their /system partition.
You can then flash the backup from within twrp and be in good shape.
This will get you 100% back to stock 4.4.3 Brazil ROM, since the rest of your partitions are already on 4.4.3
This is by far the best option for you, but you will need to convince another user with the Brazil retail xt1058 to do this for you.
Good luck
I'm late to the party. Lol. No matter what I do, I am only getting Tapatalk or XDA premium notifications for a bit...then nothing. Lol. I have to uninstall them, then reinstall...and they work...for hours only. Can't solve it either. ?
Glad the X gurus got you running! Kudos guys! ?
Another example tho that downgrading is evil. Never do it.
All this happened when 4.4.2 came out as well.
Patience is the key. Wait for your OTA's guys. Don't flash other carriers, and don't downgrade. (I know other carrier firmware fixed this issue...but it was that or no phone.).
Glad its running!!
Guilhermewpds said:
Well, I just checked and I do have those files. Everytime I switch the wifi on it switches back to off.
Click to expand...
Click to collapse
If you are interested in trying to get someone to share a TWRP backup of /system, I suggest this:
Make a new post in Q&A Section with this title: [REQUEST] TWRP backup of /system on Brazil Retail XT1058 4.4.3
And explain why you need the backup. It is very likely that another user will do this for you! If you haven't already, read my edit in the previous post: they should NOT have to reset and clear cache.
Just make sure you point out that you ONLY want a backup from someone who has not modified their /system partition, and also make it very clear that you need a backup of JUST /system.
This is fairly easy to do with TWRP. The user who provides you with their /system backup will simply boot into TWRP, click "BACKUP", and UNCHECK everything EXCEPT "System".
Then you will copy this backup provided to you to your internal memory into your TWRP backup folder.
Then YOU will boot into TWRP, press "WIPE", click "Advanced Wipe", then check "Dalvik Cache, Data, Cache, and System".
Next, press RESTORE, and find the backup that you copied to your internal memory, and start the restore.
This should do it for you!!!! Good Luck, and hope you get the needed backup
These instructions were written by memory, so I hope I haven't left out any steps. If you get stuck, let me know and I'll try to help.
samwathegreat said:
If you are interested in trying to get someone to share a TWRP backup of /system, I suggest this:
Make a new post in Q&A Section with this title: [REQUEST] TWRP backup of /system on Brazil Retail XT1058 4.4.3
And explain why you need the backup. It is very likely that another user will do this for you! If you haven't already, read my edit in the previous post: they should NOT have to reset and clear cache.
Just make sure you point out that you ONLY want a backup from someone who has not modified their /system partition, and also make it very clear that you need a backup of JUST /system.
This is fairly easy to do with TWRP. The user who provides you with their /system backup will simply boot into TWRP, click "BACKUP", and UNCHECK everything EXCEPT "System".
Then you will copy this backup provided to you to your internal memory into your TWRP backup folder.
Then YOU will boot into TWRP, press "WIPE", click "Advanced Wipe", then check "Dalvik Cache, Data, Cache, and System".
Next, press RESTORE, and find the backup that you copied to your internal memory, and start the restore.
This should do it for you!!!! Good Luck, and hope you get the needed backup
These instructions were written by memory, so I hope I haven't left out any steps. If you get stuck, let me know and I'll try to help.
Click to expand...
Click to collapse
I tried asking in a brazilian forum for the Moto X, but it seems more likely to get it here. I've run out of thanks, so thank you once again. I really appreciate your assistance!
This is simple suggestions, but worth a shot.
WiFi won't stay on at all? Or does it turn off while connecting? If you are able to...try forgetting your WiFi network if it let's you....and sign in again.
Also, reboot your router/modem.
And try a factory reset if all that fails. Yes, all apps and data will be gone. But with a try.
Basic suggestions....but who knows, something might work.
samwathegreat said:
....There is a third option that I failed to consider earlier. If you can find someone willing, with a Brazil xt1058 on 4.4.3, you could have them do a factory reset, erase cache, then do a twrp backup of JUST /system
Click to expand...
Click to collapse
Duh, I completely forgot about that too... Its been a while since I did backup/restore in CWM/TWRP that it completely slipped my mind. :crying:
KidJoe said:
Duh, I completely forgot about that too... Its been a while since I did backup/restore in CWM/TWRP that it completely slipped my mind. :crying:
Click to expand...
Click to collapse
Yep, I understand. Since we are using the STOCK rom (mostly), I rarely use TWRP anymore. Back in my "HTC Droid Incredible" days, flashing all kinds of different roms, I used to use CWM backups on a daily basis....
Oh well. OP has made a request and hopefully someone will share soon.
I finally got it in a brazilian forum. Thank you, @samwathegreat, @KidJoe and @KJ for your assistance and guidance! I really appreciate your help!

Categories

Resources