Related
How to install TWRP after Magisk?
I have a OnePlus 6 running Oxygen OS 9.0 and I managed to install Magisk by obtaining the stock boot image and using the magisk manager app to patch it to include magisk, then I flashed the patched boot.img using fastboot and ADB.
The reason I did it this way is that every time I tried to boot with twrp.img in order to flash twrp.zip, I would run into a screen saying Qualcomm CrashDump Mode and TWRP wouldn't boot.
Now I want to install TWRP and I was wondering if there is any way of doing it by using Magisk, so I wouldn't have to boot twrp.img.
Any help would be greatly appreciated.
Same problem here. Already tried to boot every version of TWRP without success.
abrahammurciano said:
How to install TWRP after Magisk?
I have a OnePlus 6 running Oxygen OS 9.0 and I managed to install Magisk by obtaining the stock boot image and using the magisk manager app to patch it to include magisk, then I flashed the patched boot.img using fastboot and ADB.
The reason I did it this way is that every time I tried to boot with twrp.img in order to flash twrp.zip, I would run into a screen saying Qualcomm CrashDump Mode and TWRP wouldn't boot.
Now I want to install TWRP and I was wondering if there is any way of doing it by using Magisk, so I wouldn't have to boot twrp.img.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
James Blode said:
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
Click to expand...
Click to collapse
But there's no button to flash, I open the app, select flash recovery, select device, but theres no button to flash it.
See screenshot
do you have fastboot and adb installed on your computer? I assume so as you have oem unlocked to flash magisk, correct?
Copy the TWRP file that ends with .img to your desktop
if so, open a command prompt (windows key +R and type cmd press enter)
type "cd desktop" without quotes and press enter
type fastboot boot "twrp.img" (whatever the file name actually is)
Congrats, you are now in TWRP. But wait, there's more! if you reboot to system or other wise leave TWRP at this point you will revert back to stock. to flash recovery onto your device permanently, install the TWRP.ZIP (The ZIP is IMPORTANT) as it changes the boot on the OP6 to have the TWRP image (oh, by the way, there is no recovery partition on OP6 like previous devices [Thanks A/B partition!])
Now you can reboot to your hearts content. remember if you update OOS, you will lose the custom recovery, so flash the TWRP.zip after every update!
Denkai said:
do you have fastboot and adb installed on your computer? I assume so as you have oem unlocked to flash magisk, correct?
Copy the TWRP file that ends with .img to your desktop
if so, open a command prompt (windows key +R and type cmd press enter)
type "cd desktop" without quotes and press enter
type fastboot boot "twrp.img" (whatever the file name actually is)
Congrats, you are now in TWRP. But wait, there's more! if you reboot to system or other wise leave TWRP at this point you will revert back to stock. to flash recovery onto your device permanently, install the TWRP.ZIP (The ZIP is IMPORTANT) as it changes the boot on the OP6 to have the TWRP image (oh, by the way, there is no recovery partition on OP6 like previous devices [Thanks A/B partition!])
Now you can reboot to your hearts content. remember if you update OOS, you will lose the custom recovery, so flash the TWRP.zip after every update!
Click to expand...
Click to collapse
Yes I have fastboot and ADB on my computer (Linux btw), and as I mentioned it the first post, I already tried that, except that instead of booting into TWRP after "fastboot boot twrp.img" I got to a screen saying Qualcomm CrashDump mode (see attached image (the image might not be exactly the same as mine, I found that on the internet because I don't have my computer to reproduce it now)).
super odd. maybe your boot image is corrupt? still doesn't explain why fastboot boot isn't working though... Try bluSpark's TWRP image. it's a solid build and I am not having issues with it.
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page17
or you can also try swapping to the other partition by typing 'fastboot --set-active=_a' (or fastboot --set-active=_b) and booting to that recovery.
if that doesn't work for ya, try and restore stock via fastboot is my only suggestion:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
[/COLOR]
abrahammurciano said:
Yes I have fastboot and ADB on my computer (Linux btw), and as I mentioned it the first post, I already tried that, except that instead of booting into TWRP after "fastboot boot twrp.img" I got to a screen saying Qualcomm CrashDump mode (see attached image (the image might not be exactly the same as mine, I found that on the internet because I don't have my computer to reproduce it now)).
Click to expand...
Click to collapse
I wonder if this problem has been solved? After having Root without TWRP since last year, I decided to flash TWRP now because I miss having a Nandroid backup. But just like op, right after I type in "fastboot boot TWRP.img", I end up with that Qualcomm crash dump error, resulting in a fastboot boot loop every time I restart the phone. My only recourse is to use the MSM flash tool that reflashes everything and returns the phone into factory stock. In the process wiping out all my data. I don't think there's anything corrupted
EDIT: the problem wasn't the procedure; it was the damned bootable TWRP .img files. I downloaded different TWRP.img versions, and they all failed to flash into temporary TWRP, except for this one that I found here: https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ You can use this bootable .img to flash any TWRP version compatible with your device
Does it work for Android 10?
oneplus 6 running oxygen os beta 30 with magisk 20.1 without twrp
Borat38 said:
[/COLOR]
I wonder if this problem has been solved? After having Root without TWRP since last year, I decided to flash TWRP now because I miss having a Nandroid backup. But just like op, right after I type in "fastboot boot TWRP.img", I end up with that Qualcomm crash dump error, resulting in a fastboot boot loop every time I restart the phone. My only recourse is to use the MSM flash tool that reflashes everything and returns the phone into factory stock. In the process wiping out all my data. I don't think there's anything corrupted
EDIT: the problem wasn't the procedure; it was the damned bootable TWRP .img files. I downloaded different TWRP.img versions, and they all failed to flash into temporary TWRP, except for this one that I found here: https://drive.google.com/open?id=1CJoBQ5ZuAExv27XLWwLMFYfHoLEu5YFJ You can use this bootable .img to flash any TWRP version compatible with your device
Click to expand...
Click to collapse
Please I need TWRP for Blackview BV9600 pro please share with me if you have a link to a webpage I may find it
James Blode said:
If you have magisk manager with working root.... Then YES you can.... Just download Official TWRP app from GPlay... Open it give root permissions and follow the onscreen instructions.... Thats it...and yes use the zip not the img file
Click to expand...
Click to collapse
Hello I'm having magisk root access and official TWRP app but can't use it for NAndroid backup, how can I use the app for backup and fishing custom ROM?
Hi all,
I've tried different methods to apply the November OTA to my Pixel 3, but so far none has worked seamlessly. Here's what I've tried so far:
- TWRP install the full OTA from Google (fails with a timestamp error)
- sideloading the full OTA from Google (same timestamp error)
- using topjohnwu's suggestion from his Magisk GitHub, which in short temporarily unroots the phone to allow the regular OTA process to take place, then before rebooting use Magisk Manager to patch the boot image of the spare partition (in this scenario, the phone won't even boot fully, it does boot but eventually restarts before hitting the lockscreen).
Is there any correct way to apply OTAs straight from the phone, without using a computer? If not, what would be the best way to update the Pixel 3?
Why not just flash-all (minus the -w) the system image?
sliding_billy said:
Why not just flash-all (minus the -w) the system image?
Click to expand...
Click to collapse
Because that requires a computer. I'd rather have a solution that would allow me to update on the fly; preferably, flashing an OTA through TWRP, which would then allow me to also reflash TWRP itself and Magisk. But, then again, this would simply be my optimal scenario - if it can't be done, I'll stick to flash-all.
GryphonBR said:
Because that requires a computer. I'd rather have a solution that would allow me to update on the fly; preferably, flashing an OTA through TWRP, which would then allow me to also reflash TWRP itself and Magisk. But, then again, this would simply be my optimal scenario - if it can't be done, I'll stick to flash-all.
Click to expand...
Click to collapse
Understood. I have just got so used to installing with the flash-all that is second nature. OTA through TWRP wasn't even working for a long time on the OG Pixel series, and putting the ~700 MB OTA file on the phone seemed like a waste since I only had a 32GB. Either way, permanent TWRP and Magisk are still installed directly from the phone and the TWRP .img fastboot boot needs a computer anyways so there is really no way to avoid the computer completely from end to end.
sliding_billy said:
Understood. I have just got so used to installing with the flash-all that is second nature. OTA through TWRP wasn't even working for a long time on the OG Pixel series, and putting the ~700 MB OTA file on the phone seemed like a waste since I only had a 32GB. Either way, permanent TWRP and Magisk are still installed directly from the phone and the TWRP .img fastboot boot needs a computer anyways so there is really no way to avoid the computer completely from end to end.
Click to expand...
Click to collapse
Well, if I could apply a full OTA directly from an already installed TWRP, then it'd be as simple as reinstalling TWRP and Magisk after the OTA. I was used to doing this on AOSP-based ROMs like Ressurection Remix or CyanogenMod/LineageOS.
GryphonBR said:
Well, if I could apply a full OTA directly from an already installed TWRP, then it'd be as simple as reinstalling TWRP and Magisk after the OTA. I was used to doing this on AOSP-based ROMs like Ressurection Remix or CyanogenMod/LineageOS.
Click to expand...
Click to collapse
No way to do it on a Pixel device (that I am aware of) since TWRP needs ran from outside of the OS. I seem to remember this coming up a bit when the OG Pixel first launched, and then it was just accepted to use fastboot boot.
sliding_billy said:
No way to do it on a Pixel device (that I am aware of) since TWRP needs ran from outside of the OS. I seem to remember this coming up a bit when the OG Pixel first launched, and then it was just accepted to use fastboot boot.
Click to expand...
Click to collapse
Yeah, there's something funky about how TWRP works with the A/B setup, because of the embedded recovery into boot and such, I assume. In any case, at this point it seems like I actually can get it updated using fastboot, so that'll have to do for the time being.
Thanks for bouncing off ideas with me!
GryphonBR said:
Yeah, there's something funky about how TWRP works with the A/B setup, because of the embedded recovery into boot and such, I assume. In any case, at this point it seems like I actually can get it updated using fastboot, so that'll have to do for the time being.
Thanks for bouncing off ideas with me!
Click to expand...
Click to collapse
Any time. Good luck!
GryphonBR said:
Because that requires a computer. I'd rather have a solution that would allow me to update on the fly; preferably, flashing an OTA through TWRP, which would then allow me to also reflash TWRP itself and Magisk. But, then again, this would simply be my optimal scenario - if it can't be done, I'll stick to flash-all.
Click to expand...
Click to collapse
Last I heard flashing OTA in twrp is broken, but even if it is fixed as soon as you flash the OTA you would lose TWRP. So you still need a computer to boot to TWRP to install it and/or root.
The key point is you have to boot to TWRP before you can flash either it or Magisk.
TonikJDK said:
Last I heard flashing OTA in twrp is broken, but even if it is fixed as soon as you flash the OTA you would lose TWRP. So you still need a computer to boot to TWRP to install it and/or root.
The key point is you have to boot to TWRP before you can flash either it or Magisk.
Click to expand...
Click to collapse
But that's what I was trying to do in the first place: booted from TWRP, apply OTA than flash TWRP and Magisk.
Which doesn't boot up, unfortunately. Not sure why.
GryphonBR said:
But that's what I was trying to do in the first place: booted from TWRP, apply OTA than flash TWRP and Magisk.
Which doesn't boot up, unfortunately. Not sure why.
Click to expand...
Click to collapse
Right, it is broke that way right now. It's hard to do because recovery where TWRP sits and boot are the same partition now. Touch one you touch both. So when you flashed the OTA you wiped TWRP out of recovery.
TonikJDK said:
Right, it is broke that way right now. It's hard to do because recovery where TWRP sits and boot are the same partition now. Touch one you touch both. So when you flashed the OTA you wiped TWRP out of recovery.
Click to expand...
Click to collapse
That's true, but when I'm using TWRP that's the runtime instance, not the installed one. So even if it gets overwritten by the OTA installation, it wouldn't matter since it would still be active at that moment.
I went nuts trying to figure out how to sideload the Nov OTA update through TWRP (was always easy with my OG Pixel) and then figured it doesnt work lol. Just did like was already suggested and took out the -w from the OTA and it went smooth after I updated my platform tools. This is the way I will do it from now on even if TWRP gets fixed which that looks unlikely.
Anyone do it without using TWRP?
Dbzruben said:
Anyone do it without using TWRP?
Click to expand...
Click to collapse
Yes, download the factory image and edit the flash-all batch file to remove the -w. Alternately, you can flash the stock boot image of your current os version and use the stock recovery to sideload the ota. Either way twrp will be replaced with the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app
Dbzruben said:
Anyone do it without using TWRP?
Click to expand...
Click to collapse
Method that worked for me (Fi Pixel3 (blueline), on Nov update, previously rooted via Magisk 17.3 Patch Boot Image File method) has been posted elsewhere & doesn't require TWRP installation. This assumes your device is already OEM Unlocked, has Developer Options/USB Debugging enabled/setup and you have the latest ADB/Drivers installed on your PC:
Download Dec Factory image (blueline-pq1a.181205.006)
Download TWRP 3.2.3-0 bootable image (twrp-3.2.3-0-blueline.img)
Download Magisk 17.3 zip
Download Magisk Manager 6.0.1 APK
Download Magisk Uninstaller (Canary)
Move TWRP bootable image file to ADB folder on PC (Win7 for me)
Unzip Dec image contents into ADB folder on PC
Find the Dec Boot.img file from extracted Dec image contents and copy it to Device Storage (Download folder)
Move Magisk Manager APK & Magisk Uninstaller zip to Device Storage (Download folder)
Modify the flash-all.bat file from the extracted Dec image contents location in Notepad (remove the -w) and save/overwrite the file back to the same directory & close Notepad
Open up command window from ADB folder on PC
adb reboot bootloader
fastboot boot twrp-3.2.3-0-blueline.img
"Install" the Magisk Uninstaller zip (via TWRP) wait for that to finish then reboot to bootloader.
(Re)Open a command window from your PC's ADB folder if you closed it.
flash-all (with the -w previously removed in Notepad). Wait for it to finish.
fastboot reboot (if it doesn't boot back to System once finished)
(Now in Android after 1st system boot) Check that Dec update has taken (Settings->System->About Phone->Build Number). No root.
To continue rooting Dec Image:
Install Magisk Manager APK (from Settings->Storage->Files->Download folder)
Open MM (ignore/dont install anything via MM if prompted). No root (as of yet).
In MM: Settings->Update Channel-> Change to "Beta"
Swipe down in MM to "Update" MM and "Install" v17.3 (17302.zip hotfix) via Patch Boot Image File method (using Dec Boot.img previously extracted and put into Device Storage (Download folder)).
Output Patched_Boot.img should now be located in Device Storage (Download folder).
Copy Patched_Boot.img file from Device Storage to ADB folder on PC
Open up a command window from ADB folder on PC again:
adb reboot bootloader
fastboot flash boot_a Patched_Boot.img
fastboot flash boot_b Patched_Boot.img
fastboot reboot
(assuming everything took) Open up MM, confirm Magisk 17.3 is installed & you have root
Re-Install all relevant MM modules (i did not have Active Edge module previously installed but heard there were issues with this module & root)
There's way more steps in that than needed and really doesn't address how to apply an ota to a rooted phone.
Line 13 is the only thing that would apply.
Sent from my [device_name] using XDA-Developers Legacy app
I cont root my pixel with Dezember Update. It stock on bootloop after i flashed the patched Magisk images.
Serial Kazama said:
I cont root my pixel with Dezember Update. It stock on bootloop after i flashed the patched Magisk images.
Click to expand...
Click to collapse
Have you tried to root using twrp and the magisk zip?
Sent from my [device_name] using XDA-Developers Legacy app
Find the solution, i forgot to use the Magist Uninstaller Zip before i root the new OTA. My fault. Thx anyway!
Hi there,
I´ve got an Update for my BV9900.
My Problem is, I can use this BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 Version
only for non rooted StockRom.
If I root my phone first, the Update will reboot TWRP Recovery and not his Flashmode.
If I Start the Update on an unrooted System it works.
But then I have the Problem, that I cannot root it anymore with my boot.img and twrp.img.
Can someone help me?
Kind Regards,
Chris
Please install the magisk manager app on your phone and check what if the ramdisk is "no" or "yes"
Ramdisk is Set "no"
dhchris said:
Ramdisk is Set "no"
View attachment 5267407
Click to expand...
Click to collapse
Here is a detailed guide
Install Magisk in Recovery and Root Android [No Ramdisk]
In this guide, we will show you how to install Magisk in the recovery partition and then root your Android device that doesn't have Ramdisk.
www.droidwin.com
dhchris said:
Hi there,
I´ve got an Update for my BV9900.
My Problem is, I can use this BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 Version
only for non rooted StockRom.
If I root my phone first, the Update will reboot TWRP Recovery and not his Flashmode.
If I Start the Update on an unrooted System it works.
But then I have the Problem, that I cannot root it anymore with my boot.img and twrp.img.
Can someone help me?
Kind Regards,
Chris
Click to expand...
Click to collapse
The problem is that your phone doesn't support 'ramdisk'. So to root, you now have to patch recovery.img
This will also disable DM verity
Hope i have understood your question properly. Very sorry if i have misunderstood it.
I tried it with my patched File before but get a bootloop.
I'll try it a seconds time with patching from my rooted System
Tab E said:
The problem is that your phone doesn't support 'ramdisk'. So to root, you now have to patch recovery.img
Magisk will also disable DM verity.
Click to expand...
Click to collapse
dhchris said:
I tried it with my patched File before but get a bootloop.
I'll try it a seconds time with patching from my rooted System
Click to expand...
Click to collapse
Once you solve the bootloop, before patching the img try the command
adb disable-verity
It might be DM verity that is stopping your phone to boot
I´ve got a TWRP Recovery image that I flashed.
Should I patch these or the recovery from stock Image?
The Stock that I have is the actual running version not the version that I want to update (come from OTA)?
adb disable-vertiy doesn´t work:
"verity cannot be disabled/enabled - USER build"
flashing the magisk-patched file generated in new version doesn´t work. bootloop
Do you know about a flashable BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 ?
dhchris said:
flashing the magisk-patched file generated in new version doesn´t work. bootloop
Do you know about a flashable BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 ?
Click to expand...
Click to collapse
Sorry I didn't see your earlier message. Did you flash the patched TWRP recovery or patched stock recovery?
patched stock from older rom. the newer rom is only on ota.
I´ve no files from this
EDIT:
The ways I tried it:
1. Stock system with installed magisk/TWRP - root works but many functions are buggy
so I tried to flash the new version by OTA. Download fine, but reboot to recovery (not flashing update)
2. Installed OTA (new version) on clean stock first rom.
Update flashing works fine but cannot install root (TWRP/Magisk from patched old recovery version)
Should I try to patch the older twrp(working on stock)?
Or should I disable the option in magisk "perserve force encryption"?
Or can I find any patchable file on running system?
Many questions :-(
When you flashed TWRP did you flash it to both partitions?
fastboot flash recovery_a twrp.img
fastboot flash recovery_b recovery.img
Things i="dhchris, post: 84768453, member: 598070"]
patched stock from older rom. the newer rom is only on ota.
I´ve no files from this
EDIT:
The ways I tried it:
1. Stock system with installed magisk/TWRP - root works but many functions are buggy
so I tried to flash the new version by OTA. Download fine, but reboot to recovery (not flashing update)
2. Installed OTA (new version) on clean stock first rom.
Update flashing works fine but cannot install root (TWRP/Magisk from patched old recovery version)
Should I try to patch the older twrp(working on stock)?
Or should I disable the option in magisk "perserve force encryption"?
Or can I find any patchable file on running system?
Many questions :-(
[/QUOTE]
I think try disabling that option. It sometimes causes bootloops
Tab E said:
When you flashed TWRP did you flash it to both partitions?
fastboot flash recovery_a twrp.img
fastboot flash recovery_b recovery.img
Click to expand...
Click to collapse
No, ok
Must try it a bit later.
Have to go out with the family
Try to flash the patched on a and b.
If doesnt work, will try flashing without encryption.
Okay flash recovery_a / recovery_b doesn´t work. command error.
flashing patched without verification works, but no twrp
dhchris said:
Okay flash recovery_a / recovery_b doesn´t work. command error.
flashing patched without verification works, but no twrp
Click to expand...
Click to collapse
OK. Now that you have root access, try flashing TWRP with the TWRP app. After flashing, Reboot to recovery from the TWRP app
TWRP-App in Rootmode crashes, trwp-app non rootmode showns not my device
Told me, device not rooted
Try https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en
App
had to reflash the stock system. bootloop...
now I tried it again.
Installed Stock, then updated it by OTA.
Installed MagiskManager and patched...
rebooted and flashed patched twrp.img in recovery.
installed the twrp manager... no root
MagiskManager shows me Installed N/A
dhchris said:
had to reflash the stock system. bootloop...
now I tried it again.
Installed Stock, then updated it by OTA.
Installed MagiskManager and patched...
rebooted and flashed patched twrp.img in recovery.
installed the twrp manager... no root
Click to expand...
Click to collapse
Do you have twrp? If yes flash the magisk zip. By installing twrp, you are removing the root access gains by patching the stock recovery.
So, backround is, I want to use AFWall+, which requires root, which I would like to use Magisk for.
In order to get Magisk I need TWRP, I learned so far.
I run LOS 18.1 and I used the lineage recovery/fastboot to flash it (according to the offical LOS-guide).
Changing the recovery is not the easiest thing for me.
Found this thread: https://forum.xda-developers.com/t/from-lineage-recovery-to-twrp-recovery.4253669/
but this seems to be very Samsung specific using Odin (I use a Pixel 4)
I also tried this guide: https://www.droidwin.com/boot-into-recovery-from-fastboot-mode/
but this just "deleted" my OS.
This is why I will be asking a few questions prior starting a new attempt, so please bear with my incompetence
At TWRP I read, I have to install a LZMA ramdisk kernel in order to get TWRP (https://twrp.me/google/googlepixel4.html).
I would go for elementalx, assuming it does support lzma.
From here things are getting tricky for me.
TWRPs guide tells me to get the kernel first, at Elementalx I get the instructions to use TWRP to install
It does say however its not neccessary to install TWRP permanently, but I would like to, because no matter what I want to do with my phone it requires TWRP. So I would like to change the recovery permanently.
The easiest way to do all of this seems to be this guide: https://elementalx.org/how-to-install/
But that will not change my recovery permanently...
What I would do (using a videoguide, because you know, I'm a noobish newbie):
1. Download TWRP img + zip, Magisk zip, Elementalx zip to my fastboot folder
2. Copy the Zips of TWRP, Magisk and Elementalx to my device
3. On my PC -> in the fastboot folder I run cmd as administrator
4. boot into bootloader
5. using cmd -> fastboot boot twrp.img
6. using TWRP -> flash the custom kernel
7. using TWRP -> flash TWRP
8. check if TWRP was proper installed: in TWRP -> boot -> recovery
hopefully the recovery was replaced
9. using TWRP - > flash Magisk
10. reboot
Would anyone please tell me if this will work?
Is there anything I need to do to avoid horrible things to happen?
This is not a request to blame something that could happen on someone afterwards. I just want to minimize the risk...
You can just flash the kernel from fastboot no twrp needed. Just fastboot flash boot boot.img.
You can have magisk patch a boot image then flash it from fastboot as mentioned above.
Usually its just recommended to fastboot boot twrp.img instead of flashing it to the actual device incase you want to revert back and install an OTA.
You can also just download the magisk apk from the device to patch the boot image, flash kernel from fastboot, then reboot with root and have magisk finish doing what it needs to do.
Thank you.
TWRP got stuck booting: I see the logo, "teamwin" and the version used 3.5.2_10-0
Everything was up to date, I'll try it again with an older version of TWRP.
Well, I dont know how to boot into LOS. It just froze on the mentioned screen.
Has anyone a idea what to do?
CodyF86 said:
You can just flash the kernel from fastboot no twrp needed. Just fastboot flash boot boot.img.
You can have magisk patch a boot image then flash it from fastboot as mentioned above.
Usually its just recommended to fastboot boot twrp.img instead of flashing it to the actual device incase you want to revert back and install an OTA.
You can also just download the magisk apk from the device to patch the boot image, flash kernel from fastboot, then reboot with root and have magisk finish doing what it needs to do.
Click to expand...
Click to collapse
Ok, I tried it my way - it wont work (of course). Maybe TWRP is still not supported for Android 11.
Now I'll try it your way (thx again).
In order to flash the kernel, I'll have to unzip the elementalx file, I assume. And boot the avaible image, which is called "dtbo.img".
I'll give this a go...
CodyF86 said:
You can just flash the kernel from fastboot no twrp needed. Just fastboot flash boot boot.img.
You can have magisk patch a boot image then flash it from fastboot as mentioned above.
Usually its just recommended to fastboot boot twrp.img instead of flashing it to the actual device incase you want to revert back and install an OTA.
You can also just download the magisk apk from the device to patch the boot image, flash kernel from fastboot, then reboot with root and have magisk finish doing what it needs to do.
Click to expand...
Click to collapse
fastboot flash boot boot.img did not work. I renamed the file to boot.img (did not mention this before).
Tried it twice, but nothing worked afterwards, not even recovery and I was not able to turn the device off.
Had to flash LOS again.
I also tried flashing the kernel using sideload while flashing the rom again.
Sideload did work, BUT the wifi was not working at all.
I dont want to bother you, but might there be another way?
I might have found something:
[VERY EASY GUIDE] ADB/FASTBOOT/RECOVORY *FULL GUIDE* for flashing ROMs, Kernels, APKs
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details. This procedure is designed to be EXTREMELY EASY and for people using...
forum.xda-developers.com
uppon2 said:
That is all. Keep in mind things like wifi might not work if you forget to flash the kernel modules! - Just be sure it is always a 2 step process.
Click to expand...
Click to collapse
This is what I am experiencing when using sideload. It does install the kernel, but wifi wont work. I guess I do need a working (permanently or temporarly) recovery.
caraman said:
I might have found something:
[VERY EASY GUIDE] ADB/FASTBOOT/RECOVORY *FULL GUIDE* for flashing ROMs, Kernels, APKs
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details. This procedure is designed to be EXTREMELY EASY and for people using...
forum.xda-developers.com
This is what I am experiencing when using sideload. It does install the kernel, but wifi wont work. I guess I do need a working (permanently or temporarly) recovery.
Click to expand...
Click to collapse
Wifi is usually a kernel module that gets loaded through an init script on boot. It's possible to build the wifi module built-in to the kernel, which makes it so it doesn't have to load separately through an init script.
So if youre not using the stock kernel you'd have to ask whoever makes the kernel you are using.
caraman said:
So, backround is, I want to use AFWall+, which requires root, which I would like to use Magisk for.
In order to get Magisk I need TWRP, I learned so far.
I run LOS 18.1 and I used the lineage recovery/fastboot to flash it (according to the offical LOS-guide).
Changing the recovery is not the easiest thing for me.
Found this thread: https://forum.xda-developers.com/t/from-lineage-recovery-to-twrp-recovery.4253669/
but this seems to be very Samsung specific using Odin (I use a Pixel 4)
I also tried this guide: https://www.droidwin.com/boot-into-recovery-from-fastboot-mode/
but this just "deleted" my OS.
This is why I will be asking a few questions prior starting a new attempt, so please bear with my incompetence
At TWRP I read, I have to install a LZMA ramdisk kernel in order to get TWRP (https://twrp.me/google/googlepixel4.html).
I would go for elementalx, assuming it does support lzma.
From here things are getting tricky for me.
TWRPs guide tells me to get the kernel first, at Elementalx I get the instructions to use TWRP to install
It does say however its not neccessary to install TWRP permanently, but I would like to, because no matter what I want to do with my phone it requires TWRP. So I would like to change the recovery permanently.
The easiest way to do all of this seems to be this guide: https://elementalx.org/how-to-install/
But that will not change my recovery permanently...
What I would do (using a videoguide, because you know, I'm a noobish newbie):
1. Download TWRP img + zip, Magisk zip, Elementalx zip to my fastboot folder
2. Copy the Zips of TWRP, Magisk and Elementalx to my device
3. On my PC -> in the fastboot folder I run cmd as administrator
4. boot into bootloader
5. using cmd -> fastboot boot twrp.img
6. using TWRP -> flash the custom kernel
7. using TWRP -> flash TWRP
8. check if TWRP was proper installed: in TWRP -> boot -> recovery
hopefully the recovery was replaced
9. using TWRP - > flash Magisk
10. reboot
Would anyone please tell me if this will work?
Is there anything I need to do to avoid horrible things to happen?
This is not a request to blame something that could happen on someone afterwards. I just want to minimize the risk...
Click to expand...
Click to collapse
Magisk should not be that complicated. All the hard work has been done and can be found in Magisk documentation. There are install instructions for just about any type device and if there is LOS for your device I'm sure it is covered. The latest Magisk is not TWRP flashable the same way as it used to be and newer devices often don't have ramdisk in boot image and root is achieved thru recovery instead. You referenced several threads and guides but no indication of Magisk instructions. Read the Magisk installation instructions for your device type, they're not just suggestions, they work.
Hi,
with the latest Magisk update I noticed the missing Magisk Hide and SafetyNet fix. So I decided to go back to Magisk 23. After a few unsuccessful attempts, I don't know what happened but now my phone is no longer rooted. So I tried some usual methods to re-root the device but nothing to do, still no root
I have used boot.img patching way with Magisk but when I send ADB command "fastboot flash boot magisk_patched.img", it seems to work fine but after reboot there is no root
So I tried the other method by booting the device with patched boot.img using ADB ("fastboot boot magisk_patched.img") then I open Magisk Manager but in the installation section there is no "direct install" option as it should be.
I also tried flashing Magisk.zip via TWRP as I did long ago and TWRP seems to do the job well but after rebooting again no root...
Any suggestions?
even though you don't have root, i suggest flashing the stock boot.img and then rebooting to be really sure that root has been removed. and then flash the magisk patched boot.img.
are you using the latest adb and fastboot? you can get the latest from here. https://developer.android.com/studio/releases/platform-tools
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.
altwu said:
fyi, i just updated to magisk 24.1 and enabled zygisk. i'm using @kdrag0n's universal safetynet fix. google pay works. i don't have any other apps that i need to hide magisk from.
Click to expand...
Click to collapse
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.
¿GotJazz? said:
How did you get this to work? I am on the latest OP7P OOS (11.0.5), and I haven't been able to get my phone rooted, even though I installed the boot.img I patched using Magisk v24.1.
Click to expand...
Click to collapse
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?
altwu said:
i'm running 11.0.5.1.GM21AA. i was already rooted with magisk v23, so i updated the magisk app to 24.1, and did a direct install to update root to 24.1.
but for any os upgrades, i download the firmware zip from my phone to my pc before installing. i extract the boot.img from the zip with payload dumper, patch it with magisk, and then flash it via fastboot. this way i know for sure that i'm using the correct boot.img. if you need the firmware zip to extract the boot.img from, you can use the oxygen updater app to download it.
did you use the stock boot.img for patching?
Click to expand...
Click to collapse
Yes, I used the stock boot.img that I extracted from the 11.0.5.1 file that was downloaded as the normal OTA update from OnePlus. I patched that boot image with Magisk v24.1 that was already installed on my OP7P.
Then, I flashed that Magisk patched boot.img using fastboot onto both A and B slots (I switched slots by booting into TWRP 3.6, since I didn't see a way to switch slots with the now-loaded OnePlus Recovery Mode).
When I rebooted through the patched image, the phone came up (which is good!), but Magisk says that I don't have root (which is bad!). I haven't figured out how to fix that.
Could you PM me your patched boot.img? I could try flashing that to see if my OP7P acts any differently.
Thanks!
OK, I'm 100% positive that Magisk v24.1 patched my OP7P OOS 11.0.5.1 boot.img properly.
I extracted the 11.0.5.1 boot.img file from the OTA image that was in my .Ota folder from my phone. I extracted boot.img from the payload.bin file using two different methods of payload-dumper. Both boot.img files had the same SHA-512 checksums, so they were identical.
I also downloaded a copy of the Magisk v24.1 patched boot.img from the intenet and compared it to my Magisk v24.1 patched boot.img file. Again, the SHA-512 checksums matched for the two patched files, so I am sure that I have a properly patched boot.img file.
Note that my OP7P has loaded the full OOS 11.0.5.1 Stock image, so I currently have the OOS Recovery Mode and I do not have TWRP Recovery Mode.
Maybe I am doing something else wrong during my installation that is keeping me from getting root?
Here is the process I followed with my patched boot.img file:
I boot into Fastboot Mode
In Fastboot Mode, I go into TWRP Recovery Mode by typing: fastboot boot twrp-3.6.0_11-0-guacamole.img
After rebooting into TWRP Recovery, I installed the 11.0.5.1 OTA by doing an Install > Browse to the .Ota folder for the OTA .Zip file.
After the OOS 11.5.0.1 OTA installed, I rebooted back to Fastboot Mode (before booting normally) by selecting: Reboot > Slot A > Home > Reboot > Bootloader
Once I am back into Fastboot Mode, I type: fastboot flash boot magisk_patched_boot.img
In Fastboot Mode, I type: fastboot reboot
After I have rebooted back to normal mode, Magisk v24.1 is already installed and I don't do any updates to that. When opening Magisk, my screen flashes a couple of times before giving me a Toast pop-up that Magisk was denied Super User access. When I look at the Magisk App screen, it says that the App is installed, but that Magisk is not installed.
Are there any steps that I am missing?
Well, I finally got OOS 11.0.5.1 rooted with Magisk v24.1.
I ended up wiping my data and installing a fresh install of OOS 11.0.5.1 (Not sure if this is necessary, but I skrood up along the way and had to wipe as a result).
The one thing that was different this time around was that I disabled encryption/lock before flashing the Magisk-v24.1 patched boot image. I suspect that was what helped me make it to the finish line this time.
Good luck out there!
¿GJ?
i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!
altwu said:
i'm glad to hear that you got it figured out. sorry for not responding sooner with a patched boot image.
i don't use twrp, so my method of upgrading and patching is different than yours.
my only guess as to why you were having trouble before is maybe you were flashing the magisk patched boot image to the wrong slot. if you run into a similar problem in the future, you can try flashing the magisk patched boot image to both slots. but it's a moot point now. enjoy your finally rooted phone!
Click to expand...
Click to collapse
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?
¿GotJazz? said:
Hey, @altwu - I used TWRP to switch between slots when flashing the Magisk patched boot images. I had patched both slots (as best as I could tell)
If you don't use TWRP, how did you switch between slots prior to flashing the patched boot images?
Click to expand...
Click to collapse
you can use fastboot to switch slots.
fastboot --set-active=a or b
i don't know if it's necessary, but i reboot the bootloader with "fastboot reboot bootloader" after switching slots.
i've never tried this, but you can also specify what slot when running fastboot flash, like "fastboot flash boot magisk_patched.img --slot a".
check out "fastboot help" to see the different options.
i haven't had to play around with slots though. when an update is available, i'll download the zip to a computer and then go through the normal update process via the os. after the update is done, the phone reboots and the correct active slot is set.
Thanks for the feedback, @altwu.
I am having issues getting my SMS notification sound working on my fresh(er) 11.0.5.1 installation. I haven't seen anybody respond back yet, and I am beginning to suspect it's just a problem on my OP7P. If I don't see anybody responding back by tomorrow, I'll assume it's "just me".
I am thinking about doing a total wipe again to see if it will clear up the issue I am seeing. I will end up trying your installation route this time to see if it helps at all.