Related
I have perm root with S OFF but have come in to quite a problem. I am having problems with the screen flickering on and off and need to exchange the device. The problem is, the nandroid backup that I made is inaccessible, and I have removed most of the stock apps off the phone.
The SD card I created the backup on seems to be corrupt, I cant even get it to mount anymore on my PC. Is there anyone that created a full nandroid back that can point me to the file (be willing to share)?
I have searched everywhere and can't seem to locate one.
Thanks for the help!
why don't you just use the "Downgrade ROM and Radio from OTA to Stock" thread?
Edit: Oh, and this is the wrong place for your thread also. Prob should go in general or Q&A.
The downgrade rom won't work w/ S-Off I don't believe. I would also a appriciate a nand backup, just the system.img if anyone has one to share.
SilverSurfR said:
why don't you just use the "Downgrade ROM and Radio from OTA to Stock" thread?
Edit: Oh, and this is the wrong place for your thread also. Prob should go in general or Q&A.
Click to expand...
Click to collapse
Also, the OTA update will not be received again if you do the downgrade.
revocation said:
I have perm root with S OFF but have come in to quite a problem. I am having problems with the screen flickering on and off and need to exchange the device. The problem is, the nandroid backup that I made is inaccessible, and I have removed most of the stock apps off the phone.
The SD card I created the backup on seems to be corrupt, I cant even get it to mount anymore on my PC. Is there anyone that created a full nandroid back that can point me to the file (be willing to share)?
I have searched everywhere and can't seem to locate one.
Thanks for the help!
Click to expand...
Click to collapse
cl2eep said:
The downgrade rom won't work w/ S-Off I don't believe. I would also a appriciate a nand backup, just the system.img if anyone has one to share.
Click to expand...
Click to collapse
Are you asking for a NAND backup of the 2.2.1 stock rom?
If so, I'll see if I can't make one for you tonight when I get home. My work's internet connection is pretty crappy and it would take forever and a day to upload.
cl2eep said:
The downgrade rom won't work w/ S-Off I don't believe. I would also a appriciate a nand backup, just the system.img if anyone has one to share.
Click to expand...
Click to collapse
I think it should work. if it does it should restore your hboot to orignal as well.
unremarked said:
Are you asking for a NAND backup of the 2.2.1 stock rom?
If so, I'll see if I can't make one for you tonight when I get home. My work's internet connection is pretty crappy and it would take forever and a day to upload.
Click to expand...
Click to collapse
Thank you in advance!
Please post questions in Q&A section. Thanks
revocation said:
I have perm root with S OFF but have come in to quite a problem. I am having problems with the screen flickering on and off and need to exchange the device. The problem is, the nandroid backup that I made is inaccessible, and I have removed most of the stock apps off the phone.
The SD card I created the backup on seems to be corrupt, I cant even get it to mount anymore on my PC. Is there anyone that created a full nandroid back that can point me to the file (be willing to share)?
I have searched everywhere and can't seem to locate one.
Thanks for the help!
Click to expand...
Click to collapse
Take a look at this thread. It has the link to the official RUU and the install instructions.
This should get you back to stock, although I have not tried it yet. I grabbed it just in case I would need it.
g351427 said:
Take a look at this thread. It has the link to the official RUU and the install instructions.
This should get you back to stock, although I have not tried it yet. I grabbed it just in case I would need it.
Click to expand...
Click to collapse
And as mentioned in that thread, nobody who has followed that process has received the OTA update after having reverted back to stock.
unremarked said:
Are you asking for a NAND backup of the 2.2.1 stock rom?
If so, I'll see if I can't make one for you tonight when I get home. My work's internet connection is pretty crappy and it would take forever and a day to upload.
Click to expand...
Click to collapse
unremarked - If you could upload the NAND backup that would be great. Thanks in advance!
As you should know if he's returning his phone he doesn't need to receive the OTA anymore. Just follow that thread. I had a rooted white one restored and took it back to get a black one. That's much easier then trying to use someone else's backup.
JWhipple said:
And as mentioned in that thread, nobody who has followed that process has received the OTA update after having reverted back to stock.
Click to expand...
Click to collapse
He said he was returning the phone, so receiving the OTA is not really necessary.
Those instructions explain how to get it back to stock, as requested.
OEM stock is 2.2. Post first OTA update is 2.2.1
I would not mind getting a hold of that, as it would make it easier to possible get the 2nd OTA (about which I have read nothing about what it does).
Also wondering if anyone has lost root and rerooted after the 2nd update.
So I am absolutely fail.
On my first device, I guess I had just froze the bloatware apps rather than deleted them because they were restored after a factory reset before I returned it to the store.
On this one, I actually deleted the bloatware apps and they are permanently gone, factory reset doesn't bring them back, and I didn't do a Titanium backup until after I had deleted them off. ><
unremarked said:
So I am absolutely fail.
On my first device, I guess I had just froze the bloatware apps rather than deleted them because they were restored after a factory reset before I returned it to the store.
On this one, I actually deleted the bloatware apps and they are permanently gone, factory reset doesn't bring them back, and I didn't do a Titanium backup until after I had deleted them off. ><
Click to expand...
Click to collapse
I did the same thing. I hope someone will post the factory rom with all the .apk files that I could install. The only one i've found is the rom without the OTA.
I actually need a 2.2.1 nandroid as well. Could someone please post one?
Here you go guys. Where I failed, another succeeded!
http://forum.xda-developers.com/showpost.php?p=9305012&postcount=3
I simply can't figure this out. I have an A500 that I have rooted successfully back a few months ago and installed HoneyVillain 1.04 ROM. It has worked flawlessly for months. Now I can't get root access with Titanium BU, BusyBox, Root Explorer or anything! I've tried re-rooting it using GingerBreak 1.2 with no success. I can access a backup that I made right after I rooted a few months ago, but that doesn't bring back root either. Can someone please tell me what to do before I make a 10.1" frisbee out of this thing. The tab's batery has been allowed to go completely dead once, but I don't think that would be the problem. I'd like to install the latest version of HoneyVillain if I can get root back. I sincerely appreciate anyone's help.
Sounds weird. You hadn't flashed anything else had you or installed a system update?
What's your kernel version & build number?
Have you tried using IconiaRoot?
Bubbamanlarry said:
I simply can't figure this out. I have an A500 that I have rooted successfully back a few months ago and installed HoneyVillain 1.04 ROM. It has worked flawlessly for months. Now I can't get root access with Titanium BU, BusyBox, Root Explorer or anything! I've tried re-rooting it using GingerBreak 1.2 with no success. I can access a backup that I made right after I rooted a few months ago, but that doesn't bring back root either. Can someone please tell me what to do before I make a 10.1" frisbee out of this thing. The tab's batery has been allowed to go completely dead once, but I don't think that would be the problem. I'd like to install the latest version of HoneyVillain if I can get root back. I sincerely appreciate anyone's help.
Click to expand...
Click to collapse
Did you by chance do a restore using cwm..? Every time I did a full restore I would loose root.
I haven't flashed anything and no system update. I'm about to try IconiaRoot 1.3. Still looking for the answer...I'll report back. Thanks!
I tried Iconia Root. It goes through the steps and says Done...Have Fun! Then a message says Iconia Root has been denied root privileges. I tried to unroot and it says something went wrong and I'm still rooted. I must be somewhere between rooted and unrooted! What now????
evangineer said:
What's your kernel version & build number?
Have you tried using IconiaRoot?
Click to expand...
Click to collapse
Kernel version is 2.6.36.4HoneyVillain-1.0+
Build number is HoneyVillain 1.04
Bubbamanlarry said:
I tried Iconia Root. It goes through the steps and says Done...Have Fun! Then a message says Iconia Root has been denied root privileges. I tried to unroot and it says something went wrong and I'm still rooted. I must be somewhere between rooted and unrooted! What now????
Click to expand...
Click to collapse
Don't use backup, reflash your rom and re root.
shaun298 said:
Don't use backup, reflash your rom and re root.
Click to expand...
Click to collapse
I'm giving that a go right now...
Bubbamanlarry said:
I'm giving that a go right now...
Click to expand...
Click to collapse
When that works I will give you the full story of what I found, if it works.
shaun298 said:
When that works I will give you the full story of what I found, if it works.
Click to expand...
Click to collapse
Well, you're right - it did work. I didn't even have to root again. Everything is back after the reflash of the ROM. Now tell me the full story. I'm wanting (I think) to try the latest HoneyVillain ROM.
By the way, thank you VERY much for you help.
Bubbamanlarry said:
Well, you're right - it did work. I didn't even have to root again. Everything is back after the reflash of the ROM. Now tell me the full story. I'm wanting (I think) to try the latest HoneyVillain ROM.
By the way, thank you VERY much for you help.
Click to expand...
Click to collapse
You must not have wiped anything...? (Not that that is bad just more tech info for me), still learning.
Anyway, I have used honey vill and taboonay many version and with different kernals and love both roms.
What happans to me is I use cwm after I get the tab set the way I want and then do a full backup using cwm. Then I always want to fire test my backups so I immediately do a full restore using cwm, soon after I start getting denials from super user..? And after checking using a app from the market to check root, I have now lost root and can't get back, same as you.
I now just reflash the rom and if I do full wipe I reroot and all is well.
So I went with a different rom, backup and immediately do full restore and now no root again.
It happaned with every rom I have tried. Someone told me to delete the android.secure.image folder from the backup set that cwm makes. I tried that and that did let the restore, restore the flex rom folder but had the same problem. I have two a500 and both do this. I don' t know if stock rooted will do this as I have not tried yet. So what good is a full backup if it fudges your system. Maybe someone has a answer, but I have not found one. Sorry if this ain't your problem at all, but might be related. Later
shaun298 said:
You must not have wiped anything...? (Not that that is bad just more tech info for me), still learning.
Anyway, I have used honey vill and taboonay many version and with different kernals and love both roms.
What happans to me is I use cwm after I get the tab set the way I want and then do a full backup using cwm. Then I always want to fire test my backups so I immediately do a full restore using cwm, soon after I start getting denials from super user..? And after checking using a app from the market to check root, I have now lost root and can't get back, same as you.
I now just reflash the rom and if I do full wipe I reroot and all is well.
So I went with a different rom, backup and immediately do full restore and now no root again.
It happaned with every rom I have tried. Someone told me to delete the android.secure.image folder from the backup set that cwm makes. I tried that and that did let the restore, restore the flex rom folder but had the same problem. I have two a500 and both do this. I don' t know if stock rooted will do this as I have not tried yet. So what good is a full backup if it fudges your system. Maybe someone has a answer, but I have not found one. Sorry if this ain't your problem at all, but might be related. Later
Click to expand...
Click to collapse
That's amazing. I want to move up to the new HoneyVillain, so I guess I can count on rooting again? Wow. I love my Iconia though. I just remembered that I recently had trouble with WIFI so I DID do a restore via CWM. I guess I just realized that things weren't rooted! Oh well, you have provided some much needed info for me. At least now, I will know what to expect. Thanks again. Have a blessed evening.
I also had the wifi problem, and that is what started the whole thing with the full restore. Have a good one.
The same thing happened to me. I just installed another ROM to fix it.
Kinda ridiculous though. At least we know how to deal with it.
Thanks for this thread -- confirmed my sanity when I lost root after a CWM restore. Does anyone know if the updated version (1.6) of CWM for the A500 fixed this problem?
Hello:
I had a 1.0.0 NST successfully rooted TouchNooter 1.6.24.
Following instructions from this forum, I updated it to 1.0.1:
Using the NST power button, I did a Factory Restore
Then, I applied TouchNooter 1.6.24 using this thread instructions.
Even though it booted properly rooted, and on 1.0.1 B&N NST software, I didn't pass trough the step:
"13. Enable Location Services when given the option."
Also, I even though I am able to connect to Wi-Fi, when I tried to activate:
"14.[...] launch Youtube from Go Launcher's App Drawer"
the YouTube app didn't respond.
However, I am able to open Gmail and sync it properly... but when I open the Market I can't seem to connect to my apps, nor to install new ones.
So here goes the questions ;-)
1) Is there a way to repair this?
2) If not or if is too much of a hassle to do so, how can I unroot my NST back to factory (1.0.0) state? With a Factory / hard reset like this or otherwise?
I don't mind loosing data, since almost all of my books are on a SD Card.
3) After unrooting, registering the 1.0.0 device in B&N and updating it to 1.0.1, will I be able to apply TouchNooter 1.6.24 succesfully again?
Awaiting your kind replies,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
For the record, the instructions above on factory reset are incorrect. The 6-8 power cycles method does not format /system (only /data, I think) or return you to the original firmware. This method, however, does. (Note that once you upgrade to 1.1.0, it seems like the backup partition is upgraded to it as well, so unfortunately you'll be stuck with it unless you were prescient enough to make a backup of your Nook's internal drives .)
1. Turn off your N2E completely.
2. Turn it on again by holding down power, and then,
3. as soon as the screen flashes, begin holding down the bottom page turn keys on the left and right of the device until the screen flashes with a message asking if you want to do a factory reset.
4. Click the home key twice, and you should be on your way.
Note that this absolutely destroys your shelves, notes, and other information, and you will be asked to register your Nook with BN again.
Hope this is helpful for people; it took a while for me to come across.
LastSilmaril said:
Hope this is helpful for people; it took a while for me to come across.
Click to expand...
Click to collapse
It is certainly helpful for me! Thank you very much!
I if I understood you properly, this method end with the NST unrooted, yes?
BTW, how do you backup the NST internal drives: simply plugging the Nook to an USB port on a PC and copying the NST internal drive thus exposed or otherwise?
Finally, how does one backups the Shelves information: names, books included in each one and so forth: copying the internal NST drive or otherwise?
Already very gratefully yours,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
sarmasm said:
It is certainly helpful for me! Thank you very much!
I if I understood you properly, this method end with the NST unrooted, yes?
BTW, how do you backup the NST internal drives: simply plugging the Nook to an USB port on a PC and copying the NST internal drive thus exposed or otherwise?
Finally, how does one backups the Shelves information: names, books included in each one and so forth: copying the internal NST drive or otherwise?
Already very gratefully yours,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
Click to expand...
Click to collapse
I already sent you a PM with the link to backup/restore, but I guess it's worth reposting it here.
http://forum.xda-developers.com/showthread.php?t=1142983
From what I understand, yes, the nook should be factory-fresh afterward.
I do not know of a way to backup shelves separate than the general backup method, which of course, if you are making a backup of a rooted system, will not give you an unrooted system on reboot.
LastSilmaril said:
For the record, the instructions above on factory reset are incorrect. The 6-8 power cycles method does not format /system (only /data, I think) or return you to the original firmware.
Click to expand...
Click to collapse
I'm sorry mate but that is incorrect:
1: 8 interrupted boot attempts (Factory Restore)
- Will extract the factory image onto /system and put you back to 1.0.0
- Will not give you a factory fresh NST
- Will not touch your existing data
2: Booting while pressing left and right bottom buttons (Factory Reset)
- Will wipe all your your /data and settings.
- Will not give your a factory fresh NST
- Will not touch your system
LastSilmaril said:
(Note that once you upgrade to 1.1.0, it seems like the backup partition is upgraded to it as well, so unfortunately you'll be stuck with
Click to expand...
Click to collapse
Triggering System Restore on 1.1 will still put you back to 1.0.0
Open up a adb shell and try for yourself:
Code:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting?
Ros:
Will any of the above methods unroot my NST?
If not, how may I unroot it: with nookRestore, otherwise, or not at all?
Awaiting your kind reply,
Sebastián Armas
Avid reader, Spanish Interactive Fiction Author
ros87 said:
I'm sorry mate but that is incorrect:
1: 8 interrupted boot attempts (Factory Restore)
- Will extract the factory image onto /system and put you back to 1.0.0
- Will not give you a factory fresh NST
- Will not touch your existing data
2: Booting while pressing left and right bottom buttons (Factory Reset)
- Will wipe all your your /data and settings.
- Will not give your a factory fresh NST
- Will not touch your system
Triggering System Restore on 1.1 will still put you back to 1.0.0
Open up a adb shell and try for yourself:
Code:
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Click to expand...
Click to collapse
Aha, I must have misunderstood, because I tried using nookRestore, which I though was the same as doing the 8 uninterrupted boots, my nook still looked like it was semi-rooted: I could still access the normal Android launcher and programs. What's more, after I did the L+R reset, I could *not* access the Android launcher, AND the version number had gone from 1.0.1. So I guess something is very screwed up here? This explains why when I did the L+R reset to 1.1 why I still didn't have WiFi though (I didn't know it was still 1.1; just shut it off and restored my 1.0.0 image, which I now understand to be compromise).
Now that I'm on 1.0.0, is there any advantage to using nookRestore again (ADB doesn't work, either by WiFi or USB) to try to get things to work? Or is there no solution to unrooting, whatsoever, unless/until you or someone else releases some sort of customized installer?
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
And I am sorry for misinforming you, sarmasm
-e
---------- Post added at 09:49 AM ---------- Previous post was at 09:39 AM ----------
LastSilmaril said:
What's more, after I did the L+R reset, I could *not* access the Android launcher, AND the version number had gone from 1.0.1. So I guess something is very screwed up here?
Click to expand...
Click to collapse
No, I see what happened. I ran nookRestore, and this got me back to 1.0.0 (I didn't check the version number afterward, so I didn't know it changed) but didn't get rid of the Android launcher and such. THEN I did the L+R reset, and it *appeared* to be unrooted because the uRamdisk was replaced (...right? from your pm), but any modifications elsewhere would still remain.
So again, is there no hope? Running nookRestore again won't do anything, right? I do not know which files touchNooter modified outside of /data and /system (which at this point have both been wiped, since I have already ran nookRestore and L+R Reset)...
Ah, this is frustrating...
LastSilmaril said:
Aha, I must have misunderstood, because I tried using nookRestore, which I though was the same as doing the 8 uninterrupted boots
Click to expand...
Click to collapse
It is the same thing, nookRestore just tricks your NST into thinking it has had 8 failed boots.
LastSilmaril said:
my nook still looked like it was semi-rooted: I could still access the normal Android launcher and programs.
Click to expand...
Click to collapse
Yes, because the launcher resides in /data/app which is not touched by Factory Restore.
The Google apps however, resides in /system/app and should normally be removed by a Factory Restore.
LastSilmaril said:
What's more, after I did the L+R reset, I could *not* access the Android launcher
Click to expand...
Click to collapse
Yes because /data/app is wiped by Factory Reset (L+R)
LastSilmaril said:
Now that I'm on 1.0.0, is there any advantage to using nookRestore again
Click to expand...
Click to collapse
Unless you have something that's not working properly, then no.
[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting?
LastSilmaril said:
And I am sorry for misinforming you, sarmasm
Click to expand...
Click to collapse
No harm done: I'm sitting on my hands, on NST rooting, resetting and/or updating until I get more clear input on the matter.
Thanks for your prompt reply!
[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting?
ros87 said:
It is the same thing, nookRestore just tricks your NST into thinking it has had 8 failed boots.
[...]the launcher resides in /data/app which is not touched by Factory Restore.
The Google apps however, resides in /system/app and should normally be removed by a Factory Restore.
Click to expand...
Click to collapse
So, just to be clear and avoid any confusion whatsoever: using nookRestore (or a Factory restore i.e. 8 interrupted boot attempts) will remove the touchnooter 1.6.24 from my 1.0.1 rooted NST and result in a (as close as possible, user data issues appart) 1.0.0 stock NST, yes?
Awaiting your kind reply,
sarmasm said:
No harm done: I'm sitting on my hands, on NST rooting, resetting and/or updating until I get more clear input on the matter.
Thanks for your prompt reply!
Click to expand...
Click to collapse
Not sure why market isn't working for you but you can always try to do a Restore, Reset, Register, Update to 1.0.1 and then TouchNooter it again, it won't do any harm.
Using nookRestore is probably the simplest way to trigger Restore.
Just don't try to update to 1.1.0 if you want to use TouchNooter as it's currently not compatible with it.
[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24: UnRooting
ros87 said:
Not sure why market isn't working for you but you can always try to do a Restore, Reset, Register, Update to 1.0.1 and then TouchNooter it again, it won't do any harm.
Using nookRestore is probably the simplest way to trigger Restore.
Click to expand...
Click to collapse
Thanks!
BTW, why the Reset after the Restore?
ros87 said:
Just don't try to update to 1.1.0 if you want to use TouchNooter as it's currently not compatible with it.
Click to expand...
Click to collapse
I hear you: I've been following some threads on the matter and it does seems an unstable issue, for the time being.
Very gratefully yours,
ros87 said:
It is the same thing, nookRestore just tricks your NST into thinking it has had 8 failed boots.
Yes, because the launcher resides in /data/app which is not touched by Factory Restore.
The Google apps however, resides in /system/app and should normally be removed by a Factory Restore.
Yes because /data/app is wiped by Factory Reset (L+R)
Unless you have something that's not working properly, then no.
Click to expand...
Click to collapse
I *do* have something that's not working properly When I upgrade to 1.1.0 from 1.0.0 from this, WiFi does not work. I suspect this is due to the rooting.
LastSilmaril said:
I *do* have something that's not working properly When I upgrade to 1.1.0 from 1.0.0 from this, WiFi does not work. I suspect this is due to the rooting.
Click to expand...
Click to collapse
Do a restore + reset + register + upgrade to 1.1
If that still doesn't help, install one of my rooted ramdisks for 1.1 with the Noogie method and do a adb logcat to see what's going on.
ros87 said:
Do a restore + reset + register + upgrade to 1.1
If that still doesn't help, install one of my rooted ramdisks for 1.1 with the Noogie method and do a adb logcat to see what's going on.
Click to expand...
Click to collapse
I did all that and it still doesn't work, but it seems like this is a problem with my router, because it works with a different one. Will doing the 1.1 root and running 'logcat' catch it? Thanks a lot, ros.
---------- Post added at 07:01 PM ---------- Previous post was at 06:35 PM ----------
LastSilmaril said:
I did all that and it still doesn't work, but it seems like this is a problem with my router, because it works with a different one. Will doing the 1.1 root and running 'logcat' catch it? Thanks a lot, ros.
Click to expand...
Click to collapse
LOL, so I did did the noogie ramDisk root, and now, WiFi works without any issues. What part of enabling ADB over WiFi would cause that to happen?
LastSilmaril said:
LOL, so I did did the noogie ramDisk root, and now, WiFi works without any issues. What part of enabling ADB over WiFi would cause that to happen?
Click to expand...
Click to collapse
Hard to say, but I have had similar issues earlier where my NST suddenly would not obtain an IP from a known router, but still work on other routers.
Didn't care to look into it back then and the problem went away on itself.
LastSilmaril said:
LOL, so I did did the noogie ramDisk root, and now, WiFi works without any issues. What part of enabling ADB over WiFi would cause that to happen?
Click to expand...
Click to collapse
Before I give this a try, I wanted to check: do you have ADB working over WiFi after applying the noogie ramDisk root to the 1.1.0 firmware?
Thanks!
[Q] Nook Simple Touch Updated 1.0.1 Rooted with touchnooter 1.6.24 Problem Solved!
Hello:
I've been waiting to see how the TouchNooter situation was resolved for the NST 1.1 update so I hadn't reseted my NST 1.0.1 just yet.
The thing his, yesterday I activated the wi-fi access at home, and just for the heck of it I used the GApp Android Market...
...and it worked just fine: I was able to download and update stuff (Go Launcher, Opera Mini) just as I expected (and wasn't able to) right after the 1.0.1 update and TouchNooter 1.6.24 re installation.
What happened in between? Other that booting normally a few times, which I always had been able to since the 1.0.1 update and TouchNooter 1.6.24 re installation, I sincerely don't know
Go figure... but thank you all for your kind advice and patience.
I'll be now watching closely the 1.1 update + TouchNooter 1.11.11 installation and see if and when will it be GApps (Market) compatible, specially so for those of us which are not very good or at least not dangerous at slicing root folders and files manually
Very gratefully yours,
rooting problem
I rooted my nook simple touch 1.0.1 with touch nooter 2-1-31. After I wrote the touchnooter to my microsd card, I put it in. There were a set of instructions. That told me to wiat until screen flashed, and to then remove the sd card and reboot. I did all that and now it is stuck on the third circle when it is trying to boot up and it flashes and goes from 1 to 2 to3 then flashes and does the process again, can somebody help me? It doesn't work anymore
Nookguy32 said:
I rooted my nook simple touch 1.0.1 with touch nooter 2-1-31. After I wrote the touchnooter to my microsd card, I put it in. There were a set of instructions. That told me to wiat until screen flashed, and to then remove the sd card and reboot. I did all that and now it is stuck on the third circle when it is trying to boot up and it flashes and goes from 1 to 2 to3 then flashes and does the process again, can somebody help me? It doesn't work anymore
Click to expand...
Click to collapse
http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
Don't use TouchNooter with FW older than 1.1.x
You can get the 1.1 update from here
https://code.google.com/p/nst-recovery/downloads/list
(use CWM to upload it to your NST)
Read first, act later etc..
Hello:
I've rooted my N2E with TouchNooter 2.1.31
I've tried to unroot using both versions of nookRestore image (0.1 and 0.2).
Even though I do passs through the Factory restore screen and my nook does go back to 1.0.0 version , after booting I'm still rooted on TouchNooter 2.1.31
Can anybody please help me on how to unroot the device?
Thanks in advance,
sarmasm said:
Even though I do passs through the Factory restore screen and my nook does go back to 1.0.0 version , after booting I'm still rooted on TouchNooter 2.1.31
Click to expand...
Click to collapse
You have removed the microSD card before rebooting, yes?
MildBill
MildBill said:
You have removed the microSD card before rebooting, yes?
MildBill
Click to expand...
Click to collapse
Indeed, Bill: every time. Same result. BTW, the internal memory library remains intact, I'm still registered as the device owner with my B&N account... and it boots still rooted.
Other that leaving the system on 1.0.0 version, no change.
I'm going to root with NookManager, but first I need to have the device in factory stock condition... so I'm rather stuck.
Any suggestions?
Thanks in advance,
sarmasm said:
I'm going to root with NookManager, but first I need to have the device in factory stock condition.
Click to expand...
Click to collapse
Huh, why?
The only reason that you might ever want to restore to factory stock is if you had a hardware problem, wanted in-warranty repair and were concerned that B&N might not honor that if you had Angry Birds showing on the screen.
If your system is screwed up, you might want to install the update for 1.2.1
Renate NST said:
Huh, why?
The only reason that you might ever want to restore to factory stock is if you had a hardware problem, wanted in-warranty repair and were concerned that B&N might not honor that if you had Angry Birds showing on the screen.
If your system is screwed up, you might want to install the update for 1.2.1
Click to expand...
Click to collapse
Thanks for your prompt reply, Renate.
[EDITED] I moved my "over rooting" question here.
To answer your question, yes I'd very much like to upgrade my N2E to 1.2.1, but I understand that firmware 1.2.1 is not compatible with TouchNooter 2.1.31 that very much still remains on my N2E.
Wouldn't that be a brick scenario?
Any thoughts?
Hi,
A couple of months back I had installed 1337 ROM on my Nook ST. However, I would now like to go back to stock ROM. Is using Nook Manger and selecting Restore factory.zip option the correct way? If not what steps should I follow?
Thanks
Using Nook Manager is the way to go. I know that there is a factory reset option available, though I can't remember that it is called. (I don' have either of my NSTs with me at the moment, so I can't check.)
David0226 said:
Using Nook Manager is the way to go. I know that there is a factory reset option available, though I can't remember that it is called. (I don' have either of my NSTs with me at the moment, so I can't check.)
Click to expand...
Click to collapse
Thanks for the prompt reply, however one thing that is bothering me is that I don't have a factory.zip file. Is it required or is it already present in an internal partition?
bit_junky said:
Thanks for the prompt reply, however one thing that is bothering me is that I don't have a factory.zip file. Is it required or is it already present in an internal partition?
Click to expand...
Click to collapse
I believe it is in the internal partition, but I am not sure if the 1337 ROM changes that or not.
David0226 said:
...
I know that there is a factory reset option available, though I can't remember that it is called.
Click to expand...
Click to collapse
Assuming that both the stock recovery and factory ROM image in the backup partition are intact, one should be able to trigger a reset to factory-fresh condition by using the "8 failed boots" method -- power on the Nook and as soon as the screen flash on press power button to turn it off, do this 8 times.
bit_junky said:
Hi,
A couple of months back I had installed 1337 ROM on my Nook ST. However, I would now like to go back to stock ROM. Is using Nook Manger and selecting Restore factory.zip option the correct way? If not what steps should I follow?
Thanks
Click to expand...
Click to collapse
Have you had any success so far? I just tried 1337 but it didn't work well on my device and restored to the original firmware. However I made a full backup image of my Nook (including boot partition and stock recovery) before installing Clockworkmod.
If you have not made this backup and installed Clockworkmod to your internal memory, it may be a bit more difficult for you to restore to the original firmware.