Related
For those wondering, the 08M update works fine with Chainfire's systemless boot image. I completely wiped the device, and manually installed each image via fastboot, then sideloaded the 2.56 supersu, and everything worked normally.
kibmikey1 said:
For those wondering, the 08M update works fine with Chainfire's systemless boot image. I completely wiped the device, and manually installed each image via fastboot, then sideloaded the 2.56 supersu, and everything worked normally.
Click to expand...
Click to collapse
So you just used the system less boot.img in place of the new one in the factory image?
elreydenj said:
So you just used the system less boot.img in place of the new one in the factory image?
Click to expand...
Click to collapse
Correct.
I did mine on the 08K and I get an update. From what I am reading, I need to flash the stock bootloader and stock recovery then do theupdate. Then reflash the TWRP recovery and systemless boot again. I guess I need to keep back up systemless recovery and boot folder and stock ones.
I am also reading that I can just flash the new system image. Downloaded the new rom, extracted it and now commands
fastboot flash radio (radioname).img
fastboot flash system (systemname).img
??????
Is xposed killing android pay for anyone on systemless root? I assume it would because it touches system files.
durag5 said:
Is xposed killing android pay for anyone on systemless root? I assume it would because it touches system files.
Click to expand...
Click to collapse
It stopped working for me once I installed exposed, even with no modules active. I could live with needing stock DPI, but I just decided android pay isn't worth staying so close to stock. I'd rather be free to mod my phone and just use a credit card.
kibmikey1 said:
For those wondering, the 08M update works fine with Chainfire's systemless boot image. I completely wiped the device, and manually installed each image via fastboot, then sideloaded the 2.56 supersu, and everything worked normally.
Click to expand...
Click to collapse
Will this allow you to have root (and xposed) on stock rom without touching system partition?
Can you provide the steps to go from completely stock to this?
This info is in the pinned thread already, section 6.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
There is also a boot.img for M in there.
skrowl said:
Will this allow you to have root (and xposed) on stock rom without touching system partition?
Can you provide the steps to go from completely stock to this?
Click to expand...
Click to collapse
If you are trying to keep android pay you will not be able to use Xposed. Best you can do right now is have root + android pay, but nothing more it seems. I am going to test out flashing a custom kernel (for double tap to wake) and see if I lose it again.
durag5 said:
If you are trying to keep android pay you will not be able to use Xposed. Best you can do right now is have root + android pay, but nothing more it seems. I am going to test out flashing a custom kernel (for double tap to wake) and see if I lose it again.
Click to expand...
Click to collapse
Like most people who have used NFC payments more than twice, I'm bored of it. I'm OK with losing Android Pay to get Xposed + Gravity Box.
Can you provide steps to do it from stock?
installing atm...
flash-all (minus -w) worked fine on my Wife's P3. Magisk 19.3 is working fine, and twrp-3.3.0-0-blueline installs (using ramdisk install method) and dycripts fine as long as you haven't done a full wipe since a couple of Google builds ago when a new install wouldn't decrypt.
public WiFi sign in issue not solved yet.
sliding_billy said:
flash-all (minus -w) worked fine on my Wife's P3. Magisk 19.3 is working fine, and twrp-3.3.0-0-blueline installs (using ramdisk install method) and dycripts fine as long as you haven't done a full wipe since a couple of Google builds ago when a new install wouldn't decrypt.
Click to expand...
Click to collapse
What is "using ramdisk install method" ?
fahmi182 said:
What is "using ramdisk install method" ?
Click to expand...
Click to collapse
That is the permanent TWRP install method that was mentioned a couple of months ago when TWRP said that they would no longer be doing the .zip installers soon. From the main screen in TWRP (after launching the fastboot boot .img), got to advanced and you will see a ramdisk install link. Use that to install the .img (make sure to put the .img on your phone before running it from fastboot) of TWRP permanently.
sliding_billy said:
That is the permanent TWRP install method that was mentioned a couple of months ago when TWRP said that they would no longer be doing the .zip installers soon. From the main screen in TWRP (after launching the fastboot boot .img), got to advanced and you will see a ramdisk install link. Use that to install the .img (make sure to put the .img on your phone before running it from fastboot) of TWRP permanently.
Click to expand...
Click to collapse
Have link for that?
fahmi182 said:
Have link for that?
Click to expand...
Click to collapse
It has been discussed on the P3 and P3XL TWRP forums, but here is the original article.
https://www.xda-developers.com/twrp-3-3-0-release/
No problem installing the July update and Magisk using my ol' pre-patch the boot image method. I've forgotten how to get the device certified in the Play Store now that you can't clear data for it anymore (it shows 0 storage used). I already have it hidden in Magisk. Does it just take some time to refresh the certified status?
CSX321 said:
No problem installing the July update and Magisk using my ol' pre-patch the boot image method. I've forgotten how to get the device certified in the Play Store now that you can't clear data for it anymore (it shows 0 storage used). I already have it hidden in Magisk. Does it just take some time to refresh the certified status?
Click to expand...
Click to collapse
The issue of not being able to clear Play Store cache and data (gray buttons) is likely caused by a Magisk module. It is for me on the 3XL, and in my case it is Edge Sense. Try disabling your modules and reboot. You should be able to clear data and re-enable your modules.
sliding_billy said:
The issue of not being able to clear Play Store cache and data (gray buttons) is likely caused by a Magisk module. It is for me on the 3XL, and in my case it is Edge Sense. Try disabling your modules and reboot. You should be able to clear data and re-enable your modules.
Click to expand...
Click to collapse
Ah, I'm using Edge Sense, too. Although since my earlier post I manually cleared the Play Store data with the package manager (pm clear com.android.vending). Now I guess I just have to wait for it to refresh the certified status (and my list of installed apps).
CSX321 said:
Ah, I'm using Edge Sense, too. Although since my earlier post I manually cleared the Play Store data with the package manager (pm clear com.android.vending). Now I guess I just have to wait for it to refresh the certified status (and my list of installed apps).
Click to expand...
Click to collapse
You can get the installed app list back (as well as any updates that aren't showing) by installing something from your library or just some random app. Delete if necessary of course. The certified status is just a matter of waiting. It'll show up randomly in a day or two most likely.
sliding_billy said:
That is the permanent TWRP install method that was mentioned a couple of months ago when TWRP said that they would no longer be doing the .zip installers soon. From the main screen in TWRP (after launching the fastboot boot .img), got to advanced and you will see a ramdisk install link. Use that to install the .img (make sure to put the .img on your phone before running it from fastboot) of TWRP permanently.
Click to expand...
Click to collapse
So use ramdisk method after. We can don't use fastboot direct into recovery?
Edemilorhea said:
So use ramdisk method after. We can don't use fastboot direct into recovery?
Click to expand...
Click to collapse
You still need to use the fastboot boot .img to even get into TWRP do the install with ramdisk. You do not need to permanently install TWRP though. You can still use fastboot to get into TWRP but leave stock recovery permanently installed. Many do that so they can sideload OTAs.
sliding_billy said:
You still need to use the fastboot boot .img to even get into TWRP do the install with ramdisk. You do not need to permanently install TWRP though. You can still use fastboot to get into TWRP but leave stock recovery permanently installed. Many do that so they can sideload OTAs.
Click to expand...
Click to collapse
If i install ramsisk, i can use magisk?
Twrp and magisk can in the phone at the same time?
Edemilorhea said:
If i install ramsisk, i can use magisk?
Twrp and magisk can in the phone at the same time?
Click to expand...
Click to collapse
Yes, the ramdisk is not something you are installing. It is simply the method that TWRP is using to install itself permanently. Of course, you can then use the permanent version of TWRP (or the fastboot .img version) to flash Magisk.
sliding_billy said:
Yes, the ramdisk is not something you are installing. It is simply the method that TWRP is using to install itself permanently. Of course, you can then use the permanent version of TWRP (or the fastboot .img version) to flash Magisk.
Click to expand...
Click to collapse
Sounds I still not use permanently Twrp, just use fastboot to into recovery enough.
I want to ask a few problems.
I use twrp flash root and magisk better than use patch boot.img?
If I root my phone and i will ota update in future. Just use magisk manager to uninstall magisk and restore factory boot.img?
And now google pay work on new one magisk?
Edemilorhea said:
Sounds I still not use permanently Twrp, just use fastboot to into recovery enough.
I want to ask a few problems.
I use twrp flash root and magisk better than use patch boot.img?
If I root my phone and i will ota update in future. Just use magisk manager to uninstall magisk and restore factory boot.img?
And now google pay work on new one magisk?
Click to expand...
Click to collapse
Using TWRP to root is much easier than patching boot.
If you take a monthly build, yes you will lose root. You don't need to uninstall anything though. Just run the TWRP .img and flash Magisk again. There are Magisk settings like app hides and such that are retained during the update since the are in user and not system. Uninstalling will cause you to have to redo that stuff.
Magisk does not in and of itself give you the ability to use Google Pay. There are a couple of threads on the Magisk page with a lot of information. I use the exact method spelled out in the OP of the thread that starts with [working] on both a Pixel 3 and Pixel 3 XL. There is always a game of cat and mouse with Google and certain methods, but this has been working for me for a few months.
https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
sliding_billy said:
Using TWRP to root is much easier than patching boot.
If you take a monthly build, yes you will lose root. You don't need to uninstall anything though. Just run the TWRP .img and flash Magisk again. There are Magisk settings like app hides and such that are retained during the update since the are in user and not system. Uninstalling will cause you to have to redo that stuff.
Magisk does not in and of itself give you the ability to use Google Pay. There are a couple of threads on the Magisk page with a lot of information. I use the exact method spelled out in the OP of the thread that starts with [working] on both a Pixel 3 and Pixel 3 XL. There is always a game of cat and mouse with Google and certain methods, but this has been working for me for a few months.
https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
Click to expand...
Click to collapse
OK And Want to know root and magisk is wrok on Q-BETA Too?
Edemilorhea said:
OK And Want to know root and magisk is wrok on Q-BETA Too?
Click to expand...
Click to collapse
Magisk is working with Q but TWRP is not yet, so you'd have to root with manually patched image. There are posts on the P3 and P3XL pages about how to manually patch to root. There does not seem to be an official solution for Google Pay yet. I don't see anything in Q that makes it worth me not waiting for all of the solutions to be created. They are on 4 of 6 test builds (public will likely coincide with Pixel 4 in the fall), so there is time.
sliding_billy said:
Magisk is working with Q but TWRP is not yet, so you'd have to root with manually patched image. There are posts on the P3 and P3XL pages about how to manually patch to root. There does not seem to be an official solution for Google Pay yet. I don't see anything in Q that makes it worth me not waiting for all of the solutions to be created. They are on 4 of 6 test builds (public will likely coincide with Pixel 4 in the fall), so there is time.
Click to expand...
Click to collapse
Really thanks your answer.
I think I still use PIE, and I will go to root my pixel 3 now, and to study how to Gpay work on Magisk 1.93 now
I saw a lot of person said to use SQL-Edit have to Gpay work on Rooted.
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)
Hey,
Has someone figured out how to root the phone after bootloader unlock? I saw some attempts in the GSI thread but it wolud be nice if somebody who done it publish a guide. [here or in the new thread]
This way it will be easier to find for future people to follow.
hi, i couldn't find a stock boot.img so far. seems we will have to wait some more time to be able to download latest firmware as full rom to get the boot.img, which we can then patch with magisk.
eagerly waiting for it, as i cannot hide my unlocked bootloader so far and some apps refuse to work now (also safetynet check fails)
juergenh99 said:
hi, i couldn't find a stock boot.img so far. seems we will have to wait some more time to be able to download latest firmware as full rom to get the boot.img, which we can then patch with magisk.
eagerly waiting for it, as i cannot hide my unlocked bootloader so far and some apps refuse to work now (also safetynet check fails)
Click to expand...
Click to collapse
You can use the Oxygen Updater app on google play to download the latest full rom. then use https://github.com/vm03/payload_dumper
to get the boot.img.
Manugamé said:
You can use the Oxygen Updater app on google play to download the latest full rom. then use https://github.com/vm03/payload_dumper
to get the boot.img.
Click to expand...
Click to collapse
Oxygen Updater says the Oneplus Nord 2 is not supported, and i couldn't find a Download of latest FullRom.
If you are already unlocked, download the boot image, patch with magisk etc Do you have to factory reset again?
moisthat said:
If you are already unlocked, download the boot image, patch with magisk etc Do you have to factory reset again?
Click to expand...
Click to collapse
That's the point....where and how to download the latest boot.img??
Bootloader is unlocked already.
That's why I want the latest full rom to extract it from that.
juergenh99 said:
That's the point....where and how to download the latest boot.img??
Bootloader is unlocked already.
That's why I want the latest full rom to extract it from that.
Click to expand...
Click to collapse
My reply was confusing, and I wasn't actually replying to you. Sorry about that. I don't know how or where to download the boot.img.
I am trying to ask the community if we need to factory reset again when we flash the patched boot.img. Or if the reset we did during unlock is the only reset needed.
moisthat said:
My reply was confusing, and I wasn't actually replying to you. Sorry about that. I don't know how or where to download the boot.img.
I am trying to ask the community if we need to factory reset again when we flash the patched boot.img. Or if the reset we did during unlock is the only reset needed.
Click to expand...
Click to collapse
unlocking the bootloader means to do a reset. flashing the boot.img does not cause a reset.
you just have root and working magisk after flashing and reboot
juergenh99 said:
unlocking the bootloader means to do a reset. flashing the boot.img does not cause a reset.
you just have root and working magisk after flashing and reboot
Click to expand...
Click to collapse
Well then, now I have joined you in the hunt for this bloody boot.img
HofaTheRipper said:
I am not respondible if you brick your device as there is no full rom download to revert all this.
i have done this:
- installed magisk on the phone and transfered the attached boot.img to the phone.
- patched it with magisk and transfered it to pc
Flashing:
- Unlock bootloader
- Reboot into bootloader
- Download https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
- `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`
- `fastboot flash boot magisk_patched_boot.img`
rebootet and root worked but wifi/bt was broken due some version conflict
Fix for wifi/bt for me was:
- unpack vendor.xz
- reboot to bootloader
- `fastboot reboot fastboot`
- `fastboot flash vendor vendor`
- reboot
My Build Version is DN2103_11_A.08.
Thanks to @phhusson for his help and for his files!
Click to expand...
Click to collapse
Found in this thread. Hope it will work for further updates.