yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] SoHardcore:
I had the same issue. Bricked my phone in a minor way, used the 2.002 files located in the aforementioned DropBox link, but as soon as I do the OTA update.... FATAL 8713 error!! It happened twice while I was on Sprint. I actually was trying out a Galaxy Note 2 the last time, and there's nothing I can do to unbrick it from this *fatal* error. There's something outside of those three images that isn't flashing to put the phones back to 2.002 stock settings. Some driver for the radio(s), perhaps? Dunno.... But I'd really like it if this phone was working again. :crying:

TL;DR -- NOTICE!! WARNING!! DO NOT UPGRADE AFTER FLASHING THE DROPBOX IMAGES!!! ... unless you have TEP on Sprint associated with this device.

:eek:
[Android Q&A, Help & Troubleshooting] x000x:
nobody has ever found a solution to 8713 error. only recourse was to send it back to sprint for repair.
[Android Q&A, Help & Troubleshooting] linyincsz:
Who can provide the phone partition table and the corresponding name? ! Very grateful
[Android Q&A, Help & Troubleshooting] jlmancuso:
A quick google search can really help anyone who is willing to take the time.

https://www.google.com/#q=adb+display+partitions

Heck the very first thing listed would have given you all the info you need.
[Android Q&A, Help & Troubleshooting] linyincsz:
I can see the partition information, but can not name one by one, and the system, and this is my problem.
[Android Q&A, Help & Troubleshooting] jlmancuso:
Read the info I just provided you. Way #2 is what you are looking for right?
[Android Q&A, Help & Troubleshooting] linyincsz:
I do not know if the partition is the partition corresponding to the index.
[Android Q&A, Help & Troubleshooting] jlmancuso:
Okay not sure what the issue is here. Why would the partitions not be what they are? Did you go in and repartition the device somehow?
[Android Q&A, Help & Troubleshooting] msmadilee:
i sent the device i was using for this thread back to Kyocera a week ago. They just returned it "Unable to repair". Not sure if this means its impossible for them to repair, or if they are just refusing to.
[Android Q&A, Help & Troubleshooting] x000x:
did you do it through sprint? I had read in the past that they gave customers replacements. i think this would only work if you were a current sprint customer however.
[Android Q&A, Help & Troubleshooting] Guardian93:
Fatal Error 8713

Has anyone figure out what to do with 8713 error for the kyocera torque? My girlfriend had this phone and sprint pushed an upgrade overnight and the phone always said it didn't have enough space, my guess is that it tried to push the update and the phone bricked it self. anyone has access to the stock firmware? we were looking to give this phone to my Girlfriends little brother since he desperately needs one, Also the device wasn't rooted
[Android Q&A, Help & Troubleshooting] jlmancuso:
8713=trashed device there is no fix. Sprint knows this issue exists but still pushes the update. Most users have been able to get sprint to replace the device.
[Android Q&A, Help & Troubleshooting] jackijumbo90:
Hi guys

Just received my kyocera torque KC-S701 for work and looking for a way to root it. I'm running 4.4.2.

Thanks.
[Android Q&A, Help & Troubleshooting] -]AF[-Death:
I associate myself looking at. Unfortunately Kingroot does not work :(
[Android Q&A, Help & Troubleshooting] amruthwo:
Temp root ---> rom dump?

if motochopper really works for temp root, could we do a rom dump that way? Use the stock recovery to make a cwm recovery via builder, then flash a su.zip?

My father just got this phone and wants to be able to tether it, but I don't have access to his phone to test this. Also, is there a way to get into fastboot on this phone?
[Android Q&A, Help & Troubleshooting] VicFreeze:
Very limited temp root with shell access via desktop ADB. I have not been able to dump at all. Fastboot does work, but, again, nothing productive has yet to surface (fastboot boot everyplausiblecustomrecovery.img) . I am on the verge of moving away from this. I just went back to a GS3 and got a waterproof Seidio case for it. I am going to play with the Torque a little more while it have it up for sale (nice price & excellent condition with original box, FYI). I had two of these, sold one and considered keeping the second if root came along...now, back to a GS3 & eventually adding an S4 Active into the mix as my two work devices. I'll try some things out though. I do think that pulling the recovery image and cooking it with the CWM Builder is the practical idea if more effective root exploits don't materialize. Otherwise, we need insight on what we can do with our existing shell root via motochopper in order to normalize it for app use. The problem seems to be with su (my way of trying to describe root access requests between apps and the Superuser handler).

I have been working with a "dirty" system (various root attempts on top of each other) so I finally have the chance to fully restore to stock and try some other methods without tying up my active daily driver...until it sells, of course.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
Anyone try this method on their Torque?: http://xdaforums.com/showthread.php?t=1886460
[Android Q&A, Help & Troubleshooting] VicFreeze:
One of the first attempts tried...and no.
[Android Q&A, Help & Troubleshooting] SoHardcore:
Is there a driver for this phone available?? .... in order to use ADB?

---------- Post added at 08:41 PM ---------- Previous post was at 08:18 PM ----------

It appears I spoke too soon. Kyocera actually has the drivers on their website....

http://www.kyocera-wireless.com/support/phone_drivers.htm

Amazing.
[Android Q&A, Help & Troubleshooting] VicFreeze:
Full Root Working and Tested (Write-Up Coming Soon)

I guess it took me wanting to sell the Torque and move on from it for the light to go off...well, a working root has been attained and confirmed on this device running the latest 1.007SP release. I am a little tied up until later tonight or sometime this weekend, but the general synopsis, for those who have been trying diligently, is as follows:

1. Hard reset and get back as stock as you can

2. motochopper

3. reboot

4. check shell root in ADB, if good, proceed to MtkDroidTools_247

5. run this in ADB shell in a seperate window to make the system folder writable for the moment: mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system

6. Superuser button in MtkDT247 to install SuperSU (it should also safely/properly remove CWM's Superuser app)

7. if you do not see SuperSU on device, reboot device

8. open SuperSU on device (make sure you have a web connection live on it) and update su binary & set Default access to "Grant" (only works like this for now, so BE CAREFUL WHICH ROOTED APPS YOU ARE USING) then reboot

*should be golden at this point*

As I said, a more thorough write-up will come later along with links to everything needed along with working Wifi Tether settings for those whose sole reason for root is that. Thanks for everyone's participation and interest in this device thus far. Enjoy it as I bid adieu to my own.

If anyone can follow the chicken scratch above and can get this going on their own virgin Torque, feel free to put together a write-up, but please don't forget the credits and point back to this thread for future reference. I plan on drawing up the deets and posting right back in here versus starting a new thread (unless it is deemed necessary).

Next stop, trying to pull the recovery & cooking up a working custom recovery, but that is up to y'all.

Update: PLEASE refrain from questions and PMs until I or someone else posts a more detailed write-up. These steps are not really supposed to be decipherable to those who don't comprehend them. Just wait for the write-up if you are stuck at all. If it isn't answered there, then bring em on.
[Android Q&A, Help & Troubleshooting] eriklion:
Well... I tried your instructions, I was able to obtain root via adb but not any application, it seemed that applications would call su and just hang there. (su binary not the application, the applications were waiting for su to reply)and moving binaries around made it so adb will hang waiting for adb too. I cant think of anything more. Mostly want root to freeze applications that are eating battery. specifically Sprint's Connectivity Optimizer /FastDormancy thing and SprintID/bloat. On reboot these applications are unfrozen in most cases.

Yes I tried both SuperSU and Superuser.

Is there a stock rom floating around? I would really like to go back to stock-stock before my first failed root attempt. (to remove any files that may have been left behind.) I got the Superuser notification to show up ONCE then.
[Android Q&A, Help & Troubleshooting] VicFreeze:
Then you did not heed all of the points of the steps.. as I said, it just a synopsis, but if you were "trying both SuperSU and Superuser" then you did not do it correctly. You should NOT have both still on your device if you have done it as I did. You will only have SuperSU (that is what MtkDroidTools_247 should be doing for you) and you have to update the binary to play nice with SuperSU and then set the prompt to "Grant" after it is all said and done.

I will try to get together a more detailed write-up over the holiday. I just got called away on some business (so it may be longer than I anticipated), but I will try to chug it out while traveling this coming week.

Oh, and there is no stock ROM that I know of. If there were, it would've made life a little easier a while back, as it would, likely, have the stock recovery packed in or available somewhere with it.
[Android Q&A, Help & Troubleshooting] eriklion:
haha, I should have clarified. No, I didnt have both on there at the same time. when I tried another, I removed the previous one with adb before trying again, before it hung the way it is now, it would let me :P

as it is now, I'll have to start fresh... I cant remember what I was going to say the first time. had to go do stuff, and thank you for the quick reply.
[Android Q&A, Help & Troubleshooting] VicFreeze:
SuperSU needs proper installation as the system default superuser handler...and it appears that needs to be done all while you already have shell root. I had very little time to check this out with a live Torque yesterday so I cannot give anything substantive on the "why" aspect other than rationalizing based off of how it ended up working.

Key steps are attaining shell root access via motochop, adb shell, successful switch into su and mounting the system folder as rw BEFORE running the SuperSU installation in Mkt247. After this, get your binary updated and change prompt to Grant. I'll eventually work with someone with a virgin Torque once things slow down a little bit.
[Android Q&A, Help & Troubleshooting] eriklion:
So, do I neeeeeed to use SuperSU? I was pondering using CWM Superuser as it's the closest to CM 10.1 I'm gonna get on any device.. :P I was on a roll this week. Got 2 devices rooted and one on a stable custom rom.
[Android Q&A, Help & Troubleshooting] jtabb1256:
I just emailed Kyocera and have yet heard back from them.

This is the email that I just sent to Kyocera. I'll edit this when they respond. If anyone has any answers to any of my concerns/ questions, feel free to tell me, but after reading this entire thread and all of its comments, I thought this email might get some answers:

I recently purchased a Kyocera Torque and am very happy with my choice. It performs how it is supposed to, but I do have two issues with it. The first issue is that if I leave my phone on over the night while it is charging, I will wake up to an unresponsive phone. I have to then take off the case and backing and take the battery out for the phone to be able to turn back on again. This gets very annoying very quickly and probably isn't good for the water seal on the backing if I have to continue to do this as a daily task. I am running Android version 4.0.4, software version 1.007SP, Hardware version 010B, Baseband version 1.007SP, and build number IMM76I. My kernel version is: 3.0.21-g7ca4fa7 build@Kyocera #1 SMP PREEMPT Thu Apr 18 10:26:35 JST 2013. My second issue with this phone is that it appears that the recovery mode is locked and that when I get into recovery mode by pressing down the volume down button and power button, the recovery mode seems to be in a safety mode and gives me an error saying: Can't find misc. I also have not been able to access the bootloader via adb or button combinations, but perhaps I haven't tried the correct combination of buttons. Could you please tell me how to fully access the bootloader and recovery mode and even maybe how to root this phone? I don't care if this voids my warranty with Sprint. I am a learning android programmer and would really appreciate it if you could please help me to root this device so that I could fully use this device to its abilities and fully use its powerful operating system. There are many people who would like to root this phone, as it would allow much more development options for it. I would really appreciate it if you could please tell me how to perform these steps and answer my questions/concerns. I'm sure that achieving root on this device would turn quite a few heads toward the Kyocera Torque and would probably help sales. I will appreciate any help that you can give.

-I hope they will answer my questions. :fingers-crossed:
[Android Q&A, Help & Troubleshooting] jtabb1256:
My attempt to push things to xbin

I did some digging in old files and found some old pheonix rom 0.2 stuff for my samsung replenish. I thought to myself, "What makes this rom rooted?" Then I remembered something about how root access is achieved when you put su in xbin, so I pulled some files from xbin in phoenix rom 0.2 and tried to push them to xbin on my Torque using ADB, but it failed because they were "Read-only file system". Maybe we could do something with these files? I'll attach the error messages and the files. ONLY DO SOMETHING WITH THE FILES IF YOU'RE CONFIDENT YOU WON'T SCREW SOMETHING UP! I don't want anybody to screw up their device using these files. Only use them if you know what you're doing. Maybe somebody could work with me to make this work? Or maybe it's just a stupid noob idea. Idk. I just think it might be worth a shot.

P.S.: I attached the xbin from under system from the phoenix rom. If anybody wants more than that, I can give the whole rom zip file, but it's too big to upload on this forum. The files that catch my eye are su, sulogin, and switch_root. Maybe there are more in the xbin that can be useful.
[Android Q&A, Help & Troubleshooting] VicFreeze:
Your posts are the reasons why others with the ability to chime in with constructive additions often don't...

For one, yes, SuperSU in conjunction with its binary appears to be what is working right now and the way it's described (so, yes, you "neeeeeed" it for the time being). If you want to try other options, do so at your own success or peril (that's what the scene is about: trial & error), but the steps to a tried and true working root solution are there...they are right there.

Second...."what makes this ROM rooted?" Yes, the binary in xbin or bin is ONE part, but you cannot just inject files all willy nilly without the use of exploits and not all binaries & handlers play nice with this device...If it was that easy, it wouldn't have taken this long. Before writing that exhaustive email, I hope you bothered to REALLY read through this thread (especially just a few posts before yours). Root is there...though there is no spoon-fed "one-click" in the OP or a cookie-cutter guide (yet), it is there. Root is usually not an OEM-supplied script either, fyi.

Please, people, really try because this was not a fluke. It is repeatable, so work with it for right now before randomly throwing other stuff into this thread and screwing other people up. If anything, great input would be improvement upon the steps to possibly allow for an alternate step-by-step that also fully works. For example, an earlier post in this thread alluding to SuperSU having the best results with 1.006SP is what led me to try to keep working with that in the current OTA.

Root is there...TESTED and there. Try and retry until you get it going. Yes, my posts in particular may be wordy, at times, but it is only to be thorough. Please read. I implore you.
[Android Q&A, Help & Troubleshooting] jtabb1256:
I did thoroughly read the thread and plan on trying your root method and appreciate the work you put into it. I only emailed kyocera that so that I could see what they would say. Maybe they have something built in that we don't know about? Highly improbable that they will say anything useful, but still worth a try. I was going to wait until more people tested your root method before trying it myself as this phone is my main and I can't have it acting up, but if you're confident in it, I'll try it out. I was also wondering if it was possible to do any of this using an android shell terminal. And when you say that I'm the reason people don't post contributions, I did warn you that my idea was a noobish one.
[Android Q&A, Help & Troubleshooting] VicFreeze:
All of it is done in shell...There are scripts performed via executables, but it is all done in shell. Go ahead and let more people try it I guess. There are less than a dozen or so people contributing anything to this plus the unknown (possibly few) others that pop in and don't provide feedback. That is how these things are created and tested.

Also, presenting random "noobish" ideas (and attachments) with warnings is, at times, even MORE dangerous because people on here do not read and just go blindly into the fire...it isn't until AFTER something happens do they come back to try to get emergency device support. I am guessing that the paragraphs & paragraphs of words in my post will turn folks away from "trying" it, but it is what it is. I was trying to contribute and figured that would be the new jumping-off point for folks, but the immediate next two users seemed to have the need to deviate and take the focus back off into obscurity.

I'll get off of my soapbox and just let yall have at it. Maybe the new owner of the rooted Torque can give you guys further insight and you can chop it up with him. -Vic Out-
[Android Q&A, Help & Troubleshooting] jtabb1256:
Should I delete my post?
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
Looks like I might be getting called out :)

I'll be happy to help any way I can. I do understand what you did to root it, and it should be relatively easy to replicate if people take their time and read Vic's instructions carefully.

Since there is no forum for the Torque here, I will probably be primarily posting on Androidforums once I have time to get used to my new phone.
[Android Q&A, Help & Troubleshooting] jtabb1256:
I followed his instructions and am successfully rooted, although I haven't fully tested it yet. One thing I am wondering is if this phone even has a boot loader.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
So in case anyone missed it, I have Vic's Rooted Torque. I haven't swapped service to it yet, but will by the end of the month.

Until then, I'd be happy to do what I can to test or help. If useful, I would be happy to do a system dump if I can get a walkthrough on how to do it :)
[Android Q&A, Help & Troubleshooting] jlmancuso:
Follow directions in second post
[Android Q&A, Help & Troubleshooting] -]AF[-Death:
Unfortunately framaroot does not work well :(
[Android Q&A, Help & Troubleshooting] jlmancuso:
Dont know what to tell you except every user here has used it.
[Android Q&A, Help & Troubleshooting] -]AF[-Death:
Is it safe I mean the new Torque.

http://www.kyoceramobilephone.com/de/s701/

This should be identical to the Kyocera Brigadier
[Android Q&A, Help & Troubleshooting] jackijumbo90:
That's the one we're talking about.
[Android Q&A, Help & Troubleshooting] adamtoinfinity:
System Apps Backup?

Can somebody make a backup of all their system apps with TitaniumBackup or something and send me a link to them? I'll pay you $5 USD in bitcoin for them. I was a bit overzealous in my deletion of them, and deleted a few that I actually need for the phone to function properly.
[Android Q&A, Help & Troubleshooting] GAMERAIDER99:
Torque root

My buddy has the old torque and I rooted it the other day via framroot so he could use the phone as a hotspot. Everything was working fine for a few days and then his girlfriend was screwing around with the phone trying to watch neflix and somehow booted the phone into safe mode. I rebooted it via the bootloader to get it out of safe mode, but now root is gone. I tried rerooting it and when i click gandalf it says successfully rooted and after reboot superuser isn't installed. Does anyone have any suggestions the guys house burnt down and this is his only means of internet because he lives out in the country. Also I use rootchecker after every atempt and it fails. Any help would be appreciated.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
What software version are you on and what version of root did u try?
[Android Q&A, Help & Troubleshooting] GAMERAIDER99:
Version 4.1.2 and framroot 1.9.3 it won't install superuser after restart.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
Try Framroot 1.90. It works but won't say it will.

Edit: posted 1.60 but meant 1.90
[Android Q&A, Help & Troubleshooting] FilthyAppetite:
Problem with 1.9.0

Tried as you suggested 1.9.0 with 3.000sp,

it said it worked, didn't install SU..

Wireless tether would finally start, but said errors..

However, even tho tether was running, it was not visible from another device.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
http://androidforums.com/index.php?threads/734700/
[Android Q&A, Help & Troubleshooting] FilthyAppetite:
I don't see anything useful there, as the phone is 3.000sp..

I've tried both a software and hard reset but cant seem to downgrade the firmware.

So lame..

I've read post about people claiming farmaroot 1.9.3 worked on their 3.000sp phones, but I've tried atleast 20+ times now and nothing.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
U aren't being clear, so I will.

I don't recall if FR 1.60 or 1.90 will work, but ONLY one of those two will work. You need to reboot immediately after trying and then install SuperSU from the Play store, as Framaroot will NOT install SuperSU as it says it will.

After you install & opened SuperSU to update binary, follow my instructions I posted in the link to get hotspot working. Make sure you choose grant all w/o notification in SuperSU because it will NOT pop up giving you the option to grant root access request.

It works for sure. If you are having trouble, try a hard reset prior to rooting.

It should also be noted there is no stock ROM to flash if you screw up, so make sure you backup the files you remove from /system should you choose to uninstall bloatware.

Beyond that, it must be user error. I have rooted 7 Torques on various firmwares, including 3.000sp with no difficulty other than trying to figure out which version of FR works.
[Android Q&A, Help & Troubleshooting] FilthyAppetite:
Thx..

I installed 1.90 then rebooted and installed SuperSu ..

Then installed wireless tether and all is good.

Thanks man..

I guess the problem was it wasn't installing SU, and I thought therefor it wasn't rooted.

Thx again for the help :)

Again,

This was on a Torque running 3.000sp
[Android Q&A, Help & Troubleshooting] Sidewlk:
Anyone still using this phone? I'm switching from Verizon to Sprint and thinking about this phone. While I will miss the stuff like CM on my current phone, I think the hardware side makes it more appealing to me (I'm a very abusive outdoor person and work in HVACR).

Sounds like I can run TiBu and maybe get CWM going? Big bonus if I can.