Kyocera DuraForce Super Thread

[kemonine96]

Welcome to the Kyocera DuraForce super thread

There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.

I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.

There is a Lollipop update available for the device as of early February, 2016. I have found a way for users to update if the OTA fails (see below). I've also updated the below posts with information regarding the Lollipop update and moved the KitKat notes to another location (link for old notes is below)

 

[kemonine96]

Ota - lmy47v1218_2217

For those who are having trouble applying a FOTA on the DuraForce, check /cache/fota/xyz_fotalog_123.dat It's a text file that contains a lot of really good info on what is going on during a FOTA. Including errors. Keep a look out for signature mismatch errors.

I had errors with the following files. Took me a few tries to get the OTA applied as each attempt resulted in one error.

• Uninstall Xposed (moar hacks)
• /system/usr/keylayout/gpio-keys.kl (disable PTT/Speaker buttons)
• /system/etc/permissions/platform.xml (sd card "fix")

If trying to address the issues manually does not work, follow the procedure below.

1. Download "vanilla" system image from HERE (link)
2. Extract zip file
3. Ensure at least 2Gb of storage is available for internal data
4. adb push mmcblk0p21_KVT49L_0617_0132 /storage/sdcard0/
5. adb shell
6. su
7. dd if=/storage/sdcard0/mmcblk0p21_KVT49L_0617_0132 of=/dev/block/mmcblk0p21
8. Reboot phone once it completes. It will take awhile and not report anything during the process.
9. After phone boots, run "adb reboot recovery"
10. Wipe data / factory reset
11. Wipe cache
12. Reboot
13. Run software update

 

[kemonine96]

General Notes - Lolipop

• Force Reboot: Pwr + Vol Up + Vol Dn + Back + Home + App Switcher buttons for ~10-30 seconds
• Root: Use KingRoot from http://king-root.net/ -- I used the android APK successfully
• SD cards bigger than 32Gb still do not work correctly on stock firmware

 

[kemonine96]

Known Working Customizations

To be determined

 

[kemonine96]

KitKat Notes

All previous notes for KitKat have been moved to a document in box. The notes can be found HERE (link)

 

[kemonine96]

Sources / Mirror(s)

The OSS drop is available on Kyocera's developer site: http://www.kyoceramobile.com/support/developers/

Misc file mirror: https://nuskunetworks.box.com/s/p5hwq3hboctl0saze0wkcv3jzfefuw45

 

[tomzweifel]

Do you trust Kingo?

I'm THRILLED to hear you were able to root and freeze all the AT&T crapware. I can't wait to do the same. But how do you feel about Kingo? I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?

Welcome to the Kyocera DuraForce super thread

There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.

I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.

If you're looking for root, look no further than Kingo. I can confirm the Windows version of Kingo is working on the AT&T varient of the DuraForce.

 

[kemonine96]

How do you feel about Kingo?

I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.

I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?

Fair enough, I was able to replace Kingo with SuperSU pretty easily:

1. Install SuperSU from Play Store
2. Run SuperSU and update su binary via "Normal" mode
3. Authorize SuperSU when Kingo prompts
4. Allow SuperSU to replace su binary
5. Freeze/Remove Kingo
6. Reboot and enjoy SuperSU
7. Optional: cleanup other Kingo remnants

 

[tomzweifel]

Components to clean up?

Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.

Thanks for the information!

I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.


Fair enough, I was able to replace Kingo with SuperSU pretty easily:

1. Install SuperSU from Play Store
2. Run SuperSU and update su binary via "Normal" mode
3. Authorize SuperSU when Kingo prompts
4. Allow SuperSU to replace su binary
5. Freeze/Remove Kingo
6. Reboot and enjoy SuperSU
7. Optional: cleanup other Kingo remnants

 

[kemonine96]

Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.

Thanks for the information!

Unfortunately I don't have notes on what Kingo leaves around on /system... Some searching online or poking about /system should yield results.

 

[tomzweifel]

New OTA Update

I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.

 

[kemonine96]

I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.

Please do. I haven't gotten any notifications yet and I'm kinda curious what the OTA will contain.

 

[Dkesler76]

http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820

Software update includes

Kyocera Remote Lock

Miscellaneous improvements, fixes, and security updates

 

[kemonine96]

http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820

Software update includes

Kyocera Remote Lock

Miscellaneous improvements, fixes, and security updates

Thanks for the heads up. Too bad it's not L.

 

[Dkesler76]

Thanks for the heads up. Too bad it's not L.

np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan

 

[kemonine96]

np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan

I managed to free up some time this weekend and I'm going to be pulling the OTA and seeing what I can do for re-packing it for those of us who are rooted and/or de-bloated.

Will post back with more info after I've had some time to poke at the OTA some.

Edit 1: Looks like this has patches for system and boot. /cache/delata looks like the directory where everything was downloaded. Hopefully binwalk and some other tools will yield useful information on what's contained within.

Edit 2: Looks like I was able to install the OTA despite being rooted. I'm waiting for 1st boot to verify root persisted and I'm also working on mirroring a number of partitions that can be used to "go back" to stock as well as images for updated partitions post-OTA.

 

[kemonine96]

np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan

I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here

You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.

Edit: The posted file is for an ATT device

 

[kemonine96]

Good news everybody! The ATT OTA doesn't remove root and can be installed as-is provided you've not de-bloated the ROM or installed Xposed. If you've de-bloated (see below) you'll need to restore the missing bloatware and if you've installed Xposed, you'll need to uninstall it prior to applying the OTA.

In one of the early OP's there's a link to the "misc file mirror" that contains partition images for boot and system partitions. These are from an ATT device and can be used to restore back to a state that'll allow the OTA to apply.

Happy hacking and OTAing everyone.

 

[Dkesler76]

I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here

You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.

Edit: The posted file is for an ATT device

weird i tried dd and busy box and no go not showing up on device

 

[kemonine96]

weird i tried dd and busy box and no go not showing up on device

What isn't showing up?