Related
I've been reading a lot of people reporting that they first tried TouchNooter and this failed, they then had to restore and try a different rooting method. Can this maybe mean that TouchNooter doesn't work anymore for some reason? Are there people which have recent successes with it?
I got it!
I tried it and failed, and panicked at first. I then realized I could reboot the device, but nothing happened still. ros82 has a great thread with backups, shown here
Anyway, I took the recovery option one, and put it into my NOOK Simple Touch and rebooted. It said resetting to factory, wait till done. When it finished, I was rooted for some reason!
Apparently that "restore to factory" doesn't get around to restoring the boot partition.
I can confirm TouchNooter works - I used 2.1.31 to root a new nook touch that I bought over the weekend (twice).
The device was running 1.1.0 out of the box and I had updated to 1.1.2 before the first attempt. That worked but "device info" showed 1.1.0 after the root, and I couldn't force update the firmware after. Market was working after the 1-day wait as well. I used the 8 hard resets to restore the device and tried again on the stock firmware. Same results. I ended up using the MinimalTouch method after updating to 1.1.2 to root while retaining the firmware update.
Touchnooter did NOT work for me.
I have a new NST, came with 1.1.1 stock, then I manually upgraded to 1.1.2. Registered to B&N, have downloaded several books and transferred some epub and pdf files.
Then tried to root:
Upon starting up the NST with the Touchnooter SD image I created, I got the touchnooter instruction screen, then 20 seconds later did see a quick flash to black, then immediately the Nook startup screen appeared with the 5 dots along the bottom.
The screen stayed there with only the first dot black and it hung.
Waited awhile....10 or 15 min.
Took out the SD card, powered the Nook off then back on without the Touchnooter SD card in it.
The Nook was NOT rooted. Went right to stock Nook screens with my books loaded.
Tried it 2 more times, same result.
WHY doesn't this work on my Nook?
didnt work for me either
looks like touchnooter worked for me, but then on reboot i dont get adw option, just normal nook boots.. tried also salsicha nooter, same thing, why doenst it work for me!!!!
Touchnooter not working
I am sure there is something I can do to get this working, no? Had firmware 1.0.1, used the Touchnooter 2.1.31 booted and saw the little android icon and I started the process. Skipped the sign in and enabled location service, then flash of the screen and back to nook reader home. Restart, no Android icon, just e-reader home screen. Updated firmware to 1.1, retried touchnooter 2.1.31, still nothing comes up on startup, just acts like an e-reader, SD card inserted or not.
Sounds to me like some of you are either missing the prompt to select the launcher on 1st restart, or it's not working for some reason. Do you see the little Button Savior button on the right of the screen? If everything worked, you should be able to use that to get back to ADW. If that doesn't work, your default launcher may be set to B&N's home screen. I'd recommend a complete wipe and try again. TN has worked very well for me on 1.1.x, but be sure to set ADW as your home default on 1st launch if that's what you want.
If you have updated to 1.2, be sure to read around before trying to root. Things have changed a bit, apparently.
No button savior
bobstro said:
Sounds to me like some of you are either missing the prompt to select the launcher on 1st restart, or it's not working for some reason. Do you see the little Button Savior button on the right of the screen? If everything worked, you should be able to use that to get back to ADW. If that doesn't work, your default launcher may be set to B&N's home screen. I'd recommend a complete wipe and try again. TN has worked very well for me on 1.1.x, but be sure to set ADW as your home default on 1st launch if that's what you want.
If you have updated to 1.2, be sure to read around before trying to root. Things have changed a bit, apparently.
Click to expand...
Click to collapse
Arrgg. Unfortunately no, I do not see the button savior on the right. I had it rooted a few months back and restored it to the plain e-reader before trying to re-root again. I thought I did a complete wipe by updating to 1.2. Should I go back to 1.1 and then try the µSD?
Cannot root my Nook touch
shadylady said:
I can confirm TouchNooter works - I used 2.1.31 to root a new nook touch that I bought over the weekend (twice).
The device was running 1.1.0 out of the box and I had updated to 1.1.2 before the first attempt. That worked but "device info" showed 1.1.0 after the root, and I couldn't force update the firmware after. Market was working after the 1-day wait as well. I used the 8 hard resets to restore the device and tried again on the stock firmware. Same results. I ended up using the MinimalTouch method after updating to 1.1.2 to root while retaining the firmware update.
Click to expand...
Click to collapse
I've tried auto-nooter and touchnooter and nothing I try works. My Nook is running version 1.1.0 and WAS rooted before but refuses to root now. I have the nooter image (linux using dd if= method) on the sd card but rebooting the device with the nooter card in it never ends with a rooted nook. It simply boots up normally and then complains that the sd card needs to be formatted. I've tried restting/deregistering the nook and trying again. No dice. This thing will not root.:crying:
praedoratrebates said:
I've tried auto-nooter and touchnooter and nothing I try works. My Nook is running version 1.1.0 and WAS rooted before but refuses to root now. I have the nooter image (linux using dd if= method) on the sd card but rebooting the device with the nooter card in it never ends with a rooted nook. It simply boots up normally and then complains that the sd card needs to be formatted. I've tried restting/deregistering the nook and trying again. No dice. This thing will not root.:crying:
Click to expand...
Click to collapse
- for NST FW 1.2 upgraded from NST with recovery image 1.1 only 'tinynooter' will work (as for now) . You will gain root + adb but not the Market/Google Play.
I
I.1 - do a full recovery (6 failed boot's in a row [reset the device just after it starts booting])
I.2- upgrade to 1.2 manually
I.3- run tinynooter from CWR.
or
II
II.1 - wipe system partition using CWR
II.2 - install 1.1 FW using CWR (from cwr_1.1_zip)
II.3 - upgrade to 1.2 manually
II.4 - apply 'tinynooter' using CWR
same procedure if you just want to root 1.1.
- I.1 or II.1 + II.2 + 'Touchnooter' or any other 'nooter' that used to work
----------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------
I.1 - http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
I.2 / II.3 http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/
I.3 / II.4 http://forum.xda-developers.com/showpost.php?p=26015994&postcount=1
II.2 http://code.google.com/p/nst-recovery/downloads/list
Worked like a charm...after
I was having problems getting touchnooter to work. Running linux and using the dd command I found out I was screwing up the dd command slightly. I'd place the sdcard in my card reader and it would show up on my system as /dev/sdb1 (for instance) so I did the dd if=touchnooter.img of=/dev/sdb1 command but this produced a card that failed to boot even though the rooting software was clearly installed. Changing it to dd if=touchnooter.img of=/dev/sdb fixed the issue and a couple of days of problems rooting my nook became instant root upon reboot.
Now the problem I'm having is installing apps (or finding them). I try and install a google android app and it refuses to install saying my system security isn't setup to allow unsigned (or something like that) apps. I cannot find any security settings anywhere in what is provided by touchnooter that changes this. Also, while I can find a kindle reader app without issue in he amazon app store with a browser on my computer, it refuses to appear when I search the amazon app store from the rooted nook! WTF?
There seems to be a number of issues, in fact. The Opera Mobile app doesn't function, I cannot get gmail set to sync automatically, and I cannot get my yahoo email setup to work. Add to that the inability to install any apps beyond the base provided by touchnooter...I'm thinking of trying again only using the auto-nooter instead.
praedoratrebates said:
Now the problem I'm having is installing apps (or finding them). I try and install a google android app and it refuses to install saying my system security isn't setup to allow unsigned (or something like that) apps. I cannot find any security settings anywhere in what is provided by touchnooter that changes this. Also, while I can find a kindle reader app without issue in he amazon app store with a browser on my computer, it refuses to appear when I search the amazon app store from the rooted nook! WTF?
There seems to be a number of issues, in fact. The Opera Mobile app doesn't function, I cannot get gmail set to sync automatically, and I cannot get my yahoo email setup to work. Add to that the inability to install any apps beyond the base provided by touchnooter...I'm thinking of trying again only using the auto-nooter instead.
Click to expand...
Click to collapse
I suggest updating your nook to FW version 1.2
root with tinynoot as osowiecki shows in the previous post
you can then use adb to install apps
tinynoot will install nookcolortools- open this - and deselect and then reselect install non-markets apps.
this will allow you to install non-market apps
tinynoot doesn't include any google apps.
instead of gmail, I use k9mail - with this I am able to set up my gmail and other emails - all in one app.
Hi,
I've manually installed FW v.1.2.0 on my NSG. Rooting with Nook Manager went without any problems.
Now I'm trying to manually add gapps from glownooter 1.5.26 package. Since it is for older FW it causes hangs on loading screen.
While putting manually files from glownooter with adb, I've found that the root of the problems lies probably in framework.jar. It was patched to provide IMEI for registration purposes, but now it seems that new FW changed that file.
It would be great if it was possible to update authentication patch for fw v.1.2.0 following this thread:
http://forum.xda-developers.com/showthread.php?t=955847
Meanwhile I can boot fine, when the new framework.jar stays untouched. But then I can not go through android initial wizard - on the first screen I can not get through clicking on droid icon. If SetupWizard.apk is removed from nook system boots fine, but apps (apart from YouTube) does not start since device is not connected to google account.
I hope that with little help we would have gapps running on new fw.
zetet said:
Hi,
I've manually installed FW v.1.2.0 on my NSG. Rooting with Nook Manager went without any problems.
Now I'm trying to manually add gapps from glownooter 1.5.26 package. Since it is for older FW it causes hangs on loading screen.
While putting manually files from glownooter with adb, I've found that the root of the problems lies probably in framework.jar. It was patched to provide IMEI for registration purposes, but now it seems that new FW changed that file.
It would be great if it was possible to update authentication patch for fw v.1.2.0 following this thread:
http://forum.xda-developers.com/showthread.php?t=955847
Meanwhile I can boot fine, when the new framework.jar stays untouched. But then I can not go through android initial wizard - on the first screen I can not get through clicking on droid icon. If SetupWizard.apk is removed from nook system boots fine, but apps (apart from YouTube) does not start since device is not connected to google account.
I hope that with little help we would have gapps running on new fw.
Click to expand...
Click to collapse
Have you had any luck with this? having similar issues! When selecting 'My Channel' in Youtube, it gives a 'There was a problem authenticating' message.
Also used NookManager as all attempts at trying to root 1.2.0 with TouchNooter failed. It would never get past the 'your nook is starting up' page.
It came pre-installed with 1.2.0 but looks like I may have to downgrade to get the play store to work:
http://forum.xda-developers.com/showthread.php?t=2040040
Guantonio said:
Have you had any luck with this? having similar issues! When selecting 'My Channel' in Youtube, it gives a 'There was a problem authenticating' message.
Also used NookManager as all attempts at trying to root 1.2.0 with TouchNooter failed. It would never get past the 'your nook is starting up' page.
It came pre-installed with 1.2.0 but looks like I may have to downgrade to get the play store to work:
http://forum.xda-developers.com/showthread.php?t=2040040
Click to expand...
Click to collapse
Hi,
I managed to get through - at least partly. I mean I have working google apps, but market is not working. It seems that BnN changed their framework.jar and the already patched version from nooter is not working anymore - that is why after rooting with nooter Nook is not booting.
If getting working gmail etc. is enough I can give You detailed instructions to get it working - unfortunately it is not single step procedure.
zetet said:
Hi,
I managed to get through - at least partly. I mean I have working google apps, but market is not working. It seems that BnN changed their framework.jar and the already patched version from nooter is not working anymore - that is why after rooting with nooter Nook is not booting.
If getting working gmail etc. is enough I can give You detailed instructions to get it working - unfortunately it is not single step procedure.
Click to expand...
Click to collapse
I already have email working, it was mainly the Play store I was after, thanks anyway.
zetet said:
If getting working gmail etc. is enough I can give You detailed instructions to get it working - unfortunately it is not single step procedure.
Click to expand...
Click to collapse
Yes please, could you explain how to get gmail etc working?
I used k9 mail for my gmail account, I find it is more useful on the nook ereader.
Did you get google calendar working yet?
I created a diff from the glownooter's framework.jar (1.1.5) and the original. I then applied this diff to the 1.2.0 framework.jar. (This is without the debug information.) Although I have since deleted all the gapp stuff, it worked at one time.
This is my first post although I have been reading and researching off of xda for the last 6 weeks.
You have to know what you are doing. If you need help, let me know.
here is the patch I used:
I just posted an addon for NookManager to install Google Apps for firmware 1.2.0 and 1.2.1. The thread is http://forum.xda-developers.com/showthread.php?t=2086582 Hope you find it helpful.
BTW, I used an awk script to patch the smali instead of diff / patch. It's more resilient to changes in the firmware and the oddities of line numbers and baksmali labels. It should make creating a new patch for the next firmware simple. I also added a patch to services.jar to get the setup wizard working and eliminate the YouTube - GMail dance. I'm uploading all my work to github now and will link it from the above thread.
One annoying feature of new Nook HD+ (and assuming Nook HD) is that during initial set up it will look for and force you to update (if one is found). There is a neat and really easy trick to bypass this process.
Once you get to that step in the process, during the process hold down the power button and force it to shut off by selecting "OK" in the prompt. You have to do it before it finishes downloading the update.
Once you power it back on you'll have to restart the whole process of entering your WiFi and information again. When you get to the point where the device looks for an update, it will look for a few seconds and determine that its got the latest version installed and proceed to the next phase.
To make sure you did it correctly just go into "Settings" and check the version. For me my default was 2.0.4, for you it may be different, but either way its not 2.0.5.
I've tested it multiple times and always with great success.
What about 2.0.4 do you prefer over 2.0.5?
Also, let us know if this actually stays on 2.0.4. Those of us who had already registered Nooks (both HD and HD+) when 2.0.5 came out got updated in spite of having turned off auto updates.
lkmiller said:
What about 2.0.4 do you prefer over 2.0.5?
Also, let us know if this actually stays on 2.0.4. Those of us who had already registered Nooks (both HD and HD+) when 2.0.5 came out got updated in spite of having turned off auto updates.
Click to expand...
Click to collapse
It was for rooting purposes, since at the time I couldn't find a rooting tool for 2.0.5, that's why. Also I too had registered once under 2.0.5, and when starting fresh found that this method does work regardless of what you initially registered under. Though it only buys you little time to do whatever modifications you need to to your device before it automatically updates you (you could also leave WiFi turned off too).
dcoke said:
It was for rooting purposes, since at the time I couldn't find a rooting tool for 2.0.5, that's why. Also I too had registered once under 2.0.5, and when starting fresh found that this method does work regardless of what you initially registered under. Though it only buys you little time to do whatever modifications you need to to your device before it automatically updates you (you could also leave WiFi turned off too).
Click to expand...
Click to collapse
What device are you running? Still would like your factory zip.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
dcoke said:
It was for rooting purposes, since at the time I couldn't find a rooting tool for 2.0.5, that's why. Also I too had registered once under 2.0.5, and when starting fresh found that this method does work regardless of what you initially registered under. Though it only buys you little time to do whatever modifications you need to to your device before it automatically updates you (you could also leave WiFi turned off too).
Click to expand...
Click to collapse
Ok, I thought that might be why. Thankfully we can root 2.0.5 now. But it's good to know this method of postponing that initial update if I ever need to reset and start over.
nook hd+ auto-updated after leapinlar root+cwm fixes
My Nook HD+ notified me last night that it had auto-updated to 2.0.6 but I was able to get back my original Nova Prime Launcher and the Google Play store continues to work (it broke Beautiful Widgets, but uninstalling it and reinstalling it fixed that)
I had originally rooted it from 2.0.5 using the Universal Root method here: http://forum.xda-developers.com/showthread.php?t=2062613
I had the following images installed:
NookHD-HDplus-Gapps+Extras-for-stock-rev1.zip
NookHD-HDplus-Universal-Root-rev1.zip
NookHD-HDplus-LocationServices.zip
Using CWM for here:
NookHDplus-bootable-CWM-6023-for-emmc-stock-4GB-rev1.zip
Note - I did not manually update or in anyway 'induce' the update, it just happened. Did I miss something in the instructions to prevent auto-update?
Atleast the play store and Nova Launcher keeps working (not had time to check if root is still working though) But I did notice that the B&N Home launcher keeps showing up more often than before (hitting apps and going back brings back Nova)
Thanks
vtmanryn said:
My Nook HD+ notified me last night that it had auto-updated to 2.0.6 but I was able to get back my original Nova Prime Launcher and the Google Play store continues to work (it broke Beautiful Widgets, but uninstalling it and reinstalling it fixed that)
I had originally rooted it from 2.0.5 using the Universal Root method here: http://forum.xda-developers.com/showthread.php?t=2062613
I had the following images installed:
NookHD-HDplus-Gapps+Extras-for-stock-rev1.zip
NookHD-HDplus-Universal-Root-rev1.zip
NookHD-HDplus-LocationServices.zip
Using CWM for here:
NookHDplus-bootable-CWM-6023-for-emmc-stock-4GB-rev1.zip
Note - I did not manually update or in anyway 'induce' the update, it just happened. Did I miss something in the instructions to prevent auto-update?
Atleast the play store and Nova Launcher keeps working (not had time to check if root is still working though) But I did notice that the B&N Home launcher keeps showing up more often than before (hitting apps and going back brings back Nova)
Thanks
Click to expand...
Click to collapse
We have known for a while that setting the OTA to manual does not seem to stop auto updates anymore. The good news is that it still accepts the root. Just flash universal root again.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
I might have found a way how to disable Nook HD OTA autoupdate feature.
For some reason setting com.bn.device.fota.mode to manual does not work, so there is more straight approach to solve this.
So far i have found two:
1) Once you have rooted your device it is just a matter of editing /etc/hosts file and adding couple of lines
127.0.0.1 nook.com
127.0.0.1 barnesandnoble.com
127.0.0.1 su.barnesandnoble.com
which effectively blocks access to autoupdates, but when you reboot your device, all your data will be erased (nook will restore itself to factory state). So some way around is needed.
2) There is an app on google store called "Android Firewall", install it. Once installed block Wifi for NookConnectivityService. GAPPS and browser will not be affected, you'll get norification "Wifi error". But otherwise wifi is fuctional.
2) There is an app on google store called "Android Firewall", install it. Once installed block Wifi for NookConnectivityService. GAPPS and browser will not be affected, you'll get norification "Wifi error". But otherwise wifi is fuctional.
Click to expand...
Click to collapse
Blocking NookConnectivityService kills connectivity to the Google Play.
greenya said:
1) Once you have rooted your device it is just a matter of editing /etc/hosts file and adding couple of lines
127.0.0.1 nook.com
127.0.0.1 barnesandnoble.com
127.0.0.1 su.barnesandnoble.com
which effectively blocks access to autoupdates, but when you reboot your device, all your data will be erased (nook will restore itself to factory state). So some way around is needed.
Click to expand...
Click to collapse
You can symlink the hosts file. See my HD/HD+ tips thread linked in my signature. Look at item 15. Of course there are othe ways to prevent the update, like symlinking build.prop and doing the white on white repair. But those just cause the update to fail, while this may prevent them even checking. If this works, I may update my CWM zip to include it.
EDIT: After researching this a little I have found an easy way to accomplish this. That is to use AdAway. You can safely use that program if you configure it to put the hosts file on /data. It automatically symlinks it for you. But you need to be rooted to use this app. And it has a feature where you can add your own sites to block. Just add those sites listed in the post above. Then every time AdAway updates its own list, it adds your list to it also. This will block B&N from using those sites to download their updates. But realize that it also blocks you from browsing their site.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
leapinlar said:
EDIT: After researching this a little I have found an easy way to accomplish this. That is to use AdAway. You can safely use that program if you configure it to put the hosts file on /data. It automatically symlinks it for you. But you need to be rooted to use this app. And it has a feature where you can add your own sites to block. Just add those sites listed in the post above. Then every time AdAway updates its own list, it adds your list to it also. This will block B&N from using those sites to download their updates. But realize that it also blocks you from browsing their site.
Click to expand...
Click to collapse
Nice! It works then Including it to CWM zip is a good idea, with a warning, that you get to loose one site. That rooting thing imho is the whole reason for not using it, but substituting with google play.
BTW Is your hybrid cm10.1 stable on nook hd+ ?
greenya said:
Nice! It works then Including it to CWM zip is a good idea, with a warning, that you get to loose one site. That rooting thing imho is the whole reason for not using it, but substituting with google play.
BTW Is your hybrid cm10.1 stable on nook hd+ ?
Click to expand...
Click to collapse
WARNING! Hybrid not for HD+ !!!
greenya said:
BTW Is your hybrid cm10.1 stable on nook hd+ ?
Click to expand...
Click to collapse
My Hybrid setup on the HD+ is experimental and a hacked version by me. And I am running verygreen's 1-07 version of CM10.1. The Hybrid works great and is very stable, but the CM10.1 is buggy.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
leapinlar said:
My Hybrid setup on the HD+ is experimental and a hacked version by me. And I am running verygreen's 1-07 version of CM10.1. The Hybrid works great and is very stable, but the CM10.1 is buggy.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
Seems i missed somewhere something
datas0ft said:
Seems i missed somewhere something
Click to expand...
Click to collapse
You did not miss it. I just got it working this weekend and this is the first I have told anyone. I am going to test it a while before I even consider making it for anyone else. It does work but I had to manually configure some things. And it only works on CM10.1, not CM10. Until we get some better CM10.1's it does not really matter anyway.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
leapinlar said:
You did not miss it. I just got it working this weekend and this is the first I have told anyone. I am going to test it a while before I even consider making it for anyone else. It does work but I had to manually configure some things. And it only works on CM10.1, not CM10. Until we get some better CM10.1's it does not really matter anyway.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
This news change many things. But seems verygreen is so busy last time or found something new interesting.
Anyway. If you need some "hard testing" (when testing may make item dead) then ask me. I have one item with no warranty and ... you know, its not mine ... and its not last one.
greenya said:
I might have found a way how to disable Nook HD OTA autoupdate feature.
For some reason setting com.bn.device.fota.mode to manual does not work, so there is more straight approach to solve this.
So far i have found two:
1) Once you have rooted your device it is just a matter of editing /etc/hosts file and adding couple of lines
127.0.0.1 nook.com
127.0.0.1 barnesandnoble.com
127.0.0.1 su.barnesandnoble.com
which effectively blocks access to autoupdates, but when you reboot your device, all your data will be erased (nook will restore itself to factory state). So some way around is needed.
2) There is an app on google store called "Android Firewall", install it. Once installed block Wifi for NookConnectivityService. GAPPS and browser will not be affected, you'll get norification "Wifi error". But otherwise wifi is fuctional.
Click to expand...
Click to collapse
Thank you for this. It works. I added the manual way to do it via AdAway to my HD/HD+ Tips thread and added a CWM zip to my HD/HD+ CWM thread to automatically do it for you if you are not rooted. Both threads are linked in my signature.
Sent from my Nook HD+ running rooted stock
leapinlar said:
Thank you for this. It works. I added the manual way to do it via AdAway to my HD/HD+ Tips thread and added a CWM zip to my HD/HD+ CWM thread to automatically do it for you if you are not rooted. Both threads are linked in my signature.
Sent from my Nook HD+ running rooted stock
Click to expand...
Click to collapse
Could you also just freeze the NookConnectivityService app using Titanium Backup - seems to work for me
docfreed said:
Could you also just freeze the NookConnectivityService app using Titanium Backup - seems to work for me
Click to expand...
Click to collapse
Someone earlier says doing that blocked his Google Play. Is yours working ok?
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Someone earlier says doing that blocked his Google Play. Is yours working ok?
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
If you mean the Play Store, yes no problem - I don't use any other Play apps (like music, books, etc.). I am on 2.06, rooted, ADW EX Launcher and see no issues whatsoever with WiFi (as a matter of fact, no issue signing in to BN.com and downloading one of my books.
Hi, I have some problems with my NST and really need your help!
1/ I bought my NST over a year ago, running firmware 1.1 and rooted by TouchNooter method for 1.1 and it worked flawlessly!
2/ Lately, I've found out that B&N released firmware 1.2. So I unroot my Nook (using 8 steps button to factory reset) and then upgrade to firmware 1.2.
3/ I also know that the NST with 1.2 firmware can be rooted so I backed my Nook up and try the GlowNooter method (some guys said it can work on NST)!
4/ I rooted my NST successfully w/ GlowNooter (be able to download app from Market, can see the Launcher)!
5/ When i try to open the Super Manager and Opera Mini (app that are installed along with this method), the screen flashes and get back to the homescreen!
6/ Because there is no Manager app on my Nook, I need to downloadd a free Manager app on Market, and sideload Root Manager app (bc I'm familiar with this app) from the SD card.
7/ I can install the app from the SD card, but when i press to run, it act like in number 5, although I check *Allow non-market app* in Nook Color Tools!
8/ I think this rooting method does not support my NST, so I reset my Nook using Noogie img to firmware 1.2!
9/ I try to use the NookManager method to root it but the thing happens again (be able to root to the launcher screen, but can't open the app installed along w/)!
I am sorry that I write a long post but can anyone help me with this problem?
Thank you so much for your help!
Jake!
Can anyone help me pls?
Starving for help!
I'dlove to help, although I don't know how to solve the problem.
But I'd love to see the answer as I'm thinking to update my nook, and don't know how I'll do it, yet.
Odp: [Q] Problem running apps on rooted NST!
Opera mini is badly build to that method. I'd say make a reset, upgrade to 1.2.1 and root using Nook Manager. I guess it is not worth wasting time on checking what is wrong, though you may try to reboot, reinstall, clean apps data...
domi.nos said:
Opera mini is badly build to that method. I'd say make a reset, upgrade to 1.2.1 and root using Nook Manager. I guess it is not worth wasting time on checking what is wrong, though you may try to reboot, reinstall, clean apps data...
Click to expand...
Click to collapse
I think you didn't read the post carefully! I try both NookManager and GlowNooter for more than 2 times (reset after each method) but thing happens the same! Not only just Opera but all the app!
Opera Mini is a piece of junk, try Opera Mobile (slightly less a piece of junk).
Clear the cache:
Code:
adb shell rm -R /data/dalvik-cache/*
Reinstall the app.
If all else fails, post a logcat output of it bombing.
Renate NST said:
Opera Mini is a piece of junk, try Opera Mobile (slightly less a piece of junk).
Clear the cache:
Code:
adb shell rm -R /data/dalvik-cache/*
Reinstall the app.
If all else fails, post a logcat output of it bombing.
Click to expand...
Click to collapse
I have to say I'm not familiar with the adb Connect but I follow your instruction to clear the Dalvik Cache by using CWM!
The apps (SuperManager, ASTRO, Root Explorer and so on) still cannot be opened!
I choose the app, then the screen flashes, back to home screen and nothing happens!
BTW, can you tell me how to change the #164 Kernel using Noogie img, because this kernel doesn't have zip file to run in CWM and I don't know how to use the ADB Connect!
Thank you!
Jake.
Any help, pls?
Odp: [Q] Problem running apps on rooted NST!
Download any zip to update your kernel, and replace the uImage in zip with the one you wish to install.
Wysłane z mojego GT-I5700 za pomocą Tapatalk 2
Hi,
I just got an alert for update to 1.2.2 for NST and NSTG ...
Dear Customer,
We are writing to you regarding a necessary software update for one or more NOOK Devices registered to this email address.
On June 29th, 2018, Barnes & Noble will be upgrading the security software used for data encryption, known as Transport Layer Security (TLS), from Version 1.1 to Version 1.2.
Our records show that your NOOK does not have the most recent NOOK software version, which includes a very important new security update. If you do not complete this update your NOOK service will be interrupted. The following NOOK Devices require an update to be compliant with TLS Version 1.2:
NOOK Color
NOOK Tablet
NOOK HD
NOOK HD+
NOOK Simple Touch
NOOK Simple Touch with GlowLight
NOOK GlowLight
If your NOOK is updated before June 29th, 2018, you should not experience any interruption in your NOOK’s performance.
IF YOUR NOOK IS NOT UPDATED BEFORE JUNE 29TH, YOU WILL NOT BE ABLE TO MAKE ANY PURCHASES OR MANAGE THE NOOK CONTENT IN YOUR LIBRARY UNTIL THE UPDATE IS INSTALLED.
To verify the necessary software version for your NOOK, and install the TLS 1.2 security update on your NOOK, click here to locate the software update file associated with your device and follow the installation instructions on the page. Once installed, your NOOK will continue to function as expected.
If you have any questions, feel free to contact us at 1-800-THE-BOOK (1-800-843-2665) Monday-Friday 8AM-11PM ET and Saturday-Sunday 9AM-11PM ET.
Sincerely,
Barnes & Noble
So what do the experts advise we do ?
@Renate NST, @nmyshkin, @pinguy1982, @yattaro, ... experts for the NST/NSTG ???
my first reaction is ... can i update to 1.2.2 and still be able to create a 'dd' backup image of this update using noogie boot backup method ... will the noogie sd card allow backing up this new version as well ?
If so MY first order of business would be to ... take a noogie backup of the current state of your devices ... factory reset ... update to this latest update version 1.2.2 ... register device ... test your nook library for full functionality ... take a noogie backup of this new version ... and save this update !!!
We can then revert back to the first backup(the current state of our devices) and use the devices as we are using currently ...
that way we will have the update saved before 29th June deadline and depending on what course the active experts for our devices take !!!
Experts advise ?
OK, so FINALLY a downloadable update zip. I'm going to try this on a rooted NST (my spare for experiments) to see what happens. I suspect it will fail. Stay tuned.
Edit: Well, er..... I got distracted so if there were messages I did not see them. What I have now is a device that appears to function but has some issues. For example, in Settings>Device Info>About Your Nook, the "Software Version" is "unavailable". Double tap in the Library (I have one free B&N book there) brings up essentially a blank page with the message "Service Unavailable". So running the update from a local zip file on a rooted device is not going to work.
In my other posts regarding this update I noted that you can root a 1.2.2 device using Nook Manager with a few changes, but there are issues with installing some apps afterwards. That problem is--at least for now--beyond my pay grade. The real problem is that for those wishing to maintain B&N function without losing their customizations, the clock is ticking. It's possible that even if you don't buy from B&N but haven't disabled all their stuff because you want to keep the Library/Reader/Dictionary functioning the system is about to become annoying. I think I have seen the beginning of this already with random error messages about B&N servers even though I disabled automatic OTA updates.
We need a fix.
Update
I had a previous backup of an unregistered 1.2.2 NST so I returned to that, rooted with a modified NookManager, and tried to install all of the apps I use on my "real" NST. What I found was that everything installs (and, I assume, runs) except for Tasker 1.3.3u2 and Opera Mobile 12.1. Even Tasker-generated apps like my Screenshot and USB Audio install and run, but not Tasker itself.
I tried "sneaking" these apps in via adb. I got a [install_parse_failed_unexpected_exception]--and no install. I tried Opera Classic 12.9 with the same result.
When I originally tried this I posted a logcat and @Renate NST remarked that some apps were trying to use SHA-1 signatures and that the NST would only accept MD5. She suggested resigning the offending apps. Exactly why the new FW 1.2.2 was throwing up this problem when the old 1.2.1 did not, I don't know.
I've never had any luck with signing apps (or resigning them, for that matter). I really would like to have both Opera Mobile (the only decent browser for the NST) and Tasker both working.
Anyone with app resigning experience/luck?
Victory!
OK, so now we've got something!
Clearly most apps will install and run without issue. I found two (Taker and Opera Mobile) that would not. Problem solved: head on over to the PlayStore (you can use the YalpStore directly on the NST/G) and install ZipSigner. Copy your non-installing apk files to the NST/G and run ZipSigner. Select the input file (eg. Opera_Mobile_12_1_Generic_Opera_Armv5v7.apk) and essentially everything else can be accepted with defaults.
A new copy of the apk file is generated with a new signature that will allow installation and will run on FW 1.2.2!!!!! And it's so easy
At least it works for Tasker and Opera Mobile. YMMV.
Of course, if you want to update to FW 1.2.2 to maintain B&N function or to avoid potential misbehavior when B&N servers can't be contacted, you will have to start from stock...alas.
I have updated my original post on adapting NookManager to work with 1.2.2: https://forum.xda-developers.com/nook-touch/general/nst-nstg-fw-1-2-2-update-t3785566
I'm not sure about all of the compatibility issues with APK signing.
There was somebody who was having problems with SHA-1 signing not working on some software on some device.
At some point I switched signing my apps with MD5 to signing with SHA-1.
I've never had a problem installing those apps on my NST.
Code:
jarsigner.exe -digestalg SHA1 -sigalg SHA1withRSA -storepass [i]mysecret1[/i] -keypass [i]mysecret2[/i] [i]myapp[/i] [i]mystore[/i]
Signatures are additive. If you want to strip them you could use a ZIP tool or the unsign.exe tool in my signature.