I rooted with z4 a few months ago. Today I got the bright idea to install Rom Manager to play around with. I clicked clockworkmod recovery without really thinking (or knowing what it does). Now Titanium Backup doesn't work because it says I'm not rooted.
I uninstalled Rom Manager but that didn't help. I tried rerooting with z4 but it only crashes.
What did I do and how do I undo it?
HELP.......
Soundchasr said:
I rooted with z4 a few months ago. Today I got the bright idea to install Rom Manager to play around with. I clicked clockworkmod recovery without really thinking (or knowing what it does). Now Titanium Backup doesn't work because it says I'm not rooted.
I uninstalled Rom Manager but that didn't help. I tried rerooting with z4 but it only crashes.
What did I do and how do I undo it?
HELP.......
Click to expand...
Click to collapse
Please try this in order
1st. You can run a restore if you have clockwork recovery
2nd. Use alternative SU if you just need to restore file
3rd. Worst come to worst, backup your data and install ROTO rom / Clock Work Rom..
Thanks. I'll give it a try tonight.
1. So, if I reinstall Rom Manager I should be able to do a restore?
Is there a good ROM that works with Rom Manager that I could install that would give me back root and also a new ROM?
Soundchasr said:
Thanks. I'll give it a try tonight.
1. So, if I reinstall Rom Manager I should be able to do a restore?
Is there a good ROM that works with Rom Manager that I could install that would give me back root and also a new ROM?
Click to expand...
Click to collapse
That really depends on what version Tab you have.
Currently for GSM devices, Overcome seems to be the ROM of choice, and I do not believe Alter has it able to update via Rom Manager.
I can't speak for CDMA devices, I don't own one.
btyork said:
That really depends on what version Tab you have.
Currently for GSM devices, Overcome seems to be the ROM of choice, and I do not believe Alter has it able to update via Rom Manager.
I can't speak for CDMA devices, I don't own one.
Click to expand...
Click to collapse
Ok, I'm running Verizon CDMA.
I coudn't root with z4root(it kept crashing), but oneclickroot (free on the market) worked like a charm.
Sent from my GT-P1000 using XDA App
I reinstalled ROM manager but there's no way to "undo" whatever the heck I did.
Is there a way to go back to stock?
I'm not sure why but the whole system is really slow now...
I just want to get back to stock (before ROM Manager and Clockwork). How do I do this?
Soundchasr said:
I just want to get back to stock (before ROM Manager and Clockwork). How do I do this?
Click to expand...
Click to collapse
You will need the original firmware + modem file etc and flashed it via heimdal and odin but that may be is last alternative you want to consider.
I am not sure if the default stock is able to reset, i have never try before but it should be able to.
Try this:
1. Switch off your tab
2. Open up your tab by pressing power and sound up
3. you should be able to see the recovery (i am not sure about this part for default stock)
4. there should be an option to do a factory reset (Make sure your current stock is default ROM)
Hope it helps.
Ok, I did what you said. Here's what I see:
Android System Recovery <3a>
Samsung Recovery Utils
- for BML -
reboot system now
apply sdcard: update.zip
wipe data/factory reset
wipe cache partition
I'm not sure what to do now. I don't really want to erase all my data......
I'd gladly install a new ROM instead of going to stock. I'm just in a limbo state now (clockworkmod, no root and really slow system) and I'm not confident that I know enough to do the flash).
Where are the instructions for stupid people?
Is my stuff gone once i do the factory reset??
How do i get TB to restore everything if it in itself is wiped from my phone?
Help to a good backup discussion source would be MUCH appreciated
Copy the backup folder to the external SD card, then pull the card when you restore. or use the built in dropbox sync.......
well i suppose you did a backup first right? you cant restore if you didint backup first.
so if you make a backup just reinstall TB (get root and sideloading first)
and then all should be fine (if you have the folder in your pc, dropbox, or whatever put again to SD card internal o external) if you change the name just make sure in preference point the Folder Name and you can restore now.
Yes i backed up, but forgot to copy the folder over to SD card....but i browsed and saw TB folder in phone memory so hopefully it'll be fine to pull from there...?
OK, so here's another question that confuses me: i was backing up so i could flash the new update 1.5.7 to try to fix some battery issues. i did a hard reset first, now am flashing 1.5.7 - then i will need to root after that i am guessing right?
What is most recommended after flashing 1.5.7 - root only then freeze manually, flash custom rom, something else? just looking for what others are mostly doing to optimize device for now
Dillsnik said:
Yes i backed up, but forgot to copy the folder over to SD card....but i browsed and saw TB folder in phone memory so hopefully it'll be fine to pull from there...?
OK, so here's another question that confuses me: i was backing up so i could flash the new update 1.5.7 to try to fix some battery issues. i did a hard reset first, now am flashing 1.5.7 - then i will need to root after that i am guessing right?
What is most recommended after flashing 1.5.7 - root only then freeze manually, flash custom rom, something else? just looking for what others are mostly doing to optimize device for now
Click to expand...
Click to collapse
Flashing directly to 1.57 will not allow you to root. You need to flash to 1.26 then use the retain root method to update to 1.57. As far as TB goes, it stores on the internal SD which isn't cleared by a factory reset but I always keep a backup on my external SD. Personally I am on 1.57 and running gingerblur 1.3 which has been quite smooth and it removes most of the bloatware for you. The rest can be frozen using TB.
Sent from my MB860 using Tapatalk
oh whoops, ok, back to 1.26, then to 1.57..sigh, that flash to 1.57 took like 4 tries and kept hanging....i don't know why my piece does that
Edit: How do i retain root?
Follow the directions here to obtain root on 4.1.57
http://forum.xda-developers.com/showthread.php?t=1016060
One last question:
Once i flash something, be it a new SBF, custom rom etc, and then do a factory reset from the device, does this just reset me to the last flash or back to a factory default?
Ok, so i lied, i have another question...where did all my messages and stuff go? not sure how to properly backup/restore those with TB....thought they would have been restored with run "restore all apps with data"
Hello, another noob here.
This is my first android phone and I am not too happy about the battery life.
As the recommendation on the forum, I plan to do the "factory reset"
I wanted to confirm some things:
1. This reset people are talking about is >Settings>Privacy>Factory Data Reset?
2. I am on 1.57 rooted and with webtop hack. I need to undo webtop hack first before reset?
3. I have titanium pro freezing motoblur stuff, I need to unfreeze them first?
4. Will I become "Unrooted" ?
5. How do i back up contacts with titanium backup pro? (do i back up contacts 2.2.1 OR contact storage 2.2.1)
6. If the reset gets rid of root, should I SBF to 1.2.6 and then factory reset and redo my mods from there?
Thank you, I hope someone can help me get a clearer understanding
So basically, I did a factory reset based on advice in the PRIME 1.4 thread. I'd already backed up my apps with Titanium Backup and so all was good.
After rebooting from CWM I went through the set up and got to the launcher. Installed TB and started restoring my apps. Straight away I started getting FCs all over the place.
I rebooted and ended up boot-looping.
I flashed back to PRIMORDIAL 3.1 and got to the setup. Rebooted into CWM and re-flashed PRIME 1.4
Started restoring one app at a time and again started getting FCs on certain apps (all variations of Angry Birds, Audiogalaxy, etc.)
Any ideas?
did you do a full wipe through CWM + dalvik wipe yet?
seshmaru said:
did you do a full wipe through CWM + dalvik wipe yet?
Click to expand...
Click to collapse
Yep. I think the full wipe started this fiasco.
To add insult to injury, tapping 'My apps' in Market now FCs too
Sent from my rooted ASUS Transformer running PRIME 1.4
I'd suggest doing a full wipe again through CWM, flash PRIME! 1.4, do a factory reset right off the bat if you want. If that fails unroot your tab by pushing the original Asus blob and rerooting your tab.
seshmaru said:
I'd suggest doing a full wipe again through CWM, flash PRIME! 1.4, do a factory reset right off the bat if you want. If that fails unroot your tab by pushing the original Asus blob and rerooting your tab.
Click to expand...
Click to collapse
OK, found a symptom, but I don't likewhat the cause seems to be. If I uninstall the app (Angry Birds, say) and then install from market, it works. I can then restore the data from TB and I'm good. Like I said, I don't like where this is going, because it *could* mean an issue with TB.
Sent from my rooted ASUS Transformer running PRIME 1.4
jhanford said:
OK, found a symptom, but I don't likewhat the cause seems to be. If I uninstall the app (Angry Birds, say) and then install from market, it works. I can then restore the data from TB and I'm good. Like I said, I don't like where this is going, because it *could* mean an issue with TB.
Sent from my rooted ASUS Transformer running PRIME 1.4
Click to expand...
Click to collapse
Sounds like a TB issue.
Restoring data from tb has always been sketchy.
Decided to do a full unroot back to 8.2.3.9 and start again. We'll see how it goes.
FYI: I *was* able to restore from TB the first time I rooted and flashed PRIMORDIAL 3.1 when I first got the device.
On Prime 1.4 did you have one of the power button reboot mods applied? If you wipe/factory reset with that applied Roach warns it will cause Boot Loops, and he has a file posted to go back to stock button mod for after wiping. Maybe this was your issue
Skater4599 said:
On Prime 1.4 did you have one of the power button reboot mods applied? If you wipe/factory reset with that applied Roach warns it will cause Boot Loops, and he has a file posted to go back to stock button mod for after wiping. Maybe this was your issue
Click to expand...
Click to collapse
Yeah I did. But I was still getting the boot-looping after re-flashing just PRIME 1.4 on its own.
Anyway I'm back up and running after going through a complete roll back to 3.0.1.
ProTip: Install solarnz's CWM prior doing factory reset if you want to avoid feeling like a complete idiot for the rest of the day (in addition to everything else!)
Also, dont restore system data through TB. defeats the whole purpose of wiping between flash
Tjwoo said:
Also, dont restore system data through TB. defeats the whole purpose of wiping between flash
Click to expand...
Click to collapse
Yeah understood (I'm a one year owner of a rooted Droid X)
Status Update: I'm back on PRIME 1.4 and didn't restore anything via TB (although it WAS useful in reminding me what was installed)
I've done a nandroid backup, so I may do a TB backup and then uninstall an app and attempt a restore though TB.
Sent from my Transformer TF101 using XDA Premium App
Agree with tjwoo. I shy away from allowing TB to restore data along with apps. Never had an issue when installing ONLY apps. Yeah, takes a bit longer but saves from the hassle you describe.
That would be RE-installing apps.
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..
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.