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

Root M130 Rooted!

I was unaware of the es explored 3.0 problem. I rooted my phone by copy and paste of edited .sh file!

I installed busybox and root checker and superuser. reboot! Bam rooted my phone.

Removed a few apps and thripled my free space!

NOW the problems arrived. I updated binaries or something and after rebooting phone nothing works right that is suppose to be dealing with roots stuff.
Rootchecker give a message saying system appears to be running slow and never tells me I am rooted or not rooted it just hangs up with the hourglass thing showing that it is checking.

No root applications or root actions actually work although I get the message that superuser status has been given when I try.

Is this because I updated the binaries? I uninstalled Superuser and busybox and reinstalled them. How can I unupdate the bianaries? Any ideas on how to get this working again???

Also I installed Apps2Rom. When I try to run it now I get this message:
Application Superuser (in process com.nushufon.android.su) is not responding.
 
omegaman66 said:
I was unaware of the es explored 3.0 problem. I rooted my phone by copy and paste of edited .sh file!

I installed busybox and root checker and superuser. reboot! Bam rooted my phone.

Removed a few apps and thripled my free space!

NOW the problems arrived. I updated binaries or something and after rebooting phone nothing works right that is suppose to be dealing with roots stuff.
Rootchecker give a message saying system appears to be running slow and never tells me I am rooted or not rooted it just hangs up with the hourglass thing showing that it is checking.

No root applications or root actions actually work although I get the message that superuser status has been given when I try.

Is this because I updated the binaries? I uninstalled Superuser and busybox and reinstalled them. How can I unupdate the bianaries? Any ideas on how to get this working again???

Also I installed Apps2Rom. When I try to run it now I get this message:
Application Superuser (in process com.nushufon.android.su) is not responding.
Click to expand...

which busybox? 1.20?
are you update binary from superuser?

i'm use busybox 1.18.2
and not update about binary from superuser.apk
 
"which busybox? 1.20?
are you update binary from superuser?

i'm use busybox 1.18.2
and not update about binary from superuser.apk "

I don't know! How can I tell? Busybox Free version 9.2??? I installed busybox from Play Store! I remember at some point being asked to update bianaries and I think it was from busybox but not 100% sure if that is the program that asked. That or SU I am pretty sure.

The com.nushufon.android.su is a blank folder if that helps.

superuser v3.1.3(46)
SU binary is v3.1.1(17)
 
Ok installed superuser v2.3.6.3

SU binary currently in my system/bin folder is about 10 times bigger than the one that came with the superuser v2.3.6.3 download. Can I just replace the current file with the one that came with the superuser zip download?

edit:
Can I simply using es explorer copy the new SU file to the system/bin folder to overwrite the old one or must I do some sort of install. I installed the superuser app by clicking on the apk and it installed but what about the su file that goes in system/bin? Delete the old and replace with the new via es file explorer?
 
delete then copy and paste worked! Showing rooted again!

Got tired of waiting for an answer so dove in head first! haha thanks for your help!!!
 
great to hear!
just for future reference, the custom gnm recovery has an option to add/fix root permissions, so that will solve your problem as well.;)
 
omegaman66 said:
delete then copy and paste worked! Showing rooted again!

Got tired of waiting for an answer so dove in head first! haha thanks for your help!!!
Click to expand...

:D
good work!!

@Willster419
how i can get a kernel 2.6.35.7-perf nmnc@nmnc #1??
i must try to flash it, hope can back my internet data..
but anticipatory i cant access recovery with a hard key :(
have a clue?
 
to boot your phone in recovery from pc:
enable android debugging on your phone
install the required drivers on to your computer
when you plug your phone to your computer in charge only mode, the phone should say that usb debuging in enabled, and in device manager in the pc it should list the adb interface in the android phone catagory.
open a command prompt
cd to adb.exe
type adb reboot recovery
---
to boot your phone in recovery from phone
download an android terminal
type su
type reboot recovery
---
hope that helps

also i reccommend trying what i had said before to find if it is a data/cache problem, or if it is system:
"Install the c771 setup wizard apk. (both of them) and make them system apps. then go to recovery and:
select factory reset option
then wipe cache
then wipe data
then wipe dalvick cache
after that reboot and it should ask you to activate your phone. activate it and you should have data.

you could also backup all your user apps via titanium backup and restore them back after.
"
 
Willster419 said:
to boot your phone in recovery from pc:
enable android debugging on your phone
install the required drivers on to your computer
when you plug your phone to your computer in charge only mode, the phone should say that usb debuging in enabled, and in device manager in the pc it should list the adb interface in the android phone catagory.
open a command prompt
cd to adb.exe
type adb reboot recovery
---
to boot your phone in recovery from phone
download an android terminal
type su
type reboot recovery
---
hope that helps

also i reccommend trying what i had said before to find if it is a data/cache problem, or if it is system:
"Install the c771 setup wizard apk. (both of them) and make them system apps. then go to recovery and:
select factory reset option
then wipe cache
then wipe data
then wipe dalvick cache
after that reboot and it should ask you to activate your phone. activate it and you should have data.

you could also backup all your user apps via titanium backup and restore them back after.
"
Click to expand...

what that's mean?
i do it but still don't have data :(

c:\casio>adb shell
# netcfg
netcfg
lo UP 127.0.0.1 255.0.0.0 0x00000049
dummy0 DOWN 0.0.0.0 0.0.0.0 0x00000082
rmnet0 UP 10.226.179.12 255.255.255.252 0x00000041
rmnet1 DOWN 0.0.0.0 0.0.0.0 0x00000000
rmnet2 DOWN 0.0.0.0 0.0.0.0 0x00000000
rmnet3 DOWN 0.0.0.0 0.0.0.0 0x00000000
rmnet4 DOWN 0.0.0.0 0.0.0.0 0x00000000
rmnet5 DOWN 0.0.0.0 0.0.0.0 0x00000000
rmnet6 DOWN 0.0.0.0 0.0.0.0 0x00000000
rmnet7 DOWN 0.0.0.0 0.0.0.0 0x00000000
rmnet_sdio0 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet_sdio1 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet_sdio2 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet_sdio3 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet_sdio4 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet_sdio5 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet_sdio6 DOWN 0.0.0.0 0.0.0.0 0x00001002
rmnet_sdio7 DOWN 0.0.0.0 0.0.0.0 0x00001002
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
sit0 DOWN 0.0.0.0 0.0.0.0 0x00000080
ip6tnl0 DOWN 0.0.0.0 0.0.0.0 0x00000080
wlan0 DOWN 0.0.0.0 0.0.0.0 0x00001002
# busybox ifconfig
busybox ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

rmnet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-00
inet addr:10.226.179.12 Mask:255.255.255.252
UP RUNNING MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:612 (612.0 B) TX bytes:846 (846.0 B)

# busybox route
busybox route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.226.179.12 * 255.255.255.252 U 0 0 0 rmnet0
# busybox netstat
busybox netstat
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State

Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ] DGRAM 2315 /dev/socket/wpa_wlan0
unix 2 [ ] DGRAM 2568 /data/misc/wifi/sockets
/wpa_ctrl_227-1
unix 3 [ ] STREAM CONNECTED 1513 /data/radio/qmux_client
_socket 112
unix 2 [ ] DGRAM 2570 /data/misc/wifi/sockets
/wpa_ctrl_227-2
unix 3 [ ] STREAM CONNECTED 1591 /data/radio/qmux_client
_socket 206
unix 2 [ ] DGRAM 1625 /data/data/com.safenet.
vpnclient/vpnc_app_to_dmn
unix 2 [ ] STREAM 1443 /dev/socket/wmdrmd
unix 4 [ ] DGRAM 2552 /data/misc/wifi/wpa_sup
plicant/wlan0
unix 3 [ ] STREAM CONNECTED 1450 @com.nec.android.ncmc.w
mc.callback
unix 3 [ ] STREAM CONNECTED 3163
unix 3 [ ] STREAM CONNECTED 2258 /dev/socket/rild
unix 3 [ ] STREAM CONNECTED 2257
unix 3 [ ] STREAM CONNECTED 2067 /dev/socket/zygote
unix 3 [ ] STREAM CONNECTED 2066
unix 3 [ ] STREAM CONNECTED 1441 /dev/socket/vold_append

unix 3 [ ] STREAM CONNECTED 2051
unix 3 [ ] STREAM CONNECTED 2043 /dev/socket/vold
unix 3 [ ] STREAM CONNECTED 2042
unix 3 [ ] STREAM CONNECTED 2032 /dev/socket/netd
unix 3 [ ] STREAM CONNECTED 2031
unix 3 [ ] STREAM CONNECTED 2022 /dev/socket/dbus
unix 3 [ ] STREAM CONNECTED 2021
unix 3 [ ] STREAM CONNECTED 1442 /dev/socket/installd
unix 3 [ ] STREAM CONNECTED 1988
unix 2 [ ] DGRAM 1626
unix 3 [ ] STREAM CONNECTED 1592 /data/radio/qmux_connec
t_socket
unix 3 [ ] STREAM CONNECTED 1579
unix 3 [ ] STREAM CONNECTED 1578
unix 3 [ ] STREAM CONNECTED 1575
unix 3 [ ] STREAM CONNECTED 1574
unix 3 [ ] STREAM CONNECTED 1514 /data/radio/qmux_connec
t_socket
unix 3 [ ] STREAM CONNECTED 1491
unix 3 [ ] STREAM CONNECTED 1490
unix 3 [ ] STREAM CONNECTED 1358
unix 3 [ ] STREAM CONNECTED 1357
# busybox ps
busybox ps
PID USER TIME COMMAND
1 0 0:06 /init
2 0 0:00 [kthreadd]
3 0 0:00 [ksoftirqd/0]
4 0 0:00 [events/0]
5 0 0:00 [khelper]
6 0 0:00 [async/mgr]
7 0 0:02 [suspend]
8 0 0:00 [irq/155-pm8058-]
9 0 0:00 [sync_supers]
10 0 0:00 [bdi-default]
11 0 0:00 [kblockd/0]
12 0 0:00 [khubd]
13 0 0:00 [kmmcd]
14 0 0:00 [rpciod/0]
15 0 0:00 [modem_notifier]
16 0 0:00 [thermo_sensor_p]
17 0 0:00 [qmi]
18 0 0:00 [nmea]
19 0 0:00 [rpcrouter]
20 0 0:00 [rpcrotuer_smd_x]
21 0 0:00 [dalrpc_rcv_DAL0]
22 0 0:00 [krpcserversd]
23 0 0:00 [krmt_storagecln]
24 0 0:00 [krmt_storagecln]
25 0 0:00 [kswapd0]
26 0 0:00 [aio/0]
27 0 0:00 [ecryptfs-kthrea]
28 0 0:00 [nfsiod]
29 0 0:00 [crypto/0]
40 0 0:00 [mdp_dma_wq]
41 0 0:00 [mdp_vsync_wq]
42 0 0:00 [mdp_pipe_ctrl_w]
43 0 0:00 [mdp_cursor_ctrl]
44 0 0:00 [vidc_worker_que]
45 0 0:00 [vidc_timer_wq]
46 0 0:00 [scsi_tgtd/0]
47 0 0:00 [mtdblock0]
48 0 0:00 [mtdblock1]
49 0 0:00 [mtdblock2]
50 0 0:00 [mtdblock3]
51 0 0:00 [mtdblock4]
52 0 0:00 [mtdblock5]
53 0 0:00 [mtdblock6]
54 0 0:00 [spi_qsd.0]
61 0 0:00 [k_otg]
62 0 0:00 [file-storage]
63 0 0:00 [usb_cdrom]
64 0 0:00 [k_rmnet_work]
65 0 0:00 [diag_wq]
66 0 0:00 [synopex_wq]
68 0 0:00 [krtcclntd]
69 0 0:00 [krtcclntcbd]
70 0 0:00 [sensor_poll]
71 0 0:00 [kbatteryclntd]
72 0 0:00 [kbatteryclntcbd]
73 0 0:00 [kstriped]
74 0 0:00 [kondemand/0]
75 0 0:00 [kconservative/0]
77 0 0:00 [usbhid_resumer]
78 0 0:00 [binder]
79 0 0:00 [l2cap]
80 0 0:00 [krfcommd]
81 0 0:00 [voice]
82 0 0:00 [acdb_cb_thread]
83 0 0:00 [khsclntd]
84 0 0:00 [kgsl-3d0/0]
85 0 0:00 [kgsl-2d0/0]
86 0 0:00 /sbin/ueventd
88 0 0:00 [mmcqd]
92 1000 0:00 /system/bin/servicemanager
93 0 0:00 /system/bin/vold
94 0 0:00 /system/bin/vold_append /etc/eut/eut.iso
95 0 0:00 /system/bin/netd
96 0 0:00 /system/bin/debuggerd
97 0 0:04 zygote /bin/app_process -Xzygote /system/bin --zygote --s
98 1013 0:00 /system/bin/mediaserver
99 1002 0:00 /system/bin/dbus-daemon --system --nofork
100 0 0:00 /system/bin/installd
102 1017 0:00 /system/bin/keystore /data/misc/keystore
103 0 0:00 /system/bin/fota_pipe
109 0 0:00 /system/bin/cnd
110 0 0:00 /system/bin/port-bridge /dev/smd0 /dev/ttyGS0
111 0 0:00 /system/bin/qmuxd
112 0 0:00 /system/bin/netmgrd
113 0 0:00 /system/bin/ptt_socket_app
116 0 0:00 /system/bin/wmcd
119 0 0:00 /system/bin/wmdrmd
120 0 0:00 /system/bin/ncmdiagd
137 0 0:01 /system/bin/ak8977daemon
138 1000 0:00 /system/bin/devstatservice
206 1001 0:00 /system/bin/rild
207 0 0:00 /sbin/adbd
224 0 0:00 /system/bin/vpnclientpm -O /data/data/com.safenet.vpnclie
227 1000 0:55 system_server
308 1000 0:02 com.android.systemui
323 10048 0:00 com.nuance.xt9.input
324 1001 0:16 com.android.phone
327 10011 0:00 com.nec.android.ncmc.wmc
332 1000 0:00 com.nec.android.ncmc.location
337 1000 0:00 com.nec.android.ncmc.net
340 1000 0:00 com.innopath.activecare
356 10047 0:04 com.sonyericsson.home
383 0 0:00 [knv-clientclntd]
384 0 0:00 [WD_Thread]
385 0 0:00 [ksdioirqd/mmc1]
386 0 0:03 [MC_Thread]
387 0 0:00 [TX_Thread]
405 10025 0:01 com.google.process.gapps
428 1000 0:00 com.nec.android.ncmc.NcmcNVforEri
429 1007 0:00 /system/bin/logwrapper /system/bin/wpa_supplicant -Dwext
432 1010 0:00 /system/bin/wpa_supplicant -Dwext -iwlan0 -c/data/misc/wi
471 1000 0:00 com.nec.android.ncmc.exchange.data.encryption
491 10022 0:00 com.vzw.sms
496 10064 0:14 com.android.mms
526 10051 0:00 com.nec.android.ncmc.flashlight.widget
533 10042 0:00 com.fusionone.android.sync.service
540 10019 0:04 com.nec.android.ncmc.gzgear.wGzSeaTide
547 10019 0:00 com.nec.android.ncmc.gzgear.wGzVirtualTrek
549 10019 0:01 com.nec.android.ncmc.gzgear.seatide
561 10014 0:01 com.nec.android.ncmc.clock.widget
562 10019 0:00 com.nec.android.ncmc.gzgear.menu
578 10019 0:00 com.nec.android.ncmc.gzgear.walkingcounter
582 1000 0:01 com.android.settings
593 10009 0:04 android.process.media
624 10007 0:00 com.nec.android.ncmc.cradleapp
632 10057 0:00 com.nec.android.ncmc.memo.widget
654 10010 0:00 com.pv.wmdrmservice
669 1000 0:00 com.pv.wmdrmproxy
704 10038 0:00 com.android.email
738 10076 0:01 com.android.vending
767 10025 0:00 com.google.android.gms
788 10025 0:00 com.google.process.location
810 10023 0:05 com.cooliris.media
820 0 0:00 [loop0]
821 0 0:00 [kdmflush]
833 0 0:00 [kcryptd_io]
834 0 0:00 [kcryptd]
836 10067 0:00 com.google.android.apps.uploader
845 10082 0:01 com.maxmpz.audioplayer
852 10008 0:00 com.android.quicksearchbox
1101 10018 0:00 android.process.acore
1109 10018 0:00 android.process.eep
1129 10040 0:00 com.nec.android.ncmc.exchange.data.encryption.app
1140 0 0:00 [irq/273-msm-sdc]
1142 0 0:00 [cqueue]
1145 10044 0:00 com.nec.android.ncmc.phone.nvwrapper
1177 10075 0:00 com.google.android.gm
1195 0 0:00 /system/bin/sh -
1197 0 0:00 [flush-31:4]
1201 0 0:00 busybox ps
# exit
that's i have test via adb
and i think have problem has kernel
CMIIW

nb: @Willster419 can we talk at chat or something?
 
Thanks to everyone here and some other threads, I successfully rooted my M130. Wifi and everything works perfectly, and battery life is at least double with all the junk gone.

I kept running into road blocks though following the various instructions but most of these are likely due to my complete ineptness at Linux commands. I'm a Windows nerd, sorry.

I suspect others will have similar stumbling blocks so when I root a friends M130 also, I'll do a guide that should help anyone like me that struggles with Linux. I'm a long time lurker, about time I gave something back.

Main stumbling blocks I encountered were....

a. Couldn't get the drivers to work on an x64 computer and I don't have access to any older machines with x86 anymore. Instead, I did everything through the phone with no connection to the computer.

b. Couldn't save my edits to the init.qcom.sdio.sh file. Instead, I copied it to the SD card using Xplorer and edited there. Only option that worked to get it back into system was to move it using Xplorer. I made an additional copy so I'd have an original to revert back to when I was all done.

c. Couldn't get root access through ADB shell. Instead, I used Xplorer to copy SU from my SD card into the system folder. From there forward I used Android terminal emulator to get root access.

d. Superuser from Google Play wanted to install an additional binary or something and then failed. Instead, I installed superuser.apk that is provided elsewhere in this tread from the SD card.

It's all working great and I'm chuffed that I figured a way to overcome each of the obstacles. I'd like to be a Linux nerd but have no time to learn it these days.

When I do my guide here in a week or so, I'll also attach all the files I used (or link to them) to try and make it a one stop shop for everything that is needed for root.

This phone rocks now with all that Verizon crap gone. My wife drove over mine on her driveway with her Ford Expedition. After cleaning the tracks off the screen, there is just one minor nick on the surround otherwise zero damage.
 
very cool! congrats on the root!
can't wait to see your guide! Just a couple of quick things that I want to add...

for saving the changes to the file, if you download es file explorer the new 3.0 one from google play this method will NOT work. I posted my link to the version used to root.
Dev-Host - com.estrongs.android.pop.apk - The Ultimate Free File Hosting / File Sharing Service

for the drivers, I know that they are tempramental. sometimes they will say they are already installed. sometimes they will give a bogus error about the phone not being connected. However, I was able to get them to install. When an error about the phone comes up, go to task manager and terminate all processes with that misexe type name. then restart your pc. Then plug your phone into your pc in charge mode, and the drivers should install. It may take some tampering, but it will work.

I really recommend that you get the drivers to work, and that you ALWAYS have usb debugging on. So many people don't and then get stuck to a point that they could have used adb.
 
I'll give those drivers another try. I read in other threads that they don't work on x64 and more or less gave up. It'll be a good Windows challenge for me, I like those.

Thanks again to everyone. I absolutely love this phone now with all the junk gone. Not too big and doesn't slip out of my hands at every opportunity. Also the fatty pad by my thumb doesn't keep hitting the search button on the bottom right of the screen while texting which has been an annoyance with other phones.
 
I am eagerly awaiting a guide on rooting the m130. I'm a little worried to do any trial and error and brick my commando.
 
Dan917 said:
I am eagerly awaiting a guide on rooting the m130. I'm a little worried to do any trial and error and brick my commando.
Click to expand...
first off this is a guide, and a very good guide. Second there always risk in rooting or anything that you shouldn't do with your phone. That is the risk you take. Third if you read and reread and read agian. You should under stand how to do it. If not then rooting is not for you. Fourth if you look there is another way too root if your not ready to try this way. Plus I have a tools posted that even makes it easier. All you need to do is read and read and learn. Follow all steps to the T then you should be good. But as always it is your risk to take.
 
briankeys said:
I'll give those drivers another try. I read in other threads that they don't work on x64 and more or less gave up. It'll be a good Windows challenge for me, I like those.

Thanks again to everyone. I absolutely love this phone now with all the junk gone. Not too big and doesn't slip out of my hands at every opportunity. Also the fatty pad by my thumb doesn't keep hitting the search button on the bottom right of the screen while texting which has been an annoyance with other phones.
Click to expand...

I am running windows 7 64 bit on two pc's (laptop and desktop) and I found this file here somewhere to help resolve the driver issue. Try this version:
Dev-Host - Drivers.zip - The Ultimate Free File Hosting / File Sharing Service
a lot of users on youtube were having the same problem. this msi file silently installs the drivers (so be patient with it :) ) and then calls a plug and play device search, so make sure that your phone is connected.
 
whatever i do, my C771 with 2.3.3 with build number M130 won't root..can't get /system/bin to RW no matter what i do..who has done this phone this week?
 
hello jiminsav,
there are a few reasons why it could not be working, like a extra space in the script, or using the wrong version of es file explorer, etc. Unless you want to continue with this method, i suggest another method that comes with a YouTube video tutorial. it may look longer, but IMHO its easier.
best of luck

http://androidforums.com/commando-a...-make-your-phone-recoverable-system-wipe.html

and the video

How to fully root and foolproof your Casio C771 Commando - take three - YouTube
 
Willster< you da man..i have tried since 6 PM yesterday, till 11 PM today to get this thing rooted...tried 15 diffrent ways on 30 difrent forums, and you got it done. now i'm gonna throw your red ROM on here and be happy.:)
 
You must log in or register to reply here.
Back
Top Bottom