I rooted my Simple Touch (1.2.1 firmware and NookManager 0.5.0) and it all worked fine, I just messed a few things up later on while playing.
I decided to redo the rooting so I restored the backup I took before I started using NookManager, the restore has worked fine (there is the good bit I dont have a brick). Now when I go back into NookManager I select the root option and it comes back almost immediately with success but restarting the Nook just gives me the original Nook software and no Android or Relauncher.
How do I get everything back to rooted (or get access to Relauncher again) ?
Many thanks.
Related
Hi guys, i really need some help here. I bought my NC at the beginning of this month and I'm pretty sure the version is 1.1.0
I wanted to restore my rooted NC back to stock but i accidentally restore it to 1.0.1 instead.
While running on 1.0.1
1) My device can't be registered. I think since I've restore it to 1.0.1, they won't allow me to register my device.
2) I've done the skip out of box experience and tried to do an update to 1.1.0 using the sideload update file (by connecting it to my pc and transferring the file directly)but nothing seem to work.
Can someone please help me?
Does anyone has the stock 1.1.0 file in full which I can try to load it in through clockwerk ?
Yeah, I'm kind of in the same boat. I tried to make a bootable sd card with froyo on it, and I ended up corrupting my Nook's system somehow. I followed the process to restore my nook to stock, but it went back to 1.0.1. Previously, I had updated to 1.1.0.
Now I would like to go back to 1.1.0 and use Autonooter 3.0 to reinstall eclair. But I wasn't able to sideload the 1.1.0 firmware.
Anybody have any tips? Thanks.
i've managed to reset it 1.2.0 instead. What i did was to skip out of the box effect in order to skip the need to register. I connected my NC to a pc and transfer the 1.2.0 update manually. After this ejecting, after a few mins it will start to auto update.
In short: After update to 1.1.2, rooting methods don't work for me. Each time after root, Nook stuck on «nook» screen with 5 circles below (dot continue running until battery discharges completely, screen refreshes non-regularly), except 1st boot with MinimalTouch, which asked about signing-in and location services.
Any help appreciated.
Long story:
Some time ago, I've been beginning with NST 1.0.1, and rooted is successfully with TouchNooter. After it updated to 1.1, and I re-rooted it, successfully again, now with «Market & Setup Script Kit» (which uses uRamdisk-replacing method).
But I didn't turn off OTA update, just not to miss new firmware.
One day about a week ago, it ceased to boot, not going beyond «nook» screen with running dot in 5 circles. I did reset with holding left & right bottom buttons, but it didn't help.
When I booted noogie, I found apparent uRamdisk.old (left from prev. rooting) near uRamdisk, and renamed it to uRamdisk. Nook booted normally, allowed me to register, and let me use it as reader.
But still, I wanted to root.
Tried both touchnooter-2-1-31 and MinimalTouch, both with same result (not loading beyond running dot). Tried installing 1.1.2 in non-rooted mode, and updating again. With MinimalTouch, it boots to sign-in 1st time, but reboots when it should go to home screen. 2nd time an on, it does not boot beyond running dot.
Currently my nook is working, non-rooted, with 1.1.2 firmware. Each time I began from this state.
http://nookdevs.com/Nook_Simple_Touch_restore_to_stock
Haven't tried these but supposedly can revert you back to original firmware then maybe upgrade to 1.1, root, and turn off updates?
I tried the 3rd method on my unrooted nook that had 1.1.2, it claimed to work but version still showed up as 1.1.2.
Regardless I used touchnooter to root and haven't had any issues since. Still shows 1.1.2 in version info but it's rooted and running fine.
Well, I've used methods #2 and #3 several times, and it doesn't help (surprisingly).
I don't think there will be any difference with #1.
What helped me to go back is n2T-Recovery_0.1.img from that post, which initiated full restoration (and it worked). Once I also used full initial backup, from which I retrived some files to undo rooting. I didn't flash it back ever, because I am not sure it's done correctly, as its size differs from one stated in backup article, and is 1'962'934'272 bytes long (exactly same as size on disk).
funny, I've just rooted with uRamdisk_wireless_adb_init_1.1_1.1.2.zip. Now will try to install google apps.
So in the ongoing saga of my nook having a wonked screen that won't respond to outside stimulus I have to ask.
If I download the stock 1.2.1 update and have my nook try installing that. Would it brick?
Thought process is 'i haven't tried taking it back to stock. so maybe that'll trigger something.'
I was able to update my rooted device from 1.1.2 to 1.2. The after re-rooting 1.2, I was able to take it to 1.2.1. I lost root every time, but I did not brick my device. (Of course my device was functioning properly at the time of the upgrades.....)
I've been told that rooted Nook Simple Touch can't be updated, you have to restore official snapshot of the system (or factory defaults) to update it, then re-root.
I've also been told that rooted Nook Simple Touch can be updated, but you will have to re-root after updating.
Personally, i've updated first (to 1.2.1), then rooted with NookManager.
If your NST is rooted it will not run update_version.zip, you will have to restore to factory settings by 8-times disrupted loading, followed by loading and pressing and holding two lower buttons once you see the white circles at start-up screen. Once you've restored to factory settings the NST will be able to run the update_version.zip. Nothing to worry - it'll go fine just make sure NST has enough charge, more than 25%. The updating process may take some time, just relax and go have some tea (coffee, beer, cigarette etc.).
If you can get adb running a much simpler/more reliable way to trigger the factory reset is with echoing the value to the file. granted, I can't remember the exact command at the moment
Yeeeaaa My folks took the thing off to a shop. Honestly kinda doubt they can do anything, not without more or less replacing the main board and the screen (so might as well just get a refurb unit and be done with it.)
But thanks for the info guys!
Hello,
I've encountered a problem that I cannot fix anyhow. Namely, my Nook Simple Touch wants to install some kind of rom and fails to do so. The thing is, I rooted it something like 4 months ago, however, I restored it to stock after a few days. It worked as a charm, but now something went wrong. The screen froze during reading and it did not respond to pushing the on/off button, so I decided to charge it. Having done so, the installation screen appeared. I tried the '8 interrupted starts' method, I tried to root it, I tried to restore it to stock via CMR, all this to no effect. I will appreciate any suggestions
My N7 16GB WiFi, rooted but stock, updated successfully to 4.3 some time ago. Basically, I used Voodoo OTA to save the root, let the OTA do its work, then restored root using Voodoo OTA. It's worked flawlessly since then.
Suddenly, after weeks with no issue, it started insisting it had to install 4.3 from a downloaded file. It nags constantly, which makes it hard to use the tablet. I've got CWM as the recovery so whatever file it's trying to install won't work from there. The only way I can find to go back to stock recovery involves wiping the tablet. I don't want to do that, unless there's no other alternative.
I looked for the update.zip file in the location that the tablet insists its stored at (root of SD card), but there's no file there by that name that I can find. It only shows up if I allow the nag screen to try and install it. Of course, CWM says that it can't verify the file and aborts the install. Which puts me right back at the ever-present nag screen.
Just to be clear, I am already running 4.3. This whole situation came up months after I'd upgraded. Is there anything I can do to stop the upgrade notices, short of running a factory reset and having to set up the tablet again from scratch?
May have found an answer. Used Wug's toolkit to force-restore the standard recovery. Had to do some old ADB driver removal for a bunch of other Android devices first. Appears to have deleted the unnecessary update file as part of the process. Will keep an eye on it going forwards, but think it's good.
Nope -- didn't work. Had to do a full factory reset/restore to out-of-the-box condition to get it to stop constantly trying to re-upgrade to 4.3. Annoying.