Database Users

[Q] Failure to update 4.2.2

after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks

williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
you probably need stock recovery to complete the update... I would just wait for someone to root the update and then flash it that way

williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.

phonic said:
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.
Click to expand...
Click to collapse
is this problem caused by flashed kernel ??

williamlaw said:
is this problem caused by flashed kernel ??
Click to expand...
Click to collapse
Did you not bother to read anything I wrote?

I had the same problem. If you have a TWRP backup from a previous android version that allowed the ota to work just flash that and you'll still receive the ota for 4.2.2
Sent from my Nexus 7 using Tapatalk HD

This happened to me too, though I have the wifi-only version. So it's not just the radio.

I got the same problem with my Wifi version. Is there any fix yet? I only rooted the device but the rest is still stock. How come the update failed?

the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?

rexxxxx said:
the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?
Click to expand...
Click to collapse
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.

spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
finally flashed back to stock 4.2.1 then OTA update 4.2.2

spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
how ? I indeed have the mount stick installed for the OTG cable !

rexxxxx said:
how ? I indeed have the mount stick installed for the OTG cable !
Click to expand...
Click to collapse
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer

I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
So, is there any way of doing this without doing a wipe ? Or losing any of your data ?
What about putting the update, downloaded from google, on a USB stick and booting into twrp then flashing from there ?
I don't mind losing root, although I have rootkeeper installed, and I don't mind losing custom recovery, all of this can be fixed.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
What I don't want to do is lose my data. I have plenty of full twrp backups done, but then these are 4.2.1 backups. Backing up my apps isn't really feasible at the moment because of their sheer size. Horn, NOVA 3, the GTA games, bards tale, all gigs and gigs of data. Infact, I only have 1 gig left on a 32Gb N7, and I just don't have anywhere left to put a full backup of apps on to. I also don't want to download them all again, NOVA 3, for example, took me 6 hours to download on wi-fi.
I have read a lot of advice and help on here, plenty of googling which simply sends you back here anyway, and most advice centers around losing your data in some way. So, any help without losing data would be most appreciated,

spiou said:
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer
Click to expand...
Click to collapse
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app

After reading many threads and articles, I finally upgraded to 4.2.2 with stock recovery. Your mileage may vary.
Based on the discussions on http://forum.xda-developers.com/showthread.php?t=2148456, the failure may be caused by an app you installed
that corrupted some system files. Therefore, you have to flash 4.2.1 stock system and boot images back. The nice thing is your data and settings remain intact.
Although you lost root, it can be easily re-rooted using nexus root toolkit.
Now you're back to 4.2.1 which is allowed to upgrade, use OTA RootKeeper to keep su and then upgrade thru OTA. If you can not longer get OTA, you can clean data/stop/start Google Framework service, Google play service, and Google play store, and then re-check update. The last tip I read it somewhere but I forgot where I read it. Sorry.
Good luck. :laugh:
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse

JohnRM said:
I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
Click to expand...
Click to collapse
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....

rexxxxx said:
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You must clear the data of the Google framework (in the list of apps) and reboot immediately the tablet. Then the update will be proposed again.
One more thing : when you replace the file, check that the permissions are identical.

khaytsus said:
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
Click to expand...
Click to collapse
Exactly. I don't understand why we need to see posts like that over and over and over again. Hell, the OTA update will even tell the user what failed, and yet people still complain and ask what's wrong.
Also, while in most cases a custom recovery is OK (though the update will overwrite it), with the N73G unit, you need to use the stock recovery, otherwise it will fail without warning ahead of time.

spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
Can you elaborate? E.g., where do you get the original debuggerd from, how do you replace it (adb push?), etc.

Installing 5.0.2 on rooted tablet

So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff

viper2ko said:
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
Click to expand...
Click to collapse
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.

So if I get this right, OTA breaks also when recovery is stock, but supersu installed, modified hosts and gps.conf file

jshamlet said:
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
Click to expand...
Click to collapse
Only changed I have made are installing ad away

viper2ko said:
Only changed I have made are installing ad away
Click to expand...
Click to collapse
The HOSTS file came with the stock image. It counts, unfortunately. (I'm also an Adaway user)

Modify /system, you don't OTA. Period.
Just download the Nexus image and flash just system.img, not the batch file.

Can I flash the system.img in TWRP or do I need to flash the stock recovery?
And will this upgrade me from 5.0.1 to 5.0.2 without losing anything except for root?
Thanks!

^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.

yosmokinman said:
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
Click to expand...
Click to collapse
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.

flyinion said:
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
Click to expand...
Click to collapse
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.

magnumlove said:
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
Click to expand...
Click to collapse
Oh I wasn't going to do a fresh install (i.e. wiping everything), just flash that system.img or modify the batch file to remove the "-w" flag and just run that. I'm wary of running 3rd party ROMs now after I couldn't play movies through Play Movies that were downloaded to the device instead of streamed. Something to do with copy protection I guess

It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.

Telyx said:
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Click to expand...
Click to collapse
Assuming this was in reply to me? I'm not worried about losing anything. I've done the whole back it up and wipe between ROMs a ton on my OG Droid and Galaxy Nexus. In this case it's a worry that Play Movies for instance will detect that it is not a stock ROM/image and will disallow playing downloaded versions of movies in the app. I.e. you can download vs. stream for offline playback. I nearly found out the hard way (night before leaving on a vacation) that I couldn't play downloaded versions (it will download but not play them) when I for instance installed AOKP to my Nexus 7. As best I could tell from a bunch of Googling, it's something to do with copy protection.

It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.

Telyx said:
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Click to expand...
Click to collapse
Ah ok. Well, I ended up using fastboot to flash the system.img last night and looks like I'm good to go. I tried unrooting (SuperSU remove root function) and changing betterbatterystats to a non-system app first but the OTA still failed. Yeah I learned how to use the basic adb/fastboot stuff when I got my Galaxy Nexus and again with the N7. I figured that way if I totally broke something I'd know how to fix it, and all the fancy tools weren't around when the GNex first came out (at least I don't think they were).

I dirty flashed scrosler's 5.0.1 ROM when I got the 5.0.1 OTA notification, but when the 5.0.2 factory image was posted I fastboot flashed the system.img from that and rerooted. Naturally, less than half a day or so later, scrosler posted his 5.0.2.

So for someone that's not really too experience with fastboot, could someone post a step by step?
Where would I get the system.img?

Check the sticky threads for guides. Read and reread then get started on setting up the Android SDK. Once complete, type in the commands letter for letter.

[Q] What to expect if OTA MM over LP Verizon XT1575?

*NOTE: I tried to update my XT1575 Moto-X Pure Edition from a file on this page and it was a disaster! I now have the OTA visible on my phone, see screenshot, that keeps popping up. My phone is currently rooted, unlocked, and has TWRP installed, all courtesy of WinDroid tool. Windroid was painless, easy, and got the job done pretty quickly. Now that I can take the OTA update, is there an instruction page somewhere showing how to take the upgrade and keep root and recovery TWRP? That is the gist of what I really need.
I have a new Motorola Moto-X Pure Edition, rooted and TWRP with WinDroid app from Windows. This made it incredibly easy to unlock bootloader, install TWRPm and root. I am very happy with this system and some Xposed modules. I heard all the hoopla about the new Marshmallow rollout but did not have it offered to me on this phone. So, I did it manually from this page:
Stock/Rooted/Debloated X1575 6.0 MPH24.49-18
So much to choose from so I downloaded the moto_x_pure_edition_rooted_x1575_mph24.49-18_v1-deodexed.zip and flashed it in TWRP, after making a nandroid backup in TWRP. Everything seemed to work fine but I had problems after problems. My 32 GB ext-sdcard "vanished" and the system insisted that I reformat the card as "Portable" or "Permanent". I chose portable. I could not get Xposed working properly. My password manager would not work, when I updated from the play store, I got the message that all Android 6 apps now require a password at first run. Huh? What password? None of the passwords I have for the password managers would open the app.
Before losing 30+ GB of data on my ext-sdcard, I copied it to PC, then when complete I put it back in the phone, allowed the format as portable, then pulled the card and restored my stuff. Nothing was working right and it was pretty scary as this is my only phone. I restored the TWRP backup and had some settling in issues, but it worked, all but for WiFi. I could not turn it on! Like a spring on the switch, the moment you switched on WiFi, it snapped right back to the OFF position. No more WiFi. A friend sent me a stock recovery zip file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip.
This file, once unzipped, will flash the entire phone back to stock. He send me a small modem-flash.bat file because he thinks that I have an Android 6 radio in an Android 5 device. After running the flash-modem.bat, I got my WiFi back.
flash-modem.bat
Code:
@ECHO Off
@Echo Test
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
.fastboot reboot
Now I am really, really gun shy. I now have the dreaded update message on my phone, see screenshot. I found some good instructions here:
[GUIDE] Unlock/Root/Flash for Moto X Style/Pure
Are these instructions safe if I take the OTA update?
What preparations should be made prior to taking OTA aside from a TWRP backup?
Must I really format my ext-sdcard to use Marshmallow?
What other kind of weird things will happen?
Thank you so much, scared "sheetless in Florida"
:

Ohmster said:
*NOTE: I tried to update my XT1575 Moto-X Pure Edition from a file on this page and it was a disaster! I now have the OTA visible on my phone, see screenshot, that keeps popping up. My phone is currently rooted, unlocked, and has TWRP installed, all courtesy of WinDroid tool. Windroid was painless, easy, and got the job done pretty quickly. Now that I can take the OTA update, is there an instruction page somewhere showing how to take the upgrade and keep root and recovery TWRP? That is the gist of what I really need.
I have a new Motorola Moto-X Pure Edition, rooted and TWRP with WinDroid app from Windows. This made it incredibly easy to unlock bootloader, install TWRPm and root. I am very happy with this system and some Xposed modules. I heard all the hoopla about the new Marshmallow rollout but did not have it offered to me on this phone. So, I did it manually from this page:
Stock/Rooted/Debloated X1575 6.0 MPH24.49-18
So much to choose from so I downloaded the moto_x_pure_edition_rooted_x1575_mph24.49-18_v1-deodexed.zip and flashed it in TWRP, after making a nandroid backup in TWRP. Everything seemed to work fine but I had problems after problems. My 32 GB ext-sdcard "vanished" and the system insisted that I reformat the card as "Portable" or "Permanent". I chose portable. I could not get Xposed working properly. My password manager would not work, when I updated from the play store, I got the message that all Android 6 apps now require a password at first run. Huh? What password? None of the passwords I have for the password managers would open the app.
Before losing 30+ GB of data on my ext-sdcard, I copied it to PC, then when complete I put it back in the phone, allowed the format as portable, then pulled the card and restored my stuff. Nothing was working right and it was pretty scary as this is my only phone. I restored the TWRP backup and had some settling in issues, but it worked, all but for WiFi. I could not turn it on! Like a spring on the switch, the moment you switched on WiFi, it snapped right back to the OFF position. No more WiFi. A friend sent me a stock recovery zip file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip.
This file, once unzipped, will flash the entire phone back to stock. He send me a small modem-flash.bat file because he thinks that I have an Android 6 radio in an Android 5 device. After running the flash-modem.bat, I got my WiFi back.
flash-modem.bat
Code:
@ECHO Off
@Echo Test
C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb reboot bootloader
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
.fastboot reboot
Now I am really, really gun shy. I now have the dreaded update message on my phone, see screenshot. I found some good instructions here:
[GUIDE] Unlock/Root/Flash for Moto X Style/Pure
Are these instructions safe if I take the OTA update?
What preparations should be made prior to taking OTA aside from a TWRP backup?
Must I really format my ext-sdcard to use Marshmallow?
What other kind of weird things will happen?
Thank you so much, scared "sheetless in Florida"
:
Click to expand...
Click to collapse
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.

Hi Ohmster. Hope you are well. I experienced the exact same "mess" as you have. In fact, I had the identical setup (Lollipop, TWRP, Nova, etc.). I tried the FLASH-ALL approach multiple times as well as separate reflash of the modem included in the CLARK_RETUS zip (followed steps line by line). But I'm still stuck without wifi (slides back to "off" immediately). prior to all this, I did a factory wipe as well as subsequent "fastboot -w". Any ideas? I'm on day 3 without a phone Thanks in advance for your wisdom!!

nypeach said:
Hi Ohmster. Hope you are well. I experienced the exact same "mess" as you have. In fact, I had the identical setup (Lollipop, TWRP, Nova, etc.). I tried the FLASH-ALL approach multiple times as well as separate reflash of the modem included in the CLARK_RETUS zip (followed steps line by line). But I'm still stuck without wifi (slides back to "off" immediately). prior to all this, I did a factory wipe as well as subsequent "fastboot -w". Any ideas? I'm on day 3 without a phone Thanks in advance for your wisdom!!
Click to expand...
Click to collapse
Hi Ohmster. Seems that your "positive mojo" did the trick... I tried one more time and finally up and running. Thanks for your posts and wisdom!!!

samwathegreat said:
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Click to expand...
Click to collapse
Do you think it would work if I did a Full Unroot using SuperSU and then uninstalled it using TiBu. Then flashed stock recovery using the restore to stock tool. So at that point I would have unrooted, removed SuperSu, and flashed back the stock recovery image. Do you think this would do the trick, or is it just best to completely flash the entire device using the restore to stock tool in full. I can recover from a soft brick but don't want a complete brick. Do you think my method is worth a try and that it wouldn't cause a complete brick condition? I would like to not have to reset my phone completely, but will if that is the only best way to get onto MM. Thanks.

nypeach said:
Hi Ohmster. Seems that your "positive mojo" did the trick... I tried one more time and finally up and running. Thanks for your posts and wisdom!!!
Click to expand...
Click to collapse
Actually my XT1575 is running and is in good shape now. I was lucky, @OldBaldy got on Hangouts with me and walked me through it. He sent me a large file which I believe to be the original stock rom for the Moto-X with a flash.bat file in so as long as you have your Windows drivers installed with ADB and Fastboot working. It took me the entire night to get that working with the correct drivers because Baldy had to go to bed.
The file I really needed for this is a 1.27 GB file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip. He told me NOT to run the FLASH-ALL.bat inside because all he wanted to do was reset the WiFi radio from an Android 6 radio to an Android 5 radio. Baldy was really smart and edited the restore system bat file to a tiny little "StockROM_FlashModem.txt" and it worked! WiFi came right back!
After that, I had to use adb over USB to flash the system back to original lollipop with no root, take the OTA update, then flash the boot.image file, update done, then flash the boot.img before installing SuperSU and most of this we did with ADB over USB. You cannot flash BETA-SuperSU-v2.52.zip until you flash that boot.img file.
If I was smart, I would have copy/pasted all the adb stuff we did into a text file, but of course, I didn't. But yes it is all working quite well now.
BEWARE:
Xposed does work in MM but not everything. I had to go back to TWRP, remove Xposed, and then enable only a couple of them that I know are safe like AdBlocker and Greenify.
I cannot give you anymore details since I screwed it up myself a couple of times and ended up redoing it on my own and again with Baldy's help.
NOTE:
Baldy did want something out of all this help he was giving me, he wanted the very first nandroid TWRP backup system files that I made immediately as soon as I got the update done because that is a perfectly clean backup and if you ever wanted to put your phone back to stock, that backup would do it.
Before giving up on Xposed and being sure that this was lousing up my phone; self boots, black screen, would not boot, bootloop, etc., I finally realized that this phone actually WORKS, man. It has to be the Xposed files,and modules that are causing the problems. And after removing all but the 2 I mentioned, the phone works great now. I will add more modules, very, very slowly and test each one for a couple of days before I clear it and dare add another one.

Ohmster said:
Actually my XT1575 is running and is in good shape now. I was lucky, @OldBaldy got on Hangouts with me and walked me through it. He sent me a large file which I believe to be the original stock rom for the Moto-X with a flash.bat file in so as long as you have your Windows drivers installed with ADB and Fastboot working. It took me the entire night to get that working with the correct drivers because Baldy had to go to bed.
The file I really needed for this is a 1.27 GB file, CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip. He told me NOT to run the FLASH-ALL.bat inside because all he wanted to do was reset the WiFi radio from an Android 6 radio to an Android 5 radio. Baldy was really smart and edited the restore system bat file to a tiny little "StockROM_FlashModem.txt" and it worked! WiFi came right back!
After that, I had to use adb over USB to flash the system back to original lollipop with no root, take the OTA update, then flash the boot.image file, update done, then flash the boot.img before installing SuperSU and most of this we did with ADB over USB. You cannot flash BETA-SuperSU-v2.52.zip until you flash that boot.img file.
If I was smart, I would have copy/pasted all the adb stuff we did into a text file, but of course, I didn't. But yes it is all working quite well now.
BEWARE:
Xposed does work in MM but not everything. I had to go back to TWRP, remove Xposed, and then enable only a couple of them that I know are safe like AdBlocker and Greenify.
I cannot give you anymore details since I screwed it up myself a couple of times and ended up redoing it on my own and again with Baldy's help.
NOTE:
Baldy did want something out of all this help he was giving me, he wanted the very first nandroid TWRP backup system files that I made immediately as soon as I got the update done because that is a perfectly clean backup and if you ever wanted to put your phone back to stock, that backup would do it.
Before giving up on Xposed and being sure that this was lousing up my phone; self boots, black screen, would not boot, bootloop, etc., I finally realized that this phone actually WORKS, man. It has to be the Xposed files,and modules that are causing the problems. And after removing all but the 2 I mentioned, the phone works great now. I will add more modules, very, very slowly and test each one for a couple of days before I clear it and dare add another one.
Click to expand...
Click to collapse
Hi Ohmster. Thanks again. So are you on Marshmallow? I got back with your info above and back to 5.1.1 (CLETUS). I tried to take the OTA and it downloaded, went to install, and I watched it just say "error" while on the installation screen. I'm going to try again. Let me know if you all set or in the same boat Thanks again!

samwathegreat said:
Two points:
1. You can never ever ever take any OTA with a custom recovery (TWRP) installed. You MUST flash stock recovery prior to taking the OTA.
2. The update will fail if you have made ANY modifications to /system. This includes using TWRP to flash SuperSu to your device.
So if you just do a complete FULL return to stock and have a working lollipop installation, DO NOT INSTALL TWRP OR INSTALL SUPERSU. Take the OTA update. Afterwards you are free to go ahead and flash TWRP. I recommend IMMEDIATELY making a nandroid backup once you have taken the OTA and flashed TWRP.
I also suggest using the new "systemless root" method instead of the traditional root method. If you use systemless root, you won't need to restore /system (as long as you didn't modify it by flashing Xposed, Adaway, or similar. If a future OTA comes out with systemless root, you simply flash the stock kernel (which will unroot you), then accept the new update, then modify the boot image again to re-gain root.
To sum it up: *IF* you are 100% stock on lollipop (no TWRP, no SuperSU), you can go ahead and take the OTA. Afterwards, you can do whatever you would like (flash TWRP, SuperSU, etc). Just keep in mind that if you don't use the new systemless root, you will have to do a full return to stock AGAIN the next time an OTA comes out.
Good Luck.
Click to expand...
Click to collapse
nypeach said:
Hi Ohmster. Thanks again. So are you on Marshmallow? I got back with your info above and back to 5.1.1 (CLETUS). I tried to take the OTA and it downloaded, went to install, and I watched it just say "error" while on the installation screen. I'm going to try again. Let me know if you all set or in the same boat Thanks again!
Click to expand...
Click to collapse
Did you get back to stock using CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip? I have still not gone through the process yet as I am concerned about messing up the process. I want to ask a few questions here. I am well accustomed to fastboot flashing but want to be exactly sure of what to flash and the reason for doing it. I am on stock 5.1.1 LP with bootloader unlocked and rooted with SuperSU. So first I need to use Shawn5162's zip to restore me back to complete stock without root, then I need to go in and setup the phone to at least get the MM OTA, then install the OTA and hope all goes well. Lastly, to root again I need to use Shawn5162's zip to flash boot.img only, then flash TWRP, and finally flash SuperSU again. Is all this correct? Thank you.

robn30 said:
Did you get back to stock using CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162.zip? I have still not gone through the process yet as I am concerned about messing up the process. I want to ask a few questions here. I am well accustomed to fastboot flashing but want to be exactly sure of what to flash and the reason for doing it. I am on stock 5.1.1 LP with bootloader unlocked and rooted with SuperSU. So first I need to use Shawn5162's zip to restore me back to complete stock without root, then I need to go in and setup the phone to at least get the MM OTA, then install the OTA and hope all goes well. Lastly, to root again I need to use Shawn5162's zip to flash boot.img only, then flash TWRP, and finally flash SuperSU again. Is all this correct? Thank you.
Click to expand...
Click to collapse
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk

OldBaldy said:
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.

robn30 said:
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
Click to expand...
Click to collapse
That boot img is for style only, not for pure. There is another called boot_root_mm_clark_retus.zip
Search for that file, it's the one you need for Supersu 2.5.2
You can use either supersu 252 of 256. I used 252 and have had no problems. If you have flashed TWRP, just put the supersu of your choice and the boot_root.zip files on you phone and flash with TWRP.
Sent from my XT1575 using Tapatalk

OldBaldy said:
That is the correct firmware. You don't need to remove anything. All you need to do is flash recovery and system, reboot and take the OTA. Make sure you have the new TWRP ( 2.8.7.1 ) downloaded, the 2.8.7.0 won't work with the new bootloader. I used the modified boot image and supersu 2.52 because I did not care about modifying the system partition. You can use Supersu 2.62 for systemless root if you wish. If you're planning to use Xposed, then systemless gives you no added benefits.
Always, before starting something like this, make a nandroid!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
IGNORE ME My Bad.... Back at 5.1.1 and staying here for a while Thanks again for your awesome support. I really appreciate it.

nypeach said:
Hi OldBaldy. Sorry I'm still having a tough time. As mentioned, I got back to 5.1.1 per the above process. I read your latest note and flashed the latest twrp (2.8.7.1) and took the MM OTA. It's now flashing the "teamwin" screen over and over. Should I be patient or bail? Thanks again for your patience and help!!!
Click to expand...
Click to collapse
You have to take the OTA BEFORE you flash TWRP. What you need to do now is get back into fastboot and flash the stock recovery img from the 5.1.1 factory image. Then reboot into system and take the OTA. After it installs, then follow the above instructions.
Sent from my XT1575 using Tapatalk

robn30 said:
So, I couldn't wait and already did it. I flashed Shawn5162's file in full. Then I took the OTA and updated perfectly. I have already installed TWRP 2.8.7.1 and made a nandroid of my Stock unrooted MM ROM. Now I want to root but want to make sure I understand this step perfectly. Which boot.img do I use? The ones in this thread http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380? The boot.img in that thread is way smaller than the one in Shawn5162's LL zip tool. Just want to be sure I am doing this correctly. Lastly am I using the SU file in that thread as well and following those exact directions? Thanks.
Click to expand...
Click to collapse
No, that is the wrong root img to flash prior to installing SuperSU 2.52.
File Type: zip boot_root_mm_clark_retus.zip - [Click for QR Code] (10.01 MB, 756 views)
The file you want is in this post #290

Ohmster said:
No, that is the wrong root img to flash prior to installing SuperSU 2.52.
File Type: zip boot_root_mm_clark_retus.zip - [Click for QR Code] (10.01 MB, 756 views)
The file you want is in this post #290
Click to expand...
Click to collapse
Yup, I realized that plus someone else informed me that wasn't the one. I got her all taken care of and she is up and running smooth as can be. The battery on MM is really good. I'm impressed. I also wrote up a huge how to on the whole process and posted it. Should contain all the necessary steps in one place now. It gets a bit crazy having to dig all over the place to gather all that is needed. These threads get quite large and finding stuff gets more difficult as the days go by.
Sent from my XT1575 using Tapatalk

Marshmallow and root

Hey. I had rooted 5.1.1 Moto X Style and did a return to stock 5.1.1. eu version (relocked bootloader). After booted up, I received update to Marshmallow, I installed it. It worked. Later I wanted to root it, so I unlocked bootloader again and also did flash custom recovery - TWRP (twrp-2.8.7.1-clark). Later I restarted device and its was stuck on logo of Motorola. Nothing boots up.
Cant find solution for this. Thanks.
UPDATE:
Solved my issue here.
UPDATE2:
If there is problems upgrading your device to Marshmallow, I would suggest install custom ROM TruPureXMM with custom KERNEL Frankenclark. I am using this combo for long period of time and now I can suggest to others too!

Mine is having a similar issue. Mine took forever to boot at your stage because it formatted itself. Once I flashed SuperSU is where mine refused to boot. I have no idea what's going on either.

I am having the exact same issue. I updated to Marshmallow, installed TWRP (twrp-2.8.7.1-clark), flashed SuperSU and the phone hung on the Motorolla Logo at boot. I was still able to access the boot loader (holidng down the volume and the power button) and attempted to restore using http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905. I was able to restore however now my wifi does not work and therefore I cannot update to Marshmallow OTA.

dgato said:
I am having the exact same issue. I updated to Marshmallow, installed TWRP (twrp-2.8.7.1-clark), flashed SuperSU and the phone hung on the Motorolla Logo at boot. I was still able to access the boot loader (holidng down the volume and the power button) and attempted to restore using http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905. I was able to restore however now my wifi does not work and therefore I cannot update to Marshmallow OTA.
Click to expand...
Click to collapse
You need to reflash the LP radio from the restore all file ( NON-HLOS.bin ). That should do it.

I'm having the exact same issue. I'm so glad you posted. I gave up and used the restore-to-stock tool as well, but my Wi-Fi isn't working either. What is LP radio and how do I flash it? Now that I've restored to stock, I no longer have TWRP, and because I don't have WiFi, I can't update to Marshmallow.

JayShams said:
I'm having the exact same issue. I'm so glad you posted. I gave up and used the restore-to-stock tool as well, but my Wi-Fi isn't working either. What is LP radio and how do I flash it? Now that I've restored to stock, I no longer have TWRP, and because I don't have WiFi, I can't update to Marshmallow.
Click to expand...
Click to collapse
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.

BooBzi said:
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
Click to expand...
Click to collapse
Terrific! It actually worked! Thank you.
Did you find a solution for it being stuck at Motorola logo? I was also stuck on that after installing TWRP.

ChadMan097 said:
Mine is having a similar issue. Mine took forever to boot at your stage because it formatted itself. Once I flashed SuperSU is where mine refused to boot. I have no idea what's going on either.
Click to expand...
Click to collapse
Looks like you flashed SuperSU but didn't flash the boot_root.img , or you can use the systemless root.

JayShams said:
Terrific! It actually worked! Thank you.
Did you find a solution for it being stuck at Motorola logo? I was also stuck on that after installing TWRP.
Click to expand...
Click to collapse
Nop, could find solution, so I did full wipe, and restored my backup file with 5.1.1. Also flashed stock logo, boot and modem, so it can boot my old 5.1.1. Moto.
Will wait for some kind of european ROM with Marshmallow, or TWRP update. Maybe later will try again to go fully stock and upgrade to Marshmallow, maybe will find something that will work, right now I just need my "phone" back so I can use it as daily driver.

I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.

JayShams said:
I just finished flashing TruPureXMM. I'm in the middle of restoring all my apps, and I still need to re-fix the WiFi, but otherwise my experience is working well. You might want to check that out.
Click to expand...
Click to collapse
For wifi you should flash modem from his thread: https://www.androidfilehost.com/?fid=24269982087017262
Its Pure modem with band 12 fix.
I was using his Rom for some hours and didnt like it, my personal opinion:
Good: easy to install; twrp, supersu, xposed is working.
Bad: modified kernel (had more problems with it, it was draining battery so fast - 4 little cores was always online for ~900-1440MHz, and 1 big core always online for same frequancy as little cores, only one big core was going idle), so I didnt like all this modifications to stock kernel, also I didnt like that mine EU version now is listed as US version XT1575, and last that I noticed after some hours of usage is that on secret menu, mine 3G network was listed as WCDMA, but on EU of mine Style same 3G is using GSM auto method. I suppose that there can be some difficulties in EU countries - after changing settings to 4G, I loosed signal, and only after restart I got it back.
Thats the main reasons why I want european rom, or to modifie stock eu MM with xposed.

patt2k said:
Looks like you flashed SuperSU but didn't flash the boot_root.img , or you can use the systemless root.
Click to expand...
Click to collapse
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.

ChadMan097 said:
I think in that case I did flash SuperSU the old way for Stock Moto Marshmallow. I then did a TWRP backup to go back to full stock and tried rooting using systemless, but something isn't right. It's showing up, apps are asking for permission, but its acting odd. The apps can't get permission and Viper for example just crashes and other apps just keep saying something is wrong. My TWRP is messed up to. It was pushed correctly, but it seems very unstable. I can't flash any ROMs and if I plug it into my computer to send a file, when I reboot it no longer shows it in my directory to install. Sometimes if I hit reboot device, it only reboots recovery or just ignores the command entirely. I think I will revert it back to moto standard and try again, but this has been a little weird.
Click to expand...
Click to collapse
Either do systemless or 2.52 had same issue til I flashed 2.52
Sent from my XT1575 using Tapatalk

Solved my issue here.

BooBzi said:
If you want WIFI on stock 5.1.1 you need to flash right modem for you.
You should download .zip file that contains all stock files, unzip it, and find "NON-HLOS.bin", thats modem file that you need.
Now boot into fastboot mode (power+volume down), and from PC use "fastboot flash modem NON-HLOS.bin"
Restart device, you should be okey now.
For XT1572 "STYLE" EU you can download this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTUU4cUVmcUtBTEU/view;
But for XT1575 "PURE" US use this file: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view.
If you are using other device, use this thread http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486 to find your device, but this threads links are very slow.
Click to expand...
Click to collapse
fastboot flash modem NON-HLOS.bin
Where and how do I type this? I have everything else done.

Hi,
I followed this instructions and I have two problems:
It only boots using flashboot boot boot.img (in fact I can't do the fastboot reboot-bootloader command because the previous command just boots the phone)
There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work

donebrasko said:
fastboot flash modem NON-HLOS.bin
Where and how do I type this? I have everything else done.
Click to expand...
Click to collapse
For this you need adb files on your PC.
You should read this thread, for how to get this files on your PC.
Then:
Basically, open terminal within adb driver folder, connect phone via USB to PC with USB Debugging ON, and you are ready to go - boot your phone into fastboot mode (shut down phone first, and then power+volume down) and now your are ready to use this command: fastboot flash modem NON-HLOS.bin, but remember to put this "NON-HLOS.bin" file into folder where you opened terminal from.
But if you experience problems, I suggest just install TruPureXMM ROM. It whould be much easier!
Good luck!

Kennyeni said:
Hi,
I followed this instructions and I have two problems:
It only boots using flashboot boot boot.img (in fact I can't do the fastboot reboot-bootloader command because the previous command just boots the phone)
There's no wifi, I tried flashing the modem linked before but I think that's for 5.1.1 so it didn't work
Click to expand...
Click to collapse
Hello!
Have you read my other thread?
I have explained all my steps there, my device is Moto X Style (XT1572).
But I can suggest also use TruPureXMM ROM. Right now I am using this rom for about month, you could try it!
Good luck!

No luck with reflashing NON-HLOS.bin
I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.

[email protected]@lker said:
I tried systemless root on my moto x pure marshamallow. Now the wifi is not working at all. I tried reflashing the NON-HLOS.bin but no luck there. Is there any way to solve this issue? Or should i revert back to lollipop seems like it is working just fine for others on lollipop.
Click to expand...
Click to collapse
Lets start from beginning.
What is your device codename (region)?

WiFI wont work after root

I should start this off by saying that i have no idea how to root a device and i am now currently aware of how stupid my actions were.
I've searched the forums for about 2 hours now and i've yet to find a solution to this problem which is stressing me out like you wouldn't believe.
about i year ago i tried to root my Moto X Pure edition but i failed miserably so i returned to stock and lived without. This morning i decided i would try to root again but it isn't going so well.
I followed this guide: http://forum.xda-developers.com/moto-x-style/general/root-moto-x-style-xt1572-br-marshmallow-t3259380 And everything worked fine until i noticed that my wifi wasn't working.
I then decided to flash back to the original boot image which i found from this site: http://androiding.how/systemless-root-moto-x-style-marshmallow-mph24-49-18/ But my wifi still refuses to turn back on
By now I'm a bit stressed out and not thinking straight. I then recalled that device encryption can screw with the rooting process so i decided to factory reset (how stupid can i get.)
So now im sitting at the welcome screen and my XT1575 cant find a wifi network so im going to have to restore my device over cellular data.
What do i do!?!?!?!?!!?!?
EDIT: i just realized the first link i posted was for the XT1572. I feel so stupid. how do i restore original functionality to my device?

I have had this issue before but on a Moto X Style (XT1572). You need to flash the modem again through fastboot/ADB. You first need to download the full stock firmware and extract it on a PC. Reboot your phone into bootloader mode and run the following command through command prompt/terminal:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
You may need to do this twice as it doesn't work always first time. Refer to this post for more information:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
HTH,
Ooms

dj_ooms said:
I have had this issue before but on a Moto X Style (XT1572). You need to flash the modem again through fastboot/ADB. You first need to download the full stock firmware and extract it on a PC. Reboot your phone into bootloader mode and run the following command through command prompt/terminal:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
You may need to do this twice as it doesn't work always first time. Refer to this post for more information:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
HTH,
Ooms
Click to expand...
Click to collapse
I've learned a lot in the past two hours. I did try to reflash the modem multiple times with multiple different files without any success. I don't think the method i was following works for XT1575 specifically.
I am currently back on stock with wifi working. I like the idea of a systemless root, but i couldn't find a method that works for the Pure. So i guess i will continue to run stock until i get a new phone (that might be a while.)

UC_Nightmare said:
I've learned a lot in the past two hours. I did try to reflash the modem multiple times with multiple different files without any success. I don't think the method i was following works for XT1575 specifically.
I am currently back on stock with wifi working. I like the idea of a systemless root, but i couldn't find a method that works for the Pure. So i guess i will continue to run stock until i get a new phone (that might be a while.)
Click to expand...
Click to collapse
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms

dj_ooms said:
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms
Click to expand...
Click to collapse
Thanks for the suggestion. Before I try rooting again though, is there a way to completely backup my phone to my computer without using twrp? its a pain logging into all my app and setting everything up every time i try to root my phone.

UC_Nightmare said:
Thanks for the suggestion. Before I try rooting again though, is there a way to completely backup my phone to my computer without using twrp? its a pain logging into all my app and setting everything up every time i try to root my phone.
Click to expand...
Click to collapse
The only app I am aware of without root is Helium. I haven't tried it personally but I think you need to have an app running on your PC and the phone connected to it. I personally use TWRP with Nandroid Manager and Titanium Backup. These both need root though. You could always make a backup through TWRP prior to flashing the pre-rooted ROM, then flash the ROM as always recommended. If you run into issues, just restore the backup through TWRP, then flash the stock recovery back through fastboot/ADB to be backup to your original state.
HTH,
Ooms

dj_ooms said:
Glad you managed to sort out your WiFi.
If you are on stock ROM but have tried root, it means you already have an unlocked bootloader. You could always try and flash TWRP and then flash a pre-rooted stock ROM from here:
[ROM] Flashable Stock/Rooted X1575 6.0 MPHS24.49-18-4 (May security update)
This will give you what you are after minus the stock recovery. You could then just reflash the stock recovery using fastboot/ADB:
Just download the full stock of the firmware version you flashed through TWRP and then extract and flash the respective version recovery from here:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
You should then be completely stock with root.
I tried systemless root on my XT1572 and didn't get on with it. Kept having issues so just went with full root and am happy with my phone as it is; stock 6.0.1 with full root and a few stock apps removed that I don't use/need.
HTH,
Ooms
Click to expand...
Click to collapse
Maybe i am missing something but why would i want to flash stock recovery after i flash for example "XT1575 Rooted 6.0 Odexed with May security update" from the first link you provided?

UC_Nightmare said:
Maybe i am missing something but why would i want to flash stock recovery after i flash for example "XT1575 Rooted 6.0 Odexed with May security update" from the first link you provided?
Click to expand...
Click to collapse
I think i can answer my own question now. TWRP is a "custom recovery" and after i use TWRP i can flash something over it so that i can be stock. The terminology around these parts is quite confusing

i've gone and ****ed everything up again. I flashed twrp and then tried to install a zip from the first link you provided but my phone refused to unlock
I did a factory reset from within twrp and reinstalled the zip but now my wifi isnt working again.
Is rooting always such a pain in the ass?

UC_Nightmare said:
i've gone and ****ed everything up again. I flashed twrp and then tried to install a zip from the first link you provided but my phone refused to unlock
I did a factory reset from within twrp and reinstalled the zip but now my wifi isnt working again.
Is rooting always such a pain in the ass?
Click to expand...
Click to collapse
When rooting, there is always a risk. I have been flashing phones for over 10 years and it is always a learning experience. Even now i have occasionally done something and thought I've completely mucked up my phone. You just need to make sure you follow exactly what is stated as the procedure and if you run into problems, there is always someone at hand to help in this great forum.
Out of curiosity, did you follow the standard procedure for installing a new ROM? You will lose all data doing the standard procedure but can restore most stuff from your Nandroid backup. The steps I always do is:
1. Make a backup
2. Wipe data, system, dalvik/art and cache partitions
3. Flash your ROM
4. Wipe dalvik/art and cache again
5. Reboot
Click to expand...
Click to collapse
That is the standard recommended procedure for flashing all ROMs in TWRP. I have an EU XT1572 and have successfully used this ROM on my phone. The ROM contains everything you need including the modem. The modem is for the US XT1575 but worked fine on my phone. For sanities sake, I flashed the EU modem after and still had everything working.
Just another point, your phone needs to have been updated to Marshmallow before you can run one of these ROMs. If you are on Lollipop you may run into issues, especially from a radios perspective.
Another thing to point out is that all ROMs are started that you flash at your own risk. Developers will not be held responsible for anything going wrong. As long as you follow the guides and don't flash a ROM for a completely different device, you shouldn't run into any issues and more often then not can bring your phone back to a functional state if you do.
HTH,
Ooms

Flash twrp
Make backup
Flash su 2.62-3
Done.

Or...
1. Flash the factory image
2. Flash TWRP
3. Flash this attachment in TWRP, which will force install SuperSU 2.78 SR-1 systemless-ly. I've shared and posted about it before in this thread.
Nothing's changed with the attached zip here, except it has the latest version of SuperSU included as of this post.