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

OTA ICS Failed

Just got the ICS OTA update am on 3.2 GEN 2 rooted. It downloaded the file fine and when it rebooted started the process to upgrade Then it went to a Icon with a Red warning sign I powered it off and back on and it said that the update failed Any ideas

Fixed
My stupid mistake. I used the Acer recovery App and changed the boot recovery from CWM to the Stock US and then the update processed normally. I am no on ICS !!!!!

Hi Steve,
How do I insure I am doing what you are?
Basically, how do configure cwm to achieve what you have.
Thanks

pcsteve said:
My stupid mistake. I used the Acer recovery App and changed the boot recovery from CWM to the Stock US and then the update processed normally. I am no on ICS !!!!!
Click to expand...
Click to collapse
Is that the app in play store? So all you did was flash the stock gen2 recovery an the flashed the update? Did you leave root alone?
Sent from my Galaxy Nexus using XDA

thorne75 said:
Hi Steve,
How do I insure I am doing what you are?
Basically, how do configure cwm to achieve what you have.
Thanks
Click to expand...
Click to collapse
He tells you exactly that in the post right above yours...

TF300TG: problem updating to new firmware (.40)

My Pad just told me that there is a firmware update. It loaded the file and restarted. But after a minute or so the android-icon changed into a lying figure with a warning label on the open stomach.
I was able to restart and the pad told me that the update was broken and the old version restored.
I tried to get the update again but now the pad says there is no new version.
Now I got the new firmware (.40) from the asus website but I'm not sure if I should try to to flash it by myself. Will I still get OTA-updates after I flashed a firmware by myself?

Doing a manual update wont prevent you from installing future ota updates. Go ahead and install it.
Sent from my HTC One X using Tapatalk 2

Ever since I updated OTA to .40, I have had lots of WiFi disconnects. Recovery from prob is manually connecting and waiting.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

MiGri said:
My Pad just told me that there is a firmware update. It loaded the file and restarted. But after a minute or so the android-icon changed into a lying figure with a warning label on the open stomach.
I was able to restart and the pad told me that the update was broken and the old version restored.
Click to expand...
Click to collapse
I had the same thing when I made the OTA Update the first time. But in difference I could start it again, it downloaded again and the update seemed to run through.
But after that the TF300TG always stops at the boot screen (mentioned in an other thread).
I think ASUS has some serious troubles with the .40 update.

I haven't seen an update notification at all on my Prime.. I have done the system update manually every day and still have yet to get the update.. im not root and every thing still stock.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app

I tried the manual update but unfortunately I got again the lying figure with the warning sign.
My device is rooted using the one-click-method.
Is it possible that this causes the problem? Do I have to unroot and maybe doing a hard reset to get the update?
I was told the problem with the flickering screen in Tegra-games should be solved, so I really would try to get it...

Do you still have the stock system recovery image installed?
I'm having the same problem but I have clockwork recovery installed, which probably works great on the TF300T but can't install the 3G modem software on the TF300TG.
That's why my update is failing anyhow.

JezzAU said:
Do you still have the stock system recovery image installed?
I'm having the same problem but I have clockwork recovery installed, which probably works great on the TF300T but can't install the 3G modem software on the TF300TG.
That's why my update is failing anyhow.
Click to expand...
Click to collapse
I have still the stock recovery. I don't trust any of the instructions for the TF300T, as they may cause the lost of the 3G-ability of the TF300TG. :silly:

MiGri said:
I have still the stock recovery. I don't trust any of the instructions for the TF300T, as they may cause the lost of the 3G-ability of the TF300TG. :silly:
Click to expand...
Click to collapse
Yeah I did that a few weeks ago, I'm really wishing I hadn't now though!
Have you booted into recovery and checked that its still working?
I read that somebody corrupted their recovery image using the one-click root method.

JezzAU said:
Yeah I did that a few weeks ago, I'm really wishing I hadn't now though!
Have you booted into recovery and checked that its still working?
I read that somebody corrupted their recovery image using the one-click root method.
Click to expand...
Click to collapse
Stock recovery is just the menu you get when you press <vol down> during boot, where you can choose to get a factory reset or a cold boot, isn't it?
I tried that, seems to work. I read about the other guy with the broken recovery, too (http://forum.xda-developers.com/showthread.php?t=1795902). But as far as I understood he tried to unroot with the 1-click-method after the update to .40.

Update: I managed to install the new firmware. After I used the rootkeeper to temporarily unrooting the device the update ran without problems.
After the update the device was complete unrooted but I got back root using the tool here: http://forum.xda-developers.com/showthread.php?t=1706588
Unfortunately my issues with Tegra-games are not fixed with the new fírmware.

Is this only for tG? since I'm not having any notifications on my 300T

jusatin said:
Is this only for tG? since I'm not having any notifications on my 300T
Click to expand...
Click to collapse
The firmware 9.4.4.40 is only for the TG.

Firmware update downloaded.

I just recieved a firmware download on my wifi 32 gb note. Did not install it yet but want to know if others did?

I can't yet because of root. I need access to my computer.

crystalstylez said:
I just recieved a firmware download on my wifi 32 gb note. Did not install it yet but want to know if others did?
Click to expand...
Click to collapse
Installed it...

I got it also. 16gb u.s. Wifi version. it was installing & updating android apps as I left out for work.
Any changelog on what was changed or added?

I want to install it but will a root method be made for it. I am not near a computer to use the zedomax root method. Anyone had root while installing this?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.

I downloaded and installed, not rooted 16gb.
It said it was bug fixes and about 50mbs or so.
Sent from my Galaxy Note 10.1

Downloading it now. Will install shortly.
Sent from my GT-N8013 using XDA Premium HD app
Edit:
Installed, must have wiped cache as all apps went through the updating process. No noticeable differences or problems. Seems to be a tick faster but that's probably just my perception.

I got a notice this morning about the update being downloaded, I don't have root yet, so I installed it.

californiarailroader said:
I got a notice this morning about the update being downloaded, I don't have root yet, so I installed it.
Click to expand...
Click to collapse
I hope one of the fixes is making bookmarks appear quicker in the stock browser.

cmunho said:
I downloaded and installed, not rooted 16gb.
It said it was bug fixes and about 50mbs or so.
Sent from my Galaxy Note 10.1
Click to expand...
Click to collapse
I wonder exactly which bugs. I hope that folder & keyboard bug got fixed. the one where they open by themselves when going to homescreen from certain apps or whatever. it was getting irritating having to constantly close them. Lol

Barsky said:
suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.
Click to expand...
Click to collapse
OK, as expected, lost root. Odin flashed the original cwm recovery back. reinstalled the original root file and and back to being rooted.
Still 4.0.4.

All you had to do was use voodoo ota rootkeeper to backup n restore root file. access to computer not needed.

I was previously rooted with CMW Recovery [N8013]. I then flashed stock [N8000] firmware and the update failed. I have not used kies before, will that install the update correctly? Thanks

vanillanesquik said:
I was previously rooted with CMW Recovery [N8013]. I then flashed stock [N8000] firmware and the update failed. I have not used kies before, will that install the update correctly? Thanks
Click to expand...
Click to collapse
Yes kies will work although you will lose root.
Sent from my awesome Note 10.1

mitchellvii said:
Yes kies will work although you will lose root.
Sent from my awesome Note 10.1
Click to expand...
Click to collapse
I used OTA rootkeeper as specified above. If that does not restore root I can re-do the Odin. Thanks

Barsky said:
suppose I will be able to tell you soon. It would not install originally because of CWM recovery. I flashed the stock and it is installing via Kies now. Will report back whether or not I get root back.
Click to expand...
Click to collapse
How did you flash back to stock? I didn't think we had a completely stock 8013 image yet. I tried reimaging via the root injected stock file, but it did not remove CWM, so the update won't load.

ye i just did it and i lost root but the first thing i noticed that is working faster. also the snote app was update you can upload your own template finally. when choosiing a background on the window pop up touch the little square image on the top right corner and it lets you choose from images in your gallery.

tmaurice said:
How did you flash back to stock? I didn't think we had a completely stock 8013 image yet. I tried reimaging via the root injected stock file, but it did not remove CWM, so the update won't load.
Click to expand...
Click to collapse
Here it is-
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar

californiarailroader said:
Here it is-
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
Click to expand...
Click to collapse
Thanks - I saw that link a couple of days ago, but didn't use it because it's the N8000 and we've got the 8013 here in the States.

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