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
Related
Well... Seems like we've got ourselves a new bootloader, after flashing the BETA1 Gingerbread for U8800. Not cool...
I tried it and didn't like it.
Furthermore, I wanted to keep my device in that zen condition which allows me to return it to my carrier under warranty.
I've tried to revert to my carrier stock ROM, but to no avail. I can run froyo alright, but the carrier costumizations are simply ignored, courtesy of the new bits that came with Huawei's beta.
Some time ago, and antecipating something like this, I connected the mobile, while in pink screen mode, to a linux box and dd'ed the entire volume to a dump file. I can mount this dumpfile through /dev/loop and confirm it carries the same partition schema that is present in the mobile. I'm tempted to dd it back to the mobile, to restore it, but affraid of bricking it for good. If bootloader gets invalid then nothing short of a factory j-tag flash will solve it, for sure.
Has anyone done this before?
Thanks in advance.
EDIT: It worked. The whole volume was restored (bootloader included, naturally).
Greetings,
Everything else aside, claiming that the installation of a manufacturer released upgrade (yes, even one labeled Beta) automatically voids your device's warranty pretty wild. That's not to say that someone somewhere won't make that argument, but there are plenty of crazy people in the world.
That said, good luck.
bonowax said:
Well... Seems like we've got ourselves a new bootloader, after flashing the BETA1 Gingerbread for U8800. Not cool...
I tried it and didn't like it.
Furthermore, I wanted to keep my device in that zen condition which allows me to return it to my carrier under warranty.
I've tried to revert to my carrier stock ROM, but to no avail. I can run froyo alright, but the carrier costumizations are simply ignored, courtesy of the new bits that came with Huawei's beta.
Some time ago, and antecipating something like this, I connected the mobile, while in pink screen mode, to a linux box and dd'ed the entire volume to a dump file. I can mount this dumpfile through /dev/loop and confirm it carries the same partition schema that is present in the mobile. I'm tempted to dd it back to the mobile, to restore it, but affraid of bricking it for good. If bootloader gets invalid then nothing short of a factory j-tag flash will solve it, for sure.
Has anyone done this before?
Thanks in advance.
Click to expand...
Click to collapse
is the dump file around 4gb then yes it will work I did it my self through restoring raw sd image
Sent from my u8800 using xda premium
By the time I red your reply, my mobile was already back to Zen state. Thank you nevertheless.
On a side note: the battery was very low by the time I initiated the restore, but since it was connected through USB, I assumed it wouldn't be an issue.
It took around 45 minutes to restore the image and when finished, the battery was exhausted to the point that I couldn't turn the mobile on. Thought I had bricked it for good...
Charged overnight and everything was fine and dandy.
Cheers
mine took 25min
I managed to downgrade to 2.2:
Get some 2.2 update, mine was b136.
First tried to update from sd card, it failed. Then tried from the internal SD and it worked (Take off the external SD first). But the update was too fast and it only booted to original recovery (with some warnings). So i did the update again and now it toke the usual time. But it it still only booted to original recovery (with some warnings). Then i did a factory reset from the original recovery, and voila, it booted to 2.2!
Once the 2.2 was booted, i copied CWM recovery in the pink screen and it works now too. Then i was able to install Miui again.
straight restore did not work for some reason, maybe needs to format everything first?
sanpsa said:
i managed to downgrade to 2.2:
Get some 2.2 update, mine was b136.
First tried to update from sd card, it failed. Then tried from the internal sd and it worked (take off the external sd first). But the update was too fast and it only booted to original recovery (with some warnings). So i did the update again and now it toke the usual time. But it it still only booted to original recovery (with some warnings). Then i did a factory reset from the original recovery, and voila, it booted to 2.2!
Once the 2.2 was booted, i copied cwm recovery in the pink screen and it works now too. Then i was able to install miui again.
Straight restore did not work for some reason, maybe needs to format everything first?
Click to expand...
Click to collapse
man you are the king!!!!!!!!!!!!!
Thanks you
sanpsa said:
I managed to downgrade to 2.2:
Get some 2.2 update, mine was b136.
First tried to update from sd card, it failed. Then tried from the internal SD and it worked (Take off the external SD first). But the update was too fast and it only booted to original recovery (with some warnings). So i did the update again and now it toke the usual time. But it it still only booted to original recovery (with some warnings). Then i did a factory reset from the original recovery, and voila, it booted to 2.2!
Once the 2.2 was booted, i copied CWM recovery in the pink screen and it works now too. Then i was able to install Miui again.
straight restore did not work for some reason, maybe needs to format everything first?
Click to expand...
Click to collapse
Yes, I had it running FROYO back too, but the phone's condition wasn't the same as before.
If I understood it correctly, the 2.3.5BETA rewrites de boot partition - the 2nd primary parition on the device, marked bootable. This becomes obvious when the "IDEOS" logo is replaced by the "HUAWEI" one during device boot-up.
The partition scheme is the same as before, however, as I had the chance to confirm.
Flashing a 2.2.1 ROM from Huawei did not write the old bootloader back, furthermore this might not be the only change.
I was able to revert to an overseas 2.2.1, both through CWM restore and "dload" method, but carrier customizations were always absent.
Along with the regular system, my carrier's ROM adds a batch of apps, ringtone, wallpaper, binaries and libs, under "cust_data/tmn/pt". These were all ignored. Not that I cared much for them, but as I stated in the original post, I wanted it back in the original condition, as TMN will consider warranty void if the device has been tampered with.
Since I had a raw dump of the volume I restored it back and got my mobile as it was some 3 weeks ago... To my relief...
Can you please make a tutorial to make and restore raw backups?
1. Step : Download a official 2.2.2 rom
2. Step : Put the dload folder at the root of your sd-card
3. Step : Power your device of and boot into bootloader by pressing volume +, volume - and power (before you do that, you can do a titanium backup)
4. Step : Wait till the prozess is done. When your device doesn't reboot by itself, reboot it manually. (if there are any problems with the rom, wipe cache and date with the original recovery)
5. Step : Download a CWM recovery. Boot your device like the same way above into the bootloader. Rename the CWM recovery you've downloaded before into recovery.img
(6. Step : Rename the recovery of your device in the folder (device):/image into recovery.img.orig, to do a backup of the original recovery)
7. Step : Put the new recovery.img in the folder from above. Unplug your phone from the PC and put the battery out to turn it off. Boot it into recovery by pressing volume + and power.
Congratulation, you've restored your Ideos X5 to 2.2.2.
Now you can download a custom rom and install it by the normal way.
FabioAreia said:
Can you please make a tutorial to make and restore raw backups?
Click to expand...
Click to collapse
Good sugestion... Will start a new thread for it.
IDEOS X5 - Update dead drives bootloader - help me
4. Use the English language.
We understand that with all the different nationalities not everyone speaks English well, but please try. If you're really unable to post in English use an online translator, You're free to include your original message in your own language below the English translation.
Click to expand...
Click to collapse
MOD EDIT: Please read the forum rules.
how can we restore a raw dump?
dd if=[image filename] of=/dev/[block device allocated to the U8800] bs=512
Search the forums for the complete tutorial...
I was trying to root a clean NST (firmware 1.1.0) with just released TouchNooter 2.1.26, but ran into the same problem as reported on the dev thread. Since I am a new member and can't reply there, I am sharing my experience here.
In a nutshell, the new release does not seem to be able to start ADW.Launcher. I found a workaround by overlaying it on top of version 1.11.20 (all Nooter versions are available from the project download page here), but still had to wait about 10 hours to get Market working.
Here are my steps:
1. Restore to factory firmware (make sure it is 1.1.0) with n2T-Recovery tool
2. Clean user data with "Settings->Device Info->Erase & Deregister Device"
3. After reboot, register the device again (It doesn't seem to require the email address to the same as Google account -- I used a different email address)
4. Start initial rooting with touchnooter-1-11-20.img
5. Step through the Android welcome screen and choose "Skip" on sign-in page
6. Enable location service when prompted
7. Verify you can bring up App Drawer, then STOP (don't go to YouTube yet)
8. Now insert the SDCard with the new touchnooter-2-1-26.img and reboot
9. You should be prompted with option to bring up ADW.Launcher
10. Now continue with YouTube sign-in, GMail sync, and Market activation, etc. steps in as per the original TouchNooter 2.1.26 instructions (I used a Google account email (not gmail) and it worked for me)
11. Wait up to 24 hours to get Market to work
I hope this helps, and would appreciate someone posting this information to the original TouchNooter 2.1.26 thread.
Rooted Forever.
I had issues with touchnooter and now I'm getting boot loops. For some reason those recovery img's are dead. Do you know of any other links to them?
Edit: Never mind I think I know what I did wrong, didn't up date to 1.1 before root. Also I just did the 8 boot loops to get it back to stock. Fixed and thanks.
yo i had problems with my gmail not syncing after signing into youtube. So i rebooted. youtube crashes to home whenever i tried to open it. So i was trying to sync my gmail with the account i entered into youtube, but of no avail. So instead, i created a new account and then my nook said it synced the account i just created, after that i tried to click on the original account, and bingo it synced too...i am just waiting for the market to load up
After boot touchnooter 2.1.26, how much time one have to "wait for the screen flash black"?
z117 said:
After boot touchnooter 2.1.26, how much time one have to "wait for the screen flash black"?
Click to expand...
Click to collapse
After 15-20 seconds, the screen turns black.
I have waited for 15 minutes, and nothing happens, and restarted the device.
I am one of the TouchNooter 2.1.26 victims too
I have gone thru the steps twice, but not with success.
So I restored my device, and now waiting for an update.
Or should I try another root method, I don't know
me neither. i waited for 10~15 mins.Screen didnt flash. So i removed card and rebooted. my Nook just showed the stock apps (stock home screen)along with the button saviour app(which didnt work) and it never showed me the rooted home screen. ended up rooting with Tomirunooter.Flawless victory
posted in the thread, confirmed this as working for me. thanks for finding a fix!!
I tried to root twice using TouchNooter 2.1.26, first time it booted but without being rooted, used n2T-Recovery, downloaded TN 2.1.26 again e tried again, now my NST is on boot loop. Where i can find touchnooter-1-11-20.img?
http://nookdevs.com/Nook_Simple_Touch/Rooting
if you scroll down you can find the TouchNooter 1.11.20 file
Nooter images download page
brunobbarcelos said:
I tried to root twice using TouchNooter 2.1.26, first time it booted but without being rooted, used n2T-Recovery, downloaded TN 2.1.26 again e tried again, now my NST is on boot loop. Where i can find touchnooter-1-11-20.img?
Click to expand...
Click to collapse
You can find all TouchRooter versions in the Nooter project's download page, see the highlighted link in my original post above.
Nevermind, found the issue, will be updating with a new version soon that fixes it.
Updated with new version that fixes Launcher not properly installing can be found here: http://forum.xda-developers.com/showthread.php?t=1343143
Duplicated apps
Hello, since I can't post on the Dev channel, I'll use this thread. Sorry, OP
Why Gabrial / Torimu (the two nooters I've tried with success) chose to rename the included apps -names+version numbers-, instead of using the unique, official name -installed app-? I think that can cause problems of duplication.
Both latest versions bring apps that some of us have from a previous root. For example, they use "NookTouchTools_v1.0-beta2.apk" instead of "io.xor.nooktouchtools.apk". Or "Opera_Mini_v6.5.2.apk" instead of "com.opera.mini.android.apk".
The result is they write some applications already present at data/app (and perhaps with different versions). I do not know exactly if this will create problems with the Android system, but can be solved very easily on nooter's part...
TIA,
jugaor
PS: btw, sorry for my bad English…
jugaor said:
Hello, since I can't post on the Dev channel, I'll use this thread. Sorry, OP
Why Gabrial / Torimu (the two nooters I've tried with success) chose to rename the included apps -names+version numbers-, instead of using the unique, official name -installed app-? I think that can cause problems of duplication.
Both latest versions bring apps that some of us have from a previous root. For example, they use "NookTouchTools_v1.0-beta2.apk" instead of "io.xor.nooktouchtools.apk". Or "Opera_Mini_v6.5.2.apk" instead of "com.opera.mini.android.apk".
The result is they write some applications already present at data/app (and perhaps with different versions). I do not know exactly if this will create problems with the Android system, but can be solved very easily on nooter's part...
TIA,
jugaor
PS: btw, sorry for my bad English…
Click to expand...
Click to collapse
I renamed the ones in TouchNooter so that users could easily identify what I was providing with TouchNooter to users, I don't think it'll cause problems as I've noticed a few times before where I'll look into my data and see com.appname.something-1.apk along with com.appname.something.apk which seems to be caused by something other than TouchNooter because I've noticed it with apps that I installed just through market. The only thing you "may" have to worry about is that the extra apps may consume more space from /data
The fix however is simple an app that's in /nooter/data/app that you know you already have for whatever reason you could simply remove (If you've previously rooted that's quite a few of them) or you could uninstall them and let Nooter install them.
Hiya, I'm another one who can't post on the dev thread.. and since this thread was already here and I had the same problem..
I rooted my new 1.1 NST last night using the current touchnooter. The device went through the steps, screen turned black, I pulled SD card and rebooted.
I did wait just in case..but all the nook did was refresh the screen with the dots on it for twenty minutes. I could not break the boot loop.
I ended up using the NST restore zip on a CWM disk (that I tucked in the slot and sort of held the power button down and prayed at). It worked and I was left with a half-rooted nook. (I had the launcher, Amazon app market and a few other random things... they really didn't work, told me a I needed a rooted device.) I was able to install and use opera funny enough.
I deregestered, reregestered.. and rechecked the specs (just in case!)...and tried again. Same result.
So I deregestered, reregestered... and now I will try the MinimalTouch 1.1beta5. I'm not sure why touchnooter did not work. It should have.
I am stuck at a blue screen, and I was told here that I need some linux backup that someone might have made so I can restore it to my phone and everything would be ok and back to normal again!
I really need as soon as possible because my phone is bricked and I need it!
The last thing I flashed to my mobile, was the official 2.3.5! for x5
Ok, here's what you should do:
Download this.
Connect phone to USB.
Copy the zip contents onto the phone (partition with size about 252mb).
Remember to keep the folder structure partition/image/boot.img etc.
Restart - if system is not corrupted, it should boot.
Blefish said:
Ok, here's what you should do:
Download this.
Connect phone to USB.
Copy the zip contents onto the phone (partition with size about 252mb).
Remember to keep the folder structure partition/image/boot.img etc.
Restart - if system is not corrupted, it should boot.
Click to expand...
Click to collapse
There is a problem, when I connect to USB and press Volume Up + Volume Down buttons to get to the purple screen it aint reading my phone as a device or sth I can put files into it!
Something with the drivers!
That was occurred even before that blue screen happened, when I installed the 2.3.5 official and the the drivers with SuperOneClick!
Ok, do you have a external SD card? If you do, check this.
After applying that, try to do the steps I posted earlier.
thanks I will this night, because I got lessons to attend at the moment!
Thanks a lot, you offered a great relieve!
I did it! I am back at official 2.3.5!
But I cant root :/ SuperOneClick Crashes when i press ROOT! Drivers and everything are installed!
It just wont root!
And I also tryed to first install SuperUser first!
See this thread for other rooting methods. I've used Doomlords method and it worked great
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:
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.