Related
I got ahead of myself and installed a radio update on a rooted handset running MoDaCo 2. I ran the updater in update mode and than it prompted a restart.
I restarted and it installed the package than next time i looked the screen was dead. the whole units been dead eversince. no reaction to USB/Power, or to any key combo startups...
Please tell me that this is not the end?
probably dead
from what i have read on this issue, if you flash a GSM radio it runs on a higher voltage and kills your phone.
if you have the insurance they most likely wont be able to tell what broke it.
well there isnt anything you can do. I hope you have insurence. this is the only way that we have found to brick these phones, is to flash the GSM radio.
good luck
arcataslacker said:
I got ahead of myself and installed a radio update on a rooted handset running MoDaCo 2. I ran the updater in update mode and than it prompted a restart.
I restarted and it installed the package than next time i looked the screen was dead. the whole units been dead eversince. no reaction to USB/Power, or to any key combo startups...
Please tell me that this is not the end?
Click to expand...
Click to collapse
Sorry, this is the end.
I didn't think MoDaCo had a v2 for CDMA heros...maybe thats why it told you to update the radio. Nothing that you can do, I think this is the only thing that has killed a Hero is someone not paying attnetion and updating the radio to a GSM one.
Please no one take this the wrong way, but...
At least once a week there's a thread like this, where someone has fried their phone by flashing the wrong package.
Accidents do happen... that's the way it goes. I've been in the tech industry for over 20 years and I've certainly done my share of "what does this do?", but there are pages and pages (and more pages) relating to the process involved in hacking around on your Hero phone and while it is getting easier to do due to the great work by the devs found here in this forum, reading and comprehension of exactly what it is you're doing should always be your #1 step.
Read, download files, read again, verify that you have the correct items, read some more and then start the process.
It's like the old woodworking saying, measure twice, cut once.
To the OP, it sucks that your phone got fried, but one can hope this serves as another warning to others.
There us definitely a modaco 2.0 cdma. What radio update did you use?
adelaney said:
There us definitely a modaco 2.0 cdma. What radio update did you use?
Click to expand...
Click to collapse
It doesn't matter what he used. There are zero radio updates for the CDMA Hero, thus there is no opportunity, at all, to flash something back to the phone that would work.
If you don't know what you're doing, you shouldn't be doing it. It's as simple as that. If you do it anyway, you should expect to get burned.
posguy99 said:
It doesn't matter what he used. There are zero radio updates for the CDMA Hero, thus there is no opportunity, at all, to flash something back to the phone that would work.
If you don't know what you're doing, you shouldn't be doing it. It's as simple as that. If you do it anyway, you should expect to get burned.
Click to expand...
Click to collapse
im sorry to do this because im totaly not into flaming but dude you are a real jerk every post I see from you is condecending and rude. yes you should be sure you know what your doing before you do it but jesus man how did you learn? where you born with total knowledge of the android system? I have posted this to you before, but once again why post anything if you can not be helpfull?
wtphoto said:
im sorry to do this because im totaly not into flaming but dude you are a real jerk every post I see from you is condecending and rude. yes you should be sure you know what your doing before you do it but jesus man how did you learn? where you born with total knowledge of the android system? I have posted this to you before, but once again why post anything if you can not be helpfull?
Click to expand...
Click to collapse
+1
10 Char limit my butt....
wtphoto said:
im sorry to do this because im totaly not into flaming but dude you are a real jerk every post I see from you is condecending and rude. yes you should be sure you know what your doing before you do it but jesus man how did you learn? where you born with total knowledge of the android system? I have posted this to you before, but once again why post anything if you can not be helpfull?
Click to expand...
Click to collapse
+1000 ..... After reading a couple foul posts from this guy yesterday, I did a search for all of his posts and at least 3/4 of them are condescending and rude, in addition to being completely unnecessary and unhelpful.
Why do you come here and post when you have nothing positive to add and nothing nice to say. Seriosly, get some anger management and dont chime in unless you plan to help and be constructive.
rockcrawler said:
+1000 ..... After reading a couple foul posts from this guy yesterday, I did a search for all of his posts and at least 3/4 of them are condescending and rude, in addition to being completely unnecessary and unhelpful.
Why do you come here and post when you have nothing positive to add and nothing nice to say. Seriosly, get some anger management and dont chime in unless you plan to help and be constructive.
Click to expand...
Click to collapse
+1....
was I constructive and helpful?
jk
to OP:
sorry dude... if u have a Sprint CDMA Hero
and you messed with the RADIO
IT is the end of that phone... dead!
As was advised before, take your phone to a Sprint store and fain ignorance. Say, "For the life of me, I tried to turn it on the other day and it just won't respond!" The techs will fart with it for two hours, calling Sprint's techs and attempting every trick in the book to flash it before finally replacing it with a heartfelt apology. Don't tell them anything that you did to it. Just let them make the determination.
posguy99 said:
It doesn't matter what he used. There are zero radio updates for the CDMA Hero, thus there is no opportunity, at all, to flash something back to the phone that would work.
If you don't know what you're doing, you shouldn't be doing it. It's as simple as that. If you do it anyway, you should expect to get burned.
Click to expand...
Click to collapse
We've all been down this road. Maybe not with flashing a phone, but with other things as well. That's called "learning from your mistake." He got a bit too enthusiastic and had a lapse in judgment...it happens to all of us, including me.
He probably thought he was flashing the MoDaCo CDMA 2.0 ROM for HTC Hero and just accidentally picked up the MoDaCo GSM 2.0 ROM for HTC Hero. Unfortunately, the problem is that the GSM Hero and CDMA Hero are named just that, HTC Hero. There is no real designation to the average user. Even the accessories like batteries between the GSM Hero and the CDMA Hero are different...causing an average user to make a mistake and buy the wrong accessory (got close in buying a battery for the GSM Hero because it was labeled as compatible with "HTC Hero"...only problem was it was for the GSM Hero and not the CDMA Hero, but nowhere on the site said that.)
Go easy on the guy...it's unfortunate, but it happened and now he's learned to be more careful in the future.
tkirton said:
We've all been down this road. Maybe not with flashing a phone, but with other things as well. That's called "learning from your mistake." He got a bit too enthusiastic and had a lapse in judgment...it happens to all of us, including me.
He probably thought he was flashing the MoDaCo CDMA 2.0 ROM for HTC Hero and just accidentally picked up the MoDaCo GSM 2.0 ROM for HTC Hero. Unfortunately, the problem is that the GSM Hero and CDMA Hero are named just that, HTC Hero. There is no real designation to the average user. Even the accessories like batteries between the GSM Hero and the CDMA Hero are different...causing an average user to make a mistake and buy the wrong accessory (got close in buying a battery for the GSM Hero because it was labeled as compatible with "HTC Hero"...only problem was it was for the GSM Hero and not the CDMA Hero, but nowhere on the site said that.)
Go easy on the guy...it's unfortunate, but it happened and now he's learned to be more careful in the future.
Click to expand...
Click to collapse
So curiosity kills me here. If 1.6+ has CDMA support in the future could we potentially have 1 set of roms for both devices?? I guess that is probably just wishful thinking due to other differences, doesn't change the fact the radio is still different and a different driver, not just kernel level stuff.
Ignore me i make less sense as i ramble.
Kcarpenter said:
So curiosity kills me here. If 1.6+ has CDMA support in the future could we potentially have 1 set of roms for both devices?? I guess that is probably just wishful thinking due to other differences, doesn't change the fact the radio is still different and a different driver, not just kernel level stuff.
Ignore me i make less sense as i ramble.
Click to expand...
Click to collapse
Theoretically, yes. The ROM should be able to determine which radio is in there and set the settings accordingly (including loading the correct driver).
But, that's in theory. Not sure if that is how this going to play out at 2.1 (since that's the next release for our phone).
wtphoto said:
where you born with total knowledge of the android system?
Click to expand...
Click to collapse
Hardly. I learn something every day.
But it doesn't take "total knowledge of the Android system" to know that:
(A) This over here isn't meant for my phone
(B) People repeatedly post saying "don't do it!"
(C) People who do it anyway report bricking their phone
should lead to:
(D) I really shouldn't do that.
It just takes normal reasoning ability.
I have zero problem with someone who says "gee, I don't understand the difference, will you tell me?"... but the one who decides to do something, I am going to assume the same of him that I would hope he assumes of me.
That he has a clue.
People who don't have a clue should be expecting to be reminded of the fact. This is how people *learn*. Conversely, if I make some stupid mistake, I hope someone pokes ME about it, too.
XDA is a great resource. If only more people would actually use it.
We now return you to your regularly scheduled fora.
To OP:
Do what they said and play it ignorant at a repair center, they will have no clue what happened and give you a new phone.
Well I have insurance so maybe that is why but who knows.
Don't worry OP I did the same mistake, just keep reading and you will be fine. Don't be afraid to get back into the modding scene, just read up before you try anything next time, and maybe create a thread to verify you have a solid process before doing it, once you learn everything that you need to be successful.
arcataslacker said:
I got ahead of myself and installed a radio update on a rooted handset running MoDaCo 2. I ran the updater in update mode and than it prompted a restart.
I restarted and it installed the package than next time i looked the screen was dead. the whole units been dead eversince. no reaction to USB/Power, or to any key combo startups...
Please tell me that this is not the end?
Click to expand...
Click to collapse
Okay...once you get your phone back from Sprint and you want to mod it again, my suggestion is to stick to the Hero CDMA subforum for your ROMs. All are guaranteed not to brick your phone.
The Darktremor has a list and links to updated ROMs.
Thanks for the info guys!
there are no sprint stores near by but I should be able to call support about it.
I know its a no no but they wouldn't be able to tell if the MEID was 0ed out would they?
arcataslacker said:
Thanks for the info guys!
there are no sprint stores near by but I should be able to call support about it.
I know its a no no but they wouldn't be able to tell if the MEID was 0ed out would they?
Click to expand...
Click to collapse
No...without actually getting into the phone, they can't tell if you messed with it. And since the phone is dead, they won't be able to tell you tried to mod it. Just do what everyone here says and play ignorant.
I am going to give my sister my Hero when I get my EVO and I was asking her if she wanted me to keep it rooted and keep the roms up to date and she said yes. When I give her my hero and she takes it to sprint to have them port her # over to it will they have to ruu it to do that or will they just leave the phone alone and punch a few things in on their kiosk things to change the #. Thanks for the help!
Crap. I was perusing the general thread and still though I was over there. Mods please move this to general. Thanks and sorry for my stupidity.
Thomas1218 said:
I am going to give my sister my Hero when I get my EVO and I was asking her if she wanted me to keep it rooted and keep the roms up to date and she said yes. When I give her my hero and she takes it to sprint to have them port her # over to it will they have to ruu it to do that or will they just leave the phone alone and punch a few things in on their kiosk things to change the #. Thanks for the help!
Click to expand...
Click to collapse
Just demand that they keep it at 1.5; they won't have to RUU, they'll just have to essentially "reactivate" it.
No it doesn't matter if it's rooted at all.
I'm mailing it to her and she isnt the most tech savvy person so she wouldnt know at first if they RUUed it or not because I'm running a 2.1 rom. Im just wondering what they would do if you brought it in and didnt say anything and wanted them to activate it on your number.
Thomas1218 said:
I'm mailing it to her and she isnt the most tech savvy person so she wouldnt know at first if they RUUed it or not because I'm running a 2.1 rom. Im just wondering what they would do if you brought it in and didnt say anything and wanted them to activate it on your number.
Click to expand...
Click to collapse
They can't say nothing why don't you just call in and just do it for her?
thatguythatdid said:
They can't say nothing why don't you just call in and just do it for her?
Click to expand...
Click to collapse
I would but I dont really know what I'm doing with phone activation stuff. Only time I've dealt with activating phones is when they are brand spankin' new so I dont really know how activating an old phone or someone elses phone on your number is. Sorry for my lack of knowledge and general noobness on this subject.
Or activate it from sprints website..
Activating by phone is incredibly easy.
If you've switched your EVO to your line already, it's really going to be a matter of her calling and asking to have a swap performed. They'll ask for the imei/esn, possibly have her use an unlock code to reprogram it (although last time I didn't even have that) and then reboot.
Takes about 3 minutes and the service person will tell her what to do step by step.
Just make sure to specify that this is a SWAP and not an upgrade.
Ok sweet. I figured it would be decently easy. Thanks for all the help guys
cant you activate the phone online using the esn if so that would be the easiest way to activate it for her
boredmug said:
Or activate it from sprints website..
Click to expand...
Click to collapse
this
12345
so how did it work for you?
I have moved his over to the appropiate section and copied and pasted my question.
I am new to this forum and apologize for my noobness in advance as i wasn't sure either to post this here or in the Android Software and Hacking General section and i appreciate any comments as i understand i am new here and have contributed nothing to this forum. Here is my dilemma, i recently purchased a t mobile g1 from a friend about two weeks ago because i was interested in the android OS. Being in the UK it is locked to the T-mobile network which my existing sim is orange. I understand that there was a developers ROM that was released (codenamed holiday (adp 1.1)) which allows other networks to be used on the g1 e.g orange etc as its a developer version. I was wondering what compatible ROMS for the g1 (htc dream) that would allow me to use my orange sim. Again i really do appreciate nay comments and help i receive and understand i have not contributed to this community and it is highly rude to ask for something when given nothing.
Changing the ROM on your device will not unlock it so that you can use it on any network. You need to get an unlock code for your device. T-Mobile US will give these out to their subscribers but I don't know about your carier. If they don't you can get it online too. They will need your phone's IMEI to generate the code. Just put in the new SIM and it will prompt you for the code regardless of the ROM you have.
isnt there such a thing as a hardware unlock though if i use a custom rom?. I brought this phone from a friend so i doubt phoning t-mobile will help get me a code.
p.s. cheers for taking the time to comment
No, I'm fairly sure the only way to unlock this device is what I posted above.
i thought you just needed a t-mob sim to login and then you were free to choose after this whole rooting/flashing thing.
its already a long time ago, so i might confuse a lot and its only that what i think to know. nothing sure..
i wanted an android phone and my friend was saying i culd get his off him and i thought that be a perfect time to get into the android os and stuff, i wasnt ure if i coulld by rooting/flashing that id be able to use another network thats why i wondered if i flashed it to a deveopler rom the adp1 one i could us another sim, i will look into the method beav_35 put but im not sure on any reputable sites to trust to do this method.
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