My phone is rooted and unlocked. I have installed adb and fastboot. I had twrp installed and I used it to install a custom rom. Then, I accidentally flashed something (maybe update.zip?) that not only changed the regular system partition, but also the recovery partition. I've been trying to get twrp back and I'm having major issues.
When I try the command "fastboot erase recovery" I receive the following error message:
erasing 'recovery'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Invalid argument))
finished. total time: 0.005s
I've searched google with several different parameters and nothing is helping me, so I figure best to post my own question. I get the same error and status e00002e8 when trying to flash recovery.img or boot.img
Related
Hi,
I have problem formatting partitions
➜ platform-tools ./fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Invalid argument))
finished. total time: 0.003s
➜ platform-tools ./fastboot erase boot
erasing 'boot'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Invalid argument))
finished. total time: 0.003s
➜ platform-tools
Using ./fastboot format fails similarly.
hrstoyanov said:
Hi,
I have problem formatting partitions
? platform-tools ./fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Invalid argument))
finished. total time: 0.003s
? platform-tools ./fastboot erase boot
erasing 'boot'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Invalid argument))
finished. total time: 0.003s
? platform-tools
Using ./fastboot format fails similarly.
Click to expand...
Click to collapse
The reason I want to format/erase the partitions is because i cannot flash my phone anymore:
./fastboot flash system ~/Downloads/split_updata.pl/kiw_l24_a6.0.1_emui4.0_d003_US/SYSTEM.img
target reported max download size of 266338304 bytes
erasing 'system'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Undefined error: 0))
finished. total time: 0.001s
Also, when I put the phone in fastboot mode I see this:
PHONE Unlocked
FRP Lock
Could that "FRP Lock" be the reason why fastboot does not work, and if so how can I get rid of this FRP Lock?
The FRP Lock appeared after I decided that I had enough with CM13 and wanted to flash back the stock images. The phone is unlocked, but i cannot boot it up unless with fastboot.
About to throw away this phone ... out of ideas...:crying:
I found this for frp lock:
*to remove the factory reset protection (frp) to do this you need to remove all pin/password/fingerprint locks, then remove all google accounts and finally do a factory reset.
Google frp lock xda honor 5x, there are some threads.
Good luck
Sent from my KIW-L21 using XDA-Developers mobile app
rodolphe06 said:
I found this for frp lock:
*to remove the factory reset protection (frp) to do this you need to remove all pin/password/fingerprint locks, then remove all google accounts and finally do a factory reset.
Google frp lock xda honor 5x, there are some threads.
Good luck
Sent from my KIW-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
I also looked at those, but they are all talking about a fully operational device. The most I can do with my phone is some limited FASTBOOT operations, like:
./fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) Root State: ROOT
(bootloader) Bootloader WidevineKey: WidevineKey_VALID
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.011s]
finished. total time: 0.011s
The way it got bricked is, because it is a KIW-UL00 device and I tried to install the US stock rom in it (KIW-L24), like this:
./fastboot flash boot ./kiw_l24_a6.0.1_emui4.0_d003_US/BOOT.img
./fastboot flash system ./kiw_l24_a6.0.1_emui4.0_d003_US/SYSTEM.img
./fastboot flash recovery ./kiw_l24_a6.0.1_emui4.0_d003_US/RECOVERY.img
after that, I tried to reboot the phone and the the restoration of the stock rom did start. However it got to about 5%, then
the phone started rebooting itself and never finished. As a result, I think the FRP Lock appered and I can no longer run the above
commands even though I have the the right stock rom for KIW-UL00.
Any chance to fix that?
Overall the problem I got into this is that no one has tested CM13 or TWRP3 with this particular Honor 5x model, KIW-UL00, which gets people to follow instructions and get their phones bricked. Should have known this before I started ... sigh ...
(This is a duplicate of thread to reach more people, original thread : https://forum.xda-developers.com/mi-a3/help/son-killed-xiaomi-mi-a3-t4060735)
So I bought a son new phone.
As he told he installed magisk first, flashing "magisk_patched.img" through windows shell, everything was fine. Then He flashed twrp and magisk, everything was almost fine, he noticed that he cant play audio. He was trying to fix it first through installing magisk audio mods like viper and sauron. It didn't fixed anything, he unistalled it, everything was still in the same state, so he decided to flash stock frimware. He flashed through mi flashing tool, unfortunetaly It was image for "global xiaomi version" I mean "PFQMIXM" when as far as I know It should be "PFQEUXM". It didn't work and he was stuck in a bootloop. He found "MiUi 11 " image and for still unknown to me reason thought that it is going to fix everything. He flashed It again through mi flashing tool. It didn't work. He did that second time but at last he just closed the flashing tool while it was doing its thing.
At last he found eu firmware but now after all of that when i try to flash it or single files like crc list i get this:
flash crclist "E:\ModCR\adb\images\crclist.txt"
Sending 'crclist' (0 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Device only boots to fastboot (no recovery/twrp either).
I tried erasing cache:
./fastboot erase cache
Erasing 'cache' FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
I tried to check slots:
./fastboot getvar active-slot
getvar:active-slot FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.003s
I tried to change slot:
./fastboot set_active b
fastboot: error: Device does not support slots
When i typed "fastboot devices" It appeared as "??????"
./fastboot devices
???????????? fastboot
I don't know how to fix it, If anyone knows or has any kind of even small idea please write it down. I would be very greatfull.
Thread closed as duplicate of https://forum.xda-developers.com/mi-a3/help/son-killed-xiaomi-mi-a3-t4060735
Do not make duplicates "to reach more people"..
Hi Guys!
So I got a phone from a friend to assist him with a problem.
When I opening the phone, the phone showing an error message "The system has been destroyed".
I tried to use Fastboot but when I running any command an error message received, for example:
Example1:
fastboot flash recovery "twrp-3.3.0-0-beryllium (1).img"
Sending 'recovery' (31068 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Example2:
fastboot devices -l
???????????? fastboot
Example 3:
fastboot flashing unlock
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
fastboot oem device-info -v
< waiting for any device >
FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
Any ideas??
Please help!
Thanks!
I know there's so many threads made but I'm hoping someone can help me with my particular solution.
So I'm using the tutorial by this site which has worked so far and I've completed Part 1 (Unlocking the Bootloader).
My issue is, when I type the command: fastboot boot <insert_name_of_TWRP_image_here>.img
I get the following message:
(base) [email protected] android % ./fastboot boot twrp-3.2.3-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.287s]
Booting ERROR: usb_read failed with status e00002eb
FAILED (Status read failed (No such file or directory))
fastboot: error: Command failed
The .img file is definitely in the 'android' folder and I'm doing it correctly afaik because I've been able to unlock the Bootloader with no issue. Does anyone know what this message means?
Im definitely using the most up-to-date twrp file, I'm on a MacBook and my phone is a Pixel 3.
Thanks for any help!
MHuncho said:
I know there's so many threads made but I'm hoping someone can help me with my particular solution.
So I'm using the tutorial by this site which has worked so far and I've completed Part 1 (Unlocking the Bootloader).
My issue is, when I type the command: fastboot boot <insert_name_of_TWRP_image_here>.img
I get the following message:
(base) [email protected] android % ./fastboot boot twrp-3.2.3-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.287s]
Booting ERROR: usb_read failed with status e00002eb
FAILED (Status read failed (No such file or directory))
fastboot: error: Command failed
The .img file is definitely in the 'android' folder and I'm doing it correctly afaik because I've been able to unlock the Bootloader with no issue. Does anyone know what this message means?
Im definitely using the most up-to-date twrp file, I'm on a MacBook and my phone is a Pixel 3.
Thanks for any help!
Click to expand...
Click to collapse
Hi,
That might be a simple answer but try to add the full path of the file at the end of the command :
./fastboot boot [drag the file and drop it next to the word "boot" to have its full path written down without any typos]
Let me know what you get
Hi all,
when installing lineage 18.1 I successfully screwed up my MOTO G8. When rebooting after all installalation steps being successfull, it says
No valid operation system could be found. The device will not boot.
Booting to fastboot again I tried to flash again, but this time I get
fastboot set_active aSetting current slot to 'a' FAILED (remote: '')
fastboot: error: Command failedTrying to to flash something does not work as well, e.g.
fastboot flash recovery recovery.imgending 'recovery' (24924 KB) OKAY [ 0.752s]Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failedApperently the partition table appears to be broken. Can I restore it?
badkey212 said:
Hi all,
when installing lineage 18.1 I successfully screwed up my MOTO G8. When rebooting after all installalation steps being successfull, it says
No valid operation system could be found. The device will not boot.
Booting to fastboot again I tried to flash again, but this time I get
fastboot set_active aSetting current slot to 'a' FAILED (remote: '')fastboot: error: Command failedTrying to to flash something does not work as well, e.g.
fastboot flash recovery recovery.imgending 'recovery' (24924 KB) OKAY [ 0.752s]Writing 'recovery' (bootloader) Invalid partition name recoveryFAILED (remote: '')fastboot: error: Command failedApperently the partition table appears to be broken. Can I restore it?
Click to expand...
Click to collapse
Does the bootloader say "flashing_locked" now?
Try
Code:
fastboot flash partition gpt.bin
sd_shadow said:
Does the bootloader say "flashing_locked" now?
Try
Code:
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
That helped, thank you!