• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ClockworkMod Recovery [For Motorola Triumph]

Status
Not open for further replies.
Edit: danthemanohyea beat me to it. lol

This is what I got.

Code: 
$ export PATH=/data/local/bin:$PATH
$su
#cd /proc
# ls -a
last_kmsg
msm_v4l2
last_alog_system
last_alog_events
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
77
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
159
160
161
162
214
293
298
302
318
320
335
375
378
382
438
514
778
837
1544
1933
2785
2795
2796
2797
2798
2805
2806
2813
2821
2862
2884
2913
2922
2930
2948
2970
2998
3010
3042
3064
3093
3101
3110
3123
3131
3135
3147
#
 
danthemanohyea said:
Part of me says to just sit back and let someone else post all this stuff, but I'm quite eager to get clockwork recovery on this phone!
Click to expand...

same lol


cat /proc/mounts
Code: 
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

cat /proc/emmcinfo
Code: 
SanDisk_2G
 
903Tex said:
How to flash;

Boot phone into bootloader mode (Hold volume down when powering on, or adb shell reboot bootloader)
run from cmd/terminal "fastboot flash recovery adb_recovery.img"
Click to expand...

No, I wouldn't do that. A) There's a possibility you might over-write something important and B) If it does write correctly, you'll flash a broken recovery image and delete the original.

I have a new version if testers want to try it: recovery.img

The way I recommend putting the new recovery on is:

1) Put the phone in BOOTLOADER mode
2) Plug the phone in your computer and a drive will show up
3) The drive contains files like boot.img, recovery.img, splash.img, etc. Go ahead and copy the ORIGINAL recovery.img and put it somewhere safe on your computer.
4) Download the test CWM recovery image I made and over-write the one on the drive. Make sure it wrote correctly.
5) Pull the battery and try booting into RECOVERY mode.

*DO THIS AT YOUR OWN RISK! I DON'T HAVE THE PHONE AND I'M ONLY WORKING OFF OF INFORMATION OTHERS HAVE GIVEN ME!*
 
isaacj87 said:
No, I wouldn't do that. A) There's a possibility you might over-write something important and B) If it does write correctly, you'll flash a broken recovery image and delete the original.

I have a new version if testers want to try it: recovery.img

The way I recommend putting the new recovery on is:

1) Put the phone in BOOTLOADER mode
2) Plug the phone in your computer and a drive will show up
3) The drive contains files like boot.img, recovery.img, splash.img, etc. Go ahead and copy the ORIGINAL recovery.img and put it somewhere safe on your computer.
4) Download the test CWM recovery image I made and over-write the one on the drive. Make sure it wrote correctly.
5) Pull the battery and try booting into RECOVERY mode.

*DO THIS AT YOUR OWN RISK! I DON'T HAVE THE PHONE AND I'M ONLY WORKING OFF OF INFORMATION OTHERS HAVE GIVEN ME!*
Click to expand...

Well as I bootlooped my phone I decided to give that .img a try, when i turn it on with vol dn and up plus power (normally how to get to the recovery) instead of vibrating and then booting it gets stuck vibrating forever and the screen never comes on.

and also here is the stock recovery.img if anyone needs it recovery.img
 
isaacj87 said:
No, I wouldn't do that. A) There's a possibility you might over-write something important and B) If it does write correctly, you'll flash a broken recovery image and delete the original.

I have a new version if testers want to try it: recovery.img

The way I recommend putting the new recovery on is:

1) Put the phone in BOOTLOADER mode
2) Plug the phone in your computer and a drive will show up
3) The drive contains files like boot.img, recovery.img, splash.img, etc. Go ahead and copy the ORIGINAL recovery.img and put it somewhere safe on your computer.
4) Download the test CWM recovery image I made and over-write the one on the drive. Make sure it wrote correctly.
5) Pull the battery and try booting into RECOVERY mode.

*DO THIS AT YOUR OWN RISK! I DON'T HAVE THE PHONE AND I'M ONLY WORKING OFF OF INFORMATION OTHERS HAVE GIVEN ME!*
Click to expand...

Still vibrates continuously.

Just in case I'm not available to test it.

Bootloader mode:
Volume Down and Power.

Recovery mode:
Volume Up and down and Power.
 
isaac13 said:
Still vibrates continuously.

Just in case I'm not available to test it.

Bootloader mode:
Volume Down and Power.

Recovery mode:
Volume Up and down and Power.
Click to expand...

Damn, well back to drawing board again. I'm not sure what's so special about the Triumph. The other 2 phones I've built CWM for used the barest, generic configs and still worked. I'm using the stock kernel (I've tried both boot and recovery image kernels) and the init.rc from the original recovery image.
 
isaac13 said:
Another dev is also interested in the phone.

Maybe he can help out as well.

Possible root Ideas that MAY work..
Click to expand...

Uh, no offense but it's pretty obvious that guy doesn't know WTF he's talking about. Those are all ideas on how to root a phone that has already been rooted. He also said the following about whether or not the Triumph had a locked or encrypted bootloader: "But ALL android phones have a boot loader ( how do you think they boot? )"

:rolleyes:
 
Bobomo said:
Uh, no offense but it's pretty obvious that guy doesn't know WTF he's talking about. Those are all ideas on how to root a phone that has already been rooted. He also said the following about whether or not the Triumph had a locked or encrypted bootloader: "But ALL android phones have a boot loader ( how do you think they boot? )"

:rolleyes:
Click to expand...

You're right but any help we can get is welcomed. If he is interested he can learn and sometime in the future he might know what he is talking about.
 
@isaacj87 I hope you are using all the released source code/ roms available from the various X6 variants. there are gingerbread roms available for them as well as kernel source code and also i believe someone was able to port CWM to one of them.
And yes this phone is unlike other Moto phones as Moto has done nearly no work. It's just a Foxconn ODM with some branding and minor tweaks (button arrangement). So you will see it has much more in common with those X6 type of phones.

And thanks for taking the time and putting in the effort really appreciate it!
 
tgpraveen said:
@isaacj87 I hope you are using all the released source code/ roms available from the various X6 variants. there are gingerbread roms available for them as well as kernel source code and also i believe someone was able to port CWM to one of them.
And yes this phone is unlike other Moto phones as Moto has done nearly no work. It's just a Foxconn ODM with some branding and minor tweaks (button arrangement). So you will see it has much more in common with those X6 type of phones.

And thanks for taking the time and putting in the effort really appreciate it!
Click to expand...


You cant use sources from another phone, especially one thats not even the same as the triumph. We have to use the sources from motorola and they havent release those yet. When i had my epic 4g these are the status of roms on this phone as of TODAY:

Epic 4g- BETA cm7, BETA miui, and no Offical gingerbread release

Now samsung captivate from the galaxy s line as well

Fully Working CM7(RC-2) Fully working froyo and GB build on MIUI, and Offical release of Gingerbread 2.3.3 running touchwiz.
 
isaacj87 said:
No, I wouldn't do that. A) There's a possibility you might over-write something important and B) If it does write correctly, you'll flash a broken recovery image and delete the original.

I have a new version if testers want to try it: recovery.img

The way I recommend putting the new recovery on is:

1) Put the phone in BOOTLOADER mode
2) Plug the phone in your computer and a drive will show up
3) The drive contains files like boot.img, recovery.img, splash.img, etc. Go ahead and copy the ORIGINAL recovery.img and put it somewhere safe on your computer.
4) Download the test CWM recovery image I made and over-write the one on the drive. Make sure it wrote correctly.
5) Pull the battery and try booting into RECOVERY mode.

*DO THIS AT YOUR OWN RISK! I DON'T HAVE THE PHONE AND I'M ONLY WORKING OFF OF INFORMATION OTHERS HAVE GIVEN ME!*
Click to expand...


Ok cool sorry bout the misleading info
 
Sure, I'll test it. I've been doing the copy/paste method for the recovery for a while now. I'm making my own ROM and trying to get a recovery working currently.
 
Hey isaacj87 I will be on that irc channel you mentioned pretty much all day I have my phone here so if you want someone to test right away you can just hit me up.
 
The new recovery you made doesn't work either. This could mean that the bootloader could possibly be locked and not accepting the new images, or it could just mean that there's a problem porting. I'm not sure, all it does is just vibrate when you try to access it.
 
Bobomo said:
Uh, no offense but it's pretty obvious that guy doesn't know WTF he's talking about. Those are all ideas on how to root a phone that has already been rooted. He also said the following about whether or not the Triumph had a locked or encrypted bootloader: "But ALL android phones have a boot loader ( how do you think they boot? )"

:rolleyes:
Click to expand...

Ok lets FIRST get something straight here, i am NOT a dev, never said i was, im helping someone else over there with this phone. also, im HERE to help devs whom do not have the phone to help them get what they need for the phone.
Im just like the dev here, i have tested MANY phones and roms and so on for forums, this is something new to me as well. Yea, i may not know what the bootloader does and what not, you may. Who knows, but i know ill learn in time for my mistakes, here is a good quote from a guy i know in some universe someone made.

''The first step to wisdom and greatness is realizing how little you know.''

and i do realize this, this phone proves that.
 
Status
Not open for further replies.
Back
Top Bottom