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

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.

Related

Need help, tried to flash and now NP stuck at Google boot screen with unlock icon

Hello,
I'll start off by apologizing for being a noob. I tried to follow the instructions found here but somehow I got stuck in a state where my NP won't boot up. It is stuck at the Google black screen with an unlock icon. I tried to flash the 2.1 Lollirock rom and now i'm stuck in this state.
I have the NP plugged in and can get to the bootloader screen but I can't seem to figure out how to fix this. I downloaded the boot.img and system.img files from the Lollirock XDA page.
Steps I did:
At the bootloader page -
1) fastboot oem unlock (twice)
2) the bootloader screen then said it was unlocked
3) flashboot boot boot.img
4) flashboot flash system system.img
5) flashboot -w
Everything was successful with no errors so I put enabled Normal Boot in the bootloader and it just sits at the Google screen for about a minute and loops.
I tried to download fugu-lmy48n-factory-3b9d8638.tgz from the nexus stock image page and tried flashboot flash system fugu-lmy48n-factory-3b9d8638.tgz and got the error:
< waiting for device >
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.223s]
sending 'system' (457721 KB)...
OKAY [ 16.014s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 18.417s
I unzipped the TGZ file and tried with the TAR file and got the same error.
Then I flashed CM Recovery and that worked and I can get into CM Recovery thinking I can just update with the CM12.1 rom. The problem is that I don't have the zip on the device's sd card so I had to push from ADB by doing -
ADB sideload cm-12.1-20150520-UNOFFICIAL-fugu.zip
and it starts and goes for about 46% and stops with CM Recovery stating:
E: Failed to verify whole-file signature
E: signature verification failed
Installation aborted.
I googled this and people said to turn off signature verification since most roms are signed but I can't find any instructions on how to do that....
I also found an OTA zip of 6.0 and when updating from CM via ADB sideload, it gives me the error:
E: Error in /sideload/package.zip
(Status 7)
So that's where I'm at....not sure what to do next so any help you guys can provide would GREATLY be apprciated. Thanks!!!
Disregard, I think I got it figured out. I guess I was in stock recover and not in CM Recovery. Flashed CM Recovery again and I was able to flash CM12.1. RIght now it's sitting at the loading screen with the happy blue android face.

Phone bricked after a crash - Flash modem_a error

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

Can't flash TWRP Recovery .img!

Hi everyone, so i created a post early today but I think it was't really clear so I deleted it and make a new one due to the lack of answers in the last one. Anyhow let0s get down to business (lol), this is what I did:
1) entered fastboot mode using ./adb reboot bootloader
2)unlocked OEM using ./fastboot oem unlock [unlock code]
..and these first two steps went
through perfectly with no
problems...
3) tried to flash twrp.img using ./fastboot flash recovery (name).img
4) rebooted using ./fastboot reboot
At first it seemed everything went straight through but apparently not because as soon as I tried o enter recovery mode it loads me into the usual warning screen that "your device is unlocked and it is not trusted.." and bla bla bla... and it gets stuck at "Your system is rebooting..." and I also left it there for 2 hours but still nothing happened. So what I tried is doing the whole process again from the flash .img part, this time with the verbose option though and this is what it output:
./fastboot flash recovery -v twrp-3.1.0-0-vtr.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "Command not allowed"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "471859200"
fastboot: verbose: target reported max download size of 471859200 bytes
Sending 'recovery' (32034 KB)
fastboot: verbose: sending command "download:01f48800"
fastboot: verbose: received DATA 01f48800
fastboot: verbose: sending data (32802816 bytes)
fastboot: verbose: received OKAY ""
OKAY [ 1.238s]
Writing 'recovery'
fastboot: verbose: sending command "flash:recovery"
fastboot: verbose: received OKAY ""
OKAY [ 0.236s]
Finished. Total time: 1.489s
Now I do see that there is a problem in the first two lines but HELL NO if I know a way to fix it, I don't even know why it is giving me that error. Anyhow it has just not yet finished because any ./fastboot command from then on just freezes on the first output line for example:
./fastboot boot -v twrp-3.1.0-0-vtr.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:01f48800"
^C
pbalatform-tools Andrea$ ./fastboot reboot
Rebooting ^C
pbalatform-tools Andrea$
And before terminating the commands I waited several minutes but sill nothing happened! What is possibly wrong?
I have got a Huawei P10 Lite (obvsly) with EMUI 5.1.
Actually there is one more wierd thing: I once installed a different type of TWRP from these forums, it was still the same version but i guess it was from a CATUVA's post as it was called TWRP 3.1.1.0 NOUGAT BY CATUVA21 P10LITE.img. Anyhow I flashed this .img and it literally did as always. By mistake I actually clicked on the update software from the settings on my huawei and rebooting normally to install the update it got me magicaly into the TWRP Catuva's recovery mode. Basically it never did the update and I was able to get back there in recovery mode just by trying to update my software again from settings. I tried every other way to access it but it just wouldn't go in TWRP: I tried also Power+Vol Up+Vol Dwn but it got me into the normal Emui 5.1. And after all these attempts I tried again getting into it with the try updating system and it got me back in... why the hell should he let me in just this way? I flashed another .img and the update thing just doesn't do anymore the trick.
HELP!!
Peskyleo said:
Hi everyone, so i created a post early today but I think it was't really clear so I deleted it and make a new one due to the lack of answers in the last one. Anyhow let0s get down to business (lol), this is what I did:
1) entered fastboot mode using ./adb reboot bootloader
2)unlocked OEM using ./fastboot oem unlock [unlock code]
..and these first two steps went
through perfectly with no
problems...
3) tried to flash twrp.img using ./fastboot flash recovery (name).img
4) rebooted using ./fastboot reboot
At first it seemed everything went straight through but apparently not because as soon as I tried o enter recovery mode it loads me into the usual warning screen that "your device is unlocked and it is not trusted.." and bla bla bla... and it gets stuck at "Your system is rebooting..." and I also left it there for 2 hours but still nothing happened. So what I tried is doing the whole process again from the flash .img part, this time with the verbose option though and this is what it output:
./fastboot flash recovery -v twrp-3.1.0-0-vtr.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "Command not allowed"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "471859200"
fastboot: verbose: target reported max download size of 471859200 bytes
Sending 'recovery' (32034 KB)
fastboot: verbose: sending command "download:01f48800"
fastboot: verbose: received DATA 01f48800
fastboot: verbose: sending data (32802816 bytes)
fastboot: verbose: received OKAY ""
OKAY [ 1.238s]
Writing 'recovery'
fastboot: verbose: sending command "flash:recovery"
fastboot: verbose: received OKAY ""
OKAY [ 0.236s]
Finished. Total time: 1.489s
Now I do see that there is a problem in the first two lines but HELL NO if I know a way to fix it, I don't even know why it is giving me that error. Anyhow it has just not yet finished because any ./fastboot command from then on just freezes on the first output line for example:
./fastboot boot -v twrp-3.1.0-0-vtr.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:01f48800"
^C
pbalatform-tools Andrea$ ./fastboot reboot
Rebooting ^C
pbalatform-tools Andrea$
And before terminating the commands I waited several minutes but sill nothing happened! What is possibly wrong?
I have got a Huawei P10 Lite (obvsly) with EMUI 5.1.
Actually there is one more wierd thing: I once installed a different type of TWRP from these forums, it was still the same version but i guess it was from a CATUVA's post as it was called TWRP 3.1.1.0 NOUGAT BY CATUVA21 P10LITE.img. Anyhow I flashed this .img and it literally did as always. By mistake I actually clicked on the update software from the settings on my huawei and rebooting normally to install the update it got me magicaly into the TWRP Catuva's recovery mode. Basically it never did the update and I was able to get back there in recovery mode just by trying to update my software again from settings. I tried every other way to access it but it just wouldn't go in TWRP: I tried also Power+Vol Up+Vol Dwn but it got me into the normal Emui 5.1. And after all these attempts I tried again getting into it with the try updating system and it got me back in... why the hell should he let me in just this way? I flashed another .img and the update thing just doesn't do anymore the trick.
HELP!!
Click to expand...
Click to collapse
Flashing twrp has only ever worked for me if I immediately go into it I have never been able to get it to stick around after a restart
Peskyleo said:
Hi everyone, so i created a post early today but I think it was't really clear so I deleted it and make a new one due to the lack of answers in the last one. Anyhow let0s get down to business (lol), this is what I did:
1) entered fastboot mode using ./adb reboot bootloader
2)unlocked OEM using ./fastboot oem unlock [unlock code]
..and these first two steps went
through perfectly with no
problems...
3) tried to flash twrp.img using ./fastboot flash recovery (name).img
4) rebooted using ./fastboot reboot
At first it seemed everything went straight through but apparently not because as soon as I tried o enter recovery mode it loads me into the usual warning screen that "your device is unlocked and it is not trusted.." and bla bla bla... and it gets stuck at "Your system is rebooting..." and I also left it there for 2 hours but still nothing happened. So what I tried is doing the whole process again from the flash .img part, this time with the verbose option though and this is what it output:
./fastboot flash recovery -v twrp-3.1.0-0-vtr.img
fastboot: verbose: sending command "getvar:has-slot:recovery"
fastboot: verbose: received FAIL "Command not allowed"
fastboot: verbose: sending command "getvar:max-download-size"
fastboot: verbose: received OKAY "471859200"
fastboot: verbose: target reported max download size of 471859200 bytes
Sending 'recovery' (32034 KB)
fastboot: verbose: sending command "download:01f48800"
fastboot: verbose: received DATA 01f48800
fastboot: verbose: sending data (32802816 bytes)
fastboot: verbose: received OKAY ""
OKAY [ 1.238s]
Writing 'recovery'
fastboot: verbose: sending command "flash:recovery"
fastboot: verbose: received OKAY ""
OKAY [ 0.236s]
Finished. Total time: 1.489s
Now I do see that there is a problem in the first two lines but HELL NO if I know a way to fix it, I don't even know why it is giving me that error. Anyhow it has just not yet finished because any ./fastboot command from then on just freezes on the first output line for example:
./fastboot boot -v twrp-3.1.0-0-vtr.img
Downloading 'boot.img'
fastboot: verbose: sending command "download:01f48800"
^C
pbalatform-tools Andrea$ ./fastboot reboot
Rebooting ^C
pbalatform-tools Andrea$
And before terminating the commands I waited several minutes but sill nothing happened! What is possibly wrong?
I have got a Huawei P10 Lite (obvsly) with EMUI 5.1.
Actually there is one more wierd thing: I once installed a different type of TWRP from these forums, it was still the same version but i guess it was from a CATUVA's post as it was called TWRP 3.1.1.0 NOUGAT BY CATUVA21 P10LITE.img. Anyhow I flashed this .img and it literally did as always. By mistake I actually clicked on the update software from the settings on my huawei and rebooting normally to install the update it got me magicaly into the TWRP Catuva's recovery mode. Basically it never did the update and I was able to get back there in recovery mode just by trying to update my software again from settings. I tried every other way to access it but it just wouldn't go in TWRP: I tried also Power+Vol Up+Vol Dwn but it got me into the normal Emui 5.1. And after all these attempts I tried again getting into it with the try updating system and it got me back in... why the hell should he let me in just this way? I flashed another .img and the update thing just doesn't do anymore the trick.
HELP!!
Click to expand...
Click to collapse
Why u want to flash that recovery?
When usb cable is in phone with power+volup u will get emui recovery without usb u will boot costum (twrp) recovery. If u want to install oreo emui 8.0 use hwota.
Послато са WAS-LX1 уз помоћ Тапатока
nemanjsb said:
Why u want to flash that recovery?
When usb cable is in phone with power+volup u will get emui recovery without usb u will boot costum (twrp) recovery. If u want to install oreo emui 8.0 use hwota.
Послато са WAS-LX1 уз помоћ Тапатока
Click to expand...
Click to collapse
I already tried to do it without an usb cable plugged in but it will still get me to the EMUI erecovery one. What could be the problem? And if I install oreo 8.0 can I then root it anyways?
Peskyleo said:
I already tried to do it without an usb cable plugged in but it will still get me to the EMUI erecovery one. What could be the problem? And if I install oreo 8.0 can I then root it anyways?
Click to expand...
Click to collapse
Use HwOta method for emui 8.0 and u can root with magisk.
nemanjsb said:
Use HwOta method for emui 8.0 and u can root with magisk.
Click to expand...
Click to collapse
Thank you. I will keep you updated then!

[SOLVED]Stuck in Fastboot

I was on MIUI Global 12.0.2 Stable. I tried to flash Pig's latest Lineage (2020.07.21) from TWRP. The flash failed with an "Error 7". When I tried to reboot, the device went to "fastboot" mode.
After that, every attempt of a reboot ended in fastboot mode. So I tried to flash TWRP.img. Flashing went OK. But "fastboot boot twrp.img" gave the error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". The result was same with "fastboot oem reboot-recovery" command.
So I was stuck in fastboot mode with the risk of battery depletion. Below is the commands I ran to flash the TWRP.
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.016s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 2.179s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.016s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.046s
C:\adb>
Click to expand...
Click to collapse
SOLUTION: One needs to flash the fastboot ROM in MiFlash.
My situation had an extra issue as there were no fastboot ROM for MIUI Global 12.0.2. So, I downloaded MIUI 11.0.5 Global Fastboot ROM and flashed it. One needs to keep in mind about the "Anti-Rollback Protection" (https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/) and take necessary steps to avoid an anti-rollback brick.
If anti-rollback compatible ROM not available, then just delete first lines in all .bat files (.bat for Windows; .sh for Linux) up to the first line that starts with "fastboot %* getvar product..." of the available fastboot ROM. Those lines are the anti-rollback check. After than you can flash it via MiFlash.
Stillness said:
So I try to flash TWRP.img. Flashing goes OK. But "fastboot boot twrp.img" gives this error "FAILED (remote: Failed to load/authenticate boot image: Load Error)"
Click to expand...
Click to collapse
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
zgfg said:
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
Click to expand...
Click to collapse
Thanks for the reply. I tried that command too, but ended with the same error.
Now, downloading the 11.0.5 Global Fastboot ROM since no 12.0.2 Fastboot available. My plan is to just delete first lines in .bat files of the ROM to avoid 'rollback protection' and flash via MiFlash before the battery goes zero. According to google, it seems flashing the full Fastboot ROM is the only solution
SOLVED
Solved. Edited the OP.
zgfg said:
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
Click to expand...
Click to collapse
Wow, thank you so much for pointing this out!
I just had a close to two hour journey through all emotions after trying to restart my phone and suddenly ending up in a seemingly inescapable fastboot hell...
I've tried booting different recoveries, all failing with
Code:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
and was already at the point of giving up getting my system back, just trying to save my data if possible. Flashing seemed to work, but
Code:
fastboot reboot recovery
just threw me back into fastboot, which I assumed to be due to the phone rejecting the flashed recoveries just as it was rejecting them when I tried to boot them directly.
When I saw this comment I wondered whether Xiaomi implemented rebooting directly to the recovery differently (as it turns out, it doesn't seem to be standardized) and
Code:
fastboot oem reboot-recovery
worked perfectly! After reflashing my ROM from TWRP I was booted back up into my system with everything intact, as if nothing has happened.

[HELP] Z00TD/ZE551KL soft-bricked? No recovery mode, no OS, locked bootloader.

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.

Categories

Resources