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.
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.
T989UVOH1 - Beginning October 5,2015 the Samsung Galaxy S II will have a software update to Android version* 4.1.2/ Software T989UVOH1 via OTA or Samsung Kies.* This update provides the Stagefright fix.
My phone wanted to update last night. did anyone take the update ? did it lose root ? what happened when it updated.
Right now i'm backing up my stuff and pushing all my contacts to google and everything before hand.
If you do not know what stagefright is then read :
http://www.xda-developers.com/stagefright-explained-the-exploit-that-changed-android/
http://forum.xda-developers.com/android/software-hacking/fix-stagefright-patched-t3173500
- I like the rom i'm on and really dont want to go updating if it breaks my root and everything on my phone.
I found out that i would mostly need to update so im updating now to a new rom SLIMLP
Well I did a little flashing this weekend to see what this update really did. I will say it did nothing. The stagefright v1 and v2 are still active.
The rom is fully bloated to hell. I jumped off the rom after that. Do not update to this build from t-mobile it does nothing.
I wonder if someone can upload the new radio that comes with it.
Last night i got new update.
I can see that they fixed low lvl sound, i dont have problems with clock any more, next few days i will see that they fixed anything more.
October 5, 2017 patch...
anyone geting this?
i added pictouer with colck problem before updating.
https://photos.google.com/photo/AF1QipMGQweIqQu9IQJQpNYtX2M5qKA2qgdgiXq8Jw-Y
https://photos.google.com/photo/AF1QipNPuzUO-CJC00WicsTdNQpFrBZBmv9avNUYY474
My Qualcomm version (Boost Mobile) hasn't received any updates, ever. It's still on the June security patch, SMH.
Also - this device doesn't seem to have any issues that I've noticed, it just works. But I do want the BlueBorne patch, Also the KRACK patch would be nice.
Sigh... Lenovo is so slow...
ATTACK said:
My Qualcomm version (Boost Mobile) hasn't received any updates, ever. It's still on the June security patch, SMH.
Also - this device doesn't seem to have any issues that I've noticed, it just works. But I do want the BlueBorne patch, Also the KRACK patch would be nice.
Sigh... Lenovo is so slow...
Click to expand...
Click to collapse
I have MTK device, XT1771. I got on myne little bit low sound, it was ok but now it is pritty loud and clear sound from him, and fingerprint is better. I didnt try headphones but i think that they are fixed to, i got little lower sound on them, i didnt try them but when i do i will report. xD
Just a hint, If you're using custom recovery DO NOT run the system update. The device will bootloop into recovery, and the only way to restore is wipe data, cache and dalvik, and after that boot into bootloader and type fastboot continue into CMD. This at least worked for me.
PoP*92 said:
Last night i got new update.
I can see that they fixed low lvl sound, i dont have problems with clock any more, next few days i will see that they fixed anything more.
October 5, 2017 patch...
anyone geting this?
i added pictouer with colck problem before updating.
Click to expand...
Click to collapse
ya i got update in my device XT1770
Camera
any bugs in the camera? or does it works fine?
PoP*92 said:
Last night i got new update.
I can see that they fixed low lvl sound, i dont have problems with clock any more, next few days i will see that they fixed anything more.
October 5, 2017 patch...
anyone geting this?
i added pictouer with colck problem before updating.
Click to expand...
Click to collapse
what were the problems with the clock? she froze?
I got the update three days ago and from what I can tell it seems that the issues with clock freezing and alarm not going off are fixed.
When it comes to the camera, the videos that I took were all very dark, but with the update this issue seems to be fixed as well for me. Pictures, well I was never a fan of the quality of the pictures anyway, I don't know.
Request for stock boot and recovery for this update
I need the recovery and boot of this release to carry on to next OTA update via stock recovery ... But fails to do that. After boot is not stock
Are you 100% stock? That's the only way to take an OTA. I know there were builds here to return to stock, but I'm not sure if they if they deleted. I'll have to look around.
Hi
Have Someone X1944-4 latest firmware to share?
if possible retbr (i am from brazil)
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
blasbenoit said:
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
Click to expand...
Click to collapse
Update has landed. Found links on teammt site few moments ago.
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2649/g1699/v133897/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...BND-L24_hw_usa/update_full_BND-L24_hw_usa.zip
http://update.hicloud.com:8180/TDS/...97/f1/full/public/update_data_full_public.zip
MD5 verified numbers ( from my working downloads)
Code:
e75a21769f049430840ea900b11600c4 c:\android\honor_7x\l24-oreo\update.zip
73414b5383e5fb3391e77a13c17dca53 c:\android\honor_7x\l24-oreo\update_data_full_public.zip
122f0e91d77fba6e399300926d1ef289 c:\android\honor_7x\l24-oreo\update_full_bnd-l24_hw_usa.zip
So can I just flash those update files with TWRP and be good to go?
I don't know if that's the stable or not, I've had that version for over a week now.
My update says C567?
I used the teammt firmware finder and, clicking on "Check Firmware Access" get "The firmware is not approved for installation."
This, I believe, means that it's not official.
We can expect the OTA to be pushed in stages, just like the beta, but, hopefully, it'll be complete by end of day this time.
johncro13 said:
I used the teammt firmware finder and, clicking on "Check Firmware Access" get "The firmware is not approved for installation."
This, I believe, means that it's not official.
We can expect the OTA to be pushed in stages, just like the beta, but, hopefully, it'll be complete by end of day this time.
Click to expand...
Click to collapse
Why would it be available if it's not official? I don't get that lol. The app is a little funky.
How long did the staged release of the beta take? Can we expect the update within hours, days, or weeks do you all think?
mparma13 said:
How long did the staged release of the beta take? Can we expect the update within hours, days, or weeks do you all think?
Click to expand...
Click to collapse
I'd say weeks, but that is just a hunch based on my experience with the rollout of the previous two patches... Once again, it would have been nice when Honor USA announced it that they didn't just say "Coming April 30" but instead were a bit more honest about how the release was being pushed out.
They shoyld have said that it will be around a certain week or something cause the frustrating lag is killing me badly and i even have a Oneplus 5t...but still is the worst lag i have seen in since 2013
I think the released update file are for update from oreo beta to oreo stable.
My first attempt to manually flash the update failed to flash the data files, only did the system update. It left me with odd build number and missing the new face-unlock feature.
I installed a second time , from the half installed oreo , and this time it completed fully. Also changed install script to use original file names instead of shortened names.
If anyone does this also please note that you will need to use the oreo flash update section as you will already be on oreo .
mrmazak said:
I think the released update file are for update from oreo beta to oreo stable.
My first attempt to manually flash the update failed to flash the data files, only did the system update. It left me with odd build number and missing the new face-unlock feature.
I installed a second time , from the half installed oreo , and this time it completed fully. Also changed install script to use original file names instead of shortened names.
If anyone does this also please note that you will need to use the oreo flash update section as you will already be on oreo .
Click to expand...
Click to collapse
How did you install it?
allrockedout said:
How did you install it?
Click to expand...
Click to collapse
I used the update oreo section from my guide.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
It was not 100% working. I am not sure if it was the shortened update-file names or because the update files are for beta update.
The update fails at about 70-80% --during the data_update and hw_update-- and then I needed to do factory reset.
After booting into half updated oreo I updated again using same guide, but used the flash update section for oreo.
And I modified the updater-binary to use the full name of updates instead of the shortened names.
Might be able to use full names on nougat update section too, but I was already in oreo, so could not test.
mrmazak said:
I used the update oreo section from my guide.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
It was not 100% working. I am not sure if it was the shortened update-file names or because the update files are for beta update.
The update fails at about 70-80% --during the data_update and hw_update-- and then I needed to do factory reset.
After booting into half updated oreo I updated again using same guide, but used the flash update section for oreo.
And I modified the updater-binary to use the full name of updates instead of the shortened names.
Might be able to use full names on nougat update section too, but I was already in oreo, so could not test.
Click to expand...
Click to collapse
Ok thanks I'm on stock bootloader still locked I'll just wait for official update
yeah....
blasbenoit said:
Good morning guys this is a thread for the people who have received the 8.0 update already today and how is looking so far.
Click to expand...
Click to collapse
Looks like they crapped the bed on the update....
East coast here and so far just crickets.
I'm not worried about it because my 7x is fast and solid so far. Loving this phone since I bought it in January.
It just sucks that there's all this hype about the Oreo release coming Monday and you get all excited and ... Then you fell frustrated
pcaseiro said:
East coast here and so far just crickets.
I'm not worried about it because my 7x is fast and solid so far. Loving this phone since I bought it in January.
It just sucks that there's all this the about the Oreo release coming Monday and you get all excited and ... Then you fell frustrated
Click to expand...
Click to collapse
Well some group is getting it(probably beta testers), because it is on firmware finder
China has a holiday right now. I think they come back to work on the 2nd maybe that's why no update. Im guessing I have no idea.
allrockedout said:
China has a holiday right now. I think they come back to work on the 2nd maybe that's why no update. Im guessing I have no idea.
Click to expand...
Click to collapse
Then why would they be so set on the 1st, shouldn't they have said the 2nd? Lol
Anyone receive official update yet?