Database Info

[ROOT][TRIAL][MAGISK] P20 Pro - Try out on Rooting Method

Hi Guys,
Note : By doing this, you know that you're gonna do a modification to your phone, and im not in any way, responsible for what happen after. Escape Route for if something wrong happen is provided, but YOU DO THIS ON YOUR OWN RISK
since this phone is fairly new, at this moment a clear rooting method haven't established yet. This is what this thread for.
Based on information gathered from P20 Lite Forum (the rooting guide for that device even already up - here), it seems the old trick of rooting (from Mate 10 Pro) using Patched Boot Method is working fine. And Magisk is working
Basically this method need few pre-requisites :
1. Unlocked Bootloader (by getting the code here ) - and if you not sure how to do it, go here for the guide
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
3. Magisk Manager 5.5.4 (from Magisk Thread) to patch the .img above, or
4. Patched RAMDISK image (i patched it) from here
5. and of course computer with ADB & Fastboot installed (make sure you have latest SDK to prevent something not working)
Now, to Root it, all you need to do is,
1. Boot into bootloader
2. Type
Code:
fastboot flash ramdisk patched_boot.img
(patched_boot.img is the file you download from prerequisites number 4, placed it in the same directory with your adb & fastboot - i assume you know that already)
3. Reboot
4. You now should have root access, download Magisk Manager to manage modules and superuser
(you might need to flash this module if you failed to pass safetynet)
In case something go wrong, flash back the stock RAMDISK from pre-requistes number 2 above using same method as what u did to flash the patched one.

That way worked. Thanks.
Edit:
Just as a hint. To get magisk work as it should..
After boot into the system and installed Magisk Manager, install Magisk from there again, so you dont get any /data/magisk problems.
SafteyNet passed then.

Fingers crossed twrp is possible soon

Works on CLT-L09
I have a German single Sim from Vodafone tested the root yesterday and works very well

Would this method work on CLT-L09 model? Thanks

danifilth4king said:
Would this method work on CLT-L09 model? Thanks
Click to expand...
Click to collapse
The post before you just confirmed yourbquestion, LoL
Yes it does

This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
otonieru said:
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
Click to expand...
Click to collapse

fl4r3 said:
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
Click to expand...
Click to collapse
It's from www.allrom.ir (its in persian) and there's another site, rusian one if am not mistaken, but i forget the exact address

Great, thanks for that! I managed to find it on allrom.ir

Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post

danifilth4king said:
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
Click to expand...
Click to collapse
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?

otonieru said:
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
Click to expand...
Click to collapse
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks

danifilth4king said:
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
Click to expand...
Click to collapse
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?

otonieru said:
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
Click to expand...
Click to collapse
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?

danifilth4king said:
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
Click to expand...
Click to collapse
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well

otonieru said:
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
Click to expand...
Click to collapse
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!

danifilth4king said:
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
Click to expand...
Click to collapse
Its better to do it from ON state, and use adb reboot bootloader command

otonieru said:
Its better to do it from ON state, and use adb reboot bootloader command
Click to expand...
Click to collapse
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol

danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Put the device off and hold power button and volume down. You should come directly into the rescue mode.

danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Ah, sorry, i got it wrong. Yes, its power n volume down.

How To Root Oxygen 5.1.7

Oneplus updated the OnePlus 6's Bootloader and you may ask yourself 'Can i still root?'
The answer is yes. It is easy.
1. At first, your bootloader has to be unlocked
2. Just download the Twrp.img and the Twrp installer from twrp.me, then the latest magisk installer
3. Put the magisk.zip and twrp installer zip into the root of your device and boot into bootloader
4. Now you have to open a new shell or cmd window in your adb folder, then type "Fastboot devices" there
5. If your phone is recognized, then do this command: " fastboot boot .\twrp-3.2.1-0-enchilada.img"
6. The op6 should boot into the TWRP, there type in your pincode, pattern, or what so ever you have. If you get a message because of system modification, click 'Keep read only'
7. Go to 'Install', then flash the TWRP installer zip, then magisk right after it
8. Just reboot and enjoy
The procedure is the same as always. I can confirm it's working because i rooted a few minutes ago

Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.

iElvis said:
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
Click to expand...
Click to collapse
Forgot the mention that, thanks!

Edit: Screenshots

Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol

joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Sorry, I thought that would be helpful for people who are worried about root because of updated bootloader.
A Moderator can remove this thread then

joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Based on how things have been going so far, people are going to be asking. Just saying.

i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol

So if I already have twrp and Magisk installed is the method still the same?
Will this update lock the bootloader back?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?

joemossjr said:
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
Click to expand...
Click to collapse
Yes I know. I mean, you're right. Thought something like "new bootloader, new confusions". I justed wanted to help people if they're worried of a brick

dgunn said:
So if I already have twrp and Magisk installed is the method still the same?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
Click to expand...
Click to collapse
Don't worry. You can use TWRP and your phone itself as always

Sconny said:
Don't worry. You can use TWRP and your phone itself as always
Click to expand...
Click to collapse
So do I flash the update in twrp?
Must the bootloader be unlocked again?

dgunn said:
So do I flash the update in twrp?
Must the bootloader be unlocked again?
Click to expand...
Click to collapse
No you flash in system via local upgrade

joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash with local upgrade, reboot to fastboot, run twrp.img, install twrp, flash Magisk and reboot? No unlocking bootloader again?
If not correct please tell me

Yup that's it

joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?

BossNexusS said:
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
Click to expand...
Click to collapse
Yes

joemossjr said:
Yes
Click to expand...
Click to collapse
What were the steps you followed if you don't mind?

Maybe someone will upload the full rom?

anyone tried hiding system updates inside magisk hide ?
it now shows only 224 update (canadian vpn), hence don't know what it will do when you take that route, anyone ?

[VS995][Oreo][Stock][Rooted] Verizon LG V20 Stock Oreo rooted flashable zip

Made this for myself, but you guys can use it to. It's stock VS995 Magisk patched (aka rooted) Oreo
Download: https://drive.google.com/file/d/129CRgvyjtc1fF01l-_fi6kLReE3oXD_L/view?usp=sharing
Ignore the "NO OS INSTALLED" prompt in TWRP if you get one after installation. It's a TWRP bug.

Anyone know if this will work on US996 on the Verizon Network?

baldybill said:
Anyone know if this will work on US996 on the Verizon Network?
Click to expand...
Click to collapse
He just posted it why don't you try it and find out if it works.
Sent from my LG-H910 using XDA Labs

This is amazing, how did you build this zip?

Can I install it on H910?

Rooted Oreo vs995 has working data?
Cause for other dirty Santa versions like h910/h915 Oreo, using it with magisk patched boot, keeping eng aboot and recovery, the Oreo modem won't work properly. The rest of the phone will be fine.

Thank you for the rom...got it on verizon dirty flash over alpharom it work...call and 4g work fine!! Waiting for kernel to fix static

Thanks you for the job.

cnjax said:
He just posted it why don't you try it and find out if it works.
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
This is intentionally bad advice. If you attempt to do this, my advice is make sure you have a KDZ to recover to and delete all files in /images EXCEPT system.bin and boot.bin. Cross-flashing bootloader partitions is a bad idea.

darkknight200 said:
Rooted Oreo vs995 has working data?
Cause for other dirty Santa versions like h910/h915 Oreo, using it with magisk patched boot, keeping eng aboot and recovery, the Oreo modem won't work properly. The rest of the phone will be fine.
Click to expand...
Click to collapse
Yes, everything works as intended except static on boot. I recommend enabling secure startup and toggling your screen before entering the startup pin so you can very quickly get rid of it.

NotYetADev said:
Yes, everything works as intended except static on boot. I recommend enabling secure startup and toggling your screen before entering the startup pin so you can very quickly get rid of it.
Click to expand...
Click to collapse
So that means you still have twrp recovery?

darkknight200 said:
So that means you still have twrp recovery?
Click to expand...
Click to collapse
You have to go into fastboot and re-flash it. I'd wait until you have gotten past setup wizard to do so, though.

NotYetADev said:
You have to go into fastboot and re-flash it. I'd wait until you have gotten past setup wizard to do so, though.
Click to expand...
Click to collapse
To clarify, the phone doesn't have dirty Santa engineer aboot anymore after flashing the zip because it gets replaced with stock aboot? But u can still flash twrp thru fastboot still?

darkknight200 said:
To clarify, the phone doesn't have dirty Santa engineer aboot anymore after flashing the zip because it gets replaced with stock aboot? But u can still flash twrp thru fastboot still?
Click to expand...
Click to collapse
It still has the engineering aboot, so you still have fastboot.

NotYetADev said:
It still has the engineering aboot, so you still have fastboot.
Click to expand...
Click to collapse
hm ok. So the vs995 oreo is the first variant that has working data with eng aboot then.
edit: @askermk2000 for vs995 oreo mk2000 kernel.

Thank you so much!

So once we get the phone going again, just go into the bootloader and do "fastboot flash recovery twrp.img"? (with the right filename) and we get a working TWRP back?
Thank you!!!!

Buzzy42 said:
So once we get the phone going again, just go into the bootloader and do "fastboot flash recovery twrp.img"? (with the right filename) and we get a working TWRP back?
Thank you!!!!
Click to expand...
Click to collapse
I try to that it does flash twrp but when I try get in twrp mode it only flash a logo then boot I also try to delete recovery.bin in the zip but not work so...also tryna debloat app througt root uninstall but some how system folder doesn't mount...

darkknight200 said:
edit: @askermk2000 for vs995 oreo mk2000 kernel.
Click to expand...
Click to collapse
I am building kernel now.
Could someone on this ROM do:
Code:
cat /proc/cmdline
I just want to check something before my kernel is installed.

askermk2000 said:
I am building kernel now.
Could someone on this ROM do:
Code:
cat /proc/cmdline
I just want to check something before my kernel is installed.
Click to expand...
Click to collapse
elsa:/ # cat /proc/cmdline
sched_enable_hmp=1 sched_enable_power_aware=1 app_setting.use_32bit_app_setting=1 kpti=1 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] androidboot.hardware=elsa buildvariant=user slub_debug=FZPU lge.rev=rev_10 model.name=LG-US996 lge.bootreason=0x8f58a242 cc_mode=0 kswitch lge.bootreasoncode=0x8f58a242 bootcable.type=NO_INIT lge.battid=SW3800_VC0 androidboot.dlcomplete=0 androidboot.ddr_size=4294967296 androidboot.ddr_info=0x6 lge.crash_handler=on lge.hreset=off boot_cpus=0-3 androidboot.revision=12 androidboot.verifiedbootstate=red androidboot.veritymode=enforcing androidboot.rpmb_state=1 androidboot.bootdevice=624000.ufshc androidboot.serialno=LGUS996e04caf92 lge.signed_image=true androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_sw49407_dsc_qhd_cmd:config1:1:none:cfg:single_dsi
elsa:/ #

Rooting of Poco x2 MIUI 12

Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......

KartikBapna said:
Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......
Click to expand...
Click to collapse
I successfully rooted the EU miui 12 rom earlier and there wasn't any bootloop.

KartikBapna said:
Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......
Click to expand...
Click to collapse
Be careful brother, there are no fastboot images of MIUI 12. If you end up bricking it, you'll have to wait 1 whole month for "miui 12 fastboot imgs" to arrive.

tuskan_supa said:
I successfully rooted the EU miui 12 rom earlier and there wasn't any bootloop.
Click to expand...
Click to collapse
superminnu said:
Be careful brother, there are no fastboot images of MIUI 12. If you end up bricking it, you'll have to wait 1 whole month for "miui 12 fastboot imgs" to arrive.
Click to expand...
Click to collapse
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?

KartikBapna said:
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?
Click to expand...
Click to collapse
Are you on the Indian build or EU build?

tuskan_supa said:
Are you on the Indian build or EU build?
Click to expand...
Click to collapse
Indian

KartikBapna said:
Indian
Click to expand...
Click to collapse
I did successfully on the EU build not on Indian. I guess you should wait few days maybe someone will try and figure it out.

KartikBapna said:
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?
Click to expand...
Click to collapse
Isn't flash Magisk will always disable dm-verity?

Never_Sm1le said:
Isn't flash Magisk will always disable dm-verity?
Click to expand...
Click to collapse
It didn't disable it in my POCO....

KartikBapna said:
It didn't disable it in my POCO....
Click to expand...
Click to collapse
And now I realize the problem in you answer. Why did you need to write into the system partition?

Never_Sm1le said:
And now I realize the problem in you answer. Why did you need to write into the system partition?
Click to expand...
Click to collapse
What is the advantage of root access if you can only read partitions not write them
And also, I want to install and uninstall apps in system partition.

KartikBapna said:
What is the advantage of root access if you can only read partitions not write them
And also, I want to install and uninstall apps in system partition.
Click to expand...
Click to collapse
You can't, because since Android 10 Google made the /system partition read-only. You can use adb to disable those app, uninstall apps in /system does not help you gain any free space anyway.

Never_Sm1le said:
You can't, because since Android 10 Google made the /system partition read-only. You can use adb to disable those app, uninstall apps in /system does not help you gain any free space anyway.
Click to expand...
Click to collapse
I don't want any free space just want to remove bloatware and install some apps in system like appninja's app

KartikBapna said:
I don't want any free space just want to remove bloatware and install some apps in system so like appninja's app
Click to expand...
Click to collapse
you can remove bloat with adb command, and install app in system using app systemizer. Install things in /system is old-school

Never_Sm1le said:
you can remove bloat with adb command, and install app in system using app systemizer. Install things in /system is old-school
Click to expand...
Click to collapse
Can't install apps with systemizer because app always crashes after moving to system.
Root is used for many things like running modules so my problem is still there how to root Poco X2 running on MIUI 12
Also systemizer is a module which requires root as well as magisk

KartikBapna said:
Can't install apps with systemizer because app always crashes after moving to system.
Root is used for many things like running modules so my problem is still there how to root Poco X2 running on MIUI 12
Also systemizer is a module which requires root as well as magisk
Click to expand...
Click to collapse
Do as usual? Or there's a different thing involved? On my redmi K30 MIUI 12, things is as simple as unlock bootloader, boot the recovery, do not swipe modify system then flash the recovery, reboot to recovery then flash magisk. I have never encounter dm-verity before when follow these steps.

Never_Sm1le said:
Do as usual? Or there's a different thing involved? On my redmi K30 MIUI 12, things is as simple as unlock bootloader, boot the recovery, do not swipe modify system then flash the recovery, reboot to recovery then flash magisk. I have never encounter dm-verity before when follow these steps.
Click to expand...
Click to collapse
Things I have tried after unlocking bootloader and then flashing the recovery
1) flash magisk zip result bootloop
2) flash patched boot.img result bootloop
3) flash patched recovery.img result bootloop
In MIUI 11 method 2 worked
Method 1 always gave bootloop

KartikBapna said:
Things I have tried after unlocking bootloader and then flashing the recovery
1) flash magisk zip result bootloop
2) flash patched boot.img result bootloop
3) flash patched recovery.img result bootloop
In MIUI 11 method 2 worked
Method 1 always gave bootloop
Click to expand...
Click to collapse
Did you use fastboot flash twrp.img or fastboot boot twrp.img?

Never_Sm1le said:
Did you use fastboot flash twrp.img or fastboot boot twrp.img?
Click to expand...
Click to collapse
I flashed twrp that means I used
fastboot flash recovery twrp.img
And then to boot
fastboot boot twrp.img
I flashed patched boot.img from twrp.
My phone boots up with twrp flashed.

KartikBapna said:
I flashed twrp that means I used
fastboot flash recovery twrp.img
And then to boot
fastboot boot twrp.img
I flashed patched boot.img from twrp.
My phone boots up with twrp flashed.
Click to expand...
Click to collapse
Try my way: boot TWRP then flash TWRP.img from TWRP. Reboot to recovery again then flash Magisk zip. Flash patched boot.img is unnecessary, like Topjohnwu said it's only for devices without TWRP. Beside if you want to use the patched method, you must patch the stock recovery image not TWRP.

How to extract boot.img from a rooted phone without twrp?

Hello, my phone doesn't have TWRP support, so i need to extract the boot.img from it so that I can install magisk. I am able to root it with KingoRoot. So How to extract boot.img from a rooted phone without twrp?

GauchoTche said:
Hello, my phone doesn't have TWRP support, so i need to extract the boot.img from it so that I can install magisk. I am able to root it with KingoRoot. So How to extract boot.img from a rooted phone without twrp?
Click to expand...
Click to collapse
As that question interested me as weil I did a bit of searching .
Found this thread
with the appropriate changes for your device/partitions it might work.

bmwdroid said:
As that question interested me as weil I did a bit of searching .
Found this thread
with the appropriate changes for your device/partitions it might work.
Click to expand...
Click to collapse
How to know what is the path to boot.img partition?
Where do i run those dd commands? Windows?

GauchoTche said:
How to know what is the path to boot.img partition?
Click to expand...
Click to collapse
If your device is on less than Android Q (you didn't tell) "DiskInfo 4.9.9 (build 10)_49910.apk" might tell you.
Did it on mine before I upgraded.
GauchoTche said:
Where do i run those dd commands? Windows?
Click to expand...
Click to collapse
I think that any terminal should work no matter which OS.