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

Sprint system update. I'm rooted and stock. What to do?

So I have a System Update waiting. I'm rooted and stock rom. I have titanium backup and froze various apps. I have stock recovery.
I will lose root by installing this right? Will all my apps be defrosted with this update? Should I defrost them myself before updating?
Anything else I should do before taking this update? A little nervous about it.
Thanks
Sent from my LG-LS980 using xda app-developers app

Bump bump bump
Sorry I'm home sick with the flu and want to take care of this today that I'll be home.
Sent from my LG-LS980 using xda app-developers app

I asked the same thing here: http://forum.xda-developers.com/showthread.php?t=2567071
I unrooted and tried to take the OTA, it seemed to start flashing but then rebooted and I'm still on ZV7

WhiteZero said:
I asked the same thing here: http://forum.xda-developers.com/showthread.php?t=2567071
I unrooted and tried to take the OTA, it seemed to start flashing but then rebooted and I'm still on ZV7
Click to expand...
Click to collapse
So confusing. I can't get a solid answer.
I'm even considering flashing the radio/modem to the newest one. But I'd need to install a recovery.
Sent from my LG-LS980 using xda app-developers app

o0adam0o said:
So confusing. I can't get a solid answer.
I'm even considering flashing the radio/modem to the newest one. But I'd need to install a recovery.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
If your stock and just rooted you can flash the ota if you don't have a custom recovery...or if you do have a custom recovery you can flash a stock ROM in Sprint development that has root and ota update included....also comes in odex or deodex...

So I just accepted the OTA. Everything went smoothly. Lost root but quickly rooted again. I'm a happy camper.
Sent from my LG-LS980 using xda app-developers app

I have TWRP on a stock rooted and received that update this morning, it rebooted into recovery and did nothing, and since then I'm stuck in recovery. Nothing works, flashing, recovering, every reboot sends me back into recovery.

crazyboy81 said:
I have TWRP on a stock rooted and received that update this morning, it rebooted into recovery and did nothing, and since then I'm stuck in recovery. Nothing works, flashing, recovering, every reboot sends me back into recovery.
Click to expand...
Click to collapse
i did the same damn thing this morning, phone said i had a system update when i woke up and half asleep i accepted it. tried flashing several roms i had on the phone and restoring some twrp backups but keep getting booted back into recovery. is there any hope?

Deejayadhd said:
i did the same damn thing this morning, phone said i had a system update when i woke up and half asleep i accepted it. tried flashing several roms i had on the phone and restoring some twrp backups but keep getting booted back into recovery. is there any hope?
Click to expand...
Click to collapse
Yahplenty of hope you could try the fix in the android development section and if not restore to stock in the general forum....

RubbleTea said:
Yahplenty of hope you could try the fix in the android development section and if not restore to stock in the general forum....
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2451696
This is thread.

[Q] HELP HELP HELP verizon ota butchered my phone

i was running digital dream vs1.1 for the verizon G2. i got ota update notification last night but i was too tired to deal with it. well my gf rolled over to check the time this morning and meant to use knock on and coincedently knocked on the part of the screen that said install now now. now no matter what i do it wont leave twrp. i tried wiping, reinstalling, restoring, nothing works. any ideas?

Using TWRP, go into command mode and type the command used to turn off the flag to boot into recovery. Should get you back booting on 11A.
If you screwed up and Factory Defaulted, then you'll gonna have to restore stock and update naturally before hacking.
To restore stock, you gotta download the stock TOT file and use the flasher to go back to stock, then update the OTA updates twice up till the latest 12B. RE-Root and reinstall TWRP.
Nothing else works. Not even restoring a backup. The Flasher app was pretty straight forward after downloading all of the DLL files needed to launch it.
Sent from my VS980 4G using XDA Premium 4 mobile app

[Q] Verizon Kit Kat OTA...just need to Un-Root?

Verizon keeps trying to push the OTA 4.4.2 update. I've been doing "install later" but now I'm ready to go ahead and pull the trigger on 4.4.2.
1. I am rooted
2. I do NOT have a custom bootloader (TWRP or CWM)
3. I do NOT have a custom ROM.
So, in order to OTA update do I simply have to un-root? If so, with the Full Unroot in SuperSU do the trick or do I need to go through the steps set up here to go back to stock?
Thank you in advance for any advice on the matter.

fettfan said:
Verizon keeps trying to push the OTA 4.4.2 update. I've been doing "install later" but now I'm ready to go ahead and pull the trigger on 4.4.2.
1. I am rooted
2. I do NOT have a custom bootloader (TWRP or CWM)
3. I do NOT have a custom ROM.
So, in order to OTA update do I simply have to un-root? If so, with the Full Unroot in SuperSU do the trick or do I need to go through the steps set up here to go back to stock?
Thank you in advance for any advice on the matter.
Click to expand...
Click to collapse
If you are rooted you can take ota, as long as you meet the requirements which are don't have custom recovery(twrp/philz/cwm),everything is stock, don't have xposed and have not removed bloat also to answer your question a full unroot from su should work no problem
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

Tried while rooted. The phone rebooted and the installer started, showing 0%, then threw an error (it went away before I could see it...something like 0x1111004?)
Did SuperSU Full Unroot. Rebooted. Tried install again and got the same results.
I'm going to try a full factory reset and see if it helps.

Well, crap!
So resetting the phone didn't help. I forgot that I mobile hotspot mod so I tried to back that out by installing the stock hotspot apk and odex.
Now, when I try to do a software update I get "unfortunately, software update has stopped". Tried force close and clear cache but no luck. Tried wiping phone again, no luck. Any ideas?

I have a boot issue on my Verizon G2. I'm on 11A stock, rooted and hotspot altered. I also have OTA updates blocked for months by titanium. Was going to undo wifi and unroot and factory reset to see if that helped my boot issue. But I hate to have mine error like yours since mine still functions. Gonna watch this thread and hope you get yours fixed. good luck

While trying to remove the hotspot mod i removed the mobile update apk. What a moron. Anyway, thank god i had a backup.
I'm back to square one. Can't ota update. It fails with 0x1111004. I'm going to look into disabling the daily push of the update and/or some other method of installing Kitkat.
Sent from my VS980 4G using xda app-developers app

fettfan said:
While trying to remove the hotspot mod i removed the mobile update apk. What a moron. Anyway, thank god i had a backup.
I'm back to square one. Can't ota update. It fails with 0x1111004. I'm going to look into disabling the daily push of the update and/or some other method of installing Kitkat.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Well if you are gonna use other method you can check out this thread there's a kk kdz for vs980 and ok roms that can be flashed
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

I had the same exact problem and solved it by:
http://forum.xda-developers.com/showpost.php?p=52088546&postcount=7

[Q] What? Custom Status?

I have a Samsung galaxy s4 running 4.2.2 AT&T, Recently I used triangle away and SuperSu to get rid of root and to get the official device status. I went into Odin and it said failure and I noticed that it said custom in the device status. So then I went to motorchopper how I rooted in the first place and did that and it also said "rooting... Failure" so now the questions is how do I get root access back so I can unroot it and then flash the official 4.2.2 and then get 4.4.2?

Flashing 4.2.2 in Odin will remove root. Why do you want to go to 4.4.2? You will no longer be able to use twrp or cwm if you do.
Sent from my Nexus 5 using XDA Free mobile app

Oh I didn't know that well thanks for the info, I'll stay on 4.2.2 then. Now my problem if when I goto motorchopper after it installs the SuperSu it waits and then fails. From what I read that means I'm still technically rooted but idk. Also idk if the status has anything to do with it but it still says custom instead of offical

OhDreamsNo said:
Oh I didn't know that well thanks for the info, I'll stay on 4.2.2 then. Now my problem if when I goto motorchopper after it installs the SuperSu it waits and then fails. From what I read that means I'm still technically rooted but idk. Also idk if the status has anything to do with it but it still says custom instead of offical
Click to expand...
Click to collapse
I don't know what the current status of your device is or what you're ultimately trying to achieve. But I would recommend you stay on 4.2.2, mdl, firmware and flash a 4.4.2 custom rom.
Sent from my Nexus 5 using XDA Free mobile app

Well OK here is what I want to do now, I want to re-root my 4.2.2. Thought when I use the moterchopper method it says failure right after it installs SuperSU for you. Now I'm stuck and don't really know what to do! I would love to know some way to fix this

OhDreamsNo said:
Well OK here is what I want to do now, I want to re-root my 4.2.2. Thought when I use the moterchopper method it says failure right after it installs SuperSU for you. Now I'm stuck and don't really know what to do! I would love to know some way to fix this
Click to expand...
Click to collapse
Does the device boot and can you check if you still have a custom recovery and whether you're rooted or not
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Does the device boot and can you check if you still have a custom recovery and whether you're rooted or not
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The device does boot, root checker says I have not root, and I believe I don't have a custom. Recovery b/c when I do power/down volume it bring me to download mode and power/up brings me into the regular recovery menu

OhDreamsNo said:
The device does boot, root checker says I have not root, and I believe I don't have a custom. Recovery b/c when I do power/down volume it bring me to download mode and power/up brings me into the regular recovery menu
Click to expand...
Click to collapse
I think at this point I'd flash the stock 4.2.2 firmware from sammobile.com in Odin and start over. But watch out for the device wanting to update itself after the Odin flash. If it does you'll lose the ability to use twrp or cwm. To avoid it, root with motorchopper, but on a custom recovery and flash a custom Rom. There also three files you can freeze our delay on the device that neuteres the updates. I only remember one of them, FWUpgrade
Sent from my Nexus 5 using XDA Free mobile app