Enabling Camera2 API and HDR+ On MI A1 - Xiaomi Mi A1 Questions & Answers

I noticed there are plenty of modified Google Camera apks that should work on the MI A1 since it has a Snapdragon processor. However they all crash because I don't have the Camera2 API enabled.
Does anyone know how to edit the build prop through ADB without root and tried to use HDR+ on this device?

I have the sama question. Can someone answer?

impossible without root, only possible if xiaomi does it in the stock ROM in future.. use feedback app to tell Xiaomi to do so.

It is possible with root add persist.camera.HAL3.enabled=1 in your buildprop under camera section..it is not possible without root
Hit thanks if i helped

ALISTON PRINCE FERNANDEZ said:
It is possible with root add persist.camera.HAL3.enabled=1 in your buildprop under camera section..it is not possible without root
Hit thanks if i helped
Click to expand...
Click to collapse
With adb?

Aman301582 said:
With adb?
Click to expand...
Click to collapse
No,,you must be rooted first

Camera2api without root
Yes you can enable camera2api without root. Do all the steps following -
1. Download twrp bootloader for Mi A1
2. Connect your phone with pc & open adb shell in PC
3. Boot your phone in fastboot by long press vol down+power
4.1. Unlock bootloader "fastboot oem unlock"
4.2. Run "fastboot boot twrpfile.img"
5. It will boot twrp bootloader without flash in your phone.
6. Go to advance in twrp & select shell
7. Run "vi system/system/build.prop"
8. Press 'i' for insert mode & then type "persist.camera.HAL3.enabled=1"
9. Press 'esc' to exit insert mode.
10. You are done. Now type "adb reboot" from your pc.
11. Next if you want you can relock bootloader by go to fastboot mode & type " fastboot oem lock"
---------- Post added at 05:13 PM ---------- Previous post was at 05:04 PM ----------
Sorry to add how to save file in vi editor.
After inserting the line & press ' esc' of step 9, press ":wq" and "enter".
(Make sure you add : and 'w' stands for write & 'q' stands for quit.)

Camera2api without root contd..
After step 9 i.e. exit from vi editor make sure you change the build.prop file with 644 permission. To do so type " chmod 644 /system/system/build.prop" in twrp shell.

Cybertronworld said:
Yes you can enable camera2api without root. Do all the steps following -
1. Download twrp bootloader for Mi A1
2. Connect your phone with pc & open adb shell in PC
3. Boot your phone in fastboot by long press vol down+power
4.1. Unlock bootloader "fastboot oem unlock"
4.2. Run "fastboot boot twrpfile.img"
5. It will boot twrp bootloader without flash in your phone.
6. Go to advance in twrp & select shell
7. Run "vi system/system/build.prop"
8. Press 'i' for insert mode & then type "persist.camera.HAL3.enabled=1"
9. Press 'esc' to exit insert mode.
10. You are done. Now type "adb reboot" from your pc.
11. Next if you want you can relock bootloader by go to fastboot mode & type " fastboot oem lock"
---------- Post added at 05:13 PM ---------- Previous post was at 05:04 PM ----------
Sorry to add how to save file in vi editor.
After inserting the line & press ' esc' of step 9, press ":wq" and "enter".
(Make sure you add : and 'w' stands for write & 'q' stands for quit.)
Click to expand...
Click to collapse
Hi!
Can you post the links to twrp boot loader, and more details about 4.2. Run "fastboot boot twrpfile.img" ??
Another intersting thing.... mi A1 have a option called Desbloqueo OEM (oem unlook) on developer options!!!
Thanks in advance!

Cybertronworld said:
Yes you can enable camera2api without root. Do all the steps following -
1. Download twrp bootloader for Mi A1
2. Connect your phone with pc & open adb shell in PC
3. Boot your phone in fastboot by long press vol down+power
4.1. Unlock bootloader "fastboot oem unlock"
4.2. Run "fastboot boot twrpfile.img"
5. It will boot twrp bootloader without flash in your phone.
6. Go to advance in twrp & select shell
7. Run "vi system/system/build.prop"
8. Press 'i' for insert mode & then type "persist.camera.HAL3.enabled=1"
9. Press 'esc' to exit insert mode.
10. You are done. Now type "adb reboot" from your pc.
11. Next if you want you can relock bootloader by go to fastboot mode & type " fastboot oem lock"
---------- Post added at 05:13 PM ---------- Previous post was at 05:04 PM ----------
Sorry to add how to save file in vi editor.
After inserting the line & press ' esc' of step 9, press ":wq" and "enter".
(Make sure you add : and 'w' stands for write & 'q' stands for quit.)
Click to expand...
Click to collapse
This will affect any OTA in future? Its this procedure safe?
thanks

nitroax said:
This will affect any OTA in future? Its this procedure safe?
thanks
Click to expand...
Click to collapse
It breaks OTA. I don't think you need these steps anymore, as far as I know latest build works fine without forcing these prop files... in any case im working on a magisk module that you can load and it adds these prop lines to the build.prop without breaking SafteyNet or system folder

TWRP Bootloader
noctambul said:
Hi!
Can you post the links to twrp boot loader, and more details about 4.2. Run "fastboot boot twrpfile.img" ??
Another intersting thing.... mi A1 have a option called Desbloqueo OEM (oem unlook) on developer options!!!
Thanks in advance!
Click to expand...
Click to collapse
Here is the link for the official twrp file
https://drive.google.com/open?id=13eaSFZM7vdDhPCd9UG6x4A5qSCrZ5bO9
So the command would be "fastboot boot recovery.img"
And I have already disscussed about OEM unlocking & relocking.

sooti said:
It breaks OTA. I don't think you need these steps anymore, as far as I know latest build works fine without forcing these prop files... in any case im working on a magisk module that you can load and it adds these prop lines to the build.prop without breaking SafteyNet or system folder
Click to expand...
Click to collapse
Which build? thank you

nitroax said:
Which build? thank you
Click to expand...
Click to collapse
The latest one, the one on the oneplus 3 forums, gcam

sooti said:
The latest one, the one on the oneplus 3 forums, gcam
Click to expand...
Click to collapse
Just to be clear, you're saying the latest gCam build works without rooting or modifying build.prop? How does it activate camera2 API?
Also, request you to link to the particular build. With developers adding new builds so frequently, it is difficult to know for sure that the latest one is not already replaced by an even more updated one.
Have been waiting to use the gCam port but didn't want to root to ensure update OTAs are not broken. Didn't want to choose either better camera or better software support if I could have both. Thanks, look forward to your answer.

deepesh_p said:
Just to be clear, you're saying the latest gCam build works without rooting or modifying build.prop? How does it activate camera2 API?
Also, request you to link to the particular build. With developers adding new builds so frequently, it is difficult to know for sure that the latest one is not already replaced by an even more updated one.
Have been waiting to use the gCam port but didn't want to root to ensure update OTAs are not broken. Didn't want to choose either better camera or better software support if I could have both. Thanks, look forward to your answer.
Click to expand...
Click to collapse
Here you go
https://forum.xda-developers.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552
Just use the latest one

sooti said:
Here you go
https://forum.xda-developers.com/oneplus-3/how-to/modded-google-camera-hdr-60fps-video-t3658552
Just use the latest one
Click to expand...
Click to collapse
Tried installing the latest one (GCam5.1.014-Arnova8G2-v11-N). It installed but crashed on opening.
Did I miss something?

deepesh_p said:
Tried installing the latest one (GCam5.1.014-Arnova8G2-v11-N). It installed but crashed on opening.
Did I miss something?
Click to expand...
Click to collapse
Did you enable camera2api?

valkyrjur said:
Did you enable camera2api?
Click to expand...
Click to collapse
How does one do that without root? @sooti mentioned there's no need to make the build.prop edits as it breaks OTAs and that the latest build of gCam works without altering the build.prop.
I'm confused. Is there a way of using gCam without root or breaking OTA updates, or not?

I've found one tip on 4pda forum, google translation (someone who speaks Russian could probably confirm):
To work with HDR mode in the camera application from Xiaomi after activating the camera api 2, you need to observe an extremely simple algorithm,
before activating camera api 2 in build.prop, the camera application should not be started . After a reboot, everything works fine.
--
Для работы HDR режима в приложении камера от Xiaomi после активации camera api 2 нужно соблюсти предельно простой алгоритм,
до активации camera api 2 в build.prop приложение камеры не должно запускаться. После перезагрузки все отлично работает
--
What I did - installed magisk, installed module to enable camera api 2, rebooted phone at least 2 times and started gcam -> it worked. Then I tried stock camera and to my surprise HDR is fully working as well. I can switch between cameras and use all features without any issues whatsoever.
Without camera api 2, none of the gcam version which I tried worked, all crashed immediately.

Related

"Friendly" root method for lg k8 and k10 [MTK]

This guide is supposed to help you root your lg k8 (2016) or k10 (2016) device (i guess any models with and unlockable bootloader and working TWRP).
Not for the 2017 models!
Why "friendly" root? Go see my old guide how unfriendly the method used to be:
https://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
Guys with latest (2017 febr. 1) security patch read this before you proceed:
https://forum.xda-developers.com/showpost.php?p=71469157&postcount=183
https://forum.xda-developers.com/showpost.php?p=72414225&postcount=250
Short version:
1. unlock bootloader (read step 2.1 if there is no device corrupt message during every boot up after unlocking bootloader!!!)
2. boot into TWRP (i tested with 3.0.0 twrp and above, never tested below)
3.1 install rce_univ.zip (download from this thread: https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327, but follow instructions here!)
3.2 install supersu
3.3 install rce_univ.zip again
reboot
Long version:
The links written with italic fonts are video guides (please excuse me for the quality they were made by my mobile phone)
1. unlock bootloader
- in settings/about phone/software info tap on build number about 10 times so you unlcok developer options
- in settings/developer options tick on "oem unlock" and "usb debugging" and untick "verify apps over usb"
- in settings/security tick on "unknown sources" and untick "verify apps"
video guide for above steps: Link Removed by Moderator
- make sure you installed all the drivers for your mobile from lg's site (LGMobileDriver_WHQL_Ver_4.1.1.exe and also lg bridge) - Link Removed by Moderator
- set up adb/fasboot using 15 seconds adb installer: https://forum.xda-developers.com/showthread.php?t=2588979 - Link Removed by Moderator
- go to the folder it's installed (in my case it's C:/adb - adb.exe and fastboot.exe supposed to be there) hold shift and right click "open cmd here" - Link Removed by Moderator
- in the command window type "adb devices"
it will start adb services and will print a line like "...lgk350... or ...lgk420... lgk430, etc"
if you can't find your device there check device manager or google how to work things out
normally in device manager you should find "LGE Mobile USB Serial Port" under Ports - Link Removed by Moderator
- now reboot to fastboot mode typing the command: "adb reboot bootloader"
your phone should go blank and only print fastboot mode on the bottom of the screen
- check your fastboot connection: type: "fastboot devices"
same as before (in my case it was writing some unrecognizable letters - probably wrong coding) if you see nothing then check device manager -Link Removed by Moderator
you may try to install android SDK (command line tool is enough - https://developer.android.com/studio/index.html - bottom of the page Link Removed by Moderator) if the connection is not working - however there must be a way to make it work (i had a hard time in device manager - i changed each driver a million times until it worked)
in device manager you should find "android bootloader interface" in my case its under "samsung android phone" i don't know why but it works
- In case you have a working adb and fastboot connection type (if you lost connection you have to get to fastboot again: "adb reboot bootloader"):
"fastboot oem unlock" - the phone will ask you if you really mean it, using the volume and the on/off buttons (twice) you can accept
you will lose all your data!!! and most likely lose warranty as well!!! Link Removed by Moderator
however your phone shell restart just fine (you have to manually restart it by taking out the battery or boot into twrp and reboot from there. There should be some message during boot up that your system is vulnerable from now on.
- after reboot you may want to check if your bootloader is really unlocked: get back to fastboot and type "fastboot getvar all" and find the line which sais if your bootloader is unlocked (if it's not you may repeat the process)Link Removed by Moderator
set up developer settings again:
- in settings/about phone/software info tap on build number about 10 times so you unlcok developer options
- in settings/developer options tick on "oem unlock" and "usb debugging" and untick "verify apps over usb"
- in settings/security tick on "unknown sources" and untick "verify apps"
Link Removed by Moderator
- !!!if there is no device corrupt message during every boot up then you need an additional step i'll describe at step 2.1!!! - Link Removed by Moderator
2. find a working TWRP for your device (i collect them in the first comment below - https://forum.xda-developers.com/showpost.php?p=70375626&postcount=2):
- put the recovery image (e.g "k8twrp.img") into your ADB folder (like c:\adb - where you opened command promt earlier)
- Get back to fastboot again and boot to TWRP - type in cmd: "fastboot boot k8twrp.img" (or whatever your TWRP image's filename is)
- if its not booting into TWRP normally try another TWRP (comment #2)
- on the first screen of the TWRP it's asking for password to decrypt data - just hit cancel
- if you have the device corrupt message during every boot up you can skip the next step (go straight to step 3.)
2.1. in case you have no device corrupt message during every boot up follow the next steps
- on the keep system read only? screen of the TWRP let it allow modifications (swipe!)
- reboot to System
- Link Removed by Moderator
you must see the device corrupt message during boot up -> you are ready to go for a root
- try to reboot the device if the device corrupt message is still there during boot up (Link Removed by Moderator). If it's not there you may repeat the process or check my old guide for troubleshooting.
3. the rooting part -Link Removed by Moderator[/I]
(you can read my old guide why we need to tweak the boot image before installing SuperSU - if you are interested)
- download the ramdisk compression exchanger: https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327 (we need this because SuperSU can only work with gzip compressed ramdisks while we have lz4 compressed ones)
- download latest SuperSU TWRP flashable version: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
- put this (rce_univ.zip) and latest SuperSU (i used v2.79) on your sd card (you need external sd because the internal sd is encrypted in TWRP)
- reboot your device into TWRP (through adb and fastboot as before)
- cancel decrypt data
- don't swipe on system modifying screen just click on "keep read only"
- go to backup, backup your boot image (tick only boot partition /untick the rest/ and select storage as micro sd card) in case anything goes wrong during the rest of the process you can always restore it
- go to install
- select storage and chose micro sd card
- install rce_univ.zip (it will recompress your ramdisk to gzip - so SuperSU can tweak it)
- when it's finished don't wipe or don't reboot! Go back (hit back button button) and install SuperSUxxx.zip
- go back again (without restart or wipe) and install rce.zip again (this will recompress your ramdisk to lz4)
- now you can reboot to system (without any wipe) - it will bootloop a few times, be patient!
If something goes wrong check my old guide for deeper understanding and troubleshooting!
If you have any problem with installing rce_univ.zip please post comments to it's thread:
https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327
Comments in this thread shell be only TWRP related or deeply device specific.
No promises... and no responsibility i take... !!!
Supported TWRPs:
in case you want to go for sure or you can't find a working TWRP port it yourself easily using my guide: https://forum.xda-developers.com/lg-k10/development/mtk-portable-twrp-porter-t3536123
or use the ones already ported:
Lg k10 k430: https://forum.xda-developers.com/lg-k10/development/teamwinrecoveryproject-3-0-0-0-lg-k10-t3404434
Lg k10 k430dsy (firmware: 10k - 2017 feb security date): Link Removed by Moderator
(Lg k10 k420n/ds: https://forum.xda-developers.com/lg-k10/development/unofficial-twrp-3-1-0-k420-ds-n-t3571943 - different root method required)
Lg K8: https://forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-lg-k8-k350-mtk-t3517894
others take a look around here: https://forum.xda-developers.com/lg-k10/development
or use this guide: http://www.chinaphonearena.com/foru...752-MT6753-MT6795-MT6797-TWRP-MT67xx-tutorial
Looks cleverly. May take a try
Could it be this SuperSU?
https://download.chainfire.eu/696/supersu/
a_lewicki said:
Could it be this SuperSU?
https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
Well... why would you use that old one? This might not even be systemless root so it would not work. Why dont you check the link i posted in the OP so you could find this one i recommend to use: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
after flashing rce.zip i got an error " unpacking boot image failed! aborting..."
what should i do to fix that? i've tried reading throught your old guide but i'm a noob and i couldn't find anything i could understand.
help anybody???
pedrodgr said:
after flashing rce.zip i got an error " unpacking boot image failed! aborting..."
what should i do to fix that? i've tried reading throught your old guide but i'm a noob and i couldn't find anything i could understand.
help anybody???
Click to expand...
Click to collapse
Next time you try, please make a recovery log (In recovery advanced menu) and send it to me or upload it here!
Which model? Which TWRP?
Also upload or send me your boot image that you backed up!
I added one more line to the script to see where its found the boot partition so please download again before you proceed for a better troubleshooting experience!
@gottlasz after everey install reboot system? (rce.zip then reboot supersu and reboot and rce.zip again and reboot?) or without rebooting?
a_lewicki said:
@gottlasz after everey install reboot system? (rce.zip then reboot supersu and reboot and rce.zip again and reboot?) or without rebooting?
Click to expand...
Click to collapse
No way! Do not reboot! Once you install rce.zip it changes the ramdisk compression so the phone can't boot up. Then the supersu tweaks the boot image (roots the phone) then you install rce.zip to change the ramdisk compression back to normal. Then you can reboot.
@gottlasz thank you so much IT WORKS
a_lewicki said:
@gottlasz thank you so much IT WORKS
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
@gottlasz thank you so much IT WORKS
Click to expand...
Click to collapse
I know it works...
Do you mind me asking which phone you have (k8/k10), which model and which TWRP you used?
gottlasz said:
I know it works...
Do you mind me asking which phone you have (k8/k10), which model and which TWRP you used?
Click to expand...
Click to collapse
twrp 3.0.2
lg k10 k430dse
---------- Post added at 02:39 PM ---------- Previous post was at 02:24 PM ----------
[mention]gottlasz[/mention] do you know how to make snapchat working on root?
a_lewicki said:
twrp 3.0.2
lg k10 k430dse
---------- Post added at 02:39 PM ---------- Previous post was at 02:24 PM ----------
[mention]gottlasz[/mention] do you know how to make snapchat working on root?
Click to expand...
Click to collapse
okay, thanks for the info. I dont know anything about snapchat. If you just download it from playstore?
yes from playstore but i read this app won't work with root
a_lewicki said:
yes from playstore but i read this app won't work with root
Click to expand...
Click to collapse
I just downloaded and tested. Works without any issue...
gottlasz said:
I just downloaded and tested. Works without any issue...
Click to expand...
Click to collapse
Hmmm that's strange...
On my device I can't login to this app and i read this app won't work with root
a_lewicki said:
Hmmm that's strange...
On my device I can't login to this app and i read this app won't work with root
Click to expand...
Click to collapse
I don't know man... i don't think it's a root related issue. The app should promt if it had any problem with root.
However if you use any paid service through the app that can be an issue. Still.. the app has to write something about root if it has a problem with it.
gottlasz said:
Next time you try, please make a recovery log (In recovery advanced menu) and send it to me or upload it here!
Which model? Which TWRP?
Also upload or send me your boot image that you backed up!
I added one more line to the script to see where its found the boot partition so please download again before you proceed for a better troubleshooting experience!
Click to expand...
Click to collapse
Thanks for the fast reply, it's the k10 430dsf
i'll try downloading it again and give it a new try.
I was also using the twrp 3.0.0
i'm downloading the 3.0.2 now and i'll let you know if it works.
Thanks once again.
Happy new year for everyone:good:
i have the LG K8 (K350F) model.
Can i root my phone with this method???. Anyone with this model has probe this tutorial???.
thanks in advanced
raul2903 said:
i have the LG K8 (K350F) model.
Can i root my phone with this method???. Anyone with this model has probe this tutorial???.
thanks in advanced
Click to expand...
Click to collapse
If you have a working TWRP then its gonna work. Did you test any TWRPs already?

[GUIDE]MI A2 Supports 1080p at 120 fps

To use 1080p at 120 fps use Snapdragon camera and enable camera api 2
Google camera video recording is not proper due 9:18 aspect ratio video dont record in proper aspect ratio (or maybe its with arnova pixel 2 mod apk)
portrait mode on arnova pixel mod2 selfie dont work as of now(but pixel mod3 work well)
Gcam dont support 4k as of now
If found fix comment down
Unlocking Bootloader
Unlocking Method
Our Xiaomi Mi A2 is locked and needs to be unlocked before flashing anything.
STEPS:
1. Power off your handset.
2. Press and hold volume down button and connect the handset to the pc/laptop.
3. Handset will now enter into fastboot mode.
4. Open command prompt on your pc/laptop and run the following command:
fastboot oem unlock
5. Your phone will be unlocked.
*** Make a backup of all your data as it might get erased during the process***
*** Warning***
After you unlock the device, it will become less secure. Your personal data might be leaked or lost.
Please think twice before flashing your phone and do it at your own risk.
Rooting Mi A2
How to flash the patched boot.img to get Magisk (and root)
If you are already familiar with fastboot and the commands in general, simply go to Fastboot flash to check out the flashing commands.
You will need fastboot command to perform the flash.
Restart into fastboot via button presses
Simply reboot the phone. Hold down the Volume Down button just at the instance when the phone turns dark to start the boot sequence. The phone should instead boot into fastboot mode.
Restart into fastboot via ADB
You will need the adb command.
Below assumes Linux bash environment with both commands located in PATH, and the phone should have already been connected to the machine.
If the phone is already booted into Android, you can go into:
Settings > System > About phone
and scroll down all the way, and keep tapping on Build number, to enable Developer options.
Now go back one screen and enter into Developer options, and enable Android debugging to allow the machine to send commands to the phone via adb.
Once done, go to the phone and accept the host key. Then go back to the machine and in bash run
adb devices
to make sure that the phone is being correctly detected.
To reboot into fastboot mode, run
adb reboot bootloader
Fastboot flash
In fastboot mode, run
fastboot devices
and make sure the phone is being correctly detected.
To flash the patched boot image to install Magisk, run
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Note that this is a destructive action and may cause bootloop if the build number of your current build is different, so make sure that the build numbers on the phone and the directory name match.
Reboot the phone with the following command
fastboot reboot
The phone should hopefully reboot back into the Android OS successfully.
Now you should have the Magisk v16.0 installed, which means your phone can now perform root operations.
reserved
how to enable camera api 2 ?
toxotis70 said:
how to enable camera api 2 ?
Click to expand...
Click to collapse
You will need to flash patch magisk img and
make your img on your own depending on your build version
download official boot.img of that build and install magisk manager and patch img through that
and through fastboot flash it
toxotis70 said:
how to enable camera api 2 ?
Click to expand...
Click to collapse
You need to have root permissions, and then you need to enter this line (down) into system file called build.prop
persist.camera.HAL3.enabled=1
So go step by step
1. unlock bootloader
2. root your phone
3. enable camera api by editing build.prop
4. enjoy your new camera possibilities !!!
i unlocked the bootloader...now, which is the easiest method to root mi A2 ?
toxotis70 said:
i unlocked the bootloader...now, which is the easiest method to root mi A2 ?
Click to expand...
Click to collapse
Just flash this patched boot.img to partition a, via fastboot, and your phone will be rooted.
CHECK THE VERSION OF ROM FIRST ! V9.6.10.0.ODIMIFE
https://forum.xda-developers.com/showpost.php?p=77295065&postcount=22
do i loose OTA ?
toxotis70 said:
do i loose OTA ?
Click to expand...
Click to collapse
I suppose yes as soon as you remove/change/alter the recovery to get it. But I would love to be shown wrong there. ?
Regards,
H.
dodjob said:
I suppose yes as soon as you remove/change/alter the recovery to get it. But I would love to be shown wrong there. ?
Regards,
H.
Click to expand...
Click to collapse
As you just modify the boot Image i guess ota will still be fine but you'll have to patch the new boot Image with magisk again to have root. That's of course as you said, when not using twrp only
I have to read a bit more about the root process acquisition for the mia2. Things are getting quite complex I must say. And specially not clear. Coming from a N5 it was then very straight forward ? I'm honestly thinking to wait a bit that things get more reliable before doing anything. I know, that's weak, but again, it seems that there has been a lot of changes since Oreo and all these boot patching and security check ? thanks for the head up Benjamin! Regards, H.
It doesn't work on Pie with December update and Magisk v18.0
It doesn't work on Lineage OS 16 unofficial for Jasmine, I've got magisk v18 and gcam3 installed and working
dodjob said:
I have to read a bit more about the root process acquisition for the mia2. Things are getting quite complex I must say. And specially not clear. Coming from a N5 it was then very straight forward I'm honestly thinking to wait a bit that things get more reliable before doing anything. I know, that's weak, but again, it seems that there has been a lot of changes since Oreo and all these boot patching and security check thanks for the head up Benjamin! Regards, H.
Click to expand...
Click to collapse
It's really simple, unlock bootloader, boot the patched boot and click install in the magisk manager app. That's it. next time search more, we have a lot of guides on xda, this one is outdated.
Matteo
Actually you can do this without any bootloader unlocking.
1. Just go to default camera app.
2. Go to video mode and enable the slow motion by clicking
three horizontal bar.
3. Now again click the three horizontal bars and go to settings.
4. In settings select 1080p 30fps.
5. Record the video and check it resolution in google photos by the detail of the video.
App crashes on pie

[How to] Enabling cam2 (GCAM) for every android version with temp root + keeping OTA

This guide worked for every OREO version, and also is working for PIE ! :good:
You will enable camera2 on your phone, and keep it stock afterwards so it can receive future OTA updates. :victory:
1 - Unlocking bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
First of all, enable the Developer Option.
To do this go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled”.
Now go back to settings -> Enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging.
Now connect the phone with your USB cable, use USB port 2.0 on your computer.
It should appear on your phone screen an asking for access privileges of your PC (device, maybe Linux), allow it.
Download ADB if you don't have it.
https://drive.google.com/file/d/1yCdMyAAOD46T4B8haFuZVF57E4-WK8l2/view?usp=sharing
In ADB folder, double click "Open CMD here.bat".
AND FROM THIS TIME, YOU DON'T CLOSE THIS CMD AT ALL, UNTILL YOU FINISH THE WHOLE GUIDE
Code:
adb devices
Your device should appear with some random numbers like this
https://www.howtogeek.com/wp-content/uploads/2012/10/image34.png
If it does, go to next stage, if it's not, you are not installed usb drivers corectly or did not enabled usb debugging.
Link for USB Drivers for Mi A2.
http://dl.adbdriver.com/upload/adbdriver.zip
Code:
adb reboot bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
Code:
fastboot oem unlock
Phone will reboot, go to check developer options > usb debugging ON once again.
Code:
adb reboot bootloader
Again in fastboot we are unlocking critical partitions, and once again it will erase verything from the phone, so be sure to do the backup as needed.
Code:
fastboot flashing unlock_critical
Again when the phone reboot, check developer options > usb debugging ON.
2. Rooting the phone (temporarily)
Download stock boot and patched boot of android version you have, if you need versions for OREO, find somewhere in forum, here it is link for PIE.
10.0.9.0 https://drive.google.com/drive/folders/1ZP5jelFGT5z9EJvHRokzLJwAikKtWI8p?usp=sharing
10.0.8.0 https://drive.google.com/drive/folders/1XNE_veO_FvOLQ46oorUBa2g7TKA1PHRv?usp=sharing
10.0.7.0 https://drive.google.com/drive/folders/1kHLYXhaWFpjh58F79xnOkN3kjkuyEdHV?usp=sharing
10.0.5.0 https://drive.google.com/drive/folders/1qCIsk1MVVq_X-mR8BBWa2NeVLB_-4q5y?usp=sharing
10.0.4.0 https://drive.google.com/drive/folders/1piLD_9mQv0XgahyIZdxRqfdwaDbfx2_0?usp=sharing
10.0.3.0 https://drive.google.com/open?id=1uO3yfxHdTr4gv4DmCaLu-naIIt8mprBT
"It seems like 10.0.3.0 OTA is withdrawn by Xiaomi due to numerous bootloops in stock phones."
My recommendation is to skip flashing this version, until next stable comes up !
10.0.2.0 https://drive.google.com/drive/folders/1_cIM0ltKD_PU1mIiWwUE-nMba964NyvN?usp=sharing
10.0.1.0 https://drive.google.com/drive/folders/18tcBVaKwH9cy_RVczf-GSc_tAkFYvn15?usp=sharing
9.6.17.0 https://drive.google.com/drive/folders/1D9RlDZRupdriCyJM4p0ixvntPE2QPP9w?usp=sharing
Put the files in adb folder, both the stock boot.img and patched_boot.img.
NOW !
There are two methods, so you can choose between those two:
1. Faster and easier one with only booting patched boot
2. Slower with flashing, but this one will teach you how to flash and root your phone
1. ENABLING WITH BOOTING PATCHED_BOOT.IMG
In CMD type
Code:
adb reboot bootloader
Code:
fastboot boot patched_boot.img
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, just skip it, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop persist.camera.HAL3.enabled 1
For PIE and for using v6 Gcam ports three more commands, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3.enabled 1
Code:
setprop persist.camera.stats.test 5
Code:
setprop persist.vendor.camera.stats.test 5
Press ctrl+c to exit adb shell (windows) or just type "exit" and again "exit"
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, and the phone should start normaly without Magisk installed, and with camera2 enabled, because nothing was flashed, you are DONE !
2. ENABLING WITH FLASHING PATCHED_BOOT.IMG
In CMD type
Code:
adb reboot bootloader
Code:
fastboot getvar current-slot
Then when you see your active partition, flash the patched image.
Code:
fastboot flash boot_a patched_boot.img
OR if it was b partition active
Code:
fastboot flash boot_b patched_boot.img
Code:
fastboot reboot
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, just skip it, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop persist.camera.HAL3.enabled 1
For PIE and for using v6 Gcam ports three more commands, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3.enabled 1
Code:
setprop persist.camera.stats.test 5
Code:
setprop persist.vendor.camera.stats.test 5
Press ctrl+c to exit adb shell (windows) or just type "exit" and again "exit"
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, prepare and hold down the volume button when phone restarts, your phone will go into fastboot.
Type the command for active partition
Code:
fastboot getvar current-slot
Code:
fastboot flash boot_a boot.img
Or
Code:
fastboot flash boot_b boot.img
Code:
fastboot reboot
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
If you're using temp recovery, just fastboot boot patched_boot.img, no need to flash, and once done just reboot
if i flash boot.img back i get stuck in android one screen
idriff said:
if i flash boot.img back i get stuck in android one screen
Click to expand...
Click to collapse
On what android version were you ?
pie, i just flashed back the modified boot and it worked but now im rooted
What version google camera you guys using?
minnuss said:
This guide worked for every OREO version, and also is working for PIE ! :good:
You will enable camera2 on your phone, and keep it stock afterwards so it can receive future OTA updates. :victory:
1 - Unlocking bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
First of all, enable the Developer Option.
To do this go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled”.
Now go back to settings -> Enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging.
Now connect the phone with your USB cable, use USB port 2.0 on your computer.
It should appear on your phone screen an asking for access privileges of your PC (device, maybe Linux), allow it.
Download ADB if you don't have it.
https://drive.google.com/file/d/1yCdMyAAOD46T4B8haFuZVF57E4-WK8l2/view?usp=sharing
In ADB folder, double click "Open CMD here.bat".
AND FROM THIS TIME, YOU DON'T CLOSE THIS CMD AT ALL, UNTILL YOU FINISH THE WHOLE GUIDE
Code:
adb devices
Your device should appear with some random numbers like this
https://www.howtogeek.com/wp-content/uploads/2012/10/image34.png
If it does, go to next stage, if it's not, you are not installed usb drivers corectly or did not enabled usb debugging.
Code:
adb reboot bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
Code:
fastboot oem unlock
Phone will reboot, go to check developer options > usb debugging ON once again.
Code:
adb reboot bootloader
Again in fastboot we are unlocking critical partitions, and once again it will erase verything from the phone, so be sure to do the backup as needed.
Code:
fastboot flashing unlock_critical
Again when the phone reboot, check developer options > usb debugging ON.
2. Rooting the phone (temporarily)
Download stock boot and patched boot of android version you have, if you need versions for OREO, find somewhere in forum, here it is link for PIE.
https://drive.google.com/drive/folders/18tcBVaKwH9cy_RVczf-GSc_tAkFYvn15?usp=sharing
Put the files in adb folder, both the stock boot.img and patched_boot.img.
Code:
adb reboot bootloader
Code:
fastboot getvar current-slot
Then when you see your active partition, flash the patched image.
Code:
fastboot flash boot_a patched_boot.img
OR if it was b partition active
Code:
fastboot flash boot_b patched_boot.img
Code:
fastboot reboot
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, let him do it, install full zip, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop.persist.camera.HAL3.enabled 1
For PIE one more command, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3 enabled 1
Press ctrl+c to exit adb shell.
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, prepare and hold down the volume button when phone restarts, your phone will go into fastboot.
Type the command for active partition
Code:
fastboot getvar current-slot
Code:
fastboot flash boot_a boot.img
Or
Code:
fastboot flash boot_b boot.img
Code:
fastboot reboot
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
Click to expand...
Click to collapse
For me it worked, but in stock camera cant see any diferences, can someone link me a gcam apk to install?
minnuss said:
This guide worked for every OREO version, and also is working for PIE ! :good:
You will enable camera2 on your phone, and keep it stock afterwards so it can receive future OTA updates. :victory:
1 - Unlocking bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
First of all, enable the Developer Option.
To do this go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled”.
Now go back to settings -> Enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging.
Now connect the phone with your USB cable, use USB port 2.0 on your computer.
It should appear on your phone screen an asking for access privileges of your PC (device, maybe Linux), allow it.
Download ADB if you don't have it.
https://drive.google.com/file/d/1yCdMyAAOD46T4B8haFuZVF57E4-WK8l2/view?usp=sharing
In ADB folder, double click "Open CMD here.bat".
AND FROM THIS TIME, YOU DON'T CLOSE THIS CMD AT ALL, UNTILL YOU FINISH THE WHOLE GUIDE
Code:
adb devices
Your device should appear with some random numbers like this
https://www.howtogeek.com/wp-content/uploads/2012/10/image34.png
If it does, go to next stage, if it's not, you are not installed usb drivers corectly or did not enabled usb debugging.
Code:
adb reboot bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
Code:
fastboot oem unlock
Phone will reboot, go to check developer options > usb debugging ON once again.
Code:
adb reboot bootloader
Again in fastboot we are unlocking critical partitions, and once again it will erase verything from the phone, so be sure to do the backup as needed.
Code:
fastboot flashing unlock_critical
Again when the phone reboot, check developer options > usb debugging ON.
2. Rooting the phone (temporarily)
Download stock boot and patched boot of android version you have, if you need versions for OREO, find somewhere in forum, here it is link for PIE.
https://drive.google.com/drive/folders/18tcBVaKwH9cy_RVczf-GSc_tAkFYvn15?usp=sharing
Put the files in adb folder, both the stock boot.img and patched_boot.img.
Code:
adb reboot bootloader
Code:
fastboot getvar current-slot
Then when you see your active partition, flash the patched image.
Code:
fastboot flash boot_a patched_boot.img
OR if it was b partition active
Code:
fastboot flash boot_b patched_boot.img
Code:
fastboot reboot
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, let him do it, install full zip, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop.persist.camera.HAL3.enabled 1
For PIE one more command, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3 enabled 1
Press ctrl+c to exit adb shell.
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, prepare and hold down the volume button when phone restarts, your phone will go into fastboot.
Type the command for active partition
Code:
fastboot getvar current-slot
Code:
fastboot flash boot_a boot.img
Or
Code:
fastboot flash boot_b boot.img
Code:
fastboot reboot
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
Click to expand...
Click to collapse
The post has some errors but I'm here to report you guys how I made it work.
adb devices
adb reboot bootloader
(I had the bootloader unlocked already so I didn't do those steps)
fastboot boot patched_boot.img
(Notice I didn't flash the patched image, you don't need to do that, my current partition was b, but that doesn't matter since I'm not flashing anything, I am just booting into the patched/rooted image)
(Installed magisk manager and rootchecker)
(magisk said it was rooted, so did root checker)
adb shell
su
(I gave the permission on my phone)
setprop persist.camera.HAL3.enabled 1
(If you check the post carefully, this line above is not the same one the OP has, that one is wrong, mine is right)
setprop persist.vendor.camera.HAL3.enabled 1
ctrl+c
adb reboot
(Notice I don't flash anything here as well, since I didn't flash the patched image, so if I reboot, it will boot into my stock boot image)
aaaaaaand it's done.
Thanks to the OP for his work, and please correct the line that is wrong. Cheers. :angel:
Google Camera working fine.
Jamesismo said:
The post has some errors but I'm here to report you guys how I made it work...
Click to expand...
Click to collapse
Hello, thanks a lot!
It's works perfect!
Best regards!!!
hugomoya said:
Hello, thanks a lot!
It's works perfect!
Best regards!!!
Click to expand...
Click to collapse
Please don't quote OP for a single line of comment.
@Jamesismo, thanx, I fixed the typo mistake, did not have the DOT in command line, it was not an error, just a typo, but thanx.
And yes, please guys, do not quote the first post.
In a guide, a neewbie can learn how to unlock bootloader, root the phone, enable cam2, and unroot the phone.
So he can choose, whether he wants to stay with rooted phone or not, or to unroot later if he wants...
I think that with this method, OTA will work even if he has Magisk installed, because nothing is changed in system, but that needs to be confirmed.
I noticed that many people want to lock the bootloader to recieve OTA. It is unnecessary you still receive OTA with an unlocked bootloader provided you have not changed the system folder etc.
Hey @minnuss good job! glad to see this.
I would change one thing i noticed: "Press ctrl+c to exit adb shell."
That's a Windows thing, doesn't work with Linux or Mac. Most people 'should' know how to exit a command prompt, but if not, safer to just say type 'exit' and hit enter. That works on all of the systems.
Cheers
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:[/QUOTE]
If may i ask what version of Gcam you recommend? I've tried
Arnova's v8.3b1 and the front facing camera doesn't work on photo mode, but work on video.
Thanks
@minnuss Hey bro, the post does still have a typo, after "setprop" there must be a space, not a dot. (First line)
---------- Post added at 06:09 PM ---------- Previous post was at 05:57 PM ----------
afajri said:
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
Click to expand...
Click to collapse
If may i ask what version of Gcam you recommend? I've tried
Arnova's v8.3b1 and the front facing camera doesn't work on photo mode, but work on video.
Thanks[/QUOTE]
It does work in protrait mode 5mpx, and if you change it from 5mpx to 3mpx, normal selfie works as well.
@[email protected]
@AsItLies
@kishd
@Jamesismo
@afajri
Fix for front cam on Arnova 8.3b1 > go to settings > developer settings > camera.enable_micro UNCHECK (all the way down in developer settings)
Back, back, exit, remove cam from memory, restart the cam...done ! :fingers-crossed::good::laugh:
The google camera APK that I've used in oreo does not work in Pie. Any new suggestions? With night sight preferably! Thanks
@hugopg
There is no version 6 gcam mod that works for our PIE, but you can use this, it works nice, and do the fix for front cam, just a post up from this.
Arnova's v8.3b1: GCam-5.1.018-Pixel2Mod-Arnova8G2-V8.3b1.apk
minnuss said:
@[email protected]
@AsItLies
@kishd
@Jamesismo
@afajri
Fix for front cam on Arnova 8.3b1 > go to settings > developer settings > camera.enable_micro UNCHECK (all the way down in developer settings)
Back, back, exit, remove cam from memory, restart the cam...done ! :fingers-crossed::good::laugh:
Click to expand...
Click to collapse
Works perfectly!
setprop persist.camera.stats.test 5
According to a newly added thread this command makes the gcam 6 version work on pie.What specifically does this command do? The OP of the said thread didnt know.

Xiaomi noob. Want to root. Need help to avoid breaking the phone

Hello everyone
I got my Mi 9T three weeks ago and I basically haven't used it because I couldn't transfer my backups so Im merely looking to root and install Titanium. The binding period for unlocking the bootloader should end tomorrow and I have a few question to avoid getting stuck on bootloop or break the phone
My device is Global 64gb MIUI 10.3.7.0 and update 10.3.12 is available
1. Which recovery do you recommend to flash on my device/version/MIUI release? Xiaomi-Miui.gr or 4PDA
2. Can I update MIUI and Flash recovery with no issues or are there any issues regarding MIUI version?
3. Do I flash using basic ADB method (phone on fastboot mode, "fastboot flash recovery ***" command") or is there anything I'm missing?
PS/ I did my research so Im aware of basic info
Thanks in advance
You should be fine doing that. I installed the Greek TWRP as well on my Mi 9T with MIUI Global version 10.3.12. Use the latest version available as it has more fixes and support for data encryption/decryption (latest version 3.3.1_12-08-19 as of today: http://www.mediafire.com/file/yuhi6pl5qtjr1nu/twrp_davinci_3.3.1_12-08-19_blue_Ss_new.img/file ).
After flashing TWRP you should format 'Data' first and flash Magisk to prevent the MIUI Global ROM from re-flashing the stock recovery. If you install the MIUI EU ROM or any other custom ROM this is not necessary though.
The bootloop issue is mostly related to the 'Anti-rollback' feature in the MIUI official ROMs. You can check the status by executing 'fastboot getvar anti'. If the result is empty or 1 you can flash whatever you want, but if it's more than 1 you should stick to flashing a MIUI ROM that is the same or higher version than it is now unless you can verify the 'anti' version in that particular ROM is equal or lower than the value in your phone.
You can follow the below video to root the device
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
And if any way you brick the device it can be recovered easily. Follow the below Video for unbricking
rocky29b4u said:
You can follow the below video to root the device
://youtu.be/dIWZGv-jCOA
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
And if any way you brick the device it can be recovered easily. Follow the below Video for unbricking
://youtu.be/JDrH8_yEO28
Click to expand...
Click to collapse
Video is not working. I'm interested since I both mine yesterday.
Sir_gpm said:
Video is not working. I'm interested since I both mine yesterday.
Click to expand...
Click to collapse
Try to open this link separately
https://youtu.be/JDrH8_yEO28
Please don't type english titles if your video will not be in english. This is straight up misleading and bad for everyone.
rocky29b4u said:
You can follow the below video to root the device
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
And if any way you brick the device it can be recovered easily. Follow the below Video for unbricking
Click to expand...
Click to collapse
sanchaz12 said:
You should be fine doing that. I installed the Greek TWRP as well on my Mi 9T with MIUI Global version 10.3.12.....
Click to expand...
Click to collapse
Thank you so much. Your answer clarified a lot of Xiaomi things I was wondering about.
I successfully flashed TWRP. I intended to install MIUI 10.3.12 after unlocking bootloader (im on 10.3.7) but I forgot and flashed TWRP directly. I remembered before flashing Magisk tho. Is the window for updating to 10.3.12 is closed by flashing TWRP?
Also, have you tested EU rom? Should I flash it or stick with stock?
Oh. I got value of 1 after executing "fastboot getvar anti" command
boot.img = ROM
rocky29b4u said:
You can follow the below video to root the device
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
In this video at 5:46 the guy is flashing boot.img as well not just recovery.
In other post I did not see that people were flashing boot.img, is this the firmware? And if its the ROM, is it necessary if I want just root the device or I can stay at stock ROM?
Click to expand...
Click to collapse
We need subs on the video or an english version of it. Don't just paste the video in every step, help us here..
SomniusX said:
We need subs on the video or an english version of it. Don't just paste the video in every step, help us here..
Click to expand...
Click to collapse
Hi,
See I will explain this in very simple steps
1. Download the TWRP image from description in the Video
2. Unlock your phone using MI Unlock Tool
3. Reboot your pone to FastBoot mode again
4. Wherever MiUnlock Folder is present on your computer go to that Folder
5. Right click anywhere on the folder keeping Shift pressed. You will see 'Command Prompt Here' option
6. Select that and Command Prompt will open
7. In command prompt type FASTBOOT DEVICES (This will show connected devices)
8. If device is detected type FASTBOOT FLASH RECOVERY <FULL PATH OF THE RECOVERY IMAGE FILE> (Example if TWRP is in C:\temp then command will be FASTBOOT FLASH RECOVERY C:\TEMP\TWRP.IMG)
9. This time type FASTBOOT BOOT <TWRP.IMG FILE> (This will boot phone to TWRP Forcefully)
10. If 9 doesn't work. Repeat 8 and Skip 9
11. After Step 8 type FASTBOOT REBOOT (Press Volume UP while phone is rebooting)
Phone will boot into TWRP this time.
Hope I was able to explain. If not let me know
rocky29b4u said:
Hi,
See I will explain this in very simple steps
1. Download the TWRP image from description in the Video
2. Unlock your phone using MI Unlock Tool
3. Reboot your pone to FastBoot mode again
4. Wherever MiUnlock Folder is present on your computer go to that Folder
5. Right click anywhere on the folder keeping Shift pressed. You will see 'Command Prompt Here' option
6. Select that and Command Prompt will open
7. In command prompt type FASTBOOT DEVICES (This will show connected devices)
8. If device is detected type FASTBOOT FLASH RECOVERY <FULL PATH OF THE RECOVERY IMAGE FILE> (Example if TWRP is in C:\temp then command will be FASTBOOT FLASH RECOVERY C:\TEMP\TWRP.IMG)
9. This time type FASTBOOT BOOT <TWRP.IMG FILE> (This will boot phone to TWRP Forcefully)
10. If 9 doesn't work. Repeat 8 and Skip 9
11. After Step 8 type FASTBOOT REBOOT (Press Volume UP while phone is rebooting)
Phone will boot into TWRP this time.
Hope I was able to explain. If not let me know
Click to expand...
Click to collapse
In the step 9 you type the name of the file or the whole path of the PC to the file?
rastip said:
In the step 9 you type the name of the file or the whole path of the PC to the file?
Click to expand...
Click to collapse
Its the file name with full path in PC for the Recovery File
rocky29b4u said:
Hi,
See I will explain this in very simple steps
1. Download the TWRP image from description in the Video
2. Unlock your phone using MI Unlock Tool
3. Reboot your pone to FastBoot mode again
4. Wherever MiUnlock Folder is present on your computer go to that Folder
5. Right click anywhere on the folder keeping Shift pressed. You will see 'Command Prompt Here' option
6. Select that and Command Prompt will open
7. In command prompt type FASTBOOT DEVICES (This will show connected devices)
8. If device is detected type FASTBOOT FLASH RECOVERY <FULL PATH OF THE RECOVERY IMAGE FILE> (Example if TWRP is in C:\temp then command will be FASTBOOT FLASH RECOVERY C:\TEMP\TWRP.IMG)
9. This time type FASTBOOT BOOT <TWRP.IMG FILE> (This will boot phone to TWRP Forcefully)
10. If 9 doesn't work. Repeat 8 and Skip 9
11. After Step 8 type FASTBOOT REBOOT (Press Volume UP while phone is rebooting)
Phone will boot into TWRP this time.
Hope I was able to explain. If not let me know
Click to expand...
Click to collapse
Thank you for the reply, and trust me, this text guide is much simpler and useful than trying to decode what you are saying in the video.
SomniusX said:
Thank you for the reply, and trust me, this text guide is much simpler and useful than trying to decode what you are saying in the video.
Click to expand...
Click to collapse
No Problem. Thanks...
Greetings everyone,im facing this error showing on tool,saying number not associated with your phone(already added mi account and was login from the day i got k20)..
please help.

Android 11 + TWRP + Root + Safetynet OK

I just want to share my trials and tribulations...
I tested many things and I manage to have my Poco F2 on Android 11 with easy way to root and have a Safetynet OK
There are many ways to do it but i never found it in only one post...
Here's my TO-DO list to make it...
1 / Starting from the bottom, I flashed the latest global rom (FASTBOOT METHOD to make a clean phone)
V12.0.3.0.QJKMIXM (Android 10)
- activate the phone after boot then go back to Fastboot Mode
2/ Unlock Bootloader via Mi Unlock (Fastboot Mode)
- activate the phone after boot then go back to Fastboot Mode
3/ Install TWRP via Fastboot mode
TWRP-3.4.1B-0328-REDMI_K30PRO
(XXXX is the name of your TWRP file)
- fastboot flash recovery XXXX.img
- fastboot boot XXXX.img
- After flash and the first boot to recovery, "format data" (The one you have to type YES) and reboot into recovery
4/ Install Latest Xiaomi.eu Stable (Or Weekly maybe)
[V12.1.2.0.RJKCNXM][Android 11]
- Copy the rom on your phone (from recovery)
- Install rom
- Wipe your data,cache,Internal storage,dalvik DONT WIPE SYSTEM OR YOU WILL BRICK YOUR DEVICE
- Reboot your device.
- If reboot to recovevy, then format data (again) and reboot system
- activate the phone after boot then start the phone to go to the desktop (google account, security,...)
5/ Root with Magisk Canary
- Reboot into recovery
- Flash Magisk-debug.zip then format cache
- Reboot till the phone ask for sim card code then restart
- Open magisk manager and check you on canary canal for update
- Root should be ok!!! (you can download the magisk zip from magisk manager then reflash it in recovery mode to be sure : i dit it lol)
Here, my safetynet was failed then my google pay didnt work
6/ For Safetynet, use MagiskHide Props (even if I don't use it cause i flashed persist.img from Official rom)
That's all from and for me
Hope it can help
PS : Maybe I have bugs but for the moment it's ok
Probably you loose possibilities to make fingerprint works again... I do the same things and now fingerprint doesn't work more, and there are no possibilities to make it works.
CarloBello said:
Probably you loose possibilities to make fingerprint works again... I do the same things and now fingerprint doesn't work more, and there are no possibilities to make it works.
Click to expand...
Click to collapse
Seems to not want to reset even after a fastboot flash rom
Maybe we need to find another persist.img file....
If you find a solution before me, tell me
Put your phone in EDL mode(install qualcomm driver) and flash fastboot rom via MiTool.
Persist.img not flash in fastboot or twrp method...only EDL
Sorry for bad English.
I try that to flash in edl mode but it not possible because Mi flash tools need authorized account, I whole day trying to flash rom in EDL mode without any luck..
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
the last thing that I now trying is to flash China stable fastboot rom through EDL mode, because Fastboot and TWRP dont change Persist.img , only EDL mode,hope that China rom dont need authrorization
tze_vitamin said:
I try that to flash in edl mode but it not possible because Mi flash tools need authorized account, I whole day trying to flash rom in EDL mode without any luck..
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
the last thing that I now trying is to flash China stable fastboot rom through EDL mode, because Fastboot and TWRP dont change Persist.img , only EDL mode,hope that China rom dont need authrorization
Click to expand...
Click to collapse
I am in the same case, after trying a lot of solutions, none have worked.
I prefer to wait for the arrival of orangefox than to open my device.
pennywise1985 said:
Put your phone in EDL mode(install qualcomm driver) and flash fastboot rom via MiTool.
Persist.img not flash in fastboot or twrp method...only EDL
Sorry for bad English.
Click to expand...
Click to collapse
NOSS8 said:
I am in the same case, after trying a lot of solutions, none have worked.
I prefer to wait for the arrival of orangefox than to open my device.
Click to expand...
Click to collapse
you think that orangefox will help?
tze_vitamin said:
you think that orangefox will help?
Click to expand...
Click to collapse
Maybe, I had sensors problem with my redmi note 7 and only orange fox was able to flash correctly the persist img.
Current twrp do not have access to this Partition, the result " FAILED remote: 'Partition is write protected".
I try this command with terminal "dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist" no error to report but not flash.
I try also to modify"rawprogram0.xml"in fasboot rom ,no error to report but no result.
https://ibb.co/QNx1Tz2
NOSS8 said:
Maybe, I had sensors problem with my redmi note 7 and only orange fox was able to flash correctly the persist img.
Current twrp do not have access to this Partition, the result " FAILED remote: 'Partition is write protected".
I try this command with terminal "dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist" no error to report but not flash.
I try also to modify"rawprogram0.xml"in fasboot rom ,no error to report but no result.
https://ibb.co/QNx1Tz2
Click to expand...
Click to collapse
I still searching for mi flash tools that allowed me to flash in edl mode
tze_vitamin said:
I still searching for mi flash tools that allowed me to flash in edl mode
Click to expand...
Click to collapse
I also tried in ELD mode and I have this error "cannot receive hello packet"...
NOSS8 said:
I also tried in ELD mode and I have this error "cannot receive hello packet"...
Click to expand...
Click to collapse
this is the closest that I get but with no luck..
For the safetynet on android 11, use magiskhide prop. Select Poco f2 pro + the option force basic key attestation. It works for me
tze_vitamin said:
I try that to flash in edl mode but it not possible because Mi flash tools need authorized account, I whole day trying to flash rom in EDL mode without any luck..
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
the last thing that I now trying is to flash China stable fastboot rom through EDL mode, because Fastboot and TWRP dont change Persist.img , only EDL mode,hope that China rom dont need authrorization
Click to expand...
Click to collapse
Which rom does not ask for permission?
NOSS8 said:
Which rom does not ask for permission?
Click to expand...
Click to collapse
MUI 12.2 20.9.17 Beta android 11 !
You need to use the last magisk manager canary version.
The prompt works for me!
Domi14fr said:
MUI 12.2 20.9.17 Beta android 11 !
You need to use the last magisk manager canary version.
The prompt works for me!
Click to expand...
Click to collapse
What are you talking about?
I solved the problem !!!!!
go to the CIT menu press the 3 dot in the top right of screen scroll down calibrate the FOD -> place a white thing on FOD click start before next step put something black on FOD and press next...wait until finish close restart and add your fingerprint have a nice day
I GOT THE SOLUTION AND IT WORKS!!!!
-Go to the CIT menu by pressing : *#*#64663#*#*
-Press the 3 dot to go in "additionnal tools"
-Go to number 12 : "fod fingerprint calibration"
-Follow the instructions :
1 / Put a white paper on the FOD then click start and wait
2/ Put a black paper (or something black) on the FOD then press next and wait
3/ Enjoy
tze_vitamin said:
I solved the problem !!!!!
go to the CIT menu press the 3 dot in the top right of screen scroll down calibrate the FOD -> place a white thing on FOD click start before next step put something black on FOD and press next...wait until finish close restart and add your fingerprint have a nice day
Click to expand...
Click to collapse
yes it works thank you very much :good::good::good:
Domi14fr said:
For the safetynet on android 11, use magiskhide prop. Select Poco f2 pro + the option force basic key attestation. It works for me
Click to expand...
Click to collapse
I still get device not certified in google play and safety net still fails after doing this.
Is decrypt for PIN on TWRP available?
Heard only pattern lock can be decrypted.

Categories

Resources