Database Info

[Tool] SparseConverter v1.0.1

About:
fastboot stores each file it receives in RAM before flashing it to your Android device.
For this reason, large partitions (such as the /system partition) must be splitted using the "compressed ext4 file system sparse image format",
this format is defined by the AOSP (Android Open Source Project) and was designed for the single purpose of flashing a large partition.
If you tried to flash system.img from backup and received the "Invalid sparse file format at header magi" error, you have come to the right place.
The Solution:
SparseConverter is a tool that can create / decompress compressed ext4 file system sparse image format (e.g. system.img_sparsechunk1).
Note for Motorola phone owners:
The factory images from Motorola contains a 128KB motorola header and a 4KB motorola footer, if you decompress those images you may want to remove the header and footer.
I had no problem using the standard Android fastboot with my unlocked Moto G and flashing images without the Motorola header / footer.
(If you keep the header / footer, then you must use Motorola's fastboot)
Usage Examples:
SparseConverter.exe /compress D:\system.img E:\ 256MB
( will compress D:\system.img to 256MB sparse files starting from E:\system.img_sparsechunk1 )
SparseConverter.exe /decompress E:\system.img_sparsechunk1 D:\system.img
( will decompress E:\system.img_sparsechunk1, E:\system.img_sparsechunk2 and etc. to D:\system.img )
The software may contain bugs and/or limitations that may result in damage to your phone, I take no responsibility for any damage that may occur.
For additional information about the "compressed ext4 file system sparse image format" see libsparse/sparse_format.h
p.s. Source code in C# is provided, Windows XP \ 2003 users must install the .Net Framework 2.0 before running this tool.

How can i flash system.img when is too large. i have compressed it using this tool, now how to flash?

Everything is explained in the original post, You need to use fastboot.exe which is part of the ADT bundle (Android Development Tools).

tal.aloni said:
Everything is explained in the original post, You need to use fastboot.exe which is part of the ADT bundle (Android Development Tools).
Click to expand...
Click to collapse
fastboot flash system system.img_sparsechunk1 ?
Not working for me. :/
It will be downloaded to device, but not flashed.

yes,
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
make sure the system partition size match the image that you're trying to flash, to flash a bigger image you'll have to reflash the partition table and all the partitions (boot, recovery etc.)
p.s. not sure what "not working" means, what error do you get exactly?

tal.aloni said:
yes,
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
make sure the system partition size match the image that you're trying to flash, to flash a bigger image you'll have to reflash the partition table and all the partitions (boot, recovery etc.)
p.s. not sure what "not working" means, what error do you get exactly?
Click to expand...
Click to collapse
Here is my error code, after attemp to flash system system.img_sparechunk1:
FAILED (remote: flash_cmds error!)
partition size match, it is system dump from another same device.

Sorry, I'm not familiar with this error.

tal.aloni said:
Sorry, I'm not familiar with this error.
Click to expand...
Click to collapse
I have Rooted my ASUS Tablet, and deleted something in system, now i am soft-bricked.
Now i cannot do somethnig, only use fastboot, butt i cannot flash system.
So i must waiting to developers, to port CWM/TWRP for my device.

Hi, I'm trying to convert a userdata.img file (60GB!) so I can flash it with fastboot onto my phone, when I run the tool I get this
Code:
C:\Users\Matt\Documents\SparseConverter_1.0.0>sparseconverter /compress C:\Users
\Matt\Documents\userdata.img "C:\Users\Matt\Documents\userdata sparse" 256MB
Image size is not a multiple of 4096 bytes
Does this mean that it won't convert my image? Thanks
EDIT: Also I know this image is valid as under linux
Code:
[email protected]:~$ sudo mount -t ext4 -o loop /home/matt/userdata.img /home/matt/ext4
[sudo] password for matt:
[email protected]:~$ sudo su
[email protected]:/home/matt# cd ext4
[email protected]:/home/matt/ext4# ls
anr bugreports dontpanic media resource-cache user
app cam_socket1 dpm mediadrm security
app-asec cam_socket2 drm misc shared
app-lib connectivity fdAlbum nfc system
app-private dalvik-cache local opponvitems time
backup data lost+found property tombstones

Hi Matt,
ext4 allocates storage space in units of "blocks". A block is a group of sectors between 1KiB and 64KiB, and the number of sectors must be an integral power of 2. Block size is specified at mkfs time and typically is 4KiB.
Click to expand...
Click to collapse
The sector size for most flash devices is 4096 bytes.
The "compressed ext4 file system sparse image format" assumes that the image is going to be flashed to a flash device, and thus expects its size to be a multiple of 4096 bytes.
I'm not sure how you created this user data partition image, the size of a proper image (for flashing purposes) should be a multiple of 4096 bytes.
Edit: BlockSize can be set to 512 instead of 4096 in SparseConverter source code (SparseCompressionHelper.cs).

tal.aloni said:
Hi Matt,
The sector size for most flash devices is 4096 bytes.
The "compressed ext4 file system sparse image format" assumes that the image is going to be flashed to a flash device, and thus expects its size to be a multiple of 4096 bytes.
I'm not sure how you created this user data partition image, the size of a proper image (for flashing purposes) should be a multiple of 4096 bytes.
Click to expand...
Click to collapse
I ran into this issue as well. I am trying to compress the userdata image from my phone that was previously bricked and I'd like to find a way to hold onto this data.
Thank you!

hazard666 said:
I ran into this issue as well. I am trying to compress the userdata image from my phone that was previously bricked and I'd like to find a way to hold onto this data.
Thank you!
Click to expand...
Click to collapse
How did you create this image? are you sure it's a raw image?
if it's indeed a raw image, you could append a the necessary amount of zero bytes to the image (e.g. using HxD) and then you could compress it.
I'm not sure what you mean by "hold onto this data", this tool is to prepare an image for flashing, if you're trying to access the files there are other methods (e.g. linux).

Awesome, I use this tool to compress system file of Motorola X2014 of 2.7GB that I was not able to flash it... works great, thank you so much

Great progress! In my case
I generate my system.img.raw by
adb root
adb wait-for-device
adb shell "dd if=/dev/block/platform/f9824900.sdhci/by-name/system of=/sdcard/system.img.raw"
adb pull -p /sdcard/system.img.raw
1st Trail below will NOT works, but at the end you will see my solution:
Windows cmd log:
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>sparseconverter /compress system.img.raw .\ 536870912
...
pause
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>fastboot flash system system.img.raw_
sparsechunk1
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.591s]
sending 'system' (524284 KB)...
OKAY [ 1.350s]
writing 'system'...
OKAY [ 13.953s]
finished. total time: 15.897s
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>fastboot flash system system.img.raw_
sparsechunk2
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.532s]
sending 'system' (524287 KB)...
OKAY [ 1.351s]
writing 'system'...
OKAY [ 8.678s]
finished. total time: 10.565s
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>fastboot flash system system.img.raw_
sparsechunk3
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.524s]
sending 'system' (411515 KB)...
OKAY [ 1.075s]
writing 'system'...
OKAY [123.069s]
finished. total time: 124.671s
Please note even we pass the fastboot flashing, but it does NOT works after flash is finished, the phone can reboot to Linux logo, but block there, can not start Android Animation and go to desktop.
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
SO, SOLUTION is:
as an conclusion, it seems fastboot can not manage the multi input images well, BUT it can handle a single compressed image files, so set the max image side to the partition size to 2684354560 can make fastboot works well.
I need to find my original dd output file system.img.raw in 2.5GB, then:
Windows cmd logs:
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>sparseconverter /compress system.img.raw .\ 2684354560
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>fastboot flash system system.img.raw_sp
arsechunk1
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.767s]
sending sparse 'system' (521371 KB)...
OKAY [ 4.530s]
writing 'system'...
OKAY [ 9.577s]
sending sparse 'system' (511116 KB)...
OKAY [ 6.465s]
writing 'system'...
OKAY [ 10.833s]
sending sparse 'system' (445892 KB)...
OKAY [ 6.274s]
writing 'system'...
OKAY [139.377s]
finished. total time: 177.831s
that will bring my system.img.raw back to my phone WELL
you can see my rooted su is there, ^_^:
E:\AzlunData\DEV Tools\ImageBakupsCMD\SYS GMS+Root+AzAppsMDP>adb shell
[email protected]:/ $ su
su
[email protected]:/ #

Matt, hazard666,
I was wrong, there is no restriction on BlockSize , you're welcome to download SparseConverter source code and set BlockSize to 512 (in SparseCompressionHelper.cs),
please let me know if this helps.

tal.aloni said:
Note for Motorola phone owners:
The factory images from Motorola contains a 128KB motorola header and a 4KB motorola footer, if you decompress those images you may want to remove the header and footer.
I had no problem using the standard Android fastboot with my unlocked Moto G and flashing images without the Motorola header / footer.
(If you keep the header / footer, then you must use Motorola's fastboot)
Click to expand...
Click to collapse
Hi, I used your tool to decompress sparsechunks into a single system image for the Moto X 2014 XT1097, AT&T. This is needed as a preliminary step in order to get root.
The next step is to convert the image into an ext4 format. However, the instructions we have to do that require using linux command simg2img and it doesn't like the header. The errors are:
"Invalid sparse file format at header magi
Failed to read sparse file"
"Bad magic"
or
"Error reading sparse file header"
How do we get rid of this header? Thanks!

JulesJam said:
How do we get rid of this header? Thanks!
Click to expand...
Click to collapse
I usually do it manually with HxD (hex editor).
JulesJam said:
The next step is to convert the image into an ext4 format. However, the instructions we have to do that require using linux command simg2img and it doesn't like the header.
Click to expand...
Click to collapse
I think you're confused, once the image is decompressed, it's no longer a sparse file, you shouldn't use simg2img (to convert it to raw image, because it's already been done).
instead, you can just mount the image, for ext4 it would be:
Code:
sudo mount -t ext4 -o loop,offset=131072 system.img mnt/
and when you're done customizing:
Code:
sudo ./make_ext4fs -l 840M -a system mysystem.img mnt/
sudo umount mnt
(note that I've used offset=131072 instead of removing the header)

tal.aloni said:
I think you're confused, once the image is decompressed, it's no longer a sparse file, so you shouldn't use simg2img.
Click to expand...
Click to collapse
Yeah, I am definitely confused, lol!
tal.aloni said:
instead, use something along the line of (note that I've used offset=131072 instead of removing the header):
Code:
sudo mount -t ext4 -o loop,offset=131072 system.img mnt/
sudo ./make_ext4fs -l 840M -a system mysystem.img mnt/
sudo umount mnt
Click to expand...
Click to collapse
Ok great, I will have someone who knows linux try that. What we want is a single file system image in ext4 format so hopefully that will work!
Thanks!

tal.aloni said:
I usually do it manually with HxD (hex editor).
I think you're confused, once the image is decompressed, it's no longer a sparse file, you shouldn't use simg2img (to convert it to raw image, because it's already been done).
instead, you can just mount the image, for ext4 it would be:
Code:
sudo mount -t ext4 -o loop,offset=131072 system.img mnt/
and when you're done customizing:
Code:
sudo ./make_ext4fs -l 840M -a system mysystem.img mnt/
sudo umount mnt
(note that I've used offset=131072 instead of removing the header)
Click to expand...
Click to collapse
JulesJam said:
Yeah, I am definitely confused, lol!
Ok great, I will have someone who knows linux try that. What we want is a single file system image in ext4 format so hopefully that will work!
Thanks!
Click to expand...
Click to collapse
And I'm someone who's running a Linux distro!
After the second command I'm getting a memory allocation error though
"error: do_inode_allocate_extents: Failed to allocate 6524 blocks"

tal.aloni said:
I think you're confused, once the image is decompressed, it's no longer a sparse file, you shouldn't use simg2img (to convert it to raw image, because it's already been done).
Click to expand...
Click to collapse
Also, just to be complete, the way I am going to modify/root the ext4 image is by using TWRP on a bootloader unlocked device according to these instructions:
http://forum.xda-developers.com/showpost.php?p=60389310&postcount=177
It worked for the XT1096 so it should work for the XT1097. Once we get the rooted ext4 image, we have a tool to flash it to the XT1097 that bypasses the signature check. Our bootloaders are locked so we have to do it this way.

[Q] Phone not mounting and unable to flash roms

I downloaded Paranoid Android OTA update (from pa_hammerhead-4.43-20140715 to pa_hammerhead-4.44-20140722), planned on a clean flash but it automatically started to install the update. Once installed had a notification saying "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable", incase it was an unstable version of PA i flashed the older version back but the UID notification kept coming up. So i attempted a clean flash (factory reset through twrp) but it failed. So i did as the phone originally said and wiped the data partition. It can no longer mount the External Memory, as soon as i boot the phone all apps crash. It will not connect to any computer so i cannot move a stock ROM on to the phone to restore it. The laptop does acknowledge when it is connected but fails to install drivers.

braddover said:
I downloaded Paranoid Android OTA update (from pa_hammerhead-4.43-20140715 to pa_hammerhead-4.44-20140722), planned on a clean flash but it automatically started to install the update. Once installed had a notification saying "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable", incase it was an unstable version of PA i flashed the older version back but the UID notification kept coming up. So i attempted a clean flash (factory reset through twrp) but it failed. So i did as the phone originally said and wiped the data partition. It can no longer mount the External Memory, as soon as i boot the phone all apps crash. It will not connect to any computer so i cannot move a stock ROM on to the phone to restore it. The laptop does acknowledge when it is connected but fails to install drivers.
Click to expand...
Click to collapse
I've never seen "uid's on the phone are inconsistent" before. Can you boot into fastboot and does your pc recognize the device when you so? I'd start by flashing the system.img in fastboot and see if that'll work. If it doesn't I'd flash the entire factory image. Back up first though.
Sent from my Nexus 5 using XDA Free mobile app

ok, first of all make sure you've got adb tools on your pc. Then reboot in recovery mode (twrp or philz) and open a prompt in the platform-tools folder; now type the following:
adb shell
e2fsck /dev/block/platform/msm_sdcc.1/system
e2fsck /dev/block/platform/msm_sdcc.1/userdata
e2fsck /dev/block/platform/msm_sdcc.1/cache
continue to press enter if requested, then exit prompt.
Now download the rom you want to install, place it under platform-tools; then (if on twrp) go to "advanced" then "adb sideload", check the two checkbox and swipe. Open again the prompt from the platform-tools folder and type:
adb sideload "rom-name".zip
then reboot
Let me know how it goes.
EDIT:
if you miss drivers you can google them from google's website, then extract them in a folder (e.g. c:/drivers). Connect phone in recovery mode, look for it as "nexus 5" in device manager, open the properties to update drivers and point the location to the folder where you put the drivers in (c:/drivers). Then reboot recovery and see how it goes.

After this update mine cycles back to recovery
I've got a similar problem. This same update (from pa_hammerhead-4.43-20140715 to pa_hammerhead-4.44-20140722) has me stuck in recovery. I have cwm v6.0.4.5 and after flashing this update the phone goes back to recovery when trying to reboot. Usb storage isn't working from recovery so I can't put a different rom into the storage.
Any ideas on the best way to solve this? I'd be super excited if I didn't have to delete the data on the phone.
braddover said:
I downloaded Paranoid Android OTA update (from pa_hammerhead-4.43-20140715 to pa_hammerhead-4.44-20140722), planned on a clean flash but it automatically started to install the update. Once installed had a notification saying "UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable", incase it was an unstable version of PA i flashed the older version back but the UID notification kept coming up. So i attempted a clean flash (factory reset through twrp) but it failed. So i did as the phone originally said and wiped the data partition. It can no longer mount the External Memory, as soon as i boot the phone all apps crash. It will not connect to any computer so i cannot move a stock ROM on to the phone to restore it. The laptop does acknowledge when it is connected but fails to install drivers.
Click to expand...
Click to collapse

Akly said:
I've got a similar problem. This same update (from pa_hammerhead-4.43-20140715 to pa_hammerhead-4.44-20140722) has me stuck in recovery. I have cwm v6.0.4.5 and after flashing this update the phone goes back to recovery when trying to reboot. Usb storage isn't working from recovery so I can't put a different rom into the storage.
Any ideas on the best way to solve this? I'd be super excited if I didn't have to delete the data on the phone.
Click to expand...
Click to collapse
USB storage doesn't exist on the nexus 5.
Use adb push.
Click the link to the sticky thread in my signature. Then from there, find the "adb and fastboot. What is it?" thread.
Everything you need is there
Sent from my Nexus 5 using Tapatalk

Fastboot
jd1639 said:
I've never seen "uid's on the phone are inconsistent" before. Can you boot into fastboot and does your pc recognize the device when you so? I'd start by flashing the system.img in fastboot and see if that'll work. If it doesn't I'd flash the entire factory image. Back up first though.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for your reply, but that is what I tried before creating this post I also tried adb sideload in twrp but every time I swipe to run it, it says failed

braddover said:
Thanks for your reply, but that is what I tried before creating this post I also tried adb sideload in twrp but every time I swipe to run it, it says failed
Click to expand...
Click to collapse
Sounds like the flash memory may be corrupt.
I think your only choice is fastboot flash /LG flash tool.
We should try that and see what errors you get,

rootSU said:
Sounds like the flash memory may be corrupt.
I think your only choice is fastboot flash /LG flash tool.
We should try that and see what errors you get,
Click to expand...
Click to collapse
Thanks very much, I shall give it a go and get back to you

_MirageX_ said:
ok, first of all make sure you've got adb tools on your pc. Then reboot in recovery mode (twrp or philz) and open a prompt in the platform-tools folder; now type the following:
adb shell
e2fsck /dev/block/platform/msm_sdcc.1/system
e2fsck /dev/block/platform/msm_sdcc.1/userdata
e2fsck /dev/block/platform/msm_sdcc.1/cache
continue to press enter if requested, then exit prompt.
Now download the rom you want to install, place it under platform-tools; then (if on twrp) go to "advanced" then "adb sideload", check the two checkbox and swipe. Open again the prompt from the platform-tools folder and type:
adb sideload "rom-name".zip
then reboot
Let me know how it goes.
EDIT:
if you miss drivers you can google them from google's website, then extract them in a folder (e.g. c:/drivers). Connect phone in recovery mode, look for it as "nexus 5" in device manager, open the properties to update drivers and point the location to the folder where you put the drivers in (c:/drivers). Then reboot recovery and see how it goes.
Click to expand...
Click to collapse
Thanks very much I shall give it a go and get back to you, I've actually got a mac book pro, is it worth sponging off a mate and using his windows machine for this to avoid driver/connection issues that may not be to do with my current issue?

braddover said:
Thanks very much I shall give it a go and get back to you, I've actually got a mac book pro, is it worth sponging off a mate and using his windows machine for this to avoid driver/connection issues that may not be to do with my current issue?
Click to expand...
Click to collapse
You can do, but if you click the link in my signature to the sticky thread, then from there go to the "adb and fastboot what is it?" thread, there is link to a Mac Installer script which should be enough to resolve the issue. But failing that, yeah windows.

Hi can you run the following commands in your terminal when the phone is connected in recovery or in android with enabled usb debugging:
adb shell
cat /proc/partitions
and post the outcome here?

rootSU said:
You can do, but if you click the link in my signature to the sticky thread, then from there go to the "adb and fastboot what is it?" thread, there is link to a Mac Installer script which should be enough to resolve the issue. But failing that, yeah windows.
Click to expand...
Click to collapse
ok....so i gave that a crack, almost every process failed. This is what came up:
bradleys-mbp:hammerhead-krt16m Brad$ ./flash-all.sh
sending 'bootloader' (2506 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.487s
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
sending 'radio' (42033 KB)...
OKAY [ 1.664s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.885s
rebooting into bootloader...
OKAY [ 0.092s]
finished. total time: 0.092s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
ERROR: usb_write failed with status e00002c0
--------------------------------------------
ERROR: usb_write failed with status e00002c0
getvar:version-bootloader FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I also tried the longer method but same issues

Change USB cable and port also?
Sent from my Nexus 5 using Tapatalk

rootSU said:
Change USB cable and port also?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Just tried it, still nothing
came up with.....
bradleys-mbp:hammerhead-krt16m Brad$ ./flash-all.sh /Users/Brad/Desktop/hammerhead-krt16m
sending 'bootloader' (2506 KB)...
OKAY [ 0.307s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.508s
rebooting into bootloader...
OKAY [ 0.097s]
finished. total time: 0.097s
sending 'radio' (42033 KB)...
OKAY [ 1.694s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.915s
rebooting into bootloader...

Its not looking good. Don't forget to do what @bitdomo asked
Sent from my Nexus 5 using Tapatalk

bitdomo said:
Hi can you run the following commands in your terminal when the phone is connected in recovery or in android with enabled usb debugging:
adb shell
cat /proc/partitions
and post the outcome here?
Click to expand...
Click to collapse
Thanks for your reply, I hope I have done this correctly....this is what it came up with in TWRP
bradleys-mbp:~ Brad$ adb shell
~ # cat/proc/partitions
/sbin/sh: cat/proc/partitions: not found
i can't run the ADB sideloader in twrp as it fails every time, also I cannot enable USB debugging as i cannot get that far in to my phone to enable it

E: unable to mount
More info: when trying to do anything in twrp the main issue seems to be that it always comes up with "E: unable to mount" followed by either /persist or /cache

braddover said:
More info: when trying to do anything in twrp the main issue seems to be that it always comes up with "E: unable to mount" followed by either /persist or /cache
Click to expand...
Click to collapse
There's a thread to fix persist by @bitdomo. Its in the root guides section of Sticky roll-up in my signature
Sent from my Nexus 5 using Tapatalk

braddover said:
Thanks for your reply, I hope I have done this correctly....this is what it came up with in TWRP
bradleys-mbp:~ Brad$ adb shell
~ # cat/proc/partitions
/sbin/sh: cat/proc/partitions: not found
i can't run the ADB sideloader in twrp as it fails every time, also I cannot enable USB debugging as i cannot get that far in to my phone to enable it
Click to expand...
Click to collapse
There is a space between cat and /proc/partitions.
The link to the guide to fix persist is here http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576

bitdomo said:
There is a space between cat and /proc/partitions.
The link to the guide to fix persist is here http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Click to expand...
Click to collapse
Whoops silly me!
This is what it brought up when i added the space:
bradleys-mbp:~ Brad$ adb shell
~ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 28551146 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
I also tried to fix persist, it doesn't seem to have worked.
Running your first command gave me this and did not repair anything:
bradleys-mbp:~ Brad$ adb shell
~ # e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/msm_sdcc.1/by-name/persist: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name/persist
So i tried the next step which produced this:
bradleys-mbp:~ Brad$ adb shell
~ # make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
Creating filesystem with parameters:
Size: 16777216
Block size: 4096
Blocks per group: 32768
Inodes per group: 1024
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 4096
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/1024 inodes and 1102/4096 blocks
However i still do not have access to be able to copy the files over...

Official bootloader unlock for ZenFone 3 (ZE552KL / ZE520KL) is now available

[Update]
If you use official unlock app to unlock bootloader, you will not receive OTA notify.
For now, there are no way to re-lock bootloader, so you can not receive OTA notify.
If you want to receive OTA notify, you should use Un-official bootloader unlock method to unlock bootloader.
ZE552KL
ZE552KL_SIGNED_Android_M_UnlockTool_2016_0715.zip
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE552KL/ZE552KL_SIGNED_Android_M_UnlockTool_2016_0715.zip
ZE520KL
ZE520KL_SIGNED_Android_M_UnlockTool_2016_0715.zip
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/ZE520KL_SIGNED_Android_M_UnlockTool_2016_0715.zip
============================
Unlock Device App: Unlock boot loader for Andriod M
Unlock Device App: Unlock boot loader
Notice:
1. Update your software image to V 13.16.5.36 or latest version
2. Before you download, install, and use the Unlock Device App you acknowledge and assume
complete risk to the quality and performance of this App, including but not limited to the following:
once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions;
the Original Product with the activated App will not be deemed the Original Product;
the Revised Product will no longer be covered under the warranty of the Original Product;
the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product,
including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product;
the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.

Original Article : https://www.asus.com/zentalk/tw/thread-177309-1-1.html (thanks [email protected])
UN-official unlock method:
All-in-one zip (unlock App+driver+adb+fastboot+twrp+SuperSU.zip) :
https://github.com/snowwolf725/RootZenfone3/archive/master.zip
1. Unzip the file.
2. Boot your zenfone 3 to boot-loader mode (you should firstly turn the phone off, then press and hold the volume up and power buttons )
3. Double click to execute "0.unlock_{Device}.bat"
0.unlock_ze520kl.bat (for ZE520KL)
0.unlock_ze552kl.bat (for ZE552KL)
If the bat file not work, you can try to execute following commands：
1. fastboot flash all unlock_{Device}.raw
(for ZE520KL)
Code:
fastboot flash all unlock_ze520kl.raw
or (for ZE552KL)
Code:
fastboot flash all unlock_ze552kl.raw
2. fastboot reboot-bootloader
3. fastboot oem unlock-go

im using apk ure given to unclok the bootloader, is that officials or un-offcials ??

kuranzi said:
im using apk ure given to unclok the bootloader, is that officials or un-offcials ??
Click to expand...
Click to collapse
XXXX.APK => Official Unlock
XXXX.RAW => UN-Offical Unlock
Official Unlock => Easy to use, stable , No computer need, can't receive OTA notify
UN-Offical Unlock => Can receive OTA notify
Be careful, unlock boot-loader will void the warranty.
After unlocking bootloader, both methods (official or un-official) got warning message when boot device.
https://www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=177309&page=4#pid929774
So, Asus engineer can easily known that this device is been unlocked.
We didn't find out the method to remove this message yet.

So we have to wait till asus release how to lock boorloader ?

Does the unofficial unlock reformat the phone?

emeraldsrs said:
Does the unofficial unlock reformat the phone?
Click to expand...
Click to collapse
Yes. The same as the official one as well.

will this work with other versions of the zenfone 3 max, such as the us version(ze520tl)? the hardware is the same, just wondering.

/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android L)
// Version V4.1 dbg (2015/07/01)
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// WIPE-DATA/CACHE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 536870912 bytes
Invalid sparse file format at heade
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 16384
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/4096 inodes and 1294/16384 blocks
Creating filesystem with parameters:
Size: 57583562752
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14058487
Block groups: 430
Reserved block group size: 1024
Created filesystem with 11/3515680 inodes and 266738/14058487 blocks
Creating filesystem with parameters:
Size: 134217728
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 32768
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/8192 inodes and 1550/32768 blocks
sending 'config' CRC (0x884ab0fe)...
OKAY [ 0.016s]
writing 'CRC'...
OKAY [ 0.047s]
sending 'config' (512 KB)...
OKAY [ 0.047s]
writing 'config'...
OKAY [ 0.109s]
sending '' CRC (0x0)...
OKAY [ 0.047s]
writing 'CRC'...
OKAY [ 0.031s]
sending '' (0 KB)...
FAILED ()
finished. total time: 0.296s
When I run fastboot flash all unlock_ze552kl.raw, I get the above output. I have tried restarting both my pc and my phone, using another usb port, deleting and reinstalling asus drivers, but it did not help. What could be the problem?
On the other hand, I can reflash boot.img and recovery.img successfully.
Also, in the course of trying out other solutions, I ran fastboot erase system. Currently my phone is stuck on the asus bootloader screen when started normally.
1. Could it be caused by fastboot erase system?
2. If so, where can I find a system image to reflash?
Thanks in advance,
Jack

Could you please check if the boot warning is just the logo like on other phones which can be replaced by the original logo image?

After failing to root my device using windows, I used my mac terminal.
When I enter
Code:
fastboot flash all unlock_ze520kl.raw
I get
Code:
target reported max download size of 536870912 bytes
sending 'all' (522 KB)...
OKAY [ 0.040s]
writing 'all'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.061s
I was having a similar problem using windows

Sorry for this dumb question, but is this any where close to rooting the phone ?

catalinrcd said:
Sorry for this dumb question, but is this any where close to rooting the phone ?
Click to expand...
Click to collapse
Nope. As with other brands that lock their bootloaders, unlocking the bootloader is only the first step to rooting your phone. After bootloader unlock, you can proceed to root your phone.
Some brands like Samsung even have an extra layer of work to go: disabling the flash counter so that the phone doesn't detect future flashings of custom ROMs, etc.

Few minutes ago i just used this tool.
all i can say is that after i check "adv devices" , now i get my phone serial but it also says "unauthorized"
It also reseted my phone. The Zenfone 3 One click tool, still does nothing for me after this . Still can't root phone.
No idea if my phone has bootloader unlocked...? A message was on the screen before OS boot, but it was to fast,and i did not get to read it. So there for i can't really say if this works or not.
Now it seams i need to install this twrp . No idea what this is, or what will it do to my phone. Will return with more news.

Nougat update
snowwolf725 said:
Original Article : https://www.asus.com/zentalk/tw/thread-177309-1-1.html (thanks [email protected])
UN-official unlock method:
All-in-one zip (unlock App+driver+adb+fastboot+twrp+SuperSU.zip) :
https://github.com/snowwolf725/RootZenfone3/archive/master.zip
1. Unzip the file.
2. Boot your zenfone 3 to boot-loader mode (you should firstly turn the phone off, then press and hold the volume up and power buttons )
3. Double click to execute "0.unlock_{Device}.bat"
0.unlock_ze520kl.bat (for ZE520KL)
0.unlock_ze552kl.bat (for ZE552KL)
If the bat file not work, you can try to execute following commands：
1. fastboot flash all unlock_{Device}.raw
(for ZE520KL)
Code:
fastboot flash all unlock_ze520kl.raw
or (for ZE552KL)
Code:
fastboot flash all unlock_ze552kl.raw
2. fastboot reboot-bootloader
3. fastboot oem unlock-go
Click to expand...
Click to collapse
Did anyone try on the new OTA Nougat? Is it safe? Does it still work?

Hi there, I have a problem when I try to get into boot-loader mode (power + volume up) , i got this.
{
"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"
}
soved: it was fastboot, the wy to get into recovery was power + volume down.

Hi @snowwolf725.
My ZE552KL was rooted following some tutorials that I found in this forum, but I don't remember which bootloader I am currently using.
Since I'd like to receive OTA notification I'd like to know if I follow your tutorial I will lose my data and the root or it just change the booloader?
Best regards.

snowwolf725 said:
Original Article : https://www.asus.com/zentalk/tw/thread-177309-1-1.html (thanks [email protected])
UN-official unlock method:
All-in-one zip (unlock App+driver+adb+fastboot+twrp+SuperSU.zip) :
https://github.com/snowwolf725/RootZenfone3/archive/master.zip
1. Unzip the file.
2. Boot your zenfone 3 to boot-loader mode (you should firstly turn the phone off, then press and hold the volume up and power buttons )
3. Double click to execute "0.unlock_{Device}.bat"
0.unlock_ze520kl.bat (for ZE520KL)
0.unlock_ze552kl.bat (for ZE552KL)
If the bat file not work, you can try to execute following commands：
1. fastboot flash all unlock_{Device}.raw
(for ZE520KL)
Code:
fastboot flash all unlock_ze520kl.raw
or (for ZE552KL)
Code:
fastboot flash all unlock_ze552kl.raw
2. fastboot reboot-bootloader
3. fastboot oem unlock-go
Click to expand...
Click to collapse
hi.. are we able to use this unofficial method after upgrading to N, or we should do it before?

snowwolf725 said:
Original Article : https://www.asus.com/zentalk/tw/thread-177309-1-1.html (thanks [email protected])
UN-official unlock method:
All-in-one zip (unlock App+driver+adb+fastboot+twrp+SuperSU.zip) :
https://github.com/snowwolf725/RootZenfone3/archive/master.zip
1. Unzip the file.
2. Boot your zenfone 3 to boot-loader mode (you should firstly turn the phone off, then press and hold the volume up and power buttons )
3. Double click to execute "0.unlock_{Device}.bat"
0.unlock_ze520kl.bat (for ZE520KL)
0.unlock_ze552kl.bat (for ZE552KL)
If the bat file not work, you can try to execute following commands：
1. fastboot flash all unlock_{Device}.raw
(for ZE520KL)
Code:
fastboot flash all unlock_ze520kl.raw
or (for ZE552KL)
Code:
fastboot flash all unlock_ze552kl.raw
2. fastboot reboot-bootloader
3. fastboot oem unlock-go
Click to expand...
Click to collapse
im upgrade my zen 3 520kl to android 7.0 but i unlock bootloader my phone then it's not successfully

T M L said:
After failing to root my device using windows, I used my mac terminal.
When I enter
Code:
fastboot flash all unlock_ze520kl.raw
I get
Code:
target reported max download size of 536870912 bytes
sending 'all' (522 KB)...
OKAY [ 0.040s]
writing 'all'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.061s
I was having a similar problem using windows
Click to expand...
Click to collapse
me too !!
u can unlock bootloader ? help me !
my zen3 520kl upgraded android 7.0

Searching TWRp for Alcatel Pixi 4 (6) 8050D

Hi @ all
XDA ever was my favorite site/board for developer solutions and modding devices.
Also in my actual case.
1. Sorry if that threat is in a false area.
2. I Know that a developer threat even exists and a special threat for the pixi 4 (6) too but I think the problem is not that specific.
3. Mods pls feel free to move or delete it if there is anything against the rules
Original Post start |---------------------------------------------------------------------------------------------->
Hi there,
i followed the instructions from the first post of this thread. Just a little log for overview:
Enable USB-debugging and OEM-unlock-possible in the developer erea of my phone --> OK
Restart via ADB to bootloader mode --> OK
Unlock bootloader with "fastboot oem unlock" and tap on the vol+ key --> OK
Flash "fastboot flash recovery [email protected]_Kevios12_v2.img" --> OK
Code:
target reported max download size of 134217728 bytes
sending 'recovery' (13432 KB)...
OKAY [ 0.391s]
writing 'recovery'...
OKAY [ 0.884s]
finished. total time: 1.276s
Now if i force reboot with vol+ and the power key and select recovery it loops like...
Logo-->Black-->TWRP Logo-->TWRP Errors-->Black-->Again...
It's impossible to input anything
The Log entries are:
Could not mount /data and unable to find crypto footer
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder.
Updating partition details. . .
Failed to mount '/data' (invalid argument)
. . . done
Unable to mount /storage
Failed to mount '/data' (invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Running recovery commands.
Formating Cache using make_ext4fs. . .
Failed to mount '/data' (invalid argument)
Done processing script file
Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.
I've found solutions that the crypto problem is about left over files in the userdata partition by some devices.
To solve this problem try "fastboot format userdata" ends with an error message:
D:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 838860800
Block size: 4096
Blocks per group: 32768
Inodes per group: 7328
Inode size: 256
Journal blocks: 3200
Label:
Blocks: 204800
Block groups: 7
Reserved block group size: 55
Created filesystem with 11/51296 inodes and 6651/204800 blocks
target reported max download size of 134217728 bytes
erasing 'userdata'...
FAILED (remote: unknown command)
finished. total time: 0.009s
Click to expand...
Click to collapse
Now I've no more ideas what can i do.
please help me (i hope i did'nt forgot anything)
<----------------------------------------------------------------------------------------------| Original Post ends.
Link: http://forum.xda-developers.com/and...el-pixi-46-3g-rom-t3450723/page3#post69473085
I ask this topic here again because i don't know where to post such questions to they where seen by much as possible people (whoa bad english)
Thx for help,.... i hope^^

poppm said:
Hi @ all
XDA ever was my favorite site/board for developer solutions and modding devices.
Also in my actual case.
1. Sorry if that threat is in a false area.
2. I Know that a developer threat even exists and a special threat for the pixi 4 (6) too but I think the problem is not that specific.
3. Mods pls feel free to move or delete it if there is anything against the rules
Original Post start |---------------------------------------------------------------------------------------------->
Hi there,
i followed the instructions from the first post of this thread. Just a little log for overview:
Enable USB-debugging and OEM-unlock-possible in the developer erea of my phone --> OK
Restart via ADB to bootloader mode --> OK
Unlock bootloader with "fastboot oem unlock" and tap on the vol+ key --> OK
Flash "fastboot flash recovery [email protected]_Kevios12_v2.img" --> OK
Code:
target reported max download size of 134217728 bytes
sending 'recovery' (13432 KB)...
OKAY [ 0.391s]
writing 'recovery'...
OKAY [ 0.884s]
finished. total time: 1.276s
Now if i force reboot with vol+ and the power key and select recovery it loops like...
Logo-->Black-->TWRP Logo-->TWRP Errors-->Black-->Again...
It's impossible to input anything
The Log entries are:
Could not mount /data and unable to find crypto footer
Failed to mount '/data' (invalid argument)
Unable to recreate /data/media folder.
Updating partition details. . .
Failed to mount '/data' (invalid argument)
. . . done
Unable to mount /storage
Failed to mount '/data' (invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Running recovery commands.
Formating Cache using make_ext4fs. . .
Failed to mount '/data' (invalid argument)
Done processing script file
Renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP.
I've found solutions that the crypto problem is about left over files in the userdata partition by some devices.
To solve this problem try "fastboot format userdata" ends with an error message:
Now I've no more ideas what can i do.
please help me (i hope i did'nt forgot anything)
<----------------------------------------------------------------------------------------------| Original Post ends.
Link: http://forum.xda-developers.com/and...el-pixi-46-3g-rom-t3450723/page3#post69473085
I ask this topic here again because i don't know where to post such questions to they where seen by much as possible people (whoa bad english)
Thx for help,.... i hope^^
Click to expand...
Click to collapse
Hi! May I know how you managed to solve this problem? I currently experiencing the same thing right now

[HELP] Nexus 5 die, can't enter recovery mode (only Bootloader mode)

Hello,
My phone fell to the floor and since than can't boot.
I see the google logo and then it turning off.
I can't enter recovery mode.
I can enter bootloader mode, tried to re-flash the rom (factory) with -w (wipe) and still can't boot / enter recovery mode.
Any suggestions?
Thanks!

time for a new phone

If the screen is okay, get a nexus 5 with a busted screen and swap internal components.

I have the same problem, but allow me to add some more details:
When trying to go to recovery, i got a dead droid with a red sign on it. See my post on android enthusiasts: /questions/169999/stuck-in-bootloop-and-flash-recovery-doesnt-work-on-nexus-5/170395 (can't post url from my account)
From fast boot, I could flash a recovery (my fastboot is unlocked) but it gave no results: still had the dead droid (tried with twrp, cwm, and stock rom).
After that I gave up trying to get back my data and tried flashing the whole stock rom, but it when bad. Now when trying to flash anything I got errors:
Code:
$ sudo ./fastboot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (13348 KB)...
OKAY [ 0.630s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.936s
- or -
Code:
$ sudo ./fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.118s
The only good news is I realized I could boot to any arbitrary recovery without flashing it with:
Code:
$ sudo ./fastboot boot recovery.img.twrp
Most functions on recory wouldn't work (it says it can't mount most partitions), but from where I can get an
Code:
adb shell
. I tried various steps but without success so far:
Code:
~ # e2fsck /dev/block/platform/msm_sdcc.1/by-name/recovery
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/recovery
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
Code:
~ # e2fsck /dev/block/platform/msm_sdcc.1/by-name/system
e2fsck 1.41.14 (22-Dec-2010)
system: clean, 1939/65536 files, 254904/262144 blocks
Code:
~ # e2fsck /dev/block/platform/msm_sdcc.1/by-name/cache
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/msm_sdcc.1/by-name/cache: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name/cache
I think I managed to somehow mess up my partition system, and I don't know much how to recover it, anyone have clues or can suggest something ?

You may need to replace the power button on the motherboard. If the phone keeps booting and then restarting when the Google logo appears, the power button might be your culprit. It was for me, and after a trip to my local repair shop, it is as good as new.

Fvolfrine said:
You may need to replace the power button on the motherboard. If the phone keeps booting and then restarting when the Google logo appears, the power button might be your culprit. It was for me, and after a trip to my local repair shop, it is as good as new.
Click to expand...
Click to collapse
The power button works fine on my phone. It's isn't constantly rebooting, but it gets stuck at the booting animation. I can use the power normally in the bootloader and it behaves as expected.

biaib said:
The power button works fine on my phone. It's isn't constantly rebooting, but it gets stuck at the booting animation. I can use the power normally in the bootloader and it behaves as expected.
Click to expand...
Click to collapse
I have the same problem sir.
were you able to solve your issue?
If yes please explain how?

If the phone is stuck at the boot animation, try flashing the oldest Kit Kat ROM from the Google site: https://developers.google.com/android/images

ahiel2 said:
Hello,
My phone fell to the floor and since than can't boot.
I see the google logo and then it turning off.
I can't enter recovery mode.
I can enter bootloader mode, tried to re-flash the rom (factory) with -w (wipe) and still can't boot / enter recovery mode.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
Well I Still am trying to fix that issue since almost 2 years now.....
My guesses are that eMMC is damaged when you thre your phone.
If you do find a solution please do let me know.
Thanks!