Custom ROM creation mentoring

[900supersport]

Re: Custom ROM creation mentoring

On the tablet from the terminal enter mount then press enter. You should see all the pre configured mounts including one for system. On my cube mini I get

app_66@android:/ $ mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock8 /system ext4 rw,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mtdblock6 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data= ordered,noauto_da_alloc 0 0
/dev/block/mtdblock5 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data= ordered,noauto_da_alloc 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/external_sd fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksi ze=4096 0 0
/dev/block/vold/31:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime, uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/31:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime, uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
app_66@android:/ $

The line below shows system is mounted ext4.

/dev/block/mtdblock8 /system ext4 rw,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0

BTW I think cramfs is read only so at best the -r will be ignored.

[elektrik]

On the tablet from the terminal enter mount then press enter. You should see all the pre configured mounts including one for system. On my cube mini I get

app_66@android:/ $ mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock8 /system ext4 rw,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mtdblock6 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data= ordered,noauto_da_alloc 0 0
/dev/block/mtdblock5 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data= ordered,noauto_da_alloc 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/external_sd fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksi ze=4096 0 0
/dev/block/vold/31:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime, uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/31:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime, uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utim e=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
app_66@android:/ $

The line below shows system is mounted ext4.

/dev/block/mtdblock8 /system ext4 rw,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0

BTW I think cramfs is read only so at best the -r will be ignored.

The only one I see is this:

/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=writeba ck 0 0

So if this is ext4...I wonder why it's not mounting... Still get the ioctl problem.... Here's my whole mount dump:

mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=writeba
ck 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journ al
_checksum,data=writeback,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journ a
l_checksum,data=writeback,noauto_da_alloc 0 0
/dev/block/vold/179:1 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,ui
d=1000,gid=1023,fmask=0702,dmask=0702,allow_utime= 0020,codepage=cp437,iocharset=
ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:64 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime =0020,codepage=cp437,iocharset
=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:64 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_ utime=0020,codepage=cp437,ioch
arset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkxda.activity-1 vfat ro,dirsync,nosu
id,nodev,relatime,uid=1000,fmask=0222,dmask=0222,c odepage=cp437,iocharset=ascii,
shortname=mixed,utf8,errors=remount-ro 0 0

[jtintle]

I've been following this thread, and did mount on my 701C running the cyanbook jellybean rom, and came up with:

u0_a34@android:/ $ export PATH=/data/local/bin:$PATH
u0_a34@android:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/nandd /system ext4 ro,noatime,nodiratime,user_xattr,barrier=0,data=or dered,noauto_da_alloc 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barr ier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,nodiratime,user_xattr,barr ier=0,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:64 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=cp437,iocharset=ascii,shortname=mixed,utf8,e rrors=remount-ro 0 0
/dev/block/vold/93:64 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=cp437,iocharset=ascii,shortname=mixed,utf8,e rrors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:1 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=cp437,iocharset=ascii,shortname=mixed,utf8,e rrors=remount-ro 0 0
/dev/block/dm-0 /mnt/asec/com.flyersoft.moonreaderp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier =1 0 0
/dev/block/dm-1 /mnt/asec/com.rovio.BadPiggies-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier =1 0 0
/dev/block/dm-2 /mnt/asec/com.noinnion.android.greader.readerpro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier =1 0 0
/dev/block/dm-3 /mnt/asec/com.google.android.apps.plus-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier =1 0 0
u0_a34@android:/ $

[900supersport]

Re: Custom ROM creation mentoring

So from Linux you should be able to mount with

sudo mount -t ext4 -o loop system.img system

[elektrik]

So from Linux you should be able to mount with

sudo mount -t ext4 -o loop system.img system

Ok, perhaps I'm going about this the wrong way. The .img file I'm using is the stock .img file taken from the southern telecom site ("PMID701C_firmware_4.0.img") renamed to system.img. I've tried the above command several times to no avail. I even tried the same command on Shawn's custom ROMs with the message of

"[ 8633.567194] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[13649.541598] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[14501.816652] EXT4-fs (loop0): VFS: Can't find ext4 filesystem
[15156.269875] EXT4-fs (loop0): VFS: Can't find ext4 filesystem"

<sigh>......

[sabercatpuck]

a few things to check

i have not had much time to mess with this for awhile, but a few things you will need to do would be first to unpack the flashable image so you get all of the support files and image files out of it. the next thing is that the images inside still need to be extracted further because to save space the images are compressed into what is called a sparse image. you will need a program called simage2image

[900supersport]

Re: Custom ROM creation mentoring

Ah that makes sense. Was thinking you where working the same image you where using.

First things first then deal with the sparse images as mentioned above and let's see where we get.

[elektrik]

i have not had much time to mess with this for awhile, but a few things you will need to do would be first to unpack the flashable image so you get all of the support files and image files out of it. the next thing is that the images inside still need to be extracted further because to save space the images are compressed into what is called a sparse image. you will need a program called simage2image

Ah that makes sense. Was thinking you where working the same image you where using.

First things first then deal with the sparse images as mentioned above and let's see where we get.

@supersport-sorry, I really am a *noob* when it comes to extracting images :-(

Thanks Saber, SuperSport. I'll search for it now. I'll try to play with it for a while before I bother anyone

[900supersport]

Re: Custom ROM creation mentoring

I'm not at all familiar with Polaroid but have some experience cooking roms , hopefully between us we will get you moving.

[elektrik]

I'm not at all familiar with Polaroid but have some experience cooking roms , hopefully between us we will get you moving.

Woot! Progress! After struggling with XP mode in windows (unimg detects the VM!!!), I ran the unimg command found in the A10 flash kitchen and successfully got a dump of the flash. I renamed the .fex file to system.img and copied it to the appropriate directory. I ran the mount command and still had the same problem though! ARGH!!

[900supersport]

have you looked into simage2image? you may need to use this first.

[elektrik]

Woot! Progress! After struggling with XP mode in windows (unimg detects the VM!!!), I ran the unimg command found in the A10 flash kitchen and successfully got a dump of the flash. I renamed the .fex file to system.img and copied it to the appropriate directory. I ran the mount command and still had the same problem though! ARGH!!

UPDATE: I finally GOT IT!!!!! I had to run simg2img first to get the raw output and THEN I was able to mount it. I now see all the lovely files (including those nasty preinstalls :-))

[elektrik]

have you looked into simage2image? you may need to use this first.

Haha, you were reading my mind! I was typing that's what I had to do right as you were typing it!!

...and now I'm scratching my head saying.... "now what?!" LOL!

[900supersport]

Haha, you were reading my mind! I was typing that's what I had to do right as you were typing it!!

...and now I'm scratching my head saying.... "now what?!" LOL!

first things first make a backup copy

what type file system is it? cramfs, ext3, ext4?

[elektrik]

first things first make a backup copy

what type file system is it? cramfs, ext3, ext4?

Ya, no doubt! I do have a backup on my ironkey drive hehe.....

It's ext4