Casio Commando users just got the Gingerbread 2.3.3 update via Verizon.
With Froyo I had easily used SuperOneClick to root my Commando and assumed Gingerbread (with Gingerbreak) would be no more difficult...BUT I WAS WRONG.
Gingerbreak does not work.
I've tried v1.0-.1-.2 of Gingerbreak and numerous iterations of SOC to no avail. Even retried with a factory reset.
I've read that there is little support for this particular phone because of it's somewhat niche status, but felt it worthwhile to start this thread in the hopes of locating and consolidating any other users with the same problem/possible solutions, but let's consider it a question thread just the same.
Have I missed an obvious method to root my newly updated Gingerbread (2.3.3) Casio Commando?
since this has received a handful of views and there is still no information/confirmation from any other commando users or anyone with any more knowledge than me, i'm going to give this thread one bump and then call it quits.
again: if you are a commando user in the same boat as me or have any leads on how to re-root after the update to gingerbread 2.3.3, please post it.
thanks, everyone.
Same Problem Sir
Same Problem, I installed 2.3.3. as well and lost root. Have tried different tactics using superoneclick to include psuneuter and ginger. The computer I was using has the Casio drivers so it was not "Waiting on Device". If needed I can post the output from superoneclick to show why it failed. Currently at work and do not have the capability.
Any help is appreciated.
I've already compared my SOC errors against issues with the same brand and different brands, and regardless of variance in method the failure repeats (the majority agreeing that it is a failure in the exploit, specifically the inability of SOC to read/write/remount at the end of the root process).
Has anyone tried rooting the 2.3.3 Commando with something other than SOC or Gingerbreak?
I am in the same boot. On top of that my display got corrupted in the process. It displays only stripes in the lower two thirds of the screen.
Any hints on how to recover from that?
Cheers
I am working on the root problem as well, I'll let you know if I have any success today. Feel free to ask if someone to test or verify something.
I am new at this but I understand that the os for the androids are based on Linux, have you tried a program in Linux? Just a question seeing as so far I have not found any there but I may not be looking in the right area.
No luck so far. I'll still be looking at it this week. The garbled offer above still applies, I'm available if anyone needs any testing or verification.
Any luck on this yet?
root
.. okay so new to the forum and excited to learn. so, not sure what everyone means by root. do have casio commando, and received auto 2.3 update. things seem to be fine, however it made my music all unknown artists and unknown titles. when i do go into any unknown tho, the title (s) of songs do appear.
I sure hope somebody can come to our aide and root gb 2.3. I never should have allowed the OTA stupid stupid stupid
Root means you own your phone. You have accesse to all files and can do whatever you want, like remove all the preinstalled crapware. Improves phone functions and tyre battery lasts longer.
Go figure, I finally decide to root my phone a week after it's made (temporarily I hope) impossible. I'm not versed in the languages required to work around this, but would love to help find a solution in any way I can.
Have there been any discoveries or developments regarding rooting the Commando post GB update? Maybe solid theories at least?
Is there anything that an average user such as myself could do to at least provide data to anyone willing to work around the GB block?
interesting, kixxit. this may have something to do with whatever app you are using as a media handler not being updated for a 2.3.3 OS.
as to the topic of the thread, i've still heard nothing about successful exploit discoveries but i will continue to scan the net and relevant forums daily until something changes.
good luck everyone, phone just doesn't feel right unrooted with all that bloat.
Anyone having any luck? Is the update even needed? I mean if I just keep the froyo, will there come a time that I need gingerbread?
I hope we can root this bad boy again...
I have the same exact problem tried every version of gingerbreak with on success i hope that there is a solution to our phones soon so we can root
Root-possible!!
Ladies and gentlemen,
Thanks to the Revolutionary team, CrimsonSentinal18, over in the Xperia Play section, Cl8rs for bringing this to the attention of some of the Xperia Play members, the Casio Commando running 2.3.3 has root!!
Here are step by step instructions to getting root on your phone!!
(I did it on my wife's Casio Commando, it worked, but she didn't want root, so i unrooted it right after I got root checker to say "You have root!")
Update!!: Guide! With Pictures!
At dropbox.com: http://db.tt/RaAUnzjW
At Ubuntu one: http://ubuntuone.com/64OujxgkGMv1N2QSoPmXin
or at Filesonic: http://www.filesonic.com/file/2711952454
(or attached)
Note: Android SDK Download link: http://developer.android.com/sdk/index.html
If you have any questions, i'll be lurking with answers!
Update: So far we have atleast 10 people who have confirmed rooting possible! (people who actually left me a message) ... no unfixable errors yet (i.e. no bricking)
Thanks for the post paxChristo!
I ran into trouble while installing the "superuser.apk"
when I re-ran the routine im an getting stuck with permissions trouble.
see below for a screen shot on how zergRush fails to run its thing even so it work the first time around and told me I am rooted.
--------------------------------------------------------------------------------------------------
C:\Program Files\Android\android-sdk\platform-tools>adb push "c:\droid\zergRush" /data/local/tmp
push: c:\droid\zergRush/zergRush -> /data/local/tmp/zergRush
push: c:\droid\zergRush/Superuser.apk -> /data/local/tmp/Superuser.apk
2 files pushed. 0 files skipped.
1690 KB/s (780946 bytes in 0.451s)
C:\Program Files\Android\android-sdk\platform-tools>adb shell
$ chmod 755 /data/local/tmp/zergRush
chmod 755 /data/local/tmp/zergRush
$ /data/local/tmp/zergRush
/data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[-] Cannot copy boomsh.: Permission denied
$ adb remount
adb remount
adb: permission denied
-----------------------------------------------------------------------------------------------
I restarted the phone but no Superuser app and when I try other apps like "SetCPU" I get the "no root access detected" errors.
Some help would be appriciated.
Thanks!
Any time you restart your phone (without making it all the way through, or even after unless you install insecure adb) you need to run zergRush to regain root priviledges,
BUT before running zergRush go into adb shell and type:
1) "rm /data/local/tmp/boomsh"
2) "rm /data/local/tmp/sh"
What problems do you have install Superuser.apk?
Have a strange one I don't know how to fix. Purchased a Pyle PTBL102BCD tablet for the Mrs. to use basically as an ebook reader (according to About, running 4.2.2). When it came in I started sideloading apps to prepare it for her (I do not have a Google account), and searched on the Net about rooting the device. Found a one-click that worked with a different Pyle tablet, so I gave it a shot.
Now I have root access _only_ through the adb shell. None of the apps (including Superuser.apk itself as tested by updating /system/bin/su) can get root access, yet I have no problem running root through an adb shell - remounted file systems, even performed an su which is the only instance Superuser.apk's log shows. Root access in the shell remains between reboots, so it's not a temporary root.
If the adb shell has root, I _should_ be able to use it to grant access to everything else, and I've followed a few different "manual" root instructions (having different permission settings for su and busybox), with no joy. So long as I connect with a USB cable and type on the Windows machine, I'm god. On the tablet itself...not so much.
I hope that someone with a more intimate knowledge of Android internals can point me in the right direction for achieving root completely. Currently have Titanium Backup and ConnectBot (long java errors when I attempt to su there) installed to test root, Superuser v3.1.3 and su v3.1.1. Permissions on su are -rwsr-sr-x. And the human is confused.
Did you get anywhere with this? I have the same problem. What one-click did you use?
mfurlend said:
Did you get anywhere with this? I have the same problem. What one-click did you use?
Click to expand...
Click to collapse
Side note; REALLY hate the new forum software. With all the untrusted Google and Amazon javascript (which my company firewalls), it's a pain for me to even log in let alone post replies. (And I wonder if I'm the only person in the world sick to death of all the unnecessary ajax garbage...)
Anywho, used Kingo, rooted and unrooted a few times, until I finally acquired complete root on the thing. Once I did, I could run Samba, and once that worked, I could more easily transfer files and apks to the tablet.
Still don't understand why it was left in such a...weird...state - having root by default in adb is just a scary thing!
thanks for the information. I tried doing that but I encountered various problems. Eventually, after trying to do it manually, I totally screwed up the device. Now it won't boot.. I still have access to adb. I need to flash this thing. Do you know what the stock ROM is?
mfurlend said:
Do you know what the stock ROM is?
Click to expand...
Click to collapse
No...I can give you the Kernel version info (3.0.36+ [email protected] #48) and build number (rk3168_k11_4.2.2_v20131230), but other than that no clue.
Hello,
Thank you for the tips form the Leagoo Lead 3 forum: I wasn't able to post there so I do it here;
I don't know how to relate my own tasks to achieve this:
At least I followed steps 1 and 2: Step 1 was never finished: hangs or failed error message:.
With Kingo Root, always ended up with failure message except the last time:
I was able to root successfully;
Before to successfully root with Kingo Root:
- After several trials with steps 1 and 2. I ended up with Lead3 being rooted as displayed on Kingo Root status, But I wasn't able to use su;
- Once Kingo root status was root, I launched mtkdroidtools 2.5.3, freshly reinstalled(ie I renamed my former version installation), Lead3 was correctly detected with green light, No Root button but ADB. I made a backup and installed SuperSu with this tool:
I clicked on ADB. Type adb shell, it gave me # root access inside Lead 3.
But on standalone, Lead 3 stayed as not rooted (default.prop ro.secure=0). Secure mode. Thank you to the Insecure forum: And the guy who explained clearly on one his article, just google 'android insecure mode' and ' Root any Android device - Whiteboard Web'.
- Last trial with Kingo Root: Root was successfull.
And I still don't understand ,,,,
- I checked Lead3, it's rooted. SuperSu, Xposed framework work Ok, and su in the terminaluf.
ps: The device manager shows android device with Alcatel ADB driver. and sometime Android ADB, depending on which tool I used.
NB:
I forgot to mention that during the rooting trial, with adb and terminal, I saw busybox was installed, at leat links in the filesystems I was able to mount -o remount, rw /system and / in order to change default.prop content (sed ,,,,). Strange isn't it ?
Baffled ,,,
But as curiosity is still here and pocket minded, I'll shop more of those phones.
Leagoo Lead 3 is really nice phone. As long long as I can control ...
Hi. I'm having trouble rooting my Envizen V100MDT tablet the manual way since it's a production build and won't allow adb as root, but also since I can't find a compatible su binary nor su moderator program to run on it without getting an weird error code while at the tablet's shell. I tried to take advice from
[KERNEL] adb "cannot run as root in production builds" fix
but to no avail since the default.prop file is also locked into read-only mode. The reason that I'm writing this post is because i'VE TRIED AT LEAST 7 ONE-TAP METHODS WITH NO RESULTS. So, since I'm not a kernel coder and will not pursue an understanding of the free code available , and I'd like to do this without giving a complete re-install/flash of the kernel and all of its important components, my post is here.
Hey, new user here. Sorry if this is miscategorised.
I have a very simple issue. I have a GT-I9305, recently rooted with some weird Android Terminal commands and a .zip file I found online. No issue with rooting. I did a root check and used root to uninstall Knox.
Issue is that beforehand I tried to root with KingRoot and I didn't know it would automatically download its own SU (probably should have been more cautious). I want to use Super SU instead but I can't because after some research, there'll be so conflict between these two. So further research suggests I need to do some deep replacement between these two.
I've tried several methods already.
An app called SuperSu Me required higher Android version, so that was a strike for me. The one with the commands with the mrw file did not work (just threw up a whole list of failures and errors), and another appears to be working with Kit Kat only (I'm on 4.3). Another limitation I have is that my computer is garbage and probably won't run Odin or whatever flashing thing, so that rules out another horde of solutions.
Further, Super SU did not update binary, which most websites suggested it will do. It tries to do it, then regurgitates an error message after five minutes.
So I was just wondering if there is some obscure way beyond the second Google search page which might help me out here, to replace King SU with SuperSU. After all, the root method I used in the first place wasn't exactly conventional.
Just wanted to ask around here before I simply unroot and forget about the whole business. Been lurking around here unregistered and you guys have been very helpful, so now I guess I'm starting a topic of my own.