Database Users

Dummy's Guide to update your I9000 from the stock software to the Official Froyo

After successfully;
researching, upgrading to the official build of my choosing, getting it to work and typing this tutorial out (for those that like me weren't knowledged in this),
I stumbled across this thread. I thought I should also share it here aswell.
Here's a N00b's (Dummy's) Guide to how to update your device from the stock software to the Official Samsung Froyo ROM (software/operating system) OF YOUR CHOICE!!
Why do this?
You get Froyo. So you get the latest version of Android to support more Apps.
It comes with some UI-tweeks, JIT-compiler, and FLASH 10.1 PLAYER!!!
Also you get a newer (better) kernel on your phone with some of Samsung's fixes for the lag and for the GPS.
You can get features/Apps not available in your native rom build and/or remove the bloatware.
This method (not incl E) can also be used to install custom ROMs (I personally can't wait for the Official English MIUI ROM).
** Denotes steps which I skipped, or was unable/unwilling to follow, or didn't quite understand
Here's the comprehensive, step-by-step, easy-to-follow breakdown/walkthrough (Section E only works on Windows Computers):
A) Remove your microSD card (this will prevent some weid issues later on)
A2) Make sure you have Kies downloaded and installed on your computer
A3) Make sure you have an extractor installed (for Windows 7, winRAR is a great free solution)
B) We need to root your device, for this goto "One Click Root/Unroot" by TGA_Gunnman at http://forum.xda-developers.com/showthread.php?t=742403
B1) Download (2.5MB) the software (depending on your computer, mine is Win7 Home Premium 64-bit) into your computer not phone
B2) Make a folder somewhere in your computer labelled "OneClickRoot" (or anything) and drag the .rar file (the one you just downloaded) into it
B3) Extract the contents of the files by Right-Click then "Extract Here" (If you don't have this option install WinRAR)
B4) Set your phone to USB Debug mode (on your phone goto MENU > Settings > Applications > Developement > USB debugging = Checked) and then connect the phone to the computer via USB cable.
B5) Open the "Galaxy S I9000 One-Click Root" application. (This step didn't work for me, so I instead opened "rootme" batchfile which started the command prompt).
B6) Your phone will shut itself off, and then turn on in a "recovery mode". DO NOT REMOVE THE CABLE. Use the Volume Up and Volume Down buttons to get to "install from " and then hit the Home button.
B7) Now your device should be restarting again but this time it will actually go to your lockscreen.
B8) Now, you have ROOT, Congratulations.
B9) Not sure? We can test to see if you have root. Goto Market on your phone and download two Apps (Superuser and Titanium Backup, use the search to find them fast).
B10) Install both and launch Titanium Backup. As soon as you turn it on it will come up with a pop up and say something like "Your device is not rooted" or "Root is not accessible" ... if you didn't get Root.
B11) If you have root it will say something like "Titanium Backup needs to gain permission from Superuser" here click Apply. If you get to the App, well done you have indeed Rooted your phone
C) Now if you want to Backup your device before the update (recommended) you can follow steps C, otherwise skip straight to Step D.
C1) On Titanium Backup if a pop up notification comes with something like "Download an updated BusyBox" allow it to do so.
C2) Now first thing you will want to backup your Apps (all paid and free and the levels/hiscores) make sure you don't have any emulator ROMs on there (they consume too much space) and delete all those unwanted Apps
C3) On Titanium Backup, hit the Menu button > More > Create "update.zip" ...
C4) On this screen select "User application" and "TitaniumBackup-3.6.2.zip" and UN-TICK the "Sign the ZIP file (with ZipSigner)"
C5) Hit the Create "update.zip"... on the bottom and Please wait
C6) Once it finishes it, exit Titanium Backup, go back to settings and disable USB debugging (as posted on B4).
C7) Connect your phone to your computer (through Kies or PC link) and then browse your My Computer until you find Galaxy S I9000.
C8) Open that folder and then open phone. Find "TitaniumBackup-3.6.2.zip" and copy that to somewhere on your computer.
C9) Now that we have backed up your applications, lets backup your ROM.
C10) According to TGA_Gunnman you can use Clockwork MOD Recovery to do this, but this is for a different (Galaxy S) device ie "Samsung Vibrant"
**C11) Follow the steps on http://forum.xda-developers.com/showthread.php?t=734164 to do so, personally I skipped doing so out of fear of bricking the device (there may be subtle differences between the devices that can make your phone a paperweight/brick)
C12) Now if you did follow the Clockwork MOD, be sure to copy the "update.zip" file somewhere into your computer (better be safe than sorry)
D1) Now we need to apply the 3-Button-Combo Fix (this is the only reason for steps A-C because it is highly recommended to have this before flashing ANY rom)
D2) I recommend the Fix by RazvanG http://forum.xda-developers.com/showthread.php?t=821698 because it seems to be the *safest*
**D3) Firstly check if your device is compatible. I wasn't successful to dump my BML1 block, so I couldn't test if the block reads "[email protected]"
**D3) RazvanG has provided some instructions on this method see his post for more information http://forum.xda-developers.com/showthread.php?p=9595936#post9595936
D4) So I took a leap of faith and continued anyways with the risk of bricking my device. I have it on contract/plan so if it fails I would just return it and say Kies was updating and it failed
D5) I followed the steps on the thread but I'll reitterate it here for your convnieance
D6) Download both files (RAZ-FiX-SGS and adbRecovery) from the thread.
D7) Make a new folder (adbRecovery) on your computer and extract the adb .zip file into there
D8) Connect your phone to the computer and copy the RAZ-FiX-SGS.zip into your phone's memory
D9) Delete the old Update.zip file AND rename the RAZ-FiX-SGS.zip to Update.zip
D10) Again, turn on USB debugging (you know how) and open "Recovery" batch file from your computer
D11) This will initiate a command prompt (on Win7) and restart your phone
D12) Your phone will go into recovery mode (like we've seen before)
D13) You need to navigate (Volume buttons) to "apply sdcard; update.zip" and hit the Home button
D14) Your phone will turn off and restart and should get to your lockscreen
D15) So you're at the lockscreen? SUCCESS! (mine didn't brick *pheww*)
D16) Now let's test to see if the 3-Button-Fix worked
D17) *IMPORTANT* Firstly browse into your phone's internal memory and delete update.zip (the one we put there from RazvanG)
D18) Now that you have done so, you can safely just turn off the device
D19) Hold the Volume Down + Home button ... then hold the power button, as soon as the device begins to turn on release the power button (keep holding Volume Down + Home)
D20) If you get a Yellow triangle with the Android robot and "Do not turn off Target", well done, you have the 3BF so you have a means to ensure that you can always recover your phone if you do brick, well done!
D21) You can *safely* remove the battery and restart your phone ONLY if you don't have a Update.zip in the root of your phone
D22) If you don't want to take a leap of faith try this method (safest method but doesn't work for some people): http://forum.xda-developers.com/showthread.php?t=860773
E1) Now is the fun part (we've just past the difficult parts)
E2) You need to hunt down the version of (official Samsung)software you wish to install ... just go through member's reviews and recommendations
E3) You need to find the product code of that build, you can do this navigating through this thread http://forum.xda-developers.com/showthread.php?t=846913
OR by asking members (they can find out with http://forum.xda-developers.com/showthread.php?t=787163)
E4) For me this was the Virgin mobile Australia build (XSA - an unbadged, no-bloatware, unlocked Froyo build with a free copy of Navigon Navigation)
E5) Make sure you update your Kies to "ver 1.5.3.10103_102" (latest as of the time I'm writing)
E6) Go visit this thread http://forum.xda-developers.com/showthread.php?t=835628 for information (the software may have been upgraded)
E7) Download (300KBs) the Kies Registry patcher 1.6.0.0 (latest as of writing) <<This only works on Windows computers, sorry Mac'ners>>
E8) Launch the Kies Registry Patcher WHEN KIES IS OPENED
E9) Click on File > Backup (and save this somewhere in your computer - this is your original product code - better safe than sorry)
E10) Make Enable Spoof to True
E11) Now where it says "Spoof Product Code as" type in the product code of your desire (mine is XSA)
E12) Hit Write Registry and it should say "Registry pathed successfully"
E13) Connect your phone via USB cable to the computer
E14) On your phone select "Samsung Kies" when the pop up comes ... it should be at the "Connected" screen (DO NOT HIT HOME BUTTON)
E15) On Kies it should find your phone, and a pop up on the corner will say "There is a firmware update available for your phone" hit that pop up
E16) Now you will see another pop up and it's asking if you want to "Back up contacts before upgrading firmware" ... seems like a good idea, tick the box and hit Upgrade
E17) If the screen on the phone shuts (ie standby) don't be alerted. Hit the power button to wake it up. DO NOT HIT THE HOME BUTTON!
E18) Another pop up will come to name the contacts file - I just hit save so its the original filename in original (Samsung)folder
E19) Another Pop up will come to say "Save to PC completed" - hit OK, its just letting you know the contacts saved properly
E20) Now you get another Pop up to start the Firmware Upgrade - This is an important area, note down the: Model Name, Current Version and Latest Version (if something goes wrong this info maybe valuable for developers)
E21) Mine is (model)GT-I9000, (current)PDA:JG4 / Phone:JG3 / CSC:JG2 and (latest) PDA:JP5 / Phone:JP3 / CSC:JP4 ......... notice they are diffirent, this is what I was looking for
E22) Hit Upgrade! (Allow Kies to function when Windows 7 or Windows Vista prompts you)
E23) Tick the "All information has been verified" and Click Next
**E24) Let Samsung record your phone number in their database? I don't care (I'm on insurance/contract/plan) and I hit "Allow saving" ad Clicked Next
E25) Wait patiently, its downloading the rom from the server, DO NOT UNPLUG THE DEVICE
E26) A progress bar will appear, your USB will get disconnected, reconnected several times, the phone will be stuck on the yellow triangle screen - these are normal
E27) The progress bar will slowly be filled from grey to blue and a progress bar will appear on your phone - almost there!
E28) The progress bar on the computer will finish and the pop up will read "GT-I9000 Upgrade completed" - Click Close
E29) Your phone will restart and will enter "recovery mode" some yellow texts will appear and scroll forward
E30) The phone will reboot again and you will see the boot image with the Galaxy S logo
E31) The phone will be stuck on that logo for awhile - be patient
E32) The phone will now get to your lockscreen, unlock it
E33) You will have to go through your initial setup firstly its the Swype tutorial, then data settings, and finally the account settings emerges
E34) If the Kies connection screen comes up: hit the home button
E35) Now you should have come to your Homescreen go and test everything (all your passwords, all your bookmarks, all your contacts, all your images/music/videos and all your apps (except bloatware) should be there but the order of all the widgets/apps in TouchWizz will be reset to abc-order)
E36) Goto Settings > About Phone Does it say Android 2.2?
E37) Well done you have passed Android Hacking 101, you are officially smarter than 50% of iPhone and Blackberry users
E38) Donate me a beer, nah just kidding, enjoy everything for free but feel free to donate to the developers that help make this possible

this is a guide for I9000 international
I9000M owners please be advised that the I9000 might cause you to lose the 850 band, and might also trigger the internal SD problem

AllGamer said:
this is a guide for I9000 international
I9000M owners please be advized that the I9000 might cause you to lose the 850 band, and might also trigger the internal SD problem
Click to expand...
Click to collapse
You made it into a thread, thanks!
Hopefully this might help fellow xdanians

Aww Mate this is awesome, I have the same Carrier and I had OPTUS crap on my Phone from custom roms, Now I'm back to Stock Froyo!!!!
A great tool to Start from afresh.....
But
At Instruction E11 - Select your product code from the drop down Box and it will populate the next field for you.

Gonna put into my favorites

Wow.
I don't think anybody that don't now much would read that.
I know allot and i would never use it either.
You should stick a warning sign on this tread.
I did read about half of it and then i just stop and shake my head.
I hope this tread is a joke.....
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram

DamianGto said:
Wow.
I don't think anybody that don't now much would read that.
I know allot and i would never use it either.
You should stick a warning sign on this tread.
I did read about half of it and then i just stop and shake my head.
I hope this tread is a joke.....
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
Click to expand...
Click to collapse
Can you elaborate?
Joke? No it's no joke but I should disclose (as always) this is a tried-and-true way of getting you to update your software but in no way can I be held responsible for damages.
Things may vary slightly in between different phones which is why the links for each source/thread is up there.
I found myself knowing what to do, but always guessing how to do it.
This is a step-by-step process of how and what I did to upgrade my phone to any ROM I want.
If this was posted up before I attempted my upgrade, I would've been so happy that someone really simplified it for me

This is a noobs guide??!!! Simplified??!! I think that everyone will appreciate the time you have spent typing this up and trying to help, but I'm with DamianGto, dude this guide is scary and just explains how YOU got YOUR particular phone running froyo and lets face it, you certainly didn't go about it the easy way!
Once again I think the time you have spent and the willingness to help is admirable, but there are much simpler and noob friendly guides out there

nagrom78 said:
This is a noobs guide??!!! Simplified??!! I think that everyone will appreciate the time you have spent typing this up and trying to help, but I'm with DamianGto, dude this guide is scary and just explains how YOU got YOUR particular phone running froyo and lets face it, you certainly didn't go about it the easy way!
Once again I think the time you have spent and the willingness to help is admirable, but there are much simpler and noob friendly guides out there
Click to expand...
Click to collapse
Well you need root + busybox to get the 3 button fix.
If anything a n00b did, they can recover with 3 button trick otherwise they will have a brick.
This is why this guide is long, to ensure things are a-ok.
If you found a friendlier guide can you post the link, much apprecated ;D

How do I exit downloading mode if I forgot to erase update.zip ?

What is it ? Kies
A2) Make sure you have Kies downloaded and installed on your computer
Thanks

Well I think this is an excellent guide that has great potential!
However, a couple of crucial mistakes, which if fixed could help make the guides less confusing...
At beginning of (D) you talk about (A-C) being solely so you could fix your 3 button download (which I don't think is actually true!)
.... But, you should mention 3 button download at the very start of the guide anyway!!
Also, you should include a quick test at the very start to check for 3 button download, because mine is already fine, so a newbie might run all those extra steps when they already had working 3 button download anyway! (The more sections that can be skipped the better!). You can then steer people to the sections they uniquely will need.
However, titanium backup isn't needed for 3 button download fix, but is a wise step before running a rom update. And this works best with root anyway. Hence I don't think your opener for (D) is very accurate. You didn't just complete those steps JUST to get download mode. The backup was important anyway!
Do others think there should be a stage added for backing up contacts etc?
A stage for backing up efi?
Anything else wise that should be in here?

[GUIDE] Install ClockworkMod, a ROM, Flash Player, and the Market Fix

This is a step by step guide to install ClockworkMod v08, a ROM of your choosing, Flash, and the Android Market fix. This guide assumes that there is no data on your device that is important to you. Back it up or prepare to lose it.
I do NOT accept responsibility for anything good, bad, or indifferent that may come from following this guide. This includes and is not limited to completely destroying your tablet. I highly recommend leaving your tablet plugged in while doing anything like this with your device. I have no idea what will happen if the battery dies in the middle of flashing a ROM (if anything…but better safe than sorry).
ALL THE FILES NEEDED FOR THIS GUIDE EXCEPT FOR THE ROM ITSELF CAN BE FOUND AT THE BOTTOM OF THIS GUIDE.
ROM XDA Pages (Look at these to pick what ROM you want to use.)
TnT Lite
VEGAn-Tab
CyanogenMod 7 (Gingerbread)
Notion Ink Adam ROM Port
You do NOT need to root your tablet to install a ROM on this device using this guide. All the after-market ROMs come pre-rooted so you don't need to root after installing either.
Part One – Install ClockworkMod v08
ClockworkMod is what will ultimately be used for all your flashing of ROMs, backing up, clearing cache, etc.
Step 1.
Download ClockworkMod v08 (This version has been found to work best...the newer version causes some issues with some ROMs.) There are two versions available; one for installing ClockworkMod from the internal memory, one for installing it from external memory (microSD/microSDHC card).
Step 2.
Unzip the file you chose (cwmod_internal.zip OR cwmod_microsd.zip) to the root folder on the storage option of your choice.
So, for example, if the storage option you chose has the drive letter “F:” assigned to it when hooked up to your computer, you would want it to look something like this…
A folder located at “F:\recovery”
A file located at “F:\update.zip”
Step 3.
Turn off your device.
Step 4.
Press the power button and the Volume+ button at the same time and release them when the Viewsonic splash screen pops up. You should see "Detect a recovery key pressed" pop up in the upper left corner of the screen.
Step 5.
Watch ClockworkMod install. This will not take long. Your tablet will reboot when installation is complete.
Step 6.
Enter ClockworkMod:
To get into ClockworkMod you need to shut down your device, then press the Power and Volume+ button (the same way you did to install ClockworkMod).
Navigating ClockworkMod: Vol+ and Vol- are to scroll up and down, the home button selects an option, and the back button backs up.
Step 7.
Re-Partition your Tablet:
In order to make sure the Android Market works correctly after installing any ROM, we must re-partition the device.
Select the advanced option at the bottom of the ClockworkMod menu, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. This erases data on your tablet. Be prepared.
Part Two – Install a ROM.
A ROM (explained in very basic terms) is like Windows on your computer (assuming you’re not running Linux or Mac OS). Each ROM contains a customized version of Android that comes packaged with software, themes, and everything else you actually see when the device powers up. You install any additional apps you would like to use after installing the ROM. Beware, ROMs are device specific. You cannot reliably install ROMs designed for another device.
Step 1.
Now that your device is essentially empty, we need to be able to put files on it. ClockworkMod can do this for us. Connect your tablet’s USB cable from your tablet to your computer. Go to the ClockworkMod main menu, then navigate down to “mounts and storage”, and then select “mount USB storage”. The tablet’s internal storage will then be accessible from your computer. You will want to open it, and create a folder called “ROMs”.
Step 2.
Download whatever ROM you want to use. The links to the ROMs are located above. Click on the link to see what that ROM looks like. The most popular ROMs for this device are TnT Lite and VEGAn Tab.
Step 3.
Copy whatever ROM you wish to install (it should be a .zip file) to the ROMs folder on your tablet. (Leave it zipped, Clockwork will install it from the .zip file as is).
Note: If the ROM you downloaded has multiple files, look for the one named “update.zip” and rename it to whatever you want (something to help you differentiate it from other ROMs), then copy that to the tablet. If an “update.zip” doesn’t exist, and you’re lost…read through that ROM’s thread and see if anybody else asked about it…if not then you probably should (on that ROM’s thread…each one is different).
Step 4.
Turn off your device.
Step 5.
Boot into ClockworkMod. (Press the power button and the volume+ button at the same time until the Viewsonic splash screen pops up, release, then you should see “Detect a recovery key pressed”. After that it will think for a few seconds and then it should boot into ClockworkMod)
Step 6.
Stand up and do a dance. Sitting too long isn't good for you.
Step 7.
Back up to the main menu, then navigate down to “mounts and storage”. When that is highlighted press the home button to select it.
Step 8.
We want to mount “/system” and “/data”.
The goal is to see the following:
“unmount/system”
and,
“unmount/data”
If either one says “mount” instead of “unmount” you need to navigate to that line and press the home button to mount it.
Step 9.
This is the step that we actually flash the ROM in.
From the ClockworkMod main menu, navigate down to “install zip from sdcard” and press the home button to select that option at the menu.
Then, navigate to “choose zip from sdcard” and press the home button to select that option.
Navigate to the line that reads “ROMs” and press the home button to select that option.
Navigate to the line that reads whatever .zip file you wish to install and press the home button to select that option.
Navigate to the line that reads “Yes – Install yourzipfile.zip” and press the home button to select that option.
You will now see it do its thing. When complete you will see something along the lines of “install zip from sdcard complete” at the bottom of the screen.
Press the back arrow over and over again until you get to the Clockwork’s main menu.
Step 10.
Here is where we prepare the system to run the new ROM.
Navigate down to “mounts and storage”, select it, and mount “/system” and “/data” again as in steps 7 and 8.
Back up to Clockwork’s main menu.
Navigate to “wipe data/factory reset”, select it. Navigate down to “Yes – delete all user data”, and select it to wipe out user data and all the cache. (You need to do this for the new ROM to function correctly)
Now, navigate to the top option “reboot system now” and select it. Your tablet will now reboot. It may take up to 15 minutes to start up the first time as it rebuilds the user data and cache for this ROM.
If your tablet boots to UID errors, or has force closes (known to fix a few of them)…
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, and then go to “Fix Permissions”. Afterwards, back out to the main menu, then select “reboot system now”. If that is unsuccessful then boot back into Clockwork and redo steps 7-10.
Part Three – Install Flash and fix Android Market
This is needed to view websites with Flash based content, and to download apps from the market. (Fairly obvious, I know, but just in case somebody doesn't know.) Log in/set up your Google Account before trying the market fix (steps vary on the ROM you are using…in most cases you can access the web accounts by opening the Contacts app, pressing the menu button (the one above the back button), and selecting accounts).
Step 1.
Download “Adobe Flash Player 10.1.120.1.apk” which you will find attached at the bottom of this post and save it on your tablet (I recommend creating a separate folder to save .apk files in).
Step 2.
On your tablet open up whatever file explorer comes pre-installed with the ROM you’ve selected. In there, open up where you saved your .apk, then select Adobe Flash Player, and follow the on screen instructions to finish installing that.
Step 3.
Open the Market app. Once it loads close it (press the home button).
Step 4.
Go into Settings - Applications - Manage Applications - Market - Clear CACHE - Force Stop
(For TnT/TnT Lite... Settings - Applications - System Applications)
Step 5.
Press back once - Google Services Framework - Clear DATA - Force Stop
Step 6.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 4 and 5 until you do.
Step 7.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 8.
Open the market again and enjoy. You should now have Flash and the Android Market.
This is the Titanium Backup method. Thanks to roebeet, xguntherc, and KorbenD.
http://forum.xda-developers.com/showthread.php?t=845175
Part Four – Show your appreciation! (First, be sure to play some Angry Birds)
I encourage everybody to take the time to send a kind message, or a small donation, to everybody that helped make this device what it is. This is not me saying "HEY HEY DONATE TO ME!!!!"...like some developers for other devices do. I just feel like the great ROM developers for this device don't get the credit they deserve, so please at least send them a quick thank you note. Keep in mind that ROMs, utilities, and yes (even guides), take a considerable amount of time to plan, compile, test, fix, and distribute.
With the following link you can donate as much or as little as you would like to me (even a dollar helps). Thanks and enjoy your tablet!
Donate Here

Thank You. This is exactly what we need. One thread with all the info consolidated into one will help many new users understand what to do. People otherwise may have come here and just been blown away by the different threads, I sure was when I first decided to Root my Eris.

scsione889 said:
This is a step by step guide to install ClockworkMod v08, TnT Lite 2.2, Flash, and get the Android Market working. This guide assumes that there is no data on your device that is important to you. Back it up or prepare to lose it.
...
Part Three – Install Flash and fix Android Market
Step 1.
Create a folder on your SD card called APKs. Download “Adobe Flash Player 10.1.120.1.apk” and "TitaniumBackup_latest.apk" which you will find attached at the bottom of this post and save them in that “APKs” folder on your SD card.
Step 2.
On your tablet open up “ES File Explorer”. In there, open up the “APKs” folder, then select Adobe Flash Player, and follow the on screen instructions to finish installing that. After that, select Titanium Backup in that same folder, and install the same way.
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps.
Step 4.
Open up Titanium Backup, go to Backup/Restore and look for Google Services Framework, select it, then select “Wipe Data”
Step 5.
Go back to your home screen and open up the market. You should get an error. If not, redo steps 3 and 4 until you do.
Step 6.
Reboot your device. After it starts back up let it sit for a minute or two to let things in the operating system normalize. Open the Market. Reboot your device.
Step 7.
Open the market again and enjoy. You now have Flash and the Android Market. (Keep in mind, this is not the FULL market, it just makes around 99% of it available. It is unknown which apps are not available. There is a full market fix, but it is MUCH more complicated).
Click to expand...
Click to collapse
Extremely Well Done!
Would be Nice to get this Stickied to keep easy for newbies to find...
Comment on Section 3... I simplified this by removing Steps 4 and 5 and modifying Step 3 to;
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps, [ADD] also 'Clear Data' on 'Google Services Framework' (after stopping it in same screen).
So removes the Need for TB in this proceedure, though TB is always something worth having...
Also I only needed the first reboot in Step 6, wait a few minutes then tried Market and all was fine! No multiple reboots needed for me at least...

Nicely done.
Can you explain in a little more detail why step 8 is needed?
I have already done everything in this post and my tab seems to be working great but never did anything like step 8. I did do the wipes in step 10 so just curious.

LTL11 said:
Nicely done.
Can you explain in a little more detail why step 8 is needed?
I have already done everything in this post and my tab seems to be working great but never did anything like step 8. I did do the wipes in step 10 so just curious.
Click to expand...
Click to collapse
This technically isn't needed for TnT Lite...but if people were to use this guide as guidelines for installing other ROMs (as I hope people would do...you know...following directions is good, but learning what your doing is GREAT), step 8 is something that is always good to get in the habit of doing before a flash.
With many other ROMs, on this device and others, not mounting /data and /system before flashing causes headaches.

jtbnet said:
Comment on Section 3... I simplified this by removing Steps 4 and 5 and modifying Step 3 to;
Step 3.
Go into Settings – Applications – Manage Applications - and Force Stop both the Market and Google Services Framework apps, [ADD] also 'Clear Data' on 'Google Services Framework' (after stopping it in same screen).
So removes the Need for TB in this proceedure, though TB is always something worth having...
Click to expand...
Click to collapse
I did it using 'Clear Data' as well...but this was my way of getting newbies to use TB (and to get more familiarized with side-loading apps). It's a great utility that I feel Android users should be familiar with.

Great guide, added clarifications
The only complication in following these instructions came when I could not locate my /sdcard2 folder using Clockworkmod. Once clockwork was installed using the removable SD card (as suggested), I moved all of my other files to the internal /sdcard folder, as it was the only one (easily?) discoverable. This guide was the only one useable for this android noob.

Tommunicator said:
The only complication in following these instructions came when I could not locate my /sdcard2 folder using Clockworkmod. Once clockwork was installed using the removable SD card (as suggested), I moved all of my other files to the internal /sdcard folder, as it was the only one (easily?) discoverable. This guide was the only one useable for this android noob.
Click to expand...
Click to collapse
Yes, it seems the clockwork version on this guide, does not redirect to SD2 for installs.
You must put them on the internal storage.

omnifox said:
Yes, it seems the clockwork version on this guide, does not redirect to SD2 for installs.
You must put them on the internal storage.
Click to expand...
Click to collapse
Sorry about this guys. Editing it now.
FIXED.

After I got tnt and market working I see the apps but I can't get any of them to download they all fail
thanks in advance
Kevin

kevin stone said:
After I got tnt and market working I see the apps but I can't get any of them to download they all fail
thanks in advance
Kevin
Click to expand...
Click to collapse
Does it display an error? Please be a little bit more specific. Did you try restarting the tablet (not just putting it into standby and bringing it back up)? Also, were you sure to force close the apps before clearing the data?

I did all these steps last night and everything seemed to work as expected. When I woke up this am and actually started to play with the Market, I realized that even though the Market looked good last night, all the important apps are gone this morning. I followed the instructions on the forms and on youtube videos and got the exact same results that were to be expected. I got all the errors and rebooted when asked and thought I was ok. When I opened Market after the Fix Process, all the same apps I would see on my HTC Evo are there. HOWEVER !! once I try to search or change the category to Apps or Games, or go to the sub catagorys 90% of the apps disappear. My app / game selection is now only 1 page long
When Market first opens up, I see Angry Birds and other apps I want, in the category description, but when I try to navigate to them, the screen simply says "loading" and never come up. It will stay that way for over an hour. The only thing I can do is change another catagory. When I do that, the loading text goes away and apps will show up, but alot are missing. Even the category description like for "Action Games" no longer lists Angry Birds in it. And if I try to search for an app I know is in the market like Advanced Task Killer... it says it can't be found.
I repeat the Market Fix process over and over and over again with the exact same results. Any Idea? Everything else seems to be working fine. Flash and Titanium Back up work perfect. Just can't get Market to show all the content.

I just picked up one of these and I'm trying to get this going, but when I mount it to the computer, it doesn't see my 2gb sd card.. The tab see's it fine, but not windows...
Any suggestions?
edit - Got it working... Although it may be getting returned later on. =\

You guys rock!
Picked up my GTab today @ Staples. 45 minutes later it's ready to go with TnT 2.2, full Market access and Flash using this guide! So far...so good!

Thanks for taking the time to write up this guide. Saved me from the slower-than-molasses-out-of-the-box-os-setup they shipped the tablet with.

Can't access Gtablet VIA USB cable from PC
I installed CWM 8, TNT lite 2.2 and performed market fix. Now my Gtab is working great. Prior to this thread I was stuck in a loop. My gtab is running great thanks a lot for posting this tutorial.
My only issue now is I can't access the internal SD from PC. Nothing shows up on my PC when I connect the USB cable to my Gtab. I have tried unmounting and mounting SD several times in CWM.
Prior to this update I was able to access and sideload APK's on my gtab running stock software with Viewsonic update.
any help would be greatly appreciated.
Wyngnut

Well after booting up a couple of times it just started to work (my Gtab showed showed the SD card option). I have downloaded several programs and they all install automatically and every one of then worked. No sideloading no additional steps for install this is amazing. I was coveting the windows 7 tabs on the horizon but the free programs available through the market are amazing and when they are Combined with the Gtab hardware its amazing.
Thanks again for posting this there is no way I would have tried to put this software on my system if I had not seen this guide.
Wyngnut

sano614 said:
I just picked up one of these and I'm trying to get this going, but when I mount it to the computer, it doesn't see my 2gb sd card.. The tab see's it fine, but not windows...
Any suggestions?
edit - Got it working... Although it may be getting returned later on. =\
Click to expand...
Click to collapse
The tablet doesn't seem to like giving the PC access to the microSD card. As far as I know this is a feature that is not available in any ROM. Also, it is my understanding that for this sort of thing to be possible we need to have the device's source code so we can make the hardware/software mesh better.
That is...unless I'm missing something very obvious...which is totally possible.

Thank you so much for taking the time to write this, worked perfectly for me

It's AMAZING!
Thanks to everyone on the site - from Roebeet and pals who pulled it together to scsione889 and others who did the walkthrough. For an absolute newbie (didn't know what "root" meant) to be able in one day to turn an absolute clunker into what I have now is unbelievable.
If you're new like me, and wondering whether you can pull it off, you can. Just make this the one time in your life when you read and follow the instructions exactly, without your usual improvisation!

[HOW TO] Fix the "Low on space" problem (in plain English)

The Problem
The HTC Droid Incredible shows a "Low on space: Phone storage space is getting low" warning despite having gobs of space free because the "Application data storage" folder (also known as /data/data) that is shared by all apps on the phone is only 150mb in size. As soon as only 10% of this folder is available, the warning appears. If it gets too much lower, apps stop responding and the phone crashes.
The Story
After many months of clearing app data, uninstalling apps, resetting my phone, and generally walking on eggshells trying to keep my data storage under the limit, I was getting ready to upgrade my device. I would search every few weeks to see if anyone had solved the problem, but all I found were more people stuck in my boat, and I was ready to give up. But then I stumbled across a series of threads on xda-developers.com that gave me new hope. In the course of one night, I learned from scratch how to root my phone, and I applied a fix that increased the "Application data storage" folder to a whopping 750mb. I am now able to download as many apps as I'd like and not have to worry about clearing out app data ever again.
However, it took a bit of scouring the forums and reading various guides to figure out how to do all this. Some of the items are quite technical in nature, and some of the guides skip steps that more experienced users would know how to do already. So I joined the forum to write this guide for the "regular" users out there like myself. My goal is to explain in plain English how to fix this nagging issue once and for all and to consolidate all the relevant info and files into one place. If you find this useful, please share this with others so we can all fully enjoy our phones!
The Credits
I did not invent any of the steps, tools, or methods I am about to describe. Hats off to the following people for supplying all the info and files I needed to fix the problem and write this how-to thread. Please let me know if I've missed anyone that should be mentioned and I will add them.
vbhines for the "New to Modding/Rooting" guide
The unrevoked team for their excellent one-click rooting software and drivers
dreamersipaq for the guide to rooting an Incredible
scotty1223 for the guide to rooting a 2.3.4 Incredible
jermaine151 for the "no data limit" mod that actually fixes the problem
cmlusco and tiny4579 for all their help answering questions and troubleshooting in this thread
The Ingredients
Here's what you'll need to perform this fix:
An HTC Incredible (obviously) with an SD card
A micro USB cable (you can use the one you charge your phone with)
A computer with a USB port and internet access (PC, Mac, or Linux)
An hour of free time
The Fix
Step 1: Read the "New to Modding/Rooting" guide so you know what you're getting into and can understand the terminology: http://forum.xda-developers.com/showthread.php?t=744807
Step 2: Back up your contacts, pictures, etc. This guide is safe for your phone and will not erase any of your data if you follow it correctly, but it never hurts to back things up just in case.
Step 3a: Make sure your phone is decently charged. (at least 50%)
Step 3b: Make sure your phone isn't currently showing the "low on space" error. Delete some apps or data until the error goes away. You don't want to go through all this effort only to have your phone crash halfway through!
Step 4: Uninstall HTC sync software from your computer. Also make sure you are not running any software that communicates to your phone using USB, such as PDANet or DoubleTwist. If you haven't had to plug your phone into your computer to do anything prior to now, you're probably OK.
Step 5: On your phone, go to Menu -> Settings -> Applications -> Development and put a check in the "USB debugging" box.
Step 6: Plug your phone into your computer, select "Charge Only", select "remember my selection", click "Done", and then unplug your phone.
Step 7: If you are on a Windows PC, follow this user-friendly guide to install the USB drivers you'll need: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
When I did this step, I actually found my Android entry from the first screenshot in the guide under "Android Phone" and it did not say "Android 1.0". Don't worry, you can still use this entry to continue with the next step in the guide to "Update Driver Software".
Mac and Linux users can skip this step.
Step 8: Root your phone. This step is a bit more involved, so be sure to read the directions carefully. On your phone, go to Menu -> Settings -> About phone -> Software information and look at what it says under "Android version" at the top.
If it says 2.3.4, do this:
Download Clockwork 5.0.2.0: http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip (link updated 6/22/12)
Extract the recovery-clockwork-5.0.2.0-inc.img from the zip file and put it somewhere you'll remember.
Download Unrevoked 3.22 (this is intentionally NOT the latest version): http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe (link updated 6/22/12)
Run Unrevoked_3.22.exe
Inside the program, go to File -> Custom Recovery and select the .img file from above. At the bottom of the program window, it should now say "Recovery: Custom" and "Waiting for device"
Plug in your phone and wait while Unrevoked runs automatically. It will reboot your phone several times and will take some time, so be patient!
Once it's done, unplug your phone and ensure that a "Superuser Permissions" application is inside your app drawer. Don't run it. Instead, go to Menu -> Settings -> Applications -> Manage applications -> All, scroll down to "Superuser Permissions", click it, then click "Clear data". Return back Home.
If it says anything other than 2.3.4, do this:
Download Unrevoked 3.32: http://www.unrevoked.com/recovery/
Run reflash_package.exe. It may start up right away, or it may ask you to extract the files. Put them somewhere you can find, and once the extraction is done, find and run reflash.exe.
Plug in your phone and wait while Unrevoked runs automatically. It will reboot your phone several times and will take some time, so be patient!
After the above steps, everyone should do this:
Launch the Android Market and search for "ROM Manager". The first result should be "ROM Manager" by ClockworkMod and it should have a picture of a top hat above a gear as its icon. Click it, then click "Download", then "Accept & download". If it is already installed, you can just return Home.
Once ROM Manager has finished installing, launch it and select "Flash ClockworkMod Recovery" (the first option). Confirm your phone model (HTC Incredible). A window will pop up asking for root permissions - click to allow it.
Optional: After the download completes, scroll down and click "Backup Current ROM". You may need a lot of space free on your SD card to perform this backup depending on what you have on your phone. Once you create this backup, you can use ROM Manager to fully restore your phone (including all apps, data, and settings) in case anything goes wrong. This can take a significant amount of time, so again, be patient!
If all went well, your phone should be exactly the same as it was before, except you now have a couple new apps, and more importantly, root access!
Step 9: On your phone, go to Menu -> Settings -> Applications -> Development and uncheck the "USB debugging" box.
Step 10: Apply the Fix. This is the step you've been waiting for!
Go to this thread: http://forum.xda-developers.com/showthread.php?t=1623038, click the link for the EXT4All files in the first post, download "Convert2Ext4_no_data_limit_normal_dalvik.zip", and put it somewhere you'll remember. You can also go directly to this URL to download the file: http://dinc.does-it.net/EXT4_Mods/ (links updated 6/22/12)
Plug your phone into your computer, bring down the notification bar, select the "USB connection type" item, select "Disk drive", and click Done.
On your computer, find your phone's SD card. If you're unsure which drive is your SD card, look at how big each drive is. The drive that has a size of 6.59GB is the phone's internal memory, so the other drive is the SD card. The SD card that comes with the Incredible is 1.83GB in size, but yours may be different if you bought your own SD card.
Move "Convert2Ext4_no_data_limit_normal_dalvik.zip" from your computer to the SD card. Do not put it inside any folders.
After the file has finished moving, bring down the notifications bar, select the "USB connection type" item, select "Charge only", then click done.
Unplug your phone from your computer.
Launch ROM Manager from your app drawer and click "Reboot into Recovery" (the second option). Click "OK" to proceed.
After the phone reboots, you will now see a black screen with some blue options on it. Use the volume buttons on the left to scroll down to "install zip from sdcard" and click the optical trackpad button at the bottom of the phone to select it.
Click "choose zip from sdcard" (the first option)
Scroll down to the very bottom and select "Convert2Ext4_no_data_limit_normal_dalvik.zip"
Scroll down to "Yes - Install Convert2Ext4_no_data_limit_normal_dalvik.zip" and click it. This step will take some time to complete, and the progress bar may not move at all. Be patient!
Once it is done, click the power button at the top of your phone until you're back at the main menu, then select "Reboot system" (the first option). If you hit power too many times and end up with a blank screen, just hit power one more time and you'll see the menu.
When the phone is done rebooting after this last step, verify that the fix worked by going to Menu -> Settings -> SD & phone storage and look at the "Application data storage" section. It should now say that the "Total space" is 748mb!
At this point you can run happily through an open field, shout from the highest mountaintop, or just shed a tear of joy, because you can now install tons of apps and let them accumulate all the data they want. Enjoy!
P.S. Please let me know if any of these steps are incorrect or unclear so I can fix them. Thanks!
Troubleshooting
Here are a couple of issues people have come across while doing the steps in this guide, along with the solutions. Thanks to cmlusco for these helpful answers!
The guide says my phone should have rebooted back to the main screen, but I'm on a black screen with a bunch of blue options!
If you're on this step and the guide doesn't say you need to be here yet, just use the volume buttons to scroll to the "Reboot System Now" option and click the optical trackpad. Then you can continue on with the guide!
I'm stuck on a black screen with white bars on the side!
If your phone is "s-off", reflash the recovery-clockwork-5.0.2.0-inc.img file from Step #8 using hboot. To get to hboot, turn your phone off, hold the "volume down" button, and turn it back on. Keep holding the "volume down" button until you get to the menu where you can flash the .img file.
If your phone is not "s-off" or you have no idea what "s-off" means, run Unrevoked again with the same .img file from Step #8.
In either case, you should be able to continue using the guide from where you left off!
My phone keeps rebooting over and over and I can't do anything!
Pull out the battery, wait for 15 seconds, and put it back in and turn the phone back on. If it still keeps rebooting, pull out/re-insert the battery again, go into hboot (see above answer) and try the following steps. You can stop as soon as one of them works!
1. Restore a backup that you made in a previous step (if you have one).
2. Reflash the .img file from Step #8.
3. Flash the .img file here: http://dinc.does-it.net/wildstang83_inc_4.08.605.2_11232011.zip (note: this one will take you back to stock, so you'll have to start the guide over).
I'm still stuck!
If all else fails, please post your issue in this thread so someone can help you out. You can also try restoring your backup (you made a backup, right??) and starting over from the top. Good luck!

Potential Alternate Solution
Soniclude that was a great very detailed write up. Here is another option that I found that seems to also solve the dreaded low disk space...
Since you clearly outlined the steps for rooting your device, I wont go into that. But, why stop at fixing one of the most annoying stock problems. Rooting is half the battle to flashing a new rom - which is precisely what I did to stop the LDS issue.
I used to use CM7 and then flashed over to MIUI but recently I flashed the best rom I have used to date - ICS-Dinc AOKP (]http://forum.xda-developers.com/showthread.php?t=1475936) which is a full fledged ICS port for your OG Dinc.
Since then I have not received any LDS errors (although I have not been using this ROM that long) but I would assume that it would be similar to my lengthy experience with CM7, in which I never got the LDS warning.
Here is what my device displays as available space for applications
View attachment 895332
As you can see I have used 144MB with 604MB free for a total of 748MB, identified as internal storage.
Also, just so you can see that this ROM is not an ICS overlay and is truly a port, here is the device info
View attachment 895331
72ls1's (the dev for ICS-Dinc AOKP) has some really good directions and make the process very easy.
For those that are interested and need a few more additional details, here are a few things that helped me:
1. Make sure you have backup your device data, this includes your apps, contacts (you should be just setting all contacts to sync with your gmail account to begin with), messages and email settings. Use an app like Titanium Backup for apps; Backup and Restore app for messages; Call Log Restore for calling
2. Download the zip files outline in the ROM posting of your chocie to your sdcard; They should be placed at the top level of your sdcard, meaning not in another folder. The zip files for ICS-Dinc AOK include the ICS-Dinc zip, Gapps (use this one gapps-ics-20120207-signed.zip - http://goo-inside.me/gapps/gapps-ics-20120207-signed.zip), and Tiamat Kernel
3. In Recovery make a backup of your device (in case you need to flash back due to an error)
4. Within Recovery prior to flashing the rom make sure to unmount data, sdcard and cache
5. Then clear cache and dalivik-cache (this one is under the advanced options)
6. Do a factory reset
7. Install from zip in the following order: ICS-Dinc AOK V.02, Gapps, Tiamat
8. Reset your device
Now go enjoy the goodness of a fresh ice cream sandwich!
Hope this helps anyone else out there in either the low disk space issue or that is having questions about flashing a rom.

Where is Unrevoked 3.22?
I'm going to use the downgrade-and-reflash method to root my 2.3.4 Incredible and after reading the forums have spent the supper hour looking around for Unrevoked 3.22. There was a megaupload site that always says bandwidth is exceeded, and one more that I found where everything is in a language I can't decipher.
Does anybody have a working link to 3.22? All I want is to turn on my stupid wireless hotspot so my wife can use her Ipad in teh car without having to pay Verizon another $30 a month for access to data I already have. Argh!
Thanks,
Ryan

Captainjerky said:
I'm going to use the downgrade-and-reflash method to root my 2.3.4 Incredible and after reading the forums have spent the supper hour looking around for Unrevoked 3.22. There was a megaupload site that always says bandwidth is exceeded, and one more that I found where everything is in a language I can't decipher.
Does anybody have a working link to 3.22? All I want is to turn on my stupid wireless hotspot so my wife can use her Ipad in teh car without having to pay Verizon another $30 a month for access to data I already have. Argh!
Thanks,
Ryan
Click to expand...
Click to collapse
You can actually acomplish that without rooting.
Open dial pad and type ##778# and hit call.
Select edit mode and enter six zeros (000000) as the password.
Select security and look for S.IP DUN username, it should look something like this [email protected]. Change it to be [email protected], just remove the "dun.".
Back out to the main menu and select M.IP Default Profile. Look for DUN NAI and change it to be [email protected], remove the "dun."
Hit the menu button and select commit modifications. Your phone will reboot.
Now just use the stock 3g mobile hotspot app. When you first open it it will say you have to have a subscription and pay, just procede you will not be charged, and verizion is none the wiser. I have been doing this my self for over a year now.

Compass sensor broken
Somebody has the same issue? after flashing the zip i cannot use correctly the compass sensor, for example in SkyMaps app.

This is by far the best tutorial out there to gain root and achieve s-OFF I've come across. Thank you SIR for your time and tutorial. Just EXCELLENT!!

for me the issue was my data/data folder (hint dont sync 1500 facebook friends and never do it with high res pics and with two differant apps haha) =] jsut removed all the contacts i didnt need and turned off the sync from normal facebook app and working perfect now

stuck in loop
I followed the instructions for the 2.3.4 and after I applied the Convert2Ext4_no_data_limit_normal_dalvik fix I got stuck in a loop with at the HTC Incredible boot screen, not sure what to do now.. can only get back to the recovery mode. Not sure what to do from here

scals37 said:
I followed the instructions for the 2.3.4 and after I applied the Convert2Ext4_no_data_limit_normal_dalvik fix I got stuck in a loop with at the HTC Incredible boot screen, not sure what to do now.. can only get back to the recovery mode. Not sure what to do from here
Click to expand...
Click to collapse
If you made or have a previous roms backup. Just wipe everything in mounts and storage menu except sdcard and emmc, then restore your backup. If you dont have a backup flash a fresh rom.

You kind sir are a gentleman and a scholar. That "low space" bug has been annoying me since July 2009. I greatly appreciate you breaking down the l337 sp33k to plain English.
THANK YOU THANK YOU THANK YOU THANK YOU

Captainjerky said:
Does anybody have a working link to 3.22?
Click to expand...
Click to collapse
downloads.unrevoked.com/recovery/3.22/reflash_package.exe
---------- Post added at 01:19 PM ---------- Previous post was at 01:11 PM ----------
Thank you for the spectacular write-up, soniclude!!!
Is there a particular reason that you did not suggest using the no_data_limit_dalvik_moved mod?
Does it not work?

[/COLOR]Thank you for the spectacular write-up, soniclude!!!
Is there a particular reason that you did not suggest using the no_data_limit_dalvik_moved mod?
Does it not work?[/QUOTE]
I agree that this was an excellent how to. Thanks for the effort.
I used the no_data_limit_dalvik_moved mod and for some reason, my phone became really laggy. I'm on Pons CM7. 2. Now I'm a little hesitant to use any of the ext4 mods b/c I don't understand them too well. I'm not clear on why there is a partition in the first place. Why htc devs made it so small... Homework to do.
Sent from my ADR6300 using Tapatalk

Thanks cmlusco I used your method to unlock the 3G Hotspot on my phone and it worked like a charm.

Issue in Step 10
Thank you very much for the easy to follow directions soniclude. I went through all the steps and when I got to step 10, I ran into an issue. After clicking on "Reboot into Recovery" the phone restarts and goes to the white htc screen. After that the screen just goes black with thin white lines down the sides and stays like that. So I never see the blue options. Has anyone come across this? If so, what do I do from there?

I get the message: failed to root. is your firmware too new? What now?
Is there anything I can do now to revert my firmware so I can gain root.

joeyz400 said:
I get the message: failed to root. is your firmware too new? What now?
Is there anything I can do now to revert my firmware so I can gain root.
Click to expand...
Click to collapse
If your on 2.3.4 you need to follow this guide http://forum.xda-developers.com/showthread.php?t=1306400 to root and get s-off.

I understand I could downgrade to 2.2 to get s off but only after I gain root. It seems I can't get rooted because I am running 2.3?
---------- Post added at 06:58 PM ---------- Previous post was at 06:53 PM ----------
It looks like the only step diffrent from the link you posted and this one is to run unrevoked as admin

I think I know what is wrong. The link to Unrevoked 3.22 is not working so I googled it and 3.22 came up but it was actually 3.32 that was downloaded and I can't find 3.22 anywhere. Does anyone have a copy of 3.22?

I found the correct 3.22 and now my Incredible is Incredible!!!! Rooted and it feels so good
Thanks for such a great thread!!!!

SWEEEEEET This worked awesome.

How to force reinstall nook simple touch update 1.2.2

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.

[NST/G] Dealing with non-US (aka "UK") devices in 2021

Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for options 3 or 4 it does not matter as much because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Nook" logo screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there are only two working reader apps besides the stock Reader that can handle Adobe DRM protected epubs: Mantano 2.2.3 Premium (activated or not), and Aldiko 2.0
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions. Since the site seems to be down, here is a link for the image zip.
b. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
c. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Eject the device from the USB connection and tap the power button to put it to sleep. If you hang around you may see the device wake up and the update commence. Otherwise come back awhile later. If the update zip is no longer visible on the Nook drive when it is reconnected to your PC via USB then the update has been done.
d. Register your device. Remember you don't need to use a credit card, just an email address.
e. If you wish to root the device select one of the updated versions of NookManager for FW 1.2.2 that are given here.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
4. Try out my unofficial UK FW 1.2.2 update.

Hello nmyshkin, so glad I found your post! I resurrected one NST glowlight that had problems just now. Thanks a lot!! I followed your instructions, changed region to US, updated to 1.2.2, then used Nook Manager to root. A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!

pkk11 said:
Hello nmyshkin, so glad I found your post! I resurrected one NST glowlight that had problems just now. Thanks a lot!! I followed your instructions, changed region to US, updated to 1.2.2, then used Nook Manager to root. A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
Click to expand...
Click to collapse
Yes, it is possible but there are some special issues surrounding the Glowlight model.
The definitive DIY summary for USB Audio by @Renate NST is buried deep in the original USB Host development thread: https://forum.xda-developers.com/t/wip-usb-host-support-working.1457971/page-19#post-43281985
I recollect that there is a minor path error somewhere in the description, but I will have to search around to find that.
For those who would rather not get their hands quite so dirty (or who don't trust their hands...), there is a CWM-flashable zip prepared by @pinguy1982: https://forum.xda-developers.com/t/cwm-usb-audio-enabler.3139603/. This is what I have used since my first initial set up following the DIY directions, although I swapped in a different kernal. More on that later. The advantage (beyond the obvious) is that the zip contains a tweaked set of audio drivers.
Here, too, there were a few minor issues which I corrected in my own copy, although clearly the package works as it was originally posted.
The issue with the Glowlight revolves around the choice of USB Host-enabled kernals. The one referenced by @Renate NST is for FW 1.1.5. It also enables multi-touch and allows you to run NoRefresh display mode if you desire. However, FW 1.1.5 was written when the concept of the Glowlight was just a glimmer in some developer's eye. Consequently it behaves poorly with the Glowlight control, in essence separating the actual light function from the light icon in the status bar. I use this kernal with my Glowlight because I also run my QuickTiles app and it controls both the light and status bar icon, bypassing the system controls. The reason I chose this kernal is because it allows the use of NoRefresh which I feel is superior to FastMode for text reading.
As far as I know all of the other USB Host-enabled kernals are over-clocked kernals that were designed to allow the usage of the FastMode display mode. This is true of the kernal included in the CWM zip created by @pinguy1982. None of these kernals, to my knowledge, will also work with NoRefresh. There is only one kernal that allows you to use both NoRefresh and FastMode (not at the same time, of course) and that is kernal 166--but for some reason this was not the base for adding USB Host to a 1.2.x kernal. Maybe there is an essential incompatibility. It's way beyond my pay grade.
I've meant to look at this more closely and get some definitive information. This will take a few days and involves backing up my device and trying the various kernals. There is one that claims to support the Glowlight function, USB Host, and NoRefresh but I suspect the author of that post was being sloppy in describing the screen refresh mode.
Anyway, that and tracking down the other minor issues I mentioned above will likely take a few days.

Yeah, I didn't have anything to do with the kernel mods on the NST for USB host mode.
There is one patch for audio sample rates on the page for MergeSmali (in sig).
The current UsbMode-2.2.apk supports NST and Glows (although the Glows need the injectd daemon also).

pkk11 said:
A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
Click to expand...
Click to collapse
OK, so I'm glad you asked this question because it prompted me to look more closely at the kernal issue and I found that there is an appropriate kernal for the Glowlight!
CAUTION: before you do this, use NookManager to make a backup of your device.
For audio playback:
You will need a CWM card to flash the zip. You can make a card from one of the two files at: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. There is a "2 gb" file and one for "128 gb". The card you choose should have at least the capacity mentioned in the file name. Download the file, unzip and burn the image to an SDcard. DO NOT try to install CWM directly onto your device. This will destroy the one fail-safe that makes the NST so hard to kill: the factory image.
Next, download the CWM-flashable USB Audio zip from here: https://forum.xda-developers.com/t/cwm-usb-audio-enabler.3139603/
The kernal in this zip is based on 1.2.x so it will work with a Glowlight. It includes multitouch, enables FastMode (with the appropriate app), and USBHost. It is overclocked, so you may want to install some kind of CPU regulator to calm it down. It will not work with the NoRefresh app.
If you would prefer a kernal that is not overclocked and works with NoRefresh (but not FastMode), you can download the zips here: https://forum.xda-developers.com/t/nstg-kernel-multitouch-usb-host-kernel.2846867/#post-54803848. Unzip the files. Open (not unzip) the CWM-flashable USB Audio zip and inspect the contents (WinRAR allows this kind of thing, not sure about other archiving software). In the "boot" folder you will find the two kernal files. Drag the replacement files you downloaded into this folder (within the archive) and set the overwrite to "storage" or "store". You don't want any more compression going on. Then close the archive.
Once you have the CWM-flashable zip set up the way you want it, copy it to the CWM card. Power down the NSTG, insert the CWM card, power up and wait for completion of boot. This is the button function layout for CWM:
Button layout:
Both Buttons on the left: BACK
Upper button on the right: UP
Lower button on the right: DOWN
n button: SELECT
Power button: TOGGLE DISPLAY
Once you've flashed the zip, you'll need to reboot. If there is a message about possibly losing root, etc., just say no. I've been down that road before.... By attempting to fix a non-existent problem it will create that very problem. So don't let it "fix" nothing.
You need some hardware to make all of these changes actually do something. Also a little software. As far as the hardware, you need an OTG cable (e.g. https://www.ebay.com/itm/Micro-USB-...48?hash=item365c5af32c:g:LmEAAOSwa6heLwTo)and a USB-C audio thingy (e.g. https://www.ebay.com/p/94253551?iid=383621510193 or https://www.ebay.com/itm/Sabrent-Us...259335?hash=item42166fae07:g:v~kAAOSwG5ZekgAB). Both are available on ebay or Amazon and are not expensive. Some audio gizmos include volume control buttons, some don't. I have one of each, but don't use the one with the buttons because it's full of LEDs and the whole USB Host thing drains power anyway, so who needs a bunch of lights?
Some people have had issues with USB Host. I suspect it's because of the OTG cables. The first one I got just did not work. The USB socket on the NSTG is not exactly an industry standard and the cheap OTG cables are not precision instruments. I finally got one that fits well but I have another (right-angle model) which sticks out half-way when fully inserted. It works, but it's worrisome. Also, do not let the cable and audio gizmo dangle. Everything should be on a flat surface. If you put stress on the USB jack and make it unhappy, you're going to have trouble doing something very important: charging. I speak from experience.
Now the software. To activate USB Host (and Audio) you need one or two apps. @Renate NST has a USB Host app as well as an Audio Control app. Both are needed for Audio and are useful if you need to troubleshoot. They can be downloaded from her signature link.
I have found that with a good OTG cable I never have initialization issues with USB Host (on all three devices I own). So I wrote a little one-touch toggle app to turn USB Audio on and off. There are screen prompts to tell you when to connect and disconnect things. Version 4 of the app displays on-screen volume controls as well. You can find that here: https://forum.xda-developers.com/t/app-nst-g-usb-one-touch-toggles.3172213/. The same functionality is also built in to my QuickTiles app, although with nicer screen prompts
If you get this working and are interested in audio recording with the NSTG, there are a few more things to do, but we'll leave that alone for now.

nmyshkin said:
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for option 3 it does not matter because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Read Forever" screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there is only one working reader app besides the stock Reader that can handle Adobe DRM protected epubs. Mantano 2.2.3 Premium (activated or not)
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions.
b. Select one of the updated versions of NookManager for FW 1.2.2 that are given here.
c. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
d. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Allow the device to sleep. Come back awhile later. If the update zip is no longer visible on the Nook drive then the update has been done.
e. Register your device. Remember you don't need to use a credit card, just an email address.
f. Use the updated NookManager card to root and perhaps customize your device.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
g. If you prefer the Oxford dictionary, you can download a copy of the UK 1.2.1 update zip at the bottom of the region changer page.
The dictionary files are located in /system/media/reference/ . Compare what's there with what's on your device and replace. Be sure the file permissions are set the same as what was there before. Reboot.
h. You will need ADB access (either via USB or WiFi) to see the complete localization menu. Connect to the device via ADB and type:
adb shell
am start -n com.android.settings/.LocalePicker --ez hideDevLanguages false
Select the language you prefer. This may cause a reboot.
If you don't have/want ADB, you can install my Nook Settings app. It gives full access to the LocalePicker. If you don't want the app, you can uninstall it after making the Locale change.
Click to expand...
Click to collapse
Heads up, this link https://sites.google.com/site/xcdguides/nook/nookregion on option 3 no longer works but it is archived at https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion and the dropbox download on that page works fine still and is https://www.dropbox.com/s/nwtz0wi6kpb1d3u/nook_region_changer.zip

alexhorner said:
Heads up, this link https://sites.google.com/site/xcdguides/nook/nookregion on option 3 no longer works but it is archived at https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion and the dropbox download on that page works fine still and is https://www.dropbox.com/s/nwtz0wi6kpb1d3u/nook_region_changer.zip
Click to expand...
Click to collapse
Thanks. I noticed the site was down just today whilst trying to help another UK individual. Fortunately I had archived the image zip some time ago against a day such as this. And I, too, referred him to the Wayback machine archive, but I didn't think to test the direct dropbox link. That was clever.
Good grief. Is nothing sacred?!

nmyshkin said:
Thanks. I noticed the site was down just today whilst trying to help another UK individual. Fortunately I had archived the image zip some time ago against a day such as this. And I, too, referred him to the Wayback machine archive, but I didn't think to test the direct dropbox link. That was clever.
Good grief. Is nothing sacred?!
Click to expand...
Click to collapse
Self host FTW!

alexhorner said:
Self host FTW!
Click to expand...
Click to collapse
yah....my Mediafire account is almost full now with all the NST and Nook Tablet stuff I'm trying to save from oblivion. Hope there's room for this one more.

nmyshkin said:
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for option 3 it does not matter because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Read Forever" screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there is only one working reader app besides the stock Reader that can handle Adobe DRM protected epubs. Mantano 2.2.3 Premium (activated or not)
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions.
b. Select one of the updated versions of NookManager for FW 1.2.2 that are given here.
c. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
d. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Allow the device to sleep. Come back awhile later. If the update zip is no longer visible on the Nook drive then the update has been done.
e. Register your device. Remember you don't need to use a credit card, just an email address.
f. Use the updated NookManager card to root and perhaps customize your device.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
g. If you prefer the Oxford dictionary, you can download a copy of the UK 1.2.1 update zip at the bottom of the region changer page.
The dictionary files are located in /system/media/reference/ . Compare what's there with what's on your device and replace. Be sure the file permissions are set the same as what was there before. Reboot.
h. You will need ADB access (either via USB or WiFi) to see the complete localization menu. Connect to the device via ADB and type:
adb shell
am start -n com.android.settings/.LocalePicker --ez hideDevLanguages false
Select the language you prefer. This may cause a reboot.
If you don't have/want ADB, you can install my Nook Settings app. It gives full access to the LocalePicker. If you don't want the app, you can uninstall it after making the Locale change.
Click to expand...
Click to collapse
How would you recommend I copy and replace the dictionaries from the original 1.2.1 firmware file? It does not appear to be a zip file even though it is labelled as such

alexhorner said:
How would you recommend I copy and replace the dictionaries from the original 1.2.1 firmware file? It does not appear to be a zip file even though it is labelled as such
Click to expand...
Click to collapse
I have a vague recollection that it can't be cracked by simply Windows. I believe WinRAR or 7zip will work. I'm downloading a copy from my archive as I type and will give it a shot. I know it can be/has been done.
Yep, WinRAR. I'll just extract the dictionary file and attach it here. Or not. Mmm....too big.
So....you'll need either WinRAR or 7zip to do the job.

nmyshkin said:
I have a vague recollection that it can't be cracked by simply Windows. I believe WinRAR or 7zip will work. I'm downloading a copy from my archive as I type and will give it a shot. I know it can be/has been done.
Yep, WinRAR. I'll just extract the dictionary file and attach it here. Or not. Mmm....too big.
So....you'll need either WinRAR or 7zip to do the job.
Click to expand...
Click to collapse
Had some trouble with 7Zip too, but after opening 7Zip on its own and manually selecting the file, it extracted.
I took the ox_en_GB.db file (the only one in there) and placed it in /system.media/references and 644'd it which is what the other files in that directory were. Nothing to replace, just add. No idea if it works or how to test it, but at least the file is there if I ever wish to use it.
Managed to get the system locale changed fine with NookSettings too, so now thats all good!

alexhorner said:
Had some trouble with 7Zip too, but after opening 7Zip on its own and manually selecting the file, it extracted.
I took the ox_en_GB.db file (the only one in there) and placed it in /system.media/references and 644'd it which is what the other files in that directory were. Nothing to replace, just add. No idea if it works or how to test it, but at least the file is there if I ever wish to use it.
Managed to get the system locale changed fine with NookSettings too, so now thats all good!
Click to expand...
Click to collapse
The only way to test the dictionary is to load up an ebook, long-press on a word, select "Look up" and see what happens.