Database Users

AOSP N for DOOGEE X30

ROM is still under development.
Downloads
20180427-1610
20181006-1451
XDA:DevDB Information
DOOGEE_X30_AOSP, ROM for all devices (see above for details)
Contributors
ttomovcik, VeteranoX, SoaringLake
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 20181127-1452
Beta Release Date: 2018-11-27
Created 2018-05-24
Last Updated 2018-11-28

Reserved

Reserved
Due to some bugs in TWRP, we recommend to charge your device to AT LEAST 70% and keep the device plugged in. I'm still waiting for DOOGEE to respond (emailed them if they can send the kernel source). So In the meantime, enjoy overheating and quick battery discharge in TWRP.
New build out! This addresses the following bugs:
Camera FC when opening settings
Camera slow-mo not working
Perfrmance issues
Enabled on-screen navbar - hardware buttons will remain enabled, however, changing Generic.kl will result in HW buttons not working
Changelog
20181018-1337 (Created by SoaringLake)
[FIX] Missing launcher
[ADDED] Face recognition
20181006
Removed Gallery2 - caused problems, needs to be replaced with GApps
Added sqlite3
Taking screenshots now works
20180427-1610
Initial release
Features / what's working
GPS
Phone calls / mobile data
Wi-Fi
DuraSpeed
Brightness (can be adjusted lower than stock)
Volume changing works (stock ROM doesn't have this for some reason)
Youtube supports VR
MiraVision
Bugs / feature requests
Settings > about phone is showing some random indian guy as maintainer. This is due to the fact that this ROM is ported from another device to X30. Will fix that later, probably
When quickboot is active, phone will charge when off without the charging screen animation
NVRAM ERROR is showing in Wi-Fi networks
Google Play services not updating automatically
Unable to open Google Assistant, opens up multitasking view instead
Split screen buggy
No mediatek gestures
Instagram videos rendering incorrectly (SoaringLake)
Camera FC when going to settings
FM Radio volume issues
Camera slow-mo not working
Installation
Unlock bootloader and flash TWRP/CWM (1)
Flash ROM and GApps in one go. DO NOT REBOOT BETWEEN ZIP FLASHING (2)
Wipe cache
Reboot
(1) - Installing TWRP
Enable OEM unlocking in developer options
Download TWRP from here
Reboot into bootloader (Power off and then power on while holding volumeUp)
On your PC, flash it with: "fastboot flash recovery <filename>.img"
Reboot into recovery (Power off, then Power on while holding VolumeUp and select Recovery)
(2) - Flashing ZIP images
Make sure to wipe device
Flash the ROM from device or SD card. Sideload will result in no OS installed error
(Optional) Flash any variant of openGapps - ARM/7.1.1

thread closed until the download links will be available @ttomovcik pm us when you`re ready to share the links
-=-=-
thread re-opened

How can I root?
Hey can you publish the instructions about to root and install Twrp?
And thanks for your work.

mediafire.com/file/3zifgay1h0c334g/TWRP%20dogee%20x30.rar
install via fastboot "fastboot flash recovery recovery.img", only remember to unlock bootloader 1. in developer options> allow OEM unlock 2. In fastboot "fastboot OEM unlock"
the first result on google after entering doogee x30 root

I'm Stuck!
I followed the steps but I got stuck in TWRP with the ROM and without the ROM that I do?

VeteranoX said:
I followed the steps but I got stuck in TWRP with the ROM and without the ROM that I do?
Click to expand...
Click to collapse
When it comes to our Rom you have to do wipe all and then install it because otherwise it likes to make mistakes, I have no problem.
PS. You can enter the twrp and use the recovery, because some img recovery that I liked liked to brick the phone
PS2. At the time of bootloader unblocking, Start the phone again because it has to restore the phone to the factory, Sam so zeged the phone because I did not read the messages on it and immediately uploaded twrp by which he had a bootloop

SoaringLake said:
When it comes to our Rom you have to do wipe all and then install it because otherwise it likes to make mistakes, I have no problem.
PS. You can enter the twrp and use the recovery, because some img recovery that I liked liked to brick the phone
PS2. At the time of bootloader unblocking, Start the phone again because it has to restore the phone to the factory, Sam so zeged the phone because I did not read the messages on it and immediately uploaded twrp by which he had a bootloop
Click to expand...
Click to collapse
Hey can you send me a copy of your stock recovery? Because now i can't turn it on just flastboot.

VeteranoX said:
Hey can you send me a copy of your stock recovery? Because now i can't turn it on just flastboot.
Click to expand...
Click to collapse
Shutdown device, press vol+ and power Button , you will see the menu, vol + you choose the option and vol-approve
and stock recovery I will send it later
recovery: mega.nz/#!raBW3CBC!LLQYl5tZEFyttQg8LWYeqdqu7sKusOUZXxEsHJthNdo

Phliz Touch recovery 6.59.0
for those willing to give a link to philz touch recovery in version 6.59.0, I worked on ClockWokMod but can not see the external sd card
mega.nz/#!PbpHlbjR!VfIomQYwPQQ6f5-1mT7tIF3x66X692rcBiYUQeusLto

I got it!
It was not necessary at the end I downloaded the stock and it was only discharged , but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
---------- Post added at 04:38 PM ---------- Previous post was at 04:25 PM ----------
SoaringLake said:
Shutdown device, press vol+ and power Button , you will see the menu, vol + you choose the option and vol-approve
and stock recovery I will send it later
recovery: mega.nz/#!raBW3CBC!LLQYl5tZEFyttQg8LWYeqdqu7sKusOUZXxEsHJthNdo
Click to expand...
Click to collapse
It was not necessary at the end I downloaded the stock and it was only discharged, but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.

VeteranoX said:
It was not necessary at the end I downloaded the stock and it was only discharged , but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
---------- Post added at 04:38 PM ---------- Previous post was at 04:25 PM ----------
It was not necessary at the end I downloaded the stock and it was only discharged, but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
Click to expand...
Click to collapse
1. go to the developer options in the system, select allow OEM unlock and debug usb.
2, issue the command in ADB "adb reboot-bootloader"
3. issue the command "fastboot oem unlock"
4. restart the "Fastboot reboot" phone
5. allow for wipe data,
6. go to fastboot,
7. issue the command "fastboot flash recovery $ image"
$ image = name with the extension image recovery

I got it!
Hey now is workin (rom and root) i'm testing now and i will send a feedback later but now just i can say
Faster!
Thank you!

Does anyone know how to fix the error: NVRAM WARRNING: Err 0x02

{root} Boot-loader unlock, TWRP flash and Magisk install after updating to Pie

* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Needed tools : Backup your phone before following any steps
1. Minimal adb and fastboot
2. official TWRP 3.3 for jasmine_sprout Download img file from twrp website
3. latest magisk manager 19.2 zip file from magisk manager website
First step : Boot loader unlock
1) Tap on build number more than 7 times and unlock developer option in about phone.
2) turn on OEM Unlocking and USB debugging
Now open command windows in adb shell folder and connect your device to computer.
type : 1) adb devies (this should show your device after giving permission in your phone : conformation that your device is
connected)
2) adb reboot bootloader
3) fastboot devices ( conformation that your phone is coonected in fastboot mode)
4) fastboot oem unlock
( after that you need to follow according steps in your phone and grant to unlock phone)
keep in mind this will reset your phone. Afteer reboot again turn on developer options and usb debugging
5) fastboot flashing unlock_critical
( the warning and steps you need to follow again in your phone like in step 4)
this will again reset your phone.Afteer reboot again turn on developer options and usb debugging
Congratulations your bootloader is Unlocked now.
STEP 2. Flashing TWRP and Magisk Install
before that keep in mind As Mi A2 follows A/B boot partition system so DONT DIRECT FLASH TWRP FROM
FASTBOOT.
" Dont forget to turn on developer options and usb debugging "
open command window in adb shell folder and boot your phone in bootloader mode as told earlier and connect to computer.
Copy twrp-3.3.0-0-jasmine_sprout.img to minimal adb and fastboot folder. you can rename it to your convenient name
type : 1) fastboot boot twrp-3.3.0-0-jasmine_sprout.img
or if you renamed it
fastboot boot YourRenameName.img
this will temporarily boot twrp in your Device. As twrp is booted you will be able to see your phone connected in computer
(file transfer mode)
Copy and paste both magiskmanager.zip (current latest stable is 19.2 ) into phone
Flash your downloaded version of Magiskmanager.zip
Reboot your Phone.
Congratulations If nothing goes sideways Your phone is Magisk Rooted.
If you want to flash something using TWRP now is the time Otherwise as Mi A2 has A/B slot form and no Recovery Partition You Cannot flash TWRP permanently.
But You can always boot TWRP from adb and use it.

ROM flashing help
Can't flash ROM after using this method

Torque422 said:
Can't flash ROM after using this method
Click to expand...
Click to collapse
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375

Failed
No such a directory problem, please help

Please elaborate more about the problem ? @shahidrok
shahidrok said:
No such a directory problem, please help
Click to expand...
Click to collapse
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
TYPHOON9055 said:
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thanks ?, i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now?
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055

Hve done everything but when i try to reboot to twrp it gets stuck on twrp logo,dont know what im doing wrong.

Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks

I get error 1 during flashing

Amnvlad said:
Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks
Click to expand...
Click to collapse
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Alucard said:
I get error 1 during flashing
Click to expand...
Click to collapse
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic ?

Torque422 said:
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic
Click to expand...
Click to collapse
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?

Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
Available custom roms are for Oreo versions if you have updated ur device to pie , it won't work.

Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
I was on stock pie + may update (10.0.9)
Follow this way , unlock the bootloader via fastboot oem unlock, fastboot flashing unlock it will reboot here, goto developer settings Enable usb debugging
Then do this fastboot flashing unlock_critical It will again reboot
Now, install the magisk app And download the patched boot image from internet Whatever your build no is, mine was 10.0.9 so i downloaded version 10.0.9_boot.img
Open the magisk app, click on install , select and patch a file, Then choose this downloaded patched image, it will flash it successfully, if it don't Then you have mistaken something..
After this there will be a patched.img in download folder Which is just created by magisk, copy this img to pc, Through fastboot Flash it "fastboot boot patched.img"
Now, flash TwrpImage3.3.img through fastboot
When you boot in , Copy and paste your rom, gapps
Now flash twrpVersion3.2.img via fastboot
Clear system,data,caches, Flash the rom in slot B
Now flash the twrp3.2.zip through installed twrp, click on recovery And it will boot to twrp
Now Flash the gapps in slot a (i used nano)
Now flash magisk.zip through twrp
Reboot , That's it!
(Twrp 3.2 is stable for flashing rom and gapps , Just for first time When we coming from stock
Twrp 3.3 latest Gives us MTP transfer, The difference is this in using both of these)
Installation of magisk is the last process, it is part of rom, First installed ur desired rom and then magisk
You said, You installed twrp, as i mentioned above You forgot to do some steps as about patched boot + installation of magisk through patched file etc..
Though you can try to search on google for your next step
patched supported magisk Version x.x.x for mi a2
If you got the file, You are lucky.. otherwise flash the stock rom with mi flash tool
And Start from unlocking bootloader

Magisk Module available.
Torque422 said:
Please elaborate more about the problem ? @shahidrok
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
Thanks , i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055
Click to expand...
Click to collapse
There is a magisk module available for installing kali nethunter in this device. i never tried installing it but it should work fine. Read proper descriptions before installing it though.

Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
the adb recognized my phone but fastboot do not, help me out please

Andrew.kathy said:
the adb recognized my phone but fastboot do not, help me out please
Click to expand...
Click to collapse
Probably a problem with drivers, check and reinstall drivers

Can i use this method to flash magisk on Mi 9T pro?

I can't boot into twrp
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs

Topper8118 said:
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs
Click to expand...
Click to collapse
Checklist:
- there is file of <compatible TWRP recovery> in ADB/Fastboot directory with the name you are typing in fastboot command
- ADB drivers installed correctly (both "adb devices -l" and "fastboot devices" return valid results in corresponding phone states)
- only one phone (namely MiA2) is connected to PC
- phone fully unlocked (OEM debugging enabled and PC was previously approved for ADB in phone)
- USB port on MB of PC is USB-2.x or USB-3.x-compatible-with-Mi-A2<which is not true in general>

Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you

HTCDevil said:
Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical

[RECOVERY][STABLE]Unoffical TWRP for Xiaomi Mi A3[laurel_sprout]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Whats Working?
Everything is working
Can change Slot A/Slot B on twrp
SDcard and OTG working
Decryption of Data working
Flashing of roms work pie and even Q roms work.
HOW TO UPDATE a ROM and Keep TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage or sdcard;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk(recommend to use Magisk v19.4);
- Reboot.
Download:
TWRP 3.3.1-2 Unofficial Installer by Nikesh Kataria
TWRP 3.3.1-2 Unofficial by Nikesh Kataria
Donations:
Credits:
Thanks to @mauronofrio for a great help to make a stable recovery
Thanks to @Typhus_ for hardcore testing
Thanks to @prakash78 for testing
Contributors
Nik001
Source Code: https://github.com/Nikesh001/android_device_xiaomi_laurel_sprout-twrp
Version Information
Status: Stable
Created 2019-10-21

Reserved

This man -> @Nik001 deserves a beer!!!
Thank you for delivering us a fully working TWRP for laurel_sprout!
Cheers!

Typhus_ said:
This man -> @Nik001 deserves a beer!!!
Thank you for delivering us a fully working TWRP for laurel_sprout!
Cheers!
Click to expand...
Click to collapse
Welcome and thank you for testing twrp.:fingers-crossed:

Thank u peru sir

A3 real modding let's start

Good Job @Nik001

Anyone tell how to flash twrp... proper commands
Please
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Is that tested anyone.

Stock fw 10.3.8 (global) not booting with this twrp - in 10.3.8 audio modules have strange dependence "saved_command_line" symbol from kernel. For loading this modules need patch kernel sources -
diff --git a/init/main.c b/init/main.c
index 6d1880f0b852..2106f54a7008 100644
--- a/init/main.c
+++ b/init/main.c
@@ -128,6 +128,7 @@ void (*__initdata late_time_init)(void);
char __initdata boot_command_line[COMMAND_LINE_SIZE];
/* Untouched saved command line (eg. for /proc) */
char *saved_command_line;
+EXPORT_SYMBOL_GPL(saved_command_line);
/* Command line for parameter parsing */
static char *static_command_line;
/* Command line for per-initcall parameter parsing */
Click to expand...
Click to collapse

Proper install method explained
Hello!
Please, @Nik001, update the OP with the install method that I'm going to describe next, ok?
It's just to avoid future complications (lost of Wi-Fi, sound, etc...) for "not that experienced users".
Your bootloader must be unlocked. If it's not, then follow step 1 of the instructions provided HERE.
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (being on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot getvar current-slot (to check what's your current active slot)
fastboot set_active b (if your active slot was a, if it was b then change it to a)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​
When TWRP recovery boots, if you have a stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)
Install the TWRP zip (always install the latest build available)
Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
Reboot to System
Why do I suggest this?
By doing this method (which seems more complicated but, trust me, it's how it should be done) we will flash TWRP img into the "inactive" slot, thus, not breaking anything on the "currently active" slot. When TWRP boots, it will patch both slots boot ramdisks. But the thing is, on the "currently active" slot (the one inactive on the beginning) it will patch the TWRP img but, on the "currently inactive" slot (the one that was active on the beginning), it will patch the stock boot.img, thus, no bug will happen that usually appears when a user accidentally flashes the wrong boot.img into boot partition.
On the other hand, if we have a stock boot.img, that matches the build on the "inactive" slot, we could flash it into boot partition before installing the zip that patches ramdisk. By doing this we will patch both stock boot.img present on both slots (instead of patching TWRP img and boot.img).
Cheers!

Sapper Morton said:
The method Typhus shared works 100% of the times; however I must say, I don't use it, just preference; as it follows, instead of flashing into the inactive slot, I flash the pre_patched boot image into the active slot, this of course will mostly like break network and other components on the ROM, if you mismatch image versions; however, if you flash the stock boot image (using install button, inside TWRP, tapping into 'images', select your stock boot.img) and then patch it using the TWRP Installer right after, you will be using the right image, so no problem will occur, and mostly important, no slot change is needed. Both methods works, choose what you prefer, just read it carefully and I repeat, always use the same boot image from your firmware, a lot of confusion comes to the fact, that when you uses TWRP.img or Magisk.img they aren't boot images, but they are; A/B partition scheme doesn't use some individual partitions anymore, as /recovery, thus is extremely important to patch your boot image, where the recovery, kernel and other components now lives.
Click to expand...
Click to collapse
So, in other words, your method is this (correct me if I'm wrong):
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (beeing on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)​
Flash stock boot.img that matches your current build using TWRP install Image feature, into boot partition
Install the TWRP zip (always install the latest build available)
Reboot to System
Is that it?
If it is, the only downside I see is that, when a new version comes out (through OTA for example), you'll first need to get your hands on a stock boot.img that matches the new build.
Right?
Cheers!

Typhus_ said:
So, in other words, your method is this (correct me if I'm wrong):
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (beeing on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)
Flash stock boot.img that matches your current build using TWRP install Image feature, into boot partition
Install the TWRP zip (always install the latest build available)
Reboot to System
Is that it?
If it is, the only downside I see is that, when a new version comes out (through OTA for example), you'll first need to get your hands on a stock boot.img that matches the new build.
Right?
Cheers!
Click to expand...
Click to collapse
As someone who just wants to root his phone with TWRP and few magisk modules, and not miss out on OTAs, seeing these many methods is so confusing and overwhelming ?

After flashing recovery from pc..then go for fastboot reboot from minimal adb and " volume+ key" i saw error in my phone "no command"

Sapper Morton said:
Use the method Typhus explained, it's more simple in the long run; there will be no need to manually flash stock boot image afterwards, since Magisk will have done a proper backup, thus, you will only need to use 'restore image' feature inside Magisk Manager; When taking an OTA, make sure to read the complete Magisk documentation before proceeding:
https://topjohnwu.github.io/Magisk/tutorials.html
Click to expand...
Click to collapse
Thank you! I will do that. But one more thing I'd like to ask. Do you know where I could find the boot image for 10.3.8.0.PFQMIXM? I checked git for dumps, but I couldn't find the boot image for this one.

Sapper Morton said:
Sure, read the OP; Typhus has linked a couple of boot images, including 10.3.8.0 PFQMIXM.
https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509
Click to expand...
Click to collapse
Sick! Thank you very much, sir!

What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?

Makishima said:
What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?
Click to expand...
Click to collapse
In that case, obviously, simply flash the new TWRP zip.
The install method I've explained is for everyone who never had TWRP, or Magisk patched boot, installed on the device.

Makishima said:
What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?
Click to expand...
Click to collapse
Just flash the zip in twrp that you have.
That's what I did and it worked no problem on pe ROM

Typhus_ said:
In that case, obviously, simply flash the new TWRP zip.
The install method I've explained is for everyone who never had TWRP, or Magisk patched boot, installed on the device.
Click to expand...
Click to collapse
I did as you said but it says 'NOTE: You are now unrooted!'. Do I need to flash Magisk again?

Makishima said:
I did as you said but it says 'NOTE: You are now unrooted!'. Do I need to flash Magisk again?
Click to expand...
Click to collapse
Yes, that's right.

[RECOVERY][UNOFFICIAL] OrangeFox R10.1

Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
OrangeFox R10.1
Working features
Android 10 ROM flashing
Internal storage decryption
Data partition backup
Consistent A/B slots flashing - local zip files always flash to ACTIVE slot, except sideload - adb sideload flashes ROM to INACTIVE slot
Known issues
You can't encrypt backups right now
Splash screen is not saved (visual bug)
Installation
If you don't have custom recovery installed
Download recovery image and installer zip
Reboot to fastboot
fastboot set_active b
fastboot flash boot OrangeFox_laurel_sprout_22-03-2020.img
Hold volume up button before executing fastboot reboot, release button after you see OrangeFox logo
Flash recovery installer zip, reboot to recovery
If already have custom recovery installed
Download recovery installer zip
Flash recovery installer zip
Update
Download recovery installer zip
Flash recovery installer zip
Downloads
22.3.2020
Image
Installer zip
Older builds
21.3.2020
Image
Installer zip
Sources
Recovery
Device tree
Credits
OrangeFox team - ROM
@nik001 - device tree and installer
@oddlyspaced
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] OrangeFox R10.1, Tool/Utility for the Xiaomi Mi A3
Contributors
Golbinex
Version Information
Status: Stable
Created 2020-03-21
Last Updated 2020-03-22

Reserved
Changelog
22.3.2020
You can backup internal storage now (you need sd card/usb flash for this, also you need to mount internal storage first)
Round corners
Less logs
21.3.2020
Initial build

Works for last android 10 stock?

facundonak said:
Works for last android 10 stock?
Click to expand...
Click to collapse
Yes, you can flash stock a10.

i tried flash from fastboot stock android 10 and the phone go direct to fastboot

New build is up.
You can backup internal storage now (you need sd card/usb flash for this, also you need to mount internal storage first)
Round corners
Less logs

facundonak said:
i tried flash from fastboot stock android 10 and the phone go direct to fastboot
Click to expand...
Click to collapse
There is no official stock A10 fastboot ROM yet, flash stock fastboot a9 and flash stock a10 via ota zip.

Flash from USB OTG supported ?

kosmasgr said:
Flash from USB OTG supported ?
Click to expand...
Click to collapse
Flash from SD card works. I can't test usb drive, because I don't have a USB-C adapter.

Thank you for your hard work!
Do you know what is the error 127?
/sbin/foxstart.sh process ended with ERROR: 127

Please help
i followed this tutorial but my phone restart always on fastboot logo
Is there a solution to restore any things please

moyses said:
Please help
i followed this tutorial but my phone restart always on fastboot logo
Is there a solution to restore any things please
Click to expand...
Click to collapse
Switch to the slot you wasn't tampering with. (find current slot with fastboot getvar current_slot, then change to inactive with fastboot set_active [slot letter].

Golbinex said:
Switch to the slot you wasn't tampering with. (find current slot with fastboot getvar current_slot, then change to inactive with fastboot set_active [slot letter].
Click to expand...
Click to collapse
It did not work, any one with stock boot image please, my phone is out

What the difference between your build and the offcial one from Orange Fox site?

moyses said:
It did not work, any one with stock boot image please, my phone is out
Click to expand...
Click to collapse
If you have pie, you can flash only boot image from fastboot stock ROM
inouext said:
What the difference between your build and the offcial one from Orange Fox site?
Click to expand...
Click to collapse
Newer version (R10.1), also installing a10 ROMs didn't work for me on that one.

It doesnt worrrrrrrrrrrrrrrrrrrrrrrrrrkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk!!

doesnt work, on both slots.

cldkrs said:
doesnt work, on both slots.
Click to expand...
Click to collapse
It does.
You are probably on android 10 yes?
This recovery.img is built with pie kernel so only works on android 9 pie.
The recovery.installer.zip will work on both android 9 and 10.
Flash twrp.img for android 10 and then use ofox installer.zip to install ofox.
---------- Post added at 11:22 AM ---------- Previous post was at 11:22 AM ----------
Noexcusses said:
It doesnt worrrrrrrrrrrrrrrrrrrrrrrrrrkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk!!
Click to expand...
Click to collapse
Read above. It does work please edit your comment to reflect this

How can i flash persist.img because my fingerprint doesnt work
Mi A3 cihazımdan Tapatalk kullanılarak gönderildi

What's happening? I can not flash any recovery on Android 10, always fastboot.

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.