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!
Related
Got a Nook Color, decided it wasn't for me even after hacking and custom romming it up and decided to restore to stock and sell. Here's a brief run down:
Followed a guide to flash stock image with custom recovery. When I was rooting I had a micro sd with CR and I had also installed a version to the NC's internal memory. From the guide I read it looked like flashing the stock image would restore it back to stock for everything. Did this and I got the standard boot screens and the setup screen with the girl and the video. Powered it off, cleaned it up, reboxed and put it up for sale. After I sold it I got a call back from the buyer saying it was hanging on the startup screen for nearly ten minutes. That later devevolved into boot loops. I would have originally held by "all sales final" mentality with craigslist buyers but then he mentioned it would flash a screen for a moment that would say "android" before boot looping again. Figured at this point I should be a guy and take it back, mainly because I HAD told him I did not root it. I got it back and it was boot looping, going through the "touch the future of reading" page and the N logo. Forced 8 failed starts and got an error message saying install could not complete. I fiddled some more (this is all while with friends at a Best buy mind you) and managed to get it to boot to screen, register my b&n account, and do a factory reset. After this it operated and ran perfectly fine, and after multiple factory resets, resetup runs, and trouble testing to force issues, it yielded perfect functionality. I even tested to make sure it would accept a credit card and that worked fine.
I'm gearing up to sell it to another buyer but I want to make sure I have my ducks in a row. I haven't fiddled with it beyond what I did the night I took it back but all testing I've done today has been fine. With B&N rolling out a froyo update though I want to be sure the unit is fine and won't give the other guy any trouble. There is no super user login or anything else that would suggest it's rooted or running anything other than stock firmware. I'm thinking that not letting it factory reset after flashing a stock rom may have contributed to my first bout of issues. Is there anything else I can check or look at to make sure the NC is good to go though?
EDIT:
Just performed a successful factory reset with deliberate 8 failed boots. Worked like a charm. Think I'm golden less otherwise advised.
Sent you a PM.
I had successfully manual nootered my NC with Manual Nooter 4.6.16 and was happily using the NC for a month.
Then suddenly the root is gone and I am back to the factory 1.01...
Any ideas on what might have caused that? I don't think anyone forced the factory restore by holding certain buttons down. I also don't think that the battery was fully drained because I had been keeping it charged.
How can I see if any part of my old configuration still exists (apps downloaded, screen layout, etc)? Is it possible that everything from the rooted configuration is still there but something got corrupted and it rebooted into factory 1.01?
Any suggestions for preventing this from happening again?
BTW I used the appropriate version of CMR to do the manual nooter and still have that SD card so rerooting is not an issue. Just trying to figure out what happened...
FWIW since magically going back to 1.01 I haven't been prompted by B&N to auto update to 1.2 ...
Thanks in advance for any advice or ideas...
Doug
Sent from my HTC Evo 4g (Android 2.2) using Forum Runner
I don't know what cause but gotta be something.
AFAIK, never heard of this case once before.
Back in the good old days --Feb or Mar -- I accidently hit Share Books on the BN menu and it did a factory reset ....back to no root.
My wonderful wife gave me an Acer a500 for Christmas. Awesome gift. I had rooted it immediately with no problems, since all of my phones and families phone are rooted, it just seemed to be the natural thing to do.
As someone that "plays" with their android a lot I did all of the backups. Well, the time came to have my tablet "approved" for use at my company and also have the appropriate "encryption" software and keys added. Just as a precaution I decided to restore the original backup and unroot the tab.
All was going well until I received the update message. I went ahead and downloaded the update and ran it. During the install process it froze. I thought it was just busy so I left it for a good 20 minutes and finally realized it was frozen. I rebooted and it went through a couple of reboots and finally settled on the lock screen. But now I find the touch screen unresponsive.
I plugged in a mouse and keyboard in hopes that I could get back into it and start over, but, although, the mouse shows up, it is jumpy sluggish and will not grab the lock to slide open and eventually freezes.
I have tried all of the "update.zip" files I could find and they all fail at one point or another.
ADB allows me to explore in shell but since I unrooted, I cannot get su privileges.
Acer is of course, useless and the vendor it was purchased from is worthless.
I have been through every thread I could find and tried every trick I could come up with. Now I'm just stuck.
Any help is appreciated
I've had this a couple of times already. Usually just turning the screen off and on a couple of times does the job (the issue seems to be with the driver, also on various custom roms). Just try it after each off-on cycle, most of the time it takes no more than two or three tries, though there are exceptions.
Thanks, but it has been rebooted many many times since it's demise.
Decided to skip sleep tonight and keep plugging away.
I found an update.zip recovery file for an a501. Figured I can't do much worse so I went ahead and ran it.
It froze at about 95% but.........
Good News:
The tablet is responsive and touch panel works again.
Bad News:
It boots straight into system settings and although you can open the settings menu, nothing actually launches.
Decided to try all of the old update.zips and still everything fails.
No more ADB response.
When you originally unrooted your device did you revert back to the stock recovery or did you leave cwm on your device?? If you left cwm on your device that may be the problem with the update.zips and OTAs.
You are sooo right. I've never gone back to a stock rom before and I completely forgot about reverting to the stock recovery.
As a matter of fact, I was on Civato's Flexstriker 3.2.1 rom with the new CWM before I reverted back to the stock rom.
Well, at least we've determined my stupid mistake, but now the question lies: "How do I get back to any working rom?"
Here's an update. I did find an update.zip file that also begins to load but does not finish. It stops at 95% still.
I will attach the photos in case someone notices something otherwise I am at a loss. In addition to all of the above, I tried everything I could to get into APX mode but nothing. I am willing to try almost anything at this point, so all suggestions are appreciated.
Something I noticed was the recovery for the a501 was android with gears spinning in the body. The recovery I have now is a package with an arrow. The recoveries are different. The current update file is Acer_A500_1.145.05_COM_GEN1
So this brings me to a question: Can I put Thor's 1.6 CWM back on the a500 and at least work from there? I do have my original backups and thought I might be able to get somewhere that way.
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.
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.