Related
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
So I've recently unlocked the bootloader of my global Mi 9T, I want to install twrp recovery but when I flash it my phone gets stuck in fastboot mode. I can't boot into recovery (stock nor twrp) or I'm not able to boot into system. Restored via fastboot rom and attempted it again and still the same thing happened. What am I doing wrong?
PHP:
when flashing twrp I get successful flash but it's not there and I'm stuck in fastboot
i flashed twrp via fastboot and then i click directly vol up and power and i come in twrp.
Verstuurd vanaf mijn ONEPLUS A5010 met Tapatalk
Flash 4pda davinci-fix recovery by click flashtwrp.bat
It worked for me when i fall in same issue
Hey Guys,
I'm stuck and need help. I've unlocked my phone and installed the PDA4 TWRP. Then I wanted to flash the AndroidParanoid ROM.
Before I could flash it, i had to format data.
Then I sideloaded the zip file via ADB to the phone and restarted
And now all I can do is get into fastboot. When I install TWRP again, the phone hangs at the MI splashscreen.
No clue what to do, as I cannot find a fastboot ROM for my global / europe Mi 9T.
Any help is welcome.
ferretmc said:
Hey Guys,
I'm stuck and need help. I've unlocked my phone and installed the PDA4 TWRP. Then I wanted to flash the AndroidParanoid ROM.
Before I could flash it, i had to format data.
Then I sideloaded the zip file via ADB to the phone and restarted
And now all I can do is get into fastboot. When I install TWRP again, the phone hangs at the MI splashscreen.
No clue what to do, as I cannot find a fastboot ROM for my global / europe Mi 9T.
Any help is welcome.
Click to expand...
Click to collapse
for firmware use https://mifirm.net/
for the recovery issue i tried this and it worked https://forum.xda-developers.com/showpost.php?p=80123401&postcount=100
beaverhead said:
i flashed twrp via fastboot and then i click directly vol up and power and i come in twrp.
Verstuurd vanaf mijn ONEPLUS A5010 met Tapatalk
Click to expand...
Click to collapse
For me, I flashed twrp via fastboot, phone booted directly into fastboot. Even vol+ and power button booted right back to fastboot. I had to restore using fastboot rom
memox44 said:
Flash 4pda davinci-fix recovery by click flashtwrp.bat
It worked for me when i fall in same issue
Click to expand...
Click to collapse
Going to try when I get home
I'm stuck and need help. I've unlocked my phone and installed the PDA4 TWRP. Then I wanted to flash the AndroidParanoid ROM.
Before I could flash it, i had to format data.
Then I sideloaded the zip file via ADB to the phone and restarted
And now all I can do is get into fastboot. When I install TWRP again, the phone hangs at the MI splashscreen.
No clue what to do, as I cannot find a fastboot ROM for my global / europe Mi 9T.
Click to expand...
Click to collapse
when you flash paosp tou have to flash dtbo.img before reboot to system
@edcedcedc Thank you so much! I didn't find that page through Google. Downloaded the fastboot-rom and flashed it with the Mi-Flash tool.
Then MIUI came up and I coul start from scratch.
Flashing TWRP with the BAT file several times didn't work when I was stuck in fastboot. As soon as MIUI was installed it worked first time I tried.
Again, thank you so much
Ok, Same happened to me But I only have Mac any hint?
I'm downloading the .tgz file stock rom. Is there a way to do this on a MAC?
I got the same.
Have you fixed this problem ?
Hi, Possibly noob question here...
I have successfully unlocked the bootloader on my redmi 9T (mi 9T) and downloaded the corresponding twrp, it flashed successfully and returned the output
Sending 'recovery' (65536 KB) OKAY [ 1.985s]
Writing 'recovery' OKAY [ 0.258s]
Finished. Total time: 2.261s
however, I got stuck on fastboot mode, tried "fastboot reboot" command as well as using hardware keys but it boots into fastboot mode again
how can I get out of the fastboot mode or at least recover the phone to the factory state
MukbanianiDavit said:
Hi, Possibly noob question here...
I have successfully unlocked the bootloader on my redmi 9T and downloaded the corresponding twrp, it flashed successfully and returned the output
Sending 'recovery' (65536 KB) OKAY [ 1.985s]
Writing 'recovery' OKAY [ 0.258s]
Finished. Total time: 2.261s
however, I got stuck on fastboot mode, tried "fastboot reboot" command as well as using hardware keys but it boots into fastboot mode again
how can I get out of the fastboot mode or at least recover the phone to the factory state
Click to expand...
Click to collapse
Are you talking about Redmi 9T or Mi 9T (aka Redmi K20, davinci) - this is the forum for Mi 9T (not for Redmi 9T)
They are different phones, make sure you flash the correct TWRP (do not flash TWRP for Mi 9T to your Redmi 9T or vice versa)
zgfg said:
Are you talking about Redmi 9T or Mi 9T (aka Redmi K20, davinci) - this is the forum for Mi 9T (not for Redmi 9T)
They are different phones, make sure you flash the correct TWRP (do not flash TWRP for Mi 9T to your Redmi 9T or vice versa)
Click to expand...
Click to collapse
Yeah sorry, however, I could not possibly get out of the loop so I had to flash stock ROM to be able to use my phone.
You need to wipe data and internal storage after installing TWRP and reboot. Happened to me too.
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.
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.
Hello,
I have a Nothing Phone 1 that hangs in bootloader/fastboot mode.
The bootloader is unlocked.
Unfortunately, the phone can no longer be booted into recovery mode.
With fastboot the device is still recognized.
So you could still flash files via fastboot.
The phone was not rooted.
The phone previously ran with the original stock firmware 1.1.7 hotfix.
It is an EEA device.
Is there anything that can be done?
Or is it now an expensive paperweight?
Try running "fastboot reboot recovery" in the terminal with your phone connected.
Unfortunately this does not work.
Thanks for the quick reply.
The device then boots back into the bootloader
It looks like they have Nothing OS downloads here. You could just try reflashing the phone through fastboot.
Looks like someone else is having the same problem. Keep an eye on that thread in case a solution comes up there.
so, i have the unpacked payload.bin image files. Here fastboot tells me several errors with odm.img FAILED (remote: '(odm_b) No such partition'), with product.img FAILED (remote: 'Partition not found'), with system.img FAILED (remote: 'Partition not found'), with system_ext.img FAILED (remote: '(system_ext_b) No such partition') and with vendor.img FAILED (remote: 'Partition not found').
After a restart, the error remains.
There is also the fastbootD mode, but this does not work or does not boot.
After this command the device hangs in bootlogo (nothing).
Unfortunately very sad that there is still no solution for this. let's hope that there is soon a solution for this.
Sapphire86 said:
so, i have the unpacked payload.bin image files. Here fastboot tells me several errors with odm.img FAILED (remote: '(odm_b) No such partition'), with product.img FAILED (remote: 'Partition not found'), with system.img FAILED (remote: 'Partition not found'), with system_ext.img FAILED (remote: '(system_ext_b) No such partition') and with vendor.img FAILED (remote: 'Partition not found').
After a restart, the error remains.
There is also the fastbootD mode, but this does not work or does not boot.
After this command the device hangs in bootlogo (nothing).
Unfortunately very sad that there is still no solution for this. let's hope that there is soon a solution for this.
Click to expand...
Click to collapse
Type "fastboot reboot fastboot" in the terminal, with your phone connected, and then run "fastboot flash <yourimagename>.img".
yes, when i enter this command the device restarts and hangs in the bootlogo and in the terminal it says then wait for any device. That means the Nothing Phone does not start the fastbootD mode.
And if he doesn't do this, I think it looks really bad.
Are you using Windows to flash it?
Yes windows 11 with the latest drivers, but I have already considered using linux.
Which linux distribution would be best. Then I will download it and try it out.
I would recommend Ubuntu, if you have a spare computer to install it on (or dual boot). Just make sure you install the tools needed from here (Scroll down to the "Command line tools only" section and download the Linux version)
I only use Linux, so let me know if you have any questions.
Ok thanks. I will have a look and install it on a notebook later.
You have to be very careful. I had the same problem (bootloop in fastboot) and by dint of manipulation, no more fastboot, my smartphone is hard brick (black screen with logo and message key to shutdown)
ziptric1805 said:
You have to be very careful. I had the same problem (bootloop in fastboot) and by dint of manipulation, no more fastboot, my smartphone is hard brick (black screen with logo and message key to shutdown)
Click to expand...
Click to collapse
If your phone has a Qualcomm processor, you still have EDL mode.
It is not bricked. Just flash any cutom rom, I recommend Paranoid Android. Then revert back to stock NOS.
@MakDroid
I just installed Topaz 1 (A13) to save my bricked phone. How can i revert back to stock NOS from A13? There is any option or i have to wait for full rom with A13?
Ostry10 said:
@MakDroid
I just installed Topaz 1 (A13) to save my bricked phone. How can i revert back to stock NOS from A13? There is any option or i have to wait for full rom with A13?
Click to expand...
Click to collapse
Download NOS 1.1.7 full from here.
Extract payload.bin and place all the extracted .img files inside a folder named "images".
Copy the images folder and the attached bat file (extract the zip to get the bat file) to the platform-tools folder.
Run the bat file and it will start flashing. Wait for it to complete and then simply update to latest version using stock updater.