Root M130 Rooted!

[Willster419]

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.

 

[tommytopdrive]

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!

 

[~aRBy~]

that file is
readable: Yes
writable: Yes
Hidden: No

That what it says for me in ES file explorer

 

[jfever311]

This is exciting!

 

[Willster419]

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.

 

[nmewarlok]

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.

 

[tommytopdrive]

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:

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

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

when you return on the ls -l the screen will scroll fast. use your page up button to search for su and see its permissions.

If all goes well, then you can install superuser.apk and install busybox...oh, and that means your rooted.

 

[nmewarlok]

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:

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

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

when you return on the ls -l the screen will scroll fast. use your page up button to search for su and see its permissions.

If all goes well, then you can 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.

 

[Willster419]

It works! chmod works! before i was just looking in es file explorer, but then i tried to move stuff and IT WORKS!!! rootin' time! :thumb:

 

[jfever311]

Yay!!!!!

 

[Willster419]

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.

 

[Willster419]

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. Turn off your WiFi and 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!

 

[nmewarlok]

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!

 

[nmewarlok]

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.

 

[tsp_2177]

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

 

[Rafael]

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.

Well done!

 

[jfever311]

7. Push su to /system/bin

What the heck does this mean, and how do I do it?

 

[jfever311]

I though this was all done via the phone. Do I have to hook it up to my computer to do this?

 

[Bigtruxz]

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?

Thanks in advance

 

[Willster419]

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://1drv.ms/1i99x1I

 

[tommytopdrive]

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.

 

[Willster419]

look what i found...
had to move files:
http://d-h.st/xpK drivers_C771_Windows.zip

 

[tommytopdrive]

7. Push su to /system/bin

What the heck does this mean, and how do I do it?

Search the forums as there is ample knowledge on using adb and how to push/pull files to/from your computer to the phone.

 

[jfever311]

I'm running ubuntu, so I think I need to do this another way.

 

[tommytopdrive]

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.