Database Info

Google is trying to update my phone

I just got a message saying there is an update available. I told it not to do it. I do not want RC30 because it gets rid of root.
However, the other side of me is tempted to see if telnetd and all the other goodies are still there.

I'm also very tempted to install it to see if it removes root access. I hope someone who doesn't care about root access tests this out and reports back soon, because my curiosity is about to get the better of me.
It won't stop prompting me and I don't think I have the heart to keep saying no.

Look on your phone, and see if there is a file named "update.install" in the /cache folder. Or maybe in the /cache/recovery folder. If so, would you mind grabbing it off your phone and posting it somewhere?

Woobins said:
I'm also very tempted to install it to see if it removes root access. I hope someone who doesn't care about root access tests this out and reports back soon, because my curiosity is about to get the better of me.
It won't stop prompting me and I don't think I have the heart to keep saying no.
Click to expand...
Click to collapse
If you ever do say yes can you tell us what your software version is?

JesusFreke said:
Look on your phone, and see if there is a file named "update.install" in the /cache folder. Or maybe in the /cache/recovery folder. If so, would you mind grabbing it off your phone and posting it somewhere?
Click to expand...
Click to collapse
neoobs said:
If you ever do say yes can you tell us what your software version is?
Click to expand...
Click to collapse
The only file of interest in the /cache directory is named, signed-RC30-from-RC29-fat.1582cace.zip. From this I'm assuming it's going to update my phone to RC30. I've made the file available here in case anyone is curious.

Ah, ok. It looks like that's the same file I just posted a link to then. Thanks

boo
neoobs said:
If you ever do say yes can you tell us what your software version is?
Click to expand...
Click to collapse
It did it.
just as I get home to catch up on the "jailbreak" and start doing it I get an
error while connecting to server, "connection refused"
error while receiving from server null
So I figured I'd check (I neglect my phone when I'm at work, and no, I don't recall accepting the update)
lo and behold:
Build description: kila-user 1.0 TC4-RC30 116143
ota-rel-keys, release-keys​Build ID: TC4-RC30
Build Date: Fri Oct 31 19:00:53 PDT 2008
Build type: user
Phone type: dream
Product brand: tmobile
Build user: android-build
Build host: undroid11.corp.google.com
Linux kernel version: 2.6.25-01843-gfea26b0
[email protected] #6​Mon Oct 6 14:13:36 PDT 2008​Baseband version: 62.33.20.08H_1.22.12.29
RIL Impl version: HTC-RIL 1.0 (Aug 19 2008,21:32:33)
Default keyboard device: trout-keypad-v3

That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
MMTest97 said:
error while connecting to server, "connection refused" error while receiving from server null
Click to expand...
Click to collapse
After starting telentd via pTerminal?

quedijo said:
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
After starting telentd via pTerminal?
Click to expand...
Click to collapse
It has more than just that fix. It patches quite a few other packages on the phone... for what purpose? I don't know.

quedijo said:
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
After starting telentd via pTerminal?
Click to expand...
Click to collapse
yes
tried pterminal and terminal emulator
netstat shows the ip
but telnet from pc fails to connect failed on port 23 and the port shown on netstat
I also tried the steps koush put up but still fail
granted I'm no linux/unix pro and I just installed cygwin a couple days after the connect bot app came out; so I may be doing something wrong

Does google check in the new change into the source tree before they push a update?

In addition to jailbreak fix there is a battery fix as well and a few others according to androidcommunity.com.

Well I finally got tired of clicking no and decided to go ahead and perform the update. After it finished, the phone rebooted and instead of booting up, the phone simply displays a '!' icon with a triangle around it and hangs. I'm not taking this as a good sign. I tried removing the battery but that didn't help.
I really hope the update didn't just brick my phone.

Woobins said:
Well I finally got tired of clicking no and decided to go ahead and perform the update. After it finished, the phone rebooted and instead of booting up, the phone simply displays a '!' icon with a triangle around it and hangs. I'm not taking this as a good sign. I tried removing the battery but that didn't help.
I really hope the update didn't just brick my phone.
Click to expand...
Click to collapse
When you're at the screen with the ! and triangle, Try pressing home+back (maybe several times). It should reboot, and hopefully boot back up normally.

JesusFreke said:
When you're at the screen with the ! and triangle, Try pressing home+back (maybe several times). It should reboot, and hopefully boot back up normally.
Click to expand...
Click to collapse
No dice. The phone reboots but still hangs at the error screen. The only thing I can think that might have caused it is that, while playing around, I set a root password and forgot to clear it before the update rebooted the phone. Who knows. I guess I'll call tmobile and see what can be done.
edit: I should mention that pressing alt-w to wipe the phone does not work either. It still returns to the error screen. I'm talking to tmobile tech support now and the original tech said that 'they were informed that a small number of users might experience this problem with the update'. I'm on hold waiting to talk to an android tech now. My advice to everyone who's played around with adding any extra files to /etc to hold off on upgrading for now. I'll report back with the results of my call with the android tech.

Now they're saying they would like to exchange the phone. Problem is the g1 isn't in their replacement program yet.
Aaaand they're out of stock so it's going to be at least 2 weeks.
I wish I'd have just kept hitting no.

Disturbing news, especially as I'm wanting to install a modified rc30. What exactly did you change?

I was playing around with trying to get dropbear to work and in the process I created some files in /etc (passwd, shadow, groups, etc). As well as creating a new regular user, I also added a password to the root account and carelessly forgot to remove it before applying the update. I'm only guessing here but I wouldn't be surprised if the new root password is what did it. The system does not have one by default and I wonder if that caused it to hang, waiting for a password to be entered while booting.
On a brighter note, I persisted and was able to get them to send me out a new phone immediatly. This has the added benefit of possibly fixing the loose-screen/creaking problem that I, like many others, am experiencing with the phone.
I'm wondering if I should try manually applying the update from the SD card while I wait for the new phone to see if that solves the problem. I probably should have tried that before calling. I'm hesitant to do that now, however, since if it does fix it, I'm not sure how tmobile would react to me returning a perfectly working phone.

Woobins said:
No dice. The phone reboots but still hangs at the error screen. The only thing I can think that might have caused it is that, while playing around, I set a root password and forgot to clear it before the update rebooted the phone. Who knows.
Click to expand...
Click to collapse
I don't get it. The update should restore whole /system folder, isn't it? /etc is actually a symlink to /system/etc, so, it should be restored too and passwd file successively removed.
Otherwise, I don't see any problem to keep the root access! Since /system is mounted without nosiud (any changes in RC30?), just keep a copy of shell with chmod 4777 somewhere there... where it wouldn't be removed by update, as it keeps passwd, and that's it.
Please, tell me where am I wrong, cause I definitely should be wrong somewhere.
PS: BTW, what was the progress with dropbear? I actually tried to make it work too, creating passwd etc, but no success...

Dimath said:
I don't get it. The update should restore whole /system folder, isn't it? /etc is actually a symlink to /system/etc, so, it should be restored too and passwd file successively removed.
Otherwise, I don't see any problem to keep the root access! Since /system is mounted without nosiud (any changes in RC30?), just keep a copy of shell with chmod 4777 somewhere there... where it wouldn't be removed by update, as it keeps passwd, and that's it.
Please, tell me where am I wrong, cause I definitely should be wrong somewhere.
PS: BTW, what was the progress with dropbear? I actually tried to make it work too, creating passwd etc, but no success...
Click to expand...
Click to collapse
Unlike the RC29 update, the RC30 update doesn't actually do a complete wipe and restore of the /system folder. It patches a number of files (which will fail if any of them have been modified), and does a recursive chmod on the entire /system directory to clear any suid bits.

New phone (RC29) - no console exploit (telnetd)

Okay, I had ordered another phone from ebay. The guy had just received it and it was new and unused. It has RC28 on it.
fingerprint= kila-user 1.0 TC4-RC28 114235 ota-rel-keys,release-keys
When I launch /system/bin/telnetd from terminal console I am not getting root. I do not see a process running when I run ps afterwards. Also, I tried typing reboot from the contact, and it is not recycling the phone.
Any chance they have updated the init.rc to close the console bug on an older RC for phones just shipping out from tmobile this past week?
I plan to update to the stock RC29 which I manually updated to on my other phone. I'd really like root before I update to the new RC30 modded, so I can back up my files before overwriting them. [Though, last time I upgraded Google did OTAs right away.]
** Anybody want me to explore the phone for any differences to the standard RC28 to see if the cause for the exploit not working?
-oldsk00lz

Just go ahead and install the official RC29 and you should be able to get root access

Are you sure it's not working? IIRC if you don't connect to telnetd fairly fast, it stops running for some reason. I know that I've had to run it a couple times before I could connect.
As for the root console bug, I've also heard that it closes after some time of the phone being on. Did you try it after a fresh reboot?
Updating to RC28 or RC29, the ones that we mirrored, should activate the console bug again, if they are fixing it.

Yeh, it was not working (telnetd/console exploit) on the RC28 I had. I tried hitting enter to clear any previous commands, tried rebooting, tried back to back calls with telnet right afterwards, telneting locally and from several boxes. Was weird.... Much different than another G1 I had. That's why I was surprised.
Only thing I could think of (besides a tweaked RC28) was that my router could have been acting up.
Anyhow, I moved forward with updating to RC29, getting root, updating to modded RC30, and all is good. Just wanted to throw this out there in case any other recent buyers encountered a similar issue.
SIDENOTE: JesusFreak lived up to his name. I was slightly "freaked" out after the recent upgrade. I went to the System settings and looked to be the standard RC30 fingerprint!!! versus the modded xda one. Thought I may have installed the stock update. :O But, everything else is as expected, root, root, and more root. I must have missed a message if he reverted back to the standard fingerprint.
-oldsk00lz

oldsk00lz said:
SIDENOTE: JesusFreak lived up to his name. I was slightly "freaked" out after the recent upgrade. I went to the System settings and looked to be the standard RC30 fingerprint!!! versus the modded xda one. Thought I may have installed the stock update. :O But, everything else is as expected, root, root, and more root. I must have missed a message if he reverted back to the standard fingerprint.
-oldsk00lz
Click to expand...
Click to collapse
Indeed, I thought the same thing, but it is much, much, much better this way. If JesusFreke left the fingerprint to be the same as the old one, Google would be able to target OTA updates specifically for rooted G1s. This way, if they release an update signed with the test keys, they'd have to have millions of non rooted G1s freak out because they couldn't update.

Gary13579 said:
Indeed, I thought the same thing, but it is much, much, much better this way. If JesusFreke left the fingerprint to be the same as the old one, Google would be able to target OTA updates specifically for rooted G1s. This way, if they release an update signed with the test keys, they'd have to have millions of non rooted G1s freak out because they couldn't update.
Click to expand...
Click to collapse
Not quite...
First, I don't think Google cares for those of us having root with RC30 moded recovery and keys. They really only care about patching the "average consumers" phone. They have to do it globaly (I mean in the distribution sense) not to get in trouble, or a BIG bug wich is what was patched.
Second, they only have to do the following if they want to put "us" back to stock (if we don't check the update of course AND don't pay attention and apply the update [BIG IF]):
Script the rewrite of recovery.img from their package (before rebooting in the background) to our phones and apply the update.... ... ... that's it.
This will get a bit of the "unaware" people who have root with RC30. But for the more savey of us, no.

quedijo said:
Script the rewrite of recovery.img from their package (before rebooting in the background) to our phones and apply the update.... ... ... that's it.
This will get a bit of the "unaware" people who have root with RC30. But for the more savey of us, no.
Click to expand...
Click to collapse
And what good would secretly rewriting recovery.img do? Once JF replaces the recovery.img with the modified one, it doesn't matter how many times they write it to flash, it's still modified.
They don't need to use the update package to take away your root. With modified RC30, any dalvik program that knows and wants to can write directly into /system. If they wanted to get draconian about it, they could push code down from Market to reflash whatever they want in /system.

You said "With modified RC30, any dalvik program that knows and wants to can write directly into /system".
Aren't these apps sandboxed? If they do have access to /system, I assume they would only have access if they ran su, assuming you didn't rename it, and was able to remount system as read/write.
Or am I missing something like a different exploit? root on 'my' phone is great for me, but not good for others.
-oldsk00lz

oldsk00lz said:
You said "With modified RC30, any dalvik program that knows and wants to can write directly into /system".
Aren't these apps sandboxed? If they do have access to /system, I assume they would only have access if they ran su, assuming you didn't rename it, and was able to remount system as read/write.
Or am I missing something like a different exploit? root on 'my' phone is great for me, but not good for others.
-oldsk00lz
Click to expand...
Click to collapse
Yeah, by invoking su. Deleting or renaming it is probably the safest bet for now. I doubt any Android devs are actively looking for phones to brick but better safe than sorry.

a new workaround for our very insecure rooted RC30
I just read a post here about a better fix for the issue.
This very smart cat, added a password routine to SU and judging by my read of the post it seems to be well implemented, you do have to type some commands and you could pooch your g1 but it seems better than runnin just about as wide open as goog had us...
Without a decent browser getting the link is a pita, if somebody can't find it ill link it when I'm at the desktop
Bhang
*EDIT*
I found the link its just a pain in the arse while typing a message, to all the helpful folks who will want to tell me how to do it, I know how I just think it could be easier
http://forum.xda-developers.com/showthread.php?t=448775

Android Browser build that AutoRotates

Here's a recompiled version of the Browser that supports auto rotate.
Here's the download location for the Browser.apk:
http://www.koushikdutta.com/2008/12/auto-rotate-for-android-browser.html
Run the following from the command prompt to install the new Browser:
Installation Instructions:
adb remount
adb shell rm /system/app/Browser.odex
adb push Browser.apk /system/app/Browser.apk
Now start up the Browser.
You may not have a Browser.odex depending on your phone model.
The change, as I mentioned before, is really trivial. In the BrowserActivity.onCreate, I did the following:
// the next line is the original code
// setRequestedOrientation(mSettings.getOrientation());
// make it use the sensor for orientation instead.
setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_SENSOR);
To restore the original Browser, flash RC30 again.

Koush, thanks so much! I have been waiting for this!

i can't get it to install and now the browser don't work and i can't install the back up

I'm getting no space available when pushing the browser.apk
JF rc30 v1.2

kron2 said:
i can't get it to install and now the browser don't work and i can't install the back up
Click to expand...
Click to collapse
You can't get it to install? Could you be more specific?

saul972 said:
I'm getting no space available when pushing the browser.apk
JF rc30 v1.2
Click to expand...
Click to collapse
Your /system partition ran out of room. Is there something you can delete from there? I've seen this before as well on some of my company's phones; I usually end up deleting some ringtones or other junk files.

took a couple of tries but installed now...thanks!
fyi i rebooted phone to initially install the new Browser. I first got errors w/o rebooting so that may fix the problem

I had the same problems with the new browser crashing and then being told that the file couldnt be copied due to lack of space,
Easiest fix is to just reinstall rc30 or rc8 and install the patched browser again.
Worked fine after that

Koush said:
Your /system partition ran out of room. Is there something you can delete from there? I've seen this before as well on some of my company's phones; I usually end up deleting some ringtones or other junk files.
Click to expand...
Click to collapse
Not sure.
Here's the message
failed to copy 'Browser.apk' to 'system/app/Browser.apk' : no space left on device

SGTDavePwnage said:
I had the same problems with the new browser crashing and then being told that the file couldnt be copied due to lack of space,
Easiest fix is to just reinstall rc30 or rc8 and install the patched browser again.
Worked fine after that
Click to expand...
Click to collapse
Will I need to start the process again?

saul972 said:
Will I need to start the process again?
Click to expand...
Click to collapse
Its basically telling you that it cant copy the file because of lack of space withing the system partition.
As koush advises, if you know how to clear space that will fix the problem.
If you dont know how to remove things and are a bit unsure of what to do, reinstalling the modified rc30 / rc8 will reset the system partition back to its defaults.
Once your back and set to default you can try to install again if you want

I'm assuming this is for those who have root access only?
If so, it would be nice to state that when posting these mods.

Henchman said:
I'm assuming this is for those who have root access only?
If so, it would be nice to state that when posting these mods.
Click to expand...
Click to collapse
Yes this requires root access,
I can see what you are saying about perhaps specifying in the post when something requires root access, but when you look at the instructions in this case its quite obvious that this one does require root.
PS.... Cheers for the upload Koush

SGTDavePwnage said:
Yes this requires root access,
I can see what you are saying about perhaps specifying in the post when something requires root access, but when you look at the instructions in this case its quite obvious that this one does require root.
PS.... Cheers for the upload Koush
Click to expand...
Click to collapse
Obviouse to em...
But probably not to everyone.
And you know the old saying. When you Assume...

where do i put Browser.apk to install it on the sd card and if so how do i use adb to see it or do i push it from like c:\browser.apk \system\app\browser.apk

SGTDavePwnage said:
Its basically telling you that it cant copy the file because of lack of space withing the system partition.
As koush advises, if you know how to clear space that will fix the problem.
If you dont know how to remove things and are a bit unsure of what to do, reinstalling the modified rc30 / rc8 will reset the system partition back to its defaults.
Once your back and set to default you can try to install again if you want
Click to expand...
Click to collapse
Finally got it!!! Thanks for your help

kron2 said:
where do i put Browser.apk to install it on the sd card and if so how do i use adb to see it or do i push it from like c:\browser.apk \system\app\browser.apk
Click to expand...
Click to collapse
Place it in the tools folder of the SDK folder on your PC

thx joshoowa i installed it finally i did have it in the tool folder but would not install but after several tries it did i was starting to think i was installing it wrong

I've deleted most of my .ogg audio related tones in the /media/audio folder but i still get no space left. what else can i delete?
btw i'm using adb shell rm /xxx/xxx/xxx/xx.ogg to delete. is that right?

Hey Hey!!!...
Had to free up some room, but it works great..
Thanks..

OTA Supersonice 1.47.651.1-1.32.651.6_r

DO NOT FLASH THIS UPDATE UNTIL YOU HEAR FROM THE BIG GUNS OR RISK LOSING YOUR ROOT!
Please Be Patient!!!!
Sprint is pushing out a system update this morning with a size 21.43mb
Update Download Links:
http://www.mediafire.com/file/2myavzqygir/OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip Thanks Calkulin!
http://www.sdx-downloads.com/sdx/evo/stock/OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip Thanks Joeykrim!
Firmware Version
2.1-update1
Baseband Version
2.05.00.06.10
Kernel Version
2.6.29-789bf291
[email protected] #1
PRI Version 1.40_003
PRL Version 60667
Thank you joeykrim for the following:
RADIO - the radio is updated through a radio.diff.
SYSTEM - no system/app files are changed
it appears this OTA is much more extensive than the previous OTA.
this one appears to apply small patches to every application in /system/app. a few are large in size, but most are very small.
it also appears to patch:
16 files in system/bin
etc/wimax/
etc/firmware/fw_bcm4329.bin and (ap)
31 files in framework
28 files in lib
2 files in lib/modules - bcm4329.ko and sequans_sdio.ko
SYSTEM updated files (might be more, researching now):
wifi module - BCM4329B1_002.002.023.0396.0402.hcd
android.hardware.camera.flash-autofocus.xml
android.hardware.telephony.cdma.xml
ton of framework files
libCamera_donut.so
libCamera_eclair.so
Fixes & Bugs:
From user npace: (I extracted and fastboot flashed the kernel zImage. Here's a rundown of the issues that I tested for fixes
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
3. 30 fps cap -- still there

same radio by your title?

Appears to be. I am waiting for it to finish downloading and I will attempt to upload.
This thread will probably be moved / deleted but I was just letting everyone know. Personally I am going to wait to hear from the Dev's on this download before even touching it.

is this breaking root access.. some unrevoked users via face book saying unrevoked is no longer working.. i guess they should have went all out and did the full root

danon.brown said:
is this breaking root access.. some unrevoked users via face book saying unrevoked is no longer working.. i guess they should have went all out and did the full root
Click to expand...
Click to collapse
Even if you rooted via toasts method, i would not update until a custom ROM is put out with the update included. You could lose root ability forever.

Anyone know the location of system updates are stored on the phone? I am trying to locate using the adb shell but have had no luck finding the download yet.

huoter said:
Appears to be. I am waiting for it to finish downloading and I will attempt to upload.
This thread will probably be moved / deleted but I was just letting everyone know. Personally I am going to wait to hear from the Dev's on this download before even touching it.
Click to expand...
Click to collapse
can you post this OTA .zip?

joeykrim said:
can you post this OTA .zip?
Click to expand...
Click to collapse
Its done downloading, just trying to find the darn file right now. Any ideas?

Awaiting an update zip

Here's the untouched update zip for those that want it. If you want to put it in the OP, feel free to
OTA_Supersonic_1.47.651.1-1.32.651.6_releaseq2wpcb5jl7uowah9.zip

huoter said:
Its done downloading, just trying to find the darn file right now. Any ideas?
Click to expand...
Click to collapse
i didn't look into the last one and this is my first HTC phone so im not familiar with their OTA process.
perhaps try /cache? or any type of temp directory on /data or /sdcard?
we know it won't be on /system.

We install this from recovery, right?

herzzreh said:
We install this from recovery, right?
Click to expand...
Click to collapse
Don't install anything until some devs have had a look around--they'll make a package to flash when it's safe.

herzzreh said:
We install this from recovery, right?
Click to expand...
Click to collapse
I'd recommend not installing it at all until the devs here have had a chance to go through it and release it themselves. You risk loosing your root if you don't. Then follow their release instructions to apply it.

Btw the radio is 2.05.00.06.10 with this update.
Sent from my EVO using Tapatalk

Shidell said:
Don't install anything until some devs have had a look around--they'll make a package to flash when it's safe.
Click to expand...
Click to collapse
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...

donatom3 said:
Btw the radio is 2.05.00.06.10 with this update.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
if you've applied this, can you take a screenshot of the about phone -> software versions or manually type all the info up on here?
im wondering about the PRI ...

herzzreh said:
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
Click to expand...
Click to collapse
No, looks like just about all the preloaded APK's are in there, including the Sprint crap. I assume if you apply it as stock you'll get them back, but I could be wrong.

herzzreh said:
I don't care if I lose root. I assume this update doesn't reinstall Sprint junk, so I'm good to go. That was the only reason why I wanted root access...
Click to expand...
Click to collapse
The official froyo release from HTC / Sprint will definitely contain all the "Sprint Junk" and if you've given up root to one of these updates and go to apply that it will all come back. You may never get root again in order to re - clean it up once you apply froyo.
Be patient. It won't take the devs here long to cook up an update for us. Flipz had the rooted .6 update rom out in 24 hours or so...
.....
Just took a look inside the zip file. All the apk files are there, including the sprint junk...

Just installed....all is well with root...

Kyocera DuraForce Super Thread

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)

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.
Download "vanilla" system image from HERE (link)
Extract zip file
Ensure at least 2Gb of storage is available for internal data
adb push mmcblk0p21_KVT49L_0617_0132 /storage/sdcard0/
adb shell
su
dd if=/storage/sdcard0/mmcblk0p21_KVT49L_0617_0132 of=/dev/block/mmcblk0p21
Reboot phone once it completes. It will take awhile and not report anything during the process.
After phone boots, run "adb reboot recovery"
Wipe data / factory reset
Wipe cache
Reboot
Run software update

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

Known Working Customizations
To be determined

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

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

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?
kemonine96 said:
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.
Click to expand...
Click to collapse

tomzweifel said:
How do you feel about Kingo?
Click to expand...
Click to collapse
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.
tomzweifel said:
I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
Click to expand...
Click to collapse
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants

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!
kemonine96 said:
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:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Click to expand...
Click to collapse

tomzweifel said:
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!
Click to expand...
Click to collapse
Unfortunately I don't have notes on what Kingo leaves around on /system... Some searching online or poking about /system should yield results.

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.

tomzweifel said:
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.
Click to expand...
Click to collapse
Please do. I haven't gotten any notifications yet and I'm kinda curious what the OTA will contain.

http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates

Dkesler76 said:
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Click to expand...
Click to collapse
Thanks for the heads up. Too bad it's not L.

kemonine96 said:
Thanks for the heads up. Too bad it's not L.
Click to expand...
Click to collapse
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

Dkesler76 said:
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
Click to expand...
Click to collapse
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.

Dkesler76 said:
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
Click to expand...
Click to collapse
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

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.

kemonine96 said:
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
Click to expand...
Click to collapse
weird i tried dd and busy box and no go not showing up on device

Dkesler76 said:
weird i tried dd and busy box and no go not showing up on device
Click to expand...
Click to collapse
What isn't showing up?