Related
I have read that it's possible to use google books on the NST (or NTG) but i can't find it in the market place. and every time i try and side load the apk i get INSTALL_FAILED_OLDER_SDK. I downloaded google play books 2.3.5 apk which is supposably built for 2.1. I thought the NST/NTG was on 2.1 (or is it 2.2?) so im curious why this doesn't work... anyone care to comment?
If i just have the wrong version please let me know the correct version to use.
You can try apktool-ing the apk and see what version it specs in AndroidManifest.xml.
You could modify the version and see if it crashes.
We're running Eclair, 2.1, API level 7 on the Nook Touch.
Any luck OP?
EDIT:
Tried this one: http://www.iapktop.com/google-play-books-2-4-3.html since it said compatible with 2.1, but I had no luck.
Then I tried this one: http://www.iapktop.com/google-books-1-4-5.html and it looks to be working! I saw my library in the window and I have it downloading one of my books now for reading to test.
EDIT2: AAaaaaand... works. Perfectly I might add. The only thing that doesn't work is the side buttons don't switch pages. I think because they are bound to PAGE_NEXT or something. Changing them to Right and Left arrow should do it.
EDIT3: Yep. A quick change to the keylayout lets me page with the right hand buttons. It does break the ability to page in the stock reading app though with those buttons. For now I'm leaving it with paging in Google books with right side buttons and paging in Nook with left side buttons. I'll probably go all in later.
What I did was edit /system/usr/keylayout/TWL4030_Keypad.kl and switch RIGHT_NEXTPAGE to DPAD_RIGHT and then switched RIGHT_PREVPAGE to DPAD_LEFT.
Hopefully that makes sense. If not I can probably make it easier for you by pulling the file itself, but I figure I'd try to "teach a man to fish."
Dynamic button remapping; getting rid of page-turn animation
(Interested lurker speaking. I don't have a NST, but a rooted Sony PRS-T1, which is similar, but running Android 2.2. Please take what I say with a grain of salt.)
The latest version of Google Play Books that does not require 3D hardware (for its carousel view and its page-turn animation) and that is available for older Android versions appears to be version 1.5.4.
I'm using that version on the PRS-T1, but was annoyed by its flickering slide animation when turning pages. If you're comfortable with the Android SDK and apktool, here's a hack I did to remove that animation:
mobileread.com/forums/showthread.php?t=187741
The problem of different Left/Right key bindings for different apps plagues the PRS-T1 as well. This led me to look for a solution to remap these buttons dynamically, depending on which app was currently running in the foreground. Here's my hack for the PRS-T1, which a semi-experienced developer could port over to the NST. I'd be happy to accept patches.
mobileread.com/forums/showthread.php?t=187054
github.com/altruizine/pgdn
(Sorry for not posting direct links – I'm not allowed to post links yet.)
altruizine said:
(Interested lurker speaking. I don't have a NST, but a rooted Sony PRS-T1, which is similar, but running Android 2.2. Please take what I say with a grain of salt.)
The latest version of Google Play Books that does not require 3D hardware (for its carousel view and it page-turn animation) and that it available for older Android versions appears to be version 1.5.4.
I'm using that version on the PRS-T1, but was annoyed by its flickering slide animation when turning pages. If you're comfortable with the Android SDK and apktool, here's a hack I did to remove that animation:
mobileread.com/forums/showthread.php?t=187741
The problem of different Left/Right key bindings for different apps plagues the PRS-T1 as well. This led me to look for a solution to remap these buttons dynamically, depending on which app was currently running in the foreground. Here's my hack for the PRS-T1, which a semi-experienced developer could port over to the NST. I'd be happy to accept patches.
mobileread.com/forums/showthread.php?t=187054
github.com/altruizine/pgdn
(Sorry for not posting direct links – I'm not allowed to post links yet.)
Click to expand...
Click to collapse
That's awesome! I only just got this device last night so haven't got too far into hacking it, but I have plenty of other Android experience. I'll see if I can replicate.
Sent from my HTC One S using xda premium
So close!
ViViDboarder said:
Then I tried this one: .iapktop.com/google-books-1-4-5 and it looks to be working! I saw my library in the window and I have it downloading one of my books now for reading to test.
EDIT2: AAaaaaand... works. Perfectly I might add. The only thing that doesn't work is the side buttons don't switch pages. I think because they are bound to PAGE_NEXT or something. Changing them to Right and Left arrow should do it.
Click to expand...
Click to collapse
Thank you so much for posting this!
I installed the1-4-5 apk without incident and all my books synced beautifully, including where I left off in them. I was pretty sure I was home free at this point but I've found that the actual content of the books never loads. I get the spinning loading icon off into infinity.
This is the way for all my books. Looks for all the world like it should work fine but just never loads the actual content.
I've tried a system reboot, scanning around between pages, fussing with text size/line spacing and same outcome.
I tried the 2-4-3 apk and got a parsing error when i tried to open the package.
This is so close I can taste it. Any ideas anyone?
Thank you
Update:
I found that if I toggled on "Original pages" in the book options the content would load. After I did that once I could switch back to "flowing text" and adjust as needed.
Update 2:
I still intermittently have issues with book content loading. Probably once per day the loading icon displays indefinitely. The flowing text/original pages workaround I listed before was likely a flook, I haven't been able to find a way to reliably get around this problem. It's terribly annoying.
Update 3:
I tried using the refresh option on the library view prior to loading my book this time and it popped up immediately afterward. I'll continue to experiment with this to see if it works consistently.
Update 4:
That's unreliable as well. There doesn't seem to be any good way to prompt my book to actually load the content of the book. Super annoying.
Version 1.0.16
jorgenric said:
Thank you so much for posting this!
I installed the1-4-5 apk without incident and all my books synced beautifully, including where I left off in them. I was pretty sure I was home free at this point but I've found that the actual content of the books never loads. I get the spinning loading icon off into infinity.
This is the way for all my books. Looks for all the world like it should work fine but just never loads the actual content.
I've tried a system reboot, scanning around between pages, fussing with text size/line spacing and same outcome.
I tried the 2-4-3 apk and got a parsing error when i tried to open the package.
This is so close I can taste it. Any ideas anyone?
Thank you
Update:
I found that if I toggled on "Original pages" in the book options the content would load. After I did that once I could switch back to "flowing text" and adjust as needed.
Update 2:
I still intermittently have issues with book content loading. Probably once per day the loading icon displays indefinitely. The flowing text/original pages workaround I listed before was likely a flook, I haven't been able to find a way to reliably get around this problem. It's terribly annoying.
Update 3:
I tried using the refresh option on the library view prior to loading my book this time and it popped up immediately afterward. I'll continue to experiment with this to see if it works consistently.
Update 4:
That's unreliable as well. There doesn't seem to be any good way to prompt my book to actually load the content of the book. Super annoying.
Click to expand...
Click to collapse
Here is an older version that I found somewhere on the web. It is version 1.0.16...I installed it and it seems to work excellently so far. The bug where version 1.5.4 often never loads the book doesn't seem to be present. :cyclops:
finitary said:
Here is an older version that I found somewhere on the web. It is version 1.0.16...I installed it and it seems to work excellently so far. The bug where version 1.5.4 often never loads the book doesn't seem to be present. :cyclops:
Click to expand...
Click to collapse
I may have to give this a shot. I am frequently annoyed with this bug. Thankfully the books I'm reading actually fit perfectly on the screen when viewing the scanned versions.
Just wanted to bump and see if you're still getting good results with that version of Google Books. I haven't switched yet (started reading something on Kindle) but I'm about to start a new book on Google Play.
Seems to work!
finitary said:
Here is an older version that I found somewhere on the web. It is version 1.0.16...I installed it and it seems to work excellently so far. The bug where version 1.5.4 often never loads the book doesn't seem to be present. :cyclops:
Click to expand...
Click to collapse
I just loaded up the 1.0.16 version and the book loaded right up where as 10 minutes ago it stubbornly refused. I'm not going to get my hopes up yet but I'll try and remember to give an update after some more use. Thanks for the post!
goodereader.com has version 1.5.2 for download. Worth a try.
Success!
jorgenric said:
I just loaded up the 1.0.16 version and the book loaded right up where as 10 minutes ago it stubbornly refused. I'm not going to get my hopes up yet but I'll try and remember to give an update after some more use. Thanks for the post!
Click to expand...
Click to collapse
Seems to be working consistently with this version of reader.
jorgenric said:
Seems to be working consistently with this version of reader.
Click to expand...
Click to collapse
Awesome! Thanks for the update.
Finally got around to rooting my Nook Touch, as I wanted to utilize the syncing feature of Google Play Books. They now let you upload your own epub files to your library, and I have been reading mainly on my phone or Nexus 7 as a result.
Unfortunately it looks like the 1.0.16 version does not support user uploaded books. All of my purchased books appear, but none of the many I uploaded. 1.5.2 and 1.5.4 both have the book not loading issue.
Anyone have any thoughts or other versions to try? Would love to get this working.
urinsane said:
Finally got around to rooting my Nook Touch, as I wanted to utilize the syncing feature of Google Play Books. They now let you upload your own epub files to your library, and I have been reading mainly on my phone or Nexus 7 as a result.
Unfortunately it looks like the 1.0.16 version does not support user uploaded books. All of my purchased books appear, but none of the many I uploaded. 1.5.2 and 1.5.4 both have the book not loading issue.
Anyone have any thoughts or other versions to try? Would love to get this working.
Click to expand...
Click to collapse
I'm in the same boat. I can see my uploaded library in play but it's not loading the book. I think it has loaded the book but it's not ending the load part of the function. Just guessing.
Hope we can get this worked out.. This would help me tremendously being able to read on the N2T and sync across my computer and Nexus.
*update For some strange reason this started working for about a minute. Book I'm reading synced right to the exact page. Exited and went back in to see if it would still work and it went back to the looping circle page. It's so close I can taste it.
*update Managed to get 1.5.2 working but only in offline mode only. I've noticed the more pages the book has the slower it is to load, but it's loading none the less 9/10 times. Progress, so it is possible to get this working.
ForSquirel said:
I'm in the same boat. I can see my uploaded library in play but it's not loading the book. I think it has loaded the book but it's not ending the load part of the function. Just guessing.
Hope we can get this worked out.. This would help me tremendously being able to read on the N2T and sync across my computer and Nexus.
*update For some strange reason this started working for about a minute. Book I'm reading synced right to the exact page. Exited and went back in to see if it would still work and it went back to the looping circle page. It's so close I can taste it.
*update Managed to get 1.5.2 working but only in offline mode only. I've noticed the more pages the book has the slower it is to load, but it's loading none the less 9/10 times. Progress, so it is possible to get this working.
Click to expand...
Click to collapse
I'm not really sure what version I am using now but it loaded once on my NST. However, the next time I tried loading a book it took forever to load (and I eventually closed the app). It might have to do with memory... Who knows... The funny thing is that once it has loaded the book it works like a charm. Really fast (I would say as fast as the native app). The only thing that don't work are the hardware buttons but it was quite expectable.
enekomh said:
I'm not really sure what version I am using now but it loaded once on my NST. However, the next time I tried loading a book it took forever to load (and I eventually closed the app). It might have to do with memory... Who knows... The funny thing is that once it has loaded the book it works like a charm. Really fast (I would say as fast as the native app). The only thing that don't work are the hardware buttons but it was quite expectable.
Click to expand...
Click to collapse
Any updates? Looks promising....
Here's a link to an old version that worked for me (I later uninstalled it,finding better sources for books).
nmyshkin said:
Here's a link to an old version that worked for me (I later uninstalled it,finding better sources for books).
Click to expand...
Click to collapse
Sorry meant the 1.5.2 or up version. I have uploaded books on Google Play that I hope to read.
I'm also searching for this solution. I have tried the older versions, but there doesn't seem to be a solution. Best I've got is installing an old Google Drive apk, and downloading from there. Box also works, but it's Drive for me.
Hi all.
i've a rooted nook touch with an old version of TouchNooter .
Now, google updated the marketplace (now play store) and since that time i can't install anything else on the device. Said so, i would like to upgrade the touchnootler version to a new one (hoping that it has the play store).
what should i do? do everything from scratch or is there another procedure?
Is there any "better" rooting?
PS: don't know if it's a rooting problem, but in the library, for the last book i was reading ("last reading" or smt like that), i've the screen saying 1 of 1 (pages) and when i open it it starts from the begining instead of the page where i left the book.
ciao.
esseti said:
Hi all.
i've a rooted nook touch with an old version of TouchNooter .
Now, google updated the marketplace (now play store) and since that time i can't install anything else on the device. Said so, i would like to upgrade the touchnootler version to a new one (hoping that it has the play store).
what should i do? do everything from scratch or is there another procedure?
Is there any "better" rooting?
PS: don't know if it's a rooting problem, but in the library, for the last book i was reading ("last reading" or smt like that), i've the screen saying 1 of 1 (pages) and when i open it it starts from the begining instead of the page where i left the book.
ciao.
Click to expand...
Click to collapse
anyone that can help?
When you say you can't install anything else, what do you mean specifically? Inability to search in Market is a known issue. If you mean you can't search, you need to install SearchMarket to search for things. The NST runs an old (2.1 Eclair) version of Android, which is NOT compatible with the new Play Store, so we're stuck with the old Market. Everything works, but searching.
Use the latest version of TouchNooter for your device. It won't be able to fix the searching problem.
bobstro said:
When you say you can't install anything else, what do you mean specifically? Inability to search in Market is a known issue. If you mean you can't search, you need to install [*URL="https://play.google.com/store/apps/details?id=youten.redo.searchmarket&feature=search_result#?t=W251bGwsMSwxLDEsInlvdXRlbi5yZWRvLnNlYXJjaG1hcmtldCJd"]SearchMarket[/URL] to search for things. The NST runs an old (2.1 Eclair) version of Android, which is NOT compatible with the new Play Store, so we're stuck with the old Market. Everything works, but searching.
Use the latest version of TouchNooter for your device. It won't be able to fix the searching problem.
Click to expand...
Click to collapse
if i click on the market icon nothing happens. even going to the play store and install it via pc does not work. i cannot install anything. ideas?
I believe you can download the latest TouchNooter and run it with no harm. Read through the TouchNooter thread to be sure.
Market should launch, even if you can't search. Installing via the web page should work. Sounds like something is broken on the system.
As far as the page numbering -- that's a known B&N bug. I quit using B&N's reader or library.
bobstro said:
I believe you can download the latest TouchNooter and run it with no harm. Read through the TouchNooter thread to be sure.
Market should launch, even if you can't search. Installing via the web page should work. Sounds like something is broken on the system.
As far as the page numbering -- that's a known B&N bug. I quit using B&N's reader or library.
Click to expand...
Click to collapse
well, upgrading to last touchnootler i'll have to do all the procedure back again (if i follow the one one the first page that i assume to be the correct one).
since it's basically like doing everything from scratch, is this the actual best mod for the touch? or is there anything better?
What do you use instead of the B&N library?
"Better" is a subjective term. TouchNooter installs the basic tools you're likely to want (Market, NOOK Touch Tools, etc.) MinimalTouch lets you have complete control over the process, but requires more work on your part.
I have used TN a half-dozen times with no problems if I follow the instructions carefully, so it's my preferred method of rooting. That doesn't mean it's the "better" approach. I do modify TN to add a file manager that works before I root with it. SuperManager that Gabrial includes has never worked for me, and I don't like waiting 24 hours to install software via the Market.
I use Mantano Reader Premium to replace the B&N Library and Reader completely. I never see the B&N Home screen, Reader or Launcher.
bobstro said:
"Better" is a subjective term. TouchNooter installs the basic tools you're likely to want (Market, NOOK Touch Tools, etc.) MinimalTouch lets you have complete control over the process, but requires more work on your part.
I have used TN a half-dozen times with no problems if I follow the instructions carefully, so it's my preferred method of rooting. That doesn't mean it's the "better" approach. I do modify TN to add a file manager that works before I root with it. SuperManager that Gabrial includes has never worked for me, and I don't like waiting 24 hours to install software via the Market.
I use Mantano Reader Premium to replace the B&N Library and Reader completely. I never see the B&N Home screen, Reader or Launcher.
Click to expand...
Click to collapse
ok thx.
i'm right now upgrading the firmware (1.1.2) since the first upgrade of the touchnootler didn't work out well.
quite interested in understanding how did you manage to rip off the B&N library and put the one you have.
esseti said:
ok thx.
i'm right now upgrading the firmware (1.1.2) since the first upgrade of the touchnootler didn't work out well.
quite interested in understanding how did you manage to rip off the B&N library and put the one you have.
Click to expand...
Click to collapse
i don't know. i had some problems while rooting but right now i booted the nook and the market is working. good. how can i know which version of the touchnootler is installed?
esseti said:
i don't know. i had some problems while rooting but right now i booted the nook and the market is working. good. how can i know which version of the touchnootler is installed?
Click to expand...
Click to collapse
Which one did you download and run? That'll be the one. TN doesn't put any sort of "About..." box anywhere that I'm aware of.
Remember that you may have to wait 24 hours to be able to search, even with SearchMarket.
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
esseti said:
ok thx.
i'm right now upgrading the firmware (1.1.2) since the first upgrade of the touchnootler didn't work out well.
quite interested in understanding how did you manage to rip off the B&N library and put the one you have.
Click to expand...
Click to collapse
I didn't rip them out. I just don't run them. I can get to them if I ever need them. I use the Mantano equivalent screens. I changed the "Library" button on the QuickMenu to run Mantano Reader using NOOK Touch Tools. That takes me to Mantano's Library screen. From there, I select books and it opens the Mantano Reader screen.
Every morning, I have Dropsync download my newspaper and magazine content created by Calibre and hit the Import button in Mantano. It's quite a nice replacement for the B&N software, especially with the improved pdf reading features.
bobstro said:
Which one did you download and run? That'll be the one. TN doesn't put any sort of "About..." box anywhere that I'm aware of.
Remember that you may have to wait 24 hours to be able to search, even with SearchMarket.
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
I didn't rip them out. I just don't run them. I can get to them if I ever need them. I use the Mantano equivalent screens. I changed the "Library" button on the QuickMenu to run Mantano Reader using NOOK Touch Tools. That takes me to Mantano's Library screen. From there, I select books and it opens the Mantano Reader screen.
Every morning, I have Dropsync download my newspaper and magazine content created by Calibre and hit the Import button in Mantano. It's quite a nice replacement for the B&N software, especially with the improved pdf reading features.
Click to expand...
Click to collapse
the fact is: when i flashed the new version of TN i had the black screen (as it should be) but it automatically restarted. So i tried to flash it again but nothing happened. I reboot the devices and i had everything working, i needed only to accept the market agreement and nothing else. For this reason i'm not sure to have the lastest version, but, as long as it works i don't care much.
what are the diffrences between the 1.11 and the last version of TN? just that the last works and the old one shouldn't?
esseti said:
the fact is: when i flashed the new version of TN i had the black screen (as it should be) but it automatically restarted. So i tried to flash it again but nothing happened. I reboot the devices and i had everything working, i needed only to accept the market agreement and nothing else.
Click to expand...
Click to collapse
Did you follow the rest of the procedure to register with YouTube to enable the Market? You'll still probably have to wait 24 hours for the Market to work, and you'll still have to use SearchMarket to find things on your device, but it should work if you've followed the full procedure. From what you've written, it sounds as if you stopped part way through.
For this reason i'm not sure to have the lastest version, but, as long as it works i don't care much.
what are the diffrences between the 1.11 and the last version of TN? just that the last works and the old one shouldn't?
Click to expand...
Click to collapse
The old one *might* but it would take you all of two minutes to be sure you've downloaded the latest (2.1.31 as of this writing) and carefully followed the procedure that GabrialDestruir has so generously provided. Follow the entire procedure. You will spend more time trying to fix things than you will doing it by the procedure the first time.
bobstro said:
Did you follow the rest of the procedure to register with YouTube to enable the Market? You'll still probably have to wait 24 hours for the Market to work, and you'll still have to use SearchMarket to find things on your device, but it should work if you've followed the full procedure. From what you've written, it sounds as if you stopped part way through.The old one *might* but it would take you all of two minutes to be sure you've downloaded the latest (2.1.31 as of this writing) and carefully followed the procedure that GabrialDestruir has so generously provided. Follow the entire procedure. You will spend more time trying to fix things than you will doing it by the procedure the first time.
Click to expand...
Click to collapse
wait. when i turned on after the flashing the nook was already ready to go as before flashing it. so with android and all the software/books i had. no android welcome or other stuff, no registration and so on. only to accept the market ToS.
Btw:i did the 8 reboot stuff for flashing to factory. after the flash the andorid mood was still there. is this normal?
after that i upgraded it to 1.12. right now i've the 1.1.0 (that was probably the flash of TN 2.1.31 doing this).
esseti said:
wait. when i turned on after the flashing the nook was already ready to go as before flashing it. so with android and all the software/books i had. no android welcome or other stuff, no registration and so on. only to accept the market ToS.
Click to expand...
Click to collapse
Hmm. That doesn't sound right. I just rebuilt my NST, so let me summarize the steps. This is from memory, so I might get it wrong, but I did it twice recently, so hopefully my memory is good:
I did a factory wipe of user data (Settings->Erase and Deregister Device).
I did an 8 failed boot reload of the original firmware. This put me at 1.0.0, IIRC.
I re-registered with B&N.
I copied the 1.1.2 update to uSD and let it update and rebooted to confirm it was a 1.1.2.
I rebooted with my TouchNooter 2.1.31 uSD card inserted and let it run until the screen went black (10-30 seconds).
I removed the TN uSD card and put my blank 8 GB card back in.
I powered up the NST. It gave me that perverted "Touch the Android to begin" screen. I touched the little bugger.
I skipped the Google sign in per Gabrial's instructions.
I accepted the location management options.
It dropped me to the ADW screen.
I launched YouTube and signed in using my existing google account, per Gabrial's instructions.
At this point, it was working and rooted. Unfortunately, the SuperManager used in TN has never worked for me, nor has Opera Mini, so you can be stuck waiting 24 hours for the Market to activate at this point. I have worked around this by adding a few select tools to my TN bootable uSD card in /data/app (ES File Explorer to load files saved to Dropbox, Root Explorer, SearchMarket).
As usual, YMMV.
It sounds like you're not seeing the initial Android setup screen. Is that correct? What are you doing differently from my steps, if anything?
bobstro said:
Hmm. That doesn't sound right. I just rebuilt my NST, so let me summarize the steps. This is from memory, so I might get it wrong, but I did it twice recently, so hopefully my memory is good:
I did a factory wipe of user data (Settings->Erase and Deregister Device).
I did an 8 failed boot reload of the original firmware. This put me at 1.0.0, IIRC.
I re-registered with B&N.
I copied the 1.1.2 update to uSD and let it update and rebooted to confirm it was a 1.1.2.
I rebooted with my TouchNooter 2.1.31 uSD card inserted and let it run until the screen went black (10-30 seconds).
I removed the TN uSD card and put my blank 8 GB card back in.
I powered up the NST. It gave me that perverted "Touch the Android to begin" screen. I touched the little bugger.
I skipped the Google sign in per Gabrial's instructions.
I accepted the location management options.
It dropped me to the ADW screen.
I launched YouTube and signed in using my existing google account, per Gabrial's instructions.
At this point, it was working and rooted. Unfortunately, the SuperManager used in TN has never worked for me, nor has Opera Mini, so you can be stuck waiting 24 hours for the Market to activate at this point. I have worked around this by adding a few select tools to my TN bootable uSD card in /data/app (ES File Explorer to load files saved to Dropbox, Root Explorer, SearchMarket).
As usual, YMMV.
It sounds like you're not seeing the initial Android setup screen. Is that correct? What are you doing differently from my steps, if anything?
Click to expand...
Click to collapse
i wasn't doing any reset. now i'm doing what you did. let's see.
esseti said:
i wasn't doing any reset. now i'm doing what you did. let's see.
Click to expand...
Click to collapse
You should not have to, but if you're not worried about losing any data, it's nice to know exactly what state your device is in.
bobstro said:
You should not have to, but if you're not worried about losing any data, it's nice to know exactly what state your device is in.
Click to expand...
Click to collapse
did it and everything worked. right now i'm waiting for the market.
I'm at wits end and am hoping someone here can help me. I recently bought a Nook Simple Touch (v 1.2.1), and tried to root it using this thread: http://forum.xda-developers.com/showthread.php?t=2040351.
Things seemed to go OK and I think I rooted it successfully, but I got frustrated because the amazon app store wasn't working and I couldn't figure out how to get google apps up and going. So I figured I'd restore it back to original state, do some more reading, and try to root it again when I had more knowledge. I was able to get it to the screen to do the factory restore (# 3 on this thread: http://nookdevs.com/Nook_Simple_Touch_restore_to_stock), but it is hung up on the start screen (the screen that says "nook by Barnes & Noble" with the dot moving across the five circles). It's been hung for over an hour.
I'm really frustrated - I've rooted phones before, and recently rooted a Nook HD+ with zero issues.
When I rooted it I thought I was making a backup by hitting the backup button before hitting the route, but I don't see any backup image on my SD card.
Any help would be greatly appreciated.
---------------------------
UPDATE:
ok, I am a huge fan of the Brontes but have never been so excited to see their faces as I am now! After a lot of frustration and cursing, but lots of persistence, I was able to successfully do the system restore, by doing #2 on this thread ((# 3 on this thread: http://nookdevs.com/Nook_Simple_Touch_restore_to_stock)). It appears that option #3 wasn't really working (I hit the home button twice per the instructions, but then it turned into a cycle of hell).
So now I will proceed more cautiously, first being certain I figure out how to make a backup...
Hiya Droid,
Getting the google maps and market etc working is a bit of a faff quite frankly but it does work!
Heres the instructions:
http://forum.xda-developers.com/showthread.php?t=2086582
Take your time and follow them step by step and you should be good to go.
Google Maps works great on the nook and is possibly the best app for it. The twitter app also works and it looked like the facebook app worked too (but it was huge!) Opera Mobile Classic is a really nice web browser to use with it, The opera mini that come pre-installed is a waste of time imho. Also UC Browser (with the squirrel) is the other web browser I recommend. I probably use it more than Opera Mobile Classic.
BTW if you are in the UK then the amazon appstore doesn't work and you can just uninstall it by doing a long press on the icon.
Hope you get it all working. I think the thing to do is just to take your time and not to get frustrated or worry when things go wrong. If you have a fresh nook then you have no data to lose anyway, and as you have found, there are a lot of ways to get you back to where you started!
Good Luck!
Freya
thank you FreyaBlack, I was able to figure it all out. Maybe my first download of nookmanager was faulty, the second time it worked like a charm. The market was a bit wonky but I think it just needed time to sync! Now I just have to figure out how dropbox works on this thing (I already use it on my desktop for audio files but need to figure out how to get those (audio files) NOT to sync on my NST.
I've just received Nook simple touch. It was bought from USA and sent to Bangladesh. After unpacking, I powered on the device and followed the steps. At one stage it connects with the wifi network successfully. Then, It shows error message -"Sorry we're having trouble setting up your Nook...."
I communicated with Nook support and share the serial number. Their feedback was "my Nook is disabled, that's why it is not registering..." usually the device is disabled for lost, stolen etc cases. But I told that the device was purchased from bestbuy.com and it reached to me with intact packet. Also I have invoice of it. But they told me to talk to Bestbuy.com.
Later, I called to Nook's hotline asked that where the issue is related to the location from where I'm trying to use it. Feedback was - Nook is useable only from USA and UK having a valid credit card. It cannot be used from Bangladesh.
Now, what should I do to make it workable from Bangladesh?
Maybe this from the Mobileread.com Nook forums:
As long as the epub files you wish to load on the machine are without DRM, like those in Mobileread's own library, the answer is yes. In fact, that is how I've been using the Nook ST for the last week. I'm setting this reader up for my mom who doesn't have wifi or internet access. Since I'm going to sideloading everything anyway, it seemed stupid to bother with registering the nook.
Here's how after you initially charge the nook and activate the unit:
How to Skip OoBE Experience
1. Enter the Factory Screen by holding the TOP RIGHT Button and slide your
finger across the top of the Nook from left to right. A button labeled
"Factory" will appear in the top left of the screen.
2. Once in the Factory screen, hold down the TOP RIGHT Button and tap in the bottom right of the screen.
3. A new button will appear labeled "Skip Oobe". Tap that and you're done!
While you are at it, you might consider installing the latest software update, which you can manually d/l on your computer and install on the nook via USB.
http://www.barnesandnoble.com/u/Soft...uch/379003175/
------------------------------------------------------------------------------------------
But....be aware that a few subsequent posts in the same thread suggested that battery drain was unusually high when using the Nook unregistered. Maybe there are other solutions out there.But it's a start.
You can gut all the B&N stuff if you like.
You will not be able to read B&N DRMed purchased content.
You will still be able to use it for Adobe Digital Editions from OverDrive (which have other DRM).
That's how you read library books (at least here).
When unregistered B&N can use a lot of current.
Turning WiFi on but never actually using it since it was started uses a lot of current.
Turning WiFi on, using it for something, leaving it on is not nearly as bad.
Sounds confusing? It is.
I'm intrigued by this problem and have done some reading online about various peoples experiences. Many had the device registered in the US before taking possession in their respective countries. Some use non-US credit cards without any problem. It seems that there are differences which may be related to firmware versions and perhaps even to changing B&N policies (many of the posts I read are 2-4 years old).
There's a lively Russian Nook users group over on the-ebook.org. Reading through a rough Google translation (always fun) it seems that the standard approach there is to select a US time zone (change it after registration) and skip the credit card part. It might be easier to set up a B&N account on the B&N website first (although that does require a credit card--surely they accept valid international CCs?). In any case, there don't seem to be any additional issues mentioned by the Russians with regard to registration. Curious.
The OP does not state if the intent is to purchase ebooks from B&N or just to have a functioning eink reader for side-loaded material. I guess it is possible to root without registering if you never want to interact with the B&N store, then remove the B&N stuff that is causing the battery drain (or however much of the B&N stuff you want to remove).
It would help to have more info about the intended use for the Nook in question. Meanwhile, shame on BestBuy....
[addendum: Aha! Try this thread]
Thanks a lot nmyshkin
Now I able to use Nook by using you bypass method. Also the battery drain seems faster (40% in 3days).
Another problem is wifi connectivity. I want to use wifi to browse internet (using the hidden trick). How can I do it?
sameee781 said:
Now I able to use Nook by using you bypass method. Also the battery drain seems faster (40% in 3days).
Click to expand...
Click to collapse
Yes, as warned. This is the reason to pursue other options because the battery ought to last for a few weeks, not a day or two.
Another problem is wifi connectivity. I want to use wifi to browse internet (using the hidden trick). How can I do it?
Click to expand...
Click to collapse
Unless you have a very early firmware release (unlikely at this date of purchase), you probably can't use that old trick. It was "fixed" in the second or third firmware update so that the default Android browser became unreachable without rooting.
If you want internet access (and/or email, etc.) your best bet is to root the device. To my mind the easiest way to accomplish this is with NookManager. If you want Google apps (and access to the Play Store for more apps) then you can do that after rooting here, or follow the link to it in the NookManager post.
However, unless you want to selectively delete some B&N stuff after rooting, it would be better if you could get the device registered before you root. Now that you know at least one work-around to get the Nook sort of running, maybe try a factory reset and then approach the registration as the Russians have and see if it works for you.
nmyshkin said:
However, unless you want to selectively delete some B&N stuff after rooting, it would be better if you could get the device registered before you root. Now that you know at least one work-around to get the Nook sort of running, maybe try a factory reset and then approach the registration as the Russians have and see if it works for you.
Click to expand...
Click to collapse
Could you please suggest the Russian method by which I'll be able to register?
sameee781 said:
Could you please suggest the Russian method by which I'll be able to register?
Click to expand...
Click to collapse
Look up back at post #4. But you will have to do a hard reset first so that the Nook goes back into registration mode.
Hi nmyshkin
As mentioned in post#4, I didn't find Nook registration trick in the-ebook.org
If you have a launcher installed you can simply select "OOBE" (Out Of Box Experience).
If you don't have a launcher installed, ADB:
Code:
adb shell am start -n com.nook.oobe/.o.ORoot
(That's dot, small O, dot, capital O)
If you are not rooted you'll have to follow the other instructions above.
sameee781 said:
Hi nmyshkin
As mentioned in post#4, I didn't find Nook registration trick in the-ebook.org
Click to expand...
Click to collapse
According to the Ruskies, you should select a US time zone during registration and skip the credit card (I didn't enter a credit card when I did my registration and everything went just fine--it says you can skip). I don't recall the entire registration process any more, but if you need to enter an address, use a fictional US address, something like "125 First Street, Montebello, CA 90640" (the little town where I grew up...). Ditto for a phone number if needed (818-792-6942) For an email address, something without a country identifier would be best, like a Gmail account you can tie to the Nook.
After registration is successful you can change the time zone in the Settings panel.
As an afterthought, a credit card on file is needed if you plan to have any dealing with B&N. For example, I was curious to see if I could get one of the "Friday Free" ebooks from B&N, even with my rooted and much amended Nook. Although the ebook was free I could not access it without a credit card on file. Once I gave them the card info I had no trouble selecting the ebook and it appeared (by magic!) on my rooted Nook within a few minutes. So whatever I've done so far has not broken that process. Now whether I'm going to be interested in reading that book, I have no idea, but I had to try the process
@nmyshkin & Renate
Current status -
I've rooted my nook using NookManager and installed NTGAppsAttack. I've installed Facebook app but cannot use it properly as it shows internet connection issue. But I can bowse internet using operamini. I've tired to use facebook using operamini. But I could not able to write dot in email address field and unable to login. These are the minor problem because my primary objective is to read books.
The main problem is battery drain. So, I want to register the device to solve battery drain issue. If I follow your instruction, will the battery drain issue be resolved? Or I should unroot it and try to register?
sameee781 said:
@nmyshkin & Renate
Current status -
I've rooted my nook using NookManager and installed NTGAppsAttack. I've installed Facebook app but cannot use it properly as it shows internet connection issue. But I can bowse internet using operamini. I've tired to use facebook using operamini. But I could not able to write dot in email address field and unable to login. These are the minor problem because my primary objective is to read books.
The main problem is battery drain. So, I want to register the device to solve battery drain issue. If I follow your instruction, will the battery drain issue be resolved? Or I should unroot it and try to register?
Click to expand...
Click to collapse
I'm not entirely clear on the order of operations with regard to registration vs. rooting. Registration WILL solve the battery drain problem, so however that can be achieved, that's the way to go, I think. If you can, with your rooted Nook, start the registration process, then try that. If there's no way to invoke registration without resetting to factory, then do that and root again after you have registered successfully.
I don't know anything about Facebook but it may be a challenge with an older browser. BTW, there is general agreement that Opera Mobile works better on the Nook than Opera Mini. You can get that from the Amazon App Market or sideload it directly from the Opera archive here. But first, you need to clear the registration/battery drain hurdle.
Registration is not appearing if I restart the device. As I've skipping oobe it is not going to registration page. If I use DeviceRegistator it gives error.
sameee781 said:
Registration is not appearing if I restart the device. As I've skipping oobe it is not going to registration page. If I use DeviceRegistator it gives error.
Click to expand...
Click to collapse
Yes, once when my too-much altered Nook lost its identity I tried to use DeviceRegistrator and it failed for me too.
NookManager is your friend. Put the SD card back in your Nook and boot it up. Choose the "Restore Factory Image" (or whatever its called).
Then try to register as described earlier with your unrooted Nook. If that works, put the SD card back in again and root. Then proceed from there as you like.
nmyshkin said:
Yes, once when my too-much altered Nook lost its identity I tried to use DeviceRegistrator and it failed for me too.
NookManager is your friend. Put the SD card back in your Nook and boot it up. Choose the "Restore Factory Image" (or whatever its called).
Then try to register as described earlier with your unrooted Nook. If that works, put the SD card back in again and root. Then proceed from there as you like.
Click to expand...
Click to collapse
Should I not face the similar problem like first time? Here is the screenshots taken at the time of getting started with my Nook. The problem was also mentioned in the first post.
sameee781 said:
Should I not face the similar problem like first time? Here is the screenshots taken at the time of getting started with my Nook. The problem was also mentioned in the first post.
Click to expand...
Click to collapse
I have no idea, but I would sure get closer to the router/modem on your Wi-Fi network so that you have a better than "fair" connection.
The one thing which has worried me about the registration process as described by the Russians is that surely the B&N server can tell if the registration info is coming from a server outside the US (or UK). Even faking the time zone doesn't seem likely since the information won't match the server clock that is sending it. But that's what they say worked.
Anyway, what do you have to lose? The Nook is fairly useless as a reading device if you have to charge it every day--or more often. You need to try registering it again. If it doesn't work, then you try something else.
nmyshkin said:
Anyway, what do you have to lose? The Nook is fairly useless as a reading device if you have to charge it every day--or more often. You need to try registering it again. If it doesn't work, then you try something else.
Click to expand...
Click to collapse
Yes, anyhow I've to solve battery drain issue otherwise the device will become useless. That's why I'll also be there in this forum for your help.
-I tired to register near from my wifi router. Also tried by making my phone (Galaxy S4) as portable wifi hotsport. Both are Failed. I'll try again and again....
-In my device there are only few timezone options available, all are US time zone. There should not be issue selecting any one of them.
I'm thinking about their authentication policy. May be their server is checking the originator IP address first which is a non US IP for my case. Hence, it is giving error.
sameee781 said:
I'm thinking about their authentication policy. May be their server is checking the originator IP address first which is a non US IP for my case. Hence, it is giving error.
Click to expand...
Click to collapse
Yes, I thought about that too, although enough people from outside the US claim to have been able to register without any problem (few details, of course....). I suppose you could try a free proxy server (Google), but most of the free ones seem to be transparent enough that they are detected as not being truly from the country of "origin". Still, if all else fails, it's another possibility.
I've found some open proxy proxy server IP
http://www.xroxy.com/proxy-country-US.htm
How can I configure this proxy so that the device IP seem to be a US IP? I've a wimax wifi router and android phone having wifi hotspot feature.
I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://forum.xda-developers.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.
The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.
Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.
Thanks!
Winston S. said:
I got a Like New NST, reset it, unregistered it, and rooted it. I haven't replaced the kernel yet. But I have noticed that (even before I rooted it) the battery consumption is unacceptable. I've seen some old threads about this (for example https://forum.xda-developers.com/showthread.php?t=1475070) , and some suggested removing some APKs like Phone.apk and TelephonyProvider.apk, while others suggested removing or disabling some B&N-related APKs.
The thing is that some other threads seem to imply these solutions are bogus and that they don't really help. There is a lot of conflicting information spread around on this topic.
Does anybody know if there is a solution to this issue? I'm really loving the NST, it's an amazing reader in all ways except for this glaring issue.
Thanks!
Click to expand...
Click to collapse
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://forum.xda-developers.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I can tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://forum.xda-developers.com/nook-touch/general/battery-usage-phone-apk-t3341370
nmyshkin said:
I sympathize and don't want to add to the conflicting information. Read what I wrote here: https://forum.xda-developers.com/showpost.php?p=78287581&postcount=2 under "Decrapify system/app". I can tell you definitively that Phone.apk has little or nothing to do with your battery drain. I did a major study on that issue a long time ago: https://forum.xda-developers.com/nook-touch/general/battery-usage-phone-apk-t3341370
Click to expand...
Click to collapse
Thank you for all your work, you are very methodic and logical, and I appreciate your generosity sharing all your knowledge about the NST (I have been reading up on different things here before I decided to buy one.) :good:
So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.
Winston S. said:
So, to condense all this, it looks as if neither deleting Phone.apk nor disabling B&N apps helps with battery consumption. Also, am I correct in concluding that having an unregistered Nook (or a Nook which is offline, even if registered) will invariably result in poor battery life? That's quite unfortunate, as I was planning to use my NST as a fully offline device.
Click to expand...
Click to collapse
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.
So register and forget. It's the easiest path to device stability and the intended power consumption pattern.
nmyshkin said:
Almost, but fortunately not quite right. Although B&N did some questionable stuff when they cobbled together the NST/G system, I don't think they expected the devices to spend a lot of time online. If the system detects that there is no WiFi, it just slaps a post-it on its internal "refrigerator" to remind it to try a check-in later. All of that happens pretty quickly and in the grand scheme of things Android where stuff is not always killed outright even when you've finished with it, it's not a Big Deal.
So register and forget. It's the easiest path to device stability and the intended power consumption pattern.
Click to expand...
Click to collapse
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?
And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.
EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3
Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.
Is there a preferred way to do this and still keep the device registered and battery life unscathed?
I appreciate your help!
Winston S. said:
Thank you again, I suppose if that's the case then I will register my NST. A couple questions: So if I register the device and never again connect to Wireless that "refrigerator post-it" won't expire?
And, most importantly, if I register with B&N will they push the 1.2.2 update on my device, or can I prevent that without any ill effect? I'd really like to stick to 1.2.1.
EDIT: I read your previous OP about the 1.2.2 OTA update, and your link for how to block it here: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3
Renate NST also suggested deleting /system/app/DeviceManager.apk, but I don't know if this would be problematic with the B&N registration issue I'm trying to fix to begin with.
Is there a preferred way to do this and still keep the device registered and battery life unscathed?
I appreciate your help!
Click to expand...
Click to collapse
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.
OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.
Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).
Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.
nmyshkin said:
I think since you are just starting out working with the device and don't have work to lose by updating and re-rooting, registering and then updating (you can do it manually by downloading the file yourself) is your best bet. The device keeps a "last date contacted" and "next date to try contact" in settings.db. If there is no WiFi, it will just keep changing the dates. That's all.
OTOH, if you do not update but NEVER connect to WiFi, there will probably be no issue. The method to block updates "works", as I found, but it did not prevent the occasional reboot when I was connected to WiFi, so I finally just threw in the towel and updated my devices, starting over from scratch. I'm happy with the many changes I've made since, so it worked out for me. Not sure why you want to stay with 1.2.1. It is virtually identical to 1.2.2 and I don't believe there is anything on-site here that worked with 1.2.1 which doesn't also work with 1.2.2. All B&N did was patch contacts with their servers for TLS 1.2 compliance.
Deleting/disabling DeviceManager will give your NST Alzheimers as far as your registration is concerned and it will just begin wondering why it can't remember who it is and how/when to phone home--wherever that is. One of the problems with disabling B&N apps is that there are also jar files which don't get disabled and the system still tries to fool with those. You can delete/disable those as well but the more you niggle at the system architecture the more unstable the device becomes and the more things fail to work properly (like the Reader and Library).
Like I said before, it's better AND easier to just treat the device the way it was designed as far as updating or registering. You don't have to use a credit card, you don't even have to use a real e-mail address, I suppose. Then when all that is out of the way you can just install your own launcher and set the "n" button to Home. Voila! You'll never see or hear from the B&N stuff again and your battery will last a good long time.
Click to expand...
Click to collapse
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)
So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?
I can't wait for the battery consumption to be normal, because I am really enjoying my NST with its great ergonomy and the ability to install different readers. Mine is going to be a dedicated offline ebook reader, but a great one. And much of the reason it is so amazing is thanks to folks like you and Renate who have contributed so much. :good:
Winston S. said:
The main reason I want to avoid 1.2.2 is because I tend to value stability overall, and since most of the stuff here was created by the era of 1.2.1 or before, I am leery of doing something that will make things less compatible. Plus I am distrustful of B&N changes on a device this old. I also thought I had read you explaining some changes that needed to be done after a 1.2.2 update to make something work (NM, maybe? I forget.)
So my question was more along the lines of whether, when I register the device, it will be flagged immediately for update and cause some trouble if I don't, or even if the update will be downloaded in the background without me being able to do anything about it. I suppose I could always patch the sqlite file to disable OTA updates and then register. That would be the safest way to go. And you need to use ADB for this to work, right? There is no way to edit the file onboard the NST itself?
Click to expand...
Click to collapse
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.
As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life
nmyshkin said:
There's really no reason to be concerned about the 1.2.2 update. It's all fine. B&N would not go to the trouble on an old device like this only to somehow wreck it. It's just a TLS security update and involves connection to their servers. Since you do not intend to use the device online, the only minor issue (resigning Opera Mobile browser-- which I've already provided elsewhere) is moot for you.
As for changing the OTA flag, you can do it via ADB if you install sqlite3. This is probably best since moving settings.db back onto the device after editing can be tricky. But you could eliminate the entire tango by just updating to 1.2.2 and going on with your life
Click to expand...
Click to collapse
Thank you for clarifying that, I think I have had an overdose of information from reading too many threads in a short span of time and somehow I got the idea NookManager had some sort of issue after the 1.2.2 update that required some tinkering. The fact that the update is limited to the TLS update means it doesn't affect me, so things would be OK. On the other hand, not installing the update also seems like wouldn't be an issue and I really wanted to get ADB going anyway to install things wirelessly, so the most logical path seems to go through the minimal effort required to change that setting anyway. It turns out I already have sqlite3 installed (I am running an Ubuntu system,) so even more reason to do this!
I'll be reading up on the way to get ADB working.
BTW, I know you have proposed probably changing NookManager to address different issues you have encountered. Let me know if I can be of any help. I have no experience building Android components and limited experience compiling, but I would be happy to learn a new skill.
Thanks! :good:
@nmyshkin I easily managed to change the OTA setting through USB ADB. (I'm keeping track of all this process so when I have everything set up I will create a thread for posterity to help anyone else with the same questions.)
Now, the problem I wasn't anticipating is that I didn't foresee the battery problems, so I used that procedure to avoid the Register prompt on startup (Bypass OOBE procedure.) But of course now I don't know how to register the Nook. Do I need to reset to Factory using NookManager, root, disable OTA, and then register? It would be nice if there is a way to avoid this?
EDIT: Searching through another thread I saw your suggestions (almost 3 years old) to use the DeviceRegistrator, so after creating a B&N account I did and it said that the registration was successful, but in Settings the Account is showing up as unavailable, so I restarted the NST, and still I am getting Account Unavailable under Settings. Does the Device Registrator not work anymore? Or have B&N stop registering NST devices?
So I checked by logging into the B&N account and as expected there are no NSTs linked to my account. The DeviceRegistrator app has a few options (Register Device, Authenticate Device, Register User, and Authenticate User.) I didn't touch the User options so I guess that is to create a new account. I just used the "Register Device" option. Do I need to Authenticate Device too, or is this just not working anymore?
I read somewhere that there is also another app called OOBE Reg or something like that that basically runs the default registration procedure, but I haven't found that app in my NST.
I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.
Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.
nmyshkin said:
I actually went down a similar rabbit hole myself at one point when I was investigating selective disabling of B&N apps, etc. Yes, you need to authenticate. That may or may not have the desired effect. Right now DeviceRegistrator is your only option. It may or may not be possible to authenticate a rooted device by this method.
Having said that, maybe it's time to take a step back and ask yourself whether all this angst is worth the end result when the path of least resistance will yield an equally functional result. The answer to that depends, in part, on how much other stuff you have already done. But before you do more things don't forget that the basic device needs to be in optimum working condition (like not eating battery) first.
Click to expand...
Click to collapse
I will Authenticate using DeviceRegistrator and see if it works. The Catch 22 is that if I revert to Factory and then register the device I might have a problem with the 1.2.2 update I want to avoid (but yes, I realize at this point my aversion to 1.2.2 is basically irrational.) So I will try this approach first and report back. I will double check to see if the Nook Device shows up in my B&N account too, and I'll report again.
I agree 100% about putting the device in a sound baseline state before installing a lot into it. I'm documenting all that I do, and when I reach that state I'll create a thread about it. Hopefully it can be of use to someone down the road, because I do see new NST units being bought still every week in eBay.
I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.
Winston S. said:
I was relieved that ADB over USB was already enabled by installing NookManager and that I only needed to create a couple of files in my Ubuntu machine for it to work.
Click to expand...
Click to collapse
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.
nmyshkin said:
That's actually news to me. I had thought the flag for WiFi ADB was set. I've never tried USB.
Click to expand...
Click to collapse
Yes, apparently ADB Konnect is set up so that if you start ADB Wireless it sets the flag, and then unsets it. I just tried ADB through Wireless and it also works.
To update on the DeviceRegistrator, I tried to Authenticate the Device and it didn't work (I got a banner saying that the operation is no longer supported.) So it looks like I will need to restore to Factory, register, and then root (which defeats the purpose of disabling OTA updates, as I can't do that until I root.)
@nmyshkin, is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?
I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?
Winston S. said:
@nmyshkin, is resetting the Nook to factory by using "Erase & Deregister Device" option in the stock Nook Settings the same as resetting to factory.zip from NookManager or holding the two Page Back hardware buttons on startup?
I reset mine using the "Erase & Deregister Device" menu option, and then registered and rooted it again, but still I am having problems with CoolReader (I am using the cr3_0_49_13.apk posted in the relevant thread.) Basically, there are no options to set the refresh interval where they should be, and the Options interface is black. Somebody mentioned this as well but they fixed it by restoring to factory, so I'm wondering what the deal is. Is this the only version of CoolReader people use with the NST?
Click to expand...
Click to collapse
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.
I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.
I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.
nmyshkin said:
No, erase and deregister does just that. It removes your account info and settings. The factory reset is an actual reimaging of the device from the protected onboard image. This can be done with the two button technique, NookManager or eight failed boot attempts.
I'm afraid I can't help much with CoolReader. I once had a version installed but found it had way too many settings for me. I ended up using only the screensaver/book cover option but that was pretty silly and I eventually got rid of and wrote my own app for that.
I located the version for the other fellow, but that's the extent of my knowledge. I'll try it in a bit and see what you're talking about.
Click to expand...
Click to collapse
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!
Winston S. said:
Please, don't waste any time with CoolReader. As usual, you saved the day. I'll reimage the device using the correct procedure, as I mistakenly believed this is what the Erase and Deregister option did. I think this will take care of the CoolReader weirdness, and if not I have found that NoRefresh works remarkably well with it anyway. Thank you!
Click to expand...
Click to collapse
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.
nmyshkin said:
Mmm.....I see nothing in that version of CoolReader thats looks anything like it was adapted for the NST. I got that version from a e-book blog post link so shame on me for passing along bogus stuff. It's definitely NOT the version I once had installed (whatever that was...). The current market version is incompatible and the "new" CoolReader GL installs but does not run. I took a look at the CR home at SourceForge and there are many versions available there but it would be trial-and-error with them--and maybe there is no magic bullet. If you search for "CoolReader" on the forum you will find a variety of references. In some lists of "working" apps there are version numbers. Tracking down one of those might be a start.
Click to expand...
Click to collapse
Thank you for looking at this. I am a little confused, because you helped @ALinkToTao who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..
So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.
Winston S. said:
Thank you for looking at this. I am a little confused, because you helped @ALinkToTao who was having problems with it, and he seems to imply that the version linked here which you referred him to ended up working for him..
So I'm just going to write that off to him being confused about the version he ended up installing. I will see if I find something that works, thanks again.
Click to expand...
Click to collapse
Yeah, so I need to redeem myself there. In my lame defense, I was just going with what was posted here: https://blog.the-ebook-reader.com/2...artial-refresh-and-page-button-support-video/
Clearly that is bogus. So I checked out @wozhere's listed working version, or something close.
I think the place to start is with the 3.1.2 series from the SourceForge home of CoolReader. The attached version looks a lot more like what I remember and has screen refresh options (only visible as settings while viewing a book).
There were many more options on the version I once had, so this one is a starting point only.