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

Root M130 Rooted!

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.

Just wanted to say thank you. Followed this exactly and now I have root access!

Now what to remove first... :)
 
So I have been having trouble with my wifi since I rooted my commando. The log is telling me that it is trying to access a file sys/class/usb_composite/acm_modem/enable. I looked for it in my file manager and the folder acm_modem didn't exist. If anything I am going have to reinstall the whole frickin image. Or does any one have a better idea? I thinking of rebuilding the folder and missing files but I can't mkdir any where in the /sys directory. So where to go from here?

logcat tells you it cant find the file because it was never there. if you get an error with your wifi it is because either you accidentally changed parameters in the sdio file you modified to get root or the permissions and/or ownership are not correct.

the ownership and permission of the file should be:
init.qcom.sdio.sh system.system rwxrwxrwx
 
So I have been having trouble with my wifi since I rooted my commando. The log is telling me that it is trying to access a file sys/class/usb_composite/acm_modem/enable. I looked for it in my file manager and the folder acm_modem didn't exist. If anything I am going have to reinstall the whole frickin image. Or does any one have a better idea? I thinking of rebuilding the folder and missing files but I can't mkdir any where in the /sys directory. So where to go from here?

logcat tells you it cant find the file because it was never there. if you get an error with your wifi it is because either you accidentally changed parameters in the sdio file you modified to get root or the permissions and/or ownership are not correct.

the ownership and permission of the file should be:
init.qcom.sdio.sh system.system rwxrwxrwx
.Thank you Tommythe ownership was set to root.root I changed it to system.system but I get no wifi love yet. I am just wondering why the log is telling me that the file exists. Thank you for the help trouble shooting. Do you think this exploit would work on an LG Enlighten, the permission are set the same on the init.qcom.sdio.sh file. This is a cool exploit and it might work on any gingerbread. I am sure I screwed something up. Maybe I removed the wrong system file thinking it was bloatware. I am going to keep working on this.
 
Awesome work guys! I am up to step 7 but can not find the su file anywhere. where do I look? I have opened all the files using ES file Explorer. update, opened the zip file with su to desktop then pushed it.
 
I used dropbox to move su from my desktop to sd card then moved it to system bin. root checker says I do not have access yet. Any suggestions?
 
Done!!!!rooted Casio! Thanks for all the great info. I used drop box to move the file around and that made it very simple. one question, what do I have to do to be able to uninstall all the bloatware apps. Deleting through the app manager is still not letting me.
 
.Thank you Tommythe ownership was set to root.root I changed it to system.system but I get no wifi love yet. I am just wondering why the log is telling me that the file exists. Thank you for the help trouble shooting. Do you think this exploit would work on an LG Enlighten, the permission are set the same on the init.qcom.sdio.sh file. This is a cool exploit and it might work on any gingerbread. I am sure I screwed something up. Maybe I removed the wrong system file thinking it was bloatware. I am going to keep working on this.

i have done alot of tweaking with the system and apart from messing with the sdio file, I have found it very difficult to mess up the wifi. However, I did install GNM recovery and made a backup as soon as i rooted so I could always get back to square one.

I am sure this exploit can work on just about any android as long as you can write in the file.
 
also, i am getting the same error on finding the modem file. this is because the commando is routing things a bit differently than the norm, so it appears when comparing different init.rc and build.props
 
So where do you think folks with this problem should go from here. I was a fool and didn't back up my firmware...not a mistake I will do again. I am wondering if I will wait for a custom rom to fix my problem. I am glad to know I am not the only one with this problem
 
Just add some more information..
After Install Superuser.apk and busybox from playstore [they should be the latest version available],Superuser try to automatically check update for su binary. It's ver. 3.1.1 this update of su binary files makes the superuser acces freeze up or taking too long. I guess su binary ver. 3.1.1 doesnt seem to work fine with M110 update.
Does Anyone get the same issue for build M130 ?
if so just repeat the same step as above guide to re-root with su binary provided by Willster419 and dont auto update that binary files.
I ran into the same problem.
 
Thank you for posting this information! I am a super-noob, and just started reading up on rooting yesterday. You can imagine my sense of good fortune in finding this thread (and not having to wait a year to be able to root my phone). Thanks again to tommytopdrive and Willster419 for your invaluable contributions. Also, I must thank immanoob for the detailed step-by-step. That was very helpful for this super-noob.

Now, if you don't mind, a few clarification questions:
1) I should not update the su file correct? (I have received the notification that has been referenced earlier in the thread that the file is outdated.)

2) tommytopdrive, you mentioned in your original post: "As a precaution, I removed the lines I added in the /system/etc/init.qcom.sdio.sh file and returned the permissions and owners for /system and /system/bin back to their original settings." How do you change the permissions?

And now...to figure out the GNM All in One Recovery and Titanium Backup! (From what I gather, those are essentials...right?)

Thanks again!
 
Thank you for posting this information! I am a super-noob, and just started reading up on rooting yesterday. You can imagine my sense of good fortune in finding this thread (and not having to wait a year to be able to root my phone). Thanks again to tommytopdrive and Willster419 for your invaluable contributions. Also, I must thank immanoob for the detailed step-by-step. That was very helpful for this super-noob.

Now, if you don't mind, a few clarification questions:
1) I should not update the su file correct? (I have received the notification that has been referenced earlier in the thread that the file is outdated.)

2) tommytopdrive, you mentioned in your original post: "As a precaution, I removed the lines I added in the /system/etc/init.qcom.sdio.sh file and returned the permissions and owners for /system and /system/bin back to their original settings." How do you change the permissions?

And now...to figure out the GNM All in One Recovery and Titanium Backup! (From what I gather, those are essentials...right?)

Thanks again!

i would first install titanium and backup all apps. then use the GNM thread to install the recovery to do a nandoid backup (similar to making a windows backup).
after this, using an android file explorer like root explorer or es file explorer, remove the text you entered into the sdio file. not sure in es file explorer, but in root explorer you can see the permissions of the file while browsing the files. to change permissions or ownership you would long press the file in question and from the popup, select the option you want (screenshot and file permissions, etc are located in this thread).

after all that then you can do prettymuch what you want, apart from following in willsters footsteps, ie wiping and NOT flashing a nandroid backup (NOT RECOMMENDED). these forums, as well as xda have all the info. it just takes time and lots of reading. i may sound mean, but i have spent hours researching and usually find what i am looking for.
 
Yes I get an error in the wireless settings. I will dump my log into a text file and post it later today so you can see the errors I am getting in there.
 
I know with other devices it is possible to boot into a custom recovery without having that recovery on the device. Don't know if this is possible with the commando, I just remember what a pain in the ass it was for me to get the stock recovery back on to restore the device to stock.

Also, has anyone tried SuperSU instead of superuser?
 
.

Also, has anyone tried SuperSU instead of superuser?


Post #178

I did have an issue using Superuser and getting the binary update error that never updated and Busybox crapped out during install using the installer or direct install.

I deleted Superuser and tried SuperSU and no binary error and Busybox updated to the current version / level.

Superuser update fix did not fix anything for me either.
Use SuperSU
 
i would first install titanium and backup all apps. then use the GNM thread to install the recovery to do a nandoid backup (similar to making a windows backup).
after this, using an android file explorer like root explorer or es file explorer, remove the text you entered into the sdio file. not sure in es file explorer, but in root explorer you can see the permissions of the file while browsing the files. to change permissions or ownership you would long press the file in question and from the popup, select the option you want (screenshot and file permissions, etc are located in this thread).

after all that then you can do prettymuch what you want, apart from following in willsters footsteps, ie wiping and NOT flashing a nandroid backup (NOT RECOMMENDED). these forums, as well as xda have all the info. it just takes time and lots of reading. i may sound mean, but i have spent hours researching and usually find what i am looking for.

Thank you very much for the guidance! I don't think you sound mean, and I know I have several hours of reading and such ahead of me. I was looking for guidance on "best practices", and you kindly provided it. Thanks again! :)
 
Also, the V6 SuperCharger helped significantly with my commando previously.
Also check http://forum.xda-developers.com/showthread.php?t=1987032
There's a lot of stuff I don't understand, but the people seeing the biggest differences have older devices. Start at the end of the thread and go back, people have posted updated versions of this tweak as the author of the OP seems to have disappeared.
Zepp has also implemented something that has the same effect into his unreleased kick ass kernelizer, so watch his thread too.
 
I know with other devices it is possible to boot into a custom recovery without having that recovery on the device. Don't know if this is possible with the commando, I just remember what a pain in the ass it was for me to get the stock recovery back on to restore the device to stock.

Also, has anyone tried SuperSU instead of superuser?

To revert to old recovery just change the name of the backup recovery made by gnm to the same as the new one, place it in the flash folder on your memory card and repeat the steps you did to flash the gnm recovery. Worked like a champ for me.
 
So I have been having trouble with my wifi since I rooted my commando. The log is telling me that it is trying to access a file sys/class/usb_composite/acm_modem/enable. I looked for it in my file manager and the folder acm_modem didn't exist. If anything I am going have to reinstall the whole frickin image. Or does any one have a better idea? I thinking of rebuilding the folder and missing files but I can't mkdir any where in the /sys directory. So where to go from here?

logcat tells you it cant find the file because it was never there. if you get an error with your wifi it is because either you accidentally changed parameters in the sdio file you modified to get root or the permissions and/or ownership are not correct.

the ownership and permission of the file should be:
init.qcom.sdio.sh system.system rwxrwxrwx

to be honest i would just get a nandroid backup of /system and not deal with it at all. i can give you mine if you want, its rooted and has no wifi problems. btw i was able to combine parts from my phone and a deactivated commando of my friend to make one for myself. i call him, "frankendroid". :)
 
New here today because of this thread :D

WOW thanks for your time spent and thread / posts
Finally rooted <insert 2 thumbs up
Whats should the chmod be set back to?
and is it normal that su wants to update to 3.1.1 but it fails
even tho I took the edit out of /system/etc/init.qcom.sdio.sh file
I manually added the su to the bin the when rooting the phone..
do I have to grab the newest su and manually add again ?

once again thanks for your time and efforts
 
odd as i am running 3.1.1 with no issues on m130.
I redid the process and this time did not update su with superuser app and it worked fine. Note I did get an error that said to put a check in Debug box in settings and it rooted again. so, either the debug box or not updating did it.
 
Back
Top Bottom