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
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
My device was running Fire OS 5.0 and I installed my copy of Titanium Pro (used APK extractor on another Android device as play not working on 5.0).
I then proceeded to kill as many Amazon processes based on my Remove Bloat thread - I actually deleted them from the device so that they were no longer there. I kept the OTA processes in place - reset the device from [Recovery Mode] and upon boot joined WiFi and proceeded with the upgrade to 5.01
The update by the looks of things repaired the Fire OS and the system processes that I had deleted were now back on the device (Kindle Book Store etc). It also removed root from the device.
So just like everyone says - disabled OTA updates if you do not wish t remove root.
Were you able to reinstall root post update?
shinji257 said:
Were you able to reinstall root post update?
Click to expand...
Click to collapse
Would love to know also
Sent from my Amazon Fire 2015
i reinstalled the firmware to give it real factory reset, and applied OTA twice yesterday, but I could make it rooted after that. So I guess you can reinstall root again because the updated system did not reject root.
shinji257 said:
Were you able to reinstall root post update?
Click to expand...
Click to collapse
Yes I was able to root 5.01 after the OTA update
I would strongly advise everyone to disable the OTA processes. If you want to update a new device from 5.0 to 5.0.1 you can do so manually. Fire (5th Gen) updates are available here https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
Who knows when amazon will roll out the next OTA, tomorrow, next week, next month. And they certainly might block root with it. The fire cost us only $50, amazon may be losing money on the straight device price. They want us to spending money on all the premium amazon services that we are striping out as bloat. They may need the money to even break even.
Huh... This actually gave me some insight into the OTA bit. I went and pulled the latest update and it basically overwrites the system partition. That's why it seems to undo everything you did. This is good though because it also means if it won't boot then I should be able to get into 3e recovery and sideload the most recent update back to the device. I tested this by flashing google play then "repairing" using the update and google play was no longer present from this. It also doesn't seem to wipe userdata when doing this which is nice.
Bought a new Fire HD 10 today, it came with OS 5.4.
I was able to get SU and load Google Play.
I did then try to set a new Launcher, but have not yet succeeded.
Now my question:
Can I update the OS to 5.6.x?
Or would I loose a lot of the other items?
Any hints, what I missed on changing the launcher?
You can update, the version 5.6.0.1 is rootable, the version from today, perhabs tomorrow it will be changed
Interestingly enough, it wont update to 5.6.xxx
I even did a factory reset and it fails to update
then i downloaded the 5.6 bin from Amazon, dropped it on the tablet and it doesn't update...
timf79 said:
Interestingly enough, it wont update to 5.6.xxx
I even did a factory reset and it fails to update
then i downloaded the 5.6 bin from Amazon, dropped it on the tablet and it doesn't update...
Click to expand...
Click to collapse
try with adb sideload