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.
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?
Hi to all. I'm new in Honor world and I've stopped my Android experience with KitKat so I'm a little bit confused ...
I've read several guides (on XDA too) that that three steps to obtain root are unlock bootloader, flash TWRP via ADB and then install Magisk or SuperSU via TWRP. But in the thread on TWRP is clearly written that to install Magisk decryption is needed and to have decryption we must flash a kernel with encryption disabled in fstab. But no guide says anything about this step. Can someone explain me how encryption/decryption work doing a standard installation of TWRP ? Is needed a flash of a modified kernel ? And where find it ?
And another question (if it's not too much ). Since I don't need to install custom rom (I want root only to use some apps like Titanium) how can I make a backup of stock rom, boot.img, efs partition and all that can be useful to restore phone to the starting point if, by chance, I need Huawei warranty ?
Thanks a lot
Hi, apparently there's a way to get root on an encrypted system. Follow the rebrand guide and then flash supersu in TWRP via ADB sideload. It worked for me and a few others, there is no comment from the developers as of right now.
So basically in short follow this guide until you are finished with the TWRP section:
https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829
Then
- enter twrp
- adb sideload supersu
Afterwards follow the "rooting!" section with point 2
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
unvisigoth said:
Thank for your answer... I'd like to try to install Magisk instead of SuperSU. In several places is written that this should be right. I'll try....
Click to expand...
Click to collapse
The method is also working fine with Magisk. Let me know if you need help
zxz0O0 said:
The method is also working fine with Magisk. Let me know if you need help
Click to expand...
Click to collapse
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
unvisigoth said:
Finally done with a couple of hours of panic. This is the story if can be useful to someone...
Unlock bootloader....done TWRP install... done. Copy magisk (apk and zip) on phone than install apk without opening it. Reboot to recovery wipe all, factory reset. Trying to boot.....BOOTLOOP But I don't have installed Magisk zip. Only apk without opening it.
Nothing to do. Bootloop and then erecovery. I try to restore the backups previously done with TWRP. I restore boot and system partition. All wipes ...no luck. I don't know what has happened. While downloading full firmware to try to reinstall it I try to install magisk.zip. Install via TWRP. All wipes and then magically (it's such a case ) phone boots. Powered off and on several times no problem. Root (verified with root checker) ok.
I habe b100 release but I don't think to update to b130. I wait for Oreo...
The only two things that I can say are these: first TWRP even after flashing magisk gave an error (unable to mount system). Two while installing magisk it seems that magisk itself has patched something.
If someone has an explanation is welcome...
Click to expand...
Click to collapse
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
shiboby said:
So do you have some step-by-step instructions for someone who wants to unlock and root the phone with magisk?
Click to expand...
Click to collapse
Here what I have done:
Unlock bootloader
install adb drivers (find something that is right for your PC. For example minimal ADB found on XDA weren't suitable for me. Google adb drivers...). Open a command windows (shift+right click). If typing "adb devices" your phone is found that's ok
Enable usb debugging and oem unlock (or in other words disable FRP, factory reset protection)
Put the phone in fastboot mode ("adb reboot bootloader"). If all ok typing "fastboot devices" your phone is found
Type "fastboot oem unlock xxxxxxxx" (xxxxxxxx is the code provided by Huawey)
Bootloader unlocked
Flash TWRP
Download TWRP recovery for Honor 9 (link found on other thread on this forum)
Put the phone in fastboot mode
Type "fastboot flash recovery xxxxx.img" (where xxxx.img is the recovery downloaded)
Reboot phone directly in Recovery to avoid erecovery overwrite TWRP. Booting on TWRP let TWRP patch to avoid erecovery booting
Now here I've had some issues as said (read previous post). My tip is the following:
after rebooting in TWRP make all wipes then reboot again in TWRP
Install Magisk.zip (for me download here https://geekaxe.com/root-honor-9-twrp-bootloader-unlocking/)
Reboot recovery
All wipes
Reboot to system
If it's all OK you can install magisk.apk and you are rooted
I suggest after flashing TWRP to make backup of all partitions on external SD (for some reasons, maybe encryption, backup on internal storage gives error). Again I suggest to copy all files that you need (i.e. magisk files) on external sd before starting all.
Pay attention that if you update firmware after this procedure I think that you must repeat all. For me I remain on original firmware found on phone (B100). B130 seems to have some bugs, B120 doesn't seem improve much. Moreover all releases are 7.0 based. I wait for Oreo, hopefully in some custom rom!
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Zuzler said:
To add to this, a bootloop or two might be normal. Let it sit for a few minutes before considering re-flashing everything.
Thanks for your guide!
Click to expand...
Click to collapse
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
unvisigoth said:
You're right. But after 20 minutes of bootlops I've chosen another way....:laugh::laugh:
Click to expand...
Click to collapse
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
adriansticoid said:
So is it fixed?
Sent from my Honor 8 Pro using XDA Labs
Click to expand...
Click to collapse
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Observe and be careful man.
Sent from my Honor 8 Pro using XDA Labs
unvisigoth said:
Yes sure. As said previously installation of magisk.zip fixed the bootloop problem. I think (but I could be wrong) that installation of TWRP corrupted the boot partition and magisk fixed it. But it's only an hypothesis...
Click to expand...
Click to collapse
Which TWRP version did you use?
I had a similar problem after formatting all data with the OpenKirin TWRP 3.1.1 Perhaps its an issue with this TWRP release?
I was able to recover in similar circumstances by flashing a stock boot.img over fastboot. Based on this, it's looking like Magisk is really the way to go for rooting atm. Making sure to pull my twrp backup with adb this time though.
If I'm lucky enough to install magisk and not get a bootloop the safetynet always fails. Anyone got a valid method of actually getting magisk working fully?
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?
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
The waiting period to unlock the bootloader will be done this Friday, and I plan to install crDroid once it is over.
I would like to confirm that these are the right steps/order since it is my first time doing such a thing to a phone and I don't want to brick it. I don't have an SD card yet, so I will be using adb sideload
Install crDroid
1. Reboot phone in fasboot mode and plug it to computer
2. From computer terminal run: fastboot boot path/to/TWRP.img to boot into TWRP 3.5.2
3. Wipe > Swipe to Factory Reset
4. Advanced > adb Sideload
5. adb sideload path/to/ROM.zip
Install TWRP + microG + Magisk
6. Boot phone and set up crDroid
7. Transfer TWRP + microG + Magisk to phone storage
8. Reboot phone in fasboot mode
9. fastboot boot TWRP.img to boot again into TWRP 3.5.2
10. Install TWRP recovery to Ramdisk (Advanced > Install Recovery Ramdisk)
11. Flash microG (Install > microG.zip)
12. Flash Magisk (Install > Magisk.apk)
13. Reboot phone and install Magisk APK
14. Be done
Should I back up any partitions before doing this? Which?
Is the microG install for RN10 done by flashing zip or Magisk Module? Does it matter?
Too many steps there... till 5 it's good but "factory reset" doesn't do what you think it does, i.e, it does not delete your INTERNAL DATA (photos, documents/etc);
That means you can put Magisk/MicroG/twrp on your phone storage like now and flash it all after you flash CRDROID, then you reboot to recovery;
It won't be TWRP because the DEV dropped it from latest build but it doesn't matter (the recovery gets replaced with the ROM flash (from any ROM) because our device (mojito/sunny) does not have a recovery partition and the recovery is inside the BOOT partition), from there you click "apply update", select the zips you want to install and install them. (respect any order of the packages you want to install as always if there's any) .
Then you reboot the phone and install magisk apk.
I only used microG for Youtube Vanced and used their app to install it without problems, now i switched to the rooted method that replaces the YT app mostly without issues (after some tinkering)
I hope i clarified a few things for you.
By the way, there's no way these days to fully brick your device, you can flash any partition / ROM from fastboot mode which can't be disabled or bricken if your device has it (most do).
A good backup is nevertheless always recommended. (either for panicking reasons or for peace of mind) , also, disabling encryption is also recommended before changing ROM's/kernel's.
Ok, so to make sure I understood correctly: you are saying I can use the recovery included in crDroid to install TWRP to ramdisk, as well as Magisk and microG, correct? (avoiding step 9.)
How did you install microG this time over? Flashing or Module?
Yes, so I hear, but I'd rather not risk soft bricking it on my first try hahaha
Will def make a backup of system, vendor, etc with TWRP.
Thanks
FYI installing TWRP from linux didn't work for me, had to go windo*s :/
P.S.:
How did you install microG this time over?
Click to expand...
Click to collapse
On my side I'll tell you for sure once I'm out of fastboot lol ^^
but usually (if your rom accept signature spoofing) on all my other install i do it this way:
install magisk module fdroid privileged extension
install fdroid
install microg fdroid repository
install microg from fdroid
launch microg and check all the boxes (sometimes you need to install more components from fdroid if you want gps or to fake playstore and stuff like that)
syntheticdingo said:
Ok, so to make sure I understood correctly: you are saying I can use the recovery included in crDroid to install TWRP to ramdisk, as well as Magisk and microG, correct? (avoiding step 9.)
Click to expand...
Click to collapse
You can use the included recovery to flash anything you'd like, except TWRP (or any other recovery), for TWRP (if you really want it, you're mentioning it too much) you do fastboot boot twrp.img, inside i think in advanced options there's an option to install TWRP which installs it into ramdisk (if you use the one made for this phone 3.5.2 ofc)
syntheticdingo said:
How did you install microG this time over? Flashing or Module?
Yes, so I hear, but I'd rather not risk soft bricking it on my first try hahaha
Will def make a backup of system, vendor, etc with TWRP.
Thanks
Click to expand...
Click to collapse
I never installed microG because i don't use it, i only tried it once because the Youtube Vanced option without root which i used in the MIUI ROM before i got permission to unlock bootloader and rooting the device, then, i use pico gapps so i haven't found a need for microG, but there's gotta be a tutorial on how to install it if you search for it.
syntheticdingo said:
How did you install microG this time over? Flashing or Module?
Click to expand...
Click to collapse
So, yep, I confirm, that works :
LaMarMôt said:
install magisk module fdroid privileged extension
install fdroid
install microg fdroid repository
install microg from fdroid
launch microg and check all the boxes (install more components from fdroid if you want, backends, fake (or modded) playstore, etc.)
Click to expand...
Click to collapse
Sweet, will try it tomorrow if nothing goes sideways with the bootloader unlock
LaMarMôt said:
So, yep, I confirm, that works :
Click to expand...
Click to collapse
Yes, that worked for me. both times. I only have an issue with Signal saying there is not Play services installed and not showing up in CLoud messaging, even though all Self-check is marked and other apps show up there.
Reinstalled the ROM (got that bootloop bc I forgot to do the wipes/factory reset), but I still have the same issue. *sighs*
syntheticdingo said:
Yes, that worked for me. both times. I only have an issue with Signal saying there is not Play services installed and not showing up in CLoud messaging, even though all Self-check is marked and other apps show up there.
Reinstalled the ROM (got that bootloop bc I forgot to do the wipes/factory reset), but I still have the same issue. *sighs*
Click to expand...
Click to collapse
Hey
Yes it is an "issue" with Signal... not sure if it's due to g**gle, signal or microG... one sure thing is that Signal dev won't do anything about it, as they stated on github (and their forums too), for them either you have "working" play services (i.e. official from g**gle), either their app can fallback to a persistent websocket which apparently shouldn't consume that much more battery in the end.. but that idk), so there's no issue according to them... (they clearly don't give a lot of a f**k regarding foss community, same attitude since a long time towards fdroid and all...)
One workaround (waiting for a better solution) would be to first install Signal 4.59.8 (or previous versions), for example here https://signal-private-messenger.de.uptodown.com/android/versions, make sure it register well via micro (reboot insist and everything... but shouldn't have too), and then, update to last version.
Even if there's messages stating some problem with play service it should stay registered and it should receive messages without any problem (at least it works well for me).
(You could check molly, a little bit more secure fork of signal, and it's the same you can install previous version from here https://github.com/mollyim/mollyim-android/releases?after=v4.59.9-1, and at least you get updates trough fdroid, that's what i use)
On a side note, Signal is becoming more and more dodgy, they even launch their own ponzi own cryptocurrency, but (which really worries me) the source code of the server side is no longer public...(same problem for the forks of course as you have to go through signal servers)
Well it is a shame after all the efforts i took to make people I interact with move to signal that I will have to make them move to matrix (element is a nice client)... (and that time Elon won't help me...)
So yeah... hope i won't have to use signal for long... (i mean if it's just as bad as using wh**tsap, what's the point...?)
Cheers !
syntheticdingo said:
got that bootloop bc I forgot to do the wipes/factory reset
Click to expand...
Click to collapse
So, in the end, what would be the exact steps one has to reproduce in order to install CrDroid on an untouched (bootloader unlocked indeed) Redmi Note 10 to succeed from first shot ?
(I messed up badly and even had to use MiFlash... and i'm not even sure how i succeeded in the end lol... A/B is gave me a hard time I guess ^^)
LaMarMôt said:
So, in the end, what would be the exact steps one has to reproduce in order to install CrDroid on an untouched (bootloader unlocked indeed) Redmi Note 10 to succeed from first shot ?
Click to expand...
Click to collapse
Well, what worked for me was:
boot into fastboot and plug into pc
run fasboot boot TWRP.img
format data and wipe all but last two partitions (dalvik, metadata, data and internal storage)
then enable adb sideload
run adb sideload crdroid.zip (it will kinda fail/succeed at 47% on terminal/just after it gets to step 2 on phone for me)
reboot phone to system and set it up
transfer magisk, twrp.img microg/gapps to internal storage
reboot phone into fastboot again
and run fastboot boot TWRP.img again
and from there flash magisk.apk, microg/gapps
install recovery to ramdisk
then install magisk app when you boot
regrding magisk: for me, both times i did this, i had to reboot into recovery after doing all that and reflash Magisk a second time in order for it to fully complete the installation. you may have better luck
I will read your other post when I wake up
hope that does it for you
syntheticdingo said:
Well, what worked for me was:
boot into fastboot and plug into pc
run fasboot boot TWRP.img
format data and wipe all but last two partitions (dalvik, metadata, data and internal storage)
then enable adb sideload
run adb sideload crdroid.zip (it will kinda fail/succeed at 47% on terminal/just after it gets to step 2 on phone for me)
reboot phone to system and set it up
transfer magisk, twrp.img microg/gapps to internal storage
reboot phone into fastboot again
and run fastboot boot TWRP.img again
and from there flash magisk.apk, microg/gapps
install recovery to ramdisk
then install magisk app when you boot
regrding magisk: for me, both times i did this, i had to reboot into recovery after doing all that and reflash Magisk a second time in order for it to fully complete the installation. you may have better luck
I will read your other post when I wake up
hope that does it for you
Click to expand...
Click to collapse
Thanks a lot !
Actually, i did install everything already , but i'm confused how i succeeded lol (see here if you have nothing better to do ^^)
I guess the "step" i missed (or messed ) was the
format data and wipe all but last two partitions (dalvik, metadata, data and internal storage)
Click to expand...
Click to collapse
idk...
well, i was asking mostly for other users who would like to succeed on the first try (and probably for me next time...)
Thanks a lot !!!
Cheers!