Related
Hope this helps.
1. Install android sdk and use the included install manager in the sdk to install the latest google usb drivers and platform tools (platform tools include fastboot and adb). Make sure adb and fastboot directory is in your Path variable as well.
2.Download latest stock image for Nexus 9 from google: https://developers.google.com/android/nexus/images?hl=en
3.Download latest twrp (here is the latest right now 10/6/2015): http://forum.xda-developers.com/nex...recovery-twrp-2-8-2-0-touch-recovery-t2944788
4.Download either a stock boot image with the no- forceencrypt flag set or a kernel with the no-forceencrypt flag set
a.I use the elementalx kernel (10/6/2015): http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657
b.A stock kernel for the MRA58K build with the no-forceencrypt flag set can be found here (boot.zip): http://forum.xda-developers.com/nexus-9/general/marshmallow-factory-images-available-t3218290/page3
5.Download the latest supersu that works with nexus (beta now) : http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
6.Make sure you have usb debugging enabled and ability to unlock bootloader (android developer options menu on nexus).
7.Unzip the 6.0 stock image into a folder and open a command window in the folder.
8.Type the following:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot oem unlock
c.flash-all, now wait a few minutes while the stock image flashes
9.At this point your nexus will reboot. Once you’re started, up you need to again enable usb debugging and the ability to unlock your bootloader in the android developer options menu. Now type the following to flash TWRP:
a.adb reboot bootloader, wait until nexus boots into bootloader
b.fastboot flash recovery twrp.img (or whatever the image filename is from the twrp download).
10.Important: now make sure you boot DIRECTLY into TWRP via the button combination (power and volume down), a fastboot command, or the fastboot menu. If you don’t TWRP will be deleted and you’ll need to reflash using the last step.
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
12.Now type adb push supersufile.zip /sdcard/supersufile.zip, make sure you’re typing from the correct directory.
13.Install supersu via the install menu on TWRP.
14.You now need to install a kernel with the no-forceencrypt flag set:
a.If you want to install a custom kernel (like elementalx), type adb push elementalxfile.zip /sdcard/elementalxfile.zip, make sure you’re typing from the correct directory. Then use TWRP to install the zip from your sdcard.
b.If you want to install the modified stock boot.img then unzip the boot.zip, boot back into the bootloader and type: fastboot flash boot boot.img. Make sure you do NOT boot back into the android OS before doing this step or you'll have to reflash twrp.
Reboot and you’re good to go.
Didnt work for me.
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
typo
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Fda979 said:
excellent guide, just a small typo on 9.b, "fastboot (not flashboot) flash recovery twrp.img"
Thank you
Click to expand...
Click to collapse
Fixed. Thanks.
Sent from my Nexus 9 using Tapatalk
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
I flashed the latest supersu and the latest elementalx kernel.... been running it since about an hour after elementalx kernel for 6.0 final was posted....... everything seems to be working fine. Are you sure? Maybe i'm having no problems with supersu because i'm using elementalx? let me know the reason, i'll check it out on my tablet and see if i can reproduce, and if so i'll modify the guide. But after about a day and a half use, i've had no issues. thx for quality checking.
gt
Am I missing something?
can I not just do a wipe and flash the img with twrp like a custom rom? Edit: Got it working. For me it was much easier to use this as opposed to the android sdk, because it would not detect my version of java. From there I followed your instructions, mostly. Putting the files you posted inside the directory the mini adb client allowed the flash-all command to work. From there I followed chainfire's instructions on the latest SU. Everything seems to be running smoothly. Thanks for the initiative, OP :good:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
dkryder said:
i used supersu 2.52 due to it seems be be required by the guides and i get the notification that the binary needs to be updated. i have not done that yet. is updating the binary something i should try to do? or, if not is it ok to turn off notifications from supersu? thanks.
Click to expand...
Click to collapse
Of course update binaries. Choose normal method.
Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
I was facing same issue, then updated fastboot(android-sdk) and flash-all script worked fine for me.
That should work as well. That sequence of commands should work with any fastboot version. Just make sure to flash the vendor.img, some scripts don't use that as it's only used for the Nexus 9.
Why so complicated? I just installed @wug's NRT toolkit(on a Venue8 pro) and it did everything for me. Now im on rooted stock 6.0 with disabled encryption. Only thing i needed to do is to flash latest super su beta 2.52, that's it.
Verttex said:
Flash-all script doesn't work for everyone use these steps:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w
fastboot flash boot boot.img [unencypted if wanted]
fastboot flash cache cache.img
fastboot flash recovery recovery.img [twrp usually]
fastboot flash system system.img
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
i did all this, no worries and no error messages
i did fastboot reboot
now I am in a weird loop of
- google screen
- your device is corrupt
- google screen
- twrp (it flashes quite quickly, error messages on mounting everything and last line says something about renaming and something about stock rom)
loop
any ideas ?
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Verttex said:
Did you make sure to flash vendor.img?
You might try flashing the regular recovery first and then boot in, turn on oem unlock and adb, and then flash twrp and modified boot.img, then reboot into twrp (don't boot normally or it will erase twrp) and flash SuperSU.
Click to expand...
Click to collapse
yes, that seems to have been it
flashing TWRP seems to have been the problem so I have left everything as stock until root etc works on the stovk kernel
thanks for your help
Nice guide.
I install Busybox from Play, I assume that's needed? Everyone else doing this?
- sYndrome - said:
You can't just flash latest stable SuperSU, you need SuperSU 2.50+ beta and a modified boot.img. Instructions here: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Click to expand...
Click to collapse
added link to the latest beta supersu. thx.
All of these steps worked for me, but my battery doesn't charge right I don't think. It says battery life is at 3,745%. It runs out somewhere around 3,000%. Any ideas on how to fix that?
delete guide
--reserved--
Hoe can i tell what image matches for my phone stil on 8.1 november 1st security patch n a unlocked boot
rob420p said:
Hoe can i tell what image matches for my phone stil on 8.1 november 1st security patch n a unlocked boot
Click to expand...
Click to collapse
Check your build and download the right file.
Matteo
While uninstalling Magisk(from rooted stock), do we need to find the current active slot and flash the stock image to it? In the guide flashing to both partitions is mentioned.
mujtahid1494. said:
While uninstalling Magisk(from rooted stock), do we need to find the current active slot and flash the stock image to it? In the guide flashing to both partitions is mentioned.
Click to expand...
Click to collapse
Flash a both slot just to be sure to pass OTA if needed.
Matteo
Matteo said:
Welcome to AIO Magisk Sub Guide.
Here you will find best methods for root Mi A2. I will maintain this guide with all safe, update methods. Currently only patched boot method is out for Stock Roms. I will add Twrp methods when we have decryption on pie.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
Install Magisk on Stock Roms Oreo & Pie
Needs:
- Bootloader unlocked, check this (currently not out) guide.
- Magisk Manager apk check Dowloads Section
- A brain
Procedure:
- Download the correct PatchedBoot file for your build from Downloads Section
- Rename the patched boot file to "patched_boot.img" and past it to your adb folder.
- Download Magisk Manager apk from Downloads Section
- Move apk to phone sdcard
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
- Now open adb(fastboot) command prompt and type :
Code:
fastboot boot patched_boot.img
Your phone shoulds boot
- Install Magisk Manager apk
- Open Magisk Manager
- Click Install then choose Direct install. Reboot.
Done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
Install Magisk on Custom Roms
Needs:
- Be on a Custom Rom
- Latest Magisk Beta zip check Dowloads Section
- Twrp latest file.img check Dowloads Section
- A brain
Procedure:
Sideload method. (It's for people who want to install Magisk on their phone during Custom Rom installation process without any permanent Twrp (usefull for people who want to root their phone when they have MTP issue during Custom Rom installation)
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your adb folder.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Navigate to Advanced > Adb Sideload
- Swipe to allow
- Open adb (fastboot) command prompt on your pc, type
Code:
adb sideload magisk.zip
Reboot and done, you have Magisk on your device.
Normal temp Twrp method. (It's for people who want to install Magisk on their phone when they are already running a Custom Rom without permanent Twrp.
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your phone sdcard.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Click Install, choose magisk.zip
- Swipe to confirm, wait for the process...
Reboot and done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
If you have any issue, or if i make any type error, reply.
don't forget to ckick the TX button.
Downloads Section:
Boot / Patched Boot images
Magisk Thread for Beta zip / Apk file
Twrp images & zip
Click to expand...
Click to collapse
Hello, the stock boot v10.0.1.0.img, does not have mirrors, please could upload it again, I need it urgently, thank you very much
ofuen said:
Hello, the stock boot v10.0.1.0.img, does not have mirrors, please could upload it again, I need it urgently, thank you very much
Click to expand...
Click to collapse
No. If you have issue with androidfilehost it's not my problem.
Matteo
Matteo said:
Welcome to AIO Magisk Sub Guide.
Here you will find best methods for root Mi A2. I will maintain this guide with all safe, update methods. Currently only patched boot method is out for Stock Roms. I will add Twrp methods when we have decryption on pie.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
Install Magisk on Stock Roms Oreo & Pie
Needs:
- Bootloader unlocked, check this (currently not out) guide.
- Magisk Manager apk check Dowloads Section
- A brain
Procedure:
- Download the correct PatchedBoot file for your build from Downloads Section
- Rename the patched boot file to "patched_boot.img" and past it to your adb folder.
- Download Magisk Manager apk from Downloads Section
- Move apk to phone sdcard
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
- Now open adb(fastboot) command prompt and type :
Code:
fastboot boot patched_boot.img
Your phone shoulds boot
- Install Magisk Manager apk
- Open Magisk Manager
- Click Install then choose Direct install. Reboot.
Done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
Install Magisk on Custom Roms
Needs:
- Be on a Custom Rom
- Latest Magisk Beta zip check Dowloads Section
- Twrp latest file.img check Dowloads Section
- A brain
Procedure:
Sideload method. (It's for people who want to install Magisk on their phone during Custom Rom installation process without any permanent Twrp (usefull for people who want to root their phone when they have MTP issue during Custom Rom installation)
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your adb folder.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Navigate to Advanced > Adb Sideload
- Swipe to allow
- Open adb (fastboot) command prompt on your pc, type
Code:
adb sideload magisk.zip
Reboot and done, you have Magisk on your device.
Normal temp Twrp method. (It's for people who want to install Magisk on their phone when they are already running a Custom Rom without permanent Twrp.
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your phone sdcard.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Click Install, choose magisk.zip
- Swipe to confirm, wait for the process...
Reboot and done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
If you have any issue, or if i make any type error, reply.
don't forget to ckick the TX button.
Downloads Section:
Boot / Patched Boot images
Magisk Thread for Beta zip / Apk file
Twrp images & zip
Click to expand...
Click to collapse
Thank you very much. It works for my stock rom. already clicked the thanks icon
dipankar.roy said:
Thank you very much. It works for my stock rom. already clicked the thanks icon
Click to expand...
Click to collapse
Thank you man, but plz next time don't quote the entire guide
Have a nice day
Matteo
No links available for stock boot 9.6.17.0
Edit: Oh I see, not his problem, dang.
Matteo said:
Welcome to AIO Magisk Sub Guide.
Here you will find best methods for root Mi A2. I will maintain this guide with all safe, update methods. Currently only patched boot method is out for Stock Roms. I will add Twrp methods when we have decryption on pie.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
Install Magisk on Stock Roms Oreo & Pie
Needs:
- Bootloader unlocked, check this (currently not out) guide.
- Magisk Manager apk check Dowloads Section
- A brain
Procedure:
- Download the correct PatchedBoot file for your build from Downloads Section
- Rename the patched boot file to "patched_boot.img" and past it to your adb folder.
- Download Magisk Manager apk from Downloads Section
- Move apk to phone sdcard
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
- Now open adb(fastboot) command prompt and type :
Code:
fastboot boot patched_boot.img
Your phone shoulds boot
- Install Magisk Manager apk
- Open Magisk Manager
- Click Install then choose Direct install. Reboot.
Done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"[/HIDE][/SIZE]
If you have any issue, or if i make any type error, reply.
don't forget to ckick the TX button.
[/SIZE]
Click to expand...
Click to collapse
After installing the patched boot image to my device (MI A2), android version 9. build number V10.0.2.0.PDIMIFJ,
the Magisk working properly. But when I turned off my phone and insert the power cable for charging, the phone start booting and stuck at "AndroidOne" logo.
Waiting for your advice...
Thanks..
dipankar.roy said:
After installing the patched boot image to my device (MI A2), android version 9. build number V10.0.2.0.PDIMIFJ,
the Magisk working properly. But when I turned off my phone and insert the power cable for charging, the phone start booting and stuck at "AndroidOne" logo.
Waiting for your advice...
Thanks..
Click to expand...
Click to collapse
That's a normal stock rom issue with magisk, you can't fix it. but if you want, we don't have this issue on custom roms
( next time plz don't quote the entire thread )
Matteo
Hey Matteo,
I've got a problem while booting with the patched boot image. Whenever I start the 'fastboot boot image' stuff, it ends with following message:
downloading 'boot.img'...
FAILED (command write failed (no error))
finished. Total time 0.002s
Phone screen goes black and says 'press any key to continue' or something like that. I tried several different USB ports and also different boot images, I cant even boot with the stock image.
When I unlocked the bootloader I had a problem that while booting the phone said I should perform a factroy reset because of a corrupt file system...after doing that, the phone itself works fine. But I really want the root access.
Have you ever encountered that message?
Thanks in advance
Update: Did the same procedure with my notebook and ironically it worked without a flaw. USB driver conflicts maybe?
On Pie V10.0.2.0, applied the patched_boot.img, Magisk was not installed at the beginning.
Installed Magisk manually but the phone was not rooted.
Applied the patched_boot.img again and I got root.
Now, every time I reboot the phone, root is gone and I have to apply the patched_boot.img again.
Thread closed on OP request
lately I did a clean install of OOS 10.0.1 on my International 6t. Installed OOS and magisk from TWRP.
After booting there was a Magisk Manager in applications claiming that Magisk itself was not installed. I tried to install Magisk from Manager, but failed. Then I reboot the phone into the recovery and TWRP was gone!! There was only a stock recovery. Well, I tried to run TWRP from computer with 'fastboot boot .\twrp-3.3.1-28-fajita-Q-mauronofrio.img'. Error - "remote: unknown command".
I searched forum and found a thread fastboot boot twrp.img FAILED (remote: unknown command). @dbarrett480 wrote: 'Twrp can't flash anything to system in A10 right now, so unless that is fixed there is no point at this moment anyway. A10 uses a virtualized system partition which doesn't allow R/W access to system....'. Does it mean that rooting is not possible with stock OOS and only possible solution is to use custom ROM?
It is. Look for the patched boot.img and flash that through fastboot. Make sure to install magisk manager first.
BesoC said:
Well, I tried to run TWRP from computer with 'fastboot boot .\twrp-3.3.1-28-fajita-Q-mauronofrio.img'. Error - "remote: unknown command".
I searched forum and found a thread fastboot boot twrp.img FAILED (remote: unknown command). @dbarrett480 wrote: 'Twrp can't flash anything to system in A10 right now, so unless that is fixed there is no point at this moment anyway. A10 uses a virtualized system partition which doesn't allow R/W access to system....'. Does it mean that rooting is not possible with stock OOS and only possible solution is to use custom ROM?
Click to expand...
Click to collapse
The information you found is outdated. I'm surprised you didn't properly read through the official TWRP thread here, more specifically this post clarifies the error in your use of fastboot (or better said: the use of fastboot according to the mistakes made by OnePlus). Which is also mentioned several times in the page you linked to.
As a senior member, please don't create new threads inquiring information you could easily find. Even though the methods to obtain it have been challenging for a short while, being able to achieve root has never been interrupted for this device. Even without being able to modify system files. Systemless rules!
Wrapped with delicious Fajita [emoji896]
bokkoman said:
It is. Look for the patched boot.img and flash that through fastboot. Make sure to install magisk manager first.
Click to expand...
Click to collapse
So, should do following:
Install Magisk Manager
Flash patched boot.img through fastboot
Install TWRP
Install Magisk
Is it correct?
The patched boot.img already contains magisk.
But you don't need twrp to be rooted, unless you really want to use it for something else... But i don't use it anymore. So I'm fully stock, except that I'm unlocked and rooted.
So it should be:
1. Install magisk manager.
2. Flash boot.img
3. Enjoy. But check magisk manager if it was successful.
bokkoman said:
The patched boot.img already contains magisk.
But you don't need twrp to be rooted, unless you really want to use it for something else... But i don't use it anymore. So I'm fully stock, except that I'm unlocked and rooted.
So it should be:
1. Install magisk manager.
2. Flash boot.img
3. Enjoy. But check magisk manager if it was successful.
Click to expand...
Click to collapse
Regarding all that was said here, is rooting possible by following these steps?
Reboot
Fastboot TWRP img
Use volume up to recovery and power button to boot to recovery
Flash 10.0.1 stock boot img from TWRP
Flash TWRP zip
Reboot to recovery
Flash Magisk 20.1
Flash kernel if want
Reboot system
Click to expand...
Click to collapse
BesoC said:
Regarding all that was said here, is rooting possible by following these steps?
Click to expand...
Click to collapse
Yes, this tutorial with the twrp should work ...
BesoC said:
Regarding all that was said here, is rooting possible by following these steps?
Click to expand...
Click to collapse
That's only if you need TWRP.
But for what I've been reading, you don't need TWRP and then i suggest to not install it.
Just flash everything stock and keep it that way. Only thing to flash is the patched boot.img with root in it.
You can always update Android from the settings and patch/install boot with magisk manager on inactive slot. This will keep your device rooted without the need of TWRP.
Here what I found:
https://forum.xda-developers.com/showpost.php?p=81111389&postcount=145
Today I installed the new update, 10.0.1 for OP 6T and then I discovered that there is no magisk patched boot.img yet. I extracted it with payload dumper, patched with the installed magisk and flashed successfully.
I uploaded it to my drive for others. https://drive.google.com/open?id=1kb...VgWNaWgLN6j17b
The commands for flashing are:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Maybe someone can add it to the first post.
original 10.0.1 boot.img https://drive.google.com/open?id=1HP...Du8zCOFMXInjXq
Click to expand...
Click to collapse
I used this method to root 10.0.01
https://forum.xda-developers.com/oneplus-6t/how-to/ultimateguide-t4004367
I went from rooted 9.0.17 to 10 to 10.0.01
Never had an issue and everything works fine for me.
Today I installed the new update, 10.0.1 for OP 6T and then I discovered that there is no magisk patched boot.img yet. I extracted it with payload dumper, patched with the installed magisk and flashed successfully.
I uploaded it to my drive for others. https://drive.google.com/open?id=1kb...VgWNaWgLN6j17b
The commands for flashing are:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Maybe someone can add it to the first post.
original 10.0.1 boot.img https://drive.google.com/open?id=1HP...Du8zCOFMXInjXq
Click to expand...
Click to collapse
My phone get stuck on the boot animation by following this guide. I have not factory reset my phone.
DrXperience said:
My phone get stuck on the boot animation by following this guide. I have not factory reset my phone.
Click to expand...
Click to collapse
I still don't get why people don't use the good old way:
fastboot flash boot twrp.img (latest version)
If you just need root use twrp to flash Magisk zip
If you need twrp flash twrp installer also
Reboot
All the mess before was because we didn't have a working TWRP! Now that we have it don't need to use patched boot img made by others.
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
How do I get Magisk 21.0 to install through Magisk Manager?
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
CraigHardy said:
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
Click to expand...
Click to collapse
This is what I am getting after following your directions to a T!
I also flashed to both partitions. Please see attachments. I sent 2 screenshots.
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
CraigHardy said:
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
Click to expand...
Click to collapse
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Doesn't work. Download the patched image, put it on the phone, use magisk canary manager to patch it again, transfer it off your phone, then boot into Fastboot and flash it.
It has to be patched in the phone it will be installed to otherwise it will not work.
akinkoff85 said:
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Click to expand...
Click to collapse
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Here is the exact size.
Problem uploading image
I am a little confused now... I uninstalled root for a few days and now have the second release of android 11... I am in fastboot mode doing fastboot flash boot... then the file name and all it says is waiting for device?? Any help??
dladz said:
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Click to expand...
Click to collapse
Indeed, using the beta version worked for me! Thanks for the tip!
imval said:
Indeed, using the beta version worked for me! Thanks for the tip!
Click to expand...
Click to collapse
No worries man, glad you're sorted
CraigHardy said:
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
Click to expand...
Click to collapse
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
rodken said:
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
akinkoff85 said:
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Click to expand...
Click to collapse
Watch this video it helped me out allot
dladz said:
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
Click to expand...
Click to collapse
I did not know that one can just boot a magisk_patched.img instead of flashing.
rodken said:
I did not know that one can just boot a magisk_patched.img instead of flashing.
Click to expand...
Click to collapse
It's preferable.
There are some things to note.
1st. You are only booting it, meaning if you reboot; you will start using the installed / flashed image and the booted image will be lost.
2nd. For the above reason. If you want to make root permanent you have to open magisk after opening and then click install - install directly.
As magisk will already have root access, it will be able to accomplish patching, if you tried this whilst unrooted it would fail, or not be an option.
3rd. By booting you avoid the potential bootloop problems you can and almost will have at some point if you always flash, bad images are pretty rife for a number of reasons.
I've got a large guide for rooting in the guides section which covers all the bases and their shortcomings /benefits.
Hello!
I want to root a degoogleifyed Pixel 3a on LineageOS 17.1 using Magisk, but I'm not sure to understand which boot.img use for this.
For an other phone, I found the boot.img in the last nightly build on lineageosroms.com. The sargo one don't seem to contain it.
I've already read some how to (like this one), but I would like to have confirmation that it apply to LineageOS. Could some confirm that I should:
1. download the boot.img directly from Google
2. patch it with Magisk
3. reboot into fastboot mode
4. flash the phone with command:
fastboot flash boot /path/to/magisk_patched.img
Sorry in advance if the answer seems obvious. My English is not very good and I start with these manipulations, so I'm a little afraid of miss something.
_yoxd said:
Hello!
I want to root a degoogleifyed Pixel 3a on LineageOS 17.1 using Magisk, but I'm not sure to understand which boot.img use for this.
For an other phone, I found the boot.img in the last nightly build on lineageosroms.com. The sargo one don't seem to contain it.
I've already read some how to (like this one), but I would like to have confirmation that it apply to LineageOS. Could some confirm that I should:
1. download the boot.img directly from Google
2. patch it with Magisk
3. reboot into fastboot mode
4. flash the phone with command:
fastboot flash boot /path/to/magisk_patched.img
Sorry in advance if the answer seems obvious. My English is not very good and I start with these manipulations, so I'm a little afraid of miss something.
Click to expand...
Click to collapse
The boot.img is in the firmware but must be extracted to get to it. Since it is different than stock, you should use it, if needed. I can get it for you later. This wasn't zipped, just renamed by afding .zip to the end so it would upload.
Thank you Tulsadiver! Your answer helped me to understand what to do.
In case it could help someone else, that's what I did:
1. download the last nightly build on https://download.lineageos.org/sargo
2. unzip it
3. dump the boot.img from the payload.bin using this guide (if you use Linux)
4. patch the boot.img with Magisk
5. reboot the phone into fastboot mode:
adb reboot fastboot
6. flash the phone with commands:
fastboot flash boot magisk_patched.img
fastboot flash boot_b magisk_patched.img
The phone is now rooted!
I installed Lineage and rooted it last night. I followed the instructions and patched the stock boot.img from Google. Boy was that mistake! My digitizer stopped working. I then patched the Lineage RECOVERY image from the Lineage website. Now my phone is rooted perfectly!
ackliph said:
I installed Lineage and rooted it last night. I followed the instructions and patched the stock boot.img from Google. Boy was that mistake! My digitizer stopped working. I then patched the Lineage RECOVERY image from the Lineage website. Now my phone is rooted perfectly!
Click to expand...
Click to collapse
Roger that. Download the Lineage recovery image that's dated same as the Lineage rom build you are using and patch it using magisk manager and flash to boot partition. sudo fastboot flash boot lineage-18.1-2021xxxx.recovery.img --slot all (enter) You should be good then. Both boot and recovery sort of reside in the same place (boot) as there is no longer a recovery partition on A/B partition devices and everything nowadays that's Android is A/B partition. Works for me on my Pixels.