Database Info

[Q] Unable to flash ROMS/OTA updates

I received my OnePlus One a few days ago and attempted install the 05q OTA update, however when the phone rebooted it was stuck in a bootloop where various artifacts would appear on screen before rebooting. I managed to flash back to the 44s firmware via fastboot and install TWRP and root the device.
I have tried to update the firmware via fastboot and TWRP but each time it ends up bootlooping. I have also tried to flash the CM12 nightlys, and although the install is successful, the same issue is present when trying to boot. Attempting to flash different kernels (eg. Franco kernel) has the same issues.
I'm not sure if this is a common problem or if I've just managed to get a dud phone. The phone I received seems to be the Chinese variant (Missing LTE bands), but it arrived with CM11S installed. Not sure if that would affect the ability to update?
Any help or information would be much appreciated

You shouldn't have any problems flashing regardless of which variant you have. Are you checking the md5 of downloaded files before flashing? Which firmware did you try to update? Saying "the firmware" is like saying nothing at all. Are you remembering to wipe properly before flashing CM12? Which version of which kernel was flashed on which ROM? There's a theme here, please provide more detailed information.

My first attempt was the OTA update from XNPH44S to XNPH05Q. This caused the device to get stuck at the OnePlus logo.
Then I proceeded to unlock the bootloader and attempt to flash the 05Q fastboot image located at http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746. It's appears to have successfully installed, but again, bootloops.
Flashing the 44S update from the link above worked.
As for CM12, a factory reset was performed before attempting to flash the cm-12-20150121-UNOFFICIAL-bacon.zip found here https://basketbuild.com/devs/klvnhng/cm-12.0_bacon. Successful install, but bootlooping persists.
Attempted to flash Franco kernel r35 found here http://kernels.franco-lnx.net/OnePlusOne/4.4/ over stock XNPH44S firmware. No luck.
If any more information is required do not hesitate to ask.

That all looks fine, except for the factory reset before flashing CM12. You really need a full wipe when changing ROMs like that, a full wipe consists of wiping system, data, cache, and dalvik cache. It seems odd that after flashing the stock images you'd end up in a bootloop. So when you say flashing the 44S update worked, you mean you flashed the 44S stock images with fastboot and the phone booted up and operated normally?

timmaaa said:
That all looks fine, except for the factory reset before flashing CM12. You really need a full wipe when changing ROMs like that, a full wipe consists of wiping system, data, cache, and dalvik cache. It seems odd that after flashing the stock images you'd end up in a bootloop. So when you say flashing the 44S update worked, you mean you flashed the 44S stock images with fastboot and the phone booted up and operated normally?
Click to expand...
Click to collapse
Correct. If I flash 44S the phone will boot normally, but if I try any other images (eg 05Q) it gets stuck.

samskies1 said:
Correct. If I flash 44S the phone will boot normally, but if I try any other images (eg 05Q) it gets stuck.
Click to expand...
Click to collapse
If you decide to make another attempt to flash the 05Q stock images, please copy/paste the text from the command prompt here do I can see.
Transmitted via Bacon

timmaaa said:
If you decide to make another attempt to flash the 05Q stock images, please copy/paste the text from the command prompt here do I can see.
Transmitted via Bacon
Click to expand...
Click to collapse
C:\Users\Samus\Desktop\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.782s]
writing 'modem'...
OKAY [ 1.243s]
finished. total time: 3.025s
C:\Users\Samus\Desktop\adb>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ -0.000s]
writing 'dbi'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Samus\Desktop\adb>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ -0.000s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.313s]
writing 'LOGO'...
OKAY [ 0.212s]
finished. total time: 0.525s
C:\Users\Samus\Desktop\adb>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.328s]
writing 'oppostanvbk'...
OKAY [ 0.234s]
finished. total time: 0.563s
C:\Users\Samus\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5956 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.328s
C:\Users\Samus\Desktop\adb>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (10432 KB)...
OKAY [ 0.328s]
writing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.954s
C:\Users\Samus\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7854 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.422s
C:\Users\Samus\Desktop\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.332s]
sending sparse 'system' (524108 KB)...
OKAY [ 18.747s]
writing 'system'...
OKAY [ 23.967s]
sending sparse 'system' (320781 KB)...
OKAY [ 11.519s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 70.597s
C:\Users\Samus\Desktop\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 3.751s]
sending 'userdata' (141075 KB)...
OKAY [ 4.436s]
writing 'userdata'...
OKAY [ 13.012s]
finished. total time: 21.199s
C:\Users\Samus\Desktop\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>

samskies1 said:
C:\Users\Samus\Desktop\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56369 KB)...
OKAY [ 1.782s]
writing 'modem'...
OKAY [ 1.243s]
finished. total time: 3.025s
C:\Users\Samus\Desktop\adb>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ -0.000s]
writing 'sbl1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ -0.000s]
writing 'dbi'...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.016s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\Samus\Desktop\adb>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.000s]
writing 'rpm'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ -0.000s]
writing 'tz'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\Samus\Desktop\adb>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.313s]
writing 'LOGO'...
OKAY [ 0.212s]
finished. total time: 0.525s
C:\Users\Samus\Desktop\adb>fastboot flash oppostanvbk static_nvbk.bin
target reported max download size of 536870912 bytes
sending 'oppostanvbk' (10240 KB)...
OKAY [ 0.328s]
writing 'oppostanvbk'...
OKAY [ 0.234s]
finished. total time: 0.563s
C:\Users\Samus\Desktop\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (5956 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.328s
C:\Users\Samus\Desktop\adb>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (10432 KB)...
OKAY [ 0.328s]
writing 'cache'...
OKAY [ 0.500s]
finished. total time: 0.954s
C:\Users\Samus\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7854 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.172s]
finished. total time: 0.422s
C:\Users\Samus\Desktop\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.332s]
sending sparse 'system' (524108 KB)...
OKAY [ 18.747s]
writing 'system'...
OKAY [ 23.967s]
sending sparse 'system' (320781 KB)...
OKAY [ 11.519s]
writing 'system'...
OKAY [ 16.032s]
finished. total time: 70.597s
C:\Users\Samus\Desktop\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 3.751s]
sending 'userdata' (141075 KB)...
OKAY [ 4.436s]
writing 'userdata'...
OKAY [ 13.012s]
finished. total time: 21.199s
C:\Users\Samus\Desktop\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\Users\Samus\Desktop\adb>
Click to expand...
Click to collapse
That all looks fine. But it's not booting correctly still?
Transmitted via Bacon

timmaaa said:
That all looks fine. But it's not booting correctly still?
Transmitted via Bacon
Click to expand...
Click to collapse
Still no luck unfortunately. This is it attempting to boot imgur.com/LIT8i5S (Apologies for the low quality. Using old phone)

samskies1 said:
Still no luck unfortunately. This is it attempting to boot imgur.com/LIT8i5S (Apologies for the low quality. Using old phone)
Click to expand...
Click to collapse
Well I'm stumped, usually the stock images are the thing that revive a One from issues like this. I think it's time to contact the seller and claim warranty.
Transmitted via Bacon
---------- Post added at 07:29 ---------- Previous post was at 07:13 ----------
Edit:
Actually, it's early, I forgot about these, give them a try:
http://forum.xda-developers.com/showthread.php?t=2991851
Unbrick Tool
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
And then try flashing 05Q.
Transmitted via Bacon

timmaaa said:
Well I'm stumped, usually the stock images are the thing that revive a One from issues like this. I think it's time to contact the seller and claim warranty.
Transmitted via Bacon
---------- Post added at 07:29 ---------- Previous post was at 07:13 ----------
Edit:
Actually, it's early, I forgot about these, give them a try:
http://forum.xda-developers.com/showthread.php?t=2991851
Unbrick Tool
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
And then try flashing 05Q.
Transmitted via Bacon
Click to expand...
Click to collapse
Tried the second method you linked. No luck I'm afraid. Attempted the OTA and via fastboot.

samskies1 said:
Tried the second method you linked. No luck I'm afraid. Attempted the OTA and via fastboot.
Click to expand...
Click to collapse
I can't think of why that's happening, you might need to RMA.
Transmitted via Bacon

timmaaa said:
I can't think of why that's happening, you might need to RMA.
Transmitted via Bacon
Click to expand...
Click to collapse
I've sent in a return request.
If you don't mind me asking, did you acquire your phone from OnePlus directly? Or buy through a third party seller?
I only ask because I am also an Australian, and I am unable to purchase from the OnePlus website, due to a lack of shipping to Australia.

samskies1 said:
I've sent in a return request.
If you don't mind me asking, did you acquire your phone from OnePlus directly? Or buy through a third party seller?
I only ask because I am also an Australian, and I am unable to purchase from the OnePlus website, due to a lack of shipping to Australia.
Click to expand...
Click to collapse
I purchased directly from OnePlus, and I know dozens of other Australians who did so. We used freight forwarding companies like Shipito, they provide you with an American mailing address and then forward it on to you. I think it cost me an extra $35 on top of the cost of the phone.
Transmitted via Bacon

timmaaa said:
I purchased directly from OnePlus, and I know dozens of other Australians who did so. We used freight forwarding companies like Shipito, they provide you with an American mailing address and then forward it on to you. I think it cost me an extra $35 on top of the cost of the phone.
Transmitted via Bacon
Click to expand...
Click to collapse
If this return to a third party seller goes though I think I may use that method to buy one directly from OnePlus.

I have similar problem, can't update official firmware through ota or manually installation, but my phone still manage to flash 3rd party roms and Calculkin's rooted 05q rom...??

johnsin5393 said:
I have similar problem, can't update official firmware through ota or manually installation, but my phone still manage to flash 3rd party roms and Calculkin's rooted 05q rom...
Click to expand...
Click to collapse
What happens when you try to flash official firmware?
Yeah I'm going to give Calkulin's rom a try when I get home from work.

samskies1 said:
What happens when you try to flash official firmware?
Yeah I'm going to give Calkulin's rom a try when I get home from work.
Click to expand...
Click to collapse
In cyanogen recovery, I couldn't flash firmware update or others zip file... Only after flashed Calkulin's packed zip, then I could flash to 05q

johnsin5393 said:
In cyanogen recovery, I couldn't flash firmware update or others zip file... Only after flashed Calkulin's packed zip, then I could flash to 05q
Click to expand...
Click to collapse
Would you happen to have a link to what you flashed?

Error 70 when trying to install GAPPS

Hi people
Yesterday I updated my phone to CyanogenMod(CM)13.0 which went fine. However when I rebooted the phone a popup came up the entire time telling me that google play services stopped working. In an attempt to fix it, I accidently removed google play services, causing a bunch of trouble at the moment.
I went to the CM Wiki and first I downloaded the "nano" variant of the GAPPS, trying to fix everything in the end. I put the file on my phone and tried to install it via recovery. This message came up however:
Insufficiënt storage space available in system partition. You may want to use a smaller GAPPS package or consider removing some apps using GAPPS-config ( bla bla) Error code 70.
As far as I can see, it is able to mount /system and /data, but the partition does not seem to have enough space left, at least so it says.
After that I tried the same with the "pico" variant, which also gave the same result. Pretty strange for a package that small.
So after taking a backup of important files I tried to wipe data/factory reset (was going to reinstall everything), to which I got an error "data wipe failed", which is correct since I can still boot in CM13 after that.
So I'm a bit in trouble here. I cannot seem to wipe my phone entirely, nor am I able to reinstall GAPPS due to this error 70.
Could this be a permissions problem somehow?
Things I have done so far to check what the problem could be:
- I've checked the space left on the /system partition which is 501 MB. Should be enough I guess?
- I've checked the /system partition for errors via adb shell while the phone was in recovery mode, which came out clean.
Below a picture of output of "mount", "df -h" and "uname -a" for extra information.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks

Was the phone dirty flashed from an older cm13 rom or was it dirty flashed over a non-cm13 rom?

What do you mean with dirty flashed?
i got this Phone from a friend and the Original stock rom was installed. I installed Cyanogenmod together with gapps and everything went fine back then.

Dirty flashing is referred to as the installation of a new rom without wiping the previous rom prior to installation of the new rom.
If the stock rom was LP or kk and cm13 is installed via dirty flash, it is likely, based on my on experience, that the phone will hang at the boot screen.

audit13 said:
Dirty flashing is referred to as the installation of a new rom without wiping the previous rom prior to installation of the new rom.
If the stock rom was LP or kk and cm13 is installed via dirty flash, it is likely, based on my on experience, that the phone will hang at the boot screen.
Click to expand...
Click to collapse
The Phone is working perfectly on its own, except for the google-applications.
That is the reason I only need GApps, to repair the initial problem.
Would it be a solution to format /data and /system and start all over? Although i'm worried that I will still not be able to install GApps due to error 70...

I agree that it may be simpler to start over by flashing a stock Mm rom, erasing userdata in fastboot, flash userdata.img in fastboot, make sure it boots, install twrp, install cm13, no then gapps.

Which recovery do you use? TWRP or CWM?
Which build date of open gapps have you tried? The latest one?

audit13 said:
I agree that it may be simpler to start over by flashing a stock Mm rom, erasing userdata in fastboot, flash userdata.img in fastboot, make sure it boots, install twrp, install cm13, no then gapps.
Click to expand...
Click to collapse
It started installing after I initiated the flash-all command. This is the output. i downloaded the correct image and searched the net to know how I had to work with fastboot and such.
W/ ( 6228): Zip: unable to truncate file to 1044902952: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
The full log:
D:\temp\Hammerhead>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.314s]
writing 'bootloader'...
OKAY [ 0.536s]
finished. total time: 0.852s
rebooting into bootloader...
OKAY [ 0.107s]
finished. total time: 0.110s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.733s]
writing 'radio'...
OKAY [ 3.121s]
finished. total time: 4.858s
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.046s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ ( 6228): Zip: unable to truncate file to 1044902952: File too large
failed to extract 'system.img': I/O Error
Press any key to exit...
So, again something about the file being to large. I locked and unlocked the lock state of my phone to make sure it would remove data, to get more space. I guess it did not really work.
Anything else I can do?

Here's the output when I flash mmb29s t0 my 16 GB Nexus 5:
D:\Downloads\Nexus 5\Nexus 5 Stock 6.01\hammerhead-mmb29s-factory-6bfcdfa4\hamme
rhead-mmb29s>flash-all
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.542s]
finished. total time: 0.849s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (45425 KB)...
OKAY [ 1.640s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.762s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 050db890002e8xxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.774s]
sending 'recovery' (10012 KB)...
OKAY [ 0.565s]
writing 'recovery'...
OKAY [ 0.824s]
sending 'system' (1020413 KB)...
OKAY [ 32.200s]
writing 'system'...
OKAY [ 68.826s]
erasing 'userdata'...
OKAY [ 8.696s]
erasing 'cache'...
OKAY [ 0.630s]
rebooting...
finished. total time: 113.718s
Press any key to exit...
I noticed your commands do not include the phone's installed baseband, bootoader, or serial number. Were these edited out before you posted the results?

audit13 said:
Here's the output when I flash mmb29s t0 my 16 GB Nexus 5:
D:\Downloads\Nexus 5\Nexus 5 Stock 6.01\hammerhead-mmb29s-factory-6bfcdfa4\hamme
rhead-mmb29s>flash-all
sending 'bootloader' (3120 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.542s]
finished. total time: 0.849s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (45425 KB)...
OKAY [ 1.640s]
writing 'radio'...
OKAY [ 3.122s]
finished. total time: 4.762s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 050db890002e8xxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.774s]
sending 'recovery' (10012 KB)...
OKAY [ 0.565s]
writing 'recovery'...
OKAY [ 0.824s]
sending 'system' (1020413 KB)...
OKAY [ 32.200s]
writing 'system'...
OKAY [ 68.826s]
erasing 'userdata'...
OKAY [ 8.696s]
erasing 'cache'...
OKAY [ 0.630s]
rebooting...
finished. total time: 113.718s
Press any key to exit...
I noticed your commands do not include the phone's installed baseband, bootoader, or serial number. Were these edited out before you posted the results?
Click to expand...
Click to collapse
Non, they were not edited out. They just did not show up.
Ok, I got the Android stock rom installed on the phone, but now something else is wrong. here is what i did:
Code:
D:\temp\Hammerhead>fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.632s]
sending 'system' (1020413 KB)...
OKAY [ 33.134s]
writing 'system'...
OKAY [ 68.970s]
finished. total time: 102.738s
D:\temp\Hammerhead>fastboot flash data data.img
error: cannot load 'data.img'
D:\temp\Hammerhead>fastboot flash data userdata.img
target reported max download size of 1073741824 bytes
sending 'data' (137318 KB)...
OKAY [ 4.556s]
writing 'data'...
FAILED (remote: partition table doesn't exist)
finished. total time: 4.745s
D:\temp\Hammerhead>fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.489s]
sending 'cache' (13348 KB)...
OKAY [ 0.647s]
writing 'cache'...
OKAY [ 1.074s]
finished. total time: 2.215s
D:\temp\Hammerhead>fastboot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (9156 KB)...
OKAY [ 0.481s]
writing 'boot'...
OKAY [ 0.774s]
finished. total time: 1.260s
I first erased the partitions "system", "data" and "cache". After that I flashed "system", "userdata", "cache", and lastly "boot"
The phone booted into the rom, I entered my PIN, after which it complained my data was corrupt. It makes sense because of this:
"D:\temp\Hammerhead>fastboot flash data userdata.img
target reported max download size of 1073741824 bytes
sending 'data' (137318 KB)...
OKAY [ 4.556s]
writing 'data'...
FAILED (remote: partition table doesn't exist)
finished. total time: 4.745s"
It prolly needs the data partition to write stuff to.
Somehow the partition table of data seems to be gone.
So, the plot thickens! Is there a way I can recreate this partition table, or am I supposed to do something else?

fastboot flash userdata userdata.img
btw, nothing is wrong with your partition table, there is simply no partition on the phone called data. Data is part of userdata partition.

The commands are:
fastboot erase userdata
fastboot flash userdata userdata.img
The img file has to be extracted from the mmb29s zip file.

Damn, stupid I didn't see that.
I'll try again tonight and see how that goes.

GTCG said:
Damn, stupid I didn't see that.
I'll try again tonight and see how that goes.
Click to expand...
Click to collapse
Ok, I got it working again. Back on stock rom atm. Thanks for help everyone!

bootloop? do i need to change the motherboard?

X:\MM>fastboot flash boot boot.img
target reported max download size of 524288000 bytes
sending 'boot' (22672 KB)...
OKAY [ 0.516s]
writing 'boot'...
OKAY [ 1.274s]
finished. total time: 1.791s
X:\MM>fastboot flash cust cust.img
target reported max download size of 524288000 bytes
sending 'cust' (204572 KB)...
OKAY [ 4.595s]
writing 'cust'...
OKAY [ 4.547s]
finished. total time: 9.143s
X:\MM>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (36118 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 1.795s]
finished. total time: 2.622s
X:\MM>fastboot flash recovery2 recovery2.img
target reported max download size of 524288000 bytes
sending 'recovery2' (36118 KB)...
OKAY [ 0.811s]
writing 'recovery2'...
OKAY [ 1.812s]
finished. total time: 2.623s
X:\MM>fastboot flash system system.img
target reported max download size of 524288000 bytes
sending sparse 'system' (511933 KB)...
OKAY [ 12.387s]
writing 'system'...
OKAY [ 11.362s]
sending sparse 'system' (511977 KB)...
OKAY [ 12.509s]
writing 'system'...
OKAY [ 11.365s]
sending sparse 'system' (510760 KB)...
OKAY [ 12.582s]
writing 'system'...
OKAY [ 11.323s]
sending sparse 'system' (482362 KB)...
OKAY [ 11.807s]
writing 'system'...
OKAY [ 10.682s]
sending sparse 'system' (282051 KB)...
OKAY [ 6.866s]
writing 'system'...
OKAY [ 6.281s]
finished. total time: 107.184s
Click to expand...
Click to collapse
i did all of this but still my phone is at Huawei Logo.
CHC-U01
the dload is not working every time i try it phone is showing black screen. but i was able to reach cwm but black screen but i can feel the vibrations
thanks sir.

SpectreZ said:
i did all of this but still my phone is at Huawei Logo.
CHC-U01
the dload is not working every time i try it phone is showing black screen. but i was able to reach cwm but black screen but i can feel the vibrations
thanks sir.
Click to expand...
Click to collapse
Try to flash in the specified order and that too with your stock KK firmware.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
flash system system.img

miststudent2011 said:
Try to flash in the specified order and that too with your stock KK firmware.
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
flash system system.img
Click to expand...
Click to collapse
i did that with stock KK now its rebooting on Huawei Logo.

SpectreZ said:
i did that with stock KK now its rebooting on Huawei Logo.
Click to expand...
Click to collapse
Is Twrp or CWM working on your device?

miststudent2011 said:
Is Twrp or CWM working on your device?
Click to expand...
Click to collapse
CWM works But i get Black Screen. Sir
Phone vibrate on volume up and downs.

miststudent2011 said:
Is Twrp or CWM working on your device?
Click to expand...
Click to collapse
UPDATE: Sir i the phone booted up on Andorid L Build B330 How do i RollBack to Kitkat without any problem?
I did your Method with Lolipop and The Phone Boots.
Thank you soo much sir but if you could help me to Get Back in Kitkat ( Storage Problems in Latest Version )

SpectreZ said:
UPDATE: Sir i the phone booted up on Andorid L Build B330 How do i RollBack to Kitkat without any problem?
I did your Method with Lolipop and The Phone Boots.
Thank you soo much sir but if you could help me to Get Back in Kitkat ( Storage Problems in Latest Version )
Click to expand...
Click to collapse
In order to roll back to KitKat you need to flash downgrade package and then flash KitKat firmware by using dload method.
But it may or maynot work as your phone is modified.
Is your phone is certified if you look into play store settings?

miststudent2011 said:
In order to roll back to KitKat you need to flash downgrade package and then flash KitKat firmware by using dload method.
But it may or maynot work as your phone is modified.
Is your phone is certified if you look into play store settings?
Click to expand...
Click to collapse
By Useing dLoad Method looks like i got the device in the same position now trying to do what you said again. sir

SpectreZ said:
By Useing dLoad Method looks like i got the device in the same position now trying to do what you said again. sir
Click to expand...
Click to collapse
Is your phone is certified if you look into play store settings?

miststudent2011 said:
Is your phone is certified if you look into play store settings?
Click to expand...
Click to collapse
i do not see any Certified or not certified on play store settings.

SpectreZ said:
i do not see any Certified or not certified on play store settings.
Click to expand...
Click to collapse
Playstore->settings->device certification

Sir Can you give me Kitkat Rom please? The one i have B070 is bugged i think everytime i try to flash it with dload or fastboot Phone gets stuck in bootloop but the buged rom Chilemovisters one runs good. thank you.

GPlay Mini CHC-U01 soft bricked ?

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

Help with bricked? Huawei Honor 6

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.