How to root:
You have two options for this, 1 is the recommended way and 2 is the lazy but works way.
Option 1 (RECOMMENDED):
Download the latest factory image from: https://developers.google.com/android/images#cheetah (at the time of writing this, it's TD1A.220804.031
Unlock bootloader (If you don't know how to do this, do not proceed further)
From the downloaded image file, extract the init_boot.img file and copy it to your phone (directory shouldn't matter)
Install the Magisk apk from: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
Launch the app, select install, patch a file, select the init_boot file you placed in your phone
After it's done, it should place a file in your phone's download folder called magisk_patched-<VERSION>_<XYXYXYXYXY>.img
Copy that over to your PC and now boot to bootloader
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Option 2 (LAZY BUT WORKS):
I'm sharing my magisk patched init_boot from the TD1A.220804.031 build (post 73MB update). Instructions are:
Unlock bootloader (If you don't know how to do this, do not proceed further)
Boot to bootloader
Download the patched init_boot from: https://sourceforge.net/projects/ag.../magisk_init_patched-25205_EfWOu.img/download
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Install Magisk apk from here: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
To get SafteyNet working:
Open the Magisk app
Open the settings from top right, Enable Zygisk
Reboot
Flash the MODIFIED SafteyNet fix module by @kdrag0n from the attached files on this thread from within Magisk Modules
Clear Play store data and you should be good!
Voila!
FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!
VERIFY THE MD5 OF THE FILE AFTER DOWNLOADING!!!!!!!
Mirror 1 | Mirror 2
MD5: 43613f520697722840ded6a15eb27459
Massive shoutout to @Some_Random_Username for Mirror 1 and @akhilnarang for Mirror 2 since SourceForge was facing issues!
Now documentation on how to do it yourself (which I'd highly recommend since you should never trust any file given, always try to do it yourself!):
How to dump your own device:
1. Download a GSI which is userdebug/eng and equal/newer Security Patch of the current build on your device from any of the unofficial community builds here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
2. Install the DSU Sideloader app from: https://github.com/VegaBobo/DSU-Sideloader/releases/latest
3. Follow instructions in the DSU sideloader app readme here: https://github.com/VegaBobo/DSU-Sideloader/blob/master/README.md
I'd recommend enabling the userdata toggle and typing 32GB as the size
4. Reboot into the DSU from the notification
5. When the device boots up, type the following in the terminal:
Code:
adb root
adb shell
mkdir -p /sdcard/dump
for file in /dev/block/bootdevice/by-name/*; do
if [ "${file##*/}" != "userdata" ]
then
echo Dumping "${file##*/}"
dd if=$file of=/sdcard/dump/"${file##*/}".img
fi
done
6. Once the dump is done, you'll have files in /sdcard/dump/
7. Copy those over to a PC
8. Voila
A massive thanks to @AndyYan @Some_Random_Username for their help (well hand holding) throughout the entire process <3
Also thanks to @OmkarTheAndroid for the re-brush up of the Android basics I forgot
Reserved
Thanks!
Have you had any luck with SafetyNet yet? People on another thread are saying that even the Modded version by @Displax isn't working on P7P with Canary Magisk
I'd like to remind all that, 1) the DSU method requires some Android/shell knowledge to correctly carry out, and 2) you're discouraged from actually flashing/using those GSIs (TD-based Android 13 GSIs are still in early phase, and P7/P will almost certainly get proper, fully functional device-specific ROMs shortly anyway).
Thanks for the dump! Could you maybe mirror it yourself to be sure? At least until Google's facory images are up Sourceforge is incredibly slow for me (and probably for others too).
so looks like vendor_dlkm has been replaced by vendor_kernel_boot and the init_boot is just the first-stage init. This will be interesting moving forward with AVB and custom images. I will start working on something when source drops. I will likely need to have some testers to see how much this requires to get a custom image up and running.
EDIT: vendor_boot is actually the one that has been separated out a bit between vendor_boot (holding modules) and vendor_kernel_boot, which has some ramdisk stuff like the vendor_boot has on Pixel 6 devices.
Kernel now consists of 6 images. init_boot, vendor_boot, vendor_kernel_boot, vendor_dlkm, dtbo and boot.img
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
mrteii1 said:
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
Click to expand...
Click to collapse
this is a soft brick, just flash the correct partition back using the stock image
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
whatsisnametake2 said:
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
Click to expand...
Click to collapse
Yes, unlocking the bootloader is still the same and will wipe data.
Current SafetyNet Status (with modded universal SafetyNet Fix + Magisk Props):
Play Integrity API Checker:
MEETS_DEVICE_INTEGRITY: fail
MEETS_BASIC_INTEGRITY: pass
MEETS_STRONG_INTEGRITY: fail
YASNAC:
Basic integrity: pass
CTS profile match: fail
Edit: GPay does work on the Pixel Watch, even though it doesn't on the phone (when rooted).
Make sure to add your cards there if you're using the Pixel Watch and can't use GPay on your phone.
zetsumeikuro said:
Yes, unlocking the bootloader is still the same and will wipe data.
Click to expand...
Click to collapse
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
mrteii1 said:
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
Click to expand...
Click to collapse
In the OP, the part with:
"FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!"
Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
Maybe you replied to the wrong user?
Hey everyone, a slight update on the website for the image dump, SourceForge was giving people incomplete files so @Some_Random_Username is generously hosting it on his servers <3
please verify the MD5 of the downloaded zip before trying to modify any parititons using the following commands:
On windows:
Code:
certutil -hashfile cheetah-TD1A.220804.031-compressed.zip MD5
On Linux/MacOS:
Code:
md5sum cheetah-TD1A.220804.031-compressed.zip
The MD5 should be: 43613f520697722840ded6a15eb27459
whatsisnametake2 said:
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Click to expand...
Click to collapse
I was thinking the reset would force it to boot off the other slot.
Related
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this procedure before doing it! YOU are choosing to make these modifications.
Click to expand...
Click to collapse
OP6 rooting without TWRP
Checklist before preceed:
Working Fastboot
Be on software OOS 5.1.5 | 5.1.6 | 5.1.7 | 5.1.8
Unlocked bootloader (Instruction here, but remember to enable OEM Unlocking first)
Funk Wizard said:
Enable OEM Unlocking
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also make sure that from now on, OEM unlocking option is enabled before you reboot as sometimes, it might get disabled itself.
Click to expand...
Click to collapse
WARNING:
Please double check that you have unlocked bootloader!
A few users has reported that instaling magisk with locked bootloader or wiping phone (using stock recovery) with patched boot.img can soft brick your phone! Please avoid doing this for now. If you've already done this and you are stuck with only fastboot working please follow this post https://forum.xda-developers.com/showpost.php?p=76608874&postcount=31 to restore your device to working state. Thank's to @SaiBork for more detailed instructions available here https://forum.xda-developers.com/showpost.php?p=76632484&postcount=82
Rooting process:
Make sure that you have UNLOCKED BOOTLOADER. DO NOT attempt to patch boot.img using Magisk Manager without unlocked bootloader because it WILL CAUSE SOFT BRICK!!!
Boot device using patched boot.img.
For OOS 5.1.5 it can be downloaded [here]
For OOS 5.1.6 it can be downloaded [here]
For OOS 5.1.7 it can be downloaded [here]
For OOS 5.1.8 it can be downloaded [here]
It can be also patched manually (see bottom of this post).
To do this you need working fastboot. Fire up your cmd/terminal and cd to directory where you've downloaded/placed patched boot image. When you are in correct directory just type in cmd/terminal:
Code:
fastboot boot patched_boot_magisk1642_518.img
(check if img filename in command is exactly same as name of downloaded boot img) The phone should boot to Android.
Once the phone has booted install Magisk Manager app and open it. It can be downloaded here or here.
Magisk Manager App should show that your phone is rooted - but at this stage it's just temporary, until next reboot (nothing flashed yet).
Go to settings and Tap on "Update channel" and change it to Beta.
Go back to Magisk main screen and make sure that "Preserve force encryption" and "Preserve AVB 2.0/dm-verity" are checked!
Tap on "Install" and select "Direct Install (Recommended)".
Wait until boot.img is patched and flashed and reboot your device when prompted to do so.
After boot there aren't any error messages shown before (or after) entering PIN code, unlike when rooting using other methods.
To check SafetyNet status just open Magisk Manager once again and tap on "Tap to start SafetyNet check". It should be all green.
wOOt wOOt you just got rOOt!
Video showing rooting process:
XDA user @GizmoFreak has made a video showing the whole procedure for 5.1.5! Thank you very much.
How to do an OTA update preserving root
Install OTA. It will be installed on the inactive slot. Do not restart your OP6 when installation finishes.
Start Magisk Manager app.
Tap on Install.
Tap on Install to Second Slot (After OTA).
Reboot your device.
Check if you got root and if safety net checks are passed.
How to extract from OTA and manually patch stock OOS boot.img using Magisk Manager:
Install python3 and PIP manager on your system .
Use pip to install "protobuf" module:
Code:
pip3 install protobuf
Download payload_dumper.py and update_metadata_pb2.py from this gist https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15 and save them in one directory.
Download full update zip with OOS (containing payload.bin). It can be downloaded from this great thread by @Titokhan
Extract payload.bin from update zip to same directory where payload_dumper.py is located.
Use payload_dumper.py to extract original boot.img
Code:
python payload_dumper.py payload.bin
After a while you should have all img's included in payload.bin dumped in your working directory.
Install Magisk Manager app on your OP6.
Place that dumped boot.img on your phone storage.
In Magisk Manager app tap install, and select "Patching boot image file". Select boot.img that you've just uploaded to your phone.
Magisk Manager will patch boot.img and save it on Phone's internal storage in "MagiskManager" directory (file called "patched_boot.img").
Download this patched file to your computer and just use it to boot using fastboot
stock recovery img please
Hi and thx for the Thread. Maybe more Details in your Guide would be nice and you dont lose you Void by OnePlus if you Root you Device only if u break the hardware with you root access (Like changing the CPU rate in the Kernel).
NeoNecOP6 said:
Hi and thx for the Thread. Maybe more Details in your Guide would be nice and you dont lose you Void by OnePlus if you Root you Device only if u break the hardware with you root access (Like changing the CPU rate in the Kernel).
Click to expand...
Click to collapse
How do they know if you manipulate the CPU frequency?
Thanks, I'd like to try patching the boot.img myself - how did you extract it from the device without root?
I also couldn't figure out how to extract it from the update files OP provided (since they are all A/B updates only containing a payload.bin)
liver20 said:
stock recovery img please
Click to expand...
Click to collapse
There is no separate recovery partition. Recovery in boot.img, as all A/B devices.
NeoNecOP6 said:
and you dont lose you Void by OnePlus if you Root you Device only if u break the hardware with you root access (Like changing the CPU rate in the Kernel).
Click to expand...
Click to collapse
I know but it's just a disclaimer
Kaeltis said:
Thanks, I'd like to try patching the boot.img myself - how did you extract it from the device without root?
I also couldn't figure out how to extract it from the update files OP provided (since they are all A/B updates only containing a payload.bin)
Click to expand...
Click to collapse
You can extract it from A/B update using python tool called payload_dumper.py Check this post for more information https://forum.xda-developers.com/showpost.php?p=76598704&postcount=80
jacdelad said:
How do they know if you manipulate the CPU frequency?
Click to expand...
Click to collapse
if that's why your smartphone broke down. Any company can find out if the device has been rooted.
http://tinypic.com/view.php?pic=2dquejq&s=9
Rooted
Thanks op
This worked perfectly for me. No vendor image issues either. No flashing (that's cool!). Thanks! I saw you posted how you did it but it'd be cool if you could add it to this thread so people can learn.
Thanks!
b1czu said:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about this procedure before doing it! YOU are choosing to make these modifications.
For all interested in rooting I suggest to do it this way:
Checklist before preceed:
- Working Fastboot
- Unlocked bootloader
- Be on software OSS 5.1.5!!
1. Boot patched boot.img that can be downloaded here [https://drive.google.com/open?id=1BIH5sGfMADfhWIAfQDsiw4f-UI_1WvqX]
To do this you need working fastboot and cd to directory where you've downloaded patched boot image. When you are in correct directory just type in cmd/terminal:
Code:
fastboot boot patched_boot_magisk1642.img
The phone should boot to Android.
2. Once phone is booted up install Magisk Manager and open it.
3. It should show that you have root - but at this stage it's just temporary, until next reboot (nothing flashed yet).
4. Go to settings and Tap on "Update channel" and change it to Beta.
5. Go back to Magisk main screen and make sure that "Preserve force encrypotion" and "Preserve AVB 2.0/dm-verity" are checked!
6. Tap on "Install" and select "Direct Install (Recommended)"
6. Reboot
After boot there are no any Error messages before entering PIN code.
Just open magisk manager once again and tap on "Tap to start SafetyNet check". It should be all green.
wOOt wOOt you just got rOOt!
Click to expand...
Click to collapse
Thanks for this. Probably a dumb question. But, does this need to be undone when TWRP comes out? Is there a way to revert back?
Thanks again.
mcdavid said:
But, does this need to be undone when TWRP comes out?
Click to expand...
Click to collapse
No, you don't need to undone this. Flashing magisk root using TWRP recovery would lead to same end-effect.
mcdavid said:
Is there a way to revert back?
Click to expand...
Click to collapse
Yes. You can flash back stock OOS 5.1.5's boot.img, because nothing other was modified. Link to download STOCK boot.img for OOS 5.1.5 https://drive.google.com/open?id=1RPQZj6HQxNNdJiMrAjtkxncH3PLBTZp_
To revert you need fastboot tool:
Code:
fastboot flash boot boot.img
And that's it. You're again rootles on stock 5.1.5's boot.img.
thanks man!!!
Op6 rooted and ready for me!
OnePlus 3: TWRP, Root & Cyanogenmod before most users got the device,
OnePlus 5: Unofficial TWRP,
And OnePlus 6: Root without any custom recovery....
Thank you!
Wow thank you for this, can't live without root and I get my OP6 tomorrow so this is great
i installed patched boot file for oss5.1.3 using boot file for oss5.1.3. my question is when i update oss to latest for now i.e oss5.1.5 will i need to re root it? or it will stay rooted? and i won't get stuck at installing the update too right? considering its gonna be full updates now(no partial updates).
dynamic_4444 said:
i installed patched boot file for oss5.1.3 using boot file for oss5.1.3. my question is when i update oss to latest for now i.e oss5.1.5 will i need to re root it? or it will stay rooted? and i won't get stuck at installing the update too right? considering its gonna be full updates now(no partial updates).
Click to expand...
Click to collapse
When you update, boot.img will be overwritten with 5.1.5's one and you'll have to repeat the process again.
@b1czu, thank you very much! Rooted flawlessly .
Worked like a charm! I'm grateful for my fellow impatient people. Time to unlock the Oneplus 6's true potential!
I try it to night
Thanks man, so far it works great!
This guide lets you install any GSI treble roms on our Daisy.
Read carefully and go step by step!
Update: Since Havoc OS doesn´t need permissive Kernel, I just installed the latest stock rom (9.6.9.0), flashed Havoc, set everything up and ended with sh...t... Camera´s not working, Opera freezes, everything sucks. It was a waste of time... So it´s still the situation:
If you want to use a custom GSI-Rom Only use this combination: Stock rom before flashing GSI: 9.6.4.0 and Kernel: Unofficial TWRP by Yshalsager - this combination works like a charm
Let´s get started: Be sure you are on Stock 9.6.4.0 (july security patch) if not, your wifi will not work in treble rom!
1) Download latest AB arm 64 gsi build. - ONLY ARM 64 AB GSI WILL WORK!
2) If you don´t have fastboot and adb download it from here: https://forum.xda-developers.com/sho....php?t=2588979 and install it!
3) Extract gsi64-ab-image to adb folder and rename it to system.img
4.a) Windows 7: right klick on white space in your adb-folder: open command prompt here
4.b) Windows 10: open command prompt as admin and navigate to your adb folder
5.) Power off your Smartphone and press pwr and vol- together -> your screen will show FASTBOOT - connect your phone to your PC
6.) type in your command prompt
Code:
fastboot oem unlock
Important: this will format your SD - All data will be lost If you perform that step! -> Backup before!7.) Phone will reboot, erase data and boot up. Power off again after boot up. Power + vol- to enter fastboot.
Now you have to decide: If you want to use Android 9 roms and TWRP together, you have to decrypt your data - else TWRP will not be able to read data! If you don´t care continue on step 11
8.) Download a patched_boot.img and place it in your fastboot folder - since only 9.6.4.0 works without bugs, you have to choose the patched 9.6.4.0 boot
9)
Code:
fastboot boot patched_boot.img
10) Connect to internet and update Magisk manager, download a root explorer - you could use this and go to
/vendor/etc/ and open the file fstab.qcom in editorreplace the text "forceencryption=footer with "encryptable=footer" and reboot to bootloader
11) Download this, rename it to boot.img and copy it to your fastboot folder
Code:
fastboot flash boot boot.img
12) Install official TWRP
13) After installing official TWRP reboot to TWRP agian and go to "wipe" -> "format data" and type "yes". Reboot to bootloader
14.) Download your GSI AB Image and place it in your fastboot folder
Code:
fastboot flash system [imagename].img
If you want, you can boot now to twrp and install magisk and/or gapps whatever - everything will work. Else you boot up your new system - Sometimes your GSI-rom will not boot up without a rooted kernel.
So if you stay in bootloop, just install magisk.zip!
Violla - Now you have a treble gsi rom on your Mi A2 Lite!
theres working twrp out for daisy, does this change anything refering to your first line:
"1) Download latest AB arm 64 gsi build. I would always use the gappsed version - twrp still not running for daisy... - ONLY ARM 64 AB GSI WILL WORK!"
thanks for the guide!
i really want to try this but im not sure which rom fully works. Also i'm not sure to do this without TWRP cause i'd like to have a complete backup of my device.
i'm in 9.6.9 version now with locked bootloader and unrooted
any suggests for me to try this rom
tutankpusch said:
theres working twrp out for daisy, does this change anything refering to your first line:
"1) Download latest AB arm 64 gsi build. I would always use the gappsed version - twrp still not running for daisy... - ONLY ARM 64 AB GSI WILL WORK!"
Click to expand...
Click to collapse
Updated: I removed that line...
merlin.berlin said:
thanks for the guide!
i really want to try this but im not sure which rom fully works. Also i'm not sure to do this without TWRP cause i'd like to have a complete backup of my device.
Click to expand...
Click to collapse
No problem - meanwhile there´s a official twrp here - and you can still use this guide
If you want to flash havoc 2.0 - I think it´s the best rom on earth , you will need to change your kernel to permissive that it will boot. To do that, read the thread there´s a vivid discussion how to do it...
elkhshap said:
i'm in 9.6.9 version now with locked bootloader and unrooted
any suggests for me to try this rom
Click to expand...
Click to collapse
If you like to have more features and/or pie (Android 9), then I would suggest to flash a custom gsi rom. If you can live with stock, I wouldn´t touch it.
Voodoojonny said:
No problem - meanwhile there´s a official twrp here - and you can still use this guide
If you want to flash havoc 2.0 - I think it´s the best rom on earth , you will need to change your kernel to permissive that it will boot. To do that, read the thread there´s a vivid discussion how to do it...
Click to expand...
Click to collapse
i want havoc OS but as i understand i can't use the fastboot method because i need the permissive fix, which only can be installed via TWRP, correct?
i would prefer fastboot over TWRP because all the problems with sdcard reading, encrypting etc.
merlin.berlin said:
i want havoc OS but as i understand i can't use the fastboot method because i need the permissive fix, which only can be installed via TWRP, correct?
i would prefer fastboot over TWRP because all the problems with sdcard reading, encrypting etc.
Click to expand...
Click to collapse
Hi,
there are so many reasons for havoc not to boot... and so less to boot...
BUT... If you won´t mind to use an unencrypted phone or no twrp, you can use (as I think) the best Android OS, havoc.
So think about, what is more important for you: TWRP or encryption.
1. With encryption: (Quite easy)
a) Go to stock 9.6.4.0 - July patch with mi flash and choose clean all (yes you will loose all your data -> back up everything) - Important: don´t install any ota after that!b) Download latest havoc and place it in your fastboot folderc) Download this TWRP and place it in your fastboot folder - you need this as Kerneld) As lazy person, I would rename the havoc file to havoc.img and the twrp file to twrp.imge) copy userdata.bin from stock to fastboot
Code:
fastboot flash system havoc.img
Code:
fastboot flash boot twrp.img
Code:
fastboot flash userdata userdata.bin
Code:
fastboot reboot
Wait and wait and wait and violla, you have havoc!
f) Gapps: download gapps, copy it to your fastboot folder and rename it to gapps.zip. Boot to recovery - twrp will not be able to read your data -> skip and allow modifications
Code:
adb push ./gapps.zip /sdcard
- Now you see gapps in your zip and you can install it!
g) Magisk: for magisk you need to download my patched twrp and place it in your fastboot folder
Code:
fastboot boot patched_twrp.img
- After booting up, you can go to magisk manager (yes: upgrade first etc.... and install magisk using the "direct method"
2. If you want to remove encryption - then you can use twrp fully, use this guide: here
Important: If you use another stock rom than 9.6.4.0 or do an ota, you will loose wifi!after doing all the steps:
Code:
fastboot flash system havoc.img
- that´s it!
Now you can use havoc
Voodoojonny said:
Hi,
there are so many reasons for havoc not to boot... and so less to boot...
BUT... If you won´t mind to use an unencrypted phone or no twrp, you can use (as I think) the best Android OS, havoc.
So think about, what is more important for you: TWRP or encryption.
1. With encryption: (Quite easy)
a) Go to stock 9.6.4.0 - July patch with mi flash and choose clean all (yes you will loose all your data -> back up everything) - Important: don´t install any ota after that!b) Download latest havoc and place it in your fastboot folderc) Download this TWRP and place it in your fastboot folder - you need this as Kerneld) As lazy person, I would rename the havoc file to havoc.img and the twrp file to twrp.imge) copy userdata.bin from stock to fastboot
Code:
fastboot flash system havoc.img
Code:
fastboot flash boot twrp.img
Code:
fastboot flash userdata userdata.bin
Code:
fastboot reboot
Wait and wait and wait and violla, you have havoc!
f) Gapps: download gapps, copy it to your fastboot folder and rename it to gapps.zip. Boot to recovery - twrp will not be able to read your data -> skip and allow modifications
Code:
adb push ./gapps.zip /sdcard
- Now you see gapps in your zip and you can install it!
g) Magisk: for magisk you need to download my patched twrp and place it in your fastboot folder
Code:
fastboot boot patched_twrp.img
- After booting up, you can go to magisk manager (yes: upgrade first etc.... and install magisk using the "direct method"
2. If you want to remove encryption - then you can use twrp fully, use this guide: here
Important: If you use another stock rom than 9.6.4.0 or do an ota, you will loose wifi!after doing all the steps:
Code:
fastboot flash system havoc.img
- that´s it!
Now you can use havoc
Click to expand...
Click to collapse
Please explain by video
thank you so much for this guide:good:
i'll try it later when im home:fingers-crossed:
Where do I find a userdata.bin file?
monzer said:
Where do I find a userdata.bin file?
Click to expand...
Click to collapse
In the Images-Folder of your stockrom after extracting...
- download fastboot stock rom
- extract archive
- look inside "images"
update: it´s userdata.img
Voodoojonny said:
In the Images-Folder of your stockrom after extracting...
- download fastboot stock rom
- extract archive
- look inside "images"
update: it´s userdata.img
Click to expand...
Click to collapse
Please post a video for ease of action
monzer said:
Please post a video for ease of action
Click to expand...
Click to collapse
Sorry, that will not happen!
Updated: view first post. This guide will definitely work well - and it´s easy! At least more easy than the other guides .
Voodoojonny said:
Updated: view first post. This guide will definitely work well - and it´s easy! At least more easy than the other guides .
Click to expand...
Click to collapse
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
KezraPlanes said:
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
Click to expand...
Click to collapse
If you would read, you would have noticed, that that broken and untested recovery is used as kernel, becouse it works great as kernel for gsi roms. Within the process it will be upgreaded by official twrp.
I spend a lot time, testing how to install custom roms on this phone, becouse I don't like like stock and I share my experience with others. Noone will break his phone with this! Perhaps you can try before complaining.
KezraPlanes said:
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
Click to expand...
Click to collapse
Voodoojonny said:
If you would read, you would have noticed, that that broken and untested recovery is used as kernel, becouse it works great as kernel for gsi roms. Within the process it will be upgreaded by official twrp.
I spend a lot time, testing how to install custom roms on this phone, becouse I don't like like stock and I share my experience with others. Noone will break his phone with this! Perhaps you can try before complaining.
Click to expand...
Click to collapse
Lol, this site has gone way down hill... It's almost a joke now.
So many people asking for the 'easy' way and want answers to easily searchable questions. Sooo many multiple posts, and people not wanting to do the research themselves. How many threads need to be created on bricked devices because you didn't heed the warnings or follow the directions...
I wonder if xda even cares? This place use to be a great tool for the ones who like to tinker.
There are definitely a few folks keeping the spirit alive, but so many unnecessary posts - like what I'm writing right now...
Anyway thanks to anyone who puts time and effort for the greater good, we should all understand that tinkering with our devices can potentially have adverse effects.
Thanks for this noob friendly guide! a massive thanks! But hotspot still not working. Haven't tried the gcam but the stock camera is working but has no portrait and other features. The havoc os 2.0 looks snappy and buggy. Ill try other treble roms in few days
Any suggestions?
Bokoko006 said:
Thanks for this noob friendly guide! a massive thanks! But hotspot still not working. Haven't tried the gcam but the stock camera is working but has no portrait and other features. The havoc os 2.0 looks snappy and buggy. Ill try other treble roms in few days
Any suggestions?
Click to expand...
Click to collapse
You're welcome. Don't have problems with bugs and havoc 2.0... Interesting to test would be arrow pie! Benzo had problems with camera and flashlight... All the 8.1 can't handle the notch and overlay!
Why This Thread?
I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for anyone who might still be uncertain about "update" procedures, I've followed thie below method twice now with no issues at all,> None of my data was lost and I kept my EX kernel!.
If You Want To Unlock Your Bootloader and Root Your Pixel 5:
This guide takes you step by step through bootloader unlock, using magic to patch the boot image and get your device rooted.
If You're Already Unlocked & Rooted, and Want To Update The Factory Image And Re-Root:
If you're already rooted and want to update to the next factory image, just follow the standard update factory image routine for the Pixel series of devices, then following the below:
After extracting the primary factory zip, and the secondary zip that is created from the first extraction (all done within the platform tools folder with the fastboot app)
Edit the FLASH-ALL file.... keep the -w for a clean install that wipes everything, or remove the -w to keep your data.
This will install the latest factory image and remove root.
Now, follow these steps here, they're perfect. (these are the same instructions for unlocking bootloader, and initial install of Magisk listed above)
If you were previously rooted, and just updating the next factory image, you can skip the entire sections on installing and hiding Magisk manager in the above instructions, (these settings remained in Magisk Manager when I did this).
And you're done!
KNOWN ISSUE:
* * * MagiskHide Props Config IS NO LONGER WORKING * * *
Please follow THIS LINK for the Universal Safetynet Fix that replaces the MagiskHide Props Config process.
If you know an easier, shorter, more efficient, or UPDATED method, please share it and I'll make the necessary corrections/adjustments
My method is updating via the OTA packages. Similar to using the factory image but no editing of files.
Download the factory image for your current software version.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Extract the boot.img from #1
Download the factory image of the version you're updating to.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Download the OTA image for the version you're updating to.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Turn off magisk modules
Apply the boot.img from step #2 (I save this from my previous update so I can skip steps 1 & 2 above.)
adb reboot bootloader
fastboot flash boot "path to boot.img"
fastboot reboot (this is a sanity check to make sure things are normal. The phone should be normal and without root. It can be skipped if you wish, simply use the fastboot menu on the phone and boot to recovery skipping steps 4 & 5.)
Sanity check phone
adb reboot recovery
Once in recovery hold the power button and click volume up
Use the volume keys to highlight "Apply update from ADB"
Click the power button.
On your computer run: adb sideload "path to #4" and wait for it to finish. You'll get status on the adb command and on the phone.
Once finished restart the phone and let it finish the update.
Your phone is now updated but without root.
Extract boot.img from #3 above.
Copy it to the phone
Open magisk manager and patch the boot.img you just copied
Copy the patched boot.img file created by magisk manager back to your computer
Apply this file using fastboot
adb reboot bootloader
fastboot flash boot "path to patched boot.img"
fastboot reboot
Turn on your magisk modules and test
You can now delete 1, 3, & 4. I save #12 for the next update. This eliminates the need for 1 & 2.
You should now have an updated rooted device.
l7777 said:
My method is updating via the OTA packages. Similar to using the factory image but no editing of files.
Download the factory image for your current software version.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Extract the boot.img from #1
Download the factory image of the version you're updating to.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Download the OTA image for the version you're updating to.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Apply the boot.img from step #2 (I save this from my previous update so I can skip steps 1 & 2 above.)
adb reboot bootloader
fastboot flash boot "path to boot.img"
fastboot reboot (this is a sanity check to make sure things are normal. The phone should be normal and without root. It can be skipped if you wish, simply use the fastboot menu on the phone and boot to recovery skipping steps 4 & 5.)
Sanity check phone
adb reboot recovery
Once in recovery hold the power button and click volume up
Use the volume keys to highlight "Apply update from ADB"
Click the power button.
On your computer run: adb sideload "path to #3" and wait for it to finish. You'll get status on the adb command and on the phone.
Once finished restart the phone and let it finish the update.
Your phone is now updated but without root.
Extract boot.img from #2 above.
Copy it to the phone
Open magisk manager and patch the boot.img you just copied
Copy the patched boot.img file created by magisk manager back to your computer
Apply this file using fastboot
adb reboot bootloader
fastboot flash "path to patched boot.img"
fastboot reboot
You can now delete 1, 3, & 4. I save #12 for the next update. This eliminates the need for 1 & 2.
You should now have an updated rooted device.
Click to expand...
Click to collapse
Thank you. Well-written, just a few minor corrections.
Download the factory image for your current software version.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Extract the boot.img from #1
Download the factory image of the version you're updating to.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Download the OTA image for the version you're updating to.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Apply the boot.img from step #2 (I save this from my previous update so I can skip steps 1 & 2 above.)
adb reboot bootloader
fastboot flash boot "path to boot.img"
fastboot reboot (this is a sanity check to make sure things are normal. The phone should be normal and without root. It can be skipped if you wish, simply use the fastboot menu on the phone and boot to recovery skipping steps 4 & 5.)
Sanity check phone
adb reboot recovery
Once in recovery hold the power button and click volume up
Use the volume keys to highlight "Apply update from ADB"
Click the power button.
On your computer run: adb sideload "path to #4" and wait for it to finish. You'll get status on the adb command and on the phone.
Once finished restart the phone and let it finish the update.
Your phone is now updated but without root.
Extract boot.img from #2 above.
Copy it to the phone
Open magisk manager and patch the boot.img you just copied
Copy the patched boot.img file created by magisk manager back to your computer
Apply this file using fastboot
adb reboot bootloader
fastboot flash boot "path to patched boot.img"
fastboot reboot
You can now delete 1, 3, & 4. I save #12 for the next update. This eliminates the need for 1 & 2.
You should now have an updated rooted device.
zeepzorp said:
Thank you. Well-written, just a few minor corrections.
Click to expand...
Click to collapse
Thanks, updated the original.
Thanks for the instructions. I was able to re-root the device, but I couldn't pass SafetyNet Attestation.
My P5 has updated to: 11.0.0 (RQ1A.210105.003, Jan 2021)
I used MagiskHide Props Config (updated) method. which is:
#su
#props
#1 (edit device fingerprint)
#f (Pick a certified finger print)
#7 (google)
#20 (pixel 3a)
#3 (Android version 11)
#y (restart)
The devices rebooted but still, no SafetyNet pass.
hamooz92 said:
Thanks for the instructions. I was able to re-root the device, but I couldn't pass SafetyNet Attestation.
My P5 has updated to: 11.0.0 (RQ1A.210105.003, Jan 2021)
I used MagiskHide Props Config (updated) method. which is:
#su
#props
#1 (edit device fingerprint)
#f (Pick a certified finger print)
#7 (google)
#20 (pixel 3a)
#3 (Android version 11)
#y (restart)
The devices rebooted but still, no SafetyNet pass.
Click to expand...
Click to collapse
Altering the model prop doesn't work for safety net any longer. There is a safetynet-fix magisk module you can use.
l7777 said:
Altering the model prop doesn't work for safety net any longer. There is a safetynet-fix magisk module you can use.
Click to expand...
Click to collapse
I have also flashed Universal SafetyNet Fix but no luck
hamooz92 said:
I have also flashed Universal SafetyNet Fix but no luck
Click to expand...
Click to collapse
I just flashed the safety net fix myself and it worked like a charm.
I also left the magisk config prop module installed (just because)
Are all your other Magisk settings in order (magisk hide, checking all the boxes under GooglePlay , etc.)?
l7777 said:
Download the factory image for your current software version.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Click to expand...
Click to collapse
current build number is RD1A.200810.021.A1
zeepzorp said:
Download the OTA image for the version you're updating to.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Click to expand...
Click to collapse
one the ota site there's only one "EU carrier" images different than the current one: RD1A.201105.003.B1 (NOV 2020). should i use this one or can i also use the this one f.e. RQ2A.210305.006 (nothing specified)
You may find my video helpfu too but it more pertains to installing the DP1 for Android 12, but the update process is practically the same.. For rooting Android 12, it seems we need to disable verity/verification of boot images, otherwise flashing a modified boot img will just boot immediately to fastboot again.
narf0815 said:
current build number is RD1A.200810.021.A1
one the ota site there's only one "EU carrier" images different than the current one: RD1A.201105.003.B1 (NOV 2020). should i use this one or can i also use the this one f.e. RQ2A.210305.006 (nothing specified)
Click to expand...
Click to collapse
In your case yes I'd probably use RQ2A.210305.006.
zeepzorp said:
Thank you. Well-written, just a few minor corrections.
Click to expand...
Click to collapse
l7777 said:
Thanks, updated the original.
Click to expand...
Click to collapse
Thank you, l7777 and zeepzorp. This is also the way I would have done it. Out of curiosity and to reduce manual steps in between, would it work to restore the original boot.img to unroot and then use the normal OTA updates inside Android? Without a spare phone or a TWRP backup I hesitate to try this.
Also, when following the manual update steps, is it safe to skip versions in between, e.g. update directly from January to March versions? In my past 10 years of manually updating ROMs I have never used any OTA update functionality from inside Android and I noticed that the OTA update process, which was performed in mid January 2021 when unpacking the phone, updated the ROM in the following order, each separated by reboots in between:
Shipped version: 11.0.0 (RD1A.200810.021.A1, Oct 2020, EU carriers)
1st OTA update: 11.0.0 (RQ1A.201205.011, Dec 2020, All carriers except AT&T and Verizon)
2nd OTA update and at that time current version: 11.0.0 (RQ1A.210105.003, Jan 2021)
Why did it not skip the version in between and directly update to the January version?
dhrv said:
Thank you, l7777 and zeepzorp. This is also the way I would have done it. Out of curiosity and to reduce manual steps in between, would it work to restore the original boot.img to unroot and then use the normal OTA updates inside Android? Without a spare phone or a TWRP backup I hesitate to try this.
Also, when following the manual update steps, is it safe to skip versions in between, e.g. update directly from January to March versions? In my past 10 years of manually updating ROMs I have never used any OTA update functionality from inside Android and I noticed that the OTA update process, which was performed in mid January 2021 when unpacking the phone, updated the ROM in the following order, each separated by reboots in between:
Shipped version: 11.0.0 (RD1A.200810.021.A1, Oct 2020, EU carriers)
1st OTA update: 11.0.0 (RQ1A.201205.011, Dec 2020, All carriers except AT&T and Verizon)
2nd OTA update and at that time current version: 11.0.0 (RQ1A.210105.003, Jan 2021)
Why did it not skip the version in between and directly update to the January version?
Click to expand...
Click to collapse
As far as skipping monthly updates, I only update every other month (unless there's a massive update for security) and I've had zero issues. Just updated to March from January, no problems.
I'm having a hard time understanding your instructions. I apologize in advance but, could I get a more detailed list of instructions?
philharmon said:
I'm having a hard time understanding your instructions. I apologize in advance but, could I get a more detailed list of instructions?
Click to expand...
Click to collapse
Follow these instructions, they're pretty much step for step.
https://android.gadgethacks.com/how...ide-for-beginners-intermediate-users-0348101/
They're included in my OP (hyperlinked) as well.
If you have a specific question, just ask!
Az Biker said:
Follow these instructions, they're pretty much step for step.
https://android.gadgethacks.com/how...ide-for-beginners-intermediate-users-0348101/
They're included in my OP (hyperlinked) as well.
If you have a specific question, just ask!
Click to expand...
Click to collapse
Be warned, nothing after step 20 in that guide is valid any longer. Passing safetynet requires a different magisk module.
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
l7777 said:
Be warned, nothing after step 20 in that guide is valid any longer. Passing safetynet requires a different magisk module.
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Click to expand...
Click to collapse
Which is why the following warning has been written in the OP since Feb 2021:
KNOWN ISSUE:
* * * MagiskHide Props Config IS NO LONGER WORKING * * *
Please follow THIS LINK for the Universal Safetynet Fix that replaces the MagiskHide Props Config process.
Has anyone tried the Pixel update and software repair tool
Google Pixel - Update and Software Repair
to go from Android 10 to 11?
Then modify the boot image with Magisk and fastbooting that?
ƒ
Az Biker said:
Which is why the following warning has been written in the OP since Feb 2021:
KNOWN ISSUE:
* * * MagiskHide Props Config IS NO LONGER WORKING * * *
Please follow THIS LINK for the Universal Safetynet Fix that replaces the MagiskHide Props Config process.
Click to expand...
Click to collapse
That assumes that people read the OP.
biTToe said:
Has anyone tried the Pixel update and software repair tool
Google Pixel - Update and Software Repair
to go from Android 10 to 11?
Then modify the boot image with Magisk and fastbooting that?
ƒ
Click to expand...
Click to collapse
It will almost certainly perform a factory reset in the process.
Just sharing how I do it in case someone is interested in a shorter path:
1. Download the new full factory image
2. Extract the file. Then extract boot.img from the image zip file within.
3. Copy boot.img to your pixel 5
4. Patch it with magisk
5. Move back the patched file, rename it to boot.img
6. Update the original zip file titled image-redfin-r*.zip with the new boot.img file (override the older one)
7. Edit flash-all file by removing -w so it won't wipe your device clean
8. Flash with flash-all
No need to unroot and reroot.
(Sorry guys, this would have been up sooner, but Android File Host hasn't been letting me upload all day for some reason, so I just temporarily uploaded May 2021's files to my Google Drive for now instead. Enjoy! --- moved back to AFH )
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ2A.210505.002, May 2021"!
Magisk v22.1 Patched Boot Image: https://www.androidfilehost.com/?fid=2188818919693794185
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=2188818919693794183
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=2188818919693794180
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ2A.210405.005, Apr 2021". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq2a.210405.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=2188818919693776320
coral-rq2a.210405.005-factory-boot.img: https://www.androidfilehost.com/?fid=2188818919693776321
May 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq2a.210505.002-ca3e88b3.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq2a.210405.005-factory-boot.img
3. fastboot flash dtbo coral-rq2a.210405.005-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq2a.210505.002-ca3e88b3.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq2a.210505.002-magisk_patched-22100.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdX/LSposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!
I am getting an error with unpacking the boot image with both the one provided as well as the one direct from Google. Any fix?
@AlphAndroid, I had no problem with Google's boot img. Maybe you should download the factory image again and check the SHA-256 checksum to make sure the download is not corrupt.
@i5lee8bit, thanks for the guide as always, worked fine! Just adding that the platform tools have been updated to r31.0.2 from r31.0.0: https://developer.android.com/studio/releases/platform-tools
AlphAndroid said:
I am getting an error with unpacking the boot image with both the one provided as well as the one direct from Google. Any fix?
Click to expand...
Click to collapse
What do you mean with unpacking the boot image? Are you trying to patch it yourself in Magisk Manager and talking about the step where it says unpacking the boot image? @Ghisy's advice is good, check the hash checksums. Here are various hash checksums of the untouched factory boot image for this month:
File: coral-rq2a.210505.002-factory-boot.img
CRC-32: cedb0fab
MD5: 987f7849b32f3a652c7d8378bbe0048a
SHA-1: f55f0e4a3fc7d4e321a4f8fea0cad157f371f564
SHA-256: d2a53c9527b21f51526a4343506b2617c8b78100c3e6fb90df517372493145ba
SHA-512: 9a3c027b5fdc9072c7955b01be5489060f66ff718ddf51dcd1350324f84d56219f20086cd8ce128721246d6b88c08fbb0de6642d3dec60c141f2496f42316364
SHA3-256: 74fe9d3d65f6e186dfc0c7708f12b7f308e2f014720fc8930549c7d2c349aaef
SHA3-512: 48d3890a8e014ff65d4e81fdaa9f13746aa4ab9632f6e600cebb1e697bff45ebbe22b16b205965d31e8056667361f217ad29db6f9a0b9d44927bfb065cf82f0c
Are you downloading from PC and then copying to the phone? If you're using MTP or FTP, sometimes they mess with the file in tiny, almost unnoticeable (annoying) ways. Try downloading directly from the phone (and check the hash while you're at it).
i5lee8bit said:
What do you mean with unpacking the boot image? Are you trying to patch it yourself in Magisk Manager and talking about the step where it says unpacking the boot image? @Ghisy's advice is good, check the hash checksums. Here are various hash checksums of the untouched factory boot image for this month:
File: coral-rq2a.210505.002-factory-boot.img
CRC-32: cedb0fab
MD5: 987f7849b32f3a652c7d8378bbe0048a
SHA-1: f55f0e4a3fc7d4e321a4f8fea0cad157f371f564
SHA-256: d2a53c9527b21f51526a4343506b2617c8b78100c3e6fb90df517372493145ba
SHA-512: 9a3c027b5fdc9072c7955b01be5489060f66ff718ddf51dcd1350324f84d56219f20086cd8ce128721246d6b88c08fbb0de6642d3dec60c141f2496f42316364
SHA3-256: 74fe9d3d65f6e186dfc0c7708f12b7f308e2f014720fc8930549c7d2c349aaef
SHA3-512: 48d3890a8e014ff65d4e81fdaa9f13746aa4ab9632f6e600cebb1e697bff45ebbe22b16b205965d31e8056667361f217ad29db6f9a0b9d44927bfb065cf82f0c
Are you downloading from PC and then copying to the phone? If you're using MTP or FTP, sometimes they mess with the file in tiny, almost unnoticeable (annoying) ways. Try downloading directly from the phone (and check the hash while you're at it).
Click to expand...
Click to collapse
i also used a hash checksum, checked out the same
I'm just a bit hesitant to use the provided patched boot image now that I'm getting the issue.
I also had an error at 96% sideloading the OTA (something like: sideloading failed, no error 0). I then did NOTHING, stayed in Bootloader and downloaded the latest adb platform tools (mine was 30.0.5 from nov 2020, rather old) - with the newest platform tools I sideloaded again and then it worked (even though it stayed on 90% for 3-4 minutes, idk why, after that it smoothly went to 100% and finished sideloading) - then after that just normally flash the magisk patched file and the phone booted up again and is working fine. It seems to be more important than I thought to have the most up to date adb tools - never had an issue with that before. Thankfully my phone didnt go into bootloop, lol.
So it seems that the newest Pixel 4 xl OTA file is uncompatible with (maybe specific) older adb platform tools, ergo people if you have a problem, check your platform tools version - the OTA file that is linked here in this thread is fine and is not the rootcause of any issues.
Best place a remark into the mainpost @i5lee8bit that it is very important to keep the adb platform tools up to date and always check it before trying to update. It might save some people from trouble.
Hello all.
I need a little help please.
I am coming from:
10 (QQ2A.200305.003)
Magisk 21201 / 8.0.4
It’s been a while since I have done this and I would like to update to the Android 11 May version and I would like to make sure that what I am about to do is procedurally correct.
And, I am hoping this is the correct place to post
Download 11.0.0 (RQ2A.210505.002, May 2021 (coral-rq2a.210505.002-factory-0ec4212f.zip)
Unhide/Uninstall Magisk - Restore Images
Is this necessary with a factory reset?
Factory reset
Boot phone into fastboot mode
Flash-all.bat –w
At this point, once the phone re-boots, I should have a “working” phone on Android 11?
Extract boot.img and copy to phone
Download Magisk-v23.0.apk to phone and install
Do I set the update channel to beta or canary?
Install/select & patch boot.img
Reboot
Copy patched boot.img to computer
reboot into fastboot
Should I / could I fastboot flash boot boot.img --slot all at this point just to be safe?
Fastboot flash boot patchedboot.img
Fastboot reboot
Safetynet fix
Set update channel
Enjoy.
Am i missing anything?
Thanks in advance
ƒ
If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 3aXL
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5a
Pixel 6
Pixel 6 Pro
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
V0latyle said:
As many of you know by now, in order to run a patched boot image on Android 12 requires disabling Android Boot Verification.
On Android 12, disabling verity and verification will require a data wipe if it hasn't been done before. What seems to "lock" the state of boot verification is booting into system; so, if you perform an update, or flash vbmeta without the disable flags, then reboot into Android, you have essentially enabled boot verification and will require a wipe to disable it again. Confusing, I know.
Here is the appropriate update process. DO NOT take the automatic OTA if you are rooted. If you allow the phone to reboot after an update without disabling boot verification, you will have to wipe in order to disable it again, as you would need to for a patched boot image.
***Note***: The boot image doesn't have to be patched before you perform the update. Some have found it works better to update, THEN patch the boot image.
OTA Sideload:
1. Download both the OTA and the factory zip.
2. Extract vbmeta.img and boot.img from the factory zip.
3. Patch the boot image and copy it back to your computer.
4. Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
5. When the OTA completes, you will be in recovery mode. DO NOT REBOOT TO SYSTEM. Select "Reboot to bootloader".
6. Reflash vbmeta to disable boot verification:
Code:
fastboot flash vbmeta --disable-verity --disable-verification --slot=all vbmeta.img
7. Flash patched boot image:
Code:
fastboot flash boot --slot=all magisk_patched-23xxx_xxxxx.img
8. Reboot to system.
Factory update:
1. Download the factory zip.
2. Extract boot.img
3. Patch the boot image and copy it back to your computer.
4. Reboot to bootloader.
5. Apply update:
Code:
fastboot update --disable-verity --disable-verification --skip-reboot image-codename-buildnumber.zip
6. Flash patched boot image:
Code:
fastboot flash boot --slot=all magisk_patched-23xxx_xxxxx.img
7. Reboot to system.
Android Flash Tool:
1. Download the factory zip.
2. Extract boot.img
3. Patch the boot image and copy it back to your computer.
4. Reboot to bootloader.
5. Follow the instructions on the Android Flash Tool to update your device. The ONLY boxes you should check are "Disable Verity" and "Disable Verification"
6. When the update completes, the phone will reboot to system without root.
7. Reboot to bootloader and flash patched boot image:
Code:
fastboot flash boot --slot=all magisk_patched-23xxx_xxxxx.img
8. Reboot to system.
REMEMBER: The most critical part of this is making sure verity and verification are disabled during the update process before the phone reboots. If you forget to patch the boot image, that's OK - you don't have to flash /boot right after update.
If you have trouble with the patched boot image, simply flash /boot back to stock and allow Android to boot, then re-patch and re-flash the boot image.
You can also, if you want, boot the patched image instead of flashing it:
Code:
fastboot boot magisk_patched-23xxx_xxxxx.img
This is considered "temporary boot" as it loads the image from your PC rather than from device storage. You can use this to confirm root works, and if you so desire, you can then perform Direct Install in Magisk.
Click to expand...
Click to collapse
You Sir are all over these forums spreading helpful advice, and knowledge. I would just like to say Thank You for all you do here. It's so greatly appreciated. You are one of the many people who make this place so special.
Also, Thank You for your service to our country.
@V0latyle can you link me to a web page that would list every adb and fastboot command that we as android modders would use. What I mean is I couldn't find a Google search that listed the fastboot command with --slot=all among other adb and fastboot commands
Krsmqn said:
You Sir are all over these forums spreading helpful advice, and knowledge. I would just like to say Thank You for all you do here. It's so greatly appreciated. You are one of the many people who make this place so special.
Also, Thank You for your service to our country.
Click to expand...
Click to collapse
I agree with @Krsmqn, @V0latyle THANK YOU FOR YOUR SERVICE !!!!! in the military and for your service in the xda community
I used the Android Flash Tool method to update to the November build, and followed the instructions precisely. It worked flawlessly. My deny list is exactly the same in Magisk, and all my modules are working perfectly. I didn't even have to disable them. I think I will use this method from now on.
Krsmqn said:
You Sir are all over these forums spreading helpful advice, and knowledge. I would just like to say Thank You for all you do here. It's so greatly appreciated. You are one of the many people who make this place so special.
Also, Thank You for your service to our country.
Click to expand...
Click to collapse
elong7681 said:
I agree with @Krsmqn, @V0latyle THANK YOU FOR YOUR SERVICE !!!!! in the military and for your service in the xda community
Click to expand...
Click to collapse
Thanks guys, I appreciate it.
elong7681 said:
@V0latyle can you link me to a web page that would list every adb and fastboot command that we as android modders would use. What I mean is I couldn't find a Google search that listed the fastboot command with --slot=all among other adb and fastboot commands
Click to expand...
Click to collapse
Boy, I wish I had that handy, because I could sure use it too! I don't have your answer but hopefully someone else does, because believe me I'll be bookmarking it!
Will this work on Android Pixel 5a?
Rafiul Bari Chowdhury said:
Will this work on Android Pixel 5a?
Click to expand...
Click to collapse
Yes. The root process is exactly the same for the 4a 5g, 5, and 5a. The update process is the same across all Pixel devices.
I patched the boot.img. Magisk 23 did not report errors. But size of the patched file is zero. This looks not promising...
nostromo12 said:
I patched the boot.img. Magisk 23 did not report errors. But size of the patched file is zero. This looks not promising...
Click to expand...
Click to collapse
What version of Magisk did you use?
The stabil one
Will this work on Android Pixel 5a?
V0latyle said:
Yes. The root process is exactly the same for the 4a 5g, 5, and 5a. The update process is the same across all Pixel devices.
Click to expand...
Click to collapse
Okay. But Should I Remove Magisk Fully before upgrading through ADB/Fastboot/AFT?
H,
I'm on Android 11 pixel 5, can I use this tutorial ?
I think it's safer to unroot/remove Magisk and modules when going from 11 to 12 right? Some modules might not be compatible with 12 causing bootloops.
thecompany said:
I think it's safer to unroot/remove Magisk and modules when going from 11 to 12 right? Some modules might not be compatible with 12 causing bootloops.
Click to expand...
Click to collapse
You're going to have to wipe /data anyway if you intend to root on Android 12. Unless you're willing to try an idea I have.
Thanks V0latyle !!
I follow the flash tool method for update from october to november on my pixel 5
Perfect update, no issues and all data ok
nico22320 said:
Thanks V0latyle !!
I follow the flash tool method for update from october to november on my pixel 5
Perfect update, no issues and all data ok
Click to expand...
Click to collapse
Did you use Magisk canary? It is not necessary to check wipe in the android flash tool?
I use standard Magisk and can not change the update path to canary
nostromo12 said:
Did you use Magisk canary? It is not necessary to check wipe in the android flash tool?
I use standard Magisk and can not change the update path to canary
Click to expand...
Click to collapse
No i use the beta version of magisk.
You need wipe only for update from Android 11 to Android 12.
Just follow the guide for update to november and enjoy
nico22320 said:
No i use the beta version of magisk.
You need wipe only for update from Android 11 to Android 12.
Just follow the guide for update to november and enjoy
Click to expand...
Click to collapse
I want to upgrade from 11 (oktober) to 12
In the first message from this thread concerning the flash tool there was no wipe mentioned.
I want to update keeping my data ! How to proceed?
The best way: save yours photos etc with your Google account and make a fresh install with Factory image on Android 12 ( with disable verity and vérification)
It's long for set up device but 100% of chance of work with no issues for futurs update
Sûre you Can try to update without wipe and disable verity and vérification but maybe bootloops or not