Root ClockworkMod Recovery [For Motorola Triumph]

[903Tex]

Made a thread on xda to see if we can get a port over for this recovery!!!

The more comments we add to this thread the better it looks for somebody to be interested!!! Making other threads on xda has lead to three guys willing to make roms for the triumph!

ClockworkMod Recovery [For Motorola Triumph] - xda-developers

 

[isaacj87]

Technically (the keyword here), this shouldn't be difficult to do. In fact, you don't even need a kernel or ROM source to port CWM to a new device. Unless there's something radically different with the MT, porting CWM would be as simple as:

1) Getting a dump of original boot.img.
2) Pulling CM7 sources. Clockwork source is found within Cyanogenmod's sources.
3) Setting the simple, but appropriate, device configs and building the recovery image.

When I ported CWM to the Ascend, I used these very instructions: My Brain Hurts: Porting Clockwork Recovery to New Devices

I could help out with doing this. I'm very hesitant about plunking down $300 bucks for this phone (it seems to have a lot of problems), but I'd more than willing to pull the CM sources and help build a recovery image for the MT. I would need the following items:

1) A clean dump of the boot partition. (Original boot.img)
2) The output of:

cat /proc/mtd

This is necessary for BoardConfig.mk.

If someone is willing to provide me those 2 items, I believe I can do it. You'll need some knowledge of adb and related tools. Like I said, I followed the directions I linked above, so if you want to take it upon yourself, that's how I ported CWM.

 

[903Tex]

I knew you woUld be coming on this thread!!! i don't have the device yet, mainly seeing where the development will come on this phone or not. No offense but tmobile unlimited everything for 60 and a g2x is looking really tempting!!! But im trying to get the ball going on this phone cause it does have alot of potential but it being a prepaid phone hurts it so much.

Heck even the mt4gslide has a spot on xda and the phone isn't even out yet!

 

[knightshade]

Hmm - if I can find some down time will need to step through that guide.

Haven't played on the development side of android, but I'm pretty comfortable with linux and java development....

How hard can it be to follow a tutorial?

 

[jdaman5518]

I will get you the things requested tomorrow night.

 

[apsterling]

I would need the following items:

1) A clean dump of the boot partition. (Original boot.img)
2) The output of:

cat /proc/mtd

I'm not 100% sure how to get the other part as I'm kinda new to this, but here's the boot.img. I was able to access that by putting the phone into bootloader mode, which mounted a volume in OS X.

 

[isaacj87]

I'm not 100% sure how to get the other part as I'm kinda new to this, but here's the boot.img. I was able to access that by putting the phone into bootloader mode, which mounted a volume in OS X.

Cool, thanks. I'll go ahead and pull the sources. I should of clarified what to do with:

cat /proc/mtd

1) Install ADB/Android SDK on your operating system (more info here: Android SDK | Android Developers)
2) Drop into shell mode on the phone and run the previously stated command.

It will produce an output that states the partition setup and size of each.

OR

1) Install a terminal emulator app from the market.
2) Run the terminal app and use type this command:

cat /proc/mtd > /sdcard/mtd_output.txt

This will generate a file called "mtd_output.txt" that contains the information I'm looking for. It will be dumped in the sdcard. NOTE: I'm guessing that's the location path for the sdcard. Make sure my assumption is correct!

 

[foobarX]

On my rooted MT I tried to do the:
cat /proc/mtd > /sdcard/mtd_output.txt
And got:
dev: size erasesize name


So I checked, and mtd is a 0 length file (permissions 444)

I'm a software guy, but not for linux, let me know what else to try and I can do it later tonight...

 

[isaacj87]

On my rooted MT I tried to do the:
cat /proc/mtd > /sdcard/mtd_output.txt
And got:
dev: size erasesize name


So I checked, and mtd is a 0 length file (permissions 444)

I'm a software guy, but not for linux, let me know what else to try and I can do it later tonight...

That's strange. Why zero-length? Do you have superuser permissions within the term app program? Run:

su

Then, the "$" symbol should change to "#"

After that, just run:

cat /proc/mtd

Does that produce anything? If not, what does this produce:

cat /proc/partitions

EDIT: I forgot that this phone is one of the FB400 variants (U9000, Mi410, etc.). I'm going to look around and see what I can come up with. Hopefully there's a kind dev who put his sources up that I can base something off of.

 

[Liquidplacidit]

Cat partitions produces this.

cat /proc/partitions
major minor #blocks name

7 0 13545 loop0
7 1 4850 loop1
179 0 1912832 mmcblk0
179 1 102400 mmcblk0p1
179 2 500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 253952 mmcblk0p7
179 8 1163264 mmcblk0p8
179 9 81920 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 204800 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 32 7761920 mmcblk1
179 33 6761718 mmcblk1p1
179 34 1000201 mmcblk1p2
254 0 13545 dm-0
#

 

[foobarX]

Mine is a little different (maybe because I have a 16GB micro-sd in mine?):

major minor #blocks name

7 0 14585 loop0
7 1 4850 loop1
179 0 1912832 mmcblk0
179 1 102400 mmcblk0p1
179 2 500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 253952 mmcblk0p7
179 8 1163264 mmcblk0p8
179 9 81920 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 204800 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 32 15558144 mmcblk1
179 33 15554048 mmcblk1p1
254 0 14584 dm-0


btw,
cat /proc/mtd
was no different for me after the su

 

[isaacj87]

major minor #blocks name

7 0 14585 loop0
7 1 4850 loop1

179 0 1912832 mmcblk0
179 1 102400 mmcblk0p1 <---- boot?

179 2 500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6

179 7 253952 mmcblk0p7 <---- system?
179 8 1163264 mmcblk0p8 <----- userdata?
179 9 81920 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 204800 mmcblk0p11 <----- cache

179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17

179 32 15558144 mmcblk1 <----- sdcard will vary based
179 33 15554048 mmcblk1p1 mini-sd size.
254 0 14584 dm-0

Yeah, this is going to be trickier than I thought. I've highlighted partitions of interest. I'd like to know where the recovery partition is.

If someone could post the output of this, please:

fdisk -l /dev/block/mmcblk0

and

mount

 

[foobarX]

Will try this in a few minutes - for some reason I have a busybox without fdisk

Update - I'm kind of paranoid about letting busybox installer update me since it can bootloop me and there are no rescue options. Looking for other ways to get fdisk working...

 

[foobarX]

Here's the mount output:

rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,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
/dev/block/mmcblk0p7 /system ext3 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p10 /hidden ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p9 /hidden/data ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p11 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,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/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,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
/dev/block/dm-0 /mnt/asec/com.mobilicos.howtodrawcartoons-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

 

[foobarX]

Maybe someone should contact this Free Radical guy...

CSL Spice MI410/Huawei Ideos X6/Wellcom A99/Cherry MagnumHD/Moto TRIUMPH/Olive VS2300 - Page 4

 

[Gmash]

See if this is useful:

Mi410_v3.18D_kernel_source_2.6.32.9.7z

 

[apsterling]

rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,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
/dev/block/mmcblk0p7 /system ext3 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p10 /hidden ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p9 /hidden/data ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p11 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,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/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,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
/dev/block/dm-0 /mnt/asec/com.canadadroid.penguinskiing-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/hu.butcher.nyanCat-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$

I got a permission denied error trying to run fdisk as superuser though

 

[isaacj87]

Here's the mount output:

rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,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
/dev/block/mmcblk0p7 /system ext3 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p10 /hidden ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p9 /hidden/data ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p11 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,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/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,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
/dev/block/dm-0 /mnt/asec/com.mobilicos.howtodrawcartoons-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

Thanks for all the responses guys.

I found the same thread and I tried to find something for both dhaway & tj_style, but couldn't. I think tj_style has a Github and I looked through it to see if he put anything related to these FB400 variants, but I didn't find anything. I have my own Github, so I'll send him a message today.

I still would like to see the fdisk output. @apsterling, I can see that when the command dropped back to prompt, it shows a '$' symbol. If you were running as a superuser within the terminal, it would be this '#'.

Did you run 'su' first? You guys are all rooted, right?

 

[apsterling]

Thanks for all the responses guys.

I found the same thread and I tried to find something for both dhaway & tj_style, but couldn't. I think tj_style has a Github and I looked through it to see if he put anything related to these FB400 variants, but I didn't find anything. I have my own Github, so I'll send him a message today.

I still would like to see the fdisk output. @apsterling, I can see that when the command dropped back to prompt, it shows a '$' symbol. If you were running as a superuser within the terminal, it would be this '#'.

Did you run 'su' first? You guys are all rooted, right?

Alright, it looks like my busybox has no fdisk support.

EDIT: Scratch that, I don't even have busybox. Fixing that right now.

 

[apsterling]

And here's the fdisk. Turns out I had no busybox installed.

Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
1 heads, 16 sectors/track, 239104 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

              Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk0p1               1       12801      102400   c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2   *       12801       12863         500  4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3           12863       13051        1500  46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4           13051      238592     1804335+  5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5           13313       14336        8192  48 Unknown
/dev/block/mmcblk0p6           14337       15360        8192  50 Unknown
/dev/block/mmcblk0p7           15361       47104      253952  82 Linux swap
/dev/block/mmcblk0p8           47105      192512     1163264  83 Linux
/dev/block/mmcblk0p9          192513      202752       81920  6c Unknown
/dev/block/mmcblk0p10         202753      206848       32768  6a Unknown
/dev/block/mmcblk0p11         206849      232448      204800  6b Unknown
/dev/block/mmcblk0p12         232449      233472        8192  7b Unknown
/dev/block/mmcblk0p13         233473      234496        8192  7a Unknown
/dev/block/mmcblk0p14         234497      235520        8192  78 Unknown
/dev/block/mmcblk0p15         235521      236544        8192  79 Unknown
/dev/block/mmcblk0p16         236545      237568        8192  7c Unknown
/dev/block/mmcblk0p17         237569      238592        8192  7d Unknown

 

[isaacj87]

And here's the fdisk. Turns out I had no busybox installed.

Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
1 heads, 16 sectors/track, 239104 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

              Device Boot      Start         End      Blocks  Id System
/dev/block/mmcblk0p1               1       12801      102400   c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2   *       12801       12863         500  4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3           12863       13051        1500  46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4           13051      238592     1804335+  5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5           13313       14336        8192  48 Unknown
/dev/block/mmcblk0p6           14337       15360        8192  50 Unknown
/dev/block/mmcblk0p7           15361       47104      253952  82 Linux swap
/dev/block/mmcblk0p8           47105      192512     1163264  83 Linux
/dev/block/mmcblk0p9          192513      202752       81920  6c Unknown
/dev/block/mmcblk0p10         202753      206848       32768  6a Unknown
/dev/block/mmcblk0p11         206849      232448      204800  6b Unknown
/dev/block/mmcblk0p12         232449      233472        8192  7b Unknown
/dev/block/mmcblk0p13         233473      234496        8192  7a Unknown
/dev/block/mmcblk0p14         234497      235520        8192  78 Unknown
/dev/block/mmcblk0p15         235521      236544        8192  79 Unknown
/dev/block/mmcblk0p16         236545      237568        8192  7c Unknown
/dev/block/mmcblk0p17         237569      238592        8192  7d Unknown

Okay, thanks. I'll need dumps of some of the partitions.

In particular, I'd like to look at mmcblk0p1, mmcblk0p9, mmcblk0p10.

Run these commands, please:

dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img

dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9.img

dd if=/dev/block/mmcblk0p10 of=/sdcard/mmcblk0p10.img

NOTE: If you didn't already know, 'dd' is a very powerful tool. Be careful with it.

You'll get 3 dumped images in the sdcard. If you could upload those somewhere for me, I'd appreciate it.

 

[apsterling]

Okay, thanks. I'll need dumps of some of the partitions.

In particular, I'd like to look at mmcblk0p1, mmcblk0p9, mmcblk0p10.

Run these commands, please:

dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img

dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9.img

dd if=/dev/block/mmcblk0p10 of=/sdcard/mmcblk0p10.img

NOTE: If you didn't already know, 'dd' is a very powerful tool. Be careful with it.

You'll get 3 dumped images in the sdcard. If you could upload those somewhere for me, I'd appreciate it.

The files are uploading at the moment, I should have em on here in 10-15 minutes. Thanks again for getting this all started for us!

 

[isaacj87]

The files are uploading at the moment, I should have em on here in 10-15 minutes. Thanks again for getting this all started for us!

No problem. I like doing all this kinda stuff. If the phone wasn't having so many issues, I would of picked one up myself. (I might to do it anyways. )

Are the images big? I was expecting them to be less than 15 megs?

 

[fireball9199]

here is the first one

http://dl.dropbox.com/u/11779080/triumph img/mmcblk0p1.img
edit:
second

http://dl.dropbox.com/u/11779080/triumph img/mmcblk0p9.img

 

[apsterling]

No problem. I like doing all this kinda stuff. If the phone wasn't having so many issues, I would of picked one up myself. (I might to do it anyways. )

Are the images big? I was expecting them to be less than 15 megs?

p1 is 104.9mb
p9 is 83.9mb
p10 is 33.6mb

A littttle more than 15mb. So I guess it'll be interesting to se exactly what's in there for you.

Download multiple files from Sendspace.com - send big files the easy way