Database Info

[ROOT][TOOL][2012-07-24] GS3DebugFSRoot: Root the Verizon GSIII without flashing

THIS WILL NOT WORK WITH JELLY BEAN.
---
Here's a easy-to-use tool based on the method in this thread.
If you like this tool, please click the Thanks button!
Even better, see my signature.
DISCLAIMER: As with any rooting tool, there is some chance that something will go wrong. Use of this tool is at your own risk, and I will not be responsible if you brick your phone in the process. Although there have been zero reports of this tool breaking anyone's phone, don't run it if you aren't comfortable with the possibility of having something go wrong and having to re-Odin back to stock or worse.
Instructions:
Install the USB drivers if you don't have them already: Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Download the package and extract it somewhere (you'll need 7-Zip or some other modern compression tool) Make sure you extract all the files to a folder somewhere! Running it straight from your compression program probably won't work.
On your phone, enable installation of third-party apps (Settings --> Security --> Unknown sources, near the bottom in the "Device administration" section)
On your phone, enable USB debugging (Settings --> Developer options --> USB debugging)
On your PC, make sure you don't have any other Android devices connected, any Android emulators running, or any Android tools like PdaNet running.
Plug your phone into a USB port on your computer. For best results, use a port directly on the machine, and not a USB hub.
Double-click RootDebugfs.bat and follow the directions on the screen. Your phone will reboot 3 or 4 times during the process; just leave it plugged in. To be safe, don't switch to any other applications while the root process is running.
DOWNLOAD GS3DebugFSRoot R2 FOR US GALAXY S III VARIANTS ONLY!!!
(Released July 24, 2012)
If anything goes wrong, post here and I'll see what I can do.
Credits:
* miloj, for the debugfs root method for the Asus TF300T
* sparkym3, for his script for rooting the Asus Transformer Prime - this is a modified version of that script
* ChainsDD, for Superuser

Version History:
The most recent version is always at the top.
r2 2012-07-24
+ Changed font color to white for readability
+ Cleaned up output
+ Fixed typo in title (GSII instead of GSIII)
+ Fixed Unknown Sources/USB Debugging directions
+ Included latest version of adb from platform-tools 13, might make things more reliable
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Known to work with LF2 and LG1.
r1 2012-07-23
* Initial beta
* Includes ChainsDD Superuser 3.1.3 and su binary 3.1.1
* Works with LF2. Probably works with LG1.
Possible future features:
* APK version of the tool! I'm still not sure if this is possible - currently researching.
Sadly, I don't think this is going to happen.
* Unroot tool.
* Choice of Superuser or SuperSU.

FAQs:
Q: What versions of the stock ROM does this work with?
A: It's known to work with anything from LF2 up to LHE. It seems likely that DebugFSRoot will be able to work with any ICS ROMs. We'll have to wait and see if it works on JB or not.
Q: I'm getting an error like "adb is not recognized as an internal or external command", or "cannot stat 'su': No such file or directory". What do I do?
A: Don't run the tool straight from your compression program. Make sure to extract all the files somewhere first.
Q: Will this wipe my data?
A: Nope.
Q: How can I unroot? Will flashing a stock ROM unroot?
A: Flashing a stock ROM will unroot and also remove any modifications you made to /system.
Q: Everything seems to have worked fine, and the Superuser app shows the binary as present and working. However, none of my root apps work. What do I do?
A: This seems to happen to a very small number of people, and the cause is unknown. If this happens to you, try installing Chainfire SuperSU.
Q: Is this any better than flashing the root66 ROM?
A: The end result should be pretty much the same, but this tool is much smaller to download than the root66 ROM.
A: If you are on a phone with the stock LG1 ROM update, root66 will downgrade you to LF2, while this tool will leave your ROM alone.
Q: Is this any better than using the VRALEC boot chain method?
A: The boot chain is a little more complicated. It requires flashing two bootloaders, flashing recovery, and using Triangle Away to reset the Custom Binary Download counter. If you intend to install a custom recovery/custom ROMs anyway, it's fine and probably quicker. However, if all you want is root to run Titanium Backup or other root apps, GS3DebugFSRoot is easier.
Q: Will this increment the flash counter?
A: Not on its own. If you flash anything else after rooting, however, you might, so read up on what you're doing.
Q: Will this cause the "custom unlock" boot screen to appear?
A: In general, no. However, the spyware Samsung/Verizon included (SysScope/libcordon) is paranoid, and a lot of tweaks you can do after rooting will trigger it. If you don't want to risk getting the custom unlock screen, don't freeze any apps using Titanium Backup and generally limit your tweaking to things you could do without root.
Q: Can Samsung/Verizon block this method in the future?
Yes. It's very possible that a future OTA will patch the exploit that this tool uses. If you want to root, it's always best to do it now!

I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.

DFieldFL said:
I just tried this and it appears to work. Installed Titanium Backup and SuperUser permissions were given. Thanks!
P.S.
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
Also title says Galaxy S II not III.

Noxious Ninja said:
Ah, I forgot to update that part in the Transformer Prime script I based this on. I'll fix it tomorrow.
Did you get the custom unlock boot screen?
Click to expand...
Click to collapse
The boot screen looks the same to me.

Worked for me, thanks

Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"

phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
Same thing happening to me.
EDIT: Just switched usb ports and unplugged and replugged my phone in and it worked!

If my gs3 came updated with the newest version, will this still work?

Next release will be out tonight after I test it.
DFieldFL said:
Some of the instructions in the console app are incorrect for the location of enabling Debug Mode and Installing Unknown App Sources.
Click to expand...
Click to collapse
Fixed in the next version. Also, I added those steps to the main post.
open1your1eyes0 said:
Also title says Galaxy S II not III.
Click to expand...
Click to collapse
Typo on my part. Will be fixed in the next release.
phantomevo77 said:
Cant recognize the phone using this tool. Yet device is recognized by adb in a standalone cmd prompt..
saying "adb is not an executable file"
Click to expand...
Click to collapse
I'm not sure about this one. However, I had packaged a slightly older version of adb, which could cause a difference. The next release will have the latest adb.
eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
I think so, but I don't know if it's been tested. Worst case should be that it would fail when trying to copy su into /system/xbin/, and you might have to manually clean up a few things:
Code:
adb shell
[COLOR="Red"]$[/COLOR] rm /data/local/tmp
[COLOR="Red"]$[/COLOR] mv /data/local/tmp.bak /data/local/tmp
[COLOR="Red"]$[/COLOR] rm /data/local/su
[COLOR="Red"]$[/COLOR] rm /data/local/debugfs
[COLOR="Red"]$[/COLOR] rm /data/local/debugfsinput
[COLOR="Red"]$[/COLOR] exit
Really worst case is that your /system is screwed up and you have to re-flash a stock ROM with Odin, but that is highly, highly unlikely with this method.

Thanks for this awesome tool!!! Will there be a reversal to what this script does, aka, non-root to reverse changes if necessary or will that require odin flash?

It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.

Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
edit: sorry I typed and posted this as others were doing the same... I couldn't delete or edit the post for a few minutes because of my newby status.

edthesped said:
Is there an unroot method that's just as easy? I'd prefer not to reflash the phone to get rid of root. I guess I'm one of the oddballs here as I can care less about custom roms, I only root to be able to backup and remove bloatware.
Click to expand...
Click to collapse
You should be able to do it via adb shell.
Code:
adb remount rw
adb shell
$ su
# rm /system/xbin/su
# exit
And then uninstall the Superuser app.
I'll try and add it to the script.

Thank You ! so much ... The tool works perfectly on my stock VZ ... Finally can get rid of all the crap that VZ puts in.

Noxious Ninja said:
It's probably possible to unroot via script. I think it might even be possible to move this into an APK and do away with adb altogether. I'll play around with it.
Click to expand...
Click to collapse
That would be awesome. It would be cool if you could make it unroot as well. Keep up the good work!
Tap'd via SGSIII(!)

CooL Very Very CooL
Thanks Noxious Ninja

eakrish said:
If my gs3 came updated with the newest version, will this still work?
Click to expand...
Click to collapse
Mine came with the update and I was able to root successfully with this tool. Very nice.

OTA failing...

I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.

ImYoungxD said:
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
That is probably why. I'd recommend doing a factory reset in recovery.

ImYoungxD said:
I download the OTA and the phone resets. When I get the Android updating screen, it dies on 20%... then reboots and tells me the update failed. anyone know why it's failing to update? I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
If you're running titanium then that means you're rooted, right? If you're rooted you should NOT (ie. Never) take a factory ota update. It has the potential to brick your phone.
What ota was it?
Sent from a SYNERGIZED GalaxySIII

Thats your device telling you to stay way the hell away from OTA's and revert to the dev section for your flashing needs!

I usually update my rooted transformer infinity OTAs with no problems.
Never knew rooted S3 can't update OTAs. meh.
I don't feel like flashing the phone because backing up the IMEI looks like such a pain ... Looks like I will have to look over it again.

ImYoungxD said:
I usually update my rooted transformer infinity OTAs with no problems.
Never knew rooted S3 can't update OTAs. meh.
I don't feel like unlocking the phone because backing up the IMEI looks like such a pain ... Looks like I will have to look over it again.
Click to expand...
Click to collapse
all you do is open terminal emulator, grant super user access, and type "NV Backup". I almost busted out in sweat the task was so strenuous.

droidstyle said:
all you do is open terminal emulator, grant super user access, and type "NV Backup". I almost busted out in sweat the task was so strenuous.
Click to expand...
Click to collapse
I have to start from scratch. I don't have ABD or whatever that thing was called. I'm going to try it out again some other day.

ImYoungxD said:
I have to start from scratch. I don't have ABD or whatever that thing was called. I'm going to try it out again some other day.
Click to expand...
Click to collapse
terminal is a app you download from the playstore... all you need is root access to use it.

droidstyle said:
terminal is a app you download from the playstore... all you need is root access to use it.
Click to expand...
Click to collapse
It's that simple...? never knew i can download it from the play store...
What is this whole site for? http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/

read this thread
http://forum.xda-developers.com/showthread.php?t=1852255

I got that link in step 1.
"1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread."
That site with the guide to install adb has terrible instructions so I gave up.

ImYoungxD said:
I got that link in step 1.
"1. If your phone does not have Terminal Emulator installed, you will need to use ADB. Download and install the Android SDK platform-tools for your platform. This is a bit non-trivial as it requires the installation of the Android SDK, however, you can find a guide for installing adb here. After installing, open a command prompt and navigate to the "platform-tools" folder within the SDK, where adb is stored. If you need additional help on this, simply ask in this thread."
That site with the guide to install adb has terrible instructions so I gave up.
Click to expand...
Click to collapse
Dude you are making this way too difficult lol...install terminal emulator from the playstore and run the nv backup command...then never worry about losing imei again.
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup

I had the same problem. Ended up using odin to push the latest stock software which included the update. Now to see if I still get the no sim error. Realizing after all this time I really didn't need to root.

ImYoungxD said:
I did freeze some apps from titanium backup.
Click to expand...
Click to collapse
This is without a doubt the reason the update failed (unless there are multiple reasons). If you unfreeze the apps, it should install as expected.

apacseven said:
This is without a doubt the reason the update failed (unless there are multiple reasons). If you unfreeze the apps, it should install as expected.
Click to expand...
Click to collapse
I had zero apps frozen and was unable to install the update. Pushing it via Odin was the only thing that worked for me.

mdt73 said:
I had zero apps frozen and was unable to install the update. Pushing it via Odin was the only thing that worked for me.
Click to expand...
Click to collapse
Yes it isnt the only thing that can cause an update to fail. But since he already stated that he had frozen some apps, then it is known that the check will fail and the update wont proceed.

If you don't know why it failed. download to OTA. And when it prompts you to install, say you'll do it later. Now extract the update file from your /cache/ directory. (That's where it was on Motorola's, I think its /cache/fota/ on our S3 ). Copy/move that file to the root of your SD card. Reboot into stock recovery and flash it. Watch the update when it fails it will call out specifically what went wrong. When you let the system automatically do it you don't get that luxury. If you initiate the update on your own through stock recovery though, you are granted that key piece of Intel as to what it didn't like.
Freezing anything in titanium will fail an OTA automatically. It checks system files to make sure certain ones are there, especially bloatware. Also having custom recovery will fail you.
As was said if your rooted you should never both with OTA anymore. If you're coming from a motorola like I did it is hard to grasp that at first. We needed official OTA to update the kernel. So you almost had to do it. Now though. We have an unlocked bootloader here. You can flash any kernel you feel. So OTA are meaningless for us on the S3. The devs steal all the good code and bits and put it in their ROMs and leave out the garbage. No reason to need official OTA anymore then unless you truly want to
Sent from a GlaDos Baked Potato

droidstyle said:
Dude you are making this way too difficult lol...install terminal emulator from the playstore and run the nv backup command...then never worry about losing imei again.
For Terminal Emulator: The actual "beef" of the command is the "reboot nvbackup" line. Therefore, if you have Terminal Emulator installed, you can just run the command straight off your phone. Enter these two commands from the app:
Code:
su
reboot nvbackup
Click to expand...
Click to collapse
Seriously..... That was easy lol. What's the point of step 1
Since I never read the next lines that says " If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.", I never completed backing up the IMEI probably because I didn't know the Terminal Emulator was an playstore app.... Now I got a backup, I'm unlocked, running a custom rom. Thanks a lot man. You helped a lot.

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM

ImYoungxD said:
Seriously..... That was easy lol. What's the point of step 1
Since I never read the next lines that says " If your phone is rooted and has Terminal Emulator installed, you don't need to do any of this. Simply open up the Terminal Emulator and go to step 2.", I never completed backing up the IMEI probably because I didn't know the Terminal Emulator was an playstore app.... Now I got a backup, I'm unlocked, running a custom rom. Thanks a lot man. You helped a lot.
Click to expand...
Click to collapse
No prblem sir, glad to help!

Root Now Available For ASUS MemoPad FHD 10 Model ME302C

Update 1-21-14: Root for 5-0-11 available - go to pg 17 for details, pg 20 for new and improved method. Having said this, there are no real benefits to Android 4.3 over 4.2, so I recommend staying with 4-7-3.
Yes, folks after two days of trial and error I finally was able to build a system image file (from the US OTA update files) that you install via fastboot.
Install Instructions:
First, BACKUP! Use ASUS App Backup for installed Apps (and their data) and I also use My Backup to backup personal and system settings info. Once rooted, use My Backup Root (or keep using ASUS App Backup for Apps and My Backup (non-root) for everything else. Always Backup to your External SDcard as a Factory Reset (should you need to do one) or if you have to or accidently run 'fastboot erase userdata' will erase your internal SDcard.
Second, Charge your Battery - make sure you do any flashing with a good charge, battery going low during this process can do 'bad things'...
Linux Users Note: I'm using Ubuntu and fastboot will not recognize the MemoPad. Still trying to resolve this, the latest Windoze version of fastboot works.
Download ME302C-US-Root.img.gz from MediaFire (see below)
Install the Minimal ADB-Fastboot into a folder (google this you're on your own)
Install the ASUS USB Drivers (google this you're on your own)
Place the image file in the adb/fastboot folder (do not decompress, install as is)
Run these fastboot commands:
fastboot devices (make sure your MemoPad is connected)
fastboot erase cache
fastboot erase system
fastboot flash system ME302C-US-Root.img.gz
Reboot from MemoPad recovery menu
Install from Market:
SuperSU v1.86 Chainfire (required for all other apps to work)
Root Checker (run it to confirm you have root)
You are now rooted
Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to enhance that by installing BusyBox from the Market and use Safe Install method to add new links to the ones already set for toolbox (explained in busybox).
Enjoy your Rooted MemoPad!
Download the image file from here:
http://support.mediafire.com/download/avhe9zizn7z0t5w/ME302C-US-Root.img.gz
If the flash fails or doesn't root, you can just go back to the original OTA update by downloading it from ASUS and running:
fastboot erase cache
fastboot erase system
fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip
Don't post questions about installing/using fastboot or USB drivers, it's been covered ad-nauseum here and other places - google is your friend. If you have the LTE model (ME302KL), that has a locked bootloader and requires the unlock utility available on the ASUS website before you run fastboot.
Thanks goes out to djsven for getting this idea started, then getting it done himself in Germany using the German distro from ASUS. I ended up having to extract the su binary he had as the three I tried from different downloads didn't work. Not sure where he got it but it's a winner!

gbkelley said:
Yes, folks after two days of trial and error I finally was able to build a system image file from the US OTA update that you install via fastboot. All I need to do now is find a free file upload site to host the file for you to download.
Install Instructions:
Download ME302C-US-Root.img.gz from (wherever)
Install the Minimal ADB-Fastboot into a folder (google this)
Install the ASUS USB Drivers (google this)
Place the image file in the folder
Run these fastboot commands:
fastboot devices (make sure your MemoPad is connected)
fastboot erase cache
fastboot erase system
fastboot flash system ME302C-US-Root.img.gz
Reboot from MemoPad recovery menu
Install from Market:
Root Checker (run it to confirm you have root)
SuperSU
Some app requiring root and run it - you should get a notification from SuperSU to grant su for app
You are now rooted
Note: this install follows the ASUS update script that links various binaries in /system/bin to 'toolbox' so you may want to replace that by installing BusyBox from the Market.
Enjoy your Rooted MemoPad!
I'll update this post when I have a download url for you.
Click to expand...
Click to collapse
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.

Turbojugend said:
Where can I find ME302C-US-Root.img.gz ???? Searches are finding nothing.
Click to expand...
Click to collapse
+1

Why not use Mega? Seems to always work and have great speed.

It is rooted...thank you.
Sent from my ME302C using Tapatalk 4

Turbojugend said:
Why not use Mega? Seems to always work and have great speed.
Click to expand...
Click to collapse
I tried RapidShare and it was crap. MediaFire was next on my list and that worked so I used it. May try Mega if there are problems with folks getting the file from MediaFire, we'll see...

Worked for me. Updated to 4.7.3 and is rooted.
Tried in Linux and could not get fastboot to recognize device.
Tried in Windows Server 2012 with this driver:
http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices
Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.
-notten

notten said:
Worked for me. Updated to 4.7.3 and is rooted.
Tried in Linux and could not get fastboot to recognize device.
Tried in Windows Server 2012 with this driver:
http://software.intel.com/en-us/articles/intel-usb-driver-for-android-devices
Ran setup file as Administrator with compatibility mode set to XP SP3. Required a restart before "fastboot devices" worked. If anyone can post a way to make fastboot work in Linux for this tablet, it would be appreciated.
-notten
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=537508
or this...
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk

gbkelley said:
Try this:
http://forum.xda-developers.com/showthread.php?t=537508
or this...
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Click to expand...
Click to collapse
Hey, thanks, but neither of those has anything I haven't tried. I'm using the latest SDK and running fastboot as root so it's not the perms. I read on some Intel forum that someone else is having trouble getting it to work in Linux also.
Any luck with iptables? I don't think the kernel for this tablet comes with iptables enabled. I tried a few methods of getting it installed (DroidWall, iptables (beta) from marketplace). If I screw up the kernel on this, will flashing over it with the system image you upped revert it?
-notten

Thanks a lot for all of this gbkelley. Cheers!!

notten said:
. If I screw up the kernel on this, will flashing over it with the system image you upped revert it?
-notten
Click to expand...
Click to collapse
No my image is the /system folder only. Kernel is in boot.ini. The OTA update zip should fix it though as it has boot.ini

Xposed framework works great. Gravity box and app settings work great. Thanks for root.
Sent from my ME302C using Tapatalk 4

Links if you don't want to google it
Minimal ADB and Fastboot
How to install USB drivers

tdamocles said:
Xposed framework works great. Gravity box and app settings work great. Thanks for root.
Sent from my ME302C using Tapatalk 4
Click to expand...
Click to collapse
Hide battery work for you?

Got Root, Thanks so much.

gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?

Turbojugend said:
gbkelley, this tablet has been out for a pretty long time, what do you think is the reason for the lack of ROM's and dev for it?
Click to expand...
Click to collapse
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.
-notten
EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15
Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.

notten said:
I would think that until a few days ago we didn't have a recovery image to which we could revert. I don't know precisely what's required to build a custom kernel for this tablet, but I'm guessing it's slightly more difficult since we don't know the exact kernel config. I don't think there are any source distributions of this kernel, and I somehow doubt we're lucky enough to have had ASUS build the kernel with CONFIG_IKCONFIG. Then there's probably custom patching that they've done to the code that they probably just won't release. But assuming we had a kernel config we can start building some nice ROMs or even updating the OS to kitkat, etc. As far as default apps/themes/whatever, I guess you could extract the recovery image, repackage it with your favorite APKs, themes, etc., and now you have a new ROM. I'll participate in ROM building for this tablet once we get a kernel config.
-notten
EDIT: Looks like kernel config was found a week ago by ze Germans: http://www.draisberghof.de/usb_mode...sid=c87b172460e22c6f0021f69c3bd5a601&start=15
Looks like it's time to start building custom ROMs for this tablet. I'll have to look into it sometime this week.
Click to expand...
Click to collapse
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version

Turbojugend said:
Maybe I am getting my versions mixed up. Is this version of the tablet brand new, not the same that has been out for months? Mine is the ME302C version
Click to expand...
Click to collapse
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.

notten said:
I believe you're right in saying that this tablet has been out for some time. I suppose there has been enough interest that things are now starting to take off. I mean, I bought it a couple weeks ago and I assumed I'd have to use the WW SKU root and try go beg ASUS for kernel configs. Seems like most of that has been taken care of in the last week. I'm actually really glad. It's a good time to be an ASUS MeMO Pad 10 FHD owner.
Click to expand...
Click to collapse
Ok cool, I just don't want to be stuck with something that will have nothing going for it. I really like the tablet, but if it was going to be dead on XDA I would exchange it for the Sony Xperia Z Tablet. Both fit my needs for what I use it for.

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?

May Update Help?

Google Store purchased, currently have root and twrp installed, bootloader unlocked.
I read briefly that to accept the new update and keep root, you have to mess with the bootloader? Is there some sort of simplified guide on this?

Thanks to chainfire, there is a guide for updating to may version and keep may bootloader.
First, you have to flash new factory image or sideload the ota
Let it reboot, now you lost recovery, custom kernel, root etc..
Reboot to bootloader and boot to twrp, flash supersu and the zip provided by chainfire for signing the bootloader
Reboot and you should have root with may update
If you want a custom kernel or twrp you should flash the zips and the verification tool, i didn't understand the right process for this, for me it looped a couple of times but after flashing those files a bunch of times in different orders it succesfully booted with no errors.
I'm currently running stock 7.1.2 may update with supersu 2.79 SR3, TWRP 3.0.1 RC1, franco kernel r15 with no errors, everything running perfectly

Where can we get the May ota download and a refresher on sideloading it? I've done that before but don't do it often enough to get through it quickly... currently running 7.1.2 / NHG47K on my Google bought Pixel which has been unlocked, and rooted. Though I've not installed TWRP, I can bootload into it fine....
My phone app has suddenly started acting all wonky, so I'd really like to update and see if that will help straighten things up.
Thanks for the assistance...

Got the May ota and will now sideload it. Where is this 'guide' that you mentioned Chainfire has setup to assist folks handling the May update?? I'd like, specifically, to get a copy of the zip file that signs the bootloader.
Thanks!!

I am wondering also. Still using NDE63P from October, wasn't aware we could take OTA's at all and keep root. Been having so many Bluetooth issues, it's worth a shot given their focus on it a month or so ago.

Well... up until this recent May ota release, it used to be pretty easy to simply download the latest Superuser zip file and re-install it on your phone, thereby re-establishing root access (assuming your phone is / was unlocked and rooted prior to taking the update). That is not the case going forward.... but I am still researching it.... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

Oh wow, that's super easy. Sweet! Now I need to find out where the past OTA's are so I can flash all of those...
I'm going to give all that a try soon, if anyone following this thread needs help or has questions, feel free to reply here with them.
To dumb down that entire OP into the reason why it's needed: the OTA's being sent out up through April 2017 was just the OTA itself. In May, they started requiring them to be encrypted with a certificate, but didn't provide requirements on from whom the certificate comes from. This means that now, instead of just flashing the ZIP, you first encrypt it with your own certificate and then flash the result of that.
They mention the private keys can be discarded later, given they are generated for the sole purpose of uploading OTA's to the phone, I would think keeping them on the internal SD card of the phone itself would be suitable. Heck, zip those puppies up and email them to yourself, they're not being used for security, why not, right?

Try here: https://developers.google.com/android/ota
Just sideload the latest... you only need one

pstgh said:
... https://developers.google.com/android/ota
Just sideload the latest
Click to expand...
Click to collapse
pstgh said:
... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yes, the first link is the ota repositories, download the zip of may, then put it in the adb folder, reboot to recovery, go in advanced menu and start sideload, without wipe cache or dalvik.
Then in cmd just type "adb sideload <name-of-the-ota.zip>"
Let it finish both steps and reboot, then you are ready to boot to twrp and flash supersu and the zip v3 from chainfire's thread for signin the bootloader.
That's it

Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!

pstgh said:
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
Click to expand...
Click to collapse
better pro tip: tab auto completes the filename.

exad said:
better pro tip: tab auto completes the filename.
Click to expand...
Click to collapse
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal.
(I use ConEmu, so right-clicking the terminal itself pastes what's on the clipboard; some Linux distros do this also Command Prompt I think right click is done on the title bar or some obscure thing like that, can't remember).

Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal. -
I like this one but when I tried it, fyi, it pastes the path with quote marks on either end.... which is burdensome

Quotes are accepted in the adb commands. Without them, each space in the path is interpreted as an argument delimiter.
adb some-command C:\Program Files\Some-Program\Main.exe
passes "C:\Program" and "Files\Some-Program\Main.exe" as two different arguments to adb. Surrounding​ it with quotes instead allows adb to use the full path correctly. Common practice with command-line apps, although not universally supported.
It does work with adb/fastboot though, just did it a couple days ago to upgrade my Huawei Watch with the Wear 2.0 OTA that it kept failing to detect was available.