Related
This thread is meant to address all the common hurdles that are commonly faced by people who are new to treble devices (chef to be specific) and help them to troubleshoot/avoid some small yet critical steps during flashing new ROMs and working with fastboot and recovery in general. It will be continually updated with new stuff as it goes along.
I will be referring to the Motorola One Power and Moto P30 Note as chef only from now on.
The unlocking guide is available in This XDA Thread!
IMPORTANT:
1. Flashing refers to the process of doing a clean flash, with the inclusion of fastboot -w command
2. Latest ADB and Fastboot drivers are required to be installed, else the installation may halt mid-way.
3. Stock ROM refers to the Android One ROM for the Motorola One Power [XT 1942-2]
IMPORTANT: AS OF RIGHT NOW, PEOPLE WHO HAVE INSTALLED STOCK PIE (EITHER VIA UPDATE OR FIRMWARE) WILL NOT BE ABLE TO USE ANY OTHER ROM OTHER THAN THE STOCK PIE ROM. RADIO INTERFACE LAYER IS BROKEN IN OREO SOURCE BUILT ROMS AND THAT CURRENTLY INCLUDES LINEAGE 16 SO PLEASE WAIT FOR PIE SOURCE CODE FROM MOTOROLA FOR THAT TO BE FIXED.
1. I unlocked my chef . How do I flash TWRP in place of the stock recovery?
Solution:Currently you cannot as there is no recovery partition in the device. You have to manually boot TWRP onto the device using fastboot to use it. Follow as directed:
Boot the device into fastboot mode
Use command fastboot boot <path/to/TWRP.img> to boot TWRP temporarily.
2. I am done with TWRP and I want to flash Lineage OS 16 on my chef. I simply flash the .zip archive right?
Solution:No. Before you flash anything,
Take a backup of atleast your EFS and PERSIST partitions using TWRP and off-load it for safekeeping to restore in future if needed. You can also trigger a full backup if you require.
SUPER IMPORTANT: Flash this .zip file to copy the System A/B partitions. If this step is skipped, you will be responsible to brick your own device. THIS STEP IS ONLY REQUIRED ONCE AND ONLY ONCE IN THE LIFETIME OF YOUR DEVICE! YOU WON'T BE NEEDING THIS THE NEXT TIME YOU FLASH ANY ROM. .
After that, flash your dearest custom ROM and get going.
For Lineage OS 16, follow This XDA Thread.
3. I am done testing LOS 16, I want to flash a GSI. Shall I use a stock Vendor Image for the GSI on my chef?
Solution:No. The stock Vendor image is causing bootloop issue in most GSIs. It is recommended to use Lineage OS Vendor to flash a GSI on chef. So flash LOS and then flash your favourite GSI.
Also, Super Important: for those who haven't used lineage before flahing a GSI, it is required to boot Lineage OS first before flashing a GSI.
4. I am done experimenting, I want to go back to the stock image. How do I proceed?
Solution:Follow this XDA thread for it. And don't install OTA updates directly from the device. It will come in the next step.
5. I want to install OTA updates on the stock ROM. How do I proceed?
Solution:Follow this XDA post for it. The installation process is described here. You have to be clever enough to get the appropriate OTA update.
Credits:
@erfanoabdi : TWRP, LOS 16, AB partition management
@rushiranpise : Unlocking guide
@dayask : Testing the process, guide for reflashing stock ROM
@nageen9211 : Testing ROMs
For any additional queries, feel free to contact us at our Telegram Group
For more regular updates, follow our Telegram Channel
Always remember: You have to be smarter than your smartphone to be able to use it!
Cheers and Happy Flashing!
Note to readers
The above guide is for stock kernels only (including lineage)
The custom Darkone Kernel has constant updates and fixes major bugs often. Please follow the linked thread to test it out if you want to. Cheers!
Anyone have flashed GSI ROM? FOr me after flash GSI HavocOS have bootloop :/
DIdn't flash copy system A/B partitions, stuck on bootloop with custom roms.
Watched some youtube videos and didn't read this post before flashing custom ROM. Flashed Custom ROM without flashing A/B partitions. Now I have a phone stuck on bootloop when done anything in TWRP. or I can use my phone with stock ROM installed by fastboot method.
Installing or restoring anything from TWRP results in boot loop.
Restoring the backup I made before flashing, completes the restoration process normally. But when rebooting to system, TWRP prompts me that no OS is installed. If I reboot anyway, its either stuck on bootloop or reboots to recovery and asks me to try again or factory reset, or boots into bootloader mode.
Installing custom ROM begins with Step 1, takes a bit time and starts step 2 and shows completed. Doesn't echos any comments. But when i reboot, same prompt shows saying no OS installed. Reboot anyway and stuck on bootloop or reboots to recovery and aks me to try again or factory reset, or boots into bootloader mode.
Now I installed stock ROM with fastboot method and phone is boots up into system just fine.
Sometimes TWRP can't mount anything.
So am I stuck with stock rom or is there any solutions?
Also, installing stock ROM with fastboot mode showed this error in between scripts
(bootloader) is-logical:xxx_a: not found
and
(bootloader) is-logical:xxx_b: not found
but is able to use the phone just fine with stock ROM.
Hi guys, this is my first time owning a Redmi/Xiaomi with a MediaTek SOC (G80). The device was released with Android 10 so it definitely supports Project Treble. My experience with booting GSIs on Qualcomm Snapdragon devices is straightforward but I attempted the same on the Redmi 9 and I noted the following things:
With no kernel sources released, no stable custom recovery to customize my Redmi 9, I went the GSI route via the standard fastboot commands in the bootloader before I discovered that it uses fastbootd instead to flash the system image. Phew! Also the Redmi 9 (lancelot) is compatible with arm64-ab GSIs.
UPDATE 1: GSI booted. Current custom recoveries cannot be used to flash GSIs on devices launched with Q because the system partition is logical and can only be flashed through fastbootd.
UPDATE 2:First successful boot at post #33. I wanted us to share ideas to make it possible for those interested to boot GSIs.
UPDATE 3: Some screenshots are attached below. Go to the guide for how to install.
nielsync said:
Hi guys, this is my first time owning a Redmi/Xiaomi with a MediaTek SOC (G80). The device was released with Android 10 so it definitely supports Project Treble. My experience with booting GSIs on Qualcomm Snapdragon devices is straightforward but I attempted the same on the Redmi 9 and I encountered the following things:
With no kernel sources released, no stable custom recovery, I went the GSI route via fastboot.
Flashing the vbmeta.img and running fastboot flash system system.img gives an error so i experimented with fastboot flash super system.img which worked without giving any errors. My understanding is the super partition contains more than just the system partition.
Despite successfully flashing the system image as the "super" image, I was unable to boot none of the arm64-ab GSIs I tried which included AOSP 10.0 v222 by @phhusson, Havoc-OS-v3.8 by @SKULSHADY and LineageOS 17.1-20200808 by @AndyYan
Lastly, this device being an MTK is very easy to brick!
Anyone successfully booted? Share your experience here with me.
Click to expand...
Click to collapse
You should not play with your device because this device is MediaTek processor device. I already broke my phone twice and I have to go to service centre my luck was good because I do not have to to pay any money but I learn that I never play with my device
[Update]:
This device launched with Android Q with dynamic partitions within the super partition and a relocated fastboot implementation from bootloader to user space. Theoretically to flash a GSI, boot into fastbootd from the bootloader by running the commands as below [Only proceed if you know what you are doing!!!]:
fastboot reboot fastboot
fastboot flash system system.img
fastboot -w
fastboot erase userdata (if this command doesn't work type fastboot reboot bootloader then fastboot erase userdata)
fastboot reboot
As a result of restoring my bricked device after flashing an unstable custom recovery, my bootloader relocked and therefore can't run above commands now to test if they work. I'll try again after 336 hours!
nielsync said:
[Update]:
This device launched with Android Q with dynamic partitions within the super partition and a relocated fastboot implementation from bootloader to user space. Theoretically to flash a GSI, boot into fastbootd from the bootloader by running the commands as below [Only proceed if you know what you are doing!!!]:
fastboot reboot fastboot
fastboot flash system system.img
fastboot -w
fastboot erase userdata (if this command doesn't work type fastboot reboot bootloader then fastboot erase userdata)
fastboot reboot
As a result of restoring my bricked device after flashing an unstable custom recovery, my bootloader relocked and therefore can't run above commands now to test if they work. I'll try again after 336 hours!
Click to expand...
Click to collapse
Ok i also wait for you...in my case i get 7 day wait time.....after your waiting time finished you should try as follow
Fastboot earse system
Fastboot flash system system.img.
Fastboot flash vbmeta vbmeta.img(download vbmeta.img from this post..it is important to disable Android verified boot.
You can warp data first or latter this prossess...
But i confused what type gsi should download.
A/b or a only....
I know our device does not support a/b. But it use system as root....
Shas45558 said:
Ok i also wait for you...in my case i get 7 day wait time.....after your waiting time finished you should try as follow
Fastboot earse system
Fastboot flash system system.img.
Fastboot flash vbmeta vbmeta.img(download vbmeta.img from this post..it is important to disable Android verified boot.
You can warp data first or latter this prossess...
But i confused what type gsi should download.
A/b or a only....
I know our device does not support a/b. But it use system as root....
Click to expand...
Click to collapse
The above commands can only run after booting into fastbootd apart from "fastboot flash vbmeta" due to the partitioning of the Redmi 9 and other devices launched with Android 10 that come with a SUPER partition that includes the SYSTEM, VENDOR and PRODUCT images. When you boot into fastbootd your device will be listed as "lancelot" in Device Manager under "other devices". Just make sure you have latest Xiaomi drivers and running fastboot commands via the latest Android Platform Tools. Use arm64 A/B GSIs even though it doesn't support seamless updates. I am still waiting for the bootloader unlock to start enjoying
nielsync said:
The above commands can only run after booting into fastbootd apart from "fastboot flash vbmeta" due to the partitioning of the Redmi 9 and other devices launched with Android 10 that come with a SUPER partition that includes the SYSTEM, VENDOR and PRODUCT images. When you boot into fastbootd your device will be listed as "lancelot" in Device Manager under "other devices". Just make sure you have latest Xiaomi drivers and running fastboot commands via the latest Android Platform Tools. Use arm64 A/B GSIs even though it doesn't support seamless updates. I am still waiting for the bootloader unlock to start enjoying
Click to expand...
Click to collapse
Tnx for great answer...
But why we use a/b gsi image file when our device does not support seamless updated??
Our device has a slot only
Shas45558 said:
Tnx for great answer...
But why we use a/b gsi image file when our device does not support seamless updated??
Our device has a slot only
Click to expand...
Click to collapse
Well I can't give a technical answer but I've come to realize that not all system-as-root devices support A/B partitioning but all A/B devices are definitely system as root! Similarly the Redmi 8a (a64-a/b) and 8 (arm64-a/b) also boot A/B GSIs. I say this after flashing GSIs on both devices in the past before I got the Redmi 9. I'm a Redmi boy :good:
nielsync said:
Well I can't give a technical answer but I've come to realize that not all system-as-root devices support A/B partitioning but all A/B devices are definitely system as root! Similarly the Redmi 8a (a64-a/b) and 8 (arm64-a/b) also boot A/B GSIs. I say this after flashing GSIs on both devices in the past before I got the Redmi 9. I'm a Redmi boy :good:
Click to expand...
Click to collapse
It is very great bro... I already broke my phone two time and I have to go to service centre. I was lucky because they do not take any money from me. When your waiting time is over then you flash gsi rom... And if you successfully boot your device then you you must share the process how you do it... I am very excited To use a gsi rom in my device...with out break it again... Because this time I think if I break my device
Then I have to pay the service centre
You should not flash unofficial TWRP recovery because our redmi 9 source code not published yet so the recovery has some problem and if you flash IT again your device is broke again. So I think fastboot method is safe for us
Shas45558 said:
It is very great bro... I already broke my phone two time and I have to go to service centre. I was lucky because they do not take any money from me. When your waiting time is over then you flash gsi rom... And if you successfully boot your device then you you must share the process how you do it... I am very excited To use a gsi rom in my device...with out break it again... Because this time I think if I break my device
Then I have to pay the service centre
You should not flash unofficial TWRP recovery because our redmi 9 source code not published yet so the recovery has some problem and if you flash IT again your device is broke again. So I think fastboot method is safe for us
Click to expand...
Click to collapse
You are right. Flashing that recovery caused me problems too and that's why my bootloader got locked again after restoring. Before that I tried everything to flash a GSI but could not boot. So I tried installing the GSI via that recovery and kaput
nielsync said:
You are right. Flashing that recovery caused me problems too and that's why my bootloader got locked again after restoring. Before that I tried everything to flash a GSI but could not boot. So I tried installing the GSI via that recovery and kaput
Click to expand...
Click to collapse
That's mean we have to wait when stable recovery made for our device....
It took forever
We may be out of luck with the kernel sources. Last I checked, Xiaomi had also not released sources for the Redmi Note 9 series so at least we are not alone. With no hope for Xiaomi EU ROMS, booting a GSI is now our only hope of customizing our device. The problem is, it has not happened yet. @Shas45558 maybe you will be the hero who boots the GSI
nielsync said:
We may be out of luck with the kernel sources. Last I checked, Xiaomi had also not released sources for the Redmi Note 9 series so at least we are not alone. With no hope for Xiaomi EU ROMS, booting a GSI is now our only hope of customizing our device. The problem is, it has not happened yet. @Shas45558 maybe you will be the hero who boots the GSI
Click to expand...
Click to collapse
Ha ha ha......
Shas45558 said:
Ha ha ha......
Click to expand...
Click to collapse
You are the most active guy in the Redmi 9 forums :good:
So moving forward I need you to try and boot a GSI on this phone. This post on Mi Community is helpful in understanding our device partition structure.
I think its fairly safe to boot a GSI because the stock recovery is actually maintained. The problem for me was the unofficial TWRP that caused my device to brick.
nielsync said:
You are the most active guy in the Redmi 9 forums :good:
So moving forward I need you to try and boot a GSI on this phone. This post on Mi Community is helpful in understanding our device partition structure.
I think its fairly safe to boot a GSI because the stock recovery is actually maintained. The problem for me was the unofficial TWRP that caused my device to brick.
Click to expand...
Click to collapse
Fastboot and fastbootd are not same...
But how i understand that my device is boot into fastbootd mood not fastboot mood....
Is their any secret key combination to go to fastbootd??
I think twrp methods is lot easier....but unfortunately we have not get stable twrp as soon ...
Shas45558 said:
Fastboot and fastbootd are not same...
But how i understand that my device is boot into fastbootd mood not fastboot mood....
Is their any secret key combination to go to fastbootd??
I think twrp methods is lot easier....but unfortunately we have not get stable twrp as soon ...
Click to expand...
Click to collapse
Sure with official TWRP life would be easy because you can also easily flash the dm-verity and forceencrypt disabler zip otherwise the device fails to boot even when you follow steps correctly. There's no key combination for fastbootd as far as I know. You have to use a command.
To enter fastbootd, run the following commands;
adb reboot fastboot (to boot into the bootloader)
fastboot reboot fastboot (to boot into fastbootd)
For the device to be recognized in Windows 10 you need to manually install unsigned Xiaomi drivers as shown here and after continue with the commands below;
fastboot flash system name_of_system_image.img
fastboot reboot recovery (and format data using MIUI recovery)
fastboot reboot (fingers crossed )
This post from the Redmi Note 9S may be helpful. The difference is that device has a Snapdragon processor as opposed to ours which is a MediaTek.
https://forum.xda-developers.com/showpost.php?p=83503955&postcount=1
Read this....
Shas45558 said:
https://forum.xda-developers.com/showpost.php?p=83503955&postcount=1
Read this....
Click to expand...
Click to collapse
Yeah I've seen it, thanks. That looks more promising than the first one. I haven't tested it yet but I'll do so as soon as I can on my own device. Have you tried it yourself though?
nielsync said:
Yeah I've seen it, thanks. That looks more promising than the first one. I haven't tested it yet but I'll do so as soon as I can on my own device. Have you tried it yourself though?
Click to expand...
Click to collapse
No i afraid to try.....u should try because you can restore your device...i can restore also but my laptop has some problem so do not want to take risk and unoffical is unofficial .....
And i think it is for chaina rom...ii use redmi 9 prime rom....
I'm still waiting a few more days now before I can unlock my bootloader. Can't wait to test it and use it to flash a GSI. The device you helped me root yesterday is also a Redmi 9 but wasn't mine and I can't mess around with someone else phone
nielsync said:
I'm still waiting a few more days now before I can unlock my bootloader. Can't wait to test it and use it to flash a GSI. The device you helped me root yesterday is also a Redmi 9 but wasn't mine and I can't mess around with someone else phone
Click to expand...
Click to collapse
I have also a waiting time of 98 hrs so im also here to help u all and flash gsi.Also theres a new for ya'll that PTRB RECOVERY is being tested nd booted also without any problem so jus wait some time nd stable version will be released .
Sorry Im new in xiaomi modding,is there a way to flash gsi without twrp?,can I flash gsi from fastboot?
yes, via fastboot. the command is flash system system.img (replace system with the name of the rom). connect to nippon gsi telefram Channel. you can find a large choice of ported rom from xiaomi devices. but i'm not sure vendor are fully compatibile with mediatek. but you can try. flashing system don't damage the bootloader. so you can reflash easy stock in case of problems
wetito said:
yes, via fastboot. the command is flash system system.img (replace system with the name of the rom). connect to nippon gsi telefram Channel. you can find a large choice of ported rom from xiaomi devices. but i'm not sure vendor are fully compatibile with mediatek. but you can try. flashing system don't damage the bootloader. so you can reflash easy stock in case of problems
Click to expand...
Click to collapse
You tried it first???
no... my phone is 3 days old. First i want to test miui. and i think this phone will recive miui 13. so at now i don't want to do heavy modding. only debloating. i like miui. aosp rom have bored me. on my old mi A3 i have try many gsi also android 12 beta. but mi a3 is not an mtk phone. so the only way to know if gsi works is try. i'm quite sure that many gsi will boot. i think the gsi much compatible are note 8 ported
Installed android 12 gsi via dynamic system update. Requires a unlocked bootloader.
Note that my phone has dm-verify corrupt on boot, but still works. The dsu loader seems to be functional. You would have package custom gsi's to load via dsu.
But being able to duel boot std ROM + gsi ROM is a win
Auswolf said:
Installed android 12 gsi via dynamic system update. Requires a unlocked bootloader.
Note that my phone has dm-verify corrupt on boot, but still works. The dsu loader seems to be functional. You would have package custom gsi's to load via dsu.
But being able to duel boot std ROM + gsi ROM is a win
Click to expand...
Click to collapse
Can you try to flash only gsi ROM?
if dsu work well, is the best safe way to try a12. great tips!!!!! sometimes gsi are not fully compatible with vendor. and in particular MTK devices are not modding phones. 99,9% of dev hare on snapdragons. maybe if xiaomi will launch more mtk devides out of China, the situation could change. But in my opinion MIUI don't need to be modded. only debloated and unlocked. Our phone sure will recive miui13 based on A12. I have tryed aosp beta, and the dynamic theming is a fantastic function. implemend on miui will make this rom super cool
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Installed phusson's AOSP using the dsu loader.
Auswolf said:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Installed phusson's AOSP using the dsu loader.
Click to expand...
Click to collapse
nice! connect to nippon gsi. there is a lot of gsi. of all major custom rom. and also miui
Auswolf said:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Installed phusson's AOSP using the dsu loader.
Click to expand...
Click to collapse
But I want only 1 boot not dual boot
use command fastboot flash system... or via twrp (twrp touch don't work but you can use twrp manager in pc terminal with phone connected via usb). internet is full of guide how to flash gsi via twrp. if you like aosp rom try android 12 beta. or dot os. new 5.2 is out. the system ui is very cool. and official gsi for all android go out soon
wetito said:
use command fastboot flash system... or via twrp (twrp touch don't work but you can use twrp manager in pc terminal with phone connected via usb). internet is full of guide how to flash gsi via twrp. if you like aosp rom try android 12 beta. or dot os. new 5.2 is out. the system ui is very cool. and official gsi for all android go out soon
Click to expand...
Click to collapse
Can you try I don't want to brick my phone
oh no! my phone is 3 day old and i love miui. it's impossibile damage bootloader flashing a generic system img. you have alreagy unlock bootloader. if phone dont dont boot you can easily reflash stock via miflash. i will bootloader only when xiaomi will stops major updates. i post my news only for user that live aosp roms
wetito said:
oh no! my phone is 3 day old and i love miui. it's impossibile damage bootloader flashing a generic system img. you have alreagy unlock bootloader. if phone dont dont boot you can easily reflash stock via miflash. i will bootloader only when xiaomi will stops major updates. i post my news only for user that live aosp roms
Click to expand...
Click to collapse
My bootloader still not unlocked ._. but I bricked my phone just putting it in fastboot mode
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
wetito said:
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
Click to expand...
Click to collapse
wetito said:
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
Click to expand...
Click to collapse
My phone bricked after going to fastboot and DM verify corrupted
wetito said:
it's obviously! before flash any non stock roms, bootloadermust be unlocked! this is the base of modding
Click to expand...
Click to collapse
Fire1511 said:
My phone bricked after going to fastboot and DM verify corrupted
Click to expand...
Click to collapse
because you flashed a bad full rom with boitloader locked. i suppose a china rom. all guide are clear "Unlock bootloader before"
using a gsi is safe to prevent big damage. because flash only system partition. probably you didn't read guide with attention. modding must do carefully. i suggest you reflash stock in edl mode. is the only solution
wetito said:
because you flashed a bad full rom with boitloader locked. i suppose a china rom. all guide are clear "Unlock bootloader before"
using a gsi is safe to prevent big damage. because flash only system partition. probably you didn't read guide with attention. modding must do carefully. i suggest you reflash stock in edl mode. is the only solution
Click to expand...
Click to collapse
I don't flashed anything lol
Fire1511 said:
I don't flashed anything lol
Click to expand...
Click to collapse
you said "my phone is bricked after going to fastboot". it can happen only if you have made a mod. like a no stock recovery or a non stock rom. or you said a lot of stupid claims
wetito said:
you said "my phone is bricked after going to fastboot". it can happen only if you have made a mod. like a no stock recovery or a non stock rom. or you said a lot of stupid claims
Click to expand...
Click to collapse
I went to fastboot fastboot
After some time I got a second Axon 10 and I spend some time figuring out what was possible with this phone in terms of root, custom ROM etc.
My results are as follows.
What is working:
Android 9 + Magisk and TWRP
Android 9 + TWRP + Custom ROMs (LineageOS 16 and patched GSI)
Android 10 + Magisk and TWRP
Android 10 + Magisk and MicroG flashed via Magisk (= stock ROM without Google Services)
Android 11 + Magisk
What is not working:
Android 11 + Magisk + TWRP (TWRP logo flashes randomly but TWRP does not load).
Android 11 + Magisk + MicroG (the nanolx patching script does not work with Android 11 as of yet)
Encryption in Custom ROMs
Method to flash files via EDL
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
Unlock Bootloader:
Before you try any of the files, you MUST unlock your bootloader!
BACKUP of your data as it will be lost!
Download the EDL tool from this Thread
If your phone is not on android 9, you must go back to Android 9 first. e.g. by using my Android 9 1.9 backup.
After you restored it, restart while holding the volume + key and do a factory reset / format data.
Boot into EDL again and unlock the bootloader.
Now you are on android 9 with unlocked bootloader.
From here you can follow the other guides in the form and install TWRP or lineageos. Or flash one of my files below.
Flashing EDL files:
Unzip / unrar my files into the backup\full folder of the EDL tool and choose restore + full in the tool.
I put all my files into this MEGA account: MEGA
Android 10 version 2.9 Magisk + TWRP
Android 11 version 3.5 stock
Android 11 version 3.5 Magisk
Android 10 version 2.10 stock
Android 10 version 2.10 Magisk (TWRP can be flashed with Magisk)
Install MicroG:
Only works on Android 9 and 10.
Before you install MicroG you must patch the stock ROM to allow for signature spoofing.
The patcher script I used is on https://downloads.nanolx.org/NanoDroid/Stable/ When I write these lines the up-to-date-version is NanoDroid-patcher-23.1.2.20210117.zip
Reboot.
Install MicroG from the Magisk repository.
After a restart there will be error messages that google apps keep crashing. With each warning, disable the apps one by one.
When you reboot again, no errors should appear and MicroG should report that it is fully working.
You can add the Bromite Framework and give F-droid system rights. Both are available from the Magisk repo.
Updates will likely install the Google apps again and uninstall Magisk...
Revive phone:
Not really related, but I bricked my phone several times.
If your phones does not boot anymore or hangs in a bootloop, try accessing the EDL mode.
The easy way:
Boot while holding volume -
The hard way:
Old Volume +, volume - and power until you end up in EDL. The screen will be black, so it helps if you have the Phone connected to Windows and can hear the system sound when the USB sees a connection.
In anyway you can then use the EDL tool to restore / flash an EDL image.
On custom ROM support:
Well there is LineageOS 16 by Unjustified Dev. https://forum.xda-developers.com/t/rom-unofficial-zte-axon-10-pro-9-lineageos-16-0.3992127/ It works well. But has a patch level that is outdated by now.
On top of it you can install the GSI ROMs created by Rafyvitto. The latest one is Resurrection Remix https://forum.xda-developers.com/t/...nofficial-resurrection-remix-q-8-6-7.4172527/
with a security patch level of mid 2021. Which is recent enough to use. The stock roms are not much better.
With both Custom ROMs, encryption is not working which poses a privacy/security risk when your phone is stolen. Do not forget that your phone does not only contain your photos and data but also your passwords to your accounts.
Added Android 10 2.10 files.
Its nice to see anything new for this phone. I wish I can use these roms but I have the American version.
Hi and thanks for your work and your files.
I'm stuck on "Loading the programmer: prog_ufs_firehose_sdm855.elf >>>", if I try to recover your edl files with EDL Tool, v 3.25.
I have to choose option 2: "Restore Full EDL from backup", right?
Is there a way to check if the bootlaoder is really unlocked?
Thanks in advance
OK, I was able to solve the problem with the "programmer" and try the backups. The next step was almost clear. The device is stuck in bootloop. I've already tried all the backups I could find on Mega. After the EDL Tool has done its work and the device has restarted, the mobile phone goes into the boot loop. And now? So the starting position was: Android 9 with an open bootloader. Maybe someone has an idea?
After I couldn't get the device out of the bootloop, I flashed the A2020G_PRO_V1.6_FULL_EDL via MiFlash and then did an OTA update to 1.8.
Then I tried unlocking the bootloader again, which unfortunately didn't work. The flash is carried out without errors, but the device then apparently does not start in the desired Fastboot mode.
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
brian117 said:
Thanks for your guide. However am I missing something with the Android 11+Magisk installation? I restored all the correct files and everything flashed correctly, however upon reboot there is no Magisk installed anywhere. Did a factory reset after the flash and still not there. Tried installing Magisk via his github and tried patching the boot.img again and it says success but after rebooting it says Magisk is not installed.
Click to expand...
Click to collapse
Maybe you need to switch the slot in TWRP. It sounds as if you install it to the other slot (like A) an then boot B. Or vice versa.
hi guys
i got scammed when i bought my second handed k20 pro after i bought the phone and came home i discovered the seller bypassed and old miui account on this devices so can't now link any miui account which mean i can't unlock the bootloader.
Does anyone of u have any idea about unlocking the bootloader by the unofficial ways or at least installing magisk with locked bootloader
THANK YOU IN ADVANCE
Le Karim HI said:
hi guys
i got scammed when i bought my second handed k20 pro after i bought the phone and came home i discovered the seller bypassed and old miui account on this devices so can't now link any miui account which mean i can't unlock the bootloader.
Does anyone of u have any idea about unlocking the bootloader by the unofficial ways or at least installing magisk with locked bootloader
THANK YOU IN ADVANCE
Click to expand...
Click to collapse
You could install Magisk by two ways:
- By first flashing a custom recovery (TWRP) in Fastboot and then by installing the Magisk zip through TWRP
- Also by flashing in Fastboot the boot.img file patched by Magisk app (Magisk app can be installed as an app to the not rooted phone but IT IS NOT the Magisk irself, you do not get root just by installing Magisk app - Magisk app is only an UI manager for the Magisk)
In both cases you must start by executing the command:
fastboot flash ...
(to flash either recovery.img or patched-boot.img)
but Fastboot WILl NOT allow the flash command to execute when Bootloader is locked
You can read on the Magisk GitHub page how to install Magisk:
Installation
The Magic Mask for Android
topjohnwu.github.io
---
I don't know if you could bypass the Mi account associated to your phone by help from an authorized EDL support
IMO, Xiaomi keeps that info which phones are registered to whose accounts on their servers (not on the phones)
You should search for an ask about the on-line EDL support eg on Telegram. I never needed but I've seen a lot of posts about (for various Xiaomi phones) - users usually need their help when they hard-brick Xiaomi phones
However, it's a paid service, hence it cannot be 'advertised' on XDA (posts with URLs will be usually removed quickly)
zgfg said:
You could install Magisk by two ways:
- By first flashing a custom recovery (TWRP) in Fastboot and then by installing the Magisk zip through TWRP
- Also by flashing in Fastboot the boot.img file patched by Magisk app (Magisk app can be installed as an app to the not rooted phone but IT IS NOT the Magisk irself, you do not get root just by installing Magisk app - Magisk app is only an UI manager for the Magisk)
In both cases you must start by executing the command:
fastboot flash ...
(to flash either recovery.img or patched-boot.img)
but Fastboot WILl NOT allow the flash command to execute when Bootloader is locked
You can read on the Magisk GitHub page how to install Magisk:
Installation
The Magic Mask for Android
topjohnwu.github.io
---
I don't know if you could bypass the Mi account associated to your phone by help from an authorized EDL support
IMO, Xiaomi keeps that info which phones are registered to whose accounts on their servers (not on the phones)
You should search for an ask about the on-line EDL support eg on Telegram. I never needed but I've seen a lot of posts about (for various Xiaomi phones) - users usually need their help when they hard-brick Xiaomi phones
However, it's a paid service, hence it cannot be 'advertised' on XDA (posts with URLs will be usually removed quickly)
Click to expand...
Click to collapse
i already bypassed the mi account on the phone thtat's why I can't link a new one