Database Develop

[STOCK][M][TMO] Guide H811 20i & 20o Bootloader Unlock + Root + TWRP

Note : This guide is for H-81120-I & H-81120-O the latest update any firmware version below it will cause hard-brick so be careful before attempting anything, i wont be held responsible.
As a user with less knowledge about Commands and all, i was searching for answers by reading threads here and there and found my answers though some time tricky and sometimes easy.
Also in reading those threads i found many fellow members stumble upon resulting Soft bricks and in some cases a Hard brick or can say making their beloved G4 a paper weight.
So i thought i must put some really easy steps in order to clearly guide people like me who are too noob to understand the sophisticated developers steps.
Another reason for this Thread is also i saw many people asking about how to etc after updating to 20-O update for our H811 MM.
Few things to Prepare before Start
1- Properly Install Drivers for your H811 Variant of G4, cant find them Install LG Bridge.
2- Read the Whole thread before starting anything.
3- Confirm that all requirements are full filled and your variant is capable of everything mention in the OP.
4- Enable Developer Option then inside it enable OEM unlock and Usb debugging.
5- Always use Command prompt as Administrator.
6- Make a folder name G4 and paste all the file required for the unlocking in it for easy access and remembrance.
7- For Safer side after unlocking the bootloader boot into TWRP from fast boot and do not install TWRP.
8- Flash your SuperSU after that boot into android and see if all works.
9- Again Via Fastboot boot into TWRP make a backup of everything working fine. Boot into android.
0- Again same Via Fastboot boot into TWRP and now install your TWRP image via TWRP install function. So if by any means this is the culprit you can still revive your phone via your backup.
Attachments to Download
1- Adb Package can be found Here.
2- Download the latest TWRP.img 3.0+ from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Since downloading is complete now simply unzip the adb folder (containing fastboot by default) and paste both the TWRP image file and SUPERSU zip inside it.
Now Hold Shift and Open Command prompt here.
1- Input command to see if your device is visible in ADB.
Code:
adb devices
if you see your device and the status is off line then there will be a prompt on your G4 screen waiting for approval, accept it and input same command now all will be fine.
2- Now input below commands one by one. ( All credits to Autoprime )
Code:
adb reboot bootloader ( This will reboot your device to Fastboot mode )
fastboot oem unlock ( This will wipe all your data )
fastboot getvar unlocked ( This will check your bootloader status: Should be successful )
fastboot boot twrp-3.0.2-0-h811.img ( Phone boots TWRP ) Please put the full file name with .img extension or it wont work.
3- Now the Phone should be in TWRP install SuperSU from there which you have already pasted inside your external SD card.
4- Reboot to system and see if SuperSU is installed. In some cases First flash of SuperSU does not work if your case is same the again boot to Fastboot and from there boot into recovery, since your bootloader is unlocked no need to repeat the unlock OEM command.
5- Now for safer side follow the steps 7, 9, 0 mention in Preparation heading above.
Hopefully all will be in your favor.
Useful Links if you still fail
Kdz 20-O after download must be unzipped
H81120o_00_0613.kdz
LGUP Software:
( All credits to MicroMod777 )
Disclaimer: Nothing in this thread is my work, if i have missed any credit please do let me know i will add. I know several guides are available for same purpose so if any body finds it offending any rights can ask the moderators to remove this thread. The purpose only is to guide simple people like me to save their devices from getting bricked.

As by reading the thread many people are falling for permanent TWRP installation as its mention in the OP anyways for people not getting permanent Recovery follow below:
Boot to TWRP from fastboot Bootloader
When recovery comes up click Install >>>> then in the right below corner you ll see a tab for IMAGE >>> press it browse the recovery IMG which you stored in your SD card >>> swipe to flash >>> From asking where to install >>> select recovery >>> DONE.

SignatureBoy said:
Attachments to Download
1- Adb Package can be found Here.
2- Download the from Here . This file needs to be on your computer and external sdcard.
3- Download the latest SuperSu zip (2.67+) from Here [Thanks to Chainfire] and stick on external sdcard as well.
Click to expand...
Click to collapse
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.

DrakenFX said:
Indeed needs to be in both but needs to be in the same Folder as Fastboot file, if not wont work.
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
the ADB package i uploaded contains the Fastboot inside it
The thread clearly states it for 20-O

SignatureBoy said:
the ADB package i uploaded contains the Fastboot inside it
Click to expand...
Click to collapse
ok i meant the TWRP file needs to be in the same folder where Fastboot file is

DrakenFX said:
ok i meant the TWRP file needs to be in the same folder where Fastboot file is
Click to expand...
Click to collapse
That is also mention if you read the first post,
Since downloading is complete now simply make a folder and put all files downloaded inside it unzip the adb folder and paste both the TWRP image file and SUPERSU zip inside it.
Click to expand...
Click to collapse

SignatureBoy said:
DrakenFX said:
beside will be cool if you add a NOTE about if they are in 20o they must stick with 20o base roms, if not they'll get Hard-Brick.
Click to expand...
Click to collapse
The thread clearly states it for 20-O
Click to expand...
Click to collapse
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.

ApokrifX said:
Guys,
If I read it right:
LG G4 must be on 20o (stock) to follow this instruction.
If it’s on 20i or below, it must be updated to 20o (OTA or whatever) first!
It might be obvious for you, but not for me.
Again, but better be safe, then sorry.
Click to expand...
Click to collapse
yes it is for 20-O only

SignatureBoy said:
yes it is for 20-O only
Click to expand...
Click to collapse
Thanks for clarification. I’d change 1st post a bit:
Few things to Prepare before Start
0. LG G4 with 20o (stock) firmware.

When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
DanGarion said:
When I do adb reboot bootloader it just boots me back into Android... shouldn't it take me to the Fastboot screen?
Click to expand...
Click to collapse
Nevermind, I forgot about OEM Unlock...

thanks for the write up

This is not specific to 20o. It's the same steps we've been using all along. Nothing new to see here.
Sent from my LG-H811 using XDA-Developers mobile app

problem with fastboot
Thanks you for helping:fingers-crossed:

problem with fastboot
Hi,
I am a newbie in xda. I am trying to root and install TWRP into my lg g4. I am using software version H81120o. I checked enable OEM unlock and USB debugging. I have downloaded lg driver though lg bridge and all the files from the post. However, I got two problem while installing the twrp-3.0.2-0-h811.img.
1st problem (stuck here and need to reboot also not showing h811 on "the list of devices attached" after typing command "adb reboot bootloader"):
C:\Windows\system32>adb devices
List of devices attached
LGH811xxxxxxxx device
C:\Windows\system32>adb reboot bootloader
C:\Windows\system32>fastboot oem unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.012s
C:\Windows\system32>fastboot getvar unlocked
unlocked: yes
finished. total time: 0.004s
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
cannot load 'twrp-3.0.2-0-h811.img': No error
2. 2nd problem(stuck here and need to reboot):
C:\Windows\system32>fastboot boot twrp-3.0.2-0-h811.img
< waiting for device >
I checked online this problem might do with driver not up to date. Under device manager, my lg g4 is recognized under android device with android bootloader interface.
What should I do now?
Thanks you for helping:fingers-crossed:

This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??

I did everything but can't seem to get TWRP installed

Thanks a lot for this write up. I have been trying for about 2 weeks to root my g4 and it worked finally, So many thanks to you

The Remedy said:
This Root-Method worked like a charm... The only issue I'm running into is for the TWRP recovery to actually stick. When i manually reboot into recovery I get the little android guy with his chest open and the red triangle with the "!" in the middle.....am I doing something wrong by any chance??
Click to expand...
Click to collapse
same problem here but I just now got it working...sort of . I still can not make anything come up except the factory data reset when I use the phone volume and power button.
I thought it might be just that I wasn't coordinated enough so I downloaded this small app to do a recovery reboot.
After I installed the app and used it, I got the little android guy with his chest opened with the red triangle. I took out my battery, put it back in and booted my phone with the power button.
I then connected my phone to computer via usb and went back into adb and opened TWRP and installed the twrp-3.0.2-0-h811.img again but this time I looked around a little more first, and noticed a setting to either install in boot or recovery partition. I selected recovery partition (neither were selected) and installed it. Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.

I had the same issue but when u get into twrp make sure the IMG is in your SD card and to permanently have twrp installed go to home and press install.. Choose from image and install hope this helps
Sent from my LGLS992 using Tapatalk

fuzzy_ said:
same problem here but I just now got it working...sort of ................
Now I can boot to TWRP recovery with the app I installed but still nothing but factory data reset with the volume and power buttons. I can live with this for a while until I can maybe find a solution.
Click to expand...
Click to collapse
In regard to booting into TWRP recovery with just the power and vol buttons, I just read this on another thread:
It boots into what appears to look like a default LG G4 factory reset page. For me, i clicked reset, and then yes, and surprisingly it brought me to where i wanted to go. TWRP Recovery.
I tried this and it worked for me as well.
I had been there before and tried it and it did a factory reset after I had spent an hour or two tweaking my phone, I was not a happy person. This time I did feel almost positive I had TWRP installed correctly and did not have nearly as much time spent getting things set up like I want them on my phone...It was still scary pressing that reset button and yes button.
If you don't have TWRP (or maybe some other recovery) installed it will factory reset your phone. I just thought I would share this and what happened with me. Do it at your own risk.

How to Re-Lock Bootloader?

I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?

TechGuruGJ said:
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
Click to expand...
Click to collapse
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore

I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.

Yes, it does work. I did it, worked perfectly. Yes it does return your device to it's original state. Just make sure the stock ROM is flashed and all should be well. I didn't try, but I see no reason why it wouldn't let you get OTA updates from T-Mobile. Let me know if you need help.

Nadeox1 said:
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Click to expand...
Click to collapse
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.

raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
Thanks both for replying.
And no @raptorddd , I did not mean that.
Your post is the only mentioning that locking the bootloader is possible, while all the other similar threads have ony people saying otherwise / it's not possible. I guess a slightly doubt is legit to have, don't take it wrongly

raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
I have follow this instructions and now it giving me and error. Any fix??

WARMANH811 said:
I have follow this instructions and now it giving me and error. Any fix??
Click to expand...
Click to collapse
What error?

TechGuruGJ said:
What error?
Click to expand...
Click to collapse
Secure booting Error!
Error code: 1003
MODIFIED ! !

WARMANH811 said:
Secure booting Error!
Error code: 1003
MODIFIED ! !
Click to expand...
Click to collapse
are you sure you have h811.? i did not get that error ive tried this twice..
i remeber getting an security boot error on LG G2 i fix by flashing firmware .. so maybe KDZ could help..
if not am not sure then search for that error and find out how to fix.

raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.

joecandle said:
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
Click to expand...
Click to collapse
no need to downgrade. to remove root and any trace if phone works. is to use KDZ then once it boots into system do the lock procedure. so it locks and the small white letter are removed. this way its like stock rom and recovery and the above commmands will make bootloader locked. and sent to repair. if bootloops try the freezing method.

Used on an LG Aristo that has Cyanogen and it worked
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
This was the only one i found that didnt brick my phone and trust me ive bricked and unbricked this phone many times

When you use the fastboot command to lock back your bootloader, the phone doesn't revert automatically to the stock recovery and actually that is partly the reason why it bricks and other main reason is that changes made to bootloader to obtain root brick the phone. before you relock bootloader, if you have SuperSU (in-app menu option) or Magisk (uninstall zip file), use their respective methods to unroot the phone, then use twrp to flash .image file of stock recovery to recovery partition then use the fastboot command to lock the bootloader. Even then it may or may not work because if whatever method the phone uses to check the integrity of bootloader and/or recovery, such as md5, if it doesn't match, the phone will still brick. Since all your data on phone will be erased regardless as soon as you lock the bootloader, i personally just fastboot lock the bootloader, remove battery to power down, use the volume up and plug usb cable in from pc to put phone in download mode and just use LGUP (uppercut) if have kdz file already, which i do, i just let LG Bridge download the file, find it in programs folder and copy it to another location before LG Bridge deletes it --OR-- just use error recovery option in Software Update tab in LG Bridge as both LGUP and LG Bridge will detect the phone in download mode even if it is bricked.
By the way, I have used both methods above dozens of times without any issues, someone above who mentioned phone boot-looping because of locking the bootloader, it is boot-looping not because of hardware flaw which was widespread in LG G3 but a software issue (phone boots up, doesn't find the software configuration it is looking for and just restarts) and they are not the same issues, no need to freeze the phone, won't help.

the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.

metropical said:
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
Click to expand...
Click to collapse
The above points to you not giving permission possibly because either you missed the permission pop-up or selected option that didn't allow permission.

Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly

Lukasz23 said:
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Click to expand...
Click to collapse
managed to solve?

Root rog 2

Hello everyone, i got rooted Rog Phone 2 and after rooting my rog phone 2 i dont have wifi signal anymore. i unroot my phone by flashing stock + tried flashing stock boot.img but wifi is still not working, what happened and how can i fix it?

@Barcovn Would you like to share how to deal with this?

https://m.facebook.com/groups/2059277157699287?view=permalink&id=2106812296279106
From my friend. He share the Tut for fixing it. Basically we upgraded new fw after open the phone so the boot.img extracted from the website will be difference with newest ota upgrade. Lost wifi. You have to manual flash the phone again

Barcovn said:
https://m.facebook.com/groups/2059277157699287?view=permalink&id=2106812296279106
From my friend. He share the Tut for fixing it. Basically we upgraded new fw after open the phone so the boot.img extracted from the website will be difference with newest ota upgrade. Lost wifi. You have to manual flash the phone again
Click to expand...
Click to collapse
Right! As I haven't got the phone yet, didn't find out that new OTA have different boot.img. So as for now, rooting means just firmware on website is usable.

In the future if there is an update you will need to unroot, flash the original boot. Flash the rom update and then extract the new boot, patch it with magisk and flash the new patched boot to enjoy root again.
Personally I would rather stay on stock enjoy the timely OTA updates and keep my warranty.

dungnghien said:
Hello everyone, i got rooted Rog Phone 2 and after rooting my rog phone 2 i dont have wifi signal anymore. i unroot my phone by flashing stock + tried flashing stock boot.img but wifi is still not working, what happened and how can i fix it?
Click to expand...
Click to collapse
Hello dungnghien,
Could you please share the steps to root it? Also, where can I find the stock firmware in case things don't go well and I need to rom it.
Would appreciate your help.

So I unlocked bootloader using apk from asus site and patched boot.img using magisk. Now how to flash "magisk_patched.img"?
Can someone help please?

havork said:
So I unlocked bootloader using apk from asus site and patched boot.img using magisk. Now how to flash "magisk_patched.img"?
Can someone help please?
Click to expand...
Click to collapse
Follow the same procedure done for the ROG phone.
https://forum.xda-developers.com/rog-phone/how-to/guide-root-t3865490

Rashad83 said:
Follow the same procedure done for the ROG phone.
https://forum.xda-developers.com/rog-phone/how-to/guide-root-t3865490
Click to expand...
Click to collapse
Tried that already. No luck.
Is the phone supposed to go into some special download mode screen like on Samsung?

havork said:
Tried that already. No luck.
Is the phone supposed to go into some special download mode screen like on Samsung?
Click to expand...
Click to collapse
After patching the boot.img did you boot into fastboot mode and runned the command for flashing the patched boot.img.
Was the flash successfull or not?
Please be specific in what step you are having issues with and what actions you took.

Rashad83 said:
After patching the boot.img did you boot into fastboot mode and runned the command for flashing the patched boot.img.
Was the flash successfull or not?
Please be specific in what step you are having issues with and what actions you took.
Click to expand...
Click to collapse
I'm trying to follow steps from the tutorial.
Device is on, USB debugging on
adb devices list my device
adb reboot recovery reboots into recovery, but I don't see "Select ADB on phone" option antwhere in recovery.

havork said:
I'm trying to follow steps from the tutorial.
Device is on, USB debugging on
adb devices list my device
adb reboot recovery reboots into recovery, but I don't see "Select ADB on phone" option antwhere in recovery.
Click to expand...
Click to collapse
There is no such option with the stock recovery. Any way why do you need that. You don't need to use ADB commands to flash the patched boot.img.

Rashad83 said:
There is no such option with the stock recovery. Any way why do you need that. You don't need to use ADB commands to flash the patched boot.img.
Click to expand...
Click to collapse
So how do I flash the patched image? I really need to root this thing and would appreciate the help.
In Samsung phones it's pretty easy, boot into download mode and flash using odin, how to do that on this phone?

Anyone wanna report if there's any issues after rooting the device?

havork said:
So how do I flash the patched image? I really need to root this thing and would appreciate the help.
In Samsung phones it's pretty easy, boot into download mode and flash using odin, how to do that on this phone?
Click to expand...
Click to collapse
Follow step 8 in the tutorial, are you following the steps in the first page of the link i gave?, because the steps are straight forward.

Step 8

Rashad83 said:
Follow step 8 in the tutorial, are you following the steps in the first page of the link i gave?, because the steps are straight forward.
Click to expand...
Click to collapse
Turn device off.
hold down volume up and power button.
I get these three options you see in screenshot.
No download mode option.

havork said:
Turn device off.
hold down volume up and power button.
I get these three options you see in screenshot.
No download mode option.
Click to expand...
Click to collapse
There used to be a fastboot mode on the ROG phone on Android Oreo, i am not sure if things changed with Android Pie.
Anyway try the hardware method to connect, turn your phone off and connect it to the PC using the side port make sure to hold the low volume key when connecting the phone to the PC. See if a fastboot mode black screen shows up.
If not:
On the bootloader screan the second one you showed. On your PC after going to your platform tools and running the cmd window from there type the command:
Fastboot devices
Does it recognize your device?, if it does run the 2 commands stated in step 8. But do it on your own risk if something goes wrong you might brick the device and if you are not able to flash back the stock boot i am afraid you will end up with a bricked device until a solution is suggested.

I can't get into fast boot mode. Tried all options, volume up, volume down, usb, no usb, debugging on, debugging off...
No luck.
$20 for whoever helps me get this thing rooted.

havork said:
I can't get into fast boot mode. Tried all options, volume up, volume down, usb, no usb, debugging on, debugging off...
No luck.
$20 for whoever helps me get this thing rooted.
Click to expand...
Click to collapse
Maybe @Barcovn can help since he got root.

Endless bootloop (Redmi 9 lancelot)

I tried installing crDroid (unlock bootloader, uploaded FW, recovery SHRP, then install ROM) and after reboot the phone would go back to recovery.
By mistake I "installed" SHRP from ZIP package (I thought I need to install latest recovery file to install ROM with android 12) and phone went into reboot loop, I can't do anything, any key combination doesn't help - I can't even turn it off.
help!

I opened the phone, disconnected the battery, but nothing happened - still bootloop
I'm planning to use SP Flash Tool
Immediately after connecting USB C, the phone boots into bootlop (after disconnecting and reconnecting the battery)

What happens when you flash the custom ROM?
Try to flash the stock firmware and miui
again. Download the latest miui recovery ROM for Lancelot and copy it to the sd card. If you can still boot into recovery you can connect the phone with a PC.
You can also try to reboot into bootloader if the reboot options work from sharp, if not connect the phone to a PC with adb and fastboot installed on it and type:
Code:
adb reboot bootloader
And now if you are in fastboot you can do anything, you can try to reflash the firmware, recovery etc.
I personally don't use SHRP, it was really buggy and not great. I use the twrp from this link: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/.
Thanks for reading and I hope u succeed,
Bye.

U can also try to flash it with MI flash tool.

Sergij-SApcPro said:
What happens when you flash the custom ROM?
Click to expand...
Click to collapse
Operation completed with status [ ]. It looks like there should be a * in the middle and then it would be a sign to me that the ROM is loaded.
Sergij-SApcPro said:
Try to flash the stock firmware and miui
again. Download the latest miui recovery ROM for Lancelot and copy it to the sd card. If you can still boot into recovery you can connect the phone with a PC.
Click to expand...
Click to collapse
At the time of writing, no key combination was working - I can't get into Fastboot or Recovery. I let the battery run out for that moment.
Sergij-SApcPro said:
You can also try to reboot into bootloader if the reboot options work from sharp, if not connect the phone to a PC with adb and fastboot installed on it and type:
Code:
adb reboot bootloader
And now if you are in fastboot you can do anything, you can try to reflash the firmware, recovery etc.
I personally don't use SHRP, it was really buggy and not great. I use the twrp from this link: https://forum.xda-developers.com/t/recovery-twrp-unofficial-twrp-recovery-3-6-1_11-0.4421301/.
Thanks for reading and I hope u succeed,
Bye.
Click to expand...
Click to collapse

Sergij-SApcPro said:
U can also try to flash it with MI flash tool.
Click to expand...
Click to collapse
That's what I'll do first, then move on to the solution below.
I opened the phone and disconnected the battery, but plugging in the USB cable immediately turns the phone on and bootloops again.
I'm using Linux and Windows, and one user hinted at hacking the USB driver so I believe it won't boot the phone, only then will I have communication? Other than that I don't know how to do it anyway.
For now, after the phone's battery runs out, I'll try with this solution
MTK Authorisation Bypass
Thanks to Dinolek ErdilS xyzz **All Steps Are Mandatory, Don't Skip Any Of Them** How to install: 1. Download the attached file: Alternate Download:https://anonfiles.com/l0yeSfD2u7/MTK-Bypass_zipAlternate Download:https://dl.uploadgram.me/6126628127c5fh?raw 2. Extract the file and open the...
telegra.ph

I've exhausted the battery, Mi Flash needs Fastboot, which I don't have.
I used
Deleted Account in Redmi Note 9 / Redmi 9 / 10X 4G Community
• Unbrick method for basically any device covered in this group. - Download SP Flash Tool from here. - Download the corresponding Engineering ROM for your device using #engrom - Download this zip and extract it. You Should find a DA file and an auth file in it. - Do the steps in this video...
t.me
I got to the point of connecting the phone to the computer and it connects (the procedure says to use the Power button, but I had to disconnect the battery because Bootloop was falling in), using the Vol- button - the phone keeps connecting and disconnecting....

For a while I tried to connect the phone via SP Flash under Linux - in administrator mode the message "memory protection violation" appears (I don't know how the message is in English).
Adding a udev exception was supposed to help - after lsusb the Mediatek device appeared, I added the exception, restarted - and the same thing happens (the program crashes).

I finally managed (with the help of a group on telegram https://t.me/HelioG85_Unified) by switching off the phone and carefully going through all the points (except the update at the very end) from this link
MTK Authorisation Bypass
Thanks to Dinolek ErdilS xyzz **All Steps Are Mandatory, Don't Skip Any Of Them** How to install: 1. Download the attached file: Alternate Download:https://anonfiles.com/l0yeSfD2u7/MTK-Bypass_zipAlternate Download:https://dl.uploadgram.me/6126628127c5fh?raw 2. Extract the file and open the...
telegra.ph
There is a little problem, because SP Flash must be from the link in this post (because it will not fit DA)
Deleted Account in Redmi Note 9 / Redmi 9 / 10X 4G Community
• Unbrick method for basically any device covered in this group. - Download SP Flash Tool from here. - Download the corresponding Engineering ROM for your device using #engrom - Download this zip and extract it. You Should find a DA file and an auth file in it. - Do the steps in this video...
t.me

Wow so many posts... Did you manage to fix the phone now? What do you mean by SP Flash will not fit the DA? Did you download the eng ROM for Lancelot? BTW I haven't done this kind of thing, but when I tried to flash my Lancelot with SP Flash tool it didn't work, because it was just waiting for device.

Sergij-SApcPro said:
Wow so many posts...
Click to expand...
Click to collapse
Often when reading threads I see "managed to fix, thanks!" but it doesn't say what and how, so that's why so many posts - so someone knows what was going on.
Sergij-SApcPro said:
Did you manage to fix the phone now?
Click to expand...
Click to collapse
Yes
Sergij-SApcPro said:
What do you mean by SP Flash will not fit the DA?
Click to expand...
Click to collapse
Other versions of SP Flash (newer) other than in the package with ENGROM didn't work with DA file with manual from links given above - it had to be the one from the package. SP Flash showed errors and crashed or informed about wrong file.
Sergij-SApcPro said:
Did you download the eng ROM for Lancelot?
Click to expand...
Click to collapse
Yes
Sergij-SApcPro said:
BTW I haven't done this kind of thing, but when I tried to flash my Lancelot with SP Flash tool it didn't work, because it was just waiting for device.
Click to expand...
Click to collapse
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.

Great to hear that you fixed the phone, congratulations!
TomekParuszewski said:
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.
Click to expand...
Click to collapse
Thanks for the info, but I don't need to flash it with SP Flash tool because that was earlier when I didn't try to install custom recovery. Now I have SHRP with CRDroid A12 and its Awesome.
Thanks for reading,
Bye

TomekParuszewski said:
Often when reading threads I see "managed to fix, thanks!" but it doesn't say what and how, so that's why so many posts - so someone knows what was going on.
Yes
Other versions of SP Flash (newer) other than in the package with ENGROM didn't work with DA file with manual from links given above - it had to be the one from the package. SP Flash showed errors and crashed or informed about wrong file.
Yes
I think that if you go through the MTK Bypass process carefully, step by step, you may succeed, as I did.
Click to expand...
Click to collapse
What version of SP Flash tools did you use? I'm running into this (status_ext_ram_exception error) kind of error while trying to flash the firmware provided in the Telegram channel.

SandShadow said:
What version of SP Flash tools did you use? I'm running into this (status_ext_ram_exception error) kind of error while trying to flash the firmware provided in the Telegram channel.
Click to expand...
Click to collapse
yes, im stuck at same error. any ideas? someone said we should let the phone completely discharge, im waiting on that, but just incase any other ideas...

voland34 said:
yes, im stuck at same error. any ideas? someone said we should let the phone completely discharge, im waiting on that, but just incase any other ideas...
Click to expand...
Click to collapse
The battery trick does'nt work for me. I can't remember exact version, sorry - but my way was going BACK with SP Flash tool version (from newest to working with file). When I found right version the rest was only going with procedure.
I did it twice: first time I was scared, second - with finding right version of SPFT, every time - like walk in the park. Looong walk all procedure was like 2-3 hours.
Second one try was after trying to load Andorid 13 (2x). Don't do it kids!
After all, my Revolut app stop working lately on my phone and Redmi is retired for now... (and also becoming unusable because slowing dramatically)

Thanks for your answer. it has worked with battery empty (though that might not have benn necessary); not on 1st atttempt v5.2020 but it did with version 5v.2216 in case it might help someone...it didnt flash miui fastboot rom 12.5 but it did flash engineering rom. and from there i will twrp and miui.
Thanks for your suggestion of trying different spflash versions.

Question IDK Redmi 10S

Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.

Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?

Andris85 said:
Hi there.
I wanted to root a Redmi 10S device. Bootloader was also opened. The flash went during fastboot mode, then after the fastboot reboot command, the device restarted, but it only shows "Redmi" and the word android at the bottom. I tried to access recovery and fastboot mode, but powr+volD only restarts the device and only the Redmi inscription is visible.
I don't know what they call this state in which the device is.
If there is a suitable link on the forum, I would appreciate it.
Click to expand...
Click to collapse
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it

gurtnyi said:
Hi there!
What did you flash excatly?
I mean, did you flash the whole phone, or just a patched boot image?
Click to expand...
Click to collapse
Just the boot.ini. but I think this would make fastboot mode work. But it's not working

tutibreaker said:
reflash stock and done to enter in fastboot mode press power and volD keep presing volD until the phone start in fastboot mode and flash it
Click to expand...
Click to collapse
What should I use to reflash? Mi flash? This is the NS

Yes... I probably mixed up the boot file in the downloads folder and not the correct received flash
Click to expand...
Click to collapse
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?

gurtnyi said:
Then, you don't have to flash the whole phone again, just flash back the original image, and try rooting with twrp and magisk zip file (rename the apk file from magisk.apk to magisk.zip, and then flash it in twrp)
If you can't install twrp, or something went wrong, take a full backup from your phone (like using google's backup service, and Miui backup--> it 'll save the backup to internal storage/miui/backup/AllBackup) and then ypu can reflash the phone with mi flash tool, but don't lock the bootloader back, and after flash, you shuold enable oem unlock in developer settings.
One quick question:
Did you enable oem unlocking in developer settings, before trying to flash the modified image?
Click to expand...
Click to collapse
yepp, enable oem unlock. But fastbootmode is required for all operations. But fastboot mode doesn't work.

What do you mean it doesn't work?
Can't enter into fastboot mode?

gurtnyi said:
What do you mean it doesn't work?
Can't enter into fastboot mode?
Click to expand...
Click to collapse
Can't enter fastboot mode. The device only shows "Redmi" lettering. If fatboot worked, I could have done it already. power+volume down, the device just restarts and shows "redmi".

Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode

gurtnyi said:
Hmm..
And if you holding the volD and power buttons together for a longer time?
Like a min, or sth
I had a similar situation, but after a few tries it went into fastboot mode
Click to expand...
Click to collapse
it just restarts, as long as I press and hold volume down+power, if I don't press it, it just shows the redmi text

I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.

gurtnyi said:
I apologise, but I 've currently ran out of ideas. If I can find any solution, I 'll post an answer about it.
Click to expand...
Click to collapse
TXH

Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss

Pegelaar_NL said:
Hi there the forgive my on my bad english and text.
The Only thing u can do is restoring the firmware by using brom mode, Look it up or follow the steps i'll give u....
First keep in mind brom works best Without the batary conected . So remove the thin cover plate at the back u can loosen it with heat , after removing the cover move all screws and remove the housing so u can disconect the batary at the mainboard .
Next u will have to install the Vcom drivers according your chipset mediatek etc.
For the Vcom drivers and install of it u can follow https://www.hovatek.com/forum/thread-16640.html
U must download or allready have a firmware file in fastboot format , Open up SP Flash tool and go to optionsd and select connection, click the w/o battery option and close it. Open your scatter file and than click on download . Insert your phone wile holding your volume down or up , with my device a redmi note 10s it was the up and down to getter for it was flashing the rom. this should flash your device back with a working fastboot and working rom.
Hope u will succeed...
Greetsss
Click to expand...
Click to collapse
Yep, this guy here 's got the point. If you can't flash with sp flash tool because auth fail, there's a method to bypass it.
You can find the tutorial here: https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
I also got some help from this guy's post, many thanks to him too.
https://forum.xda-developers.com/t/...ad_da_fail-0x7d4-2004-for-mtk-phones.3692259/
Let us know how it's going with it! ;D

I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one

Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buytoday there is a lot of devices for gaming like rog phone and red magic
Click to expand...
Click to collapse
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money

Andris85 said:
I can unbrick the device at any time. There is another problem. An incorrect boot file is probably being copied. After TWRP you will never enter android again. But TWRP also only loads up to the subtitle. I tried a lot of methods. Now I will try google p ex. android and make it root.
But, if someone can recommend a device intended for gaming, but easy to root, then I will buy one
Click to expand...
Click to collapse
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/

tutibreaker said:
today there is a lot of devices for gaming like rog phone and red magic, but is you are looking for a "gaming phone" in low or mid-range you are just wasting your money
Click to expand...
Click to collapse
If you can root it easily, then the expensive one is good for me! Normal root was not available for typical gamer phones for years. If I buy something for which root may not be available, then I'm wasting my money...

gurtnyi said:
There's a tutorial, that helped me installing twrp correctly to this phone, I'll link my post about this.
https://forum.xda-developers.com/t/twrp-on-android-12.4522273/
Click to expand...
Click to collapse
I will look today