Many of us have know that the newest update that was push 2.0.5 break root. Well, for those who didn't know, now you know. Let's me be clear, there is NOTHING TO BLOCK THE OTA UPDATE, unless you build your own firewall. That said, the mod that we had was to use sql and turn automatic OTA into manual thus unless you were looking for it, it shouldn't. Or something you did may accidentally turn it back to automatic.
That said, we had one report of successful revert back to the older firmware here from 2.0.5. I have made a suggestion to manually force the system to fail the boot 8 times and do a full wipe. And this should revert it back to the original firmware that came with the Nook HD/HD+. Well, in the future, this may no longer be the case, as newer Nook may come with 2.0.5 out of the box, but let's do this one step at a time, we aren't there yet and maybe better solution will come later. So, if you accidentally updated to 2.0.5, you should try the following.
Backup your naughty stuff that's on the internal storage (even if they are not naughty, do it so anyway)
Force the nook to fail at least 8 times. First you power the device off then hit the power button, and when it's trying to boot, hold on to the power button, and I think about 10sec after it will force poweroff. You timing have to be quite good and make sure it's not getting a success boot. You basically have to do that at least 8 times.
If you successfully did all that, it should revert back to the original firmware. I know that the 8 boot loop will reset it back to 2.0.0 from 2.0.2 because I did that before.
Try rooting it again.
I hope this help.
Interesting, I'm going to try and force the 8-loop reboot and set if I can get back to 2.04. I think then I also have to skip the out of box registration process as this automatically updates?
it Works
Confirmed !!
I have got my new Nook HD+ yesterday, and before I could root it, it was automatically updated to 2.0.5 by itself today.
So I did the 8 times boot manually, and the system was reset to the original firmware--2.0.4.
After the first boot by skipping the OOBE, I followed the "All-in-one" from someone0, and it works perfectly now with ADW launcher.
But I still cant get the titanium backup to run yet, it says SU error.
Thanks to someone0, leapinlar and verygreen for those great contribution :good:
haym said:
But I still cant get the titanium backup to run yet, it says SU error.
Thanks to someone0, leapinlar and verygreen for those great contribution :good:
Click to expand...
Click to collapse
You still need to run superuser once, did you do that?
Thank you for this very much. Is there no way to prevent updating to version 2.0.5 again? I came home, and my brother was playing on it, he told me something happened. I took a look, and it was updated to 2.0.5. Is there anyway to prevent it again in the future? Will the all-in-one basically disable updating? Since I did install that previously, and the version was still updated.
Sorry for the bother, and thank you very much. I will look into setting up a firewall.
Thank you again.
EDIT: I've conducted the 8-boot loop, and it should have loaded an earlier firmware; however, how would I bypass registration, or the version update check after the 8-boot loop? Thank you.
hiddenG. I had similar issue, I wanted to avoid update so I did a reset, but let it go too far and it updated me to 2005. I then did the 8 time interrupt and got back to 2004. I read here to google "nook color bypass OOTB" as the steps are the same for HD+.
It works
Only thing I'm having trouble running allinone. I don't think I'm doing it right. THe unregistered hd+ lists you as "test" and you have connectivity but no browser. I'm figuring I need to sideload a launcher and I'm looking into how to do that. I do have adb.
If you've registered you might have to reset and catch it as soon as you get to the language screen. You hold volume up. and touch lower left, then lower right to bring up "factory" screen. Then, holding vol up, touch lower right to bring up bypass OOTB.
Dave
Mine automatically updated even though I had automatic update blocked with sqlite. Furthermore, I no longer have access to content I previously purchased on that nook! I can't even download the nook app to fix, it keeps crashing when trying to sync.
Ps, if I re root using reset and skip oobe, then I still won't have access to my content, no?
Sent from my BNTV600 using xda app-developers app
I guess not, you're not registered at all.
dave
Thanks dbrons, that solved my problem. Thank you very much.
Is there anyway to get rid of the "your library is syncing" notification when you use OOBE without turning notifications off entirely?
Ferrian said:
Is there anyway to get rid of the "your library is syncing" notification when you use OOBE without turning notifications off entirely?
Click to expand...
Click to collapse
I also have the same question.
In addition, is there any way to get the "TEST's NOOK" text in the notification bar to be replaced with my own name?
someone0 said:
... unless you build your own firewall.
Click to expand...
Click to collapse
I'm actually curious if this would work. When it suddenly went into 'must get 2.05' mode and I 8-reset it, I disconnected internet right after letting it register...and it pushed me into a loop trying to check for updates and wouldn't proceed.
Any suggestions on domains to be blocked if I were to try this again?
Ferrian said:
Is there anyway to get rid of the "your library is syncing" notification when you use OOBE without turning notifications off entirely?
Click to expand...
Click to collapse
+1
And also, is there any way to get rid of the App Update notifications. There are some that I don't want to update but the notifications keep coming back after clearing them.
So pissed off now....for no reason, when booting up this time my Nook went into a boot loop and reset itself! It wiped everything from internal storage, effectively killing off hours I had spent last night getting everything set on it with apps and root. (this was all after using the All-in-one batch file which supposedly turned off automatic OTA updates)
someone0 said:
You still need to run superuser once, did you do that?
Click to expand...
Click to collapse
Yes, I did, and it works now, Thank you
I spent most the day yesterday toying with getting my Nook HD running again after the 2.0.5 update. I did find that by performing the 8 boot reset back to 2.0.0 and going through the setup process and immediately powering the HD off as soon as it began to check for updates that after I restarted the unit it would bypass the update upon powering it up again and completing the setup. After which I ran someone0's Allinone script which did give me root and load the Google market place. I was able to then load all my apps from the market and change the launcher etc.... After leaving the HD powered on and connected to the network while idle the unit did an auto OTA to 2.0.5 and rebooted on its own. Upon restart, I was at 2.0.5 and root was gone, but the update left the Google Market and all my apps and data in place. Granted I don't have root, but atleast I'm able to customize my own launcher and load and side load any apps I've see fit that dont require root.
Quote:
"I spent most the day yesterday toying with getting my Nook HD running again after the 2.0.5 update. I did find that by performing the 8 boot reset back to 2.0.0 and going through the setup process and immediately powering the HD off as soon as it began to check for updates that after I restarted the unit it would bypass the update upon powering it up again and completing the setup. After which I ran someone0's Allinone script which did give me root and load the Google market place. I was able to then load all my apps from the market and change the launcher etc.... After leaving the HD powered on and connected to the network while idle the unit did an auto OTA to 2.0.5 and rebooted on its own. Upon restart, I was at 2.0.5 and root was gone, but the update left the Google Market and all my apps and data in place. Granted I don't have root, but atleast I'm able to customize my own launcher and load and side load any apps I've see fit that dont require root."
This was the exact procedure that worked for me, other than the fact that my Nook HD+ 8 boot reset to 2.0.4. So its definitely a workable solution until the awesome devs come up with a true solution!
Sent from my BNTV600 using xda premium
can connect to pc
i got it to connect once and adb reconized it i was able to see its serial number by doing adb devices and then tries root and after the first boot my computer would not fully see it it would pop up in my computer and then dissappear it would continue to do this while i had adb enabled after i turned this off it would stop and the nook would show up in my computer but as soon as i turned adb on it would go all crazy and show and dissappear in my computer any help here would be great
Just sit tight I'm sure people are working on root for 2.0.5.
someone0 said:
Just sit tight I'm sure people are working on root for 2.0.5.
Click to expand...
Click to collapse
i have bypassed the update im on 2004
Related
I rooted my nook with my touch nooter when it has first arrived 3 months ago.
I've never bothered to update v.1.01 but now with release of v.1.1 I give it a go,
I've done 8'th failed boot type factory reset then installed the v.1.1
The thing I'm puzzled about is I still have the Go Launcher EX, Dropbox and other apps I've installed prior to reset and v.1.1 same time. But there is no market, and device settings as of an android device.
It's not rooted but still the major app "dropbox" and other pdf readers stays.
Is this a violation of any kind?
You need to do an L+R reset in order to get rid of all that stuff, which is under /data, as well as your settings. Turn on the nook, and then when it starts to turn on, hold the bottom page turn buttons on each side of the nook until it asks you to do a factory reset. Click the home button twice, and the reset will commence. Once you're done, you'll have to re-register your nook, but unless you changed something outside of /system and /data, I think you'll be golden.
Try talking to ros87; he's been extremely helpful and unobnoxious, in spite of my obvious n00bness
-e
ham-solo said:
The thing I'm puzzled about is I still have the Go Launcher EX, Dropbox and other apps I've installed prior to reset and v.1.1 same time. But there is no market, and device settings as of an android device.
Click to expand...
Click to collapse
Factory Restore only restores the system files, it doesn't wipe your /data and that is why you still have your apps.
The Google apps resides in a different place (/system/app) and is therefore normally lost on Restore.
Use the method outlined above or simply go into Settings->Device Info->Erase & Deregister Device which will remove all apps, data and settings for you.
Well, I'm happy that I have them,
After I've sent prior message I've used touch nooter as GabrialDestruir's suggested method, using prior data to root:
"If you're pre-1.1 rooted this SHOULD work:
Run a Factory Restore to wipe /system only - 8 failed boots, or nookRestore image
Run the 1.1 update as is from B&N
Open TouchNooter and remove framework.jar from the TouchNooter disk
Run TouchNooter without 1.0.1 TouchNooter
Go through all steps for Market/Gmail/Youtube
You SHOULD be rooted with working market now"
Now I have SUPER USER, gmail app starts recieves mail but force closes , youtube app worked for sometime after re-installing the app but now it forcecloses....
Market and the market search however works.
Button Saviour and all works either.
Now I got a rooted nook 1.1 I think...
ham-solo said:
Now I have SUPER USER, gmail app starts recieves mail but force closes , youtube app worked for sometime after re-installing the app but now it forcecloses....
Market and the market search however works.
Button Saviour and all works either.
Now I got a rooted nook 1.1 I think...
Click to expand...
Click to collapse
Glad you got it solved mate
New TouchNooter is also right around the corner, maybe that will fix your FC troubles with gmail and youtube.
I have Voodoo OTA Rootkeeper installed & had done a temp unroot, so I could access Amazon prime content, but now I can't get it to restore the root. Any ideas what I'm doing wrong? And it does say "root su restored" after I push the "restore root" button, but even after 2 device restarts, I'm still unrooted. NEED to get on the regular market!
Could it be because it update the os to 6.2? I don't recall what it was before & it never ASKED me to update it, but idk
LoriH7 said:
Could it be because it updated the OS to 6.2? I don't recall what it was before & it never ASKED me to update it, but I don't know.
Click to expand...
Click to collapse
I doubt it, it's working fine for me and many others on 6.2.
If you used it to unroot before 6.2, then when 6.2 silently upgraded, it would have undone the rooting and killed your OTA rooting.
6.2 didn't ask anyone. if you had wifi connected, it would download without messages. and at some point it would have rebooted, like for me. Or others said once they turned it off it went ahead and did it.
super one click will reroot it in less than a minute and you should be good until next time they do this.
Thelgow said:
If you used it to unroot before 6.2, then when 6.2 silently upgraded, it would have undone the rooting and killed your OTA rooting.
6.2 didn't ask anyone. if you had wifi connected, it would download without messages. and at some point it would have rebooted, like for me. Or others said once they turned it off it went ahead and did it.
super one click will reroot it in less than a minute and you should be good until next time they do this.
Click to expand...
Click to collapse
Thanks! I'd bet that's what happened. It's almost always connected to wifi & I've had it rooted for a couple of weeks. Thanks. Back to super one click....
Ok, so I rerooted, but all of my google services are broken still. Reinstalled the apks, but it refuses to install the googleframework.apk. It's on there, asks me about permissions & then says it won't install. I'm clearly missing a step or something.
wierd issue
When I try to reroot my KF after the 6.2 update it roots the device then attempts to reboot into root... and that is when it fails... it just sits on the kindle fire screen flashing like it is rebooting I let it sit for a few minutes and never fineness, however if I hold down the power it will shutdown and I can start it back up but only half way rooted ... and never finished installing superuser or busybody... any ideas?
Not sure about those issues. Different people reported different problems.
Seems not everyone used the same methods. for me googleframework and market worked perfectly fine afterwards, i didnt need to do anything else.
Once my KF updated to 6.2, I could not restore root through OTA Rootkeeper either. Connected it to my computer, ran SuperOneClick, root was restored and backed up my root once again. I think I needed to reset once to ensure that all of my sideloaded apks still worked.
Well I got it figured out I just did a factory reset and reapplied root and now it is working thanks guys
Sent from my Kindle Fire using xda premium
So i have a Nook Simple Touch I was using about 9 months ago, which fell to disuse for a bit for a variety of reasons. It's running 1.1.0, and is rooted.
I dusted it off to recently give it some more use again, and wanted to update some of the apps, but discovered that the Market doesn't seem to work anymore - I know it used to, but now, whenever I try to download anything, I get a dialog: "Download Errror: Download was unsuccessful, please try again." I've waited an extra day, as I remember that was originally necessary to complete the registration process, but still nothing. Searching (with Market Search) works, even for things I haven't looked up before, and it still recognizes my account, as I see my email, though I noticed that the Nook Touch doesn't get listed in the Google Play Store under devices.
Any ideas what might be going wrong here, or things to try? I'm also willing to upgrade to a newer firmware (1.2.1), but am not sure of the best method to update a rooted device. I can pull it into a separate post, but I'll include it here for now:
I'm sure I'l have to root again, but Is it possible to upgrade the rooted device and then simply re-root, or will I lose everything I've installed? Is it just better to wipe, update and re-root? If so, is there any convenient way to keep all of my settings?
Thanks!
mrgygar said:
So i have a Nook Simple Touch I was using about 9 months ago, which fell to disuse for a bit for a variety of reasons. It's running 1.1.0, and is rooted.
I dusted it off to recently give it some more use again, and wanted to update some of the apps, but discovered that the Market doesn't seem to work anymore - I know it used to, but now, whenever I try to download anything, I get a dialog: "Download Errror: Download was unsuccessful, please try again." I've waited an extra day, as I remember that was originally necessary to complete the registration process, but still nothing. Searching (with Market Search) works, even for things I haven't looked up before, and it still recognizes my account, as I see my email, though I noticed that the Nook Touch doesn't get listed in the Google Play Store under devices.
Any ideas what might be going wrong here, or things to try? I'm also willing to upgrade to a newer firmware (1.2.1), but am not sure of the best method to update a rooted device. I can pull it into a separate post, but I'll include it here for now:
I'm sure I'l have to root again, but Is it possible to upgrade the rooted device and then simply re-root, or will I lose everything I've installed? Is it just better to wipe, update and re-root? If so, is there any convenient way to keep all of my settings?
Thanks!
Click to expand...
Click to collapse
Sad, no one wants to reply. Or perhaps no one knows.
Did a backup, and experimented. I couldn't update directly, so I wiped back to a stock ROM, and upgraded to 1.2.1. Rooted with ManualNooter, and the market worked. So I have no idea what was going on, but it works now. Sadly, a computer accident made me lose my backups (including unrooted images). But at least I've got something functional.
I am currently in the same boat with my NST (BNRV300) running rooted 1.1.2. I last installed and/or updated some Market apps successfully perhaps about a year ago, and have not made any other change to the Nook, so I am at a lost as to what might be the cause. Any pointers would be greatly appreciated.
For now, my workaround this problem is to download the desired app's apk file from an alternate source (e.g., APKPure) then side-load it onto the NST.
My guess would be that somehow your authtication with Google has been lost on the device.
If you go to the PlayStore on a computer do you see your NST listed as a device, and if so, when you select an app that way does it eventually appear on your NST?
Sent from my NST
nmyshkin said:
My guess would be that somehow your authtication with Google has been lost on the device.
If you go to the PlayStore on a computer do you see your NST listed as a device, and if so, when you select an app that way does it eventually appear on your NST?
Click to expand...
Click to collapse
I think you are right -- my NST credential with the Playstore must have expired or more likely become invalid when I changed my password on my Gmail account.
If so I can't figure out how to re-validate the credential: I recall entering my Google login/password via the YouTube app during the course of rooting my NST using the MinimalTouch tool's 2-phase process, but now I can't even get the YouTube app to start (error message: ... problem starting up, please check your network connection and system time).
Look here
I responded to a related issue awhile back. Not sure if the info at the link might kick-start the signing in process.
Thanks for the pointer.
I decided to go the route of "factory reset, upgrade to 1.2.1 and re-root using Nook Manager", as simply re-rooting 1.1.2 using the old tool (Minimal Touch) is tedious & somewhat error-prone -- plus I'd like to try out 1.2.1.
That was what I would usually suggest but the farther I have gotten from that "day 1", the less likely I am to take/offer the same advice. I've made so many modifications at this point I don't think I'd ever get it back to its present state! Back up early and often...and, apparently, access the Market every so often, even if you don't want anything.
Good luck!
So I was (and I hope still am) happily rooted with touchnooter. Mostly I'm using my nook to read pdfs with ebooka pdf for grad school.
I had the thing plugged into my comp for a bit to download the week's assignments and I noticed once or twice the thing disconnected and reconnected itself without warning. No biggie. I finish the downloads, do a few other things eject the device and unplug the USB cord.
Since then, strange things have been happening. Symptoms I've noticed so far:
1. n button no longer emulates the home button but has reverted to the old bottom menu that comes with factory setting nooks (home/library/etc)
2. While investigating this, I noticed that the shortcut to NookColor Tools is now a dead link. Has the android box icon and doesn't do anything when you click it
3. Search market lets you enter in text, but when you hit search... nothing happens. Market seems to have vanished from my app drawer. In fact several have but I can't identify them.
4.The music app, which I thought I uninstalled, has reappeared in my app drawer
5. Multitouch zoom no longer works in eBooka PDF reader. Don't have any other apps to test multitouch with, but this one's kinda critical and was what led me to finally posting on here.
Up to this point I'd never had any of these problems. NoRefresh was always a bit funky, often turning itself off for no apparenet reason, and sometimes not being able to start up at all. But that was it. Now I feel like my nook might be losing it. Any idea what's going on or how to fix it?
Now I've noticed that Nook Touch Tools, while still installed, has lost root permissions. Also when I try to hit the B&N buttons thing, I get an error saying "No patched android.policy.jar found"
SU still installed, I'm going to try to futz with it and restore root permissions manually. Still clueless and worried.
EDIT I've been poking around more and found the following:
-BusyBox Installer, when run gives the error "The su binary was not found on your phone. This application will not work without root.
-#superuser runs fine and lists nook touch tools, button savior, norefresh, usbhostmode and ES file explorer as all being allowed to have root access. Don't see an obvious way to add more apps to that list (or why nook touch tools thinks it doesn't have access).
-Super Manager does not run
-youtube app doesn't run. Not like I use it, but given market disappearing it seems ominous
-the thing has now frozen on me multiple times while using Ebooka PDF reader, which use to be rock stable.
...do I need to factory reset and start over? I'd really rather not if I can avoid it.
EDIT (again): Man, as if this wasn't weird enough already. I've just went into nook's system settings and the firmware appears to have downgraded itself to 1.0.0. I could've sworn I'd gotten it to 1.1 before I rooted it, but since that was almost a year ago I guess I could be mistaken.
Progress! Or at least a clue. I did some research and found that 8 false boot attempts causes the thing to factory reset. I was not in the room the entire time the thing was accidentally disconnecting from my computer.
You see I have pretty much given up at this point and resigned to factory restting and re-rooting. So I backed everything up, got nook manager, made yet another backup with that, and then told it to use factory.zip. So it did. The thing restored factory settings, then rebooted... and looked exactly the same. Still registered to me and everything and all apps are pretty much exactly how they were before when I first started noticing problems.
In other words, I think this all started when, without my realizing, the thing factory reset itself.
I'm gonna try upgrading the FW and rerooting, this time using Nook Manager. If things get nasty, I can always restore the backups.
Solved. I hope this solo thread account is useful to someone else who encounters the same problem. Thinking a little more carefully, I went back to TouchNooter instead of Nook Manager and used the 1.1 FW. That and the multitouch and usb host kernel patch via CWM did the trick and my nook is back to functioning as well as it ever did. That was several hours I wish I'd been asleep for instead...
NOT Solved. The d*mn thing reverted and I don't know why. I didn't have it plugged it at all (ie none of the disconnection problems I mentioned before), but all of the old symptoms have returned and I'm back on firmware 1.0.0. Will re-root and re-patch the kernel. Anyone have any idea what the heck is going on or how to prevent it from happening again?
EDIT: Well that plan failed. TouchNooter semi-bricks the device. I can recover using Nook manager to restore factory.zip, but haven't figured out anything past that. I'm going to try erasing as much as possible and then rooting via NookManager...
Well. I erased and deregistered the device, upgraded the firmware to 1.2.1 (per Nook Manager rooting instructions), and rooted using Nook Manager instead of TouchNooter. I used GApps attack and everything seems to be working fine... except I've still lost the main features that brought me to making this thread in the first place: multitouch, usb host support, and now also NoRefresh is nowhere to be found. Is there a way to get these back without using adb? I can't get my comp to recognize my nook as a device through adb, but I've got a ClockworkMod disk image I can easily play with, so .zip patches would be most welcome. Thanks!
Ive just rebooted my fire tablet after installing some minecraft mods, when I turnt it back on it came up with a promt saying it was installing the latest software or what ever it does when doing the ota, I knew this from upgrading to 5.0.1.
is it possible it was just doing what happens when normal android optimises apps on boot. is there a app to check the installed software version as im not near my pc to unhide and go in and check what firmware im on. I put this in general as it wasnt a question but just to inform that my tablet possibly had a update despite the proper steps taken to hide the ota and updates.
Saw Same Message But No Update (whew)!
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
dubliner52 said:
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
Click to expand...
Click to collapse
Have you tried unhiding to see the software version
Sent from my HTC One_M8 using Tapatalk
I didn't unhide it, but it says I'm still on 5.0.1. There was no update.
I saw the same thing but it didn't seem to update. I know the method i provided works for 5.0.0 to 5.0.1. Until there is a bump to 5.0.2 or whatever we don't know for sure if the "fix" works under 5.0.1.
Same thing happened to me but it was 3 days ago. I had been trying all day to install my adb drivers without success and switched off the device. When I restarted it immediately went into an update and I went into a panic that the new update would block the ability to access google play but immediately after the assumed "update" I successfully installed the adb drivers and google play without problem. I also checked the version and it still showed 5.0.1 so I wondered if my initial update on switching on the fire for the 1st time had somehow been unsuccessful and that had been what had been causing the inability to load the adb drivers although the tablet hadn't seemed to have any other problems and I had already downloaded and used several apps from Amazon.
I let it update upon first booting my Fire to 5.0.1. I was still successful in installing Google Playstore and hiding ads on lockscreen.
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik runtime files after rebooting when an apk is modified. nothing to do with an ota.
julianpaul said:
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik files after rebooting when an apk is modified. nothing to do with an ota.
Click to expand...
Click to collapse
That is my conclusion also.
I had this happen to me also. Considering amazon patched a root method I made sure to root and nuke any chance of a future OTA unless I wanted it too. That was a cheap move, Amazon.