I recently bought a T-mobile M8 which was imported from USA and had sim unlocked but i don't know other details except that its not rooted (that i checked with supersu). May be it was imported as scrap since it's an old model and may be it was unlocked from t-mobile, i just have no idea. Now the phone is asking me for a few updates which describe to tell me that these are intended to prepare phone for marshmallow update (currently it's on jellybean). Should i allow update to progress or not? i don't want to loose sim unlock.
Related
Hi all, this is my first tread here, i am glad i found this forum.
I am from Brazil and i just got a Unlocked AT&T samsung focus.
The phone is unlocked, all i had to do is insert the sim card and star using it.
I am using a carrier called TIM.
When i go to setting> about it says that the carrier is AT&T
Version: 7.0.7004.0
So my question is: Since i am not using a AT&T simcard but my phone shows that my carrier is AT&T, will i get the updates by the schedule of ATT?
I see on the table "Where's my phone update?" and it says that focous is still testing the updates, so i am guessing that i will be reciving it by the ATT schedule, is this correct?
I did not recived any updates yet, not even the first one, is that normal?
by the way, i dont want to unbrand this phone, unless you guys say that i wont get the updates if i dont.
Thanks alot!
That is correct, you will not get updates until AT&T approves them since the device is branded by AT&T.
If my device was originally AT&T branded but then bootloader unlocked, then S-off, and super-CID....... ... and now has latest developer firmware flashed with Custom 5.01 ROM , like LeeDroid's latest Sense 7 -- will that phone be "carrier unlocked" if I were to try to use another SIM like from T-Mobile??
I don't have another carrier SIM to test it -- planning to sell
jcrompton said:
If my device was originally AT&T branded but then bootloader unlocked, then S-off, and super-CID....... ... and now has latest developer firmware flashed with Custom 5.01 ROM , like LeeDroid's latest Sense 7 -- will that phone be "carrier unlocked" if I were to try to use another SIM like from T-Mobile??
I don't have another carrier SIM to test it -- planning to sell
Click to expand...
Click to collapse
No. SIM locking is separate from CID/MID locking. Unfortunately, since you have flashed the most recent firmware, the one hack that used to work is probably unsafe to attempt at this point. Instead, you will need to get an unlock code from AT&T or buy one from a service. (or inform the buyer that it is still SIM locked to AT&T, but that's going to cut the value a lot)
I have an s-offed att branded phone on t-mobile. It's running an old ruu t-mobile. I just downloaded an update to lollipop. I can just run the update?
Possibly...
you need to check a few things... what's your phone's cid set to? (you can see this in your boot loader screen).
As a general rule, I've found that if I run t-mobile radio's I have more problems than if I run either a native AT&T or the DEV edition radio and then t-mobile firmware on-top of that radio... my phone doesn't seem to do some of the hspa bands from t-mobile...
check your cid, before you do much of anything else...
If he's running a tmo ruu, i would assume he's running super cid.
I would also have to assume that he's changed the mid to tmo?
scifan, have you considered using DFS to set your bands?
avg2424 said:
.
changed the mid to tmo?
DFS to set your bands?
Click to expand...
Click to collapse
What is the mid and DFS?
I have a Verizon branded m8 and am using a t-mobile mvno
(straight talk) SIM. I am considering changing RoMs from viper one to one off if the t-mobile thread in order to solve this problem of random service disconnections. Should I switch to a different Ruu? Should I have changed the RUU when I was on stock?
I apologize if the this should be on another or is own thread.
Thanks so much!
kyedmipy said:
What is the mid and DFS?
I have a Verizon branded m8 and am using a t-mobile mvno
(straight talk) SIM. I am considering changing RoMs from viper one to one off if the t-mobile thread in order to solve this problem of random service disconnections. Should I switch to a different Ruu? Should I have changed the RUU when I was on stock?
I apologize if the this should be on another or is own thread.
Click to expand...
Click to collapse
DO NOT, repeat DO NOT try to "convert" your Verizon M8 to T-Mob (with T-Mob RUU). The partitioning (possibly hardware) is different. The T-Mob RUU won't work, and may result in a permanent radio brick.
I'm not sure what is causing the service disconnects. Does the issue occur if you only use 2G and 3G? You may consider looking at enabling the proper LTE bands used by T-Mobile. From what I see, the Verizon M8 supports the proper bands that T-Mob uses for 2G and 3G. However, the VZN version only supports one of the two LTE bands (Band 4) used by T-Mob (Bands 4 and 17). Enabling LTE band 17 may or may not help. The missing support for LTE Band 17 may be related to your disconnect issues, but that's just a theory.
The hitch here, is that trying to enable LTE Band 17 requires s-off, which costs $25 by sunshine app (if you are not already s-off). And its not a sure solution, so may be money wasted.
You can take a look at the following threads, on how to enable bands on the Verizon M8. But I don't personally vouch for these:
http://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
http://forum.xda-developers.com/htc-one-m8/general/unlock-bands-qualcomm-device-phone-t2880239
Awesome thanks. I paid the 25 dollars for s-off already to root the phone. Sunshine works like a charm.
I'll check out the links you provided. I have a feeling your theory is correct. You described how I felt the problem was but lacked the knowledge to produce words to describe. Thanks again.
I don't know whether this is the right thread to ask this question but if you do know kindly advise me; i recently bought a T-mobile M8 which was imported from USA and had sim unlocked but i don't know other details except that its not rooted (that i checked with supersu). May be it was imported as scrap since it's an old model and may be it was unlocked from t-mobile, i just have no idea. Now the phone is asking me for a few updates which describe to tell me that these are intended to prepare phone for marshmallow update (currently it's on jellybean). Should i allow update to progress or not? i don't want to loose sim unlock.
I recently bought a T-mobile M8 which was imported from USA and had sim unlocked but i don't know other details except that its not rooted (that i checked with supersu). May be it was imported as scrap since it's an old model and may be it was unlocked from t-mobile, i just have no idea. Now the phone is asking me for a few updates which describe to tell me that these are intended to prepare phone for marshmallow update (currently it's on jellybean). Should i allow update to progress or not? i don't want to loose sim unlock.
I recently bought a T-mobile M8 which was imported from USA and had sim unlocked but i don't know other details except that its not rooted (that i checked with supersu). May be it was imported as scrap since it's an old model and may be it was unlocked from t-mobile, i just have no idea. Now the phone is asking me for a few updates which describe to tell me that these are intended to prepare phone for marshmallow update (currently it's on jellybean). Should i allow update to progress or not? i don't want to loose sim unlock.
Hi
I have been able to flash the unlocked non carrier specific firmware on several Verizon Samsung phones over the past few years. Through my employer, I was able to get a free Motorola One 5g UW that I want to take and use on ATT. I know it has the antennas. I can put my sim in, and it shows cricket, but it is locked through Verizon. Is it possible to flash a Motorola from one carrier specific firmware over to another like the Samsungs ? Verizon says it will unlock after 60 days, but even still, it will have Verizon bloatware on it. Thanks in advance.
It doesn't work
Radio in AT&T and VZ versions are different.
Moreover, both bootloader are dead locked and there's NO WAY to unlock