Database Info

Roots! Bloody roots!

Among our TF700 Forums/Fora, there have been some people with issues involving the acquisition of the legendary root. It seems that though it is simple to get under typical circumstances, it is possible to encounter atypical difficulty for whatever the reason. I will try to gather information from the problems people have encountered and post possible solutions. Let it be known that I, myself, have not personally encountered these issues nor am I a Master Rooter of the Transformer series. I merely want to collect and present possible solutions so that those with problems will have an easier time of finding things to try and get their Infinity properly rooted.
If you have questions regarding why DebugFS isn't working, I propose you consult the main thread here. If none of these methods work, please start your own thread involving the things you have tried and the issues you are encountering as it will be easier for those much more intelligent than I to assist you with your problems.
Notes:
You do not need an unlocked bootloader to get root access.
Rooting the TF700 does not void your warranty - unlocking the bootloader does. (e.g. Not the same thing)
All commands will be listed in "double quotes" - the quotes should not be typed.
Make sure to always use the most up-to-date version of sparkm3's DebugFS script.
I will be updating this thread as I come across more problems / solutions.
DebugFS doesn't complete:
Make sure that ASUS Sync is disabled in Settings -> Accounts & Sync
Make sure Unknown Sources is enabled under Settings -> Security (under Device Administration)
Make sure USB Debugging is enabled under Settings -> Developer Options
Make sure you have installed the drivers (you can download the drivers from sparkym3's OP)
-It should show up in Windows Device Manager as an adb composite device
Make sure your computer can see the device (use adb from within the DebugFS package and type in "adb devices" - a list should show up with your device in the list)
Make sure that ASUS Sync is uninstalled from your PC
Try a different computer
When DebugFS does complete, you should be able to open up Terminal Emulator, type in "su" and your prompt should turn from "$" to "#". Alternatively, you should be able to do the same thing via adb ("adb shell" then "su").
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.

Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.

Just received my champagne today fully updated .26, got root, busybox, and titanium back up with no problems... New to all this but had no problems getting rooted. Love the infinity (C7) so far GPS works,no light bleeds, good wifi, pretty smooth, hopefully the future updates wont screw my tablet and unlike the 4 primes I had when when it first came out defect after defect. Looks like this one maybe a keeper.

d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
You can link to this thread if you believe that it will be helpful for others to read over. Any sort of suggestions of what you think would be easier to follow or details I should provide are welcome.
Also, I read over that post you noted and I have a question about that. The post mentions changing "adb wait-for-device" and suggests that it could be changed to "pause". Reading over the batch file though, it seems that sparky uses both "pause <CON" and "@pause <CON" so it makes me believe that perhaps one of those would be more appropriate. What do you think? or should I be directing this question to sparky?
Edit: I placed a request for the information in the main DebugFS thread.

I believe wait-for-device is more appropriate for a script, while pause is better for manual adb management (just imagine what happens).

d14b0ll0s said:
I believe wait-for-device is more appropriate for a script, while pause is better for manual adb management (just imagine what happens).
Click to expand...
Click to collapse
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
(Copy & Vomited from post)
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
(/Vomit)
which may be something to try before actually going for a line-by-line manual execution.
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.

d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
If you would like to update this post you linked to, I update the tool a few days ago to include pauses along with the wait-for-device calls. I removed the pointless lines that got left in there, and I am using a better way to determine su access. Finally, I updated it to kill asus sync if it is running.
The new version that should have all the fixes is v2.2
---------- Post added at 01:36 AM ---------- Previous post was at 01:33 AM ----------
alienedd said:
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
(Copy & Vomited from post)
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
(/Vomit)
which may be something to try before actually going for a line-by-line manual execution.
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.
Click to expand...
Click to collapse
I responded to your post in the other thread, but I will copy it here as well, for easy reading.
There should be no difference between the pause that starts with @ and the one that doesn't (as far as this is concerned), I don't know how both got in there.
The reason that I added <CON to the end was because the script was ignoring the pauses and just continuing anyway (because it already had input stored in the buffer). The <CON just insures that the input is coming from the console (user) instead of some other buffer.

sparkym3 said:
I responded to your post in the other thread, but I will copy it here as well, for easy reading.
There should be no difference between the pause that starts with @ and the one that doesn't (as far as this is concerned), I don't know how both got in there.
The reason that I added <CON to the end was because the script was ignoring the pauses and just continuing anyway (because it already had input stored in the buffer). The <CON just insures that the input is coming from the console (user) instead of some other buffer.
Click to expand...
Click to collapse
Thanks for the explanation in feedback in both threads. Much appreciated it.
Added d14b0ll0s's link to post for "last resort" situations.

alienedd said:
My question was whether when modifying the batch file if the person should be using "pause" or "pause <CON" as mentioned in burningcf's post
Perhaps I should just add a link to the post itself but I'm worried that it might go over some people's heads as to what is going on there. Well, let's see if I can get some more background from sparky and then I'll include what I can.
Click to expand...
Click to collapse
Sorry for reading your post neglectfully, I was sleepy already but I believe sparkym3 responded to it now.
sparkym3 said:
If you would like to update this post you linked to, I update the tool a few days ago to include pauses along with the wait-for-device calls. I removed the pointless lines that got left in there, and I am using a better way to determine su access. Finally, I updated it to kill asus sync if it is running.
The new version that should have all the fixes is v2.2
Click to expand...
Click to collapse
Good job, thanks for this! I will update the rooting part in the tweaks thread.
And I believe there is no reason to add the pause solution here now or just you could mention it's obsolete.

Great post > thanks .... but ......
alienedd said:
Among our TF700 Forums/Fora,.......
If you have questions regarding why DebugFS isn't working, I propose you consult the main thread here. If none of these methods work, please start your own thread involving the things you have tried and the issues you are encountering as it will be easier for those much more intelligent than I to assist you with your problems.
Notes:
You do not need an unlocked bootloader to get root access.
All commands will be listed in "double quotes" - the quotes should not be typed.
Make sure to always use the most up-to-date version of sparkm3's DebugFS script.
I will be updating this thread as I come across more problems / solutions.
DebugFS doesn't complete:
Make sure that ASUS Sync is disabled in Settings -> Accounts & Sync
Make sure Unknown Sources is enabled under Settings -> Security (under Device Administration)
Make sure USB Debugging is enabled under Settings -> Developer Options
Make sure you have installed the drivers (you can download the drivers from sparkym3's OP)
-It should show up in Windows Device Manager as an adb composite device
Make sure your computer can see the device (use adb from within the DebugFS package and type in "adb devices" - a list should show up with your device in the list)
Make sure that ASUS Sync is uninstalled from your PC
Try a different computer
When DebugFS does complete, you should be able to open up Terminal Emulator, type in "su" and your prompt should turn from "$" to "#". Alternatively, you should be able to do the same thing via adb ("adb shell" then "su").
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.
Click to expand...
Click to collapse
>> sorry if I am missing something >>> pls forgive as am very very NEW TO this " rooting" process
AND am still trying to GET MY TF700 from this crazy 'bay plac e !!!
so my question(s) is...
a) what hardware I need? or Does the transfermer (TF700) come with a USB cable to connect to PC
b) if not ; where can I get one of these ordered > so am ready when i get mine.
c) from what I read @ asus website > doing ROOT and UNLOCKING = voids warranty!! true ??
thanks in advance for answers

Debbie1759 said:
>> sorry if I am missing something >>> pls forgive as am very very NEW TO this " rooting" process
AND am still trying to GET MY TF700 from this crazy 'bay plac e !!!
so my question(s) is...
a) what hardware I need? or Does the transfermer (TF700) come with a USB cable to connect to PC
b) if not ; where can I get one of these ordered > so am ready when i get mine.
c) from what I read @ asus website > doing ROOT and UNLOCKING = voids warranty!! true ??
thanks in advance for answers
Click to expand...
Click to collapse
A) It comes with it
B) no need
C) Rooting does not void warranty but Unlocking will void your warranty.
Sent from my ASUS Transformer Pad TF700T using XDA Premium App

After deleting asus sync, then reisntalling superuser from the market did the trick thanks!

Thanks
jjdevega said:
A) It comes with it
B) no need
C) Rooting does not void warranty but Unlocking will void your warranty.
Sent from my ASUS Transformer Pad TF700T using XDA Premium App
Click to expand...
Click to collapse
Thanks for info..
> looking forward to grabbin this bad boy and ridin him to ROOT ! :angel:

d14b0ll0s said:
Thanks for this, well done (I'm going to add a link to this in my tweaks how-to if that's ok).
I believe you could add this one to the list.
Click to expand...
Click to collapse
having trouble getting rooted and tried your link, everything went fine, it even shows the uid and gid as = 0, but i still dont have root when i boot up and run root checker or superuser to update binaries. starting to look like i might have to go back to stock recovery and do a fresh install of firmware. I have even flashed TWRP through fastboot and installed a rooted rom (Zues v4) and still had no root. Really at a loss for what to do next.

Somehting that might help
alienedd said:
DebugFS does complete but still can't get root:
Try to run the SuperUser application
Try to uninstall and reinstall SuperUser
Try to run the SuperUser Update Fixer (thanks to okantomi)
If all else fails, you can give this a try. (thanks to d14b0ll0s)
Hopefully, this list will eventually help someone.
Click to expand...
Click to collapse
Thanks very much for all your guide, I have always use XDA forums and learn alot about android devices. I want to tell you that yesterday I try to root my TF700 like 10 times and in 3 different computers! I follow all the steps and eveything but I wasn't able to Root it. But in my last try.. I went to setting and in USB Debugging (it was enable) I disable it and enable it again, and then try with the Debug and it finally WORK :laugh:
So well maybe this will help someone that could be in my situation.
Sorry for my bad english.

I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.

das0527 said:
I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.
Click to expand...
Click to collapse
I was in the same boat. I finally installed Black Bean rom which is JB based and it gave me root. The development seems to have tripled just in
Sent from my ICS Razr
---------- Post added at 11:36 AM ---------- Previous post was at 11:25 AM ----------
I was in the exact same boat. Installing Baked Black Bean rom gave me root. I understand your concern with JB roms, however, there are only 2 bugs I have experienced-no GPS and portrait mode. Although they sound like big issues they really aren't. Any game or app I use that runs in portrait only mode works fine. Also I have seen 3 to 4 roms drop in the last 2 days. It will not be long until the devs fix all issues. This is a popoular device among Apple haters and I foresee a lot of really good stuff coming for this tablet. Just try out a JB rom and see how you like it...you can always go back. Hope this helps...I was just as frustrated as you.
Sent from my ICS Razr

Will, thank you for the advice. However, until the custom ROMs become more stable - or until JB is pushed out officially - I'm very wary of unlocking & flashing a custom ROM.

das0527 said:
Will, thank you for the advice. However, until the custom ROMs become more stable - or until JB is pushed out officially - I'm very wary of unlocking & flashing a custom ROM.
Click to expand...
Click to collapse
This is how i kind of feel to. My galaxy nexus feeds all my flashing needs.

worked for me
das0527 said:
I give up. I tried DebugFS, and that didn't work completely. Superuser seemed to be working but Busybox installer & TiBu didn't see root. I tried the manual commands in this thread and it's still not working. Screw this. Everyone that posted help threads on rooting & unlocking & etc. has done fabulous work, including this thread. But I'm just destined to live a rootless life.
*I have no interest in installing a custom ROM till JB is pushed out and I know the ROMs are reliable. I don't want to have to deal with so many bugs.
Click to expand...
Click to collapse
>> am still using Virgin TF700..(recovered from FACTORY BACKUP) but did try the ROOT...using the "DebugFS" method..
and it works >>>>> MUST REMEMBER to stop/switch off this apps = ASUS SYNC..... that is something that got me @ first try..
DOH! than I realised .. and once turned off = worked like a charm !!!
just my 0.02c worth !

Samsung Galaxy Rugby Pro (SGH-547) Root / CWR / Other Hacks

There is now a super thread over here with this root information and some more recoveries. I plan on expanding as more things are developed for the Rugby Pro.
I have added other hacks to this thread below the root download links. Enjoy.
The below guide outlines how to gain root on the Samsung Galaxy Rugby Pro (SGH-I547 ATT / Bell (Yes, Canada works!) / commanche). Please read through the full guide before attempting to root your device.
You will need ODIN v3.04 in order to gain root on the Rugby Pro (comanche), I will not post a link due to the nature of the package. Google has plenty of links for it.
BIG thanks to utkanos for all the help and making this a reality
Install instructions -- goldenlederhosen has provided some further information and detail about the below procedure here
Please read his post as well as the instructions before attempting this procedure
Install drivers from link below
Download necessary packages (clockwork recovery, root update) from the links below
Copy root update to your devices sdcard(s) -- Copy to both if external SD card is present
Charge phone to at least 80%
Power off the phone
Unplug from USB / Charger
Boot into download mode (Home + Volume Down + Power)
When asked if you want to continue, press Volume Up to enter download mode
Plugin phone and
Launch ODIN
Check the checkbox next to "PDA"
Click the PDA button
Select the comanche_cwr_6015_utkanos.tar.md5 file
Make sure only "Auto Reboot" and "F. Reset Time" are selected
Click start
Your phone will reboot one the flash is complete
You now have Clockwork Recovery, continue with the steps to get root
Power off your phone
Unplug from USB / Charger
Boot into Clockwork Recovery (Home + Volume Up + Power -- Release when Samsung logo appears)
Select "Install zip from sd card"
Select "Choose zip from sd card"
Navigate to zip
Select zip
Confirm
Reboot
You should now have root
I am not responsible for anything bad that comes to your device when using the information posted in this thread. Everything here is dangerous, may cause a brick, will void a warranty and has the potential to just plain wreak havoc. Do not complain you followed my instructions and met with a dead device. Consider yourself warned
I've tested to the best of my ability, but I am one person with one device, I cannot catch all potential failure modes. If you find a problem and a fix, or have information that should be added let me know and I will update the necessary information.
Download Links
Head over to the super thread here (link) for links.
CWR Touch / ODIN
Courtesy of childrenofthehorn there is a now a Clockwork Recovery Touch and ODIN images for the ATT varient. The thread is: http://forum.xda-developers.com/showthread.php?t=1990519
Rootz Wiki Forum
childrenofthehorn has gotten a dedicated forum setup over at Rootz Wiki. Check it out: http://rootzwiki.com/forum/556-galax...o-development/

Works like a charm!
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.

dweide9 said:
Thanks for doing this guys. I was thinking I would have to create an insecure kernel for the stock ROM in order to get root. You saved me a lot of time & energy. Expect a donation coming from my way.
Click to expand...
Click to collapse
Thank you much for the donation
Would you be willing to pull an image of the stock boot partition (dd if=/dev/block/mmcblk0p7) and PM me a link?
Also: check the OP, I've added some info on how to get tethering (after rooting) without the need for a dedicated ATT tethering plan.

re: post-root stuff
>Would you be willing to pull an image of the stock boot partition (dd >if=/dev/block/mmcblk0p7) and PM me a link?
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
>Also: check the OP, I've added some info on how to get tethering (after rooting) without >the need for a dedicated ATT tethering plan.
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?

dweide9 said:
I would if I had any experience. My plan to insecure the kernel would have been my 1st time getting my feet wet with such a thing.
Click to expand...
Click to collapse
You can copy the contents of boot by:
Install a terminal emulator from the market
Launch terminal
su
Accept request for root
dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/mmcblk0p7_boot.img
Transfer mmcblk0p7_boot.img to your favorite cloud storage provider
Share link
If you run into trouble or have any questions let me know.
dweide9 said:
Thanks, I did but I don't find Tethering Manager. I did find Tethering Provision. Is that the same?
Click to expand...
Click to collapse
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Sent from my SAMSUNG-SGH-I547 using Tapatalk 2

boot partition image
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
So what fun stuff can you do with this file & how would my image be any different then yours? Or is it another issue, like uploading being restricted because you're a developer?
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.

kemonine96 said:
Provision is a separate app. When I'm back by my laptop in the morning I'll double check the paths and report back. I froze mine using Ultimate Backup or Titanium Backup. I forget offhand.
Click to expand...
Click to collapse
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.

dweide9 said:
I tried to provide the link to both tarball & zipped files of my boot partition image, but I haven't done 10 posts yet, so xda has restricted me. Let see if a little disguise will work:
secured [email protected]/#folders/0BwUellf9svE3M01kampaMU54NWc
Click to expand...
Click to collapse
Thanks for the file. I just finished pulling it.
dweide9 said:
So what fun stuff can you do with this file
Click to expand...
Click to collapse
I plan on using a stock boot image so I can put together an ODIN image that will flash the phone back to a stock state. If you root your phone or have a custom recovery / system / boot OTA updates will generally fail to apply. The best way to get an OTA update applied is to rollback to stock and install the OTA.
dweide9 said:
how would my image be any different then yours?
Or is it another issue, like uploading being restricted because you're a developer?
Click to expand...
Click to collapse
The boot partition should be the same across devices unless you make modifications.
I had to blindly update the boot partition on my device to get root, so I do not have an un-changed copy of it. In order to get an OTA update applied and to work with some Cyanogen / Clockwork Recovery stuff I will need a clean boot partition image.
dweide9 said:
Also, I'm interested in learning the process of how you created/edited the files , in order to root the Rugby Pro. I'm sure your busy, so pointing me toward a tutorial would be great.
Click to expand...
Click to collapse
I worked with a few people to get help putting together an ODIN image that allowed me to get custom recovery and the clockwork recovery update.zip. There is no general guide on the steps necessary.
If you are interested in diving into the custom rom / recovery stuff I will be doing some work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully working on a Cyanogenmod 10 (JellyBean) port in the future. I am working on some items for the Rugby Smart (apache) at present, as soon as that stuff is taken care of I'll be focusing more on the Rugby Pro (commanche). If you are interested in taking a shot at updating the clockwork recovery for the commanche let me know and I can maybe point you in a few directions to get you going.

stuff
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.

dweide9 said:
>I had to blindly update the boot partition on my device to get root, so I do not have an >un-changed copy of it.
You probably know this, but here's where I downloaded Samsung's ROM (disguised again, & I'm pretty sure the new "c" version is for Canada) Just search for sgh-i547:
[email protected]
Click to expand...
Click to collapse
I pulled that package as well. Unfortunately it is only the GPL components they are required to release, not the full ROM sources. It does contain the kernel sources which will be very helpful down the line.
dweide9 said:
>If you are interested in diving into the custom rom / recovery stuff I will be doing some >work with improving clockwork recovery for the Ruby Pro (commanche) and hopefully >working on a Cyanogenmod 10 (JellyBean) port in the future.
I am interested. Realize I have miniscule programming skills (http, xml & Google {now MIT} App Inventor).
Click to expand...
Click to collapse
There is a lot of testing work and guess/check for the ROM building stuff. I was thinking of setting up an IRC channel on FreeNode for discussing work on the device. Would you be interested / willing to move some of the interactive discussion over there once I have a channel setup?
dweide9 said:
Also, I did freeze TetheringProvision, but I rarely tether. Usually I only need to when it's raining & my home DSL slows too much. I'll let you know if I have any problems when I do finally try it.
Click to expand...
Click to collapse
Keep me in the loop. I tend to only tether for the purpose of my tablet when I'm not near a WiFi AP. I wanted to point it out just in case, better to have it working before it's necessary.

Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.

IRC channel on FreeNode is setup: #rugby-pro-dev for those that are interested.

Motorhead1991 said:
Let me know if you want a modded stock kernel . I'l be willing to help, even though I don't have the device on-hand.
Click to expand...
Click to collapse
I think we should be covered at the moment. The first priority will likely be getting a recovery nailed down and 100% before working on a customized kernel. I'm hoping to get recovery nailed sooner than later so we can do things like nandroid and similar before starting in on CM10 or another ROM.
I am also working on the Rugby Smart (apache) CM9/3.0 Kernel/CM10 stuff as well so my time with the Pro is limited at the moment. Hopefully the Smart stuff moves quickly so I can loop back around to the Pro quickly.

>I pulled that package as well. Unfortunately it is only the GPL components they are >required to release, not the full ROM sources.
Ah, learn something new every day.
>I was thinking of setting up an IRC channel on FreeNode for discussing work on the >device. Would you be interested / willing to move some of the interactive discussion >over there once I have a channel setup?
Sure, I already monitor #opennic on freenode, so I can just open another channel.

kemonine96 said:
Looks like TetheringProvision.apk is the one to freeze (do not delete unless you have a backup). If you try this let me know.
Click to expand...
Click to collapse
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."

MCKINLEC said:
I deleted it, and now when I try and turn on the hotspot the device temporarily freezes and then I get the message "Unfortunatley, Settings has stopped."
Click to expand...
Click to collapse
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?

kemonine96 said:
Odd, I'll have to double check my device again. Do you have a backup of the apk, or do you need a copy of it to restore?
Click to expand...
Click to collapse
Thanks, but I made a backup copy, Think the issue could be because it was deleted instead of frozen?

ETA, help, donation etc
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
@kemonine96 et.al.:
When do you think a beta CM port will be ready?
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....

goldenlederhosen said:
I'm very interested in buying the Samsung Galaxy Rugby Pro for AT&T. However, there is no Cyanogenmod port for it yet. I really only want to have a phone if it can run a free ROM.
Click to expand...
Click to collapse
You are not alone in that sentiment. I won't run a device I know won't receive a CyanogenMod port. The good news is as long as there is root, CyanogenMod can be made to work.
goldenlederhosen said:
When do you think a beta CM port will be ready?
Click to expand...
Click to collapse
"Soon". Myself and a couple others are working on a set of changes for the Rugby Smart (predecessor to the Pro) and once they are further along I will be looking into starting the CyanogenMod port for the Pro.
goldenlederhosen said:
I have not done any Android development and very little administration, but I am a seasoned Linux software engineer. Is there any way I can help with porting CM to this phone?
Click to expand...
Click to collapse
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
goldenlederhosen said:
Finally, would a donation (kemonine96 has a paypal donations link) speed up the process? I can't afford to pay hundreds of dollars, but I could do something like 50....
Click to expand...
Click to collapse
As much as I may appreciate a donation, please hold off as I cannot commit to working on CyanogenMod for the Pro in a paid capacity I am comfortable with. I am working 50-60 hour work weeks at my day job so my free time is severely limited. I have every intention on bringing CyanogenMod to the Pro but it is a free time problem more than anything else.

Foreign anglopu
kemonine96 said:
Most definitely, there are a few things that would help out a CyanogenMod port significantly. If you contact me via IRC (see OP) or via PM we can discuss some of the options and take it from there. Please note I leave my IRC connection active 24x7 so I may not respond right away.
Click to expand...
Click to collapse
Okay, will do.

[Q] ASUS Memo Pad HD 7 (ME173x) can't upgrade

So I got my self this nice tab ASUS Memo Pad HD 7 (ME173x), rooted the thing as soon as I got home, removed some bloatware and then after few hours a notification for an OTA upgrade hits me (wich ofc was not available manually).
You are obviously reading this 'couse the upgrade fails, just a broken droid when it tries to flash the upgrade.
Maybe the upgrade is like of a patch (it's just 56MB) and it fails me because I have removed some (well lots actually...) of those nice installed apps?
What to do? Wait for a maybe more substantial upgrade? Look for a full factory image? Just swap the tablet with a new one claiming that "OMG doesn-t-work" (hmm and what after I root the new one, de-bloat, and an other new upgrade hits the air...).
Thanks!

I found the upgrade, wich is cached in /cache/dlpkgfile (and it's a *.zip).
If I browse it I found a lot of apps patches in system/app : would it be safe to erase just those I've disinstalled, re-zip and try to upgrade?

Well the whole upgrade has a checksum, which is not easy to recreate as the script makepatch works (I guess) with a full source / dest combo. Nor it would be simply to re-install some of the apps from market as the versions could mismatch with those provided in the base.
This means that we should need backups from a original un-upgraded device, and see if that would get through the patching.
A factory image would be useful actually.

Hey, ea_.
Sorry that I can't really help you with the update or anything, but I was wondering if you could upload that dlpkg file somewhere for me.
A friend of mine has a MeMO Pad 7 HD here, and he messed up when (improperly) installing Chainfire 3D, rendering the device soft-bricked. Now it's all cool, because I can still access the system and manipulate it, and it's rooted on top of that, so I'm still in control. The problem is as you've mentioned: those idiots at ASUS don't have any upgrade/recovery images posted, so while I am capable of restoring the stupid thing, there's absolutely nowhere [that I can see] to restore FROM!
I was hoping to find someone with a tablet like this, who could share his system files or a recovery image of some sort from which I could recover the device...

IceDrake said:
Hey, ea_.
Sorry that I can't really help you with the update or anything, but I was wondering if you could upload that dlpkg file somewhere for me.
Click to expand...
Click to collapse
Too bad: I gave back my unit yesterday for a replacement (so I could back-up the whole thing as stock) but my shop was out of stock.
They say maybe they'll get some more by 9 August.

IceDrake said:
Hey, ea_.
Sorry that I can't really help you with the update or anything, but I was wondering if you could upload that dlpkg file somewhere for me.
A friend of mine has a MeMO Pad 7 HD here, and he messed up when (improperly) installing Chainfire 3D, rendering the device soft-bricked. Now it's all cool, because I can still access the system and manipulate it, and it's rooted on top of that, so I'm still in control. The problem is as you've mentioned: those idiots at ASUS don't have any upgrade/recovery images posted, so while I am capable of restoring the stupid thing, there's absolutely nowhere [that I can see] to restore FROM!
I was hoping to find someone with a tablet like this, who could share his system files or a recovery image of some sort from which I could recover the device...
Click to expand...
Click to collapse
I have one unit. Let me know what files you need, and I'll help you out.

ericmaxman said:
I have one unit. Let me know what files you need, and I'll help you out.
Click to expand...
Click to collapse
Sweet!
Essentially, I wanted the entire /system (/system/*) so I could compare all the files and find the ones that were modified, or in the worst case: replace them all with the working ones and keep the image for future recovery.
Seeing that the /system partition here is nearly 700MB in .tar.gz form, it might be a bit cumbersome to upload, so if there's a problem with that, these seem more essential to me than the rest:
/system/bin
/system/etc
/system/lib
/system/vendor
/system/build.prop
Click to expand...
Click to collapse
Also, /system/usr seems like it may contain device-specific/personal stuff, so you might want to skip this one either way.
Many thanks!
P.S. Sorry for shamelessly hijacking and derailing the thread. The one I created is here and may be more appropriate.

2 options:
1) restore the removed "bloatware" to its original location
I had the same problem. You can check the update log on the device after the update. I believe it is in /cache/recovery/last_log and you will find the problem.
In Android 4.2 you can better disable bloatware via app manager and disable apps you don't need. Or just rename .apk to .apk.ORG in /system/app (after used stop command and then rm /data/dalvik-cache/* and reboot)
2) restore complete firmware with these tools:
http://4pda.ru/forum/index.php?showtopic=486532
Latest full firmware is ME173X_WW_user_4.2.4.06716_20130918
If you use flash_tool.exe from ULK173_20130618_2123_CSC then load scatter file (MT6589_Android_scatter_emmc.txt) from the main firmware, then flash it.
See attached picture. It is a factory reset process!
Pandawill also has a section in the forum describing flash process: http://www.pandawillforum.com/showt...er-PX2-MTK8389-Quad-Core-(update-Sep-6th-2013)

[FRFA] SCH-I510 Frequently Requested Files Archive - Root - Return to Stock- Other

As our device gracefully ages I have often wondered if Droid Charge users will to have access to the files that were common during the earlier days. Well I did something about it, here...
TweakedROM.com - Other Files > SCH-I510
Download responsibly my friends!
Not everything has MD5 posted, not yet. I will update when validated against local working copy and/or original source if still available. Please, read the disclaimers.
(Be kind, for I am n00b.)
Note:
Please, don't ask me to host your stuff. I can take suggestions (if I missed something important), but this is the main package I fall back on when crack flashing.
Other Note:
[Q] Files, great now what?!?!? How do I root?
[A] Check HERE, and if that helps you be sure to thank JihadSquad for the concise summary. (Yes, it will still work on FP5... and FP8)
PS. If I am mirroring any of your original work, I have probably sent PM's... Let me know if there is an issue, I will make it right.

TweakTools Mirror [FP5] -- Continuity!
NEW TweakTools Mirror up and running! (As of 8/9/13)
This is all the files behind the tweaktools v36 .sh script that we have all come to love from our Android Terminal Emulator...
While I haven't procedurally tested every menu option, I've tried out a good many of the menu options. (Let me know if there are download issues, MIME extensions...)
There were like 3 stock bloat apk's I was unable to locate, but the files are is basically 99.9% there! (Not sure about the animated gif images of a flying raibow pooping pop-tart looking cat that represents some of the boot animations... HERE ...is there a back story to that?)
This time directory browsing has been enabled on the webserver. So... feel free to check out the script syntax right from your browser.
TT 36 for Tweaked 3.2 Repository Mirror:
http://tools.tweakedrom.com/SCH-I510/FP5E/tweaktools/
Note: The official repository auto updates your local scripts. NO "REAL" NEED TO POINT TO THIS MIRROR! If the powers that be want to point to this mirror they can make it happen in a way that most TT users may not even notice
However, if the http://www.tonsit.com/tweaktools/ repository goes down again I can and will post files/instructions on how to point your FP5 Tweaked 3.2 deployments at this mirror.
...feel free to play around.
bread crumbs...
there are 3 .sh scripts in "/system/bin" and "/system/xbin" just modify the variable "HOSTURL" to point to the my mirror.
Suppose you could also point "TWEAKSITE" to HERE.
Enjoy!
PS. If TT was ever forked/updated for FP8 this could serve as a fall back plan for those wishing to remain on the FP5 flavor, theoretically... (Don't hold your breath...)

Oh yeah...
Reserved cause it is cool.

Donate:
Truth is that domain names, servers, and bandwidth all have a cost. If you want to share the load feel free to chip in by clicking this:
DONATE (There is a paypal button down in the jheide44 section.)
That said, most of the real effort was put in by folks like Dwitherell and imnuts. Please consider sending your donation dollars in that direction.
PS. By donating you agree that you have read the disclaimer page, HERE... and THIS. As such, you are aware that donations formally entitle you to NOTHING.

awesome. just FYI, the links to the tweaktools (themes, applications, CWM mods) leads to a forbidden screen.
but glad to see the torch being passed on.
long live the Charge!

jco23 said:
awesome. just FYI, the links to the tweaktools (themes, applications, CWM mods) leads to a forbidden screen.
but glad to see the torch being passed on.
long live the Charge!
Click to expand...
Click to collapse
Not sure if there will be any "torch" passing... my mom doesn't let me play with fire. :silly:
Thanks, and thanks again for testing that other thing
I did throw out some RE-bloat FP8 "/system/app" goodies from my dedexing efforts. Poke around the repository, tools subdomain... Ya can't miss it (currently that is all I have to post out there).
Most folks probably just grab those bits out of the Deodexed Bloated zip that Dwith has posted here on XDA.
PS.
I left some "love notes" to the world at the top of the "repository" page. It is/was just a proof of concept thing, might lead to nothing...
Per the website...
...
This is just an sandbox/idea I dreamed up... it may go nowhere. Don't get your hopes up.
...
Quick and Dirty copy of the old TT instructions appears below... for informational purposes only... Links are Broke... This is not something I want to hear complaints about...
Click to expand...
Click to collapse

jheide44 said:
Not sure if there will be any "torch" passing... my mom doesn't let me play with fire. :silly:
Thanks, and thanks again for testing that other thing
I did throw out some RE-bloat FP8 "/system/app" goodies from my dedexing efforts. Poke around the repository, tools subdomain... Ya can't miss it (currently that is all I have to post out there).
Most folks probably just grab those bits out of the Deodexed Bloated zip that Dwith has posted here on XDA.
PS.
I left some "love notes" to the world at the top of the "repository" page. It is/was just a proof of concept thing, might lead to nothing...
Per the website...
Click to expand...
Click to collapse
ah.... well, I think they might exist somewhere still, as I was able to download them not toooo long ago (even the image of the theme was available). lone problem though is getting permission from the themers to re-post them. I still have ICA theme, BLN mod, some boot animations, and a few others if needed.
but in any event, thank you. i'm here for help.

jco23 said:
ah.... well, I think they might exist somewhere still, as I was able to download them not toooo long ago (even the image of the theme was available). lone problem though is getting permission from the themers to re-post them. I still have ICA theme, BLN mod, some boot animations, and a few others if needed.
but in any event, thank you. i'm here for help.
Click to expand...
Click to collapse
No problem.
Oh yes original credit for TT to Tonsit... Dwith and all the others that brought it together so nicely back in the day!
Credit: Original TT instructions here http://www.tonsit.com/tweaktools/ The links you mentioned are broken there also (my little thing was just a cut and paste to make sure the information is not lost forever).
The tonsit repository has been going up and down (noticed it kicking to mirror from TT terminal interface in recent weeks/months, it was back up last night).
I have been unable to make contact some of the original contributors. If I've done anything offensive let me know, I will make it right.
Permission is the Catch 22... may be no point in tryint to preserve it if there is nothing FP8 flavored to deploy.
...my last Daily driver device was FP5 Tweaked 3.2 all the way!

Thank you so much for this because i know one day the ota updates will no longer be ota available.
how do we use the OTA Updates (Stock from VZW)?

Stauf99 said:
Thank you so much for this because i know one day the ota updates will no longer be ota available.
how do we use the OTA Updates (Stock from VZW)?
Click to expand...
Click to collapse
It has been a while since I played with those... I remember how I plucked them from "/cache" better than than how I upgraded with the FP8 OTA zip. (I DID NOT RENAME THE FILES.)
I originally downloaded an FP8 OTA from XDA before it was formally rolled-out to my device. I remember trying a couple things to get on FP8 the first time (before the OTA roll-out formally hit my phone). After a return to stock, I might have just renamed it "update.zip" and installed from stock recovery, not sure anymore.
If I recall I later stumbled across this method:
Put the OTA zip files on your SD card, after an ODIN return to stock EP4D, flash custom recovery,battery pull, reboot into recovery, then install the CWM zip files like any other CWM zip install... just install the zip files in the proper sequence... I rebooted after each iteration (losing custom recovery each time), so had to re-flash CWM a lot. It was a rinse and repeat operation... (If I recall cutting corners on the full rinse & repeat turned out poorly...)
But it was so long ago I am a bit fuzzy... (so don't try anything I said from your daily driver device, cause I'm just a crazy guy from the internet!)
just a wild guess:
you might be able to temporary cwm, root via cwm install zip (without renaming/deleting "install-recovery.sh"), put the file in /cache, maybe reboot here, and install from "settings > about phone > system update" (maybe have to use stock recovery here instead) ... when it automatically reboots... repeat for each OTA zip
(I have never tried this, but it would be an interesting path to attempt)
If you do decide to play with it nandroid first... and please report your findings
Ultimately I'm sure if/when the OTA's go away someone will take the time to test and formally document the process (I know would).
PS
Wouldn't it be nice if we had an Odin return to stock FP8 option
(as always, no promises)

jheide44 said:
PS
Wouldn't it be nice if we had an Odin return to stock FP8 option
(as always, no promises)
Click to expand...
Click to collapse
haha for sure, unless a FP8 tweaked never comes out i'd probably wanna go back to FP5 for tweaked 3.2
Thanks for the response, I tried install .zip as usual with CWM 302 but it just kinda stopped when i tried.
Is there a way to ODIN the stock recovery, because no matter how many times i re-ODIN the EP4 thing i can't actually do anything, when i click on any of the options (with the power button of course) they don't work. even restart. I have to hold power to get the phone to do anything else

Stauf99 said:
haha for sure, unless a FP8 tweaked never comes out i'd probably wanna go back to FP5 for tweaked 3.2
Thanks for the response, I tried install .zip as usual with CWM 302 but it just kinda stopped when i tried.
Is there a way to ODIN the stock recovery, because no matter how many times i re-ODIN the EP4 thing i can't actually do anything, when i click on any of the options (with the power button of course) they don't work. even restart. I have to hold power to get the phone to do anything else
Click to expand...
Click to collapse
I've never had success with nandroid backups on the 302 "blue" recovery... I've never played with ext4 either... (As such no MD5 on the site and general missing MD5 disclaimer... If someone has a known working copy of the 302 "blue" ext4 friendly recovery please let me have a copy... I'd like to compare MD5s)
try "0817_charge_recovery.tar.md5" from the site, the Orange one
MD5: 681b53aedc889285d3e18e9e23bd199d
If you Odin back to stock again you will have the stock recovery, right? If your 302 CWM buttons aren't working from recovery that might be your only option...
If not, Dwith posted a stock FP8 recovery here (might also want to read up on what was said about ext4 and the stock FP8 Kernel)
Given the button thing, i am not sure about the stock recovery image from an odin thing... I've never tried that for this device (safe bet is another return to stock Odin party.)
Anyone try fastboot? I haven't yet on a samsung device....
Side Note:
I imagine lots of folks will return to Tweaked 3.2 FP5... That is where I stayed prior to the GN2...
TT 3.6 for Tweaked 3.2 Mirror:
I'm tinkering with creating a mirror for the FP5 back end of TT... (a piece of art like this needs to be preserved, or something like that...)
PS Don't try to put the FP5 bits on FP8... i'm not saying you can't or that some things won't work... it would just be IMPOSSIBLE to support/get help if/when the issues present
TT-ish like FP8 thing:
got a little ROM project floating around... I've also been tinkering with the back-end of the TT script stuffs ... may go nowhere on FP8 ... Without a bunch of flashy themes and UI tweaks (TSM Parts) most users would not appreciate it on FP8, and just complain. (Right?)
I MIGHT try to rebrand it "weaktools" on the little FP8 thing for my Jedi skills are weak. (Note: I fully reserve the right to not deliver on this!)

OOPS ignore this...
Please ignore...
Ever wonder how often a message board gets "butt-dialed?"
Sent from my SCH-I605 using Tapatalk 4

jheide44 said:
I've never had success with nandroid backups on the 302 "blue" recovery... I've never played with ext4 either... (As such no MD5 on the site and general missing MD5 disclaimer... If someone has a known working copy of the 302 "blue" ext4 friendly recovery please let me have a copy... I'd like to compare MD5s)
try "0817_charge_recovery.tar.md5" from the site, the Orange one
MD5: 681b53aedc889285d3e18e9e23bd199d
If you Odin back to stock again you will have the stock recovery, right? If your 302 CWM buttons aren't working from recovery that might be your only option...
If not, Dwith posted a stock FP8 recovery here (might also want to read up on what was said about ext4 and the stock FP8 Kernel)
Given the button thing, i am not sure about the stock recovery image from an odin thing... I've never tried that for this device (safe bet is another return to stock Odin party.)
Click to expand...
Click to collapse
the custom recoveries work just fine, but on my stock recovery i can't actually use the commands, i can scroll no problem, but when i hit the power button over any of the 4 options nothing ever happens

Stauf99 said:
the custom recoveries work just fine, but on my stock recovery i can't actually use the commands, i can scroll no problem, but when i hit the power button over any of the 4 options nothing ever happens
Click to expand...
Click to collapse
Ohhh I see...
Hit home
Sent from my SCH-I605 using Tapatalk 4

jheide44 said:
Ohhh I see...
Hit home
Sent from my SCH-I605 using Tapatalk 4
Click to expand...
Click to collapse
haha, oh my gosh if that actually works i'm gonna kick my self.
as long as ur in a could mood do u think u could help me out over here real quick?
http://forum.xda-developers.com/showthread.php?t=2244704

Reserve #2 Updated
BUMP... Reserve #2 Updated...
NEW TweakTools Mirror up and running! (As of 8/9/13)
Enjoy!

Note: The official repository auto updates your local scripts. NO NEED TO POINT TO UNOFFICIAL MIRROR! ...but feel free to play.
Accidentally quoted myself instead of updating the reserved.... Cheers to user error
*** stupid fat sausage fingers and tiny Tapatalk buttons ***
Sent from my SCH-I605 using Tapatalk 4

jheide44 said:
If I recall I later stumbled across this method:
Put the OTA zip files on your SD card, after an ODIN return to stock EP4D, flash custom recovery,battery pull, reboot into recovery, then install the CWM zip files like any other CWM zip install... just install the zip files in the proper sequence... I rebooted after each iteration (losing custom recovery each time), so had to re-flash CWM a lot. It was a rinse and repeat operation... (If I recall cutting corners on the full rinse & repeat turned out poorly...)
Click to expand...
Click to collapse
The upgrades work like a charm. Just put on to sd card and update .zip through stock recovery.
I'm not sure how well they actually "work" because I haven't actually done anything on the phone yet, but when i went to 'about phone' in settings everything was aces, with each upgrade
you da man jheide44

tweaktools
fwiw, i'm moving my web hosting solution around.
tweakedROM.com (tweaktools) will be back up and running after a few days.
Just an FYI...

[Q] Root method discovered for NEC Terrain?

So I saw network unlocked NEC Terrain up on Amazon for about $85 or so, and I was thinking of getting one. However, the fact that root permissions haven't been obtained on this phone is really what is holding me back from purchasing it, and the last time I checked, the devs still have not found a PERMANENT root method for it...
I saw an app called Towelroot by geohot that can (maybe) not only root the Galaxy S5, but ANY recent Android phone, AS LONG AS it does not have 3.4.0 kernel or newer (at least that's what the article said regarding the Note 3 anyway).
Since I do not have the Terrain, I can't test this towelroot app to see if it works. So I was wondering if anyone out there with a Terrain would be willing to test this out to see if it works,and then report back the results. This device came out last year, and has not had software updates since October of 2013 because NEC doesn't want to do Androids anymore, so I am going to assume it does not have the 3.4.0 kernel. So maybe, just maybe, it will work. And who knows, if by some chance it does work, that could even lead to greater things being done with this device...
EDIT: I just read an article from ATT regarding the software on the Terrain on what I think is the latest firmware update. It said the kernel version was 3.0.8. I probably shouldn't, but I'm getting my hopes up. I kinda want this phone
http://www.att.com/esupport/article.jsp?sid=KB421350&cv=820#fbid=ex0inqn4h0e
Sent from my MB855 from the free version of xda app because cheap

It does not work
Hello,
Towelroot doesn't work on NEC Terrain. I've tried it with different configurations. I've also tried: labda root, poot, framaroot, z4root, vroot, baidu root, saferoot. Moreover I've tried manually root phone using this guide, tried dd modified boot.img, but that didn't stick and after reboot there wasn't any changes.
Problem is that one can't remount /system partition to rw. It just says “invalid argument”. Furthermore there is not any fastboot support (locked out I guess).
I can get temp root using method discribed by justDave, remount / and /data (maybe others partitions too, nether tried) partitions, mount ././tmp/xbin (with busybox and su in it) over /system/xbin, but that doesn't get me anywhere.
I'm thinking about dd custom recovery, but I need to read on it thirst. If you have any suggestions or other rooting methonds, manual rooting guides etc., please post them here and I will try them if my knowledge lets me.
Off topic: NEC closed their mobile devision. Just google “NEC Pulls the Plug on Smartphones” (I can't post links form outside). So there isn't any good news for peaple with NEC Terrain.

Well that sucks, towelroot was pretty much my only suggestion. I'll look into others. But just as a heads up, I don't think I'll be buying one anymore, so I won't be taking a LOT of time to research root methods.
And yes, I am aware that NEC stopped with smartphones. I assume that is why they are so cheap on Amazon?
Edit: bin4ry universal root for 4.0/4.1: http://m.ibtimes.co.uk/root-android-smartphone-tablet-universal-tool-install-385487 Chances are low that this will actually work, but I posted it anyway.
Sent from my MB855 using XDA Free mobile app

Yeah... no.
Personally I don't think you should buy it if there isn't permanent root method and I don't think there will be any. NEC Terrain isn't popular so nobody with know-how will join the effort to root it. Also at least my phone has problems with battery (from the moment I got it). It holds charge for 8 hours max. "Wakelock Detector" says it's always awake. Something with suspend_backoff, but because I can't uninstall bloatware I can't find out which app actually causes it. Furthermore without the root one can't turn off "Fast Dormancy", which in my country drains battery. At this point I'm not afraid to hard brick it or nailed it to the wall, because without the root it is good as paperweight for me.
bin4ry universal root for 4.0/4.1 don't worked either. When I ran RunMe.sh (I'm on linux) nothing happens. Script is using commands like "am start -a android.intent.action.MAIN -n com.sonyericsson.android.servicemenu/.ServiceMainMenu" and moving folders which phone doesn't have.

FFDA said:
Personally I don't think you should buy it if there isn't permanent root method and I don't think there will be any. NEC Terrain isn't popular so nobody with know-how will join the effort to root it. Also at least my phone has problems with battery (from the moment I got it). It holds charge for 8 hours max. "Wakelock Detector" says it's always awake. Something with suspend_backoff, but because I can't uninstall bloatware I can't find out which app actually causes it. Furthermore without the root one can't turn off "Fast Dormancy", which in my country drains battery. At this point I'm not afraid to hard brick it or nailed it to the wall, because without the root it is good as paperweight for me.
bin4ry universal root for 4.0/4.1 don't worked either. When I ran RunMe.sh (I'm on linux) nothing happens. Script is using commands like "am start -a android.intent.action.MAIN -n com.sonyericsson.android.servicemenu/.ServiceMainMenu" and moving folders which phone doesn't have.
Click to expand...
Click to collapse
Yeah, I don't think I'm going to buy it anymore. I mean, that $80 price tag on Amazon looks good, but if no one can even get it ROOTED, then even for that price it's not worth it. I've been looking at another cheap, rugged phone to get, the Kyocera Hydro Life which is $125 at Wal-Mart for T-Mobile. At least that phone has a root method.
But maybe one day, if I see a Terrain for like $40 or something ridiculously cheap like that on an online store, I'll pick one up. Yes, smartphones can get that cheap. I saw a Motorola Bravo (not a bad phone, I have one myself with a 4.4.4 ROM) for $40 new on eBay.
But anyway, if I find a new root method, I'll be sure to post it here. Chances are really slim for anything actualy working, but hey, it's worth a try.

*BUMP* *BIG NEWS*
Just spoke with the very generous Kemonine96, a developer who I came to know through his work on the Rugby Smart. What started out as a half-sarcastic post made by me regarding Towelroot and the Terrain turned into what looks like a solution to this device's root issues! He thinks he has a solution to finally root this Terrain. And I believe him, because it sounds like he knows what he is talking about. Here are his exact words regarding some of my questions:
kemonine96 said:
You're welcome to borrow my work. All I'd ask is a note that it was adapted from the work done on the Rugby Pro.
Click to expand...
Click to collapse
He ran into a similar problem with the Galaxy Rugby where the /system would not mount as read/write. He made a root update.zip that fixed this issue. We are welcome to use it/modify it for the Terrain. But BE SURE TO GIVE HIM CREDIT IF YOU RELEASE SOMETHING BASED ON HIS ROOT.ZIP!!!! Please continue reading for more information:
kemonine96 said:
As for using it outright on the terrain: you likely need to adjust it some. Each device varies some and you'll need to hunt down the exact details. Fortunately the d2 familiy are all very similar so modifications should be minimal if necessary. I'd start by trying it and going from there.
You can use the following root (see OP root instructions). Dig through the update script and look for the file I'm renaming. You'll likely need something similar for the terrain. I developed this by gaining temporary root, unpacking an image I took of the boot partition and walking through the init scripts to see if they were calling anything "interesting" on /system. Managed to track down the file that was paving root/custom recovery. Once I knew the file I setup the update.zip to move the file out of the way so the call to it during boot would fail.
https://nuskunetworks.box.com/s/f1h6murg79lcoavvg0fk
The update.zip root stuff I've published requires a custom recovery to be available. The current "best way" prior to towel root was to flash a custom recovery with ODIN, immediately boot into recovery after the ODIN flash, applying the root update.zip and then booting into system. I came up with the exact procedure after much trial, error and chasing down ghosts.
If you have temporary root I'd do something similar to the following for permanent root
Setup busybox somewhere (/data maybe?) and use dd from it to copy off the whole emmc to an external sd card (use OTG + usb key if necessary). Do a full dd of the emmc disk under /dev and do a full dd of each partition under /dev
Start going through the partition images (BACKUPS are important here) using loopback mounts (or similar) and see where everything is at
Create a rough partition map (/dev/emmc0p1 maps to boot, /dev/emmc0p12 maps to recovery, etc [note these are contrived examples, look at the Rugby Pro stuff I've published for a starting point] -- This is a huge help to get others invovled and so you can figure out what is where quickly.
Once you find recovery/boot/system start looking for ways to adjust to get a developer version permanent root. It doesn't have to be pretty, It just needs to work to aid development along. The initial root method for the Rugby Pro was devloped by using a temp root to pull the boot partition, slip permanent root into the boot image, re-flash the updated boot image using dd. Once I had this I was able to start work on custom recovery and a saner root method.
Once you find a permanent root that can be used by developer types start looking at a proper custom recovery and get TWRP/CWM working
Ensure custom recovery (TWRP is a win all around at this point) is 100% and figure out if it's ever blown away during boot by some goofy script in /system (test by flashing custom recovery, booting it, rebooting into normal android, reboot back into recovery)
Get custom recovery mostly situated and work on an update.zip that sets up permanent root in a way that can be used by others easily (see my update.zip as a starting point)
Release custom recovery image, update.zip root and good instructions
Click to expand...
Click to collapse
This could be it. Thanks, Kemonine96. Thanks for not only this, but for your Rugby work as well
EDIT: To see the whole conversation, or in case I am leaving out information, please visit the Samsung Galaxy Rugby Pro Super Thread and go to the latest post. It should be somewhere around there.
Sent from my MB855 using XDA Free mobile app

You may also want to look at the root methods for other msm8960 and msm8660 devices. HTC, Sony and Samsung all used the platform prior to JB and there may be other examples floating around.
The Terrain was late to the party compared to some so it'll likely be trickier.

kemonine96 said:
You may also want to look at the root methods for other msm8960 and msm8660 devices. HTC, Sony and Samsung all used the platform prior to JB and there may be other examples floating around.
The Terrain was late to the party compared to some so it'll likely be trickier.
Click to expand...
Click to collapse
Since NEC gave up on smartphones after they made the Terrain, I doubt we will be getting any official drivers/kernels or anything of the sort from them.
Sent from my MB855 using XDA Free mobile app

jasonmerc said:
Since NEC gave up on smartphones after they made the Terrain, I doubt we will be getting any official drivers/kernels or anything of the sort from them.
Sent from my MB855 using XDA Free mobile app
Click to expand...
Click to collapse
As long as you can get the 3.0 kernel (it's GPL after all) you should be able to get newer releases going. It'll be a pita, but it's doable if you've got a starting point.
The real pain will likely be the keyboard / screen drivers since they are non standard compared to other devices.

kemonine96 said:
As long as you can get the 3.0 kernel (it's GPL after all) you should be able to get newer releases going. It'll be a pita, but it's doable if you've got a starting point.
Click to expand...
Click to collapse
I'd LOVE to be able to do these things myself, but alas, I am but a script kiddie as of now. I will begin my Android-modding studies as of now. Give me about 100 years and I should be good to go!
Sent from my MB855 using XDA Free mobile app

jasonmerc said:
I'd LOVE to be able to do these things myself, but alas, I am but a script kiddie as of now. I will begin my Android-modding studies as of now. Give me about 100 years and I should be good to go!
Sent from my MB855 using XDA Free mobile app
Click to expand...
Click to collapse
Guess where we all started, including myself?
The key is to keep smashing your face on your desk till you get through.

kemonine96 said:
The key is to keep smashing your face on your desk till you get through.
Click to expand...
Click to collapse
And that is why I am glad the phone is rugged.
Sent from my MB855 using XDA Free mobile app

Best way to proceed
If you have temporary root I'd do something similar to the following for permanent root
Setup busybox somewhere (/data maybe?) and use dd from it to copy off the whole emmc to an external sd card (use OTG + usb key if necessary). Do a full dd of the emmc disk under /dev and do a full dd of each partition under /dev
Start going through the partition images (BACKUPS are important here) using loopback mounts (or similar) and see where everything is at
Click to expand...
Click to collapse
Gaining temp shell root and setting up busybox isn't a problem, we already have that (again thanks to justDave). I have almost all partitions as *.img files (one was too big for sdcard file system). Tomorrow I plan to buy an OTG cable and get the last one. But it is impossible to mount most of the partitions. I'm thinking that like boot image, one must to "unzip" other partitions with special program to look inside. Anyone has any advice on this?
Create a rough partition map (/dev/emmc0p1 maps to boot, /dev/emmc0p12 maps to recovery, etc [note these are contrived examples, look at the Rugby Pro stuff I've published for a starting point] -- This is a huge help to get others invovled and so you can figure out what is where quickly.
Click to expand...
Click to collapse
Partition maps already in [DEV][REF]El Grande Partition Table Reference thread. I think there is enough information there or I had missed something?
Once you find recovery/boot/system start looking for ways to adjust to get a developer version permanent root. It doesn't have to be pretty, It just needs to work to aid development along. The initial root method for the Rugby Pro was devloped by using a temp root to pull the boot partition, slip permanent root into the boot image, re-flash the updated boot image using dd. Once I had this I was able to start work on custom recovery and a saner root method.
Click to expand...
Click to collapse
This is where my problems begins. I don't know what exactly change in boot to gain a root. I tried the simplest thing, that is changing ro.secure=1 to ro.secure=0 but that didn't stick. Maybe I did something wrong (used two different methods to create boot.img files. One image was made with mkbootimg another with abootimg), but at least other two people (aluminumx & MrMEEE) tried dd their custom boot.img without any luck. Maybe I should try dd custom recovery first? Or boot.img the way to go?
Just as reminder I want to say that there is not any fastboot support.
Can someone tell me what I should focus on? boot.img or recovery mode?

You could try it again. Just remember that ro.secure exists in multiple places. default.prop, and some inits as far as I remember. I'll check later on and repost. Had you tried to change all of them? I've also read that the image being written has to be the same size as the image being overwritten. I don't know if that's relevant for this though.

I can definitely give kemonie's suggestion a try. However, I am still not confident that we can get permanent root without unlocking/bypassing the nand lock first. I was able to identify the boot and recovery partitions relatively easily, and dd their contents out post no problem as well. Dd a new image back on was the problem... for testing purpose, using the stock boot image as base, I just added a zero length file to the folder, wrap it back up, and dd it back to boot, the file never made it thru even though dd didn't give any error. Which prompted me to think the nand was locked. So the other way of patching the boot partition would be applying an update.zip file in recovery mode, but we need a code as well, see screen shots. And yeah, no fastboot mode neither. It's very frustrating to hit all possible road blocks there can ever be to root this thing. But I do believe that the key lies in my terrain though, because reading from everyone who has posted so far, mine seems to be the only one that is confirmed unlocked. So yeah, if we can get some expert hackers to help in this effort, I wouldn't mind donating my time or even my phone to help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-I547C using XDA Free mobile app

aluminumx said:
But I do believe that the key lies in my terrain though, because reading from everyone who has posted so far, mine seems to be the only one that is confirmed unlocked.
Click to expand...
Click to collapse
What do you mean by that? In case you bought your phone from cellforce on eBay, I doubt your phone is special in any way. Some weeks ago in the light of discussions going on here I asked the seller how he unlocks the phone, whether he tampers with the software or if he just enters unlock codes. He claims he just uses unlock-codes. If that is true then your terrain should not be special, right?

laserdrome said:
What do you mean by that? In case you bought your phone from cellforce on eBay, I doubt your phone is special in any way. Some weeks ago in the light of discussions going on here I asked the seller how he unlocks the phone, whether he tampers with the software or if he just enters unlock codes. He claims he just uses unlock-codes. If that is true then your terrain should not be special, right?
Click to expand...
Click to collapse
hmmm, if that is truly the case, i.e, the seller just entered the code to unlock mine before he sold it, then yeah, mine won't be any special. However, from talking to the multiple other dealers, AT&T support and also NEC support, the unlock codes are not available for this phone at all, which would mean my seller got his batch already unlocked. I could be wrong though since I have talked to them almost a year ago and it maybe true that AT&T or NEC has released the code database. Anyway, the fact is that I haven't been able to find another owner on these forums who has their Terrain unlocked. The hope is that if we can successfully get it permanent root, then we can compare files and settings between the locked and unlocked ones. I do wish you good luck getting the code though, that would definitely be good news for a few people here

I have both a locked and unlocked NEC Terrain. And, if it were to be helpful, in the box of the unlocked one was a little slip of paper that says "CODE" and has a number on it. The phone was unlocked when I received it, so I can't confirm that the code on the paper is the unlock code for the phone.
I'd be happy to pull whatever files would be helpful from either device and post them. Give me a process and I'll get what you need.
aluminumx said:
hmmm, if that is truly the case, i.e, the seller just entered the code to unlock mine before he sold it, then yeah, mine won't be any special. However, from talking to the multiple other dealers, AT&T support and also NEC support, the unlock codes are not available for this phone at all, which would mean my seller got his batch already unlocked. I could be wrong though since I have talked to them almost a year ago and it maybe true that AT&T or NEC has released the code database. Anyway, the fact is that I haven't been able to find another owner on these forums who has their Terrain unlocked. The hope is that if we can successfully get it permanent root, then we can compare files and settings between the locked and unlocked ones. I do wish you good luck getting the code though, that would definitely be good news for a few people here
Click to expand...
Click to collapse

Hey timkiller, good that your vendor gave you the code as well. My guess is that it's the sim unlock code, which you probably don't need anymore as once your phone is unlocked, it "shouldn't" get relocked, but just in case, you should save it somewhere. However, if it's not the sim code but the maintenance code, that would be helpful for the rest of us. If you can try the following and let me know if that works. I am not exactly sure how familiar you are with android, so I will be a bit more detailed here, hope you are not insulted. I am by no means any expert, I basically just want to see If the code you got is the maintenance code or not.
1. power down the phone
2. hold the volume down button, and then the power button to turn on the phone, hold on to the keys until you see the android maintenance picture
3. press up volume, then down volume button, and a menu should show up. You are now in recovery mode. In this mode, you have to use the volume down to cycle through the menu items, the volume up to select it. You should see the following choices, if the menu is different from below, please let us know
a. reboot system now
b. wipe data/factory reset
c. wipe cache partition
d. repair software by sdcard
e. maintenance
4. use the volume down key to move to maintenance, then use volume up to select it. You should now be asked to enter the password. Again, use the volume buttons to enter the code you got. Remember to select OK at the end. If you got kicked out back to the original menu, then the code didn`t work, and proceed to step 5 below. I have no idea what it would look like if the code works though, but I imagine you will have a new menu system. Please let us know either way.
5. Las thing to try is the repair software by sdcard option. Use the volume buttons to select that, it will first ask you to confirm, volume down to yes and you will be prompted to enter password once again. Enter your code and let us know if it works.
Well, I won`t hold much hope on it, but it`s worth a try. if either option works, then we can compare your IMEI with the code, and maybe derive a pattern out of it. I know another NEC phone model is like that.
thanks for your help, crossing fingers
timekiller_9 said:
I have both a locked and unlocked NEC Terrain. And, if it were to be helpful, in the box of the unlocked one was a little slip of paper that says "CODE" and has a number on it. The phone was unlocked when I received it, so I can't confirm that the code on the paper is the unlock code for the phone.
I'd be happy to pull whatever files would be helpful from either device and post them. Give me a process and I'll get what you need.
Click to expand...
Click to collapse

I'm not insulted at all. I'm not an Android expert per say, but I am very tech savvy and can get around the device quite well. I can run a temporary root via adb, extract a partition, whatever it is that would be useful.
The recovery mode menu appears exactly as you describe it.
I tried the code I have to try to get into the maintenance and repair modes. Unfortunately neither worked, both kicked me back out to the previous menu. I suspect it's the unlock code that I have, or possibly even just a code for something else all together that the seller accidentally included in the box. It's a hand written slip of paper with just the word "CODE" and an 8 digit number on it, so we cannot be certain it's even for this device.
I'm happy to try any other ideas, or extract something for you to compare on either the locked or unlocked phone. I will be travelling for the next week so I will only have the unlocked phone with me.
aluminumx said:
Hey timkiller, good that your vendor gave you the code as well. My guess is that it's the sim unlock code, which you probably don't need anymore as once your phone is unlocked, it "shouldn't" get relocked, but just in case, you should save it somewhere. However, if it's not the sim code but the maintenance code, that would be helpful for the rest of us. If you can try the following and let me know if that works. I am not exactly sure how familiar you are with android, so I will be a bit more detailed here, hope you are not insulted. I am by no means any expert, I basically just want to see If the code you got is the maintenance code or not.
1. power down the phone
2. hold the volume down button, and then the power button to turn on the phone, hold on to the keys until you see the android maintenance picture
3. press up volume, then down volume button, and a menu should show up. You are now in recovery mode. In this mode, you have to use the volume down to cycle through the menu items, the volume up to select it. You should see the following choices, if the menu is different from below, please let us know
a. reboot system now
b. wipe data/factory reset
c. wipe cache partition
d. repair software by sdcard
e. maintenance
4. use the volume down key to move to maintenance, then use volume up to select it. You should now be asked to enter the password. Again, use the volume buttons to enter the code you got. Remember to select OK at the end. If you got kicked out back to the original menu, then the code didn`t work, and proceed to step 5 below. I have no idea what it would look like if the code works though, but I imagine you will have a new menu system. Please let us know either way.
5. Las thing to try is the repair software by sdcard option. Use the volume buttons to select that, it will first ask you to confirm, volume down to yes and you will be prompted to enter password once again. Enter your code and let us know if it works.
Well, I won`t hold much hope on it, but it`s worth a try. if either option works, then we can compare your IMEI with the code, and maybe derive a pattern out of it. I know another NEC phone model is like that.
thanks for your help, crossing fingers
Click to expand...
Click to collapse