I got an Omnia 7 on Virgin Mobile. Once I got it connected to Zune it updated to 7008 (pre-NoDo). Since then there have been no further updates.
I then put my Vodafone sim in it as this is my main account so I'd rather use that. The phone must be sim/network unlocked as it worked straight away with my Vodafone sim. I notice that Vodafone have released the latest update but my phone still isn't picking up any updates.
So, even though Vodafone don't currently sell the Omnia 7 (the do have a couple of other Windows 7 phones), will I still get the update or will I only get it if I put my Virgin sim back in?
You'll still be able to update even without a SIM. Microsoft is currently holding back the update for Samsung phones (again) to fix issues with updating.
day2die said:
You'll still be able to update even without a SIM. Microsoft is currently holding back the update for Samsung phones (again) to fix issues with updating.
Click to expand...
Click to collapse
Ok, that explains it. I went into the diagnostic menu to check if anything was locked but they are all set to disabled.
sparkymark75 said:
Ok, that explains it. I went into the diagnostic menu to check if anything was locked but they are all set to disabled.
Click to expand...
Click to collapse
ye.... i am waiting for the update
Related
Hi,
i've bought the 8x 10 days ago and after i've activated it i got some update which pumped the OS version to 8.0.10211.204 and everytime i check for update i got the message that i'm already up to date , although the GDR2 update is available for All Unlocked Devices such mine , what may be the problem ? any other one have an unlocked device and didn't get the update yet ?
Thanks
I have an unlocked HTC 8X too and I still haven't got the GDR2 update and it happens the same thing to mine. What's wrong?
none here either.. What's the os number for the update
There was an error in GDR2 for HTC 8X which bricked the phone (the audio chip overheated after a longer while of playing music or video and the phone got to unresponsive state, in many cases it needed to be sent to a service center). Therefore, HTC pulled the update and is now working on a fix.
wizaard said:
There was an error in GDR2 for HTC 8X which bricked the phone (the audio chip overheated after a longer while of playing music or video and the phone got to unresponsive state, in many cases it needed to be sent to a service center). Therefore, HTC pulled the update and is now working on a fix.
Click to expand...
Click to collapse
Are you sure about that? I mean... I still see people on the net getting the GDR2 update, and still getting some problems with it. Does it have to do with an update that I recently got (not gdr2) that updated the radio on my phone? Radio software version now is 1.14b.
Waiting
I have also waiting for GDR2 update..
all other lumia devices has received it ..
HTC seems to be pushing the update out again.
International 8X wasn't using it when the update first started then I checked for an update, but that was when they stopped so it said it was up to date. Earlier today I checked and it updated just fine.
It was two WP updates and an HTC update.
8.0.10327.41
8.0.10327.77
HTC Update
Radio: 1.17b
Bootloader: 0.0.3030.0(173542
So far I haven't gotten any issues, but have been using my One until now so lets see!
If anything check for an update if you havent gotten it yet, just to see.
Exactly, yesterday the HTC 8X started getting GDR2 update again, apparently the sound issue is fixed (because the bootloader and firmware are higher versions in comparson with the original, buggy GDR2 for 8X). I have had no problem so far, but Data Sense is still missing.
wizaard said:
Exactly, yesterday the HTC 8X started getting GDR2 update again, apparently the sound issue is fixed (because the bootloader and firmware are higher versions in comparson with the original, buggy GDR2 for 8X). I have had no problem so far, but Data Sense is still missing.
Click to expand...
Click to collapse
I haven't got the GDR2 update yet, for my unlocked 8X in India. I had flashed the stock Asia ROM on it (although it originally had a European ROM). It was built for Orange, UK.
Firmware 1532.20.20100.707
Radio 1.13b
Bootloader 165610
mangojain said:
I haven't got the GDR2 update yet, for my unlocked 8X in India. I had flashed the stock Asia ROM on it (although it originally had a European ROM). It was built for Orange, UK.
Firmware 1532.20.20100.707
Radio 1.13b
Bootloader 165610
Click to expand...
Click to collapse
I have the GDR2 update and until now, the only bug i saw is when i'm on a call, i get "SIM ERROR".. The phone stops detecting the sim card! I have to wait a few minutes until the phone recognises the card again :/
i got the update yesterday and i'm currently installing it , hope everything goes well
try removing and reinserting the SIM...I think the SIM error is just a coincidence. Also, try putting a small piece of tape or two on the back of it. There were some old posts about people having issues. I put some tape on mine when I first got it and never had a problem.
Also, Lucky!!!! It still hasn't hit T-mobile Branded devices in the US
How do i put the tape on the sim? Can you help me?
the error is getting more frequent
edit - I tried to cover the back of the sim card, (the zone with the logo from vodafone) and i still got the error.
Finally available here in Mauritius. So far no problems. The update run well and the battery seems far better even if need some more time to be sure about that.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Omfg. Unbranded 8x in Australia and still nothing... too frustrating.
I had it unlocked almost 3 months ago it a Sprint phone. Im using Tmobile but i can't get any software updates it will show on my top notification bar on phone but when i try to download it, nothing it won't download. The company that unlocked did they mess it up? I'm very new at this. When i shut my s8plus off and back on a screen comes on home screen I sent a screenshot what is says all the time i turn it back on I have to hit update successful ok...don't make no sense to me it did it after they unlocked it for me. I know my S8plus is a great phone but it very behind on updates and security patch. Please help me. I call the company that unlocked it says nothing they did lol...well they done something wrong for when i shut it off and back on that screen keeps coming on...Thank you. I went to Tmobile being better network and unlimited and the bill one monthly cost the same.
eek88dj said:
I had it unlocked almost 3 months ago it a Sprint phone. Im using Tmobile but i can't get any software updates it will show on my top notification bar on phone but when i try to download it, nothing it won't download. The company that unlocked did they mess it up? I'm very new at this. When i shut my s8plus off and back on a screen comes on home screen I sent a screenshot what is says all the time i turn it back on I have to hit update successful ok...don't make no sense to me it did it after they unlocked it for me. I know my S8plus is a great phone but it very behind on updates and security patch. Please help me. I call the company that unlocked it says nothing they did lol...well they done something wrong for when i shut it off and back on that screen keeps coming on...Thank you. I went to Tmobile being better network and unlimited and the bill one monthly cost the same.
Click to expand...
Click to collapse
Try moving to the unlocked firmware or update it manually through Odin.
Thank you but i dont know how to do that. I'm new at this I'm learning. If you could help i appreciate it.
Occurs to every phone that gets unlocked from the original carrier. Even though it's quite dumb. My suggestion is to continue to read and learn more about the device. However if you can locate the proper tmo build for your phone.. Should be CRB7 or higher. Maybe CRB9 you can update to the latest version through the SD card if you have one. I stress that if you have any issues with how you can get into recovery mode, or updating in this manner, do not attempt until you feel comfortable doing this. The quick and easy way would be to switch to the Sprint SIM and then you can get the updates over the air. If you unlocked the phone this should not be a problem.
Try to use my old Sprint SIM card not activated. Says no data connection or network. I have a SD card. I want to do this. I know how to get into recovery mode etc...with power button and volume up and Bixby button.
So a few weeks ago I bought a pixel for my son from someone local. It was very cheap and my son was using it for school using his mobile data. Today I have then tried to use the phone as I await for delivery of another handset and am faced with some issues. First the phone won’t connect to the WiFi. It’s currently running Android 8.1.0 May security patch and no matter what WiFi wont connect. At times it will say saved network but won’t connect. I have tried to reset the phone but alas no luck. The other issue is that phone is sim unlocked and can use my ee and 3uk SIM cards but the oem option states “connect to the internet or contact your carrier”. Unfortunately I cannot get the person who sold me the phone and all I remember is he told me he bought it from Very UK. Any suggestions please to fix this?. I as under the impression only phones which are sim locked have locked bootloader and also any ideas on how to fix my WiFi thanks.
marvi0 said:
So a few weeks ago I bought a pixel for my son from someone local. It was very cheap and my son was using it for school using his mobile data. Today I have then tried to use the phone as I await for delivery of another handset and am faced with some issues. First the phone won’t connect to the WiFi. It’s currently running Android 8.1.0 May security patch and no matter what WiFi wont connect. At times it will say saved network but won’t connect. I have tried to reset the phone but alas no luck. The other issue is that phone is sim unlocked and can use my ee and 3uk SIM cards but the oem option states “connect to the internet or contact your carrier”. Unfortunately I cannot get the person who sold me the phone and all I remember is he told me he bought it from Very UK. Any suggestions please to fix this?. I as under the impression only phones which are sim locked have locked bootloader and also any ideas on how to fix my WiFi thanks.
Click to expand...
Click to collapse
Seems like you've bought a Verizon locked phone. Those phones has locked bootloaders and recently there was a tutorial on how to unlock those bootloaders. So it can't be done on the traditional way. Here's the tutorial: https://www.google.se/amp/s/forum.x...unlock-bootloader-verizon-pixel-t3796030/amp/
You say you're running may security patch see if there's an update first to June. The non Verizon phones got that already on Monday.
Another thing you could try is to do a factory reset and don't restore any backups at all. Because some backups tries to restore previously remembered wifi. So try that and connect to the wifi. If all this doesn't work then you could try to enroll into Android P beta and see if that fixes it. If that doesn't work then it's an hardware defect. If you cannot get a hold of the person who sold you it then I'm sorry to say that's probably why he sold it to you cheap as he probably knew about the problems it was having. I personally would try to get a hold of him first.
Arju said:
Seems like you've bought a Verizon locked phone. Those phones has locked bootloaders and recently there was a tutorial on how to unlock those bootloaders. So it can't be done on the traditional way. Here's the tutorial: https://www.google.se/amp/s/forum.x...unlock-bootloader-verizon-pixel-t3796030/amp/
You say you're running may security patch see if there's an update first to June. The non Verizon phones got that already on Monday.
Another thing you could try is to do a factory reset and don't restore any backups at all. Because some backups tries to restore previously remembered wifi. So try that and connect to the wifi. If all this doesn't work then you could try to enroll into Android P beta and see if that fixes it. If that doesn't work then it's an hardware defect. If you cannot get a hold of the person who sold you it then I'm sorry to say that's probably why he sold it to you cheap as he probably knew about the problems it was having. I personally would try to get a hold of him first.
Click to expand...
Click to collapse
hmm many thanks. How do i tell its a verizon device as its currently working with a 3 uk and ee sim card. Am just installing the android P better now and does this resolve the wifi issue because without wifi I wont even be able to follow the bootloader unlock guide above.
marvi0 said:
hmm many thanks. How do i tell its a verizon device as its currently working with a 3 uk and ee sim card. Am just installing the android P better now and does this resolve the wifi issue because without wifi I wont even be able to follow the bootloader unlock guide above.
Click to expand...
Click to collapse
Bootloader unlock has nothing to do with carrier. If you could use 3 UK Sim then you're fine. Unlocking bootloader is only needed to flash custom ROM with some exceptions. Are you able to turn on WiFi and see your wifi but not able to connect or does it not turn on at all?
Arju said:
Bootloader unlock has nothing to do with carrier. If you could use 3 UK Sim then you're fine. Unlocking bootloader is only needed to flash custom ROM with some exceptions. Are you able to turn on WiFi and see your wifi but not able to connect or does it not turn on at all?
Click to expand...
Click to collapse
Hi thanks WiFi can be turned on but it won’t connect. At times it says connected and just saves the network. Mobile data is working fine so completely lost, and now trying to flash the P beta.
Just tried android p and same issue. WiFi will try and connect and just end up with saved but it won’t actually connect. Any other ideas please?
marvi0 said:
Just tried android p and same issue. WiFi will try and connect and just end up with saved but it won’t actually connect. Any other ideas please?
Click to expand...
Click to collapse
Have you tried pressing the wifi name and then press forget and try to put in the wifi password again. Is it the same issue on all wifi? Like at home, school, friends home or only at home? If it happens everywhere then I don't have any more ideas. My thought would be that it's a hardware defect. Is there no chance of getting hold of the previous owner?
Arju said:
Have you tried pressing the wifi name and then press forget and try to put in the wifi password again. Is it the same issue on all wifi? Like at home, school, friends home or only at home? If it happens everywhere then I don't have any more ideas. My thought would be that it's a hardware defect. Is there no chance of getting hold of the previous owner?
Click to expand...
Click to collapse
Yes tried all that different WiFi connections no luck at all. I will try and call google tomorrow but chances are they will need the receipt which I have absolutely no way of getting phew.
marvi0 said:
Yes tried all that different WiFi connections no luck at all. I will try and call google tomorrow but chances are they will need the receipt which I have absolutely no way of getting phew.
Click to expand...
Click to collapse
They would probably only need the IMEI number, but if it's out of warranty they'll refer you to a repair center. Wish you all the best and hope that they'll be able to fix it. Let us know what Google says if you do contact them. Keep us updated please.
Arju said:
They would probably only need the IMEI number, but if it's out of warranty they'll refer you to a repair center. Wish you all the best and hope that they'll be able to fix it. Let us know what Google says if you do contact them. Keep us updated please.
Click to expand...
Click to collapse
Thanks will update you as soon as I have spoken to them. The person I bought it from did say it was only bought last year from Very UK and it also looks mint. Has anyone had any dealings with Google RMA with phones without receipt?
Hello
I'm running a completely stock Pixel that was originally purchased from verizon, which was then carrier unlocked then moved to AT&T. It still has a locked bootloader.
The other day I recieved the 9.0 OTA. Everything works on my phone except the radio modem. There is absolutely no cellular service now. Trying to make a call reports "radio off".
- I've rebooted
- Cycled both data and airplane modes on and off with long breaks in between
- Reset network settings
- Spent hours online with google tech support.
- Swapped sim cards with another phone on my account. The sim is good. The problem is with the 9.0 update
Since I haven't seen any other reports of the cellular modem dieing from the update, I'm wondering if it's because I have a verizon version which was carrier unlocked? Perhaps the update re-carrier-locked my phone? I don't have a verizon sim to test the theory out..
Anybody have any other ideas how I can get my phone up and running again?
Thanks!
Someone told someone else that they need to leave the SIM in place during the upgrade. I have no idea if that's true, and that other person hasn't responded.
Did you leave yours in?
post-mortem said:
Someone told someone else that they need to leave the SIM in place during the upgrade. I have no idea if that's true, and that other person hasn't responded.
Did you leave yours in?
Click to expand...
Click to collapse
Yes, mine was in
I did finally get it to work thankfully!
I was just preparing to downgrade back to 8.1 via the April OTA. I just finished downloading the update, and installing ADB. When I enabled USB debugging on the phone and plugged it into my laptop, the cell modem sprang to life. Not a single ADB command issued or anything else. Very strange
Too bad that in my frustration I went and ordered a Note 9. Should be a fun device anyways
Glad you got it working! I know that had to be incredibly frustrating!
I don't know if anyone else has noticed, but after I updated to the latest OTA update (1.25.617.4) I can no longer access call forwarding settings nor call waiting settings. It gives me error saying 'Network Error or sim card error' when trying to view either. I thought it was an issue with my sim cause I just used the one from my HTC 10 so went to AT&T and got a new one only to have same issue. Did a factory reset and same issue. After that I figured it could have possibly been the update, so I used the ROM exe from HTC to get back to 1.21.617.3 and can access those settings again. It was nice to get VoLTE, but I don't want to lose some settings access to get that.
If anybody has had the same issue, have you found a fix other then going back to 1.21.617.3 or staying on 1.25.617.4 and not being able to access call forwarding and call waiting?
Thanks
Interesting. Mine is completely normal with the same SIM card from my HTC 10 as well. Have you tried wiping the cache partition? That actually helped me get VoLTE on my HTC 10.
Here's a link how to do it in case you don't know...
https://support.t-mobile.com/docs/DOC-25804
holz75 said:
Interesting. Mine is completely normal with the same SIM card from my HTC 10 as well. Have you tried wiping the cache partition? That actually helped me get VoLTE on my HTC 10.
Here's a link how to do it in case you don't know...
https://support.t-mobile.com/docs/DOC-25804
Click to expand...
Click to collapse
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I use AT&T.
Yusuke14 said:
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I used AT&T.
Click to expand...
Click to collapse
I know, but it's just instructions (from T-Mobile) on how to do it on your HTC 10.
No issues here, on t-mobile and used same sim as HTC 10. I know it doesn't resolve your issue, but maybe there is an issue with the update and AT&T. See if anyone else on AT&T has same issue.
I'm on Verizon and I get the following when I try to go to either Call forwarding or Additional Settings. It never gets any further.
Have not tried going to these on the previous OTAs.
mr_salvador said:
No issues here, on t-mobile and used same sim as HTC 10. I know it doesn't resolve your issue, but maybe there is an issue with the update and AT&T. See if anyone else on AT&T has same issue.
Click to expand...
Click to collapse
I was hoping to hear from others on AT&T (and other networks) by posting here. Seems T-Mobile is ok and Verizon has a similar but different issue.
Yusuke14 said:
Yeah, tried that as well. I don't know if it matters but I see that link is from T-Mobile, I use AT&T.
Click to expand...
Click to collapse
Yusuke14 said:
I was hoping to hear from others on AT&T (and other networks) by posting here. Seems T-Mobile is ok and Verizon has a similar but different issue.
Click to expand...
Click to collapse
I don't know if I mentioned it before but I'm on AT&T, and everything is normal.
I'm on AT&T, U12+ on 1.25 firmware (+ Viper 1.01), SIM card is from HTC 10 (actually even further back than that, same SIM card since 2014 or 2015).
No issues accessing call forwarding / call waiting settings. All of those features are working for me (forwarding to YouMail, waiting definitely works, so does conference/merging calling) and also now VoLTE.
You mentioned it didn't work on 1.25 even after factory resetting. Were you modded in any way? So you RUU'ed back to 1.21 and it works. Have you tried OTA'ing back to 1.25 and seeing if it now works? I'm just trying to think of anything. Sorry dude, that stinks. I'm on 1.25 and heavily modified and it all works...
I get the same error message as well. But im on T-mobile. Really doesn't matter to me personally as i don't use settings in there.
But you're not the only one that gets the error.
turbo jjjang said:
I'm on AT&T, U12+ on 1.25 firmware (+ Viper 1.01), SIM card is from HTC 10 (actually even further back than that, same SIM card since 2014 or 2015).
No issues accessing call forwarding / call waiting settings. All of those features are working for me (forwarding to YouMail, waiting definitely works, so does conference/merging calling) and also now VoLTE.
You mentioned it didn't work on 1.25 even after factory resetting. Were you modded in any way? So you RUU'ed back to 1.21 and it works. Have you tried OTA'ing back to 1.25 and seeing if it now works? I'm just trying to think of anything. Sorry dude, that stinks. I'm on 1.25 and heavily modified and it all works...
Click to expand...
Click to collapse
Hadn't done anything to phone at the time, was completely stock, nothing done at all as of yet. Only thing i have done now after going back to 1.21 is unlock the bootloader and so far that's all. Going to try taking the OTA to 1.25 again and see if it wasn't just some fluke of nature.
Will update afterwards.
Edit: went back to 1.25, getting same error and can't access call forwarding or call waiting settings.
JWhetstone02 said:
I'm on Verizon and I get the following when I try to go to either Call forwarding or Additional Settings. It never gets any further.
Have not tried going to these on the previous OTAs.
Click to expand...
Click to collapse
I'm still on the original firmware (no rush to update as of yet) and I get the same situation when accessing those settings.
1.25 RUU is available. I'm on T-Mobile with an Unlocked boot loader and custom kernel however everything works on this end.
I have the 1.25 update and I'm on ATT, and I apparently have the issue as well. No bother, though, since I don't use call forwarding.
And, this is the sim card from my 10.
I am on AT&T and my firmware 1.25.617.4 and everything working fine here
I realize this thread is a a little old but I am having the same issue. I am on AT&T. The only tweaks I have made is to unlock the bootloader and disabled tethering guard. The problem existed on 1.25.617.4 and persists on 1.30.617.2. I thought the problem was a provisioning issue with AT&T. After multiple calls with them and a couple with HTC, I found this thread. Of course I should have stopped here first. I actually need call forwarding and calling AT&T to have them manually provision it every time I need it just won't cut it. Has anyone been able to figure this out?