Database Users

Help! soft brick while upgrading to update 3.0

TLDR/update: false alarm, after a pc reboot. and leaving the shield unplugged for a few min. i was able to "adb reboot bootloader" then reflash with fastboot, all good now. mods feel free to delete this bs...
i downloaded the official 3.0 recovery image from nvidia and commented out the bit to flash there recovery so i could keep twrp just like i have previously w/o issues. now im stuck and cant seem to access the bootloader by holding the power button, adb, or fastboot. what other options do i have? flashing from update.zip on sd card?
Code:
./flash-all.sh
< waiting for any device >
target reported max download size of 67108864 bytes
sending 'staging' (3091 KB)...
OKAY [ 0.091s]
writing 'staging'...
OKAY [ 0.152s]
finished. total time: 0.243s
target reported max download size of 67108864 bytes
sending 'boot' (21772 KB)...
OKAY [ 0.527s]
writing 'boot'...
OKAY [ 1.024s]
finished. total time: 1.551s
rebooting...
finished. total time: 0.059s
< waiting for any device >
sending 'system' (1578475 KB)...
FAILED (command write failed (Protocol error))
finished. total time: 0.000s
target reported max download size of 67108864 bytes
erasing 'vendor'...
OKAY [ 0.164s]
sending sparse 'vendor' (65498 KB)...
OKAY [ 1.606s]
writing 'vendor'...
OKAY [ 3.285s]
sending sparse 'vendor' (65472 KB)...
OKAY [ 1.582s]
writing 'vendor'...
OKAY [ 2.895s]
sending sparse 'vendor' (65532 KB)...
OKAY [ 1.611s]
writing 'vendor'...
OKAY [ 3.437s]
sending sparse 'vendor' (48152 KB)...
OKAY [ 1.196s]
writing 'vendor'...
OKAY [ 2.448s]
finished. total time: 18.223s
rebooting...
if it didnt sent the reboot command i could have seen the error and hopefully fixed it. guess i gave nvidia too much credit for error detection in there script.

Unable to flash anything in fastboot - unable to enumerate usb device

Hello everybody, I've been using a Zuk Z1 since november and I'm quite satisfied with it.
Some months ago, the G Sensor stopped to work. I've tried the calibration, it seems successful but it doesn't work at all. So I'd like to try another rom, hoping it'll be working again.
Some months ago, I installed Cyanogenmod 13 and, immediately after, ZUI but it didn't work correctly with my smartwatch so I dediced to go back to the original COS, also restoring Cyanogen Recovery. Now I can't flash anything from fastboot: both on Windows 10 and Linux (on three different computers), I can use ADB when the phone is on COS, but when in fastboot I get a "unable to enumerate usb device" and isn't recognised at all.
Is there anything I can try go get out of this problem? I can go to recovery, but can't flash anything as it says that the signature isn't correct.
Thank you.

draga said:
Hello everybody, I've been using a Zuk Z1 since november and I'm quite satisfied with it.
Some months ago, the G Sensor stopped to work. I've tried the calibration, it seems successful but it doesn't work at all. So I'd like to try another rom, hoping it'll be working again.
Some months ago, I installed Cyanogenmod 13 and, immediately after, ZUI but it didn't work correctly with my smartwatch so I dediced to go back to the original COS, also restoring Cyanogen Recovery. Now I can't flash anything from fastboot: both on Windows 10 and Linux (on three different computers), I can use ADB when the phone is on COS, but when in fastboot I get a "unable to enumerate usb device" and isn't recognised at all.
Is there anything I can try go get out of this problem? I can go to recovery, but can't flash anything as it says that the signature isn't correct.
Thank you.
Click to expand...
Click to collapse
I am having the exact same problem. I have to send the phone back for warranty.
I have been trying to use the ALL IN ONE Tool for ZUK and ZUK Tool Beta. Below is the message after which nothing happens. I will post more details and if someone can help me that will be great.
Flashing your Zuk Z1 back to stock. Please wait...
-----------------------------------------------
target reported max download size of 1610612736 bytes
sending 'persist' (4664 KB)...
OKAY [ 0.149s]
writing 'persist'...
OKAY [ 0.090s]
finished. total time: 0.239s
target reported max download size of 1610612736 bytes
sending 'modem' (58545 KB)...
OKAY [ 1.849s]
writing 'modem'...
OKAY [ 0.837s]
finished. total time: 2.686s
target reported max download size of 1610612736 bytes
sending 'sbl1' (280 KB)...
OKAY [ 0.012s]
writing 'sbl1'...
OKAY [ 0.010s]
finished. total time: 0.022s
target reported max download size of 1610612736 bytes
sending 'dbi' (17 KB)...
OKAY [ 0.004s]
writing 'dbi'...
OKAY [ 0.006s]
finished. total time: 0.010s
target reported max download size of 1610612736 bytes
sending 'aboot' (414 KB)...
OKAY [ 0.015s]
writing 'aboot'...
OKAY [ 0.017s]
finished. total time: 0.033s
target reported max download size of 1610612736 bytes
sending 'rpm' (189 KB)...
OKAY [ 0.009s]
writing 'rpm'...
OKAY [ 0.009s]
finished. total time: 0.018s
target reported max download size of 1610612736 bytes
sending 'splash' (562 KB)...
OKAY [ 0.021s]
writing 'splash'...
OKAY [ 0.013s]
finished. total time: 0.034s
target reported max download size of 1610612736 bytes
sending 'tz' (339 KB)...
OKAY [ 0.013s]
writing 'tz'...
OKAY [ 0.013s]
finished. total time: 0.026s
target reported max download size of 1610612736 bytes
sending 'boot' (6538 KB)...
OKAY [ 0.208s]
writing 'boot'...
OKAY [ 0.097s]
finished. total time: 0.305s
target reported max download size of 1610612736 bytes
sending 'recovery' (9168 KB)...
OKAY [ 0.292s]
writing 'recovery'...
OKAY [ 0.135s]
finished. total time: 0.427s
target reported max download size of 1610612736 bytes
erasing 'system'...
OKAY [ 0.086s]
sending 'system' (1546759 KB)...

Screen turned black while flashing image

Ok guys let me get to point fast!
I tried to flash 8.1 leaked beat build. connected my usb cable and executed flash_a_all.bat . There was inconsistency in connection my usb conected and disconnected for a moment and the bootloader turned all black.
No light on keys or from screen but vibrates when connection to computer or power + (vol +) or power + (vol-)
in my device manager, the phones is connnected as "Qualcomm HS-USB Diagnostics 900E"
this is how flashing ended
Please help me here guys !!!
HTML:
[HTML](bootloader) Device already : unlocked!
OKAY [ 0.030s]
finished. total time: 0.031s
target reported max download size of 534773760 bytes
sending 'modem_a' (86016 KB)...
OKAY [ 3.039s]
writing 'modem_a'...
OKAY [ 0.419s]
finished. total time: 3.459s
target reported max download size of 534773760 bytes
sending 'sbl1' (384 KB)...
OKAY [ 0.068s]
writing 'sbl1'...
OKAY [ 0.024s]
finished. total time: 0.094s
target reported max download size of 534773760 bytes
sending 'rpm' (172 KB)...
OKAY [ 0.038s]
writing 'rpm'...
OKAY [ 0.022s]
finished. total time: 0.063s
target reported max download size of 534773760 bytes
sending 'tz' (1516 KB)...
OKAY [ 0.088s]
writing 'tz'...
OKAY [ 0.028s]
finished. total time: 0.119s
target reported max download size of 534773760 bytes
sending 'devcfg' (40 KB)...
OKAY [ 0.039s]
writing 'devcfg'...
OKAY [ 0.023s]
finished. total time: 0.062s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.590s]
writing 'dsp'...
FAILED (remote: check crc failed)
finished. total time: 0.806s
target reported max download size of 534773760 bytes
sending 'aboot' (584 KB)...
OKAY [ 0.047s]
writing 'aboot'...
FAILED (remote: check crc failed)
finished. total time: 0.079s
target reported max download size of 534773760 bytes
sending 'boot_a' (14880 KB)...
OKAY [ 0.540s]
writing 'boot_a'...
FAILED (remote: check crc failed)
finished. total time: 0.736s
target reported max download size of 534773760 bytes
Invalid sparse file format at header magic
sending sparse 'system_a' 1/6 (515622 KB)...
OKAY [ 17.525s]
writing 'system_a' 1/6...
OKAY [ 9.171s]
sending sparse 'system_a' 2/6 (510059 KB)...
OKAY [ 17.378s]
writing 'system_a' 2/6...
OKAY [ 9.401s]
sending sparse 'system_a' 3/6 (518707 KB)...
OKAY [ 17.880s]
writing 'system_a' 3/6...
OKAY [ 20.688s]
sending sparse 'system_a' 4/6 (481011 KB)...
OKAY [ 16.422s]
writing 'system_a' 4/6...
OKAY [ 8.830s]
sending sparse 'system_a' 5/6 (521581 KB)...
OKAY [ 17.874s]
writing 'system_a' 5/6...
OKAY [ 9.791s]
sending sparse 'system_a' 6/6 (308870 KB)...
OKAY [ 10.707s]
writing 'system_a' 6/6...
FAILED (status read failed (Too many links))
finished. total time: 156.759s
target didn't report max-download-size
sending 'lksecapp' (60 KB)...
FAILED (command write failed (No error))
finished. total time: 0.006s
target didn't report max-download-size
sending 'cmnlib' (204 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
target didn't report max-download-size
sending 'cmnlib64' (256 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
target didn't report max-download-size
sending 'keymaster' (224 KB)...
FAILED (command write failed (No error))
finished. total time: 0.000s
error: Device does not support slots
...
FAILED (command write failed (No error))
finished. total time: 0.004s
< waiting for any device >
rebooting...
finished. total time: 0.016s
Press any key to exit...
[/HTML]

Huawei Y6 (2018) , Impossible debrand?

I flashed the phone with fastboot with a non-branded STOCK ROM, file by file, when the phone was rebooted, it was branded TIM Italy, why?
Is it possible that fastboot, despite the video results, did not flasha anything?
I tried several ROMs without success.
Code:
D:\Cellulare\adb-and-fastboot>fastboot flash cust debrand\CUST.img
Sending 'cust' (134830 KB) OKAY [ 5.832s]
Writing 'cust' OKAY [ 3.059s]
Finished. Total time: 8.928s
D:\Cellulare\adb-and-fastboot>fastboot flash kernel debrand\KERNEL.img
Sending 'kernel' (45749 KB) OKAY [ 1.629s]
Writing 'kernel' OKAY [ 1.009s]
Finished. Total time: 2.676s
D:\Cellulare\adb-and-fastboot>fastboot flash ramdisk debrand\RAMDISK.img
Sending 'ramdisk' (11205 KB) OKAY [ 0.414s]
Writing 'ramdisk' OKAY [ 0.273s]
Finished. Total time: 0.726s
D:\Cellulare\adb-and-fastboot>fastboot flash recovery_ramdisk debrand\RECOVERY_RAMDIS.img
Sending 'recovery_ramdisk' (27893 KB) OKAY [ 0.998s]
Writing 'recovery_ramdisk' OKAY [ 0.630s]
Finished. Total time: 1.676s
D:\Cellulare\adb-and-fastboot>fastboot flash system debrand\SYSTEM.img
Sending sparse 'system' 1/6 (468550 KB) OKAY [ 19.835s]
Writing sparse 'system' 1/6 OKAY [ 12.017s]
Sending sparse 'system' 2/6 (513679 KB) OKAY [ 20.851s]
Writing sparse 'system' 2/6 OKAY [ 11.767s]
Sending sparse 'system' 3/6 (515737 KB) OKAY [ 20.873s]
Writing sparse 'system' 3/6 OKAY [ 12.012s]
Sending sparse 'system' 4/6 (517855 KB) OKAY [ 21.453s]
Writing sparse 'system' 4/6 OKAY [ 12.797s]
Sending sparse 'system' 5/6 (521377 KB) OKAY [ 21.275s]
Writing sparse 'system' 5/6 OKAY [ 11.808s]
Sending sparse 'system' 6/6 (57052 KB) OKAY [ 2.236s]
Writing sparse 'system' 6/6 OKAY [ 1.276s]
Finished. Total time: 222.547s
D:\Cellulare\adb-and-fastboot>fastboot reboot
Rebooting
Finished. Total time: 0.004s
D:\Cellulare\adb-and-fastboot>

Y6II Cam-L23 Bricked, Huawei usb com 1.0

hi,
i already posted this, 3 days ago in another root thread,
a friend of mine tried to flash his phone after bootloader unlocked ok, but after the flash phone bricked, and ask me for help, now I'm asking as well,
tried:
IMAGE Download Software - IDTML01Ver1001 and CAML00LMAA001063_Board_Software_null_null_Android_ 6.0_EMUI_4.1_05021XEW, it always gives error but it seems to flash the fastboot at least, so the phone from: huawei usb com 1.0 goes to fastboot, so in adb i try:
C:\SDK\platform-tools>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (455490 KB)...
OKAY [ 62.178s]
writing 'system' 1/6...
OKAY [ 30.954s]
sending sparse 'system' 2/6 (447920 KB)...
OKAY [ 25.925s]
writing 'system' 2/6...
OKAY [ 30.355s]
sending sparse 'system' 3/6 (460685 KB)...
OKAY [ 20.218s]
writing 'system' 3/6...
OKAY [ 31.334s]
sending sparse 'system' 4/6 (454527 KB)...
OKAY [ 19.641s]
writing 'system' 4/6...
OKAY [ 30.797s]
sending sparse 'system' 5/6 (458441 KB)...
OKAY [ 19.465s]
writing 'system' 5/6...
OKAY [ 30.925s]
sending sparse 'system' 6/6 (20484 KB)...
OKAY [ 0.859s]
writing 'system' 6/6...
OKAY [ 1.406s]
finished. total time: 304.135s
C:\SDK\platform-tools>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (253973 KB)...
OKAY [ 10.453s]
writing 'cust'...
OKAY [ 17.159s]
finished. total time: 27.612s
C:\SDK\platform-tools>fastboot flash userdata userdata.img
target reported max download size of 471859200 bytes
sending 'userdata' (44124 KB)...
OKAY [ 1.770s]
writing 'userdata'...
OKAY [ 3.053s]
finished. total time: 4.838s
C:\SDK\platform-tools>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23514 KB)...
OKAY [ 1.188s]
writing 'boot'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 1.531s
C:\SDK\platform-tools>fastboot flash fastboot1 fastboot.img
target reported max download size of 471859200 bytes
sending 'fastboot1' (2194 KB)...
OKAY [ 0.141s]
writing 'fastboot1'...
FAILED (remote: image verification error)
finished. total time: 0.188s
C:\SDK\platform-tools>fastboot flash fastboot2 fastboot.img
target reported max download size of 471859200 bytes
sending 'fastboot2' (2194 KB)...
OKAY [ 0.063s]
writing 'fastboot2'...
FAILED (remote: partition does not exist)
finished. total time: 0.078s
C:\SDK\platform-tools>fastboot flash fastboot fastboot.img
target reported max download size of 471859200 bytes
sending 'fastboot' (2194 KB)...
OKAY [ 0.062s]
writing 'fastboot'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 0.156s
C:\SDK\platform-tools>fastboot flash cache cache.img
target reported max download size of 471859200 bytes
sending 'cache' (6248 KB)...
OKAY [ 0.312s]
writing 'cache'...
OKAY [ 0.453s]
finished. total time: 0.766s
C:\SDK\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (37966 KB)...
OKAY [ 1.531s]
writing 'recovery'...
FAILED (remote: flash write prim vrl failure)
finished. total time: 2.031s
--------------------------------------------------------------------------------------------------
so I'm able to flash successfully
system, cust, cache and userdata
but not able:
recovery, fastboot or boot, and after i fastboot reboot,
again only red and green led and huawei usb com 1.0, to start again
thank you very much indeed, for any guide or help, or maybe a cam-l23 board software to try

Hi!
What software do you use?
I hard brico my P8 Lite ALE...
I download rom form Huawei finder and came a wrong one... -.-
So PC only see him as HUAWEI USB COM 1.0.
Your have a similar software, maybe we can hel each other!
Thanks.

hi
persona78 said:
Hi!
What software do you use?
I hard brico my P8 Lite ALE...
I download rom form Huawei finder and came a wrong one... -.-
So PC only see him as HUAWEI USB COM 1.0.
Your have a similar software, maybe we can hel each other!
Thanks.
Click to expand...
Click to collapse
you should try to find:
***IMAGE Download Software*** - IDTML01Ver1001 and CAML00LMAA001063_***Board_Software_null_null_Android***_ 6.0_EMUI_4.1_05021XEW
for your model
thanks to you, for your attention

atv said:
you should try to find:
***IMAGE Download Software*** - IDTML01Ver1001 and CAML00LMAA001063_***Board_Software_null_null_Android***_ 6.0_EMUI_4.1_05021XEW
for your model
thanks to you, for your attention
Click to expand...
Click to collapse
Hi!
Can you provid me that files and a litle tut how to use it?
.
On fastboot, can you unlock bootloader?
-

alguien con el board software