Cube U9 GT2 And Compatible ICS Finless ROM 1.4

[JDfense]

Left the boot loader out on purpose for the moment, it should be same as your ROM.

So did the it load to recovery then fail on the reboot?

Do you know if it completed the load of boot.img then failed on system.img?

Yes it load into recovery and in the reboot it fail (no loop I would say, hung up) with the one line in logcat.

No, I don't think so, it freezes on the first moage logo.

JDfense

[900supersport]

Thanks. Either my system or Bobs recovery are not working with moage.

Can you flash just your working ext4 system.img and see if it will then boot?

Thanks

[JDfense]

It is the same result (logcat) with my working ext4 system.

It is your boot.img and/or the finless recovery.
JDfense

[900supersport]

I don't think I have changed boot so can you do a full flash with your recovery, my boot and your system.img

If that fails lets check the flash tool so flash using my flash tool your kernel,recovery,boot,misc and system.

Thanks for all this testing

[JDfense]

I don't think I have changed boot so can you do a full flash with your recovery, my boot and your system.img

If that fails lets check the flash tool so flash using my flash tool your kernel,recovery,boot,misc and system.

Thanks for all this testing

Now we have a full booting rom ext4 system ro with my system and my recovery.

Btw I have uses your nice flash tool the whole test so far.
JDfense

[900supersport]

so with my system.img it didn't work?

I find that flash tool great for trying different combinations of images :-)

[JDfense]

so with my system.img it didn't work?

I find that flash tool great for trying different combinations of images :-)

For shure bobs recovery don't like this jellybean, but have not tried your system with my recovery.
Wait, I try this last choice for your system.

Hey, you have my system in the your rom?
Is this an ingelligence test for me?

[900supersport]

For shure bobs recovery don't like this jellybean, but have not tried your system with my recovery.
Wait, I try this last choice for your system.

Hey, you have my system in the your rom?
Is this an ingelligence test for me?

Sorry didn't notice this post. I think I said earlier that system.img was your system.img but I have ensured it is a full ext4 system.

so did it boot with this system.img

I've created a couple more boot.img and system.img files for us to try

[900supersport]

OK

here's a couple of boot images, one that should mount system rw and one that will add in init.d support (this will need to a new system image

ROM> boot images

and here's the system image with init.d support

ROM> system image with init.d

first try the rw boot.image and see if it boots. If the tab boots then try the system image with init.d support. Again if the tab boots then try the boot.img with init.d support.

let me know how these go.

Thanks

[JDfense]

Okay then, lets go with the boot.img

[900supersport]

just in case you missed it we posted at the same time. I've posted the links for boot and system images

[JDfense]

I start with my ext4 system ro ROM as base. Then put in your boot rw in...etc.
For shure the ICS recovery from bob finless does not work, I believe.
I'm not shure, if my the cwm ext4 5.5.04 the problem for system rw could be. My friend stevemp from xda told me that we need a cwm created for jellybean too, not for ics, but it worked so far fine for system ro jellybean, with only one issue: You must after the first boot format internal sd, but that issue has oma7144 with his touch cwm too. So I let my cwm in for the first round.
JDfense

[900supersport]

yes it seems quite common to need to format sdcard.

did you mount system rw using rootexplorer or esfileexplorer with my first system image?

[JDfense]

I use es explorer, the root explorer in my system is in parts chinese from moage.

I have the first result. Your bootrw boots full, but in system ro. Look

u0_a48@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 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 /[COLOR=#0000cd][B]system ext4 ro[/B][/COLOR],noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/mtdblock6 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/mtdblock5 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /mnt/external_sd vfat  rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro  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_utime=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_utime=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
u0_a48@android:/ $

So what is next?

[900supersport]

not certain if you have tried my boot image for rw. for the we want

• kernel
• your recovery
• my misc
• my boot with rw
• my system.img

I need to know

• does this boot?
• can you use rootexplorer or esfileexplorer to mount system rw?