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
Whenever I boot it up it says "Unfortunately, System UI has stopped.". It does allow me to hit ok, however when I hit ok I have about 1 second before it pops up again. Due to the passcode lock on my phone I am unable to get past the lockscreen as it wipes the input box everytime the popup box pops up. Despite the System UI apparently failing everything does seem to be functional behind the pop up. In the 1 second periods between pop ups I am able to interact with it. The status bar and the buttons on the bottom are not visible, however the rest of the lockscreen (including widgets) is.
The phone is rooted, however I had not gotten around to installing a custom bootloader yet. Debugging is enabled, however the device is listed as "offline" according to "adb devices". Due to this I am unable to install TWRP so as to flash the zip to disable xposed.
All of the above is still true in safe mode, the exact same thing happens.
Does anyone know how to fix this? I would prefer to keep the data on it, however if nothing else a factory reset would be fine.
Update: Solution was to do this. The offending xposed module was xhalofloatingwindow. I have managed to reproduce the error multiple times, so it would appear that xhalofloatingwindow is incompatible with the LG G2 (AT&T) on 4.2.2.
It is only the latest version that is incompatible. Uninstall Beta 2.16 and install 2.14 then it will work. Came across your post as I was searching in tapatalk for the official thread to report this in. Hope it helps.
Sent from my VS980 4G using xda app-developers app
Hey guys,
Hopefully someone can provide a bit of help or point me in the right direction.
Tonight I installed (what I thought was) an update but accidentally installed the original 6.0.0 image for my 6P (MDA89D).
I noticed that not much on my phone was working, discovered my error, and went ahead and updated to the latest image (MTC19X).
Most of the phone's functions remained unable to work using this image so I also tried the last image I was on before updating.
Now after trying to uninstall xposed, reinstall xposed, disable certain modules, etc I am unable to get certain functions of the phone to work.
The things I've noticed are: my recents button doesn't function, no notifications are popping up on my notification panel, I can't expand my notification panel to show quick settings, sometimes home button doesn't function at all. If it helps "vibrate on touch" was turned on for some reason after I updated the second time.
The first update I did was using FlashFire (undid xposed, installed update, reinstalled xposed), the rest of the updates were using fastboot to update everything but data.img.
Well I ended up finding the fix finally thanks to a little more googling.
running "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" and going through the setup ended up fixing it
Might as well leave this up in case anyone else needs help in the future
I have a rooted S7 Verizon and for the past week get a message after every reboot that there is an update that it wants to install.
If I tell it to go ahead, it will fail. But that is not the end of it, as it will ask me again and again to install (now or later). How do I delete this downloaded OTA or prevent it from re-asking if I want to install? What can freeze (Anttek manager app) or delete to solve this?
I'm running Android 7.0, build BQA4, SM-G930V phone
Thanks.
I had the same problem and same situation Verizon S7 Rooted. I went to the application manager and selected from right hand upper corner show system apps. Scroll down to System Updates app and force stop it. To make sure I didn't get any notifications while inside the app in the application manager select hide notifications for the app. Then in Titanium Backup freeze the app and it should bother you no more. Hope that helps.
Freezing both system update programs using Titanium did seem to stop the warning.
Has anyone gotten latest version of PoGo working on latest Oreo with ElementalX? I've never played but my friends keep asking me to join so I figured what the heck..
Slight problem... Device Not Compatible??
I had magisk and xposed, but I tried disabling, and even fully uninstalling xposed (and all additional xposed modules), and adding PoGo to the MagiskHide options, with no luck.
It still says that my device is not compatible...I would assume that's due to the rooting?
Or is it because I'm using ElementalX kernel?
I read somewhere that there's a (not pokemon go-specific) bypass sort of thing involving SatefyNet, but you have to install Magisk *before* going through initial phone setup, but any guide I've ever read about flashing/rooting ph-1 says to go through setup and then install magisk. I tried to find the post that talks about it but I can't find it right now. Anyway, I would imagine there's some kind of checksum against system and if magisk has been added after the fact, the checksum wont match? I really have no idea, just a guess.
I haven't seen any other posts specifically mentioning Essential being incompatible, so maybe it's just me.
I was originally thinking it was because of root or magisk remnants(?), but maybe it's the non-stock kernel.
If anyone could help, I'd really appreciate it.
I feel silly asking such a noob question, I've just never play PoGo...or any Pokemon...ever.
extra info:
I have successfully created an account using their google auth option.
I get through the first Professor Willow part, then character selection.
Usually part way through character selection, I get the error in the attached image.
Its not on any one specific section, however, it can/has occur at any point during the loading.
I've cleared cache and data a hundred times because it seems to get further each time if I do a fresh data wipe and start over -- I know the next step already so I can get through faster maybe lol
--update--
I finally got through character selection and made it to the first chance to catch pokemon. I hit a squirtle and it was trying to break free, and then that error popped up.
Haven't been able to get back in far enough again to see if it actually added to my PokeDex or not.
Sorry for the late reply, but you have to hide root detection under magisk.
For Pokemon go to work, go to Magisk > MagiskHide > then search for Pokemon go and select it then reboot.