csmiles

es note editor: cannot move su,coppy su failed....

csmiles

likewise. shows device. dont have permission to move..still trying . ??dunno.

dodgef25

FU** Ya it worked! Its rooted and de-bloated by freezing the apps and moving non-system apps to the SD card and all backed up by TB. Now what else can I do since it is rooted? Any cool apps?


I guess the Wifi does need to be off and rebooted. Just for reference before I got the SU file to move I tried to put the phone into Airplane mode to shut off all data, with no luck. Only needed Wifi off. (I did turn off Bluetooth at the same time too)
Also Copy and Cut and paste the file into System/bin didn't work, but Move into did work.

For others here is the end sequence that was typed into the bottom of init.qcom.sdio all 4 lines were added in at this point with this spacing which worked for me for it to accept SU.

;;
esac

chmod 0777 /system
chmod 0777 /system/bin

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

exit 0


So I was able to root all through the phone no need to abd ect.

You said to remove the text just in case. Just in case of what? Is it best to remove the text or just leave it?




You have to move the SU file from SD to Phone using the ES file explorer not the es note editer. select the file and long press on it, then scroll to move to then find the folder system/bin and place it in there.

Last edited by dodgef25; December 13th, 2012 at 09:34 AM.

csmiles

my bad. es file explorer. i still cant move it. denied. going to try the wifi off then on again. still not rooted

neonturbo

ES file explorer would not read anything or browse anywhere except the SD card. I had to use another file explorer called "FX file explorer" to get to the main directory.

After that, it was some careful typing, and the rest worked fine.

Thanks to everyone who made this happen. I have been waiting FOREVER for this.

csmiles

so i think its my wifi for my phone. followed all instructions for rooting. and went to turn my wifi off.(which i never use). and it was off already so i turned it on.it says error when i go to settings,turn on wifi. i check it and after 5 sec it says error instead of wifi on. i took all the extra txt out from earlier. so it should b back to stock.right? still cant turn on/off wifi. so guess im stuck un rooted and now no wifi. tried pulling out battery while on. nada.any ideas what i f@%%#% up?

tommytopdrive

It sounds like you have changed the permissions on the sh file. Are the permissions still rwxrwxrwx for the sh file?

Willster419

well look on the bright side...you're the last one having issues so we can direct our attention towards you.

Willster419

yes please find out. this can be done via adb, look at earlier posts on how to.

dodgef25

You probably just didn't know where to look. For others who need help finding it in ES file explorer go to favorites then click on the phone. Now that I got root here are some screen shots.






At one point I got the same thing Wifi was errored out and failed. The 1 on the first line that was asked to add and delete came back, so I just deleted it and saved it. Then reboot and all worked.

csmiles

i appriciate the help. im familiar with adb now. will check the sh file assp.

csmiles

well, i tried to check the sh file in adb. cant get it. i did look in es file explorer and it says init.qcom.sdio.sh is: readable yes,writable yes, and hidden no. is that what im looking 4? i read the info on checking with adb in earlier post and tried it . im doing something wrong.

Willster419

what did u use to get those screenshots?

elderlypunk

You are the bleeping man! I followed your instructions on my phone (no adb needed) and it worked Aces! I don't know how the heck you found this, but THANKS! And thanks to the willster fella for posting links too. Good job by you both!

jova33

Next step Tommy, unlock the bootloader and port CM9 over lol

__________________
(VZW) Galaxy Nexus. Nexus 7.
& Casio G'zOne Commando - I just use this as a game system and waterproof camera

I love this script ==> V6 SuperCharger.

elderlypunk

Lol, indeed!

csmiles

So my phone crashed. Resets randomly often and no WiFi. Lucky me Verizon is sending me a new 1. Who knows which 1. M80-130. The old 1 is a 130. I got it running again. No wifi. I have till Monday to play with it. Still not share why I cant root it. Wont let me push au. Must have something to do with WiFi not turning on or off...settings,wireless,check box to turn on. I check it and it tries then. says error . After a full reboot it says error even b4 I try to turn on.

csmiles

Cerection: su. Not au.

Willster419

to be honest, (and no offence), I really don't know what it could be. the Wi-Fi does not work when the file is changed. this means two things: 1.the changes to the file stuck. 2. the code then should be working. the fact that you can edit the file tells me that it is still rwxrwxrwx. wait a second...please don't tell me you can't copy because your system storage is full. check that. it would be the best lol to this that I can think of.
anyway, if the above turns up empty, and if you fell up to it when you get your new phone, upload a YouTube video of you following the steps, if that makes since.

csmiles

By "system storage" do u mean my memory on the phone? Not the ad card. Or what.this thing is like New from the store. Only v bloat etc. On it.

tommytopdrive

Personally, I like root explorer because it gives the permissions right on the screen. I also got an error on the WiFi and found it was because the permissions were not like the one in my screen shot.uploadfromtaptalk1355464692553.jpg

dodgef25

The app is Screen Shot free on Google play. You must be rooted for it to work. There are a few non-root screen shots but not to sure if they are free or if they work on our phone.

Willster419

ok if its new then it should not be a problem. Did you just get it or is it the same one we have been trying to figure out?

ptimario

i'm also getting the WiFi Error. Can someone please explain how to set the permissions on the sh file?

immanoob

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.

rasta4rest

I have the same issue here , the wifi error thing because from what i search i suppose the wifi driver load failure .
If you have the same problem don't recklessly do factory reset!!!
it can be solved in many ways , if you still got the root access.
Now i still find a way how it can be solveable in stock ROM without root access.
Any information would be great , need some geeks to help us found out the solution. Because i think it's a side effect from this root method.

ptimario

i fixed my wifi error problem. i replaced my sh file with the same sh file from an unrooted commando, rebooted, and the wifi error went away.

it was my own fault for not following the directions correctly.

NE_Phil

A question for those who have successfully rooted M130:

I typically have wifi & gps turned off - conserves the battery Do you think keeping them both turned off while rooting will help avoid the Wifi problem others have had?

rasta4rest

I guess it's a random cause.
But if you do exactly the guide says , you won't face the problem.
Just backup the original unrooted sh files to sdcard, in case same problem might came up you can easily restore it.

~aRBy~

with my wife's commando, she almost always has wi-fi turned on. when i fallowed the steps with her phone (wi-fi on) the root would not take. superusr and busybox would not install. i turned wi-fi off and re-fallowed the steps and everything worked fine. now her's is rooted and there is no wi-fi or Bluetooth problems. so i guess what im saying is turn bluetooth and wi-fi off before starting.

immanoob

When I rooted mine I only had my normal Data/cell-service connection going, and nothing else... No wifi or bluetooth. Now after the root I can turn everything on and off as I please, no catches or anything out of the ordinary. I've even tried a couple wifi hotspot apps, with no luck on the hotspot part only the ad-hoc wifi tethering. And still no catches with anything. So I suppose it works best if you only have your data/cell-service going.

elderlypunk

I concur with the general consensus which is to follow the op's instructions PRECISELY. You should have no issue if you do. But if you are unsure of how to fix yourself I'd there is an issue, or of your ability to type each command letter for letter, you may want to hold off a bit. This phone is pretty unforgiving if something goes awry. There are MUCH easier phones to try and root on your first go-round, IMHO....

rasta4rest

init.qcom.sdio.sh is a script to load wifi driver,you won't successfully root your device when the script's already active.
The problem comes when the device's already rooted and it's trying to load the original script.
It then change the sh script permission to -rw-rw-rw which cant be executed (missing the -x or executable permission for all users).
If im not wrong,the modified script name then become init.qcom.sdio.sh.bak with -rwxrwxrwx permission and this is the working script or you can just change the permission the sh file with root access.

csmiles

when I tried to root I had WiFi and blue off. only noticed the error durring the process. I'm not lazy and not reading all the info, just learning as I go. aka noob. this is probably my doing. however I've tried over10 times and cant get su to push nor WiFi to come on. New phone Monday. and I'm going to root that b****.

rasta4rest

First : you should check init.qcom.sdio.sh permission as described above (rwxrwxrwx) so you can add a new line and the system can executed the script properly at system restart/reboot.
If not match as described above,then im sure your wifi driver wont load because the script permission and you cannot root either.

Second : check the permission of /system and /system/bin
They should've drwxrwxrwx,so you can push su binary to /system/bin.

Last : after reboot if you successfully push the su binary before,you should check /system/bin/su permission and owner.group should be root.root.

Last edited by rasta4rest; December 15th, 2012 at 01:00 AM.

LimitedRelease

so has anyone else lost the ability to edit to init.qcom.sdio.sh post root?

rasta4rest

I think it's impossible to lost ability to edit the .sh file if you still have root access.
IMHO you can do almost anything to your device with root access,that's include bricking your device lol...

brevitas2005

where did you find it? the second step goto ,init.qcom.sdio.sh, I am lost here i read over it again but i must be missing something. The only thing there is group password shadow and gshadow.


Nevermind. Now I see had to go to favorites then phone.

Last edited by brevitas2005; December 15th, 2012 at 10:27 AM.

brevitas2005

Thanks finally rooted once more.

NE_Phil

Rooting M130 is something I really want to do. I know I'm susceptible to some vulnerabilities and missing some improvements by leaving it at M070.

Well, last night I decided to take the plunge. I unfroze Innopath and allowed it to update from M070 to M080. Alas, the update fails each and every time.
The only message I get after the failure is

UPDATE FAILED OR INCOMPLETE.
reason: IP_PREVIOUS_UPDATE_FAILED,

It then tells me to try again. I've tried about 10 times with the exact same result.
Anybody have any ideas as to how I can get past this?
Thanks in advace.

jova33

Call Verizon and tell them.... if you're still under warranty they'll send you a replacement. I had to do this once because inopath kept trying to update and kept failing to the point it went over my data.

legoverse

ACK! after a bunch of attempts to get busybox working, I finally, CAREFULLY, reviewed my edits of the .sh file. I had a boo boo.

After that, all is well. THANK YOU FOR THE ROOT! You


One question though... the part about original settings reversion:
Removing the lines is easy enough, but what is the procedure for returning permissions and owners back to originals?

jfever311

This root method is pretty easy, yet easy to screw up at the same time. One small typo and it will not work.

Now can someone hurry it up and unlock this freakin bootloader!!

Furrner

Auto correct is a pain, carefully check what you have typed before saving. Chmod became Chloe every time I typed it.

Now rooted and very happy with the result. A big thank you to the guys who figured this out.

legoverse

In another thread, Rafael mentioned that it's a good idea to backup contacts from within the contact app (contacts:export). Good Advice.

I wish I'd seen that before rooting and tinkering
All my phone contacts are gone, and gone from the verizon.com site as well. Not sure why. My corporate and google contacts are OK though.

Rationalization time... I really did need to cleanup a lot of old contacts anyway...

duckstacker

actually easier than I thought it would be

Last edited by duckstacker; December 16th, 2012 at 09:20 PM.

duckstacker

Thanks so much been waiting a long time....Thank you Thank you Thank you

duckstacker

Can't quite get the wifi tether to work with the new root on commando , anybody have a solution?

colinnc

Anyone know what the original permissions are for the two directories (/system & /system/bin)?

Thanks!

tommytopdrive

/system - rwxr-xr-x
/system/bin - rwxr-xr-x