yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] dayaspone:
Hopefully you are still available to help. :) I am currently sitting with a pair of Kyocera Torque running 3.000SP and they continue to fail installing SuperSu in the method you describe. I feel like I am following your instructions exactly but neither will work. I have rooted a Torque before, running 2.002. It is my phone and I love it, however, the beast has seen better days and I picked up a pair of "new" torques to replace it but just can't seem to get them to root! Any help is greatly appreciated.
[Android Q&A, Help & Troubleshooting] fendergrab:
Fyi, we are getting jelly bean,

http://www.androidcentral.com/kyocera-torque-receiving-jelly-bean-update-starting-today
[Android Q&A, Help & Troubleshooting] GTDarthYoda:
I'm gonna root my Dad's Torque, I'll see if it'll survive the update when it comes around.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
Ugh, hope it doesn't break root!! My phone is on, wifi only, but unactivated. It does nothing when I press Update Kyocera software, and when checking for Firmware, I get "Software update failed" which I believe is caused by it being unactivated.

Two interesting sidenotes for the phone being unactivated- 1) It will switch to a 4G icon if it's available in the area, which I was unsure if it would do without being "connected," and 2) It will receive emergency alerts. Scared the **** out of me when it happened; I haven't had a phone with that "ability" before lol!
[Android Q&A, Help & Troubleshooting] fendergrab:
Mine is active, but the update hasn't pushed to me yet... my GS3 would receive emergency alerts... usually in the middle of the night.
[Android Q&A, Help & Troubleshooting] jtabb1256:
If anybody does get the update, try to extract it and post it here. Remember that we are trying to find the boot.img or anything that will help with making a custom recovery mode. Maybe use the app named Rom customizer to look through the update. Also use any ota survival app that you can, but I still think that you will lose root no matter what you do if you do the ota update. Maybe we could extract the update and then flash it on?
[Android Q&A, Help & Troubleshooting] jtabb1256:
I'm downloading the update right now. I'll try to upload it here.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
Are you currently rooted? Thanks for the future upload :)
[Android Q&A, Help & Troubleshooting] VicFreeze:
Official Jelly Bean might bring me back to this thing if and only if we can keep/improve root and a decent face-in caseless holster surfaces for this phone. I got tired of waiting and didn't want to start pocketing it. Anyone know of a molded plastic face-in holster somewhere?
[Android Q&A, Help & Troubleshooting] jtabb1256:
I am currently rooted. I did download it, and it asked to install. I chose install later so that I could look for it and extract it, but then my phone rebooted and I didn't have it downloaded anymore. I'll have to wait for it to download again, which with my slow connection will probably take another 30 minutes to an hour. h:(

---------- Post added at 02:03 PM ---------- Previous post was at 01:58 PM ----------

I use a ballistic case, which has a nice holster, but it's really bulky and you said that you didn't want to use a case.

This one looks kind of flimsy:

http://kyo.addtocell.com/p-326-torque-holster.aspx

Maybe this one:

http://www.tessco.com/products/displayProductInfo.do?sku=572185

Although it might not be customized just for the kyocera torque.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
Does the one from Sprint not work for ya? http://www.ebay.com/itm/151029451500
[Android Q&A, Help & Troubleshooting] VicFreeze:
Yeah, I had not checked Kyocera's website lately (only back at launch when there was nothing), but that is what I'm looking for. I am aware of the ballistic case-in-holster setup, but I don't need all of that with a phone that already feels like it has a case on it as is. Thanks for the links.

---------- Post added at 01:14 PM ---------- Previous post was at 01:11 PM ----------

I had not even seen that one either, lol. Being an early-adopter sucks...you have to wait on accessories. I never saw anything but the ballistic case.
[Android Q&A, Help & Troubleshooting] jtabb1256:
I successfully downloaded it again. I just can't find it. Any suggestions?

I've searched for .zip and found nothing like an update. I found some files in /delta/

They may be the update, but just in different parts. They're too big to upload here, so I'll see where I can upload them. Maybe dropbox?

I found 8 files in /delta/ and a couple of them were big. I will upload them to dropbox. Dropbox says it will take an hour to upload them.

Using Qtadb, I went file by file through my entire phone and those files are still the only ones that seem like they are the update.
[Android Q&A, Help & Troubleshooting] jtabb1256:
I would advise that you all go into settings and try to update kyocera software and see if you can download the update and maybe find more of it or compare the files that you find with the ones that I find. I will post the link to dropbox where I uploaded the files here. Should I try to compress them into zip?

Should I just go through with the update and see if it then creates a complete update package that I can find?

I found and pulled all of the files that I could find, so I'm going to go through with the update and will report back with info about sustained root, etc.

My phone got through halfway and then got an error message and just started going through a boot loop. I removed the battery and turned it back on. It still is just going through a boot loop. This sucks.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
Try a hard reset. Instructions here: http://support.sprint.com/support/tutorial/Perform_a_hardware_factory_reset_Kyocera_Torque/47366-396
[Android Q&A, Help & Troubleshooting] jtabb1256:
I already tried it. It doesn't work. This could have happened because I deleted the camera noises from /system/media/audio/ui or because I used ota root keeper or maybe just because I was rooted. I don't know, but I would probably adb backup your phone and hard reset your phone before you updated it.

---------- Post added at 08:54 PM ---------- Previous post was at 08:47 PM ----------

The drop box link to the files I found after I downloaded and before I installed update:

https://www.dropbox.com/sh/iop084qr50tga1u/q0bCjESsDr
[Android Q&A, Help & Troubleshooting] jtabb1256:
My phone is covered under warranty and I'm getting a replacement for free on monday. The Sprint guy said that kyocera hasn't given them the software to reflash the torque with yet. I find this very interesting, although it may be because it is such a new phone.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
Good to hear no harm to your wallet for taking one for the team :)

Next step would be to try to root the 2.00 update after you get your new phone -or- if someone else on here has updated and wants to try rooting, it would be appreciated by all Torquers :)
[Android Q&A, Help & Troubleshooting] jtabb1256:
I'll update my phone before I root it. I would recommend that you backup your phone with adb and something else and then restore it to stock with factory hard reset, wipe cache, restore any stock files/apps you deleted, uninstall all apps that you may still have that aren't stock, and unroot your device before you update it in order to avoid the problem I had.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
Did you keep a backup of the /system/app? I deleted several (like Google+ and some Sprint stuff).
[Android Q&A, Help & Troubleshooting] jtabb1256:
Yes. Ill upload it here or on dropbox once I can get on my computer. To do this, your /system needs to be mounted as r/w, then before you update your phone, you need to mount it back to r/o. Also make sure everything else is mounted the way it should be.

*EDIT: do this before you unroot your phone.
[Android Q&A, Help & Troubleshooting] bdjohns1:
So, I just rejoined the Android world after being away for a year or so when we all got DC phones at work. Obviously, mine's a Torque.

My phone got the Jelly Bean update already. I tried Vic's method, and it didn't work. After digging around, I found that the su binary wasn't getting copied over from /data/local/tmp into /system/xbin. Why? Because /system is full.

shell@android:/system/app $ df
Filesystem Size Used Free Blksize
/dev 387M 96K 387M 4096
/mnt/asec 387M 0K 387M 4096
/mnt/obb 387M 0K 387M 4096
/system 495M 495M 0K 4096
/data 1009M 423M 586M 4096
/cache 504M 8M 495M 4096
/persist 7M 4M 3M 4096
/firmware 63M 43M 20M 16384
/sysprop 7M 5M 2M 4096
/carrier 39M 4M 35M 4096
/delta 252M 4M 247M 4096
/storage/sdcard0 14G 2G 12G 32768
/mnt/secure/asec: Permission denied
/storage/sdcard0/internalSD 1023M 16K 1023M 16384
1|shell@android:/system/app $

I did verify that the exploit itself in motochopper did work, because when I did its script manually (adb push busybox, su, and the pwn binary, then run the pwn binary), the system partition would get remounted rw. The problem is that as the exploit moves su over to /system/xbin, the copy operation fails because the partition is full. So, you end up with a su file which is SUID root, but isn't actually a complete file (su should be 300+ KB) :

shell@android:/system/xbin $ ls -la
-rwxr-xr-x root root 1798144 2013-07-11 21:15 busybox
-rwxr-xr-x root shell 55664 1969-12-31 18:11 dexdump
-rwxr-xr-x root shell 67072 1969-12-31 18:22 hciconfig
-rwxr-xr-x root shell 39796 1969-12-31 18:22 hcitool
---sr---wt root root 4096 2013-07-11 21:15 su
-rwxr-xr-x root shell 46440 1969-12-31 18:11 updateue
shell@android:/system/xbin $ ./su
Segmentation fault
139|shell@android:/system/xbin $

Any thoughts on how to work around it? How can I remove some unneeded cruft from /system to free up a few hundred KB of space?
[Android Q&A, Help & Troubleshooting] jtabb1256:
If /system is mounted as r/w, use qtadb on your computer or use a file explorer on your phone to delete some useless stuff. You may need shell root for this, but I'm not sure. Its definitely worth a shot. And I've heard that in jellybean developer settings menu is hidden. You need to have usb debgging on, so if this is the case, go to about phone and build number and tap it 7 times to discover developer settings. I would recommend going to /system/media/visual and delete the stuff in there like videos of android in space and pics of sunset.

*edit: without root, I don't think you can delete anything from /system. If you find that you can't, see if uninstalling sytem app updates would help. Although I'm not sure if that would work. Just try it anyway.

You may have to do an adb backup for everything but system and a qtadb app backup and factory reset your phone to free up memory in /system. This might uninstall jellybean though.
[Android Q&A, Help & Troubleshooting] bdjohns1:
Actually, I was able to get it to work. Here's the exact sequence I followed (stock Jellybean):

1) adb push busybox, pwn, and su over to /data/local/tmp

2) adb install Superuser.apk

3) adb shell. In the shell,

a) cd /data/local/tmp

b) ln busybox cp

c) ln busybox mount

d) ln busybox chmod

e) ln busybox chgrp

f) export PATH=/data/local/tmp:$PATH

g) chmod 755 pwn

h) ./pwn

4) At this point, the files are in place, but su isn't working. That's ok, because I was able to delete the 480p videos in /system/media/videos, since the exploit had me mounted rw even though su failed. Frees up 2MB, which is all we need.

5) back on the computer, do adb shell /data/local/tmp/pwn (for some reason, it doesn't work if you just open a shell and do it)

6) Once it runs, verify you can get a root shell.

7) Follow the previous instructions with mtkdroid to install SuperSU

Verified that it worked and survived a reboot via the root check in Titanium Backup.

edit Note: the reason I did the hardlinks to busybox and the PATH thing was that the first time I tried running the exploit, it failed, saying that it couldn't find 'cp'. So, I gave it every command I saw buried in the text near the end of the exploit executable. :good:
[Android Q&A, Help & Troubleshooting] VicFreeze:
You could just try to hard reset from fastboot with "fastboot -w".

---------- Post added at 03:18 AM ---------- Previous post was at 03:12 AM ----------

Nice. Yeah, getting shell root first is the key to putting everything else in place. How is the UI with Jelly Bean? Any different? I'm still considering grabbing another Torque, but am going to get this S4 Active tomorrow...so this would have to replace my S3 and its "everything proof" Seidio case. I'll check the local Sprint store here (if one's close) to see if their demo has been updated but I'm away in BFE on business.
[Android Q&A, Help & Troubleshooting] bramms:
Got root!!!

2.0 firmware, Android JB 4.1

Thank you guys!

P.S. Full wipe/reset is not needed, I did it without factory reset
[Android Q&A, Help & Troubleshooting] bdjohns1:
Nothing too big - some tweaks to the notification pane to make the header more compact. Basically, just incremental tweaks as best I can tell.
[Android Q&A, Help & Troubleshooting] jtabb1256:
Even when I use those modes I was talking about in a previous post, fastboot can't find my device. I guess they were just animations after all. Do you know of a way for fastboot to recognize my phone?

---------- Post added at 11:21 AM ---------- Previous post was at 11:11 AM ----------

Those of you who have successfully rooted your phone with jellybean, do you constantly have shell root? For example, when my phone was working, I would go to mtk droid tools, and it would have to achieve shell root through established su every time I wanted to do something on adb that couldn't be done on "production builds". Also, can you set superSu to ask your permission for apps getting root access?

Also, do you think that its about time to make an official thread for rooting this device?
[Android Q&A, Help & Troubleshooting] VicFreeze:
What do you mean fastboot cannot find your device? Fastboot doesn't find anything...your computer does. As long as the driver is installed and you are in the proper mode, fastboot should work.
[Android Q&A, Help & Troubleshooting] jtabb1256:
That's what I mean. What is the "proper mode"? My phone only does a boot loop or goes into recovery, and I don't know of any other mode to get in to. Do you know of some fastboot mode that I am ignorant to?

Any time I do a fastboot command, fastboot says, "waiting for device".
[Android Q&A, Help & Troubleshooting] VicFreeze:
Yes, of course. Every device must be booted into "fastboot mode" for fastboot commands to function. The hardware button method escapes me since I do not have the phone anymore, but, if adb works while in recovery, run "adb reboot fastboot".

As for hardware buttons, try vol down+camera+power, vol up+camera+power...not sure, but someone with a Torque on hand should be able to tell you.
[Android Q&A, Help & Troubleshooting] jtabb1256:
I was aware of there being a fastboot mode to get into, just not how. Thank you for your suggestions, but adb doesn't recognize it while in recovery and the vol down+camera+power just put it into recovery. vol up+camera+power doesn't do anything. Before my phone was messed up, I tried vol up+power and it just went to the first boot animation and stayed there until I removed the battery. Same thing happened when I tried to do adb reboot fastboot or bootloader. So I think that is how you get to the mode, it's just that it's locked or needs some other input.

---------- Post added at 12:52 PM ---------- Previous post was at 12:27 PM ----------

Dropbox link:

https://www.dropbox.com/sh/96ks5f5pjwged61/PUeMR2TuH4

I made a folder within the folder so that you don't have to download the files one at a time. To download the whole file, just click on the download on the top right.
[Android Q&A, Help & Troubleshooting] VicFreeze:
That is, likely, fastboot. Try plugging it into your computer and checking after the logo "sticks".
[Android Q&A, Help & Troubleshooting] jtabb1256:
The thing that is really weird is that since my phone got screwed up, it hasn't been able to do that. If it really is fastboot or bootloader, then it should work. Maybe somebody without a screwed up torque should try it.
[Android Q&A, Help & Troubleshooting] jtabb1256:
Has anyone tried to find download/ bootloader/ fastboot mode? Any results?

Those of you who have successfully rooted your phone with jellybean, do you constantly have shell root? For example, when my phone was working, I would go to mtk droid tools, and it would have to achieve shell root through established su every time I wanted to do something on adb that couldn't be done on "production builds". Also, can you set superSu to ask your permission for apps getting root access and still have it function properly?
[Android Q&A, Help & Troubleshooting] playingbball20:
I was wondering what you did to get the wifi tether to work? I was able to get the phone rooted with the same steps, thanks for the info.
[Android Q&A, Help & Troubleshooting] jtabb1256:
I get confused in step 3. When you say "In busybox...", is that the exact command you put in? I'm good enough at this to be able to do step one even though it wasn't word for word, yet I'm still a noob who is learning, so could you please help me?
[Android Q&A, Help & Troubleshooting] VicFreeze:
Don't read the commands...copy and paste. That is a lowercase LN, not uppercase i lowercase n.

---------- Post added at 07:31 AM ---------- Previous post was at 07:29 AM ----------

I'll post some info a little later, but, remember, that was on ICS not JB.
[Android Q&A, Help & Troubleshooting] jtabb1256:
Ohhh. Ok. That makes a lot better sense.thank you! :)
[Android Q&A, Help & Troubleshooting] jtabb1256:
After I give the ./pwn command, I get an error saying something like:

segmentation error:

sh: cp: permission denied
[Android Q&A, Help & Troubleshooting] jtabb1256:
When I tried to do your process, I got the same error. I tried it several different times, too. I've attached my attempt after motochopper.

EDIT: I'm also not able to delete the videos.
[Android Q&A, Help & Troubleshooting] playingbball20:
I'm not a dev by any means, but i would assume you are not copying/pasting things in correctly

adb push busybox /data/local/tmp

adb push pwn /data/local/tmp

adb push su /data/local/tmp

adb install Superuser.apk

adb shell

cd /data/local/tmp

ln busybox cp

ln busybox mount

ln busybox chmod

export PATH=/data/local/tmp:$PATH

chmod 755 pwn

./pwn

********************************

at this point you should be back at the normal command prompt, or in shell, i did it a few days ago.

If you are not in shell... adb shell

********************************

ls /system/media/videos/

********************************

see if anything is there, if there is still videos there continue

********************************

rm /system/media/videos/*

ls /system/media/videos/

********************************

see if anything is there, there shouldn't be if not, you will have to remove each one, one by one...Remove the "*" and put the file name

********************************

Hopefully this helps. I had some issues doing the root process, but I was manipulating code from a few weeks ago before and had to redownload motochopper and mtkdroid.

Make sure that all the files are where you are using adb!!! ;)
[Android Q&A, Help & Troubleshooting] bdjohns1:
You've got some other issues there - adb shouldn't be throwing all of those errors every time you push, and the adb daemon shouldn't need to restart over and over.

If you're getting an error saying that cp can't execute the first time you run pwn, that means that your busybox executable isn't executable. Try chmod'ing it to 755. You can't delete the videos because the exploit isn't running right - if the preceding steps worked, you'd at least be left with / mounted as r/w.

There could be something else weird happening too. I was working from a shell prompt on my Macbook. Maybe there's some other permissions issue at play.

At some point, I had to do a force reinstall of Superuser.apk as well.

Just some thoughts.
[Android Q&A, Help & Troubleshooting] jtabb1256:
I may have to do a factory reset. I think residual files make adb go crazy. Thanks for your suggestions. I'll try them.
[Android Q&A, Help & Troubleshooting] VicFreeze:
Hard resets typically don't do much to the system folder or bin/xbin...and I don't think that is your issue. Like others have said, make sure you are copying & pasting correctly and in the right mode with the phone hooked up right.
[Android Q&A, Help & Troubleshooting] jtabb1256:
I tried chmod'ing busybox to 755, although I'm not sure if I did it correctly. Ill upload the attempt with chmoding busybox. Thanks for all your help. I wonder why my phone is having trouble or maybe it's just me. Oh, and adb reboot-bootloader works!

---------- Post added at 10:41 PM ---------- Previous post was at 10:10 PM ----------

After messing around (I was tired and accidentally did stuff. Glad I didn't break my phone.), I got shell root. So I tried to do all the adb pushing and etc, but I kept getting permission denied errors, so I restarted my phone. Then I decided to push all the files first and then do motochopper, which successfully gave me shell root. From there, I used mtkdroidtools. Success! Thank you for all who helped.
[Android Q&A, Help & Troubleshooting] bdjohns1:
Great, glad to hear you were successful!
[Android Q&A, Help & Troubleshooting] fendergrab:
Can anyone access the 4g toggle? Its not in my mobile networks menu. I'm wondering if its because I don't have direct connect on my phone.
[Android Q&A, Help & Troubleshooting] VicFreeze:
This isn't a WiMax device, so you either have CDMA/LTE on or CDMA only...no toggle, LTE auto-switches as it's found.
[Android Q&A, Help & Troubleshooting] fendergrab:
Yeah, I was just referring to LTE as 4g. Its just that I do not have any cdma/lte or cdma only options in the mobile networks menu.
[Android Q&A, Help & Troubleshooting] playingbball20:
Figured out how to tether on JB

I finally got tethering to work!!!

Install WifiTether-TrevE_Mod_Latest.apk

In settings change

Device-Profile to generic ICS/JB (wlan0)

Setup-Method to Auto

Check WiFi-driver reload (don's us WiFi-driver reload 2, it will turn off your tether)

You can check Keep Alive if you want

Hit the back button and tether
[Android Q&A, Help & Troubleshooting] VicFreeze:
I actually used the stock WiFi Tether app (not the TrevE Mod). Are you using this on ICS or JB though?
[Android Q&A, Help & Troubleshooting] playingbball20:
---------- Post added at 01:11 PM ---------- Previous post was at 01:10 PM ----------

I'm on JB
[Android Q&A, Help & Troubleshooting] SoHardcore:
Took me a good hour or two to get the first part of rooting done, which is essentially all the motochopper apps.

I'm not sure what exactly I did... but I think it was a bit of reinstalling Superuser.apk and then noticing that pwn had to be run with the prepended "adb shell" in front of it. Anyway... I was able to successfully delete the 480p videos in the /system/media/video/ folder!!!

Now I'm curious... if "su" worked, why then do I need to run MtkDroidTools?? What does this do, exactly??
[Android Q&A, Help & Troubleshooting] VicFreeze:
Shell root (you typing su on your PC and then interacting with the file structure) is not the same as root between apps on your device. Mtk pushes that "full" root.
[Android Q&A, Help & Troubleshooting] SoHardcore:
How to copy the firmware files to sdcard??

OK, so I finally decided to go thru with the update, now that I've got root.

And I figured it'd be a good idea to look for the firmware upgrade files.

I found them!!! They're in the /delta folder

I've tried a simple "cp -r /delta /sdcard" to get these files onto the sdcard, but it's just not working. I'm wondering if the hard links that were suggested earlier are affecting this, perhaps? Dunno.... but would definitely like to get these files off and in a SAFE place. :cool:

Any ideas?