CM10 Coby 9742

[vampirefo.]

Well if that script ran on your tablet, Your tablet will no longer run, so I guess you wouldn't be concerned about your system size, any longer.

sent from my kingSing T1 via taptalk

 

[iancer]

Im sure that would be the result.
I tried ooptimizing the .apk files in the CM zip posted, but I'm sure getting it on my tablet is easier said than done.
I'm unsure if even loading the firmware from the extSD would be reasonable.

 

[vampirefo.]

post output of

busybox df-h

 

[iancer]

Here is the output of the command. I have a nandroid backup of my stock firmware; using these 3 update zips along with the Mobiz rom gives me a perfectly working 9742-8 once everything is flashed. Even turning off the auto-rotation option give me a fully landscape-locked system.

vold_fstab_k
http://www.mediafire.com/download/sv5s53fxufv74ah/9742_vold_fstab_k.zip

bt_boot
http://www.mediafire.com/download/ao35s0eop883guo/9742_bt_boot.zip

9742_modules
http://www.mediafire.com/download/u7nagkaqw6vglbr/9742_modules.zip

Filesystem                Size      Used Available Use% Mounted on
tmpfs                   407.1M     44.0K    407.1M   0% /dev
tmpfs                   407.1M         0    407.1M   0% /mnt/asec
tmpfs                   407.1M         0    407.1M   0% /mnt/obb
/dev/block/nandd        252.0M    215.9M     36.1M  86% /system
/dev/block/nande          2.0G    518.8M      1.5G  26% /data
/dev/block/nandh        503.9M      8.4M    495.6M   2% /cache
/dev/block/vold/93:81
                          4.6G    243.8M      4.3G   5% /mnt/sdcard
/dev/block/vold/93:81
                          4.6G    243.8M      4.3G   5% /mnt/secure/asec

I can upload any stock img files if needed, I used the signed CWM after retrieving my dump from CobyADB.
Thanks.

 

[vampirefo.]

Here is the output of the command. I have a nandroid backup of my stock firmware; using these 3 update zips along with the Mobiz rom gives me a perfectly working 9742-8 once everything is flashed. Even turning off the auto-rotation option give me a fully landscape-locked system.

vold_fstab_k
http://www.mediafire.com/download/sv5s53fxufv74ah/9742_vold_fstab_k.zip

bt_boot
http://www.mediafire.com/download/ao35s0eop883guo/9742_bt_boot.zip

9742_modules
http://www.mediafire.com/download/u7nagkaqw6vglbr/9742_modules.zip

Filesystem                Size      Used Available Use% Mounted on
tmpfs                   407.1M     44.0K    407.1M   0% /dev
tmpfs                   407.1M         0    407.1M   0% /mnt/asec
tmpfs                   407.1M         0    407.1M   0% /mnt/obb
/dev/block/nandd        252.0M    215.9M     36.1M  86% /system
/dev/block/nande          2.0G    518.8M      1.5G  26% /data
/dev/block/nandh        503.9M      8.4M    495.6M   2% /cache
/dev/block/vold/93:81
                          4.6G    243.8M      4.3G   5% /mnt/sdcard
/dev/block/vold/93:81
                          4.6G    243.8M      4.3G   5% /mnt/secure/asec

I can upload any stock img files if needed, I used the signed CWM after retrieving my dump from CobyADB.
Thanks.

You see how big your cache is? Over 500MB, so use it for system.

You need to modify boot.img use cache partition for system and use system partition for cache.

sent from my kingSing T1 via taptalk

 

[iancer]

Would any of the (linux) tools be sufficient for the task...?

I have a modicum of expierience with the Cubieboard SoC. That was a Sunxi machine, and required similar steps to boot debian on it...

I'm sure I could edit the boot.img, swapping system for cache; that would negate the need to actually resize any partitions with the script I linked to earlier, correct?

I have uploaded my boot.img from the CobyADB. I'm actually assuming the boot.img I should edit would be the one included in the CM10 update zip. I hope that is the image I should edit, and not the one pertaining to the Mobiz rom. I value your time.

http://a.pomf.se/wmgnyv.zip

 

[vampirefo.]

Would any of the (linux) tools be sufficient for the task...?

I have a modicum of expierience with the Cubieboard SoC. That was a Sunxi machine, and required similar steps to boot debian on it...

I'm sure I could edit the boot.img, swapping system for cache; that would negate the need to actually resize any partitions with the script I linked to earlier, correct?

I have uploaded my boot.img from the CobyADB. I'm actually assuming the boot.img I should edit would be the one included in the CM10 update zip. I hope that is the image I should edit, and not the one pertaining to the Mobiz rom. I value your time.

http://a.pomf.se/wmgnyv.zip

You would edit the boot.img that goes along with the rom you are going to install, If installing CM10 you would edit that boot.img.

Also edit the install script in the ROM's zip to point to cache partition as system.

If you are going to use CWM after this type of install you need to edit it as well, if not it will think system is on system partition and will backup and restore as such.
You need to let CWM know you have made changes.

sent from my kingSing T1 via taptalk

 

[iancer]

You would edit the boot.img that goes along with the rom you are going to install, If installing CM10 you would edit that boot.img.

Also edit the install script in the ROM's zip to point to cache partition as system.

If you are going to use CWM after this type of install you need to edit it as well, if not it will think system is on system partition and will backup and restore as such.
You need to let CWM know you have made changes.

I am 100% up to the task, thx for the info!

Honestly, I am simply unsure of what exact file to edit:
init.rc, init.d, default.prop?
Then I'm sure after unpacking the boot.img, I could reproduce the modification with the signed CWM.img.

Just posting to express gratitude before I continue reading on the matter, and to give a heads up as to my actually level of comprehension of these procedures. I feel I am following you, while being mindful to take caution.

CM10 boot.img partition swap
ROM zip install script
CWM recovery.img /system modification

 

[iancer]

It seems like I should edit the updater-script inside
"META-INF\com\google\android\"
To replace instances of 'nandd' with 'nandh'.

I think after doing so, I would want to edit both CM10 boot.img, as well as CWM recovery.img; yet I am still unsure of what files I would exactly edit - possible each img files ramdisk contains etc/vold.fstab....?

 

[vampirefo.]

It seems like I should edit the updater-script inside
"META-INF\com\google\android\"
To replace instances of 'nandd' with 'nandh'.

I think after doing so, I would want to edit both CM10 boot.img, as well as CWM recovery.img; yet I am still unsure of what files I would exactly edit - possible each img files ramdisk contains etc/vold.fstab....?

boot.img edit init.sun4i.rc

rom edit updater-script

recovery.img edit recovery.fstab

 

[iancer]

The information was priceless, so far, I have only editied the ROM updater-script, replaceing the 2 instances of nandd with nandh.

My next query is: should I be editing /etc/recovery.fstab in the recovery InitRamFS image to adjust for my specific 9742-8, which has nandk as /sdcard as opposed to nandi. So I would also need to adjust that file accordingly, in conjunction with partiton swap, correct?
So this line would become edited to read:
"/emmc auto /dev/block/nandk /dev/block/nandk1"

It really seems like the only img extract/rebuild tools exist on Linux currently.

I have also attached my edited updater-script.

 

[iancer]

Here is the finished product:
http://www12.zippyshare.com/v/86892909/file.html

Included are the 4 files I edited, swapping nandd/h and nandi/k -
boot.img edit init.sun4i.rc
rom edit updater-script + vold.fstab
recovery.img edit recovery.fstab

After editing all of the files correctly and recompiling CWM, I used CobyADB to write the recovery.img after doing a wipe data/factory reset.

After my tablet rebooted I was greeted with a black screen, I have no response from 'adb devices' anymore, no response in the device manager, or on my linux machine.

I was never able to test my edited CM10 zip either.
Thank you for you advice and time.

 

[iancer]

I am almost positive I need a little help converting my extracted my zImage kernel from my stock bootloader.img.

I am trying to recover my tablet by creating a bootable SD card as instructed here:
http://linux-sunxi.org/CWM_on_a_SDCard

The same tools I used on the other .img files error when I try to use them to extract this image.
I used disk internals Linux Reader to extract the script.bin from the image.
I am still unsure how to convert the zImage into a U-Boot compatible uImage, though...


http://www.diskinternals.com/linux-reader/
Any assistance would be appreciated.

 

[iancer]

I recieved a pure whit screen after setting up the SD card properly....

I can see my device is in recovery mode when I use 'adb devices'.
I was able to push files to /dev/root/tmp. Chmod'ing the install-recovery.sh file, after properly edited, yields no errors.

Yet I am still unable to enter CWM after running the script again.

 

[vampirefo.]

Doesn't appear to me you are using your thinking cap. You do understand modifying the recovery and then not formatting system is well not smart, think.
Seeing your system in still on your system partition, which you should have moved to cache partition before flashing recovery, so now flash normal non modified recovery.

sent from my kingSing T1 via taptalk