Related
Hi @all,
i just messed something up while testing several custom roms for my Zenfone5 so actually i cant write system neither by "sideload" nor by "fastboot flash system". i always get the a mistake like:
Code:
FAILED (remote: flash_cmds error!)
Actually i cant find a mistake by myself. Is it located in my PC or in my phone? i already searched for an errorlist for fastboot but that doesn't get me any results...
and as we say in germany:
Vielen Dank im Vorraus!
Vere'Athor
You're trying to flash a wrong file.
What's the command you're running?
I get the same error running this command:
fastboot.exe flash recovery recovery.img
I cant erase this partition too. When i run this:
fastboot.exe erase recovery
I get this:
FAILED (remote: unable to format)
¨
Please Help
Waërloga666 said:
I get the same error running this command:
fastboot.exe flash recovery recovery.img
I cant erase this partition too. When i run this:
fastboot.exe erase recovery
I get this:
FAILED (remote: unable to format)
¨
Please Help
Click to expand...
Click to collapse
Can you post a link to recovery you are trying to flash? (I will test it)
Can anyone help me out? I tried to install CM 13.1 in Zenfone 5 but when it gets to "writing boot" the following message appears:
FAILED (remote: flash_cmds error!)
How could i solve this? txs everyone
(If any of you guys could text in Portuguese i would be very pleasant)
if u want to flash custom rom
all u need is to unlock bootloader
take a look on this thread using auto.bat for unlock bootloader!
https://forum.xda-developers.com/zenfone-5/general/recovery-twrp-2-8-6-0-asus-zenfone-5-t3136263
after unlocked try flash TWRP again
to confirm success unlocked not!
if fail it will show error failed
just follow step by step read thru!
hope it helps
good luck !
I am Having The Same Error (FAILED (remote: flash_cmds error!)
What To do
When I try to wipe internal it says
Code:
Wiping internal storage -- /data/media...
Error opening: '/data/media' (No such file or directory)
When I try to format instead - I get even more errors:
Code:
Formatting Data using make_ext4fs...
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
specialk00 said:
...Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
Click to expand...
Click to collapse
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
v12xke said:
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
Click to expand...
Click to collapse
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery D:\Downloads\angler\twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I always get this weird "No error" thing.
specialk00 said:
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Click to expand...
Click to collapse
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
v12xke said:
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
Click to expand...
Click to collapse
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same.
Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash.
I tried putting the TWRP img in my fastboot folder and the results are the same.
Erasing the recovery partition gives the same error.
Code:
C:\Users\username\AppData\Local\Android\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.009s
specialk00 said:
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same. Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash. I tried putting the TWRP img in my fastboot folder and the results are the same. Erasing the recovery partition gives the same error.
Click to expand...
Click to collapse
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
v12xke said:
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
Click to expand...
Click to collapse
I tried minimal adb & fastboot (bit older version) and got this.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.007s
Then I tried another old version of fastboot - got one from july 2016 (23.0.1) and nothing happened when executing flash or format commands.
Then I tried normal, latest fastboot and both (new & old) versions of fastboot gave me this error.
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.023s
Then I tried to format (instead of erase)
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (command write failed (No error))
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
specialk00 said:
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
Click to expand...
Click to collapse
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
v12xke said:
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
Click to expand...
Click to collapse
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now.
This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
specialk00 said:
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now. This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
Click to expand...
Click to collapse
Stock fastboot does not support boot to EDL. You need a modified fastboot, BUT getting to EDL mode won't help you until you have all the proper tools and 6P specific files. I don't want to get your hopes up. I think your device is not recoverable due to a hardware issue (bad memory). If you are looking for a learning project to keep you busy with very little hope of success, keep digging. If you need a working phone, you need to buy another one, or a 6P replacement motherboard from a screen damaged parts phone. Unfortunately, there have been many onboard memory failures on the 6P.
I fixed the problem. It turned out to be a faulty USB-C to USB-A cable. The only problems were with file transfer-related commands. I then tried transferring a 1 kb file, then 1 mb (failed) then 200kb, then 300kb (failed). So it turns out the cable is ****ty. Wow. And nothing is corrupted. I'm typing this from my phone now.
Today after a successful OTA manual upgrade(downloaded latest zip and flashed) I decided to reinstall TWRP in order to reroot. However, after running first "fastboot flash recovery twrp.zip" then "fastboot boot twrp.zip", I am no longer prompted to enter my passcode(which I know) to decrypt the device, and the /system partition is empty in the TWRP file manager. The sdcard partition is filled with my encrypted files(assuming by their base64 names).
I dont think any of my actions in TWRP were significant, except possibly when I flashed the twrp.zip to have the recovery be persistent. (When I launched TWRP for the first time, I wasn't prompted for my password to decrypt then either, so I assume the damage was already done)
I have tried "twrp decrypt [password]" in the twrp terminal but I get "Failed to decrypt data"
A. Is there a way to reflash my system(e.g Can I just flash the same update.zip) and be back to normal
Or B. Can I retrieve and decrypt my data, given that I know my lockscreen passcode which is normally used to decrypt it.
Here is everything I wrote in my command prompt(Can't post links):
E:\Coding\OnePlus>fastboot
-snip fastboot help-
E:\Coding\OnePlus>fastboot flash recovery twrp-installer-fajita-3.2.3-2.zip
target reported max download size of 536870912 bytes
sending 'recovery' (16693 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.364s
E:\Coding\OnePlus>fastboot boot twrp-installer-fajita-3.2.3-2.zip
creating boot image...
creating boot image - 17096704 bytes
downloading 'boot.img'...
OKAY [ 0.361s]
booting...
OKAY [ 0.092s]
finished. total time: 0.455s
E:\Coding\OnePlus>fastboot devices
d535eae7 fastboot
E:\Coding\OnePlus>fastboot boot twrp-installer-fajita-3.2.3-2.zip
creating boot image...
creating boot image - 17096704 bytes
downloading 'boot.img'...
OKAY [ 0.361s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 0.456s
E:\Coding\OnePlus>fastboot flash recovery twrp-installer-fajita-3.2.3-2.zip
< waiting for device >
^C
E:\Coding\OnePlus>fastboot devices
E:\Coding\OnePlus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
d535eae7 recovery
E:\Coding\OnePlus>adb flash
-snip adb help-
E:\Coding\OnePlus>adb push twrp-installer-fajita-3.2.3-2.zip /data
7500 KB/s (17094317 bytes in 2.225s)
E:\Coding\OnePlus>
Click to expand...
Click to collapse
As you learned from the first command there is no recovery partition, you can't flash like that. Your data is on a different partition, so it should be ok (pictures and such, I'm assuming that's what you are worried about)
Next I don't know what ROM or OS you are using, but if it's a current one, you will need a newer version of TWRP. Download 3.3.1-6 or 3.3.1-7 from this thread (link) You need the IMG file first. Run:
fastboot boot twrp-3.3.1-6-fajita.img (Or -7 if you download -7)
Hopefully that will ask you for your password and decrypt all your data. At this point backup your data. Then I would dirty flash your ROM as it's hard to say what you did with all that flashing up above. Then run the TWRP installer. Then Reboot to recovery, flash magisk (If this was a custom ROM, remeber to also re-flash Gapps). Just like you were doing a regular update. Hopefully that fixes everything.
jonesbeverly44 said:
Today after a successful OTA manual upgrade(downloaded latest zip and flashed) I decided to reinstall TWRP in order to reroot. However, after running first "fastboot flash recovery twrp.zip" then "fastboot boot twrp.zip", I am no longer prompted to enter my passcode(which I know) to decrypt the device, and the /system partition is empty in the TWRP file manager. The sdcard partition is filled with my encrypted files(assuming by their base64 names).
I dont think any of my actions in TWRP were significant, except possibly when I flashed the twrp.zip to have the recovery be persistent. (When I launched TWRP for the first time, I wasn't prompted for my password to decrypt then either, so I assume the damage was already done)
I have tried "twrp decrypt [password]" in the twrp terminal but I get "Failed to decrypt data"
A. Is there a way to reflash my system(e.g Can I just flash the same update.zip) and be back to normal
Or B. Can I retrieve and decrypt my data, given that I know my lockscreen passcode which is normally used to decrypt it.
Here is everything I wrote in my command prompt(Can't post links):
Click to expand...
Click to collapse
Hello my friend. Did you ever find a solution to get your directory back? Mine looks like you explained now in TWRP and in a file manager. Like it was encrypted or something.
boobteg2 said:
Hello my friend. Did you ever find a solution to get your directory back? Mine looks like you explained now in TWRP and in a file manager. Like it was encrypted or something.
Click to expand...
Click to collapse
Fastboot the .IMG file not the .zip file, if it is encrypted then adb sideload or boot to system then fastboot again.
I am no longer prompted to enter my passcode(which I know) to decrypt the device, and the /system partition is empty in the TWRP file manager. The sdcard partition is filled with my encrypted files(assuming by their base64 names).
Click to expand...
Click to collapse
OnePlus uses FBE (File Based Encryption) which is why it looks like this. Just booting TWRP doesn't affect your data. As long as you're able to restore a working system partition and let phone boot your data should be accessible, but _only_ once phone fully boots.
Hi, it can happen that after flashing TWRP, Orangefox or SHRP and after restarting in recovery, the device gets stuck on the recovery logo.
This happens because the data partition is encrypted and TWRP does not often support it does not support encryption and therefore data must be decrypted.
Before following this guide I recommend making a backup because the data will be deleted.
WARNING: NEVER run "fastboot -w" on Minimal Fastboot and ADB or 15 Seconds ADB installer, doing this the DATA partition is corrupted so it must necessarily be run on platform-tools.
To decrypt with fastboot you need platform tools taken from the Android SDK, click here for download.
To decrypt you need to:
1) Reboot the device in fastboot
2) Open the CMD inside the platform-tools folder
3) Run the "fastboot -w" command.
4) Now the device is decrypted.
Why not use TWRP_4pda_edition, which decrypts /data, at least with Android P? (have not tried Android Q yet)
Aerobatic said:
Why not use TWRP_4pda_edition, which decrypts /data, at least with Android P? (have not tried Android Q yet)
Click to expand...
Click to collapse
For those who want a data decrypted or compatible with all recovery. Many people have complained about the recoveries that were stuck in the splash logo and I wanted to make a thread so instead of always asking the same question, look at the thread
XRed_CubeX said:
Hi, it can happen that after flashing TWRP, Orangefox or SHRP and after restarting in recovery, the device gets stuck on the recovery logo.
This happens because the data partition is encrypted and TWRP does not often support it does not support encryption and therefore data must be decrypted.
Before following this guide I recommend making a backup because the data will be deleted.
WARNING: NEVER run "fastboot -w" on Minimal Fastboot and ADB or 15 Seconds ADB installer, doing this the DATA partition is corrupted so it must necessarily be run on platform-tools.
To decrypt with fastboot you need platform tools taken from the Android SDK, click here for download.
To decrypt you need to:
1) Reboot the device in fastboot
2) Open the CMD inside the platform-tools folder
3) Run the "fastboot -w" command.
4) Now the device is decrypted.
Click to expand...
Click to collapse
Will this erase anything?
DinIslamJoy said:
Will this erase anything?
Click to expand...
Click to collapse
Yes, "fastboot -w" command is the full wipe.
I just do not understand why people insist on using buggy variants of TWRP and tampering their phones because of this, while there is TWRP_4pda_version successfully decrypting user data in Androids 8, 9, 10?
Probably because those who successfully used it, did it silently, and did not bother to "Star" the thread promoting TWRP_4pda_version, and thus the thread is buried behind threads with faulty TWRP variants?
Aerobatic said:
Yes, "fastboot -w" command is the full wipe.
I just do not understand why people insist on using buggy variants of TWRP and tampering their phones because of this, while there is TWRP_4pda_version successfully decrypting user data in Androids 8, 9, 10?
Probably because those who successfully used it, did it silently, and did not bother to "Star" the thread promoting TWRP_4pda_version, and thus the thread is buried behind threads with faulty TWRP variants?
Click to expand...
Click to collapse
I did this thread because many people complain about the freeze in the logo and I could not answer one by one and therefore I decided to do this guide
Fixed my issue, thanks!
XRed_CubeX said:
Hi, it can happen that after flashing TWRP, Orangefox or SHRP and after restarting in recovery, the device gets stuck on the recovery logo.
This happens because the data partition is encrypted and TWRP does not often support it does not support encryption and therefore data must be decrypted.
Click to expand...
Click to collapse
I was facing this issue and tried to do the mentioned steps but it gave me this error:-
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (56 KB) FAILED (remote: 'Error: Last flash failed : Write Protected')
fastboot: error: Command failed
device- Xiaomi Mi A2 , it always give me this error (Write protected). Any suggestions would be helpful.
adb tells me this, I dont know if it worked or not yet, but the code makes me think it didnt:
C:\adb\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.436s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\adb\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
C:\adb\platform-tools>
Update, it actually did work Thanks.
Aerobatic said:
Yes, "fastboot -w" command is the full wipe.
I just do not understand why people insist on using buggy variants of TWRP and tampering their phones because of this, while there is TWRP_4pda_version successfully decrypting user data in Androids 8, 9, 10?
Probably because those who successfully used it, did it silently, and did not bother to "Star" the thread promoting TWRP_4pda_version, and thus the thread is buried behind threads with faulty TWRP variants?
Click to expand...
Click to collapse
Im guessing it is because it doesnt work flawlessly on any device, for my redmi 9a for example, it is recomended to use PBRP or OFRP and avoid TWRP if posible, IDK man, Im just a n00b so I repeat what I hear and hope Im not spreading missinformation, but thats what I think.
Ivan.Adriazola said:
adb tells me this, I dont know if it worked or not yet, but the code makes me think it didnt:
C:\adb\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.436s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
C:\adb\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
C:\adb\platform-tools>
Update, it actually did work Thanks.
Click to expand...
Click to collapse
Strange that after two years the guide still works, it may no longer be current because it was an old problem but apparently it is still there.
To make you understand I don't even have the device anymore.
Ivan.Adriazola said:
Im guessing it is because it doesnt work flawlessly on any device, for my redmi 9a for example, it is recomended to use PBRP or OFRP and avoid TWRP if posible, IDK man, Im just a n00b so I repeat what I hear and hope Im not spreading missinformation, but thats what I think.
Click to expand...
Click to collapse
Yes, there are some errors, in reality the stability of the recovery can depend on various factors such as: device, device tree, recovery maintainer and in some cases the TWRP, PBRP or other sources.
You should never blame TWRP or recovery in general because not all TWRP of every device is the same as not all PBRP may be the same, it can change many things.
If someone still using.
facing this
C:\Users\Lucky\Desktop\MI BOOT\A2\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.142s]
mke2fs 1.46.6-rc1 (12-Sep-2022)
mke2fs: Illegal or malformed device name while trying to determine filesystem size
C:\Users\Lucky\Desktop\MI BOOT\A2\platform-tools/mke2fs failed: 1
fastboot: error: Cannot generate image for userdata
MantriJi said:
If someone still using.
facing this
C:\Users\Lucky\Desktop\MI BOOT\A2\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.142s]
mke2fs 1.46.6-rc1 (12-Sep-2022)
mke2fs: Illegal or malformed device name while trying to determine filesystem size
C:\Users\Lucky\Desktop\MI BOOT\A2\platform-tools/mke2fs failed: 1
fastboot: error: Cannot generate image for userdata
Click to expand...
Click to collapse
The guide is old and may be outdated, repair partition with TWRP
I have a Redmi 7a brick, it has an unlocked bootloader, TWRP was flashed and Android 12 custom rom
At one point, unexpectedly during normal operation, the phone froze, an attempt to restart led to freezing on the Redmi splash screen, which later switched to Fastboot. When you try to start the recovery, it loads for about 20 minutes and responds very slowly to actions, in the mount column, the internal memory partition is 0MB, attempts to format / change the file system lead to a freeze, the phone is detected through the computer using fastboot, but any attempts to flash the recovery / system are not what they don’t lead to (writes that it’s successful, but in fact nothing), as they said on other forums and examples, this is the death of internal memory, but maybe there is an opportunity to fix it
Stimayk said:
I have a Redmi 7a brick, it has an unlocked bootloader, TWRP was flashed and Android 12 custom rom
At one point, unexpectedly during normal operation, the phone froze, an attempt to restart led to freezing on the Redmi splash screen, which later switched to Fastboot. When you try to start the recovery, it loads for about 20 minutes and responds very slowly to actions, in the mount column, the internal memory partition is 0MB, attempts to format / change the file system lead to a freeze, the phone is detected through the computer using fastboot, but any attempts to flash the recovery / system are not what they don’t lead to (writes that it’s successful, but in fact nothing), as they said on other forums and examples, this is the death of internal memory, but maybe there is an opportunity to fix it
Click to expand...
Click to collapse
Try to flash with original miui ROM.
itmasen1 said:
Try to flash with original miui ROM.
Click to expand...
Click to collapse
I tried but no changes are applied
UPD: I'm again try to flash original ROM and fastboot give a
Sending 'sec' (0 KB) OKAY [ 0.004s]
Writing 'sec' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Flash sec error
How to fix it?
Stimayk said:
UPD: I'm again try to flash original ROM and fastboot give a
Sending 'sec' (0 KB) OKAY [ 0.004s]
Writing 'sec' FAILED (remote: 'flash write failure')
fastboot: error: Command failed
Flash sec error
How to fix it?
Click to expand...
Click to collapse
in principle, there is a solution by going through EDL MODE . you have a chance to restore your phone,
do your research on the net about this method.