I use custom Rom in my game Moto G4 play, and at some point in time I try to get back to the rom stock, but I always get this error:
FAIL (Command write failed (argument invalid))
Or
Preflash validation failed
Another error is also (Data tranfer failure <Too many links>)
I already tried Rsd lite and it also did not work, and also clear by adbfastboot
This may have happened because in Twrp I deleted the system, internal memory, it was kind of a layman, and I was too curious, only able to use custom rom.
Nougat coming to G4 play and I with this problem.
Can anybody help me, thank you very much? :chorando:
I'm having this problem to go back to Stock ROM, my cell phone is a Moto G4 play xt1603, I use a custom ROM, have any tips, I already tried Rsd lite and nothing ...
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot oem fb_mode_set
...
OKAY [-0.000s]
Finished. Total time: -0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash partition gpt.bin
Target reported max download size of 268435456 bytes
Sending 'partition' (32 KB) ...
OKAY [0.078s]
Writing 'partition' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 0
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Freeboot flash bootloader bootloader.img
Target reported max download size of 268435456 bytes
Sending 'bootloader' (2546 KB) ...
OKAY [0.219s]
Writing 'bootloader' ...
(Bootloader) flashing sbl1 ...
(Bootloader) flashing aboot ...
(Bootloader) flashing tz ...
(Bootloader) flashing hyp ...
(Bootloader) flashing rpm ...
OKAY [1.722s]
Finished. Total time: 2
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
S)> fastboot flash logo logo.bin
Target reported max download size of 268435456 bytes
Sending 'logo' (751 KB) ...
FAILED (data transfer failure (Too many links))
Finished. Total time: 0.187s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
S)> fastboot flash boot boot.img
Sending 'boot' (16384 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
S)> fastboot flash recovery recovery.img
Sending 'recovery' (16484 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sblocked)> fastboot flash dsp adspso.bin
Error: can not open 'adspso.bin'
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
> Fastboot flash oem oem.img
Sending 'oem' (13464 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: -0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
> Fastboot flash system system.img_sparsechunk.0
Sending 'system' (262141 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.1
Sending 'system' (262142 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: -0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.2
Sending 'system' (262140 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.3
Sending 'system' (259676 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: -0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
> Fastboot flash system system.img_sparsechunk.4
Sending 'system' (262140 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.5
Sending 'system' (262141 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: -0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.6
Sending 'system' (262142 KB) ...
FAILED (command write failed (Invalid argument))
Finished.
Try flashing from a shorter path and remove spaces, Windows (and even Linux) are kinda stupid on handling these types of path, mainly Windows.
I'm almost sure it's handling it like: C:\Users\Vin\ius\Downloads\Roms\Rom3\ADB at every command not matter what you write.
Related
Hello,
a friend gave me hier "bricked" fon. I could get it booting again, system is up and running - but with any sdcard. Not the external and neither the internal one.
That means I cant put a SAPIMG.nph or anything else to the sdcard.
I cant download an apk or modify anything.
adb shell is working, but certainly su not.
adb push hboot_2010_signed.img /sdcard
certainly doesnt work either, there is no sdcard!
ok, I tried now different fastboot operations.
to come closer:
./fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img
sending 'recovery' (4528 KB)... FAILED (remote: not allow)
... etc... all the normal stuff.. nothing wortks, I usualy get "Not allowed on a production phone"
What to do now, I have no clue anymore!
here my data:
./fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x880705C0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 64
INFOTAG:hwid 0x1
INFOTAG:skuid 0x1E300
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x2
INFODevice CID is not super CID
INFOCID is VODAP102
INFOsetting.cid::VODAP102
INFOserial number: HT93YKF06262
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =346
INFOactive commandline: board_sapphire.disable_uart3=1 board_sap
INFOphire.usb_h2w_sw=1 board_sapphire.disable_sdcard=1 smisize=6
INFO4 androidboot.baseband=2.22.19.26I androidboot.cid=VODAP102
INFO androidboot.carrier=VODA-Germany androidboot.keycaps=qwerty
INFO androidboot.mode=normal androidboot.serialno=HT93YKF06262 a
INFOndroidboot.bootloader=1.33.0007 no_console_suspend=1 console
INFO=null
INFOPARTITIOM_NUM_MAX =6 Valid partition num=6
Do you see? There is the kernel option board_sapphire.disable_sdcard=1 set !!! But I cant disable it with a fastboot -c option.
./fastboot getvar version-main
version-main: 1.89.162.1
./fastboot getvar cid
cid: VODAP102C??a
#########
Any help is appreciated, thanks!
Code:
fastboot oem enableqxdm 0
Regarding root... follow my guide found in my signature..
./fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
./fastboot devices
HT93YKF06262 fastboot
[[email protected] HTC]# ./fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img
sending 'recovery' (4528 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
this seemed to get me a little further:
./fastboot oem rebootRUU
... OKAY
[[email protected] HTC]# ./fastboot -c "board_sapphire.disable_sdcard=0 board_sapphire.disable_uart3=0" reboot
rebooting...
YEAH!"
but then..... still no sdcard when the OS was up :-(
any ideas?
Type
Code:
fastboot oem h
and post here the result.
Root and recovery = follow my guide found in my signature...
Just replace all "/sdcard" paths with "/data/local/tmp"
Zenfone ZE552KL stuck at ASUS boot logo and can only access fastboot. I tried using asus flash tool and whenever I flash stock oreo raw image it fails and status says FAILED(remote: writing partition failed)
I tried extracting the raw zip and run cmd command flashall_AFT.cmd WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw and this is the result
Code:
##################################################################
####################### FLASH RAW FILE ########################
##################################################################
## RAW: WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
## ERASE DATA: 0
## SSN:
===================================================================
[command] : fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android N 7.1.1)
// Version V1.4 (2017/05/20)
// Support_AB : 0
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 534773760 bytes
sending 'partition' CRC (0x3016d48d)...
OKAY [ 0.029s]
writing 'CRC'...
OKAY [ 0.022s]
sending 'partition' (33 KB)...
OKAY [ 0.062s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.227s
"FAILED, fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw failure, EXIT!"
The phone is not mine, a friend asked me to fix his phone and I hit a wall here. I cannot flash nor boot twrp.img. Whenever I try to flash twrp it fails and the error is remote: too many links. Any insights?
rexendz said:
Zenfone ZE552KL stuck at ASUS boot logo and can only access fastboot. I tried using asus flash tool and whenever I flash stock oreo raw image it fails and status says FAILED(remote: writing partition failed)
I tried extracting the raw zip and run cmd command flashall_AFT.cmd WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw and this is the result
Code:
##################################################################
####################### FLASH RAW FILE ########################
##################################################################
## RAW: WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
## ERASE DATA: 0
## SSN:
===================================================================
[command] : fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android N 7.1.1)
// Version V1.4 (2017/05/20)
// Support_AB : 0
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 534773760 bytes
sending 'partition' CRC (0x3016d48d)...
OKAY [ 0.029s]
writing 'CRC'...
OKAY [ 0.022s]
sending 'partition' (33 KB)...
OKAY [ 0.062s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.227s
"FAILED, fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw failure, EXIT!"
The phone is not mine, a friend asked me to fix his phone and I hit a wall here. I cannot flash nor boot twrp.img. Whenever I try to flash twrp it fails and the error is remote: too many links. Any insights?
Click to expand...
Click to collapse
Please guys, help me, I still can boot into fastboot, but can't boot into twrp(even flashing it via fastboot recovery_ramdisk) or erecovery
Successfully repaired ...:good:
I also met
How did you repair your device? I have the same problem, please help!
Sorry for my English language....
Download https://drive.google.com/file/d/1uMrmObOb78_2dp8I6rVEOJ1s9Dg8QJDs/view
extracted zip
Open -- tools_fw -- FW --remove all files
Open -- update-L09 -- remove all files
Open --update-L29 -- remove all files
Open -- Update APP Unpacker --- copy the folder - UPDATE.APP - service ROM - Huawei P10 Lite [ https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
]
Click ---- UNPACKER_RUN_ME.bat extract update.app ... Finished .... Open - output -- extracted file copy All to - tools_fw - FW....
open --- / tools_fw / - /update-L09 /
or /update-L29/ copy folder - CUST.img , USERDATA.img , VERSION.img
Connect a fastbootmode phone
CLICK 1. revive flasher ... flashed extract file ... Finished ... restart phone
Sending 'cache' (6200 KB) OKAY [ 0.148s]
Writing 'cache' OKAY [ 0.083s]
Finished. Total time: 0.265s
Sending 'crc' (273 KB) OKAY [ 0.009s]
Writing 'crc' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
Sending 'bla bla............'
Click to expand...
Click to collapse
IGNORED the Writing FAILED (remote: 'partition length get error')
Everything after this was correctly flashed.
I repaired it successfully
error: FUNC 8 : HIFI Image, Error 1 Security Verify failed
error:FUNC 11
[UNBRICK] P10 VTR-L09/VTR-L29 unbrick XLOADER2 failed downgrades with free tools.
https://forum.xda-developers.com/p10/how-to/unbrick-p10-vtr-l09-vtr-l29-unbrick-t3916694
Ashle said:
Sorry for my English language....
Download https://drive.google.com/file/d/1uMrmObOb78_2dp8I6rVEOJ1s9Dg8QJDs/view
extracted zip
Open -- tools_fw -- FW --remove all files
Open -- update-L09 -- remove all files
Open --update-L29 -- remove all files
Open -- Update APP Unpacker --- copy the folder - UPDATE.APP - service ROM - Huawei P10 Lite [ https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 ]
Click ---- UNPACKER_RUN_ME.bat extract update.app ... Finished .... Open - output -- extracted file copy All to - tools_fw - FW....
open --- / tools_fw / - /update-L09 /
or /update-L29/ copy folder - CUST.img , USERDATA.img , VERSION.img
Connect a fastbootmode phone
CLICK 1. revive flasher ... flashed extract file ... Finished ... restart phone
IGNORED the Writing FAILED (remote: 'partition length get error')
Everything after this was correctly flashed.
I repaired it successfully
error: FUNC 8 : HIFI Image, Error 1 Security Verify failed
error:FUNC 11
[UNBRICK] P10 VTR-L09/VTR-L29 unbrick XLOADER2 failed downgrades with free tools.
https://forum.xda-developers.com/p10/how-to/unbrick-p10-vtr-l09-vtr-l29-unbrick-t3916694
Click to expand...
Click to collapse
It gives many errors like "command not allowed" and many missing files...
angushev20 said:
It gives many errors like "command not allowed" and many missing files...
Click to expand...
Click to collapse
P10 VTR-L09/VTR-L29 unbrick XLOADER2 failed downgrades with free tools.
https://forum.xda-developers.com/p10/how-to/unbrick-p10-vtr-l09-vtr-l29-unbrick-t3916694
IGNORED - hisee,hisiufs,isp file P10 -- NO P10Lite file stock rom ....
IGNORED- Writing 'crc' FAILED (remote: 'partition length get error')
curver,
IGNORED the Writing FAILED (remote: 'partition length get error')
Everything after this was correctly flashed.
flashed extract file ... Finished ... restart phone
Code:
fastboot: error: cannot load 'fw\vector.img': No such file or directory
fastboot: error: cannot load 'fw\hisee_fs.img': No such file or directory
fastboot: error: cannot load 'fw\hisee_img.img': No such file or directory
fastboot: error: cannot load 'fw\isp_firmware.img': No such file or directory
fastboot: error: cannot load 'fw\HISIUFS_GPT.img': No such file or directory
Sending 'crc' (233 KB) OKAY [ 0.283s]
Writing 'crc' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
Sending 'curver' (0 KB) OKAY [ 0.273s]
Writing 'curver' FAILED (remote: 'partition length get error')
Sending 'modem_fw' (98304 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
Sending 'package_type' (0 KB) OKAY [ 0.193s]
Writing 'package_type' FAILED (remote: 'partition length get error')
Sending 'sha256rsa' (0 KB) OKAY [ 0.002s]
Writing 'sha256rsa' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
Hi all
My phone is in bootloop since many day. I was on Lineage 18.1 with deezer and google maps installed (only theses 2 apps)
After turning off (for the first time) because there was no battery left. It never restarted
And even worse, the erecoevery is no longer accessible, the TWRP is broken ..
I only have access to Fastboot.
I tested flashing a TWRP or booting on a TWRP via fastboot command ... Impossible. It crashes before splash to the TWRP. (which appears an half second)
I tested hisuite which recognizes my phone in fastboot but does not recognize the model and refuses to restore a system: "device not supported"
I am trying to flash a complete system (via command terminal or via ZRK tool) = impossible to reboot
Bellow the result of my commands
Does anyone have a suggestion for me ?
Code:
./fastboot erase system -w
Erasing 'system' OKAY [ 75.573s]
Finished. Total time: 75.632s
./fastboot flash cache CACHE.img
Sending 'cache' (6200 KB) OKAY [ 0.175s]
Writing 'cache' OKAY [ 0.176s]
Finished. Total time: 0.379s
./fastboot flash crc CRC.img
Sending 'crc' (235 KB) OKAY [ 0.013s]
Writing 'crc' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash curver CURVER.img
Sending 'curver' (0 KB) OKAY [ 0.007s]
Writing 'curver' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash dts DTS.img
Sending 'dts' (23678 KB) OKAY [ 0.679s]
Writing 'dts' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash efi EFI.img
Sending 'efi' (17 KB) OKAY [ 0.007s]
Writing 'efi' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash kernel KERNEL.img
Sending 'kernel' (24576 KB) OKAY [ 0.698s]
Writing 'kernel' OKAY [ 0.865s]
Finished. Total time: 1.590s
./fastboot flash modem_fw MODEM_FW.img
Sending 'modem_fw' (98304 KB) OKAY [ 2.745s]
Writing 'modem_fw' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash modemnvm_update MODEMNVM_UPDATE.img
Sending 'modemnvm_update' (14224 KB) OKAY [ 0.396s]
Writing 'modemnvm_update' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash odm ODM.img
Sending 'odm' (109702 KB) OKAY [ 3.108s]
Writing 'odm' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash package_type PACKAGE_TYPE.img
Sending 'package_type' (0 KB) OKAY [ 0.007s]
Writing 'package_type' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash product PRODUCT.img
Sending 'product' (113532 KB) OKAY [ 3.186s]
Writing 'product' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash ramdisk RAMDISK.img
Sending 'ramdisk' (16384 KB) OKAY [ 0.464s]
Writing 'ramdisk' OKAY [ 0.398s]
Finished. Total time: 0.890s
./fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 0.930s]
Writing 'recovery_ramdisk' OKAY [ 0.800s]
Finished. Total time: 1.760s
./fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
Sending 'recovery_vbmeta' (6 KB) OKAY [ 0.007s]
Writing 'recovery_vbmeta' OKAY [ 0.030s]
Finished. Total time: 0.067s
./fastboot flash recovery_vendor RECOVERY_VENDOR.img
Sending 'recovery_vendor' (16384 KB) OKAY [ 0.464s]
Writing 'recovery_vendor' OKAY [ 0.401s]
Finished. Total time: 0.896s
./fastboot flash sensorhub SENSORHUB.img
Sending 'sensorhub' (820 KB) OKAY [ 0.027s]
Writing 'sensorhub' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash system SYSTEM.img
Sending sparse 'system' 1/6 (460799 KB) OKAY [ 13.234s]
Writing 'system' OKAY [ 12.118s]
Sending sparse 'system' 2/6 (460074 KB) OKAY [ 13.597s]
Writing 'system' OKAY [ 12.556s]
Sending sparse 'system' 3/6 (460751 KB) OKAY [ 13.416s]
Writing 'system' OKAY [ 11.778s]
Sending sparse 'system' 4/6 (453466 KB) OKAY [ 13.196s]
Writing 'system' OKAY [ 11.609s]
Sending sparse 'system' 5/6 (454756 KB) OKAY [ 12.975s]
Writing 'system' OKAY [ 11.150s]
Sending sparse 'system' 6/6 (418060 KB) OKAY [ 11.904s]
Writing 'system' OKAY [ 10.762s]
Finished. Total time: 148.684s
./fastboot flash teeos TEEOS.img
Sending 'teeos' (2576 KB) OKAY [ 0.075s]
Writing 'teeos' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash trustfirmware TRUSTFIRMWARE.img
Sending 'trustfirmware' (115 KB) OKAY [ 0.010s]
Writing 'trustfirmware' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash vbmeta VBMETA.img
Sending 'vbmeta' (9 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.027s]
Finished. Total time: 0.060s
./fastboot flash vendor VENDOR.img
Sending sparse 'vendor' 1/2 (460710 KB) OKAY [ 13.273s]
Writing 'vendor' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash verlist VERLIST.img
Sending 'verlist' (0 KB) OKAY [ 0.007s]
Writing 'verlist' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash xloader XLOADER.img
Sending 'xloader' (68 KB) OKAY [ 0.008s]
Writing 'xloader' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
naced said:
Hi all
My phone is in bootloop since many day. I was on Lineage 18.1 with deezer and google maps installed (only theses 2 apps)
After turning off (for the first time) because there was no battery left. It never restarted
And even worse, the erecoevery is no longer accessible, the TWRP is broken ..
I only have access to Fastboot.
I tested flashing a TWRP or booting on a TWRP via fastboot command ... Impossible. It crashes before splash to the TWRP. (which appears an half second)
I tested hisuite which recognizes my phone in fastboot but does not recognize the model and refuses to restore a system: "device not supported"
I am trying to flash a complete system (via command terminal or via ZRK tool) = impossible to reboot
Bellow the result of my commands
Does anyone have a suggestion for me ?
Code:
./fastboot erase system -w
Erasing 'system' OKAY [ 75.573s]
Finished. Total time: 75.632s
./fastboot flash cache CACHE.img
Sending 'cache' (6200 KB) OKAY [ 0.175s]
Writing 'cache' OKAY [ 0.176s]
Finished. Total time: 0.379s
./fastboot flash crc CRC.img
Sending 'crc' (235 KB) OKAY [ 0.013s]
Writing 'crc' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash curver CURVER.img
Sending 'curver' (0 KB) OKAY [ 0.007s]
Writing 'curver' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash dts DTS.img
Sending 'dts' (23678 KB) OKAY [ 0.679s]
Writing 'dts' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash efi EFI.img
Sending 'efi' (17 KB) OKAY [ 0.007s]
Writing 'efi' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash kernel KERNEL.img
Sending 'kernel' (24576 KB) OKAY [ 0.698s]
Writing 'kernel' OKAY [ 0.865s]
Finished. Total time: 1.590s
./fastboot flash modem_fw MODEM_FW.img
Sending 'modem_fw' (98304 KB) OKAY [ 2.745s]
Writing 'modem_fw' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash modemnvm_update MODEMNVM_UPDATE.img
Sending 'modemnvm_update' (14224 KB) OKAY [ 0.396s]
Writing 'modemnvm_update' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash odm ODM.img
Sending 'odm' (109702 KB) OKAY [ 3.108s]
Writing 'odm' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash package_type PACKAGE_TYPE.img
Sending 'package_type' (0 KB) OKAY [ 0.007s]
Writing 'package_type' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash product PRODUCT.img
Sending 'product' (113532 KB) OKAY [ 3.186s]
Writing 'product' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash ramdisk RAMDISK.img
Sending 'ramdisk' (16384 KB) OKAY [ 0.464s]
Writing 'ramdisk' OKAY [ 0.398s]
Finished. Total time: 0.890s
./fastboot flash recovery_ramdisk RECOVERY_RAMDISK.img
Sending 'recovery_ramdisk' (32768 KB) OKAY [ 0.930s]
Writing 'recovery_ramdisk' OKAY [ 0.800s]
Finished. Total time: 1.760s
./fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
Sending 'recovery_vbmeta' (6 KB) OKAY [ 0.007s]
Writing 'recovery_vbmeta' OKAY [ 0.030s]
Finished. Total time: 0.067s
./fastboot flash recovery_vendor RECOVERY_VENDOR.img
Sending 'recovery_vendor' (16384 KB) OKAY [ 0.464s]
Writing 'recovery_vendor' OKAY [ 0.401s]
Finished. Total time: 0.896s
./fastboot flash sensorhub SENSORHUB.img
Sending 'sensorhub' (820 KB) OKAY [ 0.027s]
Writing 'sensorhub' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash system SYSTEM.img
Sending sparse 'system' 1/6 (460799 KB) OKAY [ 13.234s]
Writing 'system' OKAY [ 12.118s]
Sending sparse 'system' 2/6 (460074 KB) OKAY [ 13.597s]
Writing 'system' OKAY [ 12.556s]
Sending sparse 'system' 3/6 (460751 KB) OKAY [ 13.416s]
Writing 'system' OKAY [ 11.778s]
Sending sparse 'system' 4/6 (453466 KB) OKAY [ 13.196s]
Writing 'system' OKAY [ 11.609s]
Sending sparse 'system' 5/6 (454756 KB) OKAY [ 12.975s]
Writing 'system' OKAY [ 11.150s]
Sending sparse 'system' 6/6 (418060 KB) OKAY [ 11.904s]
Writing 'system' OKAY [ 10.762s]
Finished. Total time: 148.684s
./fastboot flash teeos TEEOS.img
Sending 'teeos' (2576 KB) OKAY [ 0.075s]
Writing 'teeos' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash trustfirmware TRUSTFIRMWARE.img
Sending 'trustfirmware' (115 KB) OKAY [ 0.010s]
Writing 'trustfirmware' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash vbmeta VBMETA.img
Sending 'vbmeta' (9 KB) OKAY [ 0.007s]
Writing 'vbmeta' OKAY [ 0.027s]
Finished. Total time: 0.060s
./fastboot flash vendor VENDOR.img
Sending sparse 'vendor' 1/2 (460710 KB) OKAY [ 13.273s]
Writing 'vendor' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash verlist VERLIST.img
Sending 'verlist' (0 KB) OKAY [ 0.007s]
Writing 'verlist' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
./fastboot flash xloader XLOADER.img
Sending 'xloader' (68 KB) OKAY [ 0.008s]
Writing 'xloader' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
Hi...
you write that you flashed a TWRP via fastboot and then try to reboot from fastboot mode to TWRP recovery right?
But there is no command to reboot from fastboot directly to recovery like fastboot reboot-recovery or some thing else!
you just can use the command fastboot reboot
then instant unplug the usb-cable and press/hold Vol+ button
i repeat...
fastboot reboot-->enter
unplug the usb cable
press and hold Vol+ button (just the 1 button Vol+ nothing more needet)
good luck
solong
speedson
Receiving the following error.. bootp is my patched image.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot C:\Users\Scott\Pictures\bootp.img
target reported max download size of 268435456 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.656s]
writing 'boot_a'...
(bootloader) Image missing cmdline or OS version
FAILED (remote: Failed to write to partition Bad Buffer Size)
finished. total time: 2.954s