Please, dont post on this thread, continue to use [NST]MinimalTouch 1.1beta5
Recomendation, Paste the commands one by one.
I am not responsible for any damage your nook suffers.
Index
Automatic Method:
[NST]MinimalTouch 1.1beta5
[NST]Touch-Formatter
Manual Tutos:
Skip registration (OOBE)
Making the manual process LESS PAINFULL
Setting up adb manually on the nook touch
Setting up root access on NST through adb and installing busybox
Improve battery life(testing)
Backup bookmarks and annotations(testing)
Enable non market app installs
Installing XorZone's B&N button modifier
Change the powered off screen image
Blocking OTA updates
Installing new fonts for your nook (testing)
Installing Gapps (+launcher, etc)
Totally uninstall Gapps (my repack), unrooting, erasing and restoring
Interesting or useful specific apps or hacks for Nook Simple Touch
nook 1.1 update
Thanks to:
GabrialDestruir for his hard work, making easy to root the NST creating the Touchnooter (http://forum.xda-developers.com/showthread.php?t=1343143) (http://forum.xda-developers.com/showthread.php?t=1132693)
ros87 for the update on uramdisk and the how to modify boot/charging images and usb drivers. (http://forum.xda-developers.com/showthread.php?t=1337653) (http://forum.xda-developers.com/showpost.php?p=17882146&postcount=11) (http://forum.xda-developers.com/showpost.php?p=19342931&postcount=12)
XorZone for NookTouchTools and his jars, book button menu and the orientation Switch (http://forum.xda-developers.com/showthread.php?t=1289894)
nookdevs for noogie and making all this possible (http://nookdevs.com/NookColor_Rooting)
mali100 for the update on framework. (http://forum.xda-developers.com/showpost.php?p=19201466&postcount=352)
xboxexpert for the working market. (http://forum.xda-developers.com/showpost.php?p=15084704&postcount=51)
Kralik for his findings. (http://www.mobileread.com/forums/showthread.php?t=156539)
bonzer2u for OTA blocking. (http://forum.xda-developers.com/showpost.php?p=10973887&postcount=1)
traycold for his images (http://forum.xda-developers.com/showpost.php?p=17822468&postcount=9)
jerryfan2000 for Button savior (http://forum.xda-developers.com/showthread.php?t=865525)
OMGWTF_BBQ for the Button Savior eink friendly mod (http://forum.xda-developers.com/showthread.php?t=1250278)
TJay99 for the Simplistic Countdown Timer (http://forum.xda-developers.com/showthread.php?t=1290900)
mdall for tweaking the screen refresh (http://forum.xda-developers.com/showthread.php?t=1241419)
dark_hawk for adding the last step on the Gaps method + Fonts (method 1) (http://forum.xda-developers.com/showpost.php?p=19441352&postcount=33)
met67 for usb drivers http://forum.xda-developers.com/showpost.php?p=19339163&postcount=11
LastSilmaril for the bookmarks and annotations info (http://forum.xda-developers.com/showpost.php?p=19483661&postcount=67)
met67 for the permissions and ownership on Gapps (http://forum.xda-developers.com/showpost.php?p=19658259&postcount=109)
mali100 for portin CWM to NST (http://forum.xda-developers.com/showthread.php?t=1360994)
salsichad2 for pointing out that the X files where corrupt and his adw theme config (http://forum.xda-developers.com/showpost.php?p=19720053&postcount=139)
kneeldug for sugesting extra steps on the automatic tuto.
bisbal for helping me beta testing.
dobbing for the copy of the 1.1 update.
Setting up adb manually on the nook touch:
If you want to restore, wipe data, or reset your nook, FIRST read how to backup your anotations and then search on this post for: Totally uninstall Gapps (my repack), unrooting, erasing and restoring.
Download noogie, and burn it into an SD-card (http://www.multiupload.com/OFI609MP8V) use Win32DiskImage.exe.
Shut down the Nook Touch completely your NST http://www.multiupload.com/CJ981FWPJG
Insert the SD-card into your Nook, connect it to the pc and turn it on.
When the nook ends booting (you should see a rooted forever splash screen on it) wait 20 seconds, you should see a new drive named boot, if not, go to MiniTool Partition Wizard Home Edition look for a partition named boot and assign it a letter.
Open boot, and replace the uramdisk, with one of these (http://forum.xda-developers.com/showthread.php?t=1337653).
This tuto is all made for the Wifi-uramdisk, if you want to use the usb change all the "adb connect yourNSTip" into "adb devices".
If you finally want to use adb over usb, follow this to make the nook recognizable by adb http://forum.xda-developers.com/showpost.php?p=19342931&postcount=12 or install this http://forum.xda-developers.com/showpost.php?p=19339163&postcount=11.
Eject the nook from the pc and reboot the NST without the noogie SD-card.
Setting up root access on NST through adb and installing busybox:
Download java JKD http://www.oracle.com/technetwork/java/javase/downloads/index.html
Download the android sdk (I recommend zipped) and extract it on C so that it looks like C:/android-sdk-windows
Open the SDK manager and update it, install for example the 2.1 platform, etc, it will automatically create /platform-tools
Download Superuser (http://nookdevs.com/images/a/a9/Superuser.zip), su (http://nookdevs.com/images/e/e0/Su.zip), and busybox (http://bit.ly/s1s7FZ or http://benno.id.au/android/busybox), extract them on C:/android-sdk-windows/platform-tools
Connect your NST to your home Wi-Fi, and check its ip.
Open cmd and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb install Superuser.apk
adb push su /data/local/
adb shell
cd /system/bin
mount -o remount,rw /dev/block/mmcblk0p5 /system
cat /data/local/su > su
chmod 6755 su
reboot
Now we will install buysbox.
Close cmd and reopen it, When your nook reboots type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
exit
adb push busybox /data/local
adb shell
su
cd /system
mkdir /system/xbin
cd /data/local
chmod 755 busybox
/data/local/busybox cp /data/local/busybox /system/xbin/busybox
cd /system/xbin
chmod 755 busybox
./busybox --install -s /system/xbin
rm /data/local/busybox
reboot
Improve battery life (testing)
As the Nook Touch hasn't got a overclocking kernel, and isn't near, as it isn't convenient to change or modify the cpu governor (it works in an unusual way), as I don't like too many apks bloating my nook, there is something that seems to be working for me, underclocking it manually of course .
The Nook has 3 stock frequencys, 300, 600, 800, and a deepsleep state.
As this small monster is just an ereader, and the refresh rates of eink are painfully slow I didn't find the need for it going all the way to 800mhz I did this small trick:
Make a backup up clrbootcount.sh.
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb pull /system/bin/clrbootcount.sh
Now lets modify it:
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
echo "echo 300000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" >> /system/bin/clrbootcount.sh
adb reboot
Check to see if the process was succesfull by typing this on cmd:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
To return back to stock file, restore the file you backed up by pushing it back or use:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
sed -i '/echo/d' /system/bin/clrbootcount.sh
reboot
Click to expand...
Click to collapse
If the output is 300000, then it worked and now your nook won't go all the way to 800mhz, if you want to limit it to 600mhz, just change 300000 to 600000.
Backup bookmarks and annotations (Haven't tried it yet)
Bookmarks and annotations are saved in /data/data/com.bn.nook.reader.activities/databases/
To backup them open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb pull /data/data/com.bn.nook.reader.activities/databases/ /bookmarks
To restore them after a reset open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
adb push /bookmarks /data/data/com.bn.nook.reader.activities/databases/
Enable non market app installs:
Download sqlite3 (http://www.sqlite.org/sqlite-shell-win32-x86-3070900.zip) and extract it on C:/android-sdk-windows/platform-tools
Open cmd and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
exit
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value=1 where name='install_non_market_apps';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Installing XorZone's B&N button modifier (Jars for 1.1, for other system versions check thread)(as I call it)
Download the jars (http://forum.xda-developers.com/attachment.php?attachmentid=781948&d=1321243370) and NookTouchTools (http://forum.xda-developers.com/attachment.php?attachmentid=750222&d=1318646585) and extract the zips on C:/android-sdk-windows/platform-tools. (Thread: http://forum.xda-developers.com/showthread.php?t=1289894)
Then backup the original jars onto the SD-card.
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
cp -p /system/framework/android.policy.jar /sdcard
cp -p /system/framework/services.jar /sdcard
exit
Then let’s push the new ones in place and install NookTouchTools:
Code:
adb push android.policy.jar /system/framework/
adb push services.jar /system/framework/
adb install NookTouchTools-1.0b2.apk
This can also be done by Nooktouchtools, but this is a manual thread, so now we will delete calvick-cache and fix permissions:
Code:
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
chown root.root /system/framework/*
chmod 644 /system/framework/*
rm -R /data/dalvik-cache/*
reboot
Now open NookTouchTools and modify settings as you wish.
Change the powered off screen image
First, let’s make a copy of the original apk.
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb pull /system/framework/framework-res.apk
You will find this file on C:/android-sdk-windows/platform-tools.
Make a copy of the file and open it with 7zip (download it if you don’t have it http://www.7-zip.org/).
Look for and open res\drawable-mdpi\
Search for cold_boot_screen.png and replace it for whatever 800x600 image you want.
Search for cold_battery_low_boot_screen.png and again replace it for whatever 800x600 image you want.
Save the modified apk on C:/android-sdk-windows/platform-tools
Then we have to push the new file and fix permissions.
Code:
adb shell
mount -o remount,rw -t ext2 /dev/block/mmcblk0p5 /system
exit
adb push framework-res.apk /system/framework/
adb shell
chown root.root /system/framework/*
chmod 644 /system/framework/*
rm -R /data/dalvik-cache/*
reboot
If you have problems pushing the framework-res.apk because the NST reboots, or hangs, use this zip (http://nooter.googlecode.com/files/RestoreFramework.zip) in conjunction with CWM (http://forum.xda-developers.com/attachment.php?attachmentid=806435&d=1323121399). (Keep reading)
You must:
Open the zip and drop your original or modifyed framework-res.apk in /system/framework, inside the zip.
Copy it to the SD card where you have burnt CWM and flash it through it.
If you see any strange behavior restore your backed up copy.
On this post, there are some nice pictures to use, http://forum.xda-developers.com/showpost.php?p=17822468&postcount=9, I modified them a bit, making them 16 bit grayscale and 800x600, see attachments..
Blocking OTA updates:
To prevent future automatic updating and unrooting you can block OTA updates.
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
adb reboot
Installing new fonts for your nook
This first method works for Opera mini, for example, not for normal apps.
The second one for changing the official interface Font (testing)
The third one for changing the Fonts on the official reader app (testing)
1º method
First open CMD and make a copy of your fonts:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p5 /system
adb pull /system/fonts
exit
Then add the new fonts.
Code:
adb push thenewfont /system/fonts
adb shell
su
chmod 4755 /system/fonts/*
2º method
3º method
Installing Gapps (+launcher, etc)
Market FULLY functional, My apps tab working and updating correctly, proof: http://forum.xda-developers.com/showpost.php?p=19602755&postcount=76
PC android market webpage working, proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dark_hawk's exprience.
My experience.
New packages, deleted all the unneeded, apks, not needed libraries, jars, etc.
You have four options:
Minimal Touch (Core Gapps (http://bit.ly/rQ3YNn))
Minimal Touch + NookColorTools (http://bit.ly/vUwXeb)
Minimal Touch + Extras (Core Gapps + Launcher + theme + Button savior + NookColorTools(http://bit.ly/skgHhe))
Everything is functional, Gmail, Gtalk, Market.
Instructions:
For this process to work, you will need to install busybox, so search for Setting up root access on NST through adb and installing busybox and go directly to installing busybox if you come from another method of installing Gapps.
Download Minimal Touch + Extras if you haven't got a launcher installed, and extract it on the C:/android-sdk-windows/platform-tools (root)
Download Minimal Touch if you already have a launcher installed, and extract it on the C:/android-sdk-windows/platform-tools (root)
First, make a backup of the files we will modify:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p5 /system
adb pull /system/framework/framework.jar
adb pull /data/system/packages.xml
adb pull /system/build.prop
exit
exit
Second, lets start with the install process.
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p5 /system
exit
exit
adb push data /data
adb push system /system
If the NST reboots before finishing the process, it may happen, start again where you left it.
Now lets fix permissions and ownership.
Code:
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p5 /system
chown system.system /data/app/*
chmod 644 /data/app/*
chmod 644 /system/app/*
chmod 644 /system/etc/permissions/*
chmod 644 /system/framework/*
chmod 644 /system/lib/*.so
reboot
When the NST reboots select adw launcher as your predefined launcher (If you haven't already), log in on YouTube (click settings, my channel) and log in the Gmail account you used on YouTube, both accounts must be the same.
It will fail to sync and force close.
Open Cmd and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p5 /system
sed -i '/uid.system/,/perms/{/uid.system/b;/perms/b;d}' /data/system/packages.xml
reboot
Gmail should already work and sync.
Open Cmd and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p5 /system
echo "ro.config.nocheckin=no" >> /system/build.prop
reboot
Let android fully load.
Open Market, it will try to connect, if it can't retry until it does (it will), if it doesn’t, you haven’t got the Wi-Fi on .
Market should be fully functional now.
After this, manually by deleting it and its data, or through your launcher, or through Nook Color Tools, you can unistall YouTube.apk, it is no longer needed, and autostarts everytime wasting resources.
Now lets make protected apps show in market
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p5 /system
sed -i 's/^.*ro.build.fingerprint.*$/ro\.build\.fingerprint=verizon\/voles\/sholes\/sholes:2\.1-update1\/ESE81\/29593:user\/release-keys/' /system/build.prop
reboot
Protected apps wont appear inmediatly, the market must check your new fingerprint and that happens at midnight, so you can wait 1 day or:
Check you have correctly changed the fingerprint, change the time to 23:50 on your Nook Touch and wait till "midnight" wait a bit more, and protected apps should appear.
Totally uninstall Gapps (my repack), unrooting, erasing and restoringTesting
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push /system/framework/framework.jar
adb push /data/system/packages.xml
adb push /system/build.prop
rm /data/app/YouTube.apk
rm -R /data/data/com.google.android.youtube
rm /system/lib/libgtalk_jni.so
rm /system/lib/libinterstitial.so
rm /system/framwork/com.google.android.gtalkservice.jar
rm /system/etc/permissions/com.google.android.datamessaging.xml
rm /system/etc/permissions/com.google.android.gtalkservice.xml
rm /system/app/Gmail.apk
rm -R /data/data/com.google.android.gm
rm /system/app/GmailProvider.apk
rm -R /data/data/com.google.android.providers.gmail
rm /system/app/GoogleApps.apk
rm -R /data/data/com.google.android.googleapps
rm /system/app/GoogleCheckin.apk
rm -R /data/data/com.google.android.server.checkin
rm /system/app/GoogleSubscribedFeedsProvider.apk
rm -R /data/data/com.google.android.providers.subscribedfeeds
rm /sytem/app/gtalkservice.apk
rm -R /data/data/com.google.android.apps.gtalkservice
rm /system/app/Talk.apk
rm -R /data/data/com.google.android.talk
rm /sytem/app/TalkProvider.apk
rm -R /data/data/com.google.android.providers.talk
rm /sytem/app/Vending.apk
rm -R /data/data/com.android.vending
reboot
Unrooting:
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
rm -R /sytem/app/Superuser.apk
rm -R /data/app/Superuser.apk
rm -R /sytem/bin/su
rm -R /sytem/xbin
reboot
Erasing and restoring:
After this, if what you want is to have a clean nook and you didnt make a backup before rooting you have to:
Use nookRestore to restore /system (http://forum.xda-developers.com/showthread.php?t=1289233), or using adb do:
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Use on settings, device, Erase and Deregistered to wipe /data
(If it doesn’t let you, force it shutting down your nook, then starting it up, and when the screen flickers press right and left bottom buttons, hold for 5+ seconds).
Update to 1.1 (http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/)
Interesting or useful specific apps or hacks for Nook Simple Touch
Calendar Pad (https://market.android.com/details?id=jp.ne.gate.calpad)
Book button menu (http://forum.xda-developers.com/showthread.php?t=1280509)
Button Savior (http://forum.xda-developers.com/showpost.php?p=9669486&postcount=1)
Button Savior eink friendly mod (http://forum.xda-developers.com/showthread.php?t=1250278)
Simplistic countdown timer (http://forum.xda-developers.com/showthread.php?t=1290900)
Tweaking the screen refresh (http://forum.xda-developers.com/showthread.php?t=1241419)
Orientation Switch [Recommended, use in conjunction with XorZone's B&N button modifier] (http://forum.xda-developers.com/showthread.php?t=1283176)
ADW launcher + Minimalist_Black - ADW Theme, nice launcher + awesome theme pack with awesome icons for eink (https://market.android.com/details?id=org.adw.launcher + https://market.android.com/details?...iwiY29tLmRhdmlkMTE3MS5taW5pbWFsaXN0YmxhY2siXQ..)
Minimalistic text, it’s a really nice free widget app, from which you can make things like this http://attachments.xda-developers.com/attachment.php?attachmentid=781918&d=1321239931, you will need version 2.6.2 or 2.6.3 here you have the 2.6.2 (http://www.megaupload.com/?d=UO7PD9BU) and the market link for the latest (https://market.android.com/details?id=de.devmil.minimaltext)
AdbWireless widget, to control when you want adb over Wi-Fi on and off with the Wi-Fi uramdisc, or to add the possibility to the usb uramdisc (https://market.android.com/details?id=siir.es.adbWireless)
Making the manual process LESS PAINFULL
To not have to open each time CMD, and go typing cd C/.... and connect yourNSTip make a small batch file like this:
Open notepad type:
Code:
@echo off
cd C:/android-sdk-windows/platform-tools
adb kill-server
adb connect yourNSTip
cmd
Save the file as .bat, or change the extension when saved.
Now each time you reboot in the proces, instead of opening CMD and typing cd ..... and adb connect.... just open this file and star copying command right away
eded333 said:
Change the powered off screen image
First, let’s make a copy of the original apk.
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb pull /system/framework/framework-res.apk
You will find this file on C:/android-sdk-windows/platform-tools.
Make a copy of the file and open it with 7zip (download it if you don’t have it http://www.7-zip.org/).
Look for and open res\drawable-mdpi\
Search for cold_boot_screen.png and replace it for whatever 800x600 image you want.
Search for cold_battery_low_boot_screen.png and again replace it for whatever 800x600 image you want.
Save the modified apk on C:/android-sdk-windows/platform-tools
Then we have to push the new file.
Code:
adb shell
mount -o remount,rw -t ext2 /dev/block/mmcblk0p5 /system
exit
adb push framework-res.apk /system/framework/
adb reboot
If you see any strange behavior restore your backed up copy.
On this post, there are some nice pictures to use, http://forum.xda-developers.com/showpost.php?p=17822468&postcount=9, I modified them a bit, making them smaller in size, 16 bit grayscale and 800x600 here is the link http://www.megaupload.com/?d=PD94ZJK9.
Click to expand...
Click to collapse
So, I did all that, but I'm stuck at the loading screen (the one with 5 dots doing stuff).
Any ideas?
I've also tried to restore the orig framework-res.apk, but nothing.
Also changed permissions back to 644.
ace7196 said:
So, I did all that, but I'm stuck at the loading screen (the one with 5 dots doing stuff).
Any ideas?
I've also tried to restore the orig framework-res.apk, but nothing.
Also changed permissions back to 644.
Click to expand...
Click to collapse
I hate you..... (not really )
Read the first page:
"Please, dont post on this thread, continue to use [NST]MinimalTouch 1.1beta5"
Anyway
It works, I've modded it myself, try to fix the the permissions:
chmod 644 /system/framework/*
What images did you use?
Please lets continue this conversation on: http://forum.xda-developers.com/showthread.php?t=1346748
Or through PM, id like to use this thread only to add more tutos, or correct the ones I allready have.
----------------------------------------------------------------------------
Edit,
didnt read you allready did that.
So after restoring the original file, you still have problems?
Try to force shut it down, and start it again, or try to erase dalvik cache, and reboot (if you can acces adb, if not I'll make you an CWM zip)
rm -rf /data/dalvik-cache/*
Skip OOBE:
On the first screen that appears on the NST without tapping any button.
1.Hold the right top button and move your finger from left to right on the top of the screen.
2.The factory button will appear at the bottom right of the screen, tap it.
3.Hold again the right top button and tap the right bottom part of the screen, where the factory button appeared
4.A button labeled skip oobe will appear, tap it, your done
Redid Gapps packages and updated links.
eded333 said:
Improve battery life (testing)
As the Nook Touch hasn't got a overclocking kernel, and isn't near, as it isn't convenient to change or modify the cpu governor (it works in an unusual way), as I don't like too many apks bloating my nook, there is something that seems to be working for me, underclocking it manually of course .
The Nook has 3 stock frequencys, 300, 600, 800, and a deepsleep state.
As this small monster is just an ereader, and the refresh rates of eink are painfully slow I didn't find the need for it going all the way to 800mhz I did this small trick:
Make a backup up clrbootcount.sh.
Open CMD and type:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb pull /system/bin/clrbootcount.sh
Now lets modify it:
Code:
adb shell
mount -o remount,rw /dev/block/mmcblk0p5 /system
echo "echo 300000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" >> /system/bin/clrbootcount.sh
adb reboot
Check to see if the process was succesfull by typing this on cmd:
Code:
cd C:/android-sdk-windows/platform-tools
adb connect yourNSTip
adb shell
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
To return back to stock file, restore the file you backed up by pushing it back or use:
If the output is 300000, then it worked and now your nook won't go all the way to 800mhz, if you want to limit it to 600mhz, just change 300000 to 600000.
Click to expand...
Click to collapse
Have you done any actual benchmarkings on this? Usually trickery like this actually make degrades battery performance because the slower the computations is done the less time is spent in deep sleep. Most of the time the device should be in deep sleep but whenever something need to be done, it should be done as quickly as is possible.
Anyway I like your guides. I just got everything up and running exactly as I want without a bunch of crappy useless apps installed. Market as well. Something the automated methods doesn't handle at all well
Fulkerson said:
Have you done any actual benchmarkings on this? Usually trickery like this actually make degrades battery performance because the slower the computations is done the less time is spent in deep sleep. Most of the time the device should be in deep sleep but whenever something need to be done, it should be done as quickly as is possible.
Anyway I like your guides. I just got everything up and running exactly as I want without a bunch of crappy useless apps installed. Market as well. Something the automated methods doesn't handle at all well
Click to expand...
Click to collapse
¬¬ please dont reply on this thread.... do it on the thread which I point out on the first post.
I did some testing, and it did last longer when being used, it lasted the same on sleep, I never turn it off, but didnt really do any real benchmarking so its just my impression.
I'm glad this manual tutos are still being used and found usefull ^^
hello everyone
I have a t-mobile note 2 rooted and i was having problems with my play store and deleted my hosts file by mistake i tried making a new one with root explorer but it fails is there anything els that i can do to get it back when i reset my phone the play store is gone and i don't know what to do any help would be great.
Bdvs said:
hello everyone
I have a t-mobile note 2 rooted and i was having problems with my play store and deleted my hosts file by mistake i tried making a new one with root explorer but it fails is there anything els that i can do to get it back when i reset my phone the play store is gone and i don't know what to do any help would be great.
Click to expand...
Click to collapse
Do you have access to a system with adb or heimdall ?
If not
You can create a new file(text) named hosts under /etc/system/ with the following line
127.0.0.0 localhost
You can set the permissions of this file to 0644 via root explorer or using Terminal Emulator:
----
cd /system/etc
chmod 644 hosts
---
Never used root explorer but there has to be a GUI option somewhere in it.
You will have to mount the /system to read-write mode in root explorer in order to make any changes.
Once you have created the file, reboot the phone and see if it works, if not then manually delete all files under /system/data/dalvick-cache.
Be careful before deleting any file, make sure you browse to /system/data/-dalvick-cache directory and select all files and then delete them.
ciphercodes said:
Do you have access to a system with adb or heimdall ?
If not
You can create a new file(text) named hosts under /etc/system/ with the following line
127.0.0.0 localhost
You can set the permissions of this file to 0644 via root explorer or using Terminal Emulator:
----
cd /system/etc
chmod 644 hosts
---
Never used root explorer but there has to be a GUI option somewhere in it.
You will have to mount the /system to read-write mode in root explorer in order to make any changes.
Once you have created the file, reboot the phone and see if it works, if not then manually delete all files under /system/data/dalvick-cache.
Be careful before deleting any file, make sure you browse to /system/data/-dalvick-cache directory and select all files and then delete them.
Click to expand...
Click to collapse
I have adb access how would i do it with adb
root explorer wont let me make a text file
Bdvs said:
I have adb access how would i do it with adb
root explorer wont let me make a text file
Click to expand...
Click to collapse
1) Using text editor create a text file named "hosts" with the following contents:
---
127.0.0.1 localhost
---
If you are on windows make sure you remove the file extension.
2) Connect phone via USB and open command prompt or shell. Make sure USB Debugging is checked under developers options.
3) Check if adb detects your device by typing: adb devices , you should see your device listed, if not please check if your phone has correct USB drivers.
4) Now push the file you created to your phone with this command : adb push /path/to/file/hosts /sdcard/hosts
example: adb push C:\tmp\hosts /sdcard/hosts
5) Now log in to your phone by typing adb shell
6) Switch to super user by typing: su , grant permissions when asked by SuperSU.
7) Mount system in read-write mode by typing: mount -o remount,rw -t yaffsw /dev/block/mtdblk3 /system
8) Move the hosts file to /system/etc by typing: mv /sdcard/hosts /system/etc
9) Browse to /system/etc by typing: cd /system/etc
10) Change file owner and group by typing: chown root:root hosts
11) Change file permissions by typing: chmod 644 hosts
12) Mount system back to read only by typing: mount -o remount,ro -t yaffsw /dev/block/mtdblk3 /system
13) Delete dalvik cache by browsing to cd /data/dalvik-cache and then type rm -f *.dex
14) type exit two times to exit.
15) Reboot phone and it should work.
I believe there might be an easy way or an apk which does this but I haven't tried it.
play store
ciphercodes said:
1) Using text editor create a text file named "hosts" with the following contents:
---
127.0.0.1 localhost
---
If you are on windows make sure you remove the file extension.
2) Connect phone via USB and open command prompt or shell. Make sure USB Debugging is checked under developers options.
3) Check if adb detects your device by typing: adb devices , you should see your device listed, if not please check if your phone has correct USB drivers.
4) Now push the file you created to your phone with this command : adb push /path/to/file/hosts /sdcard/hosts
example: adb push C:\tmp\hosts /sdcard/hosts
5) Now log in to your phone by typing adb shell
6) Switch to super user by typing: su , grant permissions when asked by SuperSU.
7) Mount system in read-write mode by typing: mount -o remount,rw -t yaffsw /dev/block/mtdblk3 /system
8) Move the hosts file to /system/etc by typing: mv /sdcard/hosts /system/etc
9) Browse to /system/etc by typing: cd /system/etc
10) Change file owner and group by typing: chown root:root hosts
11) Change file permissions by typing: chmod 644 hosts
12) Mount system back to read only by typing: mount -o remount,ro -t yaffsw /dev/block/mtdblk3 /system
13) Delete dalvik cache by browsing to cd /data/dalvik-cache and then type rm -f *.dex
14) type exit two times to exit.
15) Reboot phone and it should work.
I believe there might be an easy way or an apk which does this but I haven't tried it.
Click to expand...
Click to collapse
Thanks for all your help i got the hosts file in to system/etc folder but my play store is still not working i get a pop up that play store has stop working so i cleared cache for play store, play services and google framework and its still not working
any ideas thanks again
Did you delete dalvik cache ?
Sent from my SGH-T889 using xda app-developers app
i'm on (pixel 2xl) lineageos 16.0 rooted with magisk, i want to add a script in init.d folder but i can't do it, i tried with root explorer but it doesn't work, afwall also can't mount folder for startup script, any solution?
lg_g3_d855 said:
i'm on (pixel 2xl) lineageos 16.0 rooted with magisk, i want to add a script in init.d folder but i can't do it, i tried with root explorer but it doesn't work, afwall also can't mount folder for startup script, any solution?
Click to expand...
Click to collapse
Why? What error do you get?
Try to move/copy something into /tmp folder. It should work if you're rooted (your shell shows # instead of $).
If it doesn't work, maybe you have to remount your system as rw (read and write):
Code:
mount -o rw,remount /
after you made your modifications, mount it as ro (read only) again:
Code:
mount -o ro,remount /
If it still doesn't work, we need to see the error you get (copy and paste into this forum) while moving/coping something into /tmp.
User699 said:
Why? What error do you get?
Try to move/copy something into /tmp folder. It should work if you're rooted (your shell shows # instead of $).
If it doesn't work, maybe you have to remount your system as rw (read and write):
Code:
mount -o rw,remount /
after you made your modifications, mount it as ro (read only) again:
Code:
mount -o ro,remount /
If it still doesn't work, we need to see the error you get (copy and paste into this forum) while moving/coping something into /tmp.
Click to expand...
Click to collapse
i tried with mount -o rw, remount, but it keeps showing me the file system is read only
.
lg_g3_d855 said:
i tried with mount -o rw, remount, but it keeps showing me the file system is read only
.
Click to expand...
Click to collapse
Can you verify you entered that command as root?
Please do the following:
Do this on your computer to enter your devices shell
Code:
prompt_PC:~$ adb shell
Code:
prompt:~$ whoami
This should give you either "shell" or "root"
If it says "shell" do:
Code:
prompt:~$ su
prompt:~#
It will show a # instead of $ if you're root.
If you're already root (or you are now root due to su command), do:
Code:
prompt:~# mount -o rw,remount /
Now it should be writeable and you can do your modifications.
After you finished you need to change it to ro (read only) again:
Code:
prompt:~# mount -o ro,remount /
After that you can exit the shell:
Code:
prompt:~# exit
prompt:~$ exit
(first exits su, second exits shell)
I'm sorry if you already did that but I wan't to be sure you did it correctly.
If this procedere doesn't work, please copy and past your input and output into this forum as this might help to understand what's going on/failing etc.
User699 said:
Can you verify you entered that command as root?
Please do the following:
Do this on your computer to enter your devices shell
Code:
prompt_PC:~$ adb shell
Code:
prompt:~$ whoami
This should give you either "shell" or "root"
If it says "shell" do:
Code:
prompt:~$ su
prompt:~#
It will show a # instead of $ if you're root.
If you're already root (or you are now root due to su command), do:
Code:
prompt:~# mount -o rw,remount /
Now it should be writeable and you can do your modifications.
After you finished you need to change it to ro (read only) again:
Code:
prompt:~# mount -o ro,remount /
After that you can exit the shell:
Code:
prompt:~# exit
prompt:~$ exit
(first exits su, second exits shell)
I'm sorry if you already did that but I wan't to be sure you did it correctly.
If this procedere doesn't work, please copy and past your input and output into this forum as this might help to understand what's going on/failing etc.
Click to expand...
Click to collapse
yes I'm root, output is file system is read only despite adb commands
lg_g3_d855 said:
yes I'm root, output is file system is read only despite adb commands
Click to expand...
Click to collapse
Well, I'm sorry then... I can't help.
Good luck!