Root ClockworkMod Recovery [For Motorola Triumph]

[danthemanohyea]

I realize that other people have provided you with the information and files you requested, but I figure it can't hurt to have more than one copy of it all.

I did all of them for the sake of consistency.

These were all done via terminal emulator on my phone, with superuser privileges, of course.

cat /proc/partitions

major minor  #blocks  name

   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    1955840 mmcblk1
179       33    1955775 mmcblk1p1

fdisk -l /dev/block/mmcblk0

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

mount

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

mmcblk0p1.img File
mmcblk0p1.img

mmcblk0p9.img File
mmcblk0p9.img

mmcblk0p10.img File
mmcblk0p10.img

 

[isaacj87]

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

Lol, well I found the answer myself with the first one (mmcblk0p1). See on the Ascend there were separate partitions designated for a purpose (e.g. root, recovery, system, etc.) However, this device is a non-MTD device. In fact, I opened up the dumped image of mmcblk0p1 and it contains: boot.img, recovery.img, splash.img and some other files I'm not familiar with. (Those were the files I were looking for that are less than 15 megs). TBH, this is all VERY new to me.

Long story, short:

• /dev/block/mmcblk0p1 - contains all the necessary items needed to boot the device. (boot.img, recovery.img, etc.)
• /dev/block/mmcblk0p9 - contains things related to Virgin stuff. It has the boot sounds, custom apks that Virgin installed by default, ringtones, etc.
• /dev/block/mmcblk0p10 - this contains an iso file to install USB drivers. It also contains some apn information not related Virgin Mobile, strangely enough.

Well, now I have recovery and boot images. I'll figure out how this all works. I'll ask around on XDA and Github and see what exactly needs to be done. If anyone would like to help me as I figure this out, you can find my new dev account @ Github: http://github.com/ikarosdev (I use my isaacj87 account for personal things now).

I'll make a new repo for the Triumph after class today.

 

[apsterling]

Lol, well I found the answer myself with the first one (mmcblk0p1).
Long story, short:

• /dev/block/mmcblk0p1 - contains all the necessary items needed to boot the device. (boot.img, recovery.img, etc.)
• /dev/block/mmcblk0p9 - contains things related to Virgin stuff. It has the boot sounds, custom apks that Virgin installed by default, ringtones, etc.
• /dev/block/mmcblk0p10 - this contains an iso file to install USB drivers. It also contains some apn information not related Virgin Mobile, strangely enough.

Well, now I have recovery and boot images. I'll figure out how this all works. I'll ask around on XDA and Github and see what exactly needs to be done. If anyone would like to help me as I figure this out, you can find my new dev account @ Github: http://github.com/ikarosdev (I use my isaacj87 account for personal things now).

I'll make a new repo for the Triumph after class today.

Gotcha- the mmcblk0p1 was mounting itself under OS X when I put the phone in bootloader, and the p10 always mounts itself as a CD with drivers which I really want to stop mounting when I have the phone in.

Good to know we've got something going though, and I'll be sure to follow this. Let me know if you need anything else off the phone.

 

[isaacj87]

Gotcha- the mmcblk0p1 was mounting itself under OS X when I put the phone in bootloader, and the p10 always mounts itself as a CD with drivers which I really want to stop mounting when I have the phone in.

Good to know we've got something going though, and I'll be sure to follow this. Let me know if you need anything else off the phone.

Yeah, I'm just realizing all of this... LOL. In fact, there's a user on HF that's already made these realizations. I apologize if I'm little behind the times. I don't have the phone so I'm trying to play catch up.

When you put the phone into bootloader mode, you have read/write access, right? Maybe I can build a recovery.img and you can just swap it out. Now that I've determined where /system, /data, and /cache are, I'll just set their FS types and mount locations in recovery.fstab.

 

[apsterling]

Yeah, I'm just realizing all of this... LOL. In fact, there's a user on HF that's already made these realizations. I apologize if I'm little behind the times. I don't have the phone so I'm trying to play catch up.

When you put the phone into bootloader mode, you have read/write access, right? Maybe I can build a recovery.img and you can just swap it out. Now that I've determined where /system, /data, and /cache are, I'll just set their FS types and mount locations in recovery.fstab.

I believe so, and then if it goes awry I can still replace it with a backup stock recovery.

EDIT, this is what OS X's Disk Utility pulls up when the phone is in Bootloader. I'm kinda afraid to mount any of these.

http://d.pr/VK1L

 

[isaacj87]

I believe so, and then if it goes awry I can still replace it with a backup stock recovery.

EDIT, this is what OS X's Disk Utility pulls up when the phone is in Bootloader. I'm kinda afraid to mount any of these.

Screen shot 2011-07-27 at 11:36:37.png

Here are the things I need to figure out, if you guys could research this for me, it'd help me out tremendously.

First, we've figured out that /dev/block/mmcblk0p1 contains the boot images. So, technically we could just:

mount -o rw, remount -t vfat /dev/block/mmcblk0p1 /boot

And that way we'll give read/write access to the partition, mount it to boot so we can look into and possibly just write a new recovery.img to replace the original one. However, my question is do we need to create a whole NEW image that replaces everything contained in /dev/block/mmcblk0p1? Or can we just replace the things that matter to us (boot.img and recovery.img).

Also, I need to know how to create a proper port of CWM for the Triumph. I've established where /system, /data and /cache are. That's not the issue I'm having. What concerns me is that the supposed "/boot" partition contains other items in there (recovery.img, emmcboot.mbn, splash.img, etc.) I'm used to seeing the boot partition only being boot.img (which basically contains the kernel and ramdisk). That's kind of what trips me up as I've never seen that before (except maybe on my Nook color). I'll need more information so that when I build CWM, it'll make proper nandroid backups and more importantly, it'll flash custom ROMs correctly.

 

[apsterling]

Here are the things I need to figure out, if you guys could research this for me, it'd help me out tremendously.

First, we've figured out that /dev/block/mmcblk0p1 contains the boot images. So, technically we could just:

mount -o rw, remount -t vfat /dev/block/mmcblk0p1 /boot

And that way we'll give read/write access to the partition, mount it to boot so we can look into and possibly just write a new recovery.img to replace the original one. However, my question is do we need to create a whole NEW image that replaces everything contained in /dev/block/mmcblk0p1? Or can we just replace the things that matter to us (boot.img and recovery.img).

Also, I need to know how to create a proper port of CWM for the Triumph. I've established where /system, /data and /cache are. That's not the issue I'm having. What concerns me is that the supposed "/boot" partition contains other items in there (recovery.img, emmcboot.mbn, splash.img, etc.) I'm used to seeing the boot partition only being boot.img (which basically contains the kernel and ramdisk). That's kind of what trips me up as I've never seen that before (except maybe on my Nook color). I'll need more information so that when I build CWM, it'll make proper nandroid backups and more importantly, it'll flash custom ROMs correctly.

I'm going to guess that we probably just need to replace boot.img/recovery.img, but I could be totally wrong and would say that it's best to get a real dev to answer that.

Isn't there some way to redirect the other parts to that boot partition?

It turns out I have true RW access to that when in download mode under OS X through Finder.

 

[isaacj87]

I'm going to guess that we probably just need to replace boot.img/recovery.img, but I could be totally wrong and would say that it's best to get a real dev to answer that.

Isn't there some way to redirect the other parts to that boot partition?

It turns out I have true RW access to that when in download mode under OS X through Finder.

Got it: Installing ClockworkMod on the Huawei U8800 / Ideos X5

That answers our question right there. I think I've figured out the situation with CWM as well: https://github.com/koush/android_bootable_recovery/blob/gingerbread/mmcutils/mmcutils.c

I think if I build CWM needing mmcutils, it'll handle all the stuff happening in /dev/block/mmcblk0p1. We might be seeing CWM (latest) on the Motorola Triumph soon.

 

[903Tex]

So is the bootloader seems to be not encrypted??? Also if you replace the recovery.img and boot.img with cwm recovery.img will the phone just bootloop if its not accepted by the kernal??? Or will it just not respond at all?

 

[apsterling]

So is the bootloader seems to be not encrypted??? Also if you replace the recovery.img and boot.img with cwm recovery.img will the phone just bootloop if its not accepted by the kernal??? Or will it just not respond at all?

The boot loader is an open door.

 

[903Tex]

That's good to know! Think im going to make my purchase for this phone later this week!

 

[apsterling]

It'll be probably a few days until we have Clockwork but even then all we'll be able to do is stock and deodexed roms until we get the Kernel Source from Motorola which has no ETA aside from "soon"

 

[isaacj87]

So is the bootloader seems to be not encrypted??? Also if you replace the recovery.img and boot.img with cwm recovery.img will the phone just bootloop if its not accepted by the kernal??? Or will it just not respond at all?

One way to determine this is by checking it with fastboot. [GUIDE] Boot into fastboot - find out if bootloader is locked - xda-developers

Has anyone even tried doing this yet?

 

[apsterling]

Somehow the android sdk under OS X is lacking Fastboot, or I'm missing pieces.

It's not seeing my device under fast boot, but does it matter if we can still get to the boot loader and that partition?

 

[lanceg]

It'll be probably a few days until we have Clockwork but even then all we'll be able to do is stock and deodexed roms until we get the Kernel Source from Motorola which has no ETA aside from "soon"

Well, with no recovery and source code, we got nothing

With recovery and no source, we possibly have something if source comes out

I hope it's soon, I would kill for a Sense ROM on this device.

 

[isaacj87]

Well, with no recovery and source code, we got nothing

With recovery and no source, we possibly have something if source comes out

I hope it's soon, I would kill for a Sense ROM on this device.

The kernel source isn't completely necessary right now. It would be nice to have (for overclocking purposes), but technically you can build a CM7 port with the stock kernel I stripped out of the boot.img file. You're right though, this device needs CWM in order to do anything.

Well, I'm pulling the source as we speak. (This will take an hour or two). I'll try and have a testable recovery built tonight. Maybe some brave souls can test it for me.

@apsterling:

Download the OS X fastboot binary here: HTC - Developer Center

Go to where you downloaded and extracted the zip. Make sure the phone is in bootloader mode and run:

./fastboot-mac devices

 

[apsterling]

The kernel source isn't completely necessary right now. It would be nice to have (for overclocking purposes), but technically you can build a CM7 port with the stock kernel I stripped out of the boot.img file. You're right though, this device needs CWM in order to do anything.

Well, I'm pulling the source as we speak. (This will take an hour or two). I'll try and have a testable recovery built tonight. Maybe some brave souls can test it for me.

@apsterling:

Download the OS X fastboot binary here: HTC - Developer Center

Go to where you downloaded and extracted the zip. Make sure the phone is in bootloader mode and run:

./fastboot-mac devices

Done, and the device isn't showing up at all. Not sure how (or why) it'd be locked if when I boot in to bootloader I have full RW access on the computer to the partition.

 

[isaacj87]

Done, and the device isn't showing up at all. Not sure how (or why) it'd be locked if when I boot in to bootloader I have full RW access on the computer to the partition.

I'm inclined to agree with you, but I think the problem with locked/signed/encrypted whatever bootloaders is that when something "foreign" is trying to get passed through, it won't allow it. It doesn't seem like any of the other FB400 variants are locked in any way.

Android development is pretty frustrating. For example, I'm writing a new program in Python/Qt4. If I need to know PtQt4 specifics, I can just read through the documentation and find my answer. Android isn't like that. Just a whole bunch of scattered findings all over the Internet. I can't find a real answer on what exactly a locked bootloader is, let alone what they look like. I'll stop foaming at the mouth now.

I'm pretty sure this will work. Let's just keep our fingers crossed. Hell, if it does work, I guess that means I'll have to buy a Triumph and start making ROMs.

EDIT: BTW, why isn't this thread in the "All things root" section?

 

[apsterling]

I'm inclined to agree with you, but I think the problem with locked/signed/encrypted whatever bootloaders is that when something "foreign" is trying to get passed through, it won't allow it. It doesn't seem like any of the other FB400 variants are locked in any way.

Android development is pretty frustrating. For example, I'm writing a new program in Python/Qt4. If I need to know PtQt4 specifics, I can just read through the documentation and find my answer. Android isn't like that. Just a whole bunch of scattered findings all over the Internet. I can't find a real answer on what exactly a locked bootloader is, let alone what they look like. I'll stop foaming at the mouth now.

I'm pretty sure this will work. Let's just keep our fingers crossed. Hell, if it does work, I guess that means I'll have to buy a Triumph and start making ROMs.

EDIT: BTW, why isn't this thread in the "All things root" section?

Hopefully it does, and i'll definitely be sure to try it once you have a test out.

 

[isaacj87]

Can someone give me the output of:

cat /proc/emmc

Thanks.

 

[903Tex]

EDIT: BTW, why isn't this thread in the "All things root" section?

Well i made this thread to let others know i made a post on xda to hopefully somebody can make us a custom recovery. To let people post and show interest to a dev and hopefully he will try to do it. Well you came along lol! and pretty much went to a root section thread now lol!

 

[apsterling]

I got a "no such file or directory"

 

[fireball9199]

Same, no such file or directory

 

[isaacj87]

I got a "no such file or directory"

Do:

cd /proc

and then:

ls -a

And post everything that's within /proc.

 

[danthemanohyea]

Here's what I get when I do ls -a in the /proc directory:

last_kmsg
msm_v4l2
last_alog_system
last_alog_radio
last_alog_main
msm_pm_stats
asound
binder
dfi_upgrade
cbverify
mtd
uid_stat
sysrq-trigger
hdmi_extension_screen
edid_modes
panel_type
partitions
diskstats
crypto
yaffs
mlog
flog
pmlog
kpageflags
kpagecount
kmsg
softirqs
version
uptime
stat
meminfo
loadavg
interrupts
devices
cpuinfo
cmdline
locks
filesystems
slabinfo
vmallocinfo
zoneinfo
vmstat
pagetypeinfo
buddyinfo
config.gz
kallsyms
modules
timer_stats
timer_list
iomem
ioports
execdomains
cpu
scsi
misc
fb
sensors
poweroncause
draminfo
emmcinfo
bandinfo
baseband
devmodel
pms
wakelocks
irq
cgroups
sys
bus
tty
driver
fs
sysvipc
net
mounts
self
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
39
40
41
42
43
44
45
46
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
78
80
81
82
83
86
88
89
90
91
92
93
95
96
97
98
99
100
101
102
103
104
105
106
108
109
118
119
120
152
153
154
155
184
260
270
272
276
321
393
398
444
491
550
599
659
681
751
942
1054
1371
1501
2062
2165
2371
2572
3254
3267
3274
3278
3280
3328
3333