Database Users

Flash help. Image won't load

To say the least, I got into more than I really wanted to. I have a Motorola droid razr m model XT907. It's rooted and GSM unlocked. I'm using it on Straight Talk currently. I'm pretty sure the bootloader's unlocked. Anyway, I tried to do a full restore from TBU. Granted, I probably did it wrong. When finished, it seemed like everything error-ed with it telling me that app or service has stopped working. So, I tried to reset back to factory. It would never finish booting. I tried to restore with the same result. There's no backup or anything on the SD card. Since then I've been trying to flash a new rom in it. I used House of Moto. It seemed the simplest way. After a lot of confusion, I finally figured out how to do it, maybe. I downloaded the correct files and arranged them according to the instructions. When I run it, it seems to do fine until the end, then it says it couldn't load the image file. So now I have an operating system that can't finish booting because it has nothing inside. Here's the log from House of Moto:
Please ensure your phone is:
o] Charged
o] Connected to USB using your OEM cable
o] USB drivers are installed
o] Booted to AP Fastboot mode: [power off, hold volume down and press power]
Ready to flash...
Press any key to continue . . .
Flashing: FULL_xt907.bat
1 file(s) copied.
1 file(s) copied.
1 file(s) copied.
1 file(s) copied.
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.014s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.296s
sending 'sbl1' (100 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.562s]
finished. total time: 0.581s
sending 'sbl2' (126 KB)...
OKAY [ 0.020s]
writing 'sbl2'...
OKAY [ 1.308s]
finished. total time: 1.330s
sending 'sbl3' (512 KB)...
OKAY [ 0.050s]
writing 'sbl3'...
OKAY [ 1.315s]
finished. total time: 1.365s
sending 'rpm' (140 KB)...
OKAY [ 0.066s]
writing 'rpm'...
OKAY [ 0.569s]
finished. total time: 0.638s
sending 'tz' (192 KB)...
OKAY [ 0.025s]
writing 'tz'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.319s
sending 'aboot' (256 KB)...
OKAY [ 0.030s]
writing 'aboot'...
OKAY [ 1.429s]
finished. total time: 1.461s
sending 'modem' (30720 KB)...
OKAY [ 2.311s]
writing 'modem'...
OKAY [ 2.793s]
sending 'modem' (17576 KB)...
OKAY [ 5.446s]
writing 'modem'...
OKAY [ 4.869s]
finished. total time: 15.423s
sending 'fsg' (2794 KB)...
OKAY [ 0.221s]
writing 'fsg'...
OKAY [ 2.268s]
finished. total time: 2.491s
erasing 'modemst1'...
OKAY [ 0.931s]
finished. total time: 0.932s
erasing 'modemst2'...
OKAY [ 1.319s]
finished. total time: 1.320s
sending 'logo' (1709 KB)...
OKAY [ 0.140s]
writing 'logo'...
OKAY [ 2.580s]
finished. total time: 2.720s
sending 'devtree' (512 KB)...
OKAY [ 0.049s]
writing 'devtree'...
OKAY [ 1.196s]
finished. total time: 1.248s
sending 'boot' (10240 KB)...
OKAY [ 1.148s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.458s
sending 'recovery' (10240 KB)...
OKAY [ 0.778s]
writing 'recovery'...
OKAY [ 3.790s]
finished. total time: 4.570s
sending 'cdrom' (30720 KB)...
OKAY [ 2.587s]
writing 'cdrom'...
OKAY [ 4.473s]
sending 'cdrom' (22538 KB)...
OKAY [ 6.005s]
writing 'cdrom'...
OKAY [ 7.602s]
finished. total time: 20.671s
error: cannot load 'system.img.ext4'
erasing 'cache'...
OKAY [ 2.697s]
finished. total time: 2.698s
erasing 'userdata'...
OKAY [ 2.843s]
finished. total time: 2.844s
erasing 'tombstones'...
OKAY [ 1.698s]
finished. total time: 1.699s
rebooting...
finished. total time: 0.009s
Press any key to continue . . .
I tried the last two firmwares on this list. I have Android 4.1.2 installed. (Or at lease I did)
I used the fastboot scripts and rsd scripts from here
I don't know what I'm doing. I hope somebody can tell me what part is wrong. Help! I need my phone back.

Boot in to fast boot menu... Power device off then power on while holding all three buttons...volume up + volume down + power... Please provide the information listed on screen... Boot loader status..fast boot menu version and date...
Sent from my XT907 using xda app-developers app

:AP fastboot info
Here ya go:
AP Fastboot Flash Mode (S)
10.98(*) (sha-1e9f577, 2012-10-21 17:10:35)
EMMC Info: Size 8GB
I think I read it right, but here's a pic

Try this...http://forum.xda-developers.com/showthread.php?t=2249773 option one... Then make sure you unlock the boot loader before any update or you won't be able to later
Sent from my XT907 using xda app-developers app

Alright I'm ready to go for it, but the first thing I saw was "DO NOT USE THIS UTILITY ON THE LATEST 4.1.2 OTA UPDATE". Are they talking about my Android version, or the 98.18.78 update?

Update .78/.3... The version on your device is older then the one it flashes
Sent from my XT907 using xda app-developers app

That worked perfectly. All I have to do now is root it, unlock the bootloader and GSM again. I'll take the latest OTA when I finish that.
I can't thank you enough

Happy it worked for you...
Sent from my XT907 using xda app-developers app

I have a custom rom for this phone that's been debloated. Can I just swap the system image and XML document in the razr utility and flash it like I just did?

[Q] Problem in downgrade to 4.4.4

dear
i have Lg Nexus4 want to downgrade from lollipop to kitkat
i did download 4.4.4 file occam-ktu84p
after i connected my phone in fastboot and run the flash-all.bat
after loading some files it failed
for me i dont want to keep backup so i need flash-W so i keep bootloader locked
sending 'bootloader' (2203 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.109s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.605s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.621s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 748585716 bytes
error: update package missing system.img
Press any key to exit...
i show also image of file i used

almoudamer said:
dear
i have Lg Nexus4 want to downgrade from lollipop to kitkat
i did download 4.4.4 file occam-ktu84p
after i connected my phone in fastboot and run the flash-all.bat
after loading some files it failed
for me i dont want to keep backup so i need flash-W so i keep bootloader locked
sending 'bootloader' (2203 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.109s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.605s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.621s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 748585716 bytes
error: update package missing system.img
Press any key to exit...
i show also image of file i used
Click to expand...
Click to collapse
You need unlocked bootloader to flash image.
Sent from my Nexus 4 using XDA Free mobile app

Hello
thxfor ur quick reply
i did unlock bootloader and tested again ,but still facing this same problem as update package missing system.img even it is available in zip file if we open as i showed in before picture
sending 'bootloader' (2203 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
OKAY [ 0.296s]
finished. total time: 0.374s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.641s]
writing 'radio'...
OKAY [ 2.605s]
finished. total time: 4.262s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 748585716 bytes
error: update package missing system.img
Press any key to exit...
br

Hardware problem?

Hi there
I've got an old Nexus 10 that recently got stuck in a bootloop, so I booted into recovery and did a factory reset. After a few boots and updates everything seemed ok, but then it just died and went into a bootloop again.
I've flashed TWRP recovery, but no partitions are mounted or mountable and attempts to repair file system make the screen go squiggly (corrupted/interference) and then the tablet reboots into bootloader.
Is this likely to be a hardware issue or is there more I can try?
Slainte
mmidders
P.S. also tried flashing the stock ROM using flash-all.sh, output appended:
erasing 'boot'...
OKAY [ 0.022s]
finished. total time: 0.023s
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.097s
erasing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.150s]
finished. total time: 0.150s
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.373s]
finished. total time: 0.373s
target didn't report max-download-size
sending 'bootloader' (1280 KB)...
OKAY [ 0.192s]
writing 'bootloader'...
OKAY [ 0.115s]
finished. total time: 0.307s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.454s
< waiting for any device >
extracting android-info.txt (0 MB)...
extracting boot.img (4 MB)...
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (5 MB)...
archive does not contain 'recovery.sig'
extracting system.img (641 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-poiJRI: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

Update:
I updated adb and fastboot and ran the flash-all.sh script again with the following output (now waiting for first boot):
Erasing 'boot' OKAY [ 0.022s]
Finished. Total time: 0.025s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.093s]
Finished. Total time: 0.095s
Erasing 'recovery' OKAY [ 0.025s]
Finished. Total time: 0.027s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'system' OKAY [ 0.150s]
Finished. Total time: 0.153s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata' OKAY [ 0.372s]
Finished. Total time: 0.375s
Sending 'bootloader' (1280 KB) OKAY [ 0.194s]
Writing 'bootloader' OKAY [ 0.132s]
Finished. Total time: 0.330s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.453s
< waiting for any device >
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32F200S5XR
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
extracting boot.img (4 MB) to disk... took 0.018s
archive does not contain 'boot.sig'
Sending 'boot' (4966 KB) OKAY [ 0.745s]
Writing 'boot' OKAY [ 0.118s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (5 MB) to disk... took 0.028s
archive does not contain 'recovery.sig'
Sending 'recovery' (5532 KB) OKAY [ 0.851s]
Writing 'recovery' OKAY [ 0.121s]
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (641 MB) to disk... took 6.544s
archive does not contain 'system.sig'
Sending 'system' (657130 KB) OKAY [ 96.291s]
Writing 'system' OKAY [ 15.845s]
archive does not contain 'system_ext.img'
archive does not contain 'vendor.img'
Erasing 'userdata' OKAY [ 0.371s]
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-3eTxBH: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata

URGENT!! RN7 (lavender) stopped working suddenly

Hi everybody!
I installed Xiaomi.eu 12 stable few weeks ago and the device worked perfectly until this morning. When I unlocked the screen and clicked on the toggle wifi to activate it, the device stopped working. Totally freezed.
I tried with a reboot but the device was stuck to the boot logo. So I've tried to enter the recovery mode (Orange Fox in my case) and also it was stuck in the Orangefox logo. The only thing which works is fastboot.
So I decided to try to reset the phone, without success in all the cases. Here all my attempts:
1) Install other recoveries with fastboot (Orangefox, TWRP, Stock recovery) and depite the installation succeed, none of them worked; when I try to enter the recovery mode, it's still stuck into OrangeFox logo (also after I've installed other recoveries).
2) Install MIUI global fastboot rom with MiFlash tool. It reports error xbl.
3) The last thing I tried: several attempts with fastboot and MIUI global fastboot ROMs. In all the cases the reported error was the write protection of xbl.
NB: I used both command prompt of linux and windows without success.
Code:
[[email protected] lavender1]$ sudo ./flash_all.sh
product: lavender
Sending 'antirbpass' (8 KB) OKAY [ 0.005s]
Writing 'antirbpass' OKAY [ 0.000s]
Finished. Total time: 0.013s
Sending 'xbl' (2512 KB) OKAY [ 0.075s]
Writing 'xbl' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'xblbak' (2512 KB) OKAY [ 0.076s]
Writing 'xblbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'tz' (1924 KB) OKAY [ 0.061s]
Writing 'tz' OKAY [ 0.013s]
Finished. Total time: 0.082s
Sending 'tzbak' (1924 KB) OKAY [ 0.060s]
Writing 'tzbak' OKAY [ 0.014s]
Finished. Total time: 0.076s
Sending 'rpm' (219 KB) OKAY [ 0.015s]
Writing 'rpm' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'rpmbak' (219 KB) OKAY [ 0.011s]
Writing 'rpmbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'hyp' (272 KB) OKAY [ 0.011s]
Writing 'hyp' OKAY [ 0.002s]
Finished. Total time: 0.016s
Sending 'hypbak' (272 KB) OKAY [ 0.011s]
Writing 'hypbak' OKAY [ 0.003s]
Finished. Total time: 0.016s
Sending 'pmic' (38 KB) OKAY [ 0.006s]
Writing 'pmic' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'pmicbak' (38 KB) OKAY [ 0.002s]
Writing 'pmicbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'keymaster' (305 KB) OKAY [ 0.012s]
Writing 'keymaster' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'keymasterbak' (305 KB) OKAY [ 0.010s]
Writing 'keymasterbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'cmnlib' (216 KB) OKAY [ 0.010s]
Writing 'cmnlib' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'cmnlibbak' (216 KB) OKAY [ 0.011s]
Writing 'cmnlibbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'cmnlib64' (267 KB) OKAY [ 0.015s]
Writing 'cmnlib64' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'cmnlib64bak' (267 KB) OKAY [ 0.011s]
Writing 'cmnlib64bak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'mdtpsecapp' (1053 KB) OKAY [ 0.030s]
Writing 'mdtpsecapp' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'mdtpsecappbak' (1053 KB) OKAY [ 0.035s]
Writing 'mdtpsecappbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'modem' (111873 KB) OKAY [ 3.123s]
Writing 'modem' OKAY [ 0.745s]
Finished. Total time: 3.876s
Sending 'dsp' (16384 KB) OKAY [ 0.454s]
Writing 'dsp' OKAY [ 0.110s]
Finished. Total time: 0.571s
Sending 'bluetooth' (556 KB) OKAY [ 0.024s]
Writing 'bluetooth' OKAY [ 0.004s]
Finished. Total time: 0.031s
Sending 'storsec' (48 KB) OKAY [ 0.004s]
Writing 'storsec' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'storsecbak' (48 KB) OKAY [ 0.012s]
Writing 'storsecbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'devcfg' (47 KB) OKAY [ 0.011s]
Writing 'devcfg' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'devcfgbak' (47 KB) OKAY [ 0.012s]
Writing 'devcfgbak' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'abl' (148 KB) OKAY [ 0.012s]
Writing 'abl' OKAY [ 0.002s]
Finished. Total time: 0.016s
Sending 'ablbak' (148 KB) OKAY [ 0.012s]
Writing 'ablbak' OKAY [ 0.002s]
Finished. Total time: 0.016s
Sending 'dtbo' (8192 KB) OKAY [ 0.251s]
Writing 'dtbo' OKAY [ 0.055s]
Finished. Total time: 0.310s
Sending 'dtbobak' (8192 KB) OKAY [ 0.228s]
Writing 'dtbobak' OKAY [ 0.055s]
Finished. Total time: 0.286s
Sending 'vbmeta' (4 KB) OKAY [ 0.004s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.012s
Sending 'vbmetabak' (4 KB) OKAY [ 0.003s]
Writing 'vbmetabak' OKAY [ 0.001s]
Finished. Total time: 0.006s
Sending 'boot' (65536 KB) OKAY [ 1.860s]
Writing 'boot' OKAY [ 0.437s]
Finished. Total time: 2.301s
Sending 'recovery' (65536 KB) OKAY [ 1.836s]
Writing 'recovery' OKAY [ 0.437s]
Finished. Total time: 2.276s
Sending sparse 'system' 1/5 (786428 KB) OKAY [ 22.248s]
Writing 'system' OKAY [ 0.000s]
Sending sparse 'system' 2/5 (786428 KB) OKAY [ 22.449s]
Writing 'system' OKAY [ 0.000s]
Sending sparse 'system' 3/5 (786428 KB) OKAY [ 21.480s]
Writing 'system' OKAY [ 0.000s]
Sending sparse 'system' 4/5 (786428 KB) OKAY [ 21.680s]
Writing 'system' OKAY [ 0.000s]
Sending sparse 'system' 5/5 (327952 KB) OKAY [ 9.250s]
Writing 'system' OKAY [ 0.000s]
Finished. Total time: 97.119s
Sending sparse 'vendor' 1/2 (786428 KB) OKAY [ 21.900s]
Writing 'vendor' OKAY [ 0.000s]
Sending sparse 'vendor' 2/2 (57832 KB) OKAY [ 5.300s]
Writing 'vendor' OKAY [ 0.000s]
Finished. Total time: 29.298s
Sending 'userdata' (367876 KB) OKAY [ 10.647s]
Writing 'userdata' OKAY [ 0.000s]
Finished. Total time: 10.944s
Sending 'mdtp' (17390 KB) OKAY [ 0.483s]
Writing 'mdtp' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Sending 'cache' (128 KB) OKAY [ 0.005s]
Writing 'cache' OKAY [ 0.002s]
Finished. Total time: 0.017s
Sending 'splash' (26594 KB) OKAY [ 0.760s]
Writing 'splash' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
Erasing 'ddr' OKAY [ 0.001s]
Finished. Total time: 0.003s
Erasing 'misc' OKAY [ 0.001s]
Finished. Total time: 0.002s
Erasing 'apdp' OKAY [ 0.001s]
Finished. Total time: 0.003s
Erasing 'msadp' OKAY [ 0.001s]
Finished. Total time: 0.003s
Sending 'cust' (248280 KB) OKAY [ 7.047s]
Writing 'cust' OKAY [ 0.000s]
Finished. Total time: 7.064s
Rebooting OKAY [ 1.574s]
In windows, when I do "flash_all" it stops at write error in xbl; but when I try with linux, the terminal follows all the script, writing down all the errors. As is possible to see in the code above, there are other errors of "write protection";
Any suggest of how to proceed?
[UPDATE]
I tried the test of emmc as suggested below and the result is that the memory is broken. Thanks for the support!

probably broken emmc ? could you access data partition using fastboot, try to paste 1gb of data to there, restart the phone enter fastboot again and copy the data to your pc, use sha256 to verify the data, if its not broken then its not the emmc

Rifaldi34 said:
probably broken emmc ? could you access data partition using fastboot, try to paste 1gb of data to there, restart the phone enter fastboot again and copy the data to your pc, use sha256 to verify the data, if its not broken then its not the emmc
Click to expand...
Click to collapse
How can I get access to data partition with fastboot?

flashing it using miflash and edl mode using test point...

Brick - Please Help me ! PRA LX1 C432

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