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.
Related
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.
Hello,
I have a Mi A1 since one week and I have already a large problem.
The problem began with a basic crash on an app (Facebook). The phone didn't respond and I turned off the phone.
When I turned on, the phone was stuck on the boot image (White screen with Mi Logo and Google colors). I tried to turn off and on several times but it didn't work.
I opened the phone and disconnected the battery but always the same problem.
Then, I booted the phone in fastboot and unlocked it via the command fastboot oem unlock. Then I tried to flash the stock ROM via fastboot. I choosed this version : Android 7.1.2 Nougat (N2G47H.7.12.7) because I had the last update (from : https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/).
Immediately i have this error :
Code:
fastboot flash modem_a C:\Users\Lau\Desktop\tissot_images_7.12.7_7.1\images\modem.img ||
target reported max download size of 536870912 bytes
sending 'modem_a' (86016 KB)...
OKAY [ 2.466s]
writing 'modem_a'...
FAILED (remote: flash write failure)
finished. total time: 2.499s
"Flash modem_a error"
I tried to flash with Miflash tool 2017.7.20 but I have the same message, Flash modem_a error.
I also tried to boot the phone in EDL Mode with fastboot_edl, the phone reboot, I have a message your device software cannot be checked for corruption and then the boot screen (with the messsage "Unlocked") and after 30 seconds, I have the black screen with the droid and "No command" (https://scache.vzw.com/kb/images/google/pixel/android_system_recovery_no_command.jpg )
Someone should have an idea to restore the phone ?!
Thanks a lot !
That screen with "No command" is usually related to the recovery. If I remember well, once in that screen, you have to press and hold power button for few seconds then press and release volume up button to enter in recovery. By reading your post I can see you didn't even try the most easy thing: A factory Reset! Try to wipe data from recovery if you can enter in it.
The modem error could be related at the fact that you're flashing a firmware that is not global or for your country. Try to change firmware version and make sure it is the right firmware region.
Inviato dal mio G8141 utilizzando Tapatalk
Thank for the quick answer.
I thinked to the recovery but I didn't know how to acces. With your help, I found and I made a wipe data. It made 5 minutes I have the message Formatting /data.... It seems too long... :/
EDIT : I stopped the wiping, it's seems it was block.
When you spoke of an other firmware, do have you a link ? Here is the information of my phone
Code:
xiaomi/tissot/tissot_sprout
71.2/N2G47H/7.12.19
This is a link to the October release of the Rom
https://androidfilehost.com/?fid=745849072291684522
This is a guide of how to flash it with Mi Flash Tool
https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548
If you are not able to flash with Mi Flash tool, try this guide to Flash manually via fastboot.
Once in fastboot (i suggest you to use the official one included in Android SDK becouse are the most updated ones and don't use some other installer like minimal. Add installer for Windows) follow this guide to Flash firmware images manually. It's for nexuses but the fastboot commands are universal
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Inviato dal mio G8141 utilizzando Tapatalk
Thank you for the link, that was I made.
I tried to flash manually the ROM with fastboot and I found a clue, the filesystem seems not normal...
I have this message :
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.009s
EDIT : And I have the last version of fastboot/adb from there : https://developer.android.com/studio/releases/platform-tools.html
lolo1410 said:
Thank you for the link, that was I made.
I tried to flash manually the ROM with fastboot and I found a clue, the filesystem seems not normal...
I have this message :
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.009s
EDIT : And I have the last version of fastboot/adb from there : https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
You must flash to system_a or system_b, "system" partition really doesn't exist.
Indeed, it's work now, it's flashing !
I noticed that for TWRP, there is also a "slot A" and "slot B". Is it new in Android ? Is there 2 kind of system ?
EDIT :
Unfortunately, it didn't work...
I had this message :
C:\adb_new>fastboot flash system_a system.img
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/6 (522959 KB)...
OKAY [ 15.867s]
writing 'system_a' 1/6...
FAILED (remote: flash write failure)
finished. total time: 15.898s
And here is the log for Miflash :
Code:
[16:52:10 28ba25530704]:MiFlash 2017.7.20.0
[16:52:10 28ba25530704]:image path:C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1
[16:52:10 28ba25530704]:env android path:"C:\Users\Lau\Desktop\miflash\Source\ThirdParty\Google\Android"
[16:52:10 28ba25530704]:script :C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1\flash_all_except_storage.bat
[16:52:10 28ba25530704]:Physical Memory Usage:1355776 Byte
[16:52:10 28ba25530704]:$fastboot -s 28ba25530704 getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
[16:52:10 28ba25530704]:product: tissot
[16:52:10 28ba25530704]:$fastboot -s 28ba25530704 oem unlock ||
[16:52:11 28ba25530704]:...
[16:52:11 28ba25530704]:$fastboot -s 28ba25530704 flash modem_a C:\Users\Lau\Downloads\tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf\tissot_images_7.12.19_7.1\images\modem.img ||
[16:52:11 28ba25530704]:(bootloader) Device already : unlocked!
[16:52:11 28ba25530704]:eek:KAY [ 0.030s]
[16:52:11 28ba25530704]:finished. total time: 0.030s
[16:52:13 28ba25530704]:target reported max download size of 536870912 bytes
[16:52:13 28ba25530704]:sending 'modem_a' (86016 KB)...
[16:52:13 28ba25530704]:error:"Flash modem_a error"
[16:52:13 28ba25530704]:"Flash modem_a error"
[16:52:13 28ba25530704]:error:"Flash modem_a error"
[16:52:13 28ba25530704]:process exit.
[16:52:13 28ba25530704]:flashSuccess False
[16:52:13 28ba25530704]:isFactory False CheckCPUID False
[16:52:13 28ba25530704]:before:flashSuccess is False set IsUpdate:True set IsDone True
[16:52:13 28ba25530704]:after:flashSuccess is False set IsUpdate:false set IsDone true
Can you boot into TWRP (use version 3.1.1-0 or 3.1.1-1 "fastboot boot twrp.img")? Do you see /data partition?
Yes I can boot into but I can't install it. Before I tried to flash manually, I was able to unlock the data partition but not anymore (Error : E: Decrypt took too long, killing process - Failed to decrypt data)
I have an access with adb shell.
Some people had luck with flashing persist.img from August update, you might try that as well. There is also a chance that your flash memory is damaged and you will need to visit a service center.
Okay try this.
Download the latest build (android n) from mi firmwares official page.
Unzip the file (http://en.miui.com/forum.php?mod=viewthread&tid=1415168&extra=page=1&mobile=2)
Download miflashtool (http://en.miui.com/thread-807252-1-1.html)- guide & tool.
Past the path in the tool.
Click refresh
Click flash
Boom your good.
Make sure to select clean flash and lock.
ADB and fastboot should be installed.
_mysiak_ said:
Some people had luck with flashing persist.img from August update, you might try that as well. There is also a chance that your flash memory is damaged and you will need to visit a service center.
Click to expand...
Click to collapse
I flashed "persist.img" succesfully but always the same problem, stucked on Boot...
zeyaan said:
Okay try this.
Download the latest build (android n) from mi firmwares official page.
Unzip the file (http://en.miui.com/forum.php?mod=viewthread&tid=1415168&extra=page=1&mobile=2)
Download miflashtool (http://en.miui.com/thread-807252-1-1.html)- guide & tool.
Past the path in the tool.
Click refresh
Click flash
Boom your good.
Make sure to select clean flash and lock.
ADB and fastboot should be installed.
Click to expand...
Click to collapse
I already tried several times but I have always errors (See log of previously post). With Miflash, I succeeded to flash the 2 boot et 2 system but phone is always blocked.
I tried to wipe via TWRP but it blocks on "Formatting Data using make_ext4fs...".
I think I'm good to send it at a service center...
There's a TWRP backup of first beta build oreo.Try restoring it.
Same Problem.
inally he managed to flash the ROM action, thank you very much to everyone for your patience and help, especially PALMATRON and fosco_
He used the tutorial of this link: https://xiaomifirmware.com/roms/down...-xiaomi-mi-a1/
1. Tools Download r26 for Windows.
2. Unzipped the instruments on disk C of my computer.
3. Unzipped the files of the last ROM available for the Xiaomi Mi A1 in the folder C: \ Tools so that the Images folder and the flashing scripts that come with the ROM are included in it.
4. Then double click on flash_all.bat to delete everything and just leave the boot loader open.
5. Automatically start flashing and take about 10-15 minutes and voila!
https://uploads.tapatalk-cdn.com/20171123/37d3867bf5d0fb7967a03a05869914ae.jpg
Try do with clean and lock or just clean i was have the same problem and i fix this only with miflash and after when my mi a1 restarts on boot i copy with terminal persist.img
thanks a lot
Saved my life, thanks. The rom on this link works PERFECTLY - my Mi A1 was stuck on botlooping after a fail tentative to root it.
XDVRMX said:
This is a link to the October release of the Rom
https://androidfilehost.com/?fid=745849072291684522
This is a guide of how to flash it with Mi Flash Tool
https://forum.xda-developers.com/mi-a1/how-to/rom-factory-images-t3688548
If you are not able to flash with Mi Flash tool, try this guide to Flash manually via fastboot.
Once in fastboot (i suggest you to use the official one included in Android SDK becouse are the most updated ones and don't use some other installer like minimal. Add installer for Windows) follow this guide to Flash firmware images manually. It's for nexuses but the fastboot commands are universal
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Inviato dal mio G8141 utilizzando Tapatalk
Click to expand...
Click to collapse
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.
Hi guys,
i was on Miui Global 10.xxxx (dont know exactly)
bootloader was unlocked.
Rollback protection target was 1
my recovery was Orangefox recovery (https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899)
I have made a full backup of all partitions before.
I wanted to flash Miui 11.0.4.0 global to flash a custom rom.
First i flashed recovery and installed the recovery.zip.
That worked fine.
Then i wanted to flash Miui 11.0.4.0 with this instructions for a clean flash:
1. If you're coming from another ROM or need to perform a clean flash:
Boot into Recovery
Wipe Data/Cache/System
Flash vendor/firmware (Global 11.0.4.0 recommended)
Flash ROM
(Optional) Flash Gapps (not included!)
(Optional) Flash the latest Magisk
Reboot
Enjoy
This instructions are from here: https://forum.xda-developers.com/mi-9t/development/rom-stagos-t4072637
So, i was in recovery, and deleted data, cache and system.
Then i restarted the phone to go to recovery, but that didnt work.
It stucked in bootloop.
I now reinstalled Adb and fastboot, and erased recovery and System partition.
There were much errors in time due old adb and fastboot version etc....
But now iam at this point here again.
wait for your answers how to continue.....
It looks like just flashing or booting recovery is not possible without system partition.
It's now too late and sorry I don't want to risk to give you the wrong instructions how to unbrick
But for the others to avoid similar brick:
1) You say you were on Global MIUI 10 and you wanted to update to MIUI 11.
If so, why didn't you simply update by OTA?
2) If for some reason you were not able to apply OTA, but if you were really on Global (not on custom ROM, Indian ROM or so) and wanted to update also to Global (not switching to EU weekly or so), then you shouldn't wipe anything
You had to flash the stock Recovery back, to download the Global recovery/zip package you wanted to update to, and to force update from System Update: (so called Local Update):
https://c.mi.com/oc/miuidownload/detail?guide=1
Now, once you wiped things and bricked, I don't know but you could check the Fastboot method:
https://c.mi.com/oc/miuidownload/detail?guide=2
If reading from mobile phone, force Desktop site in browser for the two links anove
1. When you make format data, than reboot in twrp again
2.when boot second time, wipe data, dalvick, cache, system...and flash new rom.
If you wipe system partition and reboot in twrp again without system, you get fastboot.
zgfg said:
It's now too late and sorry I don't want to risk to give you the wrong instructions how to unbrick
But for the others to avoid similar brick:
1) You say you were on Global MIUI 10 and you wanted to update to MIUI 11.
If so, why didn't you simply update by OTA?
2) If for some reason you were not able to apply OTA, but if you were really on Global (not on custom ROM, Indian ROM or so) and wanted to update also to Global (not switching to EU weekly or so), then you shouldn't wipe anything
You had to flash the stock Recovery back, to download the Global recovery/zip package you wanted to update to, and to force update from System Update: (so called Local Update):
https://c.mi.com/oc/miuidownload/detail?guide=1
Now, once you wiped things and bricked, I don't know but you could check the Fastboot method:
https://c.mi.com/oc/miuidownload/detail?guide=2
If reading from mobile phone, force Desktop site in browser for the two links anove
Click to expand...
Click to collapse
Sooo....after hours of reading with errors over errors and fixing, it still doesnt work.
First i tried to flash everything via mi flashtool.
There was an error: Antirollbackcheck Error.
https://www.reddit.com/r/Xiaomi/comments/d0xmbp/what_on_earth_is_miflash_antirollback_check_error/
https://xiaomi.eu/community/threads...nd-flashing-recovery-fails-please-help.51349/
To fix this i had to move the Tool and the rom into my C hard drive next to program etc folders...
Then i editet the flashall.bat file and removed the rollbackcheck lines.
Now after doing this, it flashed for 100 seconds, and then there was this error: Failed to flash dtbo.img
sooo....Then i tried to flash the dtbo.img and all the other ones via Minimal adb and fastboot.
https://forum.xda-developers.com/mi-9t/help/flash-stuck-fastboot-soft-brick-t3962662/page3
And this didnt work for me too. Everytime if i try to flash dtbo.img, this error comes:
target didnt report max-download-size
sending dtbo (32768KB)....
FAILED (command write failed (no error))
finished.
Now everything is like before....
Flash twrp and boot in twrp. After phone boot in twrp, make format data. After format, make reboot to recovery.
When booot in twrp, wipe data, dalvick, cache, system , copy Miroom to internal and flash ROM.
Use this twrp...
https://app.box.com/s/8lkfbft44vldtt0y8kwhe6un87b5ebzx
And this rom.
https://sourceforge.net/projects/mi...edmiK20_MIUI_20.3.26_MiRoom_10.0.zip/download
Sent from my MI 9T using Tapatalk
Kidence said:
Flash twrp and boot in twrp. After phone boot in twrp, make format data. After format, make reboot to recovery.
When booot in twrp, wipe data, dalvick, cache, system , copy Miroom to internal and flash ROM.
Use this twrp...
https://app.box.com/s/8lkfbft44vldtt0y8kwhe6un87b5ebzx
And this rom.
https://sourceforge.net/projects/mi...edmiK20_MIUI_20.3.26_MiRoom_10.0.zip/download
Sent from my MI 9T using Tapatalk
Click to expand...
Click to collapse
C:\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-12-davinci-mauronofrio.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.914s]
writing 'recovery'...
OKAY [ 0.151s]
finished. total time: 2.065s
C:\Minimal ADB and Fastboot>fastboot boot recovery
error: cannot load 'recovery': No such file or directory
C:\Minimal ADB and Fastboot>fastboot boot twrp-3.3.1-12-davinci-mauronofrio.img
downloading 'boot.img'...
OKAY [ 1.891s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.900s
When you flash recovery, hold volume up and type in adb
fastboot reboot
After that, phone will be boot in twrp
Sent from my MI 9T using Tapatalk
FINALLY it worked YES
FIRST: The Story for everybody who has the same problem like me:
Device: Xiaomi Mi 9T
Firmware: MIUI 10 GLOBAL
Antirollbackprotectioncounter: 1
Bootloader: Unlocked
Story:
At the beginning, everything was working, but i wanted to install a custom rom (STAGOS)
For this step, i had to Update my Miui firmware on 11.0.4.0.
But this step didnt work so well via device OTA (error), then i decided to install it via custom recovery.
I still had the stock recovery on my device, so i went in fastboot mode, and installed Orangefox recovery via ADB and Fastboot on Windows. That worked without problems.
In Orangefox, i wiped as sayed in instructions data, cache and System. then i rebooted.
But before realised that was the wrong way, i stucked in fastboot.
No tools helped. ADB and Fastboot didnt work as seen in screenshots.
I tried everything via fastboot....
fastboot flash recovery XXX.img
fastboot boot XXXX.img
Fastboot format.....etc
But NOTHING worked. Everytime there were the following errors:
Target didnt report Max download size
Error: Cannot load recovery
No such file or directory
Error: Download size is higher that allowed
Failed to load boot image (Load error)
Command write failed (no error)
and some other ones too.....
It looked like, some flashes worked and some not. Sometimes it worked, sometimes not.
After some new tries it just showed via the command: Fastboot devices
????????? fastboot
That problem has been solved. Just unplug the device and wait for 10 minutes until it shuts down automatically.
If that doesnt work, you can try to replug it to pc some times again.
It looked like replugging and using different USB Port (one user solved the problem via USB 2.0) helps to get a better connection and prevent errors.
Then i tried some tools, for example android all in one tool, but no one worked.
After this, i reinstalled the driver and installed MI Flash tool (https://mi-globe.com/download-xiaomi-mi-flash-tool-all-versions/)
It looks like there are some mi flash tools around here which are not working right, but THIS one worked for me.
After installing, i connected my device, choosed the fastboot firmware (.tgz), unpacked it and choosed the right location in mi Flash tool.
Firmware files are find here: https://c.mi.com/oc/miuidownload/detail?guide=2
(You should check you Antirollback counter before to avoid a brick. Here you find some informations: https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/)
DONT FORGET TO CHOOSE IN THE RIGHT DOWN CORNER: CLEAN ALL !!! (normally, clean all and lock is choosen, but that bricks your device)
After doing this, i started flashing, but there was an error: Antirollbackcheck error.
I solved it via moving the mi flashtool directly into my C hard drive, and deleted some lines in the flashall.bat, as seen in post history here.
Then....it worked for some seconds longer, but than: Error: Failed to flash dtbo.img
So i tried it via ADB and Fastboot. But nothing changed.
Then i tried flashing via mi Flash tool again, and this time the following error comes: Failed to flash system.img.
After this is thought: hmmm....something is very wrong with this device....lets try again, after a device restart.
So i tried again, let it running for ~360 seconds, and IT WORKED!
At the End: there was the following error: Error: Not catch checkpoint.
But this error (you can also see in a screenshot) it not necessary.
This is the result of removing some lines in flashall.bat.
After this my phone successfully booted im Miui 11.
Hey guys, I need help with this Asus Zenfone 2 Laser that:
Cannot boot to any OS (asus logo pops up, freezes, and then a blue screen flashes for a really short period, before it powers off, see video here.)
Can't download the unlock app to unlock bootloader
Can't access ADB
Cannot access Recovery mode
Can't "factory reset", apply update over ADB, etc.
Bootloader is locked
Can't flash custom recovery, boot TWRP, or really anything...
See fastboot reference below for more info
Code:
$ fastboot boot twrp-3.7.0_9-0-Z00T.img
Sending 'boot.img' (31066 KB) OKAY [ 0.987s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
$ fastboot flash recovery twrp-3.7.0_9-0-Z00T.img
Sending 'recovery' (31066 KB) OKAY [ 0.987s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flash boot boot.img # (Original boot.img from factory image)
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 17980722).
Sending 'boot' (17559 KB) OKAY [ 1.478s]
Writing 'boot' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem device-info
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.003s]
Finished. Total time: 0.003s
As someone who has only worked with Google Pixel phones in the past, I'm very frustrated for a few reasons.
Firstly, why the hell is the ONLY WAY to unlock a bootloader through an app that was released in such a clandestine, under-the-table way?
Second, why is the manufacturer gatekeeping the recovery files? The only way I was able to find the stock recovery.img is through a comment on a Reddit post (ironically posted by an ASUS Employee).
Third, I've been scouring the internet for many, many days trying to find any kind of emergency recovery method, but every single tutorial acts on the assumption that the bootloader is unlocked, and that boot.img, recovery.img, etc. can be flashed.
Enough about the frustration. Now let's talk about what I've tried so far.
I tried ASUS Flash Tool (Finding ADB drivers was a whole different fiasco for this device), and came up empty handed, as it doesn't detect the device when in fastboot mode.
I tried using fastboot to flash boot, recovery, system, fastboot, and dnx/ifwi, to no avail.
I tried booting into recovery via `fastboot reboot recovery`, `fastboot reboot-recovery`, `fastboot oem reboot-recovery`, and by holding Vol Down while booting up. They all give the same result, which is just an instant (<1 second) reboot. My best guess is that recovery.img is either missing or badly corrupt, so the bootloader just gives up and exits immediately.
Please help. I don't want an expensive paperweight sitting in my drawer just because of a bootloop that wasn't my fault (seriously this device just bootlooped itself one day, I didn't flash a custom rom, root or anything like that).
Any help is appreciated,
Thanks in advance
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
alecxs said:
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
Click to expand...
Click to collapse
Probably a dumb question, but how can I put my device into EDL mode?
I've tried many key combinations in conjunction with plugging it into the computer, and I've tried connecting it without a battery.
if nothing else works you need to figure out test points
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87944673
you still have fastboot? try this for EDL mode.
Code:
fastboot oem enter-dload
Good news and bad news. Good news is: I was able to enter EDL mode.
Bad news is, apparently my entire partition scheme was messed up, and upon running "edl w gpt gptboth0.bin", fastboot no longer works.
I have tried flashing aboot using edl ("edl w aboot emmc_appsboot.mbn") and it's not working.
Not to mention that it is almost impossible to find the firmware file with all the factory files such as "emmc_appsboot.mbn". The place where I got my file seemed very sketchy and I'm not surprised if the reason it's not working is because it's the wrong file.
Once again, this is a result of ASUS gatekeeping their recovery files to service centers to drive up repair sales.
If anyone has a link, or would like to provide a donor file, it would be VERY much appreciated.
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
alecxs said:
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
Click to expand...
Click to collapse
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
OS were
sj-dan said:
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
Click to expand...
Click to collapse
So we're you able to find a fix in any way? I find myself in just about the same situation tho for different reasons. I have a radiant max 5g att device i moronicaly tried to download a gsi using the dsu updater, but forgot to unlock bootloader or even enable USB debugging before attempt. So OS system is crashing an saying 'device corrupted' on boot attempt. Recovery mode gets the same result. Was able to use the bugjaegar app to connect ad run the bootloader but every repair attempt is blocked by the fact the USB debugging isn't on. To make matters worse I accidentky hit boot fastbootd command instead of normal and whatever that did wiped out my ability to even connect with bootloader so I'm kind of stuck.
faisaliteb said:
Mod. edit: spammer gone. alecxs
I found many tutorials about fixing bootloops on the Nexus but they all seem to require an unlocked bootloader.
The bootloader on the device is locked. I can see the device in fastboot devices but I can't unlock it.
Any idea how to repair this? Can I somehow flash a factory image onto the device even though OEM unlock is disabled? There is no data on the device that would need to be preserved. I'm ideally looking for a Linux-based solution. more info... ***
Click to expand...
Click to collapse
Yeah man I've been looking at this problem for over a week now and can't find much online at all to help. Except for this EDLmode some devices can boot into, and apparently you can flash a locked system using this emergency download mode. I dunno still researching.