Related
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
geoff5093 said:
So this may be a stupid question, but this is my first Nexus device. I will have a 6P delivered Thursday and plan to unlock, decrypt, and install TWRP. The guides so far reference using MDB08K, and the modified boot is only for this version currently. After I install TWRP, am I able to install the factory image for the latest MDB08M and just exclude flashing certain images? Or do I need to flash them all then wait for a new modified boot image for 08M and install TWRP over again?
Click to expand...
Click to collapse
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
bitpushr said:
Its good to do this right away because when you unlock the bootloader, it wipes the phone. I haven't done this on mine yet because I'm curious about Android Pay and what impact that will have on it.
Click to expand...
Click to collapse
OH OH!!!! We have to behave, we have an Administrator with the same phone UGH!! Just kidding Hello @bitpushr
Somewheres around here someone is reporting pay working with unlock and root. If I recall correctly he removed root in su settings to add the card and then set back to root and it was working. Highly concerned individuals might want to verify that from multiple sources...
MrDSL said:
When I got mine the first thing I did was the OTA update and then I performed the root etc prcess
Click to expand...
Click to collapse
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
geoff5093 said:
But don't you need to use the corresponding modified boot image to root it? There currently isn't one for the latest factory image I believe.
Click to expand...
Click to collapse
Chainfire has one and I believe there is one in the development forum.
MrDSL said:
Chainfire has one and I believe there is one in the development forum.
Click to expand...
Click to collapse
I was looking at his thread, but I only see one for the 08K image.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The one in the dev section also appears to only be for 08K: http://forum.xda-developers.com/nexus-6p/development/kernel-stock-decrypted-kernel-verity-t3235013
I just wanted to confirm that these need to be the same, so I'll wait for an update.
I thought Build MBD08K was the latest..
I know that I'm currently running cleanrom MBD08K with modified MBD08K boot.img
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
Awesome!! ????
mysongranhills said:
Modified MBD08K boot.img from chainfire works fine with newest MDB08M. On my phone I unlocked bootloader, flashed all the MDB08M files, than flashed the modified boot.img.
I have working root, decrypted with TWRP installed.
Click to expand...
Click to collapse
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
rsmolen said:
I assume if we have MDB08K, rooted with TWRP and want to take the OTA to MDB08M, that we can use a similar procedure:
1. Flash stock boot.img and recovery.img from MDB08K factory image (temporarily disabling root and TWRP)
2. Download and install OTA
3. Reflash modified MDB08K boot.img from Chainfire
4. Reflash TWRP recovery
5. Install SuperSU 2.52 using TWRP
Has anyone tried this method?
Click to expand...
Click to collapse
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
In case anyone else is still wondering, flashing the 08M factory image and then using the 08K modified boot works fine. I'm on the latest and rooted right now.
mysongranhills said:
No, but your logic is sound. I see no problems doing it that way. Why would you prefer the OTA updates over the latest factory images? I know for me part of the reason I did it the way I did was b/c I couldn't get phone to download/recognize that OTA update existed.
Click to expand...
Click to collapse
I just thought this would be slightly easier than flashing the system.img from the factory image. However, given the modified boot.img and systemless SuperSU, I guess only flashing the system.img (and radio.img if changed) from the new build would probably be easier at this point. However, if xPosed comes to Marshmallow and modifies system, that will be another step in the upgrade process, which presumably would not need to be done if you could take the OTA the way I proposed.
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!
Follow at your own risk, I take no responsibility. This guide is for any stock(seems to work with mods) rom. I used TWRP RC1, but could possibly work with alpha 2(for adb sideload only). Not sure if this method is "better" than using flash-all.bat without -w, but the file download was smaller.
Required Files and Locations they should be placed:
TWRP RC1 Image placed in the same folder as your FASTBOOT executable
TWRP RC1 zip installer placed on phones internal storage
SuperSU 2.79 SR3 zip installer placed on phones internal storage
NOF27B or NOF27C - Rogers OTA placed in the same folder as your ADB executable
Ensure the TWRP and SuperSU zip installers are loaded onto the phones internal storage and the OTA zip and TWRP image are in the ADB/FASTBOOT executables folder.
Boot into current TWRP recovery
Make a full backup in TWRP
Connect the phone to the computer
In TWRP select the Advanced menu, click ADB sideload option
On the computer open a command window and navigate to the location of your ADB executable/OTA zip
Only execute one adb sideload command for your specific device
Execute the following command(Non-Rogers): adb sideload sailfish-ota-nof27b-8130b5a8.zip
Execute the following command(Rogers): adb sideload sailfish-ota-nof27c-fb487658.zip
Only execute one adb sideload command for your specific device
The command window should be displaying a percentage and the TWRP should be displaying the standard OTA step 1 and 2 - Let this complete
Click Reboot System and let the OTA finish installing
At this point TWRP and Root are gone, but can be restored
With the device powered off, hold volume down and turn on the device. Your device should now be in the bootloader.
With the device connected to the computer run the following command from the previous step's command window: fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Install twrp-pixel-installer-sailfish-3.0.2-0-RC1.zip in TWRP
Install SR3-SuperSU-v2.79-SR3-20170114223742.zip in TWRP
Click Reboot System
Install Kernel/Mods
Remember to restore any /system specific edits such as the tether build.prop edit, host file edits, or custom boot animations.
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
bush911 said:
This is amazing!. I have downloaded the full factory image already. followed by your guide, Can I just use an OTA package to upgrade NMF26O to latest build? I have rooted and twrp installed
Click to expand...
Click to collapse
Just remove the -w argument from the flash-all.bat and flash the factory image...
Thank you dude, so what's the difference between full factory image and full ota zip, and ota automatically downloaded to phone.
the factory image is around 1.8 G and full ota zip is around 800 M, but the ota automatically downloaded to phone is only 47 M
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
I had good luck with this method getting to NMF26O. Just a couple of things to note. Make sure you have the latest ADB files, and while it probably is assumed that you are using TWRP RC1 I'm pretty sure this did not work in Alpha2. Also, when the OP mentions losing TWRP it actually completely removes recovery so don't freak out if you try to boot into it expecting stock recovery and get a no data (or something like that if I remember correctly) error. There is no reason to check, but last time I was curious to see if it would leave TWRP in place. All is fine as long as you can get to bootloader. One other thing is the fact that this is an OTA. I would not do this unless coming from NMF26O but that is just me.
I am in no hurry to do this update since by all accounts it adds no functionality, but I was going to try it this way again. I wonder if anyone has any reason other than habit to continue to use the flash all method.
Juli112 said:
Just remove the -w argument from the flash-all.bat and flash the factory image...
Click to expand...
Click to collapse
so should we sideload the OTA over Q or download the factory image and remove the -w flag and run flash all.bat?
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
This is only for updating stock. If you want of weta then use the full image and remove the -w from the flashall bat file.
thank you! worked great!
quinejh said:
can this process be done if we are running stock rooted but with weta 2.2.1 installed? or does it need to be totallly stock? thanks
Click to expand...
Click to collapse
Because I'm groovy like that... (And had a nandroid backup) I went ahead and took the jump of sideloading the OTA update over weta 2.2.1. Personally, I wasn't too concerned about botching up the system, as the weta ROM is going away. Instead the author is now compiling his mod(s) to layer over this stock build. I'm assuming that the OTA sideload went without a hitch because weta is designed around the stock image. Of course, I had to install some of my mod's again that were lost in the "update"
**DISCLAIMER**
I'm not claiming or declaring the OTA update is safe to install over weta 2.2.1. I'm only giving my experience so others can weigh out the risks for themselves, if they decide to roll the dice. :silly:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
rohitece06 said:
I followed this method and everything went smoothly. I have the new update, supersu and elemental kernel but now I can not use android pay
Click to expand...
Click to collapse
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
spiller37 said:
I don't use Pay, but did you update to the latest Elemental kernel 1.03?
Click to expand...
Click to collapse
Yes I did.
rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
Try Franco's, his is patched for pay. Just to try and narrow it down here.
rohitece06 said:
Yes I did.
Click to expand...
Click to collapse
You might also try the patched stock kernel that was just updated.
spiller37 said:
You might also try the patched stock kernel that was just updated.
Click to expand...
Click to collapse
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Is something up with the OP or is it just my XDA app causing it to show like this..
aholeinthewor1d said:
Is something up with the OP or is it just my XDA app causing it to show like this..
Click to expand...
Click to collapse
Not sure why it displays this way in the two XDA apps. If anyone knows how to fix the formatting I would be grateful for the solution.
rohitece06 said:
Thanks it worked with patched stock kernel although I lost root and when I installed SuperSu 2.79 SR2 android pay stopped working.
Click to expand...
Click to collapse
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
spiller37 said:
Oh I didn't realize root and pay could work simultaneously on the pixel yet. Not sure which thread, but there was discussion on using the dual slots to run one slot stock with pay and one slot stock with root. Then dual booting between them.
Click to expand...
Click to collapse
it was working before this January pixel update
This morning I my phone pesented itself in TWRP.
Maybe this is because over the past days I repeatedly got notifications that a system upgrade wanted to install itself (I have a modified 26s X720 from Tora33).
I rejected those notifications.
Now I am stuck in TWRP and I cannot get around it. What I tried:
Reinstalling previous firmware (Tora33 26s) still on the phone
Restoring a TWRP backup from 6 months ago (TWRP didn't see it, maybe it's from a previous TWRP version, I now have v. 3.1)
Flash via fastbood factory image using Mauro's Tool All In One (error message "can't find file mke2fs.conf")
Wipe data, cache, dalvik cache, system; then install Mauro_V2.2 cleansed 23s firmware which I transferred to the phone
Every time it boots up in TWRP.
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Sent from my LEX720 using xda premium
mchlbenner said:
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Click to expand...
Click to collapse
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Wortelstok said:
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Click to expand...
Click to collapse
Yes, that QFIL guide is for the x720.
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
marik1 said:
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
Click to expand...
Click to collapse
If he was just going back stock that would work he flash 28s ota with twrp so this will not work.
Sent from my LEX720 using xda premium
No brick after OFW push 28s
The pushed (unvoluntary) update didn't brick my phone after all. This may be important for those that have modified stock ROMs with TWRP.
Not being able to restore OFW was a bug in Mauro's All-in-One tool which he fixed last night. After I could easily flash 20S or 26S stock from his repository. I would also recommend this as safest/easiest procedure. Afterwards you can just flash TWRP from the same tool and move from there.
By the way, immediately after flashing 20s the FW notified it wanted to update itself, again!
n my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
Click to expand...
Click to collapse
Might have tried that
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