Related
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Fixed!!!!! I used Brks Asus transformer rootkit script to root which installs an insecure bootimage to work and this is what caused the problem, I just plugged my trandormer in and restored my original files then the update went on fine first try!!!! Thanks for the help!!!!
Did you install Clemsyn/Blades OC kernel? More than likely this is causing your problem.......
I'm getting the same error. Running 3.2 stock but rooted, no modified kernel. Only thing I modified was the Netflix patch which doesn't seem like it's needed now. Is there a flash able zip for this new update?
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
magicdave26 said:
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
I rooted using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1125714
oilerseberle14 said:
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
---
Sent from my Asus Transformer using Tapatalk
Taomyn said:
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
Click to expand...
Click to collapse
You only get it offered the once. Your device is then marked as updated at Asus end. If it didn't work because you were rooted, then tough...
cavsoldier19d said:
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
Click to expand...
Click to collapse
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
I always look at the updater script in the package before I update. This script contains a bunch of asserts that check the integrity of certain files before it will apply the update. If you can get the update package just open " \META-INF\com\google\android\updater-script" with notepad and that will show everything that's happening when the update occurs including the file asserts it makes. If you've modified these files then it will not update. 8.6.5.6 initially didn't work for me but by checking the script I found the problem was my srs_processing.cfg file because I tried to fix my speaker balance and this was a file that the script asserted. After restoring the original file I was able to update with stock recovery even though I had modified other system files. As long as the specific files the update checks are ok the update will proceed.
aSIMULAtor said:
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
Click to expand...
Click to collapse
You need to UnRoot it, I don't think factory reset makes any difference to rooting
http://forum.xda-developers.com/showthread.php?t=1198303
magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
The above post about altering certain files appears it might have something to do with it. I rooted using this method... http://forum.xda-developers.com/showthread.php?t=1198303
But it was V2 when i used it. It is now currently V4.
You can re-download the update if you clear your DMClient cache.
Follow the instructions in this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
I had the error with the Android + exclamation mark so I unrooted (reflashed both the stock ROM AND the stock recovery - to get rid of clockworkmod) then cleared the DMClient cache and was I able to update OTA.
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
DT39 said:
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
Click to expand...
Click to collapse
Good point. I did not have clockwork mod recovery installed. Had stock recovery, stock ROM rooted.
Sent from my Inspire 4G using XDA App
I used brk's rootkit script and just restored the original bootimage and it installed perfect let me know if it worked for you guys as well
Sent from my Transformer TF101 using XDA Premium App
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Hizpanick said:
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Click to expand...
Click to collapse
Same thing happened to me. Tried all the above, and can't get the update to come back.
Have any of you changed original system files whilst rooted? That's why it was failing for me. I managed to get the update again but it failed. I got it once more after it rebooted but took a copy first, unrooting made no difference. Unlike the downloadable firmwares from the ftp site which I checked out, the update script checks the integrity of a ton of files mainly the system apps that cannot be changed without root. If any have changed the script aborts.
Unfortunately even though I had backed up all of them with Titanium Backup, it wouldn't restore them and TB just hung. I tried all its options but nothing helped - a little worrying.
In the end I copied off the TB backup directory to a USB stick and used the NVflash recovery to restore back to factory. I then performed the upgrade again to both the tablet and dock without issues. Four hours later I have it almost back to where I want it.
Hope this helps some of you, even though it's not the best process, but the update imho is worth it
---
Sent from my Asus Transformer using Tapatalk
Hi if we freeze the OTA Silent Install will it stop the ora did anyone try?
Sent from my Kindle Fire using xda premium
Proven to not work
krelvinaz said:
Proven to not work
Click to expand...
Click to collapse
How can it not work if it freezes or if we remove the file?
Sent from my Kindle Fire using xda premium
You can remove the file, change the file, Freeze it, remove it's permissions whatever you want, but it will NOT stop an OTA update because the process that does the update creates a new one when it it needs it.
Proven Fail!
ref:
http://forum.xda-developers.com/showthread.php?t=1401073
samomamo said:
How can it not work if it freezes or if we remove the file?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Because that app is only a tool used by the app in charge of the whole upgrade process and it appears to get reinstalled from scratch during that process if it has been moved or removed
Thank you guy's for the info.
Sent from my Kindle Fire using xda premium
What if we are not registered to Amazons account? Becouse wen I wanted to get the ota I registered ans clicked on sync to get the ota. Maybe the registration has something to do with it?
Sent from my Kindle Fire using xda premium
just root ur phone and install cm7 or try droid wall that may block it but we dont have a update to check
I bought mine when it was on 6.0.0 and installed Root Uninstaller, backed up otasilentupdate.apk and then deleted it. After that no more updates. I guess experience varies, just sharing my ways. (btw i didn't register cuz im not in the US).
because u didnt register is why u didnt get the update
We have found out that when ur registered and u try to freeze the the silent update or rename it, it still updates no matter what. I hear droid wall stops the update but not sure
samomamo said:
What if we are not registered to Amazons account? Becouse wen I wanted to get the ota I registered ans clicked on sync to get the ota. Maybe the registration has something to do with it?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Probably. I had de-registered my Kindle prior to the 6.2.1 update and I did not get the update, even though it was out for a few days and my wifi was on / tablet was being extensively used during those days.
I did get the 6.2 update before I de-registered. So almost certainly, the de-registration helped.
here is my experience:
kf was and is registered
removed /system/etc/security/otacerts.zip -> update downloaded but did not install -> was automatically deleted from cache folder after failed attempt to install
installed "nfx-update-kindle-6.2.1" -> http://forum.xda-developers.com/showthread.php?t=1407852
6.2.1 is much more responsive than older version
b.t.w. root method for 6.2.1 is available:
http://forum.xda-developers.com/showthread.php?t=1399889
It seems to me that when an individual registers amazon uses that mac address for sending the update.... I could be wrong so please do not think that I am saying this is entirely true but, if all of these methods are confirmed as not working such as freexzing,removing apps, etc... then there has to be somesort of way that amazon is still able to update to your fire...
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.
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