Does anyone know a method of temp rooting the KF with the new update?
I have been using BurritoRoot3 to toggle it to root to make minour modifications, but don't want to have any issues with video, etc...so after installing Swype etc, I turn root back off.
I love the ability to just flip the switch until the next reboot.
Voodoo OTA Rootkeeper works well.
GBH2 said:
Voodoo OTA Rootkeeper works well.
Click to expand...
Click to collapse
Actually I don't have permanent root, and I have received the update.
I don't want to permanently root, just root temporarily when necessary.
fwp said:
Actually I don't have permanent root, and I have received the update.
I don't want to permanently root, just root temporarily when necessary.
Click to expand...
Click to collapse
Oh, I misunderstood. You need to root it and then you can temporarily unroot. I am rooted and I use OTA Rootkeeper to Temp unroot and use all of Amazon's services - free Prime instant videos, Prime members free book lending library, etc. no problems.
Excellent, thanks. That is the opposite of how I was doing things, but I think that will do the trick.
Sent from my R800a using XDA
Actually, on my Kindle Fire, rooted with Stock 6.3 root, I can temp unroot and watch Prime Videos, but I still can't see the lending library. When I click Store, it takes me to the Android Kindle browser, which doesn't show the lending library. I've looked at screenshots - and it is definitely different. I've confirmed that I've temp unrooted it, and I've even rebooted it - no avail. Any thoughts?
Solution: http://raywaldo.com/2012/01/kindle-fire-works-great/
Remove Kindle App updates from Android market.
Related
When you root your kindle fire what exactly do you "lose"?
Would it be possible to root my kindle install the market then un-root and still be able to do everything plus the market?
You don't lose anything.
Unless you move to CM7 which you would then lose Amazon Prime.
If you stay with the stock rom rooted, you can use OTA Rootkeeper to unroot temporarily to use Amazon Prime, but that is about all that might need that.
If i do this will the market still work.
1 root
2 install market
3 unroot
playmobot said:
If i do this will the market still work.
1 root
2 install market
3 unroot
Click to expand...
Click to collapse
Yes
10char
Very strange.
I rooted my KF last week using KF Utility
Added TWRP and FireFireFire
Added OTARootKeeper
protected root and selected "Temp Unroot" so I could watch Amazon Video
Today I tried to re-root with OTA Rootkeeper but noticed it wasn't re-checking the "root" box. Root Explorer confirmed it didn't have root.
Rebooted to see if that would help.. and noticed the FireFireFire logo was no longer there and it was just the default kindle fire boot animation.
Somehow I lost it all!? But I am pretty sure I was already on 6.2.1 and I renamed "OTASilentInstall.apk" to .xxx
Does the OTASilentInstall rename trick not work?
Nevermind. I see that just renaming OTASilentInstall.apk is not a proven protection against updates. I must have had 6.2.0. Oh well. I'll just re-root 6.2.1
This is something that continues to worry me. I thought OTARootkeeper was supposed to block OTA updates from Amazon. Is that not the case? I don't care about the Amazon videos. If it's not on Netflix, I probably wouldn't watch it anyway.
Sent from my Kindle Fire using xda premium
I froze otasilentinstall.Apk with titanium backup . I think I'm pretty safe from any updates.
Blkegk said:
I froze otasilentinstall.Apk with titanium backup . I think I'm pretty safe from any updates.
Click to expand...
Click to collapse
Nope, people did that and still got the update.
Sent from my Gingervolt-ed VS910 4G using xda premium
OK I did not find this easily here, so am posting as a new thread - mods please delete if appropriate.
I had a rooted Atrix running 4.5.91 for ages, no issues. In looking for how to upgrade I came across a thread with the usual complicated series of steps and a side-note about OTA RootKeeper (find in Market).
So backed up (TBPro). Installed OTA RootKeeper. Unrooted. Verifyied it had. Re-rooted, to make sure it worked!
Then Unrooted and accepted the OTA upgrade.
Updated with no issues.
Restored root with no issues. All previously superusered apps still working fine, etc.
I did not find anything describing this very simple process anywhere, so thought I'd post.
(Only casualty of the upgrade is WeatherBug Elite which seems to be unable to connect - off to investigate now as mail, internet and everything else working fine).
Doesnt work
It's rootkeer doesn't keeps rot for atrix
FalconCA said:
It's rootkeer doesn't keeps rot for atrix
Click to expand...
Click to collapse
That is not true.
I actually posted that it worked for me in one of the other rooting threads. I did a little different than OP. I didn't unroot for the update. The OTA broke my root and I restored it using the app.
Installed Voodoo. Chose to backup (protect or whatever the option was) the root. Installed OTA. Went into Voodoo and restored root. It worked without any problems. Works as long as you have root before doing the update so I'm not sure what you mean that it doesn't keep the root because it worked for me and OP. I have the ATT version in case it matters.
Worked like a charm for my phone. If you google, you can find specific instructions on the web about the process of how to do it (since the app itself gives no instructions).
Are you guys using the stock recovery with this or have an alternative flashed? I have cwm flashed on mine so I don't think the ota will work. Am I correct?
Sent from my MB860 using XDA
i have bootloader unlocked, rooted and CWM flashed.i installed voodoo OTA keeper , saved the all the root stuff with that app then did temp un-root and installed OTA, when it finished installing i just went to the app and hit re-root and it worked.. checked it with root checker
rcklss1 said:
Are you guys using the stock recovery with this or have an alternative flashed? I have cwm flashed on mine so I don't think the ota will work. Am I correct?
Sent from my MB860 using XDA
Click to expand...
Click to collapse
Should work the recovery is its on part of the flash storage on the phone so i don't believe it matters much to the phone once you get cwm on there when updating through OTAs.
broke wifi
I was rooted. Hid the root, uninstalled superuser. Did OTA. Unhid root and reinstalled superuser.
Now my wifi disconnects about every 20 minutes for a few seconds then reconnects.
Can't find a fix.
Atrix 4G Unrootable after OTA Rootkeeper
OK, technicially it is still rooted, but it loses Shell Root. OTA Keeper. After I re-root or restore root with OTA Rootkeeper, all the check marks are checked off in the Status of Voodoo OTA RootKeer EXCEPT Root permission granted. Superuser app installed, Device roote, Filesyste supports root protection and Protecte su copy available are all checked, but the device does not allow permission to important apps I need and are the main reasons I root my phone. I couldn't care less about ROMs and fancy cosmetics. I need functionaity that this OTA Rootkeeper has cost me. I have tried reflashing, restoring to factory settings everything, and I still can't fully root my phone. superoneclick hangs at step #7, manual root gets an error message "device full" all because this OTA rootkeeper app has completely locked out other root methods and has an incomplete re-root method.
and that is the truth.
My Atrix was rooted using SuperOneClick. I have system version 4.5.91, Android version 2.3.4. Bootloader not unlocked. No CWM or any special ROMS installed.
I've been getting the constant nagging of the 2.3.6 update, but I don't want to lose root. I have ota rootkeeper app, and it looks like the instructions from the OP are simple enough.
My question is, is my situation similar enough to the OP's so I can go ahead with the update? I rooted my phone mainly to use Barnacle Wifi Tether, so definitely want to keep using that after the update.
Has anyone been successful in update their Nexus 7 device with the following configuration:
1. Stock ROM
2. Rooted
3. SuperSU v0.98 (recently updated)
4. Voodoo RootKeeper
5. DPI set to 160, need confirmation but assuming this needs to be reverted back to 213
I have been viewing other posts of successful upgrades but with prior versions of SuperSU, so I was hoping i could find that one person who has the above configuration and was successful in updating.
Thanks,
JBIRD
Apart from 4, the Rootkeeper, that was my setup when I updated from 4.1.2 via the 4.2 OTA (adb sideload).
Worked fine.
Re-rooted using superboot and am happycat ever since.
SuperSU (updated) kills multiuser on my 4.2.
Even setting up a new user took over 15 minutes.
I kept getting SU requests from the new user for /system/bin/id. Why id was calling SU I have no idea - but it is a killer.
I was not able to recover until I used Voodoo RootKeeper to temporarily unroot. That fixed it. Multiuser performance is great now.
I will not use SuperSU again until a full fix is released. Really don't need root anyway until stickmount is fixed.
rmm200 said:
SuperSU (updated) kills multiuser on my 4.2.
Even setting up a new user took over 15 minutes.
I kept getting SU requests from the new user for /system/bin/id. Why id was calling SU I have no idea - but it is a killer.
I was not able to recover until I used Voodoo RootKeeper to temporarily unroot. That fixed it. Multiuser performance is great now.
I will not use SuperSU again until a full fix is released. Really don't need root anyway until stickmount is fixed.
Click to expand...
Click to collapse
Thanks for the information. So do you recommend removing superSU and root from the device prior to upgrading?
jbird92113 said:
Thanks for the information. So do you recommend removing superSU and root from the device prior to upgrading?
Click to expand...
Click to collapse
No - keep SuperSU and RootKeeper.
As always - use RootKeeper to temporarily unroot before the upgrade.
After the upgrade, just wait for Chainfire to release an update before restoring root.
Actually - SuperSU seemed to work fine until I tried adding a second user. Only the multi user scenario gave me trouble.
rmm200 said:
No - keep SuperSU and RootKeeper.
As always - use RootKeeper to temporarily unroot before the upgrade.
After the upgrade, just wait for Chainfire to release an update before restoring root.
Actually - SuperSU seemed to work fine until I tried adding a second user. Only the multi user scenario gave me trouble.
Click to expand...
Click to collapse
Thanks again. Sorry for the newbie questions but to confirm, I choose Temp. Un-root button in rootkeeper prior to the upgrade then run the OTA update?
jbird92113 said:
Thanks again. Sorry for the newbie questions but to confirm, I choose Temp. Un-root button in rootkeeper prior to the upgrade then run the OTA update?
Click to expand...
Click to collapse
Yes!
rmm200 said:
Yes!
Click to expand...
Click to collapse
One last thing, I changed my DPI settings to 160, do I need to revert to back to 213...
I am not the right person to answer - but if buildprops is anything other than stock the update will fail. Think install checks the checksum.
Sent from my Nexus 7 using xda app-developers app
rmm200 said:
I am not the right person to answer - but if buildprops is anything other than stock the update will fail. Think install checks the checksum.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you recommend to be on the safe side that I disable supersu as well prior to the upgrade?
Thanks again...
Really bad things happen if you disable Supersu and someone calls su. Leave it enabled and temporarily unroot.
Sent from my Nexus 7 using xda app-developers app
Oh, you didn't mention you were on Safestrap. That may bring up some additional issues. And you do need to revert your build.prop to the original. With any luck, you have a build.prop.bak that you can restore. SuperSU hasn't caused me any problems, but I don't use multi-user.
rmm200 said:
Really bad things happen if you disable Supersu and someone calls su. Leave it enabled and temporarily unroot.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Will follow your directions. I do have other apps that require root, once I update can I use the rootkeeper to re-enable root?
Thanks again for all your help..
jbird92113 said:
Will follow your directions. I do have other apps that require root, once I update can I use the rootkeeper to re-enable root?
Click to expand...
Click to collapse
If it was me - I would not have root enabled while on a secondary user.
I am sure SuperSU will be fixed in short order.
If you use MSkips Nexus 7 Toolkit and use option 8 it will not only unlock the boot loader, but root, install busy box, your choice of either cwm or twrp, recommends using the 3.34 bootloader, and recommends using SuperSu 0.98 due to problems with superuser not being updated yet. I can attest to the fact that the 4.13 bootloader causes root issues. At least on my 7. Apparently that isn't so on all 7s.
Sent from my Nexus 7 using xda premium
rmm200 said:
If it was me - I would not have root enabled while on a secondary user.
I am sure SuperSU will be fixed in short order.
Click to expand...
Click to collapse
I am not going to use the multiuser feature as I am the only one who uses the tablet. Will rerooting work on the primary user?
Seems to work fine.
Sent from my Nexus 7 using xda app-developers app
So if I try to update to 4.2 AFTER updating supersu to v0.98 it will fail for sure? Still waiting for stickmount *fingers crossed* and Google to fix Bluetooth before I even attempt 4.2 anyway. Would uninstalling updates for supersu through app info/settings work? Tia
Sent from my Nexus 7 using xda premium
Gigabitex2 said:
So if I try to update to 4.2 AFTER updating supersu to v0.98 it will fail for sure? Still waiting for stickmount *fingers crossed* and Google to fix Bluetooth before I even attempt 4.2 anyway. Would uninstalling updates for supersu through app info/settings work? Tia
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Only problems I have seen are trying to set up / use a second user while rooted.
Stay away from multi-user and you should be fine.
Note - problems I have reported with SuperSU may just be related to multiuser and root, no matter how you get root.
I have not tried the "superuser" app, so I have no idea if the problems will be the same.
Hi,
I'm rooted running stock.
My bank's app requires that the phone will be unrooted (it won't let me sign in). Is there a way to make the app think that I don't have root access, or is there a way to temporary unroot my phone, for when I'm using the app?
I've tried to disable the root from SuperSU, to use RootKeeper OTA, and this thread instructions, and some more market apps, but none of these worked. Even titanium backup didn't believe me that I'm not-rooted
Can you guys help me out?
Thanks
Alkonost said:
Hi,
I'm rooted running stock.
My bank's app requires that the phone will be unrooted (it won't let me sign in). Is there a way to make the app think that I don't have root access, or is there a way to temporary unroot my phone, for when I'm using the app?
I've tried to disable the root from SuperSU, to use RootKeeper OTA, and this thread instructions, and some more market apps, but none of these worked. Even titanium backup didn't believe me that I'm not-rooted
Can you guys help me out?
Thanks
Click to expand...
Click to collapse
Most apps just look if you have a superuser.apk in /system/app/. Try to put "com." at the beginning of the name. So you don't have "superuser.apk" but "com.superuser.apk". I already done this and i have root and the app thinks im unrooted.
Thanks a lot! This + Rootkeeper made the app think I'm not rooted
Sent from my Nexus 4 using xda app-developers app