Related
(additional CHOWN notes added below. If you are getting "chown: unknown user/group system:system" read them!
Ok, we do have a WHOLE other thread that was made a sticky already, but you need to read the WHOLE thing to get all the properly interesting parts. I'll make sure I keep this OP up to date.
The following methods enable side loading and installing of apps onto the captivate, without the need of a program on a computer attached via the SDK. There are multiple methods, and for the most part, these methods that have worked flawlessly for many users here on this forum. We're just collecting them all in one post for speed and clarity.
Methods that assist in loading applications, without modification to the settings (a.k.a still need a computer attached) can be found at the collective wiki, http://samsungcaptivate.wikia.com/wiki/How_to_Sideload
ALL METHODS REQUIRE ROOT & BUSYBOX:
Root your phone, see http://forum.xda-developers.com/showthread.php?t=725555
Busybox : http://www.appbrain.com/app/stericson.busybox
Please, save a clean, un-altered backup copy of this file. To be safe. Rarely does corruption occur, but if it does, it won't be good.
Method 1: From Win7x64, Samsung Drivers, Android SDK installed.
This method uses the tools you already have at hand, as part of the SDK. All instances in code blocks are run inside of the command prompt. You will need to know where you installed your SDK, and the tools directory therein.
Once rooted, go install BusyBox installer from the App Market/AppBrain etc and run it. It will download and install the latest version for you.
From my Win7x64, with USB Debugging ON. Ensure that you phone is UNLOCKED as it the SU app will ask for permission for 'UNKOWN' in the following command.
Connect to PC, and Eject/Safely Remove the SD card, and "Turn off USB Storage" on the phone.
open command prompt, follow along:
Code:
> c:
> cd \android\tools
> adb shell
$ su
# cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
# exit
$ exit
mount the SD cards to the pc,
"USB Connected select to... ", Mount
mine mounted as H:
Code:
> copy H:\settings.db settings.db
> sqlite3 settings.db
~> update secure set value="1" where name="install_non_market_apps";
1 row updated
~> .quit
> copy settings.db H:\settings.db
Eject the drive, safely remove, etc.
"Turn off USB storage" etc, to mount it back to the phone
Code:
> adb shell
$ su
# cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# exit
$ exit
> adb reboot
Bam. Done.
Method 2: with Root Explorer
(courtesy of kirbo20)
This is a pretty easy process. I went in to Root Explorer - dbdata - databases - com.android.providers.settings, copied settings.db to my sd card, edited it on my pc with a db editor changed 0 to a 1 next to non market apps. Copied it back to the original directory, rebooted and installed a non market app.
(added by gotfolk)
again using FF plug in..
Click Secure on the left pane
click on install_non_market_apps
click edit
number 3 states value click there and type in 1. hit ok
(/gotfolk)
Please use caution. If you want to make sure the db save properly open it on your sd card before you copy and replace the original. It should open up as a readable table. If it opens up in a txt editor its corrupt. This permanently enables non market apps. You can not toggle it on and off.
( This is a sqlite3 database file, you can find many GUI editors that will be able to handle the editing, including a FF plugin. Search "SQLite" )
Method 3: with Root Explorer & Sqlite Editor & Terminal Emulator
(courtesy of ice3186)
- Open Root Explorer
- Browse to /dbdata/databases/com.android.providers.settings/
- copy settings.db to the root of your sd card ( /sdcard/ )
- Click on the newly copied settings.db in /sdcard/, with SQLite Editor installed, you can open and edit it here.
- Select the "secure" table, and update the value of 'install_nonmarket_apps' from 0 to 1, and save.
- close out of SQLite editor
- copy the modified file ( /sdcard/settings.db ), and browse back to /dbdata/databases/com.android.providers.settings/ and paste
- confirm the overwrite if asked and then open again to confirm it's been changed.
- open Terminal Emulator
Code:
$ su
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# reboot
- reboot phone.
No PC, no Mac, no drivers, no SDK. Viola.
Method 4: Mac & Android SDK
You will see "[sdcard]" through this method...I don't own a Mac so I'm guessing a bit.
This method uses the tools you already have at hand, as part of the SDK. All instances in code blocks are run inside of the Terminal. You will need to know where you installed your SDK, and the tools directory therein.
Once rooted, go install BusyBox installer from the App Market/AppDroid etc and run it. It will download and install the latest version for you.
From a Max OS X, with USB Debugging ON. Ensure that you phone is UNLOCKED as it the SU app will ask for permission for 'UNKOWN' in the following command.
Connect to Mac, and Eject/Safely Remove the SD card, and "Turn off USB Storage" on the phone.
open Terminal, follow along:
Code:
> cd /android/tools
> ./adb shell
$ su
# cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
# exit
$ exit
mount the SD cards to the Mac,
"USB Connected select to... ", Mount
mine mounted as [sdcard]
Code:
> cp [sdcard]/settings.db settings.db
> ./sqlite3 settings.db
~> update secure set value="1" where name="install_non_market_apps";
1 row updated
~> .quit
> cp settings.db [sdcard]/settings.db
Eject the drive, safely remove, etc.
"Turn off USB storage" etc, to mount it back to the phone
Code:
> ./adb shell
$ su
# cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings/settings.db
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# exit
$ exit
> ./adb reboot
Method 5: Android SDK only
Of course, this also requires root and BusyBox.
From the android sdk tools folder in a command prompt:
note: all linux/mac should use './adb' in place of just 'adb', and place quotes on the echo statement between echo and |
Code:
adb shell
su
chmod 666 /dbdata/databases/com.android.providers.settings/settings.db
exit
exit
adb pull /dbdata/databases/com.android.providers.settings/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /dbdata/databases/com.android.providers.settings/settings.db
adb shell
su
chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
chown system.system /dbdata/databases/com.android.providers.settings/settings.db
reboot
NOTICE
You must chown the settings.db file and reboot once it is back in its original location. If you do not, you will not be able to alter settings such as WiFi,GPS, default Ringtones, etc. It's also highly likely that you may wish to chmod to 660 (-rw-rw---), so I've tacked that in here and above.
Code:
> adb shell
$ su
# chmod 660 /dbdata/databases/com.android.providers.settings/settings.db
# chown system.system /dbdata/databases/com.android.providers.settings/settings.db
# exit
$ exit
> adb reboot
Chown Note
In the event that you are getting "chown: unknown user/group system:system" please try 1000.1000 as this has been reported to work on several of the samfirmware-released roms that fail with this message.
Absolutely do not use someone else's settings.db unless you specifially make it a point replace android_id with your android_id!
Special Note
Any of these adb comments can be run from Terminal Emulator (Android Terminal Emulator, free) from the su command. I use the ADB here as it is a lot easier to type into. Terminal Emulator will provide you with a shell that is an exact match of the 'adb shell' command, as they both simply provide the shell to you.
Result:
After completing this process you will be able to load non-market apps directly from the APK files, SDK tools, tools such as DroidExplorer and apps such as APKtor.
You will be able to download the APKs directly, and then install from your favorite file browser (e.g. MyFiles(s), Astro(f), RootExplorer($)...)
Tools
SQLite Administrator (Win, GUI, no FF required) http://sqliteadmin.orbmu2k.de/
SQLite Manager (FF addon, search for it)
Application links
Root Explorer http://www.appbrain.com/app/com.speedsoftware.rootexplorer
SQLite Editor http://www.appbrain.com/app/com.speedsoftware.sqleditor
Terminal Emulator http://www.appbrain.com/app/jackpal.androidterm
BusyBox http://www.appbrain.com/app/stericson.busybox
bump.. settings.db people.. please read the threads!!
good stuff!!!
Ok. I can find settings.db with root explorer. i can copy it and i put it in my sdcard folder but nothing is there when i try to find it on my computer. Im trying to use SQlite editor on firefox. Im also on a powermac g4 if that makes a difference. I did download sqlite editor on my phone and I can find where to change the values for installing non market apps but when I change from a zero to a one it denies me. Please help
Ok, so let me make sure I have your process:
- Rooted
- Installed busybox ?
- Installed Root Explorer
- copied settings.db to /sdcard
-- cant see the file when mounted to Mac, thus can't edit with FF plugin
-- SQLite editor for android wont allow access..
(is this the SQLite Editor you used? http://www.appbrain.com/app/com.speedsoftware.sqleditor)
Try installing "Android Terminal Emulator" from the market (http://www.appbrain.com/app/jackpal.androidterm)
- open Terminal Emulator
$ su
# cd /sdcard
# chmod 777 settings.db
# exit
- Open the sqlite editor, and make the change
- back to Terminal Emulator
$ su
# chmod 660 settings.db
- proceed with rest of instructions.
how many more threads do we need on the same thing? We already have ALL of this info posted, several times.
designgears said:
how many more threads do we need on the same thing? We already have ALL of this info posted, several times.
Click to expand...
Click to collapse
Please read my initial post, first few lines. I explained why, specifically: Consolidation.
Thanks I will give it a try later today.
Sent from my SAMSUNG-SGH-I897 using XDA App
- OP updated to reflect stock ownership settings for 'chown'
Also, which sqlite app are you using? I'll put that up as method 3 if it works out nicely for you.
fixed a typo in the chown command.. bad copy paste.. bad.. doh.
added method 3 courtest of ice3186
added links to Root Explorer ($), SQLite Editor ($) and Android Terminal Emulator (free) and added the chmod/chown commands to method 3, as they were skipped by accident.
bump** for newcomers, sry.
thanks max for adding the third method. this was by far much easier than the first two methods. I have a hard time getting my mac to talk to my phone sometimes and it was good to not have to plug the lil guy in at all. Worked like a charm
myself and ice3186 are glad we could be of help
If I had accidentally deleted the settings.db how should I go about recovering my phone? Now I have the issue that my phone won't boot past the boot animation and I'm notbsure what to do
mkslt4 said:
If I had accidentally deleted the settings.db how should I go about recovering my phone? Now I have the issue that my phone won't boot past the boot animation and I'm notbsure what to do
Click to expand...
Click to collapse
Did you make any kind of backup before hand?
You may have to use someone else's settings.db and then do a factory reset.
Depending on how much you've done with the phone I'd suggest deciding on doing a the reboot process for rooting, but choosing to clear data. This may rebuild it, I am not sure.
my dbdata directory is empty.. My phone is less then 2 hours old and i have some market apps installed..
xetrev said:
my dbdata directory is empty.. My phone is less then 2 hours old and i have some market apps installed..
Click to expand...
Click to collapse
Oh, if it's running, then this folder isn't actually empty.
What are you using to browse this folder?
i followed this guide to a T yesterday when i did this. I used option 1, ADB commands on terminal since i'm a mac and it was super easy, did it in about 5 minutes.
this is just my opinion but i think everyone should try playing with the ADB commands, they're actually really useful and educational to know. and if you should brick your phone, just use clockwork recovery to restore it.
that being said, maybe you should add a disclaimer that when done on a mac, the adb commands require a "./" in front (so adb reboot becomes ./adb reboot). cp, chown, and chmod commands don't need it though (or at least i didn't).
Hello, I rooted with unrevoked and then flashed the rom liberated_aria_FR006_signed.
I booted through clockwork and mounted /system /data /sdcard and then connected to my pc via usb, through the command prompt and adb I tried:
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
when I do rm /system/etc/hosts it says:
rm: can't remove '/system/etc/hosts': Directory not empty
What's wrong? Is /system not full perms through clockwork or is it a unrevoked root problem.
Thanks!
G226 said:
Hello, I rooted with unrevoked and then flashed the rom liberated_aria_FR006_signed.
I booted through clockwork and mounted /system /data /sdcard and then connected to my pc via usb, through the command prompt and adb I tried:
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
when I do rm /system/etc/hosts it says:
rm: can't remove '/system/etc/hosts': Directory not empty
What's wrong? Is /system not full perms through clockwork or is it a unrevoked root problem.
Thanks!
Click to expand...
Click to collapse
Lol...the error tells you exactly what's wrong...but kinda weird since the hosts is a file not a directory...so I can only assume that there are some permission issues...navigate to the /system/etc directory and do a "ls -al" and see what the permissions are for the hosts file...it'll be on the left side of the results of the ls.
Sent From My HTC Aria Using XDA App
Oh fyi...I'm dumb...are you already rooted? I dunno much about adb but you MIGHT have to run the above command through a terminal program on your phone...
Sent From My HTC Aria Using XDA App
I'm rooted but it's through unrevoked as mentioned, does that give me the proper permissions if I adb through clockwork recovery?
If not what would? I'll do a "ls -al" in a little.
G226 said:
I'm rooted but it's through unrevoked as mentioned, does that give me the proper permissions if I adb through clockwork recovery?
If not what would? I'll do a "ls -al" in a little.
Click to expand...
Click to collapse
I'm not sure...as I said im not too familiar with adb...I do know if you have a terminal program on your phone just open it, type the following:
su
cd /system/etc
ls -al
Once you so the ls, if you aren't familiar with *nix, you'll see the following:
-rw-r--r-- 1 root root 25 Aug 1 2008 hosts
Along with a bunch of other lines similar to this, this is the line I'd like to see though
Sent From My HTC Aria Using XDA App
Thanks for the help so far, I did what you said and after doing "ls -al" it said :
-al: No such file or directory
If I do a plain "ls" command it'll list all the files/folders in the system dir.
G226 said:
Thanks for the help so far, I did what you said and after doing "ls -al" it said :
-al: No such file or directory
If I do a plain "ls" command it'll list all the files/folders in the system dir.
Click to expand...
Click to collapse
1 are you doing this in adb or terminal?
2 are you typing "ls -al" with a space? And "al" as in alpha lima?
3 are you in the etc directory?
Sent From My HTC Aria Using XDA App
I did as you instructed, used the terminal program app and tried these commands through there, I'll try adb.
Thanks.
Well the only reason I asked was because ls -al is a legit command lol...I dunno of another way to view the permissions of files...I also don't know if there is a way or not through adb, Google may be your friend in regards to that...
Sent From My HTC Aria Using XDA App
This may be related to busybox on the phone. Can you do an "echo $PATH" from the adb shell and paste the results here?
So from the command prompt you would enter "adb shell" this should give you a new prompt like this #. At this prompt type "echo $PATH" without the quotes. Maybe you do not need all these instructions, sorry.
I see this all the time, from all the noobs (myself included)
First off the ARIA still has S-ON security, so if you are writing to /system/ you _NEED_ to be properly booted into recovery - otherwise you will not have write permissions. its in the FAQ but still completely overlooked. There is a post about this every day i swear.
STEP 1) UNPLUG THE USB <----- CRITICAL
STEP 2) POWER DOWN THE PHONE <----- AFTER STEP 1!!!!!!
STEP 3) HOLD VOLUME DOWN + PRESS POWER to load hboot
STEP 4) SELECT recovery to start clockwork
STEP 5) partitions --> mount --> /system/
STEP 6) connect USB
STEP 7) adb shell
edit: if you shortcut into recovery by just leaving the USB plugged in while you power down - you will not have full permissions.
dexmix said:
I see this all the time, from all the noobs (myself included)
First off the ARIA still has S-ON security, so if you are writing to /system/ you _NEED_ to be properly booted into recovery - otherwise you will not have write permissions. its in the FAQ but still completely overlooked. There is a post about this every day i swear.
STEP 1) UNPLUG THE USB <----- CRITICAL
STEP 2) POWER DOWN THE PHONE <----- AFTER STEP 1!!!!!!
STEP 3) HOLD VOLUME DOWN + PRESS POWER to load hboot
STEP 4) SELECT recovery to start clockwork
STEP 5) partitions --> mount --> /system/
STEP 6) connect USB
STEP 7) adb shell
edit: if you shortcut into recovery by just leaving the USB plugged in while you power down - you will not have full permissions.
Click to expand...
Click to collapse
3 sleepless nights later and dexmix comes to the rescue. This drove me crazy man, I just could not find the answer. Thanks!! Bed time!
I'm running a script to modify settings.db (found in the application forum) so that I can wirelessly tether and use the GPS on my phone while running Google Maps on the KF.
The script starts like this:
adb shell rm /data/local/tmp/*
adb push zergRush /data/local/tmp
adb shell chmod 755 /data/local/tmp/zergRush
adb shell ./data/local/tmp/zergRush
Click to expand...
Click to collapse
and works fine.
But I'm having problems running the script that others are having no problem with at this point in the script.
adb pull /data/data/com.android.providers.settings/databases/settings.db
copy settings.db settings.bak
sqlite3 settings.db "update secure set value=1 where name='mock_location';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb reboot
Click to expand...
Click to collapse
The script runs into permission errors. I have all the files in the same directory as adb in the platform-tools folder. adb is communicating with the device with the adb devices command. I run the .bat file from the folder while in a DOS command shell. And I get this error
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb pull /data/data/com.android.providers.settings/databases/settings.db
failed to copy '/data/data/com.android.providers.settings/databases/settings.db' to './settings.db': Permission denied
C:\Program Files (x86)\Android\android-sdk\platform-tools>copy settings.db settings.bak
The system cannot find the file specified.
C:\Program Files (x86)\Android\android-sdk\platform-tools>sqlite3 settings.db "update secure set value=1 where name='mock_location';"
Error: no such table: secure
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
failed to copy 'settings.db' to '/data/data/com.android.providers.settings/databases/settings.db': Permission denied
Click to expand...
Click to collapse
Any idea what's going on?
i assume you'r at the $ prompt - if you type in su the prompt should change to #
perhaps a hint in the right direction ...
zergrush does'nt work anymore since 6.2.1 and burritoroot
I am not at any command prompt when running the script. I'm at the Windows prompt, and I just execute the script name?
Confused.
when you type adb or adb shell your mostly at the $ prompt
when you type su the promt usually changes to # - thats root access
i think you have to integrate that in your script ...
I added
adb shell su
to the start of my script, but then it just hangs at the root prompt.
if you have rooted with burritoroot try "adb root"
It says:
adbd cannot run as root in production builds
ok then i think you will have to try it with the su method - maybe "adb su" could work - it's just a try
otherwise i think you will have to write a second unix stile script (ending .sh) to do the stuff and call it from your dos script or run it in the adn shell - but i'm not the unix expert - sorry
i'm running out of time now - wish you much luck with your script !!!
Anyone else please?
Resolved.….
Resolved how? Very curious
Please, how did you solved the problem ???
thanks
would be interested too !
Here's how.
I was so frustrated, didn't seem to be able to achieve root status and use ADB. So, I bought root explorer, went to directory where settings.db file was, and copied it to sdcard folder on the KF. Then brought it over to my PC just over the USB connection (KF was a Windows drive).
In Windows, ran the part of the script that replaces the "0" with a "1". Then copied it back to the sdcard folder on the device, and used root explorer to move it back to its proper directory.
Only one caution. Make sure that you don't change the permissions or ownerships of the file, that they are the same as when you first grabbed it.
New possible root method on Thinkpad tablet forums, by OPDECIRKEL. He needs help testing it out.
look here and lets cross our fingers =D
http://www.thinkpadtabletforums.com...nt/yareftpt-yet-another-root-exploit-for-tpt/
opdecirkel released the exploit -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/
unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
***EDIT***
updated script worked!
-=HOLLYW00D=- said:
unfortunately, it doesn't work. =( can't execute "adb remount" when the script calls for it, but hopefully things will get ironed out soon.
Click to expand...
Click to collapse
Not sure if it can help you, but try checking the TPT forum thread again, there has been some advances and troubleshooting going on
Moved To General
As the first post is just a link and contains no development, this has no place in this section
updated -> http://opdecirkel.wordpress.com/2012/03/18/yareftpt/
Someone thinkpadtabletforum reported that it worked for him.
updated script worked for me! cwm installed fine as well!
I achieved root with the new method on OTA 2.5. Also installed CWM with no issues. Works great.
Sent from my PC36100 using Tapatalk
I can confirm it worked!
I had to update first because the "Disable Battery Discharge" option was not there. (I guess my Tablet stopped getting OTA updates since I was on ThinkPadTablet_A310_02_0024_0065_US... Also, you have to update one at a time, you can't go from 24_65 straight to 37_75. Also, I stopped at 39_86 since I was impatient.)
I like this once since we can see how it worked rather than blindly running some guys program (I never tried the first root.)
I can also confirm the new method to be working. Just rooted my 0089_WE TPT. Works like a charm
I am quoting the following post (i don't have privilege to post there): forum.xda-developers.com/showpost.php?p=23902281&postcount=64
daswahnsinn said:
I unrooted and then updated, now I can't root. I updated the SDK and made sure I have the proper drivers needed. So I take back my easy comment. I'll keep trying I might just manually push the files back.
Click to expand...
Click to collapse
How did it fail? At which stage and what error did you get?
Okay, I'll try and flash the oldest update zip, and it fails as it should, then I wipe the cache part, reboot, and I hit enter when I gets to the unlock screen then the CMD window closes.
EDIT: I spent a good hour or so combing through my PC and these forums and tried both methods a lot, and this one finally worked. It wouldn't let me get to the /cache/recovery/pwn/su part of the script. Thank you all for your support.
I have problems...
Hi all,
Apologizes for my english, too bad to discuss this kind of issues. Sorry in advance.
I had the "fantastic" idea to update the firmware some weeks ago, when I was SU. After this, I've lost most of capabilities!
I tried to follow the procedure, but I cannot reach 'root' in any case. I have version WE089. Downloaded US060, but there's only 065 for Western Europe. I got both, just in case..
Unfortunately, in the first step it failed I'm not able to update anything. The process crashes when is loading old firmware, either US060 or WE065.
I've realised that during the process I loose the USB link connection (when I reboot), and the system tries to install again and again the driver. If the TPT is running in recovery mode, it seems that is not connected via USB... If I have the tablet in "normal use", I see it through the Windows Desktop.
Other question: should I disconnect the Internet connection?
I guess other requirements are right (ADBD, debugging mode,...). It's really annoying, it took me a lot of hours and I haven't found any solution.
Can anybody help me? What I'm doing wrong?
Cheers!
jm
W7 64bits - TPT WE089
@jm
goto device manager. right click on Android device. reinstall device driver.
This worked for me in recovery when the device was not recognized.
Edit: look here: http://forum.xda-developers.com/showthread.php?t=1471106&page=2
What do you mean with loosing the connection? Is the adb driver installed correctly? Where did you get it from? Is it an genuine lenovo driver? If so, than you shouldn't worry!
Perhabs it's the MTP driver, that is missing when you boot into recovery? If it's the adb driver, than you should try jlove's method.
In addition I wanted to inform you, that the new method worked for me, too! Even with some complications... by this way, thanks again to opdecirkel!
Because the run.bat script did't worked correctly, I had to do it manually. So I put the "yareftpt" on C:\\, started cmd.exe, booted the TPT into recovery and changed the directory in cmd.exe with "cd.." to "cd yareftpt" ...followed the instructions with the update...
echo 4. Reboot in RECOVERY: (shutdown the tablet, then start it and press volume + few times until it starts in recovery)
echo 5. Go to apply update, select the update from the sdcard and try to apply it. It will fail, but that is OK.
echo 5. Then, go to 'WIPE CACHE PARTITION' and select it (navigate with volume buttons and select it with power button),
echo 6. When wipe cache complete, press (here) ^<ENTER^>.
and after that I copied the first line of the script into cmd and executed. I did it line after line, just to the next step. (dark green= copy line after line, paste and execute)
adb shell "/system/bin/mkdir /data/local/pwn"
adb shell "/system/bin/mkdir /data/local/pwn-bak"
adb shell "/system/bin/cat /system/etc/install-recovery.sh > /data/local/pwn-bak/install-recovery.sh.orig"
adb shell "/system/bin/mkdir /cache/recovery/pwn"
adb push su /cache/recovery/pwn
adb shell "/system/bin/rm /cache/recovery/log"
adb shell "/system/bin/ln -s /system/etc/install-recovery.sh /cache/recovery/log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/mount -oremount,rw -t ext4 /dev/block/mmcblk0p4 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 777 /cache/recovery\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chown root /cache/recovery/pwn/su\" >> /tmp/recovery.log"
adb shell "echo \"/system/bin/chmod 4777 /cache/recovery/pwn/su\" >> /tmp/recovery.log"
echo 7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete press (here) ^<ENTER^>
pause
some of commands might cause failures, but don't worry and just go on
adb shell "/system/bin/rm /cache/recovery/log"
echo 8. On the device, select REBOOT. When startup COMPLETE press (here) ^<ENTER^>
pause
adb push Superuser.apk /data/local/pwn/Superuser.apk
adb push busybox /data/local/pwn/busybox
adb push su /data/local/pwn/su
adb push pwn-in.sh /data/local/pwn/pwn-in.sh
adb shell "/system/bin/chmod 777 /data/local/pwn/pwn-in.sh"
echo Your PC command prompt appears next. Do the following things:
echo 1. adb shell
echo when '$' (adb shell) appear, do:
echo 2. /cache/recovery/pwn/su
echo when '#' appears. You are root. run the following:
echo 3. /data/local/pwn/pwn-in.sh
now you should try if you have su, even if you don't see in your app list..
download root checker, install, open and try it!
You should have root right now.
In my case, i had root, but no CWM!
So I had to install in manually, but with root it should't be a problem. you only have to download the correct cwm version:
http://forum.xda-developers.com/showpost.php?p=21916505&postcount=71
then I installed it with the Android Terminal Emulator app, because the cmd.exe method did't worked for me. You should just follow the instructions:
or you can copy img file on /data/local/ folder of your tablet (with a file manager with root permissions)
launch "Android Terminal Emulator" application
and tape the instructions
su
mount -o rw,remount /system
echo "#!/system/bin/sh" > /system/etc/install-recovery.sh
dd if=/data/local/NameOfCWMFile.img of=/dev/block/mmcblk0p1
http://www.thinkpadtabletforums.com...nd-development/clockworkmod-recovery-for-tpt/
After a shutdown and reboot into recovery I had cwm! So I am able to do nandroid backups...
In this way, I would particularly like to thank to all devs that made the TPT root possible! Now i like my TPT 1000% more than before...e.g. no status-bar in lecture notes -> sooo great!!
I do get the following error maybe someone can help me out
[*]
[*]
[*]
/system/bin/mkdir: not found
/system/bin/mkdir: not found
cannot create /data/local/pwn-bak/install-recovery.sh.orig: directory nonexisten
t
/system/bin/mkdir: not found
699 KB/s (22364 bytes in 0.031s)
/system/bin/rm: not found
/system/bin/ln: not found
7. On the device, go to 'DISABLE BATTERY DISCHARGE' and select it. When complete
press (here) <ENTER>
Drücken Sie eine beliebige Taste . . .
it cant find the mkdir command very strange
I'm a little rusty, but are the / and \ facing the correct way? And are you in the correct directory? Not found usually means path is incorrect.
@rangercaptain
thats the commands from the root script. I didnt change them.
the commands are send over from adb shell and the tablet is in root directory i think.
When i go into shell and type in ls i get access denied error.
and you load the update zip and wiped cache before typing the commands, right? You have to do this every time you try to root...
Try to do it with another method. Don't do it directly trough adb shell...just type the shell commands in the cmd.exe
You just have to chance the directory in cmd, before executing the commands.
Then try not to input 'adb shell' before the shortened command, but the whole command as one line like:
adb shell "/system/bin/mkdir /data/local/pwn"
Perhabs it will work..?!?
@neos
yes i do the same procedure.
I also tried over cmd with adb shell "command" and also in shell.
Always the same error.
I looked into the system/bin directory and mkdir does have filesize of 0kb...
It took some doing, but after following the instructions in this link:
http://forum.xda-developers.com/showthread.php?t=2559915
I was finally able to root my Nook Glowlight. The instructions are kind of sprawled out and extremely unclear so I will sum up.
As always, you will need the ADB. In order to install the ADB, you need the Java Development Kit and the Android Studio (formerly known as the Android SDK)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
http://developer.android.com/sdk/installing/studio.html
How to obtain root via ADB: The ONLY way you can root is using Windows. I was successful on Windows 7 32 bit, but it may be possible on other versions.
step 1) install bootloader driver.
You need to grab the drivers from here (bnusbdrivers.zip):
http://forum.xda-developers.com/showpost.php?p=49665945&postcount=279&nocache=1&z=184593200683593
then, open the Device Manager (on Windows). Be ready to right click on the new device 'omap3660' that shows.
With the nook turned completely off, plug in a USB cable. you will have less than 3 seconds to right click the new omap3660 device that shows up in the system profiler.
If you were successful and you right clicked on it in time, manually install the Barnes & Noble USB driver (there are entries added to the generic Google drivers for both the TI Omap 3660 bootloader and the ADB device after you modify the uRamdisk later on)
***NOTE***
If you WEREN'T successful on your first try (took me THREE times to get to it in time), you aren't going to get another chance to install the drivers. At least not easily anyway, because after Windows tries to automatically install the drivers for the bootloader and fails, it will disregard the device any time it shows up after that. So, you are going to need to delete the registry entries that it created, which in my experience was easier said than done. Even admin access was not sufficient to make the necessary changes to the registry.
You will need to launch regedit.exe using another tool called psexec which is available here:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
after you download the pstools package, copy those .exe files to C:\Windows\System32\ (in order to add them to $PATH in cmd.exe)
Then, once you've installed the pstools commands to C:\Windows\System32\, run cmd.exe as admin (right click it and select 'run as administrator') and then open regedit.exe with the following command
Code:
psexec -s -i -d regedit.exe
Then, once regedit is open you need to find the keys created by the Nook bootloader and delete them. The Nook bootloader's device ID is 0451:d00e
You are going to be looking in HKEY_LOCAL_MACHINE\Current Control Set\enum\usb\ for the keys with the bootloader's device IDs. There may also be keys generated in control set 001 and 002 as well. Delete all of those keys and then reboot your computer. Then with the nook power off completely, repeat the process from the first step. eventually you will be successful installing the bootloader driver.
Step 2) temporarily boot with uRamdisk-noogie
you need to download omaplink.exe from here:
http://www.temblast.com/android.htm
and you also need to download the four files which allow you to temporarily mount the boot partition; omap3_aboot.bin, u-boot-ng2-exp-v03.bin, uImage-ng2-130-stk and uRamdisk-noogie.
They are available here:
http://forum.xda-developers.com/showpost.php?p=49779966&postcount=285
download usbboot-ng2-images-noogie-v1.zip
The next part is easy.
Extract the .zip file and then fire up cmd.exe. cd into the directory of the newly extracted .zip
in the new working directory, enter the command
Code:
omaplink omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-stk uRamdisk-noogie
Then, with the Nook powered all the way off and omaplink running, plug it in and a few seconds later, after the device boots up all the way, you will be looking at the contents of the boot partition instead of the internal storage like normal.
Step 3) Edit uRamdisk
you will need to download bootutil.exe from here
http://www.temblast.com/android.htm
copy bootutil.exe to C:\Windows\System32
with the boot partition mounted, copy uRamdisk to your computer and extract the files init.rc and default.prop, eg;
Code:
bootutil /x /v uRamdisk init.rc default.prop
then using notepad++ (available here: http://notepad-plus-plus.org/) edit the files as follows
default.prop
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
and
init.rc
comment out lines 375 and 392-399
(do this by adding a # to the beginning of the line)
uncomment line 215
(do this by deleting the # at the beginning of the line)
save both files and then repack them into uRamdisk
Code:
bootutil /r /v uRamdisk init.rc default.prop
copy uRamdisk back onto the Nook, eject the disk and power off the device. Reboot and you should be able to connect to ADB via WiFi
eg;
Code:
adb connect 192.168.0.10
replacing '10' with whatever IP your Nook is grabbing from your router.
Step 4) Full Root
at this point, you have root access via ADB only. You will not have root access in any apps like Root Explorer, Terminal, TiBackup, etc.
In order to finish PROPERLY rooting your Nook, you need to install 'su' to /system/bin/ and install the superuser.apk
Code:
adb connect 192.168.0.10
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
reboot your device one more time and then you will be fully rooted.
*** Note ***
this devices firmware seems to be a strange hybrid between donut and eclair, although it purports itself to be Android 2.1. The Superuser.apk and su binary came from an old Cyanogenmod 4.6 build in case anyone was wondering (Android Donut). The ones from Cyanogenmod 5 (Android Eclair) do not work. you will get the 'install failed older sdk' error.
installing busybox
I tired installing busybox by using the stericson busybox pro.apk. It would always freeze at 6.47%.
I figured out that if I grabbed an older version of the busybox binary and pushed it to /system/xbin manually and then chmodded it to the proper permissions, auto updates and proper symlinking work using the busybox app
Code:
adb shell mount -o remount, rw /system
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Then reboot, and run the busybox app to update and create symlinks.
enjoy!
installing nano and bash
Code:
adb connect 192.168.0.10
adb shell
mount -o remount, rw /system
adb push nano /system/xbin/
chmod 6755 /system/xbin/nano
adb push bash /system/xbin/
chmod 6755 /system/xbin/bash
bash
mv /system/bin/sh /system/bin/sh.bak
ln -s /system/xbin/bash /system/bin/sh
chmod 6755 /system/bin/sh
adb push profile /system/etc/
adb push terminfo /system/etc/
and then in terminal emulator under 'Preferences' change the initial command to
Code:
export TERMINFO=/system/etc/terminfo;export TERM=linux;export HOME=/sdcard;
and finally
Code:
adb push bashrc /sdcard
adb shell
mv /sdcard/bashrc /sdcard/.bashrc
exit
nano works just fine via ADB, but because of lack of 'ctrl' key (and physical buttons to assign it to) you won't be able to write files (ctrl+o) using the terminal on your nook. But between having full proper root access, busybox, a proper bash terminal emulator and nano for editing config files, this should REALLY extend the usefulness of your Nook Glowlight. It should work just fine on other versions of Nook too.
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
As far as remounting /system as ro, I would HIGHLY recommend just rebooting at this point, otherwise your nook might be stuck in a weird pseudo-rooted state. Probably won't cause any problems, but why risk it?
Thanks for clarifying the line number. I will make the appropriate edits to my instructions. I was working off the top of my head and couldn't remember what exact line the ADB over TCP config was, as I just used ctrl+w '5555' to find it myself.
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
darz said:
Hi N00b-un-2,
Many thanks for your summary!
There is one important edit that I think you missed,
in init.rc you also need to:
Line #375, comment out "disabled" with a # at the start of the line.
(see http://forum.xda-developers.com/showthread.php?p=49070213#post49070213)
without this I couldn't get adb to connect.
And since you already made it very noob friendly, might I suggested you clarify:
Line #215 remove # to enable adb over wifi
(rather than search for 5555)
Also, I'm not expert, but I believe the commands to get superuser on the device are (at least it worked for me):
adb connect 192.168.x.x
adb shell mount -o remount, rw /system
adb push su /system/bin/
adb shell chmod 6755 /system/bin/su
adb install superuser.apk
Finally, I'm not sure if this is important, but maybe remount system as read only again:
adb shell mount -o remount, ro /system
Thanks again, nice work!
---------- Post added at 01:48 PM ---------- Previous post was at 01:10 PM ----------
Hi again,
had similar issues with installing busybox, here's what worked for me (note needed to run su to create dir):
adb shell mount -o remount, rw /system
adb shell /system/bin/su
adb shell mkdir -p /system/xbin
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
cheers.
Click to expand...
Click to collapse
N00b-un-2 said:
There are several pre-edited uRamdisk images floating around the forum with various features enabled which would be easier for noobs than extracting the config files and manually editing and then repacking them. In the future I'll probably throw those on here as well.
Click to expand...
Click to collapse
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
darz said:
Would have been good if I could have easily found a pre-edited image, but your instructions were a great alternative, thanks again
Click to expand...
Click to collapse
Sorry for the really noob question, I have rooted, wifi adb running and installed apps as per your instructions, but I can't seem to access any of it on the nook. How can I get access to the launcher I installed?
You mentioned pre-edited images, do any of those come with the apps I need to get access to a custom launcher?
Cheers,
Dariusz
==============
Updated: All sorted
==============
For some reason had some issues with ADW launcher, Launcher pro worked fine.
ps I think I made a mistake with the su step I suggested, if you run a one line shell command I don't think it keeps su privileges, so I believe you need to run commands within the shell as per below:
adb shell
mount -o remount, rw /system
/system/bin/su
mkdir -p /system/xbin
exit
adb push busybox /system/xbin
adb shell chmod 6755 /system/xbin/busybox
adb install busybox.apk
Noob
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
The above instructions from N00b-un-2 should work fine running a vm with parallels on your Mac.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
valentin1985 said:
Hey guys any instructions noob friendly or a video in youtube,i stick up at dab connect 192.168.0.10.I dos't have a Windows PC and using Mac whit Parallels Desktop.Is it possible instructions for Mac?
Click to expand...
Click to collapse
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
darz said:
Before you perform the adb connect step you need to find out what your IP address is:
On your nook, click on the settings icon in the top right corner and then select "Change"
Under Wireless Networks, select the wifi name that you are already connected to (where it says "Connected to the internet")
This will display your connection details, remember that IP address
Now go back to your pc and type:
adb connect [IP address]
Click to expand...
Click to collapse
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
thenookieforlife3 said:
BIG HINT! If you're using Powershell ISE, you have to type .\adb.exe connect [IP address] or else it won't recognize "adb" as an executable!
Don't ask why, because I don't know. :?
Click to expand...
Click to collapse
So far so good,but now what?
valentin1985 said:
So far so good,but now what?
Click to expand...
Click to collapse
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
thenookieforlife3 said:
I just gave a little tip on Powershell ISE. I do not know much about the Nook GlowLight rooting process, as I have a NSTG, not a NG. Ask someone else.
Click to expand...
Click to collapse
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
valentin1985 said:
Yes,i try whit dis command .\adb.exe connect 192.168.0.9 but result is the same.
Click to expand...
Click to collapse
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
thenookieforlife3 said:
But that's okay! What I said was, if you are using the command program Powershell ISE, do it that way instead. But you are just using cmd.exe, not Powershell ISE!
In cmd.exe, which is what you are using, it is not neccessary to type .\adb.exe. Just type adb.
From there, ask someone else in this thread.
Click to expand...
Click to collapse
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
N00b-un-2 said:
I prefer to use ConEmu or Console2 when I am forced to use Windows. Not a big fan of CMD.EXE or Powershell/PowershellISE. there are plenty of other CLI alternatives out there
Click to expand...
Click to collapse
Well, as I ONLY use Windows and Powershell ISE has a nice-enough layout for my purposes, I use it. That's why I gave a tip on it.
Actually on a lot of installs just typing adb in the command console won't work either unless it's got the path variable set up correctly, I find it easiest to just right click and choose run as administrator, no need for the path to be setup.
OB
Sent from my SPH-D710VMUB using Tapatalk 2
FW 1.2.1
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
real-6 said:
Hi guys,
thanks for creating this thread. I was wondering if this rooting procedure was tested with the firmware 1.2.1 ?
Click to expand...
Click to collapse
This rooting procedure is for the new Nook GlowLight with firmware 1.3.1. Your device is a Nook Simple Touch with GlowLight, which can be rooted very easily using the rooting package here.