Database Develop

Update 1.25.405.1 released

My (rooted, stock rom) wildfire offered me this system update today:
1.25.405.1
Update Information: 1. Enhances support for Facebook status display when dialing; 2. Increases support for Google Services like Google Talk, Android Market and others; 3. Improves combining contacts from Outlook and other source
Problem is, I can't get it to install on my (rooted) wildfire. The system reboots, but the install fails, and I get booted back into clockwork. Anyone a solution?
--------
Update: What I did to succesfully install the update on a rooted phone
- unplug phone from USB, let it download update (it's about 13 Mb in size)
- phone will ask to reboot -> update will fail, you will be dumped in clockworkmod
- As always, do a Nandroid backup before doing anything that might possibly render your phone unusable.
- Select update from zip/sdcard (or similar), navigate to zip in downloads folder
- the update process will start
- reboot (this can be a longer boot than usual, took 10 minutes on my phone)
- phone will notify you that the update has succeeded! If you've upgraded from your stock ROM (like I did), the phone info screen should look similar to that in the attached image.
- (reflash needed for root)

In clockwork, I selected install update from ZIP, navigated to sdcard -> download ->HTC_Buzz_....zip file, and selected that.
Seems to be installing fine now, I'll update this post once I confirmed it worked.

Had to reroot, but it seems to have installed fine.

RUU_Buzz_HTC_WWE_1.25.405.1_Radio_13.45.55.24_3.35.15.31_release_142189_signed.exe is an exe file, you have to install it from windows and not from clockwork.
Before you install this update, you have to do a backup.

I had a zip file in my downloads folder, around 12 Mb.

Update went fine on my rooted Wildfire, using ClockworkMod.

it's nice to see that they push out the update over the air now.
its the same version as on shipped-roms.

Does this mean we can expect froyo soon?
Sent from my HTC Wildfire using XDA App

can you send the zip plz forceflow ?

Will this be a stepstone release that will result in a Froyo update?
Or does this mean Froyo is delayed for WildFire?
Sent from my HTC Wildfire using XDA App

I had this update when I bought my phone, its not a new update
Sent from my HTC Wildfire using XDA App

I've updated to version 1.25.405.1 today and suddenly wifi stopped working. When I try to turn it on 'unable to start Wi-Fi' message shows. I don't know if it is related to this update, but it starts happening immediately after that update. Has anyone the same problem?

i have tried everything
hi,
i'll really appreciate if someone will help me.
i have tried everything you guy's wrote here but it still popup a message: signature verification fail
thank's

idan1908 said:
hi,
i'll really appreciate if someone will help me.
i have tried everything you guy's wrote here but it still popup a message: signature verification fail
thank's
Click to expand...
Click to collapse
How are you installing it ?? .. is it OTA ? or ur installing it through RUU ?

Just updated fine here OTA. No problems as of yet.
Lets keep our fingers crossed that this is just a stepping stone to Froyo.

I can't update. It give me an error in clockworkmod. It's because I erase Sense and some stock apps?
Sent from my HTC Wildfire using XDA App

QAD3R said:
How are you installing it ?? .. is it OTA ? or ur installing it through RUU ?
Click to expand...
Click to collapse
I think it was OTA, because the same problem I have too. clockworkmod doesn't help to install this update after trying to instal zip from sd card receive message " signature failed" or something like this. Phone rooted, what to do?
RESOLVED
At clockwordmod before choosing zip from sdcard select "Toggle signature ver", this won't check signatures and update wil sucsess

Hi Everyone,
i just updated my Wildfire. After downloading, just clicking on the statusbar, and installed it.
Works well, no problems yet.

how do i start the clockworkmod? which key-combination is it?
i have a rooted phone (per unrevoked 3)
com

Comfreak89 said:
how do i start the clockworkmod? which key-combination is it?
i have a rooted phone (per unrevoked 3)
com
Click to expand...
Click to collapse
then update fails push at the same time POWER + Volume down

[Q] razr i wont update to jellybean ota

I can't post in developer forum as I don't have 10 posts sorry. I have rooted RAZR I using mattlgroff root tool and have made no other changes since, I am a complete noon to this so sorry if this is an easy fix Halfway through the installation if the official ota the dead DROID comes up, the phone restarts and then I get a msg saying update failed, i have looked all over but cant find a guide on how to unroot my phone to be able to update,
Can anyone help? Thanks

doug143 said:
I can't post in developer forum as I don't have 10 posts sorry. I have rooted RAZR I using mattlgroff root tool and have made no other changes since, I am a complete noon to this so sorry if this is an easy fix Halfway through the installation if the official ota the dead DROID comes up, the phone restarts and then I get a msg saying update failed, i have looked all over but cant find a guide on how to unroot my phone to be able to update,
Can anyone help? Thanks
Click to expand...
Click to collapse
do you have any custom launcher? because that is a reason that prevents from updating your device !!! if you are not rooted you can easily update to JB

mayelin911 said:
do you have any custom launcher? because that is a reason that prevents from updating your device !!! if you are not rooted you can easily update to JB
Click to expand...
Click to collapse
JB OTA doesn't work for me either and I'm 100% stock.
Downloads fine, reboots to install, and then get a little green robot with a red exclaimation mark, then boots back to the homescreen and says Update Failed.

Same issue here.
Mine was unlocked, rooted, CWM installed.
Ive since removed CWM but have the exact same issue now as you.
Ive also tried updating with the OTA file via factory recovery. This also fails part way through the process.
Currently Im trying a factory reset and OTA update. Its been a 3 hour mission so far........
---------- Post added at 10:58 AM ---------- Previous post was at 10:32 AM ----------
Factory reset....still fails. What a joke.
---------- Post added at 11:06 AM ---------- Previous post was at 10:58 AM ----------
Anyone have any words of wisdom as to another update procedure we can try?

Installing the factory OTA update from http://forum.xda-developers.com/showthread.php?t=2028814 (81.5.39001-91.2.29001.Retail.en.GB 4.0.4-4.1.2)
From recovery (default) updating from external storage gives the following error:
Code:
qe 0/1
-- Install /mnt/sdcard/ ...
Finding update package ...
Opening update package ...
Verifying update package ...
Installing update ...
Verifying current system ...
assert failed: apply_patch_check("EMMC:boot:fsdf93r9ejfwfjdsjgg.....lots of letters........")
E: Error in /tmp/sideload/package.zip
(status 7)
Installation aborted
Do we perhaps need to remove root?

I am pretty much the same as everyone else,
I have the bootloader unlocked and it is rooted, using stock ICS (No CFW what so ever)
I download update, install, get 1/4 of the way and then Andy is on his back with a red "!" above him.
Now i read somewhere yesterday that you need to un-root your phone, and then flash some stock firmware back onto it where you can the upgrade to JB?
If this is true can you direct me (and probably many others) to a link to do such thing?
Cheers
Bradley

Im thinking flashing:
CFC_8.7.1I-110_IFW-39_S7_UCASMI01E1017.0R_USASMIICSRTGB_P042_A005_S1FF_fb.xml.zip
from http://sbf.droid-developers.org/smi/list.php. That will get us back to standard retail firmware and try again?
[q] How does that effect the current unlocked status of our device? Im assuming it wont

Success!
Using RSDLite 6.1.4
Flash (retail gb) CFC_8.7.1I-110_IFW-39_S7_UCASMI01E1017.0R_USASMIICSRTGB_P042_A005_S1FF_fb.xml
Then stock recovery to flash 4.1.2 update zip
It took sometime 'Updating radio..' but otherwise processed as normal.
Its odd that it wouldn't update what was basically a stock phone to start with, but still got there in the end......

My xt890 won't come up in the LSD lite programme?
Any one know how to fix this?

coolbluelights said:
My xt890 won't come up in the LSD lite programme?
Any one know how to fix this?
Click to expand...
Click to collapse
I am going to assume you have the proper motorola drivers installed?

Drivers and steps to follow:
http://forum.xda-developers.com/showthread.php?t=1974568

Yes I have to upto date drivers installed, in fact, I un installed them and thn re installed them

coolbluelights said:
Yes I have to upto date drivers installed, in fact, I un installed them and thn re installed them
Click to expand...
Click to collapse
Developer > usb debugging enabled?
Are you in boot mode? eg pc/usb cable plugged in, press power and volume + to start phone.

Usb debugging is Checked and I put it into recovery.
I am running windows 8 with my Usb cable plugged into a 3.0 Usb socket

coolbluelights said:
Usb debugging is Checked and I put it into recovery.
I am running windows 8 with my Usb cable plugged into a 3.0 Usb socket
Click to expand...
Click to collapse
Are you able to issue fastboot commands to the phone (confirming its not a driver / connection isssue)
Perhaps someone else can confirm the operation of rsdlite under Win8?

At last I got it to work and now my razr is on JB, all i had to do was use my laptop running xp (Doesn't work on windows 8)
Cheers everyone for all you help, especially you SpookyAwol, you have been the biggest help to me :highfive: :good:

[Q] OTA 5.1 Update file location?

So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.

You need to unroot too.
Ota can be downloaded online.

d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.

rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU

Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.

OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.

Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?

Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6

Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images

Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache

Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.

Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.

liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip

Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...

Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!

Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.

/data/data/com.google.android.gms/app_download/update.zip

d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.

At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip

2016-06 Security patch won't install on Nexus 6

I get this 2016-06 Patch that wants to be installed on my Nexus 6. When I try to install it, the ERROR screen shows during the process. This happens over and over. As painful as it was, I did a factory reset on my phone and the issue still exists.
I contacted Google, because it is a Google phone and has Android, and they routed me to Motorola.
Motorola gives me this update tool which does not solve the issue.
Since it is more than 1 year old, there is no warranty even though it is not my fault at all that the 2016-06 patch does not update properly.
First, Motorola support for this device sucks. Second, any ideas to resolve this since Motorola support for this device sucks?

with your positive attitude, its hard to believe that Motorola doesn't want to go out of their way to help you..
its out of warranty, so don't expect anything support wise..

What error, on what screen? Which version do you have? Are you unlocked? Do you have a custom recovery? Are you rooted?
Do you have a computer, and did you try to sideload the OTA?

@brucechidester you need to give more information if you need help solving the issue. it could me one of very many things btw..

Answer to questions
I wish Motorola would have asked as good as questions as you have. What screen? During the upgrade process it appears to be loading properly until the error screen shows with an Android dead and the word "error" above him. What version? 6.0.1. Is a system unlocked? It had been unlocked in the past but this process was reversed and the screen shows the key in the locked position. Sideload the OTA? I am not familiar with this process so I would say not. Motorola had me install a Windows application which attempted to upgrade the firmware via USB but this did not resolve the problem. This was Motorola's only technical response to my problem. This did not work so they gave up.

Okay, then I suggest, you should look up the Nexus 6 Index thread
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
and read the The Nexus 6 All-In-One Beginner's Guide, and particularly the Nexus 6 OTA Help Desk .
After that we'll be able to speak the same language, and help you if you get stuck, because you'll be able to ask specific questions.

I attempted to update the phone using the sideload OTA process. It gets to about 47%, quits and gives an error. I definitely have a Nexus 5 and used the hammerhead image. A couple to be exact. Same result.
I noticed at the top when I got into to recovery screen:
Android Recovery
google/shamu/shamu
6.0.1/MMB30G/2756603
From this I assume I have update MMB30G
I found the update file for MMB30G identified at https://gist.github.com/jduck/53dc121820f6b30374bfa871146ca956
When I tried to update with this I get:
Installing update...
Source: google/shamu/shamu:6.0.1/MMB30G/2756603:user/release-keys
Source: google/shamu/shamu:6.0.1/MOB30I/2756745:user/release-keys
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc: 1/by-name/boot:8391910:043f426b9056cb46e8532a ..... has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted

brucechidester said:
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc: 1/by-name/boot:8391910:043f426b9056cb46e8532a ..... has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted
Click to expand...
Click to collapse
It means you modified your system partition, so the OTA fails.
But it usually means your bootloader is unlocked so you should download the factory image, and flash the bootloader, radio, boot and system from the factory image, format the cache. Then you have your update.

You should flash the factory image, Google Nexus Factory Image and maybe look around if their explanation isn't enough for you on Google's page
Sent from my Nexus 6

[GUIDE] How to install the One UI beta on an AT&T locked s9

Hey guys, just wanted to drop a quick and dirty guide on how to get the beta working on your locked AT&T device. I am by no means a developer or an expert, but I've been flashing ROMs and modding my devices for close to 8 years. I take no responsibility if you brick your device or cannot get it to work, feel free to research yourself or wait until the beta ends and Samsung releases Android 9/One UI next year.
Okay, so the first thing I had to do was install the U1 firmware. I used this thread for most of the steps.
The links to the modded version of Odin in the 2nd post of that thread were dead, so I downloaded it from this post.
I downloaded the 3ARJ2 U1 firmware here.
Following the directions in that U1 thread, I unzipped the firmware file and flashed it in Odin. Elsewhere in the thread, it was recommended to choose the CSC file that starts with "CSC_OMC_OYM..." instead of the "HOME_CSC" file.
After it boots up, you may be able to join the beta using the Samsung+ app, I'd recommend downloading this beta version.
For whatever reason, the beta registration banner showed up for me but pressing the register button never did anything. I found many reports of that problem and tried everything for about two hours to make it work before moving on and downloading the OTA beta file below and installing it through recovery.
I downloaded the OTA file for the U1 firmware from this post.
ARJ2 to ZRK9 (Beta 1)
Download link:
https://mega.nz/#!sjRnHK4S!o2sJ49Stk2GzUFhFXX1Hed8hSOsAVkfaBPVRWY989QM
After installing the beta zip, I performed a factory reset, just in case.
Now I'm happily using the beta on my locked AT&T s9. I did see an option for VoLTE, but I had to disable it due to being on a FirstNet SIM, so I can't speak to how well that feature works. I haven't had much time to play around with the beta yet, because I wanted to get this posted up before I went to work. Hope this helps someone else! Thanks to all who helped me in the various threads, I really appreciate the XDA community!
P.S. This does not trip Knox.

Thank you I'll give it a shot

You're on a FirstNet sim too huh? Me as well. Gonna give this a shot.

I'll be curious how your reception is on the beta. Mine doesn't seem as good as before. I checked the APN settings, and it's still showing that it's using FirstNet profiles.

911jason said:
I'll be curious how your reception is on the beta. Mine doesn't seem as good as before. I checked the APN settings, and it's still showing that it's using FirstNet profiles.
Click to expand...
Click to collapse
Ended up not being able to go from BRJ5 because I can't get the firmware in the correct order. Did doing this trip your Knox? Not a huge deal for me, as I am the IT in my government agency, but a big deal for device compliance in Intune.

I was on 3BRJ5 before flashing the U1 firmware. It did not trip Knox.

So does WiFi calling and VoLTE work? Can anyone confirm

xguntherc said:
So does WiFi calling and VoLTE work? Can anyone confirm
Click to expand...
Click to collapse
Ultimately those features aren't present on the U1 firmwares for Att.

I have a Verizon device and tried installing the One UI beta on my S9+ and got some error messages and wondered if anyone could point me in the right direction
E: folder is wrong
Update package verification took 0.1s (result 1)
E: signature verification failed
E: error 21
Installation aborted. #1

Sproveri said:
I have a Verizon device and tried installing the One UI beta on my S9+ and got some error messages and wondered if anyone could point me in the right direction
E: folder is wrong
Update package verification took 0.1s (result 1)
E: signature verification failed
E: error 21
Installation aborted. #1
Click to expand...
Click to collapse
Sorry, but pretty sure this is S9 only. There is another thread for S9+
That's why it keeps falling

Appreciate the patched Odin. I also have the locked SM-G960U and was unsuccessful in flashing U1.

Sproveri said:
I have a Verizon device and tried installing the One UI beta on my S9+ and got some error messages and wondered if anyone could point me in the right direction
E: folder is wrong
Update package verification took 0.1s (result 1)
E: signature verification failed
E: error 21
Installation aborted. #1
Click to expand...
Click to collapse
The reason its failing is OneUI beta isn't designed for Version G965U. You will need to got to G965U1 to load the beta.

elstano2k7 said:
Appreciate the patched Odin. I also have the locked SM-G960U and was unsuccessful in flashing U1.
Click to expand...
Click to collapse
What part of the process didn't work?

911jason said:
What part of the process didn't work?
Click to expand...
Click to collapse
The 256? error

Finally made the jump as I was too sick of waiting on samsung/att to give me the update! Thanks for the great instructions and links that actually work. Beta 3 to me feels better than using Oreo. The only weird little bug I have noticed is the night mode likes to turn itself off randomly. It's been working great as my daily driver for a almost a week now without issue.

Easy way
Found a easy way
Flash the G960U1 in the post
Completely Boot then
Then flash this via odin
https://drive.google.com/file/d/12zsai6UKCeadt0L1D765vVnksqPTi0pp/view?usp=drivesdk
Full 9.0
Unzip
Follow the flashing step
But add the user data
And boom!!
Works on att US model tested on my own

FizzyAps said:
Found a easy way
Flash the G960U1 in the post
Completely Boot then
Then flash this via odin
https://drive.google.com/file/d/12zsai6UKCeadt0L1D765vVnksqPTi0pp/view?usp=drivesdk
Full 9.0
Unzip
Follow the flashing step
But add the user data
And boom!!
Works on att US model tested on my own
Click to expand...
Click to collapse
Where is the userdata files for the FW