Related
STEP BY STEP GUIDE FOR LG V20 H918 UNLOCKING BOOTLOADER, DOWNGRADING, ROOTING AND INSTALLING CUSTOM ROMS (NOOB FRIENDLY)
DISCLAIMER: I'M NOT THE DEVELOPER OF ANY OF THE BELOW SOFTWARE'S AND YOU PROCEED WITH YOUR OWN RISK AS THIS INVOLVES BRICKING OR DAMAGING YOUR MOBILE IF THE PROCEDURE IS NOT FOLLOWED CORRECTLY. I'M JUST SHARING THE WHOLE PROCESS WHICH I HAVE FOLLOWED TO ROOT AND INSTALL TWRP IN MY LGV20 H918 UNLOCKED T MOBILE.
AND I HAVE TESTED THIS IN MY OWN DEVICE AND WAS ABLE TO ROOT AND ACHIEVE TWRP.
THIS IS ONLY FOR LGV20 H918 VERSION
ENSURE INTERNET IS UP AND RUNNING IN YOUR PC
EDIT: THE WHOLE PROCESS HAS NOW BEEN AUTOMATED IN TWO SIMPLE STEPS TO PREVENT ANY POTENTIAL DAMAGE TO YOUR DEVICE. THANKS TO THE LAFSPLOIT CREATOR BRIAN @runningnak3d.
JUST FOLLOW THE PROCEDURE BELOW AND YOU SHOULD HAVE YOUR DEVICE ROOTED IN NO TIME
1. BACKUP ALL YOUR IMPORTANT DATA BEFORE PROCEEDING.
2.MAKE SURE YOU HAVE CHARGED YOUR PHONE TO AT LEAST 90 PERCENT
CHECK YOUR PHONE SOFTWARE VERSION IN SETTINGS---ABOUT PHONE----SOFTWARE INFO
IF IT IS ANYTHING BETWEEN H91810P TO H91810U MEANS IT IS ARB1 (ANTI ROLL BACK 1) AND YOU NEED TO USE LAFSPLOIT METHOD TO ROOT AND INSTALL TWRP,
IF YOUR VERSION IS H91810O OR BELOW (ARB0), YOU CAN EITHER USE DIRTYCOW OR LAFSPLOIT METHOD FOR THE SAME.
IF YOU ARE ON ARB1, PLEASE FOLLOW THE METHOD BELOW,
PART 1: DOWNGRADING
IF YOUR VERSION IS H91810 (Q, R, S, T, U) YOU NEED TO DOWNGRADE TO A LOWER VERSION ( H91810P) TO EXECUTE LAFSPLOIT.
IF YOU ARE ALREADY ON H91810P, YOU STILL NEED TO RE FLASH THE H91810P KDZ AGAIN FOR THE LAFSPLOIT SCRIPT TO WORK CORRECTLY.
DOWNLOAD H91810P KDZ FILE FROM BELOW
https://androidfilehost.com/?w=files&flid=282709
DOWNLOAD AND INSTALL ALL THE FILES BELOW IN YOUR PC
UPPERCUT AND LGUP----
http://downloads.codefi.re/autoprime/LG/Flash_Tools/LGUP/
LG DRIVERS---
http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
CONNECT YOUR MOBILE TO YOUR PC IN DOWNLOAD MODE (SWITCH OFF YOUR MOBILE AND CONNECT THE USB FROM PC WHILE HOLDING THE VOLUME UP BUTTON SIMULTANEOUSLY)
RUN UPPERCUT.EXE WHICH WOULD OPEN LG'S UPDATER TOOL AUTOMATICALLY.
INSIDE THE LG UPDATER TOOL, CLICK ON BIN AND SELECT THE H91810P KDZ FILE DOWNLOADED EARLIER.
NOW SELECT UPGRADE AND FLASH
ENSURE THE USB CABLE IS CONNECTED THROUGH THE FLASHING PROCESS AND WAIT FOR YOUR PHONE TO REBOOT AND THEN REMOVE THE USB CABLE.
CHECK THE SOFTWARE VERSION AND ENSURE IT IS H91810P
PART 2: UNLOCKING BOOTLOADER
HEAD TO SETTINGS---ABOUT PHONE----SOFTWARE INFO (ENSURE IT IS H91810P)
ENABLE DEVELOPER OPTION IN YOUR PHONE BY CLICKING ON THE BUILD NUMBER MULTIPLE TIMES
NOW HEAD TO SETTINGS---DEVELOPER OPTIONS
TURN ON OEM UNLOCKING, ENABLE USB DEBUGGING AND DISABLE 'VERIFY APPS OVER USB'
NOW CONNECT YOUR PHONE TO PC AND OPEN ADB COMMAND CENTER PROMPT IN YOUR PC
adb devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN ADB
adb reboot bootloader--->THIS REBOOTS YOUR DEVICE IN FASTBOOT MODE
fastboot devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN FASTBOOT
fastboot oem unlock---->THIS COMMAND WOULD UNLOCK YOUR BOOTLOADER AND RESET's YOUR DEVICE.
fastboot oem device-info OR fastboot getvar unlocked ----->THIS WOULD CONFIRM IF YOUR BOOTLOADER HAS BEEN UNLOCKED OR NOT.
fastboot reboot-----> THIS WOULD REBOOT YOUR DEVICE
IF THE BOOTLOADER HAS BEEN SUCCESSFULLY UNLOCKED, THE DEVICE WILL SHOW AN UNLOCKED BOOTLOADER WARNING MESSAGE WHILE BOOTING (THIS CAN BE IGNORED OF COURSE)
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
PART 4: INSTALLING TWRP AND ROOTING USING LAFSPLOIT
BEFORE PROCEEDING ENSURE YOU BOOT YOUR PHONE AND DONE ALL THE BASIC SETTINGS
NOW HEAD TO THE DEVELOPER OPTIONS IN YOUR DEVICE AND ENSURE OEM UNLOCKING AND USB DEBUGGING ARE SWITCHED ON.
NOW CONNECT YOUR DEVICE TO THE PC (RUNNING LINUX OS FROM PENDRIVE) IN DOWNLOAD MODE (SWITCH OFF YOUR MOBILE AND CONNECT THE USB FROM PC WHILE HOLDING THE VOLUME UP BUTTON SIMULTANEOUSLY)
DOUBLE CLICK ON THE LG FOLDER INSIDE FWUL DESKTOP
INSIDE THAT, DOUBLE CLICK ON LGLAF(RUNNINGNAK3D) ICON WHICH WILL OPEN A TERMINAL
ENTER THE BELOW COMMANDS
git pull
git checkout h918-miscwrte
./step1.sh
THE ABOVE COMMAND FLASHES TWRP RECOVERY ONTO YOUR DEVICE.
WAIT AND PULL OUT YOUR DEVICE WHEN IT ASKS TO.
RECOMMENDED: NOW THAT TWRP HAS SUCCESSFULLY INSTALLED, YOU CAN MANUALLY FORMAT,FLASH LATEST TWRP RECOVERY AND USE ANY METHOD LIKE MAGISK OR SU FOR ROOTING.
INSIDE TWRP RECOVERY. FIRST FORMAT USING WIPE--ADVANCED FORMAT--TYPE yes AND FULL DO A FULL FORMAT, THEN FLASH MAGISK AND THE LATEST TWRP RECOVERY BELOW.
MAGISK ZIP DOWNLOAD:
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
LATEST TWRP BY PHOENIX(H918):
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
OR
IF YOU ARE UNSURE ABOUT FORMATTING AND FLASHING, JUST USE THE BELOW COMMAND TO DO ALL THE WORK AUTOMATICALLY
CONNECT YOUR DEVICE AGAIN IN DOWNLOAD MODE AND ENTER THE FOLLOWING COMMAND
./step2.sh
THE ABOVE COMMAND FORMATS YOUR DEVICE AND FLASHES MAGISK TO ACQUIRE ROOT.
TIP : IF YOU FACE ANY ENCRYPTION ERROR AFTER USING STEP2. SH, DO A ADVANCED FORMAT WITHIN TWRP AND FLASH MAGISK AND LATEST TWRP BY PHOENIX MANUALLY.
YOU ARE NOW ROOTED WITH TWRP RECOVERY INSTALLED.
REMEMBER TO BACK UP THE CURRENT ROM BEFORE FLASHING ANYTHING..... DO CHECK POST #2 FOR OTHER TWEAKS
IF YOU WISH TO UPDATE TO LATEST STOCK (10U) AND KEEP ROOT AND TWRP, JUST FOLLOW THIS LINK AND DO REMEMBER TO ROOT USING MAGISK AFTER FLASHING THE ROM BEFORE YOU BOOT.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
I WOULD LIKE TO THANK ALL THE DEVOLEPERS WHO HAVE CREATED THE ABOVE SOFTWARES WITHOUT WHICH THIS ISNT POSSIBLE.
CREDITS:
@autoprime FOR HIS UPPERCUT TOOL
@steadfasterX FOR HIS FWUL TOOL
@Phoenix591 FOR HIS WORKS ON TWRP RECOVERY
AND FINALLY, @runningnak3d FOR HIS EXCELLENT WORK IN ROOTING OUR DEVICE :good:
WHAT NEXT?
NOW THAT YOU HAVE ROOTED YOUR MOBILE, I WOULD RECOMMEND DOING THE BELOW TWEAKS FOR FURTHER ENHANCED EXPERIENCE....
1.THERMAL THROTTLING
IF YOUR ARE STILL ON A STOCK BASED ROM , I WOULD STRONGLY RECOMMEND TO RECONFIGURE YOUR THERMAL FILE TO PREVENT ANY POSSIBLE LAG WHEN USING EXTENSIVELY...
FIRST DOWNLOAD THE FILE BELOW:
https://drive.google.com/file/d/0B0W3xXHgfOxvLUpKNWhrWDE0TDg/view
USE A ROOT EXPLORER (PREFERABLY ES EXPLORER) AND GO TO ROOT/SYSTEM/ETC.
YOU SHOULD HAVE A FILE NAMED thermal-engine-8996.conf
RENAME IT TO thermal-engine-8996.conf.bak (JUST FOR A BACKUP IF ANYTHING GOES WRONG)
ENSURE THE ABOVE DOWNLOADED FILE IS IN .conf FORMAT
IF IT ISN'T , RENAME TO thermal-engine-8996.conf
NOW SAVE THE FILE TO THE SAME DIRECTORY VIZ ROOT/SYSTEM/ETC
GIVE PERMISSION TO THIS FILE TO rw-r--r-- USING THE ROOT EXPLORER ( SELECT FILE--->PERMISSION--->READ WRITE, READ, READ)
FINALLY SAVE AND REBOOT.
THIS WOULD OVERWRITE THE THERMAL LINKED PERFORMANCE OF THE CPU TO AVOID ANY LAG WHEN USING EXTENSIVELY.
2. RCTD REMOVER
ALSO I WOULD STRONGLY RECOMMEND TO REMOVE THE LG'S RCTD CCMD AND TRITON MONITORS AS THESE WOULD RUN CONTINUOUSLY IN A ROOTED LG PHONE AND CONSUME LOT OF RESOURCES...
JUST INSTALL THE RCTD REMOVER APP FROM BELOW LINK:
https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
GRANT SU PERMISSION AND CHECK THE DESIRED FILES (I CHOSE ALL THREE FILES) AND CLICK ON PATCH, FLASH IMAGE AND REBOOT (THIS WOULD PATCH THE BOOT FILE, SO AGAIN IT IS ADVISABLE TO CREATE A BACKUP OF THE CURRENT BOOT IMAGE USING TWRP OR WITHIN THIS APP ITSELF)
3. SCREEN CALIBRATION:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
INSTALL KERNAL AUDITOR APP FROM PLAY STORE AND GRANT SU ACCESS
CHANGE THE BELOW VALUES WITHIN THIS APP (SCREEN SETTINGS)
Minimum RGB value = 35
Saturation Intensity = 27
Screen Hue = 1520
Screen Value = 112
Screen Contrast = 132
THIS WOULD SOMEWHAT REDUCE THE BLUE TINGE AND GHOST APPEARANCES OF THE SCREEN
CREDITS: @Holyman007 for his thermal tweak @Zacharee1 for his rctd remover app
I was just about to create a post asking for a step by step for dummies so thank you very much for this! Going to do this sometime tomorrow or Tuesday and will update if I succeed or not. :good:
Got a question. Does this method stop the second screen from working?
turdbait said:
I was just about to create a post asking for a step by step for dummies so thank you very much for this! Going to do this sometime tomorrow or Tuesday and will update if I succeed or not. :good:
Got a question. Does this method stop the second screen from working?
Click to expand...
Click to collapse
this would end up with a stock rooted phone with twrp recovery if all the methods are correctly followed..
......final result would be.... you would end up with a rooted stock rom with a twrp recovery....
your second screen will work perfectly.....
please let me know if you need a different thread for installing custom rom, and to reduce the lag., install sound mod to get maximum sound output and customize second screen... i will create a noob friendly thread for these as well......
Also check the original lafsploit thread @
https://forum.xda-developers.com/v20/how-to/root-lafsploit-h918-version-t3773443
kish9046 said:
Also check the original lafsploit thread @
https://forum.xda-developers.com/v20/how-to/root-lafsploit-h918-version-t3773443
Click to expand...
Click to collapse
Thank you, I've been reading up on the main lafsploit thread for awhile but I was still not sure about the whole flashing KDZ file and stuff so when you posted this thread it was a motivator to try it out. Got a day off from work tomorrow so gonna try it then so I don't got to worry about the time.
I'm interested in the max sound output and second screen customization if you got the time and its not to much to ask. If you want to wait till either someone else comes along thats interested or till I root just so you don't waste your time I shall update hopefully sometime tomorrow. Thanks again.
kish9046 said:
sha256sum h918-twrp.img ----> THIS WOULD AGAIN THROW A HASH, CHECK IF BOTH THE HASHES ARE ABSOLUTELY SIMILAR
Click to expand...
Click to collapse
Excellent. Just a friendly suggestion, however. I would change the instruction above to use the word EXACT instead of SIMILAR, otherwise people may continue erroneously. The hash numbers must be exact.
onlineaces said:
Excellent. Just a friendly suggestion, however. I would change the instruction above to use the word EXACT instead of SIMILAR, otherwise people may continue erroneously. The hash numbers must be exact.
Click to expand...
Click to collapse
Thanks for the heads up.... Changed to EXACT...
I successfully have root now, thank you! If you're still interested in doing a guide on how to do the second screen customization I'd be grateful.
turdbait said:
I successfully have root now, thank you! If you're still interested in doing a guide on how to do the second screen customization I'd be grateful.
Click to expand...
Click to collapse
great to hear that u have root now.... will post soon on other mods including a step-by-step process on removing rct soon....
All this stuff can be found already in the forums so you posting guides is redundant js
Sent from my LG-H910 using XDA Labs
cnjax said:
All this stuff can be found already in the forums so you posting guides is redundant js
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion... but i thought this would help noobs like me to explore more about our device without doing any harm to it.....
Glad someone actually laid it out step by step.
kish9046 said:
Thanks for the suggestion... but i thought this would help noobs like me to explore more about our device without doing any harm to it.....
Click to expand...
Click to collapse
so i just wanted to say thank for for the very noobie step by step guide. im soooo use to odion and adb flash commands.
just 1 thing i had trouble with was trying to push magisk and twrp over. I rooted by pushing magisk over with otg but no twrp on recovery. then i saw it said it was on download mode. from dl mode i just flashed twrp to recovery.
BROKEN1981 said:
so i just wanted to say thank for for the very noobie step by step guide. im soooo use to odion and adb flash commands.
just 1 thing i had trouble with was trying to push magisk and twrp over. I rooted by pushing magisk over with otg but no twrp on recovery. then i saw it said it was on download mode. from dl mode i just flashed twrp to recovery.
Click to expand...
Click to collapse
So i assume you have both TWRP and root now?..... And can i ask which version r u in now....ARB0 or 1
kish9046 said:
So i assume you have both TWRP and root now?..... And can i ask which version r u in now....ARB0 or 1
Click to expand...
Click to collapse
Abr1 yes I am rooted with twrp.
As I said, the commands to push magisk and twrp to sd did not work. I used usb otg in twrp to push magisk, but forgot to put twrp to flash as well.
I forgot that twrp had replaced download mode, so I was going a bit nuts trying to figure out how to get twrp to recovery. Lolol
Now I'm on latest update with rtcd removed thanks to the op who hosted it on xda as a flashable zip.
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
As you are in twrp, you can manually flash magisk zip and twrp recovery.....
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
Download magisk and twrp here https://androidfilehost.com/?fid=746010030569963731
While you are in the last step, in mount, select otg USB. You can push it to SD card and manual flash.
If you booted to system without magisk and flashing twrp, power off the phone, hold volume up, put in the USB, connect to PC. This will put you in twrp since download mode is replaced by twrp.
Now you can flash both files.
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
Download magisk and twrp here https://androidfilehost.com/?fid=746010030569963731
While you are in the last step, in mount, select otg USB. You can push it to SD card and manual flash.
If you booted to system without magisk and flashing twrp, power off the phone, hold volume up, put in the USB, connect to PC. This will put you in twrp since download mode is replaced by twrp.
Now you can flash both files.
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
I can't speak for the rest of you, but I've been waiting for LineageOS to support this phone since I bought it almost a year ago. I saw a post on /r/LineageOS indicating that mata was finally being supported and sure enough here it is:
https://download.lineageos.org/mata
Since there doesn't appear to be a thread on the topic yet, I figured I'd go ahead and create one so all interested parties can discuss it. I probably won't get around to flashing it myself until this weekend and I'd love to hear how it's working for other people prior to that (and if not, hell I'll flash it and roll the dice).
jaylittle said:
I can't speak for the rest of you, but I've been waiting for LineageOS to support this phone since I bought it almost a year ago. I saw a post on /r/LineageOS indicating that mata was finally being supported and sure enough here it is:
https://download.lineageos.org/mata
Since there doesn't appear to be a thread on the topic yet, I figured I'd go ahead and create one so all interested parties can discuss it. I probably won't get around to flashing it myself until this weekend and I'd love to hear how it's working for other people prior to that (and if not, hell I'll flash it and roll the dice).
Click to expand...
Click to collapse
I did it and so far looks good
jowandrys said:
I did it and so far looks good
Click to expand...
Click to collapse
Can you give us a link to the procedure that you followed in order to flash it?
Thanks !
Djalil87 said:
Can you give us a link to the procedure that you followed in order to flash it?
Thanks !
Click to expand...
Click to collapse
https://wiki.lineageos.org/devices/mata
jowandrys said:
I did it and so far looks good
Click to expand...
Click to collapse
Do you play any games? I'm having issues with touch in games only so far
joha386 said:
https://wiki.lineageos.org/devices/mata
Click to expand...
Click to collapse
I think the installation guide is wrong. To unlock the bootloader, the command "fastboot oem unlock" will not work.
MattCB72 said:
I think the installation guide is wrong. To unlock the bootloader, the command "fastboot oem unlock" will not work.
Click to expand...
Click to collapse
Yes it didn't for me. I used instead:
> fastboot flashing unlock
Not able to install Gapps. Always get Error 70...
dazeone said:
Do you play any games? I'm having issues with touch in games only so far
Click to expand...
Click to collapse
I've specifically noticed touch issues in Pokémon GO. Unable to reproduce the problem reliably, but it seems that after several hours of uptime single-finger touches no longer register (again, only in PoGO -- other apps work flawlessly). Strangely, using 1 finger as an anchor anywhere on the screen, then tapping the intended button with a 2nd finger will register correctly.
Fortunately, I've been able to resolve the intermittent issue with a simple reboot.
Edit: Looks like touch issues in games may have been present back in 15.1.
Steps that I followed to get it up and running
Djalil87 said:
Can you give us a link to the procedure that you followed in order to flash it?
Thanks !
Click to expand...
Click to collapse
Clean install steps, WILL destroy ALL data, make backups!! before performing any of this and as always YMMV
0: (optional) Update firmwares/radios etc. to latest
0.1: Download latest stock package. [URL: https://www.essential.com/developer/current-builds]
0.2: Unzip to a location and modify the install script flashall.sh(*nix)/flashall.bat(win) to remove the reboot line (last line)
0.3: Reboot to bootloader: Keep pressing vol down + power buttons OR adb reboot bootloader via a privileged OS terminal.
0.3: Run the install script with admin privs: sudo ./flashall.sh(*nix) OR (run as admin) flashall.bat(win)
0.4: Reboot bootloader: Keep pressing vol down, select using power button hen you see the option OR fastboot reboot-bootloader
1: Erase userdata: sudo fastboot -w
1.1: (very optional) check slot to make sure we are in slot a (sudo fastboot getvar current-slot), if not then boot to slot a.
2: Install twrp to boot (fastboot flash boot TWRP-SEP.img or latest twrp image) (Note: I use that specific twrp image because the touchscreen works for me YMMV)
3: Boot to twrp using vol up/down buttons and power button to make the selection.
Now we are within TWRP and hopefully touch works, if the touch doesn't work, try to use a different TWRP build or try to use adb shell commands, indicated below (where applicable)
4: Here we wipe and format everything (if no touch then adb shell twrp wipe <system/data>)
4.1: Format data (Any adb shell commands to achieve a similar result?, "adb shell twrp wipe data" maybe)
4.1.1: (optional) format data to f2fs
4.2: Wipe system (adb shell twrp wipe system)
5: We start copying and initial installing ROM files to device, (adb push <file> /sdcard/)
5.1: Copy and install file: Lineageos rom [URL: https://download.lineageos.org/mata]
5.2: Copy and install file: TWRP installer [URL: https://dl.twrp.me/mata/]
6: Reboot to recovery, this should boot back up to twrp (any adb shell command to achieve this?) (Note: This step is needed otherwise gapps installation *may* fail later)
7: Now we copy and install rest of the files to device in order. (adb push <file> /sdcard/) OR (if sideloading: adb sideload <file>)
7.1: Here you get to choose if you don't want google integration (Lucky You!)
7.1.1: (optional) Copy and install file: <nanodroid> if you are interested in going the microg route. [URL: https://nanolx.org/nanolx/nanodroid]
7.1.2: (optional) Copy and install file: <OpenGapps pico> (or whatever you want man). [URL: https://opengapps.org/]
7.2: (optional, needed if disabling forced encryption) Copy and install file: DM verity_forceencrypt zip file (download zip from github and remove .git files and recompress to .zip, making sure the filename is (without quotes): "Disable_Dm-Verity_ForceEncrypt_master" [URL: https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt/archive/master.zip]
7.3: (optional, needed if root is desired or if disabling forced encryption in 7.2) Copy and install file: <Magisk stable> [URL: https://forum.xda-developers.com/apps/magisk]
7.4: (optional, untested, may break OTA) Perform step 5.2 again if you want to maintain TWRP as recovery.
8: Reboot to system.
8.1: (optional) If device is consistently bootlooping (Note: 2-4 interim reboots are normal), then GOTO step 1.
8.2: (optional) If a system app is force closing, try to erase its data and cache first, otherwise GOTO step 1.
profit?? (and/or optionally cry over wasted time in this possibly pointless exercise)
psychic_quark said:
6: Reboot to recovery, this should boot back up to twrp (any adb shell command to achieve this?) (Note: This step is needed otherwise gapps installation *may* fail later)
Click to expand...
Click to collapse
Thanks for this excellent step by step guide. I didn't get touch to work on my TWRP (latest version from TWRP site) so I did use adb shell commands in TWRP but unfortunately I didn't manage to install GApps. I think I'm missing the step 6. you are describing. I have LOS running with root but no GApps.
Any guess on how I can manage to reboot to recovery while I'm in TWRP sideload mode to get back to TWRP again?
Thanks !
Another way to use twrp without touch is by using a mouse. If you have one with a type C connector, plug it in and you can flash LOS and the twrp installer. Then boot back to recovery and flash GAPPS. I had to do it this way but I had an adapter for the type C plug so I could use a regular mouse. The adapter came with my Pixel 2XL.
I kept getting error 70, so I used MindTheGapps, which installed fine. Don't know if there's any adverse effects of doing that though, by my phone seems to be working fine.
Wish there was some way to configure fullscreen on the notch though.
theycallmetony said:
I've specifically noticed touch issues in Pokémon GO. Unable to reproduce the problem reliably, but it seems that after several hours of uptime single-finger touches no longer register (again, only in PoGO -- other apps work flawlessly). Strangely, using 1 finger as an anchor anywhere on the screen, then tapping the intended button with a 2nd finger will register correctly.
Fortunately, I've been able to resolve the intermittent issue with a simple reboot.
Edit: Looks like touch issues in games may have been present back in 15.1.
Click to expand...
Click to collapse
is there a better solution? It no longer registers my touches after several minutes, so I need to reboot my phone to play games every time…Because of the bad optimization of the kernel, before my phone runs smoothly there is some annoying minutes…
And when I try to flash Neutrino Kernel and reboot, all my PH-1 does is stuck in "phone is starting" with a dialog reminding me that there is an internal error with my system, and it never truly enters the launcher… Has anyone tried yet?
Rachel030219 said:
is there a better solution? It no longer registers my touches after several minutes, so I need to reboot my phone to play games every time…
Click to expand...
Click to collapse
Been running the 20190614 nightly for ~13 hours straight without the need to reboot. Pokémon GO is still running smooth!
Edit: Touch problems started again a couple hours after posting this. Fortunately, a reboot still resolves the issue.
Anyone try LineageOS for microg? Keep trying to flash the rom but no dice, just get sent back to twrp.
Hero2457 said:
Anyone try LineageOS for microg? Keep trying to flash the rom but no dice, just get sent back to twrp.
Click to expand...
Click to collapse
Same here, unfortunately. The first time (this was a clean flash after a full wipe), it showed the boot animation for an hour before going back to twrp. I tried flashing it again after another wipe, and this time it stayed in the boot animation overnight, for at least ten hours. I'm not sure where to send a bug report or what info to attach to the bug report.
The regular (non-microG) LOS on the other hand, works fine.
Djalil87 said:
Thanks for this excellent step by step guide. I didn't get touch to work on my TWRP (latest version from TWRP site) so I did use adb shell commands in TWRP but unfortunately I didn't manage to install GApps. I think I'm missing the step 6. you are describing. I have LOS running with root but no GApps.
Any guess on how I can manage to reboot to recovery while I'm in TWRP sideload mode to get back to TWRP again?
Thanks !
Click to expand...
Click to collapse
I was on Q beta 4 and these steps worked for me:
Here's what worked for me:
fastboot flash boot <twrp image from twrp.me>
<boot into recovery>
Touch isn't working, so instead I do: adb shell twrp sideload
adb sideload <lastest lineage rom>
(again) adb shell twrp sideload
adb sideload <twrp installer zip>
adb reboot recovery
Touch worked in twrp!
Proceeded with installing opengapps/nanodroid and all that jazz.
TBH you don't need touch to achieve most (if not all) functionality of twrp.
To reboot back to recover from within twrp (assuming you have already flashed twrp installer after flashing rom), just do: adb reboot recovery
psychic_quark said:
Clean install steps, WILL destroy ALL data, make backups!! before performing any of this and as always YMMV
0: (optional) Update firmwares/radios etc. to latest
0.1: Download latest stock package. [URL: https://www.essential.com/developer/current-builds]
0.2: Unzip to a location and modify the install script flashall.sh(*nix)/flashall.bat(win) to remove the reboot line (last line)
0.3: Reboot to bootloader: Keep pressing vol down + power buttons OR adb reboot bootloader via a privileged OS terminal.
0.3: Run the install script with admin privs: sudo ./flashall.sh(*nix) OR (run as admin) flashall.bat(win)
0.4: Reboot bootloader: Keep pressing vol down, select using power button hen you see the option OR fastboot reboot-bootloader
1: Erase userdata: sudo fastboot -w
1.1: (very optional) check slot to make sure we are in slot a (sudo fastboot getvar current-slot), if not then boot to slot a.
2: Install twrp to boot (fastboot flash boot TWRP-SEP.img or latest twrp image) (Note: I use that specific twrp image because the touchscreen works for me YMMV)
3: Boot to twrp using vol up/down buttons and power button to make the selection.
Now we are within TWRP and hopefully touch works, if the touch doesn't work, try to use a different TWRP build or try to use adb shell commands, indicated below (where applicable)
4: Here we wipe and format everything (if no touch then adb shell twrp wipe <system/data>)
4.1: Format data (Any adb shell commands to achieve a similar result?, "adb shell twrp wipe data" maybe)
4.1.1: (optional) format data to f2fs
4.2: Wipe system (adb shell twrp wipe system)
5: We start copying and initial installing ROM files to device, (adb push <file> /sdcard/)
5.1: Copy and install file: Lineageos rom [URL: https://download.lineageos.org/mata]
5.2: Copy and install file: TWRP installer [URL: https://dl.twrp.me/mata/]
6: Reboot to recovery, this should boot back up to twrp (any adb shell command to achieve this?) (Note: This step is needed otherwise gapps installation *may* fail later)
7: Now we copy and install rest of the files to device in order. (adb push <file> /sdcard/) OR (if sideloading: adb sideload <file>)
7.1: Here you get to choose if you don't want google integration (Lucky You!)
7.1.1: (optional) Copy and install file: <nanodroid> if you are interested in going the microg route. [URL: https://nanolx.org/nanolx/nanodroid]
7.1.2: (optional) Copy and install file: <OpenGapps pico> (or whatever you want man). [URL: https://opengapps.org/]
7.2: (optional, needed if disabling forced encryption) Copy and install file: DM verity_forceencrypt zip file (download zip from github and remove .git files and recompress to .zip, making sure the filename is (without quotes): "Disable_Dm-Verity_ForceEncrypt_master" [URL: https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt/archive/master.zip]
7.3: (optional, needed if root is desired or if disabling forced encryption in 7.2) Copy and install file: <Magisk stable> [URL: https://forum.xda-developers.com/apps/magisk]
7.4: (optional, untested, may break OTA) Perform step 5.2 again if you want to maintain TWRP as recovery.
8: Reboot to system.
8.1: (optional) If device is consistently bootlooping (Note: 2-4 interim reboots are normal), then GOTO step 1.
8.2: (optional) If a system app is force closing, try to erase its data and cache first, otherwise GOTO step 1.
profit?? (and/or optionally cry over wasted time in this possibly pointless exercise)
Click to expand...
Click to collapse
Brillant post @psychic_quark that was the only guide which worked for me, coming from Q beta 3. Thanks.
Step 1.1 was needed for me to flash boot_a or _b in step 2 depending on the result in 1.1.
@jaylittle thanks also for telling us. I also waited for a year to get LOS on my PH-1. I got it from the amazon deal and was ran invisiblisk ROM of Dec.
I ran the June 15 ROM with opengapps pico and magisk in recent version and yestersay I updated via OTA to June 18 ROM without loosing root. Thats very cool. With other ROMs I had to install magisk after update again.
Did anyone tried to install twrp permanently?
And my second question is about removing the red warn during booting which has to be ack-ed. I found this https://mata.readthedocs.io/en/latest/ under topic "Removing the Red Verity Warning" did anyone tried this and will this remove root?
Thanks for your help.
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.
Wanted to install NetHunter on my phone to learn. Here is a story of a foolish student decided to make his life difficult:
Device: OnePlus 6
Model: A6000
Android 10
Here are the steps I followed:
Followed these two documentations:
1) https://www.kali.org/docs/nethunter/installing-nethunter/#1-nethunter-support-and-pre-built-images
2) https://www.kali.org/docs/nethunter/
So downloaded the zip image > put android in developer mode with OEM and advanced reboot and debugging enabled > Fastboot menu
Then I followed this guide for step 3-5 from link 1:
https://forum.xda-developers.com/t/...-flash-twrp-root-nandroid-efs-backup.3792643/
(a little bit google reading said TWRP takes care of A/B style devices by itself no special steps needed)
Set up the windows machine with fastboot, adb and device drivers > run the command "fastboot oem unlock" > transferred twrp zip to the device internal storage > then flashed the new recovery mode "fastboot boot twrp.img" > install and selected the twrp zip that I had saved in internal storage before > reboot > system.
So far worked perfectly.
Then I downloaded the Magisk apk from github and installed it by transferring it to internal storage.
Next for step 6 from link 1:
I again download the ForceEncrypt disabler from zip and transfer it to internal storage then flash it using TWRP.
So far no errors.
Now the final step should have been to flash the nethunter zip image and this is where the problems started:
I tried to flash it using TWRP but it gave me an error about there not being enough storage.
Saw a YT video where he extracts the nethunter zip and via the magisk app does a install on the tar file found inside the extracted folder. This also failed.
After a bit google it said it was because I did not have custom ROM and chroot and lineageOS should solve my problem.
I flash the LineageOS zip image using TWPR > successful but says I should switch the slot to complete the zip files installed.
After switching and rebooting, fastboot goes to lineage always and its a bootloop , so no matter what I select its always reaching the same screen and I cant tranfer zip to internal anymore to try a different build.
So now I run the command fastboot boot twrp.img again and go back to slot A.
Now my phone is stuck in bootloader. No matter what option I select out of the 4:
Start
Recovery mode
restart bootloader
power off
(latter two work as expected technically)
I always end up on the same screen.
After connecting the phone it is showing it as connected in "fastboot devices" now but fastbood is not able to flash or boot any image to it: either freezes or unknown error. "adb devices" shows no devices.
Practically begging for help right now.
To fix your phone, you should use this recovery tool.
https://forum.xda-developers.com/t/op6-latest-10-3-8-collection-of-unbrick-tools.3914109/
You can follow a tutorial like this one
Good luck
You haven't chosen the right place to ask for help. delete your post or change it to "Questions and answer". Have a good day.
d
CarlosTime said:
You haven't chosen the right place to ask for help. delete your post or change it to "Questions and answer". Have a good day.
Click to expand...
Click to collapse
Thank you. I am trying the suggested video right now.
Do you also know why I get the storage error while trying to flash nethunter?
take it easy, relax i have a long story with oneplus too
send me msg on telegram so i can help u 98%
uaername : NotReal0
stay safe bro, and dont worry i dont need you money just bc im noob with english so i just know that u damaged ur phone and i know how to fix
saffron_jedi said:
Wanted to install NetHunter on my phone to learn. Here is a story of a foolish student decided to make his life difficult:
Device: OnePlus 6
Model: A6000
Android 10
Here are the steps I followed:
Followed these two documentations:
1) https://www.kali.org/docs/nethunter/installing-nethunter/#1-nethunter-support-and-pre-built-images
2) https://www.kali.org/docs/nethunter/
So downloaded the zip image > put android in developer mode with OEM and advanced reboot and debugging enabled > Fastboot menu
Then I followed this guide for step 3-5 from link 1:
https://forum.xda-developers.com/t/...-flash-twrp-root-nandroid-efs-backup.3792643/
(a little bit google reading said TWRP takes care of A/B style devices by itself no special steps needed)
Set up the windows machine with fastboot, adb and device drivers > run the command "fastboot oem unlock" > transferred twrp zip to the device internal storage > then flashed the new recovery mode "fastboot boot twrp.img" > install and selected the twrp zip that I had saved in internal storage before > reboot > system.
So far worked perfectly.
Then I downloaded the Magisk apk from github and installed it by transferring it to internal storage.
Next for step 6 from link 1:
I again download the ForceEncrypt disabler from zip and transfer it to internal storage then flash it using TWRP.
So far no errors.
Now the final step should have been to flash the nethunter zip image and this is where the problems started:
I tried to flash it using TWRP but it gave me an error about there not being enough storage.
Saw a YT video where he extracts the nethunter zip and via the magisk app does a install on the tar file found inside the extracted folder. This also failed.
After a bit google it said it was because I did not have custom ROM and chroot and lineageOS should solve my problem.
I flash the LineageOS zip image using TWPR > successful but says I should switch the slot to complete the zip files installed.
After switching and rebooting, fastboot goes to lineage always and its a bootloop , so no matter what I select its always reaching the same screen and I cant tranfer zip to internal anymore to try a different build.
So now I run the command fastboot boot twrp.img again and go back to slot A.
Now my phone is stuck in bootloader. No matter what option I select out of the 4:
Start
Recovery mode
restart bootloader
power off
(latter two work as expected technically)
I always end up on the same screen.
After connecting the phone it is showing it as connected in "fastboot devices" now but fastbood is not able to flash or boot any image to it: either freezes or unknown error. "adb devices" shows no devices.
Practically begging for help right now.
Click to expand...
Click to collapse
I had the same issue after trying to install nethunter myself. Unfortunately for me the MSMDownload tool wouldn't work because I couldn't get the phone to stay off, it would just boot back up into bootloader/fastboot mode as soon as I connected to the computer via usb cable.
Here's the solution that will work 100%. Go to this website below and download the stock OOS zip file for your phone, in my case it was the Oneplus 6T fastboot ROM. Unpack the files into your platform-tools folder, click skip all if it asks you if you want to replace any files in that folder, then run the flash-all.bat and it will unbrick your device. Keep in mind that it will unroot your device and remove twrp as well. There's a thread here that explains how to do it manually so that doesn't happen but its a bit of work to get it done that way.
FastbootRoms Activity
sourceforge.net