[NST] can't root after update to 1.1.2 - Nook Touch General

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.

Related

[Q] Problem: Unresponsive screen after update

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.

Will a Stock Update Brick a Rooted Device?

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!

[Q] Re-rooting wont work

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.

[Q] N7 running 4.3 keeps trying to update to 4.3

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.

[SOLVED] Suddenly G2 boots only into recovery mode (loop)

Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.
Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.
I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.

Categories

Resources