Database Users

Help new update wont install

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

[Q] A500 can not upgrade to 3.2 via OTA

my A500 has been rooted, but can not upgrapde to 3.2 via OTA everytime it reboot.
Help pls
thx

Yea, i'm also unable to receive the 3.2 OTA. I'm not rooted however, so I dont think thats the problem. Sometime it will finish the download but then say the file is corrupted and starts back at square one....
Sent from my A500 using xda premium

To the OP, you basically have to unroot it to update via to OTA file. Specifically, you cannot update with the OTA file using the non-stock Recovery system.
Ashy: Are you downloading it over wifi or 3g? If 3g, try downloading it via wifi...

I'm also having issues updating. I get past the download, the reboot to recovery, but the install fails with the bee/exclamation screen.
I've read recently to put the tablet in portrait orientation when installing and will try that tonight.
I remember that worked in the past for me.
Sent from my GT-I9100M using Tapatalk

Groaner, are you rooted? And if so, did you install the stock recovery back on it before trying to update?

Yes. I've tried every version of.com roms but none of them let me. I have not tried the.07 one so maybes that will be next.
Portrait orientation did not help unfortunatly.
I'm currently trying Taboonay 2.1 first.
Sent from my GT-I9100M using Tapatalk

I don't think it was really the ROM being used that matter, but that you should have the stock/factory recovery installed. I had to completely unroot my device before I could update from the OTA download.

LindtSH said:
my A500 has been rooted, but can not upgrapde to 3.2 via OTA everytime it reboot.
Help pls
thx
Click to expand...
Click to collapse
If you are rooted anyway, I wouldn't suggest the OTA update. You will lose root and if you need it then this isn't the best way to do it. What you should do is install the acer recovery from the market, use that to install CWM (if you don't have it already) and then download the ZIP of an already rooted 3.2 and install that.

Updated OTA - Now my tab seems broken

Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.

GaresTaylan said:
Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
Click to expand...
Click to collapse
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Things I have tried:
*MD5 Post-update*
*Wipe Data/Cache via stock recovery*
*Re-flash MD5*
I am now in the process of locating a UEALGB recovery/kernel. If any member has a link to it or can help its certainly appreciated.

vanillanesquik said:
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Click to expand...
Click to collapse
Are you just having OTA update issues or is your screen not responding properly to touch as well?

GaresTaylan said:
Are you just having OTA update issues or is your screen not responding properly to touch as well?
Click to expand...
Click to collapse
No touch, no pen input. Its worst-case.

vanillanesquik said:
No touch, no pen input. Its worst-case.
Click to expand...
Click to collapse
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.

GaresTaylan said:
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
Click to expand...
Click to collapse
The update restored touch function but the pen functions are completely derped.
A pre-rooted full package is being uploaded by entropy in the next 2 hours so I am crossing my fingers that this will fix it.

I have the same issues I\m trying all things to get it to work just like you are to no avail, Samsung update now things are all screwed up

Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS

vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
top link is dead, btw i lost touch functions LOL
anyway i will fix it

I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2

I had the same issue and flashed this via Odin: http://forum.xda-developers.com/showthread.php?t=1847706
Fixed it and now i'm running the latest update.

I lost touch and pen and now i have them back. Heres how:
1. IM AWESOME!
2. Rebooted my computer.
3. Wiped everything.
4. ODIN root injected original firmware.
5. Kies update.
6. ODIN Clockwork Recovery
7. Flash Superuser.
Boom, everything works.
** DISCLAIMER - There is a strong possibility this worked only due to #1. YMMV.
Sent from my GT-N8013 using Tapatalk 2

-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk

BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
I took the OTA via Kies because it was listed in the OTA update thread that it was ok to do so? And that root was working fine afterward?

BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
Because we are dangerous, exciting and chicks dig us.
Sent from my GT-N8013 using Tapatalk 2

-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
The root method 2 specified that OTA was viable with stock recovery. I flashed stock recovery and the OTA failed. We were then forced to update via KIES and touch/pen functions were then bugged. The best way is my method above.

vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
I tried this method and when my note boots up s note keeps crashing every 15 seconds or so without my even opening it.

BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
In many cases, if you ONLY have added su and Superuser.apk - you can safely apply an OTA. However if you've touched anything else in /system - boom

Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.

mi7chy said:
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
Click to expand...
Click to collapse
OK so o tried vanillas order and kies froze or disconnect me or something so I odined the md5 tar of the new update and back to no touch screen but like 5 mins so I shut it off and resume later.
What is the best thing to do to get all fixed up?
Sent from a Baked Black Jelly Belly

Stability updates

Received this update, doesn't look like anything major
Sent from my SM-P900 using XDA Premium HD app

Downloading mine as we speak.

Rolling out in the Netherlands as well. For now no significant changes. Like to see a full changelog..
New:
PDA: P900XXUANC4
CSC: P900OXAANB6
MODEM: P900XXUANC4

Downloading in on a US purchased WiFi model right now.
Sent from my SM-P900 using Tapatalk

"Your device has been modified, software updates are not available."

Tried the Cellular South version on Sammobile. Full wipe and install via Odin 3.09. Seems snappier to me. Reinstalled all my apps. Leaving it unrooted for now.
Sent from my SM-P900 using Tapatalk

Applied update today.
Two things I notice:
1. Viewing large images in stock gallery now much speedier. Before, there was a long delay drawing large images.
2. Suddenly X-plore my preferred file manager has write access on SD card! Before this update it didn't. Haven't really looked fully if other apps have write access that didn't before. Hancom office updated also but it still can only write to a specific location on SD. Maybe X-plore was just a fluke either way? I'm not sure, but happy it works now.

I just notice the update and I just want to know what it will change for better since the device already good enough for me.
Sent from my SM-P900 using Tapatalk

Update in the Netherlands caused much faster WiFi connection. It was extremely slow before while doing a test with the speedtest.net app. The whole device feels speedier and snappier now. For me a big improvement. I hope more will follow, because the speed experience on this very expensive device is a bit disappointing to me.

Lost Root
I took this update and lost root. I tried CF Autoroot and it failed, my tablet would not boot up. I had to flash stock image. I suggest if you don't want to lose root, wait awhile before taking this update. By the way, SU survival didn't work.

Russbad said:
I took this update and lost root. I tried CF Autoroot and it failed, my tablet would not boot up. I had to flash stock image. I suggest if you don't want to lose root, wait awhile before taking this update. By the way, SU survival didn't work.
Click to expand...
Click to collapse
I flashed the update in odin, lost root, flashed cf auto root again and regained root, everything working great and fully rooted on the latest firmware.
Sent from my SPH-L720 using Tapatalk

hendav said:
I flashed the update in odin, lost root, flashed cf auto root again and regained root, everything working great and fully rooted on the latest firmware.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Would you please let me know your build Number? I did so much flashing today I don't even know if I got the latest build now.

Russbad said:
I took this update and lost root. I tried CF Autoroot and it failed, my tablet would not boot up. I had to flash stock image. I suggest if you don't want to lose root, wait awhile before taking this update. By the way, SU survival didn't work.
Click to expand...
Click to collapse
you won't lose root. You just have to reinstall SuperSU and everything will be fine. I lost root after updating to the new firmware, however after rebooting I reinstalled the SuperSU and I Have root again.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.

I am now rooted on build P900UEU1ANC5 from Cellular South firmware I got from Sammobile. No noticible changes and no problems so far.

Russbad said:
I am now rooted on build P900UEU1ANC5 from Cellular South firmware I got from Sammobile. No noticible changes and no problems so far.
Click to expand...
Click to collapse
Yup, Thats the latest firmware update that was most recently rolled out for the P900 series. ( P900UEU1ANC5 )
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.

Russbad said:
I took this update and lost root. I tried CF Autoroot and it failed, my tablet would not boot up. I had to flash stock image. I suggest if you don't want to lose root, wait awhile before taking this update. By the way, SU survival didn't work.
Click to expand...
Click to collapse
same happened to me. reinstalling supersu didn't work. I tried rerooting with cfautoroot and it hangs on cach.img then my screen goes striped red and freezes. couldn't even boot, had to re flash recovery to boot.
shouldn't have updated.

madjinx said:
same happened to me. reinstalling supersu didn't work. I tried rerooting with cfautoroot and it hangs on cach.img then my screen goes striped red and freezes. couldn't even boot, had to re flash recovery to boot.
shouldn't have updated.
Click to expand...
Click to collapse
1. Reflash root with Odin.
2. Reboot.
3. Reinstall SuperSU.
4. Enjoy root privilages.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.

Android.Ninja said:
1. Reflash root with Odin.
2. Reboot.
3. Reinstall SuperSU.
4. Enjoy root privilages.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.
Click to expand...
Click to collapse
there a root to flash other than cfautoroot? that's the only one I've seen.

madjinx said:
there a root to flash other than cfautoroot? that's the only one I've seen.
Click to expand...
Click to collapse
cfautoroot is the only one that I'm aware of to flash, that's working anyways. I've seen other work in another forum however it hasn't been fully successful.

Android.Ninja said:
cfautoroot is the only one that I'm aware of to flash, that's working anyways. I've seen other work in another forum however it hasn't been fully successful.
Click to expand...
Click to collapse
as I said in my other post, cfautoroot isnt working for me.

[q] should not have rooted help please

So recently I rooted my S4 with Kingo and went fine. After a few weeks, I decided to uproot to get the Lollipop OTA. Unrooted through SuperSU app then factory reset. Finished OTA download with no issueand then it failed after two attempts, saying error and I should try using Kies.
That's strange I thought. Then after looking through the phone again, I discovered GSam Root companion is now a system app that can't be uninstalled. Other than re rooting and re uprooting or flashing stock firmware, is there another option. My computer is currently under repair for a broken LCD, so any fix that doesn't need that would help. Thanks!

Not much you can do without a pc

theDman68 said:
Not much you can do without a pc
Click to expand...
Click to collapse
So I guess bring it in to Samsung to flash stock firmware?

AB__CD said:
So I guess bring it in to Samsung to flash stock firmware?
Click to expand...
Click to collapse
Is your phone working or isn't it working? I can't figure it out based on your posts.

Lennyz1988 said:
Is your phone working or isn't it working? I can't figure it out based on your posts.
Click to expand...
Click to collapse
It is working just with an annoying "system" app and can't upgrade. May have over exaggerated a bit...

AB__CD said:
It is working just with an annoying "system" app and can't upgrade. May have over exaggerated a bit...
Click to expand...
Click to collapse
I then assume that you still run an old version of kitkat (because of the kingo root).
Why not reroot and delete the file? I think you can still use Towelroot because I think you are on an old version. That's an app that you need to install.
Do you have a custom recovery? And did you factory reset before trying to update ota?

Lennyz1988 said:
I then assume that you still run an old version of kitkat (because of the kingo root).
Why not reroot and delete the file? I think you can still use Towelroot because I think you are on an old version. That's an app that you need to install.
Do you have a custom recovery? And did you factory reset before trying to update ota?
Click to expand...
Click to collapse
Can't use towelroot and don't have a custom recovery. I'll re root once I get the update on Kies(borrowed a friend's laptop) , which currently isn't available yet.

AB__CD said:
Can't use towelroot and don't have a custom recovery. I'll re root once I get the update on Kies(borrowed a friend's laptop) , which currently isn't available yet.
Click to expand...
Click to collapse
What i don't understand is why you are so stuck on getting this OTA update... just borrow your friends laptop, and flash the Lollipop that you want through ODIN. Then factory reset, DONE...

theDman68 said:
What i don't understand is why you are so stuck on getting this OTA update... just borrow your friends laptop, and flash the Lollipop that you want through ODIN. Then factory reset, DONE...
Click to expand...
Click to collapse
Took it to Samsung and let them do that for me. Didn't lose any data either, and GSam Root let me Uninstall it afterward, which was something I didn't expect. Anyway, thanks for the effort guys!