How to root Nokia 3 in the version of Android 9 pie [WORKED] - Nokia 3 Guides, News, & Discussion

If you want to root your phone first of all you need to unlock your bootloader... I already wrote the instructions in the version of Android 9 pie.
To unlock the bootloader Link: https://forum.xda-developers.com/nokia-3/how-to/method-to-unlock-bootloader-nokia-3-pie-t4012285
After unlock the bootloader need to install latest Magisk manager in your phone
1. Magisk manager apk Link: https://mega.nz/#!6EdlHAZD!GYMjfkus4gxKUztZ5RR0lY9UPRuuCqGskadjLR1q_Q8
Download and install it
2. Open Magisk manager apk Click on the first one magisk is not installed click on install after that one dialogue box will pops up on the screen [Do you want to install magisk click on install]
3. Now there is a two options as select method 1.Download zip only 2. Select and patch a file Download the boot file from Link: https://mega.nz/#!LZFzgYjK!dwJDghKnBU7gPLJlLIxvW3cwZtZi3bA2n-kI-yBfJHA
4. Click on the second one Select and patch a file and install boot file after that you will see Patched_boot.img downloaded in Internal download folder (Internet required while installing boot file from select and patch a file...
5. Move the patched_boot.img file in pc and locate in adb and fastboot folder now boot your device in fastboot mode now write this command
Fastboot devices (wheather your device connected or not)
Fastboot flash boot (you can drag the file patched_boot.img file and hit enter) Fastboot flash boot patched_boot.img
Fastboot reboot
{Mod edit}

I can confirm that this works on Nokia3 TA-1032,
but the problem is the camera. After rooting, camera does not work!
All you get is green background, if anyone knows hot to fix the green
background, please let me/us know.
Thank you,

o333 said:
I can confirm that this works on Nokia3 TA-1032,
but the problem is the camera. After rooting, camera does not work!
All you get is green background, if anyone knows hot to fix the green
background, please let me/us know.
Thank you,
Click to expand...
Click to collapse
same problem with green camera, anyone with a fix?

Related

root for Xperia XZS so-03j (Japan Docomo Variant)

Hello,
I got a Xperia XZS SO-03J (Japan Docomo Variant). Anybody got any ideas to root this device and any custom roms. Already searched the forum but no avail. Thank you for your help.
Japanese cellular version usually unable to unlock bootloader.but still some phones can unlock. if you have twrp ,you can install some rooted ROMs modified from official ROM.(btw you have to find a ROM can install without unlock bootloader)
sinkoo1979 said:
Hello,
I got a Xperia XZS SO-03J (Japan Docomo Variant). Anybody got any ideas to root this device and any custom roms. Already searched the forum but no avail. Thank you for your help.
Click to expand...
Click to collapse
if you have docomo ubl yes you can patch kernel manual , because it's different from Au,Global,Softbank
I've tried with x compact docomo ubl yes
I think first of all need to check whether the bootloader is unlockable or not
if you can UNLOCK the Japanese Xzs then
you can use this TWRP
https://dl.twrp.me/kagura/twrp-3.2.3-0-kagura.img.html
there is a depate that you can cross flash XZ's Android 6 to extract DRM keys! but i am not going to go that, as soon as you UNLOCK you bootload, TA partition will be GONE..
what is your build number?
download your build from FLASHTOOL---> Xperfirm and send me KERNEL.sin and i will send you the modded kernel
rest PROCESS you can Read (carefully) at
https://forum.xda-developers.com/xperia-xz/how-to/rooted-kernels-f8332-41-3-2-588-0-t3748987
its for XZ but applies to XZs too!
YasuHamed said:
if you can UNLOCK the Japanese Xzs then
you can use this TWRP
https://dl.twrp.me/kagura/twrp-3.2.3-0-kagura.img.html
there is a depate that you can cross flash XZ's Android 6 to extract DRM keys! but i am not going to go that, as soon as you UNLOCK you bootload, TA partition will be GONE..
what is your build number?
download your build from FLASHTOOL---> Xperfirm and send me KERNEL.sin and i will send you the modded kernel
rest PROCESS you can Read (carefully) at
https://forum.xda-developers.com/xperia-xz/how-to/rooted-kernels-f8332-41-3-2-588-0-t3748987
its for XZ but applies to XZs too!
Click to expand...
Click to collapse
YusaHamed this is my kernel https://drive.google.com/open?id=1mGpQOcWcuCfwp4U0wrt29HzERH5SQrTr
i need your help to mod this kernel, and then this is my build number 41.3.B.1.140
:fingers-crossed:
Amirai17 said:
YusaHamed this is my kernel https://drive.google.com/open?id=1mGpQOcWcuCfwp4U0wrt29HzERH5SQrTr
i need your help to mod this kernel, and then this is my build number 41.3.B.1.140
:fingers-crossed:
Click to expand...
Click to collapse
requesting you please
send me also these three files
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
there will be system.sin in that ftf,
convert it using FLASHTOOL > tool > sineditor > selected system.sin and click extract data, it will make 6gb file SYSTEM.ext4, open it with 7zip and locate the above three file and add in the goodle drive PLZ
Amirai17 said:
YusaHamed this is my kernel https://drive.google.com/open?id=1mGpQOcWcuCfwp4U0wrt29HzERH5SQrTr
i need your help to mod this kernel, and then this is my build number 41.3.B.1.140
:fingers-crossed:
Click to expand...
Click to collapse
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
Thanks for the kernel mod, you mod it so fast that's so amazing
Anyway i will try it tomorrow, pray fo the kernel got stable
Before i use this kernel on this thread https://forum.xda-developers.com/xzs/development/root-xperia-xzs-t3726911
And i got unstable performance. Trying use kernel auditor not effect it and i decide to flash it back to normal again.
Amirai17 said:
Thanks for the kernel mod, you mod it so fast that's so amazing
Anyway i will try it tomorrow, pray fo the kernel got stable
Before i use this kernel on this thread https://forum.xda-developers.com/xzs/development/root-xperia-xzs-t3726911
And i got unstable performance. Trying use kernel auditor not effect it and i decide to flash it back to normal again.
Click to expand...
Click to collapse
I dont know about that thread
Seems like different process
Anways plz do try this and let me know
YasuHamed said:
I dont know about that thread
Seems like different process
Anways plz do try this and let me know
Click to expand...
Click to collapse
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Amirai17 said:
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Click to expand...
Click to collapse
This is a good news! , good to know that you were able to Root it.
i am sure you will find good performance.
nighlight makes your screen TINT different (reduces blue) which makes it easier on eyes while you browsing in night or from bed. blue light hurts eyes and brain and increases sleeplessness.
a shortcut toggle button next to FLASHLIGHT will appear (if arent already in your build) and display setting will have NIGHLIGHT FEATURE ENABLED- you can control the INTENSITY of this filter according to your needs
YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
I have the same phone xzs docomo so-03j on the same build, is it ok if i flash this too or will it brick my phone? thank you
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
Amirai17 said:
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Click to expand...
Click to collapse
How has it been? the performance? mine heats up akot when gaming and is even slower than my Softbank xperia xz I would like to root mine as well if it is good and if it is possible
other build number
YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
why with different build number?
i have build number 41.3.B.1.113
or can i flash to global rom and what the side effect?
plz tell me how you root your xz. my xz 601so with allowed yes
Amirai17 said:
Sorry i take a long time to try it,
But i just try it n i can root my phone
for performance, not yet test it
no any trouble on process, but
i want to ask, what the use of nightlight?
Click to expand...
Click to collapse
Temporary root is now possible on the Xperia so-03j, I personally tested a few minutes ago.
Check this comment for instructions. And here instructions to create a launcher.
YasuHamed said:
FROM THIS LINK
https://mega.nz/#F!eRh0TSiQ!j6FNfTsHpkw8DECUNRF5QQ
kindly copy into SDCARD of your mobile the following files
1. magisk17.2
2. drmFix.zip
3. NightLight.zip (optional)
4. magisk MANAGER 6.0.1.apk
and
then FLASH twrp to your XZs by Connecting in to Fastboot mode (BLUE LED) and opening "MINIMAL ADB AND FASBOOT"
you can download it from here https://forum.xda-developers.com/showthread.php?t=2317790
Code:
in adb type
FASTBOOT DEVICE (then enter)
<it will show some hex code, confirming your device is in fastboot mode connected>
now type
FASTBOOT FLASH RECOVERY <and drag twrp image file from DESKTOP to your black cmd window... it will come as path>
press enter and flashing will be done
unplug device and press and hold volume down and power until you see twrp...
- keep system read only
- goto backup
- backup boot and swipe right, it will make boot backup in your sd card (it always recommended
- now goto install
- click flash IMAGE FILE button at bottom
- select KERNEL_CLEAN_41.3.B.1.140_XZs_SO-03J.img
- it will ask where to flash ... CHECK BOX "BOOT" ( BE CAREFUL )
- twrp will flash boot with provided kernel
- now click button FLASH ZIP file & flash DRMFIX.zip
- now flash Magisk17.x.zip
- now flash NIGHTLIGHT.zip (optional)
- clear cache
- poweroff and while powering off, select DONOT INSTALL TWRP.
press power on and let device boot, first boot may goto bootloops.
the device will now boot and check for MAGISK app in app drawer, if you can find it, GOOD, otherwise install MAGISK MANAGER 6.0.1.apk from your sd card
install rootchecker from playstore and check for root access
done
Click to expand...
Click to collapse
can i root my Xperia XZs AU version with these files that are attached in this post, or do i need different files ?
thank you @YasuHamed
5crypt said:
can i root my Xperia XZs AU version with these files that are attached in this post, or do i need different files ?
thank you @YasuHamed
Click to expand...
Click to collapse
Those files seem appropriate for stock rom release 41.3.B.1.140., so don't try unless you're running that specific version (quite outdated if you ask me).
But first make sure your bootloader can be unlocked. If that's the case, you may want to install a recent rom with root support, or check the guides for rooting stock rom. Be aware that with unofficial roms you might lose camera quality or have no cam support at all.
If you're stuck with an unlockable bootloader (like myself) your choices are much more limited. My current approach is having latest stock, disable bloatware apps, and use temporary root when needed.
thank you @dinosaur99 for your quick response, i got the one that cannot be unlocked, so i'm using the temp root method, but do you know how to gain temp root access without using adb (laptop or computer), and can i automate the temp root every after reboot ?
again thank you for your response, and looking forward from you
5crypt said:
thank you @dinosaur99 for your quick response, i got the one that cannot be unlocked, so i'm using the temp root method, but do you know how to gain temp root access without using adb (laptop or computer), and can i automate the temp root every after reboot ?
again thank you for your response, and looking forward from you
Click to expand...
Click to collapse
Good question! I wanted to create a launcher too!
So I just followed these instructions and it works fine. First you need to perform the following commands from computer (have a copy of the exploit file in working directory):
Bash:
adb push su98-memory-kallsyms /data/local/tmp/
adb shell
# Run this from inside the shell
chmod +x /data/local/tmp/su98-memory-kallsyms
/data/local/tmp/su98-memory-kallsyms
chcon u:object_r:system_file:s0 /data/local/tmp/su98-memory-kallsyms
Now reboot the phone, and the file /data/local/tmp/su98-memory-kallsyms should still be there. On your favourite console app, create a new terminal launcher/profile/whatever it's called and name it "Root terminal", then make it so it runs this command on shell login:
Bash:
/data/local/tmp/su98-memory-kallsyms
Note there's a trailing <Enter> key at the end of the command. I use Connectbot and it was necessary.
Cheers!
Edit:
By the way, the last line would be the equivalent to "sudo bash" in a computer. That means you can write a script with the root commands to be executed upon reboot. Example launcher:
Bash:
/data/local/tmp/su98-memory-kallsyms /data/local/tmp/my-script

TWRP for Gionee M5 Mini MT6580

I've done deep search about this concern for 2 hours but I've only seen twrp for M5 mini but with different Mediatek. I have MT6580 so some forums doesnt give me any answers so I need help to you guys if you have twrp for this type of Mediatek. Need to flash a rom to my phone~ Thanks in advance
Upload your stock recovery, we'll see if something can be done
I'm new so i don't know how to extract my stock recovery
CSAPawn said:
I'm new so i don't know how to extract my stock recovery
Click to expand...
Click to collapse
Then you download your stock firmware just extract it with any unzipper app like winrar or 7zip, then zip it and upload it here or it´s not able upload it to some cloud host like Google Drive
This is my stock firmware Lollipop
http://www.mediafire.com/file/wd5a4xqftiao7t6/Gionee_M5_Mini_MT6580_5.1.zip
I have Marshmallow update right now so here's the update file https://mega.nz/#!jQdWkYiB
CSAPawn said:
I have Marshmallow update right now so here's the update file https://mega.nz/#!jQdWkYiB
Click to expand...
Click to collapse
Download it, you might need it in the future, and inside the zip you will see a file called recovery, extract it and upload me here, I need this file to try to made a custom recovery for your device
Okay! Le me just download it~
https://drive.google.com/file/d/1i57tu6g-qLWFHL8JknfrHJqh1SsYDk_X/view here's the recovery of Marshmallow update
CSAPawn said:
https://drive.google.com/file/d/1i57tu6g-qLWFHL8JknfrHJqh1SsYDk_X/view here's the recovery of Marshmallow update
Click to expand...
Click to collapse
This is not your recovery, there must to have other recovery with image extension, guide you for the size, atleast a 10 MB
That is the only one with the name "recovery" in the zip file, i think i should find it in Lollipop stock rom. Gonna download it first~
CSAPawn said:
That is the only one with the name "recovery" in the zip file, i think i should find it in Lollipop stock rom. Gonna download it first~
Click to expand...
Click to collapse
Show me a screen of your zip open please to see the files.
What is the size of your recovery cause the uploaded is just some kbs
And what is the size of the boot image
SubwayChamp said:
Show me a screen of your zip open please to see the files.
What is the size of your recovery cause the uploaded is just some kbs
And what is the size of the boot image
Click to expand...
Click to collapse
https://ibb.co/cYWrsy here's the main directory of the zip
https://ibb.co/nMLqkJ and recovery file found on "sig" folder on main directory
Boot Image file size is 7.48 MB
I'm now downloading the Lollipop Stock Rom because that Marshmallow Rom is just an update which might be incomplete in some files~
https://drive.google.com/open?id=1wX5N5_NzKhbg4gWG2RIQ6Ta5MzHYK0W1
Here's the link of 2 files with recovery file name in .img file format
https://ibb.co/gGCvKd
Here's the full content of the Lollipop Stock Rom
CSAPawn said:
https://drive.google.com/open?id=1wX5N5_NzKhbg4gWG2RIQ6Ta5MzHYK0W1
Here's the link of 2 files with recovery file name in .img file format
https://ibb.co/gGCvKd
Here's the full content of the Lollipop Stock Rom
Click to expand...
Click to collapse
Ok, now you need to unlock bootloader. Follow the next steps:
Download to your pc the latest version of adb installer from here https://androidmtk.com/download-15-seconds-adb-installer , in the process just type "y" to all questions. After it finishes unpack this adb folder and put it in your main drive, by i.e. c: drive
View attachment adb.zip
Install all the drivers for your device.
1- In your device go to settings/about device/build number and tap 7 times, then go back to settings and you will see developer options into settings, enable USB debugging and enable OEM unlock if it´s present,
2- Extract from the zip twrp.img and put it inside adb folder
View attachment twrp-wl2.zip
3- Connect your device power on to pc and run the file "run-adb" as administrator with right mouse button
4- Type adb reboot bootloader and you will be prompted in display of your device, tap on the small box "always allow" and tap on "ok"
5- Now device will reboot to fastboot mode, type fastboot devices you have to see a serial of your device in the window, then if it´s detected type now fastboot oem unlock you have to confirm wiith the button of your device, pay attention.
6- Then you will go to flash twrp onto your device, for this type fastboot flash recovery twrp.img and then to reboot to recovery type fastboot boot twrp.img is important that here device reboots to recovery before to reboot to system.
7- In twrp you will be prompted to allow modifications, just swipe to confirm.
If you also want to root your device download the latest version of Magisk in zip format to flash it through twrp.
When al finishes if sucessful you have to format data (all your data will gone) in order to can reboot to system again due to encryption, anyway unlocking bootloader most probably you will lose it before.
Read carefully and do steps one by one, don´t jump nor ignore nothing of the indicated to avoid any damage. If you are not sure in some steps just stops process and ask before.
I´m not sure you that this twrp matches for your device cause I can´t try before and but will see that.
Don´t forget to provide screenies of the process if something goes wrong to can clear.
OMG Thank you very much for this guide, I'll follow the steps later and post a pic after~
SubwayChamp said:
Ok, now you need to unlock bootloader. Follow the next steps:
Download to your pc the latest version of adb installer from here https://androidmtk.com/download-15-seconds-adb-installer , in the process just type "y" to all questions. After it finishes unpack this adb folder and put it in your main drive, by i.e. c: drive
View attachment 4530163
Install all the drivers for your device.
1- In your device go to settings/about device/build number and tap 7 times, then go back to settings and you will see developer options into settings, enable USB debugging and enable OEM unlock if it´s present,
2- Extract from the zip twrp.img and put it inside adb folder
View attachment 4530170
3- Connect your device power on to pc and run the file "run-adb" as administrator with right mouse button
4- Type adb reboot bootloader and you will be prompted in display of your device, tap on the small box "always allow" and tap on "ok"
5- Now device will reboot to fastboot mode, type fastboot devices you have to see a serial of your device in the window, then if it´s detected type now fastboot oem unlock you have to confirm wiith the button of your device, pay attention.
6- Then you will go to flash twrp onto your device, for this type fastboot flash recovery twrp.img and then to reboot to recovery type fastboot boot twrp.img is important that here device reboots to recovery before to reboot to system.
7- In twrp you will be prompted to allow modifications, just swipe to confirm.
If you also want to root your device download the latest version of Magisk in zip format to flash it through twrp.
When al finishes if sucessful you have to format data (all your data will gone) in order to can reboot to system again due to encryption, anyway unlocking bootloader most probably you will lose it before.
Read carefully and do steps one by one, don´t jump nor ignore nothing of the indicated to avoid any damage. If you are not sure in some steps just stops process and ask before.
I´m not sure you that this twrp matches for your device cause I can´t try before and but will see that.
Don´t forget to provide screenies of the process if something goes wrong to can clear.
Click to expand...
Click to collapse
When I type fastboot devices nothing happens, adb says <waiting for device> and my phone is now in FASTBOOT mode...
https://ibb.co/gf9RUd
Already Installed ADB installer, extract adb.zip into my C. then run administrator.
USB Debugging and OEM Unlock has been enabled in my phone but still my PC doesn't show any serial number
I think my PC doesn't recognize my phone
CSAPawn said:
Already Installed ADB installer, extract adb.zip into my C. then run administrator.
USB Debugging and OEM Unlock has been enabled in my phone but still my PC doesn't show any serial number
I think my PC doesn't recognize my phone
Click to expand...
Click to collapse
Just copy paste all the commands that I gave you. It´s fastboot devices not fastboot device in fastboot you ever have to write exactly or the command won´t work.

[How-To][Guide] Root Pixel 3 XL with Magisk 18.1 [pre-patched boot.img] - Feb

Updates
Updated to March (.002) based on Magisk 18.1. Please update to the latest adb/fastboot files provided by Google (found in "Useful Links") the latest is "platform-tools_r28.0.2-windows.zip"
As a little plus, I've but putting the stock boots up also since we started. Below in "Useful Links" is a link to my Android File Host where you can find the stock and patched boot images.
Preface
Magisk has been updated include support for Pixel XL 3 (crosshatch) and Pixel 3 (blueline) but I figured I would patch the boot.img and upload it to here for those who want to save a small amount of time or who are lazy like myself. Mishaal Rahman has put out a guide on the XDA Portal that directly inspired this guide and I give full credit to him and topjohnwu
HOWEVER, If you are new the the root/dev/command-line scene I HIGHLY recommend that you follow Mishaal's post on the XDA Portal. He goes into a lot of further detail than I will, tells you how to unlock your bootloader if you haven't already, walks you through the installation of Magisk and has suggestions of what to do with root.
I'm going to try to make this as clean and straight to the point as possible for those of us who know the ropes but also clear and concise enough for any newcomers. All credit is being given, if I overlooked where someone deserves credit, please let me know! Well, let us get to it ya'll!
Pre-Recs IMPORTANT
Unlocked Bootloader (this means no root for Verizon Pixel 3/XL owners) If you do not know how to unlock the bootloader, follow Mishaal's "Part 1" of his post and I recommend following his entire guide for those new to this
Correctly installed and up-to-date adb/fastboot and device drivers (see below for links)
This How-To is written for Windows 10
How-To
Rooting March update (.002) Links to patched_boot.March.002img AndroidFileHost | Google Drive
Make sure you are already on the March update (ending in .002)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date (latest are platform-tools_r28.0.2 for windows)
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Open Magisk Manager, it will pop up and say "Update to latest Magisk Manager," click update.
Once in Magisk Manager, it will prompt you with additional files are needed to complete Magisk install, go ahead and download the files
After a few seconds, install will be complete and you will be rooted!
Rooting February update
Links to patched_boot.001.feb.img AndroidFileHost | Google Drive
Make sure you are already on the February update (ending in .001)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Open Magisk Manager, it will pop up and say "Update to latest Magisk Manager," click update.
Once in Magisk Manager, it will prompt you with additional files are needed to complete Magisk install, go ahead and download the files
After a few seconds, install will be complete and you will be rooted!
Rooting January Update
[Links to Patched_boot.img Jan.004 AndroidFileHost | Google Drive
Make sure you are already on the January update (ending in .004)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Go to Magisk Manager and make sure says you're rooted
Rooting December Update
[Links to Patched_boot.img December.006.Magisk18 AndroidFileHost | Google Drive
Make sure you are already on the December update (ending in .006)
Download the above zip and extract to any desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Go to Magisk Manager and make sure says you're rooted
Rooting November Update (Patched_boot.img does not work on this method so you have to do it the long way...)
November update is a bit different and we cant seem to get patched_boot.img method to work. So I will outline the process that works for rooting November below. Any guide below requires that you have the latest adb/fastboot installed and that you have an unlocked Bootloader.
If coming from rooted Sept software use this guide:
Uninstall all Magisk Modules then reboot.
Download the stock factory images for Nov.
Extract and find the "flashall.bat" .bat file
Right click > Edit
In the .bat find "-w" and DELETE it
Safe the file
After removing "-w" put phone into fastboot, plug it in, and run "flashall.bat"
Wait for it to get done and reboot
boot to system > go to settings > security and remove any pin or password or pattern
Download the latest Magisk Beta (17.3 as of writing this) and transfer to device internal storage
Now, head over to the TWRP thread and download the twrp_boot.img
Return to fastboot and open cmd in its download location
run "fastboot boot twrp-3.2.3-1-crosshatch.img" and give your device a minute or two to boot into TWRP
Once there, find and flash the magisk beta on the internal storage
reboot and test to make sure it says you're rooted
If starting fresh from November (.A1.) Update
Install November update
Download latest Magisk Beta (17.3) and move it to the internal storage of the device
Reboot to bootloader
Download the .img version of TWRP for "crosshatch"
In the location of downloaded TWRP .img, open cmd and enter
Code:
fastboot boot twrp-3.2.3-1-crosshatch.img
Allow twrp to boot (this will take a minute or two)
Then go to install and install the Magisk zip
Reboot and find magisk manager and make sure it says you're rooted
Until there is an update to the patched_boot.imgs, dont follow the how to beyond this point. In fact I am hiding it for the time being.
Rooting Sept software and software that shipped with the device
[Patched_boot.img for Sept Drive | AndroidFileHost]
Download the above zip and extract to desired location
Reboot device to bootloader: power button + volume down for 2 seconds from a power-off state, or hold volume down after issuing reboot from power menu, or issue adb command "adb reboot" after enabling adb access from developer settings
This is another reminder to make sure adb and fastboot are up to date
open cmd at the location of the extracted patched_boot.img
In cmd type
Code:
fastboot flash boot_a patched_boot.img
In cmd type
Code:
fastboot flash boot_b patched_boot.img
In cmd type
Code:
fastboot reboot
Go to Magisk Manager and make sure says you're rooted
Useful links
Magisk Thread
Link to my AndroidFileHost were all stock and patched boot images are
Direct Link to platform-tools for windows, mac and lunix from Google
Refrence for Pixel 3 XL information (factory images/vendor files/KST)
->This is the one I recommend for quick setup and newcomers 15-second adb for auto install that includes system-wide (got to post #1347 for the most upto date installer)
Manually install adb & fastboot doot drivers for WIndows 10 system wide
Installing for Lunix, MacOS and Windows thanks to the XDA Portal and Aurthor Doug Lynch
Credits
@topjohnwu (link to Magisk thread) He does amazing work; if you can donate to him
@MishaalRahman (link to his amazing instuctions on XDA Portal)
@doughLynch
and
@jlee08517
@ridobe
For being OGs and being here from the begining
This is a evolving and being updated post lol Sorry for the strange layout and poor instuctions at first
it is working now. I think you had to flashed both boot slots in order for it to work. Thank you for the post. It saved me
Thank you eqbirvin. I tried my own boot image from the factory image and tried the other boot image from another thread. (of course they both needed to be patched) I followed the directions to a "T" and kept getting stuck on the bootloader screen. I forgot word for word what it said lolol but something like cannot find secure boot slot. I used your pre patched boot image and worked the first time. Thank you again.
Does this factory reset your phone?
DarkPhoenix said:
Does this factory reset your phone?
Click to expand...
Click to collapse
Unlocking the bootloader will reset your phone... If you did that already, just installing installing magisk and rooting will not reset the phone.
jrac86 said:
Unlocking the bootloader will reset your phone... If you did that already, just installing installing magisk and rooting will not reset the phone.
Click to expand...
Click to collapse
Yeah that was a stupid question, I realized that I already knew the answer after I asked it lol.
i am getting a bootloop. my pixel 3 xl starts up to the google logo screen and does the animations but right before it displays the lock screen it crashes and restarts. i am on 030 version of pie and using the boot image that came with the factory images to root with magisk. if i flash just boot_a then i get the error no slot to boot. i have to flash both boot_a and boot_b to get to the logo screen. anyone come across this and have a fix?
also anyone notice the patched image is much smaller than the stock image?
edit: i got it to work. i had to change the patched_boot.img name to boot.img for it to work. also i used the canary build of magisk. this also works for the verizon version 031. 031 boot.img file is the one i patched. i took it from the factory images.
Got approved by androidfilehost so adding another mirror
PLEASE HELP
I followed this guide;
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Unlocked my bootloder no problem, and got to part 16 for rooting, I select Start in the bootloader and it says "Enter reason: no valid slot to boot"
Zorachus said:
PLEASE HELP
I followed this guide;
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Unlocked my bootloder no problem, and got to part 16 for rooting, I select Start in the bootloader and it says "Enter reason: no valid slot to boot"
Click to expand...
Click to collapse
Did you flash to both slots or just one? also, follow the guide again and make sure that your downloaded and patched boot.imgs are both completely downloaded AND transfered to device correctly
Is there any way to get Magisk 17.3 installed now? I didn't get it done before John Wu took down 17.3 and now magisk manager will only find 17.2 to install.
Zorachus said:
PLEASE HELP
I followed this guide;
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Unlocked my bootloder no problem, and got to part 16 for rooting, I select Start in the bootloader and it says "Enter reason: no valid slot to boot"
Click to expand...
Click to collapse
I keep getting the same error
I think that this has something to do with Magisk installing 17.2 and not 17.3
State.of.mind said:
I think that this has something to do with Magisk installing 17.2 and not 17.3
Click to expand...
Click to collapse
17.3 has been pulled for some bugs.
jlee08517 said:
17.3 has been pulled for some bugs.
Click to expand...
Click to collapse
So until there is an update
.. No root
State.of.mind said:
So until there is an update
.. No root
Click to expand...
Click to collapse
U could use canary build to root. Or some people have posted a pre patched boot image in other threads. You can use one of those.
jlee08517 said:
U could use canary build to root. Or some people have posted a pre patched boot image in other threads. You can use one of those.
Click to expand...
Click to collapse
I've tried the pre patched method and for some reason I can't get that to work
My method should work using my patched boot. It was patched with 17.3. However, If he pulled it because of bugs, I recommend holding off until he updates again to fix the bugs. I will update my patched_boot as soon as I get word that he pushes an update.
jlee08517 said:
U could use canary build to root. Or some people have posted a pre patched boot image in other threads. You can use one of those.
Click to expand...
Click to collapse
Tried the Canary build and I still get boot loops

[Guide][How-to] Unlock Bootloader, Install TWRP, GSI and Magisk

Code:
[B]DISCLAIMER[/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
**All credits for this guide go to Denver Alfito Anggada and Realme 3 pro Indonesia Group. I am just sharing it here for the benefit of those people who are not on Telegram**
UNLOCK BOOTLOADER
1.Download the In depth test APK (see attachment)
2.Open the In Depth Test application
APK then tap In Query Application Status
Request Submission then
wait about 5 minutes
4. Tap the back button in the left corner
top then reopen
In Query Application status
5. When "Review Sucessful " appeared, tap
start in depth test.
6. The device will then
enter fastboot, then plug the
device to PC. Download and install
fastboot (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/)
then move the folder named
"platform-tools" to the desktop
(recommended).
7. Open the platform-tools folder
then right-click +shift, then select
open command window here (Win
7) or Open Windows
Powershell (Windows 10)
8.a. For Windows 7, you must have
installed NET Framework
4.5. Type "fastboot flashing unlock "
b. For Windows 10, type
"./fastboot flashing unlock "
9. Then, press the volume button
to UNLOCK BOOTLOADER
10. CONGRATULATIONS! YOU HAVE
SUCCESSFULLY UNLOCKED YOUR
BOOTLOADER
HTML:
<iframe width="560" height="315" src="https://www.youtube.com/embed/mZMVohIuOYU" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
TWRP
**INTERNAL MEMORY WILL BE WIPED! BACKUP BEFORE PROCEEDING**
11. Turn off your device
12. Hold the volume key
-down + power to device
-go to fastboot
13. Plug the device into a PC / Laptop
14. Download recovery.img (https://drive.google.com/file/d/1z8Mv2IBstJchXlbsHpL-Xxup2Xr_O7gR/view)
Move the recovery file that you have downloaded into the folder platform-tools
15. Inside the folder, Shift + Right-click then select open command window here (Windows 7) or open Windows Powershell (10)
16.
a. type fastboot flash recovery.img (Windows 7)
b.
type ./fastboot flash recovery.img (Windows 10)
17. After getting OKAY written, Continue to install VBMETA (see attachment)
18. Move the vbmeta.img file into the platform-tools folder
19. Return to Windows Powershell /Command prompt then type fastboot - disabled-verity - vbmeta flash-verification-enabled vbmeta.img (Windows 7)
./fastboot - disabled-verity - vbmeta flash-verification-enabled vbmeta.img (Windows 10)
20. Press the volume button to Recovery then press power to confirm
21. After entering Recovery, make sure the device is still plugged in,the select wipe then FORMAT DATA, type yes, then tap back and reboot to recovery.
22. After returning to recovery, copy Charlie Decryption by Nitish (see attachment) to your device through computer
23. Flash fix and VOILA! you successfully installed TWRP on your device
INSTALL GSI
**ONLY FLASH A/B GSI**
24. To flash GSI, enter the GSI file on your device (make sure already in the img format, if not yet, try extracting first.
25. Then, in TWRP, press install, then open the file location you, if it doesn't appear, press install the image below right,then tap the file
26. Tap System Image and slide to flash
27. VOILA YOU HAVE SUCCESSFULLY FLASHED GSI ON YOUR DEVICE
Some GSI's you can try:
AOSIP: https://sourceforge.net/projects/il.../AOSiP-9.0-GSI-arm64_ab-20190604.img/download (or whichever is latest)
Bootleggers:https://androidfilehost.com/?fid=1395089523397961183 (or whichever is latest)
Havoc OS:https://androidfilehost.com/?fid=6006931924117888100
MAGISK
Download and extract patched image.tar (https://drive.google.com/file/d/1W1DYJJH6g7AgtT3SCCDdtag1u_F9TMX-/view?usp=drive_open)
Unlock bootloader (if you haven't)
Place all extracted images in ADB tool’s folder.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
If your device asks for permission to “Allow USB debugging”, tap OK.
Once your device boots into bootloader mode, type these into the command line.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Reboot device into system
Done
if you boot on gsi you will get full mode magisk (able to use module )
if you boot on colorOS you will get core mode magisk (not able to use module )
if you boot GSI with magisk , install magisk module named SafetyPatch , this will give you safety net passed
*THE END*​
Wow. Thanks a lot bro. Anyway have you tried the gsi rom? What knid ofbugs on realme 3 pro? Some says fingerprint not work, etc.
matrix0807 said:
Wow. Thanks a lot bro. Anyway have you tried the gsi rom? What knid ofbugs on realme 3 pro? Some says fingerprint not work, etc.
Click to expand...
Click to collapse
Fingerprint/pin/pattern not working
Problems with making calls (you can make call but cannot end it) I think it is related to VoLTE
Bluetooth music (Potential fix: Go to Vendor/Overlay/BluetoothResCommon.apk delete this apk, then reboot...BT music works...) need confirmation
Bluetooth incall audio
Confirmation
Is this process working successfully?
Yes many people have followed this method
Hb20032003 said:
Fingerprint/pin/pattern not working
Problems with making calls (you can make call but cannot end it) I think it is related to VoLTE
Bluetooth music (Potential fix: Go to Vendor/Overlay/BluetoothResCommon.apk delete this apk, then reboot...BT music works...) need confirmation
Bluetooth incall audio
Click to expand...
Click to collapse
I hope I can add busybox or Xposed modules without bricking/bootlooping my phone ?
Failed fastboot commamd
I am getting failed (write to device failed (too many links)) when using fastboot command please help
How to relock bootloader
TWRP corrupted my device when I flashed now don't wanna take more risks. How to relock the bootloader please
failed (write to device failed (too many links))
Muktesharyan said:
I am getting failed (write to device failed (too many links)) when using fastboot command please help
Click to expand...
Click to collapse
I was facing the same issue on my Windows 10. To solve the issue run the same command in a windows 7 PC. It worked for me 100%. i wasted the entire day searching for the solution. but switching to good'ol windows 7 pc fixed it.
Can someone help me..I'm stuck after the following command..
./fastboot - disabled-verity - vbmeta flash-verification-enabled vbmeta.img
Command prompt says unknown command -
PS: I modified like this.. ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img everything went smooth, but rootchecker says no root access. What might be the problem?
PS: I run magisk app, now it's been rooted.
Edit: Magisk installation is lost after sometime. No root access anymore. Guide need update. Had to follow other method. Thanks to @4j17h for helping me.
Is it possibleto unlock the bootloader without the depth test apk part?
Okay I can enter TWRP after following the first part of the guide....
until I followed the Magisk guide, then I cant enter TWRP anymore...
Also, does anyone knows how to remove that irritating red flashing saying that you rooted your device?
Hb20032003 said:
Fingerprint/pin/pattern not working
Problems with making calls (you can make call but cannot end it) I think it is related to VoLTE
Bluetooth music (Potential fix: Go to Vendor/Overlay/BluetoothResCommon.apk delete this apk, then reboot...BT music works...) need confirmation
Bluetooth incall audio
Click to expand...
Click to collapse
Hi,
I am trying to delete BluetoothResCommon.apk , but it says file system is read only , Can someone help me out here.
Regards
Need help
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
do you have tutorial to remove bloatware/pre-installed in RM 3 Pro ?
No bootloader
Hi, I tried to unlock the bootloader of my Realme 3 Pro on latest version A15, but something went wrong after the Depth Test app.
When I try to boot the bootloader, it only shows me a monkey icon, with letters in chinese (I guess), with something like 6 10 written, then it reboot.
Tried to install stock A14, but nothing changed.
Would be glad if someone know a solution.
jayroulm953 said:
do you have tutorial to remove bloatware/pre-installed in RM 3 Pro ?
Click to expand...
Click to collapse
If you're rooted then no worries, just use TiBu to uninstall all those bloatwares.
Samdroid18 said:
If you're rooted then no worries, just use TiBu to uninstall all those bloatwares.
Click to expand...
Click to collapse
without root ? no chance ?
Hello...!!!! Do you know why the phone does not go into fastboot mode when you start the depth test? It restarts in system mode. Thank you.
Pasku21 said:
Hello...!!!! Do you know why the phone does not go into fastboot mode when you start the depth test? It restarts in system mode. Thank you.
Click to expand...
Click to collapse
I have exactly the same problem, I don't know what to do...

Rooting CLT-L29 (P20 Pro) UK with EMU 9.1.0.381 and Magisk (and TWRP if you want)

P20 Pro with EMUI 9.1 (9.1.0.381 c782e11r1p11 clt-l29) and root!! But it only lasts until a reboot according to Magisk
Note with the latest Magisk I still cannot get root to persist after a reboot. (v20.4 20400)
Rooting without TWRP Recovery
Terms
Recovery Image= an image which runs on your phone to facilitate recovery, we are looking to patch it with a magisk binary
Stock Firmware = the OS installed on your phone by the manufacturer/network operator (branding). We aren't looking to replace this, but we do need to extract a file from the version you currently have
Stock Recovery = the recovery image installed with the P20 'eRecovery'
Recovery RAMdisk - This is where the recovery image is flashed. Alternative locations are the bootloader or the recovery partition. None of these work with EMUI 9.1
Commands are in italics
Prerequisites
adb binary
fastboot binary
Phone is backed up (unlocking the bootloader will factory reset and erase all data/apps)
Phone is plugged in and showing with 'adb devices'
You have a bootloader code
0. Unlock your bootloader
adb reboot bootloader
Once in fastboot mode type
fastboot oem unlock <unlock code>
Let the process finish.
1. Extract stock recovery image (RECOVERY_RAMDIS.img) from the Stock Firmware using Huawei Update Extractor
Get Stock Firmware for your version from :https://pro-teammt.ru/en/online-firmware-database/
Get Huawei Update Extractor from https://forum.xda-developers.com/showthread.php?t=2433454
Get the RECOVERY_RAMDIS.img file using these instructions https://www.theandroidsoul.com/extract-huawei-firmware-update-app
Rename the RECOVERY_RAMDIS.img file something logical based on your EMUI version e.g. I've renamed mine RECOVERY_RAMDIS_9_1_0_381_STOCK.img
2. Using Magisk Manager app, patch the stock recovery image extracted in Step 1
Get Magisk Manager and install the APK (IT's NOT on the Play Store (despite being called the same name)
Magisk Manager is available here. I would suggest installing a stable version or you maybe risking a boot loop.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
or google for it. This forum blocks the URL for some reason.
Once you have installed the APK...
Tap 'Install' next to 'Magisk is not installed' .
Tap 'Install' again
Tap 'Select and Patch a File', then choose the file RECOVERY_RAMDIS_9_1_0_381_STOCK.img (or whatever you called it)
3. Copy the patched recovery image file Magisk just created to your PC
(Magisk will tell you where it put it, generally in your 'Downloads' folder)
4. Flash the Patched Recovery Image using fastboot mode
Note not possible to flash the boot or recovery with Magisk/TWP on EMUI 9+ you have to flash recovery_ramdisk
adb reboot bootloader
fastboot flash recovery_ramdisk RECOVERY_RAMDIS_9_1_0_381_PATCHED.img
(replace RECOVERY_RAMDIS_9_1_0_381_PATCHED.img file with whatever you called it)
NOW read step 5. Get ready and then...
fastboot reboot
5.This step is very important l!
As soon as you issue the reboot command and the screen goes blank, you will need to press and hold volume up and power buttons simultaneously for a few seconds.
When you're doing this, unplug the USB cable. As soon as you see the Huawei logo, release BOTH keys
You will see the unlock warning, but if you did it right, you will not see instructions on the screen telling you what to press to continue etc
If you see instructions telling you to press a key combination to continue, you didn't do it right and will need to start again at step 4 after the phone reboots.
6. Check Root with Magisk Manager/Another root tool
TWRP
You can also flash TWRP using the version at https://dl.twrp.me/charlotte/ or
Alternative: Install Magisk from TWRP? search google for "install-twrp-recovery-root-huawei-p20-pro" to find a link from the custom droid
Just replace the file in step 4 with the .img file from that URL
You can only flash TWRP or MAGISK. I've not been able to load the Magisk (optained from the Magisk Manager) through TWRP as the internal storage is not accessible
and OTG storage doesn't seem to be accessible either.
I am not 100% sure how this works as magisk occupies the recovery_ramdisk just like twrp:
Connect your phone to the PC (while it’s in TWRP) mode.
In TWRP, go to ‘Advanced’ and enable ‘ADB Sideload’.
Then, enter the following command on PC: adb sideload Magisk-v20.3.zip
Boot Lockup
If you experience a boot lockup (especially when trying to boot to recovery with power + vol up) you can do an adb reboot and boot with holding vol up
This will open EMUI erecovery and you can then choose reboot to boot normally to the system.
It all worked for me, for CLT-L09. And even keeping root after rebooting. With standard Magisk 20.4.

Categories

Resources