https://mobile.twitter.com/topjohnwu/status/1077067871660855296?s=20
From the man himself.
Seems as though it's only a matter of time now.
https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/notes.md
Or boot into twrp and adb sideload magisk-release.zip.
I'll try later.
It is possible to root without recovery for Ota updates?
Supzztar said:
It is possible to root without recovery for Ota updates?
Click to expand...
Click to collapse
OTA updates will fail if root is detected.
zgomot said:
OTA updates will fail if root is detected.
Click to expand...
Click to collapse
Is this due to emui 9? Because in 8.1 I've had OTA updates without a problem. Even when rooted with magisk.
curtricias said:
Is this due to emui 9? Because in 8.1 I've had OTA updates without a problem. Even when rooted with magisk.
Click to expand...
Click to collapse
That's strange, I could never take OTA updates while rooted, on any EMUI.
Hi,
I try this "How to" from P20 PRO forum : p20-pro/guide-how-to-finally-root-emui9-t3883295 using P20 twrp_p20_0.1.img by Pretoriano80 here : p20/recovery-twrp-3-2-1-0-t3778585
It works fine, my P20 whith Pie UMUI9 is rooted.
Be carefull :
To have root working, at each start, you have to Boot your phone with holding vol-up button.
Regards
zgomot said:
That's strange, I could never take OTA updates while rooted, on any EMUI.
Click to expand...
Click to collapse
Has to do with the custom recovery not the fact that it was rooted
Titioz said:
Hi,
I try this "How to" from P20 PRO forum : p20-pro/guide-how-to-finally-root-emui9-t3883295 using P20 twrp_p20_0.1.img by Pretoriano80 here : p20/recovery-twrp-3-2-1-0-t3778585
It works fine, my P20 whith Pie UMUI9 is rooted.
Be carefull :
To have root working, at each start, you have to Boot your phone with holding vol-up button.
Regards
Click to expand...
Click to collapse
It is possible to root without custom recovery?
Titioz said:
Hi,
I try this "How to" from P20 PRO forum : p20-pro/guide-how-to-finally-root-emui9-t3883295 using P20 twrp_p20_0.1.img by Pretoriano80 here : p20/recovery-twrp-3-2-1-0-t3778585
It works fine, my P20 whith Pie UMUI9 is rooted.
Be carefull :
To have root working, at each start, you have to Boot your phone with holding vol-up button.
Regards
Click to expand...
Click to collapse
Wow. It's so easy.
Can't seem to flash modules, though, but having root on EMUI 9 is just great!
Supzztar said:
It is possible to root without custom recovery?
Click to expand...
Click to collapse
I don't know.
With this method, you need to patch a recovery_ramdisk image to boot the system with root access
And then, you can't access to twrp anymore with patched image (but anyway, for me, this twrp version does not work anymore with EMUI9 ! => touch screen doesn't work).
Regards
Yes!
curtricias said:
Yes!
Click to expand...
Click to collapse
could you tell me how to do that? thanks
Ducati87 said:
could you tell me how to do that? thanks
Click to expand...
Click to collapse
Download latest magisk build.
Manually change update channel to canary build
https://www.google.com/amp/s/forum....sk-canary-channel-bleeding-edge-t3839337/amp/
Install magisk : patch your recovery_ramdisk
Then reboot bootloader.
Fastboot flash recovery_ramdisk patched_boot.img
When reboot, hold volume up button. As if you want to go to recovery.
But in stead recovery ,your system will boot. And magisk is installed ?
curtricias said:
Download latest magisk build.
Manually change update channel to canary build
https://www.google.com/amp/s/forum....sk-canary-channel-bleeding-edge-t3839337/amp/
Install magisk : patch your recovery_ramdisk
Then reboot bootloader.
Fastboot flash recovery_ramdisk patched_boot.img
When reboot, hold volume up button. As if you want to go to recovery.
But in stead recovery ,your system will boot. And magisk is installed ?
Click to expand...
Click to collapse
what you mean for patch your recovery_ramdisk? thank you.
edit: could be compatible with this: https://forum.xda-developers.com/huawei-p20/how-to/magisk-root-t3777612
Ducati87 said:
what you mean for patch your recovery_ramdisk? thank you.
edit: could be compatible with this: https://forum.xda-developers.com/huawei-p20/how-to/magisk-root-t3777612
Click to expand...
Click to collapse
Did you ever root your device with magisk?
ducati8701 said:
Unfortunately no
Click to expand...
Click to collapse
I suggest that you first read about magisk. And especially how to use it.
When you root your device many things can go wrong and your device can end up bricked.
Problem
So did this on my p20 and all worked well untill some module is causing the phone not to boot. I can boot without magisk but there is no way now to disable the faulty module. even reflashed the modified recovery boot image and the modules are still stuck. Any idea where i can delete all the modules?
Grumps said:
So did this on my p20 and all worked well untill some module is causing the phone not to boot. I can boot without magisk but there is no way now to disable the faulty module. even reflashed the modified recovery boot image and the modules are still stuck. Any idea where i can delete all the modules?
Click to expand...
Click to collapse
Remove magisk. Then reinstall magisk. Should work.
Villa Curtricias said:
Remove magisk. Then reinstall magisk. Should work.
Click to expand...
Click to collapse
Doesnt
But i got it right
adb shell
su
then deleted the magisk.img in data\adb i think it was
Related
Hey guys,
here is just a short guide on how to root EMUI9 with the newest Magisk 18.1 canary builds just release by John Wu.
This is not my work! All credits for this go to John Wu, the developer of Magisk.
You can try this of your own risk. I'm not responsible for any damage.
NOTE:
With the new Magisk, John Wu remapped the restart button in the standard power menu, so when you reboot with that button, you'll always reboot with root.
The power button works as normal.
You can revert to the stock recovery or an TWRP recovery at any time but without root.
- Download the TWRP app from Google PlayStore and install it.
- Go to the TWRP app and download the lastest twrp image for P20 Pro.
- Downlod one of the Magisk apk's from here and install it.
- Open the Magisk app, go to settings, put the update channel to manual and insert one of the links shown ontop of this page.
- Go back to the first page of Magisk, refresh it and make sure to install the lastet magisk apk. Open it again.
- You'll get asked to download and install the lastest Magist.zip. Do this and choose to patch only the boot.img. Choose the TWRP.img you've downloaded before.
- Plugin you device to a PC and download the patched img to your PC. Now reboot to fastboot mode and flash the patched img with "fastboot flash recovery_ramdisk patched_image.img"
- Now unplug your device and shut it down. Reboot it with holding vol-up button. Now it should boot fine with working root.
Have fun and thank you John Wu for your great work!
Not working
It's working for me. Finally have a root for EMUI 9
Do not use TWRP.img for patching,
use RECOVERY_RAMDISK instead
or simply download pre_patched one from here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
delete
works great
otonieru said:
Do not use TWRP.img for patching,
use RECOVERY_RAMDISK instead
or simply download pre_patched one from here : LINk2PATCH
Click to expand...
Click to collapse
I'm strongly thinking about getting the P20 Pro tomorrow
But I really want it to be able to run with Magisk and its wonderful modules.
So a quick question, or two:
1) That patched_boot.img - do I use fastboot and then Flash Ramdisk? Any other requirements out of the box? Do I have to unlock the bootloader (noob question).
2) Is it only for EMUI 9.0? Do I get this version by the official updater?
Best regards
ZHARQ said:
I'm strongly thinking about getting the P20 Pro tomorrow
But I really want it to be able to run with Magisk and its wonderful modules.
So a quick question, or two:
1) That patched_boot.img - do I use fastboot and then Flash Ramdisk? Any other requirements out of the box? Do I have to unlock the bootloader (noob question).
2) Is it only for EMUI 9.0? Do I get this version by the official updater?
Best regards
Click to expand...
Click to collapse
I think you'll need an unlocked bootloader and if your phone is new and locked you'll struggle obtaining root on any version of EMUI as it requires an unlocked bootloader. I believe there are paid services for that.
CaseyS said:
I think you'll need an unlocked bootloader and if your phone is new and locked you'll struggle obtaining root on any version of EMUI as it requires an unlocked bootloader. I believe there are paid services for that.
Click to expand...
Click to collapse
Just ordered it
Okay, so if I'm on 8.1 when I receive it - shall I try to unlock the Bootloader first or update to 9.0?
Thank you for your quick reply!
ZHARQ said:
Just ordered it
Okay, so if I'm on 8.1 when I receive it - shall I try to unlock the Bootloader first or update to 9.0?
Thank you for your quick reply!
Click to expand...
Click to collapse
I think you'll need to unlock bootloader before unless you receive the EMUI 9 update. But you may still need an unlocked bootloader. Better docrhst before you proceed. This is only coming from somone with an unlocked bootloader so I'm not sure if it's possible without.
ZHARQ said:
Just ordered it
Okay, so if I'm on 8.1 when I receive it - shall I try to unlock the Bootloader first or update to 9.0?
Thank you for your quick reply!
Click to expand...
Click to collapse
It almost certainly will come with 8.1
They've been boxed for sometime now
ZHARQ said:
I'm strongly thinking about getting the P20 Pro tomorrow
But I really want it to be able to run with Magisk and its wonderful modules.
So a quick question, or two:
1) That patched_boot.img - do I use fastboot and then Flash Ramdisk? Any other requirements out of the box? Do I have to unlock the bootloader (noob question).
2) Is it only for EMUI 9.0? Do I get this version by the official updater?
Best regards
Click to expand...
Click to collapse
That patched image file is only for EMUI 9,
and you need to flash it to recovery_ramdisk partition, not ramdisk. There's no longer ramdisk in EMUI 9. This is the exact reason for our trouble acquiring root, until topjohnwu, again, come as life saver, LoL
but if you decide to root on oreo and not upgrading, then you can simply use TWRP to flash Magisk.zip just like how you did with other phone.
for both, Unlocked Bootloader is a MUST. Unlock yours when you are still on 8.1. You gonna need to pay for the unlock code though. Keep your code safely in case you need it in the future.
otonieru said:
That patched image file is only for EMUI 9,
and you need to flash it to recovery_ramdisk partition, not ramdisk. There's no longer ramdisk in EMUI 9. This is the exact reason for our trouble acquiring root, until topjohnwu, again, come as life saver, LoL
but if you decide to root on oreo and not upgrading, then you can simply use TWRP to flash Magisk.zip just like how you did with other phone.
for both, Unlocked Bootloader is a MUST. Unlock yours when you are still on 8.1. You gonna need to pay for the unlock code though. Keep your code safely in case you need it in the future.
Click to expand...
Click to collapse
Thanks for clarifying that!
So I start with unlocking the bootloader (funkyhuawei .club/ buycodes - $55 )
Then see if there's an official upgrade to EMUI 9 available,
if not I will flash it myself(?),
then flash this premade patched_boot.img to recovery_ramdisk.
Another nooby question, what is it exactly that's changed on this .img?
Thanks!
ArtaxXP said:
NOTE: YOU HAVE NO MORE RECOVERY AFTER THIS AND YOU HAVE TO ALWAYS REBOOT WITH HOLDING VOL-UP BOTTON. (reboot to recovery)
Click to expand...
Click to collapse
Are you saying the power button (restart/power off) no longer works? That's weird!
What about apps that provide an advanced power menu/ reboot widgets etc?
How do we unroot/revert to stock (for future OTA purposes)? Should we be backing up our boot img? If so, how?
otonieru said:
Do not use TWRP.img for patching,
use RECOVERY_RAMDISK instead
or simply download pre_patched one from here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
Click to expand...
Click to collapse
So basically, just install Magisk apk and flash your patched boot img with "fastboot flash recovery_ramdisk patched_boot.img"?
colthekid said:
Are you saying the power button (restart/power off) no longer works? That's weird!
What about apps that provide an advanced power menu/ reboot widgets etc?
How do we unroot/revert to stock (for future OTA purposes)? Should we be backing up our boot img? If so, how?
So basically, just install Magisk apk and flash your patched boot img with "fastboot flash recovery_ramdisk patched_boot.img"?
Click to expand...
Click to collapse
I'm not certain that the patched_boot.img is the same as the one the way the topic author mentions (I can be wrong though).
Would be nice to know exactly what it's already patched with.. Magisk maybe?
colthekid said:
Are you saying the power button (restart/power off) no longer works? That's weird!
What about apps that provide an advanced power menu/ reboot widgets etc?
How do we unroot/revert to stock (for future OTA purposes)? Should we be backing up our boot img? If so, how?
So basically, just install Magisk apk and flash your patched boot img with "fastboot flash recovery_ramdisk patched_boot.img"?
Click to expand...
Click to collapse
Forget, what I told you in the first post. With the new Magisk, John Wu remapped the restart button in the standard power menue, so when you reboot with that button, you'll always reboot with root. The power button works as normal.
And for your second question:
Yeah, basically, that's it.
If you need to go back to stock, you need to extract the recovery ramdisk image from the original firmware, downloaded for example with Huawei Firmware Finder or maybe someone can provide the stock image.
ArtaxXP said:
Forget, what I told you in the first post. With the new Magisk, John Wu remapped the restart button in the standard power menue, so when you reboot with that button, you'll always reboot with root. The power button works as normal.
And for your second question:
Yeah, basically, that's it.
If you need to go back to stock, you need to extract the recovery ramdisk image from the original firmware, downloaded for example with Huawei Firmware Finder or maybe someone can provide the stock image.
Click to expand...
Click to collapse
Excellent, nice and simple that's what we like!!
Interesting way of doing it though, it's effectively booting from the recovery partition rather than the normal boot partition...hence no TWRP! I presume you could swap between rooted and stock that way...would help with those apps that even Magisk can't hide root from...would almost not want the remapping of the power button if it allowed you to swap between the two states (i.e. reboot from power button takes you to stock, reboot via up vol makes you rooted!)
colthekid said:
Excellent, nice and simple that's what we like!!
Interesting way of doing it though, it's effectively booting from the recovery partition rather than the normal boot partition...hence no TWRP! I presume you could swap between rooted and stock that way...would help with those apps that even Magisk can't hide root from...would almost not want the remapping of the power button if it allowed you to swap between the two states (i.e. reboot from power button takes you to stock, reboot via up vol makes you rooted!)
Click to expand...
Click to collapse
xactly what i thinking,
curently i swapping between root and non root simply by rebooting.
---------- Post added at 02:10 PM ---------- Previous post was at 02:08 PM ----------
ZHARQ said:
I'm not certain that the patched_boot.img is the same as the one the way the topic author mentions (I can be wrong though).
Would be nice to know exactly what it's already patched with.. Magisk maybe?
Click to expand...
Click to collapse
my file patched with magisk as well of course,
difference is, author of this thread using TWRP image as base, while am using a pure stock recovery ramdiak from .168 EMUI 9 firmware
TWRP image can work as well, but may cause issue in some devices with different firmware version,
after all, topjohnwu tell you to use recovery ramdisk image, not TWRP right
Thanks
It worked fine, but not with TWRP img, I used my own recovery img
CanĀ“t get to rooted EMUI 9. Always ended in non-rooted even after multiple reboots to recovery
Has anyone tried to use any of the root tools, such as KingRoot and One Click Root, to successfully root on X7 or 8.1?
hchao1 said:
Has anyone tried to use any of the root tools, such as KingRoot and One Click Root, to successfully root on X7 or 8.1?
Click to expand...
Click to collapse
It won't work. We need unlocked bootloader. After unlocked bootloader we can root it by patched boot img
Rajeev said:
It won't work. We need unlocked bootloader. After unlocked bootloader we can root it by patched boot img
Click to expand...
Click to collapse
I have a nokia 8.1 rooted
1st: unlock ur bootloader
2nd: install twrp from adb
3rd: boot and install magisk manager apk
4th: reboot to twrp and flash magisk
Reboot and patch your kernel boot.img
Reboot to twrp and flash the patched boot.img
Flash magisk again and u r rooted now
karrouma said:
I have a nokia 8.1 rooted
1st: unlock ur bootloader
2nd: install twrp from adb
3rd: boot and install magisk manager apk
4th: reboot to twrp and flash magisk
Reboot and patch your kernel boot.img
Reboot to twrp and flash the patched boot.img
Flash magisk again and u r rooted now
Click to expand...
Click to collapse
Good. But sadly i dont have Nokia anymore. I am using Xiaomi Mi9 Global
Rajeev said:
Good. But sadly i dont have Nokia anymore. I am using Xiaomi Mi9 Global
Click to expand...
Click to collapse
Mi9 is perfect
I like it. But a phone without sd card is not good for me.
Xiaomi seems to replace sony here in my country
root, twrp, camera api
Rajeev said:
Good. But sadly i dont have Nokia anymore. I am using Xiaomi Mi9 Global
Click to expand...
Click to collapse
Hi,
is it possible to activate Level_3 on Camera2 API when rooted phone?
Which version of TWRP you used?
Thanks
karrouma said:
I have a nokia 8.1 rooted
1st: unlock ur bootloader
2nd: install twrp from adb
3rd: boot and install magisk manager apk
4th: reboot to twrp and flash magisk
Reboot and patch your kernel boot.img
Reboot to twrp and flash the patched boot.img
Flash magisk again and u r rooted now
Click to expand...
Click to collapse
Please link the guide for unlocking and and link for twrp, thanks
paarkhi said:
Please link the guide for unlocking and and link for twrp, thanks
Click to expand...
Click to collapse
I would find that helpful as well
I've got a Nokia 8.1 (TA-1119), and want to get rid of Android 11's navigation bar. But I can't seem to find a valid TWRP for my phone.
So I'm stuck before I can begin, basicly...
karrouma said:
I have a nokia 8.1 rooted
1st: unlock ur bootloader
2nd: install twrp from adb
3rd: boot and install magisk manager apk
4th: reboot to twrp and flash magisk
Reboot and patch your kernel boot.img
Reboot to twrp and flash the patched boot.img
Flash magisk again and u r rooted now
Click to expand...
Click to collapse
Which TWRP did you use? it seems that the one available in here causes some bricks...
karrouma said:
I have a nokia 8.1 rooted
1st: unlock ur bootloader
2nd: install twrp from adb
3rd: boot and install magisk manager apk
4th: reboot to twrp and flash magisk
Reboot and patch your kernel boot.img
Reboot to twrp and flash the patched boot.img
Flash magisk again and u r rooted now
Click to expand...
Click to collapse
Can you pls provide a complete guide on how did you unlock the bootloader? pls i really need it T H A N K Y O U )
any hope for getting viper4android FX on samsung A70 now that we have root with magisk and twrp for our phone. and the source code also been released for our phone
fizzingbees said:
any hope for getting viper4android FX on samsung A70 now that we have root with magisk and twrp for our phone. and the source code also been released for our phone
Click to expand...
Click to collapse
I am using it.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
install and use.
Can i use it without root/twrp?
AbOuLfOoOoOuF said:
Can i use it without root/twrp?
Click to expand...
Click to collapse
You can't use it without root access. But TWRP or any kind of recovery is not needed for things like this.
y.erenbektas said:
I am using it.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
install and use.
Click to expand...
Click to collapse
So basically I just have to download and installed viper4android fx 2.7 apk and that's it.
No deep buffer removal or any extra steps or magisk module needed
AbOuLfOoOoOuF said:
Can i use it without root/twrp?
Click to expand...
Click to collapse
Without twrp yes. You don't need recovery for viper4android.
But root. Nope.. You need to have a rooted device for the audio drivers to get installed.
And just so you know rooting with trip knox and void your warrenty and it also involves unlocking bootloader and doing so will show a message on phone startup about the phone being insecure.
So keep that on mind before you unlock bootloader and root with magisk
fizzingbees said:
So basically I just have to download and installed viper4android fx 2.7 apk and that's it.
No deep buffer removal or any extra steps or magisk module needed
Click to expand...
Click to collapse
I have done none of them. And it's working like a charm.
There is a Viper4Android module in magisk which is installed but not by me. So I think app is doing necessary things itself.
fizzingbees said:
any hope for getting viper4android FX on samsung A70 now that we have root with magisk and twrp for our phone. and the source code also been released for our phone
Click to expand...
Click to collapse
What does it do exactly?
SniperLolz said:
What does it do exactly?
Click to expand...
Click to collapse
Viper4android is an alternative audio driver for Android that offers very granular control over each aspect of audio output coming from your phone.
You can adjust bass, treble reverberations gain etc and many more things with this.
And unlike other sound apps this works system wise.
y.erenbektas said:
You can't use it without root access. But TWRP or any kind of recovery is not needed for things like this.
Click to expand...
Click to collapse
No you don't, I try it and ask me for root
wallah said:
No you don't, I try it and ask me for root
Click to expand...
Click to collapse
Please read it again dude, thanks for agreeing.
y.erenbektas said:
Please read it again dude, thanks for agreeing.
Click to expand...
Click to collapse
Sorry, I was so happy to use it without root ?
My bad ?
y.erenbektas said:
I am using it.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
install and use.
Click to expand...
Click to collapse
was using this before and worked well, now doesnt seem to want to install drivers (root granted).
which v4a version are you using?
dj69holland said:
was using this before and worked well, now doesnt seem to want to install drivers (root granted).
which v4a version are you using?
Click to expand...
Click to collapse
Hey, I'm really sorry for this late respond. I'm busy nowadays and just had some time to check my mails etc.
Right now I'm using V4A Version 2.7.1.6. You can find it here.
If you're using Android 10, it's completely normal to have problems with V4A for now. If you're using Android 10 please let me know and I'll explain you how you should install V4A.
y.erenbektas said:
Hey, I'm really sorry for this late respond. I'm busy nowadays and just had some time to check my mails etc.
Right now I'm using V4A Version 2.7.1.6. You can find it here.
If you're using Android 10, it's completely normal to have problems with V4A for now. If you're using Android 10 please let me know and I'll explain you how you should install V4A.
Click to expand...
Click to collapse
thank you.
i had a specific build that worked flawless with android 10, but lost the apk and started then was facing issues with latest apk in xdaLabs (some with installing driver, some driver installed but not processing)
I just went one by one and tried different setups. finally got Team de Witts 2.7.1.0 to work.
fizzingbees said:
any hope for getting viper4android FX on samsung A70 now that we have root with magisk and twrp for our phone. and the source code also been released for our phone
Click to expand...
Click to collapse
Please how did you roof & installed twrp?
danbaba said:
Please how did you roof & installed twrp?
Click to expand...
Click to collapse
I haven't rooted myself yet, but on A70 forums there is twrp, magisk and bootloader unlocking guide that you follow
https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
loss of magisk
y.erenbektas said:
I am using it.
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
install and use.
Click to expand...
Click to collapse
helle there
i also installed viper4 adnroid v2.7.1.6 from xda labs . but after reboot i lost magisk root. also the driver didnt worked. on reboot the driver started working ,but the magisk root disappeared.
the only way for me to get magisk root back is to either factory reset in twrp, which will erase v4a ..or to restore stock boot.img which will erase magisk
now i am in this limbo.
if you have some advise to get me out of this mess,kindly post it here
fizzingbees said:
helle there
i also installed viper4 adnroid v2.7.1.6 from xda labs . but after reboot i lost magisk root. also the driver didnt worked. on reboot the driver started working ,but the magisk root disappeared.
the only way for me to get magisk root back is to either factory reset in twrp, which will erase v4a ..or to restore stock boot.img which will erase magisk
now i am in this limbo.
if you have some advise to get me out of this mess,kindly post it here
Click to expand...
Click to collapse
try shuting the phone down. then press and hold volume up and power button till you see the warning screen and then release those buttons. check the magisk again.
y.erenbektas said:
try shuting the phone down. then press and hold volume up and power button till you see the warning screen and then release those buttons. check the magisk again.
Click to expand...
Click to collapse
I am rooted using magisk patched recovery.img. Which was flashed as boot in twrp recovery
Elaborate which warning screen?
I'll try the magisk patched Ap. Tar flashed in AP in odin and then retry this method
I heard people brick their phones after flashing magisk. Is that their fault or it's just that magisk doesn't work on this phone yet?
Seems to be the later.
I will test some Magisk versions today.
The manager installs just fine, I downloaded the image from Mi and extracted the boot.img from their firmware. It seems to have been patched just fine with the Magisk app, I haven't flashed it yet, haven't figured out how to get to download mode on this phone. They have a custom boot loader and custom recovery on it. adb reboot download just reboots the phone. I went through the motions of unlocking the bootloader per their instructions but they're having me wait a week before I can unlock the bootloader. I'm hesitant to flash magisk before unlocking the bootloader and making sure I can re-flash with twrp if needed.
Flashing magisk bricks the phone, flashing patched boot.img also bricks the device.
Kingoroot anyone ?
A loot of people brick their phones.. but the sad part is to recover it back.. I dont know why is so hard to unbrick almost everyone Xiaomi phones...
tze_vitamin said:
A loot of people brick their phones.. but the sad part is to recover it back.. I dont know why is so hard to unbrick almost everyone Xiaomi phones...
Click to expand...
Click to collapse
bricking rn8p due to magisk installation is easy to recover by flashing boot.img from stock rom.
astrakid said:
bricking rn8p due to magisk installation is easy to recover by flashing boot.img from stock rom.
Click to expand...
Click to collapse
So did you manage to actually flash or install magisk and obtain root?
donkyshot said:
So did you manage to actually flash or install magisk and obtain root?
Click to expand...
Click to collapse
no, root is not working. but it is easily possible to recover a bootlooping rn8p.
astrakid said:
no, root is not working. but it is easily possible to recover a bootlooping rn8p.
Click to expand...
Click to collapse
Such a shame, I can't believe there's no custom recovery and root available yet for such a popular device. Let's wait and see.
Hey,
This guy here at the twrp thread says that he managed to root with Magisk 19.3.
rrk said:
Hello all,
Can somebody tell me how to replace Chinese ROM with Global one.
I am waiting now for bootloader unlock, abt 100 hrs remain, thanks in advance
Click to expand...
Click to collapse
Is this possible yet? Looking to buy this phone.
razerphynx said:
Is this possible yet? Looking to buy this phone.
Click to expand...
Click to collapse
Should be quite similar to before, but if you flash preloader & lk, you can recover from these bricks. That said, I've never had magisk bricking it for me.
I am on MIUI 12, Android 10, Chinese Beta Rom and I have Magisk installed as well...
Any update on a fully working method to root our device?
Android 11, custom ROM, CFW
astrakid said:
bricking rn8p due to magisk installation is easy to recover by flashing boot.img from stock rom.
Click to expand...
Click to collapse
There is an easier way.
I had twrp as recovery and when i flashed magisk v20 zip it bricked both the normal system and recovery
It was saying "The system has been destroyed"
So i was doing random stuff and found the solution
1) go to fastboot
2) from pc execute the "fastboot flash recovery twrp.img" you probably know how to install twrp
3) then boot to recovery
4) enter password and allow modifications
5) go to reboot > System
Thats how i did it.
I have not tested with other custom recoveries
Hope I help
nakedowl said:
I will test some Magisk versions today.
Click to expand...
Click to collapse
Did other versions of magisk work
1: Unlock your bootloader
2: Reboot to fastboot
3: Via fastboot on a PC, flash the attached boot IMG (fastboot flash boot "directory to boot IMG, can drag and drop")
4: Done!
Ill try to keep this img up to date but always verify the version before you flash
Current version: 10.5.4.IN11AA
https://drive.google.com/open?id=18fbWNm1ZLFA1dsJkiQJrcEn-unJA1UDQ
nima0003 said:
1: Unlock your bootloader
2: Reboot to fastboot
3: Via fastboot on a PC, flash the attached boot IMG (fastboot flash boot "directory to boot IMG, can drag and drop")
4: Done!
Ill try to keep this img up to date but always verify the version before you flash
Current version: 10.5.4.IN11AA
https://drive.google.com/open?id=18fbWNm1ZLFA1dsJkiQJrcEn-unJA1UDQ
Click to expand...
Click to collapse
Do you have update to 10.5.5.IN11AA ?
gaww said:
Do you have update to 10.5.5.IN11AA ?
Click to expand...
Click to collapse
If all you're looking for is the patched boot image, you can find it here, https://forum.xda-developers.com/oneplus-8-pro/how-to/magisk-patched-10-5-5-image-t4088333.
spotmark said:
If all you're looking for is the patched boot image, you can find it here, https://forum.xda-developers.com/oneplus-8-pro/how-to/magisk-patched-10-5-5-image-t4088333.
Click to expand...
Click to collapse
Just got the phone and it updated to .5, and late at night, .6 showed up. It installed without all the trouble with TMo 7.
It unrooted, and I used the .5 magisk patched.img above without any problems, but will use .6 when available.
Careful with the fingerprint enrollment, factory wiping with root has been known to break fingerprint. Just a heads up.
Theres a thread about this, there isn't a currently known fix either.
Has happened to EU BA devices but you never know.
dladz said:
Careful with the fingerprint enrollment, factory wiping with root has been known to break fingerprint. Just a heads up.
Theres a thread about this, there isn't a currently known fix either.
Has happened to EU BA devices but you never know.
Click to expand...
Click to collapse
Thanks. I didn't wipe and I don't use fingerprint.
gaww said:
Thanks. I didn't wipe and I don't use fingerprint.
Click to expand...
Click to collapse
Right ok, might want to check it if you ever do. Just in case
Will this work on the Verizon compatible phone?
skateguy1234 said:
Will this work on the Verizon compatible phone?
Click to expand...
Click to collapse
If you're using an unlocked 8 Pro, sure. If you're using an 8, purchased directly from Verizon, no.
skateguy1234 said:
Will this work on the Verizon compatible phone?
Click to expand...
Click to collapse
Check your pms if you want to tinker with the Verizon model with
I'm using a US 8 Pro running 10.5.10.IN11AA. Can I use this 10.5.4.IN11AA boot image, or do I need to wait for an update? Is there a newer way to install magisk?
Ecna said:
I'm using a US 8 Pro running 10.5.10.IN11AA. Can I use this 10.5.4.IN11AA boot image, or do I need to wait for an update? Is there a newer way to install magisk?
Click to expand...
Click to collapse
No - don't use old one. If you search, you should find 10.5.10 boot image.
Thanks, I couldn't find a new one so I downgraded to 5.9.
Ecna said:
Thanks, I couldn't find a new one so I downgraded to 5.9.
Click to expand...
Click to collapse
Now you can upgrade back to 5.10 and reinstall magisk before booting up the update. Works real easy.
^ @gaww
I've been able to unlock the bootloader on my Oneplus 8 Pro and am trying to locate a magisk patch compatible with 10.5.1.in11aa, yet can't locate this version. However, there's an OTA update available for my phone at takes it to 10.5.10. If I first perform that OTA update, where can I then find a compatible version of magisk?
TIA!
Deckardmac said:
^ @gaww
I've been able to unlock the bootloader on my Oneplus 8 Pro and am trying to locate a magisk patch compatible with 10.5.1.in11aa, yet can't locate this version. However, there's an OTA update available for my phone at takes it to 10.5.10. If I first perform that OTA update, where can I then find a compatible version of magisk?
TIA!
Click to expand...
Click to collapse
Don't make things complicated, update to 10.5.10, boot twrp, install magisk from the zip
^ Pardon my noobness, but does the Magisk version have to match the OxygenOS version, or can I simply use the latest Magisk version? Lots of chatter about getting the Magisk that matches.
Deckardmac said:
^ Pardon my noobness, but does the Magisk version have to match the OxygenOS version, or can I simply use the latest Magisk version? Lots of chatter about getting the Magisk that matches.
Click to expand...
Click to collapse
Use 20.4
^ Thanks guys. It worked flawlessly.
how to fix cts profile false on 10.5.10