Android OS Forum banner
1 - 9 of 9 Posts

· Android Apprentice
Joined
·
10 Posts
Discussion Starter · #1 ·
hey guys! sadly i do not have one yet, i will be getting one tomorrow so i can do some work on it and get it rooted. As soon as i do i will post it here as soon as i get it and root it. With this said. I will be posted POSSIBLE rooting methods that have worked on PAST phones. Please note im ONLY posting them i HAVE NOT TESTED IT since i do not have the phone, Please if you do and want to test let me know here.

DISCLAMER: You will be doing this under your own control, i am only post prior knowledge here and it has NOT been tested at all as far as i know. You can responsible if your phone does not work anymore and bricks. Do not blame me if this happens.

METHOD 1: Easy root ( not to sure since i never used this....

METHOD 2: Z4ROOT ( i did not use this ether so if it works let me know )

METHOD 3: super one click with perm root

http://dl.dropbox.com/u/4347574/Android/SuperOneClickv1.6.5-ShortFuse.zip

download from there, once you download run it with the phone IN dev mode. From there its going to stop at something.... i forgot what, once it does you can exit out of it.

Now, your going to click start, run, and type in cmd and enter. then go to the file you downloaded Super one click to and do the commands below.

adb shell
mount -o remount,rw -t yaffs2 /system /system
exit
adb push su /system/bin
adb push busybox /system/bin
adb shell
cd /system/bin
chmod 4755 su
chmod 555 busybox
exit
adb reboot

Thats all i can do for now TILL i get the phone or someone tests these methods out.
 

· Android Apprentice
Joined
·
10 Posts
Discussion Starter · #6 ·
ok here is the /dev/block you asked.

ls -l /dev/block
drwxr-xr-x root root 2011-07-27 00:13 vold
brw------- root root 179, 33 2011-07-27 00:13 mmcblk1p1
brw------- root root 179, 32 2011-07-27 00:13 mmcblk1
brw------- root root 179, 17 2011-07-27 00:13 mmcblk0p17
brw------- root root 179, 16 2011-07-27 00:13 mmcblk0p16
brw------- root root 179, 15 2011-07-27 00:14 mmcblk0p15
brw------- root root 179, 14 2011-07-27 00:13 mmcblk0p14
brw------- root root 179, 13 2011-07-27 00:13 mmcblk0p13
brw------- root root 179, 12 2011-07-27 00:13 mmcblk0p12
brw------- root root 179, 11 2011-07-27 00:13 mmcblk0p11
brw------- root root 179, 10 2011-07-27 00:13 mmcblk0p10
brw------- root root 179, 9 2011-07-27 00:13 mmcblk0p9
brw------- root root 179, 8 2011-07-27 00:13 mmcblk0p8
brw------- root root 179, 7 2011-07-27 00:13 mmcblk0p7
brw------- root root 179, 6 2011-07-27 00:13 mmcblk0p6
brw------- root root 179, 5 2011-07-27 00:13 mmcblk0p5
brw------- root root 179, 4 2011-07-27 00:13 mmcblk0p4
brw------- root root 179, 3 2011-07-27 00:13 mmcblk0p3
brw------- root root 179, 2 2011-07-27 00:13 mmcblk0p2
brw------- root root 179, 1 2011-07-27 00:13 mmcblk0p1
brw------- root root 179, 0 2011-07-27 00:13 mmcblk0
brw------- root root 7, 7 2011-07-27 00:13 loop7
brw------- root root 7, 6 2011-07-27 00:13 loop6
brw------- root root 7, 5 2011-07-27 00:13 loop5
brw------- root root 7, 4 2011-07-27 00:13 loop4
brw------- root root 7, 3 2011-07-27 00:13 loop3
brw------- root root 7, 2 2011-07-27 00:13 loop2
brw------- root root 7, 1 2011-07-27 00:13 loop1
brw------- root root 7, 0 2011-07-27 00:13 loop0
brw------- root root 1, 7 2011-07-27 00:13 ram7
brw------- root root 1, 6 2011-07-27 00:13 ram6
brw------- root root 1, 5 2011-07-27 00:13 ram5
brw------- root root 1, 4 2011-07-27 00:13 ram4
brw------- root root 1, 3 2011-07-27 00:13 ram3
brw------- root root 1, 2 2011-07-27 00:13 ram2
brw------- root root 1, 1 2011-07-27 00:13 ram1
brw------- root root 1, 0 2011-07-27 00:13 ram0

and mount

# mount
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=or
dered 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,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#
 

· Super Amazing Elite Recognized Developer
Joined
·
464 Posts
one of these /dev/block/mmcblk0p* partitions are the kernel, getting that kernel dumped will tell us if the bootloader is locked or not

to dump it do (as root):

dd if=/dev/block/mmcblk0p* of=/sdcard/mmcblk0p*.img

where * is the parition

from your mount the following partitions are already identified as not the kernel:
mmcblk0p7 = system
mmcblk0p8 = data
mmcblk0p9 = hidden/data
mmcblk0p10 = hidden
mmcblk0p11 = cache

dump all except these partitions, do not dump mmcblk0 either as thats the full internal card (and wont fit on your sdcard)

the mmcblk0p* partition to look for should be under 10MB, zip any partition under that and upload them for me so i can figure it out. :)
 

· Android Apprentice
Joined
·
10 Posts
here are the dumps i got 1-6 and the 6th one or the 1st one is 100 mb, but i added that anyway to make sure it was all there. download link is below let me know what you find

http://dl.dropbox.com/u/4347574/dumps.rar

edit: Hey, i was looing over at android gorums and it seems somoene is already working on it if you wanna take a look, there trying to post over CMD recovery, here is the link with info, from this site also, it smees you know the first one for recovery.img and boot.img. the rest are not for this.

http://androidforums.com/motorola-triumph/383332-clockworkmod-recovery-motorola-triumph.html
 
1 - 9 of 9 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top