MobileRead Forums - View Single Post

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.

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.