yashsingh1/xdaforums huggingface dataset:
[Nook Touch Android Development] bobcdy:
Windsor1959

Thanks for the help! I used the tn2.1.31 a second time (see below), and the black flashed after about 30 sec. Tried the market and it connected for a few seconds, then crashed. I'll try again tomorrow.

I may still may have a problem though: I had done a number of rooting attempts, and finally used the older touchnooter and it worked. I was able to access the market but when I tried to install an ap from a non-market source, it was blocked.

On the internet I read that there is a app called nookcolor tools that should be installed during rooting, and is used to fix this problem BUT that app apparently is not installed, so I tried again with tn2.1.31. The first time it never flashed but on the second try it behaved as you found. However, there is still no nookcolor tools app installed, and I don't know how to get non-market apps to work.

Have you had a problem such as this, and if so, how to fix it?

---

ADDED THIS EVENING: I found nookcolor tools, unchecked, then rechecked it; will see if the marker works tomorrow.
[Nook Touch Android Development] Windsor1959:
I was just about to ask you if you had ADW launcher on your NST, so that you could find Nook Color Tools. But it seems that you found it! It might take up to a day for Market to work. Good luck!
[Nook Touch Android Development] bobcdy:
Can't get into unrooted nook

Help! Everything was going so well, until I check the 'home' option on boot screen where 'home' and 'adw launcher' resides. I was experimenting with various things, and apparently this was the wrong thing to do because now I can't get to the adw launcher. Thus I'm locked into the unrooted Nook without access to the rooted change. What can I do to access the launcher? I've tried rebooting but this doesn't help! Do I have to start over and reinstall the root?? If so, why on earth does the rooting give an option to permanently lock into the unrooted B&N nook???
[Nook Touch Android Development] bobstro:
Don't panic:

1. When you power cycle the device, it should let you get back to ADW on first boot.

2. If you did not get rid of Button Savior (the itty bitty button at the right of your screen) you can click the Home icon there.

3. Depending on how you set up ADW, you might be able to press and hold the 'n' button until the recent menu appears. If enabled, there will be a home button there.

The reason "rooting did this" is that you told it to. Options mean something. Especially when you've rooted!
[Nook Touch Android Development] bobcdy:
Thanks for the info. Actually though I'm not sure if I know what a 'power cycle' is. I searched for it on google, and it seems it might be a hard reset by powering on/off for 8 times? If so, won't this destroy the rooting?

I checked on xda and found that it did not reset everything so I tried the power cycle for 8 times, but the result was no change - still locked into the unrooted Nook ST. Also, you mention the 'N' on the Nook but it is not visible - I looked at the user manual and found no reference to it.

I'll probably do one more power cycle, and then I'll go ahead and to a hard restore/deregister, and re-register it, then do another rooting. I still question why there should be any possibility of such an option - when I check the box on 'home'; if someone wanted to lock it into the unrooted state, & if he/she knew enough to root it in the first place, then it seems the proper way to lock into an unrooted state is the simply restore it to it's state before the rooting. Otherwise, as with most critical steps in programs such as this, there is clear warning repeated twice to be sure no irrevocable mistakes happen.
[Nook Touch Android Development] bobcdy:
apology

I'd like to apologize to Gabrial Destruir and others who developed the excellent TN2.1.31 for my belief that there was some defect in the initial screen checkbox for home. After re-rooting it, and looked more closely and I found that my problem seemed to result from corruption of something in the root, probably because I didn't properly install it.

I'd had difficulties in re-rooting though and never got the flashing screen - the best I could get was a completely black screen that never finished opening. I tried re-rooting 3 times and never succeeded with the black flash, but starting it using a usb connection seemed to work, and the root seems ok. Everything seems to work fine, except there is no video on the you tube app.
[Nook Touch Android Development] GabrialDestruir:
What I'm understanding is that when you root the screen goes black?

If so this is what I meant by "flashes to black". What happens when the screen goes black is instead of completely flashing to the next "page" which would be the nook loading with the three dots, it's turning off the device, meaning that root is done.

As for the lack of video on the youtube app, I'm not sure about you, but videos seem pointless without sound, and the e-ink probably couldn't quite keep up, the only real purpose for it being there is so that you can sign in for market.
[Nook Touch Android Development] bobcdy:
Thanks for the feedback. I was worried that not flashing black meant dire things happened, but I'm now relieved to find that all should be ok - I'm installing various apps and rearranging my home screen, and all indeed seem to work perfectly! Thanks for the great root pgm. I agree about the you tube videos; they seem absolutely useless without color, sound, and large screen.
[Nook Touch Android Development] digixmax:
I ran into problem in rooting my Nook SimpleTouch using TouchNooter: the NST's screen never flashed to black, so I power-cycled the NST and it booted up but appears to be in a "half rooted, broken" state: apps like browsers don't seem to work, NookTouchTools's has exclamation mark on its all menu items, etc.

So I decided to revert to stock using the n2T Recovery method (http://xdaforums.com/showthread.php?t=1289233) without success: judging by the black progress bar of the "Factory Restore" process it seems to stop midway, and the NST booted up in the same "half-rooted, broken" state.

I next tried TouchFormatter method and finally were able to restore the NST to stock 1.1.0.
[Nook Touch Android Development] tiber:
Two questions:

1) What browser is anyone using? The stock one sucks. Opera and Opera Next both crash after "installing".

2) Is there a way to make an icon for the B&N app? I would set my launcher to ADW except that I happen to like the stock B&N app.
[Nook Touch Android Development] Renate:
With ADW, "Library" in the app drawer gets you to the Library and

the upper left hand icon on the status bar gets you to the book that you were last reading.
[Nook Touch Android Development] krenb:
rooting - use class 6 memory

Mine wouldn't root until I used a class 6 micro SD card. Faster memory might work, but I just decided to spend the $7 and follow instructions for a change.

The Class 4 I tried using stalled out on black flash like everyone else.

The NST root wiki specifically says to use class 6 memory, and stresses that you will run into problems using lesser class of memory.

I like what I have so far, there definitely could be some refinements.

Opera Mini is pretty darn amazing on this little sucker.

Thanks for all the hard work.
[Nook Touch Android Development] tiber:
I actually used ADW to make a launcher action to invoke the home.android.bn.app (or whatever their home screen is called). I wanted their home screen because that's where the "special offers" (free stuff) pops up.

Still stumped on the browser. It crashed frequently before I updated it, it crashes every time now that I updated it. I can't win.
[Nook Touch Android Development] tiber:
Anyone looking for a browser which works well with this rom should check out

https://play.google.com/store/apps/details?id=com.mx.browser
[Nook Touch Android Development] digixmax:
Have you tried running "Fix Permissions" (in NookColorTools)? I have found that it usually fixes crashes/forced-closes that plagued some newly installed apps.
[Nook Touch Android Development] roustabout:
@myshyak --

I threw together a clockwork based rooting tool for the Glowworm this weekend using (and stripping down even more) the minimal nooter approach.

I did not including the framework or any google apps, pretty much just su, xbin, a launcher and the Amazon appstore (which doesn't require the framework patching that the Google appstore requires. But, until someone has time to patch the framework, it's a fairly simple way to root the device.

I also did not include the modified uRamdisk - I've found on my device that I don't need to modify uRamdisk, the only downside is that when connected via ADB you have to type "su" to get root.

Since the adb install command pushes files to

/data/local/tmp/ by default, and you can install software from /data/local/tmp without being root, the result is fully functional for me. (I adb installed the underclock on my unit this morning, in fact.)

You can find the full writeup here

http://xdaforums.com/showthread.php?t=1650593
[Nook Touch Android Development] yochaigal:
Use Opera Mobile (not via the market). Here's a quick link I found:

http://handheld.softpedia.com/get/Internet-Utilities/Browsers/Opera-Mini-for-Android-92867.shtml
[Nook Touch Android Development] tiber:
After much LOLWUT, I figured out you were suggesting opera MOBILE, not opera MINI.

This link will help people, it's the final (12.0.2) release of opera MOBILE:

http://dl.dropbox.com/u/78952019/Nook Apps/Opera_Mobile_web_browser_12.0.2.apk
[Nook Touch Android Development] Sepharite:
Is there a way to install CWM on this?

edit: I logged in with Youtube, and everything seemed okay so far. But GMAIL failed to sync accounts, and now Youtube doesn't open up. Should I reflash?

I'm using 1.1.2 if that matters. I just want to try running manga reader on it :)
[Nook Touch Android Development] brendan10211:
There is a "booting android from SD card" floating around, is that what you mean about CWM?

and i used minimaltouch, so can't help you sorry
[Nook Touch Android Development] Sun_Cat:
Non-Market Apps?

I got what sure looks like a successful root with TouchNooter 2.1.31 on an NST running 1.1.2. Opera Mini won't run, though, so I'm trying to install Opera Mobile.

I downloaded the Opera .apk from Softpedia and copied it to my microSD card. When I launch the Super Manager File Manager and try to install it, I get a pop-up saying "Install blocked. For security, your phone is set to block installation of applications not sourced in Android Market."

In Nook Color Tools, "Allow Non-Market Apps" is checked. What am I doing wrong?

Thanks for any clues!

ETA: I was mistaken. Opera Mini actually does run now. (I'm not sure what changed.) But I'd still like to know how to install non-market apps. Thx.

ETA: The same "Install blocked" message comes up in the Amazon Appstore. My device shows up in my Amazon account as "BarnesAndNoble Nook 2." I can buy apps, and they show up on my NST when I launch the Appstore and go to My Apps. When I try to install one, it does download it (I can see the progress bar), but when it tries to install I see that pesky "Install blocked. For security, your phone is set to block installation of applications not sourced in Android Market" message. In Nook Color Tools, "Allow Non-Market Apps" is still checked. I've tried unchecking it and checking it again. No change.
[Nook Touch Android Development] Sun_Cat:
Still no joy on the non-market apps. Here's what else I've done.

I updated the settings database table manually following the instructions in this post. Then I re-pulled the table and did a sqlite SELECT to make sure that the value of that row really got set to 1 on the Nook. It did.

Non-market apps still are blocked. Any ideas, anyone?

ETA: Two more discoveries. One, when I try to push an .apk file to the /system/app directory, I get the message "Failed to copy : Read-only file system." Two, when I try to install using adb ("adb install package.apk") it works! I got Opera Mobile installed and running with that method. Is my Nook a little unstable, or is any of this normal?
[Nook Touch Android Development] Renate:
Generally you should install apps with:

adb install myfavoriteapp.apk

To swap out apps in /system/app you will have to remount your system.

mount -o rw,remount /dev/block/mmcblk0p5 /system

Of course, you backed up your Nook already?
[Nook Touch Android Development] Sun_Cat:
Thanks, Renate. Yes, I backed it up before I started messing with it.

I only installed TouchNooter this morning, so I'm still in the waiting period to see if the Market is going to work. I'm still baffled about why I'm getting the "non-market apps blocked" message in the Amazon Appstore.
[Nook Touch Android Development] GabrialDestruir:
If you actually pay attention to the instructions in the post GMAIL failing is normal, when the market fixes itself, so will Gmail, Youtube will remain broken unless you reinstall it which is pointless since the NST has no sound or acceptable framerate with which to watch videos. The entire reason Youtube exists is so that you can login. Nothing more.
[Nook Touch Android Development] Dopedangel:
If I recall correctly you have to disable and then enable Allow now market option but all the things you tried you must tried that as well so sorry cant help. Another way I found to install app was to add the apk file to the nooter apps folder.
[Nook Touch Android Development] Sun_Cat:
Yes, I did try that as well. Yesterday it looked as if Amazon apps were blocked, though I could use ADB to install direct from any compatible APK. Today whatever was ailing the Amazon Appstore seems to have fixed itself. It's working fine now. Don't ask me what's going on. I'm just happy it's working!
[Nook Touch Android Development] Renate:
I use Opera Mobile, because Opera Mini can't display local files.

In any case, the problem is clearly that it can't find the shared library libom.so

Android looks in two places, the APK and /system/lib

Take the Opera Mini apk that you have, rename it to something.zip and look at it/extract it.

(You don't need to do a full apktool extraction or anything, unzip is good enough.)

Is there a lib directory?

Is there a lib/armeabi directory?

Is there lib/armeabi/libom.so ?

Where do you have anything with libom.so in it?

You may have an apk for something besides ARM.
[Nook Touch Android Development] imachine:
Well, thing is I used this here nooter on my otherwise stock NST 1.1

Opera came with it; it never worked from the start.

So if it works for everybody else using this here nooter (2.1.31), I guess I must've done something wrong.

It seems that NoRefresh displays errors in logcat, market can't search any app (says a network error has occured) and Social says This device is not supported. The stock browser also isn't very good here - it FCs when I press the google search box on google.com in order to type something in the search box.

It could all be known and accepted errors but I only have the NST for 2 days so haven't read much about the subject yet.

If they're not, I understand it had to do with the nooter therefore I write it here in order to help fix them. I haven't made a backup ;-)
[Nook Touch Android Development] :
I have the identical errors and problems.
[Nook Touch Android Development] Renate:
@ imachine:

I can't see anywhere in your post where you answered my questions.
[Nook Touch Android Development] imachine:
I figured I can just leave the info here and let the nooter devs take care of the somewhat simple (or so it seems) packaging/directory issue.

There are more - I'm sorry I didn't catch your drift - I think we can work out a solution, I have some basic linux knowledge.

Reporting back in 10...

*edit*

sorry, had a busy day yesterday -,-

I'm uploading the system base of the nooter I have used, it should be available here

http://tiny.cc/znsffw

It's md5 should be bd34538ab75ae62bbda9156ef6077e5b

What I did was mount the .img file like so:

mount touchnooter-2-1-31.img test/ -o offset=$((32*512))

and then tgz'ed the files from test/nooter into nooter.tgz

Interestingly, I see the system/xbin/busybox file is a normal binary, like so:

file -s system/xbin/busybox

system/xbin/busybox: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped

but when I had the nooter on my nook, it was a dangling NFS link, so it said.

I can't test however since I've moved to stock by a method found here and rooted using MinimalTouch1.5-beta5.

*edit*

Just to make sure - I've used these files:

b80bd8f87f5085940b4da6c379da38fa touchnooter-2-1-31.zip

8058ba8fed54555f4719007ee06346dc touchnooter-2-1-31.img
[Nook Touch Android Development] DarkenCypher:
Re-download opera....mine didn't work either.
[Nook Touch Android Development] Renate:
This thread deals with the TouchNooter.

A few people have complained of problems with the Opera Mini packed in TouchNooter.

I would like to help solve this problem.

I have asked people to check on an aspect of the Opera Mini apk packed in TouchNooter.

Nobody did.

Somebody please post a copy of the Opera Mini apk that is packed in TouchNooter.

(A copy of Opera Mini from another source will not do.)
[Nook Touch Android Development] imachine:
Look above, I edited my post :-)

I can help iron out other issues - such as the one with webrowsers like the built in one or dolphin FCing.

This error exists in both MinimalTouch1.5-beta5 and touchnooter-2.1.31.

Here's the (seemingly relevant) logcat:

http://pastebin.ca/2158517

^--- that's me opening up "stock" browser (with google.com as home page), typing in (surprisingly this time it didn't fc upon touching of the search box) 'browser test' and hitting the 'search' button on the webpage. it searched, then I scrolled one page down (I might have scrolled up too), and then clicked on a result. then it FC'ed.

go dolphin:

http://pastebin.ca/2158516

^--- here's me opening up Dolphin from a crash, chosing normal startup (not recovering tabs from previous session), clicking the default present google.com link (first button from top left), waiting, pressing the seach bar in order to type in text. it then crashes; often this moment the keyboard pops up and the rest of the screen becomes black. afterwards dolphin asks to send a report where I choose to exit (not generate crash report).

Dolphin Browser HD 8.1.1

I'm here to help!
[Nook Touch Android Development] Renate:
Well, I unpacked the Opera Mini out of that nooter.tgz

It appears completely in order.

D/dalvikvm( 1529): Trying to load lib /data/data/com.opera.mini.android/lib/libom.so 0x49f13140
D/dalvikvm( 1529): Added shared lib /data/data/com.opera.mini.android/lib/libom.so 0x49f13140

OTOH, this was not guaranteed to be the same binary that you were having trouble with.

If you had installed some other Opera Mini and then used TouchNooter the old version might have remained.
[Nook Touch Android Development] imachine:
Well, I don't know anymore; I think something might be wrong with that nooter process; I've since restored and nootered it with FT-1.5-beta5

The busybox was a NFS symlink like I wrote, and the nooter.tgz doesn't show it to be like that either.

Maybe I have interrupted the process or something went wrong during the install.

I can try and use the nooter on a stock nook again, just to make sure, I'll try it over the weekend.

Any ideas about the failing browsers though? That would be awesome to iron that out, having such device without the browser that works partially is just not very usable.

Honestly, I don't even care for stock nook apps; I'd ideally just run stock android on it or CM7; I don't even have a credit card to use B&N shop and don't live in the usa so am unlikely to walk into a B&N store to use their Wi-Fi.
[Nook Touch Android Development] Agrajag27:
Some months back--before the official Nook wifi update came out--I rooted via TouchNooter and now have everything running fine. However, I have noticed my wifi is a bit off.

Given this I wondered how hard the process is to get the official update on my Nook and the reroot.

Is it simple now? Is it worth bothering?

Thanks.
[Nook Touch Android Development] viskon:
Opera mobile works best for me.
[Nook Touch Android Development] shogzilla:
Apologies for not reading the entire thread; I searched for key terms, specifically 'formatted' and 'unrecognized', as they seemed logical for anyone experiencing this issue. I browsed the last ~ 8 or so pages, so I'm praying I didn't just miss it and look foolish as a result.

I'm attempting to root / etc a NST, reporting as software version 1.1.0, which I believe indicates that it's good to go for purposes of touchnooter 2.1.31.

I've registered the device, and powered it off via long-press of power followed by 'do you want to fully power off', followed by 'Your NOOK has turned off completely'

Using a 1g microsd card in an external reader on linux, I've dd'd touchnooter-2-1-31.img to the card (with the mount unmounted):

(df result prior to umount, the 1g microsd is /dev/sde1:

/dev/sde1 969M 96K 969M 1% /media/457B-0FEB

umounted /media/457B-0FEB.

dschutzn@Fooiel:~/Desktop$ dd if=touchnooter-2-1-31.img of=/dev/sde1

249345+0 records in

249345+0 records out

127664640 bytes (128 MB) copied, 28.3721 s, 4.5 MB/s

)

Removed microsd from external reader; put microsd into NST. Pressed power button.

Short press ( under 1 second) appears to not do anything; expected?

Longish press (under 2 seconds but over 1 second), device boots, shows nothing touchnooter specific, boots to normal nook-ness.

Upon sliding to unlock, dialog box. Title: 'SD card format required'. Body: 'This memory card is unrecognized and needs to be formatted.'

Cancel / Format Now buttons follow.

Powering off NST w/o formatting microsd, back to reader, fdisk partition info:

Disk /dev/sde1: 1015 MB, 1015741952 bytes

128 heads, 32 sectors/track, 484 cylinders

Units = cylinders of 4096 * 512 = 2097152 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

Device Boot Start End Blocks Id System

/dev/sde1p1 * 1 38 77808 c W95 FAT32 (LBA)

/dev/sde1p3 7 7 0 0 Empty

Partition 3 has different physical/logical beginnings (non-Linux?):

phys=(0, 0, 0) logical=(6, 10, 2)

Partition 3 has different physical/logical endings:

phys=(370, 0, 50) logical=(6, 10, 1)

Partition 3 does not end on cylinder boundary.

Any thoughts? Anyone spotting something where I'm doing it wrong, etc? Please see where I'm doing something wrong =(

EDIT:

Found some info in http://xdaforums.com/showthread.php?t=1506004 - basically, same issue, same scenario (more or less), 1,1 NST and touchnooter and linux to dd the image to the card, card not seen properly as a result. He was able to get it working via a windows machine; I have no windows machines. So it's just 'problem exists for more than just myself' at this point, I guess. Any linux solutions?
[Nook Touch Android Development] GabrialDestruir:
dd if=touchnooter-2-1-31.img of=/dev/sde

You have to copy the image to the entire disk not just one partition.
[Nook Touch Android Development] shogzilla:
Perfect, thanks, and now I feel more than a bit derpy.
[Nook Touch Android Development] elty123:
Can I apply Nook update from B&N before running this tool?
[Nook Touch Android Development] zbeyuz:
Does this update apply to Nook Simple Touch with GlowLight too ( Multitouch ) ?
[Nook Touch Android Development] GabrialDestruir:
Touchnooter does not work for Nook Glow
[Nook Touch Android Development] pgonza02:
Can't Get to ADW Home

Hi Guys,

Quick question.

The battery on my Nook drain all the way and now when I boot in, I still have the side, pull-out drawer, but when I hit the Home button instead of opening ADW, it goes to the B&N home screen.

Any ideas?

Thanks in advance.
[Nook Touch Android Development] jrowe1977:
I am having a problem trying to sideload an apk when I try to install it it says for security your phone is set to block installation of applications not sourced in android market how can I tern this off thanks
[Nook Touch Android Development] osowiecki:
Uncheck the "allow non market installations" (something) box then check it again.

That should work.