I have flashed the uro rom of the galaxy tab on a us sgh-1987 att samsung tab , i inserted my at&t sim card and it will not allow me to make calls . Can some point me in the right direction to fix this. The at&t sim card i am using has voice and data. Or have i not done something properly.
You need to be using a different modem than the one included in the Euro rom. I believe either the Bell Canada or Rogers modems should work to enable voice on ATT. I'm using the Euro JMI rom with the Bell JK5 modem and it works fine for me.
See here: http://forum.xda-developers.com/showthread.php?t=847273
I followed the instructions and for some odd reason the sim that came with my samsung is the only one that will work even though my phone is unlocked and i am using another att sim card that has voice and data.
And when i go to check wireless settings it keeps me me in flight mode.
Using JMIv2 here. Just made a call -- seems fine.
I full flashed JMIv2 over top of JMEv4.
Your not doing something correct.
Also please post in the correct subforum. This in no way has anything to do with android development. This belongs in general. Read much??
Sent from my MoDaCo powered Galaxy Tab.
Pls change the title of your post. It's completely baseless, and it's obvious you did something wrong. Thanks!
mistadman said:
Pls change the title of your post. It's completely baseless, and it's obvious you did something wrong. Thanks!
Click to expand...
Click to collapse
How so? Its clearly a question, he has a question mark after the million exclamation marks...
Sent from zombie infested Gingerbread.
rushstatus1 said:
I have flashed the uro rom of the galaxy tab on a us sgh-1987 att samsung tab , i inserted my at&t sim card and it will not allow me to make calls . Can some point me in the right direction to fix this. The at&t sim card i am using has voice and data. Or have i not done something properly.
Click to expand...
Click to collapse
Weren't you on other threads contradicting people about 3g+ voice using service menus?
I am confused about your setup - what model tab? I thought you had t-mobile tab.
Anyway, on an at&t tab use the bell i9000 modem. Check your apn and network mode afteryou reboot.
The iemi blocking by t-mobile stops people from using data.
And besides clubtech does a perfect write up to get everything working. SEARCH IS YOUR FRIEND.
Good point!
Thank you
i appreciate the advice in pointing me in the right direction. but it seems like a lot of you aren't very newbie knowledge friendly. i posted what i was experiencing in the hopes of getting a point in the right direction. not a solution. turns out my Sim card was corrupted. all i had to do is go and grab a new one. i apologize if my question seemed too basic and trivial to you . but it turns out that i just made a logical investigative approach to my problem . I followed rotos guide to the letter so i assumed that AT&T had also latched on to the idea of imei blocking. I have done several apps for the android market ,and am constantly wanting to learn more . some of you have great skill sets but no patience for new comers. but all in all i will not post in the forum anymore if it involves being downgraded for simply asking for help, isn't this why we have forums for the techs the geeks the cpu nerds. who would have thought amongst intelligent people we still deal with aristocracy .
i did have a t-mobile tab and then returned and bought att tab and it works just fine now . like i said in the forum i am learning so please bear with me
Aristocracy has and will always be common among us nerds blame it on our our societal influences.
Regardless of that, people are more upset about you not searching the forum/threads. Please use the search option , it will save us all time and wasted bandwidth. Also post in the correct sub forum. This section is meant for what it was named for, development only. There is a general/ Q&A section.
Once again, I can't stress the search feature enough. It will seriously help. I promise.
Not flaming you, just trying to help direct you
i appreciate it thank you
hey guys im on roto's v4 and it works for both tmous and att
Hello All,
I realize this issue has been addressed, and there are a few short threads on the topic. Frankly, I am surprised that there is not more chatter regarding the lack of Android 6.0 - Marshmallow for Nexus 6 devices purchased through T-Mobile!!!!!!!!!!!!!!
I am no expert, but would not consider myself in the "noob" category. I am fully aware of the wider LTE spectrum required for T-Mobile Nexus devices, i.e. Band 12, as well as carrier enabled Wi-Fi calling over T-Mobile's network.
I just can't seem to understand how almost 2 months later, my d*mn Nexus 6 is still on 5.1.1. ?!?!?!?
Does anyone have anymore insight regarding this? Can we discuss and find out WHY they are still in their "Testing" phase? Honestly, I'm glad that they are doing the properly required due diligence and QA testing, but 2 months?!?!?!?!? COME ON T-Mobile/Google!
At this point, I would NOT be surprised to get 6.0 on my Note 5 before my Nexus 6. Wait, on second thought, I doubt it. Will probably get it after the Note 7 comes out.
And please don't tell me I can flash the factory image from https://developers.google.com/android/nexus/images?hl=en I am fully aware and we have all gone this route plenty of times. I simply want to start a meaningful discussion that may shed some light on WHAT in the WORLD is taking T-Mobile so long to finish validating their Marshmallow build, or if it's not truly that, then what is the hold up??????
Do you really think your going to get a meaningful discussion here? Especially when your ranting your head off throwing caps around and cursing in the thread title?
Regardless of if its what you want to hear or not... Google made the update available for you the instant it came out. If you have chosen not to take it, then that was your choice.
Wait patiently, or make the choice to go take the update... Those are your options.
Cursing in the title? I took the courtesy of censoring it, if you haven't noticed and Hell isn't exactly a "bad word". Relax man, it isn't directed at you or anyone else for that matter. If you have nothing "meaningful" to say, then why waste time even replying. Didn't realize there were so many sensitive females on this website.
It's quite obvious you don't like to read things in it's entirety prior to replying to a stranger. I would recommend Neurontin, or maybe Zoloft. Might help with the impulse control.
Punctuation exists for a reason. If I want to complain about a Nexus branded device not receiving a major update two months after release within the context of a website that exists to discuss just these types of issues, I will.
Again, Neurontin... ENN, EE, YOU, ARR, OH, ENN, TEE, EYE, ENN. Talk with your shrink about it. Might help get your head out of your rectum. Unless of course your father prefers it that way.
Then by all means, carry on.
Anyhow, spoke to a T-Mobile tech support representative, not that they have ever been much help historically, but apparently they are testing T-Mobile specific applications to ensure that they play well with Android 6.0 (He Mentioned Visual Voicemail, T-Mobile My Account, etc.). Does that mean that the Nexus 6 devices purchased via T-Mobile will have a disparate build? Based on what this guy said, it looks like it.
Another reason why I didn't just blindly flash the Universal builds. Not to mention, many T-Mobile customers who have already done so, are experiencing bugs with their devices and/or broken functionality.
Android1126 said:
Cursing in the title? I took the courtesy of censoring it, if you haven't noticed and Hell isn't exactly a "bad word". Relax man, it isn't directed at you or anyone else for that matter. If you have nothing "meaningful" to say, then why waste time even replying. Didn't realize there were so many sensitive females on this website.
It's quite obvious you don't like to read things in it's entirety prior to replying to a stranger. I would recommend Neurontin, or maybe Zoloft. Might help with the impulse control.
Punctuation exists for a reason. If I want to complain about a Nexus branded device not receiving a major update two months after release within the context of a website that exists to discuss just these types of issues, I will.
Again, Neurontin... ENN, EE, YOU, ARR, OH, ENN, TEE, EYE, ENN. Talk with your shrink about it. Might help get your head out of your rectum. Unless of course your father prefers it that way.
Then by all means, carry on.
Click to expand...
Click to collapse
That was a great delivery, lmao.
I don't give a **** if you say hell. Just saying if you want the reasonable conversation your claim to, your doing a pretty ****ing bad job of starting it.
Your Nexus branded devices DOES have an update. You're just waiting for it to be sent to you, by all means continue to do so.
scryan said:
I don't give a **** if you say hell. Just saying if you want the reasonable conversation your claim to, your doing a pretty ****ing bad job of starting it.
Your Nexus branded devices DOES have an update. You're just waiting for it to be sent to you, by all means continue to do so.
Click to expand...
Click to collapse
Son, you really DO NOT know what you are talking about. Go look at the Factory Image page at https://developers.google.com/android/nexus/images?hl=en , now go to Shamu, and read the images (might take a bit of scrolling, so resist the urge to give up and rant and rave, in an attempt to teach me etiquette). Do you see where it says "5.1.0 (For T-Mobile ONLY) (LMY47M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28E)" or "5.1.1 (For T-Mobile ONLY) (LYZ28J)" or 5.1.1 "(For T-Mobile ONLY) (LYZ28K)" or "5.1.1 (For T-Mobile ONLY) (LYZ28M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28N)"??
Again, impulse control. Do a little research before replying. Not to mention VoLTE and Cat 14 LTE that only T-Mobile uses (in this country, and at this time). Not saying that the universal build absolutely WON'T work, but there are more than a few stories out there stating that exact opposite. I for one, would like to wait for a build that is catered to the frequencies of my Mobile network for the simple fact that it will address all of those incompatibility issues.
Anger issues? Abused as a child? Watch your dirty little mouth. Also, learn some basic grammar "I don't give a **** if you say hell. Just saying if you want the reasonable conversation "your" claim to, "your"doing a pretty ****ing bad job of starting it"?
I think you meant "you" and you're"
How do we go from hell to F***? You're one sick little boy.
Moderator, please close this thread, as you deem fit.
Also, many people who have downloaded the universal image, wiped their devices, and installed the update, have had to root, downgrade their Radio for 5.1.1. just to get an LTE signal and WiFi calling as well as a number of other features to work properly.
Again, read before you reply.
Android1126 said:
Son, you really DO NOT know what you are talking about. Go look at the Factory Image page at https://developers.google.com/android/nexus/images?hl=en , now go to Shamu, and read the images (might take a bit of scrolling, so resist the urge to give up and rant and rave, in an attempt to teach me etiquette). Do you see where it says "5.1.0 (For T-Mobile ONLY) (LMY47M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28E)" or "5.1.1 (For T-Mobile ONLY) (LYZ28J)" or 5.1.1 "(For T-Mobile ONLY) (LYZ28K)" or "5.1.1 (For T-Mobile ONLY) (LYZ28M)" or "5.1.1 (For T-Mobile ONLY) (LYZ28N)"??
Again, impulse control. Do a little research before replying. Not to mention VoLTE and Cat 14 LTE that only T-Mobile uses (in this country, and at this time). Not saying that the universal build absolutely WON'T work, but there are more than a few stories out there stating that exact opposite. I for one, would like to wait for a build that is catered to the frequencies of my Mobile network for the simple fact that it will address all of those incompatibility issues.
Anger issues? Abused as a child? Watch your dirty little mouth. Also, learn some basic grammar "I don't give a **** if you say hell. Just saying if you want the reasonable conversation "your" claim to, "your"doing a pretty ****ing bad job of starting it"?
I think you meant "you" and you're"
How do we go from hell to F***? You're one sick little boy.
Moderator, please close this thread, as you deem fit.
Click to expand...
Click to collapse
theres only one build for marshmallow. no matter which carrier you use, you use the same build. yes, wifi calling works on it. lte, volte, and everything else too. im on tmobile as well.
Android1126 said:
Anger issues?
Click to expand...
Click to collapse
Yes. You have them.
https://support.t-mobile.com/thread/116433
Please note, as documented by tmobile support, no tmobile specific build is presented because beginning with 6.0 its a unified build.
Android 6.0 (Marshmallow) is a unified build and is the same version across all carriers. WiFi Calling is baked into the OS.
Click to expand...
Click to collapse
simms22 said:
theres only one build for marshmallow. no matter which carrier you use, you use the same build. yes, wifi calling works on it. lte, volte, and everything else too. im on tmobile as well.
Click to expand...
Click to collapse
simms22, thanks for the advice. I do realize that, and I have read as much for the most part. My main point was really an attempt at trying to gain an understanding as to why Nexus 6 devices from T-Mobile have not yet been updated to Marshmallow.
I appreciate your comment. I have also read about a number of incompatibility issues when flashing the universal build, so I like to err on the side of caution, especially considering that I use my Note 5 as a daily driver. Also, not trying to do a full wipe just yet (I realize I can do so without, but from what I have read, that is what is causing the bugs/incompatibility).
Like I stated earlier, the T-Mobile tech. rep. stated that there will be a T-Mobile specific build out soon. Now what that contains, I cannot say. Just trying to gain some insight. It could just be T-Mobile bloatware, though I am fairly certain they are addressing some of the known issues that are affecting a portion of Nexus 6 devices running Marshmallow on T-Mobile.
Thanks again.
scryan said:
Yes. You have them.
https://support.t-mobile.com/thread/116433
Please note, as documented by tmobile support, no tmobile specific build is presented because beginning with 6.0 its a unified build.
Click to expand...
Click to collapse
You just linked me to a site where a bunch of amateurs are discussing flashing a non standard build. Where, by the way, a person poses the question "a) Is that a T-Mobile Build? I am not seeing Wi-Fi calling related section anywhere"
Really, do you read anything before posting replying?
I would look at this page that T-Mobile has published.
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Do you see what it says? If you need help reading (and then pausing to process), let me know.
Here is a recap for people with learning disabilities (no offense if you really have one, seriously).
UPDATE PROCESS 3 stages. Current: Stage 2 T-Mobile testing.
Please man, just stop replying. Because I can keep making you look like your mother dropped you on your head all night.
scryan said:
Yes. You have them.
https://support.t-mobile.com/thread/116433
Please note, as documented by tmobile support, no tmobile specific build is presented because beginning with 6.0 its a unified build.
Click to expand...
Click to collapse
Also, do you see where the correct answer states "Flashing with a T-Mobile rom is going to require you to unlock your bootloader...." Key words "T-Mobile ROM"
Where does it say that all builds are unified starting at Android 6.0? That may be the case for all other carriers, but it is PRETTY obvious, that this does not apply to the T-Mobile build for 6.0.
Android1126 said:
You just linked me to a site where a bunch of amateurs are discussing flashing a non standard build. Where, by the way, a person poses the question "a) Is that a T-Mobile Build? I am not seeing Wi-Fi calling related section anywhere"
Really, do you read anything before posting replying?
I would look at this page that T-Mobile has published.
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Do you see what it says? If you need help reading (and then pausing to process), let me know.
Here is a recap for people with learning disabilities (no offense if you really have one, seriously).
UPDATE PROCESS 3 stages. Current: Stage 2 T-Mobile testing.
Please man, just stop replying. Because I can keep making you look like your mother dropped you on your head all night.
Click to expand...
Click to collapse
Your not really making me look like I have been dropped on my head, your making yourself look like a raving lunatic.
I gave you the same answer as simms, other than the fact that I linked to the official support site where the answer marked as correct supports what I said.
Android1126 said:
Also, do you see where the correct answer states "Flashing with a T-Mobile rom is going to require you to unlock your bootloader...." Key words "T-Mobile ROM"
Where does it say that all builds are unified starting at Android 6.0? That may be the case for all other carriers, but it is PRETTY obvious, that this does not apply to the T-Mobile build for 6.0.
Click to expand...
Click to collapse
Flashing ANY rom is going to require a bootloader unlock, so yes flashing a tmobile rom would require a bootloader unlock.
Other carriers then T-Mobile have a unified build? lol, check your definitions there man
u·ni·fy
ˈyo͞onəˌfī/
verb
past tense: unified; past participle: unified
make or become united, uniform, or whole.
It's not united or uniform if its different for tmobile... the entire basis of a unified build is it's the same for everyone.
This thread is too good. Nothing but multiparagraph rants and personal insults from you about how others have anger issues. :laugh:
Android1126 said:
Also, do you see where the correct answer states "Flashing with a T-Mobile rom is going to require you to unlock your bootloader...." Key words "T-Mobile ROM"
Where does it say that all builds are unified starting at Android 6.0? That may be the case for all other carriers, but it is PRETTY obvious, that this does not apply to the T-Mobile build for 6.0.
Click to expand...
Click to collapse
6.0 is one build...I'm pretty sure everyone else that has upgraded by now have already said that...if I take my "sprint" nexus 6 and put a t-mobile sim in...and I have 6.0 after it realizes, hey, I'm on t-mobile...wifi calling will pop up and t-mobile service will work...and before you try to say I'm wrong or t-mobile knows better...why did this work when I tried just that to help someone with the same issue
scryan said:
Your not really making me look like I have been dropped on my head, your making yourself look like a raving lunatic.
I gave you the same answer as simms, other than the fact that I linked to the official support site where the answer marked as correct supports what I said.
Flashing ANY rom is going to require a bootloader unlock, so yes flashing a tmobile rom would require a bootloader unlock.
Other carriers then T-Mobile have a unified build? lol, check your definitions there man
u·ni·fy
ˈyo͞onəˌfī/
verb
past tense: unified; past participle: unified
make or become united, uniform, or whole.
It's not united or uniform if its different for tmobile... the entire basis of a unified build is it's the same for everyone.
This thread is too good. Nothing but multiparagraph rants and personal insults from you about how others have anger issues. :laugh:
Click to expand...
Click to collapse
Yes, I know how to flash an image and/or a ROM, unlocking the bootloader has nothing to do what this conversation, other than I do not want to wipe my device Einstein. Do you know how to SSH into a RHEL Server across a minimally perforated firewall to change jre environments for global profile enabled Linux applications on let's say, an Apache Web Server LBP?
I know how Linux works. Android is child's play.
You are completely ignoring the fact that there is a reason that T-Mobile Nexus 6 devices have NOT been given the green light for Android 6.0.
Really, why do you think that is? If it were such a simple solution, then it wouldn't have been 2 months and no update. Clearly, there are some technical details, that are probably WAY above your intrinsic level of comprehension, that are delaying the release of this image.
If you are too dense to comprehend that, then continuing this conversation is futile.
If anyone has any insight or information as to the delay, feel free to let me know.
Thanks.
A2CKilla said:
6.0 is one build...I'm pretty sure everyone else that has upgraded by now have already said that...if I take my "sprint" nexus 6 and put a t-mobile sim in...and I have 6.0 after it realizes, hey, I'm on t-mobile...wifi calling will pop up and t-mobile service will work...and before you try to say I'm wrong or t-mobile knows better...why did this work when I tried just that to help someone with the same issue
Click to expand...
Click to collapse
Brother, no offense, I'm not following you. The reason Wi-Fi calling pops up when you throw a T-Mobile SIM card into a Sprint phone, is because Wi-Fi calling is baked into Android 5.1.1.
Sorry, not sure what point you are trying to make. You do know that on the Google Developers Factory Images page, there are T-Mobile specific builds for the Nexus 6 right?
Even Verizon users, just started receiving 6.0 in this past week. The only other time this happened was with the Samsung Galaxy Nexus, and we all know what happened there. Exact same thing I am talking about. As a matter of fact, (will link to it later), we have already had an in-depth discussion about this on a different forum on this site. There are in fact different builds for different carriers.
The Universal build WILL work, no one is saying that it won't, but keep doing some research and you will see that many (and I mean many) users have reported incompatibility and/or broken functionality when flashing the Factory Images on their T-Mobile and also Verizon devices.
As far as what you are saying about a T-Mobile SIm card working in a Sprint Nexus 6. I don't think anyone is arguing that. We all know that to be the case, although I can guarantee you that if you put a Verizon SIM card into your Sprint/AT&T/T-Mobile Nexus 6, it will NOT work.
I know because I have Verizon service (for work), and I have tried. That is less about the phone being locked, and more about non Verizon IMEI's being blacklisted. My point is, that we know that the Nexus 6 is unlocked. That is not the question I am asking here.
Android1126 said:
Brother, no offense, I'm not following you. The reason Wi-Fi calling pops up when you throw a T-Mobile SIM card into a Sprint phone, is because Wi-Fi calling is baked into Android 5.1.1.
Sorry, not sure what point you are trying to make. You do know that on the Google Developers Factory Images page, there are T-Mobile specific builds for the Nexus 6 right?
Click to expand...
Click to collapse
For LP yes.
Android1126 said:
Even Verizon users, just started receiving 6.0 in this past week.
Click to expand...
Click to collapse
Yup, VZW took their sweet ass time testing and distributing it too.
Yet check that developer image page... and where is the VZW MM image?
Just because the carrier has not pushed it as an OTA does not mean it's a different build, because M is unified. So even though it took until last week for VZW to push it to their phones.... It's the same unified build that has been out this whole time.
Android1126 said:
As far as what you are saying about a T-Mobile SIm card working in a Sprint Nexus 6. I don't think anyone is arguing that. We all know that to be the case, although I can guarantee you that if you put a Verizon SIM card into your Sprint/AT&T/T-Mobile Nexus 6, it will NOT work.
I know because I have Verizon service, and I have tried. That is less about the phone being locked, and more about non Verizon IMEI's being blacklisted. My point is, that we know that the Nexus 6 is unlocked. That is not the question I am asking here.
Click to expand...
Click to collapse
I have a non VZW phone btw, and on VZW with a VZW sim. It works fine. You need to do your reading on this one, lots of us don't have Verizon issued phones, its only ATT that is carrier locked.
Many people had issues getting VZW to activate their nexus 6, this was not technical as much as it was people bringing their phones to VZW and VZW declining. People also had issues not getting their discount for buying a phone outright, but from early launch you could stick a VZW sim into a nexus 6 and use it
See this droid life article from launch
http://www.droid-life.com/2014/10/31/nexus-6-working-on-verizon-out-of-the-box/
Enough ranting now...
Thread closed