i have a huawei p8 lite ALE-L21 with unlocked bootloader, i am trying to flash stock rom but when i start flashing system.img i get this error
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'system' 1/3 (460798 KB)...
OKAY [ 21.245s]
writing 'system' 1/3...
FAILED (unknown status code)
finished. total time: 21.268s
context: i flashed twrp and it did not boot, so i am trying to reflash stock tom
Related
Hello there guys! I'll resume my history.
So this was me one month after buying the Motorola Moto G XT1032 8GB, unlocking the bootloader without any problems So I wasn't really into the device info and didn't know about a GPE. So I downloaded a folder with a couple of images and .bin files and excuted a .bat inside the folder that turned my Stock 4.4.4 into Stock 4.4.2 GPE. After first reboot I just installed Paranoid Android and didn't come back to stock since then (a few months back).
Now I tried to go back to stock NON-GPE flashing "Android 4.3 Blur_Version.14.71.8.falcon_umts.Latam.en.AR" and "Android 4.4.2 Blur_Version.173.44.9.falcon_umts.Latam.en.AR" with this method GUIDE] Moto G - Restore stock firmware and I got this two errors in both of the cases:
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.030s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.363s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash motoboot motoboot.img
target reported max download size of 536870912 bytes
sending 'motoboot' (1940 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.405s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (619 KB)...
OKAY [ 0.079s]
writing 'logo'...
OKAY [ 0.161s]
finished. total time: 0.240s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.378s]
writing 'boot'...
OKAY [ 1.124s]
finished. total time: 1.502s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.379s]
writing 'recovery'...
OKAY [ 1.237s]
finished. total time: 1.617s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
sending 'system' (256840 KB)...
OKAY [ 8.098s]
writing 'system'...
OKAY [ 17.707s]
finished. total time: 25.805s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk2
target reported max download size of 536870912 bytes
sending 'system' (243300 KB)...
OKAY [ 7.668s]
writing 'system'...
OKAY [ 14.775s]
finished. total time: 22.443s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash system system.img_sparsechunk3
target reported max download size of 536870912 bytes
sending 'system' (219577 KB)...
OKAY [ 6.920s]
writing 'system'...
OKAY [ 23.237s]
finished. total time: 30.157s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (47104 KB)...
OKAY [ 1.526s]
writing 'modem'...
OKAY [ 2.332s]
finished. total time: 3.859s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.070s]
finished. total time: 0.070s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.137s]
finished. total time: 0.137s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml# fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (107 KB)...
OKAY [ 0.082s]
writing 'fsg'...
OKAY [ 5.303s]
finished. total time: 5.385s
[email protected]:/home/nicolas/Dev/android-sdk-linux/platform-tools/falcon_repw_user_4.4.2_KXB20.9-1.10-2.27_33_release-keys-cid6.xml#
Click to expand...
Click to collapse
You see? I got error with gtp.bin and motoboot.img but I kept flashing to see where that would take me. It turned out to take me witha bootloop Never going further than logo.
So what did I do? I ran that GPE 4.4.2 I flashed the first time I unlocked my bootloader. And it was alive again, booting like a charm. Now on crDroid again.
And my question is: what happened? Why am I able to flash a GPE 4.4.2 but not a Latam stock Retail for my country (Argentina)? I don't get it. I flashed from Windows and Ubuntu, with differents fastboot files, with mfasboot given in that Tutorial but nothing worked except turning it into a GPE Moto G.
Any contribution will be helpful, still want to go to stock Moto G. Cheers.
XXtremiXX said:
Hello there guys! I'll resume my history.
So this was me one month after buying the Motorola Moto G XT1032 8GB, unlocking the bootloader without any problems So I wasn't really into the device info and didn't know about a GPE. So I downloaded a folder with a couple of images and .bin files and excuted a .bat inside the folder that turned my Stock 4.4.4 into Stock 4.4.2 GPE. After first reboot I just installed Paranoid Android and didn't come back to stock since then (a few months back).
Now I tried to go back to stock NON-GPE flashing "Android 4.3 Blur_Version.14.71.8.falcon_umts.Latam.en.AR" and "Android 4.4.2 Blur_Version.173.44.9.falcon_umts.Latam.en.AR" with this method GUIDE] Moto G - Restore stock firmware and I got this two errors in both of the cases:
You see? I got error with gtp.bin and motoboot.img but I kept flashing to see where that would take me. It turned out to take me witha bootloop Never going further than logo.
So what did I do? I ran that GPE 4.4.2 I flashed the first time I unlocked my bootloader. And it was alive again, booting like a charm. Now on crDroid again.
And my question is: what happened? Why am I able to flash a GPE 4.4.2 but not a Latam stock Retail for my country (Argentina)? I don't get it. I flashed from Windows and Ubuntu, with differents fastboot files, with mfasboot given in that Tutorial but nothing worked except turning it into a GPE Moto G.
Any contribution will be helpful, still want to go to stock Moto G. Cheers.
Click to expand...
Click to collapse
Do this at your own risk:
If your phone is a gsm xt1032 then grab a EU(european) 4.4.4 stock firmware and flash that via fastboot. Should work...
If not then try flashing a custom recovery like twrp or clockworkmod. Grab the EU or US 4.4.4 untouched from this link: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and flash it via recovery.
Ok. Today after i updated my honor 8 to EMUI 5.0 my root was gone. I went and tried rooting my system again and when i was in TWRP i acidentally deleted EVERYTHING on the device (dont ask me how i can be so retarded). I then tried to find a solution on how to unbrick my Honor 8.
After downloading the stock firmware for Honor 8 and trying to flash it onto my device i ran into a problem. When i tried flashing cust.img, and system.img it just didnt work. Here are the results.
Code:
target reported max download size of 471859200 bytes
sending 'boot' (15464 KB)...
OKAY [ 0.330s]
writing 'boot'...
OKAY [ 0.371s]
finished. total time: 0.703s
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 9.281s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 9.292s
target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.789s]
writing 'recovery'...
OKAY [ 0.871s]
finished. total time: 1.662s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (435393 KB)...
OKAY [ 9.902s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.942s
As you can see it says "FAILED (remote: sparse flash write failure)" when i try to flash system.img. Does anyone know how i can fix this or is my Honor 8 fully bricked and do i have to buy a new one now?
Also, my bootloader is unlocked.
Little searching wouldn't hurt. https://forum.xda-developers.com/honor-8/how-to/guide-fix-boot-loop-bricked-honor-8-t3545202
So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
This is really bad. The solution to your first problem was to simply remove encryption by formatting data.
Jdelacrix said:
So I have an Honor 8 FRD-L04 that I was trying to root today. I flashed TWRP and all was good. Until I tried to install SuperSU using TWRP. It said my data partition wasn't able to be found or something, I can't remember. So I did some quick Googling and tried some fixes (changing the partition format to FAT and back to EXT4, etc). This just screwed it up even more. So here's the scenario:
*Can't access ADB anymore, doesn't show up in devices
*Can access fastboot, however:
I usually get "FAILED (remote: Command not allowed)" when I try to do any commands (bootloader is unlocked). Because of this, I can't flash extracted .IMG files.
*eRecovery tells me "Getting Package Info Failed"
*Don't have access to TWRP anymore
*Have tried multiple firmwares using the dload method, either they can't install or simply do nothing
*I've tried Huawei Multi Tool and got the following output:
Code:
RNV0216B29003646 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (15440 KB)...
OKAY [ 0.332s]
writing 'boot'...
OKAY [ 0.370s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (252389 KB)...
OKAY [ 5.407s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 5.418s
target reported max download size of 471859200 bytes
sending 'recovery' (36976 KB)...
OKAY [ 0.791s]
writing 'recovery'...
OKAY [ 0.879s]
finished. total time: 1.675s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (424496 KB)...
OKAY [ 9.894s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 9.945s
*I've tried using the dload method by first installing the rollback package (which actually installed), and then installing the actual firmware. But of course, the installation of the actual firmware failed.
I've probably tried a few other things, but I'm just so frustrated I can't remember. If anyone can suggest anything else, I'd greatly appreciate it.
Click to expand...
Click to collapse
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
sonicscrewup said:
I'm going to cover the basis here, as I've seriously screwed over my phone before but recovered.
If you managed to get the phone responsive with the rollback package try flashing the EMUI 4 package.
If that doesn't work, plug into the computer and press and hold the power and volume down buttons to get into fastboot: unlock oem if possible
let me know if that gets you started.
Click to expand...
Click to collapse
i was in a similar situation and this method worked! connect the phone to pc in switched off condition, press power+vol down and get into fastboot and then oem unlock, install twrp and tried to installed the zips.. worked and phone booted!!
Hey,
I could install Kitkat 4.4.2 EMUI 3.0: Cofface Custom Recovery, but could find any os what would install from zip. Getting error 7
today I tried to flash TWRP-3.0.2-r4 for the 4C. So I unlocked the bootloader flashed the new recovery img and then restarted and couldn't access the recovery menu. It freezes right at the Huawei logo.
Then I tried to flash the latest 4C android, so I extracted the boot.img, recovery.img and system.img from the update.app.
Flashing was successful I guess?
Code:
λ fastboot flash boot boot.img
target reported max download size of 524288000 bytes
sending 'boot' (23486 KB)...
OKAY [ 0.527s]
writing 'boot'...
OKAY [ 1.566s]
finished. total time: 2.098s
λ fastboot flash recovery RECOVERY.img
target reported max download size of 524288000 bytes
sending 'recovery' (33548 KB)...
OKAY [ 0.753s]
writing 'recovery'...
OKAY [ 1.742s]
finished. total time: 2.501s
λ fastboot flash system SYSTEM.img
target reported max download size of 524288000 bytes
sending sparse 'system' (510886 KB)...
OKAY [ 12.234s]
writing 'system'...
OKAY [ 12.280s]
sending sparse 'system' (497530 KB)...
OKAY [ 12.190s]
writing 'system'...
OKAY [ 11.563s]
sending sparse 'system' (511911 KB)...
OKAY [ 12.414s]
writing 'system'...
OKAY [ 12.407s]
sending sparse 'system' (509238 KB)...
OKAY [ 12.379s]
writing 'system'...
OKAY [ 12.039s]
sending sparse 'system' (362252 KB)...
OKAY [ 8.826s]
writing 'system'...
OKAY [ 8.523s]
finished. total time: 114.883s
But I tried to boot into the stock recovery but it freezes at the huawei logo again and I can't boot into android either.
After that I tried to erase the cache and userdata but I am getting the message that I am not allowed to do so.
Code:
λ fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.005s
Does anybody knows a workaround or a possible fix ?
Regards Artur
any updates ??
Up up..
Help guys
Hallo,
Please, I need help with a bricked Huawei Honor 6.
I have almost no knowledge about unbricking and the like.
I tried to update my Smartphone Firmware and used Huawei Update Extractor
combined with cmd Commands.
My Smartphone is in an eternal bootloop and I can only access Fastboot&Rescue Mode.
I ve tried to install another firmware, but there is this command lines in CMD (Huawei Fastboot Flasher):
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending sparse 'cust' (459730 KB)...
OKAY [ 48.349s]
writing 'cust'...
OKAY [ 16.092s]
sending sparse 'cust' (16208 KB)...
OKAY [ 1.711s]
writing 'cust'...
OKAY [ 0.532s]
finished. total time: 66.689s
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.416s]
writing 'recovery'...
OKAY [ 0.439s]
finished. total time: 1.857s
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (10596 KB)...
OKAY [ 1.091s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 1.102s
C:\Users\Kevin und Christina\Documents\Huawei Fastboot Flasher GSM HELP\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (431287 KB)...
OKAY [ 45.667s]
writing 'system'...
OKAY [ 16.017s]
sending sparse 'system' (446975 KB)...
Can some one of u see what's wrong and how to solve this problem? There is one FAILED line and maybe that's the Problem?
In my fastboot mode there I can read in red letters: PHONE Unlocked.
As I said, there is only one mode possible to enter, holding Volume up and then I get into Fastboot&Rescue Mode.
Unfortunately I've got almost zero flashing knowledge.
Pls help me.