yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] toberly:
Did they work for you?

Also I pulled the recovery.img and boot.img if anyone knows a user that can make a custom recovery. I submitted them to the online builder but it didn't work
[Android Q&A, Help & Troubleshooting] jlmancuso:
Yes it work fine thank you.
[Android Q&A, Help & Troubleshooting] x000x:
i found a forum topic with a guide http://xdaforums.com/showthread.php?t=1866545

but if its correct someone has to have Ubuntu. Maybe you can ask someone in that topic to help you build one.
[Android Q&A, Help & Troubleshooting] jlmancuso:
I run Ubuntu. Maybe I will look into it. I have done source builds for the EVO 4g and 3d. I am no developer so no promises.
[Android Q&A, Help & Troubleshooting] miketrill:
did anyone ever post a detailed write up to this? and if so, can someone show me the link?

---------- Post added at 10:54 PM ---------- Previous post was at 10:38 PM ----------

what do u mean go into settings?

i'm doing this on osx btw
[Android Q&A, Help & Troubleshooting] jlmancuso:
The settings in superuser. You must change it to grant all instead of ask. I am posting a pic of it. While this is a different ROM and superuser app it is the same principal.
[Android Q&A, Help & Troubleshooting] x000x:
I don't think you need to use motochopper anymore.

only thing needed now is http://xdaforums.com/showthread.php?t=2130276

i used the latest one 1.8.1 w/o problems.

make sure to click "Gandalf"

after SuperSU app is installed, go into the settings of SuperSU, and choose "Grant" for default access.
[Android Q&A, Help & Troubleshooting] miketrill:
one more question

awesome that worked. and link2SD is up and running. but i can't move apps to SD, it just says "Moving to SD..." forever. so i'm thinking maybe it's the way I partitioned the SD card? i partitioned it using Disk Utility and did both with file system ms-dos which can be both FAT32 and FAT16 from what i understand.

may i ask how you partitioned your SD card? seems like it should always work with FAT filesystems
[Android Q&A, Help & Troubleshooting] jlmancuso:
Your first partition should be ext3 or ext4 and the rest should be fat.
[Android Q&A, Help & Troubleshooting] miketrill:
.

it works now with both as FAT partitions. am i going to run into problems in the future?
[Android Q&A, Help & Troubleshooting] jlmancuso:
Well if you use the link2sd or similar it will want an ext2-4 type partition.
[Android Q&A, Help & Troubleshooting] jeffyxd:
flashing torque to metro.

I just recently got some torque's from ebay also and cant find anywhere how to flash them and unlock the lte sim? could you help me out compensation can be available
[Android Q&A, Help & Troubleshooting] jlmancuso:
The two I got off ebay did not have a lte sim. I just flashed it with DFS tool. I installed all the drivers for torque and my donor (a cheap samsung from cricket). Rooted both phones to get the msl (needed in DFS). Put both phones in diagnostic mode, connected the donor and pulled all the info off it. Next connected the torque and wrote all the info to it. Talk, sms, 1x, and 3g worked (no lte since cricket and sprint use diff freq for lte). Then I setup the apns and mms worked.

You mentioned that you are wanting to use metro pcs so you can look over a few guides for flashing to metro to get the apn info you need.
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
The Torque does NOT have a GSM SIM card slot, so you'll have to flash it to a CDMA carrier.

If you need a guide, the process is exactly the same as flashing a Samsung Epic (and there are plenty of guides floating around). Only difference I am aware of is how you put the device into diag mode; it's ##3424# on the Torque.
[Android Q&A, Help & Troubleshooting] jeffyxd:
i was able to get all the information such as meid msid and metros aaa password then i used QPST to flash the stuff now voice phone calls and sms text messaging works but i cant get 3g data or any data for that matter working. As for lte sprint uses a tri band lte frequencies of which metro uses 2. Now i was told once the torque connects to the cdma data network the lte sim will unlock and use metros bands.
[Android Q&A, Help & Troubleshooting] x000x:
anyone know how to put this phone on a sprint mvno? from my searching none of them seem to allow push to talk phones to be used on sprint mvno. i don't really care about the push to talk feature, i'd be perfectly fine disabling it. would i have to get a donor phone or something?
[Android Q&A, Help & Troubleshooting] jlmancuso:
You should be able to get it activated as long as the esn is good. They only reason they say no push to talk phones is because they don't have push to talk service. If esn is bad then you will need a donor phone.
[Android Q&A, Help & Troubleshooting] x000x:
esn is good, but a sprint mvno like ting for example won't allow it to be activated. they have a 'whitelist' of allowed devices.
[Android Q&A, Help & Troubleshooting] jlmancuso:
Well then find a cheap lte donor phone. Once you have service on the donor you can transfer the settings to the torque and tbey wont know the difference.
[Android Q&A, Help & Troubleshooting] x000x:
so i'd basically have to do the same thing you did to get yours on cricket?
[Android Q&A, Help & Troubleshooting] jlmancuso:
Yes
[Android Q&A, Help & Troubleshooting] SeynalKim:
Torque droidz match tv recovery mode boot

hello? i am new here in xdadevelopers..i just want to ask a question.. i have a mobile phone "TORQUE DROIDZ MATCH TV", so any body can tell me how can i boot in recovery mode on my mobile phone? thank you guys...:confused:
[Android Q&A, Help & Troubleshooting] x000x:
"TORQUE DROIDZ MATCH TV" is not the same phone as a Kyocera Torque.
[Android Q&A, Help & Troubleshooting] mrossgeek:
i nailed fast boot and download mode. go to start like your starting recovery and toggle to vol up with a sliding motion as to make both buttons at once before you make the vol up Button and same thing back to vol down it should boot into fastboot/bootloader it may take a few trys but once you get you can get it almost every time, to do download mode start like your starting recovery and then switch to vol up directly after a few seconds. these key combos must be acheived before the phone starts to boot. I've also found that changing how fast you change from vol down to vol up seems to matter. Slowly gets fastboot quickly get download mode.
[Android Q&A, Help & Troubleshooting] x000x:
i was able to get into download mode pretty easily with your instructions. with phone powered off i pressed power plus the vol down button for a few seconds, then before the phone displayed a splash screen and still holding power plus volume down, i slid my thumb to the volume up. not sure if this had to be done before the first splash screen, but that worked for me the first try.

still have not been able to get into fastboot though. I think one time i almost got it but my phone froze on the kyocera splash screen.
[Android Q&A, Help & Troubleshooting] SoHardcore:
Can someone help me out with the ownership & permission attributes of every folder/file under the /system folder????

I was moving some apps from /data/app to /system/app and I had actually rebooted several times without problem. But I ran into one problem with moving the GoogleSearch.apk (or whatever it's called) to Velvet.apk. Which was not really the issue. The issue is that even tho it was in the proper place, it had to be installed before it could be used... not just moved into the /system/app folder. And "adb push Velvet.apk /system/app" wasn't working, so it was suggested to run the remount system as r/w command, and THEN run "chmod 777 /system/app". I also ran "chown root:root Velvet.apk" before restarting, altho, it was never suggested to do this... it was just one extra thing I thought might help.

When I restarted,

the phone never stopped restarting!!!

It's stuck in an endless loop. I've got maybe 15 seconds or so to run some commands before the phone restarts again. I panicked and just ran a "chmod root:root /system/*", which was probably not the best idea. After that, I though to use the "dmesg" command, and I'm seeing a lot of errors, and the end of them are definitely related to inability to access apps in the /system folder.

Soooo..... folder and file ownership and permission of the entire /system folder could help me out a bunch. You have no idea....

EDIT:

I just thought to change the permissions of the entire /system folder to 777 now, and it actually got to a graphical screen where it halted the bootup process. But it still gave an error about some camera. But after one more reboot, I am no longer able to even use the SU command at all. Now it's definitely in an unrecoverable perma-reset. This is absolutely terrible. But perhaps a bitter sweet end for this phone anyway. I was hoping to make it a whole nother year. But a phone that doesn't have a recovery available is really not much good to anyone. FFS... SMH... WTFUUUUUUUUUUU
[Android Q&A, Help & Troubleshooting] toberly:
Are you sure that wasn't fastboot? Whenever I rebooted into fastboot that's the screen that showed. The computer recognizes it as fastboot but the phone just looks frozen

---------- Post added at 02:02 PM ---------- Previous post was at 01:57 PM ----------

Are you on 2.002 or a different one? I have the imgs pulled from 2.002 you could flash the system.img from fastboot and that should get you going again.
[Android Q&A, Help & Troubleshooting] x000x:
I wasn't sure at first. The only other experience I had with fastboot had a nice, simple gui involved and said 'fastboot' :o

like with google nexus device for example this.

i was just assuming that was how fastboot looked like with all devices
[Android Q&A, Help & Troubleshooting] toberly:
Ya its different on this phone. See if you can do it again then plug it into your computer and use the command fastboot devices. If it's there then we have a way to recover from bad flashes.
[Android Q&A, Help & Troubleshooting] mrossgeek:
I recoverd from bad stuff. I knew x000x was posting img files on dropbox so i screwed around with flashing whatever i had around and hard key fastboot always came up and once the imgs were uploaded I booted into fastboot and reflashed it with the proper images and away she went
[Android Q&A, Help & Troubleshooting] SoHardcore:
I was actually on 2.000 when I last checked.

Those images would be great. Can you post them to Dropbox or something?

I'm assuming fastboot is the thing you get to when holding Vol Up and Power at boot?

Just let me know. This is the first Android phone I've actually used on a daily basis, and now I'm panicking. :eek:
[Android Q&A, Help & Troubleshooting] toberly:
Fastboot mode

Ok, here is just a little bit better explanation on how to get into fastboot mode. I am just explaining mross post a little better, he found how to do it.

1. Start by holding power+vol down.

2. After about a sec, while still holding both power and vol down, hit vol up.

3. Let go of vol down while still holding power and vol up.

3. While still holding vol up and power, hold vol down.

4. Let go of vol up, the red light should come on and the kyocera screen should come up. Let go of all the buttons and your in fastboot! :good:
[Android Q&A, Help & Troubleshooting] SoHardcore:
WOW!!

I actually got into "Download Mode". Definitely a different screen from the Recovery Mode, which is worthless for my situation.

Is this Download Mode different from fastboot? Wasn't able to get into that if it is different.

So.... once I have the system.img file. Then what do I do?? Just type in these commands??

fastboot devices
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot reboot

???
[Android Q&A, Help & Troubleshooting] toberly:
if you got into download mode, you did the keys wrong. just pull the battery and try it again with my previous post. its a weird combination but when youll get it the phone will look froze. i would then use

fastboot flash system system.img

i think that should work. if not ask mross he did it with his. if you erase the boot youll have to reflash the boot img too
[Android Q&A, Help & Troubleshooting] SoHardcore:
I've got both good news and bad news now.

I was able to get into fastboot. YAY!!

I realized I didn't have fastboot installed, so I downloaded the [TOOL]Minimal ADB and Fastboot [7-18-13] exe file to make it quick and easy.

I opened the folder as Administrator. And then I ran "fastboot devices", along with any other fastboot command... and it keeps telling me....

"< waiting for device >"

Are there fastboot drivers that are separate from the kyocera torque driver that I've already got installed?? Or do I need the newest version of fastboot?? Or am I hopeless at this point?
[Android Q&A, Help & Troubleshooting] toberly:
When you plugged it in did windows update look for drivers? It should be able to find the right ones.
[Android Q&A, Help & Troubleshooting] SoHardcore:
Hmm....

I am getting an error that pops up now:

Device driver software was not successfully installed.

Android ---------- X. No driver found

Maybe there's something else I'm not getting??

EDIT: I've got the 64bit kyocera driver installed. But the Minimal ADB & Fastboot is installed in the Program Files (x86) directory.... perhaps this is what's causing the problem??
[Android Q&A, Help & Troubleshooting] toberly:
Sent you a pm since I can't post links yet. Should be everything you need
[Android Q&A, Help & Troubleshooting] SoHardcore:
I tried a different laptop that had Windows 8.... and..... IT WORKED!!!

First time. No problems after getting a fresh Windows box. I actually like Windows 8 a good deal more than Windows 7 after installing the Pokki start menu. The backend of Win 8 is much better than Win 7.

But alas.... I wish I had known that all this was possible YESTERDAY, before I started wiping my personal data.

This definitely means that custom roms are possible, tho. So things are definitely starting to look up with this clean slate. Hell yes!! :good:

Thanks for the help, Toberly! :highfive:

---------- Post added at 11:34 PM ---------- Previous post was at 11:26 PM ----------

Now the question for me is....

Is it still easy to root on 2.300 ?? Or should I stick with 2.002?

I was reading earlier yesterday before all my drama began that some people who rooted on earlier 2.0** versions had problems when upgrading to 2.300...
[Android Q&A, Help & Troubleshooting] UPdownLoAD:
I unrooted and 'restored' all the APKs I removed to upgrade to 2.300. Root was kept on upgrade.
[Android Q&A, Help & Troubleshooting] mrossgeek:
Download mode

Does anyone know what Sprint or Kyocera are using to push full system images to devices with download mode? I remember using flashing tools to do updates back in the day with download modes. I also remember being able to apply some really good tweaks to the phones system because it flashes the system as a whole, things that just flashing images with fastboot can't and won't do (such as boot parameter stuff, change signing keys, removal of signing keys, partition sizes and locations). Does anyone know if said software will be be device specific? I can't remember anymore if I used a generic utillity or device specific. Does anyone know know of windows drivers for it when its in download mode? The computer I use at work is running windows XP. It seems to want a KL21 driver. I can't locate that specific driver. I run linux on all my personal stuff at home. My linux boxes see it but in download mode its not a fastboot or adb device so I cannot communicte with it. Download mode could be really useful if we could get ahold of a copy of the software that communicates to it download mode. I'm itching to play maybe this week I'll set up SDK on my new alienware and start trying to mess with compiling a custom recovery again all my previous attempts failed, but i was running 32 bit linux on my previous machine and I don't think i had it set up right to run on 32 bit I'm a little new to devoloping on android so any good info anyone has on getiing a proper build environment rolling on a 64 bit linux distro would be really helpful. If I figure anything out I'll post back as soon as i can.
[Android Q&A, Help & Troubleshooting] x000x:
I'm on 2.300sp and rooted. it was very simple. at the time i used Framaroot 1.81 w/o any issues. i see there is a newer version, but i have not tried that one.

I'm running windows 7x64, while in download mode i plugged the phone in and it attempted to install a driver but failed. gave me a message about the KL21 driver not being properly installed or something.

on the kyocera site http://www.kyocera-wireless.com/support/phone_drivers.htm i see 2 windows drivers:

32bit Driver	kc02us_setup_x86.msi (7.02 MB)

64bit Driver	kc02us_setup_x64.msi (4.80 MB)

not sure what they are used for though.

edit: installed the x64 driver, plugged the phone back into the computer while still in download mode and it gave me this:
[Android Q&A, Help & Troubleshooting] jlmancuso:
How much of a difference is 2.3 from 2.002?
[Android Q&A, Help & Troubleshooting] x000x:
from what i recall it was a very minor update. not sure why the huge number change between the two b/c i didn't notice much, if any, difference between the 2.300-2.002 versions.
[Android Q&A, Help & Troubleshooting] jlmancuso:
Okay. It is my gf's phone so I will hold off on updating.
[Android Q&A, Help & Troubleshooting] mrossgeek:
Cool I'll try and install the drivers on my pc at work this weekend. I thought I already did but we are on our 7th computer in my departments office in the past year.
[Android Q&A, Help & Troubleshooting] SoHardcore:
Supposedly 2.300 has "HD Voice" or something like that. So the call quality should be better. Haven't heard either way from someone who was conscious of the actual effect of this change. But the idea sounds good. :cool:

I guess I'll update and see how it goes...
[Android Q&A, Help & Troubleshooting] SoHardcore:
Well, I _was_ going to update it. But every time I go to "Update Kyocera Software" and attempt to Download the new firmware package, it fails instantly and tells me to "Please try again later".

I'm wondering if something in the system.img I installed has something to do with it. Other than that, the only thing I've noticed about this system.img is that at boot it says "Please wait.... Preparing for encryption. Process may take several minutes." But I have absolutely no problem with this at all, because there is no annoying boot up sound like there was before. Anyone know how to the bootup sound and/or encryption features manually??
[Android Q&A, Help & Troubleshooting] toberly:
Haha sorry man. I disabled the boot sounds and changed the boot animation to that. It's not actually doing anything. Forgot I did the pull after that. Mrossgeek has the 2.300 system img that you can flash to update.

EDIT: did you flash the boot. Img too? If not there might not be a match and it might not update. I redid my system back to stock and pull it again to have it on hand if needed. It won't be til at least tomorrow I'll let you know when it's up. To do it manually its back a few pages on this thread. The backups are in the same folder. Just delete the words disabled and backup to reactivate them
[Android Q&A, Help & Troubleshooting] SoHardcore:
No need to apologize!! I like the changes a lot.

I see that the boot sound file can be renamed and it will stop that. But I didn't see where you got the boot animation. :cowboy:

I'll try installing the boot.img and see if it allows me to upgrade. Do I need to flash the recovery.img, too? Was anything changed in there?
[Android Q&A, Help & Troubleshooting] toberly:
I don't think the recovery should matter but I'm not sure. I don't know if the boot will make a difference either but it's worth a shot. I found the boot animation in the same folder as the sound. I just made a coy of it and changed the name to the sprint one that I made a backup of. The boot sound was super annoying.
[Android Q&A, Help & Troubleshooting] SoHardcore:
Flashed the boot.img and it is still failing instantly. I doubt the recovery.img would make a difference if you didn't change anything to it.... so don't think I'll change that.
[Android Q&A, Help & Troubleshooting] toberly:
Are you above 50% battery and plugged in? If it doesn't work from that then you'll have to get the other system img from mrossgeek or x000x. If you can't get it from them I'll update and pull it sometime for you
[Android Q&A, Help & Troubleshooting] SoHardcore:
Definitely above 50% and plugged in.

I'll just wait. :cool:
[Android Q&A, Help & Troubleshooting] mrossgeek:
FYI

For everyones information. My radios failed again sprint gave me a brand new device, so i have bone stock 2.300 I can rip out, Although I have a 2.300 system rip that seems to be stock its the one I put on the phone before i returned it. only thing that won't be stock is it will need me to root it in order for dd to be able to access the /dev folder to rip the partition images out. I have noticed on the 2.300 update my phone hasn't been rebooting on its own every 6-8 hours, but i've only had it like 24 hours.
[Android Q&A, Help & Troubleshooting] jlmancuso:
I got two used off ebay 2 weeks before xmas both had 2.002 and so far only issues they have is that when the battery gets low touchscreen acts up. For example the letter a is pressed and something else will show up. Never had any random reboots or freezes. I did read lots of reviews before purchasing and was a bit worried because so many people had major issues. Yet I needed a phone that had the ruggedness like this and some decent power. Only other option was the gzone but that thing sucks. Guess i just got lucky enough to get two good ones.
[Android Q&A, Help & Troubleshooting] mrossgeek:
I had reboot issues with my other one that sprint has now, but i am REALLY REALLY rough on my torque. I'd have to say if anyone has given it a true torture test it'd probably be me. I work on maintenance in a large machine shop. I go through 2-3 phones a year the torques final death was the radio software or hardware. In the past year it has fallen from the 40 ft ceiling in the shop onto concrete more thatn once, submersed in machine oils and coolant and even lost in the bottom of a cast iron chip container w/ machine coolant for 5 hours. not a scratch on the screen or the camera lens cover. after 3 falls from the ceiling the case started to split around the speaker phone button but it has taken a few more since then and sprint still reported no physical damage. I love the torque it is truely a beast. I saw the ballistic case at the sprint store the yesterday and WOW does that make me think with it this phone would be indestructable.
[Android Q&A, Help & Troubleshooting] x000x:
i really like the phone too. my only two complaints is the lack of android 4.4, and i think the back plastic battery cover could have been a little beefier. every time i pop it off i keep thinking one day i'll accidentally snap off one of those little tabs.

as for 4.4, i asked a few times on their twitter and facebook account if they are even considering it and... got no reply. maybe their twitter and fb is just for pr stuff and they don't have any answers, they mostly just post about contests etc.
[Android Q&A, Help & Troubleshooting] jlmancuso:
Kk can be done by unofficial builds once/if we get a custom recovery. As far as official release I doubt it will happen. I have had multiple high end devices (evo 4g, evo 3d) yet they only get one or two updates before they get nothing. The evo 4g went from froyo to gingerbread and the 3d went from gingerbread to ics. These were high end devices unlike the torque. So don't expect much for official releases. Now the evo 4g is up to 4.3 and the 3d is running kk they had a massive amount of great developers. The torque does not even have a thread on xda much less any developers.
[Android Q&A, Help & Troubleshooting] x000x:
yeah i'm not too hopeful really. the only thing i'm still holding on to is theres a motorola phone with nearly the same specs as this phone and its getting an official 4.4 update. i know, a different company etc, but if a phone like that is getting an official 4.4 maybe some others will too.