Related
Since the May Security Update, there have been changes.
I won't get into that here, as there are already a number of threads where the new AVB process and what it means for updates and root is discussed at length on this forum.
For example - https://forum.xda-developers.com/an...-boot-images-android-verified-t3600606/page16
I'm just going to outline my process for installing the new security updates via full image (Not OTA) and then rooting the phone via TWRP.
A few things to bear in mind first.
You will need to have the following:
0. Know how to use ADB/Fastboot and have them installed. If not, you should please do some research first.
1. Full Image for Pixel (https://developers.google.com/android/ota)
2. TWRP boot image and zip files (https://dl.twrp.me/sailfish/)
3. Latest SuperSU by Chainfire (https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip)
4. VerifiedBootSigner by Chainfire (https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606)
Also...I don't make use of the vendor provided flashing scripts, I simply use the script commands and eliminate the '-w' flag manually.
*The SuperSu, TWRP and VerifiedBootSigner zips need to be saved to your phone*
From the bootloader ->
fastboot flash bootloader bootloader-sailfish-8996-012001-1704121145.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot update image-sailfish-njh47b.zip
***The phone will automatically reboot at this phase and you will need to reboot back into the bootloader to continue either by manual means or by using "adb reboot-bootoader"
fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
from TWRP (using files saved on phone) ->
TWRP install twrp-pixel-installer-sailfish-3.1.0-0RC2.zip
reboot TWRP
TWRP install SR3-SuperSU-v2.79-SR3-20170114223742.zip
TWRP install VerifiedBootSigner-v8.zip
reboot system
Edit - You should also update your SuperSU binary to 2.82 from within the app once you're booted into Android.
You're Done!
DISCLAIMER
I didn't create any of these files or take credit for them in anyway. This is simply an instructional that I hope will help many of you.
It requires some proficiency in using fastboot and TWRP.
If you don't know what you're doing and mess up your device, I take no responsibility for your actions or the results.
gonna give it a try, thanks dude.
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
churchmice said:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
Click to expand...
Click to collapse
You're right.
I should update the instructions about that.
The reboot isn't really an issue, but it does add an additional step and some inconvenience.
churchmice said:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
Click to expand...
Click to collapse
phonepersonality said:
You're right.
I should update the instructions about that.
The reboot isn't really an issue, but it does add an additional step and some inconvenience.
Click to expand...
Click to collapse
fastboot has an option to skip reboot:
--skip-reboot
so the command would be something like: fastboot --skip-reboot update image-sailfish-njh47b.zip
Can't we just use ota? Like:
- sideload ota
- let reboot
- reboot bootloader
- boot twrp rc1
- flash twrp rc1
- flash bootloader signer
- reboot recovery
- flash root
- optional kernel
- flash bootloader signer
- reboot
I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know
TENN3R said:
Can't we just use ota? Like:
- sideload ota
- let reboot
- reboot bootloader
- boot twrp rc1
- flash twrp rc1
- flash bootloader signer
- reboot recovery
- flash root
- optional kernel
- flash bootloader signer
- reboot
I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know
Click to expand...
Click to collapse
If you'd like.
I don't like to use the OTA files, personally.
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
mikeprius said:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
Click to expand...
Click to collapse
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.
Tulsadiver said:
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.
Click to expand...
Click to collapse
I did manual fastboot commands earlier, not the autoscript, automatically wiped my data.
---------- Post added at 05:43 PM ---------- Previous post was at 05:31 PM ----------
Not sure what happened. Just pretty much treated like a dirty flash and fastboot flash the image. It must have detected the prior and wiped it. Had the thing rooted which is the only thing I can think of, it was not untouched stock.
mikeprius said:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
Click to expand...
Click to collapse
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.
Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.
Did anyone else have to install the TWRP 3.1 zip via USB-OTG? After flashing the full factory image for June 2017, rebooting to system, rebooting to bootloader then running fastboot boot twrp3.0.2-RC1.img, I wasn't prompted to enter my password so my user data remained encrypted and I couldn't install the TWRP 3.1 zip from the internal SD card, had to load it on a usb dongle and mount USB-OTG storage.
TENN3R said:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.
Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.
Click to expand...
Click to collapse
I've tried to take out the -w erase flag. I've also tried to reflash the stock boot in the past when reloading a new kernel. Not sure if it is triggering some kind of system default but it just auto wipes. It's not the end of the world, I have everything backed up, I just have to restore everything. Just have not had any luck
Guys I can confirm also sideload ota method works flawlessly, 7.1.2 june rooted
Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?
Coronado is dead said:
Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?
Click to expand...
Click to collapse
A phone setup according to this thread is not expected to pass the Safetynet check. I've been updating with SuperSU using FlashFire, and my phone just shows Netflix VR in the Play Store. The Magisk discussions are primarily the threads that have been active recently for having root and passing Safetynet.
Pixel discussion:
https://forum.xda-developers.com/pixel/how-to/magisk-pixel-t3573845
Pixel XL discussion:
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
TENN3R said:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp.
Click to expand...
Click to collapse
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.
My current steps are:
1) adb reboot recovery
2) adb sideload ota-update.zip
3 Reboot and check if everything is okay (root and TWRP are lost, data are not)
4) adb reboot bootloader
5) fastboot boot TWRP.img
6) Flash TWRP and SuperSU
7) Flash boot signer
8) Reboot
Flitskikker said:
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.
My current steps are:
1) adb reboot recovery
2) adb sideload ota-update.zip
3 Reboot and check if everything is okay (root and TWRP are lost, data are not)
4) adb reboot bootloader
5) fastboot boot TWRP.img
6) Flash TWRP and SuperSU
7) Flash boot signer
8) Reboot
Click to expand...
Click to collapse
I use the same method I don't think there are any others
TENN3R said:
I use the same method I don't think there are any others
Click to expand...
Click to collapse
Thanks for confirming.
Does this VerifiedBootSigner-v8.zip apply to the August security patch as well?
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.
I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?
+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)
+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...
+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?
GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?
GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good:
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.
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!