Database Users

SCH-R970X (CSpire) ROMS

Hey, Guys.
I've had this phone for a while, now. I'm pretty attached to it. I'm pretty sure I have some 2 or 3 year old posts here about this very phone.
BUT...
I haven't seen any new support for it. I'm currently running PAC-ROM, but I'm still on jellybean and while I LOVE the rom, it can be a bit glitchy (blame Tyler). I've tried flashing plenty of roms for this thing over the years. i9500's, i9505's, jfltexx's, etc. etc..... I've even gone in and added my phone's model to the rom compatability list (I'm sure there's some other technical name for it, but hey). But nothing actually work works.
Can anyone point me in the direction of some snazzy newer rom for my phone? I don't wanna go back to stock just so I can have lollipop/marshmallow.
Stock sucks.

FalseP77 said:
Hey, Guys.
I've had this phone for a while, now. I'm pretty attached to it. I'm pretty sure I have some 2 or 3 year old posts here about this very phone.
BUT...
I haven't seen any new support for it. I'm currently running PAC-ROM, but I'm still on jellybean and while I LOVE the rom, it can be a bit glitchy (blame Tyler). I've tried flashing plenty of roms for this thing over the years. i9500's, i9505's, jfltexx's, etc. etc..... I've even gone in and added my phone's model to the rom compatability list (I'm sure there's some other technical name for it, but hey). But nothing actually work works.
Can anyone point me in the direction of some snazzy newer rom for my phone? I don't wanna go back to stock just so I can have lollipop/marshmallow.
Stock sucks.
Click to expand...
Click to collapse
JDC ROMs are compatible with the SCH-R970.
There doesn't seem to be any difference except for the carrier. Yours is C-Spire, and the other is US Cellular.

GDReaper said:
JDC ROMs are compatible with the SCH-R970.
There doesn't seem to be any difference except for the carrier. Yours is C-Spire, and the other is US Cellular.
Click to expand...
Click to collapse
thanks for replying.
US Cellular runs on a CDMA network, while CSpire runs on GSM.
Meanwhile, T-Moble ALSO uses a GSM network (every other major carrier uses CDMA), but I believe that they use a different chipset.

935F vs 935W8 roms

Hello all I've been out of the phone modding game for about 4 years and just picked up a w8 model and like the phone though sad to see no cm.
I've been browsing the site and had a few questions about modding my phone.. Several roms specifically say it supports w8 while others just say 935F.. is there really additional code to support the w8 or the rom just hasn't been verified by the developer?
Also several roms say to install the latest bootloader and modem but the link only takes you to the 935F versions.. I already have the latest update from Wind in Canada which ends in API1 is this good enough or do I need to flash a different downloaded version and if so can someone point me in the right direction for the Wind files..
One last thing.. I see a lot of people discussing flashing a csc.. but not sure what that is. I assume it's local carrier settings or something but how often is it needed? And does it only need to be done with certain roms or if there are certain issues.
I've only really used HTC and Nexus phones previously so don't wanna brick this pretty new toy as I bought it second hand and don't have warranty.
Also.. probably not the place to ask but what roms do you guys prefer that supports w8? I'm looking for something fast debloated and lots of customization.. haven't really seen the N7 so not sure about new UX.. I've usually gone cm all the way so used to default android..
Thanks for any info/advice/recommendations

I can't believe this question isn't answered. All samsung line with a pile of unecessary variations is confusing. I just picked up the phone and have no idea, while it should be same cpu=same rom

Attention Note 7 ports!

If you are using any N7 port rom. You need to read below linked post.
This guy's imei was blacklisted because showing as Note 7. :crying:
This was on Nemesis rom but I'd beware on all N7 roms.
I came across this and wanted to share and inform you all.
http://forum.xda-developers.com/showpost.php?p=70078576&postcount=1053
Only thing i don't understand, i thought when a phone was produced, it is given a range of imei numbers. So these companies should be able to determine this isn't true Note 7.

aaron74 said:
If you are using any N7 port rom. You need to read below linked post.
This guy's imei was blacklisted because showing as Note 7. :crying:
This was on Nemesis rom but I'd beware on all N7 roms.
I came across this and wanted to share and inform you all.
http://forum.xda-developers.com/showpost.php?p=70078576&postcount=1053
Only thing i don't understand, i thought when a phone was produced, it is given a range of imei numbers. So these companies should be able to determine this isn't true Note 7.
Click to expand...
Click to collapse
Just asking
Can the developers of N7 ports deal with this issue?
My note 4 is all I have.
Can't afford to mess it up

natibongo said:
Just asking
Can the developers of N7 ports deal with this issue?
My note 4 is all I have.
Can't afford to mess it up
Click to expand...
Click to collapse
I don't know about the devs.
But these service providers and also samsung should be able to tell not to do this. They shouldn't just read 1 value (like ro.build.model) from build.prop to determine if it's a note 7. All they would need is a script to read a few hardware values to tell is not a true note 7. Plus i always thought your imei was coded to certain models. So no matter what rom you have, your imei will show as a note 4. That's what didn't make sense to me in that post.
But either way, i wanted to share it. So precautions could be taken.

aaron74 said:
If you are using any N7 port rom. You need to read below linked post.
This guy's imei was blacklisted because showing as Note 7. :crying:
This was on Nemesis rom but I'd beware on all N7 roms.
I came across this and wanted to share and inform you all.
http://forum.xda-developers.com/showpost.php?p=70078576&postcount=1053
Only thing i don't understand, i thought when a phone was produced, it is given a range of imei numbers. So these companies should be able to determine this isn't true Note 7.
Click to expand...
Click to collapse
Considering that carriers are supposed to be able to block a single phone via IMEI (if that phone is stolen, for example), it stands to reason that they're supposed to be unique per phone - no two note 7s should have the same number, let alone two phones with different models
So if there's a custom rom out there that is changing everyone's IMEI to the same number, the blacklist in this case might not have anything to do with whether it's a Note 7 IMEI - using the same IMEI on two devices at the same time should raise red flags

styles420 said:
Considering that carriers are supposed to be able to block a single phone via IMEI (if that phone is stolen, for example), it stands to reason that they're supposed to be unique per phone - no two note 7s should have the same number, let alone two phones with different models
So if there's a custom rom out there that is changing everyone's IMEI to the same number, the blacklist in this case might not have anything to do with whether it's a Note 7 IMEI - using the same IMEI on two devices at the same time should raise red flags
Click to expand...
Click to collapse
Exactly, kinda what i meant is, they shouldn't be turning off your phone because of build.prop properties showing as N7. It should all be done by imei.
But that post had me worried, cause he makes it sound like his phone was shut down just for having N7 port rom. Which should not be the case. Unless there's something going on there we don't know about (like changed imei)
Thanks for your input. Cause i was trying to ease my mind about running these roms.
My thought and conclusion on this, is these roms should be fine to run, unless you change or mask your imei to show as a N7. Unless these carrier tech guys are stupid enough to use a script that only detects your build id. Which shouldn't be how it's handled.

aaron74 said:
Exactly, kinda what i meant is, they shouldn't be turning off your phone because of build.prop properties showing as N7. It should all be done by imei.
But that post had me worried, cause he makes it sound like his phone was shut down just for having N7 port rom. Which should not be the case. Unless there's something going on there we don't know about (like changed imei)
Thanks for your input. Cause i was trying to ease my mind about running these roms.
My thought and conclusion on this, is these roms should be fine to run, unless you change or mask your imei to show as a N7. Unless these carrier tech guys are stupid enough to use a script that only detects your build id. Which shouldn't be how it's handled.
Click to expand...
Click to collapse
He never said that it was due to a build.prop value, so I'm not sure where you got that - he specifically said that it was because of the IMEI

styles420 said:
He never said that it was due to a build.prop value, so I'm not sure where you got that - he specifically said that it was because of the IMEI
Click to expand...
Click to collapse
He really didn't say what caused it, just that the IMEI was black listed: "The (AT&T) representative was adamant that the phone imei had been blocked by TMobile, but a call to them confirmed that while at&t put in the blacklisting, reported the phone as stolen as soon as Nemesis ROM registered a note 7 to their system yesterday night, and that there was nothing in their system they could do to unblock the imei. Long story short, after explaining the concept of custom Roms to the rep, at&t has put an unblock request in to be resolved by the 14th, hopefully it works, and just a word of warning to everyone!
PS. I had also changed build.prop product model to SM-G935F shortly after installing yesterday, so the red flag must've gone into their system as soon as it went online. Maybe developers need to stop putting the N9300 as the product model stock to avoid this!!"
It's hard to tell if the fact that he changed the model in the build.prop is what caused the blacklisting. I wonder if he had it properly unlocked from T-Mobile to use it on AT&T? That could have been part of the problem. I was told once, by T-Mobile, that the original owner of a phone had to request the unlocking, on T-Mobile. One thing I do know, is that it is illegal to take an IMEI from one phone and put it on another phone. For example, say you had Note 4, with a broken digitizer. You bought a working, but blacklisted Note 4. Then took the IMEI from your original N4 and put it on the blacklisted one. That's illegal. I fail to see how it would even work if you had 2 different models of phone, though. Or maybe, that was, indeed, what caused the blacklisting. OTOH, people have been porting ROMS from different models forever, and no one has complained of this that we've heard of. As we all know, there were Note 5 ports, as well as S7 ports...

smarcin said:
He really didn't say what caused it, just that the IMEI was black listed: "The (AT&T) representative was adamant that the phone imei had been blocked by TMobile, but a call to them confirmed that while at&t put in the blacklisting, reported the phone as stolen as soon as Nemesis ROM registered a note 7 to their system yesterday night, and that there was nothing in their system they could do to unblock the imei. Long story short, after explaining the concept of custom Roms to the rep, at&t has put an unblock request in to be resolved by the 14th, hopefully it works, and just a word of warning to everyone!
PS. I had also changed build.prop product model to SM-G935F shortly after installing yesterday, so the red flag must've gone into their system as soon as it went online. Maybe developers need to stop putting the N9300 as the product model stock to avoid this!!"
It's hard to tell if the fact that he changed the model in the build.prop is what caused the blacklisting. I wonder if he had it properly unlocked from T-Mobile to use it on AT&T? That could have been part of the problem. I was told once, by T-Mobile, that the original owner of a phone had to request the unlocking, on T-Mobile. One thing I do know, is that it is illegal to take an IMEI from one phone and put it on another phone. For example, say you had Note 4, with a broken digitizer. You bought a working, but blacklisted Note 4. Then took the IMEI from your original N4 and put it on the blacklisted one. That's illegal. I fail to see how it would even work if you had 2 different models of phone, though. Or maybe, that was, indeed, what caused the blacklisting. OTOH, people have been porting ROMS from different models forever, and no one has complained of this that we've heard of. As we all know, there were Note 5 ports, as well as S7 ports...
Click to expand...
Click to collapse
I know the build.prop isn't a factor - custom rom developers have used a different device model for various reasons without issue (I've seen it used in order to allow apps to be downloaded from the play store that were incorrectly marked as incompatible with that device, by changing the build.prop model to that of a device that was compatible with the app)
I seriously doubt that a developer included his own (or anyone else's) IMEI in a custom rom - they either know better, or they brick devices with the various other similar mistakes they would make. Besides, there wouldn't be just one user with this issue...
The most likely scenario is that the user tried something questionable with his IMEI and wants help fixing the mistake/bad decision without having to admit what really happened

styles420 said:
I know the build.prop isn't a factor - custom rom developers have used a different device model for various reasons without issue (I've seen it used in order to allow apps to be downloaded from the play store that were incorrectly marked as incompatible with that device, by changing the build.prop model to that of a device that was compatible with the app)
I seriously doubt that a developer included his own (or anyone else's) IMEI in a custom rom - they either know better, or they brick devices with the various other similar mistakes they would make. Besides, there wouldn't be just one user with this issue...
The most likely scenario is that the user tried something questionable with his IMEI and wants help fixing the mistake/bad decision without having to admit what really happened
Click to expand...
Click to collapse
First of all i agree with your last sentence and there is definitely something going on with his IMEI between AT&T and T-Mobile. that the part of the equation that is a bit fishy to me. I don't think he was completely forthcoming with his IMEI situation to begin with.
Another thing, the IMEI is never part of any device's flashable software package. Ever. This stuff get's written to EFS and other databases after the flash and during the initial rom setup and activation process so no rom chef can or will include any EFS or IMEI information into any rom. that simply makes no sense.
I also agree that blacklisting in this situation with the recalled N7 should be handled by IMEI databases and not solely on the devices "reported" device model over the network. That's how blacklisting is typically done in situations of lost/stolen devices or when you file an insurance claim on the device. The insurance company and the carrier enter the device's serial numbers into the IMEI blacklist database so they cannot be activated on that network. I can only assume that all network providers are going to honor Samsung's request to deactivate all N7's as well as it being banned by the FCC which also requires carriers to remove these devices from the stores and prevent them from working on their networks. Carriers have a legal obligation to follow these laws and guidelines set forth by the FCC. Period.
So in my opinion we should technically be able to use ported N7 roms on other devices with the build.prop device model etc to the values of that of the N7 variants and not have to worry about our phones' IMEI getting blacklisted. But I have already taken the precaution and changed the build.prop values in my current Sprint N7 port rom (still in final testing phase) just to be safe. I may test the N7 device model in build.prop once the "deactivation" date passes and see what happens. I have two N4's so I can deal with it if my phone incorrectly gets blacklisted due to running a port rom.

tx_dbs_tx said:
First of all i agree with your last sentence and there is definitely something going on with his IMEI between AT&T and T-Mobile. that the part of the equation that is a bit fishy to me. I don't think he was completely forthcoming with his IMEI situation to begin with.
Another thing, the IMEI is never part of any device's flashable software package. Ever. This stuff get's written to EFS and other databases after the flash and during the initial rom setup and activation process so no rom chef can or will include any EFS or IMEI information into any rom. that simply makes no sense.
I also agree that blacklisting in this situation with the recalled N7 should be handled by IMEI databases and not solely on the devices "reported" device model over the network. That's how blacklisting is typically done in situations of lost/stolen devices or when you file an insurance claim on the device. The insurance company and the carrier enter the device's serial numbers into the IMEI blacklist database so they cannot be activated on that network. I can only assume that all network providers are going to honor Samsung's request to deactivate all N7's as well as it being banned by the FCC which also requires carriers to remove these devices from the stores and prevent them from working on their networks. Carriers have a legal obligation to follow these laws and guidelines set forth by the FCC. Period.
So in my opinion we should technically be able to use ported N7 roms on other devices with the build.prop device model etc to the values of that of the N7 variants and not have to worry about our phones' IMEI getting blacklisted. But I have already taken the precaution and changed the build.prop values in my current Sprint N7 port rom (still in final testing phase) just to be safe. I may test the N7 device model in build.prop once the "deactivation" date passes and see what happens. I have two N4's so I can deal with it if my phone incorrectly gets blacklisted due to running a port rom.
Click to expand...
Click to collapse
I use my note 4 outside US so I think there is no worry about blacklist since I use it in non-US CDMA carrier so I am waiting for your N7 rom with no worry ... And I hope that you include international languages to the ROM because the system apps included only 6 languages in their res folder.
Also WIFI HOTSPOT feature as always in your roms.
Thank you.

Here's the latest the guy posted over in the Nemesis thread:
"I'm following up, my debacle from the blacklisted imei / suspended service with AT&T continues (after installing this ROM). AT&T tech rep confirms all of my issues stem from actions lead by Samsung and automatically carried out by AT&T's system. Dev, please updated your build.prop to new update as maybe many of the new people flashing this rom are not getting service / data, as Samsung is becoming increasingly more aggressive and they have no way to tell if it's a real Note 7 or not, according to AT&T people..."
You'd think Samsung and the carriers have both the IMEI and it's corresponding model in their databases. But maybe they think that a Note7 owner could be desperate enough to keep their N7 and tried to reassign the IMEI from their Note 4 to a Note7. I know I really liked my Note7, but not THAT much! Also, we can probably safely discount that the AT&T tech rep really knew what he or she was talking about.

wel in any case i'm rebuilding my still unreleased N7 port and simply tweaking the build.prop and csc cures the N7 ban concerns. No worries on my end. I just need a little time to rebuild my rom from the latest softwares.

Funny I remember flashing a N7 port rom on my wife Note 4 from Verizon, when we had them.. When you plugged the phone into the computer, it would recognize it as a Note 7. I wonder why?

tx_dbs_tx said:
wel in any case i'm rebuilding my still unreleased N7 port and simply tweaking the build.prop and csc cures the N7 ban concerns. No worries on my end. I just need a little time to rebuild my rom from the latest softwares.
Click to expand...
Click to collapse
Take your time man. As much as I was hoping to see it released before this weekend I, along with others, will gladly wait patiently while you work on polishing this ROM. Looking forward to it! And many many thanks (can only press the thanks button once lol)

jbuggydroid said:
Take your time man. As much as I was hoping to see it released before this weekend I, along with others, will gladly wait patiently while you work on polishing this ROM. Looking forward to it! And many many thanks (can only press the thanks button once lol)
Click to expand...
Click to collapse
Me too! Many thanks. I'm sure it'll be great!
Also,
I'm still in disbelief that samsung or at&t would be so noobish to shut down a phone just by reading it's build.prop as a N7(or whatever the case was). Even if they were worried about just going by imei lookup, this just don't seem right. I'm sure they could run some remote script to read it's hardware or bootloader, or modem (I can go on), and know it's not a N7.
Has anyone heard of anyone else this happening to? I'm just thinking there was more to this story than getting blacklisted from flashing aN7 port.
Sorry to rant about this but i can't believe a tech that high up the chain would write code that simple, to allow this to happen.

aaron74 said:
Me too! Many thanks. I'm sure it'll be great!
Also,
I'm still in disbelief that samsung or at&t would be so noobish to shut down a phone just by reading it's build.prop as a N7(or whatever the case was). Even if they were worried about just going by imei lookup, this just don't seem right. I'm sure they could run some remote script to read it's hardware or bootloader, or modem (I can go on), and know it's not a N7.
Has anyone heard of anyone else this happening to? I'm just thinking there was more to this story than getting blacklisted from flashing aN7 port.
Sorry to rant about this but i can't believe a tech that high up the chain would write code that simple, to allow this to happen.
Click to expand...
Click to collapse
From what I can tell the network looks at the FCCID so unless you change that in the rom it will flag on the network and service will be terminated on the device.

tx_dbs_tx said:
From what I can tell the network looks at the FCCID so unless you change that in the rom it will flag on the network and service will be terminated on the device.
Click to expand...
Click to collapse
Cool, Thanks for the info. I'll have to remember that. Ive changed that in floating features before in another rom. But i only changed G to P, to denote sprint model. I'll remember to not change model#.
Any word on your roms arrival?

aaron74 said:
Cool, Thanks for the info. I'll have to remember that. Ive changed that in floating features before in another rom. But i only changed G to P, to denote sprint model. I'll remember to not change model#.
Any word on your roms arrival?
Click to expand...
Click to collapse
I'm rebuilding the rom as I type this. Lots of things i'm having to do to get the rom where I'm happy with it. As for the FCCID in floating features set it to that of the N5 variant and that will be good. Same in build.prop device model. Set that to N920P and that will do the trick and not have any negative effects on the rom. This is what I have done to my N7 test rom and tests have proven this to be the best workaround according to my test group who are running the rom as their daily for weeks now. Sorry about the delay with my N7 rom but I want it to be ready with little to no issues before I release it to the public. There's a lot on the line and I have to make sure peoples' phones will not be impacted by running this custom firmware. It seems to be perfectly fine and no loss of services yet. I will post when the rom is actually ready for a public release so not to keep people in suspense when the rom just isn't up to my standards yet.

tx_dbs_tx said:
I'm rebuilding the rom as I type this. Lots of things i'm having to do to get the rom where I'm happy with it. ....
There's a lot on the line and I have to make sure peoples' phones will not be impacted by running this custom firmware. It seems to be perfectly fine and no loss of services yet. I will post when the rom is actually ready for a public release so not to keep people in suspense when the rom just isn't up to my standards yet.
Click to expand...
Click to collapse
Thank you, I understand. I was not trying to sound impatient, just curious. No worries here! I empathize with the amount of time it must take to port and debug these TW roms.
I know you only release your roms stable and working great.
I'll be anticipating it's announcement. Thanks for your reply and heads up about everything else. :good:

tx_dbs_tx said:
I will post when the rom is actually ready for a public release so not to keep people in suspense when the rom just isn't up to my standards yet.
Click to expand...
Click to collapse
I have been refreshing the thread and searching on your posts for what seems like weeks now. I'm a bit anxious.

New to S7... Why are there only 3 roms posted here?

Is there something I'm missing?

Sammy locked the Bootloader

Yup. This is the most highly sought after device with almost no developer support.
If you wanted root then you should get pretty much any other phone.

if you change the Android Code, you have to share it.
ahq1216 said:
Sammy locked the Bootloader
Click to expand...
Click to collapse
Correct me if I am wrong, but according to the Android Platform User Agreement (I think), if you change the Android Code, you have to share it. Or some form of developers open source agreement. Correct?

So there has been no root accomplished whatsoever on the T-Mobile S7? If that's true, then I'm hanging on to my Note 7 and selling the S7E.

Binary100100 said:
Yup. This is the most highly sought after device with almost no developer support.
If you wanted root then you should get pretty much any other phone.
Click to expand...
Click to collapse
Then what is the post in your signature about?
https://forum.xda-developers.com/ve...sed-unroot-t3411039/post67605246#post67605246

And what's the deal with the engineering bootloader?
http://www.theandroidsoul.com/root-t-mobile-s7-edge-engineering-bootloader/
Looks like S7 has had an unlocked bootloader with this for a while... Still very confused as to why there are no roms here.

unkellsam said:
Then what is the post in your signature about?
https://forum.xda-developers.com/ve...sed-unroot-t3411039/post67605246#post67605246
Click to expand...
Click to collapse
unkellsam said:
And what's the deal with the engineering bootloader?
http://www.theandroidsoul.com/root-t-mobile-s7-edge-engineering-bootloader/
Looks like S7 has had an unlocked bootloader with this for a while... Still very confused as to why there are no roms here.
Click to expand...
Click to collapse
I suppose you really need to read a bit more.
For all Qualcomm US devices the bootloader is LOCKED.
This is well known and documented. Root is possible only with an engineering kernel. The page that you referenced is inaccurate as it referenced an engineering bootloader. It's actually an engineering boot.img file that the writer mistook for a bootloader. Again... it's an engineering kernel not engineering bootloader.

unkellsam said:
So there has been no root accomplished whatsoever on the T-Mobile S7? If that's true, then I'm hanging on to my Note 7 and selling the S7E.
Click to expand...
Click to collapse
There is, but it's very unstable. Phone tends to lag and overheat due to the (something i dont understand).

serendipityguy said:
Correct me if I am wrong, but according to the Android Platform User Agreement (I think), if you change the Android Code, you have to share it. Or some form of developers open source agreement. Correct?
Click to expand...
Click to collapse
Well, yes and no. Parts fall under GPL, and parts of what Samsung uses to enable full functionality of the phone are NOT. The fact that they use special digital signatures in the boot process to prevent loading unsigned code is totally up to them (i.e. its all the stuff that happens before "android" starts...

sbaeder said:
Well, yes and no. Parts fall under GPL, and parts of what Samsung uses to enable full functionality of the phone are NOT. The fact that they use special digital signatures in the boot process to prevent loading unsigned code is totally up to them (i.e. its all the stuff that happens before "android" starts...
Click to expand...
Click to collapse
But arn't there other S7 roms from Verizon, AT&T and Sprint having developers pushing out custom kernels? Is this something that T-mobile can release but won't?
Google gives/updates the OS, Samsung gives the S7 hardware / Updated OS - Patches the OS & then gives to the Carriers (Tmobile) and they plug in their hellware (Bloatware), surely they have the source or the ability to modify the stock rom when updates are being pushed out to the carriers.
When a New Stock drops, it is the phone carriers who modify the kernel's, boot animation, build property, and sets their modems and such . . . Not Samsung because they would not be want to push out the kernels, modems, build property, boot animation & custom roms for each phone carrier in each region of each county. So lf what I am thinking that our phone carriers developers are lame ducks....
Going the other way on this, how does Sam Mobile play into this? how is it that they are able to host the roms on their servers? Arn't there any links from Samsung to host the roms?
Please if I am wrong, please someone correct me.

It's complicated...
Samsung locked the bootloaders on all US (Qualcomm) S7 but left the bootloader unlocked on international (Exynos) roms and some international Qualcomm roms.
This sucks and hopefully is not repeated on the upcoming S8 which may be Qualcomm only.
Last summer, an engineering bootloader was leaked and a group of people here got a root that uses the engineering bootloader. It's not perfect, as it forces people to use a non-production kernel. More people here came up with settings to get the most out of that kernel.
Right now we are in the middle of the transition to Android 7 and the engineering root doesn't work with it presently. Until a solution for that is reached
At the same time, the international rom deveopment has gone smoothly with over a dozen roms updated and a few tweaked kernels. The Exynos phone itself seems to be faster and with better battery life (but worse reception) compared to a standard qualcomm. Rooted with a custom kernel on both, it's like night and day how much better the exynos performance is. Some people ported T-mobile wifi calling and Volte (through CSC settings) to the international version, so for a certain user (of which I am one), the ideal root solution is to run a full speed exynos 930F on Android 7 and retain t-mobile functionality.

unkellsam said:
Is there something I'm missing?
Click to expand...
Click to collapse
Samsung blows

T-Mobile and Samsung both ****ed up around this time
Sent from my SM-G935T using XDA-Developers Legacy app

fracture8 said:
T-Mobile and Samsung both ****ed up around this time
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I hear you.
Im gonna pay off the half of the phone in 7 months and then will jump ship to a one plus 4/5 when its released.
So much wasted potential

I would get the G935F.
serendipityguy said:
But arn't there other S7 roms from Verizon, AT&T and Sprint having developers pushing out custom kernels? Is this something that T-mobile can release but won't?
Google gives/updates the OS, Samsung gives the S7 hardware / Updated OS - Patches the OS & then gives to the Carriers (Tmobile) and they plug in their hellware (Bloatware), surely they have the source or the ability to modify the stock rom when updates are being pushed out to the carriers.
When a New Stock drops, it is the phone carriers who modify the kernel's, boot animation, build property, and sets their modems and such . . . Not Samsung because they would not be want to push out the kernels, modems, build property, boot animation & custom roms for each phone carrier in each region of each county. So lf what I am thinking that our phone carriers developers are lame ducks....
Going the other way on this, how does Sam Mobile play into this? how is it that they are able to host the roms on their servers? Arn't there any links from Samsung to host the roms?
Please if I am wrong, please someone correct me.
Click to expand...
Click to collapse
T-Mobile and Samsung keep playing around. I'm really hoping the Note 8 comes with an unlocked boot-loader or this may be there strategy going forward for the US.
rp3 said:
It's complicated...
Samsung locked the bootloaders on all US (Qualcomm) S7 but left the bootloader unlocked on international (Exynos) roms and some international Qualcomm roms.
This sucks and hopefully is not repeated on the upcoming S8 which may be Qualcomm only.
Last summer, an engineering bootloader was leaked and a group of people here got a root that uses the engineering bootloader. It's not perfect, as it forces people to use a non-production kernel. More people here came up with settings to get the most out of that kernel.
Right now we are in the middle of the transition to Android 7 and the engineering root doesn't work with it presently. Until a solution for that is reached
At the same time, the international rom deveopment has gone smoothly with over a dozen roms updated and a few tweaked kernels. The Exynos phone itself seems to be faster and with better battery life (but worse reception) compared to a standard qualcomm. Rooted with a custom kernel on both, it's like night and day how much better the exynos performance is. Some people ported T-mobile wifi calling and Volte (through CSC settings) to the international version, so for a certain user (of which I am one), the ideal root solution is to run a full speed exynos 930F on Android 7 and retain t-mobile functionality.
Click to expand...
Click to collapse
I was dead set on getting the Note 7 but after the fiasco i settled for the S7 edge. the G935F also has all the bands that t-Mobiel uses so we get band 12 as well. The issue with getting the G935F is trying to buy online as it has to be imported and still get insurance and so forth. Bought from B&H photo ( aa reputable US store) for insurance and good support. The g935F turned out to be a good gamble. As long as you wait there was alot of development. Since alot of us T-Mobile guys hopped over we were able to get Volte and wificalling ported over via various CSC edits and other workarounds. So we get alot of custom roms and T-Mobile support as well. Only issue you have to root and loose Samsung pay but for me that a okay lol.

should I root or rom this phone??

Hello. I have noticed in these threads recently that there is an IMEI, 4G, and VOLTE being lost by flashing roms (it seems like it might be only oreo roms??).
I am in the process of buying this phone (it is amazing for carrier compatibility), and am curious on what your guys thoughts are on this.
I am not at all new to rom'ing, but I definitely want to make sure that I am not permanently loosing any important functionality with this phone.

royredman said:
Hello. I have noticed in these threads recently that there is an IMEI, 4G, and VOLTE being lost by flashing roms (it seems like it might be only oreo roms??).
I am in the process of buying this phone (it is amazing for carrier compatibility), and am curious on what your guys thoughts are on this.
I am not at all new to rom'ing, but I definitely want to make sure that I am not permanently loosing any important functionality with this phone.
Click to expand...
Click to collapse
I'd recommend staying stock until the devs figure out what's going on with VoLTE and they come up with something unless it's Motovo/Lenovorola's fault, in that case you're better off staying stock anyways atleast until the issue is taken care of.

psychopac said:
I'd recommend staying stock until the devs figure out what's going on with VoLTE and they come up with something unless it's Motovo/Lenovorola's fault, in that case you're better off staying stock anyways atleast until the issue is taken care of.
Click to expand...
Click to collapse
can you explain when this happened? Are all roms vulnerable to this, or just oreo roms? Also, how long has the developers been looking into this for?

royredman said:
can you explain when this happened? Are all roms vulnerable to this, or just oreo roms? Also, how long has the developers been looking into this for?
Click to expand...
Click to collapse
This is happening with Oreo ROMs at the moment, at least that's what I've been seeing.

I go back to this statement... if you have to question whether you want/need to root or ROM, then you don't need to and should not do so.
Honestly, rooting today is now like years ago... most "normal" users gain little and give themselves more headaches than it's worth.

acejavelin said:
I go back to this statement... if you have to question whether you want/need to root or ROM, then you don't need to and should not do so.
Honestly, rooting today is now like years ago... most "normal" users gain little and give themselves more headaches than it's worth.
Click to expand...
Click to collapse
I wasn't questioning whether I wanted to or not. I like the idea of rooting and Roming my phone. I have done it many times before. The reason I am buying this phone is close to exactly that reason. I was asking the users if it was a good idea since a vast amount of users are losing their VOLTE and possibly their 4G connections because of doing this.
There can be a fair amount of advantages to with rooting and roming overall, but the reasons for doing this tends to become less and less important as modern cell phones get more powerful and more customizable .

royredman said:
I wasn't questioning whether I wanted to or not. I like the idea of rooting and Roming my phone. I have done it many times before. The reason I am buying this phone is close to exactly that reason. I was asking the users if it was a good idea since a vast amount of users are losing their VOLTE and possibly their 4G connections because of doing this.
There can be a fair amount of advantages to with rooting and roming overall, but the reasons for doing this tends to become less and less important as modern cell phones get more powerful and more customizable .
Click to expand...
Click to collapse
Literally, the title of this thread is "should I root or ROM this phone" so forgive me if I misunderstood.
I don't think anyone properly rooting or installing a quality ROM is losing 4G/LTE connectivity, although a few seem to lose VoLTE but it makes no sense why as the radio firmware doesn't change with a custom ROM and the kernel and AOSP VoLTE implementation source code is available.
Check threads for the ROM you're interested in, and look for information specific to your carrier. I can't speak for some but VoLTE isn't allowed from this device to Verizon or AT&T and most of their MVNOs.

acejavelin said:
Literally, the title of this thread is "should I root or ROM this phone" so forgive me if I misunderstood.
I don't think anyone properly rooting or installing a quality ROM is losing 4G/LTE connectivity, although a few seem to lose VoLTE but it makes no sense why as the radio firmware doesn't change with a custom ROM and the kernel and AOSP VoLTE implementation source code is available.
Check threads for the ROM you're interested in, and look for information specific to your carrier. I can't speak for some but VoLTE isn't allowed from this device to Verizon or AT&T and most of their MVNOs.
Click to expand...
Click to collapse
Good point. I'll look into the threads. Thanks for the tip!