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
Related
I may have missed this in another thread, so please feel free to redirect me if so...
Without thinking, I updated my Droid with the OTA push and my previously rooted Droid 2 is now not rooted.
I did try to run the oneclick and 1-2-3 root processes. Both end with "your device is now rooted", but of course it's really not. I do have the Superuser APK, but my rooted programs are not communicating with it. And I'm not able to uninstall the Superuser program (thought I'd try to reinstall it). No go.
I had Titanium Backup, ad am wondering if I can wipe my phone and restore it, then upgrade, and root after. I'm a newbie with limited knowledge, so wondering if I've backed myself into a corner on this one.
All feedback appreciated!
Yesterday, I did the same thing you tried and I was successful in rerooting my phone after the OTA update. When you used the 1-click process did you choose option 1 or 2. I tried 2 and it didn't work. I had to chose option 1 (reload everything) to be successful. BTW, remember to make a new recovery backup of the system.
unrooted
xberry said:
I may have missed this in another thread, so please feel free to redirect me if so...
Without thinking, I updated my Droid with the OTA push and my previously rooted Droid 2 is now not rooted.
I did try to run the oneclick and 1-2-3 root processes. Both end with "your device is now rooted", but of course it's really not. I do have the Superuser APK, but my rooted programs are not communicating with it. And I'm not able to uninstall the Superuser program (thought I'd try to reinstall it). No go.
I had Titanium Backup, ad am wondering if I can wipe my phone and restore it, then upgrade, and root after. I'm a newbie with limited knowledge, so wondering if I've backed myself into a corner on this one.
All feedback appreciated!
Click to expand...
Click to collapse
Same issue here - how I fixed
I had already made titanium backups of important stuff - you have to go into applications (that use root) and force stop and clear data. Once this is complete open titanium backup for instance, and you should be asked for super user and then be good to go. Same goes for rest of apps that need root
OTA update Loop?
i have my d2 rooted after the ota 2.2 update. i just received a notification to accept the most recent OTA update ... whatever it is... and assumed it was one of my apps as i didnt read it thru completely b4 tapping 'ok'. now it is stuck in a download, reboot, update, "update unsuccessfully installed", redownload, reboot...........
is there a way to cancel the update? i dont really care if i have it or not
or some way to stop this process aside from the airplane mode i had to set it to so it would stop this madness
So you can do the OTA update without having to unroot and reroot?
Great advice from all - thanks! I'm not sure exactly what fixed it, but I ran DOROOT several times, did the unplug/plug when it hung for a minute, force closed/cleared data from previously rooted items, and also put phone into 'charge only' mode when USB Debugger would not run.
Finally - success! My advice to users with this same issue - try and try again.
Thanks all!
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
I rooted my phone using towel root, everything seemed fine until it started randomly crashing. Now the crashing happens like this, the screen will freeze (with like weird tearing) then either restart or stay frozen. The only root app I use is wifi tether router. I did notice supersu will fail to update the binaries. Not sure if that could be a cause.
My question is how do I unroot it. So I can at least attempt any kind of fix. I'm still under warranty.
Can anyone help me at all? Please
waterbottels said:
I rooted my phone using towel root, everything seemed fine until it started randomly crashing. Now the crashing happens like this, the screen will freeze (with like weird tearing) then either restart or stay frozen. The only root app I use is wifi tether router. I did notice supersu will fail to update the binaries. Not sure if that could be a cause.
My question is how do I unroot it. So I can at least attempt any kind of fix. I'm still under warranty.
Can anyone help me at all? Please
Click to expand...
Click to collapse
A thorough way to unroot and reset everything is to Odin back to stock and then do a factory reset. The stock tar can be found here.
kinstre11 said:
A thorough way to unroot and reset everything is to Odin back to stock and then do a factory reset. The stock tar can be found here.
Click to expand...
Click to collapse
I was able to get supersu to work again, could I do an unroot through that even if I used towelroot?
waterbottels said:
I was able to get supersu to work again, could I do an unroot through that even if I used towelroot?
Click to expand...
Click to collapse
There is an unroot option in SuperSU (although I've never done it so I don't know if it actually unroots or just cleans up things to allow a clean unroot. The other thing I'm not sure it does is restore Knox which is something that will be checked for by the manufacturer). If you're taking your phone back or sending it in under warranty you probably should make sure you uninstall anything you need root for prior to unrooting, but if you're on a custom rom or want to make sure everything is back to factory (including Knox) I would recommend doing what I suggested in my last post.
Same Problem
Same problem as OP. I had a Note 3 originally that I took the update to 4.4.2 and used Towelroot and everything was fine. I recently broke the bejesus out of my Note 3 and got a replacement under the warranty. I used Towelroot on the new Note 3 and I am getting random freezing and a weird line that appears across the screen once it freezes. Sometimes it will reboot others I need to pull the battery.
What is happening? I am now back to stock and want to root again. Anyone have a solution to this?
I just wanted to share with you that i just successfully rooted my shield with Kingroot
It is just install apk, touch root and wait.
It rebooted my tlet thefirst try,but worked the second one! No wipe, no flash, no data loss
It worked with my galaxy mini s5 too...
It worked!!!! By the God's!!!! On ota 2.2.1!!! I don't have access to a PC and when I got to one it was xp and didn't work on adb, after a catastrophic recovery fail. I got lucky and got a full ota to flash in nvidias stock recovery but ended up with no root. I thought I was gonna be stuck for a month until family visited with a laptop.... This worked enough to use flashify !!! Thanks for the heads up
Worked for me too.
First three times the operation was unsucessful and the tablet rebooted itself, but then I remember to activate USB depuration and that was it! Rooted at Last.
Anyone have a link to the APK?
There is a post in xda general:
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Greetings
Does this work on the latest update anyone can confirm?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Yes, I would also like to know if this will root 5.1. Would also like to unlock the boot loader.
Yes, OTA 3.0 rooted using kingroot, y just installed it to try and viola.
Confirmed on ota 3
I installed it and it locks up around 22% then reboots comes back with a fail. Tried a couple times and my shield tablet on 5.1 will NOT root! Grrr!! It is Kingroot 4.1.
JohnK71 said:
I installed it and it locks up around 22% then reboots comes back with a fail. Tried a couple times and my shield tablet on 5.1 will NOT root! Grrr!! It is Kingroot 4.1.
Click to expand...
Click to collapse
Did you activate USB debug in development options?
Yes, USB debugging was on. It rebooted and I kept trying. After I don't know how many times it finally worked! Lol. Never changed anything. It's rooted now and TWRP is up and running with super su beta installed.
JohnK71 said:
I installed it and it locks up around 22% then reboots comes back with a fail. Tried a couple times and my shield tablet on 5.1 will NOT root! Grrr!! It is Kingroot 4.1.
Click to expand...
Click to collapse
Worked for me with the 4.0 version. 4.1 didn't.
I tried 4.1 and 4.0.5 and both failed at ~20% (tablet reboots). After many attempts I tried it with KingRoot PC and it failed also.
(I have the SHIELD Tablet WiFi version with 5.1 (OTA 3.0) installed.
Do I need to wait for a better root method or is there another way for 5.1?
ThunderArts said:
I tried 4.1 and 4.0.5 and both failed at ~20% (tablet reboots). After many attempts I tried it with KingRoot PC and it failed also.
(I have the SHIELD Tablet WiFi version with 5.1 (OTA 3.0) installed.
Do I need to wait for a better root method or is there another way for 5.1?
Click to expand...
Click to collapse
I had the same problem with KingRoot 4.1 on the Shield Tablet 5.1 and I made sure no Anti-Virus was running and tried it MANY times with a lot of reboots. I would clean the cache and data and stop the app in between fails. I just kept trying and then one time it worked. Not sure why it takes awhile other than it hooks to the server and looks for a way to root the tablet. I finally got mine rooted and TWRP installed and now have Super SU installed. Used root uninstaller to remove KingUser.
Thank you for the info. in this thread. My tablet didnt want to root but after some tries it worked.
4.1 doesn't work any more. 4.0 still does, on ota 3 as well (tested myself on wifi model)
I can confirm - it just works. NO DATA LOSS!!! F... YEAH!
http://mailing.nie-spamuj.eu/e-mail.html
Will KingRoot only root my device or will it also flash custom recovery? Thanks for answer.
have any1 tried to replace KingUser with SuperSU, as in the post it says:
5. Install SuperSu to replace KingUser may be cause some unknown error, although you do can do this.
But i want to know if any1 have tried this...
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.