Related
If you like me have just upgraded to the 2.03 rom released in January and now HTC released a new rom with exactly the same changelog it may not be worth all the hassle with reinstalling / configuring all your stuff once again already.
I was pissed at HTC since they couldn't tell us what they changed since they told us to REAPPLY this update if we had installed it prior to february 27. So today I sent them this email:
Latest ROM update for HTC Touch Diamond. It took me over a week to customize my device after the 2.03 ROM released in january since I prefer to cleanly re-install everything instead of backups. Now a new ROM with the same changelog is already released & you say we should re-apply this ROM if we installed before february 27! Why? We are many people who don't wanna go trough all the hassle again. Why can't you just tell us what you fixed so we can decide for ourselves if it's necessary. The january ROM works just fine. Yours sincerely, ******.
And I just got an answer from them that I can't post here since it came with a confidentialy note. But I can tell you in short that they explained that there are lots of things and bugs for different time made devices and changes and that is why they can't say what is changed in the february 27 rom.
They also told me not to reapply the update if my device is working fine, there is no need to.
So you can without any worries stick with the january update for now if you don't experience any issues or don't feel like installing all your stuff from scratch
owziee said:
If you like me have just upgraded to the 2.03 rom released in January and now HTC released a new rom with exactly the same changelog it may not be worth all the hassle with reinstalling / configuring all your stuff once again already.
I was pissed at HTC since they couldn't tell us what they changed since they told us to REAPPLY this update if we had installed it prior to february 27. So today I sent them this email:
Latest ROM update for HTC Touch Diamond. It took me over a week to customize my device after the 2.03 ROM released in january since I prefer to cleanly re-install everything instead of backups. Now a new ROM with the same changelog is already released & you say we should re-apply this ROM if we installed before february 27! Why? We are many people who don't wanna go trough all the hassle again. Why can't you just tell us what you fixed so we can decide for ourselves if it's necessary. The january ROM works just fine. Yours sincerely, ******.
And I just got an answer from them that I can't post here since it came with a confidentialy note. But I can tell you in short that they explained that there are lots of things and bugs for different time made devices and changes and that is why they can't say what is changed in the february 27 rom.
They also told me not to reapply the update if my device is working fine, there is no need to.
So you can without any worries stick with the january update for now if you don't experience any issues or don't feel like installing all your stuff from scratch
Click to expand...
Click to collapse
I have to soft-reset my device everytime during an installation, then run the install again. The x-button doesn't work properly (turned "close programs using x" on). Never had to use the red soft-reset button as often as with this ROM (crashes easily). Plus it's much slower than my previous official ROM.
I think this ROM update is for people like me...
Well maybe... I don't experience any of the problems you mentioned.
owziee said:
...It took me over a week to customize my device after the 2.03 ROM released in january since I prefer to cleanly re-install everything instead of backups. Now a new ROM with the same changelog is already released & you say we should re-apply this ROM if we installed before february 27! Why? ...
Click to expand...
Click to collapse
are u suggesting that htc should stop releasing updates for diamond?! dude, why using stock rom's, what's the fun in it anyway!?
No no, absolutely not!!!
But HTC released this rom (february 27) with the same changelog as the 2.03 rom they released in january and I've just gone trough reinstalling everything so the idea of installing virtually the same rom once again gave me a headache.
HTC urged us to reapply the update if we installed it before february 27 and I really needed to know why so I had to send them the email.
Of course I would be very happy to see new rom upgrades in the future as long as there are changes / fixes worth mentioning (They didn't even mention any fixes this time since they just posted the same changelog all over and it was only 1 month between the updates).
ROM info...
What's more... take a look at the version numbers:
January's ROM: v2.03.405.2
February's ROM: v2.03.405.3
When a version number change isn't even a point (i.e. the '.03' in the above example), believe me, not a lot has changed. But this is worse than that, a change from .03 to .04 would probably mean just correcting a spelling mistake... this change is so far down the points, it doesn't even make it past the 'what's the POINT' stage with me (get it... what's the POINT!!) - OK, rubbish joke
Maybe the newer ROM fixes problems that only appear under special constellations.
For my part it fixed a problem i had:
Sometimes TouchFlo 3D diddn't start correctly after a softreset (from Sprite Backup),
device kept powered on until battery was empty.
They don't list a newer changelog for this ROM, but i find it strange that the Jannuary
version is no more available on the website.
But i agree, if the Jannuary version runs fine absolutely no need to upgrade.
I'm posting this because I didn't see anybody with this build yet...
Okay, so here is my story, like most of you, I was pretty frustrated that my stock build wasn't getting ICS, I was running 2.007.04_EMEA_GB. First off I wasn't sure if the EMEA_GB version is designed for Canada (since I bought my A100 off of someone from Craigslist). I took many backups of my system by using the DD commands before trying the leaked versions of ICS that were posted by Vache, starting in March. When 14 was out, I loaded it up but really didn't think it was the "official" firmware, as there were still a few lingering issues with the ICS build, so I went back to HC (using the Gen2 HC full update package) rooted it, then and reimaged all of the partitions with the old DD images I kept from the original firmware that shipped with my device.
ICS was supposed to have been released yesterday, and I had in my mind from March that I was going to have ICS from Acer as my birthday present... and Today is my birthday (haha) so I had to make it happen! I didn't want that v14 on there, and I had read in a different thread that an A100 actually had a build 15 on it, which sort of verified hypothesis that v14 might not be the official firmware, so I went ahead and flashed the original GEN1 stock Honeycomb rom, Acer_A100_1.014.08_COM_GEN1 : http://vache-android.com/v1/download.php?fileID=109 .
Once that was flashed, (with a data reset) I immediatley tried to run an update check but it told me that the device was up to date (haha what a lie). Since this was about 2am and I was supposed to be sleeping, I let it sit for about an hour before trying the update check again. The device had 4 updates in total, after the second update, it changed to a PA_CA release, then before the 4th update came in, the update wizard warned me that Kobo and Adobe Flash wasn't part of the system, but could be downloaded. I figured this was the ICS update, and I wasn't wrong. Once everything was done updating (at about 3:30, the Acer update servers were really fast at that point LOL) I checked the system version and found that I was on v17_PA_CA. Attached is my screenshot.
After running this version for ~8 hours, I havent had any freezing, menu transitions are very smooth, no touchscreen bugs yet either. This build feels like it is a perfect match for my hardware. Also, it looks like the battery life is better, but only time will tell on it.
I have attached a screenshot of the build that I'm on as well, just in case anyone has any questions. It's really possible that since I used the original firmware that it checked in to the acer servers as a new device and it should send me all the updates in one shot.
danifunker said:
I'm posting this because I didn't see anybody with this build yet...
Okay, so here is my story, like most of you, I was pretty frustrated that my stock build wasn't getting ICS, I was running 2.007.04_EMEA_GB. First off I wasn't sure if the EMEA_GB version is designed for Canada (since I bought my A100 off of someone from Craigslist). I took many backups of my system by using the DD commands before trying the leaked versions of ICS that were posted by Vache, starting in March. When 14 was out, I loaded it up but really didn't think it was the "official" firmware, as there were still a few lingering issues with the ICS build, so I went back to HC (using the Gen2 HC full update package) rooted it, then and reimaged all of the partitions with the old DD images I kept from the original firmware that shipped with my device.
ICS was supposed to have been released yesterday, and I had in my mind from March that I was going to have ICS from Acer as my birthday present... and Today is my birthday (haha) so I had to make it happen! I didn't want that v14 on there, and I had read in a different thread that an A100 actually had a build 15 on it, which sort of verified hypothesis that v14 might not be the official firmware, so I went ahead and flashed the original GEN1 stock Honeycomb rom, Acer_A100_1.014.08_COM_GEN1 : http://vache-android.com/v1/download.php?fileID=109 .
Once that was flashed, (with a data reset) I immediatley tried to run an update check but it told me that the device was up to date (haha what a lie). Since this was about 2am and I was supposed to be sleeping, I let it sit for about an hour before trying the update check again. The device had 4 updates in total, after the second update, it changed to a PA_CA release, then before the 4th update came in, the update wizard warned me that Kobo and Adobe Flash wasn't part of the system, but could be downloaded. I figured this was the ICS update, and I wasn't wrong. Once everything was done updating (at about 3:30, the Acer update servers were really fast at that point LOL) I checked the system version and found that I was on v17_PA_CA. Attached is my screenshot.
After running this version for ~8 hours, I havent had any freezing, menu transitions are very smooth, no touchscreen bugs yet either. This build feels like it is a perfect match for my hardware. Also, it looks like the battery life is better, but only time will tell on it.
I have attached a screenshot of the build that I'm on as well, just in case anyone has any questions. It's really possible that since I used the original firmware that it checked in to the acer servers as a new device and it should send me all the updates in one shot.
Click to expand...
Click to collapse
cool beans...im on pa_ca as well...but sticking on HC for now to crack the darn sbk.
they must be planning future updates as your image version still looks like it could be a release candidate. :-D
glad to hear theres several builds being pushed tho!
Sent from my SGH-I897 using xda premium
I was on 3.2.1 COM_GEN2, and couldn't upgrade, so went back to 3.2 GEN1 from there going a similar path as you did: 4 updates, and the last being PA_CA. I that time I though "almost there", but found I no longer have spanish language as an option
My first impression: ICS is faster and better looking. But,
Do you know where can I download a language patch to it?
on a side note...fellow rogers user...you jumpin on the one x ?? i just ordered mine
rising power said:
I was on 3.2.1 COM_GEN2, and couldn't upgrade, so went back to 3.2 GEN1 from there going a similar path as you did: 4 updates, and the last being PA_CA. I that time I though "almost there", but found I no longer have spanish language as an option
My first impression: ICS is faster and better looking. But,
Do you know where can I download a language patch to it?
Click to expand...
Click to collapse
I've the same problem, not italian language and "PA_CA" Build.. WHY ??
i have Acer A100 in Russian
and yesterday it updated to 4.0.3
i lost my language in OS and apps
version PA_CA too
((((((((((
ptesmoke said:
on a side note...fellow rogers user...you jumpin on the one x ?? i just ordered mine
Click to expand...
Click to collapse
Hehe cool, when it comes to phones, I need a keyboard, so I actually picked up a bell Moto xt860 and unlocked it. I might be stuck with this one for a while since I hear keyboard android phones don't sell as well as blackberries up here. We will see what happens to RIM...
My other goal is not to sign another contract again, and I have a really sweet deal with Rogers now also...
Sent from my XT860 running ICS
devitos said:
i have Acer A100 in Russian
and yesterday it updated to 4.0.3
i lost my language in OS and apps
version PA_CA too
((((((((((
Click to expand...
Click to collapse
It really looks like PA_CA is geared towards Canada, with only English, French and Chineese (simplified and traditional). I don't know another way of pulling another language, unless you can grab them from the WW 014 package somehow... let me look at it
Sent from my XT860 running ICS
I am very interested - how Canada firmware got in Russia)))
acer have a bug in service
Isn't possible flash directly Acer_A100_AV041_1.014.00_COM_GEN1 ? (to gets languages)
This is the third post today I have read someone say that the build 14 is not official. I have myself and numerous other people received this update OTA from Acer. Unless Acer is beta testing on our devices, you can't call it anything but official. It is the exact same rom ZN posted.
devitos said:
I am very interested - how Canada firmware got in Russia)))
acer have a bug in service
Click to expand...
Click to collapse
I've just buyed my own one here in spain and it comes with the PA_CA firmware as well
My wife's fully stock (4.4.2) N5110 started getting update notifications from Samsung Software Update.
Per the info, it's a 7.61 MB 'device stability and bug fixes' patch that includes security enhancements and StageFright fix.
Is there information on everything installed with this patch?
Will installing this block any future attempts at root / installing a custom ROM? (If she ever lets me; this is solely her device and doesn't care about root/ROMs )
Since this is a wifi only note8 - how vulnerable is it to stagefright if I don't patch? Everything I've read says 'stagefright is more than an MMS vulnerability' but then the details only go into the MMS vuln :|
Thanks in advance and sorry if this has been covered elsewhere - I searched and didn't find anything.
I noticed the update today and decided to install it. It did not take very long to install and the Android version number is still 4.2.2, so it doesn't seem that there is anything major. I have yet to notice any changes, but I haven't used my tablet much today I should note that I am also using the wireless version of the Note 8.0 and I have never rooted this devices.
If I learn anything else I'll post here.
It's too bad that they didn't decide to bump things up to 4.4.4 (could use those Bluetooth fixes that were introduced in 4.4.3) while they were at it.
Anyway, I just noticed that there's a new stock rom posted for the USA variant on Sammobile.com and samsung-updates.com. So this is officially "a thing." Haven't flashed it myself yet and I probably won't; I've moved on to Cyanogenmod 12.1. But it's nice to know that Samsung is still pushing out updates for this thing.
Sent from my GT-N5110 using Tapatalk
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...??
Is this possible and how can it be done? July update is horrible, full of bugs, empty of fixes and has worsened battery life exponentially.
You can if you use the full image : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
But phone might be wiped, so backup your data. And disable OTA after flash so your phone will not install july update again
novak.vujacic97 said:
Is this possible and how can it be done? July update is horrible, full of bugs, empty of fixes and has worsened battery life exponentially.
Click to expand...
Click to collapse
Allowing you to downgrade means they admit to make mistakes and bring up bugs to new updates that are supposed to FIX whatever was wrong until then.
You can revert by flashing a stock image, but note... you'll start up fresh and next months maybe you'll get a fix for what's wrong this month, or you can get even worse. Because ... why the hell shouldn't we make Android One like iOS and ... phones in the One class get Pixel updates... let's give them Pixel updates with mods by Xiaomi... Then why this program, just for monthly security patches with no bug fixes and even more bugs?