[lug] Convertion of ext4 Sparse Files

stimits at comcast.net stimits at comcast.net
Sat Jan 6 14:01:23 MST 2018


FYI, the file systems were originally created on ordinary Ubuntu and Fedora systems via a loopback mounted file. This file is copied bit-for-bit exactly to the device...or read back bit-for-bit exact during cloning. It is the conversion from non-sparse to sparse which has the unknown Android issue, but when not sparse it is entirely plain vanilla desktop PC Linux.
 
----- Original Message -----From: Aaron D. Johnson <adj at fnord.greeley.co.us>To: Boulder (Colorado) Linux Users Group -- General Mailing List <lug at lug.boulder.co.us>Sent: Sat, 06 Jan 2018 20:33:47 -0000 (UTC)Subject: Re: [lug] Convertion of ext4 Sparse Files

stimits at comcast.net writes:> > Search on Android sparse image. I found all kinds of tools> > referenced online.> > In order for reading a sparse file to result in the bytes of a> non-sparse file the reader or the driver of the file system must> recognize this as such...apparently this version is recognized as> an Android sparse image when the "file" command is run on it, but no> other tool...even some of those specific to Android ...seems to work> on this. I'm trying to get more information from the creator of the> tool which created the sparse file.

Your "Android sparse image" file is something different than a sparsefile on a UNIXy filesystem like ext4. This is unfortunately veryconfusing for those of us trying to help out -- we saw "ext4 sparsefile" in your subject line and went off trying to understand how thatmight cause the problems you're experiencing.

At this point, you are correct -- the tool which created the Androidimage file (sparse or otherwise) has left you with something thatneeds to be extracted if you'd like to access using a more "normal"(by which I mean desktop or server-ish) Linux system. I would hopethe image creator tool's author is capable of explaining how toextract the image file's contents.

Please let us know if you can get anywhere on that front. If not,perhaps you can share the image file itself somewhere and others cansee what it might take to make use of it.

- Aaron_______________________________________________Web Page: http://lug.boulder.co.usMailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lugJoin us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20180106/7599ba22/attachment.html>


More information about the LUG mailing list