Database Users

Please Help me! I can't flash stock rom

Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery

Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.

I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux

daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later

Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.

daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery

Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file

sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .

This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo

sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble

Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.

I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...

Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.

Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?

Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again

Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here

Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .

Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot

sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img

[Guide][Bricked][Unbrick][ZE551ML][ZE550ML] Black screen,No fastboot,Rec. vib only

For those who bricked their phone and facing any of the following issue (Black screen, vibrating only, no fastboot, unable to start, unable to install firmware etc.)
If you got No Fastboot, No recovery, No Display, hard bricked your device.You must perform sequential steps indicated below, process will include many small steps. Plz make sure to perform all steps in same sequence and same manner as prescribed. Remove all drivers related to mobile you have installed earlier.
Step 1: Install the Intel Soc USB driver:
(if you are using windows 8 or 10. it is very important to disable driver signature enforcement. see the sections related to your windows below. (note: if you will reboot pc after disabling it will be enabled again)).
This Is the driver which help a computer connecte to your Zen2 IntelSoc mode. To install these driver you need to perform special steps if you are using windows 8 / 8.1, 10 . you need to disable driver signature enforcement before installing drivers. below i have mentioned steps needed to install driver for various versions of windows. but first download the needed driver from link given below.
https://drive.google.com/open?id=0B72QQTXqZSRwR0JGeFI2U3FUZ2c
Step 1.1 - how to install these drivers:
(Note: if you see the image like below attached thumbnail and you click install software any way 2 times means drivers are installed correctly. if you don't see image below while installation it means you need to disable driver signature enforcement)
If you're using Windows 7:
Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc.
If you're using Windows 8 / 8.1 :
On Keyboard press Windows + I to show charm bar in the right corner,
click on the option setting. Choose "Change PC Settings" to enter the PC Settings.
Choose the General tab and navigate to Advanced Startup section, continue click Restart now.
This will reboot windows and allows you access to the advanced mode, now select the following options: Troubleshoot - -Startup Settings Advanced Options and then click the Restart button to restart the computer.
now you will see screen with various options numbered from 1. Find disable driver signature enforcement. And press the appropriate number on keyboard your pc will reboot
Now Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2
If you're using Windows 10 :
On Keyboard press Windows + I or click Start, select Settings.
In The Settings window, select the Update & security.
Continue Choose recovery and then advanced startup and click "Restart now".
When The computer has access to the Advanced screen you will see screen with various options numbered from 1. Find disable driver signature enforcement. And press the appropriate number on keyboard your pc will reboot
Now Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2
1.2 Connect Zenfone with computer IntelSoc Mode:
Now you must complete this step before installing xfstk downloader. it helps to setup device's connection to PC
on your pc open device manager and find Intel Soc.
Click to expand it. You will see a single option under here.
Connect your phone to computer via USB cable,
now back to the phone, hold power button for 10 seconds to shutdown completely, then press simultaneously the key "power" + "volume down", until phone vibrates. Or computer makes detection sound, wait a few seconds. it will add an item immediately below intelSoC in device manager ?MOOREFIELD? new devices is connected successful.
Now Download intel android USB Driver and install normally from link below:
https://drive.google.com/open?id=0B72QQTXqZSRwSU5CdDNuUElEcUE
( only after installing the above driver with correct steps and connecting Soc then only install xFSTK).
Step: 2 Installing xfstk-downloader:
installation of xFSTK is very simple. download xFSTK setup from the link below. to install. right click the setup file and run as Administrator. click next next simply until you finish the installation process
Here is the download link:
https://drive.google.com/open?id=0B72QQTXqZSRweDdfMjlPOGEyTW8
Now to Unbrick Process.
( only after installing the above driver with correct steps) go ahead to unbrick process.
Unbrick Process:
-The Necessary files:
ZE551ML: https://drive.google.com/open?id=0B72QQTXqZSRwV0QyWFRXbjMxaFk
ZE550ML: https://drive.google.com/open?id=0B72QQTXqZSRwY1AyLUdKdkI3OWM
After downloading the necessary files extract it. it will contain 3 files:- dnx_fwr.bin, ifwi.bin, droidboot_dnx.img.POS_sign.bin.
-Run XFSTK Downloader as Administrator, click the second tab at bottom MRD A0 / B0 + MOOR A0 + CRC .
-Then Go to Options to change the value in the Value Section Override Flag GP 0x80000807. Tick GP value over ride, change device detection time out value to 220 and Click OK is complete initial preparation. (important note: never use wrong gp flag value it may complicate things)
+ First select Firmware files FW DnX: and IFWI: by clicking small three dots:- IFWI DNX 2 dnx_fwr.bin and ifwi.bin file.
+ Now select operating system : skip the first box, in second box select file droidboot_dnx.img.POS_sign.bin
now switch off your mobile by holding power button for long and connect to pc.
now click begin download on xFSTK. after that simply power on mobile.
-Here You may see error multiple times just try to power off device completely and turn on again. flash again and again Until you see success: FW+OS Download complete!
After that you may see a 4 color screen, just like some TV stations stop broadcasting on TV. You have to wait a little. after few seconds or minutes device will boot into bootloader. wait 10 to 15 min if no success, If not repeat the xFSTK process again. once you get fastboot screen on device go ahead to flash RAW firmware
Now there are two ways to flash RAW firmware one is Asus Flash Tool (AFT) other is without AFT with help of commands. Personally, i like command method as it is much more reliable than Asus Flash Tool. both methods are provided here under.
Flash Raw Firmware Using Asus Flash Tool:
Required Files:
Asus Flash Tool: https://drive.google.com/open?id=0B72QQTXqZSRwUDZqa0M4SWRObVE
Raw Firmware File:
ZE551ML: https://drive.google.com/open?id=0B72QQTXqZSRwb2x1SHg2UUlsT0U ( Link updated to google drive and latest raw firmware 2.20.40.194)
ZE550ML:https://drive.google.com/open?id=0B72QQTXqZSRwcTBDaXZOYUNBdHM
Download Asus Flash Tool and install. Run asus flash tool as administrator. And select the phone model. Then select the downloaded raw file and click start button to flash.
Note: sometimes flash process may go endless. If this happens remove the usb from computer. Kill asus flashtool process from task manager. Now run tool again and flash.
Flashing Firmware Without AFT:
For this you need two things first is adb tool and second is raw firmware file both links are provided here under:
Fastboot and adb tool: ( includes setup as well as independent files ) latest version updated
https://drive.google.com/open?id=0B72QQTXqZSRwMGVuT0cwRlp2UG8
Adb fastboot tool for 64 bit windows and for those who are facing issue to load zip files while adb sideload. or unable to load system.img
https://drive.google.com/open?id=0B72QQTXqZSRwUkFRMl81b1pWa0k
Raw firmware ( you can use any earlier downloaded RAW firmware file)
ZE551ML: https://drive.google.com/open?id=0B72QQTXqZSRwb2x1SHg2UUlsT0U ( Link updated to google drive and latest raw firmware 2.20.40.194)
ZE550ML: https://drive.google.com/open?id=0B72QQTXqZSRwcTBDaXZOYUNBdHM
Now very first of all, rename .raw firmware file to .zip file and extract all files from it.. now place all files in adb and fastboot folder. ( Note: to extract raw file to avoid extension issue please give firmware file a complete new name ie: "user.zip" or anything you like
now in folder ( where you placed files from raw firmware and adb and fastboot tool folder) at empty place anywhere in folder hold Shift on computer keyboard and right click with mouse. Now click open command window here.
perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Phone will successfully reboot into system. don't worry, first boot gonna take a little longer time. so have patience and watch some funny video till phone boots up.
Now you can install any firmware version via adb sideload. make sure to install latest lollipop firmware before flashing Marshmallow. follow the guide to sideload.
How to Install firmware using adb sideload:
First of all go to setting > About >Software information > tap build number 7 times to enable developer options. now under setting go to developer options and find USB debugging here. tick to enable USB debugging
Now go to Asus website and download the desired firmware and place that file in adb fastboot tool folder. rename the files to your desirable short name ( lets take an example rename it to User.zip). now move your mouse cursor in folder anywhere at some empty place, press and hold the keyboard shift Button now right click your mouse button and open command window here. in cmd type adb devices and press enter ( note it will prompt an option on mobile to authorize the computer for adb. Please authorize this computer. ) after this your device will be listed under adb devices with some number. if not type command once again, if no success this time please ensure you have installed usb driver and authorized computer.
after adb recognize the device. run the following command
"adb reboot recovery"
phone will reboot into recovery ( Note you can go to recovery manually as well. for doing so power down your device. after that press and hold volume + button and press power button as mobile shows asus logo leave power button but keep holding volume button. you will boot into fastboot mode use your volume up and down key to go to option recovery mode. now click power button. phone will reboot into recovery mode.
once phone reboot into recovery mode find option apply update from adb and press that option with the help of power button
now go to cmd and run the following command
" adb sideload user.zip " ( Note: User.zip is the firmware file you download from asus and placed in adb tool folder and renamed so can be replaced with the name you renamed your file)
now let the computer do its work sit back and relax. once file loaded successfully reboot device.
( note first boot always takes little longer time so don't panic have patience and wait till phone boots completely
if you have any question please post here. use hide button while replying to avoid unnecessary length of post..
If the guide was helpful to you and your device is alive again. Hope you can hit the Thanks button. it will not take much effort or long time. Thank you.

Well hello sorry for the silly or stupid question but since I'm new to asus, And I see a lot of peoples bricking your devices I wanted to ask, There are some risk in update it if my bootloader locked and my phone fully stock? I received it some weeks ago and I not rooted or unlocked bootloader yet, so there are some chance to I get in a brick? Like some peoples did? I going to update next week, but just on case I wanted ask.
I gonna be very thankful if someone answer me

Tayanarak said:
Well hello sorry for the silly or stupid question but since I'm new to asus, And I see a lot of peoples bricking your devices I wanted to ask, There are some risk in update it if my bootloader locked and my phone fully stock? I received it some weeks ago and I not rooted or unlocked bootloader yet, so there are some chance to I get in a brick? Like some peoples did? I going to update next week, but just on case I wanted ask.
I gonna be very thankful if someone answer me
Click to expand...
Click to collapse
if you are stock. you can update without any issue. just keep in mind update to latest lolipop first.. ( Z00A-WW-2.20.40.194 ) then to MM

those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds

thank you
i could not flash the raw file via Asus Flash Tool. then i followed this process. after successful reboot updated to last official lollipop rom by copying it to phone root directory. after that finallly upgraded to official android 6.
phone working fine now. thanks a lot

touhid7 said:
i could not flash the raw file via Asus Flash Tool. then i followed this process. after successful reboot updated to last official lollipop rom by copying it to phone root directory. after that finallly upgraded to official android 6.
phone working fine now. thanks a lot
Click to expand...
Click to collapse
Glad to know that it was helpful for you

sukhwant717 said:
After a long time Asus funally launched MM for ZE551ML. but be very careful to install. Do not try to install it from custom recovery, do not install if you have rooted the phone. first return to stock rom. install latest lolipop build. then only update to MM.
any how for those who bricked their phone: use the following guide to unbrick ZE551ML
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Read the above guide carefully. but even after that people are unable to unbrick. people who are unable to flash raw. perform step 2 of the above guide. after that do not use the asus flash tool. Try the following guide,
very first of all. rename .raw firmware file to .zip file and extract all files from it.. now place all files in adb and fastboot folder.
open command window here. ( where you places files from raw firmware and adb and fast boot tool folder)
perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Question is,, if I'm already in android mm,,will my custom recovery still be there? Or do i need to flash it again via adb? Thnks..

jeffrey roy said:
Question is,, if I'm already in android mm,,will my custom recovery still be there? Or do i need to flash it again via adb? Thnks..
Click to expand...
Click to collapse
yes you need to flash if you want to install custom recovery . but flash it after updating to latest MM
if you are on unofficial MM. and you have custom recovery installed. don't try to install official MM. you will brick your device

Ahm question again bro..you mention in op install first to latest lollipop right,, how did you install it,, i mean via twrp or what?
---------- Post added at 03:43 PM ---------- Previous post was at 03:38 PM ----------
jeffrey roy said:
Ahm question again bro..you mention in op install first to latest lollipop right,, how did you install it,, i mean via twrp or what?
Click to expand...
Click to collapse
Sorry for bunch of questions,, I'm just making sure bro..

jeffrey roy said:
Ahm question again bro..you mention in op install first to latest lollipop right,, how did you install it,, i mean via twrp or what?
---------- Post added at 03:43 PM ---------- Previous post was at 03:38 PM ----------
Sorry for bunch of questions,, I'm just making sure bro..
Click to expand...
Click to collapse
if yoy want to install latest MM. for that purpose you must install official asus recovery.. or if you want lolipop only then you can install it from twrp

sukhwant717 said:
if yoy want to install latest MM. for that purpose you must install official asus recovery.. or if you want lolipop only then you can install it from twrp
Click to expand...
Click to collapse
ok, got it, but where can i download official recovery? for firmware 2.20.40.194? thanks!!
---------- Post added at 05:16 PM ---------- Previous post was at 05:08 PM ----------
jeffrey roy said:
ok, got it, but where can i download official recovery? for firmware 2.20.40.194? thanks!!
Click to expand...
Click to collapse
nah never mind found it!!!

jeffrey roy said:
ok, got it, but where can i download official recovery? for firmware 2.20.40.194? thanks!!
---------- Post added at 05:16 PM ---------- Previous post was at 05:08 PM ----------
nah never mind found it!!!
Click to expand...
Click to collapse
just flash firmware with sideload i think it will replace recovery automatically. if not then you can flash manually afterwards

Not able to go to the legit serial number... Can I start from the fastboot steps?

surajpai said:
Not able to go to the legit serial number... Can I start from the fastboot steps?
Click to expand...
Click to collapse
yes. you can but exit the Asus flash tool

Recovering to android L from back up
sukhwant717 said:
After a long time Asus funally launched MM for ZE551ML. but be very careful to install. Do not try to install it from custom recovery, do not install if you have rooted the phone. first return to stock rom. install latest lolipop build. then only update to MM.
any how for those who bricked their phone: use the following guide to unbrick ZE551ML
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Read the above guide carefully. but even after that people are unable to unbrick. people who are unable to flash raw. perform step 2 of the above guide. after that do not use the asus flash tool. Try the following guide,
very first of all. rename .raw firmware file to .zip file and extract all files from it.. now place all files in adb and fastboot folder.
open command window here. ( where you places files from raw firmware and adb and fast boot tool folder)
perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the volume down button and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Before installing custom CM13 I had taken the backup of my device which ran android L.
I have just begun the operation to recover that. Hopefully it should not brick my phone
---------- Post added at 01:21 AM ---------- Previous post was at 01:12 AM ----------
deepankdude said:
Before installing custom CM13 I had taken the backup of my device which ran android L.
I have just begun the operation to recover that. Hopefully it should not brick my phone
Click to expand...
Click to collapse
Good news people, my phone did not brick.
Did not need to move to android L via any method, just restored my back up

please help.
My phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
what i did is update the zf2 through twrp.
pd: excuse my english.

sukhwant717 said:
if you are stock. you can update without any issue. just keep in mind update to latest lolipop first.. ( Z00A-WW-2.20.40.194 ) then to MM
Click to expand...
Click to collapse
Oh thank you for the reply, I'm on latest stock firmware, so I going to update to MM next week

xFSTK seems to detect my phone and copy files, but at the end of the process it won ´t reboot. The program then makes 20 retries, and gives up. No error message, only "success"
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--GetOpCode
16:00:43 - XFSTK-LOG--ReadInAck
16:00:43 - XFSTK-LOG--GetAck - HLT$(4)
16:00:43 - XFSTK-LOG--FW: Firmware update completed...
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--LogError
16:00:43 - XFSTK-STATUS--Error Code: 0 - Success
16:00:43 - XFSTK-LOG--void MerrifieldDownloader::do_abort()
16:00:43 - XFSTK-LOG--Abort
16:00:43 - XFSTK-LOG--C:/Users/agm21_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin size:4194468 bytes
16:00:43 - XFSTK-STATUS--PASS
16:00:43 - XFSTK-STATUS--Firmware download completed. Continuing to OS...
16:00:53 - XFSTK-STATUS--Reconnecting to device - Attempt #20
16:00:54 - XFSTK-STATUS--Timeout to detect the device, make sure to charge up your phone before flashing
Can someone help me, please ...

agm2112 said:
xFSTK seems to detect my phone and copy files, but at the end of the process it won ´t reboot. The program then makes 20 retries, and gives up. No error message, only "success"
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--GetOpCode
16:00:43 - XFSTK-LOG--ReadInAck
16:00:43 - XFSTK-LOG--GetAck - HLT$(4)
16:00:43 - XFSTK-LOG--FW: Firmware update completed...
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--LogError
16:00:43 - XFSTK-STATUS--Error Code: 0 - Success
16:00:43 - XFSTK-LOG--void MerrifieldDownloader::do_abort()
16:00:43 - XFSTK-LOG--Abort
16:00:43 - XFSTK-LOG--C:/Users/agm21_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin size:4194468 bytes
16:00:43 - XFSTK-STATUS--PASS
16:00:43 - XFSTK-STATUS--Firmware download completed. Continuing to OS...
16:00:53 - XFSTK-STATUS--Reconnecting to device - Attempt #20
16:00:54 - XFSTK-STATUS--Timeout to detect the device, make sure to charge up your phone before flashing
Can someone help me, please ...
Click to expand...
Click to collapse
you can power on manually while device connected to it. have you changed device detection time out to 120. when it give three four tries and phone don't starts press power button and start in manually

I have following errors on last cmds :
Code:
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
error: write_sparse_skip_chunk: don't care size 1650659389 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1078366269 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 516055101 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 45117 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 3.181s]
sending sparse 'system' (472927 KB)...
error: write_sparse_skip_chunk: don't care size 1650659389 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1650659389 is not a multiple of the block size 4096
OKAY [ 17.123s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 23.692s
Full process :
Code:
C:\adb>fastboot devices
C:\adb>fastboot devices
C:\adb>fastboot devices
0123456789ABCDEF fastboot
C:\adb>fastboot oem erase_osip_header
...
(bootloader) cmd_oem!arg= erase_osip_header S
(bootloader) [0]erase_osip_header S
OKAY [ 2.274s]
finished. total time: 2.275s
C:\adb>fastboot oem erase_token
...
(bootloader) cmd_oem!arg= erase_token S
(bootloader) [0]erase_token S
OKAY [ 1.805s]
finished. total time: 1.807s
C:\adb>fastboot oem start_partitioning
...
(bootloader) cmd_oem!arg= start_partitioning S
(bootloader) [0]start_partitioning S
(bootloader) Start partitioning
OKAY [ 2.255s]
finished. total time: 2.256s
C:\adb>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 1.685s]
writing '/tmp/partition.tbl'...
OKAY [ 2.253s]
finished. total time: 3.941s
C:\adb>fastboot oem partition /tmp/partition.tbl
...
(bootloader) cmd_oem!arg= partition /tmp/partition.tbl S
(bootloader) [0]partition S
(bootloader) [1]/tmp/partition.tbl S
OKAY [ 2.404s]
finished. total time: 2.405s
C:\adb>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 3.950s]
finished. total time: 3.951s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.441s]
finished. total time: 2.441s
C:\adb>fastboot erase data
******** Did you mean to fastboot format this partition?
erasing 'data'...
OKAY [ 18.099s]
finished. total time: 18.108s
C:\adb>fastboot erase APD
******** Did you mean to fastboot format this partition?
erasing 'APD'...
OKAY [ 2.632s]
finished. total time: 2.633s
C:\adb>fastboot erase ADF
******** Did you mean to fastboot format this partition?
erasing 'ADF'...
OKAY [ 2.373s]
finished. total time: 2.374s
C:\adb>fastboot oem wipe splashscreen
...
(bootloader) cmd_oem!arg= wipe splashscreen S
(bootloader) [0]wipe S
(bootloader) [1]splashscreen S
(bootloader) CMD 'wipe /splashscreen'...
(bootloader) erasing volume "/splashscreen", size=4194304...
(bootloader) wrote ret 194304, count 2, "/dev/block/by-name/splashscreen
(bootloader) read back ret 194304, count 2 "/dev/block/by-name/splashscre
OKAY [ 2.351s]
finished. total time: 2.353s
C:\adb>fastboot oem stop_partitioning
...
(bootloader) cmd_oem!arg= stop_partitioning S
(bootloader) [0]stop_partitioning S
(bootloader) Stop partitioning
OKAY [ 2.261s]
finished. total time: 2.262s
C:\adb>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 2.135s]
writing 'fastboot'...
OKAY [ 2.556s]
finished. total time: 4.693s
C:\adb>fastboot flash token PROD_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 1.681s]
writing 'token'...
OKAY [ 2.442s]
finished. total time: 4.124s
C:\adb>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 1.804s]
writing 'ifwi'...
OKAY [ 3.350s]
finished. total time: 5.158s
C:\adb>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 1.712s]
writing 'splashscreen'...
OKAY [ 2.276s]
finished. total time: 3.991s
C:\adb>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 2.058s]
writing 'boot'...
OKAY [ 2.601s]
finished. total time: 4.662s
C:\adb>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 2.051s]
writing 'recovery'...
OKAY [ 2.586s]
finished. total time: 4.644s
C:\adb>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 2.560s]
sending 'APD' (183963 KB)...
OKAY [ 7.546s]
writing 'APD'...
OKAY [ 7.787s]
finished. total time: 17.898s
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
error: write_sparse_skip_chunk: don't care size 1651515453 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1076383805 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 511402045 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 12349 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 3.206s]
sending sparse 'system' (477812 KB)...
error: write_sparse_skip_chunk: don't care size 1651515453 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1651515453 is not a multiple of the block size 4096
OKAY [ 17.487s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 24.071s
C:\adb>
Can you help me ?
History :
Wanted to update to MM
- unrooted
- try recovery mode and install from asus support new firmware with adb, problem was that i had a custom recovery, i think this is what failed and i had black screen after the update.
- followed your tutorial
- stuck at asus boot logo after having the error i pasted above.
Edit : Seems the archive is corrupted, 7zip throw following error when i extract : Data error : system.img
Gonna try raw file from there : http://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
May be i had a problem while downloading the previous one, but i prefer to test another one.

soft brick mi2s - fastboot loop can't go to recovery mode

Today I was trying to install a newer rom (MIUI 8.1)(also MIUI 4.11 after the 8.1 failed a couple times) through twrp 3.1.1.0-aries and my mi2s got soft bricked after the update failed with error code 7 something about being unable to write system to /system.
So I tried to install the new rom using MiFlash and got there a different error
Code:
[4:25:07 PM 9063612]:target didn't report max-download-size
[4:25:07 PM 9063612]:sending 'tz' (196 KB)...
[4:25:07 PM 9063612]:error:FAILED (data transfer failure (Unknown error))
[4:25:07 PM 9063612]:"Flash tz error"
[4:25:07 PM 9063612]:error:FAILED (data transfer failure (Unknown error))
Then I tried to flash it using Mi PC Suite which got stuck at 52% for 2 hours at "sending system.img". I saw it wasn't going anywhere so I disconnected the device and terminated the task.
At that point the phone didn't go into the recovery mode anymore. I think Mi PC Suite might have done something to the partition table.
Right now the phone is stuck in fastboot loop and can't go into recovery mode unless I run the command
Code:
fastboot boot twrp.img
which can sometimes fail as well with error:
Code:
FAILED (status read failed (Too many links))
At the first time I managed to get back into twrp using the above command I felt some relief and I tried doing a factory reset from the twrp menu. It didn't help.
Flashing twrp using the command
Code:
fastboot flash recovery twrp.img
says everything is okay and is finishing without errors but I still can't boot into it. It just goes straight to fastboot.
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (10346 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 1.793s]
finished. total time: 2.225s
trying to flash new rom using MiFlash gives an error about the partition table
Code:
FAILED (remote: partition table doesn't exist)
Please help me unbrick my device I'm open for suggestions!
Thank you.

I fixed this by downloading "aries_images_4.11.21_4.1_cn" and editing the "flash_all.bat" script to include
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash partition error" && exit /B 1
in the third row right after the 2 "soc-id" checks.
I am still not sure how to upgrade from here to one of the newer miui roms.

XDA1515 said:
I fixed this by downloading "aries_images_4.11.21_4.1_cn" and editing the "flash_all.bat" script to include
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash partition error" && exit /B 1
in the third row right after the 2 "soc-id" checks.
I am still not sure how to upgrade from here to one of the newer miui roms.
Click to expand...
Click to collapse
Solved. I managed to flash aries_global_images_V8.1.3.0.LXAMIDI_20161122.0000.00_5.0_global using MiFlash.
At first I thought it didn't work because it flashed the whole rom way too quickly in like 5-10 seconds and booted back to fastboot but then I just left the device there to rest and when I came back after a few minutes I saw it booted to a black screen with a white MI at the center of it and then android and 3 dots appeared at the bottom so I just waited for a few more minutes and it installed everything.
I hope this might help someone else with similar issue.

[GUIDE] How to Flash Android 8.1/9.0 on Lenovo Z5 (WiFi and Data also working now)

Hi Guys,
I have finally successfully flashed a phh AOSP 8.1 provided in the following thread to Lenovoz5
Before proceeding, here are the basics,
Do not Ever ever ever EVER flash zui_3.9.075_Z5_L78011_multi
Bootloader needs to be unlocked only if you wantto flash custom Android 9.0 Pie roms,
If you want to stick to stock Lenovo rom, then you do not need to unlock bootloader.
If you start your phone and it says "Your device is corrupt" then your phone has zui_3.9.075_Z5_L78011_multi.
This rom is a dirty version of stock rom, that Chinese sellers sells your phone with. This is not the original rom.
Always use "L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst" for unlocking bootloader, 075, this version is the only version that allows unlocking bootloader.
With other versions like L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.390_ST_180809_qpst, L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.200_ST_180809_qpst
This option is hidden by manufacturer under Developer options.
If you start your phone and you dont get option to activate via Wifi or Network, then your phone doesnt have stock rom and it has been tweaked by your seller.
Here is the download link for stock rom, do not use the rom that has _multi in its name.
https://mega.nz/#F!9953xR6a!76EEVKmW3LtjE7tYPF2Z1Q
If you get Sahara error when flashing through QFIL
1) Make sure your phone is in edl mode, follow the video for that
2) Make sure the config is correctly set in Settings within QFIL
3) Try changing USB ports on your PC, It only works on USB 2.0, will throw error on USB 3.0 and 3.1
Make sure you go through this thread, each and every question is answered already.
If you have any questions, make sure to list out everything you did and what you are trying to do,
My phone doesnt start
I cant proceed
I cant flash
I am stuck
I cant unlock bootloader
This doesnt help, please post full description with screenshots , what you have done to your phone after your received it from your seller, what you want,
Google the basics, bootloader unlocking, stock rom, custom rom, Android 8.0, Android 9.0 etc
I have created Lenovo z5 group on telegram, pls post there if you have any questions, i dont check xda, but i will respond on telegram whenever i can.
Check out this video on how to flash using qfil
https://youtu.be/TdkNaKpiiUw
Go through this thread and read all the posts, most of your questions is probably already answered.
I would recommend if you are not good at flashing then back up all partitions on external sd card. (WIFI and data working now )
To backup stock partitions,
1. Unlock bootloader
2. Flash TWRP through fastboot
3. Boot to TWRP and do a full back up of all partitions.
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
All the credits for the rom goes to developers in that thread, i have only flashed it to Lenovo z5.
Flashing guide for Android 8.1: (Everything is working on Android 9.0, check out second post in this thread.)
What you will need:
ADB: https://www.mediafire.com/file/8j84x6j1g2xb8z6/adb.zip/file
TWRP.img https://drive.google.com/open?id=1yj9Vu-1YqR8kxMReP5pZerpLa-PKnZ1z
boot.img - This is the same boot.img in stock qpst from L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.200_ST_1807 21_qpst
or get it from here https://drive.google.com/open?id=14WNBcstAB3A40fafEhI2NWMAhGBtJge_
vbmeta.img https://drive.google.com/open?id=1dTIuxwKnfZFrE7HFtYSMqUx6gItXvxEB
ROM - system-arm64-ab-gapps-su.img from the above link
superuser flash file (To be flashed through TWRP recovery) https://drive.google.com/open?id=1w0PHZFvfYvExBAEnyDyqBpBjMGLBoLes
superuser apk(not necessary to install) https://drive.google.com/open?id=1XU9pydDRPOZ2weq14j6S-hveM98C8zHe
Procedure to Flash custom rom on Lenovo Z5:
Step 1: Flash stock version L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst using qfil mentioned earlier in this thread
(After flashing this stock rom, if your phone goes in to boot loop then don't worry about it, continue with the rest of the process)
Step 2:Unlock bootloader (This will void your warranty) (unlocking command: fastboot flashing unlock)
Step 3: boot to bootloader
Flash with the following commands.
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a system-arm64-ab-gapps-su.img
6. fastboot -w flash system_b system-arm64-ab-gapps-su.img
7. fastboot flash boot twrp.img
8. Once twrp is flashed, do not turn off or restart your phone, press volume down twice, select option boot to recovery
9. Flash superuser flash file(mentioned above)
10. Do not clear any data or cache, we already did that, Start and Enjoy!
After completing these steps please wait for about 25 to 30 mins
(My logs when i flashed the rom)
c:\adb>adb reboot bootloader
c:\adb>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Sending 'vbmeta' (4 KB) OKAY [ 0.018s]
Writing 'vbmeta' OKAY [ 0.037s]
Finished. Total time: 0.079s
c:\adb>fastboot flash boot_a boot.img
Sending 'boot_a' (52261 KB) OKAY [ 1.795s]
Writing 'boot_a' OKAY [ 0.037s]
Finished. Total time: 1.842s
c:\adb>fastboot flash boot_b boot.img
Sending 'boot_b' (52261 KB) OKAY [ 1.798s]
Writing 'boot_b' OKAY [ 0.036s]
Finished. Total time: 1.843s
c:\adb>fastboot flash system_a system-arm64-ab-gapps-su.img
Sending sparse 'system_a' 1/3 (524284 KB) OKAY [ 18.954s]
Writing sparse 'system_a' 1/3 OKAY [ 0.006s]
Sending sparse 'system_a' 2/3 (488160 KB) OKAY [ 20.940s]
Writing sparse 'system_a' 2/3 OKAY [ 0.005s]
Sending sparse 'system_a' 3/3 (514508 KB) OKAY [ 21.349s]
Writing sparse 'system_a' 3/3 OKAY [ 0.010s]
Finished. Total time: 68.562s
c:\adb>fastboot flash system_b system-arm64-ab-gapps-su.img
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 12466167 4k blocks and 3121152 inodes
Filesystem UUID: 98e2d366-b46f-11e8-9d3d-3d9d543f2291
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending sparse 'system_b' 1/3 (524284 KB) OKAY [ 19.159s]
Writing sparse 'system_b' 1/3 OKAY [ 0.037s]
Sending sparse 'system_b' 2/3 (488160 KB) OKAY [ 20.708s]
Writing sparse 'system_b' 2/3 OKAY [ 0.007s]
Sending sparse 'system_b' 3/3 (514508 KB) OKAY [ 21.250s]
Writing sparse 'system_b' 3/3 OKAY [ 0.007s]
Erasing 'userdata' OKAY [ 3.849s]
Sending 'userdata' (4348 KB) OKAY [ 0.167s]
Writing 'userdata' OKAY [ 0.007s]
Finished. Total time: 73.993s
c:\adb>fastboot flash boot twrp.img
Sending 'boot_a' (58524 KB) OKAY [ 2.021s]
Writing 'boot_a' OKAY [ 0.007s]
Finished. Total time: 2.041s
c:\adb>adb reboot bootloader
c:\adb>fastboot erase cache
Erasing 'cache' FAILED (remote: 'Check device console.')
Finished. Total time: 0.013s
Not working:
Notification LED (Thanks to DarkerMaster)
Pictures taken by camera are always 90 degrees rotated
Google Camera app is crashing
Working on Android 8.1:
Call
Camera
Fingerprint reader
WIFI
Mobile data ...
Almost everything
I am still testing the device. I will post details later.
Android 8.1
https://drive.google.com/open?id=1k1bgp3sLedy-e5vqYKZF47WXRIVfO-tN
https://drive.google.com/open?id=11RAiDNS-1_bv7ceYJDLriOuGtMIkfbXt
https://drive.google.com/open?id=1hDrJHaKKHhowWJSvVUN3Y9scZeCMMLIz
https://drive.google.com/open?id=1bvKErzYwF9qH87Leie_acnwElINM8qxQ
https://drive.google.com/open?id=1Sg5mHLgm6_Bl4xz3ZBrgq7sLDbrveGWg
https://drive.google.com/open?id=1XxaiVKaImXZ64mH-TwuXcXNEFaTn2ydK
https://drive.google.com/open?id=1ABII2x3hWMKwgTr8mVxI-cYTiej1lVlN
https://drive.google.com/open?id=1rn7CXYnhiiiDBYoF_K1us9vXjgTMOigq
Imp:
If you have flashed one of these Roms, and you can boot in to it successfully, please do not use Factory reset. If you do, then the rom wont boot, since Magisk/SU is installed.
If you still do, then boot to Bootloader, flash vbmeta, boot_a, boot_b, twrp, Magisk(Android 9)/SU(Android 8).
If you have unlocked bootloader, do not relock it, ever
Special Thanks to phhusson for his [AOSP 8.1] [2018-08-16] Phh-Treble
Experimental:
Zui FM Radio app (Not working yet!)
Please note this is still under development, i am only posting it here, if anyone wants to work on it.
https://drive.google.com/open?id=1raHCHhMxOQVM8L0rbSjoKeTVLmbtBSIc
Don't forget to hit that Thanks button !
Cheers

Android 9.0 flashing guide
Back up all partitions on external sd card.
Check out this video on how to flash using qfil
https://youtu.be/TdkNaKpiiUw
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Rom: PixelExperienceP-arm64-ab.zip
All the credits for the rom goes to developers in that thread, i have only flashed it to Lenovo z5.
What you will need:
TWRP.img https://drive.google.com/open?id=1yj9Vu-1YqR8kxMReP5pZerpLa-PKnZ1z
boot.img - This is the same boot.img in stock qpst from L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.200_ST_1807 21_qpst
or get it from here https://drive.google.com/open?id=14WNBcstAB3A40fafEhI2NWMAhGBtJge_
vbmeta.img https://drive.google.com/open?id=1dTIuxwKnfZFrE7HFtYSMqUx6gItXvxEB
ROM - PixelExperienceP-arm64-ab.img from the above link
Magisk superuser flash file (To be flashed through TWRP recovery) https://drive.google.com/open?id=1FV_ogrSU488bpI_hhuyA8rHm3Fj_xLqb
Magisk superuser apk https://drive.google.com/open?id=1hi_58d1nJ-PNe3aPKb_0YsLrh5ElOXVn
Step 1: Flash stock version L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst using qfil mentioned earlier in this thread
(After flashing this stock rom, if your phone goes in to boot loop then don't worry about it, continue with the rest of the process)
Step 2:Unlock bootloader (This will void your warranty) (unlocking command: fastboot flashing unlock)
Step 3: boot to bootloader
Flash with the following commands.
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a PixelExperienceP-arm64-ab.img
6. fastboot -w flash system_b PixelExperienceP-arm64-ab.img
7. fastboot flash boot twrp.img
8. Once twrp is flashed, do not turn off or restart your phone, press volume down twice, select option boot to recovery
9. Flash Magisk flash file(mentioned above, once this is done take pictures of the TWRP logs)
10. Do not clear any data or cache, we already did that
11. On first boot install Magisk apk mentioned above. That's it !
Not working:
Notification LED
Working on Android 9:
Call
Camera
Fingerprint reader
WIFI
Mobile data(4G not sure about 3G)
Google Camera (If app crashes then follow procedure in this thread https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-enable-camera2-api-t3419579 )
Almost everything
Android 9.0
https://drive.google.com/open?id=1L_q2b8V0V7lIafcQsMVbKgqyRq3Tt2Hp
https://drive.google.com/open?id=1grkAu-FhZ56LKN82ubXYN3163ChTUVwr
https://drive.google.com/open?id=1yd5B0HN9Bund6UbJrEScbRsvrofExtT2
https://drive.google.com/open?id=1lWnH408p6aIREmEzl8IIKyE4UKS5V0Nk
https://drive.google.com/open?id=12EDJRbNm_4KVPD72FJ4Yem0gt3XE-BVr
https://drive.google.com/open?id=1RBt2miHzcvC9punEytJd_9aRyDwwhtV9
https://drive.google.com/open?id=1saTXcINKgbjw4HKxvRrSlbPrYk6GJfRr
https://drive.google.com/open?id=1QfLT5_gUk6k3U7o6ZJig8skn7Ckr--GK
https://drive.google.com/open?id=1pWJxmxO-ZzdNdGCK4LVO_zqxKpCQV5fG
Some snaps taken from the phone
https://drive.google.com/open?id=1w0GCNHKjuhE3x_A6xAwVgkYua0pMWGj-
https://drive.google.com/open?id=1GZ4LXyBHOL-zWEXrJVSMRPc07Nabg-eB
https://drive.google.com/open?id=1kTyVHk2Gr8LHekjvn7AwtnC92xrj0_7G
https://drive.google.com/open?id=1qgADqYoePMN9B5OMcpXw2pUc5DYXPCLI
If Windows doesnt detect phone in File Transfer mode:
Enable Developer options, turn off USB debugging.
If Mobile data doesnt work:
Settings > mobile data > Preferred network type = 4G and Choose your network providers Access point, if there is none then create one.
Special Thanks to EnesSastim and phhusson for their [9.0][GSI] PixelExperience P - UNOFFICIAL
Follow this process if you want to remove encryption:
This will delete the os and data on your phone. please backup everything before proceeding. External SD card will be untouched.
Flash L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.390_ST_180809_qpst via qfil (This step is to flash latest persist, firmware, vendor etc images available in 390, if you want to stay on 075 and you already have this stock image flashed, then you can skip this step)
TWRP: https://forum.xda-developers.com/an...overy-lenovo-z5-special-edition-twrp-t3850041
boot.img and persist.img are from version 390 of stock rom. (you can also use 075 images)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash boot recovery-TWRP-3.2.3-1002-LENOVO_Z5-CN-wzsx150.img
Press volume down button twice and go to Recovery
(change language to english if needed)
In recovery backup all of your partitions on to External SD card.
Mount system, persist, firmware
Advanced > RM Forceencrypt
Select Remove DMVerity and Remove Forceencrypt
Swipt to confirm
(This should not throw any error in red fonts, should show Done in the end)
(If it says failed to mount Persist, then reboot to bootloader, fastboot flash persist persist.img)
In recovery goto Wipe
Select Format Data
type Yes (This will remove the encryption)
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash persist persist.img
fastboot -w flash system_a PixelExperienceP-arm64-ab.img
fastboot -w flash system_b PixelExperienceP-arm64-ab.img
fastboot flash boot twrp.img (older version of TWRP)
Boot to TWRP and flash Magisk
Here is the link to the video
https://www.youtube.com/watch?v=brS5tqfx2BQ&index=3&list=PLNqXvI29Azcg9lxA_n6ltytf9aFhn3T1d&t=1081s
download for 075
https://mega.nz/#F!9953xR6a!76EEVKmW3LtjE7tYPF2Z1Q
Return to Stock:
Downloads : ZUI5 https://drive.google.com/open?id=1IL8Pu3Ame9gu6jqAAkBQrEiRL1a93rHK
ZUI10 https://drive.google.com/open?id=1ANAZXbbygyZHAVNGmgoPimJ1fIKbK38D
Credits for ZUI 5 and Zui 10 goes to @M.Z.F and the original developer of the images in these zip files.
https://forum.xda-developers.com/android/development/lenovo-z5-custom-roms-pie-t3904607
Steps to return to stockbackup your data or everything will be wiped)
IF you are on Android 9.0
1) go to TWRP and back up all partitions on SD card (persist, vendor, system, data, boot, firmware, ... )
Step 2 and 3 will turn encryption on, so if u want to disable encryption, after step 3, flash recovery-TWRP-3.2.3-1020-LENOVO_Z5-CN-wzsx150.img and disable encryption. v 474 has new firmware and i have seen better call reception and data connectivity.
2) Flash stock L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst through QFIL
3) Flash stock L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.474_ST_190118_qpst through QFilL
4) Boot to bootloader
5) go to Zui5 folder (link is above) and click on Batch.bat file
6) Press 2, Hit enter, enter, enter
7) phone will automatically restart and boot to ZUI5
8) go to ZUI10 folder and click on Batch.bat
7) Press 2, Hit enter, enter, wait for phone to restart.
Congrats you are back to stock ZUI.
Don't forget to hit that Thanks button !
Cheers

Wooow! A few questions%
Have you tested camera? How is the quality?
Also Android 9 working ok? What is the file.Zip that should be downloaded and flashed from the Pixel Experience list in the second link?
First link of Android 8.1 doesn't work.
Thanks!

nfraccar said:
Wooow! A few questions%
Have you tested camera? How is the quality?
Also Android 9 working ok? What is the file.Zip that should be downloaded and flashed from the Pixel Experience list in the second link?
First link of Android 8.1 doesn't work.
Thanks!
Click to expand...
Click to collapse
Thanks for letting me know about the broken link, i have updated it.
I have everything working on Android 8.1 , not tried 9 yet. I will test camera quality tomorrow during day time. But camera does work.
Second link is the boot image.

GREAT!
Wanna go home quickly and play with my Z5!!!

Thank you for your work!!
Notification led work?
Did you tried Google Camera?

Also would you be so kind to explain how to flash another image? For example from AOSP 8.1 to 9.0?or viceversa. Thanks

nfraccar said:
Also would you be so kind to explain how to flash another image? For example from AOSP 8.1 to 9.0?or viceversa. Thanks
Click to expand...
Click to collapse
I have tried that multiple times for Android 9.0, wifi and data just doesnt work, may be we will have to wait for new firmware from Lenovo.

rendroid15 said:
I have tried that multiple times for Android 9.0, wifi and data just doesnt work, may be we will have to wait for new firmware from Lenovo.
Click to expand...
Click to collapse
Is it always possible to reflash stock ZUI?
How?
Thank you for Your kind support

nfraccar said:
Is it always possible to reflash stock ZUI?
How?
Thank you for Your kind support
Click to expand...
Click to collapse
Unless you mess with Vendor and stock firmware partitions, you can always go back to ZUI.
For flashing stock ZUI, please see below thread, it has all the information you need including downloads
https://forum.xda-developers.com/android/help/help-lenovo-z5-chinese-updates-t3812110

DarkerMaster said:
Thank you for your work!!
Notification led work?
Did you tried Google Camera?
Click to expand...
Click to collapse
Google Camera is crashing on start up. I have tried 6 different versions. No luck.
Push Notifications are working so it rings but the led is not blinking.

rendroid15 said:
Google Camera is crashing on start up. I have tried 6 different versions. No luck.
Push Notifications are working so it rings but the led is not blinking.
Click to expand...
Click to collapse
Of course you enabled camera 2 API right?

Yo rendroid, I managed to get my phone working again (first time in a week, woo hoo!)
Since flashing the system image didn't work with the adb, I put it in my phone's storage and flashed it with twrp.
(Btw, enabling the file extensions to be seen in file explorer didn't help with flashing the system image)
I was actually surprised it worked!
So my phone now has a working rom on it but I have a few problems:
-WiFi and Data not working. (The wifi toggle actually causes the phone to freeze. However, it breaks itself out and crashes the wifi toggle, leaving you to use the phone again)
-This is a minor issue but the notifications aren't cropped right (cut off and stuff)
This honestly has been a major breakthrough for me ( now that my phone isn't a paperweight anymore) and it's all thanks to you and the other devs for your hard work.
If you could help me with the wifi and data issue, that would the final piece to the puzzle and I could stop using my malfunctioning S4.

Cirus61 said:
Yo rendroid, I managed to get my phone working again (first time in a week, woo hoo!)
Since flashing the system image didn't work with the adb, I put it in my phone's storage and flashed it with twrp.
(Btw, enabling the file extensions to be seen in file explorer didn't help with flashing the system image)
I was actually surprised it worked!
So my phone now has a working rom on it but I have a few problems:
-WiFi and Data not working. (The wifi toggle actually causes the phone to freeze. However, it breaks itself out and crashes the wifi toggle, leaving you to use the phone again)
-This is a minor issue but the notifications aren't cropped right (cut off and stuff)
This honestly has been a major breakthrough for me ( now that my phone isn't a paperweight anymore) and it's all thanks to you and the other devs for your hard work.
If you could help me with the wifi and data issue, that would the final piece to the puzzle and I could stop using my malfunctioning S4.
Click to expand...
Click to collapse
nice !
now for the wifi and data
i need you to flash the same rom using fastboot not twrp
The File explorer setting was just to see if the file has any extensions. So if you dont see an extension then add .img in the end.
I think there is a bug in twrp that is causing wifi and data to not work.

I have tried flashing the 8.1 and it has given me error in all files by fastboot

rng30 said:
I have tried flashing the 8.1 and it has given me error in all files by fastboot
Click to expand...
Click to collapse
can you post the screenshots?
Its most likely you dont have adb installed,
You can get it from here https://forum.xda-developers.com/showthread.php?t=2317790

nfraccar said:
Of course you enabled camera 2 API right?
Click to expand...
Click to collapse
not yet, i am testing stock rom right now.

rendroid15 said:
not yet, i am testing stock rom right now.
Click to expand...
Click to collapse
Then Google Cam can't work. Activate camera 2 API if you have time and try again Google Cam!

rendroid15 said:
nice !
now for the wifi and data
i need you to flash the same rom using fastboot not twrp
The File explorer setting was just to see if the file has any extensions. So if you dont see an extension then add .img in the end.
I think there is a bug in twrp that is causing wifi and data to not work.
Click to expand...
Click to collapse
Well crap. Just when I thought everything was good. The file does the .img extension but for some reason adb just can't find it even though it's literally in the same folder. I'll try again and let you know.

Cirus61 said:
Well crap. Just when I thought everything was good. The file does the .img extension but for some reason adb just can't find it even though it's literally in the same folder. I'll try again and let you know.
Click to expand...
Click to collapse
try this, copy all files directly in adb folder, get rid of folder "Minimal adb drivers", the spaces in that folder name may be the problem.
If that doesnt work then just rename the rom name to rom.img and use that in fastboot command.

Xiaomi Mi 9T stuck in fastboot

Hi!
First off: I'm new to this forum, so if this is not the right place to post or is in the wrong format or whatever, please point me in the right direction.
I'm trying to install LineageOS on my Xiaomi Mi 9T and have gotten stuck in fastboot. I am currently trying to flash the recovery image for Lineage so that i can sideload the Lineage zip, but the phone just boots back to the fastboot mode no matter what I do.
One single time I managed to enter the custom recovery I flashed onto there, but after formatting all partitions, my attempt to sideload the LineageOS zip failed.
I thought I'd just reboot to the recovery and repeat my steps, but since then I have not managed to come back into the recovery mode.
Now I am frantically trying to flash the recovery image onto my phone with no success. The fastboot tool on my PC just says this (which seems fine):
Code:
fastboot flash recovery lineage-17.1-20210327-microG-davinci-recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.446s]
Writing 'recovery' OKAY [ 0.148s]
Finished. Total time: 1.600s
After that I've tried:
Holding power off + vol up
Holding power off + vol down
Holding power off
Holding power off + vol up + vol down
After some searching I have also tried:
Code:
fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
Which SHOULD have booted it into recovery mode, bur nope. Whatever I do I find myself back in fastboot mode.
I have also tried flashing TWRP recovery image (never used it before), just to try something else, but with no success. Same results as with the Lineage recovery image.
How do I get out of this loop and back to installing LineageOS?
I've done this once before with a OnePlus2, but that was painless compared to this.
I appriciate any help. Thanks in advance.

Just found this thread: https://forum.xda-developers.com/t/mi-9t-stuck-in-the-fastboot-menu.4089181/
I'll be looking into it

Hi, same problem here. Flashed TWRP in 1.932 seconds or something but never was able to boot into TWRP. I found a thread on here saying to oem reboot-recovery. Tried that, didn't work. Found some message by the guy who wrote the TWRP saying to flash some other file, but I don't understand what he means. Have you been able to solve the problem ?

Okay, I have solved this for my phone.
I found this soulution on some forum, but do not remember where exactly, so credit is not mine.
I am new to all of this, so proceed on your own risk with this "guide". It worked for me and got me a running install of MIUI (chineese version).
Download the zip from here. There are two buttons to do so. This zip contains a set of scripts and resources to fix your phone.
Extract the zip to a folder somewhere.
Connect your softbricked phone with USB and make sure it is in fastboot mode and that your computer see it as a fastboot device (run "fastboot devices" in cmd and make sure the device shows up).
Run "flash_all.bat" from the extracted zip, if the script finishes successfully, skip to step 7.
For me the following lines failed when running the script:
Code:
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1
Delete or comment these lines from the script.
Run the script again. If it didn't work the first time, it hopefully worked now.
Reboot the phone if it does not do so itself. MIUI (chineese version) should now boot.
From here you should be able to enable developer options and ADB or boot into fastboot and flash new recovery images or whatever you want to do.
What caused the soft brick initially remains unclear to me, but this solved my problem and I am now running the ROM I wanted to run initially (Lineage for microG).
I hope this helps.

a

hannesknutsson said:
Run "flash_all.bat" from the extracted zip, if the script finishes successfully, skip to step 7.
For me the following lines failed when running the script:
Code:
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1
Delete or comment these lines from the script.
Click to expand...
Click to collapse
Hey, thanks for that. I tried that but I got some other error :
davinci_images_V12.1.1.0.RFJCNXM_20210221.0000.00_11.0_cn_c268db27f4\davinci_images_V12.1.1.0.RFJCNXM_20210221.0000.00_11.0_cn>fastboot flash sparsecrclist C:\Users\cbkra\Downloads\davinci_images_V12.1.1.0.RFJCNXM_20210221.0000.00_11.0_cn_c268db27f4\davinci_images_V12.1.1.0.RFJCNXM_20210221.0000.00_11.0_cn\images\sparsecrclist.txt ||
target reported max download size of 805306368 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.011s]
writing 'sparsecrclist'...
FAILED (remote: update sparse crc list failed)
finished. total time: 0.016s
"Flash sparsecrclist error"

It does not look like you deleted the lines I specified from the script. Are you sure you have deleted the lines:
Code:
fastboot %* flash crclist %~dp0images\crclist.txt || @echo "Flash crclist error" && exit /B 1
fastboot %* flash sparsecrclist %~dp0images\sparsecrclist.txt || @echo "Flash sparsecrclist error" && exit /B 1

I hadn't, but now I have. It seemed to worked fine until it got an unknown error.
sending sparse 'system' (774312 KB)...
OKAY [ 23.168s]
writing 'system'...
OKAY [ 0.002s]
sending sparse 'system' (774312 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 83.881s
"Flash system error"

From here I have no idea how to solve your problem.
I would just try running the same script a couple of more times, but that's just because I can't come up with something better to do.

hannesknutsson said:
From here I have no idea how to solve your problem.
I would just try running the same script a couple of more times, but that's just because I can't come up with something better to do.
Click to expand...
Click to collapse
Thank you for your help. I took it to a shop and that yielded the same result. They suggested the motherboard may have become faulty. I'll try again, thanks !

Yeah. If your anti rollback protection has triggered your phone may be bricked. I'm not sure how all that work, but that's what I understand of it.

Yeah the fix is actually to have the ROM and the MiFlash tool both on your C: drive for whatever reason.
Did work for me afterwards, without the Anti Rollback error

Only the path to the ROM is important : I always copy mine to C:\ but something simple like C:\TEMP\ should work too!
Avoid :
- Spaces in your path.
- Very long paths.
And you are good to go!
Also note that deleting lines in scripts can be dangerous and you should always tick the right options in the tool you are using!
Only Flash Custom ROMs via TWRP and Stock ROMs via the Mi Flash Tool

EDIT: I mistakenly thought this thread was talking about the Redmi 9T but it's for the Xaomi Mi 9T. So ignore all the links I pasted below as they are for the wrong phone.
Thanks so much for posting this I managed to recover my redmi 9t. I had to use the lime version of the firmware https://mifirm.net/download/6391 as opposed to the davinci version. Also I used official xiaomi flashing tool MiFlash20210813.zip from windows. It reset my phone to stock. I attempted to flash OrangeFox recovery again via OrangeFox-R11.1_2-Unofficial-avicii.zip and OrangeFox-R11.1_0-Unofficial-garden.zip as well as the latest beta from https://orangefox.download/device/garden and they all result in a fastboot loop.... I'm not really sure how to avoid it. Luckily it's easy to recover by flashing back just the recovery.img from the stock image, now that I've fully flashed the whole phone so I know which stock image to use.
UPDATE:
I just used twrp in the end as orangefox wasn't working for me, i would have liked to have used the "juice" version mentioned here https://forum.xda-developers.com/t/...t-r11-1-juice-lime-citrus-unofficial.4257459/ as the newer garden version wasn't working for me, but the files seem to have all disappeared in favor of the newer ones that don't work for me.

peter64 said:
Thanks so much for posting this I managed to recover my redmi 9t. I had to use the lime version of the firmware https://mifirm.net/download/6391 as opposed to the davinci version. Also I used official xiaomi flashing tool MiFlash20210813.zip from windows. It reset my phone to stock. I attempted to flash OrangeFox recovery again via OrangeFox-R11.1_2-Unofficial-avicii.zip and OrangeFox-R11.1_0-Unofficial-garden.zip as well as the latest beta from https://orangefox.download/device/garden and they all result in a fastboot loop.... I'm not really sure how to avoid it. Luckily it's easy to recover by flashing back just the recovery.img from the stock image, now that I've fully flashed the whole phone so I know which stock image to use.
UPDATE:
I just used twrp in the end as orangefox wasn't working for me, i would have liked to have used the "juice" version mentioned here https://forum.xda-developers.com/t/...t-r11-1-juice-lime-citrus-unofficial.4257459/ as the newer garden version wasn't working for me, but the files seem to have all disappeared in favor of the newer ones that don't work for me.
Click to expand...
Click to collapse
To avoid any confusion. Your post is about Redmi 9T (lime) - but this thread here is about Mi 9T/Redmi K20 (davinci)
Phones are different: firmwares, recoveries for one do not apply to the other
Different size, design, chipset, display, everything:
Compare Xiaomi Mi 9T vs. Xiaomi Redmi 9T - GSMArena.com
www.gsmarena.com
The corresponding XDA forum for your Redmi 9T:
Redmi 9 Power / 9T
The Redmi 9 Power is a 6.53" phone with a 1080x2340p resolution display. The Qualcomm SM6115 Snapdragon 662 chipset is paired with 4GB of RAM and 65/128GB of storage. The main camera is 48+8+2+2MP and the selfie camera is 8MP. The battery has a 6000mAh capacity.
forum.xda-developers.com

zgfg said:
To avoid any confusion. Your post is about Redmi 9T - this thread here is about Mi 9T.
These are totally different phones: firmwares, recoveries for one do not apply to the other
Different size, design, chipset, display, everything:
Compare Xiaomi Mi 9T vs. Xiaomi Redmi 9T - GSMArena.com
www.gsmarena.com
XDA Redmi 9T forum:
Redmi 9 Power / 9T
The Redmi 9 Power is a 6.53" phone with a 1080x2340p resolution display. The Qualcomm SM6115 Snapdragon 662 chipset is paired with 4GB of RAM and 65/128GB of storage. The main camera is 48+8+2+2MP and the selfie camera is 8MP. The battery has a 6000mAh capacity.
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, I totally missed that. It's good I noticed davinci wasn't the same as lime. I'll edit my comment to ensure I don't confuse anyone else unecessarily.