I have an HD1907 purchased from B&H that I converted to an HD1901 awhile ago for dual sim purposes and was running great.
I upgraded to android 12 months ago and like many others had fingerprint reader issues.
Just upgraded to the final ROM released with the December security update and while they fixed the fingerprint, I seem to have lost my dual sim capability.
This really sucks.
thetoady said:
I have an HD1907 purchased from B&H that I converted to an HD1901 awhile ago for dual sim purposes and was running great.
I upgraded to android 12 months ago and like many others had fingerprint reader issues.
Just upgraded to the final ROM released with the December security update and while they fixed the fingerprint, I seem to have lost my dual sim capability.
This really sucks.
Click to expand...
Click to collapse
Downgrade to oos11
yes, I probably will, sadly will lose all my state when I do. :/
Related
So, I recently bought a secondhand Google Pixel XL 1st gen. I am using it as a secondary device to manage some Instagram pages I have and to use the camera to take ever so amazing pictures with the best camera on the market (blanket statement covering the Pixel 2 and 3 as well).
Anyways, I've had the phone for about a month and recently the SIM card slot stopped reading SIM cards. No water damage and I have no dropped the phone at all. The phone has actually sat longer than I have used it, as my daily driver is a Note 8. Sometimes, before now, I was switching back and forth between the Pixel and my Note 8. Everything was fine for awhile...
At first I was thinking that Verizon had somehow noticed that I was switching phones on their Network, but then I thought logically about that and considered that Verizon doesn't really care because I'm paying them either way and last time I checked, there isn't a known software check to make sure a SIM is being used on the phone it was purchased with.
Now I'm thinking that it is either the Android Pie update or maybe a security update - currently it's the February 5th installment. Not really sure either way and it's frustrating me on a daily basis and I am not really sure what to do or how to further troubleshoot the issue. Again, no water and drop damage interference since owning the device and the SIM card slot was working up until about 3 weeks ago roughly.
Update: Successfully rolled back to the Jan 5th security patch and nothing changed. Phone still is not reading the SIM. Although, last night before doing so, I popped in my Verizon SIM from my Note 8 and the phone showed the mobile network icon in the status bar for a split second and then it disappeared basically as fast as it showed its face. I'm thinking the phone can read SIMs still, but the tray is screwed up somehow. 19 views and somehow no response...
Just received this OTA on my unlocked s10 plus in US
Do you notice any changes?
Sent from my SM-G975U using XDA Labs
I have an unlocked S10+ purchased in the US. I'm currently traveling in Australia and using their Optus network. Got a notification to install this update. Figured since it was security related, it wouldn't matter. Boy was I wrong. My phone is borderline unusable now unless I pull the SIM out. Trying to find a place to download a previous version of firmware to swap out.
My phone is working flawlessly.
I haven't experienced any issues at all.
Update fixed my camera, slightly more stable WiFi and cellular, battery tho, seems a bit worse. Usually get 2 days at 9-10 sot. Barely hitting 7
Hello,
I have two Z2 Force phones still brand new in the box that I bought last year when Motorola sold them for $99 on their website, they are for ATT and I have read ATT isn't pushing anything past Android 8.0
Is there anyway I can install a custom ROM to get to android 9 or 10? or is that only for factory unlocked Z2 force from Motorola?
Thank you!
cms062407 said:
Hello,
I have two Z2 Force phones still brand new in the box that I bought last year when Motorola sold them for $99 on their website, they are for ATT and I have read ATT isn't pushing anything past Android 8.0
Is there anyway I can install a custom ROM to get to android 9 or 10? or is that only for factory unlocked Z2 force from Motorola?
Thank you!
Click to expand...
Click to collapse
LOL, it was not last year, it was before the last year (November, 2018).
You can get upgraded when you have att sim card in.
Or do a offline upgrade to the whatever the last 8.0 version.
No Android 9 for att version so far.
Verizon and unlocked version can get Android 9
Sent from my LG-LS997 using Tapatalk
cgigate said:
LOL, it was not last year, it was before the last year (November, 2018).
You can get upgraded when you have att sim card in.
Or do a offline upgrade to the whatever the last version.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
lol, oh..didn't realize I've had these phones sitting around for so long, i guess
I use ATT and could put my SIM in...but is there anyway to unlock this bootloader, install TWRP and a custom ROM?
cms062407 said:
lol, oh..didn't realize I've had these phones sitting around for so long, i guess
I use ATT and could put my SIM in...but is there anyway to unlock this bootloader, install TWRP and a custom ROM?
Click to expand...
Click to collapse
You need try to get bootloader unlocking code from Motorola.
Last check a year ago, Motorola/Lenovo not giving the code.
I sold mine two brand new as well.
Sent from my LG-LS997 using Tapatalk
I am currently a Tmobile subscriber and I usually buy my OnePlus phones thru Tmobile. But this time I just purchased the phone outright from OnePlus.com. I received the phone on Mar 31st and everything works except when I go on the Tmobile website it still lists my OnePlus 9 pro as 'unknown phone'. For other people who have purchased their phones directly from Oneplus for use on Tmobile is this normal?? It's been 9 days and I am wondering. I still get 5g speeds and everything but Im an old worry wart. Thanks in advance.
TAMARETTE said:
I am currently a Tmobile subscriber and I usually buy my OnePlus phones thru Tmobile. But this time I just purchased the phone outright from OnePlus.com. I received the phone on Mar 31st and everything works except when I go on the Tmobile website it still lists my OnePlus 9 pro as 'unknown phone'. For other people who have purchased their phones directly from Oneplus for use on Tmobile is this normal?? It's been 9 days and I am wondering. I still get 5g speeds and everything but Im an old worry wart. Thanks in advance.
Click to expand...
Click to collapse
Yes this normal, as both 9 Pro and 7 pro shows as unknown. Most likely is because I have been using the same SIM card since the 6T and taking it out and putting it in the newer model.
Thanks, so much that makes me feel a lot better.
Mine is the same. I think it shows up that way for any device you didn't purchase from T-Mobile. (I could be wrong.)
Also, the same....normal
Same here as well, but what's funny is I recently got a second line with an unlocked device on it as well and it shows up as it's supposed to. But mine has been an unknown device for about 7 or 8 phones now. I recently did upgrade my sim card to the newest version for 5G and it still shows as unknown.
Thanks guys n galz :0-) I just love the phone and it seems to be fine. I get blazing fast speeds and frankly could not be happier with my new phone. As long as I can take my phone anytime anywhere I won't worry.
FWIW ... make sure you have a new SIM card.
To access the Tmo 5G network, you need the current "R" sim card.
steve841 said:
FWIW ... make sure you have a new SIM card.
To access the Tmo 5G network, you need the current "R" sim card.
Click to expand...
Click to collapse
That would be false.
schmeggy929 said:
That would be false.
Click to expand...
Click to collapse
Disagree. The rep made it VERY clear. And the SIMs are colored.
From Tmo support:
While your current SIM card is 5G compatible, it is not capable of using the 5G standalone technology we recently rolled out.
All of my phones that I purchased outside of T-mobile (all of the pixels, the 8pro and now the 9pro) show up as unknown even though T-mobile sells the phones.
I updated my pixel to A13 last week and on restart was prompted to enter my sim lock pin, all seemed well but it wasn't. Somehow, my sim stopped working although my phone recognises it. Could it be the update broke my sim or is it just coincidence?
skinnykins said:
I updated my pixel to A13 last week and on restart was prompted to enter my sim lock pin, all seemed well but it wasn't. Somehow, my sim stopped working although my phone recognises it. Could it be the update broke my sim or is it just coincidence?
Click to expand...
Click to collapse
If you've tried the SIM Card in another phone & it's still not working, my guess is that it's a coincidence.
I'd reach out to your service provider for a new SIM Card, especially if the one you're using is more than a year old, it may not be able to fully take advantage of any/all of the newer/5G Bands on your network.
I know that this is recommended for T-Mobile US.
KOLIOSIS said:
If you've tried the SIM Card in another phone & it's still not working, my guess is that it's a coincidence.
I'd reach out to your service provider for a new SIM Card, especially if the one you're using is more than a year old, it may not be able to fully take advantage of any/all of the newer/5G Bands on your network.
I know that this is recommended for T-Mobile US.
Click to expand...
Click to collapse
I did try my sim in my old Samsung S7 and it didn't work. It just seemed strange that it broke after updating my phone but yes, it most probably is a coincidence
skinnykins said:
I did try my sim in my old Samsung S7 and it didn't work. It just seemed strange that it broke after updating my phone but yes, it most probably is a coincidence
Click to expand...
Click to collapse
FWIW, I've run several betas of 12 & pre & post stable 13,including stable 13 & haven't had any connectivity issues. The SIM is new, used the one that came with the phone.
Since it's not working on another device, I'd chalk it up to pure coincidence.
Before responding, I did a bit of Google-Fu, as I'm sure you did as well & didn't see anything pointing to the update causing the problem.
Now, wireless charging, especially with Google's 2nd Gen charger, that's another story.......