Assistance before rooting Nougat - X Style (Pure) Q&A, Help & Troubleshooting

Hi all
Ok so, I am updated to Nougat (EU) with no modifications besides an unlocked bootloader.
Since the last fastboot firmware file currently available to us is the September 2016 security patch, I'm a little hesitant to root right now. I want to be sure I'm be able to take new OTAs (if we ever get more). But I'm not sure if the September build will work now after updating to Nougat.
So what can we do in the meantime. Well that's where I may need guidance, but I think I have the idea down, so might still be useful information.
Ok, so to root, I first need to install TWRP - a custom recovery. But to accept OTAs I need to keep the stock recovery.img (which is overwritten by TWRP). Then I'd flash Magisk for root - and Magisk will modify the boot.img, so i need to keep the stock boot image (all of which we'd have if we had the actual fastboot files).
Anyways, I think it's quite easy. The only tricky part for me is the recovery. How do I get a backup of the stock one? Does TWRP make a backup during install ("fastboot flash recovery TWRP.img")? If so, where is this backup? I know I can back up the boot.img with TWRP before flashing Magisk (I believe Magisk makes a backup anyways, so if you use the Magisk uninstaller, the stock boot will be restored). But the recovery... If these two stock images can be backed up then it's easy to restore them to accept an OTA. Or is it not that simple? Can you actually flash the stock recovery from within TWRP (thereby overwriting itself)?

1. Unlock bootloader.
2. Boot only twrp 3.1.+ with:
fastboot boot NameOfTwrp.img
2a. Create your own full backup(recovery, boot, system, efs, opt. data).
3. Flash twrp for stable:
fastboot flash recovery NameOfTwrp.img
Boot into twrp from BL menu without rebooting system.
4. Magisk, read here, post #4
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Newest version is 13.3, you need twrp for magisk updates or modules.
https://forum.xda-developers.com/apps/magisk
---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------
@d.casper.b

dzidexx said:
1. Unlock bootloader.
2. Boot only twrp 3.1.+ with:
fastboot boot NameOfTwrp.img
2a. Create your own full backup(recovery, boot, system, efs, opt. data).
3. Flash twrp for stable:
fastboot flash recovery NameOfTwrp.img
Boot into twrp from BL menu without rebooting system.
4. Magisk, read here, post #4
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Newest version is 13.3, you need twrp for magisk updates or modules.
https://forum.xda-developers.com/apps/magisk
---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------
@d.casper.b
Click to expand...
Click to collapse
Awesome thanks, I'll try that when I get home tonight.
And one can just restore stock recovery when needed from within TWRP?
One must really prepare well for OTAs these days without the actual fastboot files readily available.

d.casper.b said:
Awesome thanks, I'll try that when I get home tonight.
And one can just restore stock recovery when needed from within TWRP?
One must really prepare well for OTAs these days without the actual fastboot files readily available.
Click to expand...
Click to collapse
All canbe restored with twrp.
Only modified logo.bin you have to flash with fastboot. It is in "stock ota nougat reteu" thread.
---------- Post added at 12:17 PM ---------- Previous post was at 12:14 PM ----------
#163 & next few posts
https://forum.xda-developers.com/mo...7-0-nougat-t3630248/post72928449#post72928449

I've just booted TWRP and backed up all partitions...but I don't see recovery.
All that is available is: Boot, System, Data, Cache, and EFS.
It seems silly, but I know the official TWRP app from the play store has a backup recovery option but it needs root...
So my thinking is: boot into TWRP (don't flash it) then root the device with magisk. Use the TWRP app to backup recovery .............. and you just replied with my same thinking...
HAHA, I just unistalled flashfire today. I'll install it again.

d.casper.b said:
I've just booted TWRP and backed up all partitions...but I don't see recovery.
All that is available is: Boot, System, Data, Cache, and EFS.
Click to expand...
Click to collapse
Hmm...
I thought twrp 3.1.1 can backup stock recovery.
Don't flash twrp.
Boot twrp, root with magisk(same way), reboot phone.
Install flashfire app(play store) and do backup of stock recovery(option - for fastboot).
Flashfire: , backup, ..., it will reboot the phone and do backup. After it you can flash twrp with fastboot.

awesome man, I was just editing my post when the email that you replied came through
I think I'll do this tomorrow night now! I'll update if it's successful.

Thanks for assisting me to get this done!
Ok, well I decided to get it over with.
Backed up the recovery with TWRP app and just made a fastboot backup of recovery with flashfire now..
Actually, if you never flash TWRP then it would just be a matter of restoring the boot.img - but of course, then you always need to be at a PC.
Last thing, can I use the No Unlocked Bootloader warning logo and it won't break anything (like later OTAs)?

d.casper.b said:
Last thing, can I use the No Unlocked Bootloader warning logo and it won't break anything (like later OTAs)?
Click to expand...
Click to collapse
I don't know(about ota).
Original Logo bin - flashfire can backup it(normal or full section).

All done! Now hopefully prepared for whenever the time comes!
Thank you so much for helping me out on this little journey

You're welcome.
I hope it will be useful to others. Everyone should do so.

dzidexx said:
You're welcome.
I hope it will be useful to others. Everyone should do so.
Click to expand...
Click to collapse
My thoughts exactly.

Related

[ROOT] CWM Test 8/Flashable SuperSU

As discovered in the Q&A post found here: http://forum.xda-developers.com/moto-x-2014/help/root-t2886674/page2
Just like the first Moto X, users have been having success rooting by unlocking the bootloader and just flashing SuperSU with CWM. This is a test release so it may be wise just just boot to CWM to flash SuperSU instead of flash it. Use caution as always.
Bootloader Unlock Guide: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
CWM Test 8: http://d-h.st/XJr
SuperSU flashable ZIP: http://forum.xda-developers.com/showthread.php?t=1538053
I can report that this did work for me and I have achieved root.
Steps I took:
1. Unlock bootloader using Motorola's website
2. boot to bootloader, flash or boot to recovery with fastboot command (fastboot flash recovery cwm.img/fastboot boot cwm.img) *There really isn't a reason to flash this. It is very broken. Consider keeping your original recovery!*
3. boot to cwm and flash superSU zip
4. CWM will prompt to fix root, choose YES
5. Rooted!
Almost everything besides flashing a zip is broken in this CWM release, don't expect to be able to backup with it.
Vultorus said:
This hasn't been posted yet, so I'm just sharing what was found in the Q&A post found here: http://forum.xda-developers.com/moto-x-2014/help/root-t2886674/page2
Users have been having success rooting by unlocking the bootloader and just flashing SuperSU with CWM. This is a test release so it may be wise just just boot to CWM to flash SuperSU instead of flash it. Use caution as always.
Bootloader Unlock Guide: http://forum.xda-developers.com/moto-x-2014/general/guide-unlock-bootloader-moto-x-2014-t2876773
CWM Test 8: http://d-h.st/XJr
I can report that this did work for me and I have achieved root.
Click to expand...
Click to collapse
I appreciate you posting this, could you by any chance post a little bit more detail on how to do the flash? Is it as simple as extracting the recovery image and flashing from ADB? How do you then flash SuperSU?
km8j said:
I appreciate you posting this, could you by any chance post a little bit more detail on how to do the flash? Is it as simple as extracting the recovery image and flashing from ADB? How do you then flash SuperSU?
Click to expand...
Click to collapse
I added some basic steps to original post, use caution as this isn't the most secure way to root but it will do for now. If you need further help, you should probably wait for a safer method.
Vultorus said:
I added some basic steps to original post, use caution as this isn't the most secure way to root but it will do for now. If you need further help, you should probably wait for a safer method.
Click to expand...
Click to collapse
What are the gaps in security? When you say secure, do you mean safe as in not bricking the phone or security as in data is at risk, etc.?
Vultorus said:
I added some basic steps to original post, use caution as this isn't the most secure way to root but it will do for now. If you need further help, you should probably wait for a safer method.
Click to expand...
Click to collapse
the steps you listed are pretty much it. can't get any easier than that. exactly how it was on the previous MotoX. unlock bootloader, fastboot flash recovery .img. then just reboot to recovery and flash SuperSU zip. very straight forward.
edit: also, fix permissions shouldn't be required...
mrvirginia said:
the steps you listed are pretty much it. can't get any easier than that. exactly how it was on the previous MotoX. unlock bootloader, fastboot flash recovery .img. then just reboot to recovery and flash SuperSU zip. very straight forward.
edit: also, fix permissions shouldn't be required...
Click to expand...
Click to collapse
It was just mentioned in the original post, I guess it doesn't matter. And by not secure I mean that the CWM is a test release so I don't know what could go wrong.
Vultorus said:
It was just mentioned in the original post, I guess it doesn't matter. And by not secure I mean that the CWM is a test release so I don't know what could go wrong.
Click to expand...
Click to collapse
yeah i'm still awaiting a device so i'm not 100% sure on the persmissions. the zip should do all the work for the user, though, via the update-binary.
btw thanks for posting.
Thanks for posting this, I suggested the guys in Q&A to do that. If anybody needs help, I made the process successfully back on Q&A (when they were testing the recovery)
If anyone notices the permissions making a difference let me know, I'm curious as to why everyone was saying it had to be done..
"cannot load 'recovery': Permission denied" when trying "fastboot boot recovery cmw.img"
My bootloader is unlocked.
---------- Post added at 08:56 PM ---------- Previous post was at 08:37 PM ----------
rogeriorc said:
"cannot load 'recovery': Permission denied" when trying "fastboot boot recovery cmw.img"
My bootloader is unlocked.
Click to expand...
Click to collapse
ops, forget about it.
the command is "fastboot boot cmw.img"
And I am rooted! :laugh:
Worked for me. I'm now rooted
2/10 needs more Verizon
rogeriorc said:
"cannot load 'recovery': Permission denied" when trying "fastboot boot recovery cmw.img"
My bootloader is unlocked.
---------- Post added at 08:56 PM ---------- Previous post was at 08:37 PM ----------
ops, forget about it.
the command is "fastboot boot cmw.img"
And I am rooted! :laugh:
Click to expand...
Click to collapse
I apologize, I did not realize if you are just booting, you don't need the "recovery" part of that command. Glad it worked for you!
You mention that this version of CWM is limited to basically sideband loading and won't do backup. Do you happen to know where I can find a copy of CWM for the X 2014 that gives me shell access? I've already unlocked and rooted my phone, but busted my screen and want to back things up. I went to their rom manager page and can't find either version of the X. Would either a 6.0.5.1 or one of the Nexus ones work?

[OBSOLETE] Root Android 7.0 Nougat after clean Install - Just use TWRP 3.0.2.1

Edit: Obsolete now. Twrp 3.0.2.1 is Out.
For now TWRP cant decrypt Android Ns vendor images so you cant flash SuperSU. So why not flash back old vendor to root the device and reflashing the NRD90M Vendor?
It works great. I root my clean install from factory image Android 7.0 NRD90M:
1. Flash the just released NRD90M via Fastboot
2. Reboot and set up your device.
3. Reboot to fastboot and flash vendor_mob30w.img by entering: fastboot flash vendor vendor_mob30w.img
4. Boot TWRP 3.0.2.0 temporary by entering: fastboot boot twrp-3.0.2-0-flounder.img
5. In TWRP copy UPDATE-SuperSU-v2.76-20160630161323.zip to your device and install it.
5.1 If you want to use adaway flash also AdAway_systemless_hosts_v2.zip.
6. Go back - back - back and reboot your device to fastboot.
7. Reflash the original vendor vendor_nrd90m.img by entering: fastboot flash vendor vendor_nrd90m.img
8. Reboot your device. Its rooted!
Extract the vendor files from the factory images or take these just extracted files from my google drive:
Download vendor_mob30w
Download vendor_nrd90m
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
corkiejp said:
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
Click to expand...
Click to collapse
Is that one system less?
edit: nevermind this
osnapitsjoey said:
Is that one system less?
Click to expand...
Click to collapse
Yes CFAR is systemless.
If you were not a very smart man and encrypted your device during the install will this method work? Does it allow you to take monthly security updates still?
corkiejp said:
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
Click to expand...
Click to collapse
I don't know if what I did was right, but without changing vendor image my N9 got boot loop at TWRP welcome screen. TWRP could only run properly after flashing old vendor image.
GialanG said:
I don't know if what I did was right, but without changing vendor image my N9 got boot loop at TWRP welcome screen. TWRP could only run properly after flashing old vendor image.
Click to expand...
Click to collapse
It will bootloop and eventually load. At least that is what it did on the previews. Haven't tested on final release.
You still can not modify/read encrypted data partition, hence OTG or sideloading of zips.
Edit:- Just tested and it eventually loads.
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9.
corkiejp said:
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9.
Click to expand...
Click to collapse
Cool, thanks ! Is there also a way to decrypt the tablet ?
TheLonelyCyborg said:
Cool, thanks ! Is there also a way to decrypt the tablet ?
Click to expand...
Click to collapse
Make sure you have flashed latest supersu.zip which has encryption flag disabled.
Then format your data partition.
For future updates make sure to flash supersu again before booting your tablet other wise it will re-encrypt.
---------- Post added at 01:44 PM ---------- Previous post was at 01:33 PM ----------
@Donald Nice Maybe you should update the first post, now that a working TWRP is available for encrypted Nexus 9.
corkiejp said:
Make sure you have flashed latest supersu.zip which has encryption flag disabled.
Then format your data partition.
For future updates make sure to flash supersu again before booting your tablet other wise it will re-encrypt.
---------- Post added at 01:44 PM ---------- Previous post was at 01:33 PM ----------
@Donald Nice Maybe you should update the first post, now that a working TWRP is available for encrypted Nexus 9.
Click to expand...
Click to collapse
Thanks @corkiejp it worked like a charm !
Can you please update this guide?
Sent from my Nexus 9 using Tapatalk
Twrp bootloop
I stupidly updated my nexus 9 (wi-fi) to nougat which I think is awful. I flashed it via wugfresh as it was unlocked and rooted. Flashed back to 6.0.1. Trying to install twrp 3.0.2.1. It bootloops but eventually loads. I added a pin as it was the only way I could decrypt, I get the partition decrypted and then it bootloops again. Haven't been able to root. Now running 6.0.1 no root trying to install twrp 3.0.2.1. Should I just use 3.0.2.0?
lawlor059 said:
I stupidly updated my nexus 9 (wi-fi) to nougat which I think is awful. I flashed it via wugfresh as it was unlocked and rooted. Flashed back to 6.0.1. Trying to install twrp 3.0.2.1. It bootloops but eventually loads. I added a pin as it was the only way I could decrypt, I get the partition decrypted and then it bootloops again. Haven't been able to root. Now running 6.0.1 no root trying to install twrp 3.0.2.1. Should I just use 3.0.2.0?
Click to expand...
Click to collapse
Use 3.0.2-0 for Marshmallow! 3.02-1 is for nougat only.
corkiejp said:
Use 3.0.2-0 for Marshmallow! 3.02-1 is for nougat only.
Click to expand...
Click to collapse
3.0.2-1 works perfectly fine for marshmallow.
dictionary said:
3.0.2-1 works perfectly fine for marshmallow.
Click to expand...
Click to collapse
Thanks @corkiejp. @dictionary I couldn't get into the recovery with 3.0.2.1. Entering the decrypt code would just cause it to loop again. Ignoring the decrypt code I could get into the recovery but with nothing mounted it's useless. It will install successfully but nothing can be done with it.

Android Pie 9.0 root possible ??

Hi guys, I had read many posts about rooting essential phone. But those articles aren't mention if it is suitable for android Pie version. Is there anyone knows how to root my essential phone with Pie 9.0 ??
See this thread.
prabs99 said:
See this thread.
Click to expand...
Click to collapse
Thanks for your reply. I had read this thread. But in step 4. Once you're in TWRP, install the stock boot image and then the Magisk zip.
I wonder which boot image I should install, cause both NMJ32F & NMJ20D are not same as android P build number which is "PPR1.1806.10.091".
I will appreciate for your help.:laugh:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
eric672913 said:
Thanks for your reply. I had read this thread. But in step 4. Once you're in TWRP, install the stock boot image and then the Magisk zip.
I wonder which boot image I should install, cause both NMJ32F & NMJ20D are not same as android P build number which is "PPR1.1806.10.091".
I will appreciate for your help.:laugh:
Click to expand...
Click to collapse
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Try this for just the boot image.
prabs99 said:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
Click to expand...
Click to collapse
prabs99 said:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Try this for just the boot image.
Click to expand...
Click to collapse
Got it , I will try this. Thanks so much:laugh:
eric672913 said:
Got it , I will try this. Thanks so much[emoji23]
Click to expand...
Click to collapse
Try but fail and get boot loop [emoji27] . Reboot to bootloader and flash twrp, then get into TWRP recovery , flash Magisk then boot img. Anything wrong?
Sent from my [device_name] using XDA-Developers Legacy app
eric672913 said:
Try but fail and get boot loop [emoji27] . Reboot to bootloader and flash twrp, then get into TWRP recovery , flash Magisk then boot img. Anything wrong?
Click to expand...
Click to collapse
Your doing the order wrong.
When you get into TWRP, flash the boot.img that matches the current build you are on, then flash the magisk zip, then reboot.
NaterTots said:
Your doing the order wrong.
When you get into TWRP, flash the boot.img that matches the current build you are on, then flash the magisk zip, then reboot.
Click to expand...
Click to collapse
I just got a new unrooted phone and took the Pie OTA. Just to be sure I understand you, in my case, I already have the correct boot.img and can go ahead and flash TWRP, then Magisk just like on old phones, right?
jwinstonsf said:
I just got a new unrooted phone and took the Pie OTA. Just to be sure I understand you, in my case, I already have the correct boot.img and can go ahead and flash TWRP, then Magisk just like on old phones, right?
Click to expand...
Click to collapse
That's not what I wrote
First go into settings and make sure you have the build that ends with 091.
Then from either the BTS zip you downloaded, or from the Root guide thread, make sure you have the boot.img that is tagged 091. (Personally I've been using the boot.img's that are uploaded in the OP of the Guide to root thread)
Then, go through the fastboot process to install TWRP,
boot into TWRP,
then install the boot.img,
then flash the magisk zip.
Reboot profit.
You have to flash the boot.img for the current build your running Everytime you want to flash something through TWRP.
NaterTots said:
That's not what I wrote
First go into settings and make sure you have the build that ends with 091.
Then from either the BTS zip you downloaded, or from the Root guide thread, make sure you have the boot.img that is tagged 091. (Personally I've been using the boot.img's that are uploaded in the OP of the Guide to root thread)
Then, go through the fastboot process to install TWRP,
boot into TWRP,
then install the boot.img,
then flash the magisk zip.
Reboot profit.
You have to flash the boot.img for the current build your running Everytime you want to flash something through TWRP.
Click to expand...
Click to collapse
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Sent from my [device_name] using XDA-Developers Legacy app
eric672913 said:
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Click to expand...
Click to collapse
Boot.img
eric672913 said:
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Boot image should go to the boot partition.
Click on link, Download essentials zip
Reboot to bootloader
Flash twp img
Boot to recovery
Once in twrp, flash pie img first "boot partition"
Then magisk zip and well-being If you want app timer/dashboard
Reboot device
(When rebooting, press "do not install" twrp as system app)
Contains latest ph1 update boot img and latest twrp.
https://drive.google.com/file/d/1R8wMO2ELfOsjRXYfPP6_100J6OCmRshd/view
When installing Magisk zip, Sideload it.
manr1mg said:
Click on link, Download essentials zip
Reboot to bootloader
Flash twp img
Boot to recovery
Once in twrp, flash pie img first "boot partition"
Then magisk zip and well-being If you want app timer/dashboard
Reboot device
(When rebooting, press "do not install" twrp as system app)
Contains latest ph1 update boot img and latest twrp.
https://drive.google.com/file/d/1R8wMO2ELfOsjRXYfPP6_100J6OCmRshd/view
Click to expand...
Click to collapse
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
eric672913 said:
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
Click to expand...
Click to collapse
Im sorry for the inconveniences but for some reason when installing Magisk, I had to Sideload it. I'll see how come but for now just Sideload Magisk after you flash boot img, that should do the trick.
After you flash twrp, go into twrp, install boot.img, MAYBE make sure system is mounted THEN install magisk. I've read some of the red errors happen regardless so I'd just fire up the phone afterwords and see if it works.
eric672913 said:
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
Click to expand...
Click to collapse
you are flashing the boot image as system image and not as boot. I made that mistake too. Im pretty sure your phone doesnt boot to system after flashing magisk correct? Flash stock image again, go to twrp and when flashing boot image make sure you flash it to boot, not system.
luisoman2000 said:
you are flashing the boot image as system image and not as boot. I made that mistake too. Im pretty sure your phone doesnt boot to system after flashing magisk correct? Flash stock image again, go to twrp and when flashing boot image make sure you flash it to boot, not system.
Click to expand...
Click to collapse
Thanks for your reply. I am sure that I check "boot" when flashing stock img. Now I had try the following two ways:
1. when get into TWRP, I mount system first. and then install stock img, and then magisk. there's no error.
2. using sideload, fist sideload magisk, and reboot to bootloader , and then flash stock img, there's no error.
when I restart phone. No magisk apk installed. quite werid. Need your help.
manr1mg said:
Im sorry for the inconveniences but for some reason when installing Magisk, I had to Sideload it. I'll see how come but for now just Sideload Magisk after you flash boot img, that should do the trick.
Click to expand...
Click to collapse
Now I had try the following two ways:
1. when get into TWRP, I mount system first. and then install stock img, and then magisk. there's no error.
2. using sideload, fist sideload magisk, and reboot to bootloader , and then flash stock img, there's no error.
when I restart phone. No magisk apk installed. quite werid. Need your help.:fingers-crossed:
Painful thread to read.

What is the proper way to update stock 6t after rooting?

This is my first oneplus and non-carrier device and I'm unsure of whether to accept this OTA update. I'm pretty sure I would lose root, maybe twrp but stay unlocked? My concern is having to wipe device again. Without an SD card I'd have to transfer a lot of stuff back and forth.
I read that I could just flash magisk from TWRP after installing an OTA update. I took the update and now my phone thinks I just installed the OS for the first time and TWRP is gone. So.... don't do that.
I am SO frustrated. I should have read more posts.
Bubba Fett said:
This is my first oneplus and non-carrier device and I'm unsure of whether to accept this OTA update. I'm pretty sure I would lose root, maybe twrp but stay unlocked? My concern is having to wipe device again. Without an SD card I'd have to transfer a lot of stuff back and forth.
Click to expand...
Click to collapse
My method:
Download the TWRP 3.2.3-22 installer zip to your device https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Download the full 1.6 GB ZIP to your device - OnePlus6TOxygen_34_OTA_018_all_1812260723_29c01e732b714cfa.zip
https://forum.xda-developers.com/on...os-9-0-4-ota-oneplus-6t-t3860953/post78026655
Boot into recovery and install TWRP 3.2.3-22 zip
Reboot Recovery
Backup (see next post)
Install the full 1.6 GB download
Install TWRP 3.2.3-22 zip again
Reboot Recovery
Flash Magisk-v18.0.zip
Reboot System
Sent from my crosshatch using XDA Labs
Follow the guide here: Link
If you have TWRP, and are rooted:
- Download the full package from above.
- Boot to TWRP, flash that full ROM package you downloaded.
- Flash the TWRP installer.
- Reboot to recovery. (The ROM installs to the opposite slot, so rebooting to recovery again switches to that slot that you just installed that update to)
- Now that you are in TWRP again install Magisk.
- Reboot to System.
- No data or Apps lost. You will be good to go.
I get it now. Little different than I'm used to. Thanks!
Edit.. Just saw the answer to my question farther into the link. I thought it was for devs. Thanks for not beating me up! ?
valzi said:
I read that I could just flash magisk from TWRP after installing an OTA update. I took the update and now my phone thinks I just installed the OS for the first time and TWRP is gone. So.... don't do that.
I am SO frustrated. I should have read more posts.
Click to expand...
Click to collapse
I did something similar, but just flashed twrp using adb again, like you did the first time. Then flash the twrp installer after. It made twrp stick when you reboot to recovery. Don't forget to flash Magisk again. The link in post 4 is great. wish I would have read it before asking.
It was so much easier on my Oneplus One. I just took OTA updates without doing anything unusual at all. No flashing. I was using a custom rom though. Maybe that's the answer now?
Or maybe I should just unroot and deal with the inconveniences of an unrooted phone.
Well, first of all you want lose your data when you do upgrade through OTA.
If you use magisk, tap uninstall and restore images. Then do OTA update but do not reboot. Clear recent apps and go back to magisk: install it to inactive slot. Then reboot.
You will lose customer recovery though, so if you want it, sideload it again with PC.
geminium said:
Well, first of all you want lose your data when you do upgrade through OTA.
If you use magisk, tap uninstall and restore images. Then do OTA update but do not reboot. Clear recent apps and go back to magisk: install it to inactive slot. Then reboot.
You will lose customer recovery though, so if you want it, sideload it again with PC.
Click to expand...
Click to collapse
What is the advantage to this method?
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
OhioYJ said:
Follow the guide here: Link
If you have TWRP, and are rooted:
- Download the full package from above.
- Boot to TWRP, flash that full ROM package you downloaded.
- Flash the TWRP installer.
- Reboot to recovery. (The ROM installs to the opposite slot, so rebooting to recovery again switches to that slot that you just installed that update to)
- Now that you are in TWRP again install Magisk.
- Reboot to System.
- No data or Apps lost. You will be good to go.
Click to expand...
Click to collapse
If I have TWRP, do I still need to uninstall Magisk, or can I just follow the TWRP guide and skip the Magisk guide?
@valzi I don't remove Magisk when doing the updates. I just reinstall. I always use the TWRP method.
valzi said:
What is the advantage to this method?
Click to expand...
Click to collapse
I've only used this method, the only thing I can think of is, it's just easier. Go into Magisk, click Uninstall, click restore images, don't reboot, do your OTA update, don't reboot after it's done, go back into Magisk, click install, then click install to slot (Or something like that. It'll say after OTA next to it.) All of those steps are done within Android and not recovery. Do note though, I haven't tried it with custom recovery INSTALLED on my device. YMMV
OMGWTFISTHIS said:
I've only used this method, the only thing I can think of is, it's just easier. Go into Magisk, click Uninstall, click restore images, don't reboot, do your OTA update, don't reboot after it's done, go back into Magisk, click install, then click install to slot (Or something like that. It'll say after OTA next to it.) All of those steps are done within Android and not recovery. Do note though, I haven't tried it with custom recovery INSTALLED on my device. YMMV
Click to expand...
Click to collapse
Hmm. That seems a lot more complicated to me if you have to lose your data though.
---------- Post added at 03:04 AM ---------- Previous post was at 02:57 AM ----------
OhioYJ said:
@valzi I don't remove Magisk when doing the updates. I just reinstall. I always use the TWRP method.
Click to expand...
Click to collapse
Thanks for the help!

Magisk Question, about updating the Rom.

Hello there, I was told that to update the rom to the latest os. I am suppose to uninstall magisk, with restore image option. Doing this I am suppose to be able to install the rom and reinstall magisk. Yet when I click on restore image it says my stock backup does not exist. Is there a workaround to get this to work so I can install the latest OTA?
Thanks
Looking all over for a solution to this as well. Hopefully somebody gets back to you!
js2shanks said:
Hello there, I was told that to update the rom to the latest os. I am suppose to uninstall magisk, with restore image option. Doing this I am suppose to be able to install the rom and reinstall magisk. Yet when I click on restore image it says my stock backup does not exist. Is there a workaround to get this to work so I can install the latest OTA?
Thanks
Click to expand...
Click to collapse
Do you have stock boot.img u can flash?
If you flashed a magisk patched boot.img then you won't have a backup.
If you flashed magisk through twrp then it must have been deleted. If so just flash magisk and after boot try the restore option.
Deleted
js2shanks said:
Hello there, I was told that to update the rom to the latest os. I am suppose to uninstall magisk, with restore image option. Doing this I am suppose to be able to install the rom and reinstall magisk. Yet when I click on restore image it says my stock backup does not exist. Is there a workaround to get this to work so I can install the latest OTA?
Thanks
Click to expand...
Click to collapse
You probably didn't install root with magisk, so you don't have a backup img.
Install OTA then root again using fastboot to boot temporary on TWRP then flash magisk zip installer. This way you'll have the backup boot.img created for next time
Striatum_bdr said:
You probably didn't install root with magisk, so you don't have a backup img.
Install OTA then root again using fastboot to boot temporary on TWRP then flash magisk zip installer. This way you'll have the backup boot.img created for next time
Click to expand...
Click to collapse
That's what I ended up doing as well. Except I just decided to keep TWRP.
In case anyone doesn't know how to do this..
Booting temporarily into TWRP:
Enter fastboot on your phone
Open command prompt on PC
Type in fastboot boot twrpname.img
That boots you into TWRP. Then flash the OTA.zip, then optionally flash TWRP.zip to keep TWRP on your recovery you have to reboot to to recovery once. Then you can flash the magisk.zip and this will create a stock backup image.
But you can skip flashing TWRP.zip and just do ota.zip then flash magisk.zip, this will still create your stock backup images but not keep TWRP as your recovery.
GuestK00179 said:
That's what I ended up doing as well. Except I just decided to keep TWRP.
In case anyone doesn't know how to do this..
Booting temporarily into TWRP:
Enter fastboot on your phone
Open command prompt on PC
Type in fastboot boot twrpname.img
That boots you into TWRP. Then flash the OTA.zip, then ...
Click to expand...
Click to collapse
No, the fastboot boot command didn't boot to anywhere. I got stuck on LG Logo.
And how am I supposed to flash OTA.zip from TWRP (provided you give me an answer to the problem above)? Is the OTA.zip on any location I can browse with TWRP?
All I want to do is to OTA from v20b to v20c on my rooted device, without losing data and reinstalling everything. So I don't mind needing to re-root, and I don't mind installing TWRP if needed, but hell, this should be easier, it's less than 180Mb update!!!!!
I have magisk but no backup image, and I don't have TWRP, and never succeeded installing it, not even temporarily. I do have access to what should be the stock and magisk images from a Google Drive fellow, but I don't know what to flash, when, how, etc. All tutorials I've googled are useless, and the ones here in xda assumes many things that are NOT obvious to me.
Thanks
---------- Post added at 09:30 PM ---------- Previous post was at 09:24 PM ----------
alangt said:
No, the fastboot boot command didn't boot to anywhere. I got stuck on LG Logo.
And how am I supposed to flash OTA.zip from TWRP (provided you give me an answer to the problem above)? Is the OTA.zip on any location I can browse with TWRP?
All I want to do is to OTA from v20b to v20c on my rooted device, without losing data and reinstalling everything. So I don't mind needing to re-root, and I don't mind installing TWRP if needed, but hell, this should be easier, it's less than 180Mb update!!!!!
I have magisk but no backup image, and I don't have TWRP, and never succeeded installing it, not even temporarily. I do have access to what should be the stock and magisk images from a Google Drive fellow, but I don't know what to flash, when, how, etc. All tutorials I've googled are useless, and the ones here in xda assumes many things that are NOT obvious to me.
Thanks
Click to expand...
Click to collapse
I'm terribly sorry, don't mind my post. I'm on the wrong phone thread (seems to be the only thread that says about the magisk wihout backup).
So sorry!
---------- Post added at 09:30 PM ---------- Previous post was at 09:30 PM ----------
alangt said:
No, the fastboot boot command didn't boot to anywhere. I got stuck on LG Logo.
And how am I supposed to flash OTA.zip from TWRP (provided you give me an answer to the problem above)? Is the OTA.zip on any location I can browse with TWRP?
All I want to do is to OTA from v20b to v20c on my rooted device, without losing data and reinstalling everything. So I don't mind needing to re-root, and I don't mind installing TWRP if needed, but hell, this should be easier, it's less than 180Mb update!!!!!
I have magisk but no backup image, and I don't have TWRP, and never succeeded installing it, not even temporarily. I do have access to what should be the stock and magisk images from a Google Drive fellow, but I don't know what to flash, when, how, etc. All tutorials I've googled are useless, and the ones here in xda assumes many things that are NOT obvious to me.
Thanks
Click to expand...
Click to collapse
I'm terribly sorry, don't mind my post. I'm on the wrong phone thread (seems to be the only thread that says about the magisk wihout backup).
So sorry!

Categories

Resources