Can't flash TWRP Recovery .img! - Huawei P10 Lite Questions & Answers

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!

Related

Please Help me! I can't flash stock rom

Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.
I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...
Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.
Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?
Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again
Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .
Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img

Help for bricked Device[Solved]

Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Thanks
bijilidk said:
Hi,
i was running on MIUI 7 on Lenovo A6000 by Sourav_8434 and it was working fine.For my mistake i have updated weekly update i thought it will be normal.But after that my phone is showing a black screen.I can get in to fastboot and i have flashed twrp using 'fastboot flash recovery recovery.img' and when i tried to boot in to twrp(using fastboot flash recovery recovery.img) its giving me an error.
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.756s
I have send a personal message to Sourav_8434 and he replied me with some suggestions.He told me he also got the same problem and fix this issue by flashing twrp and pressing 3 buttons same at a time(vol+,Vol-,Power button).But i have tried this several times but its not working for me.If anyone got this situation before please help me. I dont want to go to service center for this problem.
Thanks
Click to expand...
Click to collapse
This happens when you flash wrong version. You must be using the twrp for KK, while MIUI is LP.
So try this one
https://userscloud.com/a25aszfwkn2z
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
bijilidk said:
Tried but not working same error is showing.
Once I did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
sasukay said:
Give these a try too
Twtp 3.0.2 http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=55585
Twrp 2.8.6 https://userscloud.com/m4jy6u5chkkp
Cwm http://www15.zippyshare.com/v/j9lHGdJf/file.html
Click to expand...
Click to collapse
No hope tried everything..same error.
bijilidk said:
No hope tried everything..same error.
Click to expand...
Click to collapse
Extract "boot.img" from the root of MIUI rom zip and flash that with "fastboot flash boot boot.img"
Then flash the twrp for lollipop
Otherwise, you'll need to flash the firmware through QFIL Downloader
bijilidk said:
Tried but not working same error is showing.
[email protected]:~/Desktop/TWRP/img$ sudo fastboot flash recovery twrp.img
[sudo] password for user:
Sorry, try again.
[sudo] password for user:
target reported max download size of 268435456 bytes
sending 'recovery' (13204 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 2.022s]
finished. total time: 2.438s
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot recovery twrp.img
cannot load 'recovery': No such file or directory
[email protected]:~/Desktop/TWRP/img$ sudo fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.417s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.449s
Once i did this before 'fastboot erase recovery.img' is that a problem?
Click to expand...
Click to collapse
It seems you successfully flashed the twrp recovery...............
If your recovery is right i.e.according to your previous os
Then just u need to enter into recovery by pressing 3 buttons at the same time....
if not worked then flash another twrp version....
-Sourav_8434
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
bijilidk said:
Thanks for the support @sasukay @Sourav_8434 Revert back to Stock lolipop via Lenovo firmware software.
Click to expand...
Click to collapse
Please explain how you did it. I'm also stuck with blank screen and only vibration
neerut said:
Please explain how you did it. I'm also stuck with blank screen and only vibration
Click to expand...
Click to collapse
Refer this link. I used the ( THIRD METHOD )Installing the firmware using Lenovo Downloaders.
https://boycracked.com/2015/06/03/unbrick-lenovo-a6000/
So everything is solved here right ? you can close this thread now i think !

Axon7toolkit

Device is unlocked (A2017G)
Tried flashing twrp/root using axon7toolkit(version 1.2.0)
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Can anybody help with this?
still_living said:
Device is unlocked (A2017G)
Tried flashing twrp/root using axon7toolkit(version 1.2.0)
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Can anybody help with this?
Click to expand...
Click to collapse
edit: whatever, i'll let bkores help you with this
still_living said:
Device is unlocked (A2017G)
Tried flashing twrp/root using axon7toolkit(version 1.2.0)
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Can anybody help with this?
Click to expand...
Click to collapse
Do this in command prompt and tell me the output:
Code:
cd C:\Axon7Development\Axon7Toolkit
fastboot flash recovery twrp\twrp-3.1.1-0-ailsa_ii.img
Also failed
bkores said:
Do this in command prompt and tell me the output:
Code:
cd C:\Axon7Development\Axon7Toolkit
fastboot flash recovery twrp\twrp-3.1.1-0-ailsa_ii.img
Click to expand...
Click to collapse
This is what I got.
C:\Axon7Development\Axon7Toolkit>fastboot flash recovery twrp\twrp-3.1.1-0-ailsa_ii.img
target reported max download size of 536870912 bytes
sending 'recovery' (14452 KB)...
OKAY [ 0.362s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.383s

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

Today I was trying to install a newer rom (MIUI 8.1)(also MIUI 4.11 after the 8.1 failed a couple times) through twrp 3.1.1.0-aries and my mi2s got soft bricked after the update failed with error code 7 something about being unable to write system to /system.
So I tried to install the new rom using MiFlash and got there a different error
Code:
[4:25:07 PM 9063612]:target didn't report max-download-size
[4:25:07 PM 9063612]:sending 'tz' (196 KB)...
[4:25:07 PM 9063612]:error:FAILED (data transfer failure (Unknown error))
[4:25:07 PM 9063612]:"Flash tz error"
[4:25:07 PM 9063612]:error:FAILED (data transfer failure (Unknown error))
Then I tried to flash it using Mi PC Suite which got stuck at 52% for 2 hours at "sending system.img". I saw it wasn't going anywhere so I disconnected the device and terminated the task.
At that point the phone didn't go into the recovery mode anymore. I think Mi PC Suite might have done something to the partition table.
Right now the phone is stuck in fastboot loop and can't go into recovery mode unless I run the command
Code:
fastboot boot twrp.img
which can sometimes fail as well with error:
Code:
FAILED (status read failed (Too many links))
At the first time I managed to get back into twrp using the above command I felt some relief and I tried doing a factory reset from the twrp menu. It didn't help.
Flashing twrp using the command
Code:
fastboot flash recovery twrp.img
says everything is okay and is finishing without errors but I still can't boot into it. It just goes straight to fastboot.
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (10346 KB)...
OKAY [ 0.432s]
writing 'recovery'...
OKAY [ 1.793s]
finished. total time: 2.225s
trying to flash new rom using MiFlash gives an error about the partition table
Code:
FAILED (remote: partition table doesn't exist)
Please help me unbrick my device I'm open for suggestions!
Thank you.
I fixed this by downloading "aries_images_4.11.21_4.1_cn" and editing the "flash_all.bat" script to include
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash partition error" && exit /B 1
in the third row right after the 2 "soc-id" checks.
I am still not sure how to upgrade from here to one of the newer miui roms.
XDA1515 said:
I fixed this by downloading "aries_images_4.11.21_4.1_cn" and editing the "flash_all.bat" script to include
Code:
fastboot %* flash partition "%~dp0images\gpt_both0.bin" || @echo "Flash partition error" && exit /B 1
in the third row right after the 2 "soc-id" checks.
I am still not sure how to upgrade from here to one of the newer miui roms.
Click to expand...
Click to collapse
Solved. I managed to flash aries_global_images_V8.1.3.0.LXAMIDI_20161122.0000.00_5.0_global using MiFlash.
At first I thought it didn't work because it flashed the whole rom way too quickly in like 5-10 seconds and booted back to fastboot but then I just left the device there to rest and when I came back after a few minutes I saw it booted to a black screen with a white MI at the center of it and then android and 3 dots appeared at the bottom so I just waited for a few more minutes and it installed everything.
I hope this might help someone else with similar issue.

[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.

Categories

Resources