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

Root M130 Rooted!

Hey guys,

I'm new and never rooted a phone b4... I followed the step by step from post #125 but got confused by the last few steps... I believe everything I had done up to this point has worked, besided having to turn debugging mode off to move the files over to my phone. Can someone kinda help me better understand step 39?

Thanks! :)

"39. Using ADB in the command prompt, verify that the phone has been rooted by finding "su" with the following steps and has "rwsr-sr-x" by it.
38. Press return after each line within the command prompt on your computer:

adb shell
cd /system/bin
ls -l

40. Install superuser.apk and busybox.apk. Find them on the play store if need be. And you should be rooted."
 
So, for all of you who want to root, this is a quick 10-step beta guide. Use at your own risk, im not responsible, etc.

1. Install es file explorer.
2. use it to go to /system/etc/init.qcom.sdio.sh
3. long press, open as text, use es note editor.
4. (The follwoing some quoted parts are copied from TommyTopDrive's posts. His work, not mine) Navagate to, "the very bottom (just above "exit 0")" and, add the following:

chmod 0777 /system
chmod 0777 /system/bin

5. Save the file. Then repeat step 3. and add a 1 after the "#!/system/bin/sh" and save. Then repeat step 3 again and remove the 1. The reason you do this is because, "it makes a backup and might try to load the backup."
6. restart your phone.
7. Push (or copy from sd card) the su bianary file to /system/bin
8. do steps 2 and 3, then below the code you put in earlier, put in, "

chown root.root /system/bin/su
chmod 06755 /system/bin/su

9."reboot again and verify by adb from a command prompt that su is owned by root and is rwsr-sr-x by doing the following (press return after each line):

adb shell
cd /system/bin
ls -l

10. "install superuser.apk and install busybox...oh, and that means your rooted." :)

And then your all set! You welcome to all!:)

I did all the steps except #9... I dont know how to verify using adb :/ When I click on the adb on my computer it runs cmd for a split second and then disappears...
 
I did all the steps except #9... I dont know how to verify using adb :/ When I click on the adb on my computer it runs cmd for a split second and then disappears...

Go to the Google play Store down /install root Checker. That will tell you. It free as well
 
Go to the Google play Store down /install root Checker. That will tell you. It free as well

Thanks! I ran the test on 2 Root Checker apps just to be sure. SuperUser pops up and asks to allow and when I do it says its successfully rooted....

BUT I can't delete apps via ES File Explorer. Is this not how you go about deleting them? I'm really just doing this to remove some bloat ware from Verizon. And maybe the Bing search bar :)
 
Thanks! I ran the test on 2 Root Checker apps just to be sure. SuperUser pops up and asks to allow and when I do it says its successfully rooted....

BUT I can't delete apps via ES File Explorer. Is this not how you go about deleting them? I'm really just doing this to remove some bloat ware from Verizon. And maybe the Bing search bar :)

First you best do a full nadroid backup. Search for m130 [ I forget the thread name. I forget. but is in here all thing rooted... Then go to the app store and grab root App Delete and freeze.. That's after a back up... start by freezing the apps for a few days with that app.. Once your sure they will not cause errors then go to the recycle part of the app and then delete them...
Also there is a thread on safe apps to remove on the Casio G'zOne Commando C771... Good luck
 
First you best do a full nadroid backup. Search for m130 [ I forget the thread name. I forget. but is in here all thing rooted... Then go to the app store and grab root App Delete and freeze.. That's after a back up... start by freezing the apps for a few days with that app.. Once your sure they will not cause errors then go to the recycle part of the app and then delete them...
Also there is a thread on safe apps to remove on the Casio G'zOne Commando C771... Good luck

Awesome! Thanks a lot! :D
 
OK did all the steps,ran adb su is owned by root and is rwsr-sr-x.
Root Checker shows not rooted.
Cannot update supersu either.
Could someone help out here please?
thanks
 
OK did all the steps,ran adb su is owned by root and is rwsr-sr-x.
Root Checker shows not rooted.
Cannot update supersu either.
Could someone help out here please?
thanks

For me I'm stuck on pushing the "SU" to /system/bin/ with ADB. Tried to copy it to the file with ES File Explorer, but it won't accept it "unable to move BINSU". Can anyone help with this??

Greatly appreciated,

C.
 
Did you install superuser and busybox from the play store?


OK did all the steps,ran adb su is owned by root and is rwsr-sr-x.
Root Checker shows not rooted.
Cannot update supersu either.
Could someone help out here please?
thanks

Does not seem like you the /system and /system/bin chmod to 777
Recheck those dirs. To push via adb use this command


adb push /sdcard/su /system/bin

Or if you have the su stored on your c drive
Example
adb push c:\casio\adb\su /system/bin

I for get if you need a / @ the end of bin.
So if it does not work the first time try adding the /


Note the system and bin NEED to be set to 777
Or you'll get permission denied...
Hope this helps


For me I'm stuck on pushing the "SU" to /system/bin/ with ADB. Tried to copy it to the file with ES File Explorer, but it won't accept it "unable to move BINSU". Can anyone help with this??

Greatly appreciated,

C.
 
Did you install superuser and busybox from the play store?




Does not seem like you the /system and /system/bin chmod to 777
Recheck those dirs. To push via adb use this command


adb push /sdcard/su /system/bin

Or if you have the su stored on your c drive
Example
adb push c:\casio\adb\su /system/bin

I for get if you need a / @ the end of bin.
So if it does not work the first time try adding the /


Note the system and bin NEED to be set to 777
Or you'll get permission denied...
Hope this helps

Checked all file permissions and they were correct.I had installed supersu wouldn't take update,so I replaced it with superuser.Superuser took update now rooted,yea.
 
If all else fails READ the directions!! Everyone is having great success rooting the G'zOne so WTH was I doing wrong... then it dawned on me. Wifi was still on (don't know if it would make a difference) and I was trying to (move) the "SU" file when I was suppose to copy/paste the file to the right dir. Now I've got permissions...

I give special thanks to; tommytopdrive; r_hippie and all the other great folks, who took the time and effort to make this possible and to share with all of us
:party:

Let the Games Begin


I'm always having a PICNIC.....Problem In Chair, Not In Computer :D
 
If all else fails READ the directions!! Everyone is having great success rooting the G'zOne so WTH was I doing wrong... then it dawned on me. Wifi was still on (don't know if it would make a difference) and I was trying to (move) the "SU" file when I was suppose to copy/paste the file to the right dir. Now I've got permissions...

I give special thanks to; tommytopdrive; r_hippie and all the other great folks, who took the time and effort to make this possible and to share with all of us
:party:

Let the Games Begin


I'm always having a PICNIC.....Problem In Chair, Not In Computer :D

Wifi off is a must..
Push the su.. Don't copy it over. And reset the permissions to it the remove those two lines that set the root and chmod to the su then edit the first two lines to set system and bin back to 0777 hope this helps.... First this after success root do the all in one recovery to make a backup in case of a brick...Good luck
 
Has anyone else had problems with their touchscreen while the phone is on the charger? Now that my phone is rooted (thanks to all the great posts!) is there any fix for this?
 
Has anyone else had problems with their touchscreen while the phone is on the charger? Now that my phone is rooted (thanks to all the great posts!) is there any fix for this?

Not one issue. Only one thing but not related to the root. When I turn Wifi on after a few days it seems I have to reboot to get it to work but I think it's related to a Wifi script. Other wise its like no other Gz'One Commando C771 m130 ever lol
 
I downloaded one of those simple one-touch reboot apps and it solved the Wifi issue...kind of. The indicator will light up blue on the bottom of the stock Widget, but nothing else. Hit the soft reset and the Wifi will start.

Finally, I updated the recovery to GNMs all in one recovery for the commando from
http://androidforums.com/getitnowmarketing/330813-all-in-one-recovery-thread.html

*I highly recommend you install the GNM recovery as soon as your rooted and do a nandroid backup BEFORE you start freezing and removing bloatware. In this, you can always return to an operational commando if you fudge something up....experience is the best teacher.

So I've successfully rooted the device.

Now I'm confused as to what I'm doing with the All in One Recovery & nandroid?

I'm guessing just download Nandroid from Play, make a backup, and place it in a safe location?

Edit: So I've made a backup using Nandroid, and copied it over to my computer (as well as leaving one on the SD).

Do I need to make a backup with Titanium before I go removing bloatware?

I just really don't want to jump the gun here and cause havoc with the phone.
 
I downloaded one of those simple one-touch reboot apps and it solved the Wifi issue...kind of. The indicator will light up blue on the bottom of the stock Widget, but nothing else. Hit the soft reset and the Wifi will start.



So I've successfully rooted the device.

Now I'm confused as to what I'm doing with the All in One Recovery & nandroid?

I'm guessing just download Nandroid from Play, make a backup, and place it in a safe location?

Edit: So I've made a backup using Nandroid, and copied it over to my computer (as well as leaving one on the SD).

Do I need to make a backup with Titanium before I go removing bloatware?

I just really don't want to jump the gun here and cause havoc with the phone.

this will explain better for our phone

Casio C771 Unlock Bootloader and Install GNM Recovery via Fastboot
 
I've tried both.... I have Root Explorer on my rooted TF700 and ES File Explorer on my newly rooted Commando. Thanks to you tommytopdrive. I don't know which one I prefer because I like the permissions on the screen with Root Explorer, like you, but I like the look of ES File Explorer and it seems to be safer for the things that could potentially brick my phone if I wasn't aware of what I was doing.

I'm not a software writer/engineer by any means, but I followed exactly what you did on your first try, just without turning any of my wireless stuff off. It worked, and my wifi/gps/3g/bluetooth all work. Thanks again for sharing all this with us.

For those of you who don't know what you're doing, don't just skip to where it might look like there's good information for rooting your Commando. READ THROUGH EVERYTHING, all the answers are somewhere in this thread, THOROUGHLY search for them and you'll find them. I just followed what tommytopdrive posted as an experiment and then found what Willster419 posted about the 10-steps to root, on the bottom of the same page of the thread (page 1). It worked flawlessly for me, and I'm not a software kinda guy.

For those of you still too lazy to look at everything on the thread, here are the steps to root the M130 build of the Casio G'zOne Commando. If there are quotation marks around something, that means I am referencing it. The stuff in between the quotation marks is the important material.

Pre-requisites:
A. YOU ALSO NEED TO DOWNLOAD THE commando "drivers.zip" THAT HAVE BEEN POSTED. ALONG WITH THE "casio 130 root.zip" FILE PROVIDED IN THIS THREAD. Unzip them to a place you won't forget. And install the "drivers" before connecting your phone to the computer.
B. Turn on USB Debugging on your phone.

1. Install es file explorer from the play store.
2. Open it once it is done downloading and installing.
3. In the top left corner of the screen, there is a star with "Favorites" under it... Click on it.
4. Select the phone icon with a "/" under it.
5. In that so-called directory or folder you'll find another folder named "system". Select that folder.
6. Within that directory you'll find "etc". Select it.
7. In that folder there is a file named "init.qcom.sdio.sh"... Long press (hold your finger on that file) until a menu pops up. (filepath should be /system/etc/init.qcom.sdio.sh).
8. Select "open as text".
9. Then choose the "es note editor" option.
10. You'll see some weird looking writing that is coherent at the top. However, navigate to the very bottom part of the file notes where you'll see "exit 0".
11. Add exactly the following, just above "exit 0"

chmod 0777 /system
chmod 0777 /system/bin

12. Press the back button until you are prompted as to whether or not you want to save the file, select "yes" and save the file.
13. Then repeat steps 3-9.
14. On the top of the notes you should immediately see something that says "#!/system/bin/sh". Place a "1" at the end of that line.
15. Then press back again, twice, to save the file once more.
16. Then repeat steps 3-9.
17. This time remove the "1" you just added.
18. Save the file by backing out again and selecting "yes" when prompted to save it. As said by tommytopdrive: "The reason you do this is because, sometimes it makes a backup and might try to load the backup."
19. Restart your phone.


20. Using ADB, push the "su" file from your computer to your device.
21. ALTERNATIVELY you can copy the unzipped "casio m130 root" folder from your computer to some place on your phone that you won't forget. I put my folder right inside "/sdcard/".
22. Disconnect your phone from your computer.
23. Open ES File Explorer again and go the place where you copied the "casio m130 root" folder to.
24. Open that folder and find "su". For me the filepath was "/sdcard/casio m130 root/su"
25. Long press the file and select copy.
26. Click on the star in the upper left corner again.
27. Select the phone icon with the "/" under it.
28. Find the "system" folder and select it.
29. Now within the "/system/" directory you'll find a folder named "bin", select it.
30. Click the little blue box in the bottom and center of your screen with the blue circle and arrow in it.
31. Click on "su". You should get a confirmation saying the file has been successfully inserted. If you didn't, you did something wrong, check what you wrote from step 11 and make sure it was on the right file.
32. Save the folder by backing out of ES File Explorer.
33. Open ES File Explorer again.
34. Follow steps 3-10.
35. Just above "exit 0" and right below the lines you added during step 11, insert the following two lines, exactly as they are:

chown root.root /system/bin/su
chmod 06755 /system/bin/su

36. Press back twice to save again.
37. Follow steps 13-18.
38. Restart your phone again.
39. Using ADB in the command prompt, verify that the phone has been rooted by finding "su" with the following steps and has "rwsr-sr-x" by it.
38. Press return after each line within the command prompt on your computer:

adb shell
cd /system/bin
ls -l

40. Install superuser.apk and busybox.apk. Find them on the play store if need be. And you should be rooted.






I dont understand step 39.....

How do I run ABD in the command prompt?
 
You need to enter these commands through the Command Prompt in Windows.

For simplicity, putting the ADB folder directly in the C:\ drive will save time.

Win7/Vista: hit start, type CMD, hit enter
XP: start, run, CMD

Once that is open, you need to type in cd C:\ADB (or where ever you've got the folder). This will change the directory from C:\ to C:\ADB.
 
My first post here.

First of all I would like to thank everyone who posted your problems and successes. They spurred me on toward having my own success in ROOTING MY PHONE!!!!!!!!!
I tried zergRush and it didn't work...
The first two times I tried the method outlined in this thread it didn't work either.
Once was due to making a code mistake and the next time I couldn't get the su binary file to move into system/bin. I finally copied it and it went.
ADB gave me a few issues... not too familiar with the command prompt.
It was and is definitely worth it.

It felt great to rid myself of way too much bloatware.

My question is now that I've rooted this thing, Would some of you be so kind as to share your experiences with some of the better apps and/or Roms you are using or have used?

Thanks in advance for your responses.

BIG THANKS AGAIN!!!!!!!!!!!!!!!!
 
My first post here.

First of all I would like to thank everyone who posted your problems and successes. They spurred me on toward having my own success in ROOTING MY PHONE!!!!!!!!!
I tried zergRush and it didn't work...
The first two times I tried the method outlined in this thread it didn't work either.
Once was due to making a code mistake and the next time I couldn't get the su binary file to move into system/bin. I finally copied it and it went.
ADB gave me a few issues... not too familiar with the command prompt.
It was and is definitely worth it.

It felt great to rid myself of way too much bloatware.

My question is now that I've rooted this thing, Would some of you be so kind as to share your experiences with some of the better apps and/or Roms you are using or have used?

Thanks in advance for your responses.

BIG THANKS AGAIN!!!!!!!!!!!!!!!!
no roms at the moment and I don't think anyone will take it on since the phone is not liked..

Wish they would .. they have to understand in some line of work you need a tuff phone..
I can fist hand tell you that this is the one..
and after the root . removing the un wanted crap with Root App Delete (uninstaller) and using zeppelinrox v6 supercharger script [U9RC12T6]Put a V6 SuperCharger +DIE-HARD Launcher in Your Pocket=She'll B Happy 2CU!
this phone can be called a phone and not a calculator anymore
all the best to my fellow G'zOne Commander users
 
Think I almost caused some issue with mine. Was playing around with init.d & A2SD and everything was still working fine (though I can't get A2SD to work properly the phone wasn't freaking out).

But then I wake up this morning and she is sitting there at the Initializing... section of boot up. Pull the battery, power on, same thing. Remove the SD card, power on, same thing.

Plug it into the PC and start up ADB, adb reboot recovery, restore NAND and its working again.

Had myself quite scared there for a second...

But now I need to figure out exactly what I did and how to avoid doing it...though I seriously want A2SD to operate on here.
 
Back
Top Bottom