Classic Worth Rooting?

Noah98 · 06-10-2011, 01:58 PM

Is the classic nook worth rooting? I have an older serial number model (3g), so the process seems pretty simple.

How stable is the current custom firmware compared with the 1.5 official? Also, are there still battery drain problems? That's one of the reasons that I never rooted in the past. What are the best new apps? Trook looks really cool, but I'm not sure if anything else is worthwhile.

I'd like to breathe a little more life into my old faithful ereader, but I want to get some advice as to whether or not it is worth it.

chas0039 · 06-11-2011, 08:40 AM

I have a retired nook with 1.5 and the 2.5.1 softroot and all is well. You still need to get the latest nookLibrary but the battery issues were addressed. I can't remember what needed to be off as it was a long time back, but it works. Watch out for the 1.6 update, it is buggy. I would almost go back and get the hack which blocks updates as there is nothing more coming and 1.6 could well crash the softroot.

Noah98 · 06-11-2011, 10:00 AM

Quote:

Originally Posted by chas0039

I have a retired nook with 1.5 and the 2.5.1 softroot and all is well. You still need to get the latest nookLibrary but the battery issues were addressed. I can't remember what needed to be off as it was a long time back, but it works. Watch out for the 1.6 update, it is buggy. I would almost go back and get the hack which blocks updates as there is nothing more coming and 1.6 could well crash the softroot.

Thanks for the response!

So, I'm not sure if I'm understanding the process completely:

http://nookdevs.com/Softroot

1. Roll back the firmware (I'm currently at 1.5)
2. Install the custom firmware
3. Replace nookLibrary (Do I just adb install the 1.7 version, and also adb install the Nook Sync app?)
4. Block updates:
adb the following command (1.3):

<code>adb shell rm /system/app/FirmwareUpdateService.apk</code>

Am I missing anything? Also, will I lose all of my books/media when I roll back the firmware, or will everything still be there? It doesn't mention backing up your library.

chas0039 · 06-11-2011, 01:14 PM

I think you pretty much have it, although I did it a long time ago. Check here to see if there is anything else you want. I used Android Commander to do my installs but I remember ADB was essential in any case. Also, a lot of the time, the new install won't work for apps, so sometimes you need to delete and then install. Never delete the main app, the Launcher or you have nothing to use to get back a new Launcher. I always kept all my books on an SD card; you should assume you will lose everything on the internal memory.

I just removed the FirmwareUpdateService.apk myself with Android so you have that step.

I think you are OK. Make sure your SD card is fat 32. and don't mix up the bravo update files.

As I look at the apps, I seem to recall that WiFiLocker was the culprit responsible to draining the battery. Something about a default that turned it on rather than off, so I would delete that. When I did, the problem went away. Once you have the new Launcher in, deleting is easy, they never tell you about this one, you hold down an icon and the "add/ delete" overlay comes up.

chas0039 · 06-11-2011, 10:24 PM

I just took a look at nookLibrary 0.1.7 and it looks terrible. It seems to be unable to deal with authors and the title now includes the epub extension. If you want the 0.1.3 which seems to be the last version without bugs, send me a PM with an email and I will send it to you.

apastuszak · 06-17-2011, 08:04 AM

Instead of nook Library, I highly recommend File Browser by Nomad. I posted about it here: https://www.mobileread.com/forums/sho...d.php?t=130328

geistjaeger · 07-09-2011, 10:06 AM

The softroot process that places 2.5.1 on the nook classic is very stable (I would still heed the warnings about nook serial numbers--e.g. newer nooks have a possibility of getting "bricked"). One interesting side note, though... I tried to disable the auto-update capability (narrowly avoiding the B&N 1.6 firmware update debacle), but found that when B&N posted the 1.7 update, that my nook went through the process of updating to 1.7... ARRRGGGGHHHH!!!

But, it seems all is well...nook status reports it has 1.7, and it still operates and has the software associated with the rooted nook. So, it appears that the 2.5.1 root is more stable than originally thought.

On an another note, "mystical" draining of the battery does seem to have been a thing of the past--as long as you don't purposely turn on and leave the wifi on, say by using WIFI-LOCKER, which I never have, or by using GREADER (a google-reader app: have to report to the author of that app that particular ill side-effect). One thing I've found is that I'm unable to get ADB_OVER_USB to work in LINUX, but am able to WIRELESS ADB (i.e. adb connect <your nook's wireless ip address>:5555). In finding that out, I stumbled upon an unintended wireless locker that B&N built into the nook in the first place: the WIFI button. When you select that button, it brings up the wireless status and network selection screen, selecting the network you are connected to will show the status of your connection (including the ip address your nook is using)...and incidentally, keep your wireless on your nook alive until you go back to the home screen or turn off the nook.

Earlier poster said he uses Android Commander, but the DDMS tool will also provide a graphical view to interact with an Android device, instead of the command-line nature of ADB--haven't personally used Android Commander, so I can't say which is necessarily easier to use.

chas0039 · 07-09-2011, 10:35 PM

Quote:

Originally Posted by geistjaeger

....One interesting side note, though... I tried to disable the auto-update capability (narrowly avoiding the B&N 1.6 firmware update debacle), but found that when B&N posted the 1.7 update, that my nook went through the process of updating to 1.7... ARRRGGGGHHHH!!!.

What did you do to block the update? Did it fail or did you remove it and then got caught? I was under the impression that removing the file mentioned at nookdev stopped the updates for good.

geistjaeger · 07-10-2011, 09:03 PM

I did in fact do what I thought was required to remove the file suggested by nookdevs, and so I was completely surprised when the update took place. But as I said, there have been no ill effects...but then again, as you've no doubt seen, details on 1.7 are sparse at best.

chas0039 · 07-10-2011, 09:39 PM

Thanks much. I'll keep my WiFi off from here on out.

06-10-2011, 01:58 PM	#1
Noah98 Eccentric Posts: 510 Karma: 342150 Join Date: Dec 2009 Location: Florida Device: The nook, ipad 3, Kindle Fire HD (8.9), Kindle Paperwhite	Worth Rooting? Is the classic nook worth rooting? I have an older serial number model (3g), so the process seems pretty simple. How stable is the current custom firmware compared with the 1.5 official? Also, are there still battery drain problems? That's one of the reasons that I never rooted in the past. What are the best new apps? Trook looks really cool, but I'm not sure if anything else is worthwhile. I'd like to breathe a little more life into my old faithful ereader, but I want to get some advice as to whether or not it is worth it.

06-11-2011, 01:14 PM	#4
chas0039 Sceptic Posts: 573 Karma: 73436 Join Date: Jul 2010 Location: The Lake Device: rooted Nooks, retired. JetBook Lite, Kindle 3, 4, Kobo Nia, Libra H2O.	I think you pretty much have it, although I did it a long time ago. Check here to see if there is anything else you want. I used Android Commander to do my installs but I remember ADB was essential in any case. Also, a lot of the time, the new install won't work for apps, so sometimes you need to delete and then install. Never delete the main app, the Launcher or you have nothing to use to get back a new Launcher. I always kept all my books on an SD card; you should assume you will lose everything on the internal memory. I just removed the FirmwareUpdateService.apk myself with Android so you have that step. I think you are OK. Make sure your SD card is fat 32. and don't mix up the bravo update files. As I look at the apps, I seem to recall that WiFiLocker was the culprit responsible to draining the battery. Something about a default that turned it on rather than off, so I would delete that. When I did, the problem went away. Once you have the new Launcher in, deleting is easy, they never tell you about this one, you hold down an icon and the "add/ delete" overlay comes up. Last edited by chas0039; 06-11-2011 at 01:18 PM.

07-09-2011, 10:06 AM	#7
geistjaeger Junior Member Posts: 2 Karma: 10 Join Date: Jul 2010 Device: Nook	Rooting the nook classic and updates The softroot process that places 2.5.1 on the nook classic is very stable (I would still heed the warnings about nook serial numbers--e.g. newer nooks have a possibility of getting "bricked"). One interesting side note, though... I tried to disable the auto-update capability (narrowly avoiding the B&N 1.6 firmware update debacle), but found that when B&N posted the 1.7 update, that my nook went through the process of updating to 1.7... ARRRGGGGHHHH!!! But, it seems all is well...nook status reports it has 1.7, and it still operates and has the software associated with the rooted nook. So, it appears that the 2.5.1 root is more stable than originally thought. On an another note, "mystical" draining of the battery does seem to have been a thing of the past--as long as you don't purposely turn on and leave the wifi on, say by using WIFI-LOCKER, which I never have, or by using GREADER (a google-reader app: have to report to the author of that app that particular ill side-effect). One thing I've found is that I'm unable to get ADB_OVER_USB to work in LINUX, but am able to WIRELESS ADB (i.e. adb connect <your nook's wireless ip address>:5555). In finding that out, I stumbled upon an unintended wireless locker that B&N built into the nook in the first place: the WIFI button. When you select that button, it brings up the wireless status and network selection screen, selecting the network you are connected to will show the status of your connection (including the ip address your nook is using)...and incidentally, keep your wireless on your nook alive until you go back to the home screen or turn off the nook. Earlier poster said he uses Android Commander, but the DDMS tool will also provide a graphical view to interact with an Android device, instead of the command-line nature of ADB--haven't personally used Android Commander, so I can't say which is necessarily easier to use.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Classic Classic: Rooting still worth it?	sangahm	Barnes & Noble NOOK	10	04-24-2011 09:56 AM
What is rooting?	Belle2Be	Nook Developer's Corner	23	02-11-2011 07:05 PM
Rooting Help!	penworth	Nook Developer's Corner	8	01-20-2011 07:09 PM
Rooting?	PomMom12	Nook Developer's Corner	4	12-24-2010 01:52 PM
Classic Rooting help	Care	Nook Developer's Corner	5	08-02-2010 10:06 PM

06-11-2011, 08:40 AM	#2
chas0039 Sceptic Posts: 573 Karma: 73436 Join Date: Jul 2010 Location: The Lake Device: rooted Nooks, retired. JetBook Lite, Kindle 3, 4, Kobo Nia, Libra H2O.	I have a retired nook with 1.5 and the 2.5.1 softroot and all is well. You still need to get the latest nookLibrary but the battery issues were addressed. I can't remember what needed to be off as it was a long time back, but it works. Watch out for the 1.6 update, it is buggy. I would almost go back and get the hack which blocks updates as there is nothing more coming and 1.6 could well crash the softroot.

06-11-2011, 10:24 PM	#5
chas0039 Sceptic Posts: 573 Karma: 73436 Join Date: Jul 2010 Location: The Lake Device: rooted Nooks, retired. JetBook Lite, Kindle 3, 4, Kobo Nia, Libra H2O.	I just took a look at nookLibrary 0.1.7 and it looks terrible. It seems to be unable to deal with authors and the title now includes the epub extension. If you want the 0.1.3 which seems to be the last version without bugs, send me a PM with an email and I will send it to you.

06-17-2011, 08:04 AM	#6
apastuszak Evangelist Posts: 436 Karma: 125599 Join Date: Feb 2011 Location: Bensalem, PA Device: Kindle Paperwhite, nook Glowlight Plus, Apple iPad Air 2	Instead of nook Library, I highly recommend File Browser by Nomad. I posted about it here: https://www.mobileread.com/forums/sho...d.php?t=130328

07-10-2011, 09:03 PM	#9
geistjaeger Junior Member Posts: 2 Karma: 10 Join Date: Jul 2010 Device: Nook	I did in fact do what I thought was required to remove the file suggested by nookdevs, and so I was completely surprised when the update took place. But as I said, there have been no ill effects...but then again, as you've no doubt seen, details on 1.7 are sparse at best.

07-10-2011, 09:39 PM	#10
chas0039 Sceptic Posts: 573 Karma: 73436 Join Date: Jul 2010 Location: The Lake Device: rooted Nooks, retired. JetBook Lite, Kindle 3, 4, Kobo Nia, Libra H2O.	Thanks much. I'll keep my WiFi off from here on out.

Advert

Advert