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?
Related
XZ Dual Recovery is not yet compatible with Marshmallow and because of this I was forced to unlock the BL. Are there any recovery that we can use as of this moment? It seems that the development section for this is not so active.
infinitylook said:
XZ Dual Recovery is not yet compatible with Marshmallow and because of this I was forced to unlock the BL. Are there any recovery that we can use as of this moment? It seems that the development section for this is not so active.
Click to expand...
Click to collapse
I saw that there is a prerooted 6.0.1 with only TWRP recovery installed, not dualrecovery. Can you guide me on steps to get from official 6.0.1 to root status on an unlocked bootloader? I can't do anything to go back to previous firmwares and it seems I have to unlock as the only way to get anywhere.
GigaSPX said:
I saw that there is a prerooted 6.0.1 with only TWRP recovery installed, not dualrecovery. Can you guide me on steps to get from official 6.0.1 to root status on an unlocked bootloader? I can't do anything to go back to previous firmwares and it seems I have to unlock as the only way to get anywhere.
Click to expand...
Click to collapse
I tried flashing the TWRP from the site of TWRP but it results in blank screen. Also XZDR is not compatible with Marshmallow.
Did you already backup your TA? You can only do this by obtaining root so it is a must to flash previous FW (KK or LP) then root and backup your TA partion unless you don't care for your DRM keys.
1. Go to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and follow instructions to unlock your bootloader. Alternatively you can use flashtool (just search here in the forums).
2. Download a TWRP image of Scorpion Windy (Z3 Tablet Wifi) https://twrp.me/devices/sonyxperiaz3tabetcompact.html
3. Download older versions of SuperSU. Systemless root doesn't seem to work with Xperia Stock so you go the system way, older versions are preferred. Will attach the zip I used.
3. Flash MM FW by Flashtool, do initial setup.
4. Boot into fastboot, fastboot the TWRP image you downloaded. Reboot and you should be in recovery
5. Flash the SuperSU. Flash also the RIC defeat zip. Reboot and you'll notice your just in TWRP.
6. Force shutdown.
7. Open flashtool flash the mM FW but only kernel and the FotaKernel, dont wipe anything. Reboot. It should start.
That worked for me.
After you, need to install busybox from playstore and the SELinux Changer app
P.s I can't attach any file however you can find everything i mentioned (Zips) here at XDA and TWRP. I still need to enable init.d but I guess that's difficult with stock rom stock kernel. Oh, and you can install flashfire in substitute of your recovery. Be careful with flashing Zips after you have a stable system since you don't have recovery and therefore no Nandroid backup
infinitylook said:
I tried flashing the TWRP from the site of TWRP but it results in blank screen. Also XZDR is not compatible with Marshmallow.
Did you already backup your TA? You can only do this by obtaining root so it is a must to flash previous FW (KK or LP) then root and backup your TA partion unless you don't care for your DRM keys.
1. Go to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/ and follow instructions to unlock your bootloader. Alternatively you can use flashtool (just search here in the forums).
2. Download a TWRP image of Scorpion Windy (Z3 Tablet Wifi) https://twrp.me/devices/sonyxperiaz3tabetcompact.html
3. Download older versions of SuperSU. Systemless root doesn't seem to work with Xperia Stock so you go the system way, older versions are preferred. Will attach the zip I used.
3. Flash MM FW by Flashtool, do initial setup.
4. Boot into fastboot, fastboot the TWRP image you downloaded. Reboot and you should be in recovery
5. Flash the SuperSU. Flash also the RIC defeat zip. Reboot and you'll notice your just in TWRP.
6. Force shutdown.
7. Open flashtool flash the mM FW but only kernel and the FotaKernel, dont wipe anything. Reboot. It should start.
That worked for me.
After you, need to install busybox from playstore and the SELinux Changer app
P.s I can't attach any file however you can find everything i mentioned (Zips) here at XDA and TWRP. I still need to enable init.d but I guess that's difficult with stock rom stock kernel. Oh, and you can install flashfire in substitute of your recovery. Be careful with flashing Zips after you have a stable system since you don't have recovery and therefore no Nandroid backup
Click to expand...
Click to collapse
Well then, I knew what I should have done before I lost root. In any case, what certain DRM keys would I be losing on the tablet? I know the biggest commotion on the phones were the camera algorithms.
GigaSPX said:
Well then, I knew what I should have done before I lost root. In any case, what certain DRM keys would I be losing on the tablet? I know the biggest commotion on the phones were the camera algorithms.
Click to expand...
Click to collapse
You would lose camera algorithm (I don't care for that, it's a tablet and its pictures are bad from the start).
X-reality and display enhancements, sound and noise cancellation (This is i don't want to lose since i use mine mainly for graphic projects) and remote play. That's only what I remember, i don't know if I missed out something.
NO NEED TO UNLOCK THE BT, flash a MM prerooted zip you can make it yourself with prf you need the FTF, recroot and superSu.
Anyway if you still want unlock the bt backup the drm keys with backupta
dnnz said:
NO NEED TO UNLOCK THE BT, flash a MM prerooted zip you can make it yourself with prf you need the FTF, recroot and superSu.
Anyway if you still want unlock the bt backup the drm keys with backupta
Click to expand...
Click to collapse
That won't work and would cause bootloop. tried the latest supersu. anyway, i found the workaround and it's been working good now.
infinitylook said:
You would lose camera algorithm (I don't care for that, it's a tablet and its pictures are bad from the start).
X-reality and display enhancements, sound and noise cancellation (This is i don't want to lose since i use mine mainly for graphic projects) and remote play. That's only what I remember, i don't know if I missed out something.
Click to expand...
Click to collapse
Wow, yeah that's too dire for me to go forward to. I should've just stayed on lollipop since it was already what was best for me.
infinitylook said:
That won't work and would cause bootloop. tried the latest supersu. anyway, i found the workaround and it's been working good now.
Click to expand...
Click to collapse
But but but if many did that without problem including me, check the th "when is mm out"
dnnz said:
But but but if many did that without problem including me, check the th "when is mm out"
Click to expand...
Click to collapse
i willread on that. last timme i checked it out mostly devices are with sgp 612 (wifi) anyway thanks for the tip.
Can you give me the link on that thread? i checked the threads here on this device forum and they are for sgp 612 and 611 (wifi versions)
I have global Honor 9, updated to 8.0.0.379(C432), unlocked and rooted.
I read that Huawei rolled out an update which broke Magisk, does anyone know if the latest update is safe?
How can I tell if an update is safe to use?
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
mtvento said:
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
Click to expand...
Click to collapse
as opposed to version 8.0.0.379?
I currently have magisk and TWRP with no problem, is this problem you describe is new to the latest version?
Do you have a different custom ROM?
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
mtvento said:
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
Click to expand...
Click to collapse
So on EMUI9 there's no option of Root+Custom recovery?
So the options are either root or custom recovery?
Did I understand correctly?
Thank you
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
mtvento said:
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
Click to expand...
Click to collapse
That sucks big time.
What do you mean by "have to boot to recovery each time"? every time I restart the phone or turn it off and back on I must go through recovery?
I think I'll avoid EMUI9 and stick with EMUI8.
For some reason there are not much custom ROMs or honor 9
That is the last time I buy a non root friendly phone like Huawei/Xiaomi
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
buchman said:
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
Click to expand...
Click to collapse
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Clonimus said:
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Click to expand...
Click to collapse
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
buchman said:
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
Click to expand...
Click to collapse
When I do that it gives me 2 options, one is download a zip file (and then I need to install using TWRP, right?)
The other option is patch a boot image, and it lets me look for one. Is this option to patch a downloaded boot image and then I need to flash it? what do I do with this option?
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,
I have been using my p20lite with unlocked bootloader (via dcunlocker), twrp recovery and magisk for root access for quite a while. Then, magisk updated itself to the new system, and because i had to hide magisk to get banking working, somehow root is completely b0rked now, and magisk just doesnt work. Whenver an app needs secure, unrooted access to install, it says my device is rooted, yes whenever an app needs rooted access (like backup app) its complains about the system being unrooted.
Does anyone have suggestions to how to regain or reinstate default bootloader/recovery to erase magisk, or completely wipe the phone, WITHOUT losing unlocked bootloader? AFAIK, getting bootloader unlocked is nigh on impossible these days....
I've searched and searched and my google-fu - or lack hereof - hasn't been able come up with solid advice!
Thanks in advance!
The bootloader state is largely separate from software issues. I am not familiar with this particular device, but the principles remain the same.
Does Magisk report "Installer's and Ramdisk: "Yes"? If so, try this:
- Use Complete Uninstall in Magisk to remove and clean up the Magisk installation. Allow it to reboot your device.
- Your device will boot without root. If you have custom recovery, just reboot to recovery and reflash Magisk. If not, install Magisk, patch the boot image, then reboot to bootloader and flash the patched image.
Hope this helps.
madgabz said:
how to regain or reinstate default bootloader/recovery to erase magisk,
Click to expand...
Click to collapse
Are you on EMUI 9.1? Then simply flash stock recovery_ramdisk (in fastboot mode or in TWRP), download Here
madgabz said:
completely wipe the phone, WITHOUT losing unlocked bootloader
Click to expand...
Click to collapse
madgabz said:
(via dcunlocker
Click to expand...
Click to collapse
so you have BL unlocked code, right? This code is permanent, so you can unlock the bootloader whenever needed.
madgabz said:
completely wipe the phone
Click to expand...
Click to collapse
Via eRecovery & Wi-Fi .
V0latyle said:
The bootloader state is largely separate from software issues. I am not familiar with this particular device, but the principles remain the same.
Does Magisk report "Installer's and Ramdisk: "Yes"? If so, try this:
Click to expand...
Click to collapse
Nope, only Ramdisk, Installed/A/B, SAR all says: N/A or No
V0latyle said:
- Use Complete Uninstall in Magisk to remove and clean up the Magisk installation. Allow it to reboot your device.
Click to expand...
Click to collapse
I have Magisk app version 23, there is NO uninstall function/menu anywhere.
V0latyle said:
- Your device will boot without root. If you have custom recovery, just reboot to recovery and reflash Magisk. If not, install Magisk, patch the boot image, then reboot to bootloader and flash the patched image.
Click to expand...
Click to collapse
I guess, I'll have to extract the current bootimage... any smart way of doing it?
V0latyle said:
Hope this helps.
Click to expand...
Click to collapse
Just getting an answer from you made my day ) Thank You very much!!!