How to enable camera2Api after September OTA without losing further OTA updates? - Xiaomi Mi A2 / 6X Questions & Answers

My mi A2 is currently running on the September update, the bootloader is locked, it's fresh and clean.
From the Mi A1 Gcam experience, I'm not having that much satisfying results on the default A2 stock camera. On my A1 I used that gcam toolkit for enabling Camera2Api. So the process was pretty clean and hassle free. OTA updates were nice and fine as well.
On my A2 the case is different. So far I haven't found any sort of things like that. Most of the processes include unlocking bootloader and root then magisk. And that'd be the last thing I'd ever try to do.
So is there anyway to get Google camera working on Mi A2 without losing OTA, BOOTLOADER UNLOCK AND ROOT?
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
I've found this link. But I'm not clear about the processes.
Anybody in the community with a kind heart will be generous enough to help me out? That'd be a big help. ?

Search and read read and read ... you need to have knowledge if you want to mess with this phone, and if you are afraid of flashing, then don't do it, if you are lazy, don't do it.
There is no way to enable camera2 without unlocking botloader, and then after enabling camera2, bootloader needs to stay unlocked.
Unlocking bootloader
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
And then, there are two ways of enabling camera2, via twrp, and with magisk install and then uninstall.
Read and learn...
TWRP method
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
Magisk method
https://forum.xda-developers.com/mi-a2/help/how-to-install-ota-magisk-rooted-google-t3846324
Good luck.

minnuss said:
Search and read read and read ... you need to have knowledge if you want to mess with this phone, and if you are afraid of flashing, then don't do it, if you are lazy, don't do it.
There is no way to enable camera2 without unlocking botloader, and then after enabling camera2, bootloader needs to stay unlocked.
Unlocking bootloader
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
And then, there are two ways of enabling camera2, via twrp, and with magisk install and then uninstall.
Read and learn...
TWRP method
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
Magisk method
https://forum.xda-developers.com/mi-a2/help/how-to-install-ota-magisk-rooted-google-t3846324
Good luck.
Click to expand...
Click to collapse
for me it's no problem To stay bootloader unlock but i don't want to root & don't want to lose ota successful installation.

Sohailsamdani said:
for me it's no problem To stay bootloader unlock but i don't want to root & don't want to lose ota successful installation.
Click to expand...
Click to collapse
Use this tool. I used today with September update, camera api enabled and the tool only use temporary root. You have to unlock the bootloader and leave unlocked.
Good luck
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585/page12

Daniesz said:
Use this tool. I used today with September update, camera api enabled and the tool only use temporary root. You have to unlock the bootloader and leave unlocked.
Good luck
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585/page12
Click to expand...
Click to collapse
I don't want to sound silly (sorry if i do) i am on the September update, unlocked bootloader and wanting to enable camera2 api, is it as simple as pressing the corresponding number that enables the unlock or do you have to do something before and after, regards

daveparki said:
I don't want to sound silly (sorry if i do) i am on the September update, unlocked bootloader and wanting to enable camera2 api, is it as simple as pressing the corresponding number that enables the unlock or do you have to do something before and after, regards
Click to expand...
Click to collapse
Sure, just choose the right option and choose the not rooted option

Daniesz said:
Sure, just choose the right option and choose the not rooted option
Click to expand...
Click to collapse
you mean 1st i select Option 1 lock/unlock bootloader then number 7 enable camera 2 api then number 10. exit then reboot my phone. Right?

Sohailsamdani said:
you mean 1st i select Option 1 lock/unlock bootloader then number 7 enable camera 2 api then number 10. exit then reboot my phone. Right?
Click to expand...
Click to collapse
Yes, if your bootloader still locked. Remember, if you unlock your bootloader, you will loose your data, so you have to wait to boot the phone and set it up. And than option 7.
Follow the instructions in the toolkit

If I unlock and relock the bootloader, do I lose my warranty? It's the single most deciding factor for me.

Daniesz said:
Use this tool. I used today with September update, camera api enabled and the tool only use temporary root. You have to unlock the bootloader and leave unlocked.
Good luck
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585/page12
Click to expand...
Click to collapse
Would you please share the processes you've gone through using this tool? ?

I follow the instruction and I installed the Gcam, put with Camera2 api app shows only Level_3, is that normal or I did something wrong.

ali7_has said:
I follow the instruction and I installed the Gcam, put with Camera2 api app shows only Level_3, is that normal or I did something wrong.
Click to expand...
Click to collapse
Lvl 3 is camera2 api enabled :good:

minnuss said:
Search and read read and read ... you need to have knowledge if you want to mess with this phone, and if you are afraid of flashing, then don't do it, if you are lazy, don't do it.
There is no way to enable camera2 without unlocking botloader, and then after enabling camera2, bootloader needs to stay unlocked.
Unlocking bootloader
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
And then, there are two ways of enabling camera2, via twrp, and with magisk install and then uninstall.
Read and learn...
TWRP method
https://forum.xda-developers.com/mi-a2/how-to/tutorial-camera2api-gcam-root-t3842475
Magisk method
https://forum.xda-developers.com/mi-a2/help/how-to-install-ota-magisk-rooted-google-t3846324
Good luck.
Click to expand...
Click to collapse
I tried to go on with the twrp method using that toolkit. Unlocked my bootloader manually. The when I tried to use the toolkit to temporarily get access of twrp and run cmd from computer. When I enter the command adb shell, that showed my devices wasn't found. But when the phone is turned on then that shows my devices there. So I failed to figure out that. And on the other hand it want twrp as well. It was pitch black recovery something.
Secondly when I tried to go with the command 7 to enable camera2Api, it asked to temporarily root. I kept continued with Y. It came up with a note that allow USB debug with the phone will turn on again and make sure to keep phone connected. After that my phone never turned on again :") ♥. It was bricked and I wasn't even able to flash using miflash tool. So I had to go to the repair shop to get my phone fixed.
I wonder why the process is so ugly and annoying on A2 when it was the easiest thing on the A1.
Trust me? I had enough trouble. My wholes night's sleep was gone thinking that I've just got this phone 7 days ago! ?

afridishamsofficial said:
I tried to go on with the twrp method using that toolkit. Unlocked my bootloader manually. The when I tried to use the toolkit to temporarily get access of twrp and run cmd from computer. When I enter the command adb shell, that showed my devices wasn't found. But when the phone is turned on then that shows my devices there. So I failed to figure out that. And on the other hand it want twrp as well. It was pitch black recovery something.
Click to expand...
Click to collapse
With TWRP you have to enter the commands "setprop persist.camera.HAL3.enabled 1" and "setprop persist.camera.eis.enable 1" inside TWRP's terminal on your phone screen.
afridishamsofficial said:
Secondly when I tried to go with the command 7 to enable camera2Api, it asked to temporarily root. I kept continued with Y. It came up with a note that allow USB debug with the phone will turn on again and make sure to keep phone connected. After that my phone never turned on again :") . It was bricked and I wasn't even able to flash using miflash tool. So I had to go to the repair shop to get my phone fixed.
I wonder why the process is so ugly and annoying on A2 when it was the easiest thing on the A1.
Trust me? I had enough trouble. My wholes night's sleep was gone thinking that I've just got this phone 7 days ago!
Click to expand...
Click to collapse
To "unbootloop" your phone, you should enter "fastboot flashing unlock" and "fastboot unlock flashing_critical" (without quotes) in fastboot command line prompt and proceed with MIFLASH tool. Worked twice with me and I'm pretty sure can work for you.
But another advice: the process with Majisk (with the tool -> number 7) doesn't worked with me at all. I tried twice and had to MIFLASH before just bcz of Majisk. So, for a while, I recommend keep a distance from it.

kadu20es said:
With TWRP you have to enter the commands "setprop persist.camera.HAL3.enabled 1" and "setprop persist.camera.eis.enable 1" inside TWRP's terminal on your phone screen.
To "unbootloop" your phone, you should enter "fastboot flashing unlock" and "fastboot unlock flashing_critical" (without quotes) in fastboot command line prompt and proceed with MIFLASH tool. Worked twice with me and I'm pretty sure can work for you.
But another advice: the process with Majisk (with the tool -> number 7) doesn't worked with me at all. I tried twice and had to MIFLASH before just bcz of Majisk. So, for a while, I recommend keep a distance from it.
Click to expand...
Click to collapse
Please correct me if I'm going wrong.
1) unlock my bootloader.
2) put the phone in fastboot and connect to pc while USB debug enabled.
3) open the toolkit and proceed to twrp, only boot but not install method.
4) now I've to come to my phone. On the twrp I've seen an option called terminal. I've to click and enter there.
5) now I've to enter this command on my twrp terminal.
Setprop persist.camera.eis.enable 1
setprop persist.camera.HAL3.enabled 1
6) and then reboot to phone?

kadu20es said:
With TWRP you have to enter the commands "setprop persist.camera.HAL3.enabled 1" and "setprop persist.camera.eis.enable 1" inside TWRP's terminal on your phone screen.
To "unbootloop" your phone, you should enter "fastboot flashing unlock" and "fastboot unlock flashing_critical" (without quotes) in fastboot command line prompt and proceed with MIFLASH tool. Worked twice with me and I'm pretty sure can work for you.
But another advice: the process with Majisk (with the tool -> number 7) doesn't worked with me at all. I tried twice and had to MIFLASH before just bcz of Majisk. So, for a while, I recommend keep a distance from it.
Click to expand...
Click to collapse
i tried with the terminal method. and phone was not booting. It was on bootloop again. Now again stuck with the miflash thing! please help me!!!!

afridishamsofficial said:
Please correct me if I'm going wrong.
1) unlock my bootloader.
2) put the phone in fastboot and connect to pc while USB debug enabled.
3) open the toolkit and proceed to twrp, only boot but not install method.
4) now I've to come to my phone. On the twrp I've seen an option called terminal. I've to click and enter there.
5) now I've to enter this command on my twrp terminal.
Setprop persist.camera.eis.enable 1
setprop persist.camera.HAL3.enabled 1
6) and then reboot to phone?
Click to expand...
Click to collapse
Reboot and test if the camera settings that requires camera2api are working. If they are, I recommend to torn off and go to fastboot mode again and replace the modified boot (TWRP) to the stock one.
So, you setted partition b to TWRP, restore the original boot in place of it.
---------- Post added at 08:51 ---------- Previous post was at 08:11 ----------
afridishamsofficial said:
i tried with the terminal method. and phone was not booting. It was on bootloop again. Now again stuck with the miflash thing! please help me!!!!
Click to expand...
Click to collapse
There are (probably) some files missing with the tool. As you can see in the error message, the required bat to the process is missing. Download the complete tool with its .bat files and try again.

Related

Stuck in bootloop. No custom recovery or unlocked bootloader.

So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
As far as I know the only fix is the one in that link but it does require custom recovery. I'm assuming the fastboot boot command doesn't work when locked but I've never tried, if it does then you could temp boot into twrp. Worth a shot I guess.
Hindsight's 20/20 but NEVER touch anything other than your data or cache partition with a locked bootloader. Google's security jump with lollipop has caused nothing but havoc for us.
ChaosDr0id said:
So this morning I was lazy and tried rooting with the kingroot app, because I didn't want to factory reset. It went okay and I had root but I wanted to use SuperSU as my root manager. Well the binary wouldn't update so I figured i'd unroot from the kingroot app and remove kingroot from my phone, and root the proper way later. I pressed the unroot button and my phone rebooted, but now it's stuck in a bootloop.
I don't have an unlocked bootloader or a custom recovery, and I never checked the enable oem unlock in developer options so flashing stock isn't an option.
I tried sideloading the OTA for the build I was on, but I guess kingroot didn't actually unroot me, because it told me I needed to reflash.
I tried factory reset and wiping the cache in the stock recovery, and tried 'fastboot format userdata' and 'fastboot format cache' but that didn't work either.
The only thing I could find that might help is this post http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
but since I don't think you can run adb commands in stock recovery or bootloader this won't work.
So is there any way to fix this or am I boned?
Click to expand...
Click to collapse
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
or, you can grab the factory image of whatever version of android that you were on, "unzip" it, grab the system.img, and flash it via fastboot. its the same thing as if was a "custom recovery", youre just reflashing the rom, and wont lose your data
first thing id do is flash a custom recovery and unlock my bootloader, and make a backup in recovery.
AlkaliV2 said:
If you already installed the drivers and know how to run fastboot commands skip to step 4. Otherwise, start at the beginning
1.) Install the Wugfresh Toolkit from here: http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 so that the drivers you need get installed along with fastboot and adb commands.
2.) Open Nexus Root Toolkit after it has finished installing. Under advanced utilities click "Launch" then choose launch command prompt for manual mode.
3.) Put your device in bootloader mode (pwr+vol down) and connect it to the computer. Type: "adb devices" into the command prompt and it should list a device serial number. If it does, go to step 4. If it doesn't, unplug the phone and plug it back in and re-run command.
4.) Then run the command "fastboot oem device-info" and tell us what the output is.
Hopefully when you rooted it, it unlocked your bootloader automatically. If you successfully rooted and rebooted it should technically be unlocked. We won't know until you run fastboot oem device-info
Click to expand...
Click to collapse
Hi, thanks for the reply.
It says
'device info' is not a supported oem command. See fastboot oem help.
FAILED <remote failure>
However I'm fairly certain the bootloader is still locked as I was unable to flash TWRP, or a stock image of android, as it tells me to unlock before doing those things.
AFAIK when you have this problem together with a stock recovery and a locked bootloader means bricked. >repair
Your bootloader is lock and you can't boot android to enable OEM unlock to unlock it. You have ruined your phone and there is no known fix.
RMA time for you.
Literally no solution unless you can invent one on your own.
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
yes
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc?
Click to expand...
Click to collapse
Absolutely. Otherwise anybody with a notebook could swipe your phone, download everything you've got on it, then return it without you knowing, and that would mean more nekkid selfies on reddit.
CapitalParallax said:
Is it necessary to have your bootloader unlocked to boot into a custom recovery from your pc? Say you download twrp on your pc, would fastboot boot twrp.img be a work around for that?
Click to expand...
Click to collapse
The entire concept of a locked bootloader is that you can't flash images through it.

How to Unlock Bootloader, Flash TWRP, and ROOT LG G4 H811 T-Mobile.

Now, I know this tutorial exists all over the place, like one-click and UnjustifiedDev tutorial but none seemed to work. I am sharing the steps and method I used IN-DEPTH command for command on how to unlock, flash, and root the LG G4 from Tmobile.
NOTE THIS WILL FACTORY RESET YOUR DEVICE SO BACKUP ALL YOUR DATA
1. Activate developer settings by entering the about section and tapping build number 7 times.
2. Enter your developer settings and MAKE sure you have 'Allow OEM unlock' and 'USB Debugging' enabled.
3. Download the latest SuperSU zip and move it onto your SD card.
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
5. Once the Command window is linked to the folder, connect your device via USB and allow the connection.
6. On the command window type 'adb reboot bootloader' and the device should reboot with the fastboot options on the upper left of the phone screen
7. Once again on the command window type 'fastboot oem unlock' and the command window should say OKAY and complete the action.
8. To Confirm that the device is unlocked type 'fastboot getvar unlock' and the window should respond with 'Unlock: YES'
9. Now download the latest available TWRP and drop it into the platform-tools folder where your ADB.exe is located.
10. On your Command Window type 'fastboot flash recovery "NAME OF TWRP FILE" if you get the error ' cannot load 'twrp-X.X.X.X-h811' you need to add .img to the end of the filename
11. Once the process completes you will see 'target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 1.088s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time:'
THE FAILED UNKNOWN COMMAND NOTICE CAN BE IGNORED
12. Once the process completes the device may not let you enter recovery from the traditional method using the buttons on the back of the phone so the easiest method is to, on your command window, type
'fastboot boot twrp-2.8.7.0-h811.img' and the device should respond within just a few seconds and reboot into TWRP.
13. Once the device reboots, enter twrp and tap on install and locate the SuperSU.zip and allow it to install.
14. Once the process completes successfully, wipe cache to be safe and reboot your device.
15. Resetup your device and restore your data if necessary and install a root checker from Google Play to confirm root!
THATS IT GUYS! This took me a long time to figure this out and it's a combination of different methods to get it to work!
All credit goes to the Devs of TWRP and SuperSU!
I posted in General because I'm a new user so please move to appropriate forums! thanks!
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Please refer to the first line of my post. I understand that there are a large series of posts about how to do this but this is the only one that works for me even with me running android M.
Shows how to install TWRP for devices on 6.0
marcviado said:
This thread should be closed as theres already a proper one on here..http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Its more of people really dont like to search and read things
Click to expand...
Click to collapse
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
marcviado said:
Uhm..like i said nobody likes to read now a days lol. If you look closely the guide i linked shows you how to unlock bootloader,flash twrp,root,downgrade,and have all the files you need.
Click to expand...
Click to collapse
It is totally there... I looked at that guide for a really long time too. I concede.
joeyicecream said:
The guide you linked does not show how to unlock the bootloader or install TWRP to allow the install of SU for users that are already on Marshmallow. The other guide would have been perfect if I already had bootloader unlocked and SU installed.
Click to expand...
Click to collapse
Yes it does. You do not need to use any codes, just enable oem unlocking in dev settings and type fastboot oem unlock and it will be unlocked.
Can't get twrp installed
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
I have the G4 LGUS991 gotta can I tell if it's h811?
4. Using the android issue SDK. Open a command window and link it to your SDK folder where ADB is located (typically Platform-Tools)
Click to expand...
Click to collapse
What if your device could not be found despite having the latest LG drivers?
mr_blonde55 said:
Thanks for the step by step directions. I'm having trouble restarting my H811 after I've flashed TWRP. My device doesn't respond to the button method of entering recovery and 'fastboot boot twrp-2.8.7.0-h811.img' command doesn't do anything. My device is 20i and I've unlocked the bootloader. Any ideas? Seems like I've tried everything and can't get TWRP to install. Any help would be great...thanks
Click to expand...
Click to collapse
Can't remember which thread, but I ran into the same problem you have and solved it by using an additional command like fastboot erase userdata. If you google it, you'll see the commands I mean. Basically, I had to factory reset the device through fastboot first (it sits there for several minutes to do this) before installing/booting twrp. And yes, the log will show that the process was successful, not a failure as mentioned by OP. Once I did that, I booted in twrp and flashed the rom zip without any trouble.
So, you guys mean we have Marshmallow on T mobile G4, I didn't get it yet.
Please somebody give me a link to the OTA or update.zip for MM of LG G4
This one worked for me!
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Sent from my LG-H811 using XDA-Developers mobile app
NardVa said:
If you are already on Marshmallow, can't you do the 'fastboot oem unluck' with ADB and install SuperSU through the play store to get root? The part for TWRP would only give you the ablity to flash other roms.
Edit: Nevemind I'm wrong. You need TWRP to install SuperSU which roots the phone. SuperSU in the Play Store will only grant root acess to your apps.
Click to expand...
Click to collapse
Could you help me with is or point me in the right direction ? Please & thanks
Sent from my LG-H811 using XDA Labs
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
Majestyk007 said:
This is the only guide that worked for me.
I unlocked bootloader using adb, no problems...
I tried to flash TWPR with fastboot but kept getting errors. Booting into recovery got a dead android minion and red triangle with ! I ran this stupid recovery a dozen times and read a dozen threads with no obvious answers.
This guide says "ignore the error" and run fastboot boot twrp-2.8.7.1-h811.img which immediately opened TWRP and allowed SuperSU-2.71.zip to be flashed.
The part most guides are missing is the fastboot boot twrp-2.8.7.1-h811.img, so my thanks go here. Some other guides are so difficult to read and follow.
Thanks OP !
Yes, MM Android 6.0 went OTA for T-Mobile a month or so ago...
Click to expand...
Click to collapse
I keep getting this problem.
Sent from my LG-H811 using XDA Labs
I've just got a H811 and it automatically updated to Android 6 when I loaded it up. I will be giving this guide a go this evening. Many of the other links on the web are for lollipop and were released when the phone came out, so I'm thankful that this seems straight forward. http://uslugi.nie-spamuj.eu/rtv,1,0.html Hoping that it goes that way.
How to lock bootloader or hide status: bootloader state: unlocked?
Sr for my English!
So I followed this guide and I appear to be soft bricked at best and hard bricked at worst. I did read the other guide linked in the second response and I found a major difference that might be my problem. So in the guide linked in the second response it doesn't say to even try flashing TWRP from fastboot. It says to just boot from it then install it from within TWRP. I followed the steps verbatim and my phone is currently stuck at the T-Mobile splash screen. Any suggestions? I have tried to boot into recovery by holding down and the power and releasing the power for a second when the logo comes up. I get into the Factory data reset screen and select Yes twice then the green guy shows up and the phone resets but stays at the T-Mobile splash screen. I don't have ADB or fastboot with the phone in this state.
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
rmdeathwish said:
hi Guys,
So i just wanted to make sure and present my ask -
So, currently twrp flashing and obtaining root is still buggy for those who have android 6.0 preinstalled? Is this a correct assumption?
Also, my ask - I dont want root but i would like a custom recovery so that I may flash custom fonts. My work email (Good for Enterprise) is very much needed (although i hate it to the core).
Can someone please answer me / correct if I mentioned something wrong?
Thanks
Click to expand...
Click to collapse
It's not buggy at all. All the tedium has already been bypassed if you already have Marshmallow installed.
Follow autoprime's original guide, steps 2, 4, 5, 6, and 8 under the Bootloader OEM Unlock + Root section. I would recommend a more up-to-date version of TWRP than 2.8.7.1 though. Go to TWRP's download site for the latest version.

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?

Mi Mix fresh out of the box - How do I get Resurection Remix on it?

Hi Community,
I'm a little bit "scared" to ask for the following, but I have read a lot about it and I'm just getting more confused, so I hope someone can bring clarity.
Situation looks like this: I will unpack my Mi Mix 256gb EU-version this evening and I want to put Resurection Remix on it. Now, what steps do I need to follow to get this done? I know the steps of each process is written in the related post, but how does it play together?
I understood that I need TWRP (to add and remove roms, right?) and then install the rom on top of it. Also, is it then rooted? flashed? unlocked? If I would want the original software on it again, is it possible to install it without leaving marks of the rom?
What confuses me also is, that I somehow have to unlock something through the xiaomi page and wait a few days?
Thank you in advance and best regards from Switzerland!
Everything you need to know is in this thread: https://forum.xda-developers.com/mi-mix/how-to/guide-flash-global-china-rom-root-gapps-t3510592
Dont forget to decrypt your phone after you unlock your bootloader.
First you have to unlock your bootloader in order to flash recovery or fastboot rom. I will add all the links you need in order , so that you can access them fast and without problems.
For unlocking your bootloader first login into your Mi Account on your Mix , after this is done , go to unlock site (en.miui.com/unlock) and apply for unlock permissions ( Remember to use the same account you logged into your device if not you won´t be able to unlock it).Remember too to enable Developer Settings and allow Usb Debugging.
Afer this is done download and find this on google (xda adb drivers) and if you have windows its super -easy to set it up ( Remember to execute the batch file with admin privileges)
Once this is done if you still have adb problems just google and install universal adb driver, I will give you all the links at the end.
After all this and you have received approbation from Xiaomi to unlock and got the code , just plug-in your phone to your computer and enter fastboot mode ( Volume down+power buttons at the same time).
Open Mi Unlock program and enter the same account you used for unlock permissions and your device. After this is done wait for the unlock process to finish and click reboot.
Once you have rebooted your device download twrp , put it into adb folder (C://Adb) and with your device plugged-in type next : adb fastboot flash recovery twrp.img (or the name of your twrp.img , or just change it to twrp).
If you followed all the steps you should have twrp working and ready to flash any rom without problems. If you need more help just answer or send pm . Good luck and happy flashing.
1-http://en.miui.com/unlock/
2-https://forum.xda-developers.com/showthread.php?t=2588979
3-https://adb.clockworkmod.com/
4-https://www.androidfilehost.com/?fid=529152257862692530
YazumiWuHung said:
First you have to unlock your bootloader in order to flash recovery or fastboot rom. I will add all the links you need in order , so that you can access them fast and without problems.
For unlocking your bootloader first login into your Mi Account on your Mix , after this is done , go to unlock site (en.miui.com/unlock) and apply for unlock permissions ( Remember to use the same account you logged into your device if not you won´t be able to unlock it).Remember too to enable Developer Settings and allow Usb Debugging.
Afer this is done download and find this on google (xda adb drivers) and if you have windows its super -easy to set it up ( Remember to execute the batch file with admin privileges)
Once this is done if you still have adb problems just google and install universal adb driver, I will give you all the links at the end.
After all this and you have received approbation from Xiaomi to unlock and got the code , just plug-in your phone to your computer and enter fastboot mode ( Volume down+power buttons at the same time).
Open Mi Unlock program and enter the same account you used for unlock permissions and your device. After this is done wait for the unlock process to finish and click reboot.
Once you have rebooted your device download twrp , put it into adb folder (C://Adb) and with your device plugged-in type next : adb fastboot flash recovery twrp.img (or the name of your twrp.img , or just change it to twrp).
If you followed all the steps you should have twrp working and ready to flash any rom without problems. If you need more help just answer or send pm . Good luck and happy flashing.
1-http://en.miui.com/unlock/
2-https://forum.xda-developers.com/showthread.php?t=2588979
3-https://adb.clockworkmod.com/
4-https://www.androidfilehost.com/?fid=529152257862692530
Click to expand...
Click to collapse
Hey Thanks for the quick reply. I think this will help alot. So far I'm stuck at the first stage :silly: Did not receive an SMS even after 10 minutes. With the second click I received it but my IP is now blocked. Starts good
I can't even get it to reboot into recovery, it now freezes at the screen that prompts you to go to pcsuite!
i killed tupac said:
I can't even get it to reboot into recovery, it now freezes at the screen that prompts you to go to pcsuite!
Click to expand...
Click to collapse
Do you mean fastboot, have you installed a recovery? We don't know how far you have got. Power and vol- for fastboot. When mi logo appears let go of power button but keep vol- pressed till you see fastboot screen.
jazz452 said:
Do you mean fastboot, have you installed a recovery? We don't know how far you have got. Power and vol- for fastboot. When mi logo appears let go of power button but keep vol- pressed till you see fastboot screen.
Click to expand...
Click to collapse
doesn't work, I had to go this route:
http://en.miui.com/thread-500625-1-1.html
and to threadstarter: if you are not in China, you don't have to do the unlock request. If you're on EU rom already, you're unlocked. Just use the thread I posted, it is much, much easier.
You have to use the version in the thread I linked (official MIUI forum) or you'll get a TWRP where the touchscreen doesn't work and you can't confirm
i killed tupac said:
doesn't work, I had to go this route:
http://en.miui.com/thread-500625-1-1.html
and to threadstarter: if you are not in China, you don't have to do the unlock request. If you're on EU rom already, you're unlocked. Just use the thread I posted, it is much, much easier.
You have to use the version in the thread I linked (official MIUI forum) or you'll get a TWRP where the touchscreen doesn't work and you can't confirm
Click to expand...
Click to collapse
Things have changed, most people did this a year ago when there was no EU ROM, just China ROM and vendor ROM, most came with bootloader unlocked, which is the first thing you should of checked. The fact you have EU ROM would normally mean that bootloader has been unlocked but sometimes they re-lock the device.
jazz452 said:
Things have changed, most people did this a year ago when there was no EU ROM, just China ROM and vendor ROM, most came with bootloader unlocked, which is the first thing you should of checked. The fact you have EU ROM would normally mean that bootloader has been unlocked but sometimes they re-lock the device.
Click to expand...
Click to collapse
fwiw, I flashed the EU rom first
jazz452 said:
Things have changed, most people did this a year ago when there was no EU ROM, just China ROM and vendor ROM, most came with bootloader unlocked, which is the first thing you should of checked. The fact you have EU ROM would normally mean that bootloader has been unlocked but sometimes they re-lock the device.
Click to expand...
Click to collapse
Yeah... so that's what I meant. Even more confused now. My phone is definitely locked (checked with bootloader) and after I tried to apply again after 24 hours the weird chinese message pops up again and the application fails.
i killed tupac said:
fwiw, I flashed the EU rom first
Click to expand...
Click to collapse
Did you check using fastboot if your already unlocked,
fastboot OEM device-info
Assuming you have your pc set up which is the guides section.
Sorka_1 said:
Yeah... so that's what I meant. Even more confused now. My phone is definitely locked (checked with bootloader) and after I tried to apply again after 24 hours the weird chinese message pops up again and the application fails.
Click to expand...
Click to collapse
It worked today after trying it from a friend's computer. I also got the permission already.
Sorka_1 said:
It worked today after trying it from a friend's computer. I also got the permission already.
Click to expand...
Click to collapse
So now I'm getting this message in the unlock-programm when it finishes:
"Couldn't unlock - After 59 hours of trying to unlock the device"
What does that mean?
Sorka_1 said:
So now I'm getting this message in the unlock-programm when it finishes:
"Couldn't unlock - After 59 hours of trying to unlock the device"
What does that mean?
Click to expand...
Click to collapse
Are you still using your friends computer, maybe you are still blocked on your own. O and real friends aren't allowed on XDA.?
jazz452 said:
Did you check using fastboot if your already unlocked,
fastboot OEM device-info
Assuming you have your pc set up which is the guides section.
Click to expand...
Click to collapse
yeah, but the phone it totally ****ed now, not even sure what happened. I used XiaoMiTool and it hasn't worked right since.
i killed tupac said:
yeah, but the phone it totally ****ed now, not even sure what happened. I used XiaoMiTool and it hasn't worked right since.
Click to expand...
Click to collapse
Factory reset? It can't be broken, careful you don't kill it completely. Did you use the correct tool from miui.eu?
http://en.miui.com/thread-471497-1-1.html
I'm running viper ROM and I love it.
Sent from my MI MIX using Tapatalk
Lithium-Fusion said:
A bit of irrelevant with the thread, isn't it? [emoji1]
Click to expand...
Click to collapse
Yup sure is, sorry for offending you!
Sent from my MI MIX using Tapatalk
Sorka_1 said:
So now I'm getting this message in the unlock-programm when it finishes:
"Couldn't unlock - After 59 hours of trying to unlock the device"
What does that mean?
Click to expand...
Click to collapse
Just a quick follow up:
I waited 59 hours and now I could successfully unlock the phone. Will proceed now with TWRP. Yey.

How To Guide Master Guide to Unlock Bootloader/Flash TWRP/Root Device/Flash EU ROM/Pass SafetyNet

Hi All, as this device is fairly new and there is not much clarity on things so, I decided to create a master guide as you see below. I am also attaching a PDF version of this guide as I have not formatted this XDA post to what I feel it should be like. You may download and follow that, I will keep updating things as I find.
Lets start​
1. Unlock Bootloader​1.1 Apply for Bootloader Unlock​
Enable developer settings
Go to Settings>About phone/My device> All specs> Hit MIUI Version 8 times
Access Developer Settings from Settings>Additional Settings
Enable OEM Unlocking option
Now login to your desired Mi Account that you wish it to be associated with your device (Mi account should have a mobile number registered for OTP and verification sometime asked by MI flash unlock tool)
Your unlock bootloader wait time starts now. Wait for 7 days (168 hours from the time you added MI account) to unlock bootloader
1.2 Unlocking Bootloader​So you have crossed the wait period…. Now follow below to unlock assuming you have all the USB drivers for Mi devices (usually auto installed when you connect mobile)
Warning: All your userdata (including pictures and files) will be wiped out
Download official Mi flash unlock tool from this link: https://miuirom.xiaomi.com/rom/u1106245679/5.5.224.24/miflash_unlock-en-5.5.224.24.zip
Boot into Booloader: Power off your mobile then hold Volume Down + Power Button till fastboot bunny pops up
Open Mi Flash unlock tool downloaded in step 1
Sign in with same account that you used to sign in in Developer Settings in step 1.1.d. It may ask to verify your account with OTP. do it.
Click Unlock on the tool.
Your device will be unlocked and rebooted. Wait till reboot.
Congrats… you have an unlocked mobile device now
Now let’s go to Rooting your device for which we will have to flash TWRP to Mobile
2 TWRP Flash and Rooting​2.1 TWRP Flash​
Download and Install Minimal ADB and Fastboot for windows for this link: https://androiddatahost.com/wp-content/uploads/Minimal_ADB_Fastboot_v1.4.3.zip
Download unofficial TWRP (only one available as of writing this guide) from here: https://sourceforge.net/projects/xi....6.0_11-0_LOCAL-20220203-01-vili.img/download and rename it to twrp.img
Also download Magisk from below link: https://github.com/topjohnwu/Magisk/releases/download/v24.0/Magisk-v24.0.apk we will use it next section for rooting.
Rename the downloaded magisk file from magisk.apk to magisk.zip and copy it to your device’s storage
Copy the above twrp.img file to Minimal ADB and Fastboot folder (not necessary if you know some directory navigation using command prompt)
Boot mobile into bootloader (follow 1.2.b)
From your Minimal ADB and Fastboot folder open Cmd here.exe file to access the ADB tool
Connect your device to PC
Verify if device has connected successfully using the command below
Fastboot devices
This should return your device id
Now boot into TWRP using below commands
Fastboot boot “twrp.img” if you pasted twrp.img in minimal adb and fastboot folder
Fastboot boot “path to twrp.img” if you did not move it to the minimal adb and fastboot folder
Let the device boot to TWRP
In above step we just booted by TWRP which is temporary. Now let’s flash it to make it permanent:
Go to Advanced settings in TWRP and click Flash Current TWRP
Reboot to TWRP
2.2 TWRP Backup of Current Rom​
You should have a working TWRP
Boot to TWRP and navigate to Backup section
Select all partitions and swipe to confirm
If you see error in backing up, uncheck Data and EFS partition backup
The backup should complete successfully
Have this backup copied to a PC for emergency wipout of your mobile
2.3 Rooting/Flashing Magisk​
Go to Install in TWRP and select magisk.zip you copied in step 2.1.d
This will flash magisk and root your device. Now reboot to system from recovery
Once you have the device booted, rename the magisk.zip to magisk.apk again and install the magisk app on device
You may update if you see any updates to magisk or app
2.4 Passing Safetynet​
Download this magisk module zip from here: https://drive.google.com/file/d/1QJHPpL4R8fcxjB35XbcpaCOipKzpvL2I/view?usp=sharing
Go to magisk app settings and enable Zygisk (beta) also enable Enforce Deny List
Select Hide the Magisk app and give any desired name for Magisk to hide its identity
Now go to modules page in Magisk app.
Select Install from source/storage option and chose the downloaded safteynet zip
Reboot
This will pass safetynet but still Indian bank apps won’t work. Keep following below for clear
Go to magisk settings and enter Configure DenyList
Add all the apps you want to hide magisk and root from (such as phonepe, Gpay)
Don’t leave any service from the selected apps unchecked
3. Flash EU Rom​Warning: All your userdata (including pictures and files) will be wiped out
A TWRP backup of current rom is recommended before following the next steps
You can see section 2.2 for the instruction on backup
Download Fastboot EU rom from here: https://androidfilehost.com/?fid=17825722713688263895
Extract all the contents in zip file to any normal folder
We will be using Bootloader/Fastboot mode. Boot into Bootloader: Power off your mobile then hold Volume Down + Power Button till Fastboot bunny pops up
Connect your device to PC
From the extracted folder Open windows_fastboot_first_install_with_data_format.bat(for windows).
You may execute appropriate similar named file if you are running Linux or MacOS
The EU rom flashing process will start. Hit “Y” on keyboard to accept Formatting
Wait patiently while the PC does its Job.
You may see a long pause post “writing Cust” command depending on PC configuration. You should wait for 5 minutes at least, then try hitting any letter key on your keyboard, the process continues this way.
You may hit letter key whenever you see unusual pauses during pushing of super partition file sparse sending 1 of 9 to 9 of 9
Wait till process finishes and reboots
For TWRP and Rooting you can follow the same guide in section 2.
Updating to Miui13/Android 12 EU Rom​
Check out this guide to Update to Android 12
Happy Rooting… Njoy your device.
Lastly.. All the credit goes to respective owners, I have just compiled everything together and in an easy manner. PM me for credits.
Do let me know if you have any suggestions and corrections.
Thanks & Regards,
Abdus Saboor Asad
Reserved
Reserved
Much appreciated, good overview.
Will try when I get my bootloader unlocked.
Rammetje.b said:
Much appreciated, good overview.
Will try when I get my bootloader unlocked.
Click to expand...
Click to collapse
You are welcome.
sasaboor64 said:
You are welcome.
Click to expand...
Click to collapse
Quick question if you allow me.
The unlock boot loader timer starts ticking even without hooking the phone up to the mi unlock tool? Just the dev options, OEM unlock and login to mi account is sufficient?
I remember I messed around with this when I tried to unlock my Poco F1 at the time.
Thanks
Bram
Rammetje.b said:
Quick question if you allow me.
The unlock boot loader timer starts ticking even without hooking the phone up to the mi unlock tool? Just the dev options, OEM unlock and login to mi account is sufficient?
I remember I messed around with this when I tried to unlock my Poco F1 at the time.
Thanks
Bram
Click to expand...
Click to collapse
Good question... I think we should hook once, that's how I unlocked. But I feel it should work without hooking as well.
Anyone should test it and update for us the other way.
When i download the TWRP and boot into TWRP (through fastboot boot "twrp.img"), my touch screen will not work anymore. How could i fix this?
working on miui 13 android 12?
paulboqs said:
working on miui 13 android 12?
Click to expand...
Click to collapse
you may go through the last thread in my post for miui 13 related rooting. this guide is for miui12 rooting and there is no TWRP yet for miui13 for our device
at what point exactly will all my data be wiped?
yuukiw said:
at what point exactly will all my data be wiped?
Click to expand...
Click to collapse
the moment u hit unlock after your waiting period...
sasaboor64 said:
the moment u hit unlock after your waiting period...
Click to expand...
Click to collapse
is there a way to back upp all apps + data?
MIUI13 Android12 How to enter bootloader?
I'm try but FASTBOOT "orange" Showing?
how to enter bootloader? any driver or any solution?
m38d1 said:
MIUI13 Android12 How to enter bootloader?
I'm try but FASTBOOT "orange" Showing?
how to enter bootloader? any driver or any solution?
Click to expand...
Click to collapse
Please make sure you are having latest ADB installed on your machine. The best option is to install Android Studio . Secondly make sure to enable USB debugging .
You can reboot to fastboot through adb commands.
Once you are connected to ADB enter the command below.
ADB reboot Bootloader.
This will reboot to fastboot mode.
Fastboot devices
The above command shows whether you are on fastboot or not.
Now open the unlock tool and unlock your bootloader. Else if you are confident in recovering your device. use the command below
Fastboot flashing unlock
Hope the above helps.
AwkwarddWhale said:
When i download the TWRP and boot into TWRP (through fastboot boot "twrp.img"), my touch screen will not work anymore. How could i fix this?
Click to expand...
Click to collapse
did you found a solution?
this is the first time this happen to me since mi3, RHnote5,7, pocox3nfc, mi11tpro.
tactil isn't working as soon i ented the twrp.. and theres no orange fox for this devices.. shame.
Jctatis said:
did you found a solution?
this is the first time this happen to me since mi3, RHnote5,7, pocox3nfc, mi11tpro.
tactil isn't working as soon i ented the twrp.. and theres no orange fox for this devices.. shame.
Click to expand...
Click to collapse
There is no solution, there is no twrp for Android 12 / MIUI13 yet.
Well I did manage to make it work using a mouse otg. But it useless since theres no storage to flash
mm_rajesh said:
Please make sure you are having latest ADB installed on your machine. The best option is to install Android Studio . Secondly make sure to enable USB debugging .
You can reboot to fastboot through adb commands.
Once you are connected to ADB enter the command below.
ADB reboot Bootloader.
This will reboot to fastboot mode.
Fastboot devices
The above command shows whether you are on fastboot or not.
Now open the unlock tool and unlock your bootloader. Else if you are confident in recovering your device. use the command below
Fastboot flashing unlock
Hope the above helps.
Click to expand...
Click to collapse
thanks
The problem was the phone cable
This TWRP from the first post is Android 12 too?

Categories

Resources