Related
Well, I should have listened to myself. I was going to stick with the stock gtab because of the dangers of modding a new ROM. I even started a thread about keeping my tablet stock.
But stock is so messed up and so hard to work with I decided to go ahead and mod Roebeet's 1.01a version.
It installed the first time. Then I reset the data from the Security Menu. Seemed to be running, but the Tnt side didn't work. Worked from the new Launcher menu and I thought I was home free.
Then it went off and automatically came back on, then the VS birds, the GTab, then birds, then tab.....off button no longer turns off....tried redoing the ROm again....no change....tried again....no change.
Loaded CWM 08 satisfactorily. Tried cleaning the data as suggested in threads. No change. I put 2.20 on another sd card. edited it for SDCARD2. Now I can't get CWM to see the external card to load it.
It did load CWM from SDCARD2!
I'm sure there's something I don't know or have done wrong, but I'm stalemated for the time being. Can't shut the machine off, so just have it idling on AC power.
Can anyone tell me how to get CWM to load from the SDCARD2 so I can see if TnT 2.20 or something else well work?
I'd appreciate suggestions. I knew I should have stuck with stock -- but didn't listen to myself. My bad!
Rev
Follow this guide word for word
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
it will take you back to stock and you can start again.
Im pretty sure you just need to repartition the sdcard. Its under advanced in cwm.
butchconner said:
Well, I should have listened to myself. I was going to stick with the stock gtab because of the dangers of modding a new ROM. I even started a thread about keeping my tablet stock.
But stock is so messed up and so hard to work with I decided to go ahead and mod Roebeet's 1.01a version.
It installed the first time. Then I reset the data from the Security Menu. Seemed to be running, but the Tnt side didn't work. Worked from the new Launcher menu and I thought I was home free.
Then it went off and automatically came back on, then the VS birds, the GTab, then birds, then tab.....off button no longer turns off....tried redoing the ROm again....no change....tried again....no change.
Loaded CWM 08 satisfactorily. Tried cleaning the data as suggested in threads. No change. I put 2.20 on another sd card. edited it for SDCARD2. Now I can't get CWM to see the external card to load it.
It did load CWM from SDCARD2!
I'm sure there's something I don't know or have done wrong, but I'm stalemated for the time being. Can't shut the machine off, so just have it idling on AC power.
Can anyone tell me how to get CWM to load from the SDCARD2 so I can see if TnT 2.20 or something else well work?
I'd appreciate suggestions. I knew I should have stuck with stock -- but didn't listen to myself. My bad!
Rev
Click to expand...
Click to collapse
CWM .12 (the newest one) actually reads from the microSD. But (and this is a big BUT) it has issues with non-padded boot.img files, which is what TnT Lite, and TnT stock based 1.01a1, and stock itself, use. So it's a double edged sword. I still use .08 because of this issue.
I would also recommend the SD card re-partition. You have cwm already so you are halfway there. Worst case it's nvflash time - I have a post on that process, as well.
Fate Zero,
Thanks for the quick reply. I had that post laying on the desk before I even started. It wouldn't work because the G-Tablet would not read or access SCCARD2 as I mentioned in the first post.
Rev
GideonX,
It wasn't that simple, but your suggestion was part of the solution!!! Thanks!!!
Rev
P. S. -- See answer to Roebeet for more info.
Roebeet,
I am back up on TnT 2.20 and your suggestion was a part of what I did.
I really believe something messed up the SDCARD2 operation. After I loaded CWM that way, I couldn't get it to work anymore and so the re-installs keep just trying to load the faulty 1.01a setup.
But here's what I did.
I found the USB option on the Mounts and Storage menu in CWM. I plugged in the cable to mini-USB and my PC. I mounted/turned on the USB and the drive popped up in Explorer on the PC. I could see the old "Update.zip" file and "Recovery" folder on the SDCARD (the ones for 1.01a) and so I erased them. I then copied in the TnT 2.20 files and shut down the links and went back to the G-Tablet and CWM. Still wouldn't work.
So I went to the Advanced menu and re-partitioned the SDCARD -- 2048 and 256 as everyone suggested. Then I just went down the menu in CWM and formatted all the system/cache/sdcard/etc. folders. Then I went by to the USB-PC connection and loaded the ROM files into the newly created and formatted SDCARD folder. Went to the other menu item and told it to apply the zip file -- which it immediately did setting up TnT 2.20.
That rebooted and I went through most of the basic setup, got wireless working, web, etc.
Only problem is I need to get Root Explorer installed to do the Market Fix, and when I went to ES Explorer to go to downloads and install it, it didn't find it in the market. So I will have to figure out a way to install or use something that will let me install the Root Explorer apk I have in the "Downloads" directory on the SDCARD.
I will try to re-think this account and re-write it more accurately when I'm not so bleary-eyed and thick-headed. I have not seen a G-Tablet account of someone rebuilding using the kind of "side-loaded" method I scrabbled together.
Suggestions on how to get to the downloads directory to install apps?
Rev
From CWM,
butchconner said:
Roebeet,
I am back up on TnT 2.20 and your suggestion was a part of what I did.
I really believe something messed up the SDCARD2 operation. After I loaded CWM that way, I couldn't get it to work anymore and so the re-installs keep just trying to load the faulty 1.01a setup.
But here's what I did.
I found the USB option on the Mounts and Storage menu in CWM. I plugged in the cable to mini-USB and my PC. I mounted/turned on the USB and the drive popped up in Explorer on the PC. I could see the old "Update.zip" file and "Recovery" folder on the SDCARD (the ones for 1.01a) and so I erased them. I then copied in the TnT 2.20 files and shut down the links and went back to the G-Tablet and CWM. Still wouldn't work.
So I went to the Advanced menu and re-partitioned the SDCARD -- 2048 and 256 as everyone suggested. Then I just went down the menu in CWM and formatted all the system/cache/sdcard/etc. folders. Then I went by to the USB-PC connection and loaded the ROM files into the newly created and formatted SDCARD folder. Went to the other menu item and told it to apply the zip file -- which it immediately did setting up TnT 2.20.
That rebooted and I went through most of the basic setup, got wireless working, web, etc.
Only problem is I need to get Root Explorer installed to do the Market Fix, and when I went to ES Explorer to go to downloads and install it, it didn't find it in the market. So I will have to figure out a way to install or use something that will let me install the Root Explorer apk I have in the "Downloads" directory on the SDCARD.
I will try to re-think this account and re-write it more accurately when I'm not so bleary-eyed and thick-headed. I have not seen a G-Tablet account of someone rebuilding using the kind of "side-loaded" method I scrabbled together.
Suggestions on how to get to the downloads directory to install apps?
Rev
From CWM,
Click to expand...
Click to collapse
Bleary eyed as well (time for sleep) -- I personally use Titanium Backup for the (primary) Market fix. Has worked every time and I've done it a alot, as you might expect. I'm not sure why the file manager won't let you run an apk from the downloads section, but I believe you can download (and run) the TB apk right off their web site.
I'm guessing from the root explorer comment that you are trying the additional Market fix, for even more apps? Maybe you can get it working enough with the primary fix, to get root explorer? I see it in my own Marketplace, although it's not a free app.
Sounds like you are getting there. I replied back to your PM but I guess I saw it a little late
I was hoping you wouldn't run into a bunch of issues when I wrote you back. You will get it. I think you are almost there.. And I have been in the same boat myself a bunch of times. Nothing like thinking you just wrecked your new toy....
You can use the microsd to load the Vanilla with ClockworksMod, but you are still in a boot loop. So, like others stated format the internal SD. Then use your USB mount option to copy over the stock rom and flash. This will get you back up and running.
Reboot, install TNT lite using Clockwork, reboot, skip Google sign in. Install Titanium and clear that google process. Create a Google Account and reboot.
Market should work after that.
butchconner said:
Roebeet,
I am back up on TnT 2.20 and your suggestion was a part of what I did.
I really believe something messed up the SDCARD2 operation. After I loaded CWM that way, I couldn't get it to work anymore and so the re-installs keep just trying to load the faulty 1.01a setup.
But here's what I did.
I found the USB option on the Mounts and Storage menu in CWM. I plugged in the cable to mini-USB and my PC. I mounted/turned on the USB and the drive popped up in Explorer on the PC. I could see the old "Update.zip" file and "Recovery" folder on the SDCARD (the ones for 1.01a) and so I erased them. I then copied in the TnT 2.20 files and shut down the links and went back to the G-Tablet and CWM. Still wouldn't work.
So I went to the Advanced menu and re-partitioned the SDCARD -- 2048 and 256 as everyone suggested. Then I just went down the menu in CWM and formatted all the system/cache/sdcard/etc. folders. Then I went by to the USB-PC connection and loaded the ROM files into the newly created and formatted SDCARD folder. Went to the other menu item and told it to apply the zip file -- which it immediately did setting up TnT 2.20.
That rebooted and I went through most of the basic setup, got wireless working, web, etc.
Only problem is I need to get Root Explorer installed to do the Market Fix, and when I went to ES Explorer to go to downloads and install it, it didn't find it in the market. So I will have to figure out a way to install or use something that will let me install the Root Explorer apk I have in the "Downloads" directory on the SDCARD.
I will try to re-think this account and re-write it more accurately when I'm not so bleary-eyed and thick-headed. I have not seen a G-Tablet account of someone rebuilding using the kind of "side-loaded" method I scrabbled together.
Suggestions on how to get to the downloads directory to install apps?
Rev
From CWM,
Click to expand...
Click to collapse
FateZero said:
Follow this guide word for word
http://forum.xda-developers.com/showpost.php?p=9439414&postcount=7
it will take you back to stock and you can start again.
Click to expand...
Click to collapse
Worked flawlessly for me. Thanks!
All,
Thanks to those who replied for help, moral support, suggestions, and whatever.
I have been up on 2.2.0 ever since the malfunction that started all this and now have added my desired software, etc.
Bottom line is that with this experience I now think I know enough to hold things together and do whatever testing I want to do. I hate to have learned it the hard way. And I wish I had known enough about CWM to load it first and preserve the stock hardware on it.
I will say that IMHO the G-Tablet rocks. Yes, the screen is substandard, but I usually hold it in front of me or set it up on a stand anyhow. And straight on it's not bad. I will keep following watching for a screen mod.
Again, thanks all.
Rev
I need a .img of the original rom, where can i find? Thanks
Aran83 said:
I need a .img of the original rom, where can i find? Thanks
Click to expand...
Click to collapse
You cant, every NST is unique and using an image from another NST will cause trouble for both you and the NST it came from.
Thanks, nook is bricked but I can read the main partition, which .img I install?
Sorry for my english.
Aran83 said:
Thanks, nook is bricked but I can read the main partition, which .img I install?
Sorry for my english.
Click to expand...
Click to collapse
There's no img you can install.
You can try booting n2T-Recovery (v0.2) from a SD card and see if that helps. (Do not write that image to your NST!)
If not, send me a PM and I'll try to help you out
Something else you can try:
1) Flash noogie.img to an sd card.
2) Hook up your nook to a pc via usb once it has booted, and you should see all the partitions exported there.
3) In one of those partitions (recovery maybe? I'm struggling to remember), there's a factory.zip, which you can then install using the "Install from zip" feature of clockwork mod.
If you go this route, you'll have to reflash your sd card with clockwork mod after you've extracted the factory.zip using noogie.
Seems like kind of a pain, but I just recovered my device using this.
Remains in the screen ROOTED FOREVER and i can't do anything
I think, for michaelwill's method, you need to have linux running. I suggest you to try ros87's suggestion.
if I use backup from nook of my friend?
Aran83 said:
if I use backup from nook of my friend?
Click to expand...
Click to collapse
That is not a good idea, since each NookTouch has a unique information to register. If you are thinking of full restore from your friend's image (1.8GB image), it will overwrite your unique information. In that case, you and your friend's devices cannot register to BnN (or just one device). People says the info is stored in /rom. If you want to know more, you need to dig more. Otherwise try factory reset suggested by ros.
herofmm said:
That is not a good idea, since each NookTouch has a unique information to register. If you are thinking of full restore from your friend's image (1.8GB image), it will overwrite your unique information. In that case, you and your friend's devices cannot register to BnN (or just one device). People says the info is stored in /rom. If you want to know more, you need to dig more. Otherwise try factory reset suggested by ros.
Click to expand...
Click to collapse
Correct!
Using a image from another NST is a very very bad idea!
There are a lot of stuff that's unique to your NST stored in /rom and in rombackup.zip on the Factory partition.
This includes:
Serial Number
Main Board Serial
Product ID
Manufacturing date
SHA hash of Private Key
Public Key in modulus form
WiFi Calibration file
Some unique binary file for your eInk screen
MAC Address
Battery Type
Duplicating the serial will make you or your friend unable to register with B&N
Duplicating / Faking the private/public key pair, will most likely make you unable to register with B&N (I'm currently testing this)
Duplicating a WiFi calibration can cause degraded WiFi performance
Duplicating that EPD vcom file (eInk screen).. well who knows
Duplicating the MAC will cause network troubles if used on the same network.
The wrong Battery Type (I've seen three different so far) can cause charging troubles, and will cause incorrect charge indication.
Don't go there!
NookRestore.img
Try writing NookRestore.img to an mSD card. (You can get a copy at my website: NootRoot)
Hard reset
I had issues rooting my NST and got stuck in a boot loop. After digging and digging through forums I finally discovered the secret to a hard reset. The instructions said to hold the power and the two bottom side buttons down together for over 20 seconds. That worked! My NST was back to when I pulled it out of the box. I then proceeded to re rooting. (my mistake was I did not upgrade the OS before rooting). My bad. Hope this helps someone recover from a stuck boot loop.
Good luck.
chucktate said:
My NST was back to when I pulled it out of the box.
Click to expand...
Click to collapse
No it wasn't, Factory Reset doesn't remove root files or system apps installed by root tools, it only clears custom apps and settings.
While you might think it's back to stock, there are still leftover files and changes in /boot and /system
ros87 said:
Correct!
Using a image from another NST is a very very bad idea!
There are a lot of stuff that's unique to your NST stored in /rom and in rombackup.zip on the Factory partition.
Click to expand...
Click to collapse
Hi, I've just found a way around this - it is possible to restore somebody else's .img file, provided you've backup up your rombackup.zip. Then after, using Noogie, you can overwrite rombackup.zip and the contents of it which are on a different partition. The only danger is that you would potentially overwrite battery type config file, as Nook has couple of them. I gave it a try on mine and it seems fine.
sokoow said:
Hi, I've just found a way around this - it is possible to restore somebody else's .img file, provided you've backup up your rombackup.zip. Then after, using Noogie, you can overwrite rombackup.zip and the contents of it which are on a different partition. The only danger is that you would potentially overwrite battery type config file, as Nook has couple of them. I gave it a try on mine and it seems fine.
Click to expand...
Click to collapse
That is correct.
Problem is that most people who end up in a state where Factory Restore doesn't work has usually managed to overwrite their partition tables and part of the /rom partition.
And at this point it is too late to backup rombackup.zip as it's usually fragmented and cannot be recovered by ext2 file recovery tools.
So.. do a full backup before you do anything to your NST
I found if you restore with holding the two lower buttons it will remove all rooted files.
Googie2149 said:
I found if you restore with holding the two lower buttons it will remove all rooted files.
Click to expand...
Click to collapse
Read post 13 by ros87!
ros87 said:
No it wasn't, Factory Reset doesn't remove root files or system apps installed by root tools, it only clears custom apps and settings.
While you might think it's back to stock, there are still leftover files and changes in /boot and /system
Click to expand...
Click to collapse
Go to my website, download nookRestore.img and write it to an mSD card, Erase and De register, Power Off, then insert mSD then power up, then follow on screen instructions!
[OT - Removed]
[OT - Removed]
Torimu.Joji said:
I'll update the website and post links to XDA.
Click to expand...
Click to collapse
Thank you sir!
By posting proper links you help ensure that people get the most recent software and information
Hello fellow nook owners. My Nook is running 1.1 with TouchNooter. I just noticed there is and update for 1.2 and a alternate root method. My question is how would I go about updating to 1.2. In the NookManager thread it says, "If you've tried rooting your nook unsuccessfully with another utility, it's best to do a factory restore (from NookManager, choose the "Restore" menu and then "Restore factory.zip") and, if your nook came with older firmware, upgrade to the latest 1.2.1 firmware." Does that mean I can install NookManager with what I have now and then do the factory restore?
I apologize if this has been answered before. I am reading through all these separate threads trying to make sense of it, but want to be on the safe side. Thanks for reading.
Odp: [Q] Revert back to stock from touchnooter
NookManager is not something you install, it is an interactive utility which let's you root, backup or restore your nook to default. Restore will extract what is in your factory.zip, after wiping whole data. So I suggest that you push expected system's version, so you will no longer need to perform upgrades, just root after that.
I am on my phone so I won't post steps to do that, they are somewhere here.
Wysłane z mojego GT-I5700 za pomocą Tapatalk 2
domi.nos said:
So I suggest that you push expected system's version, so you will no longer need to perform upgrades, just root after that.
Click to expand...
Click to collapse
Thanks for the quick reply. I am a little unclear where you say, "push expected system version". Are you saying to install the 1.2 update like they recommend on the Barnes and Noble site?
Manual Download Instructions
1. From your computer, click here for the software update file. Select Save and select Desktop as the location. Do NOT modify or change the downloaded file's name in any way. Do NOT open the *.ZIP file.
2. Tap Settings on your NOOK's Quick Nav Bar, then tap Device Info and make sure your NOOK battery charge is at 20% or more.
3. Connect your NOOK to your computer using the USB cable that came with your NOOK. A new, removable drive should show up in My Computer (Mac users will see the NOOK drive appear on the desktop or in devices). You should also see a "USB Mode" message on your NOOK screen.
4. From your computer, drag and drop the downloaded *.ZIP file onto the main directory of the NOOK drive. Do NOT open or unzip the file. You should not create a new folder on the NOOK drive or add the file to any other existing folder.
5. Eject or Safely Remove the NOOK drive after the file transfer is complete.
6. Your NOOK will automatically recognize the file after a few minutes when it goes to sleep mode, and proceed to install the updates.
7. Please do not turn off your NOOK during the installation process.
8. Once the installation is completed, your NOOK will automatically restart.
9. The software has been successfully updated; tap on the small "n" that appears in the status bar for additional information.
Click to expand...
Click to collapse
Thanks again for reading and offering any help. It is much appreciated, Its what keeps me coming back to XDA.
toebee76 said:
Thanks for the quick reply. I am a little unclear where you say, "push expected system version". Are you saying to install the 1.2 update like they recommend on the Barnes and Noble site?
Thanks again for reading and offering any help. It is much appreciated, Its what keeps me coming back to XDA.
Click to expand...
Click to collapse
If you want to upgrade FW version after using any "Nooter" you should perform 'factory reset' (this will remove all your apk's and settings obviously so back them up using for example. 'Titanium Backup'.)
As far as I remember, after rooting Nook no longer sees the update.zip in 'NOOK drive'.
- Revert back to unrooted state (factory reset, manually or using NookManager).
- reboot
- register nook once again
- put update.zip in "NOOK drive" (internal memory)
- put nook to sleep and let it upgrade itself
- let it boot into newly installed 1.2.x
- register nook once again
- turn nook off
- run NookManager again to get root access on new FW
- use 'NTGAppsAttack' to get 'Google Play' on FW 1.2.x
I guess what 'domi.nos' is trying to say is that you could replace your factory.zip (stored in Nook's internal partition) containing FW 1.x with the one containing FW 1.2.x.
After this procedure every time you perform 'factory reset' your nook should revert to FW 1.2.x instead of FW 1.1.x.
Am I right, domi.nos ?
Odp: [Q] Revert back to stock from touchnooter
Yes, i find it better because in my case it was harsh to update using BN instructions.
Wysłane z mojego GT-I5700 za pomocą Tapatalk 2
osowiecki said:
If you want to upgrade FW version after using any "Nooter" you should perform 'factory reset' (this will remove all your apk's and settings obviously so back them up using for example. 'Titanium Backup'.)
As far as I remember, after rooting Nook no longer sees the update.zip in 'NOOK drive'.
- Revert back to unrooted state (factory reset, manually or using NookManager).
- reboot
- register nook once again
- put update.zip in "NOOK drive" (internal memory)
- put nook to sleep and let it upgrade itself
- let it boot into newly installed 1.2.x
- register nook once again
- turn nook off
- run NookManager again to get root access on new FW
- use 'NTGAppsAttack' to get 'Google Play' on FW 1.2.x
I guess what 'domi.nos' is trying to say is that you could replace your factory.zip (stored in Nook's internal partition) containing FW 1.x with the one containing FW 1.2.x.
After this procedure every time you perform 'factory reset' your nook should revert to FW 1.2.x instead of FW 1.1.x.
Am I right, domi.nos ?
Click to expand...
Click to collapse
I guess I don't understand why the B&N firmware update process itself doesn't upgrade the internal copy used
for a factory reset. Why leave this up to the user to figure out? As a back-out stopgap if the 1.2.x firmware is found
defective?
Presumably 1.2.x has been tested a lot before being issued to the user community. Stop laughing.
After all, by definition, 1.x has been found to be defective, otherwise they wouldn't have bothered issuing 1.2.x.
So how can the possibility of a defect in 1.2.x justify keeping around the known defective 1.x in the factory
reset zip? Plus the Nooks are awesome in that it's impossible to brick them(short of taking a screwdriver blade to
the SD slot).
Does somebody know what their reasoning is for this?
Thanks guys. Updating now!
Just because a new version was released doesn't mean the old one was corrupt. If a new feature was added, that justifies the new release, but the old one was in no way broken.
Also, you have a known working firmware archive, any updates could have corruption, bricking the system if used. From a dev standpoint, best to keep a known good version as backup in case something goes wrong, even if there is a vital update.
Backup
I used a backup from another NST to restore my NST, now I noticed my NST has the same MAC address and ID as the other machine. What can I do to get it's identity back?
Unless you have some backup of your nook, you don't have a lot of options. I have to see if the serial and MAC address are on a label anywhere.
If you can some how find the info, you can mount your image, and edit the files that keep it by hand to show your info instead. This is why dd style images aren't always recommended.
In the future make a back before installing or hacking, and make a backup before attempting to restore. The process isn't always fool proof so it helps to roll back.
steveharr said:
I used a backup from another NST to restore my NST, now I noticed my NST has the same MAC address and ID as the other machine. What can I do to get it's identity back?
Click to expand...
Click to collapse
Sorry, took a while to respond, because I forgot which forum this was on.
Anyway, if you still have the box, the serial number should still be on that.
If you no longer have the box, but you did register it with your account, you can pull it up on B&N's website. Log in, goto "My Nook", and then "Manage My Nook". Mouse over the picture of the nook, and it will show you your serial number.
I bought a used nst glowlight (bnrv350), I made a backup, and then I tried to root using glownooter, but had a limited success : I could not install google market or opera mobile.
So I tried to restore the backup, but after "read forever, your nook is starting up", nothing happens, the message just stays there. I can boot with the back button, but it does the same.
I then tried to restore the factory image several times, using all the methods I could find in the internet, but it does the same as above. It has been going on for 24 hours.
The problem might have originated when I could not use winimage in my windows 10 computer to make the backup, and I used windows xp in a virtualbox in my linux computer instead. I used also dd, but I am afraid I don't remember the exact order. The backup size is 426.8 MB.
I reverted back to windows 10 with win32diskimager, with the same result.
Can anything be done ?
sinlog said:
I bought a used nst glowlight (bnrv350), I made a backup, and then I tried to root using glownooter, but had a limited success : I could not install google market or opera mobile.
So I tried to restore the backup, but after "read forever, your nook is starting up", nothing happens, the message just stays there. I can boot with the back button, but it does the same.
I then tried to restore the factory image several times, using all the methods I could find in the internet, but it does the same as above. It has been going on for 24 hours.
The problem might have originated when I could not use winimage in my windows 10 computer to make the backup, and I used windows xp in a virtualbox in my linux computer instead. I used also dd, but I am afraid I don't remember the exact order. The backup size is 426.8 MB.
I reverted back to windows 10 with win32diskimager, with the same result.
Can anything be done ?
Click to expand...
Click to collapse
That backup is too large, I think. Should be more in the neighborhood of 250 MB? Have you tried the factory re-image where you just see the booting up screen and then hold down the two bottom hardware buttons until you get a prompt?
It's difficult--but not impossible--to damage the factory image unless you've been messing with the partitions. If that method does not get you there, consider making a NookManager card and trying to access the re-image routine from its menu.
Thank you for your reply. I just used nookManager. After 5 seconds, it said the backup was successful, but there was no backup in the card. Similarly, it said that rooting was successful, but when I removed the card, it did the same as before : "starting up..." and it stays there.
Do you have another idea ? I downloaded the 1.2.2 update from the b&n site. Can nookManager install it ?
PS: The nook was already 1.2.2
Yes, I used the two lower buttons trick.
sinlog said:
Thank you for your reply. I just used nookManager. After 5 seconds, it said the backup was successful, but there was no backup in the card. Similarly, it said that rooting was successful, but when I removed the card, it did the same as before : "starting up..." and it stays there.
Do you have another idea ? I downloaded the 1.2.2 update from the b&n site. Can nookManager install it ?
PS: The nook was already 1.2.2
Yes, I used the two lower buttons trick.
Click to expand...
Click to collapse
5 seconds is not enough time for NookManager to correctly make a backup. And, backups can only be seen on the card if you connect your NSTG to your PC while NookManager is running. Otherwise the partition is invisible.
It's hard to know since I have no experience with the NSTG. If it were an NST I would suggest that you perform the region change flash, but it's not clear if that will remove your light function or, indeed, if the flash is deep enough to rewrite the areas of your device that appear to be preventing boot. AFAIK there are no ROM images for the NSTG available. But there might be. Somewhere.
I guess if you have exhausted all the possibilities, rather than trashing the device I would try the region change (just flash the US firmware again--I assume that's what's on there already). It may or may not preserve the glowlight capability, but it might at least produce a functioning e-reader. But only as a last resort.
Edit: Hmm.... seems like I've been down this winding road before: https://forum.xda-developers.com/showpost.php?p=72551413&postcount=57
But I emphasize that this process worked for a plain NST, not the NSTG, so it is an absolute last resort (and might not work anyway because you could have a completely different situation). Next thing is to look at the innards of the 1.1 updater and see if Glowlight updates could be substituted...
O.K. So here is a thread that contains a link to an NSTG image and the instructions to write to your device (read down in the thread).
https://forum.xda-developers.com/showthread.php?t=2608815
What "may" happen: your device could end up with a mismatched serial number and or MAC address depending on how this image was made. There is information on this forum for correcting the MAC address. Just a disclaimer. I don't know. IF this is successful, you can then do a manual update to 1.2.2 and then root with the updated NookManager. I've checked the link to the image and it is still good. I got a file that is about 245 MB--seems about right. Presumably you use the image in place of your backup in the restoring process described in the thread.
I am very grateful for your help, but I am afraid I need more. The nook is now functioning and I might not have done it without your hints. As you suspected, the serial number and mac address have changed (I wrote them down before all this). I suppose that's why it did not automatically upgrade to 1.2.2 . Also the device says it's connected to the internet, but it doesn't seem to be.
I searched xda (nstg mac address, nstg serial number), but I didn't find anything meaningful to me (there are posts by Renate and by ros87 but too complex). Can you help, please ?
sinlog said:
I am very grateful for your help, but I am afraid I need more. The nook is now functioning and I might not have done it without your hints. As you suspected, the serial number and mac address have changed (I wrote them down before all this). I suppose that's why it did not automatically upgrade to 1.2.2 . Also the device says it's connected to the internet, but it doesn't seem to be.
I searched xda (nstg mac address, nstg serial number), but I didn't find anything meaningful to me (there are posts by Renate and by ros87 but too complex). Can you help, please ?
Click to expand...
Click to collapse
Oy.
I didn't think you would act so rashly with all my disclaimers. Well, it's done. I actually don't think the MAC address is a big deal unless you begin to have issues.
Did you actually manage to register? If so then the serial number must not currently be in use and the change you effected was deep enough to pass muster. If not....well battery life is said to be shorter for devices that have skipped registration.
Correcting the MAC address is described (sort of) here: https://forum.xda-developers.com/showthread.php?t=1483600
As far as I can guess it involves editing a hex file. Doable, but maybe not needed. There is no way to correct the serial number. It is heavily encrypted with private keys. Again, if you managed to register then this is all moot.
How are you judging lack of internet connectivity?
I was not given the opportunity to register and I don't care about registration, but I'd like to have connectivity. The link you just gave me is for the ros87's thread that I mentioned, and I don't know how to use it. So I suppose I cannot upgrade to 1.2.2 . Should I root the device ?
PS : ros87's last activity was 2 years ago
EDIT : I copied nook_1_2_update.zip in the device and it was installed. I have now 1.2.2
sinlog said:
I was not given the opportunity to register and I don't care about registration, but I'd like to have connectivity. The link you just gave me is for the ros87's thread that I mentioned, and I don't know how to use it. So I suppose I cannot upgrade to 1.2.2 . Should I root the device ?
PS : ros87's last activity was 2 years ago
EDIT : I copied nook_1_2_update.zip in the device and it was installed. I have now 1.2.2
Click to expand...
Click to collapse
You didn't answer my question about connectivity. Are you not able to make a connection? With only the stock device there is nothing to connect to other than B&N. What does it say about "Owner" in the Settings?
Yes, you should root. Be sure to use the NookManager update or it won't work.
Before we even think about the MAC address issue you need root access and some way to tell if you actually have an internet connection. That means some kind of functioning browser, etc.
Do you still have that weird backup? If so, keep it safe somewhere. You may want that someday.
I tried to download a book and I got this : Unable to download, Internal error...
I can ping the nook from the computer.
I will look into rooting the device in 2 or 3 hours and then post again. I suppose this is what you're referring to :
https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048
Thank you for your patience with me.
sinlog said:
I tried to download a book and I got this : Unable to download, Internal error...
Click to expand...
Click to collapse
There is an entire galaxy of mystery contained in that statement. Download from where? Download with what? Do you have an sdcard inserted for storage?
nmyshkin said:
There is an entire galaxy of mystery contained in that statement. Download from where? Download with what? Do you have an sdcard inserted for storage?
Click to expand...
Click to collapse
I meant to download a book from the home page of the nook, where it says New reads. I am still unrooted and I don't leave an sdcard inserted.
sinlog said:
I meant to download a book from the home page of the nook, where it says New reads. I am still unrooted and I don't leave an sdcard inserted.
Click to expand...
Click to collapse
Hmm... I'm surprised there are any books populating that section at all since the device is not registered. In any case, that is no test of connectivity since without registration the NSTG will spit out all kinds of generic messages about connections and failures if you attempt anything that requires access of B&N servers--like buying/downloading a book (which you can't do unless you are registered).
Rooted with nookManager updated. Opera mobile needs to be reinstalled. I can connect to the computer using es file explorer, so wifi is ok. BUT I can't use nookManager because I can't read the icon labels. I'll restore the backup tomorrow and I will try another rooting method. There are 2 more, I think : tiny and glownooter. Are there others ?
sinlog said:
BUT I can't use nookManager because I can't read the icon labels.
Click to expand...
Click to collapse
? Do you mean ADW Launcher? You can fix the icon label issue in the Settings. As I recall the default font color is white. That needs to be changed to black. The size can also be changed. Depending on what icon style you pick the label will either be on one line or, if longer, on two. LOTS of Settings in ADW. Don't write it off without spending some time working with it.
Sorry, I used glownooter. It's a lot like touchnooter, with which I am familiar. I still have to sign in to my google account and to install opera mobile. I'll be back when finished.
Opera mobile is installed and working. I still can't sign in to google but I can use yalp store and that's good. Thanks again, nmyshkin, you saved my nook glowlight.
My nook touch (unrooted) runs 1.2.2, but it has bugs now ( the home button doesn't work most of time, screensaver goes on in several seconds during reading, etc. ). I think a reinstallation of the firmware may most likely resolve the issues. ( already tried erase and deregoster, doesn't change anything, as expected ). But the problem is after putting the update zip file into nook's root directory, nook just erases it without doing anything. So my question: any tool can be used to force nook reinstall the update zip without checking version number? Thx in advance for any help.
smjohn1 said:
My nook touch (unrooted) runs 1.2.2, but it has bugs now ( the home button doesn't work most of time, screensaver goes on in several seconds during reading, etc. ). I think a reinstallation of the firmware may most likely resolve the issues. ( already tried erase and deregoster, doesn't change anything, as expected ). But the problem is after putting the update zip file into nook's root directory, nook just erases it without doing anything. So my question: any tool can be used to force nook reinstall the update zip without checking version number? Thx in advance for any help.
Click to expand...
Click to collapse
You need to do a factory re-image so that the onboard OS version will be older than 1.2.2.
Power down. Then restart, and as soon as the "Read Forever" screen appears, press and hold the two lower hardware buttons. Wait for the prompt. Once the Nook is re-imaged it will accept the update again.
Thank you, but by two lower hardware buttons, you mean the page turning buttons?
nmyshkin said:
You need to do a factory re-image so that the onboard OS version will be older than 1.2.2.
Power down. Then restart, and as soon as the "Read Forever" screen appears, press and hold the two lower hardware buttons. Wait for the prompt. Once the Nook is re-imaged it will accept the update again.
Click to expand...
Click to collapse
Ha, I tried, but problem is the Home button doesn't work. Any other suggestions? Thanks.
smjohn1 said:
Ha, I tried, but problem is the Home button doesn't work. Any other suggestions? Thanks.
Click to expand...
Click to collapse
Yes the two lower "page turning" buttons. Is the "n" button used during that sequence? I didn't remember that. I guess that's in the prompts. Well, I dunno. NookManager can be used to trigger the factory image, but if you say that requires the not-working button, then you are SOL. Even CWM is going to need that button to select options.
nmyshkin said:
Yes the two lower "page turning" buttons. Is the "n" button used during that sequence? I didn't remember that. I guess that's in the prompts. Well, I dunno. NookManager can be used to trigger the factory image, but if you say that requires the not-working button, then you are SOL. Even CWM is going to need that button to select options.
Click to expand...
Click to collapse
Any tools that can be used to peek into Nook's file system through PC ( Linux ) to delete something and add something to trigger re/installation? The whole reason I am trying to reinstall is that the Home button doesn't work most of time, and I checked it is not a hardware problem.
smjohn1 said:
Any tools that can be used to peek into Nook's file system through PC ( Linux ) to delete something and add something to trigger re/installation? The whole reason I am trying to reinstall is that the Home button doesn't work most of time, and I checked it is not a hardware problem.
Click to expand...
Click to collapse
AFAIK what you want to do (if you knew exactly what) requires root access--which you don't have. There is an app that has an option which makes the NST very angry and triggers a no-escape factory reset (I've fallen victim to it once), but to install it you would need--you guessed it--root.
I honestly don't remember whether the factory reset option of NookManager is promptless or just the usual. Seems to me it just takes off once you remove the card and the device reboots, but I could be misremembering. I have another day of work on something and then I will be doing a reset on one of my devices, so I could tell you then.
nmyshkin said:
AFAIK what you want to do (if you knew exactly what) requires root access--which you don't have. There is an app that has an option which makes the NST very angry and triggers a no-escape factory reset (I've fallen victim to it once), but to install it you would need--you guessed it--root.
I honestly don't remember whether the factory reset option of NookManager is promptless or just the usual. Seems to me it just takes off once you remove the card and the device reboots, but I could be misremembering. I have another day of work on something and then I will be doing a reset on one of my devices, so I could tell you then.
Click to expand...
Click to collapse
Thank you very much. Waiting for your experiment results.
1) I can do root. But I couldn't find the package any more. Any pointers?
2) What do you by removing the card? Which card? I was planning to open the back cover and remove the battery, but then I found out you would need a T5 Torx screwdriver, which I don't have. So I gave up.
smjohn1 said:
Thank you very much. Waiting for your experiment results.
Click to expand...
Click to collapse
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
nmyshkin said:
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
Click to expand...
Click to collapse
Thanks a lot and I am in US!
Everything you said was correct with only one minor thing: NookManager doesn't have to be updated to 1.2.2. As is, it will boot. But after factory re-image, 1.2.2 has to be applied, otherwise Nook cannot register due to Nook server's TLS issue even NST says network connection problem.
Thanks again for this wonderful guide. Hope this is useful to other (unlucky) people.
As for my NST, after reinstallation, the Home button still doesn't work. So I have to believe it seems to be hardware problem and the cover has to be opened.
nmyshkin said:
So this is your lucky day. Mark it on the calendar and remember it sometime when it seems to be raining excrement on you.
NookManager invokes the factory re-image without user input. All you have to do is make a NookManager card. If you're not interested in rooting, etc., you don't need to do any of the updates. The original NookManager thread is here and the files are available. You just need an SD card which you can recover later if you don't want to root, etc. If you want to play around with rooting, NookManager needs to be updated for 1.2.2. The directions are in this post. Frankly, if I were you I'd just want to get my device working properly right now and possibly think about other stuff after all the dust has settled.
To use NookManager for the factory re-image, all you have to do is boot your NST with the NookManager card inserted. The app will load and eventually you are asked about starting WiFi. Just say no (I hope your side buttons are working..........). Then you get a screen of options. You want "Rescue" (upper left). Then the lower right (Factory reset). And so on. When you are prompted to remove the SD card, do so and the device will reboot and begin the sequence, eventually delivering you to the start screen for setting up your device.
From my experience, it is possible at this point to connect your NST via USB to your PC and copy the update zip to the "Nook". If you then just let the device sit, it will go to sleep on that first screen and the update will commence. If that's not your experience then you might have to register the older firmware first and then try the update.
Two things: tell me you are not outside the US. That could change everything. And, download a fresh copy of the 1.2.2 update zip. It's possible your original is corrupted.
I hope you are right and that this is not a hardware issue.
Good luck.
Click to expand...
Click to collapse
See the previous one.
smjohn1 said:
Thanks a lot and I am in US!
Everything you said was correct with only one minor thing: NookManager doesn't have to be updated to 1.2.2. As is, it will boot. But after factory re-image, 1.2.2 has to be applied, otherwise Nook cannot register due to Nook server's TLS issue even NST says network connection problem.
Thanks again for this wonderful guide. Hope this is useful to other (unlucky) people.
Click to expand...
Click to collapse
Yes the only reason to update NookManager is to root 1.2.2
I'm sorry about the apparent hardware issue. I don't know where to go with that, but just to throw this out: rooting with NM installs NookTouchMod which would allow you to reassign the "n" button function to another hardware button. Awkward and less than ideal but perhaps a way to salvage the device if all else fails.
nmyshkin said:
Yes the only reason to update NookManager is to root 1.2.2
I'm sorry about the apparent hardware issue. I don't know where to go with that, but just to throw this out: rooting with NM installs NookTouchMod which would allow you to reassign the "n" button function to another hardware button. Awkward and less than ideal but perhaps a way to salvage the device if all else fails.
Click to expand...
Click to collapse
Wonderful and thx again!
Already rooted, and after reboot, saw "Home" and "ReLauncher", chose "ReLauncher", and then the setting icon at upper right. Lots of functions, but didn't see NookTouchMod or where can set up buttons functions. Only saw "Screen buttons behavior" in the Advanced Settings, but these are not to set hardware buttons.
The only I need is in a book reading mode, press a button to return to the library, so that can switch to another book easily. But I guess I am closer now
smjohn1 said:
Wonderful and thx again!
Already rooted, and after reboot, saw "Home" and "ReLauncher", chose "ReLauncher", and then the setting icon at upper right. Lots of functions, but didn't see NookTouchMod or where can set up buttons functions. Only saw "Screen buttons behavior" in the Advanced Settings, but these are not to set hardware buttons.
The only I need is in a book reading mode, press a button to return to the library, so that can switch to another book easily. But I guess I am closer now
Click to expand...
Click to collapse
Mmm....Relaunch. Not my favorite, but many people like it for its "simplicity". There is a way in Relaunch to get to an "app drawer" type screen which shows all the installed apps. That's where you'll find NTM and everything else. The sad truth is, I can't tell you how to get there. For me, Relaunch is counter-intuitive and strange, but I do know that thereis an app drawer as I have seen it myself back in the day when all this was new to me. I've done a cursory forum search but come up empty. That's the other thing that always riled me up about Relaunch. It's like its operations are a secret. There must be documentation somewhere, but I don't know where. I have a vague recollection that at the center bottom of some screen or another there is an actual app drawer symbol, but getting to that magic screen is the issue.
I'll keep looking, but right now I'm coming up empty.
Edit: in the long run, once you find NTM and reassign the "n" button, you might be better served by having the standard B&N home screen as your default launcher. This would provide you with your accustomed functions, easy access to the Library via the quick-nav buttons, etc. You could assign along press of the same button to bring up Relaunch for the few times you'll want it.
nmyshkin said:
Mmm....Relaunch. Not my favorite, but many people like it for its "simplicity". There is a way in Relaunch to get to an "app drawer" type screen which shows all the installed apps. That's where you'll find NTM and everything else. The sad truth is, I can't tell you how to get there. For me, Relaunch is counter-intuitive and strange, but I do know that thereis an app drawer as I have seen it myself back in the day when all this was new to me. I've done a cursory forum search but come up empty. That's the other thing that always riled me up about Relaunch. It's like its operations are a secret. There must be documentation somewhere, but I don't know where. I have a vague recollection that at the center bottom of some screen or another there is an actual app drawer symbol, but getting to that magic screen is the issue.
I'll keep looking, but right now I'm coming up empty.
Click to expand...
Click to collapse
You are right again. I do see "app drawer" at the bottom. Inside there are things like "library", "setting", "app (amazon)", "Kconnect", etc., just couldn't find NTM.
I could reboot to Home too, but I didn't find NTM either. Anyhow, I will dig and search too, and report back here.
Thx again.
smjohn1 said:
You are right again. I do see "app drawer" at the bottom. Inside there are things like "library", "setting", "app (amazon)", "Kconnect", etc., just couldn't find NTM.
I could reboot to Home too, but I didn't find NTM either. Anyhow, I will dig and search too, and report back here.
Thx again.
Click to expand...
Click to collapse
You're fast.
Info on basic ReLaunch functions here: https://github.com/yiselieren/ReLaunch. NTMM icon looks like big bold "n" with a bold little broken circle in it. Gotta be there.
Edit: ...unless....something went awry during the rooting process. You can root "again" with no harm/no foul and watch carefully this time the list of "dones" to make sure it did not throw an error for NTMM.
nmyshkin said:
You're fast.
Info on basic ReLaunch functions here: https://github.com/yiselieren/ReLaunch. NTMM icon looks like big bold "n" with a bold little broken circle in it. Gotta be there.
Edit: ...unless....something went awry during the rooting process. You can root "agai n" with no harm/no foul and watch carefully this time the list of "dones" to make sure it did not throw an error for NTMM.
Click to expand...
Click to collapse
OK, I think I need to go back to basics:
1. here is the NM used: http://download.doozan.com/nook/NookManager-0.5.0.zip
2. Here are some screen shots from relaunch:
1) relauncher
2) all apps installed ( from the middle icon at the bottom ): no NTMM there
3) and 4) settings ( from right icon at the top )
3. I don't see a way to install other Android apps, except from Amazon stores ( which I didn't try ) but not from Google App store. Did I install a "wrong" version of NM?
4. One more thing: I "rooted" again, finished quickly, and no changes after boot ( My guess is NM sees the same root package to decide not to do anything ).
Any advice?
----------------------------------------------------------------------------------------------------
After posting above, I installed NTMM-0.4.0.apk successfully, but it says it needs modified jars. From https://forum.xda-developers.com/showthread.php?t=1991048 and https://github.com/doozan/NookTouchPatches.
So NTMM wasn't installed during root.
Now my questions:
how to install these patches? I am using Linux with no adb ( I don't want to use adb anyway ), any apk file that can be written to sdcard for quick and easy installation?
and does this patch work for 1.2.2?
smjohn1 said:
OK, I think I need to go back to basics.
Click to expand...
Click to collapse
Yes, I think you missed some important points from what I wrote previously. Here is the only sequence that is going to give you the desired result:
1. Factory re-image
2. Install 1.22 update
3. Register
4. Prepare NookManager card from here.
5. Update NookManager card following the directions here. You MUST do at least the update for 1.2.2 or root will not be successful and your device will be messed up. Other updates are optional, but know that some apps like Amazon App Store are dead. Other updates deal with these issues.
6. Boot with the NookManager card inserted.
*Optional* 7. Make a back-up of your registered device running 1.2.2. This can save you extra steps if you need to go back for any reason or suffer some catastrophe that seriously messes with your system.
8. Root using NookManager. Watch the screen for check for any failures.
9. Reboot, choosing ReLaunch as a launcher (but do not set as default yet).
10. Use NTMM to assign "n" button function ("Home") to some other hardware button. This is how you will get to QuickNav buttons.
11. Use NTTM to assign long-press of your reassigned "n" button to ReLaunch.
12. Reboot.
13. Select "Home" as default launcher (i.e., check the little box before choosing "Home". This choice can be changed later if you want.
Now you're back to a functioning system. Additional apps are installed by moving the apk file from your PC to a folder on your NST ("Download"?) and tapping the app icon in ReLaunch. Apps are uninstalled by long-pressing the app icon (I think).
The Amazon App Store is useless as you can read in the directions for updating NookManager.
Don't skip any steps.
nmyshkin said:
Yes, I think you missed some important points from what I wrote previously. Here is the only sequence that is going to give you the desired result:
1. Factory re-image
2. Install 1.22 update
3. Register
4. Prepare NookManager card from here.
5. Update NookManager card following the directions here. You MUST do at least the update for 1.2.2 or root will not be successful and your device will be messed up. Other updates are optional, but know that some apps like Amazon App Store are dead. Other updates deal with these issues.
6. Boot with the NookManager card inserted.
*Optional* 7. Make a back-up of your registered device running 1.2.2. This can save you extra steps if you need to go back for any reason or suffer some catastrophe that seriously messes with your system.
8. Root using NookManager. Watch the screen for check for any failures.
9. Reboot, choosing ReLaunch as a launcher (but do not set as default yet).
10. Use NTMM to assign "n" button function ("Home") to some other hardware button. This is how you will get to QuickNav buttons.
11. Use NTTM to assign long-press of your reassigned "n" button to ReLaunch.
12. Reboot.
13. Select "Home" as default launcher (i.e., check the little box before choosing "Home". This choice can be changed later if you want.
Now you're back to a functioning system. Additional apps are installed by moving the apk file from your PC to a folder on your NST ("Download"?) and tapping the app icon in ReLaunch. Apps are uninstalled by long-pressing the app icon (I think).
The Amazon App Store is useless as you can read in the directions for updating NookManager.
Don't skip any steps.
Click to expand...
Click to collapse
Ha, the step missed was 5, as it was difficult to change the files. But I remade an NM card ( there must be something wrong with the old one ), afterwards it was to update NM to 1.2.2.
Now buttons are reassigned and this reader is usable again ( I don't plan to make it a full android pad, as there are already too many tablets in house ). So this e-reader owes its life to you. Big thanks!
One last thing: how to reset Default back to Home instead of Relaunch? ( The re-root was quick, as it probably installed NTMM. But reboot doesn't give chance to reset default back to Home, it still goes straight to Relaunch. Of course I can live with it, but it would be nicer to configure as you suggested. )
smjohn1 said:
One last thing: how to reset Default back to Home instead of Relaunch? ( The re-root was quick, as it probably installed NTMM. But reboot doesn't give chance to reset default back to Home, it still goes straight to Relaunch. Of course I can live with it, but it would be nicer to configure as you suggested. )
Click to expand...
Click to collapse
If there is a way to access the App Manager through ReLaunch, you can run down the list until you get to ReLaunch and there remove any default actions associated with it.
If that is not obvious then the next easiest thing is to install yet another launcher! So you could transfer a copy of ADW Launcher from the NookManager update page to your NST and install it. If you then reboot it will trigger the App Picker dialog again because now there is a new choice. Before you select "Home", be sure to tick the little check box.
Then you can uninstall ADW Launcher. It's possible that may trigger another App Picker with the remaining two choices but I don't think so.
Once that's sorted you can finish your button reassignments. I think ReLaunch actually hijacks some of the QuickNav buttons so you might have to use NTTM to return them to default or pick completely new assignments, as you like.
I'm glad you were able to get the device back in a usable state. I love my NST for reading. After all these years I think it's still a great little piece of technology.