Database Develop

TMOTouch Pro 2 Radio 3.45.25.14 on Touch HD

I have searched both google and this forum and have not found any relevant information so I am hoping someone might know the answer to this. I have the Touch HD in NYC working on Tmobile with no 3G service. It appears that Tmobile now has the Touch Pro 2 with 3G service. I called Tmobile and they confirmed that it has the 1700/2100 bands. I then called HTC and was told that the radio can/may unlock the needed bands to run on Tmobiles high speed service. So....has anyone tried this? The radio version for the Tmobile Touc Pro 2 is 3.45.25.14 but I cant find it available anywhere to give it a try. Maybe it's lucky I didnt find it as I dont really know the effect it would have on my phone.
So....any thoughts?

OK. I now found a tmobile test version shipped with radio 3.44.25.17
I figured since noone seems to want to take the time to answer I would
just see what I can figure out.
Using NBHextract I was able to get to, from what I can assess is the radio file,
02_GSM.nb
I then found another program that supposedly should help to create a new nbh file with just the radio. I followed the instructions including a text file with the following inside:
Blackstone
00000000
3.44.25.14
USA
300,02_GSM.nb (I do not know if 300 is correct for the HD)
It did create an NBH file, when I tried to run it all I got was an error code "0058002"
I have no idea what the error code means and I do not know what else I can do to try and make this work.
Anyone have any suggestions as to where I might have gone wrong?
Is it just that you cannot use the radios interchangeably between the 2 devices??

bugdeyez said:
noone seems to want to take the time to answer
Click to expand...
Click to collapse
You should read that first :
http://forum.xda-developers.com/showthread.php?t=521206 (sticky on this forum)
Where you find that :
Security Unlock lets you flash radios from other devices... technically speaking you can flash any radio, but some will brick it (such as Topaz) - however, Diamond, Raphael and Kovsky should all be fine. It can also be an insurance policy against evil radios - people who had the Kaiser radio from hell will know what I mean.
Click to expand...
Click to collapse

as CaiCai says you will need security unlock your HD.
this will cost you £10 gbp read the thread, as you have minimal posts.
Please also be aware this isn't a helpdesk, if you ask a question there's no guarantee it's going to be answered with your 1st 1 1/2 hour of asking
I'd suggest trying some patience, some people actually do have a life away from this forum, I know it doesn't appear that way sometimes, but we do try to escape the cords that bind us..
Personally I cant see how unless they included the hardware to enable the extra frequencies it could possibly work how you want. But I can hex edit the radio after you've done security unlock.
If you read this very forum there is a thread on radios, in fact there's two.

CaiCai: thanks for your straight forward answer and info. I will look into the things you suggested.
Fards:
If I am reading into your post incorrectly, forgive me, but I just sense as if your response has a tinge of attitude. You are absolutely right, i am impatient. However I was not disrespectful about it. I just explained my experience with the methods i tried in attempting to apply the new radio.
That being said, the two radio threads from what ive read, dont address this kind of question. I will reread them to be sure. In regards to your statement about the phone not having the physical capability to work on those bands, there are some people that have postulated that it may be more of a low level programming issue. Also as I said I spoke to someone at HTC and he said it is possible for a radio to allow a phone to work on additional frequencies.
Thanks for your suggestions also. I will look into unlocking the phone as you suggested. I was under the impression I had already done that, but as you see, I am still relatively new to this. Ive been around for over a yr and half, just not many posts. Also, how would hex editing the radio file help in the inatallation of it? I havent heard any references made to that before.
Thanke again fpr taking the time to respond.

As stated previously by others you need to security unlock your device first. Info on this is available here. Radio's from other devices which are known to work on the HD with this security unlock can be found here. Once your device is security unlocked it will state 'Security unlocked' along the top of bootloader screen.
The radio you mention 3.44.25.17, I don't believe has been tried on the HD before, it may work with this security unlock, but it may not. Some radio's from other devices can still brick your device even when you use security unlock, so do this at your own risk.
As fards stated, try and be patient and don't go trying things unless you are 100% certain. Read up on everything first. Myself and others will always try to help when online. If unsure of anything, you can always PM me.
Ta
Rick

Rick, thanks for the info. I know people ask the same questions over and over and it can get annoying. There is just such a wealth of information on here that sometimes it definitely is possible to get lost in it all. I really appreciate all the help i get, especially when it is packed in such a friendly tone.
The radio you mention 3.44.25.17
Click to expand...
Click to collapse
Ideally, I am looking for radio 3.45.25.17
I havent found it as of yet found it. That 3.44
was from a test rom for the TMO touch pro 2.
I have the raw files from the TMO TP2 but from
what ive read, you cant make a radio installer from
a rom dumped from a phone. You need the ruu-signed.nbh file.
Thanks a lot.

theres a good chance that the radio will still need hex editing, if you read the threads about radio unlocking it's mentioned in both of them.
It's not hard to do at all, it just needs one section changing
me attitude.. noo never ..

Thanks guys for directing me to the right locations. I think the problem was I was searching with my terms being too specific. Looking for exactly that radio on the HD. Anyway, I will be bringing up the same issue here for anyone that would like to follow how it plays out.
MODS:
I guess you can delete this if you would like.

Rhodium radios are not compatible with the HD, they will kill it.

wat a shame. Very disappointing. Well, maybe they will come out with another winmo 3G phone soone to help me out. Thanks everyone for your responses.

If Olipro states Rhodium radios are not compatible with the HD, and they will kill it. Then I would believe him. Unfortunate though
Thread closed

Question about my device!!

I don't know how strict people are about "searching" things before posting on the forums, but I rather get yelled at by some nerd on the internet, than to have my $350 device screwed over because I followed the wrong tutorial. Anyways here are my questions:
1) I bought this device from someone brand new, and it came out of the box configured to work with Windmobile, but I was able to get my FIDO SIM card to work by simply inputting it into the device. So does this mean that my device is already unlocked?
2) I still have the old 2.2 version on my phone, and I want the new version (2.3), but since I cannot update the OS from the device itself, I don't know what method I should follow from my computer, also I am afraid that I might lose my unlock (if it is) with the update.
Please link me to the proper tutorial, or give me some insight on my problem, Thank you.

Aint this community lovely, 160 views, yet no replies. Well I guess it is still better than spam and calling each other names.

hey, hey, hey...relax newbie.......
First of all you decide to spit on everybody's face about the fact that you are too lazy to search for stuff and now you cope an attitude??
I was going to leave this thread open to allow other member's input and for teh LULZ but I do believe you will have to actually do some search now.
Cheers,
PS: Do not re-open this thread mate...it will not end well

[Q] Can my phone get root?

I've been trying to figure out on the forums which device has which path to get root and wow it doesn't make sense to me. I'm no noobie but I don't get all the updates and processes.
I just want root so i can use Xposed. i don't care about loading different roms or kernels.
I bought it from swappa. It has android version 4.4, system 140.44.5.ghost_att.en.US, Build 13.11.1Q2.X-69-3
this thing sucks HARD without root. there is so much you could do that you can't. It astounds me how diligently manufacturers and carriers are about preventing you from using the phone to its fullest. So i void a warranty, i don't care...

a10fjet said:
I've been trying to figure out on the forums which device has which path to get root and wow it doesn't make sense to me. I'm no noobie but I don't get all the updates and processes.
I just want root so i can use Xposed. i don't care about loading different roms or kernels.
I bought it from swappa. It has android version 4.4, system 140.44.5.ghost_att.en.US, Build 13.11.1Q2.X-69-3
this thing sucks HARD without root. there is so much you could do that you can't. It astounds me how diligently manufacturers and carriers are about preventing you from using the phone to its fullest. So i void a warranty, i don't care...
Click to expand...
Click to collapse
I have an AT&T Moto X running Kit Kat 4.4 (from OTA) and I'm also not clear on whether I can root my phone. I'm also unclear about whether I can unlock my phone
I would also appreciate guidance and direction.
Many thanks!

The AT&T branded Moto X cannot be unlocked, but the GSM unlocked DE will work on AT&T and is unlockable. The TMobile Moto Maker Moto X will work on AT&T and has an unlockable bootloader, too, but if you unlock the bootloader on it, your warranty is void. So I would stick with the GSM unlocked DE. There may be some issues with 4G LTE on AT&T using the TMobile devices but I am not sure. That is probably covered in the forum somewhere if there are any issues.
Click to expand...
Click to collapse
Okay, so I can root, but not unlock. I think I'll wait till an easier and simpler root method is developed like there was for my Samsung GS2.
I appreciate the guidance.

CartlandSmith said:
We are lucky to even have this method. Google is making Android more and more secure by incorporating SELinux. If a root method for 4.4.2 is ever found, it will likely be even more complicated.
4.4 Security Enhancements
Also, the dev who came up with the current root method, jcase, is not interested in finding a root method for Motorola phones running 4.4.2.
So rooting now is likely your only chance at rooting. If you take the 4.4.2 OTA unrooted, it is doubtful you will ever be able to gain root because the 4.4.2 bootloader is not downgreadable.
Since the developer edition phones are so readily available from Motorola at such a good price and since only AT&T and Verizon retail/customized phones are not unlockable, there isn't much interest in trying to find a way to root locked Motorola phones running 4.4.2. Sprint, US Cellular and TMobile retail/customized Moto X's are unlockable as are the developer edition Moto X's.
Click to expand...
Click to collapse
Thanks for the thoughtful and informed reply, Cartland. My last phone was a Samsung GS2 and it was easy to root (all automated). Though I have rooted and flashed ROMs on a number of phones, this process seems complicated and readily screw-upable (not a real word, I admit). I like being rooted, so I can flash tweaked-out ROMs that are better than stock.
I'll explore rooting more and see how comfortable I am with it.
Much appreciated.

CartlandSmith said:
We are lucky to even have this method. Google is making Android more and more secure by incorporating SELinux. If a root method for 4.4.2 is ever found, it will likely be even more complicated.
4.4 Security Enhancements
Also, the dev who came up with the current root method, jcase, is not interested in finding a root method for Motorola phones running 4.4.2.
So rooting now is likely your only chance at rooting. If you take the 4.4.2 OTA unrooted, it is doubtful you will ever be able to gain root because the 4.4.2 bootloader is not downgreadable.
Since the developer edition phones are so readily available from Motorola at such a good price and since only AT&T and Verizon retail/customized phones are not unlockable, there isn't much interest in trying to find a way to root locked Motorola phones running 4.4.2. Sprint, US Cellular and TMobile retail/customized Moto X's are unlockable as are the developer edition Moto X's.
Click to expand...
Click to collapse
CartlandSmith said:
It takes some time to do it. I did it on a relative's phone. There are unfortunately some pointers that are left out of the original posts that help everything to go smoothly if you know them. You can find them in the threads, but the threads have gotten so long it makes the process take longer when you have to read through them to find all of the pointers.
If you are only flashing using RSD Lite - RSD Lite will stop you from bricking your phone.
You are never going to get a simpler method with a locked bootloader Motorola phone - it is only going to get harder and I predict the devs won't invest much energy in it going forward because it is just not worth it when there are developer editions available to us. I think those that are doing it get a kick out of it, but when it becomes too time consuming, well, they have their day jobs they have to make sure they focus enough time on to pay their bills. They get donations for this sort of thing, but I am sure the donations don't compensate them very well for all of the time they take trying to find exploits the more secure Android becomes.
With a locked bootloader, you can't flash ROMs because you don't have a custom recovery. But what you can do it use Xposed Framework and its modules like Gravity Box if you are rooted.
I spent some time this weekend rooting a relative's Verizon Moto X with a locked bootloader due to the 4.4.2 OTA coming. You have some breathing room on AT&T right now to root, but don't wait too long or you will lose the opportunity once the OTA comes.
Click to expand...
Click to collapse
I don't think I have the time or energy to go through the process of finding those pointers and then going through the root method. I'm wondering if anyone will compile those pointers (as you suggest, I have noticed with previous rooting and flashing methods, some key steps aren't described which can cause major problems).
A clarification. You say that if I just want to flash ROMs, I can use RSD Lite. But then you say that with a locked bootloader, you can't flash ROMs.
I do appreciate your taking the time.

POINTER - sell or trade your phone for a Dev edition

It is difficult to root if you can't unlock your bootloader. There is a thread in this forum telling you how to root your device with both locked and unlocked bootloader.

Rooting this device isn't difficult. If you can read and type verbatim, letter for letter, you can get root. People need to stop psyching themselves and others out.

CartlandSmith said:
Yes you can get root, but it takes a bit of work
First you have to downgrade to 4.2.2 by flashing the sbf firmware for your device.
Click to expand...
Click to collapse
can you specify what sbf is? searching didn't help. Try not to use so many acronyms for us dummies.
CartlandSmith said:
Then use RockMyMoto to get root on 4.2.2. Then use MotoWPNoMo to disable write protection.
Then reflash 4.2.2 and use SlapMyMoto.
Click to expand...
Click to collapse
do i use ODIN? what do i use to flash?
CartlandSmith said:
You will be rooted on 4.4 and write protection will be disabled when you are done with all of that.
Once you have root, be sure and freeze MotorolaOTA to stop the 4.4.2 OTA. If you take the 4.4.2 OTA, you may keep root, but write protection will be enabled.
Click to expand...
Click to collapse
Does motorolaOTA automatically download the latest updates and install them without warning you?
thanks for giving me hope!
EDIT: does anyone know if http://forum.xda-developers.com/moto-x/orig-development/script-root-moto-x-root-script-locked-t2603051 will work?

I'm getting close to knowing what to do!
But the individual steps are not very well written.
For example on the RockMyMoto page, he just starts giving you commands. He doesn't tell you what to type them into. In the video, everything is already open. I tried the command in cydia impactor and it didn't do anything. I though maybe you do it in adb, I don't really know what that is but I found adb.exe and launched it but the command window it opens goes through a bunch of commands and then closes. I can't even get past step one because he never said how he got to the point where he starts!
CartlandSmith said, in the third post, that i am supposed to reflash 4.2.2 at the end.. Did he mean 4.4? Or 4.2.2 then slapmymoto then take 4.4 over the air?
It would be really helpful (to me at least) if someone could put step by step instructions. Like humiliatingly degradingly redundant instructions for a complete idiot. I will put them up if I ever figure it all out. It's so frustrating when the instructions are so detailed from where they start, but they never show you how they got to where they are.
Thanks to everyone for the help.
EDIT: probably stupid question but does the phone ever need to be connected by USB? none of the posts mention it but all other devices i've used needed it. adb (here is a tutorial)/ isn't recognizing my device with USB connection or not. Both connected to same router, all drivers and everything updated, Debugging enabled...

No offense intended...at all....but if you value your phone, you really need to study up and read LOTS of stuff here. Until you understand what you are about to do, don't do anything.
Just trying to save you from a bricked phone. You seem very unsure of everything at this point. No one can post anything here that isn't already covered in the guides. Look at the stickies, complete Moto x guide is there.
Good luck.
Sent from my Nexus 5 using Tapatalk

Hmm i rebooted my computer and factory reset my X and now everything is connecting. Guess you should always try the IT Crowd's advice before doing anything else lol
I agree that everything is covered on this site, it's just not organized.

It seems unorganized when you don't understand. Read enough of it and it all makes sense eventually. This has everything about bootloaders, rooting...etc. BUT, you need to know what applies to your situation. And again...that comes when you understand the stuff.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my Nexus 5 using Tapatalk

CartlandSmith said:
It's even more clear how unorganized the info here is the more educated you become.
The thing that becomes the most clear eventually is how much misinformation is posted.
Sorry but the "it only appears disorganized and unreadable and full of misinformation" because you don't understand it won't fly with those of us who do understand it.
Click to expand...
Click to collapse
The OP of the thread I linked is well organized. Its about the only one that is. Its also stickied, so should be incredibly easy to find.
As far as misinformation goes, that's due to people being quick to post advice when they clearly don't have a handle on this stuff themselves.
How to avoid the clutter and misinformation? Maybe point people to good threads that already exist instead of filling new ones with more misinformation. No? Or God forbid, suggest they search for the information that already exists? Instead of helping to grow yet another repeated thread with both good and poor information within it.
Xda's number one rule was created for a reason. To keep clutter and thread after thread of similar content to a minimum. A lot of inaccurate information gets repeated over and over as well. But, so many refuse to search cause its too much work, and just as many others condone this behavior by answering.
I know most don't agree with what I'm saying, as the forums prove with the repeated information here in truck loads. And I also know when any of us remind people of rule number one here on xda....we're called trolls, flamers and much worse....even when the reminder was posted respectfully.
So who exactly are the flamers? LOL
Its looking like reminding members to search and read and actually help them help themselves is becoming a dangerous practice. I'm tired of the misinformation and cluttered forums....and if reminding is just going to start drama at every turn, I suppose reporting the offenders is the easier option. Tho not my first choice.
But if you read this carefully, you'll see I'm completely agreeing with you. LOL. So lets agree to agree and leave it at that.
And as a member who's been around a while, I won't stop doing my part to try to cut down the misinformation and lack of respect for the xda rules. Not abiding by rule number one is EXACTLY why the mess of confusing information exists. You see that, right?
If the newer members want to make me the bad guy for this, fine. I'll be the bad guy.
And I help more people here than most as well.....but that's forgotten if you disagree with anyone or remind anyone of the rules here. Fine. Again.....call me the bad guy. Better get used to it too, I'm not going anywhere.
I'd apologize for the off topic, but this thread should have been closed anyway.
Have a good one!
Sent from my Nexus 5 using Tapatalk

CartlandSmith said:
The most confusing thing of all is why someone with a Nexus 5 self-appoints themselves to be the "hall monitor" of the Moto X forums. *shrugs*
Click to expand...
Click to collapse
Um, perhaps I own both.
How bout you drop it and stop commenting on multiple posts of mine since you appear to dislike the things I say. K?
Try the ignore member feature.
Sent from my Nexus 5 using Tapatalk

Please search before posting
Check the sticky guides before asking questions about rooting
Thanks
FNSM

kennyglass123 said:
Please search before posting
Check the sticky guides before asking questions about rooting
Thanks
FNSM
Click to expand...
Click to collapse
Ninja'd .....:good:

Nexus 6 purchased via T-Mobile. Where the H*** is Marshmallow?

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

root guide for sm-n960u

what guide should i follow for this phone to root it? android v10

You must be new here. I believe you have to be on Android 8 to be rooted and plus, it's pointless from what I read, anyways. For one, your phone will never fully charge and 2, I'd already inquired about it, the rooting process ends up not being dependable and your phone will no longer be a daily driver. So, the thought of it is a no for me.
I doubt there's even a way to go back to Android 8 and any necessary security patch levels.
https://forum.xda-developers.com/ga...r-development/root-extreme-syndicate-t4043723

You don't have to be on oreo right now for it to work, you just need a combo firmware that uses the same bootloader revision as what you're currently on. You can currently get an oreo combo firmware up to revision 4. Basically it's a "modded" oreo firmware that uses the same bootloader version as newer firmwares.

Please change title or close this thread. Got me excited for nothing

Why close ? Its informative.
Now i know i need to sell my phone caz it cannot be rooted.
How ever, S8+ on 9.0 had root but some devices such as mine were turning into brick attempting to root them due to bootloader version conflict which was not identified by root method or person who wrote the method.
Bricked several S8+ phones attempting to root. Was too afraid to try my last one.
Hell, am not made of money buying phones every time root turns it into a brick where even EDL'ing wont fix it.

What about this ?
How to root Samsung Galaxy Note 9 SM-N960U With Odin Tool - Gogorapid
(Last Updated On: October 29, 2019)How to root Samsung Galaxy Note 9 SM-N960U With Odin Tool
www.gogorapid.com
I dont like to just follow steps on some dodgy website, i'd rather follow steps here on forum since people can validate it.
Too scared to try, too little information about side effects.

tonycstech said:
What about this ?
How to root Samsung Galaxy Note 9 SM-N960U With Odin Tool - Gogorapid
(Last Updated On: October 29, 2019)How to root Samsung Galaxy Note 9 SM-N960U With Odin Tool
www.gogorapid.com
I dont like to just follow steps on some dodgy website, i'd rather follow steps here on forum since people can validate it.
Too scared to try, too little information about side effects.
Click to expand...
Click to collapse
Yeah, don't trust random websites. They mostly contain generic procedures that are either vastly outdated or downright wrong.
I have a rooted N960U, and this is what it takes to get there:
To actually be able to root an N960U, you have to be on a software version with an Android security patch level of February 1, 2021 or older (if you look at the baseband version under software information in the About phone section under Settings, the 5th digit from the right should be a 7 or lower number). Anything newer than that is unrootable as far as I know. And for the rooting procedure, you have to unlock the bootloader first which currently requires a paid service as mentioned in the following post:
https://forum.xda-developers.com/t/...iers_fix_safetynet_aio.4217753/#post-85381639

Finlay someone giving useful info.
I looked at the sampwn website for unlocking service and i didnt like it.
It threw some kind of subscribe message at me covering entire page so i couldn't even see what the website is all about.
Then it constantly showing "someone purchased this or that" and opens a chat i dont want to see.
Those are 3 red flags for a fishy website so i have to pass.
I did how ever manage to look at the purchase process page and it was also full of red flags.
It was asking too much personal information.
It did not say what you are buying, how much you going to pay for it or what payment method is accepted.
Entire website has a theme of a scammer website, or at the very least it was built using those themes and thus it acts just like it.
Telegram, discord username required ? What if i dont have one ?
Do you want my password to my bank as well ?
Card number with expiration date and full name address and 3 security digits to pay ?
Are you F'ing serious ?
I dont know a single website that sell you stolen serial keys or cracked software that ask you this much information and claim "its required"
Besides, if there is a paid way, there must be a free way.
Who is this guy, owner of some sort of unlocking device ?
Whats the point of locking it if some lone wolf can unlock it anyway ?
Very sketchy.

tonycstech said:
Finlay someone giving useful info.
I looked at the sampwn website for unlocking service and i didnt like it.
It threw some kind of subscribe message at me covering entire page so i couldn't even see what the website is all about.
Then it constantly showing "someone purchased this or that" and opens a chat i dont want to see.
Those are 3 red flags for a fishy website so i have to pass.
I did how ever manage to look at the purchase process page and it was also full of red flags.
It was asking too much personal information.
It did not say what you are buying, how much you going to pay for it or what payment method is accepted.
Entire website has a theme of a scammer website, or at the very least it was built using those themes and thus it acts just like it.
Telegram, discord username required ? What if i dont have one ?
Do you want my password to my bank as well ?
Card number with expiration date and full name address and 3 security digits to pay ?
Are you F'ing serious ?
I dont know a single website that sell you stolen serial keys or cracked software that ask you this much information and claim "its required"
Besides, if there is a paid way, there must be a free way.
Who is this guy, owner of some sort of unlocking device ?
Whats the point of locking it if some lone wolf can unlock it anyway ?
Very sketchy.
Click to expand...
Click to collapse
Whatever method is being used to unlock the bootloader on these models has not been made public, so that's why there are only paid ways.
I can't speak for SamPWND as I used the first link with UNSAMLOCK, and the guy running it was quite helpful and did things quickly. But you do need to contact him through Telegram.
This is certainly not for everyone, so you really have to be sure you want it as it's a one-time, one device only thing. Otherwise, you'll have to look at the Exynos models or the international Snapdragon N9600 model for freely available bootloader unlocking and rooting methods.

SamPWND is a group on telegram i joined.
But i cant contact anyone there. All i get is what the owner posts.
How am i suppose to contact the owner if i want to unlock my bootloader ?
Jeezes ! Why they make things more complicated then they need to ?
In any case, the owner of that channel is some guy named Mohammad Afaneh
Are you F'ing kidding me ?
I am not sending my phone to some guy named Mohammad. Hell no !
He either hack it or put ship me a bomb back that will explode when i open it.

tonycstech said:
SamPWND is a group on telegram i joined.
But i cant contact anyone there. All i get is what the owner posts.
How am i suppose to contact the owner if i want to unlock my bootloader ?
Jeezes ! Why they make things more complicated then they need to ?
Click to expand...
Click to collapse
That's pretty strange for a Telegram group. Check the UNSAMLOCK one then as that's the one I used and had no problems with.
But remember that only older software versions are eligible. If yours is later than February 2021, then you won't be able to do anything.

tonycstech said:
SamPWND is a group on telegram i joined.
But i cant contact anyone there. All i get is what the owner posts.
How am i suppose to contact the owner if i want to unlock my bootloader ?
Jeezes ! Why they make things more complicated then they need to ?
In any case, the owner of that channel is some guy named Mohammad Afaneh
Are you F'ing kidding me ?
I am not sending my phone to some guy named Mohammad. Hell no !
He either hack it or put ship me a bomb back that will explode when i open it.
Click to expand...
Click to collapse
Afaneh has a good rep on XDA, for all I've seen. But I read you about Telegram, kinda irritrates me how it's taken away from the much more available xda forums. I could join, but like I was saying elsewhere just last night, I'm already way too "joined" as it is.