Related
which uRamdisk to Replace into touchnooter-1.6.24 to make it work on 1.1 is not clear (there are 2 of them).
The answer is ONLY /nooter/boot/uRamdisk (don't touch the one in the root)
with this configuration (and the framework.jar) i got it to work on the first boot, no need to make the 3 boots sequence.
concluding (starting from an 1.1 virgin system):
download touchnooter-1-6-24.zip
extract touchnooter-1-6-24.img
download one of those uRamdisk
download framework.jar
replace ONLY /nooter/boot/uRamdisk in touchnooter-1-6-24.img
replace framework.jar in touchnooter-1-6-24.img
write touchnooter-1-6-24.img on the SD
just 1 boot as usual to the android welcome page,
then remove the SD,
reboot,
double skip as usual
NookColorTools - disable and re-enable non market apps (uncheck and check it again),
Youtube (error 401),
Gmail
and finally...
Market (install at least 1 application with this version, search doesn't work)
now (after you have installed 1 app) eventually replace Vending.apk with this to enable search
i also putted this inside my touchnooter, the 2 .jar into the framework directory and the apk into the app but this shouldn't be necessary...
this is how it worked for me, enjoy
Since i don't have enough posts for development forum, i will post this here, may be someone can move it to the right place, i'm not used to spam, but this 10 posts rule seems to encourage new users to spam 10 posts around...
move it here if you can
I think what you are addressing is exactly apeine's problem:
changed both uramdisk ... Booted with SD in and it either locks up or goes to regular nook (on 12 tries, 10 lock ups and 2 going to regular nook)
Click to expand...
Click to collapse
Incidentally, how long did it take to boot and work on the first try? With 1.0.1 firmware I rooted three nooks and left it for over 30 minutes on the first one without success. Then on the other two I was impatient and gave it two boots. So I never let 1.1.0 go on that long before rebooting since I assumed it was going nowhere.
Kralik said:
I think what you are addressing is exactly apeine's problem:
Click to expand...
Click to collapse
yes, that's why i wrote this, i cannot reply in the development section because i have too few posts on the forum
Kralik said:
Incidentally, how long did it take to boot and work on the first try? With 1.0.1 firmware I rooted three nooks and left it for over 30 minutes on the first one without success. Then on the other two I was impatient and gave it two boots. So I never let 1.1.0 go on that long before rebooting since I assumed it was going nowhere.
Click to expand...
Click to collapse
In my case it took slightly longer than a normal boot, no freeze at all, just about 1-2 minute on "Rooted Forever", then some time, may be 1-2 minutes on the nook dots screen with the dots moving (they never froze) and then the android guy page, no more than 4-5 minutes globally.
Anyway when i used touchnooter on 1.0.1 the first time, i had to reboot 2 times as you reported, same problem, more or less, may be the freezing at boot is something which happens, but not regularly
thank you for the description!
so if i understood correctly, there's no drawback with this method, everything works as it was before upgrade to 1.1.0, including the Market?
what about the installed apps, especially the non-free ones? (I've purchased OrientationControl)
can I simply download it from Market again, or should I backup the APK file and copy it back after upgrade/root?
glezmen said:
thank you for the description!
so if i understood correctly, there's no drawback with this method, everything works as it was before upgrade to 1.1.0, including the Market?
Click to expand...
Click to collapse
Yes, my nook behave exactly as with 1.0.1
glezmen said:
what about the installed apps, especially the non-free ones? (I've purchased OrientationControl)
can I simply download it from Market again, or should I backup the APK file and copy it back after upgrade/root?
Click to expand...
Click to collapse
No idea, never bought an app, just free ones, but to keep an .apk backup is always a safe choice
about orientation... i remember Orientation Switch and this (just in case someone wanted rotation for free)
glezmen said:
what about the installed apps, especially the non-free ones? (I've purchased OrientationControl)
can I simply download it from Market again, or should I backup the APK file and copy it back after upgrade/root?
Click to expand...
Click to collapse
You can re-install purchased apps from Market whenever you want.
Celebom said:
about orientation... i remember Orientation Switch and this (just in case someone wanted rotation for free)
Click to expand...
Click to collapse
thanks for the hint, I will have a look on it (especially if i can't download the app again for free )
btw 1 EUR was not a big pain (I tried ADW launcher and rotation before, but it was not really convenient)
As long as you have market working with your prior GMail account, you should have no problem redownloading both your free and paid apps.
Thanks. Worked like a charm.
I first installed Astro File Manager, which is the second one in the list under the "Productivity" -> "Top Free". This allows me to install Vending.apk (Market where the search function works), and then follow it with Titanium Backup.
Using Titanium Backup re-installed all the apps from my previous backup, plus installed the XorZone's NookTouchTools for 1.1 (jars are different from 1.0.1).
I'm not sure what the significant difference is between the firmwares, but I understanding that the screen refresh is a bit quicker, and that the battery report is more accurate (previously batt reading would fluctuate when first turned on).
As for the firmware upgrade.... my STR just did not want to download the upgrade, even though I set the screensaver to 1 hour. There could be several reason why this didn't work, such that I don't live in US, or the process of rooting had modified something (even thought I factory reset it).
In the end I just connected it using USB, and loaded it into the root directory of the my STR (a simply file copy in Windows XP). Then the upgrade started a minute after the copy.
Thanks for your guide! I've just finished rooting my 1.1 Nook Simple Touch firmware
Remember everybody :
ONLY REPLACE URAMDISK IN NOOTER/BOOT/ (OF TOUCHNOOTER .IMG FILE)
uRamdisk mirror?
Hello, guess I shouldn't have started without all the downloads but I assumed they would be somewhere? any alternative downloads for uRamdisk_rooted because all the links are broken.
Thanks
I want to root my nook simple touch - what works TODAY?
Hi all.
I find this thread interesting and helpful. I have noted that a lot of the information here, on nook developers, or in two articles I read (one in lifehacker.com and the other in Que Publishing) all contain help that includes links to files that are either not there or I can't find.
Can someone point me to a current simple solution that will allow me to root my nook and toggle between the original home screen and the better Android one?
Thanks in advance!
Halfhoff said:
Hi all.
I find this thread interesting and helpful. I have noted that a lot of the information here, on nook developers, or in two articles I read (one in lifehacker.com and the other in Que Publishing) all contain help that includes links to files that are either not there or I can't find.
Can someone point me to a current simple solution that will allow me to root my nook and toggle between the original home screen and the better Android one?
Thanks in advance!
Click to expand...
Click to collapse
ButtonSaviour should have been installed with the Root, so just look for a transparent(translucent?) arrow button thing on the right screen, near the middle. It might be hard to hit it. The Home button on that will be like hitting the Home button on a normal Android device, and when you press the Quick Nav button, the home on that will lead to the B&N home unless you used Xor's mods to change what it leads to.
broken link..........
+1
All the links that I find on the internet for the uRamdisk_rooted file appear broken also...
Markey1979 said:
All the links that I find on the internet for the uRamdisk_rooted file appear broken also...
Click to expand...
Click to collapse
uRamdisk, rooted, adb wireless, fixed init, 1.1 and 1.1.2
http://code.google.com/p/nst-recovery/downloads/detail?name=uRamdisk_wireless_adb_init_1.1_1.1.2.zip
uRamdisk, rooted, adb usb, fixed init, 1.1 and 1.1.2
http://code.google.com/p/nst-recovery/downloads/detail?name=uRamdisk_usb_adb_init_1.1_1.1.2.zip
I attempted to use the multitouch kernel with clockwork mod after rooting my glowlight and for some reason it seems to have hosed the glowlight controls completely. I was hoping that the n2t recovery by ros87 would help but the server hosting the image is not working. Does anyone have a mirror of the image?
EDIT: In my panic I didn't check the entire thread and found a dropbox mirror of the file further on in the thread. Let this serve as a warning to first stay calm and also not to attempt multitouch on the NTG. Sorry if I wasted your time.
Schneicw said:
I attempted to use the multitouch kernel vi clockwork mod after rooting my glowlight and for some reason it seems to have hosed the glowlight controls completely. I was hoping that the n2t recovery by ros87 would help but the server hosting the image is not working. Does anyone have a mirror of the image?
Click to expand...
Click to collapse
Here you go.
Just wait for a NTG modded kernel, dont use the device specific resources for the NST.
Thanks for the quick response and the advice which I will be sure to remember. Any idea how long it's going to take to port multitouch to the NTG
Schneicw said:
Thanks for the quick response and the advice which I will be sure to remember. Any idea how long it's going to take to port multitouch to the NTG
Click to expand...
Click to collapse
It'll take about the amount of time for whoever brought multitouch to the Nook Simple Touch to download the source for NTG and then make the appropriate changes. That's if they even care.
Hi,
the kernel in the attachment should work for the NTG. I patched it a month ago and totally forgot to upload it .
Works also on the normal NST.
The zip file includes only the kernel, its not flashable by cwm, you have to push it manually to your boot partition and add the permissions in the xml-file.
Git-Repository: https://github.com/mali1/NST-kernel_115
Thank you. Is it possible to replace the uimage in the original CWM zip with this one and do the same thing as for the nst or should I follow the directions in the original thread which if I understand right involves burning noogie to an sdcard then then booting the nook up, connecting it to a computer, finding uimage and replacing it.
Schneicw said:
Thank you. Is it possible to replace the uimage in the original CWM zip with this one and do the same thing as for the nst
Click to expand...
Click to collapse
Yes, that should work.
Hello everybody!
I haму some questions about this: http://forum.xda-developers.com/showthread.php?p=24180134
Can I use this method if I had already NST [email protected] with root? I want get multitouch, NoRefresh and usb-host.
All what I should to do is just replace uImage through Noogie?
This particular thread is regarding Multitouch on the Nook Touch Glow, not the Nook Simple Touch.
mali100 said:
Hi,
the kernel in the attachment should work for the NTG. I patched it a month ago and totally forgot to upload it .
Works also on the normal NST.
The zip file includes only the kernel, its not flashable by cwm, you have to push it manually to your boot partition and add the permissions in the xml-file.
Git-Repository: https://github.com/mali1/NST-kernel_115
Click to expand...
Click to collapse
I've installed this kernel on my NTG and it works great. Thanks!
>>you have to push it manually to your boot partition and add the permissions in the xml-file
Using Root Explorer, where do I have to copy the (extracted kernel) file to (exact path/folder)?
Add permissions: Can I do that in Root Explorer rather than opening the xml file (filename?)? I do not have an editor for xml files....(which one would you recommend if I cannot change the permissions directly using Root Explorer)?
Thanks!
nrseife said:
>>you have to push it manually to your boot partition and add the permissions in the xml-file
Using Root Explorer, where do I have to copy the (extracted kernel) file to (exact path/folder)?
Add permissions: Can I do that in Root Explorer rather than opening the xml file (filename?)? I do not have an editor for xml files....(which one would you recommend if I cannot change the permissions directly using Root Explorer)?
Thanks!
Click to expand...
Click to collapse
Follow the instructions in the original multitouch thread http://forum.xda-developers.com/showthread.php?t=1563645
Glowlight not working
Hello,
I have a problem with my Nook Simple Touch Glowlight that I hoped you could help me with.
I rooted it and it was working fine. Then, I tried to add the multitouch mod, but I think it was for the NST, and now the glowlight doesn't work at all. I did not have a backup, unfortunately. I tried doing a factory reset and rerooting, but when it gets to the "try the glowlight" part of the setup. I can't go any further because the light doesn't work. How do I fix this problem?
Thanks,
Joe
Glow + multitouch + Norefresh?
After rooting my Glow I downloaded and installed the .zip I found in another thread to enable multi touch and an APK that was to enable NoRefresh. The norefresh didnt work at all and the multi touch worked but killed the glowlight. Now I understand what happened, but basically i ended up with the kernal for the NST that enabled Multitouch.
After downloading and ADB pushing the the kernal that has both Glow and MultiTouch I am satisfied but not completely happy. I would really want the addition of norefresh but I have not been able to find a kernal that has all three.
USB host would not be a bad thing to have also, as long as it doesn't hose the battery life. It isn't a required component for my needs.
I've been looking around to see who has been working on this.
As mentioned elsewhere, EpdController has been changed in 1.2 which will break anything designed to play with Epd modes.
I've no experience or real interest in "NoRefresh" since for what I want
it's better to integrate Epd control at the application level, which I do.
Oh, I should have mentioned. I am at 1.1.5. I used Glownooter because I wanted the Market access, utilizing the Search Market tool. As far as I could tell, the rooting methods that work on 1.2 don't include Market capability.
If I could update to 1.2 and keep market that would be cool. It might be that any dev work has been scrapped for 1.1.5 as that is an old version.
here is multitouch for nook glowlight, it is in zip format for installing with CWM, I made it changing the uimage file for the rigth one in the NST CWM zip file from the first post
I have tried it in my nook glow with firmware 1.2, spanish language, and previously rooted with glownooter, I had installed too the norefresh toggle previously, it works like a charm with opera browser, and of course light is working
I installed it after previously have done with the no glow version and having lost my light, so it works also as an amendment to this failure
View attachment multitouchNSTG.zip
elsita could you please tell if this kernel is compatibile with fw 1.21 on NSTG to enable multitouch and fast refresh on this device? thanks!
soolcio said:
elsita could you please tell if this kernel is compatibile with fw 1.21 on NSTG to enable multitouch and fast refresh on this device? thanks!
Click to expand...
Click to collapse
I can't tell for sure but I guess so, no refresh though is an app AFAIK
Enviado desde mi ZP800 usando Tapatalk 2
soolcio, will you share your attempt's results here, please, if any - a lot of people now have NSTG FW 1.2.1 and wanna have multitouch without loosing GlowLight feature working as usual
Just caught the BN support page for the Nook Touch devices.
BN is rolling out a software update, version 1.2.0, which will apply to both the NST and NSTG.
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
From what I'm reading, it sounds like this software was preinstalled for devices in the UK, and that the current generation of rooting tools will need to be looked at again.
I'll test tonight, but from what I've read about the UK experience, Tinynoot should work, I'm not sure how eded's tool will do, and the UK folks already have a viable root with a few more tweaks built in.
On the whole, I think it's great that there's a common software stack since we'll see fewer folks blowing out their devices.
A quick comparison between the published 1.2.0 and the extracted 1.2.0 factory.zip from the UK nooks shows that the system files are identical between the two systems, with the only differences being in non-application spots like build.prop definitions, boot/shutdown images, dictionaries, license agreements, and the wifi config uses AT&T instead of B&N hotspots.
From experience, the 1.1.5 rooted uRamdisk works just fine with 1.2.0, so any minimal rooting methods for 1.1.5 will continue to work with 1.2.0. Rooters that muck about with replacing framework.jar and such will need to be updated accordingly with patches for the new binaries.
Please don't post general discussion topics in Development. It's only for sharing development you're working on.
Thanks
AvRS
jeff_kz said:
A quick comparison between the published 1.2.0 and the extracted 1.2.0 factory.zip from the UK nooks shows that the system files are identical between the two systems, with the only differences being in non-application spots like build.prop definitions, boot/shutdown images, dictionaries, license agreements, and the wifi config uses AT&T instead of B&N hotspots.
From experience, the 1.1.5 rooted uRamdisk works just fine with 1.2.0, so any minimal rooting methods for 1.1.5 will continue to work with 1.2.0. Rooters that muck about with replacing framework.jar and such will need to be updated accordingly with patches for the new binaries.
Click to expand...
Click to collapse
So, would uRamdisk_wireless_adb_init_1.1_1.1.2.zip work for NST 1.2?
I'm not a noob when it comes to rooting but with this new device NST I'm wondering what are the differences in these two root methods. I've read through both and have the necessary files for both downloaded to my computer already. As of right now, I'll be using Nookmanager. Are there any features I'd be missing using this as opposed to Noogie?
Answers to my question are appreciated... along with any other useful info you care to throw in.
TIA
*Brand new Nook ST with the latest v1.2 update installed*
Hi,
Welcome to the B&N Nook Touch Help Thread!
Thanks so much @[color=black]undercover[/color], @[color=green][i]immortalneo[/i][/color] and @[color=green][i]dagger[/i][/color] for giving me the idea to create a help thread, and thanks so much @[color=purple][i]malybru[/i][/color] for the idea of a device-specific help thread and the outline of this thread (check out his [HELP THREAD] Galaxy S4 | Ask any question | Noob friendly.).
Barnes and Noble Nook Touch variants
This thread deals with all three Nook Touch models.
Nook Simple Touch
Nook Simple Touch with GlowLight
Nook GlowLight
I would highly recommend that you read entirely through this thread's OPs before posting anything on XDA.
Whatever question you ask, you will either get a straight-out answer or get pointed in the right direction. This is a noob-friendly thread; please, act like it and don't flame new users! If you abuse newcomers, your post will be reported.
The 10 Golden Rules
Please follow these rules before and during your question post.
Don't act rudely toward other members.
Do your best to state your question clearly and concisely; don't give us a memoir of your life.
Research your question before asking it here - if a simple Google search is all it takes to solve your problem, please, do it yourself!
Please try to only ask one question at a time.
Proofread your question before posting it, and use your best grammar and spelling.
Look at the Useful Links before posting - you might find what you need there!
Avoid PMing and/or emailing users your questions - just stick to posting in the thread, please.
Don't forget that the people who help you do it voluntarily, and have no obligation to assist.
If you find a solution yourself, make sure to edit your question post to display that your problem is solved.
If the above occurs, please feel free to share your solution with others, as well.
Thanks @[color=black]_JKay_[/color] for the idea of a "Top 10 Rules" list.
Hall of Fame
The users who have assisted people in this thread.
@NOOKIE (me)
@nivieru
@OverByter
@nmyshkin
@David0226
@kazikas
If you'd like your name on this list, please shoot me a PM, and I'll look into it.
If you like the thread, please consider rating it.
That's all for now. Enjoy!
If you find someone's post useful, please make sure to click the "Thanks!" button in the bottom-right corner of their post.
Useful Links
All of the Nook Touch threads below are for the Nook Simple Touch (with GlowLight) with firmware 1.2.1 unless specifically stated otherwise.
Important Threads
• Hacking the new Nook GlowLight - @Edgur - Development and discussion thread for hacking the new Nook GlowLight
• [Guide][NST] Parental control over web browser - @thenookieforlife3 - Tutorial on how to disable hidden web browser for parental control
• [Guide][1.2.1] Mounting USB Devices - @thenookieforlife3 - Extensive tutorial on how to mount USB devices to the Nook Touch
• Guide/HowTo/Tips'nTricks - The perfect Nook Simple Touch Setup w/ battery optimization - @jam_dev - Instructive on how to optimize the Nook Touch's battery life
•
Quick & useful links to Kernels / ROMs / Great apps
- @TheChouffy - List of kernels, apps, ROMs and useful commands
• [Solution] Yet another way to unbrick: unplug the battery for a while - @Aqq123 - Self-explanatory title
Apps
• Temblast Android Apps - @Renate NST
• [APP][NST][NSTG][1.2.x]NTGAppsAttack - Google Apps Installer Addon For NookManager - @straygecko
• E-paper: Simple drawing app - @marspeople
• [APP][5/3/14] ScreenshotSaver - keep reading while nook sleeps - @nivieru
• NoRefresh enabler - @bardo8430
• [APP] NookCalc - @sega dude
Rooters
• [Root] NookManager - graphical rooter for 1.2.x and beyond - @jeff_kz
• [NTG][1.2]GlowNooter 1.12.25 - @GabrialDestruir
ROMs
• [NST/NSTG][ROM] Tweaked Modded ROM [Feb16] - @pinguy1982
• [NST/NSTG][ROM] 1337 ROM [Nov. 6] - @yattaro, @thenookieforlife3
Kernels
• [Kernel] OC to 1100Mhz and linaro gcc 4.7 (New version with fast display mode) - @guevor
• [NSTG][Kernel] Multitouch/USB Host Kernel + uRamdisk - @thenookieforlife3
Themes
• [NST/NSTG][Theme] Status Bar Modification [Sept. 17] - @thenookieforlife3
Tools/Utilities
• NoRefreshToggle CWM Install + SuperUser CWM Install + init.d+busybox CWM Install - @pinguy1982
Other Mods
• Fix for a rattling power button - @Tharg0r
• Changing your WiFi MAC address - @dumalkin
Want your thread on this list? Shoot me a PM and I'll look into it.
can't re-register: help please
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1675706 and successfully rooted and installed android on my new NST Glowlight. Sadly, I didn't take a back-up image of the device before rooting.
After I got it working I decided I would like to use my main Google account rather than the alternate one I had used, both for Barnes and Noble and for Android on the device. I thought that I could delete my account from the device and start again, so I used the trick of resetting the device by holding down the lower left and right page turn keys for 30 seconds then choosing to reset to factory settings.
Since doing this, every time I attempt to re-register with Barnes & Noble it tells me "ERROR Sorry we're having trouble setting up your Nook, please shut down your device and try again". I have tried using Clockwork Recovery to wipe all the partitions it can access. I went to the Barnes & Nobles site to see if I had a device registered and although I have an account there with the Gmail address I used it says there is no device registered, so I can't "de-register" from there.
I tried the hold down the power button for 15 seconds after the screen flashes black and repeat six times, and nothing doing there.
Suggestions appreciated. Thanks!
@dc72,
Well, you have a couple of options here.
First, if you don't absolutely need to have B&N on your Nook, you can bypass the sign-in step by holding the top-right hard button and sliding your finger right-to-left across the top of the screen at the "Welcome to Nook Simple Touch with GlowLight" screen, pressing "Factory", holding the top-right hard button and tapping the bottom-right corner of the screen at the "Factory" screen, and tapping "Skip Oobe".
Second, if you do need B&N, try using the NookManager "Restore factory.zip" feature to factory-image-wipe your Nook.
:good:
Thank you!
Brilliant! The first procedure got me in to the ereader. So I know I can reinstall android now and bypass B&N.
Ideally I would like to have it as it was out the box again though. I don't have a back-up image as yet and because my device is now rooted I was not sure that NookManager would be able to create a clean one.
I don't want to mess things up any further than I have, so can you confirm that in my particular scenario, on the rooted NST Glowlight, I can create and restore a Factory.zip?
I was under the impression that since I have rooted I can no longer create a factory image. I will await your investigation and response before meddling further. Thank you!
EDIT: Actually I'm sure you have already thought of all that, so I'm going to trust you and go ahead with your suggestion to use Nookmanager. I'm sure it will work exactly as described! Thank you so much!
EDIT 2: I don't actually need B&N at all and would kind of rather not have them pushing books at me I have no interest in etc, so thank you greatly for the method to bypass that! Can you tell me will I be able to install 1337 rom from this thread now with my NST Glowlight in it's current state? I'm a bit reluctant to install CWM over the top of the existing recovery system so would try it from the micro SD I think.
http://forum.xda-developers.com/nook-touch/development/1337-rom-t2931567
dc72 said:
Brilliant! The first procedure got me in to the ereader. So I know I can reinstall android now and bypass B&N.
Ideally I would like to have it as it was out the box again though. I don't have a back-up image as yet and because my device is now rooted I was not sure that NookManager would be able to create a clean one.
I don't want to mess things up any further than I have, so can you confirm that in my particular scenario, on the rooted NST Glowlight, I can create and restore a Factory.zip?
I was under the impression that since I have rooted I can no longer create a factory image. I will await your investigation and response before meddling further. Thank you!
EDIT: Actually I'm sure you have already thought of all that, so I'm going to trust you and go ahead with your suggestion to use Nookmanager. I'm sure it will work exactly as described! Thank you so much!
Click to expand...
Click to collapse
@dc72,
Glad my suggestions helped!
One thing you need to understand, though - factory.zip is not something that can be created or modified. Factory.zip is the original factory image that your device came with out-of-the-box.
Backups are the things that can be created and restored. You can create a backup absolutely any time, even if your device is rooted. In fact, creating a backup when you first root is a great idea, because if something messes up in the future, you can restore the backup that's already rooted, and you won't have to go through the rooting process all over again.
EDIT - Yes, you most certainly can install 1337 ROM over your current rooted state. You will need to just follow the installation instructions to the letter, and then you'll be good to go.
So to install 1337 I have to install CWR to the actual Nook? Considering that with your help the standard recovery has pulled me out a hole I'm not sure I want to loose that at this point.
Can 1337 be installed using CWR from SD, what is the reason it's advised to install it to the Nook directly, and can the NST Glowlight still be reset to factory the way you directed me earlier after following the current 1337 install instructions?
Much appreciate your help and instruction!
dc72 said:
So to install 1337 I have to install CWR to the actual Nook? Considering that with your help the standard recovery has pulled me out a hole I'm not sure I want to loose that at this point.
Can 1337 be installed using CWR from SD, what is the reason it's advised to install it to the Nook directly, and can the NST Glowlight still be reset to factory the way you directed me earlier after following the current 1337 install instructions?
Much appreciate your help and instruction!
Click to expand...
Click to collapse
It doesn't matter whether or not CWM is installed on your NST - you just need to be able to boot into it, which, of course, can be done by simply writing the image to the sdcard, turning off the Nook, plugging the sdcard into the Nook, and turning the Nook back on. Installation is recommended, but optional.
The Nook can be factory-image-reset using the NookManager method whether or not CWM is installed as the default recovery. FYI, I personally also have an NST GlowLight, and I have had CWM installed on it for many months. It's much better than the stock recovery.
You're a star! I will take your advice and go for the 1337 install with CWM installed on the Nook. I also have a Kobo touch with android installed on it, and really like the interface they have used. It works really well! I got the NST Glow for the light and the text looked clearer in the shop... Looking forward to trying the 1337 upgrade! Big thanks!
I just purchased nook glowlight new.
I cannot find what version it is (is not listed in the box).
B&N online also keeps the version number obscure.
Can't find out how to find the version in the settings.
It has the white frame. have some questions prior to my giving up and returning.
.1. How do I find out what the model number is?
(assume it is the BNRV500 but am not sure).
2. most of the memory I find out after purchased is reserved for B&N downloads (2 gb) so there is only .5 gb for my own personal supply.
If I cannot root to unlock the 2 gb, I will likely return the thing. Can I unlock the memory via rooting, or is there another way to do this?
3. How do I root the thing (if it will unlock the memory).
Thanks
11,000th post in the Nook Touch General forum!
@leiko49,
Answers to your questions in red.
I just purchased nook glowlight new. Good choice!
I cannot find what version it is (is not listed in the box). If you mean the software version, it's 1.3.1.
1. How do I find out what the model number is?
(assume it is the BNRV500 but am not sure). I have an idea, but I don't know for sure. Can you tell me if there's a Device Info page and/or an About Your NOOK page?
2. Can I unlock the memory via rooting, or is there another way to do this? I think this has been achieved before, but I'm not 100% sure. If so, it's probably beyond my level. Search these forums a bit.
3. How do I unroot the thing (if it will unlock the memory)? Unrooting can be achieved by a simple factory reset.
Thanks
unlocking memory
I have the BNRV500
Will rooting this unlock the memory?
Thanks!
Is it possible to use the current screen as the sleep wallpaper? As in, instead of displaying a wallpaper when the Nook automatically goes to sleep, simply show the last static image on the device. For example, you're reading a book and you put the book down for a few hours. When you come back the last page is still on the screen, but the nook is asleep. You don't have to wake it up to finish reading the page/map/flashcard etc. One of the primary benefits of e-ink is that you can have static images displayed indefinitely without additional battery drain, it would be nice to take advantage of this instead of just using it to display standard wallpapers.
@leiko49, no, rooting your Nook Glow will not free up any memory - rather, it will take up more!
jun127 said:
Is it possible to use the current screen as the sleep wallpaper?
Click to expand...
Click to collapse
This can be achieved in two ways (thanks, @nivieru!):
• This app, which takes a screenshot every 01:50 and uses it as the screensaver; or
• Editing /system/framework/services.jar to not use the screensaver when the Nook sleeps, which is discussed here.
jun127 said:
Is it possible to use the current screen as the sleep wallpaper? As in, instead of displaying a wallpaper when the Nook automatically goes to sleep, simply show the last static image on the device. For example, you're reading a book and you put the book down for a few hours. When you come back the last page is still on the screen, but the nook is asleep. You don't have to wake it up to finish reading the page/map/flashcard etc. One of the primary benefits of e-ink is that you can have static images displayed indefinitely without additional battery drain, it would be nice to take advantage of this instead of just using it to display standard wallpapers.
Click to expand...
Click to collapse
Hi jun, there are two ways to achieve this,
the first is with this app, that takes a screenshot every 110 seconds and makes it the screensaver.
the second is by making the screensaver invisible, which is a bit more complicated than installing an app. It is detailed in this thread
thenookieforlife3 said:
(snip)
Unrooting can be achieved by a simple factory reset.
Click to expand...
Click to collapse
Hi there, First, nice job creating this useful thread. :good: I'll thank and like in a min...This is not my device and I'm trying to help someone out. My question to clarify, if I may:
Since simple factory reset unroots, by using the factory.zip Restore via Nook Manager, am I all set for a warranty claim? She had a custom launcher on here, with Kindle reader and other apps, obviously superuser in there, etc. I went through factory.zip via Nook Manager, and the device is reset. Like, "Hi, welcome to Nook. Press this button to begin tutorial..."
Since this device isn't familiar to me, I have to ask if I'm missing something. On some devices there's more to do, things to "re-lock" and all that. Using factory.zip, has the superuser app been wiped, and anything else that indicates tampering is removed... so this should be all set for warranty return? Thanks in advance. :highfive:
Edit: @thenookieforlife3 - I just noticed that your goal is to join the RC team. Good effort!
erikalin said:
Hi there, First, nice job creating this useful thread. :good: I'll thank and like in a min...This is not my device and I'm trying to help someone out. My question to clarify, if I may:
Since simple factory reset unroots, by using the factory.zip Restore via Nook Manager, am I all set for a warranty claim? She had a custom launcher on here, with Kindle reader and other apps, obviously superuser in there, etc. I went through factory.zip via Nook Manager, and the device is reset. Like, "Hi, welcome to Nook. Press this button to begin tutorial..."
Since this device isn't familiar to me, I have to ask if I'm missing something. On some devices there's more to do, things to "re-lock" and all that. Using factory.zip, has the superuser app been wiped, and anything else that indicates tampering is removed... so this should be all set for warranty return? Thanks in advance. :highfive:
Click to expand...
Click to collapse
Great to have an RC in here!
First of all, thanks for the nod - I do try to help everybody I can with this device, as it's my specialty.
To answer your question, if you execute the "Restore factory.zip" NookManager feature, it very literally doesn't just wipe the device - it restores the entire device to the image it came with from the factory, hence "factory.zip". Since, of course, when it came off the assembly line, the Nook had no Superuser or root mods of any kind, the Nook is 100% back to regular, and is all set for a warranty claim.
On the subject of the warranty claim, however… I just hope B&N is still accepting NST devices. They stopped selling them a while back. Just keep this in mind so that you're not too disappointed when/if the lady at the help desk says "Oh, I'm sorry, but we don't accept Nook Touches anymore."
Hope this helps!
EDIT - @erikalin, thank you for the RC encouragement. :good:
thenookieforlife3 said:
On the subject of the warranty claim, however… I just hope B&N is still accepting NST devices. They stopped selling them a while back. Just keep this in mind so that you're not too disappointed when/if the lady at the help desk says "Oh, I'm sorry, but we don't accept Nook Touches anymore."
Hope this helps!
Click to expand...
Click to collapse
Thanks for confirming. Yeah, I talked with the girl at the desk of the local B&N by phone re: warranty claim. It's all set - they just need to get it in hand, thus the restore. Since I don't know this system at all, just wanted to see that I wasn't overlooking anything. Good luck XDA-ing. :highfive:
Unfortunately the ONLY way to get a NST with/without glolight from B&N is through warranty exchange, when I did it a few months back I received one in a sealed certified pre owned box that appeared brand new without a single mark on it and the second one was in fact a sealed brand new device.
OB
Sent from my SPH-D710VMUB using Tapatalk 2