I am intending to purchase a carrier unlocked windows phone either online or while overseas.
Despite the warranty issue which i'm not too worried about, what happens to the update deliveries?
I have a Omnia 7 and updates are triggered by your carrier (if i understand correctly). If I introduce a new phone say a Nokia which they don't sell, will I still receive crucial updates?
If not (which is something i fear), what other way would there be to "force" updates?
Any help and suggestions would be greatly appreciated.
I see no reasons to expect updating problems, zune will find the updates available for your new unbranded phone as it actually finds those for the Omnia...nothing wrong with the fact that the device comes from another country.
It exists few 'tricks' to force some updates (i.e. click "update", wait 3 sec. and unplug dsl cable) which work well, you'll find them in "general" thread i think.
Related
I just wondering as still haven't!
I never got 1.47, I'm still on 1.28. I'm not sure why.
My DS is an unbranded unlocked UK model.
We are certainly not the only people not to get 1.47.
At first I was glad that I did not get 1.47, but now I notice that (so far) only people with 1.47 seem to be getting the recent upgrade.
Least am not the only one! HTC support seems to think I would need to send my phone away for repair to have it updated!
podycust said:
Least am not the only one! HTC support seems to think I would need to send my phone away for repair to have it updated!
Click to expand...
Click to collapse
Seriously. All HTC seem to say is any update news will appear first on Twitter or Facebook, yet when anyone has questioned them on there they deny any knowledge of the update even with proof
The only thing they use social networking for is product spamming and corporate shindig promoting!!
Got a small update months ago which installed an updater, but never got 1.47. Still on 1.28. Unbranded, unrooted.
Interested to learn what HTC told you about returning it...
Yes I got those same updates months ago too! This is what they said after first saying 1.28 was the latest and then me saying I know about some with 1.47
Thank you for your reply regarding your Desire S.
The case there is an update available and you cannot receive it through 'OTA', the device may need to be sent for repair. then your device gets updated to the latest version.
Please confirm the following information in order to be able to book the device for repair:
From which address you wish the collection to happen
On which day you wish the collection to happen (please allow 48 hours’ notice)
The Serial Number of your device. (Serial Number can be found underneath the battery.) I will then book and confirm this via Email and provide further repair instructions:
We can arrange for UPS to collect your device from an address (Mainland UK only) that is convenient for you. UPS can collect on Monday through Friday from 1pm to 5pm. There is no UPS service on Weekends and Public Holidays.
Click to expand...
Click to collapse
Do have in your applications (settings> manage applications> all) an install called Updater version 2.3?
I think - not sure - that this is what was installed by the small update? Or is it for the Market? Terribly tempted to uninstall it and see what happens, eg if it updates again, but to 1.47. Or perhaps just try clear data.
Unfortunately to ignorant to know the risk if any...
Yes I and this what small update was it just updates the FOTA program which updates the phone firmware
podycust said:
Yes I and this what small update was it just updates the FOTA program which updates the phone firmware
Click to expand...
Click to collapse
Say again please?
yes it did install updater version 2.3. if you uninstall it you will be asked to install it again!
DON'T INSTALL 1.47!
Please! If you're looking to depress yourself, google "desire s late sms", look at the hundreds of pages of results, from users all over the world with the same problem.
You lucky ones who are still on 1.28 havent suffered the misery of the problem with 1.47 and the Desire S. Just imagine how much fun could be had, every time you're connected to a mobile data network (GPRS, 3G or HSDPA), knowing that there's a better than 50/50 chance all your 2G functions will stop working. Calls will go straight to voicemail, texts will fail to arrive for hours on end... And then randomly, you'll get a dozen messages at once, from people wondering why you've ignored them all afternoon...
Seriously, stick with 1.28 for now, wait for the next update.
We will need to have 1.47 before we can get 2.10!
fasty said:
I never got 1.47, I'm still on 1.28. I'm not sure why.
My DS is an unbranded unlocked UK model.
We are certainly not the only people not to get 1.47.
At first I was glad that I did not get 1.47, but now I notice that (so far) only people with 1.47 seem to be getting the recent upgrade.
Click to expand...
Click to collapse
can you use wireshark to analyze what the update sever's response is?
as when I've done that it replys {"time_msec":"1317992280856","stats_ok":true,"reason":"FOTACANCEL_NO_MATCH_RULE_FOR_CID","intent":[{"action":"android.server.checkin.FOTA_CANCEL"}]}
as mine is also an unbranded unlocked uk model
podycust said:
can you use wireshark to analyze what the update sever's response is?
as when I've done that it replys {"time_msec":"1317992280856","stats_ok":true,"reason":"FOTACANCEL_NO_MATCH_RULE_FOR_CID","intent":[{"action":"android.server.checkin.FOTA_CANCEL"}]}
as mine is also an unbranded unlocked uk model
Click to expand...
Click to collapse
I'd prefer not to install wireshark right now, but I'm certain that I would get the same response.
There are plenty of other people in the same situation. I'm guessing that HTC may have aborted deployment of 1.47 because they noticed that it caused so many issues.
I assume that the "no match rule for CID" simply means that there are no updates available for our particular software version at the moment.
I've just factory reset my DS in the hope of fixing another issue, and after doing so it politely updated the version of it's FOTA loader but nothing else new.
Starting deployment of the sense 3.0 version to a few users without any explanation seems a bit dumb of HTC unless they are simply beta testing.
I could understand them prioritising those who have already loaded 1.47 as clearly this is causing them the most issues. We just need to hope that they don't forget those if us who are still on 1.28
- Steve
had your phone been rooted before you get it?
helicopterpro said:
had your phone been rooted before you get it?
Click to expand...
Click to collapse
Nope, I don't think so. My phone was new, carrier unlocked "sim-free" version from an authorised HTC retailer in the UK. I was previously using an Orange SIM in it, although recently switched to Three. (Have tried to get update when connected to both)
Why after the Mango update I don't receive the Htc update drive ? I update my phone with the U2M7720
Can Some bodyes help me ?
Assuming you used U2M7720 to update to Mango ISV.
Go and see this thread: http://forum.xda-developers.com/showthread.php?t=1287505
Skip all parts until you reach the "HTC ADDITIONAL UPDATE" part.
There you will find a guide to get the official HTC update, but do keep in mind that at the moment, you will not be able to use applications such as Advanced Config, FileXplorer.
-Xeno
doesn't start
I just read and try the guide, but my Zune doesn't find the HTC Update and I don't want come back to NODO
is there a litle solution for me ?????
I read it somewhere that htc update depends on regions too, which means that not necessarily everybody with htc device will get the same update. I have not gotten any htc update for my mozart, and I live in indonesia. I haven't asked around whether other people have got htc update on theirs, because I think I am the only one using windows phone in indonesia ahahahahahahah.....
As far as I know, people with htc in european and US regions get updates... I am not sure about the people in asian regions. Maybe others can confirm this. What sort of rom and region do you live in?
as you can see from here:
http://wmpoweruser.com/firmware-update-for-htc-mozart-pops-up-did-you-receive-any-notifications/
not everybody got updates either.. just dont worry about it too much
cheers
joseph.sapri has a valid point.
In my case I live outside the USA, but have a T-Mobile HTC HD7, hence why I received the updates early on.
Let us know the ROM and region.
I'm in Italy, but some people that live in Italy have just receive the update, why i don't receive ?
Well, you can try to wait for a while I guess. Since the update is deployed randomly to people, means your neighbor might get the update but you won't.
Have you tried the force update technique?
Otherwise I'm all out of ideas.
I update my phone with the U2M7720 method......but my main problem is that the program usb switch doesn't run on my phone and I think that it's depend on the htc update
Can you link me the thread for program usb switch?
I will see if it works on my HD7.
http://forum.xda-developers.com/showthread.php?t=1271253
ecco il link
So this morning I woke up to a security update message from T-Mobile. So if your interested they are rolling out a security update this morning. Now I'm actually with Metro Pcs but I recently flashed my device with the T-Mobile variant since it has less bloat ware and just ain't garbage as Metro's firmware. So being that Metro is part of the T-Mobile network I'm assuming you will be receiving it as well.
Now as for anyone ever hoping to require root you might want to block this update as I have just done. As you can see from the picture attached they are not giving you an option as in these updates make it harder and harder for someone to find an exploit or a (back door) as many say to aquire root. As as since it has been mentioned that these devices if and do receive the Android Pie 9.0 update it wouldn't be until late 2019 so til then I'm going to keep exploring and working on finding a way to root this device. For noobies, YES I ALREADY HAVE READ THE ANDROID TECH ARTICLES AND YOU TUBE VIDEOS. The switch in developer options will not unlock bootloader and LG does not have these devices on their list of phones even capable to be unlocked. So til then it's back to the grind.
~~~~FUN IS ILLEGAL
Paranoid "security" is purely meant to stifle open source community activity, nothing else (Maybe someone would need this if worked as CIA/MOSAD spy )
Hey, Funisillegal to turn off the automatic update just the toggle in developer options is enough right?
FullAccessForAll said:
Hey, Funisillegal to turn off the automatic update just the toggle in developer options is enough right?
Click to expand...
Click to collapse
No it's not brotha it will still force update just like clicking the unlock bootloader doesn't unlock bootloader
Funisillegal said:
No it's not brotha it will still force update just like clicking the unlock bootloader doesn't unlock bootloader
Click to expand...
Click to collapse
So how do you turn off automatic updates?
And isnt't enough simply to switch updates off from Android regular settings?
Settings->System->About Phone->Security updates (or somehow similar, watching just on my Polish menu)
Funisillegal said:
So this morning I woke up to a security update message from T-Mobile. So if your interested they are rolling out a security update this morning. Now I'm actually with Metro Pcs but I recently flashed my device with the T-Mobile variant since it has less bloat ware and just ain't garbage as Metro's firmware. So being that Metro is part of the T-Mobile network I'm assuming you will be receiving it as well.
Now as for anyone ever hoping to require root you might want to block this update as I have just done. As you can see from the picture attached they are not giving you an option as in these updates make it harder and harder for someone to find an exploit or a (back door) as many say to aquire root. As as since it has been mentioned that these devices if and do receive the Android Pie 9.0 update it wouldn't be until late 2019 so til then I'm going to keep exploring and working on finding a way to root this device. For noobies, YES I ALREADY HAVE READ THE ANDROID TECH ARTICLES AND YOU TUBE VIDEOS. The switch in developer options will not unlock bootloader and LG does not have these devices on their list of phones even capable to be unlocked. So til then it's back to the grind.
~~~~FUN IS ILLEGAL
Click to expand...
Click to collapse
Is anyone even working on a root for this device? Doesn't seem like it, I have one of these phones sealed in box never opened for the off chance someone picks up the charge and needs a stock firmware to toy around with given the phone was BOGO when I picked it up for my DIGITS line.
So far relying on ISLAND and IceBox, and it yields nice results.
Lg has equiped system with many quite useful and convenient features.
Not needed applications are just frozen.
However waiting for brealing from such utilities as KingoRoot.
So far disabled automatic updates hopefully making would-be exploits available for future versions of KingoRoot.View attachment 4747486
Hey guys,
I posted on the other threads but it seems like my concern shifts to be another.
First off: Yes I have tried switching regions with the tutorials. No nothing happened. I switched back to EuEx, no dualism because I don't need it.
Yes I tried every possible EU VPN Tunnel and updating OTA.
Nothing helped.
Now I have searched for my current Firmware, and there is no actual discussion about it. It is CPH2025_11_A.52 I am on the security Patch Level December 2020. So it came to my mind that it could actually be the firmware that prevents the updatingprocess. Is this possible?
With every other EU-Colleague of mine getting at least C59 with EuEX I'm starting to think it's just my phone.
Is there something I can do about it or do I have to wait for a flashable Android 11 zip? Which would ultimately leave me with selling the phone since I purchased it in regards to receiving an android 11 smartphone.
Thanks for reading in advance!
No problem with your version ,its just Oppo s way of doing things.I have cph 2025.11.A50 november security patch.
I reached them and they said i should take my unit to service ,i asked them why?its not broken !
Very wierd solution.
My phone works like a charm ,great performance ,good battery life ,so im happy with the software.
P.s bought phone from Switzerland.
@andreiselegean1984 @CaptainRage while it may not be broken on the hardware level there definitely seems to be something wrong with it, so sending it in is not that weird a solution imho. There surely is some sort of repair service in your country that acts as an official Oppo partner for warranty repairs, so why not just contact them and see if they can help by just flashing the newest software onto it and be done with it. The only hassle being that you'll have to do without it for a couples of days but maybe you still have one of your older phones that you can use instead for the time being...
Well Oppo doesn't seem to be cooperating that much:
We are sorry to know that you didn’t receive the ColorOS 11 update on your Find X2 Pro just yet.
In order to clarify this for you, please allow us to offer you a background explanation.
To make sure everything of the new version can run smoothly and reduce the unnecessary risk of the end-user, the ColorOS 11 update is released in batches. This is a protective measure used in global leave for all the new software versions.That’s why a certain amount of devices don’t receive the update on the announced date. But don’t worry! As your satisfaction is our priority, we at OPPO are doing our best to release the update for your phone as soon as possible. Rest assured that you will receive ColorOS 11 soon.
I appreciate your understanding and wish you a wonderful day!
Click to expand...
Click to collapse
CaptainRage said:
Well Oppo doesn't seem to be cooperating that much:
Click to expand...
Click to collapse
This is just the usual BS the customer service gives you, forget about that. There have to be companies in your country that are official Oppo service partners which do all the repairs that are eligible for warranty. Contact one of them directly and tell them what the problem is and see if they accept it as a warranty repair.
Hello XDA!
First of all, long time lurker, but infrequent poster here. My phone is an Asus ROG Phone 5s Pro running stock and non-beta software and is not rooted. I am reaching out to see if anyone on here who has more technical savvy than me (which is probably most of y'all) can help me figure out how to reinstall a fresh factory image on my Asus ROG Phone 5s Pro or can offer any other possible solutions for my issue.
The reason I am wanting to do this is because I recently installed a software update from Asus that seems to have a persistent issue that is a pretty major problem to me. The issue is that whenever I reboot the phone and plug in headphones and audio plays, but it stutters and BLASTS out of the headphones (multiple sources tried, even happens with system notification sounds). This only happens with wired headphones and never with Bluetooth. I had this happen to me once for less than a half a second and my ears were persistently ringing for about 3+ hours after this and I am certain that it damaged my hearing to a small degree. Because of this I no longer trust to use any headphones with the phone and this is a huge bummer because I use wired headphones A LOT.
I have tried to factory reset the phone several times already and the issue persists through without any restoring of anything during setup (in fact it won't recognize the backup that it created the day before the factory reset), but the issue is still present. I contacted Asus customer support (for which lets just say I have strong feelings on) and explained the issue and they want me to RMA the phone for a hardware issue.
I really do not wish to do this as this means I will have to either switch phones a few times which is always incredibly time consuming or be without a phone for an estimated period of up to 10 days if I do the RMA. I also disagree that this is a hardware issue because of two things: 1) if it were a hardware issue then I would think that the problem would be constant and not happen just once after each reboot and I would think that doing something in the software, i.e. a reboot, wouldn't consistently recreate the problem. Thus I am trying to find a way to "restore" the operating system of this device to see if I can solve what I believe to be a software issue that shouldn't require any RMA.
I have seen that posts that linked official files from Asus before, such as the "AsusUnlock_1.0.0.7_210127_fulldpi.apk" found in the OP of the "Install any custom ROM on ROG Phone 5 / 5s (GSI)" thread here in this very forum. Is anyone aware of any officially sourced files for stock software/firmware for this phone and a process through which I could reinstall it?
I am also open to thoughts and other possible options to consider.
Also I will give bonus points to anyone who can help me figure out how to fix the issue where my Google backup by this very same phone won't restore its own Google backup when going through the setup and can help me restore it. It does recognize a different Google backup for a tablet that is set up for my child to use, so it is not an issue with the restore being completely broken.
Thanks in advance for anyone willing to try and lend a hand.
Hi, here you can find stock firmwares make sure you got for right region.
ROG Phone 5s Pro | Gaming Phones|ROG - Republic of Gamers|ROG Global
Fueled for winning by the latest Qualcomm® Snapdragon® 888+ 5G mobile platform, ROG Phone 5s Pro launches your mobile gaming experience into the next dimension. With an unbelievably responsive 360 Hz native touch-sampling rate, the 144 Hz / 1 ms display brings you the smoothest ever viewing...
rog.asus.com
Yeah, just for additional info for anyone who finds this. I've also been working with ASUS customer support. I was given two links on flashing official firmware:
Unofficial guide on flashing - https://www.asus.com/support/FAQ/1009748/
Official firmware images - https://rog.asus.com/phones/rog-phone-5s-pro-model/helpdesk_bios (same as previous comment above; thanks Teddy)
When I asked why my version is newer than any they currently have listed on the site I was told that it "could be a preview release given directly by Google" (I doubt this as this appeared as an official OTA by Asus that had very specific patch notes to this phone in it) and that because my version is newer than any listed on their site would result in trouble if I tried to flash the newest version listed, but an older firmware than what is currently installed and that I should still just RMA my phone.
For reference my current firmware is RKQ1.210303.002.WW_Phone-18.1220.2201.186 and the latest firmware listed on their site at the time of this writing is WW-18.1220.2111.164.
Great phone (aside from the hearing damage), but utterly useless support.
Still open to thoughts and ideas though if anyone still has any.
You can "downgrade" your firmware by doing a RAW flash directly to version you need OR to any lower version and then install the official ASUS version you want manually. Also need to disable OTA updates to avoid being updated to the latest automatically.
Having the device checked for hardware issues is probably the best idea however.
Andrologic said:
You can "downgrade" your firmware by doing a RAW flash directly to version you need OR to any lower version and then install the official ASUS version you want manually. Also need to disable OTA updates to avoid being updated to the latest automatically.
Having the device checked for hardware issues is probably the best idea however.
Click to expand...
Click to collapse
Could you provide more info on this "downgrade" via "a RAW flash"? Is there a guide or something that will give more info about this?
I think I might be screwed though for the RMA. Customer service says apparently its a Taiwan version and cannot be serviced in the USA and has to be sent to via Taiwan RMA and the page they gave me seems to indicate there are no service centers for ROG Phones; see https://www.asus.com/support/service-center/taiwan#.
Short rant is that I literally spent hours and I mean HOURS (if not possibly days) of my time with Asus customer service and searching online trying to find a US version with US warranty and ultimately getting nowhere and deciding to go with the one I have now. Four months in to a $1700 phone and basically I am stuck with a dangerous headphone jack and no option to fix it other than maybe what you mentioned, Andrologic.
Today has not been kind.
ChrisMills83 said:
Could you provide more info on this "downgrade" via "a RAW flash"? Is there a guide or something that will give more info about this?
I think I might be screwed though for the RMA. Customer service says apparently its a Taiwan version and cannot be serviced in the USA and has to be sent to via Taiwan RMA and the page they gave me seems to indicate there are no service centers for ROG Phones; see https://www.asus.com/support/service-center/taiwan#.
Short rant is that I literally spent hours and I mean HOURS (if not possibly days) of my time with Asus customer service and searching online trying to find a US version with US warranty and ultimately getting nowhere and deciding to go with the one I have now. Four months in to a $1700 phone and basically I am stuck with a dangerous headphone jack and no option to fix it other than maybe what you mentioned, Andrologic.
Today has not been kind.
Click to expand...
Click to collapse
There are links to download RAW images along with guides in the help thread pinned to the top of this forum. You should find what you need there. The RAW's come include flash scripts that does it all for you.
Just curious for opinions while this thread is still going:
Does anyone lean towards my issue being a hardware problem or something else (and if you could be specific and suggest something for me to try about it)?
The reason why I ask is because I personally feel like this is an issue with when the headphone jack initializes output or something because it only ever blasts audio after a reboot and I any audio plays. After it stops and plays again the levels seems to return to normal. I can also reliably make this happen the same way every single time. Finally (and somewhat conspiratorially), the update I installed just before this started to happen had patch notes that included "optimized audio parameters."
My appreciation in advance for any thoughts and insights.