hello there, i'm a new member in xda-developers
i have a problem, where i failed to root my nook glowlight and i didn't create any backup before that
so, i restore my nook with alpha-format touch where results i lost the glowlight function
i need a factory reset image files so badly, could anyone provide me a link to download the image file?
thanks in advance
have a pleasant day!
The good news is, you can probably restore your device.
The device ships with a partition that touch formatter seems to leave alone, and the partition includes some files that you need.
To trigger that recovery, try using the 0.1 release of the recovery tool, the 2 meg download, from here:
http://forum.xda-developers.com/showthread.php?t=1289233
All that tool does is tell your NSTG that it did not boot 8 times and needs to reset.
There is no single "recovery image," every NST or NSTG has some unique data which, should you restore someone else's device, will prevent you from registering your device correctly with BN.
If you still are unable to get the glow working, you will need to manually install a working kernel after you have restored your correct OS.
Hopefully you don't need to do that, but PM me if you need assistance - post publically as well, but PM me so I have a better chance at seeing it. I'm not reading every day.
Restoring Factory Image
This is a good thread for tips and tricks with your nook nookdevs.com/Tips_and_tricks (can't insert links, because I'm noob here)
To restore your Nook ST to a factory image, not the stock image. But the same as when it came from the factory. You will lose all you shelves and books. But the books are downloadable again from B&N.
1. Hold down power button for 3 to 5 seconds, when asked tell it to shut off.
2. Wait a couple of seconds.
3. Hold down power button for 3 to 5 seconds. As soon as Nook ST begins to start, flashing a white page, immediately followed by black page, grab hold of the power button again for 12 to 15 seconds.
4. Repeat 5 times.
Your Nook will not start up all the way.
After the 6th time you should see a pop up that asks if you want to put yout Nook back to factory default settings.
Say yes, say yes.
Let it do it's thing then restart the Nook.
You should be good to go.
Hope this helps,
dandielionous
To boot into recovery (either factory or Clockwork Mod if you installed that):
Power down your Nook.
Power it up.
As soon as the screen changes at all, hold down the lower left and lower right hard keys.
Wait with sore thumbs for 30 seconds or so until the recovery screen show ups.
Renate NST said:
To boot into recovery (either factory or Clockwork Mod if you installed that):
Power down your Nook.
Power it up.
As soon as the screen changes at all, hold down the lower left and lower right hard keys.
Wait with sore thumbs for 30 seconds or so until the recovery screen show ups.
Click to expand...
Click to collapse
Thanks a lot! I've been asking this for a few days now over in the nook dev section under the specific tools used for rooting. Worked perfectly.
Nook Glowlight help.
roustabout said:
The good news is, you can probably restore your device.
The device ships with a partition that touch formatter seems to leave alone, and the partition includes some files that you need.
To trigger that recovery, try using the 0.1 release of the recovery tool, the 2 meg download, from here:
http://forum.xda-developers.com/showthread.php?t=1289233
All that tool does is tell your NSTG that it did not boot 8 times and needs to reset.
There is no single "recovery image," every NST or NSTG has some unique data which, should you restore someone else's device, will prevent you from registering your device correctly with BN.
If you still are unable to get the glow working, you will need to manually install a working kernel after you have restored your correct OS.
Hopefully you don't need to do that, but PM me if you need assistance - post publically as well, but PM me so I have a better chance at seeing it. I'm not reading every day.
Click to expand...
Click to collapse
----------------------------------------------------
So... i've tried to root my nook touch but I used the icorrect tool meant for the nook touch without a glowlight. Doing this, I seem to have lost the ability to use the glowlight feature, in fact it is now non-existent after many attempts at restoring everything to factory defaults. At least the device works again, but I really need the light back and I don't know what else to do. You're my last hope! I saw you mentioned something about installing a kernel after getting the correct OS back on there, and I would love to know how to do this. Thank you so much for your help in advance!
When you go to Settings, Device Info, About Your Nook, what software version is displayed?
Is it 1.1.5? I think that's the correct version for the US nook glow at this time. (and, are you in the US, and/or using a US model? the overseas models are different.)
One very quick thing you can try - after you back up your current, working but unhappy, device - is to download the OC kernel at this thread: http://forum.xda-developers.com/showthread.php?p=34292271#post34292271
The 166 version of that kernel works on both the US and UK glow devices from what I've read, but this process is best known for US devices.
You can either use Clockwork to install it or - if you're comfortable with linux commandline tools and your device, while unhappy, is rooted and you have ADB installed - you can use this very fast technique based on http://forum.xda-developers.com/showpost.php?p=24168019&postcount=21
Be sure to name the file uImage.
from a command prompt on your computer:
c:\adb connect <nook-ip-address>
c:\adb push uImage /media
c:\adb shell
$
$su
#mkdir /media/boot
#mount -t vfat /dev/block/mmcblk0p1 /media/boot
#cp /media/uImage /media/boot
#umount /media/boot
#rmdir /media/boot
#rm /media/uImage
If all you need is a kernel, that kernel supports the Glow functionality.
You may need to replace more of your boot environment, though. If you do, it becomes important to know if you're using a US or UK glow.
I have made and tested an image of just the first partition of my NSTG (us version, running the overclock kernel) and am able to reboot properly after putting it on my device.
I made it by :
# dd if=/dev/block/mmcblk0p1 of=/media/part1.img bs=1M
and as a test, then did a
# dd if=/media/part1.img of=/dev/block/mmcblk0p1 bs=1M
both via ADB on my rooted device.
If you are rooted, this may be something you could try IF you're using the US release. If not, you could ask one of the folks with the UK release if they'd be willing to image their boot partition for you.
As far as I can see, that first partition image might reenable the glowlight part of your NSTG, but I'm not 100%. Before you go there, it's important to know what release of the software your recovery image was able to set up for you.
Thanks
Renate NST said:
To boot into recovery (either factory or Clockwork Mod if you installed that):
Power down your Nook.
Power it up.
As soon as the screen changes at all, hold down the lower left and lower right hard keys.
Wait with sore thumbs for 30 seconds or so until the recovery screen show ups.
Click to expand...
Click to collapse
:highfive: Thank You So Much Renate NST it really works :good:
Related
Hi,
A couple days ago my rooted NST got into a bootloop all of a sudden (it's been rooted for several months and I have had no problem prior to that). I searched for all the "bricked" posts and followed the relevant advice, to no avail. Let me explained the problem, and outlined steps I have taken so far. Your help is desperately needed and greatly appreciated.
(1) The bootloop -- "read forever" showed up, following by the flashing dots, and then back to reboot -- was first triggered by using "quickboot" app to shut down the device (it's worked fine for months up until that point). I long pressed the power button to shut it down, rebooted, got in to a bootloop, repeated, ... I shutted it down for the night.
(2) The next day I looked up the "bricked" posts on xda and tried to follow the steps there. I don't remember if I had tried the 8 failed boot (first); I did try the n2T recovery http://forum.xda-developers.com/showthread.php?t=1289233 but that didn't work (NST just ignored the scard).
(3) Big mistake:
I made a backup following http://forum.xda-developers.com/showthread.php?t=1142983
when I first got my device so I tried to restore it. But I forgot that my backup was incomplete (252MB, not 1.82G). When I rebooted the NST, the laucher did showed up but then it hanged, complaining about missing files (not being able to find /su ?).
(4) I belatedly discovered the hard-reset method: power up, hold left-and-right button down. It brings me back to firmware 1.0.0, unrooted. I updated it to 1.1.0 and it now functions properly as an unrooted NST.
(5) Can't root
The first time I rooted the NST I used SalsichaNooter 0.3. I no longer have the img and the download site is down, so I tried touchnooter-2-1-31. After I inserted the sdcard and powered up, it quickly booted back to the regular NST. It did complain about "this memory card is unrecognized and needs to be formatted" (I clicked cancel). I tried several sdcards (all prepared on my desktop) and got the same message.
I also tried minimaltouch 1.1beta5 via CWM. When I powered up, and then pressed both lower buttons when "read forever" shows up, I got the factor reset screen and not the CWM screen -- this is the case with or without any additional zip.
-------------------------
Question: Did my incorrect restore (step 3) permanently messed up the NST? And can I root it again? It does power up as a regular NST, but I really need the extra functionality coming from roots.
MANY THANKS!
When you go to boot into CWM, you're not supposed to hold anything to boot from the mSD.
Googie2149 said:
When you go to boot into CWM, you're not supposed to hold anything to boot from the mSD.
Click to expand...
Click to collapse
Thanks for your reply. I did try to boot into CWM from the sdcard without holding any button, but that quickly brings me to the regular NST boot screen (with no complain about a badly formated sdcard -- see item #5 of my original post).
I put a couple of epub files into a blank sdcard and NST can read those. It also created two folders, my files & lost.dir, so that part of the read/write function is okay.
It seems that my partly bricked/recovered NST loses the ability to read CWM/touchnooter zip files, but the rest of the unrooted NST functions are okay. This is very strange and annoying...
What program are you using to write the image to the mSD?
Googie2149 said:
What program are you using to write the image to the mSD?
Click to expand...
Click to collapse
I used dd on my linux box (as I did when I rooted my nook color). Upon reading your message, I dug up my old xp box and made a new noogie.img and touchnooker using win32.
WA LA! It works!
This is so weird... but I'm glad I got my NST back...
THANKS!
did you used "sudo dd" ? You can write directly to the sdcard if you have root rights.
mali100 said:
did you used "sudo dd" ? You can write directly to the sdcard if you have root rights.
Click to expand...
Click to collapse
Yes, I did "sudo", otherwise I can't even run dd (mom said that it's not safe to log in as root
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.
drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App
The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.
Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk
If your on the rooted stock rom you could always wait until Amazon pushing the next OTA
You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.
Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.
There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!
After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.
Hello,
I get my nook simple touch rooted using the minimal touch nooter.
But it seems I have some problems. Superuser is install, but when I install an application that require root, it states that, it is not possible with my device (something like that).
I want to install it back perhaps i did soemthing wrong at the beginning when I was testing the function.
Could you please tell me how I can do, to I have to make some wipe ? go back to factory ? doing the whole process from the beginning ?
thanks in advance,
You could try rerooting with minimal touch nooter.
It sounds like you may have picked a wrong default for superuser when the dialog was first presented asking if you wanted to grant root access with the choices being allow, deny and a tickbox for remember.
I have a vague memory of accidentally hitting "deny" with "remember" ticked on a device the first time the dialog presented itself and ultimately deciding to reset to stock and re-root the device.
So, if reapplying the root doesn't work, yes, you should boot from noogie and restore your backup or failing that force a device reset using the 8 failed boots method. There is also a method for resetting that I've had mixed luck with on the NST that uses the lower left and lower right buttons held down at power on.
Eded's got tools for making the device wipe process much simpler, though, posted at
http://forum.xda-developers.com/showthread.php?t=1475613
The 'old' tool is a really good one to know about as long as your device is largely intact
http://nooter.googlecode.com/files/Alpha-FormatTouch.zip
It doesn't include a replacement OS but assumes that you have not formatted your partitins - as long as that's true (as it is in your case) the tool makes one change to your device and then uses the onboard recovery process.
That's great, because it means that tool supports both the NST and the glowworm.
roustabout said:
You could try rerooting with minimal touch nooter.
It sounds like you may have picked a wrong default for superuser when the dialog was first presented asking if you wanted to grant root access with the choices being allow, deny and a tickbox for remember.
I have a vague memory of accidentally hitting "deny" with "remember" ticked on a device the first time the dialog presented itself and ultimately deciding to reset to stock and re-root the device.
So, if reapplying the root doesn't work, yes, you should boot from noogie and restore your backup or failing that force a device reset using the 8 failed boots method. There is also a method for resetting that I've had mixed luck with on the NST that uses the lower left and lower right buttons held down at power on.
Eded's got tools for making the device wipe process much simpler, though, posted at
http://forum.xda-developers.com/showthread.php?t=1475613
The 'old' tool is a really good one to know about as long as your device is largely intact
http://nooter.googlecode.com/files/Alpha-FormatTouch.zip
It doesn't include a replacement OS but assumes that you have not formatted your partitins - as long as that's true (as it is in your case) the tool makes one change to your device and then uses the onboard recovery process.
That's great, because it means that tool supports both the NST and the glowworm.
Click to expand...
Click to collapse
thanks for your reply. I don't understand everything you wrote, i forgot to explain that I am a NOOB with capital letters....
So, I need to try first with minimal touch as describe , as it is the first time I do it (i use this to root my nook first). If it doesn't work, i go back to factory and root it again ? no wipe cache, data, to do ? when I put a new rom I my defy I have to wipe either data or at least cache depending of what I install, this is why I ask
you'll need to wipe /system and /data. The tools Eded provides do that for you.
On your NST is a hidden file that restores your system. Eded's tool leverages that file.
- boot from clockwork
- install his zip
- remove the clockwork disk
- hit reboot.
Once your device restores, stop trying to root it.
Read up on making a backup. There are a couple of threads about backing up your NST. One of the great things about the NST is that you can easily make a complete backup of it.
I prefer to use a disk called noogie to make my backups.
Verify that your noogie backup is 1.8 gig. Folks sometimes try to restore from partial backups and that's a big headache.
Now that you've got a backup, try rooting again -- if it fails, you can either use the reset tool or restore from your backup.
For the last two weeks, I've tried pretty much everything I can think of to get my TPT booted again. Symptoms of its current illness include:
Lots of error messages when booting into CWM recovery ("E:Can't mount /sdcard" for example)
If I attempt to boot normally, I get stuck on the Lenovo logo screen.
Randomly I'll boot into CWM recovery and get its logo on the screen, and a line of text, but no menus.
Other times I'll attempt to boot into CWM recovery, and just get a blank screen
So last night I used nvflash to put a new CWM recovery into partition 6: after which I was able to boot into CWM with no errors. (Yay) However, when I tried to reinstall CynogenMod (whose zip file was sitting on my external sd card), it hung during the installation. I rebooted anyway; this time it got as far as the CyanogenMod spinning logo and hung there. I went to bed, and seven hours later it was still spinning away.
Then I rebooted into CWM (without errors) and managed to install CM ROM this time also with no errors. However, again I can't boot. I get as far as the Lenovo logo, and if I boot into CWM recovery I have all the mount errors again.
Along the way I've erased the cache; done a factory reset, etc.
So: nvflash, new CWM recovery (but still errors), reinstalled CM ROM, but can't boot into it.
Any suggestions? Has this machine packed it in - is its hardware faulty in some way? Or is there something I could try which I haven't already?
Thanks folks - I think I've reached the limits of my fixing ability, and would be very gratefiul of some advice.
Thanks again,
Al
In CWM check to see if your /System folder is mounted with read-write privileges or only with read-only. If the former, then your bootloader may have locked itself. Also, what is your device model? If you have a have a US device then it cannot be unlocked as it has been encrypted by Lenovo...
Sent from my ThinkPad Tablet using Tapatalk
Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.
amca1960 said:
Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.
Click to expand...
Click to collapse
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...
eKeith said:
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...
Click to expand...
Click to collapse
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.
amca1960 said:
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.
Click to expand...
Click to collapse
No offense intended but you are somewhat peculiar as you are familiar with NVFlash, can determine which partitions to flash with the correct images but you don't have a record of, or can't find your device's model number? Check on your SD Card port flap (or your invoice). Then check out this page for details.
However if you decide to replace the motherboard then search eBay for "thinkpad tablet motherboard" and choose either of the 1838 or 1839 options. Any will fit and work but you probably won't get your (non-US) choice of replacement motherboard so will probably just have to get what's available.
See here for some basic dis-assembly instructions. Then just take you time and the rest will be obvious. Good luck!
Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?
amca1960 said:
Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?
Click to expand...
Click to collapse
No problem at all.
"I'm in the same boat": I replaced my motherboard with another US version about 6 weeks ago, rooted, installed CWM recovery and steady so far... "with fingers crossed"...
Let us know how it goes...
Hi,
First of all, sorry about my english. It's not my primary language.
I recently bought a used Nook Simple Touch on eBay. The previous owner had tried to root it, but failed somewhere along the way. I got it dirt cheap and figured I could fix it..
I've read "all" the unbricking guides here on the forum, but I'm yet to make it start. I can boot CWM, but for some reason noogie is not starting at all.
At first, the device said "Rooted forever" all the time, but after some messing around in CWM it's instead displaying "Your NOOK is starting up..." in five different languages, and stops there.
The thing is, I'm not even interested in the reading features (B&N apps, e-books, etc.), I just want to use the device to display a status webpage that I've made (weather updates, bus/subway/tram departures, etc. etc.), so as long as it can run Chrome or similar I would be perfectly happy! Is there a vanilla android ROM available so I don't need to care about the "device specific" data that I've been reading about (the one you're supposed to take a backup of)? Or can I just flash it with any NST firmware if I'm not interested in the reading functionality?
Thanks!
Have you tried Nook Manager? I've had really good luck with it and it includes a factory image reset. It may be a way to get back to something you can work with.
nmyshkin said:
Have you tried Nook Manager? I've had really good luck with it and it includes a factory image reset. It may be a way to get back to something you can work with.
Click to expand...
Click to collapse
I agree. I just received my nook from ebay a couple of days ago. I've tried a number of different root methods and google apps installers. Nook Manager + NTGApps was by far the simplest for me.
Also, have you tried the stock factory reset?? I'm new to this, so I'm not sure if it will work -- but I thought I bricked mine 3-4 times and the factory reset saved me every time.
0) Take out any SD cards (just making sure you don't have anything bootable on the card)
1) Press and hold the power button until it resets
2) As soon as it begins to reboot press and hold the bottom left and bottom right physical buttons until you see a prompt.
3) Wait for the prompt and press the "n" button once to confirm the factory reset
4) Press the "n" button again to begin the factory reset again.
After you factory reset, upgrade to 1.2.1 and then root using Nook Manager. Then, you'll have the browser available to you.
* Use Nook Manager to make a backup *
Thanks for the suggestions you guys! I finally got it to work!
Noogie finally booted up. I just left the nook, with the noogie sd card in, connected to my computer when I went to work. When I got home, it had started. Since then it started every reboot. No idea why it didn't work in the beginning?
Alright, this is how I did. This information is scattered around the forum already, but hopefully it can help someone in my position.
1) I realized that the partitions table was probably messed up, so after "aligning" it using fdisk and the table found here:
http://forum.xda-developers.com/showpost.php?p=29585690&postcount=6
I could restore my /rom partition. After I've made a backup of the /rom files...
2) ... I flashed this file using noogie:
http://forum.xda-developers.com/showpost.php?p=49389880&postcount=2
3) I mounted partition2 on my computer (still using noogie) and copied my /rom files back to it.
4) It started! So I applied the official 1.2.1 update from B&N. After update I realized that I actually have a glowlight! It was listed as a regular Simple Touch, so that was a pleasant surprise.
5) Rooted using NookManager. Worked flawlessy. Installed Opera Mobile 12.1 (which have websocket support that I needed). I now have an awesome status "frame".
Thank you for all you help, including the guys & girls posting in the threads linked in this post.