Downloaded OTA update 2.18.707.5 .
But while installing ...RED EXCLAMATION mark ..and reboots
Tried Thrice..
Flashed Kernel and Stock Recovery and Relocked Bootloder..Still no success
Please anyone upload OTA file ...I will Try installing using TWRP recovery.
Update- I tried installing using TWRP and encountered with an error. (assert check failed- Automative_internet radi0.apk
Suggestion are always welcome
networkofhell said:
Downloaded OTA update 2.18.707.5 .
But while installing ...RED EXCLAMATION mark ..and reboots
Tried Thrice..
Flashed Kernel and Stock Recovery and Relocked Bootloder..Still no success
Please anyone upload OTA file ...I will Try installing using TWRP recovery.
Update- I tried installing using TWRP and encountered with an error. (assert check failed- Automative_internet radi0.apk
Suggestion are always welcome
Click to expand...
Click to collapse
i got an "assert failed: apply_patch_check" error for the calculator widget.
AdX9170 said:
i got an "assert failed: apply_patch_check" error for the calculator widget.
Click to expand...
Click to collapse
This means you have flashed some previous update not intended for your region, like some of us flashed 1.17.401.3 when we weren't supposed to have it, hence we coudnt update ota 4.2.2 as our ots was to patch 1.17.401.1, maybe this will help you, but its not 707, its 401, should still be able to flash though if unlocked through twrp. http://forum.xda-developers.com/showthread.php?t=2419784&page=3. You will need your firmware.zip not mine, different cids. or you could just flash this http://d-h.st/cK4, twrp again. Im sure as long as your unlocked with custom recovery you can flash different cid, except of cause the firmware.zip.
boe323 said:
This means you have flashed some previous update not intended for your region, like some of us flashed 1.17.401.3 when we weren't supposed to have it, hence we coudnt update ota 4.2.2 as our ots was to patch 1.17.401.1, maybe this will help you, but its not 707, its 401, should still be able to flash though if unlocked through twrp. http://forum.xda-developers.com/showthread.php?t=2419784&page=3. You will need your firmware.zip not mine, different cids. or you could just flash this http://d-h.st/cK4, twrp again. Im sure as long as your unlocked with custom recovery you can flash different cid, except of cause the firmware.zip.
Click to expand...
Click to collapse
That's not the case here.. I got an ota update in the device a couple of months back but it wouldn't install on its own so I installed that very downloaded zip file through cwm recovery..
AdX9170 said:
That's not the case here.. I got an ota update in the device a couple of months back but it wouldn't install on its own so I installed that very downloaded zip file through cwm recovery..
Click to expand...
Click to collapse
That will be why then, I bet if you left out that previous update, you would be able to install no problems. Sam problem for me, assert patch failed, but mine was the build.prop, because im UK and the forced ota wasn't for me.
boe323 said:
That will be why then, I bet if you left out that previous update, you would be able to install no problems. Sam problem for me, assert patch failed, but mine was the build.prop, because im UK and the forced ota wasn't for me.
Click to expand...
Click to collapse
No no I think u didn't get me. the ota update was shown on my phone. It gave me a notification that an update is available. I didn't download the update manually from xda. the download happened on my phone thru the ota service itself.
I have solved it and done update completely..
Problem --- STOCK nandroid backup have got problem.. so HTC update fails
Solutions -- Need to Update system folder with proper files for update to be sucessful
Action plan -- Those people who went to STOCk android ( INDIA) using Nandroiod backup will face issue
I will upload proper Nandroid backup ( old backup with files updated) ..
Then download update from HTC and it works and Hboot is upgraded to 1.7 from 1.4
Note -- this is for only CID 038 Which i use in India
https://drive.google.com/folderview?id=0B4wYr_bVgSTBd2ZvaHc1YllZa0U&usp=sharing
Related
I have a rooted Amaze with just some bloatware removed. Yesterday I received a notification in the status bar that a system update was available. When I try to run the update the phone reboots and then freezes with a big green X on the screen. Doesn't look like something official. Has anyone seen this before or know what it's about? I'm thinking maybe it's just failing to run the update because of being rooted or a related issue but can't find any info on Google about the green X.
I finally pulled the battery out because it wouldn't respond and then turned the phone on again. It booted fine and I still have the notice about the update. I'm reluctant to try again until I find out what's going on. Thanks.
I don't think you're able to install an update through a custom recovery..There should be a ROM with that update already in it.
If you have a Custom ROM you can't take the update that is intended for stock unrooted ROMS.
Sent from my HTC Amaze 4G using xda premium
Thanks for the feedback. I don't have a custom rom - just the stock minus some bloat. I can see how the custom recovery, however, might interfere.
I can't find any info on the update and what it includes or why I might want/need it but assuming it would be good to install then is there an easy way to remove the custom recovery? Would running the stock update.zip do this or do I need to go through the full un-root process?
If you have CWM recovery already,
1. Go to /downloads folder inside the internal Storage. You can find the OTA.
2. Rename it to "update.zip" and copy to External SD.
3. Reboot the device to recovery.
4. Select update.zip and update manually.
5. After update & reboot, delete both original files to get rid of notification.
Thanks for the directions. Tried and got this error
Code:
verifying current system...
assert failed: apply_patch_check("/system/app/FriendStream.odex", "some very long hex number", "some other long hex number")
E:Error in /sdcard/update.zip
(stage 7)
Installation aborted.
droidux said:
Thanks for the directions. Tried and got this error
Code:
verifying current system...
assert failed: apply_patch_check("/system/app/FriendStream.odex", "some very long hex number", "some other long hex number")
E:Error in /sdcard/update.zip
(stage 7)
Installation aborted.
Click to expand...
Click to collapse
Seems its not possible as you have removed some programs
Think you removed friendstream also.
It seems to work only if the ROM is unmodded
skr_xd said:
Seems its not possible as you have removed some programs
Think you removed friendstream also.
It seems to work only if the ROM is unmodded
Click to expand...
Click to collapse
Yes, I removed facebook and friendstream. Not sure why those would be necessary to run a system update but you may be right about not being able to update a modified phone. Maybe the update isn't anything I need anyway if it wants to update an app I don't want.
Thanks for the help.
In case anyone has a similar issue, here is what I've figured out.
The update won't run on a modified system - even if it's a stock, but changed, rom. In the interest of exploration, I restored my backup using clockwork and then ran the update. It still didn't work, but following skr_xd's advice above I was able to run the update manually. The result was a more or less stock phone without root but with the most current software. I then re-rooted the phone and re-removed all the bloat with no apparent ill effects.
Thanks for the help.
Btw, I didn't know what the green X was all about, but I think it's related to clockwork mod. Could be wrong though.
droidux said:
In case anyone has a similar issue, here is what I've figured out.
The update won't run on a modified system - even if it's a stock, but changed, rom. In the interest of exploration, I restored my backup using clockwork and then ran the update. It still didn't work, but following skr_xd's advice above I was able to run the update manually. The result was a more or less stock phone without root but with the most current software. I then re-rooted the phone and re-removed all the bloat with no apparent ill effects.
Thanks for the help.
Btw, I didn't know what the green X was all about, but I think it's related to clockwork mod. Could be wrong though.
Click to expand...
Click to collapse
yes its the custom clockworkmod i made
xboarder56 said:
yes its the custom clockworkmod i made
Click to expand...
Click to collapse
Thanks for the confirmation and awesome software. I noticed there is work on version 5.0.2.7. Assuming it would be wise to update once released.
Same issue here. I have stock rom without any bloatware removal.
I just unlocked the bootloader than installed CWM and rooted the phone.
when I try to update phone OTA it stucks in splash screen (With Big Green X logo)
Flash prerooted rom you good to go
Sent from my HTC Amaze 4G using xda premium
I just spent abut 4 hours trying t figure this out...
This is my journey..
Relock bootloader
Flash one of the stock tmobile ruby rom in development section
Did the OTA update on stock
Unlocked my bootloader again
Then i tried to root using one click zerg method but it didnt work
So i flashed clockwork mod using fast boot
Then applied a su binary update i found in the development section.
In less than a minute i got root back.
Then i restored my data from nandroid backup.
My phone is pretty much rooted, bootloader unlocked, bloatware free alongside having the ota update that enabled wifi calling installed.
You don't need to relock your phone to do the update. If you do xboarder's recover to stock method just skip the relock part you can update your phone. So far going back to stock is the only way to get the radio updated as well which I am noticing way better 4g coverage than before!
bmbrad said:
You don't need to relock your phone to do the update. If you do xboarder's recover to stock method just skip the relock part you can update your phone. So far going back to stock is the only way to get the radio updated as well which I am noticing way better 4g coverage than before!
Click to expand...
Click to collapse
working on a way maybe this weekend will have it ready
xboarder56 said:
working on a way maybe this weekend will have it ready
Click to expand...
Click to collapse
NICE! Dude you must never sleep! Always the first to get something done!
I figured out what to do. You just need to rename this update file to update.zip. then reboot in recovery and choose install update from sd card. Next navigate to download folder and install update.zip file. You will be updated and stay rooted at the same time.
This worked for you because you didn't remove any of the t-mobile bloatware from your phone.. This will not work for people who messed with the pre-installed bloatware.
darll said:
This worked for you because you didn't remove any of the t-mobile bloatware from your phone.. This will not work for people who messed with the pre-installed bloatware.
Click to expand...
Click to collapse
Maybe, but 8m I've got another problem after updating this way. Wifi doesn't work anymore. I receive an error while trying to switch on wifi.
I did an OTA upgrade to LG8 and Rooted with CF-Root6.4 and now every time I reboot it shows the "Android is upgrading" message, so anyone know how to fix this without reflashing Rom because I won't be home until next week.
Try to remove the synchronization with samsung account , if there is still a notification, you have to do a wipe date , factory reset ....
unable to update after root
why did i can run the OTA after root? is it normal? the clockwork recovery said the the signature was not recognized.
Fundamental element in order to be able to complete the update process of the Galaxy is to have a firmware entirely original.
If you have on your phone a test version, root permissions enabled or a modified kernel installed (e.s. , CF-Root) will be unable to update.
kintol said:
why did i can run the OTA after root? is it normal? the clockwork recovery said the the signature was not recognized.
Click to expand...
Click to collapse
Root no OTA update as per then thousand posts .
jje
I was Rooted when I got the OTA update and apart from this problem which isn't really a problem it all went through fine, so guess I'll just wait and use Odin to see if it fixes.
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
Anytime you root the phone it changes the stock recovery so when the OTA tries to run it fails because the recovery needed to do it is the stock one. Just wait for someone to post a updated ota that works with twrp.
For the most part, updates will be baked into roms so you won't need to take the OTA
Sent from my Tricked out HTC One
jznomoney said:
Anytime you root the phone it changes the stock recovery so when the OTA tries to run it fails because the recovery needed to do it is the stock one. Just wait for someone to post a updated ota that works with twrp.
Click to expand...
Click to collapse
On top of stock recovery, you need to have all stock apps present on the phone. They can be frozen, but they must be there. The first thing any official OTA does it check the signatures of all .apks it expects to find on the device--if any are missing, the update will abort. I learned today that when you unlock your bootloader, several HTC-specific applications are automatically deleted from the phone and this will prevent the phone from accepting the OTA. You'll need to either A) replace those apks, or B) flash a stock NAND backup, flash stock recovery, do the update, then re-flash custom recovery and continue on from there.
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
I installed it and it worked great. I have a unlocked bootloader but I am not rooted.
AT&T update file name and location?
Same experience. If I knew the location and file downloaded through AT&T Software Update, perhaps I could install it through TWRP. Anyone know? Tried?
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
StanAnderson said:
Same experience. If I knew the location and file downloaded through AT&T Software Update, perhaps I could install it through TWRP. Anyone know? Tried?
Click to expand...
Click to collapse
no it will not work
Please...a little advice
Many thanks for all your help.
One question:
I have an HTC One (ATT) - SW Ver 1.26.502.10, bootloader unlocked, rooted, bloatware erased.
If I flash CM 10.1 - does this include the latest OTA update.
Many thanks
My Nexus 9 is stock, un-rooted with an unlocked bootloader.
I have received the OTA update but when it reboots it gets part way through then shows "error" with and android on his back. I have downloaded the OTA file from AndroidPolice and tried flashing via adb sideload.
It attempts to verify the current system but then errors with the following message:
Package expects build fingerprint of google/volantis/flounder:5:/LRX21L/1546449:user/release-keys or google/volantis/flounder:5:/LRX21Q/1573789:user/release-keys; this device has google/volantis/flounder:L:/LFW73W/1491895:user/release-keys
Click to expand...
Click to collapse
Why have I got a different build?! Is there a different OTA that i need?
I have the same issue, any one any idea?
same here. tried factory reset just to eliminate didn't help
https://plus.google.com/110305043896789356373/posts/bHyo4UazRpH
As I have an unlocked bootloader i've just flashed the recovery from the factory image and then applied the OTA update (mostly to see if it would work, otherwise i'd have continued with factory image). It's booting up now. I guess Google will need to push a new OTA that updates from this version... a bit of a screw up though!
ATT sent B180 down...
And of course, overnight, my phone tried to update - and is now stuck in a boot loop with TWRP.
Yay.
Hope everyone else is having a better day.
Rename
"/system/priv-app/DMClient/DMClient.apk"
by appending ".xxx" to the end using TWRP file manager.
Clear /cache partition.
Reboot and see if it works .
Paisley Pirate said:
ATT sent B180 down...
And of course, overnight, my phone tried to update - and is now stuck in a boot loop with TWRP.
Yay.
Hope everyone else is having a better day.
Click to expand...
Click to collapse
For those wondering about updating to B180.....
See this post and links in it for how we updated before if the phone was already unlocked bootloader/rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
reloaded 170 full version on and it worked fine. Need to clean it up, as it threw the bloat back on - but didn't lose anything. Unfortunately, between 2 jobs, and moving (working on new house now, move in a couple weeks, then work on old house to sell it) I'm not seeing much time in my future to play with it much.
Is B180 rootable?
I imagine like the other version so far, it should be.
Ad86shwks said:
Is B180 rootable?
Click to expand...
Click to collapse
I have B170 installed. But I have it debloated, rooted, and custom recovery on it. I want to update to B180. Anyway someone can make it a standalone update? Like B170?
im waiting on the files from someone and i will release a b180 stock update as well as update my rom to b180 once i get the b180 files
b180 uploaded stock preroot atm will do full stock soon b180
i installed the b180 zip. There is one problem wifi is broken.
Thanks for the hard work to update to b180.
hi5five said:
i installed the b180 zip. There is one problem wifi is broken.
Thanks for the hard work to update to b180.
Click to expand...
Click to collapse
wifi is broke? i flashed it before i uploaded it worked fine try doing a clean flash format data system cache etc then flash
Did you previously have B170, then used your zip to update to B180?
madvane20 said:
wifi is broke? i flashed it before i uploaded it worked fine try doing a clean flash format data system cache etc then flash
Click to expand...
Click to collapse
i flashed b170 stock then flashed my b180 stock if wifi is broke i can redo it but it worked on mine just let me know
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
I believe you will need to flash updates as nobody has been able to OTA after unlocking the bootloader.
dabadguycr said:
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
Click to expand...
Click to collapse
divineBliss said:
I believe you will need to flash updates as nobody has been able to OTA after unlocking the bootloader.
Click to expand...
Click to collapse
I was able to update to b140 from b130 from a unlocked bootloader but that was from before I rooted.... It was before root was available.
Thanks for that detail. I wonder which partitions aside from the boot partition get modified after rooting that then breaks OTA from working.
dabadguycr said:
I was able to update to b140 from b130 from a unlocked bootloader but that was from before I rooted.... It was before root was available.
Click to expand...
Click to collapse
---------- Post added at 10:50 PM ---------- Previous post was at 10:35 PM ----------
I don't think there's any way to put your phone back to the state where an OTA will work - at least nothing we currently have on the XDA forums here that I've seen.
You could always try what you wrote below - I expect OTA will fail. If it fails, you could flash B180 - which I believe is unrooted from what I recall @clsA writing about his method to flash B180 in the B170/B180 thread by @madvane20 - but please double check on that before doing it since you want to be able to remain unrooted.
dabadguycr said:
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
Click to expand...
Click to collapse
divineBliss said:
Rename
"/system/priv-app/DMClient/DMClient.apk"
by appending ".xxx" to the end using TWRP file manager.
Clear /cache partition.
Reboot and see if it works .
Click to expand...
Click to collapse
hi thanks for this advice buy my device does not have this directory or files. I am in the same boat on 170 slim and fast, got AT&T update and now in force reboot update and fail loop. i really want to find a way to make it stop force rebooting? surely something i can do in twrp terminal. any advice? but alas I might just have to reflash.
make sure u mount system in twrp that folder and file should be there and make sure to clear cache like the other post said