Related
*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
The phone is the Huawei Nexus 6P (MMB29M). No clue how this happened, but I managed to get root (working fine I can run apps that require root), but TWRP isn't on my phone. When I try to boot to recovery, it gives me the dead android symbol (dead android with front flap opened up and little red exclamation point). I can get into the boot loader just fine though, it's ONLY the recovery that is missing. Is it okay to use the TWRP app to install recovery the easy way? I have the TWRP app on my phone from the (failed) TWRP install, I guess. Or do I need to go through the whole root/recovery fastboot process again?
I don't know how I even got root without recovery, tbh. I was obviously in TWRP when I flashed superSU and busybox, but for whatever reason, it didn't stick. The only thing I can think of is that the phone took the liberty of replacing the recovery on its own when I restarted the phone (I didn't think to go back into recovery immediately, so the phone overwrote it...is that possible?)
The reason I'm asking about the TWRP app is because it has a very specific directory that it says it needs to install into and if that directory is wrong, the phone could be bricked. I've had the phone for less than a week, I'd prefer not to brick it. This is my 5th android device and I've never run into this issue before...in fact, I didn't even know it was POSSIBLE to get root without recovery. I did get a soft-brick earlier in the process, but I fixed it by re-flashing the stock android ROM (I also had to go change my pants afterward, but that's a story for another thread).
Thanks in advance for any assistance you can provide and have a nice Friday.
baronmax said:
The phone is the Huawei Nexus 6P (MMB29M). No clue how this happened, but I managed to get root (working fine I can run apps that require root), but TWRP isn't on my phone. When I try to boot to recovery, it gives me the dead android symbol (dead android with front flap opened up and little red exclamation point). I can get into the boot loader just fine though, it's ONLY the recovery that is missing. Is it okay to use the TWRP app to install recovery the easy way? I have the TWRP app on my phone from the (failed) TWRP install, I guess. Or do I need to go through the whole root/recovery fastboot process again?
I don't know how I even got root without recovery, tbh. I was obviously in TWRP when I flashed superSU and busybox, but for whatever reason, it didn't stick. The only thing I can think of is that the phone took the liberty of replacing the recovery on its own when I restarted the phone (I didn't think to go back into recovery immediately, so the phone overwrote it...is that possible?)
The reason I'm asking about the TWRP app is because it has a very specific directory that it says it needs to install into and if that directory is wrong, the phone could be bricked. I've had the phone for less than a week, I'd prefer not to brick it. This is my 5th android device and I've never run into this issue before...in fact, I didn't even know it was POSSIBLE to get root without recovery. I did get a soft-brick earlier in the process, but I fixed it by re-flashing the stock android ROM (I also had to go change my pants afterward, but that's a story for another thread).
Thanks in advance for any assistance you can provide and have a nice Friday.
Click to expand...
Click to collapse
This happened to me after the first time I installed twrp. I selected read only system after booting into twrp for the first time(they ask you if you want a read only option) and the stock rom would over write twrp with the stock recovery. Only fix for me was starting from scratch using step 11 here http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928. When you install twrp dont select the read only option and you'll be fine. Just remember not to let twrp install Su when it asks you to.
did you not read and follow the VERY detailed and specific instructions on how to do all of this, before beginning the process?
mistakes happen, and we are all here to help, but a softbrick followed by no recovery etc just seems like you tried to wing it without taking the proper time to read how to do it on your new device.
I'm sure someone will be able to give you a definite answer, but I also advise you to read @Heisenberg's guide on how to do it all on your 6P in the General section
Soulfly3 said:
did you not read and follow the VERY detailed and specific instructions on how to do all of this, before beginning the process?
mistakes happen, and we are all here to help, but a softbrick followed by no recovery etc just seems like you tried to wing it without taking the proper time to read how to do it on your new device.
I'm sure someone will be able to give you a definite answer, but I also advise you to read @Heisenberg's guide on how to do it all on your 6P in the General section
Click to expand...
Click to collapse
I read everything and my only mistake was selecting the read only option which clearly tell you that if you select read only it cant prevent the stock rom from over writing twrp with its own recovery. Mistakes happen.
can you not just install twrp again from the bootloader?
ahfu25 said:
I read everything and my only mistake was selecting the read only option which clearly tell you that if you select read only it cant prevent the stock rom from over writing twrp with its own recovery. Mistakes happen.
Click to expand...
Click to collapse
I was responding to the OP, not you.
uicnren said:
can you not just install twrp again from the bootloader?
Click to expand...
Click to collapse
Yes, but I was wondering if it was a bad idea to just let the TWRP app do it? That's what it's designed to do (that, and update TWRP). That's why I asked the question, I wasn't sure if that was a viable way to go about this or whether I just needed to re-do it from the nexus 6p "how to" that's on the site here.
Soulfly3 said:
I was responding to the OP, not you.
Click to expand...
Click to collapse
OK...have a nice day
I can't say for sure that I understand what you mean by using twrp when you don't even have it... but maybe see this post. (The bottom of that post.)
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
oh, I get what you're saying now - can you do it with the twrp app - as in an actual app. i missed that word. I think i remember Heisenburg saying that, no, you shouldn't use the app. I think it doesn't get the right twrp version. the version we need for the 6p is in beta and not available throught the app.
---------- Post added at 12:07 PM ---------- Previous post was at 11:51 AM ----------
In a previous post of mine, I quoted the explanation from TWRP of the system read-only vs read-write thing: http://forum.xda-developers.com/showpost.php?p=64707169&postcount=2143 I think you may need to mount the system read-write to get twrp to "stick". ...or you need root (according to sirxdroid)? I don't know which... I'd love to know how you get it working again!
p.s. Sorry to keep appending to my response...
Good explanations and links, I had the same issue when I decided to root. I did not choose read only during my initial flash of TWRP and could not figure out why every time I flashed TWRP, rebooted then went into recovery, I lost TWRP! After I did my due diligence and read the threads, I realized what I did wrong. I flashed back to stock, then flashed TWRP as recovery. I went into recovery via bootloader and chose read only. Then I installed the su.zip, rebooted the bootloader, then it was all good. Good luck.
I think what I did wrong is fail to wipe the caches (not sure how I missed it, but I did, originally). I'm not entirely sure why that makes any difference, but I went through the rooting process again and installed TWRP, now things are working properly. I did two things differently, wiping the cache and booting directly back into recovery after installing recovery. I saw on the TWRP website that some ROMs will overwrite the boot.img and recovery sections if you don't boot back into recovery immediately (it doesn't overwrite them after the second time, for whatever reason). I'm not sure if this is what happened or not, but it's the one thing that actually makes SOME sense to me.
It's interesting that there's an app out there which claims to install TWRP, but people shouldn't use it, that would be a mighty handy app to have if it worked properly, no more worries and very little fuss.
Why not just fastboot flash recovery........takes 10 seconds.
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
Yes you can via Rczrider 's TWRP backup
tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
XblackdemonX said:
Yes you can via Rczrider 's TWRP backup
Click to expand...
Click to collapse
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
rczrider said:
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Click to expand...
Click to collapse
if someone can make a guide on HOW-TO (Steps + FIles + Images needed) i can give it a shot...
just send me a PM if you know the HOW-TO :good:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
DrakenFX said:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
Click to expand...
Click to collapse
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
tele_jas said:
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
Click to expand...
Click to collapse
I'm curious too and I wanna give it shot,
P. S. Any way to use terminal or adb to pull the partition list with their Extension?
Like for sample. " ext4 system /dev/block/sde13 " or something similar with extension?
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
tele_jas said:
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
Click to expand...
Click to collapse
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
peramikic said:
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
Click to expand...
Click to collapse
those steps were the same i was planning to do plus flashing something else, but seems like i may be not doing the other flashing file now......well still gathering more info and will see.
P.S. Thanks for the info. @peramikic
DrakenFX said:
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
Click to expand...
Click to collapse
Gottcha.... I was just curious, because I'm starting to have a few random issues (reboots, apps opening without tapping them, google voice commands not working like they did just a few days ago) I'd like to get back to stock and maybe start over. Of course, I didn't make a backup up until after I flashed SuperSU and my apps downloaded so I have no "stock" TWRP backup. **But, this all could be "theme" related too, since I'm running a dark theme that isn't quite compatible with the A7 yet.
I may try removing the theme and let it run a day or two and see how it does?
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
I'm just trying to understand what I did here. This is the first phone that's given me this much trouble.
Was running 7.1.1 stock. Finally got annoyed by that auto volume thing from sony that I had time to flash AOSP. I followed
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I used xperifirm/flashtool to update to newest UK firmware ( US has no fingerprint ) . I did NOT backup my drm keys. I have them from before when I rooted. Besides I didn't need them really. I use opencamera.
Followed that guide exactly. Everything worked. Then I flashed twrp 3.1.1 from adb. I think this is where I went wrong. I wanted to flash supersu and viper4android. As soon as I tried this I got twrp errors about mounting /data. Missing crypto footers. I also noticed that supersu binary always said it needed updating, and viper4android would not install drivers.
Did some googling. Saw I just had to format /data from twrp. TWRP was unable to format data with the same errors. More google, saw I had to recreate the /data from terminal from this link https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 .
Did that. Same errors in twrp. Ok had enough. Restored my twrp backup from 7.1.1 where everything worked. That went through and just hosed everything, due to not being able to read /data. After this finished I was stuck in a boot loop.
Got into fastboot and reran the original AOSP guide above. Now I'm there. Everything left exactly as it was. No twrp etc.
My question is what the heck did I break and how? And as a secondary question can I root this, if so how? The recovery that is flashed with that guide cannot mount /sdcard so I don't see a way to flash supersu for example.
Just trying to understand before I really break something.
j1tters said:
I'm just trying to understand what I did here. This is the first phone that's given me this much trouble.
Was running 7.1.1 stock. Finally got annoyed by that auto volume thing from sony that I had time to flash AOSP. I followed
https://forum.xda-developers.com/x-compact/development/nougat-7-1-1-android-source-project-t3555510
I used xperifirm/flashtool to update to newest UK firmware ( US has no fingerprint ) . I did NOT backup my drm keys. I have them from before when I rooted. Besides I didn't need them really. I use opencamera.
Followed that guide exactly. Everything worked. Then I flashed twrp 3.1.1 from adb. I think this is where I went wrong. I wanted to flash supersu and viper4android. As soon as I tried this I got twrp errors about mounting /data. Missing crypto footers. I also noticed that supersu binary always said it needed updating, and viper4android would not install drivers.
Did some googling. Saw I just had to format /data from twrp. TWRP was unable to format data with the same errors. More google, saw I had to recreate the /data from terminal from this link https://forum.xda-developers.com/xperia-sp/help/format-data-using-twrp-3-0-2-t3371137 .
Did that. Same errors in twrp. Ok had enough. Restored my twrp backup from 7.1.1 where everything worked. That went through and just hosed everything, due to not being able to read /data. After this finished I was stuck in a boot loop.
Got into fastboot and reran the original AOSP guide above. Now I'm there. Everything left exactly as it was. No twrp etc.
My question is what the heck did I break and how? And as a secondary question can I root this, if so how? The recovery that is flashed with that guide cannot mount /sdcard so I don't see a way to flash supersu for example.
Just trying to understand before I really break something.
Click to expand...
Click to collapse
I don't know if I know what went wrong, but I wonder, 1) why not Magisk, and 2) why not TWRP 3.2.1? Might be better off...
levone1 said:
I don't know if I know what went wrong, but I wonder, 1) why not Magisk, and 2) why not TWRP 3.2.1? Might be better off...
Click to expand...
Click to collapse
I've never really used magisk. Flashable zip? I'd need a working twrp since the recovery included with that rom can't mount /sdcard.
I think I just happened to grab 3.1.1, I must have missed the 3.2.1 version. At this point I'm not flashing anything until I know it works. I don't remember seeing it in nougat, but I see that under 8.1 the phone status shows as encrypted.
I'm a little leery of flashing anything currently since I currently have no root so I cant use titanium to backup. I also don't want to end up with a non working recovery again. I posted to that aosp thread seeing if anyone rooted it.
At this point I'd almost like to get a working twrp just to go back tro 7.1 where everything worked.
j1tters said:
I've never really used magisk. Flashable zip? I'd need a working twrp since the recovery included with that rom can't mount /sdcard.
I think I just happened to grab 3.1.1, I must have missed the 3.2.1 version. At this point I'm not flashing anything until I know it works. I don't remember seeing it in nougat, but I see that under 8.1 the phone status shows as encrypted.
I'm a little leery of flashing anything currently since I currently have no root so I cant use titanium to backup. I also don't want to end up with a non working recovery again. I posted to that aosp thread seeing if anyone rooted it.
At this point I'd almost like to get a working twrp just to go back tro 7.1 where everything worked.
Click to expand...
Click to collapse
Find twrp in rom forum here, and search xda for Magisk. Flash twrp, wipe everything, then flash rom, then flash Magisk. See if all better... Also, you can flash V4A modules, (and many others), through Magisk.
Twrp - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
levone1 said:
Find twrp in rom forum here, and search xda for Magisk. Flash twrp, wipe everything, then flash rom, then flash Magisk. See if all better... Also, you can flash V4A modules, (and many others), through Magisk.
Twrp - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
j1tters said:
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
Click to expand...
Click to collapse
I have never flashed recovery with aosp, because it doesn't do anything. I haven't tried aosp O yet, though. Typically, yes, skip the recovery flash and flash twrp instead.
levone1 said:
I have never flashed recovery with aosp, because it doesn't do anything. I haven't tried aosp O yet, though. Typically, yes, skip the recovery flash and flash twrp instead.
Click to expand...
Click to collapse
I'll give it a whirl. One question though, since I've never run into this. What do you mean because it doesn't do anything? Granted this is the only aosp I've played with so far, so my knowledge is a bit limited.
j1tters said:
I'll give it a whirl. One question though, since I've never run into this. What do you mean because it doesn't do anything? Granted this is the only aosp I've played with so far, so my knowledge is a bit limited.
Click to expand...
Click to collapse
Stock recovery is usually limited to stock functions. If you want to customize, you need custom recovery.
levone1 said:
Stock recovery is usually limited to stock functions. If you want to customize, you need custom recovery.
Click to expand...
Click to collapse
Ohhh. right. I thought you meant recovery didn't do anything with aosp. Read that wrong, brain fart.
So nope. Twrp cannot read /data. Same error as before. Magisk seems to have installed.
My guess is this is all coming from the forced encryption, though I haven't done enough research.. I'm going to see if I can get viper running..
j1tters said:
Ok. So I'm reflashing the rom via fastboot just like that guide states. Just ignoring the recovery flash?
Click to expand...
Click to collapse
Just wanted to say thanks. Magisk and viper are installed and working. TWRP still errors out with not being able to read /data but I got viper and root, and thats all I wanted.
Thanks!
j1tters said:
So nope. Twrp cannot read /data. Same error as before. Magisk seems to have installed.
My guess is this is all coming from the forced encryption, though I haven't done enough research.. I'm going to see if I can get viper running..
Click to expand...
Click to collapse
Yeah, I guess still no custom kernels for O yet, so... Did you already try decrypt data with twrp?
Nope. I got what I wanted at this point. I'm leaving well enough alone. I don't see having to really do anything with TWRP in the near future. I'll miss being able to do a full backup, and I'm a little annoyed I cant restore my 7.1 backup but I can live with that. I see I can decrypt but I'm a little gun shy and don't want to break anything again.
At the end of the day AOSP + viper is really all I needed.
Thanks again for all the help.