Go Back   Android Forums > Android Phones > Casio G’zOne Commando > Commando - All Things Root

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

Like Tree64Likes

test: Reply
 
LinkBack Thread Tools
Old December 28th, 2012, 04:04 PM   #201 (permalink)
Senior Member
 
jova33's Avatar
 
Join Date: Oct 2011
Location: El Paso
Posts: 1,567
 
Device(s): Samsung Galaxy Nexus VZW Casio G'zOne Commando
Carrier: Not Provided

Thanks: 30
Thanked 181 Times in 152 Posts
Default

I'm going to report this exploit. Make sure it gets patched in the next update.
bestaudioguy likes this.

__________________
(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.
jova33 is online now  
Reply With Quote
sponsored links
Old December 28th, 2012, 05:23 PM   #202 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

How would I unroot it using this process? Sorry if this has already been said. :P

I'm new to this all, to unroot it, would I just, like, hit the default button on the phone?
Blazewalker is offline  
Last edited by Blazewalker; December 31st, 2012 at 11:31 AM.
Reply With Quote
Old December 29th, 2012, 05:09 PM   #203 (permalink)
Member
 
Join Date: Jan 2012
Location: Branchburg
Gender: Male
Posts: 116
 
Device(s): Casio Commando
Carrier: Verizon

Thanks: 11
Thanked 5 Times in 5 Posts
Default Upgrade to M130

Might seem like a dumb question, but I currently have a rooted M080 phone. Now that there is a root for the M130, would it make sense to un-root, do the update to M130 and re-root?
Is there anything to gain by making the upgrade to M130? Features, etc??

Thanks
MikeDilligaf likes this.
bestaudioguy is offline  
Reply With Quote
Old December 29th, 2012, 06:23 PM   #204 (permalink)
New Member
 
Join Date: Sep 2011
Posts: 13
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 2 Times in 1 Post
Default Same question

Quote:
Originally Posted by bestaudioguy View Post
Might seem like a dumb question, but I currently have a rooted M080 phone. Now that there is a root for the M130, would it make sense to un-root, do the update to M130 and re-root?
Is there anything to gain by making the upgrade to M130? Features, etc??

Thanks

Ditto - although I'm running M050.
MikeDilligaf is offline  
Last edited by MikeDilligaf; December 30th, 2012 at 04:25 AM.
Reply With Quote
Old December 30th, 2012, 09:55 AM   #205 (permalink)
Member
 
Join Date: Jan 2012
Location: Branchburg
Gender: Male
Posts: 116
 
Device(s): Casio Commando
Carrier: Verizon

Thanks: 11
Thanked 5 Times in 5 Posts
Default

Quote:
Originally Posted by MikeDilligaf View Post
Ditto - although I'm running M050.
Not sure I understand your answer. I guess it really was a dumb question?
I should just leave well enough alone?

Also asked the morons at Verizon if they knew of the new Casio coming out, and of course they were clueless. I heard the FCC is testing it now!
bestaudioguy is offline  
Reply With Quote
Old December 30th, 2012, 11:20 AM   #206 (permalink)
New Member
 
Join Date: Sep 2011
Posts: 13
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 2 Times in 1 Post
Default Same question as you

Originally Posted by bestaudioguy
Might seem like a dumb question, but I currently have a rooted M080 phone. Now that there is a root for the M130, would it make sense to un-root, do the update to M130 and re-root?
Is there anything to gain by making the upgrade to M130? Features, etc??

Thanks




Quote:
Originally Posted by bestaudioguy View Post
Not sure I understand your answer. I guess it really was a dumb question?
I should just leave well enough alone?

Also asked the morons at Verizon if they knew of the new Casio coming out, and of course they were clueless. I heard the FCC is testing it now!

I have the same question as you ... looking for others to answer it
MikeDilligaf is offline  
Reply With Quote
Old December 30th, 2012, 04:58 PM   #207 (permalink)
Junior Member
 
dodgef25's Avatar
 
Join Date: Aug 2011
Posts: 79
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 7 Times in 6 Posts
Default

For those asking if it is worth it to upgrade from m50 or m80.

It is only worth it if you froze your stock apps instead of uninstalling them. The update won't work if you uninstalled the apps even if install all of them back.

The only way to upgrade if you uninstalled apps at one point is to call Verizon to get them to send you a replacement phone for it failing to upgrade. Rooting is against their rules and if they find out it was rooted they will charge you full price for it.

I had mine rooted back with M50 and it would not update to M80 since I uninstalled some apps and reinstalled them but wouldn't update. So I called them and they sent a replacement with no problem with them, they never found out I had root once I unrooted it.
dodgef25 is offline  
Reply With Quote
Old December 30th, 2012, 06:28 PM   #208 (permalink)
New Member
 
Join Date: Dec 2012
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default init.qcom.sdio.sh

SO I made a copy of init.qcom.sdio.sh and saved it to my card. I preformed all the steps and rooted my phone. Sweet stuff. I reset the permissions and replaced the untouched version of init.qcom.sdio.sh. From there my Wi-Fi is having an error. logcat tells me that it is my init.qcom.sdio.sh that is gumming up the works. DOes any one have a solution for this? I might have screwed the original and will have to find a new one. Lame.

Also what should the original owners be set as before chown?
professerslime is offline  
Reply With Quote
Old December 30th, 2012, 10:04 PM   #209 (permalink)
New Member
 
Join Date: Apr 2012
Location: South Jersey
Posts: 2
 
Device(s): Casio Commando
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Thanks. Havent a clue how to do anything with computers code-wise but managed to do this will little difficulty. For anyone getting stuck at putting the SU in the system/bin/ make sure your wifi is disabled. Goodbye VZW
Sleepy42 is offline  
Reply With Quote
Old December 30th, 2012, 10:10 PM   #210 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 0 Times in 0 Posts
Default

awesome. awesome. awesome. add me to the list. thanks guys.
generutledge is offline  
Reply With Quote
sponsored links
Old December 31st, 2012, 09:04 AM   #211 (permalink)
Senior Member
 
Join Date: Feb 2012
Location: New Hampshire
Gender: Male
Posts: 552
 
Device(s): Archos 43 IT (dead), Casio Commando(s) (C771), Casio COmmando 4g
Carrier: the big bad "V"

Thanks: 43
Thanked 143 Times in 70 Posts
Willster419
Question A little help, please...

so i have done the equivalent of uninstalling the windows operating system on a computer. On my commando, the entire /system folder is wiped, thanks to GNM recovery. So from this point, i can power on my phone to see a casio virtual serial port and a usb composite device. is there a way to transfer the /system folder back to it using that? no adb, by the way, thats in the /system folder. Is there some sort of "download mode" or way to get into the recovery, without the hard reset as that does not work? or am i going to have to go to the big bad v on this one?
any input is appreicated, thanks in advance
Willster419 is online now  
Reply With Quote
Old January 1st, 2013, 11:31 AM   #212 (permalink)
New Member
 
Join Date: Jan 2013
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

Awesome! Thanks to everyone, I am rooted, and Now I Can Clean up my phone!! My previous phones have all went the way of the water gods, meaning they all have somehow taken a dunk in the pond so to speak and died a hideous death. This phone stands up to me and now can be clean and shiny (on the inside)! Again thanks!
mickeythered is offline  
Reply With Quote
Old January 1st, 2013, 02:27 PM   #213 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by Blazewalker View Post
How would I unroot it using this process? Sorry if this has already been said. :P

I'm new to this all, to unroot it, would I just, like, hit the default button on the phone?

I'm told that I shouldn't root it unless I can unroot it for insurance reasons so I really would like some manner of reply. I'm very new to this so... lol even if it's obvious I'm probably not noticing it.
Blazewalker is offline  
Reply With Quote
Old January 1st, 2013, 02:37 PM   #214 (permalink)
Senior Member
 
Join Date: Nov 2009
Location: Virginia Beach, VA
Posts: 523
 
Device(s): Verizon S4 16gb, rooted, TWRP, custom ROM. Asus Transformer Prime, unlocked & Energy ROM.
Carrier: Not Provided

Thanks: 31
Thanked 71 Times in 43 Posts
Default

I would bet that verizon, or the insurer, would void your warranty if they knew you rooted it.
You can ask them to clarify warranty coverage.

So......you are asking for assurance that you will be able to commit fraud if you screw up your phone?

I have rooted both my android devices with the knowledge that my warranty is now void.
Its a choice I made.
Rafael is offline  
Last edited by Rafael; January 1st, 2013 at 02:40 PM.
Reply With Quote
Old January 1st, 2013, 03:26 PM   #215 (permalink)
Junior Member
 
Join Date: Aug 2012
Location: USA
Posts: 59
 
Device(s): Commando 4G
Carrier: Verizon

Thanks: 4
Thanked 10 Times in 7 Posts
Default

If any insurance coverage you might have covers mechanical damage I would simple drive over it with the car. The last thing I would want to do is hand them a rooted phone becasue the odds are against them covering that IF they figure it out.
JKH62 is offline  
Reply With Quote
Old January 1st, 2013, 03:30 PM   #216 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2012
Posts: 51
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 65 Times in 9 Posts
Default

SO I made a copy of init.qcom.sdio.sh and saved it to my card. I preformed all the steps and rooted my phone. Sweet stuff. I reset the permissions and replaced the untouched version of init.qcom.sdio.sh. From there my Wi-Fi is having an error. logcat tells me that it is my init.qcom.sdio.sh that is gumming up the works. DOes any one have a solution for this? I might have screwed the original and will have to find a new one. Lame.

Also what should the original owners be set as before chown?


Check the permissions of the file. Should be rwxrwxrwx.
tommytopdrive is offline  
Reply With Quote
Old January 1st, 2013, 03:46 PM   #217 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2012
Posts: 51
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 65 Times in 9 Posts
Default

so i have done the equivalent of uninstalling the windows operating system on a computer. On my commando, the entire /system folder is wiped, thanks to GNM recovery. So from this point, i can power on my phone to see a casio virtual serial port and a usb composite device. is there a way to transfer the /system folder back to it using that? no adb, by the way, thats in the /system folder. Is there some sort of "download mode" or way to get into the recovery, without the hard reset as that does not work? or am i going to have to go to the big bad v on this one?
any input is appreicated, thanks in advance


I think you should start a new thread with this one. If you dont need the phone right away we might be able to do some investigating to try to revive your now bricked casio commando.
tommytopdrive is offline  
Reply With Quote
Old January 1st, 2013, 06:35 PM   #218 (permalink)
New Member
 
Join Date: Oct 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 0 Times in 0 Posts
Default

This might sound extremely dumb,but i can't get past line two in ten steps. Where is that in the file explorer? How do I access it? I have checked every where i could see and couldn't find it. It says local sd card. This is all new to me. What am i doing wrong????
tsevard is offline  
Reply With Quote
Old January 1st, 2013, 07:31 PM   #219 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by Rafael View Post
I would bet that verizon, or the insurer, would void your warranty if they knew you rooted it.
You can ask them to clarify warranty coverage.

So......you are asking for assurance that you will be able to commit fraud if you screw up your phone?

I have rooted both my android devices with the knowledge that my warranty is now void.
Its a choice I made.
Seriously, guy. Why the hostility? Get the stick out of your ass and take care to notice that I was just stating my grasp of the reason they were telling me I shouldn't root it unless I can unroot it. Which I explained simply in the hopes that someone would take a moment to reply to the question with, at the very least, a "you can't." Now chill out.
Blazewalker is offline  
Reply With Quote
Old January 1st, 2013, 07:43 PM   #220 (permalink)
Dr. Feelgood
 
Rxpert83's Avatar
 
Join Date: Aug 2011
Location: MN
Gender: Male
Posts: 16,109
 
Device(s): Nexus 7, Nexus 5
Carrier: Sprint

Thanks: 13,634
Thanked 11,788 Times in 6,789 Posts
Default

Bricking your device and then getting insurance on it is fraud and that's why rooting has such a bad rap with insurance companies.

However, I see absolutely nothing wrong with using your warranty to replace defective hardware that was not caused by the device being rooted.

I've done that myself
Rxpert83 is online now  
Last edited by Rxpert83; January 1st, 2013 at 07:48 PM.
Reply With Quote
sponsored links
Old January 1st, 2013, 07:58 PM   #221 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

lol I never even stated a concern about bricking it, I'm not too worried about that. I was talking about using it to replace defective or physically broken hardware through the warranty. You folks are making some pretty crazy assumptions. :P

PRETTY sure you couldn't unroot a bricked device anyway, so that would be a moot question, wouldn't it?

and even so, I don't see a reason to get so... seemingly angry about it. not like you'd be sued for it.
Blazewalker is offline  
Last edited by Blazewalker; January 1st, 2013 at 08:01 PM.
Reply With Quote
Old January 1st, 2013, 08:03 PM   #222 (permalink)
Senior Member
 
Join Date: Feb 2012
Location: New Hampshire
Gender: Male
Posts: 552
 
Device(s): Archos 43 IT (dead), Casio Commando(s) (C771), Casio COmmando 4g
Carrier: the big bad "V"

Thanks: 43
Thanked 143 Times in 70 Posts
Willster419
Red face ok...

well i just bought one off ebay, cause warrenty being void and crap, the motherboard of the commando is in front of me and looks preety cool, but no way to take out the internal storage and screw with it...oh well. Everything else works, so if any of you guys want parts send me an email to willsterdudeyo@gmail.com and we'll deal
I can give anything exept the motherboard and stuffs on it.
Willster419 is online now  
Reply With Quote
Old January 1st, 2013, 11:40 PM   #223 (permalink)
Senior Member
 
jova33's Avatar
 
Join Date: Oct 2011
Location: El Paso
Posts: 1,567
 
Device(s): Samsung Galaxy Nexus VZW Casio G'zOne Commando
Carrier: Not Provided

Thanks: 30
Thanked 181 Times in 152 Posts
Default

Quote:
Originally Posted by Rxpert83 View Post
Bricking your device and then getting insurance on it is fraud and that's why rooting has such a bad rap with insurance companies.

However, I see absolutely nothing wrong with using your warranty to replace defective hardware that was not caused by the device being rooted.

I've done that myself
If you lose your phone, and you have insurance on it, they'll replace it. So if you brick your phone, just lose it and pay the insurance for the replacement.
JKH62 likes this.
jova33 is online now  
Reply With Quote
Old January 2nd, 2013, 01:11 AM   #224 (permalink)
Junior Member
 
Join Date: Aug 2012
Location: USA
Posts: 59
 
Device(s): Commando 4G
Carrier: Verizon

Thanks: 4
Thanked 10 Times in 7 Posts
Default

Quote:
Originally Posted by jova33 View Post
If you lose your phone, and you have insurance on it, they'll replace it. So if you brick your phone, just lose it and pay the insurance for the replacement.

Bingo.
JKH62 is offline  
Reply With Quote
Old January 2nd, 2013, 10:47 AM   #225 (permalink)
New Member
 
Join Date: Dec 2012
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

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?
professerslime is offline  
Reply With Quote
Old January 2nd, 2013, 01:52 PM   #226 (permalink)
New Member
 
Join Date: Apr 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by immanoob View Post
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...
neuman1812 is offline  
Reply With Quote
Old January 2nd, 2013, 02:46 PM   #227 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2012
Posts: 51
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 65 Times in 9 Posts
Default

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
tommytopdrive is offline  
Last edited by tommytopdrive; January 2nd, 2013 at 02:50 PM.
Reply With Quote
The Following User Says Thank You to tommytopdrive For This Useful Post:
professerslime (January 3rd, 2013)
Old January 2nd, 2013, 10:12 PM   #228 (permalink)
New Member
 
Join Date: Dec 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 0 Times in 0 Posts
Default

So now that we have root, any concerns with doing a factory reset? Forgive the beginner question
elysian722 is offline  
Reply With Quote
Old January 3rd, 2013, 12:43 PM   #229 (permalink)
New Member
 
Join Date: Dec 2012
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by tommytopdrive View Post
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.
professerslime is offline  
Reply With Quote
Old January 3rd, 2013, 06:46 PM   #230 (permalink)
New Member
 
Join Date: Jan 2013
Posts: 5
 
Device(s): Casio Commando
Carrier: Not Provided

Thanks: 2
Thanked 0 Times in 0 Posts
Default

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.
FIDtodaycom is offline  
Last edited by FIDtodaycom; January 3rd, 2013 at 09:40 PM. Reason: I did not read the rest of the posts
Reply With Quote
sponsored links
Old January 3rd, 2013, 08:14 PM   #231 (permalink)
New Member
 
Join Date: Jan 2013
Posts: 5
 
Device(s): Casio Commando
Carrier: Not Provided

Thanks: 2
Thanked 0 Times in 0 Posts
Default

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?
FIDtodaycom is offline  
Reply With Quote
Old January 3rd, 2013, 09:37 PM   #232 (permalink)
New Member
 
Join Date: Jan 2013
Posts: 5
 
Device(s): Casio Commando
Carrier: Not Provided

Thanks: 2
Thanked 0 Times in 0 Posts
Default

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.
FIDtodaycom is offline  
Reply With Quote
Old January 3rd, 2013, 09:38 PM   #233 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2012
Posts: 51
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 65 Times in 9 Posts
Default

.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.
tommytopdrive is offline  
Reply With Quote
Old January 3rd, 2013, 09:42 PM   #234 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2012
Posts: 51
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 65 Times in 9 Posts
Default

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
tommytopdrive is offline  
Reply With Quote
Old January 4th, 2013, 12:24 AM   #235 (permalink)
New Member
 
Join Date: Dec 2012
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

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
professerslime is offline  
Reply With Quote
Old January 4th, 2013, 01:20 AM   #236 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2012
Posts: 51
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 65 Times in 9 Posts
Default

What exactly is happening with the WiFi? Is it showing an error under settings-wireless?
tommytopdrive is offline  
Reply With Quote
Old January 4th, 2013, 10:31 AM   #237 (permalink)
New Member
 
Join Date: Jan 2013
Posts: 5
 
Device(s): Casio Commando
Carrier: Not Provided

Thanks: 2
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by rasta4rest View Post
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.
FIDtodaycom is offline  
Reply With Quote
Old January 4th, 2013, 11:54 AM   #238 (permalink)
New Member
 
Join Date: Jan 2013
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 0 Times in 0 Posts
Default Thank You!

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!
0Ri0N0iD is offline  
Reply With Quote
Old January 4th, 2013, 12:04 PM   #239 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2012
Posts: 51
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 65 Times in 9 Posts
Default

Quote:
Originally Posted by FIDtodaycom View Post
I ran into the same problem.
odd as i am running 3.1.1 with no issues on m130.
tommytopdrive is offline  
Reply With Quote
Old January 4th, 2013, 12:30 PM   #240 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2012
Posts: 51
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 65 Times in 9 Posts
Default

Quote:
Originally Posted by 0Ri0N0iD View Post
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.
tommytopdrive is offline  
Reply With Quote
sponsored links
Old January 4th, 2013, 01:14 PM   #241 (permalink)
New Member
 
Join Date: Dec 2012
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

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.
professerslime is offline  
Reply With Quote
Old January 4th, 2013, 01:30 PM   #242 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2012
Posts: 51
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 65 Times in 9 Posts
Default

Quote:
Originally Posted by professerslime View Post
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.
if your using logcat extreme, check the dmsg under settings
tommytopdrive is offline  
Reply With Quote
Old January 4th, 2013, 01:32 PM   #243 (permalink)
Senior Member
 
jova33's Avatar
 
Join Date: Oct 2011
Location: El Paso
Posts: 1,567
 
Device(s): Samsung Galaxy Nexus VZW Casio G'zOne Commando
Carrier: Not Provided

Thanks: 30
Thanked 181 Times in 152 Posts
Default

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?
jova33 is online now  
Reply With Quote
Old January 4th, 2013, 01:43 PM   #244 (permalink)
Junior Member
 
Join Date: Aug 2012
Location: USA
Posts: 59
 
Device(s): Commando 4G
Carrier: Verizon

Thanks: 4
Thanked 10 Times in 7 Posts
Default

Quote:
Originally Posted by jova33 View Post
.

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
JKH62 is offline  
Reply With Quote
Old January 4th, 2013, 02:13 PM   #245 (permalink)
New Member
 
Join Date: Jan 2013
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 0 Times in 0 Posts
Smile

Quote:
Originally Posted by tommytopdrive View Post
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!
0Ri0N0iD is offline  
Reply With Quote
Old January 4th, 2013, 02:20 PM   #246 (permalink)
Senior Member
 
jova33's Avatar
 
Join Date: Oct 2011
Location: El Paso
Posts: 1,567
 
Device(s): Samsung Galaxy Nexus VZW Casio G'zOne Commando
Carrier: Not Provided

Thanks: 30
Thanked 181 Times in 152 Posts
Default

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.
jova33 is online now  
Reply With Quote
Old January 4th, 2013, 02:50 PM   #247 (permalink)
Junior Member
Thread Author (OP)
 
Join Date: Oct 2012
Posts: 51
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 65 Times in 9 Posts
Default

Quote:
Originally Posted by jova33 View Post
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.
tommytopdrive is offline  
Reply With Quote
Old January 4th, 2013, 02:52 PM   #248 (permalink)
Senior Member
 
Join Date: Feb 2012
Location: New Hampshire
Gender: Male
Posts: 552
 
Device(s): Archos 43 IT (dead), Casio Commando(s) (C771), Casio COmmando 4g
Carrier: the big bad "V"

Thanks: 43
Thanked 143 Times in 70 Posts
Willster419
Smile

Quote:
Originally Posted by tommytopdrive View Post
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".
Willster419 is online now  
Reply With Quote
Old January 4th, 2013, 05:40 PM   #249 (permalink)
Member
 
r_hippy's Avatar
 
Join Date: Jan 2013
Location: New Jersey
Gender: Male
Posts: 153
 
Device(s): Google Nexus7 Casio G'zOne Commando C771 v6SuperCharged
Carrier: Verizon

Thanks: 60
Thanked 20 Times in 20 Posts
Send a message via AIM to r_hippy Send a message via MSN to r_hippy Send a message via Skype™ to r_hippy
Default

New here today because of this thread

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
r_hippy is online now  
Reply With Quote
Old January 4th, 2013, 06:34 PM   #250 (permalink)
New Member
 
Join Date: Jan 2013
Posts: 5
 
Device(s): Casio Commando
Carrier: Not Provided

Thanks: 2
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by tommytopdrive View Post
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.
FIDtodaycom is offline  
Reply With Quote
Reply


Go Back   Android Forums > Android Phones > Casio G’zOne Commando > Commando - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 08:21 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.