yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] calipso-l:
tried it more then 20 times to enter recovery with power button + volume up and down - no success
[General Questions and Answers] sl2208:
Duraforce PRO recovery mode

I was able to get into the recovery menu on my ATT Kyocera Duraforce Pro (hope it works for Verizon/Sprint/T-Mb versions):

1.Turn off your phone

2.Press and hold the power, vol up and vol down buttons at the same time.

3.After Kyocera logo finally appears release the power button but continue holding the vol up and vol down buttons until the reset menu appears.
[General Questions and Answers] SergP2008:
Please make a video how do you get into recovery
[General Questions and Answers] hgomezc:
Hello,

In a few days, my daughter will be dumping this phone, and I'm going to take possession of it to replace my current, ancient non-android phone, and finally go back to Android since my last device on Jelly Bean 4.1.2.

A few days back we had an issue with a stuck app, and in several intents, I was not able to get the DuraForce into recovery mode. Finally, I solved the app's problem by clearing the app's cache, and that was it, daddy was a hero again! But I was left with the doubt about the recovery mode.

However, now that the Duraforce is going to be mine, the first thing I'll do is to perform a factory reset (it has stock ROM), and then I would like to install a custom ROM on it to get it to the latest Android version available for this device.

So, I would like to join forces with someone doing the same, to share knowledge and experience while traveling this treacherous path.
[General Questions and Answers] TishPunk:
Hello! Did you get to root on your device? Do not you get to get into bootloader mode?
[General Questions and Answers] hgomezc:
I don´t have the phone yet, maybe in a couple of days. I'll let you know as soon as I manage to work on it.
[General Questions and Answers] scotty9009:
Recovery menu Verizon

With phone on hold power and vol- down when phone shuts down the red ligth will blink 12 times when light turns green release power button. From there you can get into bootloader light in upper left coner.
[General Questions and Answers] hgomezc:
This didn't work for my phone. Nothing happens at all; the phone doesn't even shut down while pressing that combination. Thank you anyways.

I've had the phone for a few days now, and I've tried a lot of ways to get it into recovery mode without success. My device was draining the battery very badly, it lasted about 5 to 6 hours on stand-by mode before going down to 2%, so I thought that I need to root it and install a clean rom instead of the AT&T stock rom. Besides, it has a lot of bloatware that I don't want.

Finally, yesterday my battery usage was way better, it consumed 15% in about 12 hours on stand-by, so it is an outstanding improvement for me. What I did is that I disabled the unwanted apps and configured the APN which was missing for my carrier. I'm not saying that the APN thing had anything to do with the battery drain, but I don't know for sure.

For the meantime, I will leave it as it is. If I still experience unusual battery drain, then I will try again to install a custom rom.
[General Questions and Answers] richie138:
doing this booted me into "Safe Mode"
[General Questions and Answers] JudahYehudi92:
I

I got the phone as well and for now there is no root for Android OS 6.0.1. Guess we gotta be patient
[General Questions and Answers] Celti:
I've found myself with a Duraforce Pro and am eager to find a way to root it. I don't know a great deal about the process but I know how to follow instructions if anyone wanting to work on this needs information from the phone to try and get this done.
[General Questions and Answers] Mr_Sm1th:
following this just got duraforce pro and would love to be able to get Galaxy S8 rom for the phone.
[General Questions and Answers] DevCake:
I've been trying to get into fastboot to unlock the bootloader with no success. I have the Verizon E6810 version. No button combo seems to do it and via ADB is a bust. Please post updates if you have one.

~DC
[General Questions and Answers] olegfusion:
Did somebody try to unlock bootloader? In developer settings there are OEM unlock switch, somebody tried to enable it and unlock via fastboot?
[General Questions and Answers] richie138:
I have tried this and it didn't work. neither adb nor fastboot will reboot to the bootloader for me. adb reboot bootloader reboots the phone "normally" and any fastboot command such as fastboot oem unlock just says < waiting for any device >

I'm using OS X but I've tried various things on Windows in the past without luck as well

:crying:
[General Questions and Answers] Sirachi:
Anybody have luck with this? I just bought the phone. Willing to work with a developer on rooting it.
[General Questions and Answers] Sirachi:
Found this link: http://www.androidinfotech.com/2016/12/root-kyocera-duraforce-pro-marshmallow-twrp.html

Anybody tried it yet?
[General Questions and Answers] Rickgmi:
Little circle

when I shut off phone then hold the Volume up and down with power button I get a regular boot screen but with a little round circle in upper left corner, it seems to stay there till I press and hold the power button then boots like normal.. could that be the boot menu blocked from the screen
[General Questions and Answers] BigBallSak17:
If you press the vol up/vol down/power buttons at the same time then when Kyocera appears on the screen release the power button but keep holding the vol up/vol down bottom. This puts you to where you can reboot to bootloader, erase your phone, clear cache partitions ..... May this will help someone. I sure would love to get mine rooted!
[General Questions and Answers] Sirachi:
No such luck for me either. Attempted on both Mac OS and Windows 7. When I reboot into bootloader it just sits there on the Kyocera splash screen.
[General Questions and Answers] gazumph:
I'm looking to root my Kyocera DuraForce Pro AT&T E6820. No luck anywhere.
[General Questions and Answers] :
Almost there...

The best way to enter bootloader mode is using the latest version of adb/fastboot from google in conjunction with valid drivers. If done properly, the following command will return a serial no: "adb devices". Then, one can type "adb reboot bootloader" which will boot the phone to a screen with the Kyocera logo and a tiny circle in the upper left corner (this is normal). You interact with the bootloader via USB Debugging from the PC it's connected to. Every command will take the form of fastboot <option> <command>. The command to unlock the bootloader is supposed to be "fastboot oem unlock". However, it and almost every other fastboot command, including "fastboot flashing unlock" fails. Once successfully unlocked, all of the fastboot commands should work as expected. Since Kyocera publishes a setting to allow oem unlocking in the first place (via developer options), it seems fair to assume they also provide a mechanism to actually unlock it. If one can accomplish that, rooting the device is all downhill.
[General Questions and Answers] :
Please, everyone. I implore you to recreate the above scenario in hopes someone will clear that last hurdle (or even bypass it altogether). If you find my instructions lacking, I'll happily provide clarification for anyone willing to try.
[General Questions and Answers] :
My efforts thus far were performed strictly from a Windows 10 PC using Verizon's flavor of the Duraforce Pro (E6810) running the recently released Android 7.1.2 (Nougat) update. They include but aren't limited to the following major points:

Installed the newest Windows drivers from both google and Kyocera.

Installed the newest and a deprecated version of the adb/fastboot executables.

Identified at least one other working fastboot command (fastboot getvar all).

Launched the recovery environment using a button combination instead of adb reboot recovery.

Connected multiple cables to both USB 2.0 and USB 3.0 ports.

Toggled the Legacy USB support setting in BIOS setup.

Inspected the recovery logs for anything useful (option 6 in the recovery menu).

Installed and studied the Android Development Environment for any leads.

All ideas, no matter how unlikely, are welcome and encouraged. The following specific conditions have yet to be ruled out:

Testing from a native Linux environment.

Testing on both the Sprint (E6830) and ATT (E6820) implementations of the phone.

Testing on a phone still running the stock Android 6.0 (Marshmallow) operating system.
[General Questions and Answers] :
ATTN: Moderators

I suspect this thread would attract more attention in another forum, possibly "Android Development and Hacking --> Android General" since the content here pertains exclusively to, and is the only such thread of any significance focused on rooting the Kyocera Duraforce Pro. If you agree, please direct me to the appropriate procedure and forgive my naivete. I am very new to the site as well as the newest participant of this thread.
[General Questions and Answers] :
Further experimentation with the following scenarios continued failing in a manner identical to previous efforts:

Fastboot from a native Linux installation of Ubuntu Live version 16.04.3 LTS amd64.

Fastboot with the phone in "System Update" mode, hoping for a correlation with Samsung "Download" mode.

Fastboot after removing all accounts, Google or otherwise, and disabling all security options in phone settings.

Until we can advance beyond "Bootloader" mode, our testing should focus specifically on Fastboot/OEM Unlocking.

Note: One can explore (but not touch) protected areas of the phone's native Linux file system from the ADE Device Monitor and other limited tools.
[General Questions and Answers] OPIUM57:
Root Kyocera Duraforce pro

Hello could you show how to proceed for Root Kyocera Duraforce pro thanks
[General Questions and Answers] :
Sure, I'll get right on that. :rolleyes:
[General Questions and Answers] emgo:
Rooting the 6810

Ynotme, I'll be watching your posts. I need root access on my Duraforce Pro 6810. Thanks for all your work. I just upgraded to Nougat.

Ken
[General Questions and Answers] NE-Phil:
Anyone Try this Neopodapsi Root?

So far, my Kyocera Brigadier is working just fine but I am interested in getting the DuraForce Pro. I also want to see if it can be rooted since the Brigadier cannot.

Obviously no luck at rooting it here so I just googled how to root the DuraForce Pro and came up with an interesting link. I'm unable to post the link as I don't have the qualifying 10 posts yet. I can tell you where it is. Go to Neopodapsi DOT com . Click on Android and do a search on DuraForce Pro. 4 articles appear, two of them having to do with rooting it.

Might be another dead end but you never know.

Phil
[General Questions and Answers] Nesbocaj:
Survey scam, good luck.
[General Questions and Answers] sanjananb:
Check these steps

Get root access will be via Rootkhp Pro free program.

load program Rootkhp Pro on a PC

Connect your mobile device to your computer

The program runs without installation

Click on the Root button and wait for the notification to start work

We are waiting for about 10 minutes and get a notification that you are ready

Attention! The end result may depend on the firmware version of your mobile device
[General Questions and Answers] :
Regarding the last two proposals; My initial impression of them is not positive. Even if we determine that one or both is feasible, each requires installing a custom recovery ROM which can only be accomplished after successfully unlocking the bootloader. That aside, I was unable to locate any reputable websites with independent reviews or threads corroborating their efficacy. I also found the terms and conditions of their software unreasonable and even preposterous. Furthermore, closer inspection of their actual procedures exposes them as generic instructions applicable to 90% of smartphones. Undeniably, the gaudy marketing and pervasive trickery stains their credibility the most. Since neither suggestion was even acted upon, I presume the authors have their own serious reservations. So, with all due respect, we need results not suggestions.
[General Questions and Answers] Celti:
Working from an Arch Linux system with a DuraForce Pro Sprint (E8630).

Booted into Android normally: `adb devices` lists the phone, `adb reboot recovery` boots into recovery, `adb reboot bootloader` reboots the phone with no special action and without the screen with the Kyocera logo and the circle in the corner. Selecting "Reboot into bootloader" from the recovery does the same thing.

At any point between rebooting the phone and getting back into Android proper (e.g., while booting and while in recovery) both adb and fastboot do not recognise the phone, and in fact the phone is not even listed in my laptop's current connected USB devices for adb/fastboot to work with.

I do have the Enable OEM Unlock option turned on in Developer Tools.
[General Questions and Answers] :
Got my hands on ATT's version (E3820) and was unable to the access the recovery environment at all. Customary adb commands just reboot the phone so fastboot useless. Holding both volume buttons while booting yields a featureless black screen with a dead android robot captioned "No Disc!" Now that we've examined all three varieties of the D-Pro (Thank-you Celti), we need to get creative with our research. To keep the momentum going, I'm chasing a few long-shots that I'll report back on soon...
[General Questions and Answers] :
I've captured the primary archive used by the update software for the E6810 which contains all of the latest internal partitions including, system.img and recovery.img among others all easily extracted using 7-zip. Next steps are to mount the system image (ext4) under Linux, add the su binaries, and re-insert the archive into the update software. The latter being the most challenging step because it likely includes anti-tampering protection of some sort.
[General Questions and Answers] OPIUM57:
Good job guy
[General Questions and Answers] hetty:
Any progress?

I too am looking for help to Root the Duraforce Pro. I really like the phone but have the problem with Android that it doesn't save new APN data or says the user cant do it. Hence the desire to Root it to try resolve this. I want to use it in multiple countries which my data subscription allows but it doesn't work.

I have tried Kingoroot, Towel root but like the first post, no joy.

Post #53 is incomprehensible to me :)...... looks interesting but I need more baby steps.

I have a Duraforce and it rooted fine with Kingoroot.
[General Questions and Answers] vodny:
No go with rooting this device for me either, but I have noticed on the Kyocera homepage, that it should receive Nougat update around 8th December, which may solve some performance problems it has. I tried to update it, but it didnt find it yet. Maybe my DFPro will not receive it anyway, cause I have the 2GB RAM variant.
[General Questions and Answers] :
Thank-you for the kind words, and I apologize for my lapse in communication. Instead of blaming the season or a full schedule, I really really want to believe my lack of progress is largely the result of a steep learning curve. I've spent far too long trying unsuccessfully to mount the image files I plucked from the E6810 update tool, and it's long past time to ask for help. Hopefully there's a Linux guru monitoring this thread who can/will determine categorically whether these partitions are indeed mountable and if the current path is still feasible. When/if someone steps up, I'll make the files accessible and recount the details of my fruitless efforts. In the meantime, I have no intention of giving up.
[General Questions and Answers] Celti:
Linux guru with a E8630 here, watching this thread eagerly. Shoot me a message and let's get cracking!
[General Questions and Answers] :
Thank-you Celti for coming forward and your contributions so far. Your confidence and enthusiasm is encouraging. That said, I must remind you that our work on the E6810 may have little or no bearing on the E6830. Alongside MTP, the USB menu on my phone includes an entry called "System Update" that is not present on the other two models. Selecting it creates a virtual drive containing proprietary software that downloads the latest OEM builds used to repair or update the device. I saved the source file (binfile74.bin) by replicating the Windows temp directory in realtime during a repair operation with a tool called Goodsync. The current package contains several files comprising Android Nougat 7.1.2 totaling about 1.5GB after being repacked. My actual attempts to mount them consisted of only the most basic Linux commands on a clean install of Ubuntu 16.04 loaded in VirtualBox. Many thanks and good luck. I'll make every effort to remain responsive.

https://drive.google.com/file/d/1JvfbA6wI1SsafOLn4xMHxd0xKslJD3e9/view?usp=sharing
[General Questions and Answers] Celti:
It might, it might not. Either way, progress will be made for someone.

Taking a preliminary look at the file, it's a bunch of concatenated partition images and other files (I've noticed NON-HLOS.bin specifically, part of the baseband firmware image) prefixed with a Kyocera-specific security header.

Of particular note is a file in this bundle named "SUM_MEM_Script.txt", generated by something called "KC SUM calc Ver 1.07" with what looks like filenames and checksums for the entire device structure. Ought to help with extracting these safely.
[General Questions and Answers] emgo:
Thanks to all of you working on root for the Duraforce Pro. I have a 6810 that I would really like to get rooted, I'll be watching.

Ken
[General Questions and Answers] Celti:
You now can find all of the files extracted from the binary at https://repo.celti.name/kc/. They all appear to be bog-standard Android sparse images/bootimgs/the various other bits and blobs that make up an Android update.
[General Questions and Answers] :
Your altruism is refreshing even now. Did you too encounter errors mounting the partition images, mainly system.img and recovery.img? The others, including those inside gpt_main.bin, are inconsequential at the moment.
[General Questions and Answers] Celti:
I have not. system.img is an Android "sparse image" ext4 filesystem while recovery.img is an Android "boot image". Have you worked with either format before? There are standard Android development tools for both, but I prefer using IMGtool; simply run "imgtool system.img extract" and "imgtool recovery.img extract"; the former will generate a mountable image file,. while the latter will generate a kernel, kernelimage, and a .tar.gz format ramdisk.
[General Questions and Answers] :
Thank-you. That's what I was hoping to hear and exactly why I asked for help. Since unlocking the bootloader seems unlikely, I laid out a quick plan earlier to 'import' the superuser binaries to the system image so they would automagically appear in the system folder when the repair operation completed (Specifically busybox and su in system/bin and Superuser.apk in system/app). It sounds like that solution is still workable, though not as straightforward.
[General Questions and Answers] :
The next step requires editing the contents of an Android sparse image as stated above. Celti, are you still able to assist with this task? Since the target partition is now available for download with the main package or individually, I urge anyone with a comparable skillset to undertake the challenge. Meanwhile, I'll commit my limited patchwork of free time to learning the ability.
[General Questions and Answers] sudex1:
huhu

I am new to this forum and a new owner of the DuraForce PRO E6820 6.0.1 (3.017AT) at&t branding and bootloader signature.

Though I got no android/linux skills I try my best to get that rooted. I found kernel and other software here: kyoceramobile.com/support/developers/

but not sure if this is a clean kernel or the same at&t plaqued kernel already installed.

Through my researches I also found this document niap-ccevs.org/MMO/Product/st_vid10742-st.pdf and wonder if it may help.

cheers sudex.

be back soon.
[General Questions and Answers] Rafael4096:
Not sure if this helps, but I am working on buying a secondary Duraforce Pro so I can experiment without losing my primary phone.

If anyone comes up with test methods or files, I am willing to risk my "spare" for the cause. I love the phone, but not the bloat.

I really hate the messaging app, its really glitchy and cumbersome. I prefer the Google messages app, but it doesn't seem to play well with the Duraforce Pro.
[General Questions and Answers] ColdAtrophy:
I'm new here and I'm no hacker, but I just wanted to say thank you to you guys that are working on the Kyocera DFP. I have an E6820 (AT&T) with Marshmallow 6.0.1 and I am more than willing to help however I can. I've exhausted all the usual stuff with ADB and Fastboot and got stuck at not being able to get into the recovery or the bootloader so I'll be in watching with great interest.
[General Questions and Answers] :
Thanks everyone for your enthusiasm and various snippets of information. Aside from my work on the E6810, our best odds ride almost entirely on finding and exposing a vulnerability. The kernel images on the Kyocera web site are actually classified by service provider suggesting congruency with commercial releases of the same version making them viable test subjects for potential weaknesses in the E6820 and E6830.
[General Questions and Answers] duntou:
root my e6820 not success

adb reboot bootloader

<waiting devices>

Anyone have a new way? thanks
[General Questions and Answers] Rafael4096:
Got my spare Duraforce Pro

Got the spare today so I can experiment without losing my personal phone.

If anyone has ideas to try, glad to try it on my spare if it looks like it wont permanently brick it. It still may brick, but I am willing to try.
[General Questions and Answers] wanderingturtle:
I am considering buying this phone, since it is the only durable verizon phone I can find on the market. I would want to install a custom ROM like cyanogen. I don't have the skills, but I could contribute to a bounty to get this done.
[General Questions and Answers] ColdAtrophy:
I'll 2nd that. I'm willing to throw down some cash to make this happen. Someone fire up the bat signal.
[General Questions and Answers] ilia3367:
Tell me please, does the Sprint phone have a bootloader mode?
[General Questions and Answers] :
I will at least finish the work I started on Verizon's baby (E6810) using the recent update as proof of concept. Look for results within a week.
[General Questions and Answers] emgo:
I'm anxiously waiting on root access for my 6810. Will this be for the Nougat update?

Thanks,

Ken
[General Questions and Answers] ilia3367:
The Verizon bootloader will never be unlocked.
[General Questions and Answers] emgo:
I was thinking you could have a rooted phone without having the bootloader unlocked, it that incorrect?