Database Info

[Q] Unable to erase cache partition

Today I was facing a 4.4.3 issue so I've thought about doing a factory reset to see if this fixes it. So I've gone into Recovery and run a factory reset. Strangely this was taking so long, so after 2 hours I've decided to stop it. I know that stopping this process is not recommended, but I've considered it was getting out of the reasonable range. I've rerun it and same problem, so after 3 hours I've stopped it. And I've thought about restoring the factory image. Unfortunately the process get stuck in the "erasing cache" step:
Code:
# ./flash-all.sh
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
OKAY [ 0.452s]
finished. total time: 0.749s
rebooting into bootloader...
OKAY [ 0.131s]
finished. total time: 0.132s
sending 'radio' (45409 KB)...
OKAY [ 1.614s]
writing 'radio'...
OKAY [ 3.102s]
finished. total time: 4.716s
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...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.13
Serial Number........: 063b7fa3f0d88342
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8700 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.740s]
sending 'recovery' (9284 KB)...
OKAY [ 0.540s]
writing 'recovery'...
OKAY [ 0.776s]
erasing 'system'...
OKAY [ 1.074s]
sending 'system' (721400 KB)...
OKAY [ 23.132s]
writing 'system'...
OKAY [ 49.064s]
erasing 'userdata'...
OKAY [ 13.622s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
sending 'userdata' (139109 KB)...
writing 'userdata'...
OKAY [ 13.895s]
erasing 'cache'...
I'm afraid that even if I let it work for hours it'll be stuck forever. What can I do? What could be happening? Any suggestions? Thank you!

Just fastboot flash the cache image manually without erasing it.
fastboot flash cache cache.img
Sent from my Nexus 5 using Tapatalk

Thank you, the command works well:
Code:
# fastboot flash cache image/cache.img
erasing 'cache'...
OKAY [ 0.513s]
sending 'cache' (13348 KB)...
OKAY [ 0.640s]
writing 'cache'...
OKAY [ 1.075s]
finished. total time: 2.228s
[email protected]:/home/jpabloae/Descargas/hammerhead-ktu84m# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
After that and following this tutorial for flashing the factory image (Method 2) I select "Recovery" and then press Power Button + Volume UP when the small Android appears. When I do that the small Android gets grey and it outputs "Formatting /data...", but it doesn't finish. I'm not sure what could be happening, any ideas?

What is your ultimate goal?
Sent from my Nexus 5 using Tapatalk

rootSU said:
What is your ultimate goal?
Click to expand...
Click to collapse
To boot a fresh stock 4.4.3.

To be unrooted forever?? What about bootloader?
Sent from my Nexus 5 using Tapatalk

rootSU said:
To be unrooted forever?? What about bootloader?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well, as a first step I'd like to at least have the phone functional.
These are all the steps I've followed (the bootloader is unlocked):
Code:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.13.img
fastboot reboot-bootloader
sleep 5
fastboot flash system image/system.img
fastboot flash userdata image/userdata.img
fastboot flash boot image/boot.img
fastboot flash recovery image/recovery.img
fastboot flash cache image/cache.img
And then what I said before: select "Recovery" and then press Power Button + Volume UP. And it get stuck on "Formatting /data...".

I don't know what the recovery is doing. Try and flash a custom recovery like philz or twrp. Then fast boot flash it
Then fastboot flash the system, boot, cache and userdata and then see what happens.. If it boots etc
By boot,, I mean kernel
Sent from my Nexus 5 using Tapatalk

I've been able to recover the phone back to stock with TWRP. You've been really helpful, thank you!
One last question: how does one manage to return to a stock image, stock recovery, locked and untampered device? Following these steps I'm able to do it all except for the recovery.

jpabloae said:
I've been able to recover the phone back to stock with TWRP. You've been really helpful, thank you!
One last question: how does one manage to return to a stock image, stock recovery, locked and untampered device? Following these steps I'm able to do it all except for the recovery.
Click to expand...
Click to collapse
Those steps are for someone who has returned to stock and forgotten to reset the tamper flag, so the recovery they are flashing is a custom one.
Full normal instructions are linked in my signature

rootSU said:
Full normal instructions are linked in my signature
Click to expand...
Click to collapse
I might be missing something, but on the signature's guide, in the last step (Locking your bootloader+ Resetting the tamper flag) it uses TWRP to install the zip file that resets the temper flag, and this process lockes the bootloader as well. I mean, after doing this you don't end up with the stock recovery but with TWRP.

jpabloae said:
I might be missing something, but on the signature's guide, in the last step (Locking your bootloader+ Resetting the tamper flag) it uses TWRP to install the zip file that resets the temper flag, and this process lockes the bootloader as well. I mean, after doing this you don't end up with the stock recovery but with TWRP.
Click to expand...
Click to collapse
In the steps he doesn't flash TWRP. He boots to it.
fastboot boot recovery.img
as opposed to
fastboot flash recovery recovery.img
That means you have stock recovery already installed at that point and you do not replace it.
There is also an app called BootUnlocker, which resets the taper flag from within android (With root) so you can just use that. I use that and mine is constantly showing as not tampered

rootSU said:
In the steps he doesn't flash TWRP. He boots to it.
Click to expand...
Click to collapse
You're absolutely right, I took it for granted it was necessary to flash it before using it. My phone is now 100% recovered, thank you so much!

jpabloae said:
You're absolutely right, I took it for granted it was necessary to flash it before using it. My phone is now 100% recovered, thank you so much!
Click to expand...
Click to collapse
No probs

My Nexus 5 isn't bricked, but I can't seem to fix it. I can get into bootloader/recov

I seem to be having a ton of issues after getting my phone back from my wife. I can't get /data/ to mount unless I format it as FAT, but it won't format as ext4 or anything else. I tried flashing stock, but no dice. I did manage to get PA and CM up and running but I get a message telling me my storage is encrypted, and I definitley don't have a password. Factory resets dont help because if it tries to format /data/ it'll never finish. I let it run for hours even.
Is there any creative ideas I can try? I really can't afford a new phone, so I need to get this fixed, and I was defintley under the impression that if you can get into bootloader/recovery, then it is not bricked .

Zarilenth said:
I seem to be having a ton of issues after getting my phone back from my wife. I can't get /data/ to mount unless I format it as FAT, but it won't format as ext4 or anything else. I tried flashing stock, but no dice. I did manage to get PA and CM up and running but I get a message telling me my storage is encrypted, and I definitley don't have a password. Factory resets dont help because if it tries to format /data/ it'll never finish. I let it run for hours even.
Is there any creative ideas I can try? I really can't afford a new phone, so I need to get this fixed, and I was defintley under the impression that if you can get into bootloader/recovery, then it is not bricked .
Click to expand...
Click to collapse
fastboot flash userdata userdata.img
It'll wipe data and internal storage but it's the easiest way.

Lethargy said:
fastboot flash userdata userdata.img
It'll wipe data and internal storage but it's the easiest way.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata.img
erasing 'userdata'...
OKAY [ 2.031s]
sending 'userdata' (137318 KB)...
OKAY [ 4.547s]
writing 'userdata'...
OKAY [ 8.884s]
finished. total time: 15.494s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I tried it and then tried fastboot update image-hammerhead-lpv79.zip and now it is hanging at erasing 'system'

Zarilenth said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata.img
erasing 'userdata'...
OKAY [ 2.031s]
sending 'userdata' (137318 KB)...
OKAY [ 4.547s]
writing 'userdata'...
OKAY [ 8.884s]
finished. total time: 15.494s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I tried it and then tried fastboot update image-hammerhead-lpv79.zip and now it is hanging at erasing 'system'
Click to expand...
Click to collapse
Close and just try running flash-all.bat/sh

Lethargy said:
Close and just try running flash-all.bat/sh
Click to expand...
Click to collapse
Now it is hanging at erasing 'cache'
< waiting for device >
sending 'bootloader' (2508 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
OKAY [ 0.484s]
finished. total time: 0.781s
rebooting into bootloader...
OKAY [ 0.078s]
finished. total time: 0.078s
sending 'radio' (45505 KB)...
OKAY [ 1.563s]
writing 'radio'...
OKAY [ 3.114s]
finished. total time: 4.693s
rebooting into bootloader...
OKAY [ 0.078s]
finished. total time: 0.078s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-2.0.50.2.08
Serial Number........: 0651fd67006b5ff4
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8754 KB)...
OKAY [ 0.484s]
writing 'boot'...
OKAY [ 0.750s]
sending 'recovery' (9412 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.781s]
erasing 'system'...
OKAY [ 1.250s]
sending 'system' (683564 KB)...
OKAY [ 21.820s]
writing 'system'...
OKAY [ 46.359s]
erasing 'userdata'...
OKAY [ 2.125s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 14.092s]
erasing 'cache'...

Zarilenth said:
Now it is hanging at erasing 'cache'
Click to expand...
Click to collapse
Try taking cache.img out of the zip and flash it separately?

Lethargy said:
Try taking cache.img out of the zip and flash it separately?
Click to expand...
Click to collapse
This sounded genius, I would have never thought to try this. I took it out and rezipped the folder, but it still tried to erase the cache and stopped there. Is there any way to stop it from trying to erase the cache?

Zarilenth said:
This sounded genius, I would have never thought to try this. I took it out and rezipped the folder, but it still tried to erase the cache and stopped there. Is there any way to stop it from trying to erase the cache?
Click to expand...
Click to collapse
When you flash something using fastboot it'll always erase. Try erasing cache without flashing, "fastboot erase cache"

Lethargy said:
When you flash something using fastboot it'll always erase. Try erasing cache without flashing, "fastboot erase cache"
Click to expand...
Click to collapse
I erased it and formatted it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
< waiting for device >
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.637s]
finished. total time: 0.651s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format cache
erasing 'cache'...
OKAY [ 0.526s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 2.118s]
finished. total time: 2.669s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Zarilenth said:
I erased it and formatted it.
Click to expand...
Click to collapse
Reflash and see if it works?

Lethargy said:
Reflash and see if it works?
Click to expand...
Click to collapse
No still stuck at erasing 'cache'

Zarilenth said:
No still stuck at erasing 'cache'
Click to expand...
Click to collapse
Lg flashtool? Check my signature.

Zarilenth said:
No still stuck at erasing 'cache'
Click to expand...
Click to collapse
Weird then. Try using LG Flashtool. You can find it in the first link of my signature
---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------
bitdomo said:
Lg flashtool? Check my signature.
Click to expand...
Click to collapse
Damn. xD

Lethargy said:
Weird then. Try using LG Flashtool. You can find it in the first link of my signature
---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------
Damn. xD
Click to expand...
Click to collapse
I followed the steps very closely it got to 6% and then froze saying userdata erase fail

Zarilenth said:
I followed the steps very closely it got to 6% and then froze saying userdata erase fail
Click to expand...
Click to collapse
Try locking your bootloader:
fastboot oem lock
Then reboot it with:
fastboot reboot-bootloader
If it still shows as unlocked after the reboot, then your eMMC is dead/damaged and there isn't much you can do other than RMA or motherboard replacement

Lethargy said:
Try locking your bootloader:
fastboot oem lock
Then reboot it with:
fastboot reboot-bootloader
If it still shows as unlocked after the reboot, then your eMMC is dead/damaged and there isn't much you can do other than RMA or motherboard replacement
Click to expand...
Click to collapse
I am able to oem lock and unlock no problem. Should I be locked or unlocked for lg flashtool?

Zarilenth said:
I am able to oem lock and unlock no problem. Should I be locked or unlocked for lg flashtool?
Click to expand...
Click to collapse
I haven't had to use it myself yet so I'm not sure. Just go with unlocked anyways. Try it once more, if it doesn't work then I'm not sure whats up with your device.

Lethargy said:
I haven't had to use it myself yet so I'm not sure. Just go with unlocked anyways. Try it once more, if it doesn't work then I'm not sure whats up with your device.
Click to expand...
Click to collapse
I tried locked and unlocked and no go. I guess it's actually unfixable. What a waste of time.
I would ask Google for a replacement, but I am guessing that's not going to be free with all the tampering I did, and plus I live in Canada now, after buying it in the States.

Zarilenth said:
I tried locked and unlocked and no go. I guess it's actually unfixable. What a waste of time.
I would ask Google for a replacement, but I am guessing that's not going to be free with all the tampering I did, and plus I live in Canada now, after buying it in the States.
Click to expand...
Click to collapse
If you bought from the Play Store they'll replace it regardless any tampering, if its a real hardware fault. If you know anybody in the US you should be able to send it to them to RMA. Not sure if you can give Google a call from Canada if you bought it in the US, though

Wow. Google was so nice when I called. They're going to replace it for free and do shipping to and from Canada, because I did buy it from the US Play Store. Thanks for your help Lethargy. So glad to not have to try anything anymore.

Acer A1-830 stuck in boot loop soft bricked.....

Okay i have an A1-830 & was installing a game, made a couple of modifications & now i have a soft bricked device.
I was installing Gangstar Rio & made some changes to try & get it to run as the minimum specs, my device had to run it but @ 1st it stated that the license was invalid so i changed the date backa year on advice from someone & it worked but then it stated that the device was incompatible, so i researched & found that was happening to most with devices that should have ran it but someone had advised to make some change to the 'batch.prop' file to fool the game to think it was a different device. I may have accidentally changed something in the batch file that caused this. i can't be certain but yeh, when i rebooted my tablet it got stuck @ the Acer logo in bootloop.
I tried recovery & did a factory reset & it acted like it was working but when i rebooted my device it still bootlooped. I then did some research & i tried to flash the stock rom but got errors each time i tried. i'll list the errors below;
i started off trying to flash the 'system.gz' file as follows;
>fastboot flash system Acer_AV052_A1-830_1.014.00_WW_GEN1.system.img.gz
> target reported max download size of 614470997 bytes
Invalid sparse file format at header magi
error: write sparse_skip_chunk: don't care size 202408408 is not a multiple of the block size 4096
sending sparse 'system' (600068 KB)
error: write sparse_skip_chunk: don't care size 202408408 is not a multiple of the block size 4096
error: write sparse_skip_chunk: don't care size 202408408 is not a multiple of the block size 4096
OKAY [ 68.091s]
writing 'system' . . .
FAILED (remote: flash_cmds error!)
>fastboot flash system Acer_AV052_A1-830_1.014.00_WW_GEN1.system.img
> target reported max download size of 614470997 bytes
Invalid sparse file format at header magi
sending sparse 'system' (585989 KB) . . .
OKAY [ 61.418s]
writing 'system' . . .
FAILED (remote: flash_cmds error!)
.................and these were the bootloader errors that appeared;
E: Unknown chunk type
failed: no such file or directory
E: flash system failed
FLASH FAILED!
--------------------------------------------------------------------------
these are my build & region details too;
region: Australia (South East Asia)
build #: ' Acer_AV0K0_A1-830_1.007.00_WW_GEN1
------------------------------------------------------------------------------
so that is where i am stuck @, i even made sure that i had the correct 'Java Development Tool Package' & 'Android Studio' was complete but everything else is out of my depth of knowledge. Any help will be 10 fold appreciated in advance...... :good:

acer a1-830
hi, i also have this problem, and i couldn't solve it yet. please inform me when you will have an resolve at mail [email protected]. best regards
---------- Post added at 09:10 PM ---------- Previous post was at 08:46 PM ----------
at the first flash boot, fastboot and recovery, then poweroff, after that flash system.img.gz

trinky13 said:
hi, i also have this problem, and i couldn't solve it yet. please inform me when you will have an resolve at mail [email protected]. best regards
---------- Post added at 09:10 PM ---------- Previous post was at 08:46 PM ----------
at the first flash boot, fastboot and recovery, then poweroff, after that flash system.img.gz
Click to expand...
Click to collapse
finally sorted it out.... it was simply the order that i was doing it in.... was basically flashing it backwards, hence causing the errors i was getting, arrrrrgh..... but @ least sorted, thanks a heap trinky for advising of the order @ the bottom of ur post!

KENTzee said:
finally sorted it out.... it was simply the order that i was doing it in.... was basically flashing it backwards, hence causing the errors i was getting, arrrrrgh..... but @ least sorted, thanks a heap trinky for advising of the order @ the bottom of ur post!
Click to expand...
Click to collapse
can you share how did you solved it? i'm also stuck in bootloop acer iconia a1-830, trying to find stock firmwares and flash it.
thanks...:crying:

trinky13 said:
hi, i also have this problem, and i couldn't solve it yet. please inform me when you will have an resolve at mail [email protected]. best regards
---------- Post added at 09:10 PM ---------- Previous post was at 08:46 PM ----------
at the first flash boot, fastboot and recovery, then poweroff, after that flash system.img.gz
Click to expand...
Click to collapse
Still getting these errors even I follow your instruction.
target reported max download size of 614886058 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 201994712 is not a multiple of the block size 4096
sending sparse 'system' (600472 KB)...
error: write_sparse_skip_chunk: don't care size 201994712 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 201994712 is not a multiple of the block size 4096
OKAY [ 68.063s]
writing 'system'...
FAILED (remote: flash_cmds error!)
finished. total time: 81.760s

I also have a problem along the same lines, I have a feeling I'm getting closer to solving it, but I can't seem to get it to boot.
It all seems to go well..
Code:
sending 'boot' (7591 KB)...
OKAY [ 0.886s]
writing 'boot'...
OKAY [ 0.919s]
finished. total time: 1.810s
sending 'fastboot' (9893 KB)...
OKAY [ 1.309s]
writing 'fastboot'...
OKAY [ 1.016s]
finished. total time: 2.332s
sending 'recovery' (9227 KB)...
OKAY [ 0.996s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.979s
sending 'system' (797732 KB)...
OKAY [ 51.121s]
writing 'system'...
OKAY [ 70.428s]
finished. total time: 121.554s
Then I try to start the tablet but just get a quick flash of the USB symbol and nothing else. I've tried various things but I'm not sure if I'm missing something here or not. Can anyone suggest anything? This is driving me crazy.

darkfilth101 said:
can you share how did you solved it? i'm also stuck in bootloop acer iconia a1-830, trying to find stock firmwares and flash it.
thanks...:crying:
Click to expand...
Click to collapse
http://www.mediafire.com/download/dxyx2q9ef4p8n17/SDs_Acer_AV0K0_A1-830_1.007.00_WW_GEN1.zip
here you go buddy

Hi RAZERZDAHACKER, how can I flash this zip?
all tutorials are about img files, but there are folders on zip
---------- Post added at 04:42 PM ---------- Previous post was at 04:24 PM ----------
nevermind, so easy, "apply update from external storage"
but I got error
Code:
E:end of footer from /tmp/sideload/package.zip not 0xFFFF (File exists)
E:signature verification failed

tictacbum said:
Hi RAZERZDAHACKER, how can I flash this zip?
all tutorials are about img files, but there are folders on zip
Click to expand...
Click to collapse
Download this to your computer and unzip it. Don't unzip the system folder in the zip file. Open fastboot and do fastboot flash boot (the boot img) then once that's done, do fastboot flash fastboot (fastboot img) then do fastboot flash recovery (recovery img) and then do fastboot reboot-bootloader. Then do fastboot flash system (system img.gz). Then on the tablet using the volume keys and the power button, go to recovery and wipe data then reboot, now it should be done!
---------- Post added at 05:42 PM ---------- Previous post was at 04:47 PM ----------
p0st3r^ said:
I also have a problem along the same lines, I have a feeling I'm getting closer to solving it, but I can't seem to get it to boot.
It all seems to go well..
Code:
sending 'boot' (7591 KB)...
OKAY [ 0.886s]
writing 'boot'...
OKAY [ 0.919s]
finished. total time: 1.810s
sending 'fastboot' (9893 KB)...
OKAY [ 1.309s]
writing 'fastboot'...
OKAY [ 1.016s]
finished. total time: 2.332s
sending 'recovery' (9227 KB)...
OKAY [ 0.996s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.979s
sending 'system' (797732 KB)...
OKAY [ 51.121s]
writing 'system'...
OKAY [ 70.428s]
finished. total time: 121.554s
Then I try to start the tablet but just get a quick flash of the USB symbol and nothing else. I've tried various things but I'm not sure if I'm missing something here or not. Can anyone suggest anything? This is driving me crazy.
Click to expand...
Click to collapse
I am not sure but by now you must have probably fixed it but try to boot into recovery and wipe data and reboot. That usually fixes bootloops upon flashing stock roms *ehum*samsung*ehum*, never the less, it also worked for me in my acer and I am back and running!

big thanks! tablet is booting fine again

tictacbum said:
big thanks! tablet is booting fine again
Click to expand...
Click to collapse
YAAAAAAAAAAAAY!!! Ah, I remember when I was stuck in a bootloop (and was a noob at android) so I took it down to the shop and they gave me a new one, then it happend again and I got another one for free! But as always, I'm so glad it worked!

I'm also having the FAILED (remote: flash_cmds error!) error. I have tried to do the steps in the specified order in the comments and I still get the error.
Can anyone help me?

ricardodeus said:
I'm also having the FAILED (remote: flash_cmds error!) error. I have tried to do the steps in the specified order in the comments and I still get the error.
Can anyone help me?
Click to expand...
Click to collapse
Reboot droidboot and try flashing the 4.2.2 image, also, try flashing in this order (boot, fastboot, recovery, system).
Hit thanks if I helped.

RAZERZDAHACKER said:
Reboot droidboot and try flashing the 4.2.2 image, also, try flashing in this order (boot, fastboot, recovery, system).
Hit thanks if I helped.
Click to expand...
Click to collapse
Is the 4.2.2 image the Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG version?
If so, I got the exact same error.

ricardodeus said:
Is the 4.2.2 image the Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG version?
If so, I got the exact same error.
Click to expand...
Click to collapse
Nope that's KitKat, 14 is 4.2.2

RAZERZDAHACKER said:
Nope that's KitKat, 14 is 4.2.2
Click to expand...
Click to collapse
I first tried Acer_AV052_A1-830_1.014.00_WW_GEN1_FLASHPKG, then Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG and got the same error for both.
target reported max download size of 614541994 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
sending sparse 'system' (600136 KB)...
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
OKAY [ 64.487s]
writing 'system'...
FAILED (remote: flash_cmds error!)
finished. total time: 78.156s

​
ricardodeus said:
I first tried Acer_AV052_A1-830_1.014.00_WW_GEN1_FLASHPKG, then Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG and got the same error for both.
target reported max download size of 614541994 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
sending sparse 'system' (600136 KB)...
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
error: write_sparse_skip_chunk: don't care size 244878635 is not a multiple ofthe block size 4096
OKAY [ 64.487s]
writing 'system'...
FAILED (remote: flash_cmds error!)
finished. total time: 78.156s
Click to expand...
Click to collapse
Have you wiped data? Also, reboot droidboot and make sure fastboot recognizes the device. Maybe you can try adb pushing the files via fastboot oem startftm command.

Delete this

a1 830 no droid boot
ramiabouzahra said:
Delete this
Click to expand...
Click to collapse
help me guys my a1-830 no droid boot or recovery hang on logo only do you have solutions

rolly20 said:
help me guys my a1-830 no droid boot or recovery hang on logo only do you have solutions
Click to expand...
Click to collapse
How are you trying to access droidboot? You can't hang on logo if you don't have droidboot (it's the bootloader mate).

Nexus 5 stuck in boot animation?

Hi,
my Nexus 5 was plugged on my laptop.
After a while I saw, that my phone rebooted. I saw the google logo.
I pressed and hold the "Power Button".
My phone booted again and stuck in the booting animation.
This happened three days ago.
I tried so many things. It's not working.
Maybe I messed up the partition.
The first thing I tried was to flash the android factory image like this (Flashing instructions - don't forget to press the button "ACKNOWLEDGE"):
https://developers.google.com/android/images
I first thought, that maybe the eMMC is fried.
I checked this like this ( https://forum.xda-developers.com/showthread.php?t=1284196 ):
Code:
adb shell
dmesg | grep mmc0
I didn't get a message like this:
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
I read, that I should change to usb 2.0 port and the usb cable.
I've also a Galaxy nexus. I've tried to flash a new stock with WugFresh. Everything worked with the usb 2.0 port and the usb cable.
When I tried to do that with my nexus 5 nothing works. I get this failure messages:
FAILED (remote: flash write failure)
I used TWRP (twrp-3.0.3-0-hammerhead.img) and clockwork mod (recovery-clockwork-touch-6.0.4.4-hammerhead.img).
The main errors I get:
Can't mount /data
...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovers/log
E: Can't open /cache/recovers/log
...
I really don't know what to do.
Is there a method to build the partition new? Or what else can I do?
Thank you for any help.

Does the bootloader relock when rebooted after being unlocked? Have you tried flashing the stock KK ROM?

Yes. It relocks when rebooted.

Do you mean Kit Kat? No, I didn't. I've tried only the new versions like 6.0.1 (MOB31E), 6.0.1 (M4B30Z, Dec 2016).
I will try KK Rom later.

I've downloaded this factory image:
"hammerhead" for Nexus 5 (GSM/LTE)
4.4.4 (KTU84P)
from here: https://developers.google.com/android/images
This is the original "flash-all.bat" file:
Code:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip
echo Press any key to exit...
pause >nul
exit
I've changed the "flash-all.bat" a little bit. I added this line "fastboot oem unlock". When I not add "fastboot oem unlock", I get a message like "not unlocked":
Code:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
[B]fastboot oem unlock[/B]
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip
echo Press any key to exit...
pause >nul
exit
I've started the "flash-all.bat". This is the output:
Code:
target reported max download size of 1073741824 bytes
sending 'bootloader' (2508 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.406s
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
< waiting for any device >
...
OKAY [ 4.109s]
finished. total time: 4.109s
target reported max download size of 1073741824 bytes
sending 'radio' (45409 KB)...
OKAY [ 1.625s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.844s
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
< waiting for any device >
...
OKAY [ 6.250s]
finished. total time: 6.250s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
wiping cache...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ20f
Baseband Version.....: M8974A-2.0.50.2.29
Serial Number........: 04ae306b2524b05b
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ20f'.
Update requires 'HHZ11k'.
finished. total time: 0.594s
Press any key to exit...

Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.

audit13 said:
Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.
Click to expand...
Click to collapse
I have the same problem and after doing that I can see that my eMMC is in fact fried since the bootloader relocks. I was wondering, where is the bootloader/fastboot stored on the device? On the CPU/GPU/RAM stack or on the eMMC. If I swap out the eMMC chip, will I still be able to access it (the bootloader) with a blank eMMC or is it on the eMMC as well? I'm trying to find out what are the steps to format and partition the eMMC after a new one is installed...

I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.

audit13 said:
I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.
Click to expand...
Click to collapse
Thank you very much for sharing your experience!
I would assume that the bootloader is located on the eMMC since I can't write to the bootloader (or any other) partition from fastboot. I'll have to look into solutions during the weekend since I don't have much time until then, but replacing the MB is a no go for me because of the price.

I'm not sure where you are located but I live in a big city in Canada where I can find deals for people selling Nexus 5 phones with smashed screens and working internal components.
Good luck and please share your results. Thanks.

@audit13: When I unlock the bootloader and then reboot the phone into fastboot. The bootloader relocks.
Is the memory chip now really damaged? Can't I do nothing? My N5 is three years old. I don't want to pay a lot of money for a main board.

The cheapest solution for a damaged emmc chip may be to buy a used Nexus 5 with a smashed screen and working motherboard. This is what I had to do for 2 phones with self re-locking bootloaders.

I bought a display damaged nexus 5. It arrived today. Changed the main board. And Voila! It's working.
The other guy has installed this build:
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (MOB30H)
No my question: Which factory image should I install?
https://developers.google.com/android/images
"hammerhead" for Nexus 5 (GSM/LTE)
...
6.0.1 (MOB30H)
6.0.1 (MOB30M)
6.0.1 (MOB30P)
6.0.1 (MOB30Y)
6.0.1 (MOB31E)
6.0.1 (M4B30X, Oct 2016)
6.0.1 (M4B30Z, Dec 2016)
I'm not sure, because the last two has dates. Are they meaning something (I mean, are they special builds), because the other factory images don't have dates.

Or should I do this:
https://developers.google.com/android/ota
OTA binary image files that allow you to manually update your Nexus or Pixel device. This has the same effect of flashing the corresponding factory images, but without the need of wiping the device.
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (M4B30Z)
Is OTA better than factory images?

OK. I've installed this version 6.0.1 (M4B30Z, Dec 2016). Everything works.

TF700T - Bootloop TWRP after install with official TWRP app

Hi Guys, I need some help.
I tried to flash TWRP 3.1 over a 3.0 using the official TWRP app from the store (With root access) The img file I downloaded using the app is the one specific for the TF700T.
Now my device got stuck in a TWRP bootloop. Initially I got the classic RCK/ANDROID/WHIPE DATA menu, but since I used whipe data it is only cycling through TWRP boot loops. (No more menu)
I can only stop the loop using the volume-up rocker during boot.
I'm trying the adb sideload but I am unable to flash the recovery partition.
adb devices does return the device ID followed by 'recovery' but when flashing the new img file the process only waits for a responding device.
> adb devices (output above)
> adb reboot bootloader
> adb devices (output above)
> fastboot -i 0x0B05 flash recovery twrp31.img (Here is where it fails, the device reboot by itself returning to the bootloop / TWRP is obviously not flashed)
Tx a lot for your help
JS:crying:

Geez - where to start?
You should never use Wipe Data from the bootloader menu if you have a custom recovery installed!
You cannot use fastboot commands while connected in adb.
Two different protocols or tools:
Use adb in recovery or Android, and fastboot when I the bootloader.
And that is where you want to be to fix this.
So you have to use bootit.ko to kick the tablet out of the loop and into the bootloader. Not literally please
Check out the guide below and ask if not clear before you completely brick it...
And then never use an app again to flash a recovery. Ever!
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my Nexus 5X using Tapatalk

Hi
Thanks for your comments on my post. I will have a good look at the info tonight and check if all is clear before I execute the next step.
Kindest regards
JS
PS: I'll be a good boy from now on and keep your advice in the back of my head at all times.

It's not the first time that I see a story like yours. These apps have to be designed for many, many different devices and identify the correct partition to the flash the recovery to for each device. So they either need a large data base of Android devices with the correct partition tables (not likely) or they need to read the partition table off the device - correctly... And that's the weak spot. If you're unlucky it could flash the recovery to the boot partition - good luck getting out of that one.
In your case it flashed it wrong but not super wrong and then you made it worse with that wipe data.
As long as you have adb in recovery this should be fixable. Good luck!
Sent from my Nexus 5X using Tapatalk

Made some progress
Here are the results of my attempt
adb push bootit.ko /
1136 KB/s (27690 bytes in 0.023s)
adb shell insmod /bootit.ko
(No return, so I asume its ok)
GOT OUT OF BOOTLOOP
fastboot devices
015d2bbce63fec14 fastboot
fastboot erase misc
erasing 'misc'...
OKAY [ 0.260s]
finished. total time: 0.261s
fastboot reboot
rebooting...
finished. total time: 0.020s
fastboot -i 0x0B05 flash recovery twrp31.img
< waiting for device >
sending 'recovery' (7218 KB)...
OKAY [ 2.863s]
writing 'recovery'...
OKAY [ 8.069s]
finished. total time: 10.933s
fastboot reboot
rebooting...
finished. total time: 0.021s
TWRP 3.1.0.0 is loaded, when I boot I get the splash screen, but there it loops again. Stop bootloop by using Volume down rocker.
I have used following commands with the new 3.1.0.0
fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.249s]
finished. total time: 1.249s
fastboot -w
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
erasing 'userdata'...
OKAY [ 64.078s]
sending 'userdata' (139133 KB)...
OKAY [ 25.092s]
writing 'userdata'...
OKAY [ 2.166s]
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 96.343s
fastboot -i 0x0B05 flash recovery filename.img
sending 'recovery' (7126 KB)...
OKAY [ 2.029s]
writing 'recovery'...
OKAY [ 7.546s]
finished. total time: 9.590s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
TWRP does start OK, I am able to flash a custom ROM
Thanks a lot for your incredible support. I hope to have your knowledge and understanding on this topic on day
Kindest regards
JS

It's just practice my friend, just practice. And making a lot of stupid mistakes. Like you did.
Glad you're up and running
Sent from my Nexus 5X using Tapatalk

Hi,
I had to erase/format the system and data partition to get access to TWRP. (fastboot -w)
Once that was done, it all went smooth and silky.
Tx again
JS :good:

berndblb said:
Geez - where to start?
You should never use Wipe Data from the bootloader menu if you have a custom recovery installed!
You cannot use fastboot commands while connected in adb.
Two different protocols or tools:
Use adb in recovery or Android, and fastboot when I the bootloader.
And that is where you want to be to fix this.
So you have to use bootit.ko to kick the tablet out of the loop and into the bootloader. Not literally please
Check out the guide below and ask if not clear before you completely brick it...
And then never use an app again to flash a recovery. Ever!
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
Click to expand...
Click to collapse
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!

[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!
Click to expand...
Click to collapse
Hey @[email protected] - how about sharing the script? I'd like to add it to the guide.

[email protected] said:
I made this same stupid mistake. However, my situation is a bit more irritating. TWRP never actually finishes loading on my TF700T; rather the splash screen appears and about 20 seconds or so later it reboots and continues this same vicious cycle. So I can't keep an adb device attached long enough to issue the adb commands. Any ideas how I can get out of this mess? Any ideas are much appreciated!
---------- Post added 15th April 2017 at 12:01 AM ---------- Previous post was 14th April 2017 at 11:49 PM ----------
Ha, never mind. I created a batch file to execute the two commands quicker than I could type them and ran it as soon as TWRP appeared and this got me back to the bootloader. Thanks!
Click to expand...
Click to collapse
Hello can you share your batch file because I have the same problem as you had.