Related
If i install the early leaked build of the 2.2 update will i get the final one as a ota when it is official
chrishornet said:
If i install the early leaked build of the 2.2 update will i get the final one as a ota when it is official
Click to expand...
Click to collapse
You should, but only if the final isn't the same as the leaked one. You can also flash the final build once its released, manually.
You could just wait 1 day, too. I know it's killing you to get your hands on Froyo (it's killing me) but patience is a virtue. To be honest, I don't think it would have been as bad if Sprint didn't say we could initiate the update by downloading and installing it manually earlier. People have been hitting the "Check Now" button since last Friday (myself included). Why say that at all if you're not going to allow it?
BTW - your post title is very misleading... may want to change it to a question of some sort instead of statement implying what it isn't.
I highly doubt Sprint wouldn't allow the people that updated early to update again. That would be absolutely ridiculous. Either wait for the next update or for a root method on your current version.
to hopefully decrease the number of posts from members in the coming days about the new OTA that Sprint/HTC released today (but will not officially "push" to devices until January 24,) I would like to point out some things to new members as well as veterans, as we see this happen every time a new OTA is pushed.
1. Number one rule, and i will cap this DO NOT ACCEPT A OTA UPDATE IF YOU ARE ROOTED. it has been said many many times here, and members with rooted phones do it anyways. why risk it???? we all saw the gingerbread debacle last year.
2. New HBoot. it seems the new ota update has a new h-boot, 2.18, and from what it seems and this may remain to be seen 100% it is not unlockable with revolutionary. i can not confirm this personally.
3. New Radios. seems the baseband /radio has been updated. we eagerly await caulkin to possibly update his posts with the new updates.
edit: seems new radios have been posted in his thread: http://forum.xda-developers.com/show...postcount=3214
4. Why the update? The big part of this update was to remove CIQ from the evo's. yay. There were small improvements to Peep (the htc twitter client) and other various fixes.
5. So when will my favorite rom be updated to the OTA base? well, we already have a stock rom based on the ota (actually 2!) , it is located here:
http://forum.xda-developers.com/show....php?t=1455340
so this is a start. your favorite rom will be updated by it's developer when the dev has time, last update we had (4.54) we saw a rapid update of roms.
6. Great, so has sense changed at all? No we are still at sense 1.0 sigh.
7. so how about the new kernel? it is now based on htc 2.6.35.10 dated december 21, 20011. Captain_Throwback has extracted the kernel standalone: http://forum.xda-developers.com/show...postcount=3214
7a. What "hacks" work with the the new stock rom you posted? from what I have read, none of them, although people are still flashing/testing.
8. i have a question!! well use the search function and see if it has been answered, look here, the general threads, or the dev threads. I hope this will clear down some of the clutter that comes up during this wonderful thing called an OTA update.
Moto X Force Official Android 7.0 Nougat Release Note - https://motorola-global-en-aus.custhelp.com/app/answers/prod_answer_detail/a_id/118889
Model: Motorola MOTO X Force XT1580
System version: 25.11.12
Build number: NPK25.200-12
Android Version: Android 7.0 Nougat
Android Security Patch Level: 1st April 2017
I have received the update and installed it too! Everything seems buttery smooth and faster than before! Install it now! :good:
Note: I do not know how to extract OTA file from the update, so hope someone could be able to help in sharing the OTA zip file with us.
Seems you are using VPN to receive the update. Which VPN are you using? What is your / the VPN location?
Which screen protector You use? Looks good, any specs or link? I'm in Germany, still no update for eu version.
Seems like only the Motorola employees are getting the update. above photos are familiar to me. Seen somewhere in Facebook page of Moto.
FredericDelany said:
Seems you are using VPN to receive the update. Which VPN are you using? What is your / the VPN location?
Click to expand...
Click to collapse
Hi, I am not using VPN. Just using Adguard. I need to turn on the VPN to activate Adguard adblocking. Cheers!
zammi said:
Seems like only the Motorola employees are getting the update. above photos are familiar to me. Seen somewhere in Facebook page of Moto.
Click to expand...
Click to collapse
Hi, this phone is a retail version from the store. And the photos belongs to me and I shared to some Facebook pages.
You should be getting your update soon!
zammi said:
Seems like only the Motorola employees are getting the update. above photos are familiar to me. Seen somewhere in Facebook page of Moto.
Click to expand...
Click to collapse
Nope. Mine is UK retail. The update came yesterday.
Sent from my XT1580 using Tapatalk
bobyn said:
Nope. Mine is UK retail. The update came yesterday.
Click to expand...
Click to collapse
Mine also UK retail. No update yet.
What network are you on?
The most important question, were you guys able to keep root, or install root after updating to Nougat? Thanks!
Yeah, with unlocked bootloader it's easy, just flash a zip in TWRP
Thank you Lonixlon, have you personally updated your X Force while having TWRP? I had a problem with installing OTA security patch as phone booted directly to TWRP. Do you know any workaround for that?
can anyone help this guy to share OTA file?
My idea, maybe stupid and wrong - Update arrives depending on the CID of the phone.
The version of the system says "retapac", which stands for "Retail Asia Pacific" - a retail version of the phone for Asia and the Pacific.
But I do not understand what is written in "On the phone" before upgrading to NUGA. Take on incomprehensible things, mismatches, in the version of Android, the Baseband version, the system version and the build number. In the build number is very old version of the system mpks24.78-8-12, in the version of the system is the latest version of the system with the upgrade to 6.0.1, but here the old version 6.0 and the old modem.
I have a lot of questions without answers ...
ilia3367 said:
My idea, maybe stupid and wrong - Update arrives depending on the CID of the phone.
The version of the system says "retapac", which stands for "Retail Asia Pacific" - a retail version of the phone for Asia and the Pacific.
But I do not understand what is written in "On the phone" before upgrading to NUGA. Take on incomprehensible things, mismatches, in the version of Android, the Baseband version, the system version and the build number. In the build number is very old version of the system mpks24.78-8-12, in the version of the system is the latest version of the system with the upgrade to 6.0.1, but here the old version 6.0 and the old modem.
I have a lot of questions without answers ...
Click to expand...
Click to collapse
Well, may I express my opinion here too. I have an XT1581 Kinzie from China, it came with Lollipop 5.1.1. Workling perfect.
I go and update it to MM 6.0 using a Mexican or LKatin America rom, I keep the modem for the baseband from the Lollipop 5.1.1 Chinese rom, everything works almost better than before, not a single issue.
Now,m I tried to update it to Nougat 7 following the Google+ guide, a nightmare, although an enjoyable one!
First, I have only one sim working, no wif. Try anoth system, now I have two sims OK but still no wifi.
At the end, after many trials, I went back to my old MM 6.0 LAt rom, backed using TWRP, and the system is back to normal with everything working OK.
Did you ask me if I'm going to change? Nope, I'm happy the way things are, unless an official Nougat 7 ir 7.1.1 rom comes by, not loosing other time.
I agreemthere is a lot of confusion between the various roms and regions.
This news about the update and the video is very similar to the fake... Just why from such an ordinary case as an update do such a stupid circus?
not yet arrived in Indian version XT1580
neither for reteu.retfr
I have moto x play, is that mean android nougat not so far from us...??
Hi everyone,
Just to notify that I got new firmware update 47.2.A.11.228.
It includes September Security Updates... and that's a 401.4 MB update..!
Usually it was more like 200 Mo updates if I remember correctly... I wonder why. ^^
Possibly due to Sony focusing on the same time on Android 10 update.
It was more or less the same with Android 9 update last year: no October 2018 update and 2 updates for December, one being Android 9.
From what I read, "What's New" app is still there, but Xperia Lounge disapeared.
... but even being there, What's New is an empty app now ! When you open it, you have a "What's New is no longer available" message.
DanLo-peria Compact said:
Hi everyone,
Just to notify that I got new firmware update 47.2.A.11.228.
It includes September Security Updates... and that's a 401.4 MB update..!
Usually it was more like 200 Mo updates if I remember correctly... I wonder why. ^^
Possibly due to Sony focusing on the same time on Android 10 update.
It was more or less the same with Android 9 update last year: no October 2018 update and 2 updates for December, one being Android 9.
From what I read, "What's New" app is still there, but Xperia Lounge disapeared.
... but even being there, What's New is an empty app now ! When you open it, you have a "What's New is no longer available" message.
Click to expand...
Click to collapse
Yeah I got it also but I can't see any difference lol
Dark Emotion said:
Yeah I got it also but I can't see any difference lol
Click to expand...
Click to collapse
But you are more secure )
Is there any official Changelog available ?
Removing "whats new" was the number 1 reason for rooting my phone in the past.
The second reason was to dark theme apps... though now most apps seem to be dark.
Hi,
where can i get the whole firmware for g8441 as normal download? Or can someone upload the 47.2.A.11.228 firmware which will work surely? All downloadlinks i found do not work if i dry to flash them with twrp (different errors for different files).
My friends. I have a sony x f5121. When it heats up, the camera's functionality soon becomes limited and then the native camera ends up closing. After these Sony XZ1 updates, does the same problem still persist on the XZ1? (At the time of launch, many reported this problem as well). I am interested in the Sony XZ1, but if it has the same camera problems as the Sony X, it is not viable. Thanks
sony xperia xz1 updated 47.2.a.11.228 I want to root it can someone please give me boot img file etc
Where I can download the 47.2.A.11.228 stock image.
I need this firmware to install LOS 17.1.
Thank you.
sardighi said:
Where I can download the 47.2.A.11.228 stock image.
I need this firmware to install LOS 17.1.
Thank you.
Click to expand...
Click to collapse
XperiFirm
Xperifirm Tool allows to download the current firmware for all Sony Xperia Smartphones, Tablets, and Accessories running Android OS.
xperifirm.com
How is it possible pixel 6 pro to be faster and smoother on a beta version than stable android 12???
Fingerprint sensor is very good, brightness is higher than android 12 specially under sun and camera is far way more derailed than android 12 stable... Why is this happening? Are they trolling us?
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
NippleSauce said:
Presumably because this is a beta build release that is much further ahead in the current development schedule. Keep in mind that stable Android 13 releases in about two months and a week or so (August is currently the scheduled release).
It wouldn't really be a great idea in development to only start optimizing your product for stability and performance after it releases. So, that is what they are working on now; optimizing the stability, speed and performance so that they can spend the last few months of development ensuring that the new system functionality works well and is a pleasant update for us Pixel 6 users.
Also, it's important to make sure that you are releasing a great OS build - especially when that OS version's effectiveness will aid in the sales of your upcoming smartphone product that is going to launch with it (the Pixel 7 series)!
So overall, there are *Noexcusses* for being crummy with your software development and management =). Google had suffered enough with their Pixel 6 series release as they were still lacking funds in their phone development department due to a crummy lawsuit. But as a result of that issue, I'm assuming that they are shaping themselves up for that upcoming Pixel series.
Click to expand...
Click to collapse
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
biohaz55 said:
There is no Beta 3 yet. The latest release is Beta 2.1 which has some bug fixes for Beta 2.
More info here
Click to expand...
Click to collapse
Ok then Beta 2,1!
Noexcusses said:
I want my phone better than pixel 3xl at least on camera and still it is not. Im using pixel phones from Nexus 6p..
Click to expand...
Click to collapse
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Alekos said:
And it will be. Beta 2.1 (on a newly wiped 6 pro) is excellent. Battery life has settled and is more consistent, image processing is getting better and so is the overall experience.
I also have the 3 XL and I remember that it took 6 months for the device to improve. When it was upgraded to A10, it was a different phone. This happens on all Pixels/Nexus devices. Software optimization takes time and is probably more visible on Google devices just due to the way they develop and improve their software over time (just different than apple or other oems, not necessarily better or worse)
Click to expand...
Click to collapse
Hope so... Im on beta 2.1 also and i have realised brightness improvements and charging improvements too... Battery duration on 2.1 isn't so good as Android 12 but is fine as soon as is so early Beta.
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Lughnasadh said:
Patching the boot image works for me on A13B2.1. Direct install may cause bootloops though. If you encounter a bootloop using direct install you can just boot into the bootloader and flash your patched Canary 24313 (or whatever you were on) and it will boot and then patch the boot image rather than using direct install with 24314. No need to wipe the device, in my experience.
I also have verity and verification disabled.
Click to expand...
Click to collapse
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
NippleSauce said:
You're correct here. I forgot a few words in my original comment there, haha. It should have said "if the patched boot image was installed via Magisk". Sometimes I make comments too soon after rolling out of bed LOL.
Regardless, I did a full wipe and reinstall as I hadn't done my typical device setup when I had first upgraded to 13B2.1. I usually install all updates onto both slots (a and b), however, I hadn't done that initially. So a full wipe and installation onto both slots was required by my standard practices - as I wasn't even sure which one I was currently using, haha. Anyway, I've been trying to resolve some problem with Google Phone as the Visual Voicemail hasn't been working for me. So, I had figured a full wipe and reinstallation across both slots would have definitely resolved the boot loop as well as that visual voicemail problem....but it hasn't fixed the latter... =(
Click to expand...
Click to collapse
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
uicnren said:
Here's Google's workaround for visual voicemail bug on Android 13 betas
Rolling back to a v81 release of the Phone by Google app can fix the issue
www.androidpolice.com
Click to expand...
Click to collapse
Thank you for this! Unfortunately, downgrading the phone app to V81 didn't resolve the issue. I have also tried some of the other methods that were being discussed in that Reddit post but haven't had any luck with those tricks either.
I'm going to try removing myself from the Google Phone Beta next though. Worst comes to worst (if removing myself from the phone beta list doesn't work), I'll have to wait a few weeks for the next Android 13 beta update.
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
Im not rooted sir
notnoelchannel said:
Woah! This is offtopic but the pictures are so good! You're lucky that you have a pixel 6 pro
Click to expand...
Click to collapse
On android 13 beta 2,1 photos are much better than android 12...
NippleSauce said:
Beware if you're on Android 13 Beta 2.1. There is a Magisk update that released today, however, it prevents the phone from booting if installed. Requires a device wipe and reinstallation if you install that update =(.
(or maybe I'm just an unlucky duck lol)
Click to expand...
Click to collapse
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Amd4life said:
I updated to A13 beta 2.1 without a full wipe, using canary 24314 just fine. I did of course disable all modules before installing the A13 update.I also removed the -w command in the flash all bat file.
Click to expand...
Click to collapse
It seems to be a known error after clean wipe updates to the latest A13 beta build based on @uicnren 's post. According to users on the Reddit thread, the issue has to do with the beta and a current OS build miscommunication with the phone carriers in the United States. So, if this is truly the case, users experiencing this issue won't have it resolved until the next beta build release (or later). Time will tell =)
I'm abut ready to jump in and load the 13 beta on my P6 and wanted to know it there are any hotspot issues since that would be the one deal breaker for me.
Does anyone know When would be next Beta update?
Thanks...