Database Info

[Q] Screen capture?

Hi guys,
I've been looking but couldn't find an easy answer. Is there a way to screen capture on the Sensation?
Thanks in advance!!!

I got this from the Incredible S forums:
1.Download Android SDK (zip one)
2.Download and Install Java JDK 6
3.Connect phone to PC in debugging mode
4.Where you have extracted Android SDK, go to the tools folder and open ddms.bat
5.Click on the device tab and click screen capture.
6.Capture and save

Any way to do it WITHOUT using a PC?

Toeeknee said:
Any way to do it WITHOUT using a PC?
Click to expand...
Click to collapse
Yes this is what I wanted to know. Isn't there a way to just do a capture and have it saved to your phone without a computer?

Here you go
https://market.android.com/details?....screenshotitfullnoroot&feature=search_result
nothing come for free!!

not without root if you don't want to be tethered to a pc

prateekgujral said:
Here you go
https://market.android.com/details?....screenshotitfullnoroot&feature=search_result
nothing come for free!!
Click to expand...
Click to collapse
i tried the free version of this app , which also stated NO ROOT and it didnt work !!

Dandandroid said:
i tried the free version of this app , which also stated NO ROOT and it didnt work !!
Click to expand...
Click to collapse
u could try this paid one.. maybe it works.. and if it doesnt.. u can always uninstall and claim refund (i think within a certian time frame)

So I go to the HTC Sensation support page and I see that under mechanical I see this issue (sorry I tried to post a link but I guess I'm too new for the forum to let me...something about avoiding spam...).
The second question is my question, is it not? But I can't seem to make is work. Anybody else try this?
*EDIT*
I went to the HTC website's forums and they said that this was some sort of misinformation. This feature currently does not exist even though it came from HTC themselves! Someone did state, though, that there is supposed to be an update soon that MIGHT have this feature...not sure if that also includes unlocking the boot loader!

[MOD]One Click Root and custom recovery

This one click root is only for windows. Make sure to enable usb debugging, then simply extract, then click on root tool sharp program. Once up, just click on the root button, press yes if windows asks you if it is ok to run this program, and soon enough your og droid will have rz recovery, and full root. This works on all froyo builds, including frk76. It does not work on eclair. Do not use this if you already have root, or are running a custom rom simply because you do not have to.
Should have put this here a long time ago. This will NOT work, if you do not have a sd card inserted and working properly on your device:good:
OG droid oneclick V1.0#: http://dl.dropbox.com/u/46535328/droid_oneclick_sharp.zip
Please give feedback, and if this program helps you, then please press the thanks button
Disclaimer: I can not be held responsible for any negative side affects this program causes
Thanks: motocache1,Cyanogenmod, ChainsDD, and raidzero.
If this program does not work for you, you may need to go download .net 4.0 redistributables from microsoft, and/or the motorola drivers.

the root tool app doesnt open any ideas? im running windows 7

joey.gunnarson said:
the root tool app doesnt open any ideas? im running windows 7
Click to expand...
Click to collapse
Yeah, there is a c++ redistributable error. I will fix this and get a new version up in a while. I will have to rewrite in c#, which means my extra features will be gone for now, but one click will still be there.

Wow...That was SUPER EZ!!! Thanks has been GIVEN!!!!b You guys are AWESOME!!!!

rootfan said:
Yeah, there is a c++ redistributable error. I will fix this and get a new version up in a while. I will have to rewrite in c#, which means my extra features will be gone for now, but one click will still be there.
Click to expand...
Click to collapse
So is this a windows 7 problem or something wrong with the method itself?
If I root my og droid will it speed up at all?

well you can overclock, flash new roms, and flash different kernals so yes you can speed it up.

and does this link work as is?
i know what i'm doing with tbolt but clueless with droid.

recDNA said:
and does this link work as is?
i know what i'm doing with tbolt but clueless with droid.
Click to expand...
Click to collapse
The link does work as is, but only for windows operating systems. If you choose to install kernels using rzrecovery which my program installs , then your droid will have major speed improvments.
If you have any problems with the procedure then read the op, and make sure to thank me

windows 7 too?

recDNA said:
windows 7 too?
Click to expand...
Click to collapse
xp, vista and windows seven will all work perfectly

Sleep 300 was kinda stupid but the script works!
It made my Nod32 go nuts though, so if you're getting "this is a virus" from your software, you'll have to disable that before downloading, unzipping and using then re-enable it afterward.

I have no idea what you're talking about?

recDNA said:
I have no idea what you're talking about?
Click to expand...
Click to collapse
Line 10 in the root script:
adb shell "./data/local/tmp/rageagainstthecage & sleep 300;kill $!"
It hangs for like 5 minutes. I got a laugh out of it. And there are no virus' on the download, my stupid anti-virus thought there was so I was just letting people know it's safe, even if their software says it isn't.

why is sleep 300 there?

rootfan said:
This one click root is only for windows. Make sure to enable usb debugging, then simply extract, then click on root tool sharp program. Once up, just click on the root button, press yes if windows asks you if it is ok to run this program, and soon enough your og droid will have rz recovery, and full root. This works on all froyo builds, including frk76. It does not work on eclair. Do not use this if you already have root, or are running a custom rom simply because you do not have to.
OG droid oneclick V1.0#: http://dl.dropbox.com/u/46535328/droid_oneclick_sharp.zip
Please give feedback, and if this program helps you, then please press the thanks button
Disclaimer: I can not be held responsible for any negative side affects this program causes
Thanks: motocache1,Cyanogenmod, ChainsDD, and raidzero.
If this program does not work for you, you may need to go download .net 4.0 redistributables from microsoft, and/or the motorola drivers.
Click to expand...
Click to collapse
well, not sure what I'm doing wrong but here is my experience:
OG Droid 2.2.3 (build FRK76). Attached to computer with usb debugging on in charge only mode. Run root tool sharp.exe, one click root box opens. Click on the 'Root' button and the cmd prmt window pops up and runs some scripts. It hang on line 10 for about 5 mins, blazes through the rest of the script (too fast for me to read what it's doing), closes itself and reboots my phone. when the phone reboots i do not have SU installed. I'm running Windows 7 (64bit) if that matters. Please let me know if i'm missing a step or doing something wrong.
thanks in advance.

i'm having the same issue as the guy above.. seems to be issues with the chmod777 part for me.. mostly the "rageagainstthecage" file doesn't seem to push or activate right, then adb can't find it..
Any Tips?
i'm in USB debug mode.. i have an sd card in.. i have the USB drivers from moto..

For anyone with problems make sure your sdcard is inserted and indeed working properly Make sure it isnt to full eaither. If you have a screen lock set up, make sure to unlock your phone before performing this process. should work after that.

i know this sounds stupid but this recovery will work on all roms?¿ and how do i enter into the recovery?¿ sryy my bad english am from dominican republic

htc s620 said:
i know this sounds stupid but this recovery will work on all roms?¿ and how do i enter into the recovery?¿ sryy my bad english am from dominican republic
Click to expand...
Click to collapse
The recovery will work on all roms just make sure to wipe before install

You can get into recovery by holding the x button on the physical keyboard and the power button.
Sent from my SCH-I535 using xda premium

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] 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

Windows RT 8.0 Recovery Environment Jailbreak

This is a version of the 8.0 jailbreak that will run in the recovery environment. This is meant more for developers than end-users.
It does not force a two minute wait at the start, but that is still required.
As always, it was developed for a Surface RT. Vivo tabs, etc..., your mileage may vary. I developed it targeting the Windows RT 8.0 image that MS uploaded after the 8.1 upgrade issues. I don't know if this varies from the stock image, I don't have it anymore.
I'm also curious as to if it'll run on a Surface 2 in the recovery environment. If anyone can test, I'd be grateful.
The trick to getting cdb and whatnot to run was plugging in valid certificate catalogs for cdb (and some other tools).
It also doesn't work with the side volume keys, though it does work with the volume keys on my Type 2 keyboard.

I think you need to add an batch file to download the symbol. The preloaded one may not work on some other tablets.

LolitaPlus said:
I think you need to add an batch file to download the symbol. The preloaded one may not work on some other tablets.
Click to expand...
Click to collapse
There is no Internet in recovery mode. If you can send me aystem32\ntkrnlmp.exe and system32\ci.dll for your recovery I can add them.

netham45 said:
There is no Internet in recovery mode. If you can send me aystem32\ntkrnlmp.exe and system32\ci.dll for your recovery I can add them.
Click to expand...
Click to collapse
However you can run it under normal Windows RT environment, don't you? I know there is no internet so I said it should be in another file.

LolitaPlus said:
However you can run it under normal Windows RT environment, don't you? I know there is no internet so I said it should be in another file.
Click to expand...
Click to collapse
You can't get at the recovery files easily from a full system either.

netham45 said:
It also doesn't work with the side volume keys, though it does work with the volume keys on my Type 2 keyboard.
Click to expand...
Click to collapse
So, seriously, that was my mistake. I only try to use side volume key. And I delete all my work for recovery jailbreak yesterday. Want to cry now. :crying:
Thank for your work, again.
netham45 said:
There is no Internet in recovery mode. If you can send me aystem32\ntkrnlmp.exe and system32\ci.dll for your recovery I can add them.
Click to expand...
Click to collapse
Is there anyway I can done it myself?

LolitaPlus said:
However you can run it under normal Windows RT environment, don't you? I know there is no internet so I said it should be in another file.
Click to expand...
Click to collapse
I get what you're saying, misread your other post. I don't have my device in a bootable state right now, but once I get it fixed up I'll make a .bat you can run to dump the PDBs for the other kernels.

hisoft said:
So, seriously, that was my mistake. I only try to use side volume key. And I delete all my work for recovery jailbreak yesterday. Want to cry now. :crying:
Click to expand...
Click to collapse
That really stinks. Sorry for your loss.
Assuming we have a way to run unsigned code, does anyone have a way to perform raw reads of a block device? I don't think there's any way to do it with managed code, and my development skills only extend a little into that. I figure there should be a way to compile C++ for ARM though. It might help you recover some of what you lost.
Also, it might help us get deleted files off system partitions. A few of us got lucky in getting Vivotab RTs that didn't have signing files deleted. If we could boot from a USB stick and undelete them, then just about everyone could have them...

nice work and a useful way to boot an RT8.1 system into an 8.0RT RE + jailbreak system
I had to get the correct symbols for my Sept 2012 kernel
You have to unlock the os drive if system has a Live account and it is Bitlockered
I usually skip that and run a batch file
manage-bde -unlock c: -recoverypassword xxxxxx-...
WindowsRE RT8.0
doesn't have a full windows environment or full win32 api (obviously) and no network (so far)
but can run many unsigned RT desktop apps
eg
putty
Strangely it can't run RT8.1 standard OS utilities -- must be some version number etc in the header it doesn't like
I might look into a way to dual boot it from HD (rather than booting from a USB) in due course

This is awsome! Been waiting for some update on something about RT jailbreaking even though it's in a RE environment.