Related
(Sorry for not posting actual links - the system won't let me because I'm still a "new user.")
I already rooted my Sprint Hero using this (thread 583291) guide and can successfully tether using the WiFi Tether app. Yay!
Now I want to delete and/or replace the boot up sound (boot.mp3 located in /system/media/bootscreen) When I try to delete it right now (either through adb shell on my computer or from within a file manager app on the phone itself) I get permission denied or "read-only file system."
I see two threads regarding busybox, superuser, and adb remount. Thread 591303 which is dated 11/28/09 and is just for busybox and Thread 593952 which is dated 12/03/09.
I'm not sure which of these two I need to install. If it's the latter which includes ADB remount and superuser as well as busybox, then I'm not sure if I am supposed to unzip them before pushing them to my phone.
Could anyone point me in the right direction based on what I want to do (delete files on my phone - ANY file I want)?
Thanks in advance for any help you can offer.
All you should need to do is:
Code:
adb remount
rm /insert file path/file
So yours would be
Code:
rm /system/media/bootscreen/boot.mp3
Mr. Biggz said:
All you should need to do is:
Code:
adb remount
rm /insert file path/file
So yours would be
Code:
rm /system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
will rm work without busybox?
As long as you can shell into the phone it should work. The rm command is to be run inside the shell.
So it actually should be
Code:
adb remount
adb shell
rm /system/media/bootscreen/boot.mp3
You want to install the busybox remount and superuser Rom if you want to run stock.
Or manually install busybox, superuser whitelist and adb remount
Biggz - looks like they are on stock. No adb remount.
gbhil said:
Biggz - looks like they are on stock. No adb remount.
Click to expand...
Click to collapse
Unfortunate, custom is so much better.
If you are on stock, do this:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mv /system/media/bootscreen/boot.mp3 /system/media/bootscreen/boot.mp3.old
exit
[you can also do rm /system/media/bootscreen/boot.mp3 instead]
gbhil said:
You want to install the busybox remount and superuser Rom if you want to run stock.
Or manually install busybox, superuser whitelist and adb remount
Biggz - looks like they are on stock. No adb remount.
Click to expand...
Click to collapse
successfully removed (rm) the boot.mp3 in the shell - Thank you for that. I do want to replace it with a different one (I'll use the same file name since the .xml file still refers to it) so I'll need the cp command and I've noticed that it's missing in shell. I'm assuming I need to install busybox to get this functionality. I'm not really sure I want to install a complete new ROM and I don't mind manually installing busybox, adb remount, etc. What does installing "superuser whitelist" and "adb remount" allow me to do? I'm not sure what their potential uses are?
I installed busybox and have the cp command functionality now (see above post) but now when I try to copy anything to the /system/media/bootscreen folder I get "cp: cannot create '/system/media/bootscreen/boot.mp3': Permission denied"
I type "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" after getting into shell and typing "su" and getting the "#" prompt and it takes successfully (this is the only way I was able to actually "rm" the original boot.mp3 file to begin with.
See anything I'm doing wrong?
Nope, that is correct.
/system is normally mounted as read-only, so you can't add or delete anything. The mount command remounts it as read-write, so you can modify it as root.
armyturtle said:
<snip> I'm not really sure I want to install a complete new ROM and I don't mind manually installing busybox, adb remount, etc. What does installing "superuser whitelist" and "adb remount" allow me to do? I'm not sure what their potential uses are?
Click to expand...
Click to collapse
Superuser whitelist is an application that warns you and asks for you to provide permission whenever an app tries to use the su binary to run as another user. You want this, as without it there's no way to know if an application runs as root.
Adb remount is a service that allows you to toggle the +RW bit on the /system/ partition through the shell. IIRC the one one floating around also kills color terminfo so you don't get all the extra chars on a windows PC when using the ls command. Just a matter of convenience.
jonnythan said:
Nope, that is correct.
/system is normally mounted as read-only, so you can't add or delete anything. The mount command remounts it as read-write, so you can modify it as root.
Click to expand...
Click to collapse
I can't create/copy anything after getting into the shell and remounting as read-write. From CMD prompt I type:
adb shell
and get:
$
Then I type:
su
and get:
#
This is where I type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Then trying to copy anything into the /system directory gives me:
Permission denied
It will let me DELETE anything I want from this folder (as confirmed by now deleting boot.gif just to check) but it won't let me cp (copy) anything to this folder. WHY?
What the heck?
try these commands for the boot mp3
Code:
cd/
cd /androidsdk/tools/
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
adb push directoryonpcwhereyourbootmp3is /system/media/bootscreen/
make sure that you rename the mp3 to boot.mp3 or it wont work anyways.
the other option (this is what I do) is find a bootscreen that you like (I use this one). open the zip file useing winrar or 7zip, navigate into the files where you see the boot.mp3 and drag in YOUR (now renamed) boot.mp3 close the window, put the zip file onto the root of your sd card, boot into recovery, choose flash from zip, flash the file and your good to go.
wtphoto said:
try these commands for the boot mp3
Code:
cd/
cd /androidsdk/tools/
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
exit
adb push directoryonpcwhereyourbootmp3is /system/media/bootscreen/
make sure that you rename the mp3 to boot.mp3 or it wont work anyways.
the other option (this is what I do) is find a bootscreen that you like (I use this one). open the zip file useing winrar or 7zip, navigate into the files where you see the boot.mp3 and drag in YOUR (now renamed) boot.mp3 close the window, put the zip file onto the root of your sd card, boot into recovery, choose flash from zip, flash the file and your good to go.
Click to expand...
Click to collapse
tried this just now and still get "failed to copy 'C:\android-sdk-windows\tools\boot.mp3' to '/system/media/bootscreen/boot.mp3': Permission denied"
It's the /system folder... I can push to /data/local all day long, but anything in the /system folder is read only. How the hell can I change this?
/system/media/bootscreen/boot.mp3
Click to expand...
Click to collapse
if this is the code you are using then that could be your issue
the code line should look like this
Code:
adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/
doing adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/boot.mp3 says that you are trying to push the boot.mp3 to the directory bott.mp3 and there is no boot.mp3 directory the folder where you want the boot.mp3 is bootscreen. try the ubove code and see what happenes.
wtphoto said:
if this is the code you are using then that could be your issue
the code line should look like this
Code:
adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/
doing adb push C:\android-sdk-windows\tools\boot.mp3 /system/media/bootscreen/boot.mp3 says that you are trying to push the boot.mp3 to the directory bott.mp3 and there is no boot.mp3 directory the folder where you want the boot.mp3 is bootscreen. try the ubove code and see what happenes.
Click to expand...
Click to collapse
Nope, was a typo on my part (here in the post, not when issuing the command). Still permission denied. I don't think it's actually mounting the /system folder as writable. Is there a way to check after issuing the remount command?
A quick command of "ls -l" at root prompt gives the following for the /system folder:
drwxr-xr-x root root 2009-09-21 06:30 system
after you run the remount command what does it say? does it say remount succeded?
After typing the remount command it simply repeats my command back at me and returns to the "#" prompt.
honestly at this point what I would try doing is do a back up then flash a custom rom like fresh 1.1 that has all the tools built into it. then go into the cmd prompt and cd to where sdk is then type adb remount and see what it says then adb shell and try to cp the file to that directory.
this is more a test than anything else.
wtphoto said:
honestly at this point what I would try doing is do a back up then flash a custom rom like fresh 1.1 that has all the tools built into it. then go into the cmd prompt and cd to where sdk is then type adb remount and see what it says then adb shell and try to cp the file to that directory.
this is more a test than anything else.
Click to expand...
Click to collapse
I'll try this - so you recommend trying fresh 1.1 then? I know it's just a test, but just in case I like the ROM and decide to stick with it, might as well try a really good one! I'll try this tomorrow - I'm beat! (Thanks again!)
One thing that I really love about Android, is the Gnu/Linux system running in the background. I use Linux on all my regular machines where I do most work via my beloved terminal.
Playing in CLI on Android Phones is just as much fun only Android is missing a lot of the toys I'm used to. So I'm making a collection of some of these tools, some found on the Web and some Home made.
Here if the first collection of the things I've collected so far.
Most of it can be found in different places on the Web, but I find it a lot easier to just get it in one place.
http://dl.dropbox.com/u/14234754/XDA_GLOBAL/android_cli_extras.tar.gz
This small Archive contains the fallowing:
Bash 4.1 - This shell is made to become the default shell on your phone regardless if you connect via SSH or local terminal. Also added an bashrc file.
SSH Shell Client
Remount script - Makes it easier to optain RW on /system (HTC Users will need S-Off)
Nano Editor with terminfo not defined, fix
Init Script to set a user defined hostname and update the hosts file
Now, I don't remember where everything comes from. I believe that the Nano Editor is from the MoDaCo Forum (The terminfo fix is placed in the /system/bin/sh script). The Remount Script is from somewhere on this forum. Bash, I don't remember. SSH Client is from the Better Terminal APK (Perhaps an SFTP client would be nice to). The rest is just some small home made shell scripts.
The Hostname can be changed in /system/etc/init.d/05userinit (Make sure that your current ROM does not already has init scripts to alter hostname. Some custom ROMs do)
The bashrc file is placed in /system/etc/bashrc
This location can be changed in /system/bin/sh
The remount script makes it faster and easier to option RW on /system.
Just type "remount rw" in the shell to switch to Read/Write and then "remount ro" to switch back to Read-only. HTC Users needs S-Off in order to write to /system.
In order to copy the files to the /system partition, you need to option Read/Write without the remount script. In the Shell type "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system". (HTC Users without S-Off will need to do this using ADB in recovery)
If you use the Better Terminal APK for Android, you need to go to settings and make sure that it uses Android Terminal. Otherwise it will use it's own bash which only works when in Better Terminal and also it's full of errors. Also in the option "Command Line" it should be "/system/bin/sh". Make sure that there is NO - at the end, example "/system/bin/sh - ". You might need to remove it twice before it is gone.
(Just in case anyone should wonder. Yes your phone needs to be rooted)
Also if anyone has more fun CLI stuff for android then please bring it
Evening all,
I am getting very frustrated with my DroidX, since I cannot seem to get it rooted. I believe the crux of my problem lies in that I cannot seem to keep USB Debugging active, even though its enabled. It seems to show up once in awhile, and then just disappears. This does not allow rooters like Z4 to do its job.
I was running the Moto version 5 USB drivers, but backed down to the 4.9 USB drivers and still no luck. Has anyone run into this and can you guide me in rectifying this?
Thanks,
Steve
stevefxp said:
Evening all,
I am getting very frustrated with my DroidX, since I cannot seem to get it rooted. I believe the crux of my problem lies in that I cannot seem to keep USB Debugging active, even though its enabled. It seems to show up once in awhile, and then just disappears. This does not allow rooters like Z4 to do its job.
I was running the Moto version 5 USB drivers, but backed down to the 4.9 USB drivers and still no luck. Has anyone run into this and can you guide me in rectifying this?
Thanks,
Steve
Click to expand...
Click to collapse
what version of Android you have?
I am running VZW stock 2.2.1 but the problem seems to lie in the fact I cannot keep USB debugging on, even though it is enabled on the phone.
Has anyone seen this?
Root your phone without your computer - This would be the path someone on a Mac could take or someone without access to a computer.
This works for the DX and D2 phone, won't work for the D1
Visit the market and get the free Android Terminal Emulator installed.
Visit the market and make sure you have Astro installed.
Grab rageagainsthecage.zip with your phone http://www.droidforums.net/forum/at...s-root-them-unroot-them-rageagainsthecage.zip
Use Astro to navigate to the /sdcard/download folder
Long press on the rageagainstthecage.zip file and "extract to this directory"
The 4 files, from the zip file should now be in the /sdcard/download folder (rageagainstthecage-arm5.bin, su, superuser.apk and busybox.
What are we going to do?
Steps 1- 5: Change to the /tmp folder on your phone, copy the file to the tmp directory, change its permissions. run it, and wait.
Step 6: make sure we can proceed
Steps 7 - 14: make system read-writable, copy the superuser. su and busybox files to where they need to go, use chmode to change their permissions, then make the system folder read-only, and exit Terminal Emulator.
If you want to know more about the commands being used here: cd, cp, chmod, mount, and exit are all Linux commands you can look up on your favorite search engine.
Okay, let's do it - type the blue parts in Terminal Emulator
cd /tmp
cp /sdcard/download/rage*.bin /tmp/
chmod 777 rage*.bin
./rage*.bin
This will take some time, just wait for the $ to show up so you know it is done.
Go to Settings > Applications > Manage Applications > Terminal Emulator > and Force Stop the application
Sanity check - Go into Terminal Emulator again and make sure you have a # symbol as a prompt. If so you are ready to proceed.
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/download/Superuser.apk /system/app/Superuser.apk
cp /sdcard/download/su /system/bin/su
cp /sdcard/download/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
exit
For USB debugging, it might be your usb connection type. Try changing it to computer, mass storage, etc, until you find what's stable. I used Z4root when I did mine. Took like 2 minutes, and no computer, no terminal commands, true one-click root. Don't have the APK anymore, since I've moved on to the Bolt, sorry. But a google search should pull it up.
Thanks to all. I am now rooted. Woo hoo!
If you are having trouble getting read/write access, try the following code in either Terminal Emulator on the device or through 'adb shell' from your computer:
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
That has worked for me without fail on multiple Android devices (Hero CDMA, NS4G, Sprint Galaxy Tab w HC, Samsung Moment). Obviously, you need to have Busybox/Superuser installed.
This is useful for removing stubborn, factory-installed applications (Sprint, I'm looking at you!). However, you need to type this every time you want get read/write access which can be very hard using Terminal Emulator and tiny soft keyboards on the device. One way around it is creating a simple shell script. One example is below. I named mine 'readwrite' but you are free to name it whatever you want.
Disclaimer: I am not responsible if this screws your phone up, blows your phone up, or makes your phone hate you. It usually is pretty safe but still proceed with caution and type commands exactly as shown. Your mileage may vary.
Code:
su
cd /system
cat > readwrite
#! /system/bin/sh
echo -n "Mounting file system as read/write"
mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
echo -n "Finished mounting system as read/write"
exit
Press <ctrl><d> when done. Usually, <ctrl> is Vol-Dn button on most devices. Check 'Special Keys' section within Terminal Emulator to be sure.
Now time to make the script executable. Type in
Code:
chmod a+rwx readwrite
To double check that readwrite is executable, type in
Code:
ls -al
The the first column of the row containing readwrite should read "-rwxrwxrwx"
Now, to get read/write access anytime you wish on the go, just type in the following in Terminal Emulator:
Code:
su
cd /system
sh readwrite
That should do it
PS: If you have Root Explorer, by all means use that. My understanding is that the application is not free. This tutorial is for cheapstakes like me
This isn't easy, this is pretty difficult for the noobs.
An easy way would be to download 'mount /system rw/ro' from the market, enable it to run after boot, mount rw and grant it su access. Now that's simple.
Sent from my GT-P1000 using XDA Premium App
I agree this is not the easiest way to do it but is just another option. I for one hate installing applications if I can get the job done myself
GANJDROID said:
This isn't easy, this is pretty difficult for the noobs.
An easy way would be to download 'mount /system rw/ro' from the market, enable it to run after boot, mount rw and grant it su access. Now that's simple.
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
manfa said:
I agree this is not the easiest way to do it but is just another option. I for one hate installing applications if I can get the job done myself
Click to expand...
Click to collapse
heheheh....so why use windows when you can use DOS?
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.