So today i decided to update magisk to its latest versio, it all whet well,i did within android. later on in the day i decided to reboot myphone, and to my surprise it got stuck o thelgv30 thinq scree, after decide 10m was enough i rebooted and the it was stuck in bootloop, so i decided to restore my nanddroid , after it was done i hit reboot to system, and now it will only noot to fastootmode,, its as if there is nothing flashed to boot or system. any help will greatly appreciated.
EDIT: VERY OLD POST; WE CAN NOW USE NEWER MAGISK
____________
By "latest" you mean Magisk beta? You can only use stable 16.0 Magisk. Stated in the bootloader unlock/TWRP/root instructions that beta Magisk will mess up your phone.
Download Magisk or SuperSu. Magisk 16 (Use stable Magisk -- which right now is 16.0! Magisk "beta" will mess up your phone.)
Click to expand...
Click to collapse
You may need to Master Reset (wipe everything), reflash TWRP, etc. Good luck.
ChazzMatt said:
By "latest" you mean beta Magisk. You can only use stable 16.0 Magisk. Stated in the bootloader unlock instructions that beta Magisk will mess up your phone.
You may need to Master Reset (wipe everything), reflash TWRP, etc. Good luck.
Click to expand...
Click to collapse
yea that what i did fml. what do i do reflash the oreo kdz?
siulmagic said:
yea that what i did fml. what do i do reflash the oreo kdz?
Click to expand...
Click to collapse
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
ChazzMatt said:
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
Click to expand...
Click to collapse
Isint the master reset disabled with twrp? master reset only boots twrp, when you have twrp installed, i will try to wipe with lgup.
Thanks for the help man, phone is backup and running.
siulmagic said:
Thanks for the help man, phone is backup and running.
Click to expand...
Click to collapse
I've tried using LgUP to try and get me back onto an OS, but it will not boot into the OS, only into fastboot. Anything I can do?
If you were using Trebel TWRP you have to use normal TWRP and restore the backup GPT in order for a stock nandroid to work or a stock based clean flash...
jmej88 said:
I've tried using LgUP to try and get me back onto an OS, but it will not boot into the OS, only into fastboot. Anything I can do?
Click to expand...
Click to collapse
To fix stuck in fastboot or download mode
Connect phone in download mode
go in patched LGUP flash h93320f_00_open_ca_op_0612.kdz
With partition dl option
(not working go in device manager select modem
Then lge mobile usb modem right click disable driver try again)
help me:,(
ChazzMatt said:
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
Click to expand...
Click to collapse
I had the same problem but I tried many different versions but it was still stuck in fastboot i'm so scared help me pls
Im stuck in fastboot mode too after chip reset. Tried kdz us998 10 with no luck.
Anybody have other suggestions?
....edit.
Fixed flashing Canadian kdz.
mines wont go into download mode just keeps going to fastbootloader
r3m3dy478 said:
mines wont go into download mode just keeps going to fastbootloader
Click to expand...
Click to collapse
Flash twrp and flash rom.
Sent from my VS996 using Tapatalk
r3m3dy478 said:
mines wont go into download mode just keeps going to fastbootloader
Click to expand...
Click to collapse
Download kdz flashable zip then extract it. Flash the system.img and boot.img file via fastboot
This just happened to me today. It was either from the newest Magisk (v22) or from the newest YouTube Vanced. Those were the only things that changed recently on my phone. Rebooted today and it will only go to Fastboot mode and that's it.
Master Reset will get me into TWRP, but I think my USB port on the phone is damaged, it will charge but neither my Windows nor Linux PCs will recognize that it's plugged in. So it's like only USB charging works but not USB data. So I think I'm screwed, idk if it's fixable. Sad day.
Am also stack here qhile trying to unlock my bootloader using @bilong9 thread on my v300l .please help
This also happened to me while trying to update to Magisk 22. First I had an error with Magisk in a restart cycle, then when I tried to update manually from the APK I got stuck in a fastboot loop with no ADB access. I was able to boot to TWRP from fastboot on my PC, then re-flash the Pie image. My settings were all lost, but I did get my phone back at least. BEWARE of Magisk 22, or at least until it's fixed for the V30!
edit: I found that I COULD install Magisk 22.0.zip while following these instructions for restoring my phone:
LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions)
(WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions) WTF...! LG V30,V30+,V30S (MOST VARIANTS) BOOTLOADER UNLOCK, TWRP, ROOT INSTRUCTIONS HERE >>>CLICK HERE TO POST #193
forum.xda-developers.com
after a few extra prompts from the Magisk app, v22 now works.
I've had no issues using Magisk v22 with an LOS 17.1 (Android 10) based ROM. It could just be that there's a problem with it on either LG stock or Pie ROMs.
UPDATE
* Variant: US998 US Cellular/Carrier Unlocked
* ROM: Rooted Stock Pie (US99830b)
* Magisk: v21.4
So it seems the issue is not that it "soft bricks", but something about the new installation process of Magisk v22 goes wrong with the /boot partition, causing the phone to only be able to boot into Fastboot mode.
After getting my phone fully recovered and restored from the last failed attempt (and making a new TWRP backup), I attempted the v22 update again. First Magisk attempted to download and install the new v22 app, and then a popup notification said "additional setup is required for your device, press OK to reboot". So I hit okay, and that's when once again I got stuck in Fastboot with no other options.
If you have a TWRP/nandroid backup, you can easily fix this by performing the Master Reset process in order to boot into TWRP, and then just Restoring the /boot partition from your TWRP backup. This will get you back to Magisk v21.4 where you were before, which is where I'm currently at.
At this time, unless Magisk releases a TWRP-flashable .zip for v22, or unless there's a way to update to v22 via Fastboot, it doesn't look like updating to v22 will be possible, at least for the Stock Pie ROM.
I've seen on both reddit and XDA that several people are saying they updated to v22 without issue, but it's unclear if they were on Stock or Custom ROM. My guess would be that Custom ROMs are probably working fine and it's the Stock ROM that's having the issue.
At this time, unless Magisk releases a TWRP-flashable .zip for v22, or unless there's a way to update to v22 via Fastboot, it doesn't look like updating to v22 will be possible, at least for the Stock Pie ROM.
Click to expand...
Click to collapse
I simply renamed the available .apk to .zip and it flashed in TWRP.
edit: the ROM I'm using is from this thread, which says it is 99% stock, whatever that means.
Related
Updated for more serious reference. Hope this info helps you!
Procedure:
Once you have updated to Nougat, you would have to unlock your bootloader
The APK that unlock the bootloader works (Even though is marked as M version). (Remember that this will wipe your device!) For ULBL -> Version UnlockTool_2017_0803(android M) (FROM ASUS) https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_Download/
Zenfone will reboot and you will able to see a new splash screen that informs you that your device is unlocked giving you boot options Don't press anything. (You will see this everytime you reboot). The next screen will show an erase process. Phone will reboot.
Once booted enable developer options and adb via usb.
You can find TWRP builds right here: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w (Special thanks to: @shakalaca) Use the latest one.
Go to fastboot mode and install TWRP. (fastboot flash recovery (nameoffile).img)
Let fastboot do it's magic, once you finish press volume buttons till you find reboot recovery press power button to select. It will boot again to the first splash. Do not press anything, let it work. It will boot TWRP in a whistle.
Once in TWRP make a backup. You know it's necessary, and will save your ass in case of a softbrick.
Flash latest magisk (Current Ver: 13.3) Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot, check drawer for magisk manager, magisk and root should be enabled.
Voila. Safetynet test passed :good:
what version was twrp are you using and what steps did you take to get magisk to work.
smariob said:
So today finally I got my Asus Zenfone 3 Zoom. I couldn't contain myself to start playing with it.
My very first surprise was that the phone requested for an update. I've done it. I ended with a stock 7.1.1 AZ3Z.
This is my experience:
The APK that let you unlock bootloader works. (Remember that this will wipe your device)
After auto reboot I cheched safetynet. At this point test failed (Little bit obvious)
I was able to go to fastboot mode and install TWRP (The same you can find right here at the forum)
Let fastboot do it's magic, press volume buttons till you find reboot recovery. It will boot TWRP in a whistle.
Once in TWRP I made a backup. You know if necessary.
The next step was a crossfinger procedure. Just flashed latest magisk Beta (13)
Reboted checked for magisk manager on drawer.
It was there and root also. Enabled magiskhide, and voila. Safetynet test passed :good:
Hope this Info help you.
Click to expand...
Click to collapse
Do you know if this works with Android Pay?
magicmanfk said:
Do you know if this works with Android Pay?
Click to expand...
Click to collapse
It should work with it, im able to login intoy bank account with no problem with this method, I will give it a try for you though.
mr573162 said:
what version was twrp are you using and what steps did you take to get magisk to work.
Click to expand...
Click to collapse
magicmanfk said:
Do you know if this works with Android Pay?
Click to expand...
Click to collapse
It's twrp 3.1.0
It should work as it passes CTS profile and Basic Integrity I can't test it myself because I live in Mexico and Android Pay is not avialable here yet.
Will edit OP
Just a question as I'm having difficulty booting into TWRP.
My device is unlocked and when flashing TWRP using the command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens other than my device going into the bootloader. I have tried flashing both the most recent TWRP 3.1.1 and 3.1.0 yet I keep on coming to the same problem. Can anyone provide help? thanks in advance.
GarGarStinks said:
Just a question as I'm having difficulty booting into TWRP.
My device is unlocked and when flashing TWRP using the command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens other than my device going into the bootloader. I have tried flashing both the most recent TWRP 3.1.1 and 3.1.0 yet I keep on coming to the same problem. Can anyone provide help? thanks in advance.
Click to expand...
Click to collapse
Everytime you reboot the pone starts into boot loader. It has a countdown to boot into whatever is commanded.
Once you flashed succesfully the recovery img you just have to select option to boot recovery with vol keys and power.
Phone will reboot into bootloader agin let it boot on contdown (don't press any key)
Then it will boot into twrp.
Hello, on nougat i am trying to install the twrp, I downloaded the official bootloader release program (after installing the message "unlocked device") but trying to install the twrp via fastboot me by an error message. ... but I think the problem is the unlocking of the bootloader (if I turn the ze553kl in fastboot mode I see my device is "locked") ... there is another version of the bootloader release software? The one available on asus site would look for android M ... maybe there is one for Nougat? Thanxs
Wop. I used the M version apk on Nougat. It worked with no issues, the unlock of boot loader is successful when all the content of your smartphone is wiped.
For reference: https://www.youtube.com/watch?v=hg77b8o8Jk4 Min 1:29
Thank you! But running the software, does not run any wipe, it only displays an "unlocked" message without having to restart anything else. I also tried to make a "factory reset" and repeat lab process but the result does not change ...
TWRP tip!!
smariob said:
Go to fastboot mode and install TWRP. You can find TWRP and how to install it right here: https://forum.xda-developers.com/zenfone-3-zoom/how-to/twrp-zenfone-3-zoom-t3624551
:
Click to expand...
Click to collapse
If you follow that link and flash the recommended version, TWRP might load upside down and mirrored, impossible to use. I flashed the latest version from the MEGA link (3.1.1) and it was back to normal. Just a head's up for future reference, you might want to update your post.
---------- Post added at 09:39 PM ---------- Previous post was at 09:32 PM ----------
smariob said:
Go to fastboot mode and install TWRP. You can find TWRP and how to install it right here: https://forum.xda-developers.com/zenfone-3-zoom/how-to/twrp-zenfone-3-zoom-t3624551
:
Click to expand...
Click to collapse
If you follow that link and flash the recommended version, TWRP might load upside down and mirrored, impossible to use. I flashed the latest version from the MEGA link (3.1.1) and it was back to normal. Just a head's up for future reference, you might want to update your post.
Updated, never had mirror issues but is always better to have latest recovery.
Edit. Jimbo, I got an anwer from the source it notes: "please use 'fastboot flash recovery' instead of 'fastboot boot' to avoid up side down screen"
I've also tried installing from scratch with Asus flash tool, but I still can not unlock bootloader ... Anyone know if there is also an unofficial method for unlocking the bootloader?
@bizzino what model of Z3Z are you using?
Maybe Unlock bootloader app is intended for specific models... Let me do a little bit of research
Double posted... (Don't know for what reason this is happenning)
smariob said:
@bizzino what model of Z3Z are you using?
Maybe Unlock bootloader app is intended for specific models... Let me do a little bit of research
Click to expand...
Click to collapse
Ze553kl. WW_Z01H
bizzino said:
Ze553kl. WW_Z01H
Click to expand...
Click to collapse
Couldn't find another unlock tool than 2017_0803 ...
What info gives you fastboot mode?
smariob said:
Couldn't find another unlock tool than 2017_0803 ...
What info gives you fastboot mode?
Click to expand...
Click to collapse
Locked
Works just fine, thank you
But how would I go about setting the phone back to stock if needed in the future? (Removing Magisk, and replacing TWRP with the original recovery software).
@bizzino No news for you i wasn't able to find more info I'm sorry. Maybe change it for warranty? @subsector you should flash original recovery via fastboot and then sideload the stock rom
Back to Stock with @raystef66's Files
This guide used a method stemmed from paranoia. Now that we have decent flashable files everything is much simpler!
We'll be using raystef66's flashable TWRP files to go completely back to stock. At the end there's instructions if you want to lock your bootloader.
Be sure that you are on the latest TWRP version!
1) Files to Download:
- TWRP Flashable Bootstack/Stocksystem Image from here: Download Center. Download the latest BOOTSTACK and STOCKSYSTEM from there.
- If you want to lock the bootloader, also download the STOCK RECOVERY zip from the same stocksystem version that you downloaded. The flashable stock recovery zips are on the Factory Images Division, right above the TWRP flashable files.
- Magisk 15.2 (or latest), or SuperSU 2.79 (Latest not recommended ). If you will relock the bootloader, skip this part.
2) Installation
- Put all the files on the internal storage or SD card. Backup your important stuff from the internal storage, because you might need to format it!
- Go to TWRP. Wipe data, system and cache (don't format data though).
- Install the bootstack that you downloaded. Then install the stock system.
- If you will NOT relock the bootloader, install Magisk or SuperSU
- Reboot
If the phone asks for a password when it gets to the system, go to TWRP. It will ask for a password, just select Cancel. After you're on the main TWRP screen, select Wipe, then Format data, then type yes. After that, reboot.
3) 5 second screen removal / restore Fastboot
This is useful whether you're relocking the bootloader or not. Just go to raystef66's guide and follow it completely. After doing it your phone will have Fastboot (very good for softbricks and relocking), no 5 seconds screen (your phone will boot up faster) and it will be even closer to full stock.
4) ONLY FOR RELOCKING - Replace TWRP with Stock Recovery
Simply go to TWRP and flash the stock recovery file you downloaded. After that, enable OEM unlocking and USB debugging from the dev options, and then go to Fastboot and issue "fastboot oem lock".
@Choose an username... thanks for the credits.
you can return to stock in that way. you can reflash twrp with tool, allways checking bootloader still unlocked.
I allway update in this way, reboot to twrp, flash the recovery image, not a zip, its the same, but I make sure that the recovery correspond to the base version in my phone. after that, I reboot to system directly, update in the ota way, or the zip way, but from running android, rooted or not, and I dont have to wipe.
After update is done, the most important thing is leave the phone till it is completly booted, then you can reflash twrp with axon7tool again.
You dont need to root, you dont need anything to keep twrp. You only need to flash supersu or magisk if you use darkenfx zips. And if you do it, you have to backup wipe and restore cause you lose encryptation.
But thats all. I think stock rom its still the best, not in battery life, but in camera and bundled apps, It works perfectly, except, I have 2 bugs since allways, wake up with proximity sensor covered, and whatsapp online with app in background, I can live with that
I can re-lock bootloader after this process?
thanks for the guide.
Help Needed ! A2017g Bricked while trying to returning to stock
Hi, Please help me to get my Axon 7 in a working state. I was using Xenon HD Rom for A2017g Oreo. With twrp version as suggested in the guide.
I followed the procedure, installed the bootstack and then stock system B09
But when I tried to reboot, it said no OS Installed. Then I rebooted, and it was stuck at bootloader with no twrp and just the message as follows :
Android Recovery : ZTE/P996A04_N/ailsa_ii
7.1.1/NMF26V/20171120.101942
user/release-keys
Use volume up/down and power
and then certain other options in blue
Please help !
I also have a Problem.
I tried going back to stock from LOS 14.1. Now I am stuck on the 5 seconds screen, it won't continue.
The files I used were the Nougat B10 Files :-/
HansWursT619 said:
I also have a Problem.
I tried going back to stock from LOS 14.1. Now I am stuck on the 5 seconds screen, it won't continue.
The files I used were the Nougat B10 Files :-/
Click to expand...
Click to collapse
Enter the recovery, it should be the stock one (turn the phone off, then hold vol+ and power). Then download a stock B10 file (not the twrp flashable one) and install it from an SD card
No its not the stock one, its still TWRP.
I only flashed Bootstack and stock system (step 2). The reboot afterwards doesnt work
What do you mean by "a stock B10 file"? There are so many files types :-/
I am not quite sure what I should do now, do I have to do the EDL route? That one sounds confusing as well.
EDIT: I tried using B08 Files and now the reboot prompt in TWRP tells me there is no os installed.
Will I, like naveen09y, end up without TWRP if I reboot now?
HansWursT619 said:
No its not the stock one, its still TWRP.
I only flashed Bootstack and stock system (step 2). The reboot afterwards doesnt work
What do you mean by "a stock B10 file"? There are so many files types :-/
I am not quite sure what I should do now, do I have to do the EDL route? That one sounds confusing as well.
EDIT: I tried using B08 Files and now the reboot prompt in TWRP tells me there is no os installed.
Will I, like naveen09y, end up without TWRP if I reboot now?
Click to expand...
Click to collapse
Probably, so just don't. You should just wipe system and data, flash the bootstack, then the system. Also follow raystef's guide to "remove bootloader unlocked inscription"
I now managed to get the phone working with EDL flash of MM B10.
But I cant relock the bootloader :-/
Bascially my bootloader is gone so I cant reboot to it and do "fastboot oem lock".
Why is this such a hassle
HansWursT619 said:
I now managed to get the phone working with EDL flash of MM B10.
But I cant relock the bootloader :-/
Bascially my bootloader is gone so I cant reboot to it and do "fastboot oem lock".
Why is this such a hassle
Click to expand...
Click to collapse
You didn't follow my instructions. Follow raystef's removed unlocked bootloader inscription and you'll get fastboot back. You can do that with the phone on.
Don't relock it unless it's really necessary (i.e. warranty). If you're gonna sell it just follow that guide and don't relock, the 5 seconds screen will disappear and it'll look like it's locked
I cant follow the guide because I can't access the bootloader...
Also the TWRP files in https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 this guide (step 6) are no longer accessible.
HansWursT619 said:
I cant follow the guide because I can't access the bootloader...
Also the TWRP files in https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 this guide (step 6) are no longer accessible.
Click to expand...
Click to collapse
What? Lol
First of all - you are basically installing the bootloader with raystef's guide, so I have no idea why you want to enter it...
You have to enter TWRP and follow the guide from there.
The guide from Controllerboy is basically the same guide but it also has instructions on other things (i.e. unlock etc.). I don't know what you are trying to accomplish with it. Use EDL Tool by djkuz if you want to install TWRP (it is explained there how to do that).
Phone was rooted with Magisk 16, I was on AEX Android 8.1 ROM. I'm trying to return to stock and relock bootloader.
I wiped everything, I flashed A2017G-N-B10-bootstack and A2017G-N-B10-stocksystem from "TWRP flashable Bootstack/Stocksystem Images" section. Booted to system and now phone is stuck on the ZTE POWERED BY android boot screen. 5 minutes there. Is it normal?
Edit: Got tired of waiting and kept pressing the power button. After doing so, the phone reboots but same thing. And I can't access TWRP with VOL INCREASE + POWER BUTTON.... VOL DECREASE + POWER BUTTON takes me to Factory Test Mode.
aLexzkter said:
Phone was rooted with Magisk 16, I was on AEX Android 8.1 ROM. I'm trying to return to stock and relock bootloader.
I wiped everything, I flashed A2017G-N-B10-bootstack and A2017G-N-B10-stocksystem from "TWRP flashable Bootstack/Stocksystem Images" section. Booted to system and now phone is stuck on the ZTE POWERED BY android boot screen. 5 minutes there. Is it normal?
Edit: Got tired of waiting and kept pressing the power button. After doing so, the phone reboots but same thing. And I can't access TWRP with VOL INCREASE + POWER BUTTON.... VOL DECREASE + POWER BUTTON takes me to Factory Test Mode.
Click to expand...
Click to collapse
Try this.
Oki said:
Try this.
Click to expand...
Click to collapse
Yes, thanks. I already had seen it some minutes ago. It's so convenient that you posted this guide today lol
I want to flash stock rom from RR Nougat. I have installed latest twrp, flash bootstack and then stock system. After that I flash supersu 2.79. But when I press reboot system it say no OS installed
Willchi said:
I want to flash stock rom from RR Nougat. I have installed latest twrp, flash bootstack and then stock system. After that I flash supersu 2.79. But when I press reboot system it say no OS installed
Click to expand...
Click to collapse
The best way to return to stock is via EDL, for example MiFlash or EDL tool. If you have an U, then DrakenFX's zips can do that, it happened to me already. Usually G zips like raystef's work just fine.
Try using Magisk instead of SuperSU, just in case. Use 16.7
@Choose an username...
Thanks for posting this.
Credits to all concerned a big thumbs up.
I do however feel that there are to many versions of the Axon 7 packages and I can see why people are ending up with boot issues etc.
Syberclone said:
@Choose an username...
Thanks for posting this.
Credits to all concerned a big thumbs up.
I do however feel that there are to many versions of the Axon 7 packages and I can see why people are ending up with boot issues etc.
Click to expand...
Click to collapse
what
you do realize this guide is older than a year right?
Yeah, its all good
Last updated May 2020
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
This will work with ANY Xiaomi phone, and should work with ANY ANDROID phone as well. The difference between phones would be in where you can get your boot image from.
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
https://youtu.be/KsxHial1v1U
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
https://youtu.be/USHcCMYlexM
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
fastboot reboot
Click to expand...
Click to collapse
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Update May 2020
Hello again,
Sorry for being away for so long. Here are some of the things I have noticed people are confused with and need to make them clear:
This method works for ANY Android phone. As long as you have the Correct boot.img and can unlock the bootloader
MAKE SURE 100% you have the correct boot.img file for your CURRENT ROM
MAKE 100% SURE, the boot.img file you get from the FULL ROM zip file, not an OTA update zip file
Make sure you check the date and time of the "magisk_patched.img" file to make sure that is the one you made
Make sure you use the LATEST magisk manager
Make sure you open magisk after flashing the magisk_patched.img as boot image. Magisk manager will tell you if there is another step needed, just click yes and it will be done in seconds
Make sure to enable "Hide Magisk" to allow you to have your BANK apps working as well as security checks
If any app you use gives you an error "YOU ARE Rooted bla bla bla" Use magisk manager to hide the root for this specific app (in the settings)
That's all I can remember, good luck
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Kiwironic said:
Keeping it short. This is a simple way to root your device. You will need a computer and a data cable for this.
Steps:
Download the ROM full zip file. This could be the ROM ALREADY installed on your phone or you are updating your phone to it. Here is a video of one way to get your ROM file.
Open the file and extract "boot.img" on your phone or Computer.
Move the boot.img file to your phone
Download and install the latest Magisk official manager app from here: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
Open Magisk manager and click install then "select and patch a file" like in this video
Copy the Patched image from the download folder to your computer adb/fastboot folder
Reboot your phone into fastboot (press and hold power and vol down) and connect it to the computer
Flash that patches image file using fastboot
Open Magisk manager and complete the installation if needed. The app will prompt you for action.
Enjoy
Click to expand...
Click to collapse
After fastboot flash, reboot, open magisk manager, tap INSTALL beside "magisk is up to date". Then select direct install; reboot.
Works on MIUI 11.0.2; davinciin. ??
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
People report different amounts of wait time, depends on the mi account I think
welder73 said:
I know that when I unlock the bootloader,the phone is going to reset...but,is it going to happen immediately or after that 168 hours of waiting?
Sent from my Xiaomi Mi 9T using XDA Labs
Click to expand...
Click to collapse
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Can do with locked bootloader?
Micdu70 said:
Phone is reset when the bootloader is unlocked, not before/during the waiting time.
Click to expand...
Click to collapse
Thank you man :good:
Sent from my Xiaomi Mi 9T using XDA Labs
Cabeção-Flu said:
Can do with locked bootloader?
Click to expand...
Click to collapse
No, bootloader has to be unlocked.
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Lazer Bear said:
@Kiwironic followed your guide and worked very well, although I had to wipe data through the stock recovery to get the phone to boot, I believe that's just how newer Xiaomi phones work. I do have one question though, now that I'm rooted with stock recovery, would I be able to install OTA updates? I'm assuming I would of course lose root and have to redo the process from scratch if that's the case.
Click to expand...
Click to collapse
I had root on MIUI10 and updated the ROM to MIUI11 then did my root again the way mentioned and did NOT have to wipe. You can get OTA anyway, it will try the update first, it will fail, then it download and install a full ROM zip automatically. You have to wait for it to do that twice, that's all. The first boot after the update takes some time.
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
kryzeK said:
@Kiwironic First, thank you so your simple guide!
Can this cause bootloop on my device? If yes, can I simply flash the original boot.img to boot without any data loss?
Also another question: my device is rootless and bootloader unlocked, so my Google Pay doesn't work. When installing Magisk it goes back to work immediately or I have to do something to work?
Click to expand...
Click to collapse
If you flash the full rom, chances of bootloop is minimal. And should have stock experience except for being unlocked.
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
stone_henge said:
I got bootloop, using indian global V11.0.2.0.
After flashing patched boot, it gets bootloop recovery, only way is to wipe all data and reboot
After booting up and opeing magisk it shows a recommendation to install some ZIP
Accepting the recommendation results in bootloop,
Rejecting the recommendation and trying to Install > Direct Install results in bootloop as well
Posted a thread with this issue here
Click to expand...
Click to collapse
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
oblyvision said:
This
I got the exact same issue, every time it asked me to install additional zip files it went into recovery immediately after booting up.
Anyone know why this happened?
Click to expand...
Click to collapse
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Kiwironic said:
Do you have stock recovery or TWRP? Which version of Magisk are you using?
I have patched my boot stock image, installed full ROM, then flashed the patched boot image. Magisk did not show any recommendation installation.
There are a few guides online on how to deal with Magisk Bootloop without the need to wipe data.
Click to expand...
Click to collapse
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
On first installation MM asks to download what it needs e.g. to verify SafetyNet. Allow and there is no problem about. TWRP is generally not needed to install Magisk. Things are documented in Magisk guides
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk/HomePage
oblyvision said:
TWRP 3.3.1-8, magisk 20.1
Patching boot image with magisk wasn't a problem. The Superuser itself works normally, module doesn't. The magisk manager suggested to download additional files for the magisk to be working properly.
I'm on MIUI 11.0.1 Global
Was TWRP the cause in the fist place?
Click to expand...
Click to collapse
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Kiwironic said:
Yes, as the title suggests "without TWRP". The reason is, you cannot install OTA and magisk easily without using the stock recovery. Any attempt to update OTA or use any recovery script on the phone will result in a boot loop.
The solution to get out of the boot loop is simple. Actually a couple of solutions.
One, flash your stock recovery, or
Two, flash a full ROM that includes the stock recovery.
No need to wipe data
That's the only reason I made this post and the other about OTA on root. I don't like to use TWRP because I want OTA install without boot loop. At the same time I want root. Hence the solutions I provided
Click to expand...
Click to collapse
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
oblyvision said:
I've tried flashing magisk via recovery and didn't work, the same bootloop. Here's the thread: https://forum.xda-developers.com/mi-9t/how-to/guide-miui-11-v11-0-1-0-pfjmixm-rooted-t3997299
I thought this might be a working alternative.
Gotta try installing magisk with stock recovery then, and if it still didn't work, well, more research for me..
Click to expand...
Click to collapse
You have to understand the requirements :
- stock recovery
- install magisk manager app
- patch the boot image for your stock ROM (same version on your phone)
- flash that Patched boot image.
- reboot
- done, that's magisk installed
Hi guys, dealing with a H933 --> US998.
TL;DR - stuck on LG logo, no download mode, no fastboot, master reset does not work, LGUP (patched or unpatched) doesn't recognize phone, computer doesn't recognize it either.
----
Frankenstein method followed correctly, and had unlocked bootloader + root.
Followed H933 specific steps to install AOSP/Linage ROMS. Attempted to install Lineage 16.0 and flashed Lunar kernel. Booted to animation logo and didn't get past that.
Decided to revert back to stock Pie by flashing one of the US998 kdz's. To be honest with you, I tried a few different ones and everything was working fine (I went from Nougat --> Oreo --> Pie in order to bring myself back to Pie firmware to try Lineage install once more but with stock kernel).
This time, phone wouldn't move past the LG animation (right after the logo).
At this point, I lost access to download mode - but I still had fastboot. Installed TWRP again through fastboot and attempted to flash TWRP-JOAN_H933_CANADA_20i.
Lost unlocked bootloader image - lost access to fastboot and recovery - and still didn't have download mode (it would not pass the original download mode image) and would not be recognized by LGUP (patched or unpatched). The phone would be stuck at LG logo, and keep rebooting.
At that point I decided to try a Master Reset. On the second YES, it would hang, and then go back to the LG logo bootloop. Phone does not get recognized by computer.
I know I messed up in numerous points. I got overzealous and likely didn't pay enough attention. Spent all night trying to resurrect it, but to no avail. Any advice for me? Or is the device fully bricked? :crying:
Greatly appreciate any feedback and assistance. Thank you in advance.
Sorry to hear that. I think you have four options.
1) Reach out on the telegram v30 forum to someone with an Octoplus box to remotely resurrect your device.
2) Send it in for "repair".
3) Do it yourself, see https://forum.xda-developers.com/g4/general/guide-unbrick-via-external-sdcard-qfil-t3748946.
4) Buy a new phone.
The third option isn't hard, but may involve a lot of work so I'd go with the first one.
don"t worry too much, that phone is almost unbrickable, at least you are really unlucky, you will revive it. Wait for @ChazzMatt to give you some help before giving up hope entirely
Meanwhile, I can give you some advice because I was stuck one time on LG Logo, you were on which firmware when it last booted up?
While it is bootlooping, connect it to the pc, do a soft reset with power and volume down buttons, release them when the screen goes black and immediately press the volume up button to access fastboot menu, and if PC doesnt recognize it, shut down the phone by selecting it with volume button.
Deconnecting the phone and press volume down while reconnecting it to the pc to try to go to download mode and kdz your phone.
Somewhat working
Hey guys - brief update. I got back to US998 Oreo with bootloader unlocked and root. I tried to upgrade to US998 Pie by flashing US99830b.zip in TWRP following all the steps, and now the phone doesn't boot again and gets stuck on the LG Logo. Download mode shows "Now waiting For Any Connection" and doesn't detect PC. Any idea how to get this to work so I can flash back to US998 Oreo and just stick there?
Update: Flashed US99820H and back in running order. I still wonder how to get my phone onto Pie while keeping bootloader unlocked and have root, without having the phone get stuck.
Ergo-sum said:
Update: Flashed US99820H and back in running order.
Click to expand...
Click to collapse
Glad you got your phone working again!
Ergo-sum said:
I still wonder how to get my phone onto Pie while keeping bootloader unlocked and have root, without having the phone get stuck.
Click to expand...
Click to collapse
Thoroughly discussed in the US998 Pie KDZ thread. Top of post #2 (one method), all of post #6 (three different workarounds).
If none of the 4 methods work for you, there are no other answers and you have to wait for another US998 Pie KDZ.
I've struggle for a couple days and finally i can flash pie stock rom to my us998. What i did :
1.Refurbish us99820h lgup, boot os
2.flash and boot twrp via fastboot
3.flash magisk,dm verity, rctd, via twrp...format data reboot format data then magisk again
4. Boot OS
5. Boot recovery then shutdown
6. Partition DL h93310h lgup except RECOVERY AND RECOVERYBAK
7. Boot OS .... Once your lg logo appeared ( BEFORE LG ANIMATION ) press and hold vol down + power. Release power and hold it again IMMEDIATELY once you see LG LOGO ( BEFORE LG ANIMATION ) click the "yes" and "yes"
8. You got the twrp
9. Flash us99820e + magisk via twrp , boot up
10. Refurbish us99820h, boot up
11. Do step 2 and 3
12. Boot OS
13. Boot recovery
14. Flash us99830b via twrp then flash magisk
15. Done u should have pie now
What you are describing is Method #3 in post #6 of the US998 KDZ Pie thread.
It's the workaround which has the most success but is also most complicated.
havetolearn said:
I've struggle for a couple days and finally i can flash pie stock rom to my us998. What i did :
1.Refurbish us99820h lgup, boot os
2.flash and boot twrp via fastboot
3.flash magisk,dm verity, rctd, via twrp...format data reboot format data then magisk again
4. Boot OS
5. Boot recovery then shutdown
6. Partition DL h93310h lgup except RECOVERY AND RECOVERYBAK
7. Boot OS .... Once your lg logo appeared ( BEFORE LG ANIMATION ) press and hold vol down + power. Release power and hold it again IMMEDIATELY once you see LG LOGO ( BEFORE LG ANIMATION ) click the "yes" and "yes"
8. You got the twrp
9. Flash us99820e + magisk via twrp , boot up
10. Refurbish us99820h, boot up
11. Do step 2 and 3
12. Boot OS
13. Boot recovery
14. Flash us99830b via twrp then flash magisk
15. Done u should have pie now
Click to expand...
Click to collapse
ChazzMatt said:
What you are describing is Method #3 in post #6 of the US998 KDZ Pie thread.
It's the workaround which has the most success but is also most complicated.
Click to expand...
Click to collapse
I heard that i will got many problem if i flash aosp rom after upgrade to pie.... Can i fix it with that method?
havetolearn said:
I heard that i will got many problem if i flash aosp rom after upgrade to pie.... Can i fix it with that method?
Click to expand...
Click to collapse
Yes.
What you are talking about is you can't run LOS-16 ROMs on stock Pie. You have to downgrade back to Oreo, and even then you will forever have to run permissive kernel with Oreo firmware for camera/flashlight to work since you once flashed stock Pie.
You would downgrade to Oreo 20h, flash all those steps (H933 Nougat, etc) and eventually get back to US998 20h and then stay there.
More commentary here about stock Pie:
https://forum.xda-developers.com/showpost.php?p=80876797&postcount=65
ChazzMatt said:
Yes.
What you are talking about is you can't run LOS-16 ROMs on stock Pie. You have to downgrade back to Oreo, and even then you will forever have to run permissive kernel with Oreo firmware for camera/flashlight to work since you once flashed stock Pie.
You would downgrade to Oreo 20h, flash all those steps (H933 Nougat, etc) and eventually get back to US998 20h and then stay there.
More commentary here about stock Pie:
https://forum.xda-developers.com/showpost.php?p=80876797&postcount=65
Click to expand...
Click to collapse
Man there are so many broken oreo's firmware after update to pie.... Hmm, i think i will stay at pie because i need lg screen recording feature. It can record screen and system sound together. Thx for replying ChazzMatt
ChazzMatt said:
Yes.
What you are talking about is you can't run LOS-16 ROMs on stock Pie. You have to downgrade back to Oreo, and even then you will forever have to run permissive kernel with Oreo firmware for camera/flashlight to work since you once flashed stock Pie.
You would downgrade to Oreo 20h, flash all those steps (H933 Nougat, etc) and eventually get back to US998 20h and then stay there.
More commentary here about stock Pie:
https://forum.xda-developers.com/showpost.php?p=80876797&postcount=65
Click to expand...
Click to collapse
Uhh sorry Chazz.. Can you help me? I found my phone have trouble with wifi... Whenever i try to connect it just told me "saved"
havetolearn said:
Uhh sorry Chazz.. Can you help me? I found my phone have trouble with wifi... Whenever i try to connect it just told me "saved"
Click to expand...
Click to collapse
1) On my backup V30+ which is on stock US998 30b Pie (but doesn't have a SIM card inserted nor even signed into my Google account), it's connected fine to my home Wi-Fi network so I know it's not a stock US998 Pie issue...
2) This happens even on public free Wi-Fi networks? (Here in the U.S. we have McDonalds, Starbucks?) That would give you clue whether it's one particular router or all your phone has problem with. Or possibly problem with the type of encryption you have on your router.
Usually that message means the router is rejecting the device. You just have to figure out why. But is it one router or all?
3) If one particular router, try rebooting the Wi-Fi router itself.
4) Make sure you don't have any kind of router whitelist for certain devices or MAC addresses and your phone is not included. Or that you don't have some older b/g Wi-Fi chipset standard set; this one is not likely but I had that happen for an older Wi-Fi printer when I had "N" or higher set on my router.
5) On the phone, try forgetting the Wi-Fi network and refinding it. Enter in the password again.
6) Almost last, on the phone try the Network Settings Reset. (See screenshot from US998 30b Pie.) It will reset all network settings including Wi-Fi, Bluetooth.
7) Last, try Factory Reset?
In the same boat
Ergo-sum said:
Hi guys, dealing with a H933 --> US998.
TL;DR - stuck on LG logo, no download mode, no fastboot, master reset does not work, LGUP (patched or unpatched) doesn't recognize phone, computer doesn't recognize it either.
----
Frankenstein method followed correctly, and had unlocked bootloader + root.
Followed H933 specific steps to install AOSP/Linage ROMS. Attempted to install Lineage 16.0 and flashed Lunar kernel. Booted to animation logo and didn't get past that.
Decided to revert back to stock Pie by flashing one of the US998 kdz's. To be honest with you, I tried a few different ones and everything was working fine (I went from Nougat --> Oreo --> Pie in order to bring myself back to Pie firmware to try Lineage install once more but with stock kernel).
This time, phone wouldn't move past the LG animation (right after the logo).
At this point, I lost access to download mode - but I still had fastboot. Installed TWRP again through fastboot and attempted to flash TWRP-JOAN_H933_CANADA_20i.
Lost unlocked bootloader image - lost access to fastboot and recovery - and still didn't have download mode (it would not pass the original download mode image) and would not be recognized by LGUP (patched or unpatched). The phone would be stuck at LG logo, and keep rebooting.
At that point I decided to try a Master Reset. On the second YES, it would hang, and then go back to the LG logo bootloop. Phone does not get recognized by computer.
I know I messed up in numerous points. I got overzealous and likely didn't pay enough attention. Spent all night trying to resurrect it, but to no avail. Any advice for me? Or is the device fully bricked? :crying:
Greatly appreciate any feedback and assistance. Thank you in advance.
Click to expand...
Click to collapse
How did you unbrick your phone? I'm in the same boat as you. I can get to the Download mode, but not past the blue dot image. If I try to master reset, the phone just restarts after the second time I select yes. It's been bootlooping like this for a while now. For context, I was on US99820H(dirty flashed via twrp) when I tried to flash H93330k. @ChazzMatt, I know this is a long shot as what I did was incredibly stupid, but is there anyway I can get out of this?
Ergo-sum said:
Hey guys - brief update. I got back to US998 Oreo with bootloader unlocked and root. I tried to upgrade to US998 Pie by flashing US99830b.zip in TWRP following all the steps, and now the phone doesn't boot again and gets stuck on the LG Logo. Download mode shows "Now waiting For Any Connection" and doesn't detect PC. Any idea how to get this to work so I can flash back to US998 Oreo and just stick there?
Click to expand...
Click to collapse
But, how did you do that if you cant (couldnt) access to fastboot or recovery? Im crazy ?
please. help me.
Ergo-sum said:
Hey guys - brief update. I got back to US998 Oreo with bootloader unlocked and root. I tried to upgrade to US998 Pie by flashing US99830b.zip in TWRP following all the steps, and now the phone doesn't boot again and gets stuck on the LG Logo. Download mode shows "Now waiting For Any Connection" and doesn't detect PC. Any idea how to get this to work so I can flash back to US998 Oreo and just stick there?
Click to expand...
Click to collapse
Please help me, I am the same as you. please
phamtuyenk7d said:
Please help me, I am the same as you. please
Click to expand...
Click to collapse
See this post for Recovery of botched US998 30B upgrade:
https://forum.xda-developers.com/showpost.php?p=81728547&postcount=641
This Guide will explain how to root your LG G8X
* Disclaimer*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*Wait, what? No. Me or somebody else will help you
Click to expand...
Click to collapse
Prerequisites
Unlock phone using the guide here: https://forum.xda-developers.com/t/guide-how-to-unlock-bootloader-of-lg-g8x.4198025/
Do not restore abl before rooting.
Magisk Patched Boot (20e, Indian Variant): https://drive.google.com/file/d/1s2A7RUOptXer5LGMtbGV9SKg0kcyL_NP/view?usp=drivesdk
1. Download the magisk patched boot.
2. Copy it over to your fastboot directory.
3. Connect phone in fastboot mode.
How to put phone to fastboot mode?
#1: Using Button Combination
Power off phone, press and hold Vol- and insert usb cable. You’ll be in fastboot
#2: Using ADB
Connect phone to pc, enable USB Debugging. Then run this command
Code:
adb reboot fastboot
4. Now run the command
Code:
fastboot flash boot Magisk_Patched.img
fastboot reboot
5. Download and install Magisk Manager
6. Done! Your phone is rooted now.
To restore Network follow the guide in bootloader unlock thread...
If you have a different G8X variant or are on a different firmware
1.Backup boot_a or boot_b using QFIL (Partition Manager>Read Data, Check Bootloader unlock guide for more details)
2. Install Magisk Manager
3. Click on Install and use Patch image function.
4. Save the boot image to pc.
5. Flash it in Fastboot using the command given above.
Known Issues: FP is broken
Thankyou
(copypasta'ed from the other thread)
For those who have yet to do this, I suggest extracting boot_a/b at the same time you flash the abl image. Prior to doing the fastboot oem unlock, use the Magisk patch file option (installed on the same or another device, and doesn't need to be rooted) to create a rooted boot image using adb push/pull. Once you fastboot oem unlock, go back into the bootloader and instead of fastboot flash boot, you can fastboot boot magisk_patched.img.
Once you go through the setup, you can open Magisk, which will download and install the full Manager app, at which point it will most likely reboot. You will need to fastboot boot again, and you should be able to do a normal Magisk install. I've usually found that as long as the patched boot is of the same Android version and within a few month of the patch level, it'll boot happily enough to do this. Afterwards, you can restore your abl image as you no longer need to use fastboot commands.
Doing this allows Magisk to save the stock boot image, and also allows you to get OTA updates by restoring the stock image right before any updates. Otherwise you will never be able to do an OTA update as it checks if the boot partition has been modified before installing the updates. Since there are no kdz for the US carrier models, your only other option would be to "brick" your device to try get your carrier's service center to restore a working firmware image.
-- Starfox
Sorry I posted in the wrong thread. I've deleted the contents, but wasn't able to delete the post itself
Guys, I am trying to follow this guide using the "different variant" method, but as soon as I boot after flashing boot.img the touchscreen doesn't work. Only way to get it back is to flash the boot_a.bin and boot_b.bin using QFIL. What am I doing wrong?
Is there a magisk patched image for the g850u20i
Is there an update for magisk patch image for 20b (unlocked US variant)?
Edit: Got my 20b version rooted.
Downloaded stock rom for the G850QM20b, extracted the kdz file to dz to .img grabbed the stock boot_a.img file and ran it in Magisk manager app, took the converted .boot.a.img (now renamed magisk_patched_clT14.img) and dropped it in platform tools, went fast boot, then flashed it. Came back up great, no issues and root access is clear.
Dapeplezchamp said:
Is there a magisk patched image for the g850u20i
Click to expand...
Click to collapse
I have 20j and I can't even get into edl or fastboot... Can you get into fastboot mode? I've tried adb and button combos
robnitro said:
I have 20j and I can't even get into edl or fastboot... Can you get into fastboot mode? I've tried adb and button combos
Click to expand...
Click to collapse
I cannot.I've tried everything I know to do.I'm so cautious with this phone because I got it at a steal off of eBay and would hate to brick it.
Dapeplezchamp said:
I cannot.I've tried everything I know to do.I'm so cautious with this phone because I got it at a steal off of eBay and would hate to brick it.
Click to expand...
Click to collapse
follow the video here, I got it to work
hold power and vol down , itll countdown to reboot.... as soon as it does that- while holding down and power tap the up button
How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)
All fix avilable (no network solved) Watch it carefully do it step by step as showen in my video you will never brick if you follow my video :):love: All required files are in the video description This guide Tested on the firmware (20e...
forum.xda-developers.com
Is there a image for the g850UM20g?
edit:
I have a copy of boot_a but in the fastboot it tells me that I am using abl_b and I don't know if boot_a is compatible with abl_b and i can't enter EDL mode
So my understanding is you can have a rooted phone, but FP will be broken no matter what and possibly audio as well. You can fix this by reinstalling a Pie version from KDZ, fix it then reinstalling a 10, but then the root will be gone (but the bootloader remains unlocked). Is this correct?
zdanee said:
So my understanding is you can have a rooted phone, but FP will be broken no matter what and possibly audio as well. You can fix this by reinstalling a Pie version from KDZ, fix it then reinstalling a 10, but then the root will be gone (but the bootloader remains unlocked). Is this correct?
Click to expand...
Click to collapse
Yes, rooting will be gone and Bootloader remains unlocked forever. You have to root it again in A10
For anyone in the future: you can have both root and fingerprint. Follow the bootloader unlock guide up to the point where you have to backup your boot_a. After that you don't use the patched boot_a in the instructions, instead patch your own version with magisk and flash that instead with QFIL. I now have a working V20h EU version with root, fingerprint and working audio.
Anu one have LMG850UM 20f magisk patched boot file?
Country china
Lg g8x
Kanhei015 said:
Anu one have LMG850UM 20f magisk patched boot file?
Country china
Lg g8x
Click to expand...
Click to collapse
I do. But it's an EU version, so I'm not sure it would work for you. However it's easy to just make your own!
- Install Magisk manager on the phone. You don't need open bootloader or anything for that
- Get your own 20f boot_a using QFIL
- Copy your own boot_a to the phone or on an SD card
- In Magisk Manager you choose to install magisk, select patching an IMG file method and give it the boot_a
- If Magisk reports success you'll now have a magisk_patched_boot_a file. Copy that back to your PC
- Using QFIL flash that in place of your original boot_a
- Keep a copy of your original boot_a thou, you can go back with QFIL at any time.
- If you mess up royally and the phone doesn't boot, you can still recover it by re-flashing your firmware with LGUP 1.17. You'll have to download your region's firmware for that and you'll loose all data, so make a backup beforehand!
edit: double post
zdanee said:
For anyone in the future: you can have both root and fingerprint. Follow the bootloader unlock guide up to the point where you have to backup your boot_a. After that you don't use the patched boot_a in the instructions, instead patch your own version with magisk and flash that instead with QFIL. I now have a working V20h EU version with root, fingerprint and working audio.
Click to expand...
Click to collapse
Hi, thanks for sharing the steps!
I followed your steps but don't have audio/network/fingerprint after flashing patched boot. Later I also tried to restore abl_a/b, then I had audio and network working, but still no fingerprint.
In my case, fingerprint stopped working once bootloader is unlocked, before even flashing the patched boot.
Did you have working fingerprint right after you flash patched boot? Did you restored abl_a/b?
I also tried to follow another post to get fingerprint working, but I can only find 10b kdz of my variant (twn), I downgraded to android 9 using that kdz, still cannot get fingerprint to work.
james508959 said:
Hi, thanks for sharing the steps!
I followed your steps but don't have audio/network/fingerprint after flashing patched boot. Later I also tried to restore abl_a/b, then I had audio and network working, but still no fingerprint.
In my case, fingerprint stopped working once bootloader is unlocked, before even flashing the patched boot.
Did you have working fingerprint right after you flash patched boot? Did you restored abl_a/b?
I also tried to follow another post to get fingerprint working, but I can only find 10b kdz of my variant (twn), I downgraded to android 9 using that kdz, still cannot get fingerprint to work.
Click to expand...
Click to collapse
I also messed up at first, since there were no ready-made boot_a for my region/version I just grabbed the indian one for 20e, and yes, that did break my audio, fingerprint and possibly network, I didn't test that one. I did have a KDZ for my region thou, so I flashed back a 10c version, I needed the 1.17 tool, not the 1.14 or 1.16 one (those did not work) and in my case I needed the second version of 10c, not the first one to fix the fingerprint. After flashing 10c I did all the steps and regained my fingerprint reader without an issue (so no, it did not work right away, I did need to go into the service menu and do the test), audio and network also worked right away. After that I flashed my latest KDZ (20h) and using magisk manager made my own boot_a and was able to root with a working fingerprint. I did not dare to update Magisk after this thou, I only needed it to grant root for my adblocker, and it's hidden from everything else, I don't think I'll ever even start magisk again, so I don't really want to update it either.
Did you restore abl_a/b at all? I can only get into download mode (to use LGUP) after I restore abl_a/b.
Anyways, I think flashing using LGUP overrided the abl, and that's why audio and network worked right away (to my understanding)
My LGUP tool worked fine, but there only 10b for my TWN variant, I couldn't find 10c anywhere... (only 10b, 20a, 20b available)
I never flashed other's patched boot, I used QFIL to get my boot_a.bin and patched it using Magisk on another phone. Then I used fastboot to flash boot. (I did this right after unlocked BL, all before I restored abl).
Did you also use QFIL to get boot_a or did you use KDZ extractor? I'm having problem with my KDZ extractor tool, encoding issue or sth.
My variant is G850EMW, should I try the indian 10c kdz (which is also G850EMW)? Would that work? Not sure what risk cross region flashing poses, or even if LGUP would let me flash it at all.
james508959 said:
Did you restore abl_a/b at all? I can only get into download mode (to use LGUP) after I restore abl_a/b.
Anyways, I think flashing using LGUP overrided the abl, and that's why audio and network worked right away (to my understanding)
My LGUP tool worked fine, but there only 10b for my TWN variant, I couldn't find 10c anywhere... (only 10b, 20a, 20b available)
I never flashed other's patched boot, I used QFIL to get my boot_a.bin and patched it using Magisk on another phone. Then I used fastboot to flash boot. (I did this right after unlocked BL, all before I restored abl).
Did you also use QFIL to get boot_a or did you use KDZ extractor? I'm having problem with my KDZ extractor tool, encoding issue or sth.
My variant is G850EMW, should I try the indian 10c kdz (which is also G850EMW)? Would that work? Not sure what risk cross region flashing poses, or even if LGUP would let me flash it at all.
Click to expand...
Click to collapse
No, I did not restore abl_a/b, and after KDZ the bootloder remained open, so there is no need to, the phone still reports an open bootloader at boot. If it _does_ override it thou it seems it's not neccessary to have, as I could root the phone and could keep the open bootloader anyways.
I used QFIL to get my own boot_a, and used it again to flash it back too.
My EU (Hungarian T-mobile) version is also G850EMW. My understanding is that if LGUP lets you flash a KDZ it's probably gonna work, but in the worst case scenario as long as you have a known good KDZ for your model you can always come back to that, so I guess you can experiment?
I've also only found a 20b version of KDZ for TWN, but it's release date is similar to 20h in the EU, so maybe these numbers doesn't mean they are the same KDZ, only that 20x meant it's Android 10 and the letter is the revision. Based on this it's possibe you don't need a 10c to restore your fingerprint, just try the earliest 10x KDZ you can get your hands on (for me the 10c was the earliest one). Alternatively you can try the 10c I used for mine, it's EU Hungarian, but the default language is still English and you'll re-flash it anyways: https://lg-firmwares.com/downloads-file/21667/G850EMW10c_00_OPEN_EU_DS_OP_1122