Hi,
After reading this thread and learning that you CAN replace HTC's apps with stock Android ones, I have started messing around to see what other apps I can / should change. I'll use this thread as kind of a log, so if I mess things up I can come back and see where I went wrong. Fellow noobs can surely use it too!
I am using SDK in Ubuntu, but the procedure should be pretty similar in Windows.
First, follow the Unlockr's method to root your phone.
Download a stock Android rom and extract its /system/apps folder inside /sdk/tools. I named the folder "Apps-stock
Check if Ubuntu recognises your phone:
Code:
./fastboot devices
Load the recovery image and mount the system:
Code:
./fastboot boot cm-hero-recovery.img
./adb shell mount /system
Replacing HTC's calendar:
Code:
./adb shell rm /system/app/Calendar.apk
./adb shell rm /system/app/Calendar.odex
./adb push Apps-stock/Calendar.apk /system/app/
I'll edit the thread, add details as I go on
Nice one!
Please keep us informed!
Thanks for this thread.
Post moved to a more appropriate topic :
http://forum.xda-developers.com/showthread.php?p=4477971#post4477971
Thanks for setting this thread up!
Firstly, you should probably say in the first post that everyone should do a Nandroid backup first - it's saved my bacon. Might be an idea to link to the files, too?
Second, I've got a problem trying to run this method. I removed the original calendar.apk and .odex without any problems, and copied the new one over, but on rebooting, it wasn't in the list of applications anywhere. I browsed there in Astro and opened the file, which gave me an option to install it - which then gave an error of "Calendar could not be installed on this device".
I'm running the MoDaCo 2.1 custom ROM and using the calendar.apk from this thread.
Thanks for your time!
fastboot
can you tell me where this fastboot command is located? I am using Ubuntu too, but can not find fastboot. What is it for by the way?
dragonflyFZX said:
can you tell me where this fastboot command is located? I am using Ubuntu too, but can not find fastboot. What is it for by the way?
Click to expand...
Click to collapse
fastboot and adb are executables you get from the Android SDK - see here.
This thread does require your phone to be rooted, though, which would require you to have already used adb at least once....
frandavid100 said:
........
Replacing HTC's calendar:
Code:
./adb shell rm /system/app/Calendar.apk
./adb shell rm /system/app/Calendar.odex
./adb push Apps-stock/Calendar.apk /system/app/
I'll edit the thread, add details as I go on
Click to expand...
Click to collapse
how about simply replacing those files using a file explorer (like linda)? possible, or would that screw up my system?
Hi I have been trying all evening to remove com.wsandroid.apk from my phone, using terminal but I simply cannot. I've tried many different commands and I'm just being told either permission denied, directory not found/not empty. I have a Wildfire which is obviously rooted. Please help me out, tearing my hair out here.
So you're using modaco custom rom?
Download the latest version of HTC Sync and install. This will also install the adb drivers. (I presume you use windows, if not, I apologise)
Download the Android SDK
Put the phone in fastboot mode (Power+Volume down) and plug it into your computer.
When the drivers are installed, use the command prompt to navigate to the tools folder within the android sdk folder.
Type the following commands, pressing enter at the end of each line:
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
cd app
rm -r com.wsandroid.apk
That should do it
I'm using the stock ROM but it is rooted with Unrevoked. I'll try these instructions anyway.
- Connect your phone to the PC
- Clear WaveScure's cache on the phone
- Open a command prompt
- go to run go to C:\androidSDK\tools and then run these 2 commands
1. adb remount
2. adb shell rm /system/app/*wsandroid*
Click to expand...
Click to collapse
I'm trying these settings, but when I get to adb remount, I get this error: remount failed: Operation not permitted
EDIT: I put the phone into recovery mode and mounted it and it said remount succeeded, I then followed step 2. both *wsandroid* and com.wsandroid.apk and it says that they cannot be found.
EDIT: Nevermind, deleted it
There's currently no write access to system partition using Unrevoked on Wildfire. So you can't remove it. You flashed it with update.zip? I'm not an expert (yet) but I assume the only way (or easiest way) to remove it is to flash your stock ROM again.
To start off I want to say, I am NOT claiming to have created this exploit, I am merely letting people know that it works on the arc.
All credit for this goes to Chainfire and The Android Exploid Crew
The origional thread is here: http://forum.xda-developers.com/showthread.php?t=1044765
Download here
Install the APK and run it.
For people getting "could not extract assets" error execute
adb shell rmdir /data/local/tmp
and then
adb shell mkdir /data/local/tmp
Click to expand...
Click to collapse
Quote posted by jassired
works for me
So just push the apk to the phone, install and you're done?
no need to "push", just stick it on your sd card and install
diggedy said:
no need to "push", just stick it on your sd card and install
Click to expand...
Click to collapse
I get the error thing...and I can't find the effing map where I need to remove stuff....
where do I find the god damned map to remove the files I need to remove when it only fails to install?????
I've checked every single map on the memory card, going nuts here...
Cim_XII said:
where do I find the god damned map to remove the files I need to remove when it only fails to install?????
I've checked every single map on the memory card, going nuts here...
Click to expand...
Click to collapse
What do you mean?
double post :s will use this later
I have put the .apk in my download map on the sd card of the phone, installed the apk and run it and I get the: "could not extract assets" error execute
and then when I get that I am supposed to remove some files from a map on the sd card, and I cannot find said map....I hava rebooted the phone, and I still cannot find data/local/tmp or what ever map I need to find.....
Cim_XII said:
I have put the .apk in my download map on the sd card of the phone, installed the apk and run it and I get the: "could not extract assets" error execute
and then when I get that I am supposed to remove some files from a map on the sd card, and I cannot find said map....I hava rebooted the phone, and I still cannot find data/local/tmp or what ever map I need to find.....
Click to expand...
Click to collapse
you need to execute the commands in the origional post via ADB with USB debugging enabled, because the location is in the system and ironicly you dont have the root privelages to delete them
I don't even know what ADB is....that's how much I know...
Cim_XII said:
I don't even know what ADB is....that's how much I know...
Click to expand...
Click to collapse
I have attached it to this post. ADB is the Android Debug Bridge. It is used to excecute commands on android devices. Just extract the zip, then open a command prompt and change to the directory of ADB, then excecute the commands.
if you get the error for esset you need to remove all the files inside to /data/local/tmp/
press: adb shell
press ls /data/local/tmp
and remove one by one the files as my example:
$ ls /data/local/tmp/
ls /data/local/tmp/
Superuser.apk
Gingerbreak
runscript
sysrun
$ rm /data/local/tmp/Superuser.apk
rm /data/local/tmp/Superuser.apk
$ rm /data/local/tmp/Gingerbreak
rm /data/local/tmp/Gingerbreak
$ rm /data/local/tmp/runscript
rm /data/local/tmp/runscript
$ rm /data/local/tmp/sysrun
rm /data/local/tmp/sysrun
and now try again with app and may it works (in my case, works)
dh2311 said:
I have attached it to this post. ADB is the Android Debug Bridge. It is used to excecute commands on android devices. Just extract the zip, then open a command prompt and change to the directory of ADB, then excecute the commands.
Click to expand...
Click to collapse
maybe I should've mentioned I'm on a Mac computer with no access to windows....damn, this is so frustrating....
Ah... Its still possible you just have to get the android sdk for mac.
Get the SDK from here
Then in the tools folder ADB should be there
Then its commands as normal I think... not sure tho, don't have a mac.
Search around on here for tutorials, I'm sure someone has put up a tutorial on setting up adb on mac
dh2311 said:
Ah... Its still possible you just have to get the android sdk for mac.
Get the SDK from here
Then in the tools folder ADB should be there
Then its commands as normal I think... not sure tho, don't have a mac.
Search around on here for tutorials, I'm sure someone has put up a tutorial on setting up adb on mac
Click to expand...
Click to collapse
kewl, and the exact commands is in post #1 right?
so this root's the OS, title is confusing, does it enable fastboot? allow you to flash custom roms?
should be....
dh2311 said:
you need to execute the commands in the origional post via ADB with USB debugging enabled, because the location is in the system and ironicly you dont have the root privelages to delete them
Click to expand...
Click to collapse
did exactly what you said, but get the message
adb: permission denied
No does not enable fastboot
Hello,
I have found a way to remove unwanted applications from probably any Android phone with stock ROM (like Motorola Defy XT320). Linux console basics needed.
Procedure is safe as long as you know what you are doing.
However if you remove important applications you will damage your ROM. Some bloatware is needed by ROM.
I do not take responsibility. Experiment, but backup your phone first!
1) Root phone
2) Install and setup SSHDroid on the phone
3) Connect through ssh to your phone and login as root. Depending on system use putty (WIN) or console command ssh (LINUX).
command: su (login as root)
4) Find package of the aplication you want to remove
command: pm list packages (list packages installed in the phone)
command: pm path <PACKAGE> (use package name found in previous step to determine where the file is)
5) Move to this folder and change file access rights and move file to ie. SD card. Probably you will need to remount first folder applications are in. So if application is in /flex/app, then remount only /flex as below.
command: mount -o rw,remount /<FOLDER>
command: chmod 777 <FILENAME>
command: mv <FILENAME> /mnt/sdcard/
6) Probably we don't need this, but change access rights to the file and remount folder again.
command: chmod 644 <FILENAME>
command: mount -o ro,remount /<FOLDER>
7) Enjoy more internal memory on your phone! Comments welcome!
[Guide] Moving applications to SD card
You can also move heavy applications to SD card and still use them.
Not all applications may be moved this way. Some will disappear from application menu.
I do not take responsibility. Experiment, but backup your phone first!
command: mv <FILENAME> /mnt/sdcard/
command: ln -s <TARGET FILENAME> <APPLICATION FILENAME>
In my example I have moved 10MB Quickoffice from internal memory to SD card and created symlink in /flex/app folder:
mv Quick* /mnt/sdcard/app/
ln -s /mnt/sdcard/app/Quickoffice-Motorola-SP-5_0_104_V_Signed_2012-01-03_10-18-47.apk Quickoffice-Motorola-SP-5_0_104_V_Signed_2012-01-03_10-18-47.apk
Works like a charm!
I think that is easier to remove through root explorer.
pgreed said:
I think that is easier to remove through root explorer.
Click to expand...
Click to collapse
You are probably right. I bought my first Android phone two days earlier. Pieces of software I have tried were unsuccessful in removing bloatware. So I was looking for other way. Using console allows you to remove ie. default wallpapers or sounds. It frees some additional memory which is scarce in Defy Mini.
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.