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!
Related
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
I have a Moto X Developer Edition rooted on Verizon with TWRP 2.6.3.1 and stock Android 4.4 on it. I have been trying to upgrade to 4.4.2 without doing the OTA, and without having to reflash TWRP.
So far, I have been unsuccessful.
I have tried Blur_Version.140.45.5.ghost_verizon.Verizon.en.US.zip (approximate file size 150MB) from multiple sources as all the posts I read keep saying that is what works. I have also tried a ~650MB version I found somewhere. In addition, I tried the upgrade located here: sbf.droid-developers.org/phone.php?device=0 which is called VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml.zip (It's the 4.4.2 upgrade listed under Verizon US).
All of these fail. In TWRP, about 2-3 steps after it verified md5, it simply says "Failed" with no explanation as to why.
Here is my question:
How can I upgrade to 4.4.2 without a data wipe, and without having to reflash TWRP?
I have no interest in going to a ROM, I want to stay stock, and if I must, I will reflash the recovery if I have to, but I *really* don't want to.
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
tcrews said:
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
Click to expand...
Click to collapse
I was hoping to avoid that (Yep, I really am that lazy...) but that's what I was going to do tonight if I couldn't get my hands on a .zip to flash.
Ironically, I bought the Dev Edition specifically so things like this would be easy.
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
tcrews said:
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
Click to expand...
Click to collapse
Oh, that last bit is good to know! Well, I think even if it did remove root, getting it back is easy on the DE.
I think you're right though, I probably won't install TWRP again, I specifically got the Moto X because I was tired of messing around with stuff when I all I want is a rooted, stock Android experience.
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Taegost said:
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Click to expand...
Click to collapse
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
kj2112 said:
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
Click to expand...
Click to collapse
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Taegost said:
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Click to expand...
Click to collapse
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
kj2112 said:
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
Click to expand...
Click to collapse
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Taegost said:
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Click to expand...
Click to collapse
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
kj2112 said:
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
Click to expand...
Click to collapse
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Taegost said:
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Click to expand...
Click to collapse
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
kj2112 said:
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
Click to expand...
Click to collapse
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Taegost said:
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Click to expand...
Click to collapse
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
if using fastboot/mfastboot, I would still erase cache, as it doesn't touch your data/apps/config.
Another tip, use this mfastboot -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
or you can use RSDlite to flash the SBF, but there is a corresponding line for "erase data"
Two helpful links that will help explain what you saw...
Taking the OTA -> http://mark.cdmaforums.com/MotoX-OTA.html
various ways to Return to stock -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
kj2112 said:
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
Click to expand...
Click to collapse
Alrighty, well I was able to successfully flash to 4.4.2 using the Fastboot instructions. Flashed TWRP afterwards and got root right back. Now that I know, this won't be a trial in the future (fingers crossed!)
Thanks for your help and patience
Hi,
I am flashing a factory image using RSD lite i was get error "SP space is not enough " what is that mean ? but finally no problem to my device .
Any help appriciating
Thnks
Mahesh
Mahesh8348 said:
Hi,
I am flashing a factory image using RSD lite i was get error "SP space is not enough " what is that mean ? but finally no problem to my device .
Any help appriciating
Thnks
Mahesh
Click to expand...
Click to collapse
Known error after you use twrp to wipe data. It shouldn't cause any problems..
samwathegreat said:
Known error after you use twrp to wipe data. It shouldn't cause any problems..
Click to expand...
Click to collapse
Can I try "fastboot erase system" before flashing system partition?
I'm afraid though the phone will not boot if flash fails after system erase.
ks73417 said:
Can I try "fastboot erase system" before flashing system partition?
I'm afraid though the phone will not boot if flash fails after system erase.
Click to expand...
Click to collapse
flashing anything should be proceeded by a system wipe anyway. No matter how you wipe it.
There's always risk in this hobby. Luckily, most problems are fixable.
Did you take a Nandroid backup before doing anything? That's always a good habit. Then you can restore if things go wrong.
---------- Post added at 01:24 PM ---------- Previous post was at 01:22 PM ----------
Oh, RSDLite will erase your backups anyway.
Either way, most problems can be fixed. Still need to wipe.
You can flash with Fastboot also.
I have taken a backup in TWRP and have restored that without any problem too. I would just go ahead and try copying the whole SDCARD to my computer just in case.
After that, if I do "fastboot erase system" before flashing stock system.img, do you think that will get rid of this "space is not enough" message?
I know I should not be worried about this, but, my stock camera is messed up and it continues to give me error even after return to stock. I have a feeling that this error message is leaving bad stuff on system partition that's causing this camera error.
Camera used to work find a couple of weeks back and I have not dropped the phone or anything for it to be broken now. Is there a diagnostic app that can tell me if my camera is physically broken? I have tried google camera too, it gives "can't connect to the camera" error.
It's likely an app that has taken the camera hostage, or its hardware. A fresh firmware install will prove which.
And yes, wiping system is important when you have issues like that. So do what you feel good about backing up and flash your firmware.
If you continue to get the Space error, I can't help....never encountered that one. Hopefully that's not hardware too....and related to the camera issue.
Good luck!
Can't erase system partition from fastboot, getting the following error:
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
ks73417 said:
Can't erase system partition from fastboot, getting the following error:
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
Click to expand...
Click to collapse
Well, you can try this guide from @KidJoe from step one and see how it goes.
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Other than that, not sure what else you can try. You have tried RSD Lite also??
And have you ever downgraded?? That could cause any number of issues.
Sorry, but out of ideas myself.
ks73417 said:
Can I try "fastboot erase system" before flashing system partition?
I'm afraid though the phone will not boot if flash fails after system erase.
Click to expand...
Click to collapse
First off, when working with SYSTEM, always use mFastboot. System on Moto phones is bigger than the stock fastboot can deal with.
Next, I've never seen anyone mention ERASING /system before. I've seen some posts by some who accidentally WIPED/Formatted /system from TWRP and had a heck of a time getting back to a working phone.
If you're trying to get rid of an error, its always safest to backup your data to a PC (connect the phone to PC via USB cable and copy the /SDcard contents to the PC's drive). NOTE: this doesn't keep game data, app data, etc. Just pix, video, music, downloads, etc. Then from mfastboot erase USERDATA and CACHE. You then need to re-install all your apps, and copy any data back.
If that doesn't fix the error, try using RSDLite or mFastboot to re-flash the STOCK SBF file for your phone, making sure it again erases userdata and cache. Standard warning: once on 4.4.2 or higher, NEVER DOWNGRADE the ROM on your phone!!! as you have the risks of bricking your phone!!!
Thank you KJ for your detailed response.
Turns out I have a defective phone, Motorola is sending me a replacement. It's very strange, if I pressed around the Camera thingy on the back, Camera will start working, then will go out after some time. I definitely think it's faulty hardware. I bought this Nov 2013 if that matters.
Has anybody else have had this issue with the Camera? everything else is flawless otherwise.
Next question I have is, when I do get my replacement phone tomorrow, what version of Android will it have? Will I be able to use sunshine on it just like I did on my current Moto Maker phone?
Thanks.
ks73417 said:
Thank you KJ for your detailed response.
Turns out I have a defective phone, Motorola is sending me a replacement. It's very strange, if I pressed around the Camera thingy on the back, Camera will start working, then will go out after some time. I definitely think it's faulty hardware. I bought this Nov 2013 if that matters.
Has anybody else have had this issue with the Camera? everything else is flawless otherwise.
Next question I have is, when I do get my replacement phone tomorrow, what version of Android will it have? Will I be able to use sunshine on it just like I did on my current Moto Maker phone?
Thanks.
Click to expand...
Click to collapse
Hopefully it's not 4.4.4. That's the only version I think you may have no luck with Sunshine on. Sunshine needs temporary root... And 4.4.4 can't be rooted this way. But definitely try sunshine anyway.
Hopefully you get a lower version... Or you get your device back.
---------- Post added at 03:48 PM ---------- Previous post was at 03:47 PM ----------
Also... You realize you may have a problem if Motorola realizes your current phone is unlocked? ?
I'm getting the replacement delivered tomorrow and will ship my current one on Thursday. what problem can I have potentially? they have already RMAed the current device for hardware problems, does it really matter to them if the bootloader is unlocked?
The bigger problem for them should be seemingly soft back of the phone that would make camera unusable after a little pressure !
ks73417 said:
I'm getting the replacement delivered tomorrow and will ship my current one on Thursday. what problem can I have potentially? they have already RMAed the current device for hardware problems, does it really matter to them if the bootloader is unlocked?
The bigger problem for them should be seemingly soft back of the phone that would make camera unusable after a little pressure !
Click to expand...
Click to collapse
Many have had no problems with warranty and unlocked devices.... Just technically unlocking bootloader voids the warranty on any X except the Dev Edition. Even if it's hardware related.
Just a heads up. ? cause just cause they are sending you a replacement, doesn't guarantee they don't inspect the device and decide to charge you for the replacement.
Tho when it's a completely obvious hardware issue... I'm sure someone would have to be in a very bad mood that day to do that.
Would be nice for others to hear how it works out for you. ?
I will keep you posted. Is there a way to lock the bootloader once I have used Sunshine to unlock it? I'm guessing there is not else you would have suggested that.
Believe I would have... I just did all that on my M8. But no, on the X you can relock the bootloader, but it's status will be " relocked". It won't return to "locked" status. So probably not worth relocking.
So, my worst fears are realised, the new phone has 4.4.4.
What are my options? Is there anyway to root? All I care about is Moto X tether using XPosed as I have UDP .
You can't root on locked 4.4.4.
Sunshine won't work cause it needs temp root first, which it can't do on 4.4.4.
Your only hope would be the China middleman. But it seems only January to May 2014 models (manufactured dates... See China middleman thread in general about it) can get codes from.
samwathegreat said:
Known error after you use twrp to wipe data. It shouldn't cause any problems..
Click to expand...
Click to collapse
Will it affect taking ota?? I got the same message on bootloader screen but phone booted up fine. I'm a little worried....
Thanks in advance.
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.
So I have a Nexus 6 stock room rooted (Systemless root). I have been a cm user ever since my Evo supersonic. I am unfamiliar with the correct way to apply the OTA that came out recently.
I have read that all that is needed is to flash system.img from the new archive. Is this true? Keep in mind I want to update without wiping my apps and data. I have been asking myself if I can give up phone-wide adblocking, and I'm going to give it a shot. The reason I've been asking this is because as I understand it, updating will remove twrp. This I don't really understand... Why would flashing system wipe recovery? Aren't they in different partitions?
I have done a lot of searching over a stupidly long period of time and have not found satisfactory answers.
Can I simply :
fastboot flash system system.img
or is there more to it than that?
Could someone please lay it all out for me?
Thanks
And yes I did see this thread: http://forum.xda-developers.com/nexus-6/general/easily-apply-ota-update-to-rooted-nexus-t3204018
And this one as well: http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
There are unanswered questions with both.
On the first link, why the hell would I erase the system partition? Wouldn't that be like doing a factory reset???
On the second one, why the hell would I flash the bootloader? Would it have changed from version to version and why would it matter if it had?
Why do I need anything other than to flash system.img over what is already there and flash the new radio?
So, erasing system before flashing is not really necessary, but it doesn't hurt, and definitely it's not factory reset. Erasing only makes sure that while flashing erases all files before flashing a partition, you want to be extremely sure.
And no, erasing system is not factory reset. Factory reset is erasing the data partition where the application data is stored, even for the system and private system apps. Actually TWRP only deletes the /data/data folder and some Android folders and leaves your other files safe when performing "factory reset".
You might need the boot.img, because it contains the kernel itself, so as these updated are security updates, it's probable they have patched some security hole in the kernel itself.
Finally the radio might have changed, but it usually doesn't. In fact AFAIK it hasn't changed since after the M previews, and the bootloader is the same as in the M previews. But if you don't have the previous factory images to do quick file diffs, it won't hurt to update them anyway.
So you need to flash boot and system, the re-flash SuperSu, and that"s that. If you want to make sure you won't have some system apps FC-ing in TWRP delete cache and dalvik. And if it'S TWRP prior to 3.0 don't let it modify your system partition.
And that's that.
Thank you
Forboding Angel said:
And yes I did see this thread: http://forum.xda-developers.com/nexus-6/general/easily-apply-ota-update-to-rooted-nexus-t3204018
And this one as well: http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Click to expand...
Click to collapse
Did you also take a look at this one: http://forum.xda-developers.com/nexus-6/help/how-security-update-ota-twrp-t3307409 ? Post #23 in that thread may answer your question as to why TWRP might get replaced with stock recovery.
Ahhhh ok that explains a lot. I think I'm going to try going straight stock with adblock browser and no root and see if I can put up with it.