Related
Anyone tried and confirmed working the old adb backup method that doesn't require root?
http://forum.xda-developers.com/showthread.php?t=1420351
Was hoping to use this method to backup before unlocking. I got into the usual problem of not wanting to unlock right away (in case issues etc.) then once I was comfortable with the unit too lazy to want to set up all up again from scratch....
Use helium. Backup each app individually. There are some apps that will Bork restore.
Sent from my Nexus 7 using XDA Premium HD app
bummer screw that for a joke then LOL
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
wintermute000 said:
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
Click to expand...
Click to collapse
Unlocking doesn't prevent you from getting the OTAs.
If you want root to be compatible with OTAs, see this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
yeah I know that, I know I can reflash stock recovery and unroot etc. just too lazy to be bothered setting up all my apps losing saves etc. at this point short of mucking around with carbon. TBH if the multitouch issue is fixed or at least toned down there's not a lot of incentive to root for me aside from adblock.
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
wintermute000 said:
yeah I know that, I know I can reflash stock recovery and unroot etc.
Click to expand...
Click to collapse
My point is you don't need to unroot nor flash stock recovery (though it is safest to flash stock recovery)
The JSS15J OTA update will flash fine with root and twrp with just the small fix I referenced.
wintermute000 said:
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
Click to expand...
Click to collapse
JSS15J already included firmware updates, it updated aboot, sbl, tz, and rpm. Bootloader went from 3.05 to 3.14 and it flashed ok with root and twrp (though again, personally I suggest using stock recovery)
Also you don't need to install twrp persistently to root. I just boot into twrp one-time by using fastboot boot twrp.img to install the root files and leave stock recovery on the tablet.
With the one simple fix referenced above, you can have stock recovery, root, and be totally compatible with future OTAs, no need to revert anything. Of course after the OTA is successful, just re-run the SuperSU zip and the fix to set yourself up with root and await the next OTA.
On this nexus, you need to unlock even to do the official factory restore google published. The official images don't come with signatures.
To answer the question re adb bu, yes it works just fine.
Sent from my Nexus 7 using Tapatalk 4
*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
I take no credit for any of this. Monkey saw, monkey did. MAKE SURE YOU FULLY READ THE ORIGINAL POSTS AS THE MONKEY MAY HAVE OMITTED SOMETHING. If you are clueless, not good at following instructions, or apprehensive you might want to pass. If you managed to already get unlocked and TWRPed, I imagine you are good to go. Still, if you break your phone, it's on you.
1. Do a TWRP backup.
2. Flash one of the choices here (READ THE ENTIRE THREAD) :
https://forum.xda-developers.com/moto-x-style/development/rom-marshmallow-6-0-september-2016-t3536120
REBOOT.
I went with the Deodexed one. Check out the Mods too. I added Viper.
3. Get Systemless Root back using using the flash-able Script in Post #8 here (READ ALL 1st):
https://forum.xda-developers.com/moto-x-style/general/systemless-root-info-t3373864
3a. Direct Link here:
https://forum.xda-developers.com/attachment.php?attachmentid=3809946&d=1468261256
REBOOT
I was still stock but Rooted with Xposed and I successfully Dirty Flashed. OP still recommends a CLEAN Install. After running the script, the phone came back looking the same. I did lose my custom Boot Animation and Viper so I re-flashed them. I also flashed the latest SU just to be sure i had the latest. Probably makes no difference.
Build now says MPHS24.49-18-8 and security Patch 09/01/2016.
Be sure and thank the OP's for the flash-able Update and the Systemless script.
THANK YOU OP'S,
Monkey
Except people have to understand... this puts you in a potentially precarious position. Your bootloader, radios, and partition table are all from a previous ROM version, but your system and boot/kernel are from the current release. Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
acejavelin said:
...Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
Click to expand...
Click to collapse
When you say "cannot go back" does something get flagged where a TWRP system wipe and restore of a backup would not work?
G_Man18 said:
When you say "cannot go back" does something get flagged where a TWRP system wipe and restore of a backup would not work?
Click to expand...
Click to collapse
No... That's fine. I mean you can't flash the full system image via fastboot.
acejavelin said:
No... That's fine. I mean you can't flash the full system image via fastboot.
Click to expand...
Click to collapse
Thanks for the quick response. I am surprised how many people get in trouble when TWRP backups are easy to do and can get you going when you screw up--which does happen to all of us. I post little but do read quite a bit in these forums; most of my questions have already been answered. You say you will nudge people in the right direction, but from what I have seen, no one on here answers as many questions so meticulously as you. Thanks!
acejavelin said:
Except people have to understand... this puts you in a potentially precarious position. Your bootloader, radios, and partition table are all from a previous ROM version, but your system and boot/kernel are from the current release. Meaning your stuck on this or other custom ROMs and cannot go back to "pure" stock, at least until there is official full factory firmware release for the September update.
Not saying this isn't a valid way to do it, but it isn't truly getting the update... not completely, so my advice to others is proceed with caution and know the possible consequences, they may or not matter to you.
Click to expand...
Click to collapse
I just received the notification for this update, is it okay to take it, or is it going to cause issues. I am unlocked and rooted currently running MPHS24.49-18-4. I would restore back to a non-rooted TWRP backup of the same build, then flash back the original recovery image, clear cache and dalvik, and finally flash the update.
Will this work and is It okay to update to this build? Thanks.
robn30 said:
I just received the notification for this update, is it okay to take it, or is it going to cause issues. I am unlocked and rooted currently running MPHS24.49-18-4. I would restore back to a non-rooted TWRP backup of the same build, then flash back the original recovery image, clear cache and dalvik, and finally flash the update.
Will this work and is It okay to update to this build? Thanks.
Click to expand...
Click to collapse
If you return to stock, meaning the /system and /boot partitions and recovery is stock, it should work... how you get there isn't as important. But you can't just "flash" the OTA zip file, not directly... and I am not positive if the stock recovery supports sideloading official ZIPs or not, but you should be able to accept it and let it apply itself. The lock or unlock state of the bootloader isn't relevant.
So most likely it would work fine... but backup first, just in case something goes wrong.
acejavelin said:
If you return to stock, meaning the /system and /boot partitions and recovery is stock, it should work... how you get there isn't as important. But you can't just "flash" the OTA zip file, not directly... and I am not positive if the stock recovery supports sideloading official ZIPs or not, but you should be able to accept it and let it apply itself. The lock or unlock state of the bootloader isn't relevant.
So most likely it would work fine... but backup first, just in case something goes wrong.
Click to expand...
Click to collapse
Backup is running right now, so that will be good to go. With systemless root can I perform a full unroot using SuperSU or is it better to restore the unrooted TWRP backup? Thanks.
robn30 said:
Backup is running right now, so that will be good to go. With systemless root can I perform a full unroot using SuperSU or is it better to restore the unrooted TWRP backup? Thanks.
Click to expand...
Click to collapse
If you are rooted, it means you did something with root, right? So unless you are going to undo everything root and then unroot, better to restore the pre-root backup
acejavelin said:
If you are rooted, it means you did something with root, right? So unless you are going to undo everything root and then unroot, better to restore the pre-root backup
Click to expand...
Click to collapse
Very good, thanks for the advice. Good thing I made an unrooted backup when I updated to the May Security update. I knew that would come in handy eventually.
robn30 said:
Very good, thanks for the advice. Good thing I made an unrooted backup when I updated to the May Security update. I knew that would come in handy eventually.
Click to expand...
Click to collapse
Update went perfectly smooth by restoring back to an unrooted 24.221.4 TWRP backup, then flashing stock recovery, and finally taking the update to 24.221.8. I did perform a wipe off cache and dalvik at least twice during the process.
Sent from my XT1575 using Tapatalk
robn30 said:
Update went perfectly smooth by restoring back to an unrooted 24.221.4 TWRP backup, then flashing stock recovery, and finally taking the update to 24.221.8. I did perform a wipe off cache and dalvik at least twice during the process.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Just to be sure. I ran TWRP from Fastboot in ADB as soon as Unlocked and turned the phone on. So you have confirmed I can then flash Stock recovery and take the "full" Update. Mind providing the link to Stock recovery?
Thanks.
schneid said:
Just to be sure. I ran TWRP from Fastboot in ADB as soon as Unlocked and turned the phone on. So you have confirmed I can then flash Stock recovery and take the "full" Update. Mind providing the link to Stock recovery?
Thanks.
Click to expand...
Click to collapse
Pretty sure there is a post in here somewhere that has a link to the 24.221.4 recovery, but I just used the one in this full firmware download. Just extracted the recovery.img file only and flash it using fastboot. Here is the link.
https://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://www.androidfilehost.com/?fid=745425885120733909
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
TheSt33v said:
Do not take this if your bootloader is locked and you'd like to unlock it at some point.
Click to expand...
Click to collapse
There, fixed it for you.
Gotta bold the important stuff.
ChazzMatt said:
There, fixed it for you.
Gotta bold the important stuff.
Click to expand...
Click to collapse
You're inhibiting natural selection.
TheSt33v said:
Here is the latest OTA. Verizon says it has security (*cough* Sunshine *cough*) patches. I can confirm that it does not re-lock an unlocked bootloader. It's so minor, they just decided to slap an extra -5 on it.
https://mega.nz/#!70Zh1BbS!cC_mZ8xouLVwvMlOZLKW2UyC-JXDS7SdnCjxDoafXbI
Do not take this if your bootloader is locked and you'd like to unlock it at some point. If you'd like to unlock it at some point, do it now! What are you waiting for?
You cannot flash this with TWRP.
Click to expand...
Click to collapse
hweew ... new kernel ...
could you upload it?
3Dota said:
hweew ... new kernel ...
could you upload it?
Click to expand...
Click to collapse
TWRP flashable, including kernel, version will be up shortly.
TheSt33v said:
TWRP flashable, including kernel, version will be up shortly.
Click to expand...
Click to collapse
Any modem updates?
koftheworld said:
Any modem updates?
Click to expand...
Click to collapse
Yes. Will also be included in TWRP version.
Yee!
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
mustafu said:
I'm already unlocked on Stock with Stock recovery, and tried taking the OTA, but got an error when it rebooted to install
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Have you done any modifications at all? Even in the past? For example, if you were rooted and then unrooted, if any files were left over from that process, the update will fail. If you had xposed and removed it, same deal. Even if you replaced your emoji file with an updated one, that will also cause it to fail. Did you modify build.prop? Fail.
The only way to be sure that it will pass is to reflash MCG24.251-5 with fastboot before taking the OTA. Or you could always do it the easy way and flash MCG24.251-5-5 with TWRP: https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Install titanium backup and freeze the app called Motorola Update Services.
Shtiff1 said:
I'm running 24.81.5 and just received 24.91.5. Did not install. Unlocked and rooted. If I take this will it fail or cause issues?
Sent from my XT1254 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
So I'm guessing it's for "security" issues. So I really don't need to take this, because it involves to much crap... Unrooting, cleaning cache, reflashing, having to do the phone over again, etc.... If that is all true, then how can I get rid of the system update?
g0ndor said:
I have a "system update paused, waiting for wi-fi" in the status bar. I don't want to take this update - can someone help me remove the notification, and block future updates? I have bl unlocked and rooted...
Tia
Click to expand...
Click to collapse
Download "Disable Service" from the play store
TheSt33v said:
It will fail. Any modifications at all (like root or TWRP, for example) will cause the update to fail.
Click to expand...
Click to collapse
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Sent from my XT1254 using Tapatalk
mustafu said:
I'm not aware of any modifications, I thought I went back to all stock. Recovery says qe 1/1, is it supposed to be 0/1?
Click to expand...
Click to collapse
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
trial TWRP or temp TWRP custom recovery
trial TWRP or temp TWRP custom recovery
TheSt33v said:
If you look at the update script for the OTA, the first two thirds of it are dedicated to checking the system partition (and maybe other partitions. It's a pretty long read and I certainly haven't read all of it) for modifications. If the update is failing, that means it has detected something that does not match what it is checking for. I don't think the qe flag matters, because in the past I'm pretty sure that I've been at 1/1, and after a successful OTA it changes to 0/1.
Click to expand...
Click to collapse
Don't know if this would help someone install an update like this, but let me throw this out there. There's a way to boot to TWRP custom recovery and use TWRP without installing TWRP. Think of it as "temporary" TWRP.
Thus, you should still be able to flash stuff, including any TWRP-flashable updates, boot logos (to replace the unlocked bootloader warning, SuperSu, etc -- and when you reboot you still have stock recovery.
Now, I don't know why anyone would want to keep stock recovery when TWRP recovery does so much more... But I just recently helped someone with the same suggestion. He wanted to install SuperSu, get root, but keep stock recovery -- for some reason.
Anyway, think of it as "trial TWRP" or "temp TWRP".
I remembered when I made factory images for my Quark, in a variety of states, I used this temporary TWRP trick. I'd almost forgotten about it!
So, seems like you could flash THIS TWRP-flashable version of this update while temporarily booting to TWRP (but not actually installing it), and it wouldn't matter if everything "checked" out or not.
Of course, if you like it, then you can always install it permanently.
For reference, here's the most recent version of TWRP for our phone. (use the one with the most recent post date. @bhb27 updates it fairly often.)
TWRP FOR QUARK
https://www.androidfilehost.com/?w=files&flid=39562
Here's my complete reply:
______
Rahuld107 said:
@ChazzMatt,
Hi, can i root xt1225 using temporary twrp ( one time method). I don't need twrp/custom recovery. Just want root with stock recovery. I am on stock marshmallow, bootloader is unlocked .
Click to expand...
Click to collapse
TEMPORARY TWRP
OK, here's another suggestion. There is a way to boot to TWRP to install SuperSu but NOT install TWRP. You will not be flashing TWRP over stock recovery. You will STILL have stock recovery when you reboot. Think of it as "temporary" TWRP.
Put the TWRP file in your ADB folder and use this command. Your phone will boot to TWRP, but it will not be permanently installed. You can then flash SuperSu while booted into the TWRP interface and then reboot back to your system.
fastboot boot file-name.img (whatever your file name of TWRP is.)
Whereas, the command to permanently install TWRP is this:
fastboot flash recovery file-name.img (whatever your file name of TWRP is.)
___
Back when I first got this phone -- now over two years ago -- I made a bunch of backups in TWRP and posted the images online in various stages -- pure stock, stock + root, stock + root + TWRP. I made the first two with the "temporary" TWRP. People could flash them and already have root without having TWRP installed.
Moto Maxx - Moto Turbo XT1225 factory images (Mexico | Puerto Rico | India | Brazil)
https://forum.xda-developers.com/moto-maxx/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
1) TWRP BACKUPS which I made in various stages, such as
stock, unrooted
stock + rooted
stock + rooted + permanent TWRP
Click to expand...
Click to collapse
See? Even just stock + rooted but with no TWRP. I made that backup with a "temporary" TWRP which did not overwrite the stock recovery.
But they were only for 4.4.4 Kitkat, which came with this phone. After we went to Lollipop, I posted some more images, but just pure factory. Still, the "temporary" TWRP trick is useful.
Is it just me or the Gallery app in 6.0.1 scrolls really slow? Btw i didnt do a clean update from LP in case that could be the reason
Hi All,
I just recovered from a hard brick on my G4 plus due to various complications from flashing the Elemental X ROM as suggested before flashing the root file.
Though the root was successful on the stock Nougat OS (NPJ25..93-14), the main issue which I immediately noticed after rooting was that there was no notification sound. I fiddled through all the settings to get this working, but didn't get through. Not sure if anybody has faced this issue.
So, my queries are as below:
----- Why is a custom kernel needed to root? Just flashing a root zip file wouldn't be enough?
----- What's the issue with the sound getting disabled after flashing the Elemental X kernel? Is there a fix to re-enable the notification sounds?
----- Is there any other custom kernel which I could flash when rooting on the Stock N OS if indeed a custom kernel is required to root? (this shouldn't screw up the notification sound)
Regards,
Shonilchi
Shonilchi said:
Why is a custom kernel needed to root? Just flashing a root zip file wouldn't be enough?
Click to expand...
Click to collapse
The stock kernel from Motorola can only have temporary root access. Check the thread by Shreps if you're interested in that. There's no other way, at the moment to get permanent root access. Why? That's some way Motorola has worked out the kernel.
What's the issue with the sound getting disabled after flashing the Elemental X kernel? Is there a fix to re-enable the notification sounds?
Click to expand...
Click to collapse
Hadn't happened for me when I rooted my device. Specific to you, for some reason. Try flashing again. Backup your existing kernel (Google how to) and restore the backup if anything goes wrong.
Is there any other custom kernel which I could flash when rooting on the Stock N OS if indeed a custom kernel is required to root? (this shouldn't screw up the notification sound)
Click to expand...
Click to collapse
You can, of course try Dreamstar's Vegito or rahulsnair's Quark kernel's stock versions and then flash a superuser ZIP file (the same phhSU or Chainfire's SuperSU.
You should not have had a hard brick. Perhaps you had a soft brick. A hard brick would require a blank flash using special software to fix. What did you mean when you said your phone got hard bricked?
Great thanks for the answers. Yes, it was probably a soft brick which happened. I was able to downgrade to MM and then do a N upgrade.
BTW, I see many supersu.zip files floating around to be flashed. Do you recommend a most suitable one to flash for the G4+. I know that I need to install the pHH supersu app after I boot up.
And for the stock kernel revert I found this statement: "Do a nandroid backup and do advanced restore instead of complete restore. boot.img is the kernel." - can you please confirm if this is a good way to revert back to the stock kernel?
deleted.
Shonilchi said:
BTW, I see many supersu.zip files floating around to be flashed. Do you recommend a most suitable one to flash for the G4+. I know that I need to install the pHH supersu app after I boot up.
Click to expand...
Click to collapse
Install the phhSU zip as mentioned in the link in the post above, or, install the latest SuperSU Beta from the SuperSU XDA thread.
And for the stock kernel revert I found this statement: "Do a nandroid backup and do advanced restore instead of complete restore. boot.img is the kernel." - can you please confirm if this is a good way to revert back to the stock kernel?
Click to expand...
Click to collapse
All you need to do is backup boot.IMG from TWRP and restore it upon a botched flash.
Shonilchi said:
Great thanks for the answers. Yes, it was probably a soft brick which happened. I was able to downgrade to MM and then do a N upgrade.
BTW, I see many supersu.zip files floating around to be flashed. Do you recommend a most suitable one to flash for the G4+. I know that I need to install the pHH supersu app after I boot up.
And for the stock kernel revert I found this statement: "Do a nandroid backup and do advanced restore instead of complete restore. boot.img is the kernel." - can you please confirm if this is a good way to revert back to the stock kernel?
Click to expand...
Click to collapse
Was walking around here and couldn't help the itchy need to leave my own straight answers to your questions, mostly as an exercise, since G4/Plus is no longer that news nor the thing of excitement it still was (arguably) back in March 2017.
Whatever, as for superuser means, @topjohnwu "Magisk" has gained a lot of popularity over former Chainfire's "SuperSu" since he's no longer supporting it and development seems pretty much at iddle nowadays. Say I'm a purist (which I'm not), that's why I'm still relying on latest, all @Chainfire built SuperSu (v2.82 SR5) probably for the last time though...
On the other hand, ABSOLUTELY YES, it's a good way and you can restore just boot.img right from your nandroid backup to revert back to stock kernel. Actually, we all know it's the best practice to always do a nandroid backup right before messing around with our devices and TWRP comes with the benefit to choose which partitions you can either backup or restore...
As for @flar2 ElementalX, it wasn't really a must because I refused upgrade to "N" due to the lack of Xposed support (both came a bit late) but I flashed it anyways in order to "fix" the so called "burn screen" issue primarily... and just because it's cool. No unwanted side effects by the way and my personal experience with Moto G4 Plus aside from the "burn screen" issue (which turned out no big deal for me) is of pure joy until early days of 2018 and counting. There you (all) have it.
Sent from my Moto G4 Plus using XDA Labs
u need to reboot the device once or wait for sometime..the tones comes back automatically..its not a kernel issue. Since, no one else is facing it...
Custom kernels are better than stock as they give u an option to tweak for performance or battery.. if you don't need it keep it stock.. if u want it, the method u know is correct. Always make backups, incase u mess up.
Good luck!