yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] ColdAtrophy:
I am by no means an expert. I've only recently started to get into learning everything I can about Android, Linux, root, ROMs, flashing recovery, etc.

I got my hands on a Verizon Galaxy S4 for free. The owner got an upgrade to a new phone and doesn't care what I do to it.

It took me about a day to figure out how to root it. I've noticed a few things in the process.

1) I can easily get into the recovery on the S4.

2) Odin, the proprietary Samsung flashing tool, is available for fixing any screwups. Since I rooted it the first time, I flashed it back to stock twice and went through the process again.

3) Download mode is accessible on the S4. I've seen it referenced elsewhere as "fastboot/download mode".

With all that said, the S4 cannot get the usual custom ROMs flashed to it if it has been updated to Lollipop. And even if it hasn't, the only way around the bootloader is to use something called Safestrap which, as I understand it, creates a second boot partition and sidesteps the stock Verizon one. According to my research on this, this was on the only viable option for the same exact reason. Verizon's bootloader is locked.

So anyone who knows better, please correct me, but the way I see it is this: locked bootloader does not mean root is impossible. It seems to mean that flashing custom ROMs is impossible. I'll still take a stock OS with SuperSU installed and working any day over what we have now.
[General Questions and Answers] jfever311:
Any updates on possible root exploits?
[General Questions and Answers] ColdAtrophy:
Alrighty. It's been a little while since anyone has posted anything of progress or value, no offense intended of course. What's the standard procedure for posting a root bounty for a phone? I'd like to attract some real interest in getting this thing done.

Edit: No idea if this is even remotely helpful, but I came across something that I found interesting.

I ended up with a soft brick, black screen after boot. I tinkered a little too hard I think. I used Google's Find My Device app to send a factory reset command to the device. And wouldn't ya know it? The system recovery screen loaded and then the recovery processes ran. I couldn't interact with it, but still. Kyocera told me that there was no way to fix it without an RMA and AT&T had no method for accessing recovery either. It left me wondering if this represented a potential vulnerability that could be exploited for access to the recovery environment.

I looked into the documentation on the Device Admin aspect of Android and I didn't find much that seemed helpful, so maybe this is absolutely nothing, but I thought I'd share.
[General Questions and Answers] MisterWillie:
Just what root method were you trying to use?
[General Questions and Answers] ColdAtrophy:
Honestly, I don't recall off the top of my head. It was likely either Kingoroot or Kingroot that yielded the black screen. At the time, I was trying anything and everything that looked like it wasn't a total scam.

I've tried everything. I mean it. I looked into every single method I could come across over a period of 4 or 5 months. I either couldn't use the root method due to the fact that I can't access the recovery to flash a new image (like with Magisk for example), or the application didn't offer an exploit that worked. Also, fastboot is inaccessible.
[General Questions and Answers] :
Gentlemen, I confess I've never rooted a smartphone before, much less one with a locked bootloader. In fact, the E6810 is my very first Android. Far from an expert, I'm rather just an enthusiast faced with a steep learning curve at every turn. Unfortunately, despite calls for a bounty, I passed the point of diminishing returns soon after my last post. I hence took an alternate route utilizing ADB and Tasker to achieve the desired functionality. However, I still believe my original approach holds the greatest chance of success for a committed individual or team thereof. As before, the next steps require merging the superuser files with a recovery image and fooling Verizon's software into loading it. I suspect Celti is well equipped to accomplish the former, but owning an E6820 means he has little incentive to do so (Regrettably, after reviewing our dialogue, I suspect my poor choice of words inadvertently offended him). The final step depends less on technical know-how, but will likely involve much trial and error. Theoretically, everything needed to proceed exists within this thread except for the raw determination. I apologize for ditching the party early, but I'll try to remain available for consult.
[General Questions and Answers] ndt44:
This worked on my AT&T E6820 and got the phone to a screen with a green android guy with a red warning sign and "no command" on the screen. Unfortunately, I am having some version issues with ADB on my laptop right now.
[General Questions and Answers] naveenroy:
Just trying to bump this thread up. Would really love to remove some bloatware from this phone!
[General Questions and Answers] agladservo:
I've already stated before, I can do it, but either someone needs to send me the Sprint variant, or at least get in direct touch where I've got the information for that or an AT&T version on the stock firmware that's currently in service. The stock Verizon firmware still works with VIKIROOT (albeit buggy) despite being compiled past the patching of CVE-2016-5195 & the Verizon consumer utility software will load an entire packed & signed image to the device through it's own method, at least one of which has been dumped, shared, and unpacked, but without the prerelease Verizon firmware mentioned on those Russian forums, which presumably still has the other pre-Q3 '06 Qualcomm exploits unpatched there's no fastboot access on the other-than Sprint versions, and using temporal CVE-2016-5195 escallation to raw flash a patched boot/aboot will almost certainly brick it in the worst way possible. Alternatively, the method used for the Cat S60 *might* work here, but obviously it won't work with that Verizon utility image, so, either someone needs a full flash image & utility from Sprint, or something to root & dump in its entirety through ADB/standalone exploits that aren't the rowhammer or temporal CVE-2016-5195 ones that mostly do work because the quadrooter vulnerabilities (or something) are needed to get around dm-verity for lack of both a signed engboot and the ability to write it through fastboot
[General Questions and Answers] j_yenals:
Hi,

Junior member just wondering if there has been any progress made on rooting the Duraforce pro 6820 AT&T or either of the other versions.

I will provide a phone and hope that others might contribute after the fact. Just sayin.

Thanks
[General Questions and Answers] Celti:
Not offended, just been repeatedly punched in the face by life. Also, I have an E6830 (Sprint), not an E6820 (AT&T) — but I no longer have service for it.
[General Questions and Answers] rhys8582:
Hey all! I just finished reading through this thread from start to finish. At one point someone posted "The Verizon bootloader will never be unlocked!". I don't really want to go back through the 9 pages I just read to locate that comment; can someone clarify what is meant by that?

Thanks!
[General Questions and Answers] :
The E6810 (Verizon) and possibly other models, include a setting in developer options called "OEM unlocking." Ideally (and logically) it would grant access to the boot loader from boot menu which is launched by depressing the volume down button when powering on the unit. Sadly, the setting in developer options changes nothing when enabled and appears defunct. That means the boot loader is disabled deeper within the image and likely very difficult to reach. Therefore, one must employ more complex methods to gain root access such as exploiting a security vulnerability.

http://technotif.com/rooting-locked-boot-loader/
[General Questions and Answers] 3l3tric:
I just received the DuraForce Pro 2 from AT&T yesterday and found this thread, what all do you need?
[General Questions and Answers] servimp:
This was done on a 6810 [YOUTUBE]https://www.youtube.com/watch?v=gLZnLH7QNOM[/YOUTUBE]

For this, the phone had to have been rooted (not sure here).

I currently have a pair of 6810s to spare, and available for anyone to test.

Besides, I can get my hands in one of those e6810s with Russian firmware, just in case some investigation is needed.
[General Questions and Answers] 11sword11:
The phone withe russian firmware don't have root. In this firmware even removed trigger for enable adb in developer settings. The russians do not want to share the secret of how they patched device with this firmware. I suspect they are solder wires to the board and flash the memory chip directly on the programmer.

Or maybe they have a special cable or software tool that they don't want to share with anyone.
[General Questions and Answers] Vailed:
Did anyone ever achieve root on e6820? Have one and can only get to safe mode and no joy with adb
[General Questions and Answers] SpockSpock:
Kyocera Duraforce pro 2 root.

I have the AT&t version of this device and I would love to get it rooted. If I can provide any info that will help some genius do this please let me know.

Also is there a beginner's programming guide for how to become a route specialist?
[General Questions and Answers] albert3434:
First thing I want to give thanks to everyone that has posted here. This is an amazing community. I have spent a couple days trying the many suggestions on this and other XDA Kyocera DF Pro threads. Unfortunately I've had no success unlocking the bootloader or rooting.

Here's what I've tried:

I have a Kyocera DF Pro E6833 (Sprint) that I factory reset. It shows Android 6.0.1 under settings/about phone/software info. I've enabled OEM unlocking under the developer options. I then download abd platform-tools, connect my phone to my windows pc, enable MTP file transfer, and then run commands from an admin command line. The "adb devices" command works and results in showing my device and serial # but the "fastboot devices" command doesn't show any results - it just returns me to a command prompt. I then tried to download and install many different USB drivers and repeat the process. I always get results for the "adb devices" command but the "fastboot devices" command always shows nothing. Every time I try the "fastboot oem unlock" command, it's reply is <waiting for device> and stays there for 30+ minutes before I press ctrl-c and exit.

I have tried almost all of the suggested root programs in this thread that I can find. Nothing has worked. This phone is getting old now but I still love it. I just want to be able to get rid of this sprint bloatware that's always running and killing my battery.

So anyone got anything else to try? I'm thinking of paying the $40 on the OneClickRoot site but friends have said that's a waste of $ and wont work. They told me to look here first and I'm glad that I did.
[General Questions and Answers] Onebigburb:
Would factory open source help? Something hidding as a clue?

https://kyoceramobile.com/support/developers/
[General Questions and Answers] Keilaron:
Hello from the future. I was going through some old devices laying around in a box, and found a Verizon-branded Kyocera Duraforce Pro, except..

C:\Users\--->fastboot devices
------- fastboot

... (redacted) this one responds on fastboot. So far it looks like I can only use a few commands (like getvar product confirms it uses a MSM8952 chipset). Is anyone still interested in figuring out these devices?
[General Questions and Answers] Devicarious:
I am having the same issues
[Mate 8 General] tommmyanderson:
Can someone please help me. I installed andriod n for my mate 8, but in doing so the phone has completely screwed up. I honestly have no idea what went wrong. So many apps just crash, the whole ui is so slow its ridiculous. I have no sim that doesnt work like i cant send messsages or anything. I have tried installing twrp and for the life of me thats not working either. Like the bootloader is unlocked and everything, but i cant seem to find a twrp version for 7.0 only 6.0 and down, so at the moment i have no way to repair my phone and its brand new!! If anyone can help that would be so appreciated.
[Mate 8 General] MarceloAF:
What model? And which system? EMUI 5.0, Android 7.0?
[Mate 8 General] tommmyanderson:
Model is NXT-AL10 which isnt my original model, and yes emui 5.0 and andriiod 7.0
[Mate 8 General] MarceloAF:
Yes, mine is a DL00, but its system and 3 other Chinese variants is the AL10CXXBXXX. Would yours be a DL?
[Mate 8 General] tommmyanderson:
Full number is AL10C00B523
[Mate 8 General] MarceloAF:
AL10 = chinese version, unlocked

TL00, DL00, CL00 = chinese versions, locked to chinese carriers

L29 = international version, unlocked, dual sim

L09 = international version, unlocked, single sim, only available in 3/32 GB

Mine should be stuck with an operator called Unicom, but it's not. Unlocked. The operator is the only difference between models that use the AL10 system.

But what model is it? Mine is a"HUAWEI NXT-DL00", firmware NXT-DL00C17B523, see what appears on your device. If it's a DL00, just use dload with a specific file. I had several problems, but I managed to solve it on my device.
[Mate 8 General] tommmyanderson:
How on earth did i go from NXT-L29A to a chinese verison? Have you got any idea how i go back at all? Because i cant do anything with this phone atm its dead lol
[Mate 8 General] MarceloAF:
When you went to Emui 5.0, you used 2 files, right? The second file is what defines your network and region according to the device. In my case, even being from Brazil, I had to use the second file according to my device to dload. Chinese. I installed these two that are in the link, I was not without network, but I was with apps locking, crashes in the system, another name in my system, everything because of this second file, when I downloaded the correct, my cel was perfect. I needed to install "update_data_full_dualcu_cn". That is correct for the DL00. Answering your question, I think you used the wrong file at the time of dloading or updating by TWRP, it turned into a Chinese model, so the problems. You must try the reversal process. I just wanted to get back to Emui 4.1, but no procedure worked for me, even though it was originally a Chinese model, but who knows, you're in luck.

http://xdaforums.com/mate-8/general/guide-how-to-install-nougat-al10c00b523-t3500327

How to install Nougat AL10C00B523

1. Download files from

http://update.hicloud.com:8180/TDS/d...ull/update.zip

http://update.hicloud.com:8180/TDS/d...ull_all_cn.zip
[Mate 8 General] tommmyanderson:
That makes alot of sense now. I just dont get how i am meant to reserve it? Nothing is working, how did you manage to do it?
[Mate 8 General] MarceloAF:
Go to the dialer and type, * # * # 2846579 # * # *. Go to Network Information Query and then to Vendor Country Info. What's in there?
[Mate 8 General] tommmyanderson:
Vendor: all

Country: CN
[Mate 8 General] MarceloAF:
Yeah, he changed the region. So it is without network and with the problems, try the method of donwgrade, it did not work with me, but it can work with you, because it is directed to the Western devices.

You can try to use the dload with the UPDATE.APP that has within those regions files, like the ones I mentioned from China. That's what I did. For this, you need to know exactly what your original model is.

Mine was like that, too.

Vendor: all

Country: cn

But when I switched to my official archive, the problems ended. It is so now.

Vendor: dualcu

Country: cn

http://xdaforums.com/mate-8/general/guide-how-to-install-nougat-al10c00b523-t3500327
[Mate 8 General] tommmyanderson:
I tried the downgrade but i have no way on intalling twrp for this version of andriod, like i have tried to install it so many times but it never boots into twrp which is the problem for me at the moment
[Mate 8 General] MarceloAF:
Only with the dload method.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] ZION959:
Reserved
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] sevsman:
This is absolutely great mate, and I'll be sure to try it at the weekend, but, could you add any known bugs to the OP?

Much appreciated dude

Nathan
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] tweetyfiestuky:
Woow, how can I download it??

Enviado desde mi LG-H850 mediante Tapatalk
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] joemossjr:
in the op?
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] Nick216ohio:
Yeah guys its in the OP. Downloading now myself
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] joemossjr:
All ready flashed seems to be running good camera force closes using footej i can record video BUT audio is very soft apps installed fine and its working well
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] PrinceLc:
What about advanced reboot ?? Broken too ??
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] joemossjr:
still broke
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] LittlePlumb:
I think H850 isn't up yet. Only file I can find is for 830.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] tweetyfiestuky:
Me too

Enviado desde mi LG-H850 mediante Tapatalk
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] joemossjr:
Also vibration is still super low

---------- Post added at 10:59 PM ---------- Previous post was at 10:31 PM ----------

And flashlight toggle brokr
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] King_lilrowrow:
Massive credits list but no love for the ConquestDev team, we fixed mostly everything :D
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] shaneg79:
Flashlight toggle works for me
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] joemossjr:
Weird I'm on the Tmobile firmware
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] ZION959:
I apology Just give me some time . no one will miss out. I copy my note 4 thread over. I will add all tonight or tomorrow is latest. Thanks
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] shaneg79:
Same here unlocked T-Mobile h830 using it on cricket's $70 unlimited plan :) I wiped everything but internal then flashed the ROM then gapps.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] ZION959:
Just to let you know kernel is oc and some extra features. Use Kernel Adiuter for setting
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] ZION959:
Use Open Camera for now. Thanks
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] nima0003:
Quick question, can you flash this over a current build of CM 14.1?
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] gwolfu:
wouldn't advise as it contains diferent system files
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] liushangrong:
H850 17/11 The camera program stops running
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] Nick216ohio:
$70? Get on Tmobile family plan bro. I am paying literally half what your paying
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] shaneg79:
T-Mobile coverage sucks here I don't actually pay $70 that's for a single line I pay $30 because I'm on a family plan and my line is the 5th line. It's $70 for 1st line, $60 for second, 50 for 3rd, 40 for 4th, and 30 for 5th line.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] jis251:
Sorry to ask but how can you announce this as official? CM is not official yet and this based on CM.

This is not a blame or anything, just wondering. All bugs are fixed which exists still on CM?

Big THX for ROM anyway
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] King_lilrowrow:
The bugs will be the same as CM, even though this is (based) on CM, CMRemix is a spin-off ROM that has no relation to the actual CM team hence they can class what ever builds they want as official/unofficial.

ROM's like Dirty Unicorns and CyanogenMod have higher expectations for the devices they support, hence its harder to gain the official status for CM and DU ROM's.

CrDroid, CMRemix, AICP etc have slightly lower expectations and will even make devices official before they are fully stable.

Hope this helped!
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] azztech30:
My Camera is not working but have found a temp fix (see in bugs) this happens in this ROM and crdroid rom

---------- Post added at 03:14 PM ---------- Previous post was at 03:07 PM ----------

http://xdaforums.com/g4/themes-apps/root-v10-camera-ported-to-g4-t3366878

Download v5.1 LG Camera it works nice and fast triple tested, it is faster than open camera but at least you have a camera it will not activate wide angle though but still awesome work guys
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] jrplaga25:
How did you do it? I keep getting the Camera has stopped pop out.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] anaschillin:
Hi, I am thinking of flashing this rom. Does this rom support Magisk Xposed and SU?
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] davitox87:
There is no xposed for android 7.x and its recommended to use the built in superuser app in cm vs SuperSU because SuperSU breaks many things.
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] azztech30:
Right so I have tried numerous ways to fix this camera issue as installing another camera app or what I suggested earlier, I have done the following (usual flash, full wipe etc) rom boots all is good go into developer allow the usual for root, use titanium backup restore apps.........

Camera then stops working?? okay flash again (full wipe etc) this time flashed supersu did titanium backup all good camera worked 3 times then crashed, amongst other app errors keyboard etc.

And the big thing here is sorry to the developer :) Flashed the rom (full wipe again), then the usual into developer options allow for root, (not supersu) but this time in my list of backups unticked the backed up camera apps I had, let it finish and ta da!! all good (still no wide angle) but it is way faster, smoother ad the camera works!!

So it must of been the issue with 3 similar camera apps working together causing an issue, just thought I would share this, for those of you who may be restoring via titanium backup and forgetting you had a camera app backed up then this is what is causing the issue (well it is for me) oh and please do not install SuperSU
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] rpsweb:
Great ROM thanks

But battery seems a bit poor is the because betterbattery stats says bluesleep is causing 100 percent wakelock?
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] ZION959:
new update is up today

http://romwarehouse.com/zion959/CMRemix Nougat/CMRemixNightly/
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] rpsweb:
Thanks change log doesn't mention battery issue but I assume you did something since you replied to my post, great rom fyi
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] RicardoSal24:
Good rom. Like I've always experienced, camcorder doesn't work and video playback is a little glitchy, especially on Snapchat. Running the latest 11/24 build for H830.I hope those issues are fixed soon
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] rpsweb:
Update has much better battery life thanks :) but the cm remix update button causes a crash, can I dirty flash future updates ie update without having to full reset, ROM is epic keep up the good work will donate
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] ZION959:
New update again with new cm source and ota is fixed
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] ZION959:
Fixed now. Will add lots more features in next two days anyway performance and battery is main priority. Thanks
[LG G5 ROMs, Kernels, Recoveries, & Other Developme] rpsweb:
Yup I accidently flashed SuperSU caused loads of problems

---------- Post added at 05:29 PM ---------- Previous post was at 05:27 PM ----------

Cool can I flash the update and not lose settings/appS?