I want Lollipop and my Nexus 4 won't shut up about the OTA update. Naturally, it failed, and i have since tried to find a fool-proof guide to uptade it WITHOUT LOOSING DATA. Not been so lucky. Theres talk about fastbooting (?) and going back to stock, but not much in the way of step-by-step guides. I think most people with nexus 4 and root are like me - did it because it was easy, not knowing a lot about it...
I have rooted with towelroot, installed TWRP custom recovery with flashify, unlocked bootlocker with Bootunlock, installed Xposed framework and SuperSU. Never used ADB or any commands. Can't be the only one in this exact situation
What excactly do i need to do to get Lollipop without loosing any data (like a regular OTA update)?
Maybe user Titanium Backup or some kinda backup software to backup files and stuff then just go for a fresh installation? Most of the basic settings should be saved to your google account.
This post should help you with setting up ADB in your computer and to get you up to speed with using ADB and Fastbooot
KishanW said:
Maybe user Titanium Backup or some kinda backup software to backup files and stuff then just go for a fresh installation? Most of the basic settings should be saved to your google account.
This post should help you with setting up ADB in your computer and to get you up to speed with using ADB and Fastbooot
Click to expand...
Click to collapse
Thanks for the quick reply! But i was hoping for a solution that DIDN'T wipe my phone. I just wanna undo all the rooting business, so i can do the OTA...
605
tommyhj said:
Thanks for the quick reply! But i was hoping for a solution that DIDN'T wipe my phone. I just wanna undo all the rooting business, so i can do the OTA...
Click to expand...
Click to collapse
That would be interesting if someone has an answer for your question. I can use it too
Sorry that I couldn't help you.
tommyhj said:
I want Lollipop and my Nexus 4 won't shut up about the OTA update. Naturally, it failed, and i have since tried to find a fool-proof guide to uptade it WITHOUT LOOSING DATA. Not been so lucky. Theres talk about fastbooting (?) and going back to stock, but not much in the way of step-by-step guides. I think most people with nexus 4 and root are like me - did it because it was easy, not knowing a lot about it...
I have rooted with towelroot, installed TWRP custom recovery with flashify, unlocked bootlocker with Bootunlock, installed Xposed framework and SuperSU. Never used ADB or any commands. Can't be the only one in this exact situation
What excactly do i need to do to get Lollipop without loosing any data (like a regular OTA update)?
Click to expand...
Click to collapse
Hey,
Follow these instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312.
there are a few things to note:
1. You do not need to unlock the bootloader, you will have done that when you rooted
2. Download the 5.0 image instead of the original stock image when you do this.
3. DO NOT flash userdata.img. That will wipe your data.
Those are the steps I followed to flash over to 5.0 without losing data.
But I would absolutely do a backup anyway, just in case something goes wrong.
gardn227 said:
Hey,
Follow these instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312.
there are a few things to note:
1. You do not need to unlock the bootloader, you will have done that when you rooted
2. Download the 5.0 image instead of the original stock image when you do this.
3. DO NOT flash userdata.img. That will wipe your data.
Those are the steps I followed to flash over to 5.0 without losing data.
But I would absolutely do a backup anyway, just in case something goes wrong.
Click to expand...
Click to collapse
Ok, cool. So you're saying to towel-root my device, unlock bootloader with bootunlocker app, remove root by installing SuperSU and using the clean-up funtion. And then adb fastboot flash boot/recovery/system from the FACTORY img? Why not sideload the OTA instead? Because it wont work unless i reflash stock 4.4.4 completely?
*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 really just want to root stock. I have the Boost Mobile Perry.
guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
Yes. Install twrp, flash no verity, format data (to remove encryption) flash magisk. Some people have said if you took the last security update, you may have to patch the boot.img with magisk manager then flash the patched boot.img in fastboot or twrp to root. And will likely need the latest magisk beta (16.4).
I really don't care about encryption.
guitardoc64 said:
I really don't care about encryption.
Click to expand...
Click to collapse
You have to remove encryption.
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
guitardoc64 said:
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
Click to expand...
Click to collapse
Don't neglect to backup EVERYTHING in TWRP before doing ANYTHING (and store those images off-device!). Strongly suggest booting a TWRP image to perform this task vs. installing/flashing to the recovery partition, especially if interested in preserving/restoring OTA capability at a future time.
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
Welcome to the 5% club which is probably generous based on the number of noobs (and veterans) who neglect to image their device before messing with core components. Of course that figure may be skewed as those that do take proper precautions rarely write posts that begin with "help!" and have no path back to the prior working state.
Also, resist the temptation to flash a custom recovery (twrp) vs booting from fastboot if you want to accept accept future OTA updates or roll back to pure stock. While restoring stock recovery is possible it certainly complicates the process. Can always revisit the decision at later time.
guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
Don't have a definitive answer on the latest firmware. Suggest going through the above steps first. If no joy it's a simple matter to patch/flash boot.img .
You are wise to boot a twrp image vs flashing over stock recovery. Simplifies fallback should the need arise. Don't neglect to backup stock and store off device (or at least on a SD card).
davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
For .3, format data to remove encryption.
But the rest should work. If not, you have to download the current firmware ( the version you're on) if you can find it. Extract the boot.img from it. Then use magisk manager to patch it. And use fastboot to flash the patched boot.img
i have the moto e4 mkt which no verity version do i have to flash ?
Rafasama said:
i have the moto e4 mkt which no verity version do i have to flash ?
Click to expand...
Click to collapse
You shouldn't need a no-verity any longer. Newer versions of magisk should take care of it. Just TWRP, and magisk.
madbat99 said:
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
Click to expand...
Click to collapse
Hello, I am running a Samsung Galaxy J5 Prime at the moment, a friend told me I must flash no verity.zip after flashing TWRP because of the verification and I tried making a backup if the entire rom but it failed so I need to confirm, do I factory reset my device then flash the no verity file or I flash the no verity file and then factory reset the device??
I know it's an old thread but a quick reply would be awesome
I apologize if this question has been asked before, I can't seem to find a clear answer.
Moto G6 Plus XT1926-7
Android 9 build PPWS29.116-11-13
Up-to-date as of 11/01/2019
note: retla channel
I had an app "break". I contacted author who said reinstall. However, reinstall erases my existing data, which is of course, stored on /data/data outside of reach. Further the app opts-out of Google Backup in favor of proprietary backup, which I did not know or use.
Isn't there some way to gain root access, even temporarily, to copy my data? Unlocking the bootloader and factory reset aren't really solving the problem. I've looked at Kingoroot, KingRoot, Towelroot, etc... none support Pie.
I can't believe this problem is uncommon or that there's no solution. Any guidance/opinion/hint appreciated.
Thank you
Try installing the app without uninstalling it. Download an .apk of it online and install it. Usually it doesn't delete any data as this is to make an update for the app
Otherwise, the only way to get your app data is by rooting your android. So start by booting into TWRP and flashing the magisk installer zip. Then install a file manager like total commander and get the files.
Possible Solution
Goddard260 said:
I apologize if this question has been asked before, I can't seem to find a clear answer.
Moto G6 Plus XT1926-7
Android 9 build PPWS29.116-11-13
Up-to-date as of 11/01/2019
note: retla channel
I had an app "break". I contacted author who said reinstall. However, reinstall erases my existing data, which is of course, stored on /data/data outside of reach. Further the app opts-out of Google Backup in favor of proprietary backup, which I did not know or use.
Isn't there some way to gain root access, even temporarily, to copy my data? Unlocking the bootloader and factory reset aren't really solving the problem. I've looked at Kingoroot, KingRoot, Towelroot, etc... none support Pie.
I can't believe this problem is uncommon or that there's no solution. Any guidance/opinion/hint appreciated.
Thank you
Click to expand...
Click to collapse
I can suggest you to factory reset your device, sometimes dev are lazy to tell you the instructions, if the problem still, you should consider root your device, for new people Rooting is something complicated, but WORTH the try. I can tell you the steps to root your device.
1. Unlock Bootloader
2. Install TWRP
3. Wipe/Erase data (not included internal storage)
4. Install Magisk Flash Zip
5. Enjoy your brand new rooted device
DoomSlayer2019 said:
I can suggest you to factory reset your device, sometimes dev are lazy to tell you the instructions, if the problem still, you should consider root your device, for new people Rooting is something complicated, but WORTH the try. I can tell you the steps to root your device.
1. Unlock Bootloader
2. Install TWRP
3. Wipe/Erase data (not included internal storage)
4. Install Magisk Flash Zip
5. Enjoy your brand new rooted device
Click to expand...
Click to collapse
And here things get complicated...
On a Moto G6 plus TWRP cannot be installed. You will have to boot it.
The next thing is TWRP can decrypt /data, so you won't have to erase userdata. Not for Magisk either.
You can install twrp, there is a file where you can install twrp inside of it, letting use it in Recovery Mode
DoomSlayer2019 said:
You can install twrp, there is a file where you can install twrp inside of it, letting use it in Recovery Mode
Click to expand...
Click to collapse
Where is this file?
WoKoschekk said:
Where is this file?
Click to expand...
Click to collapse
I don't recommend you installing twrp in your phone, you don't access all the time, also it brings bugs like wifi drop
DoomSlayer2019 said:
I don't recommend you installing twrp in your phone, you don't access all the time, also it brings bugs like wifi drop
Click to expand...
Click to collapse
I know, just wondering how to manage to install TWRP on this phone.
Heya everyone,
I've got my 6T with Android 10 rooted that it's giving me some troubles. I made some mistakes when I updated to android 10 so now I would like someone to help me doing these steps the proper way.
I would like to:
Reset the whole phone with a fresh install of Android like factory, if possibile already updated to the Android 10.3.0 (i've already downloaded the full OTA and Ive got ADB installed and working),
then I'll want to install TWRP and Magisk from scratch too and at the end I'll install apps and I'll restore datas (only those needed like pictures or google drive/whatsapp backups).
I'm not sure which steps do I have to follow to do this without breaking something during the process.
Thanks
All is written here and still valid, read first posts carefully.
Use latest .30 twrp version and latest Magisk zip
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789
Striatum_bdr said:
All is written here and still valid, read first posts carefully.
Use latest .30 twrp version and latest Magisk zip
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789
Click to expand...
Click to collapse
Thanks. I'll follow the guide.
Before rooting how could I factory reset everything and update the phone. I would like to be sure that everything done in the past will be cleared.
Thanks
Sent from my ONEPLUS A6013 using Tapatalk
RikiBez said:
Thanks. I'll follow the guide.
Before rooting how could I factory reset everything and update the phone. I would like to be sure that everything done in the past will be cleared.
Thanks
Click to expand...
Click to collapse
Unlocking the bootloader is a factory reset. If already done, reboot in recovery and do it from there
Striatum_bdr said:
Unlocking the bootloader is a factory reset. If already done, reboot in recovery and do it from there
Click to expand...
Click to collapse
Do you mean from the TWRP recovery? I checked it but I don't know from which menu to do it.
Or is it possible and better to do it from ADB? If yes which command do I need to use?
RikiBez said:
Do you mean from the TWRP recovery? I checked it but I don't know from which menu to do it.
Or is it possible and better to do it from ADB? If yes which command do I need to use?
Click to expand...
Click to collapse
There is a factory reset function in phone settings > system
If not enough
https://twrp.me/faq/whattowipe.html
Please use Google that's exactly what I do to answer you
Striatum_bdr said:
There is a factory reset function in phone settings > system
If not enough
https://twrp.me/faq/whattowipe.html
Please use Google that's exactly what I do to answer you
Click to expand...
Click to collapse
I used Google and searched the forum. I read some guides but I made the thread cause I would like to have an help from someone that knows what I need to do step by step cause I don't want to fail.
Sent from my ONEPLUS A6013 using Tapatalk
[deleted]
Follow this thread to rollback to pie..
This will wipe your data and do the reset that you want..
From there you can update to latest 10.3.0 and install twrp and magisk afterwards...
https://forum.xda-developers.com/on...owngrade-oos-android-10-t4000645/post80843523
An important question is. Do you need TWRP? Because you don't need TWRP for root. If you want root, i suggest just flashing the patched boot.img.
You can factory reset from any recovery by wiping everything.
bokkoman said:
An important question is. Do you need TWRP? Because you don't need TWRP for root. If you want root, i suggest just flashing the patched boot.img.
You can factory reset from any recovery by wiping everything.
Click to expand...
Click to collapse
I'm not really sure for what I need TWRP but I always used to install it with Magisk.
Sent from my ONEPLUS A6013 using Tapatalk
Steps that I followed to solve
I would like to thanks @Striatum_bdr and @cultofluna for their tips.
I solved doing this:
I saved camera pictures, downloads folder and anything else I need by dragging and dropping from phone to PC. I also made backups of Whatsapp, Nova Launcher and other tools I would to restore.
I downloaded the rollback and folloed the instructions from here: https://forum.xda-developers.com/on...owngrade-oos-android-10-t4000645/post80843523
After that I started the phone skipping most of the requests
Updated it a couple of times until I was on Android 10.3.0
Then I followed the standard rooting guide for the OnePlus 6T: https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789 using files from this new post related to Android 10: https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
When I finished I had a fully rooted Android 10.3.0 with TWRP on both slots.
At the end I made a factory reset from the system setting to clear the my answers to the questions that I skipped at the beginning and I configured it as I wish.
I downloaded apps and restored files and backups from PC and cloud drives
List of files that I've used:
https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view (PC)
https://drive.google.com/file/d/1-uWQn-oHu_ROuDVCzIyrExoRbsSBYTtU/view (PC)
https://www.androidfilehost.com/?fid=4349826312261677894 (PC)
https://www.androidfilehost.com/?fid=4349826312261677893 (Phone)
https://github.com/topjohnwu/Magisk/releases/download/v20.1/Magisk-v20.1.zip (Phone)
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk (Phone)
I guess the easiest way would to just go to recovery, wipe everything (after backup first of course).
Then adb sideload your ROM (in this example OOS 10.3.0) in recovery and let it install.
Reboot your phone and go thru first steps.
Go to fastboot and flash patched boot.img (magisk patched, look for the boot corresponding to your ROM) to gain root and reboot again.
Now you're all set.
No need for TWRP or anything. Just update the normal way and install magisk through magisk manager to inactive slot before you reboot after update.