Related
If we don't have TWRP,
How do we root the device?
Magisk has the option to patch a boot.img file. Technically, you could:
1. pull the boot.img file from the A10 OB1 zip
2. copy it to the phone's internal storage
3. install latest magisk manager, click on install - patch boot.img - choose the boot.img
4. copy the patched boot.img to a pc with ADB and USB drivers
5. put the phone in fastboot mode, sideload the boot.img
I have no idea if this would work, but you could give it a go. I believe that someone else already made a guide for exactly this here in the OP6T forum.
Refer to the twrp thread for OB 10.
https://forum.xda-developers.com/oneplus-6t/help/how-to-flash-twrp-android-10-beta-1-t3986345
Either do the OTA local upgrade and magisk uninstall then install to inactive slot method, or use the boot patch which there is another thread on that on the ROM Dev section.
I used the first, worked fine. But there is no supported twrp yet. Only magisk root is officially supported on Q.
Hello, After Root, it's impossible for me to boot on recovery mode
Always i'll want to do or, thé phone reboot on fastmode.
g4seb said:
Hello, After Root, it's impossible for me to boot on recovery mode
Always i'll want to do or, thé phone reboot on fastmode.
Click to expand...
Click to collapse
Yes, likely because the update flashed to the inactive, and there is no recovery now. So...if you want recovery, only way is to full wipe and do a MSM or flash all and wipe with older stable.
OP support/forums made announcements on their thread on what will happen with upgrading, or rolling back.
They have a rollback file you can download if you want it all working again including recovery. But you will get wiped as mentioned, and be back on the last stable and firmware. Then you can twrp and root all over again.
That is Beta testing for you!!
Hi, I'm interesed on android beta 11 but I have a lot of customizations root related in Android 10, (includes soli radar use and GSM doze, for example).
The question is Magisk Canary version works on 11? Or the better is wait for a update or android stable version?
Hi, root is working with the canary version of magisk. Most of the apps who needs root are working....( Titanium Backup,Adaway) The only app that isn t working for me is Swift installer for theming.....
Greetz
Hi, can someone help me? I'm on the Pixel 4 Android 11 Beta, I installed the new Magisk manager (the Canary version I think?), and patched the boot image, but after flashing I'm stuck in the bootloader and I can't even turn off the phone anymore. Also, I saw 4 channels in the settings of the manager, stable, beta, canary and canary (debug), but I don't know which one to use and if it matters? Help is really appreciated!
bjonkheer said:
Hi, can someone help me? I'm on the Pixel 4 Android 11 Beta, I installed the new Magisk manager (the Canary version I think?), and patched the boot image, but after flashing I'm stuck in the bootloader and I can't even turn off the phone anymore. Also, I saw 4 channels in the settings of the manager, stable, beta, canary and canary (debug), but I don't know which one to use and if it matters? Help is really appreciated!
Click to expand...
Click to collapse
what boot.img do you use? i´m a little cofused because the image for download is flame-rpp4.200409.015-factory-8012c549 but my pixel says are in rpp4.200409.020 I´m scared for the bootloop or something if I flash the 015 boot image.
***Edit:
Forget it, I found and download the RPB1.200504.020
caballero221 said:
what boot.img do you use? i´m a little cofused because the image for download is flame-rpp4.200409.015-factory-8012c549 but my pixel says are in rpp4.200409.020 I´m scared for the bootloop or something if I flash the 015 boot image.
***Edit:
Forget it, I found and download the RPB1.200504.020
Click to expand...
Click to collapse
How did you root I have difficult to do it years Root pixels and pixel 4 won't root.
Any guide apriciated.
caballon said:
How did you root I have difficult to do it years Root pixels and pixel 4 won't root.
Any guide apriciated.
Click to expand...
Click to collapse
It's really simple: you download the build from Google the build you have installed on your phone, unzip It, and unzip it again and again the archives inside the unzip folder until you see the boot.img
Copy this boot.img and paste to your internal storage, install the magisk Canary apk and select install magisk zip. Select "patch selected image" in the instalation metod, and select the boot.img copypasted before. Copy the new patched boot.img to your computer and flash to your phone via fastboot mode.
Sent from my Pixel 4 using XDA Labs
caballero221 said:
It's really simple: you download the build from Google the build you have installed on your phone, unzip It, and unzip it again and again the archives inside the unzip folder until you see the boot.img
Copy this boot.img and paste to your internal storage, install the magisk Canary apk and select install magisk zip. Select "patch selected image" in the instalation metod, and select the boot.img copypasted before. Copy the new patched boot.img to your computer and flash to your phone via fastboot mode.
Click to expand...
Click to collapse
In the bootloader or fastboot mode.
caballon said:
In the bootloader or fastboot mode.
Click to expand...
Click to collapse
In the bootloader, via fastboot commands
Sent from my Pixel 4 using XDA Labs
I get the problem when I try to flash patched boot img, I end up in the bootload with status 'no valid boot slot to boot'. Any hints?
Can anybody upload patched magisk boot img for pixel 4 .020 ?
I get the same error in beta2, I think must flash the same boot.img of the zip (patched, obviously) but this means clean flash (flash-all) every update and lost the data
Sent from my Pixel 4 using XDA Labs
Has anyone managed to root android 11 beta3? when I try to flash patched boot img, I end up in the bootload with status "no valid boot slot to boot".
Do you use Magisk Canary to patch?
You update via OTA or full flash?
Sent from my Pixel 4 using XDA Labs
caballero221 said:
Do you use Magisk Canary to patch?
You update via OTA or full flash?
Sent from my Pixel 4 using XDA Labs
Click to expand...
Click to collapse
I've used latest Magisk Canary. I've update via ota the i've used Factory Image (cancelled -w) to reboot the phone to normality .
I've also a Pixel 3 that i root without no problem with the same method.
grigiotitan said:
I've used latest Magisk Canary. I've update via ota the i've used Factory Image (cancelled -w) to reboot the phone to normality .
I've also a Pixel 3 that i root without no problem with the same method.
Click to expand...
Click to collapse
I don't know why, but since beta 2 the method don't work. My pixel 4 fall in bootloop in the same way, and only fix flashing the OTA. Before, I think only work with full whipped beta installation and patch specific the boot.img of the full beta img flashed, but not tested yet
Sent from my Pixel 4 using XDA Labs
Good day fellow XDA members,
I recently updated my 8 Pro to 11.0.5.5 and forgot that i should not have rebooted it. (Worst idea ever, i know)
I had Root with Magisk before, but now I don't obviously.
So I thought to myself, that this shouldn't be a problem just flash the patched_boot.img anew and i'll have Root again.
Well that was certainly not the case.
I tried just about anything I could find on some Forums the last two days, but couldn't get the device rooted.
What i tried:
Several boot.img from XDA and also patched my own boot.img from the extracted payload with every Magisk apk from 21 onward(Also beta and Canary).
The old patched boot.img i used before the update.
Horizon bootloader
There is obv no Magisk module present anymore to disable/delete.
I also have EdXposed installed.
Everytime i tried something other than the original boot.img i got either a bootloop or a crashdump screen.
Can i get root back without fully wiping my 8 Pro?
If yes, how?
If not, how can i backup everything because some Data from some Apps is crucial to me and is not saved in the Cloud.
Thanks in advance
Dead1y_Wolf
I'm on the same boat I did direct install instead of install to inactive slot
Just follow my guide, change the payload dumper you're using, use the latest version of magisk
Bare in mind that you need to match the version used to create it.
Also don't flash the image. Just boot it.
Make sure modules are removed beforehand.
If that still fails then use the ADB magisk removal command then proceed.
I've booted, flashed, directly installed and updated then installed a lot and have never had a single problem..
So the process is correct..
I've been running custom roms since before android was a thing so I'm usually pretty good at this stuff.
I'm running 11.0.9.9 IN11AA
It refuses to root. I'm not sure if there is some step I'm missing that's so obvious nobody mentions it?
I was rooted, but when the new Magisk 23 came out without Magisk hide.. it was a big problem for me. I have corporate apps that will refuse to work on a rooted device. I restored the stock images (just like I do to get my OTA).. but then I uninstalled Magisk 23 and Installed 22.1. I then patched the bootloader (Dire3ct Install) and all was good, until I rebooted and had no root.
My bootloader is unlocked.
So I downloaded the full stock rom v11.0.9.9 IN11AA directly from Oneplus.
Extracted payload.bin
Used Payload dumper to get the proper boot.img.
Copied boot.img to my device and used magisk 22.1 to patch the file.
Downloaded the patched boot.img to my desktop.
Used ADB to flash it
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
Nothing. No Root.
I tried this over and over with different versions of magisk.
I tried downloading pre-patched version, and using fastboot boot patched_boot.img.
The device just hangs, and then boots using the stock image. No root.
I have no idea what could be wrong.
Ideas?
I just updated from v11.0.8.8 to v11.0.9.9 today on the EU variant.
Downloaded the update via Oxygen Updater, then used the built in updater with the local file downloaded.
Before restarting the device, opened up Magisk, then clicked "Install to inactive slot" since the new update gets put on the inactive slot. After it installed, rebooted the phone, and done. Updated to latest, and kept root. Didn't even turn off the modules, although I only have 1 installed.
This is my usual method to keep root while updating.
I'm not sure where you got your Magisk from, but i'm using v23.0 from the official github page (HERE), and it still has MagiskHide built-in, and currently using it for all of my banking apps, and it works.
Most likely the issue is that you have used the old Magisk version to patch the file.
Download the app from the link above, and use that to patch your boot.img file.
While the extracted file should work as flashed, I like to just boot from it rather than flash it and make it "permanent".
Use fastboot boot patched_boot.img to boot using the file once only.
After starting up, you should have Magisk installed in a couple of seconds. It might prompt you to restart the phone when opening it first time, but just ignore that and do not restart as you'll lose the root. Alternatively, you can install the app when you're not rooted yet, and when you boot using the patched boot.img, you won't need to restart.
When done, Magisk should tell that you have 23.0(23000) installed.
Then just use the built-in Install > Direct Install (Recommended) option within Magisk to install it to the current slot.
Do NOT install it to inactive slot. This option only to be used when updating via OTA.
Other option:
Download the Magisk app from the link above, and rename it to magisk.zip then copy it to your phone.
Download TWRP from HERE to your PC and use fastboot flash recovery twrp.img to flash this recovery.
Reboot to recovery. (Might take 2-3 mins to boot first time)
Flash the magisk.zip using recovery.
That's all you should need to be able to root.
I appreciate the help.
I was so hopeful you gave me what I needed, but it didn't work.
So, It wasn't an update issue... it was more of an attempt to downgrade Magisk.
I always OTA the same way as you and it always works.
I also always get Magisk from the official Github page.
What I got excited about was that I wasnt aware there was a working TWRP! So I thought.. THAT will fix it.
I didnt flash it, I just booted from it. I flashed Magisk that way, BUT... still not rooted.
Here is the interesting bit.. when flashing Magisk via TWRP, it detected that my boot.img was already Magisk patched and not stock (Which is right). It's like the boot.img is correctly patched, Magisk just isn't seeing it.
I'd be ok with a full wipe and factory reset at this point, but I'm not even sure that will fix it.
** Edit - I tried manually flashing the latest full OOS downloaded from Oneplus. It didnt help. I finally factory reset and it's working now.
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
ps000000 said:
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
Click to expand...
Click to collapse
Agreed, this is a great method. I tried that too before I ended up doing a reset... no good. I somehow broke something with the rom outside of Magisk so that Magisk wouldnt work. Whatever it was, A full wipe fixed it..
Hello there, back in the day (2019 in March or April the phone shipped with Android 9) I rooted my galaxy S10+ Exynos with Magisk and stock recovery (because TWRP method did not exist yet or did but non twrp method looked safer, I forgot the reason)
Then I forgot about TWRP and even upgraded to Android 10 like this:
(standard procedure, download android with Friya, then patch ap file with magisk, then flash it with odin)
Well I used my phone as always, forgot about twrp, but always had a little voice in my head telling me, that twrp is good idea, what if something happens, I would at least be able to copy my data)
So I decided to flash twrp, to ease my mind a bit, and also be able to copy apps to /system/priv-app
So I am using Android 10 (see no reason to upgrade, what I need is there I prefer OneUI 2.0 over later versions and I dont want to make my device slower or loose some obscure api function that I dont even know exists until I need it)
Now, can I just use official twrp app and let it do its thing (I have root), or do I need to download twrp with the app, but prepatch it with magisk before I install it? (I read conflicting info, on xda they say you need to prepatch it, while on twrp guide: https://twrp.me/samsung/samsunggalaxys10plus.html
They say to just use the app if you already have root, so I am confused now
It seams using the app is the easiest and most safe method
Thanks for Anwsering and Best Regards
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
well, I gues this did apply to me, because I tried to flash TWRP with the app (latest version: twrp-3.7.0_9-2 that the app offered, it offered 2 files .img or .img.tar, and I chose to flash .img), and now my phone cannot boot, its stuck in download mode it says with red letters
kernel: Could not do normal boot, (DT LOAD failed)
I don't know know what happened, I only flashed recovery, and bootloader is unlocked
adb doesn't work
I cannot even get to recovery
So what now? Can at least flash TWRP somehow back so I can get ot my files (I have most of my videos on an SD card, but 2 or 3 are on internal storage )
I would reflash Android 10 anyway if it wasn't for the files
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
I would first try older TWRP as DT LOAD failed (device tree) looks like TWRP problem to me.
alecxs said:
you can flash recovery.img as tar file but that is useless for backup stock ROM userdata. if you still have the magisk_patched.tar you can flash it to get your data back. don't flash unpatched stock boot.img this will most likely result in data loss.
Click to expand...
Click to collapse
OK
after installing TWRMP
3.4.0 I got into recovery
I guess the latest version twrp-3.7.0_9-2 is broken (because I tried flashing from Odin and I got the same error
but 3.4.0 works now
Well then I got into a non rooted android state (I couldnt boot into the rooted one because if I held volume up I just got into TWRMP)
I do have my magisk patched AP file (I did keep that), so I tried flashing it by odin to get into rooted state again, but then got scared because I was aftaid it would delete my data, so pulled the plug out, immediately after I discovered its flashing system.img (it just started)
thats where I interupted it
<ID:0/035> SingleDownload.
<ID:0/035> dt.img
<ID:0/035> dtbo.img
<ID:0/035> system.img
<ID:0/035> __XmitData_Write
<ID:0/035> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So then phone would not boot, not in TWRMP not in android anymore, so I flashed TWRMP again and now at least
I am in TWRMP (I can see my files, but they are encrypted (they have wierd names but size does seam to match my files)
So how do I reflash android now, without messing with /data partition?
or can I somehow backup just data partition, reflash android and flash /data back?
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
alecxs said:
let the magisk_patched.tar flash, just make sure you don't flash CSC (HOME_CSC is fine it won't erase userdata)
Click to expand...
Click to collapse
Yey, that did it (that was scarry), now root works, as well as android 10 (for some reason Magisk Manager does not open (but all the magisk modules work)
Now, I did patch this ap file back in the day I updated android to 10 so
I used Magisk Manager 7.4.1.291c718b
and if I remember corecly (thanks got I recorded everything) I patched the AP file for Magisk 20.2-11b7076a)
Now I have Magisk Manager 8.0.7 installed
So after I downgraded my Magisk manager to 7.5.0 it opened
Now I just have to figure out how to install Magisk v21.4 which is the version that belongs to my Magisk Manager 8.0.7, because Magisk Manager won't let me install a custom magisk, it only wants to download the latest version
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
or you can paste this url as custom channel and install older magisk if you want to.
https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
alecxs said:
you can install latest Magisk apk and patch stock boot.img again. Anyway I would do a backup with Migrate and adb pull -a /sdcard first.
Click to expand...
Click to collapse
aha, I see
is there any other way besides patching my AP file again? (I mean Magisk can clearly update itself somehow)
I mean, Magisk Manager does open (but only version 7.5.0, not version 8.0.7), and I have root its just that I don't have Magisk Manager 8.0.7
So how do I install a specific Magisk version from Manager? (I did try to install like a Magisk module, but now I am stuck in download mode again, so lets install Android 10 again )
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
alecxs said:
look in the json for download link
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
https://github.com/topjohnwu/magisk_files/commits/master/stable.json
https://github.com/topjohnwu/magisk-files/commits/master/stable.json
Click to expand...
Click to collapse
OK, after I installed Android again (with my older prepatched magisk)
Not sure what happened but now Magisk Manager 8.0.7 opens and says I have 20.2-11b7076a installed
of course as this combo should not exist, magisk Manager cannot see any modules (modules are there in /data/adb/modules and they do work, its just that Magisk Manager cannot see them installed, which means you can not easly delete them and you could install them over and over again, since Manager would not know that they are there)
So now I need to find a way to update to Magisk 21.4
So how would I do that (I tried the module install method before (I downloaded 21.4 from official github release pages) , but that just got me stuck into download mode again, so any other way, is there a patcher for computer maybe?
I mean I can only install the latest version, even if I disable internet, I cannot select a specific version
refer to post #8
Thanks, after spending 3hours to get into magisk I decided to share my procedure (because I forget it a lot)
FIrst: make sure your phones last state was power off (you can eather power off from red button or from recovery)
Then turn phone on and start holding power button + bixby + volume up, and count to 10 then release (not 11, 10, if you count to 11 you will get to recovery)
To try out if you are in magisk mode (without ruining your saved wifi passwords), you can plug the phone into the charger, if it turn on normaly, you are in magisk, if it shows battery charging, then you are not in magisk mode)
OK, I tried updating Magisk with https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
but for some wierd reason, it doesn't want to update, its stuck on 20.2-1
OK,. I tried installing Magisk Manager v7.4.1 and when launching it, it said that it patched dtbo.img and it needs reboot, so after I reboot, I am stuck on download mode again
It sayd: DT table header check fail
well, lets install Android 10 a third time
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
alecxs said:
wait, you're booting into recovery to get into Magisk? you can use Nemesis kernel to skip this.
https://forum.xda-developers.com/posts/81316371
Click to expand...
Click to collapse
Yes I am, but its allright, I am used to this
one day I will have to compile my own kernel anyway (to add some drivers to the phone)
Now I have to figure out why Magisk 21.4 won't install
I tried patching my AP file with it, but no matter what I do, I cannot get into it for some reason? (even my trust and tried method does not get me into it, while it got me into 20 all the time)
Is this version broken?
Whats the latest magisk version that still supports Magisk Hide (usefull thing that always worked for me)
With Nemesis kernel no need for button dance, it boots straight into Magisk. Magisk Hide exist up to v23 but there is also unofficial Magisk v25
[Discussion] Magisk Delta - Another unofficial third-party Magisk fork
This is not an officially supported topjohnwu project. If you are looking for official Magisk source, please go to this page Introduction Custom Magisk fork by HuskyDG. Sync with official Magisk adding back MagiskHide...
forum.xda-developers.com
alecxs said:
only in case recovery and boot share the same partition, you will lose magisk after flashing TWRP (does not apply)
Click to expand...
Click to collapse
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
WoKoschekk said:
Magisk needs the ramdisk of the recovery/TWRP to patch it. If flashing a non-prepatched image you will lose root.
Click to expand...
Click to collapse
Yea, I discovered that already
Now I am trying to get it back and failing
UPDATE: after installing Magisk 23 (last version that has Magisk Hide), prepatching AP file, and flashing it like 10th time, I finaly have root
Do I dare to try TWRP again? (I guess I need to prepatch it with Magisk before I install it with odin? (but which file do I install there are 2 files provided (twrp-3.4.0-2-beyond2lte.img.tar or twrp-3.4.0-2-beyond2lte.img)?
patch the tar file