Hello
I just bought a 7.7 on Verizon. Primarily for SD Card & LTE. But I have major issues with lag on my training videos. I think if I upgrade to ICS this might help. I know Verizon is not releasing anytime soon....
Any suggestions? I Have been searching for 2 days now and just really confused. I really dont want to return this thing. I also bought a Nexus 7 and have had no issues with lag but the 7.7 is so much nicer (expect the lag)
thanks
Do visit this site and find P6800 ROM http://www.filefactory.com/f/16e5683c3e667a17[
For ICS, download XXLQ2 ROM. (Latest)
Happy flashing!
marwanxx said:
Do visit this site and find P6800 ROM http://www.filefactory.com/f/16e5683c3e667a17[
For ICS, download XXLQ2 ROM. (Latest)
Happy flashing!
Click to expand...
Click to collapse
Awesome. Thank you. Is there a "go back to stock" in case things dont go well?
thx
agunjal said:
Hello
I just bought a 7.7 on Verizon. Primarily for SD Card & LTE. But I have major issues with lag on my training videos. I think if I upgrade to ICS this might help. I know Verizon is not releasing anytime soon....
Any suggestions? I Have been searching for 2 days now and just really confused. I really dont want to return this thing. I also bought a Nexus 7 and have had no issues with lag but the 7.7 is so much nicer (expect the lag)
thanks
Click to expand...
Click to collapse
You have a Verizon tab. It's a different model, with different hardware. The 6800/6810 firmwares will not work for you. In fact, they will probably brick your device. Do NOT Download any file for the international, GT-P6800/GT-P6810!!!
Over at the development forum, you will find CM9/CM10. Those are independent from Samsung/Verizon, based on Google's ICS/JB code. They are currently the only choice of ICS+ for the Verizon model.
Steve_max said:
You have a Verizon tab. It's a different model, with different hardware. The 6800/6810 firmwares will not work for you. In fact, they will probably brick your device. Do NOT Download any file for the international, GT-P6800/GT-P6810!!!
Over at the development forum, you will find CM9/CM10. Those are independent from Samsung/Verizon, based on Google's ICS/JB code. They are currently the only choice of ICS+ for the Verizon model.
Click to expand...
Click to collapse
phew..thanks...I was just about to...I am returning this thing and will wait until they update it...thanks everyone
You can use iocerra's cm9 and cm10 builds for ics and jb, but they don't have lte so that might be a deal breaker. Or you can root, install titanium backup and freeze/remove some apps to see if you can reduce lag. Or you can wait. All good options, depending on what you want / need.
Sent from my Nexus S 4G using Tapatalk 2
Been many a yore since I've been on Android consistently, been out-of-the-loop since the earliest days.
Just curious, is it technically possible to get a "Nexus-like" experience on a device like the Note 4 nowadays?
I'm attracted by all the sw/service benefits of a Nexus device, but I really love the hw of the Note 4*...
Is it possible to have "the best of both worlds" or close? I realise it's not an option so early in the device's life-cycle, but later perhaps?
Thank-you.
*Also considering the Note Edge (more research needed), but not 100% sold on it yet, unless someone can make a compelling case
jalyst said:
Been many a yore since I've been on Android consistently, been out-of-the-loop since the earliest days.
Just curious, is it technically possible to get a "Nexus-like" experience on a device like the Note 4 nowadays?
I'm attracted by all the sw/service benefits of a Nexus device, but I really love the hw of the Note 4*...
Is it possible to have "the best of both worlds" or close? I realise it's not an option so early in the device's life-cycle, but later perhaps?
Thank-you.
*Also considering the Note Edge (more research needed), but not 100% sold on it yet, unless someone can make a compelling case
Click to expand...
Click to collapse
What you want is a rom based on AOSP (like cyanogenmod). It has the advantage of being nearly stock android with updates nearly as fast as google can push them out. It is much much quicker than carrier updates. Plus, AOSP is community/google supported so you can count on updates long after the carriers stop supporting your phone. This support is what allows kitkat to run on a galaxy s2 or a barnes and noble nook. lol.
So the catch to all this is you MUST have an unlocked bootloader. ATT and verizon are out because they have locked their bootloader.
On the note 3, people who had the tmobile note 3 (unlocked bootloader) had kitkat months and months before the ATT touchwiz kitkat was pushed by ATT.
But I'm not worried all that much about carriers not supporting my phone...
I usually buy unbranded/unlocked (i.e. outright: it makes more sense in my country -not USA), I imagine the same -or similar- applies to ODM/OEM's?
How far out are they (AOSP-based ROMS like CM) exactly from being stock Android?*
Are there many major differences, or only some minor ones, what are they exactly?
Thank-you/goodnight, bed time, 2am!
*i.e. what we have on Nexus devices
^Anyone? Thank-you!
P.S.
How do we delete posts, it says "EDIT/DELETE" but I can't find delete anywhere!?
jalyst said:
How far out are they (AOSP-based ROMS like CM) exactly from being stock Android?*
Are there many major differences, or only some minor ones, what are they exactly?
Thank-you/goodnight, bed time, 2am!
*i.e. what we have on Nexus devices
Click to expand...
Click to collapse
It's as close as you can get, almost to the point of being the same. I honestly can't think of any major differences. My wife went from CM to a nexus 5 and she new exactly where everything was. My nexus 7 interface looks like my cm11 nook tablets.
Apart from the UX though, what are all the major (or minor) services/functionalities you lose?*
I mean mostly compared to stock Android that's found on the latest Nexus devices, but I guess also compared to Samsung's spin.
Also, you missed this post...
http://forum.xda-developers.com/note-4/help/stock-android-t2882646/post55566887
Finally, any idea how to delete posts?
Cheers mate!
*Given that mircury isn't sure on this point, can someone else please have a crack.
The main issues with going to AOSP are the inferior camera app and the lack of multiwindow support. With the big Volantis tablet coming out soon, Google may finally bake some multiwindow support into "L", and maybe devs can use the RAW access APIs to fix the camera, but I wouldn't expect miracles out of the box.
If you do want AOSP, you'll probably want to get a Qualcomm-based Note instead of an Exynos one - for various reasons a lot of the dev goes quicker on the Qualcomm platform. Not sure which will be the standard version in your country.
s44 said:
The main issues with going to AOSP are the inferior camera app and the lack of multiwindow support. With the big Volantis tablet coming out soon, Google may finally bake some multiwindow support into "L", and maybe devs can use the RAW access APIs to fix the camera, but I wouldn't expect miracles out of the box.
Click to expand...
Click to collapse
That's literally it? That's nothing if that's all there is!?!
I'm used to hanging out mostly on quite esoteric/hack-ish platforms, so if that's all I have to deal with, "no biggy".
If you do want AOSP, you'll probably want to get a Qualcomm-based Note instead of an Exynos one - for various reasons a lot of the dev goes quicker on the Qualcomm platform. Not sure which will be the standard version in your country.
Click to expand...
Click to collapse
Yeah I suspected that might be the case, I haven't checked that yet, I'm in Australasia/Oceania, Australia specifically.
I hope I've lucked out there, IIRC the international version (i.e. not local/telco-centric) usually is Qualcomm isn't it?
And this post???
http://forum.xda-developers.com/note-4/help/stock-android-t2882646/post55566887
Also, anyone know how to delete posts?
Thank-you.
...
*BUMP* @ anyone
TY/GN
No need to bump your post 3 times. I would suggest you go on youtube and watch some video reviews. You will find that it is very much nexus like with no features lost.
Pretty sure you'll lose any proprietary stuff. Like the heartrate sensor...etc...especially the special uses for the S-Pen.
SiNJiN76 said:
Pretty sure you'll lose any proprietary stuff. Like the heartrate sensor...etc...especially the special uses for the S-Pen.
Click to expand...
Click to collapse
He's talking about the difference between stock android on a nexus device and aosp. The stock rom from Samsung is a totally different ballgame.
mircury said:
No need to bump your post 3 times.
Click to expand...
Click to collapse
Bumped twice, both with healthy time gaps. Going to YT won’t get this addressed:
jalyst said:
But I'm not worried all that much about carriers not supporting my phone...
I usually buy unbranded/unlocked (i.e. outright: it makes more sense in my country -not USA), I imagine the same -or similar- applies to ODM/OEM's?
Click to expand...
Click to collapse
Or this…
jalyst said:
How do we delete posts, it says "EDIT/DELETE" but I can't find delete anywhere!?
Click to expand...
Click to collapse
jalyst said:
^Anyone? Thank-you!
Click to expand...
Click to collapse
You forgot this one in your list.
Well, that was more than day earlier, but aside from that, able to address the 2 points above?
SiNJiN76 said:
Pretty sure you'll lose any proprietary stuff. Like the heartrate sensor...etc...especially the special uses for the S-Pen.
Click to expand...
Click to collapse
Is that the only notable proprietary stuff that will go?
And is it unlikely that the AOSP community will eventually add support for such things?
mircury said:
He's talking about the difference between stock android on a nexus device and aosp. The stock rom from Samsung is a totally different ballgame.
Click to expand...
Click to collapse
No I'm talking about all 3, i.e...
If I switch to AOSP (CM etc) what features will be missing* compared to: (1) stock on Nexus devices, & (2) stock Android for the Note 4.
Although I'm mostly interested in the former...
As I can easily work out the latter once (if) I have a Note 4, simply by using Samsung's flavour of Android for a while.
*& what bugs will I encounter
jalyst said:
Well, that was more than day earlier, but aside from that, able to address the 2 points above?
No I'm talking about all 3, i.e...
If I'm to switch to AOSP what features will I be missing* compared to stock on Nexus devices, & stock Android for the Note 4.
Although I'm mostly interested in the former...
As I can easily work out the latter once (if) I have a Note 4, simply by using Samsung's flavour of Android for a while.
*& what bugs will I encounter
Click to expand...
Click to collapse
So we've basically established in previous posts that AOSP = Nexus features wise. No need to hash that out again.
Compared to Samsung's stock rom there is a TON of stuff and even more stuff when compared to Samsung's stock rom after each carrier has had it's way with it.
1. Multi windows
2. all the Spen features (Some spen features can be added back. See thread in note 3 forum.)
3. Tmobile wifi calling
4. Touchwiz
5. Different Notification pull down.
6. Different settings menus.
7. Carrier Bloatware
8. 4K recording not available in stock AOSP. Some have used Oneplus camera app. (Camera app not as good as Samsung's stock)
9. HDMI out not working.
10. NFC not working on some builds.
11. All the Samsung specific apps like milk music and SBeam.
12. Tethering limitations on the Carrier version stock (This is a big one)
I'll add more as I think of them...
mircury said:
So we've basically established in previous posts that AOSP = Nexus features wise. No need to hash that out again.
Click to expand...
Click to collapse
But have we really? Not so sure about that. What's been put forward so far doesn't seem iron-clad conclusive.
Compared to Samsung's stock rom there is a TON of stuff, and even more stuff when compared to Samsung's stock rom after each carrier has had it's way with it.
1. Multi windows
2. all the Spen features
3. Tmobile wifi calling
4. Touchwiz
5. Different Notification pull down.
6. Different settings menus.
7. Carrier Bloatware
8. 4K recording not available (Camera app not as good as Samsung's stock)
9. HDMI out not working.
10. NFC not working on some builds.
11. All the Samsung specific apps like milk music and SBeam.
12. Tethering limitations on the Carrier version stock (This is a big one)
I'll add more as I think of them...
Click to expand...
Click to collapse
Cheers buddy...
Don't care about what carriers may or may not add, I'll most likely be getting one that isn't carrier-based.
Even if I do get one from a carrier it won't be a US-based one, it'll most likely be from Telstra, & IME it never adds anything of value.
jalyst said:
But have we really? Not so sure about that. What's been put forward so far doesn't seem iron-clad conclusive.
Click to expand...
Click to collapse
I thought we did. lol. I don't know how much clearer we can get. Google controls AOSP. It is stock android through and through. Go read up on what AOSP is and then read what CM is.
hello everyone!
I'm thinking of finally buying a tablet and came here to see what roms were available foR the s4 tab. However, does the size of the tablet matter for the rom and where do i find the the model number for the device? Or would anyone suggest a better tablet my only requirment is it needs a micro sd slot and preferably under 350.
Thanks to anyone who can help.
from my understanding, yes the size of the tablet does matter, as well as the brand.
At&t has a locked bootloader so everything besides root is a no go as of right now. and root requires some work on at&t. (http://forum.xda-developers.com/tab-4/general/rooted-nk2-att-t377a-t2992639)
as for the model number as far as I know, you can only get find that once you have the device under "about device" in settings. at&t 8" is sm-t337a (I would imagine all at&t devices end in the "a"" ) - other than that no real clue besides googeling
Bishtaw said:
hello everyone!
I'm thinking of finally buying a tablet and came here to see what roms were available foR the s4 tab. However, does the size of the tablet matter for the rom and where do i find the the model number for the device? Or would anyone suggest a better tablet my only requirment is it needs a micro sd slot and preferably under 350.
Thanks to anyone who can help.
Click to expand...
Click to collapse
The model numbers go SM-T### (# = number). SM-T23# is a 7.0 inch, SM-T33# is an 8.0 inch, and SM-T53# is a 10.1 inch. If the last number is 0 it's a Wi-Fi only model, if not it's most likely either 3G or 4G LTE. Model number is crucial to the rom; roms are designed for specific model numbers, with only a small amount of cross-compatibility (if any at all). Right now there are a bunch of Cyanogenmod roms out for the Wi-Fi only models of the 10.1; all other sizes and models only have stock-based rom. That might be changing soon, but it's hard to tell for sure. I'm fairly certain all variants come with a micro sd slot.
OK thanks I'm definitely getting wifi only. probably gonna get 10.1 since I'll be rooting and getting a rom immediately.
Bishtaw said:
OK thanks I'm definitely getting wifi only. probably gonna get 10.1 since I'll be rooting and getting a rom immediately.
Click to expand...
Click to collapse
Didn't want to tell you what to do but now that you've said this, I think that's the smartest move. Plenty o' roms. And just so you know, the model number for WiFi only is SM-T530, there is also a version with an IR blaster, SM-T530NU. Any ROM designed for one will work perfectly fine on the other, with the only issue of course being potentially losing IR function if you have it going to a ROM that doesn't. That said custom kernels have just been released to address that exact issue, so it really is a great time to have this model. I am posting this using my SM-T530NU running CM12.1, a rom originally designed for the SM-T530.
TLDR: Good choice and don't get hung up on T530 vs T530NU
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.
Hi Friends,
Hope you're all having a great new year. So last time I was lurking the S7E forums, we had a leaked Engineering Bootloader that was used to acquire root on all US Snapdragon models, albeit, with a lot performance issues and etc.
I came here to glance as well as all other variant forums for the SD model and now we have Root for every model, with even ROMs being baked like the Echo ROM for Verizon, Sprint, AT&T models, usually the toughest to achieve these things on. I'm trying to read through the forums, but I fear I'm missing the details, that will help me pull the trigger for getting the device or not.
Can one of you very experienced, knowledgeable, and kind members educate me on the latest?
1. Do we have unlocked Bootloader and Root for all US carrier S7Es? How is it done? I use people using Flashfire. So no TWRP?
2. Does this process still trip Knox and render Samsung Pay to never be used again on the device?
3. If I bought the Verizon variant, for example, can I root, unlock Bootloader, and etc, and then return to stock, to return to the store in case I don't like the phone?
4. Xposed Framework working for all models?
Much appreciate your responses, any and all of them in advance! Thanks!
ProFragger said:
Hi Friends,
Hope you're all having a great new year. So last time I was lurking the S7E forums, we had a leaked Engineering Bootloader that was used to acquire root on all US Snapdragon models, albeit, with a lot performance issues and etc.
I came here to glance as well as all other variant forums for the SD model and now we have Root for every model, with even ROMs being baked like the Echo ROM for Verizon, Sprint, AT&T models, usually the toughest to achieve these things on. I'm trying to read through the forums, but I fear I'm missing the details, that will help me pull the trigger for getting the device or not.
Can one of you very experienced, knowledgeable, and kind members educate me on the latest?
1. Do we have unlocked Bootloader and Root for all US carrier S7Es? How is it done? I use people using Flashfire. So no TWRP?
2. Does this process still trip Knox and render Samsung Pay to never be used again on the device?
3. If I bought the Verizon variant, for example, can I root, unlock Bootloader, and etc, and then return to stock, to return to the store in case I don't like the phone?
4. Xposed Framework working for all models?
Much appreciate your responses, any and all of them in advance! Thanks!
Click to expand...
Click to collapse
Absolutely nothing has changed on root (only possible due to ENG kernel) and bootloader unlock (which is not yet possible).
1. No
2. No
3. No
4. No idea about all models. For the t-mobile one, please check: https://forum.xda-developers.com/tmobile-s7-edge/how-to/guide-installing-xposed-framework-t3414718
You can use the search feature in xda for finding out
CravingMender9 said:
Absolutely nothing has changed on root (only possible due to ENG kernel) and bootloader unlock (which is not yet possible).
1. No
2. No
3. No
4. No idea about all models. For the t-mobile one, please check: https://forum.xda-developers.com/tmobile-s7-edge/how-to/guide-installing-xposed-framework-t3414718
You can use the search feature in xda for finding out
Click to expand...
Click to collapse
Hey bud, thanks for getting the ball rolling on these questions. If you could add some more information, I'd appreciate it :
If we still don't have a way to Root or Unlock bootloader, how are these ROMs (Echo, Tek, and other stock ROMs) available with root? And how are these flashed? Are we somehow bypassing the BL by using FlashFire?
Can you also educate me on the U Firmware and why people install it and is it reverseable?
Lastly, if I got a T-Mobile variant for example, installed these ROMs Tek, Echo, etc, can I return to Stock completely and return to T-Mobile, by any chance for them to take it back? Thank you again!
for the t mobile variant, I was able to flash the U firmware and flash back to stock t mobile. NOTE: I did not flash the U bootloader. I kept the T mobile bootloader just be sure I could flash back to stock t mobile(APK1). I'm sure this method would work with other carriers as well. so what ever variant you have, make sure you stay on that BL and only flash the U firmware CSC and AP. As for the CP(modem) I would flash your carriers latest CP file. That's what worked best for me with the U firmware. Currently I'm using the latest nougat BETA
Thank you very much for your response, bud. One last follow up question: Since all the US variants are rooting based on the ENG Kernel, is there really a benefit of getting one variant over another, for rooting or etc purposes?
P. S. May I ask why you flashed the U Firmware? What are the advantages of it? ?
ProFragger said:
Thank you very much for your response, bud. One last follow up question: Since all the US variants are rooting based on the ENG Kernel, is there really a benefit of getting one variant over another, for rooting or etc purposes?
P. S. May I ask why you flashed the U Firmware? What are the advantages of it?
Click to expand...
Click to collapse
The u firmware basically does not include all of the software that is usually included with the phone. For example.. Tmobile with their software on it, Verizon att etc... Makes the phone a bit snappier especially if you were to root. Even tho I hope for a more stable root still. I am rooted at the moment. Wish they didn't recall the note 7 because the root on that was better
ProFragger said:
Hi Friends,
Hope you're all having a great new year. So last time I was lurking the S7E forums, we had a leaked Engineering Bootloader that was used to acquire root on all US Snapdragon models, albeit, with a lot performance issues and etc.
I came here to glance as well as all other variant forums for the SD model and now we have Root for every model, with even ROMs being baked like the Echo ROM for Verizon, Sprint, AT&T models, usually the toughest to achieve these things on. I'm trying to read through the forums, but I fear I'm missing the details, that will help me pull the trigger for getting the device or not.
Can one of you very experienced, knowledgeable, and kind members educate me on the latest?
1. Do we have unlocked Bootloader and Root for all US carrier S7Es? How is it done? I use people using Flashfire. So no TWRP?
2. Does this process still trip Knox and render Samsung Pay to never be used again on the device?
3. If I bought the Verizon variant, for example, can I root, unlock Bootloader, and etc, and then return to stock, to return to the store in case I don't like the phone?
4. Xposed Framework working for all models?
Much appreciate your responses, any and all of them in advance! Thanks!
Click to expand...
Click to collapse
You're confused. At least, you were.
We do not have an "unlocked Bootloader" and we never did. We had an engineering kernel. That engineering kernel allows certain commands that enabled us to acquire root access. But without that kernel, the system (with the original kernel or boot partition) checks for any changes in the /system partition. If any are found it triggers a bootloop. So basically, if you want root we MUST have the engineering kernel. Unless someone else finds another way that's just the way that it is.
Personally, I unrooted and went back to stock. Root was okay at first but with the lack of development, Samsung Pay and the fact that Android 7+ will probably not be seeing root... well... time to accept the fact that Samsung owns the phone even though we bought it. What else can we do?
nitroevo said:
The u firmware basically does not include all of the software that is usually included with the phone. For example.. Tmobile with their software on it, Verizon att etc... Makes the phone a bit snappier especially if you were to root. Even tho I hope for a more stable root still. I am rooted at the moment. Wish they didn't recall the note 7 because the root on that was better
Click to expand...
Click to collapse
Binary100100 said:
You're confused. At least, you were.
We do not have an "unlocked Bootloader" and we never did. We had an engineering kernel. That engineering kernel allows certain commands that enabled us to acquire root access. But without that kernel, the system (with the original kernel or boot partition) checks for any changes in the /system partition. If any are found it triggers a bootloop. So basically, if you want root we MUST have the engineering kernel. Unless someone else finds another way that's just the way that it is.
Personally, I unrooted and went back to stock. Root was okay at first but with the lack of development, Samsung Pay and the fact that Android 7+ will probably not be seeing root... well... time to accept the fact that Samsung owns the phone even though we bought it. What else can we do?
Click to expand...
Click to collapse
Thanks for your helpful responses fellas. I understand root is not perfect, but for some folks like me, Xposed seems to be worth the trouble. For Samsung Pay, I intend to use the Gear S3 one day ?.
Final question, since all US Snapdragon models are using the engineering kernel to root and etc... Is there a benefit of getting one carrier variant, over another? For example, Verizon is usually the cheapest. Is it wise to get that, with the U Firmware, to use on AT&T? Thanks!
ProFragger said:
For Samsung Pay, I intend to use the Gear S3 one day .
Final question, since all US Snapdragon models are using the engineering kernel to root and etc... Is there a benefit of getting one carrier variant, over another? For example, Verizon is usually the cheapest. Is it wise to get that, with the U Firmware, to use on AT&T? Thanks!
Click to expand...
Click to collapse
Let me know if that works out for you then.
I just purchased the S2 Classic (on T-Mobile) and use Samsung Pay quite a bit. But I can tell you that it does open Samsung Pay on the phone and if you are rooted, Samsung Pay will not work at all. So I'm not sure if it will work at all for you even with the S3.
In regards to your other inquiry, I haven't tried the U firmware. I read something about data issues, no wifi calling (which is pretty important to me), no hotspot (which is also really important to me) but I heard that it is really fast. Not sure how much of that is still a problem but you should probably read up on it before doing anything first. But the rooting method is all the same between carriers I believe. All require the engineering kernel and breaks Samsung Pay along with a couple of other apps.
Just make back ups, have a stock firmware available to flash with ODIN just in case and remember that it's almost impossible to brick this device (because we don't have an unlocked bootloader.)
Binary100100 said:
Let me know if that works out for you then.
I just purchased the S2 Classic (on T-Mobile) and use Samsung Pay quite a bit. But I can tell you that it does open Samsung Pay on the phone and if you are rooted, Samsung Pay will not work at all. So I'm not sure if it will work at all for you even with the S3.
In regards to your other inquiry, I haven't tried the U firmware. I read something about data issues, no wifi calling (which is pretty important to me), no hotspot (which is also really important to me) but I heard that it is really fast. Not sure how much of that is still a problem but you should probably read up on it before doing anything first. But the rooting method is all the same between carriers I believe. All require the engineering kernel and breaks Samsung Pay along with a couple of other apps.
Just make back ups, have a stock firmware available to flash with ODIN just in case and remember that it's almost impossible to brick this device (because we don't have an unlocked bootloader.)
Click to expand...
Click to collapse
Thank you again for a helpful post. So the S3 has a dedicated MST/NFC chip in it, that allows for Samsung Pay to work from the watch, it's done through the Gear app. That's what I have read.
About the rest of it, again, curious to see if there is one US variant, superior to another in terms of Root capabilities or bands and radios available and etc? Can anyone confirm this for me?
Thanks!
ProFragger said:
Thank you again for a helpful post. So the S3 has a dedicated MST/NFC chip in it, that allows for Samsung Pay to work from the watch, it's done through the Gear app. That's what I have read.
Click to expand...
Click to collapse
So does the S2.
When I was setting up the Samsung Pay on my watch it said that it had to download an update.
Then I went through the setup process through my phone which was from the Samsung Pay app.
You go to "Add card" on your watch and it opens Samsung Pay on your phone.
You click "Next" and it displays your Samsung account information.
Then it takes you to a screen that says "Setup complete" telling you that you're ready to use it and at the bottom says "Add card"
You do that all from the Samsung Pay app on your phone which leads me to suspect that if you root your phone, you won't be able to use Samsung Pay on your watch.
People on this thread that you have to set it all up first, remove the Samsung Pay app on the phone but leave it on the watch. If it's all done correctly then it should work. Just make sure you get it all set up first.
Next thing that I'm going to try is using my watch in "Standalone" with my phone out of bluetooth or wifi range. See if that still works.
ProFragger said:
About the rest of it, again, curious to see if there is one US variant, superior to another in terms of Root capabilities or bands and radios available and etc? Can anyone confirm this for me?
Thanks!
Click to expand...
Click to collapse
As far as I know, the U firmware permits use of some other bands that aren't normally used. Not sure which ones though.
Binary100100 said:
So does the S2.
When I was setting up the Samsung Pay on my watch it said that it had to download an update.
Then I went through the setup process through my phone which was from the Samsung Pay app.
You go to "Add card" on your watch and it opens Samsung Pay on your phone.
You click "Next" and it displays your Samsung account information.
Then it takes you to a screen that says "Setup complete" telling you that you're ready to use it and at the bottom says "Add card"
You do that all from the Samsung Pay app on your phone which leads me to suspect that if you root your phone, you won't be able to use Samsung Pay on your watch.
People on this thread that you have to set it all up first, remove the Samsung Pay app on the phone but leave it on the watch. If it's all done correctly then it should work. Just make sure you get it all set up first.
Next thing that I'm going to try is using my watch in "Standalone" with my phone out of bluetooth or wifi range. See if that still works.
As far as I know, the U firmware permits use of some other bands that aren't normally used. Not sure which ones though.
Click to expand...
Click to collapse
Thanks for the correction/education on the S2, bud, much appreciated. I wonder if the rooted phone works with the S3, because Samsung has allowed many other non Samsung phones to know work with the S3? But I could be wrong, I thought it was open like that with the S2 as well, no? Looking forward to your testing, hope there is a breakthrough in there! ?
if you want root and customizability and roms, just don't get this phone. you will be very disappointed with the performance once you root and it gets so much worse with Xposed. not worth it at all, you will have better performance and speed from a 4 year old phone that has an unlocked bootloader and strong development. I mean my Nexus 5 (from 2012) had better performance than my rooted S7. it sounds like you do want roms, and if you want roms then AOSP/Cyanogenmod is the way to go. there will probably never be any AOSP or CM ROM on the QC S7/E so you're better off getting an older galaxy model that does have a great development community and unlocked bootloader. or just get a OnePlus or Nexus or something.
xVermicide said:
if you want root and customizability and roms, just don't get this phone. you will be very disappointed with the performance once you root and it gets so much worse with Xposed. not worth it at all, you will have better performance and speed from a 4 year old phone that has an unlocked bootloader and strong development. I mean my Nexus 5 (from 2012) had better performance than my rooted S7. it sounds like you do want roms, and if you want roms then AOSP/Cyanogenmod is the way to go. there will probably never be any AOSP or CM ROM on the QC S7/E so you're better off getting an older galaxy model that does have a great development community and unlocked bootloader. or just get a OnePlus or Nexus or something.
Click to expand...
Click to collapse
Or a Exynos S7.
Binary100100 said:
Or a Exynos S7.
Click to expand...
Click to collapse
exactly this. except for some reason I thought exynos variants are lacking certain bands/features on American networks. could be wrong.
xVermicide said:
if you want root and customizability and roms, just don't get this phone. you will be very disappointed with the performance once you root and it gets so much worse with Xposed. not worth it at all, you will have better performance and speed from a 4 year old phone that has an unlocked bootloader and strong development. I mean my Nexus 5 (from 2012) had better performance than my rooted S7. it sounds like you do want roms, and if you want roms then AOSP/Cyanogenmod is the way to go. there will probably never be any AOSP or CM ROM on the QC S7/E so you're better off getting an older galaxy model that does have a great development community and unlocked bootloader. or just get a OnePlus or Nexus or something.
Click to expand...
Click to collapse
Binary100100 said:
Or a Exynos S7.
Click to expand...
Click to collapse
xVermicide said:
exactly this. except for some reason I thought exynos variants are lacking certain bands/features on American networks. could be wrong.
Click to expand...
Click to collapse
Very helpful inputs guys, thank you! If I were to be honest with myself, I don't want AOSP/CM/Lineage, especially on a Samsung phone, so unlocked bootloader is not a deal breaker for me. However, I think root is cool for me for doing some SystemUI tweaks, Xposed and etc. Exynos was an option I was exploring, but lack of warranty, no Samsung Pay, and the price are enough to keep me at bay. I think I just need to put my big boy pants on and try to use a phone without rooting it. Something I have yet to do in EVER using an Android phone since about 10 years ago, and I have never ever used or bought an iCrap... I mean... an iPhone !
ProFragger said:
Very helpful inputs guys, thank you! If I were to be honest with myself, I don't want AOSP/CM/Lineage, especially on a Samsung phone, so unlocked bootloader is not a deal breaker for me. However, I think root is cool for me for doing some SystemUI tweaks, Xposed and etc. Exynos was an option I was exploring, but lack of warranty, no Samsung Pay, and the price are enough to keep me at bay. I think I just need to put my big boy pants on and try to use a phone without rooting it. Something I have yet to do in EVER using an Android phone since about 10 years ago, and I have never ever used or bought an iCrap... I mean... an iPhone !
Click to expand...
Click to collapse
Get a One+ 3T good development and really nice phone if you want root. Root is dead on Samsung phones and so are ROMs.
So by reading thru this thread, I assume having a T-mobile S7E (G935T) rooting is pointless and really not available the way I'm used to it coming from a Note 4. That's kind of a bummer... I've been using Android and have always had ROOT and all the goodies that come with it. And I recently starting really enjoying my Note 4 with all the cool development in Note 7 ported roms oh well... I wonder if the S7E is enough of an upgrade to keep my interest as stock?
I see there is a G935U firmware, but that seems a bit hit and miss? But I'm just starting to read up on all this... :good:
ShrekOpher said:
Get a One+ 3T good development and really nice phone if you want root. Root is dead on Samsung phones and so are ROMs.
Click to expand...
Click to collapse
Believe me bud, if Oneplus 5 or even 3T had an SD Card, I'd already have that phone, but thanks for your wisdom !
Araltd said:
So by reading thru this thread, I assume having a T-mobile S7E (G935T) rooting is pointless and really not available the way I'm used to it coming from a Note 4. That's kind of a bummer... I've been using Android and have always had ROOT and all the goodies that come with it. And I recently starting really enjoying my Note 4 with all the cool development in Note 7 ported roms oh well... I wonder if the S7E is enough of an upgrade to keep my interest as stock?
I see there is a G935U firmware, but that seems a bit hit and miss? But I'm just starting to read up on all this... :good:
Click to expand...
Click to collapse
You and I both man... The last few years, I have lived off the mercy of T-Mobile and their BLs being unlocked. But Samsung sure done them all in ! Even the International unlocked ones disable Samsung Pay (forever, mind you!) if Knox is tripped, which I believe it is, when rooted and TWRP'd.
As I understand it,
Android pay / Samsung pay is why they frown on rooting now. I can understand it, though I don't agree with it.
The first time someone's financial information is compromised, and they've ever used one of the "pay" methods, on a rooted device the pr nightmare that would ensue would make the note 7 fiasco look like child's play.
"Samsung unsecured device compromises persons credit card information today, while Apple is still secure" I can see the headline.
Sent from my Samsung Galaxy S7E