After a week of gnashing of teeth and scratching of heads, I have a rooted M130 Casio Gzone Commando. I found a file (/system/etc/init.qcom.sdio.sh) that was rwxrwxrwx.
First, I made a backup of the file to my sd card.
Second, I turned wireless off
I then edited it with root explorer and added at the bottom just above "exit 0" the following lines:
chmod 0777 /system
chmod 0777 /system/bin
I edited it with root explorer by first adding the commands above then saved the file. I noticed it made a backup so I edited it again by adding a "1" after the "#!/system/bin/sh" on the first line and saved it again. Finally, I remove the "1" and saved again. This process may not be necessary, but sometimes I have seen where a backup might try to load.
After this I rebooted and found that the /system and /system/bin folders were now read/write without superuser.
I used adb to push su (I used the su file from zergRush, however you can use the one from the link below) to the /system/bin folder. Alternately you can do this from your phone by using a file explorer to copy/paste from your sd to the /system/bin folder
I checked with root explorer that su was, in fact, in the /system/bin folder. However, its permissions and ownership were incorrect.
I went back to the /system/etc/init.qcom.sdio.sh file and below the lines I added earlier I added the following:
I saved the file three times like above and then rebooted.
I went into root explorer and verified the ownership and permissions of su. They were correct.
After that I installed superuser and busybox installer from the play store.
The M130 was officially rooted.
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.
Finally, I updated the recovery to GNMs all in one recovery for the commando from All In One Recovery Thread
*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.
I just did a factory reset to see if I could reproduce what I have done, however, the file mentioned above is already 0777, as well as su and busybox are already installed.
so this will be kind of hard to figure out what exploit opened up that file to 0777. I need to do some more research and backtracking. I do have voice on the phone, however, dont have data (I was able to get VZ to assist with provisioning the phone, and they did say my area has data outages, but it has been a while now so still checking on that). Once again it could have been because I was messing with QPST.
I think there was an exploit for the droid bionic that might have done it, or possibly a chinese one called kingroot.
By the way for a screen shot for proof of root, what is the best way to do that?
Last edited by tommytopdrive; December 9th, 2012 at 08:17 AM.
After a week of gnashing of teeth and scratching of heads I think I have a rooted M130 commando. I still have to find out exactly what allowed it, but while trying many different exploits, I found a file (/system/etc/init.qcom.sdio.sh) that was rwxrwxrwx. I edited it to add chmod for /system and /system/bin, pushed su and then edited it to chown su to root. I had to (after making a back up) restore nv with QPST several times to get the results (that part needs dissecting to to see why). After that installed superuser.apk and busybox.
And finally updated the recovery to GNMs all in one.
Now, We just need to do some testing to find out at what point the file came avaliable as 0777.
The only issue I have encountered (which could have been due to my own messing around) is that the phone is connected to the verizon network, but I dont have data, and when I try to make a call I get a recording to call support. I am heading over to verizon now to see if all they need to do is reprogram the phone to connect, hopefully without a hard reset.
So this may be a slight noob question, but could one of you explain what chmod is? and with that, what exactly the file is and how it works to root the phone? Im sure i can say on behalf on all the noobs hungry for root, we would like to know
The Following User Says Thank You to Willster419 For This Useful Post:
How do I use chmod? / What is chmod?
It has some nice information on what chmod actually is.
Just some basic info for people from the site:
chmod (change mode)
permissions for the owner, the group and the world, respectively
digits include 4 (read only), 5 (read and execute), 6 (read and write) and 7 (read, write and execute).
so 777 means that owner, group and world have read write and execute permissions.
hope this lifts some of the fog of confusion
I am a little curious, can anyone open up /system/etc with any file explorer (i use root explorer as it will let you view quite a few things even when not being rooted) and see what the permissions are for the file i mentioned in my first post on a unrooted commando.
After a week of gnashing of teeth and scratching of heads I think I have a rooted M130 commando. I still have to find out exactly what allowed it, but while trying many different exploits, I found a file (/system/etc/init.qcom.sdio.sh) that was rwxrwxrwx. I edited it to add chmod for /system and /system/bin, pushed su and then edited it to chown su to root. I had to (after making a back up) restore nv with QPST several times to get the results (that part needs dissecting to to see why). After that installed superuser.apk and busybox.
And finally updated the recovery to GNMs all in one.
Now, We just need to do some testing to find out at what point the file came avaliable as 0777.
The only issue I have encountered (which could have been due to my own messing around) is that the phone is connected to the verizon network, but I dont have data, and when I try to make a call I get a recording to call support. I am heading over to verizon now to see if all they need to do is reprogram the phone to connect, hopefully without a hard reset.
ok so i have the file open now, (already backuped my stuff), and am trying to edit it. I just have 2 questions and then i believe im all set.
1. Where did you put the chmod? In the begining before the arg=$1, or later?
2. Did you use the # symbol, or $, or none at all?
thanks for the good info by the way. Hope to root soon!
I am a little curious, can anyone open up /system/etc with any file explorer (i use root explorer as it will let you view quite a few things even when not being rooted) and see what the permissions are for the file i mentioned in my first post on a unrooted commando.
yes you can. You have to change a few settings, but ES File Explorer will let you view files and will also tell you if they are readable and writable.
ok so i have the file open now, (already backuped my stuff), and am trying to edit it. I just have 2 questions and then i believe im all set.
1. Where did you put the chmod? In the begining before the arg=$1, or later?
2. Did you use the # symbol, or $, or none at all?
thanks for the good info by the way. Hope to root soon!
What are your permissions for /system/etc/init.qcom.sdio.sh?
i tried adding chmod in what i think is proper syntax into the file, and nothing has happened. looked to see if the directories that i typed were writable, and they were not. also i tried running it from adb and it says permission denied. getting a little spotty here...please help me out...
i tried adding chmod in what i think is proper syntax into the file, and nothing has happened. looked to see if the directories that i typed were writable, and they were not. also i tried running it from adb and it says permission denied. getting a little spotty here...please help me out...
until that file is writable, you wont be able to edit it. You can check the permissions by using ES File explorer or adb. In adb from the $ type:
cd /system/etc then press enter
ls -l then press enter
that will tell you the permissions of all the files in that folder.
If you can modify init.qcom.sdio.sh and push it to the /systerm/etc folder or edit it directly from a file explorer in android, then you can add the commands at the very bottom (just above "exit 0") REMEMBER: as you are messing with the file system you take all responsibility, etc, etc, etc.
You would add the following:
chmod 0777 /system
chmod 0777 /system/bin
I would push it twice or edit it twice with file explorer (I actually edited it three times by first adding the commands -save. Then added a "1" after the "#!/system/bin/sh" on the first line - save. Finally remove the "1" and save again.) as it makes a backup and might try to load the backup.
After this reboot your phone and see if the new commands stick and make your /system and /system/bin writable. It might work, but I think we will have to take more steps to envoke the file to execute.
Last edited by tommytopdrive; December 9th, 2012 at 09:46 PM.
it did not work, but the changes did stick. I can not turn on my WiFi, but when I put the original file in, I can turn it on. am I doing something wrong?
it did not work, but the changes did stick. I can not turn on my WiFi, but when I put the original file in, I can turn it on. am I doing something wrong?
Try to modify the file from the file explorer with above procedure with the wifi off. Try rebooting still having wifi off. Reboot and turn wifi on.
Try to modify the file from the file explorer with above procedure with the wifi off. Try rebooting still having wifi off. Reboot and turn wifi on.
no good, i think. i need someone to confirm if the /system/ directory was writable on the origional non-chmodded commando. if no, then it did something. if yes, then the file is not activating.
no good, i think. i need someone to confirm if the /system/ directory was writable on the origional non-chmodded commando. if no, then it did something. if yes, then the file is not activating.
I think I have it figured out, but I need to know one thing. Is the file /system/etc/init.qcom.sdio.sh in a stock non rooted casio commando with M130 set up with the permissions rwx rwx rwx (0777). Can someone verify this for me?
If so, then we have some good news as the process will not be too bad.
Also after fixing my mess up. I have voice and data again...so this baby is fully rooted and working good now!
I think I have it figured out, but I need to know one thing. Is the file /system/etc/init.qcom.sdio.sh in a stock non rooted casio commando with M130 set up with the permissions rwx rwx rwx (0777). Can someone verify this for me?
If so, then we have some good news as the process will not be too bad.
Also after fixing my mess up. I have voice and data again...so this baby is fully rooted and working good now!
I don't know about any special permissions, I don't think there are, but the file IS rwx rwx rwx. so 0777 it is.
Last edited by Willster419; December 10th, 2012 at 10:04 AM.
I can confirm on my non rooted commando that file is writeable. Inserted the chmod commands into the file, adding one for the /app directory, and I can delete .apk files from the app directory as well as copy them from the sdcard back to the app directory. I can also write a random sound recording i had laying on the sdcard to the app directory. Now .. how to root fully so I can uninstall these abominations of bloatware that was included ive been having to look at for a year now.
Also It did not affect my wireless at all, I can enable and disable it and connect to wireless. Data is working as well.
Last edited by nmewarlok; December 10th, 2012 at 12:35 PM.
Reason: Additional Information
So after you added the chmod and rebooted, your /system and /system/bin file became 0777? If so then you can adb push su to the /system/bin folder. After that in the same file you chmod you can add:
So after you added the chmod and rebooted, your /system and /system/bin file became 0777? If so then you can adb push su to the /system/bin folder. After that in the same file you chmod you can add:
I can safley say that out of all the testing, my m130 Casio commando is rooted. I have had the superuser request, and stuff is good. Thanks TommyTopDrive for letting me be like your "beta tester" and providing me with this great information. It does work people.
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, "
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."
Will let know in a few hours. Have an appointment I must attend to in about 15 mins.
drwxrwxrwx root root 2012-10-20 02:32 system
drwxrwxrwx root shell 2012-10-20 02:32 bin
I pushed root and then redid the file to chmod and own it, and now have a # prompt instead of the $ prompt. Superuser and busybox both installed like a champ. Looks like its working to me. Thank You for discovering this permissions flaw in a executable script!
drwxrwxrwx root root 2012-10-20 02:32 system
drwxrwxrwx root shell 2012-10-20 02:32 bin
I pushed root and then redid the file to chmod and own it, and now have a # prompt instead of the $ prompt. Superuser and busybox both installed like a champ. Looks like its working to me. Thank You for discovering this permissions flaw in a executable script!
Would like to report another successful root on a co workers Verizon Commando. That is 2 so far ... with 2 more to go.
Still have my old commando laying around. Might have to try this tonight! Too bad there are no roms if it was any smoother I would go back to it since its way tougher than this droid 3. I know it wont compare to the droid 3 though. May just have to play around with it though
Device(s): Casio Commando, rooted.
Asus Transformer Prime, unlocked & JB rom
Carrier: Not Provided
Thanks: 31
Thanked 68 Times in 43 Posts
Nice work!
I stayed rooted at M70.......so I won't be using it, but I can certainly sympathize with those who never rooted back when I did.....or never had this early a version.
Device(s): Casio Commando C771
Motorola Razr XT 912 - rooted
Previous:
HTC Incredible OG - CM
Carrier: Verizon Wireless
Thanks: 0
Thanked 0 Times in 0 Posts
I had my commando rooted under the M80. Superuser.apk is still located on the system/app directory and it will not give my access to delete or uninstall the file. Could this be affecting the "chmod..." Added to the directory?
After adding these commands in the file previously mention I'm having no luck with root access...
If so how could I get rid of the SU.apk file without having root access?
these are the files y'all need in order to root, besides the USB phone drivers which are on another forum post in the "all things root" area.
had to move files: http://d-h.st/Z21
Last edited by Willster419; March 26th, 2013 at 03:43 PM.
The Following 8 Users Say Thank You to Willster419 For This Useful Post:
I would use adb to install su, however, I would install superuser.apk and busybox installer from the play store. I would also after rooted remove the chmods and chown from the file. I would also change the permissions for the /system and /system/bin back to there originals.
The Following User Says Thank You to tommytopdrive For This Useful Post:
you can do it under ubuntu. You have to install the android sdk as the adb drivers are automatically installed. You might even be able to put the su file into your sd card and copy over to /system/bin with a good file explorer downloaded from the play store. You can make the changes to the /system/etc/init.qcom.sdio.sh file with the edit function of most file explorers as well.
56Likes
M130 Rooted!
