[Q] Can't Side Load Apps on Root NST Glow - Nook Touch General

I recently rooted my Nook Simple Touch Glow and when I try to side load apps through dropbox I get an error "Install Blocked; For security reasons you phone is set to block installation of applications not sourced in the Android Market."
I've read up and there should be a check box in the applications menu that allows unknown sources. The trouble is there is no applications menu.
Any idea on how to fix this?
Thanks in advance!

If you have sqlite3 on your desktop or your Nook, you can just do:
Code:
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';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db

Sqlite
I haven't used Sqlite before. I downloaded it. Do I just run the text you posted in the dos box?
Also, do I need to have the nook attached through usb?

Well, you have to have ADB working however you use ADB.
That's either WiFi or USB.
The quoted code is normally what you enter.

check in dos box that you have sqlite3 command available. Also you need working android debug bridge (adb) working, through wifi or usb, in your case it would probably be through wifi. I do not recommend you to continoe unless you learn something about adb and make it work. (search forum or use google)
the rest is piece of cake. first (adb) command from #2 downloads one database from nook. Another 3 commands opens that database locally, changes the security setings that enables installation of non-market application and quits sqlite3 client.
last command uploads the changed database back to nook.

ADB?
Thanks for getting back to me. Unfortunately, I really don't know what ADB is.
I haven't used any of these tools. Can you give me a little more detail? I'd hate to make a mistake and screw something up.
Thanks again!
Mark

Sqlite
Thanks for the instructions. I was able to turn on the ADB bridge using adbWireless and connect the device.
I'm confused about the command line in SQLite3. I entered everything as listed, but nothing happens. I don't want to copy over the settings.db until I know it has been changed.
What should SQLite say if I have entered in the command properly?
Thanks again

Code:
sqlite3 settings.db
update secure set value=1 where name='install_non_market_apps';
select value from secure where name='install_non_market_apps';
.q
As you can see I have added one 'select' command into sql section. If your database has been updated properly, select command should print new value 1 (before zero).
I have written this command right now, don't have a chance to test it but it should work.. at least it cannot screw up anything.

Sqlite
I'm entering everything as is and either I get
...> with nothing after it
or
Error: near "sqlite3": syntax error.
In either case, the select command does not tell me if it is updated.
Again, sorry for asking so many times. I'm close!!

Sqlite
I figured out what I was doing. I opened the SqLite window separately when it should have all be in the one cmd window.
So what exactly did this do? I keep getting the same error message that it can't install non market apps. Is there a menu setting I should change?
Thanks again

Got it
Just rebooted and now it's working. Thanks!!

A simpler way to do this, assuming you've used something like GlowNooter and is to go into Nook Color Tools and uncheck and recheck the Non-Market Installs. This will allow you to sideload.

Related

[Q] allow mock locations

Our nook touch's don't have the ability to allow mock locations for using tetherGPS.
It is usually found Settings->applications->development but we don't have Applications tab under settings.
Any ideas how I can get a touch to allow mock locations? Rooted running touchnooter.
Or, since running 2.1 it is host usb so that can't receive usb data, I have to use serial data. I have found serial pins under the sd card slot. Anyone have any ideas to see if touchnooter has the gps libraries? Yep, I'm a noob so maybe not even asking it properly.
Any feedback on getting GPS to work would be appreciated! thanks
lolokai said:
Our nook touch's don't have the ability to allow mock locations for using tetherGPS.
It is usually found Settings->applications->development but we don't have Applications tab under settings.
Any ideas how I can get a touch to allow mock locations? Rooted running touchnooter.
Click to expand...
Click to collapse
Assuming you have rooted your N2 and know how to use adb with it:
Code:
#adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
#sqlite3 settings.db
Code:
sqlite> update secure set value=1 where name='mock_location';
sqlite> .q
Code:
#adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
#adb reboot
To verify it working you can fetch an app called "My Fake Location" from the market and use it to set your mock location
Just tested the above solution with TetherGPS Lite and my X10 as server and it worked just fine.
thank you ros87
I can't get my laptop to recognize my NT yet but I will figure that out.
So basically, I run adb and paste that code for first section. ADB pulls that file.
I then run? sqlite to get that variable changed, then push the file back? I am researching all I can but this is all new to me so thanks again for your feedback.
I found the easiest way to get laptop to recognize the nook by using ADB Wireless app, way simpler than messing with usb drivers etc.
When I ran the first pull command, it says: remote object does not exist '/data/data........
In sqlite3 I tried to change the values and it came back with:no such table: secure
So it seems it doesn't have that code. Back to square one. Touchnooter seems to run nook color so any code would be that of nook color (I think).
Any idea on how to proceed now? Can I create table and then push it?
lolokai said:
In sqlite3 I tried to change the values and it came back with:no such table: secure
So it seems it doesn't have that code.
Click to expand...
Click to collapse
This is not possible. secure table is the same table where you enable non-market install (e.g. with touchnooter). There has to be something wrong in the command you have use.
cceerrtt said:
This is not possible. secure table is the same table where you enable non-market install (e.g. with touchnooter). There has to be something wrong in the command you have use.
Click to expand...
Click to collapse
I just read this:To use sqlite3 locally, instead of within a shell, pull the database file from the device and start sqlite3:
Copy a database file from your device to your host machine:
adb pull <database-file-on-device>
Start the sqlite3 tool from the /tools directory, specifying the database file:
sqlite3 <database-file-on-host>
So since I couldn't pull the database as I mentioned, that is why sqlite3 coulnd't find the table.
Any ideas on why I can't pull the database?
Is your devices properly connected? Do you see nook in "adb devices" output?
Are you able to pull any other file?
Is the filepath in the command correct?
Why don't you copy & paste the terminal log? Much easier than let us guess what's wrong.
Update: another option - you should be able to use boot with noogie sdcard and copy that db file directly to your computer.
Device is connected. I will research how I can copy terminal log and paste that here. I was typing the post below when I saw your post but will work on terminal log.
If the goal is to change a value in sql, I just downloaded an app called SQLite Editor on the NT and changed the mock location variable from 0 to 1 there. I can see why it didn't pull the code in previous tries as i was not there on my system. The route for anyone else trying to get this done via SQLite:
settings storage>settings.db/secure
As a non-programmer flailing through this I found adb wireless app much easier than screwing with usb stuff which I never did get ADB (win7) to recognize device via command prompt. Also the SQLite editor is much easier than messing with ADB. Again, these are noob workarounds for someone who doesn't know that much about android stuff.
Alas, I still can't get TetherGPS to work. It says from the widget I can allow mock locations and turn on GPS but there are no menu items I can see from the widget. Also, I put in the IP address I used from ADB wireless- is that what I should use on both server and client? I did run a GPS toggle app and turned on GPS, no idea what that does but it didn't FC and stays 'on'. No response from Compton Soft who made the app.
Any ideas? Paypal ready for whomever can get me closer to running GPS on a Nook Touch, I might be able to get it but at this rate, it will take a long time.
I got the NT to see the GPS but it wasn't updating. I was using TetherGPS lite and when I bought TetherGPS, it showed some GPS data.
As ros87 said, My Fake Location is the way to get the NT to Allow Mock Location.
Now I have to see how to get the GPS to send data fast enough so the app I use can be of value.
I feel like the guy on the car forums who is troubleshooting the ECU but doesn't know how to change spark plugs lol. Thanks ros87 and cceerrtt!
com.android.providers.setting should be com.android.providers.settings to pull the file
Thiso said:
com.android.providers.setting should be com.android.providers.settings to pull the file
Click to expand...
Click to collapse
Thanks mate, fixed!

Trying to root but can't get ADB working

I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.
66 people have read this and nobody has any suggestions to help?
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?
Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'
juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.
Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer
If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!
I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.
Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer
OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."
ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number
Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?
First problem solved then!
Yes but follow this Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.

Installed touchnooter, no "Touch Tools" = impossible to add apps

So I used the touchnooter instructions in the developers forum to root my Simple Touch, everything went smoothly until I went to install programs from the Amazon store and after downloading I received the "For security reasons" message that said my device blocked applications not sourced from the Market. I searched around for how to undo this setting, and it said to open an application called Nook Touch Settings and change the setting to allow outside applications. The problem is that the Settings application is not on my device. Is there something wrong with the ROM or my installation? Is this something that can be fixed without starting all over again?
Thanks.
There are two solutions:
Load Nook Touch Tools from somewhere and use it.
-or-
Get ADB on your desktop and sqlite3 on either your Nook or desktop.
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
sqlite> update secure set value=1 where name='install_non_market_apps';
sqlite> .q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db

[Q] help with keyboard

After rooting my NST, I'm having trouble with the keyboard. It has no period key, and without a period, I can't give my email address.
To try to solve the problem I installed a different keyboard - first I tried go keyboard but could not enable it, next I tried the Swiftkey x keyboard from Amazon Apps but had same problem - installs but I cannot choose the new keyboard over the native NST one. I used the choose methods according to instructions for the new keyboard.
I also tried the long press on a text enter box but that only gave the native NST keyboard without a period key. Also tried uninstalling the keyboard app, the copy/pasting it to system/app and using Nook Color Tools 'choose keyboard', but the only keyboard available is the 'android' keyboard, the new keyboard is not a choice.
Does anyone know what to do?
Also, can't search with Market - tried reinstalling vending.apk but didn't help. The search box appears, and I can enter text, but no results appear.
See in the lower right hand corner of the Android soft keyboard?
There is a question mark with two dots under it.
The bottom is a period when unshifted, the top is a question mark when shifted.
Thanks! Now it isn't that important to download a new keyboard, although I wonder why I can't get them to work.
Bob
Oh, sorry, I missed the second part.
You have to enable the keyboards that you put in.
If you have a replacement Settings.apk it might be in there under "Language & keyboard".
The code is actually in the stock Settings.apk, but they disabled it.
To do it manually, first, figure out what is the exact name of the keyboard service.
For instance GoKeyboard is com.jb.gokeyboard/.GoKeyboard
Then use sqlite3 either on the Nook or your desktop to enable it.
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update secure set value='com.android.inputmethod.latin/.LatinIME:com.jb.gokeyboard/.GoKeyboard' where name='enabled_input_methods';
update secure set value='com.jb.gokeyboard/.GoKeyboard' where name='default_input_method';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Thanks Renate,
Please bear with me with my elementary questions; I'm not a programmer and so do not have much experience with command line programs.
I've downloaded to my pc the most recent sqlite.zip, unzipped it, and ran the sqlite.exe to see what happens: a cmd window opens and is ready for line entries.
I think what you are then saying is to use adb wireless to retrieve a file from the nook, change it using sqlite on the pc, and then return it to the android.
But will sqlite be able to see the file because it will not be placed in the sqlite folder by adb?
You should already be good friends with the command line on every device.
Don't start sqlite3 out of the the blue.
Open an "MS-DOS" window, also known as a command shell.
From Windows, that's a <WindowsKey> & <R>, then type cmd.exe
Pick any directory you like.
Pull settings.db
Run sqlite3 as above in the same window.
If you put sqlite3 somewhere else, the command may look like:
Code:
E:\Where\Did\I\Put\The\Darn\Thing\sqlite3.exe settings.db
Do the SQL commands.
Push settings.db
Thanks again Renate. I have used the cmd on Windows and have a slight familiarity with it, so I'll experiment a bit and see what happens. First, I think it best to backup the nook in case of problems.
bobcdy said:
Also, can't search with Market - tried reinstalling vending.apk but didn't help. The search box appears, and I can enter text, but no results appear.
Click to expand...
Click to collapse
That is a common problem, install SearchMarket, it will do the search and bring up Market.
--
Unfortunately I still have problems with the go keyboard, and this time it is completely my fault. Following Renate's instructions about sqlite3, I was able to install the free version of the keyboard, but hated the ads that came with it. My mistake was in uninstalling the ad-ridden version when I think I should have replaced the it with my other version. After unstalling it, I tried installing the new version but was unable to do so - I've tried everything I can do to install it. Rebooted - reinstalled. No luck. Deleted the old version from the system/ap folder using root explorer, then tried reinstalling - again no luck. Tried repeating the sqlite commands - nope! etc.
Is there any way to install the new version, or it it too late?
I do have a backup made with noogie/roadkil's Disk Image and Windows xp so I could restore that image but I'd prefer not to do this.

[Q] Rooting Nook Classic (Nook First Edition)

I know that this is for second edition but I don't seen a forum for the first edition so this seems to be the closest match. Anyway I am trying to root my Nook Classic (the one with a E-ink display on the top and color touch screen on the bottom). I am following the instructions on nookdevs for rooting the Nook Classic on all hardware and firmware versions (I can't post the link here as I am new but PM me and I can pass it that way if you need). The method is that sometimes when the web browser browses a certain type of website it crashes and sometimes starts adbd and you can connect adb at that point.
I have managed to get adb to connect, pull the init.rc file, make the needed change, but when I try to push the ratc.bin file adb says it goes though but then the second command $ cd /sqlite_stmt_journals (after starting adb shell) says it is not found. So I can't go any further. ratc.bin is what gives root access long enough to push the init.rc back and without being able to run that, well I am up a creek.
Any ideas?
dob43 said:
I know that this is for second edition but I don't seen a forum for the first edition so this seems to be the closest match. Anyway I am trying to root my Nook Classic (the one with a E-ink display on the top and color touch screen on the bottom). I am following the instructions on nookdevs for rooting the Nook Classic on all hardware and firmware versions (I can't post the link here as I am new but PM me and I can pass it that way if you need). The method is that sometimes when the web browser browses a certain type of website it crashes and sometimes starts adbd and you can connect adb at that point.
I have managed to get adb to connect, pull the init.rc file, make the needed change, but when I try to push the ratc.bin file adb says it goes though but then the second command $ cd /sqlite_stmt_journals (after starting adb shell) says it is not found. So I can't go any further. ratc.bin is what gives root access long enough to push the init.rc back and without being able to run that, well I am up a creek.
Any ideas?
Click to expand...
Click to collapse
>> http://www.mobileread.com/forums/forumdisplay.php?f=209
>> http://www.the-ebook.org/forum/viewforum.php?f=44&sid=e250da1c3a4967da22dae8ca2d104ac8
Thanks osowiecki, I did find a thread on Mobile read shortly after I posted this. The other is non-english I am afraid, and sadly I only speak english.
Anyway I did mange to root my nook today. And I am posting here as I hope it will help someone in the future:
Yessssssssssssssss! I finally hacked my Nook Classic (Nook First Edition called by some)! I followed most of the instructions at http://nookdevs.com/Rooting_B&N_revision_1.4_to_1.7_on_any_hardware
I only tweeked in a few places. Here is a general list of what I did:
1. Look at the site above and grab the linked file (ratc.bin). Then go to this thread http://forum.xda-developers.com/showthread.php?t=1474956 and at the top there grab the adb + fasboot + drivers.zip. The reason I used this is because it is much smaller than the full Andriod SDK (which is over 500mb btw) and I figured this would work since it works for Nook Tablets. I didn't install the drivers or anything though. Just used adb.
2. Went with nook browser to http://nookadb.suspended-chord.info/ to crash the browser. If this should ever be down I see on the nookdevs page there is a discussion with the code that is on the crash page so you can put it on any web server and still do this procedure.
3. Once it crashed I went to cmd (comand prompt) and navigated to the folder that had the adb package I downloaded and decompressed earlier. I suggest putting this folder on your desktop for easy use. I gave the command
adb connect yournookip:5555 please note that the nookdevs instructions are not specific in that you NEED the :5555 after the IP. If it doesn't connect, keep crashing the browser by going to that page until it connect.
4. extracted the init.rc file with the command
adb pull /init.rc then edited as per the instructions on nookdevs
5. Now here is where things are different. I tried to push the ratc.bin file and while that seemed to work the commands after it didn't. It would keep saying the file wasn't there. I was cut and pasting the commands direct from the website so I don't think that was the issue. So what I did was grab the bat file at www.mobileread.com/forums/showthread.php?t=121655&page=2 by Jackr and edit it slightly removing the bit about location of adb and placed the bat in the same folder as adb on my desktop and ran it.
6. This actually worked and the bat prompted me to crash the browser again. I kept trying it took a while but as soon as I did it pushed the modifyed init.rc to the nook. The another reason why I think the bat/script is important as my nook totally froze a second after I crashed it. I think that if I was trying to paste that command manually after connecting I would still be trying lol.
7. After reboot I was fully rooted and I installed a bunch of apps from nookdevs using adb. Just make sure the apk (app file) is in the same directory as adb and use the command install nameofapp.apk
8. If you want to use nookmarket app to install files by itself then you need to:
adb connect nookIP:5555
adb shell
then type this after the #
/system/xbin/sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update secure set value=1 where name='install_non_market_apps'"
It will allow nookmarket to install apps on the fly over the net. If you ever want to turn it back off just change the value=1 to value=0 in the above command. Of course you can always use adb, but it can be handy.
Of all the apps I would definitely suggest Nooklibary and wifilocker along with Nooksync. There are several other good nook apps such as trook. Oh I should also mention that Nook Browser still works fine. I think using the batfile/script helped with that situation.
I hope this helps someone who is thinking of taking the plunge (and trying to find out HOW). I wouldn't have bothered if B&N actually continued to update the Nook Classic and add the features that we BEGGED for (and are in NookLibrary). Instead of spending time adding things we didn't like games.
I've tried a thousand times, but always get "failed to copy 'init.rc' to '//init.rc': Permission denied" so RATC must not be working. And I'm on mac, so no bat. Any ideas?
lolbutts said:
I've tried a thousand times, but always get "failed to copy 'init.rc' to '//init.rc': Permission denied" so RATC must not be working. And I'm on mac, so no bat. Any ideas?
Click to expand...
Click to collapse
I would suggest looking at the bat, and creating the equivalent in apple script. If I remember right Mac's still have that option. Another option would be to run say WinXP in emulation (with virtual box for example) and do it that way.
How to root the original Nook tablet (model number: BNRZ100)
dob43 said:
Yessssssssssssssss! I finally hacked my Nook Classic (Nook First Edition called by some)! I followed most of the instructions at http://nookdevs.com/Rooting_B&N_revision_1.4_to_1.7_on_any_hardware
Click to expand...
Click to collapse
Okay, since nookdevs.com has apparently been down for sometime now, I was checking out the mobileread.com link that was shared above and found out the info that I have been searching for to find out how to root the Nook. Be forewarned that I have not tried this yet, but I am about to, and afterwards I will post the results, I am just posting it as sort-of a guide for myself and anyone interested at this point. I will edit this post accordingly once I am successfully rooted.. Please see below for links / details.
Disclaimer: I am not responsible for any damage that is done by you to your Nook, either physically or otherwise. I am just showing you what I have researched and if you choose to follow these directions it is at your own risk.
Which Nook Device Do You Have?
click here to find out:
http://glyde.com/glydecast/how-to/which-nook-do-you-have/
Remember, this is for the first generation only (model number: BNRZ100)
Here is a visual aid that will help you find the SD card that you need to look for once you get the Nook opened up (yes, you will need to open your Nook and access the motherboard):
http://www.wired.com/2009/12/nook-torn-open-hacked-and-rooted/
How to open the Nook up:
https://www.youtube.com/watch?v=GEDqiNiQFHk
Hint: you don't need to take to front panel / bezel off, just the back section because all we need is access to the motherboard to be able to remove the internal SD card, which contains the file that we will be editing.
Finally, the info that you need to root the device (also posted below the link for quick reference, and just in case the link gets broken):
http://www.mobileread.com/forums/showthread.php?t=128210
How to root the Nook, after you figute out how to open it up:
Just you need a microSD Card reader + Linux (any linux ) !
just you should remove the System file MicroSD ( which is inside the Nook )
put it in your PC , change the "init" file with Any txt editor !
just find "service adbd /sbin/adbd" and change the "disable" to "enable" ...
you are done !
Wow I had no idea that Nookdevs went down. Thankfully I did archive all the information on that page. While the method you mentioned is great, and the best, only the earliest nook classic's had removable system SD cards. After the first batch they were soldered chips instead.
With that in mind I am posting what was contained in the link I posted before on NookDevs since it is not available on the internet archive.
------------
This method of rooting is known to work on B&N firmware revisions 1.4-1.7, on all hardware versions. Unlike the other rooting methods, this one involves an element of luck -- it takes advantage of a memory-corrupting bug in the web browser, and its success depends on the current contents of the memory which depends on more variables than we can control. As such, the method requires a little bit of (or more) patience. Warning: After this root is completed, the web browser will be irreversibly damaged.
Contents
1 Preparation
2 Enable adbd on the Nook
3 Pull and modify /init.rc
4 Getting root access
4.1 Keeping root access
5 Your rooted Nook
6 Notes
Preparation
Install Google's Android platform tools from developerdotandroiddotcom. These include many useful utilities, such as the ADB control software.
Open up a terminal to use ADB
Open a command prompt
Navigate to the directory that you installed, then go into the platform-tools subdirectory. This is where the adb executable lives.
Connect your nook to the same WiFi that your computer is on. You need direct (non-firewalled) access to the Nook's IP address to connect via ADB.
Find your Nook's IP address (How to find our your nook's IP address)
Write it down somewhere.
Enable adbd on the Nook
This is the luck portion of the root. adbd is the other half of ADB: ADB runs on your computer, and tries to connect with adbd on the nook. Once connected, you can issue commands, shuffle files, and install applications. Our final goal is to be able to start and stop adbd at will[1].
Open the Nook's web browser and navigate to the web site nookadb.suspended-chord.info. You may want to bookmark the page for a quicker access.
When you load this web page, the browser will crash. (It may automatically reload itself a few times first.) After it crashes, it might enable adbd.
Go back to the command prompt on your computer, and type:
adb connect <nook's IP>
One of two things will happen:
You will get the message unable to connect to <ip address>:5555.
In this case, restart your web browser and load the web page again (from the history or the bookmark). You may have to do this a dozen times or more, so keep at it!
You will get the message connected to <ip address>:5555.
Success!
At this point you have (temporarily) access the nook via ADB, can now enter commands on your PC for the Nook, and can move files back and forth. If you reboot the nook, adbd (the nook companion to ADB) will not be running.
Pull and modify /init.rc
If this isn't your first time through, and you have a modified copy of init.rc, skip this step.
Now that you can connect into the Nook, you will want to pull and edit the /init.rc file. This file is run when the nook turns on, and includes an option to enable adbd (disabled by default). Download the file to your PC with:
adb pull /init.rc
Open this file with Notepad (or a different plain text editor), and find the part the lines:
service adbd /sbin/adbd
disabled
Change 'disabled' to 'enabled' and save the file.
Getting root access
You got the web browser to launch adbd, but you only have the privilege level of the web browser's user - system. To install software and to start adbd when the Nook reboots, you need root access. Rage Against the Cage will give you root access. Next, you'll restart adbd, and push the modified init.rc back to the nook. After that, reboot the nook and you're done!
Download [ratc.zip].
Extract it to the same directory that adb is stored in, then go back to the command prompt:
adb push ratc.bin /sqlite_stmt_journals
adb shell
$ cd /sqlite_stmt_journals
$ /system/bin/chmod 777 ./ratc.bin
$ ./ratc.bin
(several lines of output follow -- don't do anything, a few seconds later adb will disconnect you.)
Keeping root access
If everything went well, you should have root access on the Nook. However, the Nook is now relatively unstable and may stop working at any point, so work quickly!
The nook may crash - just reboot, then restart the process from scratch. (Remember, you don't need to pull init.rc again.)
First, you need to stop your PC's ADB server. It still thinks that it's connected to the nook.
adb kill-server
Second, you need to re-establish the connection with adbd on the nook and then push init.rc file. You can do this by typing these commands[2]:
adb connect <nook IP>
adb push init.rc /
Perform the browser crash procedure again. After each attempt, check if the computer successfully transferred init.rc. If it did, you're done!
If the nook crashes before the transfer completes (so you are not able to connect to your nook), go back to "Enabling adbd on the Nook". You can skip "Pull and modify /init.rc", but do the other steps.
If the adb push gives a permission denied error, redo the "Getting root access", and try again. You may have to do this quite a few times until the whole process succeeds.
Your rooted Nook
Assuming everything worked, you now have a rooted Nook with adbd running on reboot, with root access. You should be able to establish the connection with adbd on the nook without jumping through any other hoops.
What's next? Browse the applications, and install to your heart's content.
Suggestions:
Mynook.ru Launcher A polished replacement launcher. You must replace the launcher to access additional applications with the nook.
Trook A RSS feed reader for the nook, and much more! It can install applications, too. Just go into the nookdevs feed.
NookLibrary A replacement library for the nook. If unifies sideloaded books with Barnes & Noble content, and offers other improvements.
NookMarket A program that allows you to easily install everything on nookdevs. Trook offers more functionality (imho)
Games There are a few games on the applications page.
Notes
↑ There's also a Python script to automate the process: root-nook-eink.tar.xz (Updated Jun 6 , 2011)
↑ You may want to run a script that automatically issues the following commands, reducing the chances of the nook crashing before init.rc has been pushed to it. In this case, extract this [batch file] to the same directory as ADB. Run it by typing:
push.bat
It will prompt you for your nook's IP address, then try connecting. Every few seconds, ADB will complain that it can't connect to the nook. Let's fix that.
------------------------------------------------
The above is from Nookdevs.com and I did not write it I am only posting it here as the site has went down.
I am also posting the html file that is needed to do this (although here it is in txt format). If the the site listed above ever dies you can put this on a website somewhere to use it. And the ratc.bin file needed.
And finally I am adding the apps that make rooting the nook classic worth while. The improved library definitely. Which btw are two parts, the library app and the nooksync which enables you to download from B&N directly. Otherwise you need to use the normal nook library app to download then you can read with the nookdev version. I am not sure which version of the library works best, been a while since I installed it so I included both.
Also wifilocker is great to turn wifi on/off not to mention lock it and keep the nook from going to sleep while you are connected to adb. I definitely suggest installing that as well. The others are handy. Trook can connect to calibre and download books from your desktop. The nook browser is a improved web browser for nook classic, although I never really bothered with it.
Nook notes is good for quick little notes when you don't have any other device handy. Txt reader reads txt files, not the best but it is handy. Personally I just make epubs of anything with calibre. But if you don't want to bother making a epub first, this is handy.
Hope this helps someone!
I downloaded files and rat.bin has malware in it.
I also have hard time understanding the ones that are explained above. Is there any easier way to do it? Does anybody have a good tutorial video or "fool-proof" instruction on this? I have Nook classic wifi version.
I would like to read kindle books on nook as well as the nook books. Is this even possible on this model?
Thanks for the help
kidollt said:
I downloaded files and rat.bin has malware in it.
I also have hard time understanding the ones that are explained above. Is there any easier way to do it? Does anybody have a good tutorial video or "fool-proof" instruction on this? I have Nook classic wifi version.
I would like to read kindle books on nook as well as the nook books. Is this even possible on this model?
Thanks for the help
Click to expand...
Click to collapse
Er of course rat.bin would be flagged as malware, because technically it is. You are hacking a system that is designed not to let you in. But in this case all rat.bin will do is let you in so you can get root of your own device, nothing else. No back doors for anyone else or making your device do odd things.
The problem you are having is not using rat.bin, without that you might as well not try. I also only managed to do it with a BAT file so that it would keep trying to push the init.rc RIGHT AFTER the rat.bin was used. Generally you can't type fast enough to do the push. The window of opportunity is very very small.
This does work but is tricky as the window of opportunity is very small. I tried for hours trying to get it to work, then I used the BAT file to make the push automatic and on the second try it worked. Rooting the Nook Classic is the toughest device to root that B&N made. If you have one of the really early models that has a removable internal SD card then you can pull that, made modifications (install a old version of the ROM, make a modification to init.rc), and reinstall the SD card. I forget the serial numbers of the models that this worked with, but I do know it was the first batch of Nooks B&N made. If you got yours after the first Christmas, then it is likely it doesn't have a internal SD card that you can remove. Later on they soldered them to the board.
As for reading kindle books, no. There isn't a mobi reading app that I have found, let alone kindle books with DRM. The better bet is to use Calibre calibre-ebook.com to convert your kindle books to epub. But they can't be encrypted/DRM. If they are, then you have to remove that. There are scripts for Calibre that can do it for nook and kindle. I use calibre to convert my mobi/kindle books to epub then side load them. Another benefit of rooting a nook classic, you can then browse and download wireless from your calibre library with the took app. Although I never bothered and just did the transfers via USB.
Hi!
I would like to ask for help in this case:
I followed all the instructions here, however for some reasons I wanted to install this app first using the command "adb push Home.apk /system/app" pushing the app found here: Github
Now it turns on/off, shows "Home", batter and time at the top bar, but everything else is black both the Eink screen and the touchscreen as well.
It does not connect to wifi automatically so I can't connect via ADB to switch back to the original Home apk
Please help me, what should I do?
Is 1.7 software not rootable?
I can't get adb to come on, no matter how many browser crashes I do. Even wrote a script for it:
@echo off & setlocal
set IP=192.168.0.119
set loopcount=0
set s
:loop
set /a loopcount=loopcount+1
echo Connecting %loopcount% time...
adb connect %IP% | find /i "connected to" > %s
if errorlevel 1 (
echo Not successful + %ERRORLEVEL% + %s%
goto loop
) else (
echo Successful + %ERRORLEVEL% + %s%
adb shell
goto exitloop
)
:exitloop
pause
Click to expand...
Click to collapse
Is OTA rooting (by redirect on sync.barnesandnoble.com) not possible any longer as well?
Sorry for the late response, for some reason the email telling me there was a post here just arrived TODAY lol.
It should be, I did it with 1.7. The script I have I modded a little from another one I found online here is mine:
Code:
@echo off
echo The website hack seems to work on the round right after it has an instant crash.
echo.
adb kill-server
adb start-server
set /p ip=Enter the IP here.
:CON
cls
echo Crash the browser.
echo.
adb connect %ip%
for /f "tokens=2" %%A in ('adb devices') Do (Set dev=%%A)
if %dev%==device goto INT
echo.
goto CON
:INT
if exist ratc.bin (set f1=1) else (set f1=0)
if exist init.rc (set f2=1) else (set f2=0)
if %f1%==%f2% (if %f1%==1 (goto RTT) else (goto 2fi)) else (goto 2fi)
:2fi
if %f1%==0 (echo "The ratc.bin file is not in the %cd% directory.") else (echo Ratc.bin file present.)
echo.
if %f2%==0 (echo "The init.rc file has not been pulled from the device to the %cd% directory, pulling now.") else (echo Init.rc file present.)
if %f2%==0 adb pull /init.rc
echo.
echo Please add the required files and restart this batch. If init.rc was just pulled, you will need to modify the file.
cmd
:RTT
adb push ratc.bin /sqlite_stmt_journals
adb shell cd /sqlite_stmt_journals
adb shell /system/bin/chmod 0777 /sqlite_stmt_journals/ratc.bin
adb shell /sqlite_stmt_journals/ratc.bin
adb kill-server
adb start-server
goto CO2
:CO2
cls
echo Re-crash the browser.
echo.
adb connect %ip%
for /f "tokens=2" %%A in ('adb devices') Do (Set dev=%%A)
if %dev%==device goto PSH
echo.
goto CO2
:PSH
adb push init.rc /
adb shell reboot
echo.
echo Congrats! The device is now rooted.
echo.
cmd
It is RANDOM on the browser crashes. Sometimes it happens fast, another time it look me a hour or two to get a good crash and root the nook. Also if it doesn't seem to be doing it for a long time, try rebooting the nook (hold down the power until the screen blanks then press the button again to restart it). In my opinion, this is the toughest Nook to root, but definitely worth it. Especially now that B&N ended support some time ago. Also make sure the ADB, this script, and the ratc.bin is in the same folder. I used a folder on the desktop as it made it much easier/faster to get to. Also after you get the init.rc and modded, that should be in the same folder as well.
As for OTA rooting, I have no idea if it will work or not. I never used that method. But if it depended on any sort of connection from B&N, I doubt it will work now since they have abandoned the Nook classic.
If you need any of the nook apps that were on the nook developer site let me know. I downloaded all the apps before the site went down.
dob43 said:
Sorry for the late response, for some reason the email telling me there was a post here just arrived TODAY lol.
It should be, I did it with 1.7. The script I have I modded a little from another one I found online here is mine:
Code:
@echo off
echo The website hack seems to work on the round right after it has an instant crash.
echo.
adb kill-server
adb start-server
set /p ip=Enter the IP here.
:CON
cls
echo Crash the browser.
echo.
adb connect %ip%
for /f "tokens=2" %%A in ('adb devices') Do (Set dev=%%A)
if %dev%==device goto INT
echo.
goto CON
:INT
if exist ratc.bin (set f1=1) else (set f1=0)
if exist init.rc (set f2=1) else (set f2=0)
if %f1%==%f2% (if %f1%==1 (goto RTT) else (goto 2fi)) else (goto 2fi)
:2fi
if %f1%==0 (echo "The ratc.bin file is not in the %cd% directory.") else (echo Ratc.bin file present.)
echo.
if %f2%==0 (echo "The init.rc file has not been pulled from the device to the %cd% directory, pulling now.") else (echo Init.rc file present.)
if %f2%==0 adb pull /init.rc
echo.
echo Please add the required files and restart this batch. If init.rc was just pulled, you will need to modify the file.
cmd
:RTT
adb push ratc.bin /sqlite_stmt_journals
adb shell cd /sqlite_stmt_journals
adb shell /system/bin/chmod 0777 /sqlite_stmt_journals/ratc.bin
adb shell /sqlite_stmt_journals/ratc.bin
adb kill-server
adb start-server
goto CO2
:CO2
cls
echo Re-crash the browser.
echo.
adb connect %ip%
for /f "tokens=2" %%A in ('adb devices') Do (Set dev=%%A)
if %dev%==device goto PSH
echo.
goto CO2
:PSH
adb push init.rc /
adb shell reboot
echo.
echo Congrats! The device is now rooted.
echo.
cmd
It is RANDOM on the browser crashes. Sometimes it happens fast, another time it look me a hour or two to get a good crash and root the nook. Also if it doesn't seem to be doing it for a long time, try rebooting the nook (hold down the power until the screen blanks then press the button again to restart it). In my opinion, this is the toughest Nook to root, but definitely worth it. Especially now that B&N ended support some time ago. Also make sure the ADB, this script, and the ratc.bin is in the same folder. I used a folder on the desktop as it made it much easier/faster to get to. Also after you get the init.rc and modded, that should be in the same folder as well.
As for OTA rooting, I have no idea if it will work or not. I never used that method. But if it depended on any sort of connection from B&N, I doubt it will work now since they have abandoned the Nook classic.
If you need any of the nook apps that were on the nook developer site let me know. I downloaded all the apps before the site went down.
Click to expand...
Click to collapse
Does this still work? I recently dug up my old nook 1st edition, I tried the website and it didn't crash my browser, it just sat there forever loading.. I looked at the site, now it's using TLS 1.3, but old nook 1st edition is stuck with TLS 1.2... I tried for many hours just couldn't "crash" the web browser at all...

Categories

Resources