U8110 Android 2.1 ROM

[Guest BigBearMDC]

Another idea:

Flash Eclair, boot amon-ra with 2.6.29 kernel and remount the fs as rw with it.

Then replace build.prop and, voilá, root!

Theoratically at least, I don't think this will work though :P

[Guest BigBearMDC]

By the way, I think I now know why just flashing the eclair update.zip doesn't work:

The new bootloader searches for the boot.img header at the wrong memory address, and can't find it and then drops me to the recovery.

[Guest Spooke]

Another idea:

Flash Eclair, boot amon-ra with 2.6.29 kernel and remount the fs as rw with it.

Then replace build.prop and, voilá, root!

Theoratically at least, I don't think this will work though :D

Ahh I see, whats the current state of your phone? *Rooted??* Elcair 2.1, Amon_Ra recovery but the Touch screen doesnt work?

Well I say go for it aslong as you know what your doing, but I wouldnt want you to brick your phone :P

[Guest BigBearMDC]

Ahh I see, whats the current state of your phone? *Rooted??* Elcair 2.1, Amon_Ra recovery but the Touch screen doesnt work?

Well I say go for it aslong as you know what your doing, but I wouldnt want you to brick your phone :P

My current state is 'booting' :D

Just flashed the 1.7 U8230 MCR to be able to reflash Eclair.

Once I flashed eclair, I'll boot the amon-ra recovery with fastboot.

Then I want to replace the build.prop, located in /system, with a rooted one (ro.secure=0 etc.).

If I'm able to mount the fs with rw permissions, I could root it.

But I think that this won't be possible as the device locks the fs until the kernel is rooted?

I don't know I'll just try it...

[Guest Spooke]

My current state is 'booting' :P

Just flashed the 1.7 U8230 MCR to be able to reflash Eclair.

Once I flashed eclair, I'll boot the amon-ra recovery with fastboot.

Then I want to replace the build.prop, located in /system, with a rooted one (ro.secure=0 etc.).

If I'm able to mount the fs with rw permissions, I could root it.

But I think that this won't be possible as the device locks the fs until the kernel is rooted?

I don't know I'll just try it...

Well I hope it works for you :P :D

So when you get it rooted etc, it will be a simple case for us to just flash it? :P

[Guest BigBearMDC]

Well I hope it works for you :P :D

So when you get it rooted etc, it will be a simple case for us to just flash it? :P

I hope so, but I can't test it as I'm not able to return to Cupcake :P

[Guest Spooke]

I hope so, but I can't test it as I'm not able to return to Cupcake :D

So does that mean we also wouldn't be able to go back to cupcake?

Keep us updated with ur progress :P

[Guest BigBearMDC]

So does that mean we also wouldn't be able to go back to cupcake?

Keep us updated with ur progress :P

I don't know xD

[Guest BigBearMDC]

Okay I got root in amon-ra recovery, but I can't mount the system partition...

[Guest Spooke]

Okay I got root in amon-ra recovery, but I can't mount the system partition...

Well the first parts good I guess, I dont know what you could do except try to root again?

How do you know that it worked? :S

[Guest BigBearMDC]

Well the first parts good I guess, I dont know what you could do except try to root again?

How do you know that it worked? :S

I could only imagine to boot some kind of minimal linux environment, that gives me more options than the amon-ra recovery...

[Guest David Horvath]

If you could drop to shell in amon-ra recovery that would be a big help. Couldn't you connect through ADB shell somehow?

[Guest mr.a]

Okay I got root in amon-ra recovery, but I can't mount the system partition...

i don't know if this helps but i found this on the internet

Very often when you want to write files to a particular partition on ADP1, you will get a "Permission Denied" if the partition is mounted read-only.

To get around this, you need to mount the partition read-write. Typically this is done with /system partition


$ adb shell

$ su

$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system


(Replace /dev/block/mtdblock3 & /system with appropriate device path and mount point, as obtained from cat /proc/mounts)

good luck, anyway

[Guest Tom G]

Okay I got root in amon-ra recovery, but I can't mount the system partition...

What info can you get about the location of the system partition from /proc/mtd and dmesg (if you don't have busybox try /proc/kmsg instead of dmesg). I'm fairly sure the partition offsets are set by the bootloader, so I would have expected mounting /dev/block/mtdblock1 to work. What error do you get?

Below is from my 2.6.27 kernel based on the december update source showing offset of partitions.

# cat /proc/mtd

dev:	size   erasesize  name

mtd0: 00280000 00020000 "boot"

mtd1: 05500000 00020000 "system"

mtd2: 06940000 00020000 "userdata"

mtd3: 01400000 00020000 "cache"

mtd4: 00500000 00020000 "recovery"

mtd5: 00040000 00020000 "misc"


# dmesg

Linux version 2.6.27-perf (tom@ArchServer) (gcc version 4.3.1 (GCC) ) #8 PREEMPT Sun Apr 25 04:34:00 EST 2010

CPU: ARMv6-compatible processor [4117b362] revision 2 (ARMv6TEJ), cr=00c5387f

Machine: QCT SURF7201A Board

Partition (from atag) boot -- Offset:2600000 Size:280000

Partition (from atag) system -- Offset:2880000 Size:5500000

Partition (from atag) userdata -- Offset:7d80000 Size:6940000

Partition (from atag) cache -- Offset:e6c0000 Size:1400000

Partition (from atag) recovery -- Offset:fac0000 Size:500000

Partition (from atag) misc -- Offset:ffc0000 Size:40000

Edited May 8, 2010 by Tom G

[Guest eckengucker1]

The problem is with the internal partitions, not with the memory card. I was thinking about the same, but for that you would need a device powered up, without loading the OS and you would need direct (root) access to the partitions.

indeed my fault. thought a bit too simple XD

[Guest DanWilson]

| Lots of problems and |

| Lots of confusing messages |

Any luck yet BigBear?

[Guest dadme]

I understand now why you need 2 weeks for releasing :P .

You don't know how to root this rom.

[Guest mr.a]

I understand now why you need 2 weeks for releasing :P .

You don't know how to root this rom.

Well, Do you know...?

If you can help -> appreciated

but if you can't help, then don't comment like this

Edited May 8, 2010 by mr.a

[Guest Spooke]

I understand now why you need 2 weeks for releasing :D .

You don't know how to root this rom.

Uhh he does know how to root it, just hes running into problems :P

[Guest dadme]

Well, Do you know...?

If i had any chance to try....

[Guest David Horvath]

He must have been kidnapped by Huawei SWAT :P

[Guest eckengucker1]

or he simply sleeps or he commited suicide or he went out for buying a new fon XD

[Guest David Horvath]

or he simply sleeps or he commited suicide or he went out for buying a new fon XD

Du bist sehr positiv!

[Guest Bigsy]

Uhh he does know how to root it, just hes running into problems :P

But does he? I mean really know?

I'm sure BigBearMDC tries his best but enthusiasm seems to outweigh ability.. Just an observation but he seems to have ultimately failed at all the 'dev' projects hes attempted on this forum.

I don't understand why this hasn't been sent to one or two of the other trusted devs here who could root it and remove whatever watermarks are present.

Edited May 8, 2010 by Bigsy

[Guest DanWilson]

But does he? I mean really know?

I'm sure BigBearMDC tries his best but enthusiasm seems to outweigh ability.. Just an observation but he seems to have ultimately failed at all the 'dev' projects hes attempted on this forum.

I don't understand why this hasn't been sent to one or two of the other trusted devs here who could root it and remove whatever watermarks are present.

I dont think that this is the way to think of it.. Maybe he wants to prove himself, show you nonbelievers that he can, not that he'll give up. Hes running into problems, so give him a break.