Help me !! remote : flash_cmds error - Asus Zenfone 4

i have zenfone 4 A400CG(kitkat) always display error facebook, system ui, youtube etc. now i flash with same rom.
on adb folder i type in cmd : fastboot flash boot boot.img(success) but when i type fastboot flash fasboot fastboot.img
"Failed (remote : flash_cmds error !" can u help me ?
flash cmds error solve problem, now i flash error : "fail: no enought DATA space,please free 998 MB at least"
i try flash raw file in SD Download, after that stuck Asus logo. help me...

Related

Failed to flash TWRP.

Hi,
I tried to flash TWRP to my phone using the command: "fastboot flash recovery twrp-3.0.2-0-titan.img"
This failed and gave me a message saying "mismatched partition size (recovery)"
What can I do?

Device is Corrupt and will SHUTDOWN in 30 seconds. DEAD DEVICE?=(

I had rooted Nokia 8 TA-1004(Android 9 ), but decided to switch back on 8.1
First step in instruction was to lock the bootloader to make a critical unlock
I used "fastboot oem lock" command and after that i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again
What i've already tried:
fastboot flash unlock unlock.key (FAILED (remote: Fail to verify)
fastboot flash boot_a boot.img (Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash boot_b boot.img (Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash system_a system.img (Invalid sparse file format at header magic)
fastboot -i 0x2e04 flash unlock unlock.bin (FAILED (remote: Fail to verify)
fastboot -i 0x2e04 oem unlock-go (FAILED (remote: Flashing Unlock is not allowed)
fastboot set_active a (FAILED (remote: 'Slot Change is not allowed in Lock State)
fastboot set_active b (FAILED (remote: 'Slot Change is not allowed in Lock State)
adb sideload (
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found)
Help me please. IDK what to do. I do have my old unlock.key, but couldn't install it to open the bootloader....Any ideas, please :crying:
First of all why the hell would u even lock your bootloader if you wish to flash anything ? There's nothing that should justify relocking your device perhaps apart from giving out your phone for repairs on warranty.
Can you access your recovery menu mode ?
KonikoO said:
First of all why the hell would u even lock your bootloader if you wish to flash anything ? There's nothing that should justify relocking your device perhaps apart from giving out your phone for repairs on warranty.
Can you access your recovery menu mode ?
Click to expand...
Click to collapse
I needed to make a critical unlock, and according to instruction 1st step was to lock the bootloader.
I can access download mode only
well this is completely messed up situation here. Maybe going to service center is the only option left. Btw, you repaired your phone yet or it is still like that??
This actually happened because you were on modified system when you locked the bootloader. You need to be completely stock while locking the bootloader.
sumitinhome said:
well this is completely messed up situation here. Maybe going to service center is the only option left. Btw, you repaired your phone yet or it is still like that??
This actually happened because you were on modified system when you locked the bootloader. You need to be completely stock while locking the bootloader.
Click to expand...
Click to collapse
Everything is fine. Ntool helped me to install stock 8.1
Mihalsch said:
Everything is fine. Ntool helped me to install stock 8.1
Click to expand...
Click to collapse
Process please.
sumitinhome said:
Process please.
Click to expand...
Click to collapse
Bought Ntool credits, download stock 8.1, flash it from Ntool..that's all.
pls help bro im having the same probelm of urs for 1 month
Mihalsch said:
Bought Ntool credits, download stock 8.1, flash it from Ntool..that's all.
Click to expand...
Click to collapse
which version of ntools did you use and where can i download stock 8.1 im new to this pls help :crying:
gogeta blue said:
which version of ntools did you use and where can i download stock 8.1 im new to this pls help :crying:
Click to expand...
Click to collapse
0.036 version
Here is 8.1. Pass (techmesto.com)
https://drive.google.com/file/d/1g4rsUE2sohL9EISb0Uu5FPRlNs0D73Xl/view
Mihalsch said:
0.036 version
Here is 8.1. Pass
Click to expand...
Click to collapse
0.036 version is not found any where i can only find 0.1 pls help
gogeta blue said:
0.036 version is not found any where i can only find 0.1 pls help
Click to expand...
Click to collapse
Try this
https://fex.net/635965328106
Mihalsch said:
Try this
Click to expand...
Click to collapse
Error while flashing
RUNNING NTool 0.036
PHONE "NB1GAD1791302820" CONNECTED
ProjectCode : NB11
model : NB1
sub_model : none
software version : NB1-488K-0-00WW-B01
SW model : 00WW
build number : B01
hardware version : 3.1
RF band id : G_850_900_1800_1900^W_1_2_4_5_8^L_1_2_3_4_5_7_8_
secure : yes
Bootloader type : commercial
Download size : 00000512 mB
Elapsed: 40 secs.
SELECT FIRMWARE PACKAGE
Will flash : NB1-488B-0-00WW-B04.mlf
PLEASE CONNECT POWERED OFF PHONE
PHONE "NB1GAD1791302820" CONNECTED
ProjectCode : NB11
model : NB1
sub_model : none
software version : NB1-488K-0-00WW-B01
SW model : 00WW
build number : B01
hardware version : 3.1
RF band id : G_850_900_1800_1900^W_1_2_4_5_8^L_1_2_3_4_5_7_8_
secure : yes
Bootloader type : commercial
Download size : 00000512 mB
Security version : 0004
Challenge : 9AEEE713ECEF3D6448B2E0842D1C8B34EA5D12BF
Waiting for calculation process ...
recv error [10054]
FATAL ERROR: server error: No server found.
Elapsed: 0 secs.
Mihalsch said:
I had rooted Nokia 8 TA-1004(Android 9 ), but decided to switch back on 8.1
First step in instruction was to lock the bootloader to make a critical unlock
I used "fastboot oem lock" command and after that i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again
What i've already tried:
fastboot flash unlock unlock.key (FAILED (remote: Fail to verify)
fastboot flash boot_a boot.img (Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash boot_b boot.img (Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash system_a system.img (Invalid sparse file format at header magic)
fastboot -i 0x2e04 flash unlock unlock.bin (FAILED (remote: Fail to verify)
fastboot -i 0x2e04 oem unlock-go (FAILED (remote: Flashing Unlock is not allowed)
fastboot set_active a (FAILED (remote: 'Slot Change is not allowed in Lock State)
fastboot set_active b (FAILED (remote: 'Slot Change is not allowed in Lock State)
adb sideload (
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found)
Help me please. IDK what to do. I do have my old unlock.key, but couldn't install it to open the bootloader....Any ideas, please :crying:
Click to expand...
Click to collapse
I meet the same thing,but my phone is nokia3.1plus(ta1104),I flash by ntool, every thing passed,but it still show that,the phone shutdown itself。please help me
same problem with my nokia 8 ta-1004
dugu1248 said:
I meet the same thing,but my phone is nokia3.1plus(ta1104),I flash by ntool, every thing passed,but it still show that,the phone shutdown itself。please help me
Click to expand...
Click to collapse
you must change your battery ,thats battery problem
Mihalsch said:
I had rooted Nokia 8 TA-1004(Android 9 ), but decided to switch back on 8.1
First step in instruction was to lock the bootloader to make a critical unlock
I used "fastboot oem lock" command and after that i got this notification:
"Your device is corrupt. It can't be truster and will not boot. Your device will shutdown in 30 seconds." And it's actually shutting down all the time without system load! =(
I can enter Download mode only. Platform tools also see my device (latest platform-tools_r28.0.1-windows). I couldn't access recovery mode. When i hold vol.+ and plug in USB, that warning shows again
What i've already tried:
fastboot flash unlock unlock.key (FAILED (remote: Fail to verify)
fastboot flash boot_a boot.img (Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash boot_b boot.img (Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot flash system_a system.img (Invalid sparse file format at header magic)
fastboot -i 0x2e04 flash unlock unlock.bin (FAILED (remote: Fail to verify)
fastboot -i 0x2e04 oem unlock-go (FAILED (remote: Flashing Unlock is not allowed)
fastboot set_active a (FAILED (remote: 'Slot Change is not allowed in Lock State)
fastboot set_active b (FAILED (remote: 'Slot Change is not allowed in Lock State)
adb sideload (
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found)
Help me please. IDK what to do. I do have my old unlock.key, but couldn't install it to open the bootloader....Any ideas, please :crying:
Click to expand...
Click to collapse
same device, same problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Error twrp

Please help, my devices after instal rom globe can not enter to recovery mode . .
And try reinstalling it TWRP not responding/unavailable
And try reinstalling TWRP recovery to devices in command ,
Failed ( remote : Failed to load/authenticate boot image : Load Error)

Deleted boot.img

I accidently deleted my boot.img on mi Mi 9 Lite (Mi CC9) by doing: fastboot boot "random file". What can I do now?
Can Someone please send me their boot.img or a link?
..
realseal3 said:
..
Click to expand...
Click to collapse
https://www.sendspace.com/file/nddami
:fingers-crossed:
Thank you very much but I get an error message:
Sending 'boot.img' (15360 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
realseal3 said:
Sending 'boot.img' (15360 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Click to expand...
Click to collapse
What's the rom you have, miui version?
miui_PYXISGlobal_V11.3.3.0.PFCMIXM_6a3205a4b8_9.0
I have this one but it didn't boot before I did anything.
lmt399 said:
What's the rom you have, miui version?
Click to expand...
Click to collapse
realseal3 said:
miui_PYXISGlobal_V11.3.3.0.PFCMIXM_6a3205a4b8_9.0
I have this one but it didn't boot before I did anything.
Click to expand...
Click to collapse
Bootloader unlocked/locked?
Maybe it is better to flash the whole system through fastboot or mi flash tool.
..
It didn't work with the tool but I reflashed twrp and flashed the stock miui rom from there and it worked. Thank you anyway.
Download Fastboot rom and extract, then copy system.img to fastboot folder and also recovery, boot.img too...
Open fastboot:
Type: fastboot format system
Type: Fastboot flash boot boot.img version that you have when you brick device
Type: Fastboot flash system system.img
Type: Fastboot flash recovery recovery.img use wzsx1050 3.3.1-0709 version
Type :Fastboot boot recovery.img and device should reboot in recovery, without Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')

Can't install TWRP on my X2 Pro Fastboot Error

Hello I have this problem with my realme X2 Pro
I wanted to install TWRP on my phone using ADB and Fastboot after unlocking with success my bootloader The problem Is I first intalled with success TWRP BUT the touch was not working so I decieded to try a newer version but now this error apears
Sending 'recovery' (98304 KB) OKAY [ 2.354s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Volume Full')
fastboot: error: Command failed
I Tried to do adb push twrp-3.4.0-0-RMX1931-mauronofrio.img /dev/block/bootdevice/by-name/recovery but i did not work It got me this error
adb: error: failed to get feature set: no devices/emulators found
If anyone could help me it would very apreciated
I though it was (from Fastboot mode):
Code:
fastboot flash recovery <your recovery image here>
and then
Code:
fastboot flash vbmeta vbmeta.img
Uqbar said:
I though it was (from Fastboot mode):
Code:
fastboot flash recovery <your recovery image here>
and then
Code:
fastboot flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Hello when I try to use fastboot flash recovery twrp.img that is creating the Volume full error
How can I solve it ?
Farchyk said:
Hello when I try to use fastboot flash recovery twrp.img that is creating the Volume full error
How can I solve it ?
Click to expand...
Click to collapse
Are you really really sure the twrp image is the right size?
Mauronofrio's one is exactly 81920 KB, not 98304 KB.
Also the official TWRP has the same size, AFAIK.
I would re-download it and maybe checksum it.

Categories

Resources