ClockworkMod Recovery [For Motorola Triumph]


Thread Status:
Not open for further replies.
  1. 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
    Code (Text):
    1.  
    2. major minor  #blocks  name
    3.  
    4.    7        1       4850 loop1
    5. 179        0    1912832 mmcblk0
    6. 179        1     102400 mmcblk0p1
    7. 179        2        500 mmcblk0p2
    8. 179        3       1500 mmcblk0p3
    9. 179        4          1 mmcblk0p4
    10. 179        5       8192 mmcblk0p5
    11. 179        6       8192 mmcblk0p6
    12. 179        7     253952 mmcblk0p7
    13. 179        8    1163264 mmcblk0p8
    14. 179        9      81920 mmcblk0p9
    15. 179       10      32768 mmcblk0p10
    16. 179       11     204800 mmcblk0p11
    17. 179       12       8192 mmcblk0p12
    18. 179       13       8192 mmcblk0p13
    19. 179       14       8192 mmcblk0p14
    20. 179       15       8192 mmcblk0p15
    21. 179       16       8192 mmcblk0p16
    22. 179       17       8192 mmcblk0p17
    23. 179       32    1955840 mmcblk1
    24. 179       33    1955775 mmcblk1p1
    25.  
    fdisk -l /dev/block/mmcblk0
    Code (Text):
    1.  
    2. Disk /dev/block/mmcblk0: 1958 MB, 1958739968 bytes
    3. 1 heads, 16 sectors/track, 239104 cylinders
    4. Units = cylinders of 16 * 512 = 8192 bytes
    5.  
    6.               Device Boot      Start         End      Blocks  Id System
    7. /dev/block/mmcblk0p1               1       12801      102400   c Win95 FAT32 (LBA)
    8. Partition 1 does not end on cylinder boundary
    9. /dev/block/mmcblk0p2   *       12801       12863         500  4d Unknown
    10. Partition 2 does not end on cylinder boundary
    11. /dev/block/mmcblk0p3           12863       13051        1500  46 Unknown
    12. Partition 3 does not end on cylinder boundary
    13. /dev/block/mmcblk0p4           13051      238592     1804335+  5 Extended
    14. Partition 4 does not end on cylinder boundary
    15. /dev/block/mmcblk0p5           13313       14336        8192  48 Unknown
    16. /dev/block/mmcblk0p6           14337       15360        8192  50 Unknown
    17. /dev/block/mmcblk0p7           15361       47104      253952  82 Linux swap
    18. /dev/block/mmcblk0p8           47105      192512     1163264  83 Linux
    19. /dev/block/mmcblk0p9          192513      202752       81920  6c Unknown
    20. /dev/block/mmcblk0p10         202753      206848       32768  6a Unknown
    21. /dev/block/mmcblk0p11         206849      232448      204800  6b Unknown
    22. /dev/block/mmcblk0p12         232449      233472        8192  7b Unknown
    23. /dev/block/mmcblk0p13         233473      234496        8192  7a Unknown
    24. /dev/block/mmcblk0p14         234497      235520        8192  78 Unknown
    25. /dev/block/mmcblk0p15         235521      236544        8192  79 Unknown
    26. /dev/block/mmcblk0p16         236545      237568        8192  7c Unknown
    27. /dev/block/mmcblk0p17         237569      238592        8192  7d Unknown
    28.  
    mount
    Code (Text):
    1.  
    2. rootfs / rootfs rw,relatime 0 0
    3. tmpfs /dev tmpfs rw,relatime,mode=755 0 0
    4. devpts /dev/pts devpts rw,relatime,mode=600 0 0
    5. proc /proc proc rw,relatime 0 0
    6. sysfs /sys sysfs rw,relatime 0 0
    7. /dev/block/mmcblk0p7 /system ext3 rw,relatime,data=ordered 0 0
    8. /dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
    9. /dev/block/mmcblk0p10 /hidden ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
    10. /dev/block/mmcblk0p9 /hidden/data ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
    11. /dev/block/mmcblk0p11 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
    12. none /acct cgroup rw,relatime,cpuacct 0 0
    13. tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
    14. none /dev/cpuctl cgroup rw,relatime,cpu 0 0
    15. debugfs /sys/kernel/debug debugfs rw,relatime 0 0
    16. /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
    17. /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
    18. tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
    19.  
    mmcblk0p1.img File
    mmcblk0p1.img

    mmcblk0p9.img File
    mmcblk0p9.img

    mmcblk0p10.img File
    mmcblk0p10.img
  2. isaacj87

    isaacj87 Well-Known Member

    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.
    ItsameScott, Gmash and apsterling like this.
  3. apsterling

    apsterling Well-Known Member

    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.
  4. isaacj87

    isaacj87 Well-Known Member

    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.
  5. apsterling

    apsterling Well-Known Member

    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
  6. isaacj87

    isaacj87 Well-Known Member

    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:

    HTML:
    1. 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.
  7. apsterling

    apsterling Well-Known Member

    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.
  8. isaacj87

    isaacj87 Well-Known Member

    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.
  9. 903Tex

    903Tex Well-Known Member

    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?
  10. apsterling

    apsterling Well-Known Member

    The boot loader is an open door.
    fireball9199 and 903Tex like this.
  11. 903Tex

    903Tex Well-Known Member

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

    apsterling Well-Known Member

    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"
  13. isaacj87

    isaacj87 Well-Known Member

  14. apsterling

    apsterling Well-Known Member

    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?
  15. lanceg

    lanceg Well-Known Member


    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.
  16. isaacj87

    isaacj87 Well-Known Member

    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:

    Code (Text):
    1. ./fastboot-mac devices
  17. apsterling

    apsterling Well-Known Member

    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.
  18. isaacj87

    isaacj87 Well-Known Member

    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. :mad: :)

    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. :p

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

    apsterling Well-Known Member

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

    isaacj87 Well-Known Member

    Can someone give me the output of:

    Code (Text):
    1. cat /proc/emmc
    Thanks.
  21. 903Tex

    903Tex Well-Known Member


    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!
  22. apsterling

    apsterling Well-Known Member

    I got a "no such file or directory"
  23. fireball9199

    fireball9199 Member

    Same, no such file or directory
  24. isaacj87

    isaacj87 Well-Known Member

    Do:

    Code (Text):
    1. cd /proc
    and then:

    Code (Text):
    1. ls -a
    And post everything that's within /proc.
  25. Here's what I get when I do ls -a in the /proc directory:
    Code (Text):
    1.  
    2. last_kmsg
    3. msm_v4l2
    4. last_alog_system
    5. last_alog_radio
    6. last_alog_main
    7. msm_pm_stats
    8. asound
    9. binder
    10. dfi_upgrade
    11. cbverify
    12. mtd
    13. uid_stat
    14. sysrq-trigger
    15. hdmi_extension_screen
    16. edid_modes
    17. panel_type
    18. partitions
    19. diskstats
    20. crypto
    21. yaffs
    22. mlog
    23. flog
    24. pmlog
    25. kpageflags
    26. kpagecount
    27. kmsg
    28. softirqs
    29. version
    30. uptime
    31. stat
    32. meminfo
    33. loadavg
    34. interrupts
    35. devices
    36. cpuinfo
    37. cmdline
    38. locks
    39. filesystems
    40. slabinfo
    41. vmallocinfo
    42. zoneinfo
    43. vmstat
    44. pagetypeinfo
    45. buddyinfo
    46. config.gz
    47. kallsyms
    48. modules
    49. timer_stats
    50. timer_list
    51. iomem
    52. ioports
    53. execdomains
    54. cpu
    55. scsi
    56. misc
    57. fb
    58. sensors
    59. poweroncause
    60. draminfo
    61. emmcinfo
    62. bandinfo
    63. baseband
    64. devmodel
    65. pms
    66. wakelocks
    67. irq
    68. cgroups
    69. sys
    70. bus
    71. tty
    72. driver
    73. fs
    74. sysvipc
    75. net
    76. mounts
    77. self
    78. 1
    79. 2
    80. 3
    81. 4
    82. 5
    83. 6
    84. 7
    85. 8
    86. 9
    87. 10
    88. 11
    89. 12
    90. 13
    91. 14
    92. 15
    93. 16
    94. 17
    95. 18
    96. 19
    97. 20
    98. 21
    99. 22
    100. 23
    101. 24
    102. 25
    103. 26
    104. 27
    105. 28
    106. 29
    107. 39
    108. 40
    109. 41
    110. 42
    111. 43
    112. 44
    113. 45
    114. 46
    115. 53
    116. 54
    117. 55
    118. 56
    119. 57
    120. 58
    121. 59
    122. 60
    123. 61
    124. 62
    125. 63
    126. 64
    127. 65
    128. 66
    129. 67
    130. 68
    131. 69
    132. 70
    133. 71
    134. 72
    135. 73
    136. 74
    137. 75
    138. 76
    139. 78
    140. 80
    141. 81
    142. 82
    143. 83
    144. 86
    145. 88
    146. 89
    147. 90
    148. 91
    149. 92
    150. 93
    151. 95
    152. 96
    153. 97
    154. 98
    155. 99
    156. 100
    157. 101
    158. 102
    159. 103
    160. 104
    161. 105
    162. 106
    163. 108
    164. 109
    165. 118
    166. 119
    167. 120
    168. 152
    169. 153
    170. 154
    171. 155
    172. 184
    173. 260
    174. 270
    175. 272
    176. 276
    177. 321
    178. 393
    179. 398
    180. 444
    181. 491
    182. 550
    183. 599
    184. 659
    185. 681
    186. 751
    187. 942
    188. 1054
    189. 1371
    190. 1501
    191. 2062
    192. 2165
    193. 2371
    194. 2572
    195. 3254
    196. 3267
    197. 3274
    198. 3278
    199. 3280
    200. 3328
    201. 3333
    202.  
Loading...
Thread Status:
Not open for further replies.

Share This Page