Related
I received a Motorola OTA notification for a minor maintenance update which patched the "stagefright" vulnerability in my Moto X 2014 Pure Edition xt1095. I captured the OTA ZIP file from my cache folder, and it is attached to this post. Size of OTA ZIP is 4.29MB. (Note that Motorola OTA updates are named for the software version from which you must apply the update, not the software version to which you are upgrading.)
This is for a stock, unrooted xt1095 running Android Lollipop 5.1.
Prerequisite:
System version: 23.16.3
Build number: LPE23.32-21.6 or LPE23.32-21.3
After update:
System version: 23.16.6
Build number: LPE23.32-21.6 or LPE23.32-21.3 (unchanged)
You should be able to adb sideload this from stock recovery if you know how. If you're rooted, you'll need to request the stock 23.16.3 firmware from Motorola, and at least flash system.img and recovery.img to get back to stock system and recovery. After you do that, you might be able to sideload the OTA zip.
Deleted, sorry.
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Flash fails (TWRP finds something incorrect with HindiIME file or somesuch). Can this be caused by me removing unneeded system apps?
EDIT: Yes it was, worked perfectly after reflashing system.img.
Thanks thenestor and Romracer worked perfectly as stated I went with twrp flash -
I just installed this update from the stock recovery and it worked flawlessly. Thanks for uploading this. My wife got it a few days ago and updated before I could grab the the zip file.
Sent from my XT1095 using Tapatalk
Flintberg said:
Flash fails (TWRP finds something incorrect with HindiIME file or somesuch). Can this be caused by me removing unneeded system apps?
EDIT: Yes it was, worked perfectly after reflashing system.img.
Click to expand...
Click to collapse
System.img? Download please
I reflashed system.img of my current version and then flashed the zip in twrp.
romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
I had a stock bootloader+recovery, so I just updated via the OTA, but now my phone won't boot! Any ideas?
I'm rooted with adaway applied, I tried flashing romracer's file but I'm stuck on the boot screen saying that my bootloader is unlocked. Is it because of adaway?
romracer said:
Thanks! With public exploit code available now, this is all the more important. You can modify the updater-script to not require a stock recovery. It will work fine, as long as you haven't modified anything else in /system.
For the uninitiated, here's a version you can flash with TWRP. You must still have a stock system partition. SuperSU/Xposed is fine, but you can't have changed any files it needs to patch, like the dialer or camera. I've used it fine myself.
PS: If you do have Xposed installed, uninstall it, flash the update, then reinstall Xposed.
Click to expand...
Click to collapse
Thank you so much for this! I lost my stock recovery so this is a godsend.
Flintberg said:
I reflashed system.img of my current version and then flashed the zip in twrp.
Click to expand...
Click to collapse
system.img have the backup to download and can flash? Sorry my english
tbs1977 said:
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
Click to expand...
Click to collapse
I'm having the same problem! Any idea how to fix it?
Damn. That file from romracer broke my phone
seriously....i can't fix it
@romracer
not sure if i understood correctly, so is it fine to have xposed? or better remove it before?
i have gravity box, bootmanager, amplify and appops
sh33z0r said:
@romracer
not sure if i understood correctly, so is it fine to have xposed? or better remove it before?
i have gravity box, bootmanager, amplify and appops
Click to expand...
Click to collapse
If you have Xposed, you need to reflash the installer zip.
---------- Post added at 07:34 AM ---------- Previous post was at 07:29 AM ----------
supremekizzle said:
Damn. That file from romracer broke my phone
seriously....i can't fix it
Click to expand...
Click to collapse
Re-flash the system.img and try again. You can find LP-5.1 for XT1095 here. (the only thing you should be upgrading from anyway).
tbs1977 said:
Thanks for this. I successfully flashed with TWRP, but now I'm hanging on the initial boot screen. Did I do something wrong?
Click to expand...
Click to collapse
macravin said:
I had a stock bootloader+recovery, so I just updated via the OTA, but now my phone won't boot! Any ideas?
Click to expand...
Click to collapse
RSchmauk said:
I'm having the same problem! Any idea how to fix it?
Click to expand...
Click to collapse
Did you have Xposed install? Reflash the install zip. Otherwise see above.
romracer said:
If you have Xposed, you need to reflash the installer zip.
---------- Post added at 07:34 AM ---------- Previous post was at 07:29 AM ----------
Re-flash the system.img and try again. You can find LP-5.1 for XT1095 here. (the only thing you should be upgrading from anyway).
Did you have Xposed install? Reflash the install zip. Otherwise see above.
Click to expand...
Click to collapse
i was rooted with xposed only, and now my phone won't turn on, stuck on the boot screen...
i have two questions,
If i reflash system.img, will that wipe anything?
is there a system.img only file that i can download, downloading 1.1 gbs on my slow connection will take 4 hours, i can't afford 4 hours without a phone....
After the ota, my phone won`t turn on, like many here. What i`m worried about is that my PC is not recognizing my phone in adb. What can I do?
I was also rooted, with stock everything else but hung on the unlocked bootloader warning screen. I'm thinking AdAway or Greenify must have modified /system since that's really the only root stuff I use. For the time being I just restored my /system backup and it's working but I'll eventually need to flash stock system.img I'm guessing. Otherwise I'm gonna end up accidentally tapping the update nag screen and screwing it up again.
Hello there,
I thought that there were more people with this problem, but I've this problem: first off, I got stock MM installed on my Style xt1572. Unlocked bootloader and the latest TWRP. But when I try to install SuperSU via TWRP, it just get stuck before the reboot animation. Any idea's what I could try perhaps?
Edit: Solution is just using the SuperSU in this thread: http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792
Thanks.
Did you select install SuperSU when twrp asked ? After flashing newest supersu?
Sent from my XT1575 using Tapatalk
Settler11 said:
Hello there,
I thought that there were more people with this problem, but I've this problem: first off, I got stock MM installed on my Style xt1572. Unlocked bootloader and the latest TWRP. But when I try to install SuperSU via TWRP, it just get stuck before the reboot animation. Any idea's what I could try perhaps?
Thanks.
Click to expand...
Click to collapse
Which SuperSU version are you using?
Settler11 said:
Hello there,
I thought that there were more people with this problem, but I've this problem: first off, I got stock MM installed on my Style xt1572. Unlocked bootloader and the latest TWRP. But when I try to install SuperSU via TWRP, it just get stuck before the reboot animation. Any idea's what I could try perhaps?
Thanks.
Click to expand...
Click to collapse
Men i have the same problem and i dont know what to do :/
@patt yes.
@Doktaphex The one TWRP asked me to install and the latest beta. 2.49. Same problem.
Depending on the version of SuperSU that you are using there are 2 different rooting methods.
My suggestion would be to use the systemless root option here: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
v2.65 is what you want. When you flash this in twrp it will automatically patch the boot image on your device (whilst also creating a backup of the original). It sounds as though you are both trying to use a version of SuperSU that implements the standard rooting method, this would mean that you must manually flash a modified boot image in order to bypass Android 6.0's internal system modification checks!
Flash the stock boot.img. Then see if it boots. Then ^^^ this^^^
Settler11 said:
@patt yes.
@Doktaphex The one TWRP asked me to install and the latest beta. 2.49. Same problem.
Click to expand...
Click to collapse
Do not allow twrp to attempt to install superSU
IMPORTANT!!!!
Because you have already allowed twrp to do this, you will need to reflash your system partition to ensure that all traces of that version of SuperSU are removed before you flash the newer version.
I hope this helps you guys.
patt2k said:
...
reflash your system partition
....
Click to expand...
Click to collapse
What do you mean with that? We've to reflash a rom, kernel? What?
Settler11 said:
@patt yes.
@Doktaphex The one TWRP asked me to install and the latest beta. 2.49. Same problem.
Click to expand...
Click to collapse
You are not suppose to click install superSU when twrp asks for it.
Sent from my XT1575 using Tapatalk
patt2k said:
You are not suppose to click install superSU when twrp asks for it.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Yes.. But as you can see, I've done that already. But I got a restore without it. But even if I install that latest beta, the problem still presumes.
Settler11 said:
What do you mean with that? We've to reflash a rom, kernel? What?
Click to expand...
Click to collapse
Sorry, I should have been more clear in my instructions. I would go ahead and reflash the rom that you want to use and then flash superSU v2.65.
Reboot and if twrp asks if you want it to install superSU choose the option for it NOT to do so.
Settler11 said:
Yes.. But as you can see, I've done that already. But I got a restore without it. But even if I install that latest beta, the problem still presumes.
Click to expand...
Click to collapse
I had this issue but I had backup of my stock rooted rom. I'd suggest maybe go back to stock with restore tool?
Sent from my XT1575 using Tapatalk
patt2k said:
I had this issue but I had backup of my stock rooted rom. I'd suggest maybe go back to stock with restore tool?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I'M on stock! And that restore tool is for Pure, not Style! And I don't want to install a custom rom. Stock rom is still fine for me.
Settler11 said:
I'M on stock! And that restore tool is for Pure, not Style! And I don't want to install a custom rom. Stock rom is still fine for me.
Click to expand...
Click to collapse
Idk then sorry I have pure
Sent from my XT1575 using Tapatalk
Also tried Kingo root funny enough, but no go.
Edit: Wow, okay. Installing some kind of version of SuperSU does the trick apparently. It's in here:
http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792
I was running Adaway on my rooted/soff M7 and would like to run it on my now rooted/soff 10. I tried downloading v3.3.1 from @mrRobinson thread here but each time I tried to open the program it said something about a SuperSU error. I'm guessing that it didn't like the modified SuperSU we used rooting the 10 to keep forceencrypt? Any one have an idea or see something I did wrong?
Edit:
Looking through my apps list I can't find SuperSU, but I know it's on here cause it ran when sunshine requested root access and I had to side load it through TWRP for root. Why wouldn't it show up in my app list?
use this, then adaway works fine: http://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
Load this app: jRummy Root Check
It should work if the SuperSU process was successful. I used jcase's guide Root-optionally-s-off-radio
After that, I loaded the XDA Labs App, then loaded AdAway. Everything working as it should.
You may want to retrace your steps to jcase's quide, and see what might have been missed.
HTH.
I followed jcases method for root and soff and had to side load the modified SuperSU that @starbase64 linked to in that process. That jRummy app says I do not have root. Can I just flash the modified SuperSU in TWRP? I'm definitely soff, so how would I be able to get soff without root? So weird
yes, but restore stock boot.img first
Yes that should work.
Root these days is in the boot.img so if you reflashed that at any point you are back at stock.
Adaway is working fine here!
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Light1984 said:
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Click to expand...
Click to collapse
starbase64 said:
use this, then adaway works fine: http://forum.xda-developers.com/htc-10/development/root-supersu-2-71-forceencrypt-verity-t3373258
Click to expand...
Click to collapse
Did you flash this file in twrp yet? That should be all you need to do.
Light1984 said:
The only thing I did after jcases root/soff procedure was flash the Verizon radio from @dottat. Not sure how I would have messed with the boot.img
Click to expand...
Click to collapse
Oh well
If SuperSU isn't in the app tray and you haven't hidden it manually, flashing back SuperSU (preferably topjohnwu version) should bring it back.
10-4 brb. Thanks
Edit: yes, I checked with jcase too. Just reflashed the zip in TWRP. Although when it was going through its process it said it already found the files and over wrote them anyways, maybe something got corrupted at some point. All is well now, thanks for the help all.
May also be something in /data/ somewhere which will be lost as S-Off forces data to be reset -- but again a TWRP install of SuperSU should cover it.
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
You must do the following:
1. Return to complete stock - that means get rid of root and TWRP. Best way to do that is download the factory image from Google, extract the boot, recovery, and system images from the factory image, and Flash those, for example: fastboot flash recovery recovery.img Don't flash data.img so you can keep your data.
2. OTAs depend on stock recovery to load, so now that you're back to stock, you have 2 choices. You can simply boot your phone normally, wait for the notification for the update, install it, and you're done - or, you can access android's stock recovery and side load the OTA zip using ADB. Good luck
Sent from my Nexus 6P using Tapatalk
Gamer_Josh said:
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
Click to expand...
Click to collapse
I forgot to mention that I also had TWRP recovery installed. The result was like it is with a normal OTA update, as none of my data/apps/settings were affected. Worked like a charm!
DJBhardwaj said:
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
ponzi314 said:
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
Click to expand...
Click to collapse
You are sure that you used the correct OTA file?
DJBhardwaj said:
You are sure that you used the correct OTA file?
Click to expand...
Click to collapse
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
ponzi314 said:
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
Click to expand...
Click to collapse
That's weird. It has worked for me everytime, and most users here.
DJBhardwaj said:
That's weird. It has worked for me everytime, and most users here.
Click to expand...
Click to collapse
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
tech_head said:
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
Click to expand...
Click to collapse
Sideloading the update, right?
DJBhardwaj said:
Sideloading the update, right?
Click to expand...
Click to collapse
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
tech_head said:
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
Click to expand...
Click to collapse
I also avoid using any toolkits. Yes I know they are fast and easy, and of course someone's hardwork. But I like to everything manual, same as you. :highfive:
I usually like to do things like that manually, because I like to know how things work. But I was under a bit of a time crunch at that point, so decided to try the Nexus Root Toolkit. Though I do understand the procedure of sideloading OTA updates via ADB, from researching and reading on the forums here.
Anywho, I hope you are able to get it going OP.
The OTA fixed it for me, thank you so much!
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Guitarboarder28 said:
Has anyone had any issues trying to flash the latest supersu beta on 7.1.1? I get an abort message whenever I flash
Click to expand...
Click to collapse
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
ohlin5 said:
Chainfire has stated before that root with SuperSU on 7.1 may be a while, that he's working on it but a lot has changed (at least I read this all from him on a Pixel related thread...I assume much of it holds true for 7.1 in general).
Click to expand...
Click to collapse
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Mgrev said:
I rooted the 7.1 DP 1 With supersu SR1-v2.78.
No issues at all (even A.R.I.S.E. worked after deleting audio_effects.conf)
Click to expand...
Click to collapse
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Guitarboarder28 said:
Did you root after flashing the ota or full image? I've been trying sr1 and for whatever reason after the ramdisk patch script it fails.
Click to expand...
Click to collapse
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Mgrev said:
I used Fastboot and flashed every image manually (so that i wouldn't loose data). I used twrp 3.0.2-2 fyi. What about you?
Click to expand...
Click to collapse
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Guitarboarder28 said:
you sound like you need a hug!
Oh thanks. I've seen others talk about rooting on 7.1 no problem. I'll have to do more digging I guess
Click to expand...
Click to collapse
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
ohlin5 said:
Interesting...maybe he was exclusively referring to the new Pixel partition structure, etc...Not sure. Good luck
Click to expand...
Click to collapse
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
dratsablive said:
I was able to flash SuperSU R1 from TWRP and it worked, but when I added SUHIDE it hangs at boot animation. I flashed the factory image file by file, and not the OTA.
Click to expand...
Click to collapse
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Guitarboarder28 said:
Yes that's my guess too I'm assuming he's talking about the pixel and it's new partitions
oh thanks for the heads up. Who knows if we'll ever see an updated suhide with safetynet checking the bootloader it may never be possible to pass safety net anymore
Click to expand...
Click to collapse
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
dratsablive said:
Well not worried about passing safetynet, since I can do without Android Pay, just want to hide root to play PoGo.
Click to expand...
Click to collapse
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Guitarboarder28 said:
Oh is it no longer using safetynet? There's a new hide method with magisk V8 maybe that'll work
Click to expand...
Click to collapse
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Guitarboarder28 said:
I was trying after flashing the ota. I even tried the full image without wiping (same version of twrp as you). Something must have just gotten messed up flashing the ota though. I gave up and did a full flash with wipe and sr1 flashed no problem. Thanks for trying to help me out though, I appreciate it
Edit: worded better. @Mgrev no hate was meant, thanks for trying to help me out!
Click to expand...
Click to collapse
I didn't think you meant to express hate either!
I seemed to forget to mention that i backed up my data with titanium backup, flashed, then wiped, and then restored it. So in the end, you probably need to wipe (just like you did)
dratsablive said:
Well my bootloader is unlocked, but having suhide installed on the developer preview causes a boot hang. Will have to try the other method out. Thanks.
Click to expand...
Click to collapse
Magisk hide just hides Magisk itself... it doesn't do anything for root. As for PoGo, right now the only way to do that on 7.1.1 is to NOT be rooted.
Once the kernel sources for the 7.1.1 are released, this patch will make its way onto custom kernels, which means you'll still be able to edit /system while rooted, unroot, and keep the changes via the patched kernel, as well as bypassing the SafetyNet bootloader check.
A kernel does exist now with that patch (francokernel), but it is based on the 7.0 kernel sources, so some things are broken if used on 7.1.1.
In re: to the superSU ramdisk install failure, this will happen if there are old files left over in /data from a previous magisk install and/or patched boot images. The SuperSU installer script will detect those and step into code branches that it doesn't need to be in, and thus fail. The solution is deleting the offending files from TWRP w/ adb, and installing SuperSU zip again.
/thread
Thread cleaned a bit, please stay on topic.
Have a good day!
Forum moderator,
Matt
Works fine for me flashed 7.1.1 OTA then flashed SuperSU zip