Database Users

OTA fail help

Hello all
Have searched this forum, but im not really sure what to do.
I've used titanium backup to perm remove a few stock apps, the exchange stock app and amazon app
Now i can't recive any updates OTA, and i get this message..:
assert failed: apply_patch_check("/system/app/Stock.apk"....
E:Error in /sdcard/download/OTA_Ace_HTC_WWE_172_405_3_r2_1_32_405_6_release_1632939lowfu0y78jktpp2.zip
(status 7)
using 2.2 android version number 1.32.405.6
please help
//Cham

You can't accept OTA updates when you are rooted.

I see, but only used temp root with visionary
is that going to affect something?

Or what are my options to get a hold of updates in the future, a costum rom instead? I do kinda like the stock rom, just without stock apps

anyone?

Once again, if you are rooted, it doesnt matter how, you CANNOT accept ota update.
If you deleted something you shouldnt have, then restore the backup to that, or do a factory reset and re-root.

Ok i just figures since it was TEMProot that it didn't matter. Tnx for the reply, tried the factory default option (no luck), is there any place where I can get the Stock firmware to re-flash the phone?
Or would anyone in here recommend another rom ? Tons of custom roms, as I can tell.

Thread moved in Desire HD General.

go here and youll find your rom that you need,
you need the ones that are "RUU_Ace_HTC_WWE" in the file name, as these are what we call World Wide Editions

Thank you very much.
Just to make sure I do not **** something up, what are the steps i should follow, to install the rom?

This is what I did: http://forum.xda-developers.com/showthread.php?t=888109

Got the same problem -- some time ago I removed some "useless" apps from my /system/app folder, and when 1.72 update was released I wasn't able to install it in any way (I was trying to follow this guide). I restored the missing apps, and then everything went fine using the guide mentioned above!
Hope this helps.
sitlet said:
You can't accept OTA updates when you are rooted.
Click to expand...
Click to collapse
Sorry but that ain't correct... You *can* update your phone if you're rooted, the main problem is that root will be gone after update. The best solution is to *always* reject OTA updates provided by HTC and wait until devs here have found a safe way to update your device without losing root privileges.

Thank you
Thank you all, it gave perfectly sense since I'm quite happy with the stock firmware, i'll stick with this. The root is not so necessary for me at least for now
I'm glad it was corrected that visionary did not remove the ability for OTA, that was also what I've read before used it.

Updating to 4.1.2 Whilst Keeping Root (With a Slight Twist)

Hey guys,
I'm hoping this should be a relatively simple question for you to answer. I rooted my Nexus 7 using Wug's Toolkit (on 4.1.1) quite some time ago and received an OTA notification just the other day for 4.1.2. Without thinking, I allowed it to download and let it reboot to install. That was when it booted into Clockwork and there was a signature verification fail. It gave me the option to disable it, but remembering now that I was rooted, I cancelled the update as I figured an OTA wasn't the most sensible thing to do without checking first. My device rebooted fine and is still running 4.1.1 with full root.
After doing some research, I see now that if I use an app like OTA Runkeeper, I can safely run the OTA (or just run it, lose root and then root again).
The problem is that the OTA won't come up anymore. I've tried manually checking for updates a few times but it thinks my device is up to date. What would you suggest I do?
Is there somewhere I can manually download the update and install via Clockwork etc?
Any assistance would be much appreciated!

jazacoop said:
Hey guys,
I'm hoping this should be a relatively simple question for you to answer. I rooted my Nexus 7 using Wug's Toolkit (on 4.1.1) quite some time ago and received an OTA notification just the other day for 4.1.2. Without thinking, I allowed it to download and let it reboot to install. That was when it booted into Clockwork and there was a signature verification fail. It gave me the option to disable it, but remembering now that I was rooted, I cancelled the update as I figured an OTA wasn't the most sensible thing to do without checking first. My device rebooted fine and is still running 4.1.1 with full root.
After doing some research, I see now that if I use an app like OTA Runkeeper, I can safely run the OTA (or just run it, lose root and then root again).
The problem is that the OTA won't come up anymore. I've tried manually checking for updates a few times but it thinks my device is up to date. What would you suggest I do?
Is there somewhere I can manually download the update and install via Clockwork etc?
Any assistance would be much appreciated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1764794

wbbigdave said:
http://forum.xda-developers.com/showthread.php?t=1764794
Click to expand...
Click to collapse
I saw that, but it was posted back in July, and seemed smaller than the original OTA.
Nevermind... I didn't see the October update to the post further down.
Cheers!

[Q] Will rooted device get future update from Google?

Hi all,
Just got a Nexus 7. Say if I root my device with the Toolkit, will it be able to get future updates when Google releases them? And if it's posible, will a update from Google remove the root hack?

stan2 said:
Hi all,
Just got a Nexus 7. Say if I root my device with the Toolkit, will it be able to get future updates when Google releases them? And if it's posible, will a update from Google remove the root hack?
Click to expand...
Click to collapse
You'll always be able to update. It's more a matter of whether or not you'll need to undo some of the changes you made. Changes that cause OTA updates to fail include: custom kernels, modified system apks, etc. It really depends on what the OTA update is patching.
If the only change is adding root, you'll most likely be able to install OTA updates, but will need to re-flash supersu or fix the permissions on the su binary manually.
Sent from my Nexus 4

comminus said:
You'll always be able to update. It's more a matter of whether or not you'll need to undo some of the changes you made. Changes that cause OTA updates to fail include: custom kernels, modified system apks, etc. It really depends on what the OTA update is patching.
If the only change is adding root, you'll most likely be able to install OTA updates, but will need to re-flash supersu or fix the permissions on the su binary manually.
Sent from my Nexus 4
Click to expand...
Click to collapse
Thanks for your reply.
So re-rooting is needed after an update? Sry, I'm still new with all the superuser lingos atm =D

stan2 said:
Thanks for your reply.
So re-rooting is needed after an update? Sry, I'm still new with all the superuser lingos atm =D
Click to expand...
Click to collapse
It's a bit of a misnomer that the device will need to be re-rooted. I say this because the su binary does not get removed, rather the owner and permissions for /system/bin and /system/xbin are set by OTA updates. This leads to a lot of talk about "losing root" after updating.
Technically all that needs to be done is to have the owner and permissions reset on the su binary. Most people find it easier to just re-install the SuperSU apk rather than modify the file permissions.
Pro-tip:
The ownership and permissions should be as follows:
owner: root, group: root (uid:0, gid:0)
permissions: 06755

YES. Mine was rooted on the first day I got it back in September and its been updated twice since then.
Sent from my Nexus 7 using xda app-developers app

You can always use OTA RootKeeper its the tool I always use when updating and has never failed
Sent from my SIII in a Galaxy Far Far Away

*GalaxyDev* said:
You can always use OTA RootKeeper its the tool I always use when updating and has never failed
Sent from my SIII in a Galaxy Far Far Away
Click to expand...
Click to collapse
Absolutely agree that OTA RootKeeper is a must have for OTA updating. Makes it totally painless to reestablish root.

Thanks everyone for replying, super useful! I got my device rooted =)

Rooted or not, if you delete any system apps you may have issues with getting updates.

[Q] How Do I Prevent OTA 4.3 Update

So my Nexus 7 has downloaded the OTA firmware before I realized that Google was doing a roll-out. The Nexus 7 want me to reboot and do the FW upgrade but I don't want to upgrade the tablet. There does not appear to be a easy way to retain Root, and i'm not interested in teh steps for CFW, etc so it easier for me to stay on v4.2.x. Is there a way to prevent the upgrade? can I delete the downloaded OTA update or something? What is the path to the OTA update files? I would like to know before rebooting as I'm not sure if rebooting will just force the update. I have rooted the tablet but no other hacks such as unlocked boot loader have been performed on the device. I did a web search but did not see a in dept conversation on how to refuse the update once it has been downloaded onto the device

You could try a root keeper app that will retain root after the update. As for preventing the update, I'm not sure how that would work. Should be easy enough to keep root though.
Sent from my Nexus 7 using Tapatalk 4 Beta

A RootKeeper does not work with 4.3 due to the way that secuirity is implemented in the new FW. This has been noted in the description of the RootKeeper app on the Play store

The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.

Sound Anarchist said:
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Click to expand...
Click to collapse
I checked the cache folder using es explorer and it showed no data files(zip) in that folder. maybe the file was not downloaded yet or was already applied and the device is just waiting for a reboot to consummate the upgrade

Or you could just flash CleanROM and have 4.3 and root.
Sent from my NookColor using xda app-developers app

u could take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1998378

Thanks for all of the input. I resolved this issue. I just enabled root in es explorer which showed the hidden OTA zip file in the Cache folder. I renamed the file, but the OS deleted it after the rename so I could not even save a copy of the file. I have since rebooted and the OTA did not re-download (which is a good thing) although I still get an icon in notification indicating that the OTA is ready to install.
I'm just not interested in updating to the latest 4.3 build due to lack of time. I have many Android devices and spending the time to Root and or unlock the boot loader on each device is just taking to much of my time. So I'll just stay on the current build until I have time to tinker again. Thanks again everyone for your input

I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.

downwiththebanksters said:
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
Click to expand...
Click to collapse
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.

timnik said:
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
Click to expand...
Click to collapse
I wish I had seem this warning earlier too. I blindly accepted the OTA update yesterday thinking "Oh hey Android 4.3! Awesome!" and now I'm running in a whole load of problems and glitchs. I'm also not rooted yet which makes another problem because I can't find anything to root 4.3 yet. Also can't find anything on how to restore back to stock Android 4.2.2. Does anyone know anything about this? Will factory reset do the trick? I have all my stuff backed up.

verizon note 4 5.1.1 root "very unstable"

Last night I was bored and tried kingroot again on 5.1.1. It had been a while since I had tried, and it always said they were looking for a method. This time, it rooted successfully, but made the system very unstable. It caused Lag, and the keyboard stopped functioning, but root checker confirmed root. Temp root of course.

Reminon said:
Last night I was bored and tried kingroot again on 5.1.1. It had been a while since I had tried, and it always said they were looking for a method. This time, it rooted successfully, but made the system very unstable. It caused Lag, and the keyboard stopped functioning, but root checker confirmed root. Temp root of course.
Click to expand...
Click to collapse
I stopped messing with KingRoot some time ago, just didn't seem worth my time considering you lose root after a reboot. Especially when certain apps require a reboot to take effect, such as Adaway, Xpose, and several others. I'm more-or-less fine without root, but that doesn't mean I wouldn't root my phone if I were to come across a stable and perm root solution.:cyclops::fingers-crossed:

will4958 said:
I stopped messing with KingRoot some time ago, just didn't seem worth my time considering you lose root after a reboot. Especially when certain apps require a reboot to take effect, such as Adaway, Xpose, and several others. I'm more-or-less fine without root, but that doesn't mean I wouldn't root my phone if I were to come across a stable and perm root solution.:cyclops::fingers-crossed:
Click to expand...
Click to collapse
I was on KK, and a friend of mine updated to 5.0.1. I said screw it and fully updated, not caring about root anymore. If this were more stable I would use it more. Temp root is annoying, but it survives hot reboots, which is sufficient for apps most of the time..

Reminon said:
I was on KK, and a friend of mine updated to 5.0.1. I said screw it and fully updated, not caring about root anymore. If this were more stable I would use it more. Temp root is annoying, but it survives hot reboots, which is sufficient for apps most of the time..
Click to expand...
Click to collapse
I tried to use the hot reboot feature of a rooted reboot app I have on my Tab 3 8.0 after installing something like Xpose, but the root didn't survive. The only real reason I tried to install Xpose was to use the Motorola hotspot app found in it. I'm currently using the paid version of FoxFi and it works great, it's just a four step activation compared to the one touch I got spoiled by on my S4. No biggie.

Over on AT&T note 4 thread someone said that they have temp root for 5.1.1
Edit: someone already posted that disregard this ..[emoji4]
Sent from my SM-N910V using Tapatalk

Temp root only will give two things uninstall bloatware, SD card fix.... I don't see any other advantage, well I'll give a shoot and put my conclusion over here

EdrickMG said:
Temp root only will give two things uninstall bloatware, SD card fix.... I don't see any other advantage, well I'll give a shoot and put my conclusion over here
Click to expand...
Click to collapse
When I was on 4.4.4, I realized I could use the default file explorer to manage my SD card, meaning copy to, delete from, or anything else I needed to do with it. I'm currently on 5.1.1 now and have been for about a few weeks now. On occasion, when I install a big game, I'll get a prompt asking me if I want to move the app to my SD card, so no need for the SD card fix app. The only thing I don't like about the 5.1.1 update, though, is that the sidebar seems to pop out a bit slower than it did on 4.4.4, but that's to big a thing for me. Since I have the two apps I use the most that can be accessed from the sidebar on my Pie Control app, I can access them much quicker. Keep the dream of root alive, people. It'll come someday, hopefully. If not, at least we have cool phones to play with.

ok i can confirm that i obtained temporary root, uninstall all bloatware... so well its not perfect cuz system its very unstable but at least its a begining, now im gonna give a try to sd card fix and other stuff...
Ok SD card fixed worked... but i dont belive it will remain after reboot, so.... well at least i uninstall that Amazon stuff and Activation Agent "Not a Verizon card" stuff

Wait What........... Are we saying we now have temp root on 5.1.1

gersrt said:
Wait What........... Are we saying we now have temp root on 5.1.1
Click to expand...
Click to collapse
That's it right, at least now you can uninstall all Verizon and Amazon crap from the system

Would it be possible to disable the ****ty Verizon logo boot screen and have it disabled after reboot. Thanks

It's important saying temporary root was achieve in BPA1 bootloader, 5.1.1

I managed to get a keyboard to open by switching from the stock keyboard to kii keyboard. Have not tried any others. Is there a mod we can do for hotspot with temp root to use the native hotspot app? I'm so tired of using foxfi.

Is there a safe upgrade yet from 5.01 to 5.1.1 Thanks. I need to know in case I need to roll back to 5.01.
Thanks

Wasn't the sole purpose of the BPA1 update to "remove pre-installed Amazon apps"?

nubleeet said:
Wasn't the sole purpose of the BPA1 update to "remove pre-installed Amazon apps"?
Click to expand...
Click to collapse
Only the appstore and its widget..

Most of bloatware remains like NFL, and even instagram, however after deleted most of it, I don't know which one.. Allow me to use Hotspot without foxfi

Unstable indded
Reminon said:
Last night I was bored and tried kingroot again on 5.1.1. It had been a while since I had tried, and it always said they were looking for a method. This time, it rooted successfully, but made the system very unstable. It caused Lag, and the keyboard stopped functioning, but root checker confirmed root. Temp root of course.
Click to expand...
Click to collapse
I tried it out and it says it root is successful, but on my phone it just locks up after the rooting. I just wanted to uninstall the crap. Bummer.

Ok So Ive been checking the ATT note 4 forum and they have been suggesting that the root exploit may have been found through the Note 4 Stock keyboard. A suggestion also made was before you root change your keyboard to Swype mode then root and it appears to be more stable. Maybe someone could try install a third party keyboard before root and see if it makes a differwnce.

Nada
gersrt said:
Ok So Ive been checking the ATT note 4 forum and they have been suggesting that the root exploit may have been found through the Note 4 Stock keyboard. A suggestion also made was before you root change your keyboard to Swype mode then root and it appears to be more stable. Maybe someone could try install a third party keyboard before root and see if it makes a differwnce.
Click to expand...
Click to collapse
So I downloaded Swype and Nada. Just keeps locking up. Kingroot even updated a few min ago to 4.8.1. I thought yes! But still false hopes. Still locks up for me and can't do a darn thing. Can't wait until my contract is up I am so dumping Samsung and Verizon. I think I am gong back to a flip phone and a laptop. So tired of no root and feel like I got duped into this phone.