yashsingh1/xdaforums huggingface dataset:
[General Topics] nugiedha:
Hi all..need help

If the device hangs on 5.1.1 while charging the phone is off

Find answer on

https://4pda.ru/forum/index.php?showtopic=732962&st=420#entry57925998

but file not found

Anyone?
[General Topics] gnanava:
how to enter recovery or fastboot mode on kyocera duraforce pro att?

i want to know key combination, not adb command
[General Topics] jayram1408:
I have had a Dura Force HD thats FRP locked for over a year now

Can anyone tell me how to FRP bypass this phone? I have FRP bypassed my S5, ZTE Z981, aS8 s8 edge+, actualy quite a few but for the life of me I can find no way to do it on this phone. I have seen hundreads of YouTube videos, been to all the forums and Nada, not even anything here. It is a E6790TM Kyocera Dura Force HD. Thats as much as I know as thats as far as this phone will let me go. I can not figure it out and its not from not looking first and trying 50 million ways to Sunday. Trust me I would not post this if I didnt look very hard and try several options before wanting to brick this phone by chucking it into a brick wall. It has not come to that yet but Im near my wits end with this thing. Thasts how much of a head ache this thing has caused me. Thanks to anyone who can help. By the way I looked for a year literally first because sometimes I get stubborn and want to figure it out on my own. Im not going to buy one of them Sigma boxes for one phone either.
[General Topics] ndt44:
Hello,

See my post on the DuraForce Pro thread:

https://xdaforums.com/general/help/how-to-root-kyocera-duraforce-pro-t3502056/post77750183

Edit: hmm- the link didn't post correctly--see page 9 of that thread towards the bottom.
[General Topics] calipso-l:
hi! does anyone have any idea where and how i can unlock duraforce pro 6820 under contract?

thanks
[General Topics] grundlestain:
does anybody know if the e6560L variant is the same as anything else? can i flash the e6560 5.1.1 on it?

I bought this unlocked phone online and am using on T-mo.

Update: It will not take anything that is posted here, and the links at the begining are dead.

If anyone can provide me with any image from a canadian telus e6560L please feel free to do so... Thanks
[General Topics] azaliaperez:
informacion

hola amigo queria saber si existe algun fimwere lolipop para mi kyocera e6560 , ya que con el actualizador de sistema no me funciona actualizar el android ,y si existe algun lugar donde poder descargarlo me avisas xfa , soy de managua nicaragua
[General Topics] edyasia:
duraforce e6560c

Hi. i have a6560 with security error due a failure on upgrade...

were i can find rom and method to recover it? thanks in advance

https://ibb.co/3sSNRqv
[General Topics] Lil.nguyen:
E6810 root?

need help to unlock bootloader and root Kyocera Duraforce Pro Verizon (E6810) !! Please
[General Topics] BigB451:
I've been using a DuraForce Pro 2 on Verizon for about 18 months. Visual Voicemail worked beautifully until I had to send the phone back to Kyocera for repair. Kyocera sent me a new phone, but VVM stopped working. I notice that the app icon is slightly different--the old VVM icon's corners was more rounded on the old phone than on this one. I suspect that the problem is that the new version of VVM isn't working with Verizon's services. Does anyone happen to have, or able to extract, the APK file for the DuraForce Pro 2?
[General Topics] Kaiser357:
I figured I'd try here first. Has anyone figured out a way to root a Kyocera Duraforce Ultra 5g (E7110)? I don't want to brick my phone, but I also think it has more potential. I'm most interested in Magisk right now, but I'm willing to give up on it if it's not feasible.
[General Topics] ReiJ2125:
I have this same exact model and here is what I've found.

Root is possible if the issue around the false OEM-Unlock option gets resolved.

And by false OEM-Unlock option, I mean that the device says oem-unlocking is enabled through the developer settings, but it does not enable oem-unlock from the adb & fastboot level at the very least.

When I tried to flash Twrp for android 11 [cause that seemed to be the only thing that may be supported on/for this phone], I kept getting errors like Flashing Unlock is not allowed etc. etc. Come to find out, the errors were happening because OEM-Unlocking wasn't enabled [note that it said it was in the dev options].

At first, I couldn't detect the device through fastboot [when it was in the bootloader] but could detect it through adb. This was because Windows 10 is stupid when it comes to drivers; however, a simple reinstall of some fastboot drivers made it work [kinda].

After I got fastboot working, I tried to unlock the bootloader to flash twrp using commands like fastboot oem unlock fastboot flashing unlock and fastboot flashin unlock_critical. Note that fastboot flashing get_unlock_ability returned the code [1] [1 = it is possible | 0 = it is not possible].

I agree with you that this phone has potential that, if left untapped, would equal a brick. The specs on this thing are amazing [for the most part] It has the majority of the capabilities on the software side. Sadly, unless someone can find a way to force oem-unlocking to be enabled, I highly doubt we can root this phone anytime soon.

~Rei
[General Topics] JiMBoTeK:
I have a similar issue. I cannot find the stock rom for E7110. I have malware that made it past the bootloader block.. I've got pics of the system log files 👍

I've got a similar issue with my E7110. I downloaded a crypto miner from somewhere I shouldn't have.. very intelligent malware. It successfully modified the bootloader and verizon's vendor privileges as well as adding custom permissions to modified pre-installed apps. I cannot get a true data wipe nor a true factory reset. Bootloader seems to be designed to block and deter all attempts to sideload. I think they call this variant HiddenMiner/MoneroMiner 👍

Here is what I found as far as stock rom goes->http://android-dev.kyocera.co.jp/source_en/versionSelect_duraforce-ultra-5g.html

The pics are from the system log accessed from the bootloader menus

[/QUOTE]
[General Topics] calipso-l:
hi

have any idea how to unlock it from verizon?

thanks
[General Topics] Suncatcher16:
Verizon devices are all unlocked out of the box
[General Topics] calipso-l:
not now

as well as verizon samsung xcover pro
[General Topics] Suncatcher16:
dunno about xcover, but when they were selling Duraforce Pro 2 it definitely was. It is already outdated phone, now they sell newer Kyocera Durasport 5G
[General Topics] tarasishe30:
I have Kyocera DuraForce Ultra 5G, and it's locked to Verizon.

contacted their tech support yesterday, they told me 60 days after purchase it will be unlocked.

Will waiting

Didn't find solution to unlock it earlier
[General Topics] Suncatcher16:
60 days is not a long term, it's easier to wait
[General Topics] Suncatcher16:
did it finally get unlocked by itself? Verizon keeped their promise?
[General Topics] jb881122:
This is probably many years too late, but I haven't seen it posted anywhere yet (even though a few Russians have evidently done something like this), so...

EDIT #2: There's really nothing new here. The aboot in the 4PDA zip file is an older version of the bootloader, which has no checks for the unlock status upon running "fastboot boot", so that's how TWRP is able to run even when is_unlocked is 0. At the very least, this shows how is_unlocked is determined and allows TWRP and custom kernels to run with the newer bootloader.

Kyocera DuraForce E6560 (AT&T) Bootloader Unlock -- Kind Of (Tethered)...​

WARNING: By doing this, you are overwriting your bootloader. This may result in a hard-brick if something goes wrong with the download or flash. Proceed at your own risk. I assume that if you are following this, you know what you are doing.

EDIT: This only works for boot images booted using "fastboot boot". Integrity for the boot and recovery partitions is still checked regardless of unlock status (this depends on use_signed_kernel() instead, which IIRC reads an integer given by SBL).

Download the attached aboot images, check the CRC32s (in case something got corrupted during the download):

e6560-aboot-unlocked.img: 43EE8C5A

e6560-aboot-locked.img: 7A60A3A8

Enter bootloader mode and run these two commands:

fastboot flash aboot aboot-unlocked.img
fastboot reboot-bootloader

To make sure it worked, run the following:

fastboot oem device-info

and look for the line "Device unlocked: true".

If you want to re-lock the bootloader, repeat this process using e6560-aboot-locked.img instead.

This works because some boot-related information, including whether the bootloader is unlocked, is stored in the last 512 bytes of the aboot partition in a block starting with "ANDROID-BOOT!". The is_unlocked field is 0x10 bytes after the aforementioned string. Here is a forum post on a different website that has a glimpse into the same behavior on a different phone (one with "fastboot oem unlock") and the relevant portion of the lk source code.

For a custom recovery, SergP2008's post (#197) has a 4PDA link where you can download a TWRP 3.0 image (which is larger than the phone's recovery partition, so it will need to be used via "fastboot boot TWRP_3.0.3.img").

Since linking to 4PDA appears to be frowned upon around here, I will mirror the recovery image here. If you download the zip from 4PDA, there's no need to flash aboot in the zip file if your bootloader is unlocked. In fact, I took a look and think it will re-lock your bootloader if you try it.

If anyone has any issues, let me know. Also, this method *might* work for other variants, but you will need to patch your own aboot partition manually (DON'T flash these files on other variants), so let me know if you have any questions on that as well.

EDIT #3: I've been looking for a way to boot unsigned images without the help of a computer, and while it's been a long road, I finally have something starting to work using the "unified boot method!" I'll make another post in the coming weeks when more comes of this.
[General Topics] Suncatcher16:
Awesome! I wish I'd found it couple of years earlier, this was so actively needed. Anyway you did a great job, better late than never.
[General Topics] bjorn-17:
Any tips on trying to unlock bootloader+root KYOCERA durforce pro 2 E6910 Kv

4.4.192-perf. I feel like I've looked everywhere online for methods, but came up empty.

Nevermind KYOCERA had made the bootloader unavailable and it is only possible to get Into recovery mode. They got my hopes up with oem unlocking.
[General Topics] jb881122:
Yeah, I wouldn't hold my breath. I'm in a similar situation with my LG K20 (M255) where there isn't a way to get it into the bootloader or to read/flash any partitions directly. A temp root might be possible using something like CVE-2019-2215, but I've never seen it exploited on 32-bit Android and I wouldn't know where to start given my limited knowledge on Linux kernels.

For the E6910, I see it's a bit newer than my K20 and has a 4.4 kernel (and likely 64-bit Android), so I'd check the security patch date to see if it's past Oct 2019 or not. That said, even if it's not, you'd probably be mostly on your own for exploiting it, as it's not a terribly-common phone so I doubt a large number of people would be pursuing root for it.

One other possible vector for reading/writing partitions is EDL mode, but I believe firehose files are signed for most phones, so you would need to find one specifically for Kyocera SDM630 devices (and probably specifically for the E6910 as well), which I doubt would leak or be released from Kyocera.

EDIT: I should probably mention this: Android Marshmallow and newer check the integrity of the system partition, so it can't be rooted in the same way as Lollipop and prior by dropping files on that partition. I think this is the main reason one-click apps like the ones that start with King and end with Root don't support newer versions of Android, as any permanent root would entail unlocking or bypassing the bootloader and booting a custom boot image. In most cases, that is pretty much impossible to do in one click.
[General Topics] bear-bjor:
Alt Account. Thanks for the information. I think I may just give up on this device. I accidentally bricked it while experimenting. To be honest I don't have much experience with rooting or anything of the sort. I've only rooted my nexus 5x. I put in the command adb reboot edl thinking at worst it would do nothing to my Kyocera. Since all other commands did nothing or just outright failed. Naive thinking on my part. I may just get a different phone that's easier to root, but thanks again for the info you provided me.
[General Topics] jb881122:
AFAIK, "adb reboot edl" shouldn't brick your phone. Holding some combination of the volume and power buttons (I think just the power button in your case, but try others if that doesn't work) for long enough should cause it to reboot. At worst, it will stay in EDL mode until the battery runs out, though I wouldn't recommend draining the battery if you have alternatives as that's not good for battery health.
[General Topics] bear-bjor:
I tried getting into recovery mode with volume and power, but that did not work. Same with just holding power button. Charging light would not go on when plugged in it was unresponsive. So, I went into the phone and just took out the battery and put it back in and that did it, rebooted like normal. Well, I am happy the phone still works. Still pretty bummed out that no such bootloader is on the phone. May just sell it and get an unlocked pixel or OnePlus. Thanks, jb881122 for still providing info on this forum.
[General Topics] jb881122:
I finally got something workable using the "unified boot method" I mentioned in an edit in an earlier post.

If anyone else still has an E6560 (AT&T version only) and wants to try it out, see https://github.com/jb881122/unified-boot-hijack.

Also, if anyone has a similar phone (must be rooted) and wants to see if this same method might be able to work on it, either contact me or reply to this post.

Hopefully, this is just the start of a long journey with this phone (and possibly others).
[General Topics] Average8821:
Anyone got around to rooting the Ultra E7110?
[General Topics] chozycorleon:
Did you get root?
[General Topics] breadopolis:
I'm trying to unlock the bootloader on a Kyocera Duraforce Pro model 6810. I'm hoping to port Ubuntu Touch onto it. So far, I've had no success. Here is a summary of what I've learned so far in case it helps anyone else:

The manufacturer's website hosts usb drivers.

They are .msi files, meant to run on Windows, not Linux.

On my Ubuntu host machine, I was able to open the driver file and list its contents with 7zip, but I'm not sure what to do with the binaries beyond that.

I've tested these steps using exe files on a Windows 10 virtual machine with the usb drivers installed. I used virt-manager, then gnome boxes, then virt-manager again, but I didn't get any farther than I did on the Ubuntu host machine without the usb drivers. I'm not sure they're necessary because adb accesses the phone's filesystem without them. For brevity's sake, I'm only including my notes regarding my Ubuntu host machine.

Backup the things on your phone that bring you joy before you start this process.

Enable developer options by tapping on “Build Number” in About Phone 7 times.

In your newly available “Developer Options” menu in Settings, find and enable “USB Debugging”.

Install adb and fastboot on your host machine.

Plug your phone into a usb port. A message box will pop up on your phone, asking if you want to allow your computer to debug your phone over usb. Accept this request.

Open a terminal, and type adb devices.

If you don't see your devices, disconnect and reconnect the usb cord.

If you see your device, but it is unauthorized, make sure you accepted the message on the phone and that usb debug is enabled in developer options.

Type adb devices again to make sure your device is connected and authorized.

Type adb shell.

Now you can take a little tour of your phone's directory tree using ls.

I tried ls --color -ARZn1 | more, but even with more, the output was so long it was unreadable.

I recomment typing ls and picking out individual directories from the standard output to look at, one at a time.

Run this command to peak at any directory or folder that appears interesting: ls --color -ARZn1 <directory> | more

There were many directories and files flagged as Permission Denied.

I tried typing su to get root permissions, but adb shell cannot locate the command on my phone. It is not in /bin/, and I can't see inside /sbin/.

Type exit to get out of the adb shell and back into your host computer.

Type adb reboot bootloader.

Your phone will reboot into the bootloader.

If you type fastboot devices, you should see an entry for your device.

If you type fastboot getvar all, you'll see a little more information about your phone.

fastboot oem unlock fails.

fastboot flashing unlock fails.

fastboot reboot fails.

fastboot flashing get_unlock_ability fails.

This is as far as I've gotten with this phone. I've got some ideas, but I would love to see what someone else does with this.

Sources:

https://ubuntu-touch.io/

https://docs.ubports.com/en/latest/porting/introduction/index.html

https://tweakdroid.com/bootloader/kyocera-duraforce-pro-with-sapphire-shield-e6810-e6810-3gb-2/
[General Topics] Dkesler76:
maybe im doing it wrong but seems i cant transfer the partition to phone plus its not showing an image file. i may be doing it all wrong lol:D
[General Topics] kemonine96:
You need to copy the image file to an external SD card then use DD (as root) to write the file to the system partition. There should be some good writeups on xda that explain the general process.

You'll want to use the bigger of the two files posted as that is a copy of the system partition.
[General Topics] Dkesler76:
so i need to use busybox dd to write to partition then .
[General Topics] kemonine96:
Yes. That should work. Just be sure to run it as root.
[General Topics] Dkesler76:
ok ty do i run dd from busybox plus i will need to unzip the file then add it to the sdcard
[General Topics] Dkesler76:
# dd if=/sdcard/mmcblk0p21.img of=/dev/block/mmcblk0p21

cannot open for read: No such file or directory

i getting this error
[General Topics] kemonine96:
Does that file exist at the path? You can verify using "ls /sdcard". If you transferred the file to your external SD Card it'll be somewhere under /storage/sdcard1 . If the file is at /sdcard/ , the shell may have a hard time reading from that particular location and you can use /storage/sdcard0 instead.
[General Topics] Dkesler76:
tmp-mksh: is: notfound
[General Topics] kemonine96:
Lowercase LS
[General Topics] s0crates82:
OTA update

It's the super thread, so I'm mentioning it. The 1.102AT OTA update made my stock device significantly more unstable. I'd not have done it, had I been patient enough for a change log.

Out of the box, this thing was a rock. Slow recent-app-button behavior, but otherwise very satisfactory. Now, the damn thing reboots itself nearly daily, whether I'm using it or not. Pocket reboots are easy to recognize due to the stupid SD card mount notification; never thought that would ever come in handy.
[General Topics] tomzweifel:
"Eco" Mode makes data connection wonky

If you haven't tried it yet yourself, I don't have good things to say about the "Eco" mode setting / widget. It made the data connection for several specific apps unreliable, and in the case of a few like Hangouts and Google Voice made it relatively unusable. Turning it off didn't correct it. So far a factory reset was the prescription. Stay far far away....
[General Topics] syabiz:
I had run into trouble after trying to throw the default application with TitaniumBackup located in

/system/app/

and

/system/priv-app/

consequently failed start-ups.

"Unfortunately, the Setup Wizard has stopped"

I tried to return it via adb, but not because of status Disable USB Debugging...

But I managed to get into Fastboot Mode / Bootloader manner;

Holding down Power + Volume Down + Back Button (accompanied by an orange LED)

If only someone could make recovery.img as a stock rom, it is helpful to re-flash the fastboot mode if there is a problem....

----

In addition, I've disassembly of curiosity contents

See the pics here--> hxxps://www.facebook.com/syabiz/media_set?set=a.1129431140403910.1073741828.100000111040226
[General Topics] kemonine96:
The "misc file mirror" in post 6 has partition images for recovery and system. No clue if they'll work with fast boot but may be worth a try.
[General Topics] syabiz:
can flashe with Fastboot mode?
[General Topics] kemonine96:
No idea, never tried.
[General Topics] syabiz:
EXPERIMENT CRAZY, BUT FAILED!

I follow this method for My Kyocera Duraforce....

hXXp://webtrickz.com/how-to-flash-cm12-lollipop-factory-image-on-oneplus-one-using-fastboot/

I Know this for OnePlus One.... but thats almost similar spec....

Result:

Now Hard Brick Already... Hahaha.... :D

Hope Advanced Developer can get any clue?
[General Topics] kemonine96:
When I was last poking about on the DuraForce I noticed the bootloader appeared locked and fastboot oem unlock had no affect (you need a key which I didn't have). I gave up pretty quickly after that point. You can't do too much to a device with a locked bootloader beyond basic root stuff.
[General Topics] syabiz:
Do not be too quick to give up. Make this as a lesson. Viewed from above logs after I try to flash with 12 cm for oneplus one, there are some parts of success, why do not we all try to find a clue on the part that failed.

I am not an expert like you all. But I assume that the device is like a machine that you can replace the operating system.

Maybe there is a way that can clear the partition and create a certain partition in order to run the kernel and include related os?

Sorry I am just a newbie? and I do not know programming languages.

My assumption is simple, if someone makes a padlock, they must create the key. If the key can not get, we could destroy, breaking, damage or any other tool to padlock...

Peace

Edit:

Last status, now when i connect my device to PC, No adb, No Bootloader, no fastboot....

But in device manager detect Serial Port COM10.... with LED with Orage Color like fastboot mode before... Any clue?
[General Topics] kemonine96:
I didn't give up per se, more of a ran out of time and also don't want to make more time presently.

The failures were likely partition names/data not lining up with what the phone expected. This is pretty normal all things considered when flashing firmware from another device.

You can, provided you've got signed firmware that's accepted by the boot loader or you're monkeying about in fastboot like you were.

You can probably do something along these lines by grabbing data from an existing device and doing a flash of data pulled from another device. Just be careful though, a locked bootloader means the kernel/system image needs to be signed or "known" by the boot loader for it to actually boot/run anything useful.

That's exactly what I was referring to with the "oem unlock code". You can get a code from some manufactures that unlocks the boot loader. Other devices (Moto X 2013 for example) have practical exploits that let you unlock the boot loader without needing a code. None of these exist that I'm aware of for the DuraForce.

You've likely got a mostly bricked device. That COM port could be a QCom diagnostics port that can pop up in certain circumstances. If it is a QCom diag port, you'd need to use the QCom tools to flash a system image to the EMMC. Unfortunately I have no practical experience in this area, I just know it exists.
[General Topics] syabiz:
That explanation is remarkable for a newbie like me..

You not only as a developer... but you also deserve as lecturer..

Thank you kemonine96