Related
So with the inevitable release of KitKat tomorrow, I have the quandary of upgrading or not. I understand the 4.4 will kill my root, but I really haven't used the root option due to interceding life getting in the way since I rooted it (originally I was going to use Ti Backup and go from there, but have never bought it). So losing root is not a huge deal breaker one way or another currently.
With the leaked build, does it look like a good update to do or has the current ROM users of KitKat feel it's not worth it? I'd like to get some input to help make up my mind...
scottiemedic said:
So with the inevitable release of KitKat tomorrow, I have the quandary of upgrading or not. I understand the 4.4 will kill my root, but I really haven't used the root option due to interceding life getting in the way since I rooted it (originally I was going to use Ti Backup and go from there, but have never bought it). So losing root is not a huge deal breaker one way or another currently.
With the leaked build, does it look like a good update to do or has the current ROM users of KitKat feel it's not worth it? I'd like to get some input to help make up my mind...
Click to expand...
Click to collapse
I own both an I337 and an M919 and, given the flexibility of the M919, I was able to try both official and leaked 4.4 TW releases mainly for the I9505. Based on those experiences I would say take the update. 4.4 update should be noticeably faster.
In regard to keeping root, I'm hoping SuperSu Pro's Survival mode works.
I'd say go with the update if you don't care about root. The only problem is Knox is more locked down, also more bloat/crap ware on the new update. I do love the camera on the lockscreen, plus the album artwork on the lock screen is a big + for me. I don't know if art is implemented into the gs4 but it does make a difference but the only thing is, is that most apps are not optimized for it yet.
Sent from my XT1058 using xda premium
So should I revert the few changes I have done? IE, I've killed startup apps with ES Task Manager and (obviously) disabled the software update checker.
I'm on the original/not locked down 4.2.2. What do I need to do, to accept the update? I too found that I don't use Root much, but T.B. would be nice to have. I have clockword installed now as a bootloader, so maybe I need to revert to stock bootloader somehow. Previous OTA's have failed.
As far as experience goes, I say wait and keep your options open. I like the freedom of a clean rom, free from bloat and clutter of apps that i dont use. Not to mention a battery life that exceeds far beyond a regular un-rooted device. Visit the numerous threads of other people's experiences. I'm rooted and have been able to try out different rooms from 4.2 to 4.4. Accepting an ota will unroot your device without anyway of reverting back. Good luck with your decision.
Sent from my GT-I9505 using XDA Premium 4 mobile app
aiwapro said:
I'm on the original/not locked down 4.2.2. What do I need to do, to accept the update? I too found that I don't use Root much, but T.B. would be nice to have. I have clockword installed now as a bootloader, so maybe I need to revert to stock bootloader somehow. Previous OTA's have failed.
Click to expand...
Click to collapse
If you're on the not locked down version, then you shouldn't take the update. It will lock your bootloader and that device will never see an AOSP ROM again. You should wait for something like StockUp to be updated to the new 4.4 or use any of the many other 4.4 ROMs available. If you really want to get one with the stock update and locked bootloaders, I'm sure someone would love to trade.
aiwapro said:
I'm on the original/not locked down 4.2.2. What do I need to do, to accept the update? I too found that I don't use Root much, but T.B. would be nice to have. I have clockword installed now as a bootloader, so maybe I need to revert to stock bootloader somehow. Previous OTA's have failed.
Click to expand...
Click to collapse
We were able to get the MK2 tar files rather quickly after the OTA release and will hopefully be able to get the 4.4 tars just as quickly. If that's the case you will be able to flash all partitions, except the bootloader, to run the 4.4 ROM and keep your unlocked bootloader. I would not give up the unlocked bootloader if I were you.
scottiemedic said:
So with the inevitable release of KitKat tomorrow, I have the quandary of upgrading or not. I understand the 4.4 will kill my root, but I really haven't used the root option due to interceding life getting in the way since I rooted it (originally I was going to use Ti Backup and go from there, but have never bought it). So losing root is not a huge deal breaker one way or another currently.
With the leaked build, does it look like a good update to do or has the current ROM users of KitKat feel it's not worth it? I'd like to get some input to help make up my mind...
Click to expand...
Click to collapse
Sounds like you are not someone that really uses or needs root like us flashaholics. I love having complete control over my devices. The extraordinary battery life, increased performance, extra capabilities like tethering and so forth. If I want to delete an un-wanted app or service ( At&t navigator anyone) or try a new rom I can. With a stock rom with locked boot loaders (really an oxymoron for "open source" Android isn't it?) you have what you get, like it or not. It's sad they load these awesome devices up with so much performance killing bloat ware. It's like buying a new corvette & then attaching a loaded u-haul trailer to it. What's the point of having it if you can't use it as intended? Anyway my 2 cents worth. Choose your path wisely grasshopper, as there's no turning back.
Hello everyone!
I have been thinking about getting myself one of these lovely phones but after reading what y'all have been saying about the locked bootloader I'm not sure I want to... I won't be able to actually get a phone until next week so I'm assuming it will come already pre-loaded with this update??
I would like to be able to root this phone just like I did my old ET4G from Sprint... would this be an option if I was to get one next week?
Just an FYI I will be on the AT&T network.
ttfn
CDL
crazy_dragonlady said:
Hello everyone!
I have been thinking about getting myself one of these lovely phones but after reading what y'all have been saying about the locked bootloader I'm not sure I want to... I won't be able to actually get a phone until next week so I'm assuming it will come already pre-loaded with this update??
I would like to be able to root this phone just like I did my old ET4G from Sprint... would this be an option if I was to get one next week?
Just an FYI I will be on the AT&T network.
ttfn
CDL
Click to expand...
Click to collapse
Get a nexus 5. You'll love it
Sent from my Nexus 5
jd1639 said:
Get a nexus 5. You'll love it
Sent from my Nexus 5
Click to expand...
Click to collapse
AT&T doesn't offer that phone... unless I'm just not seeing it LOL
crazy_dragonlady said:
AT&T doesn't offer that phone... unless I'm just not seeing it LOL
Click to expand...
Click to collapse
They don't but it works fine on att. Very easy to root and mod. No locked bootloader.
Sent from my Nexus 5
John The Rhino said:
Sounds like you are not someone that really uses or needs root like us flashaholics. I love having complete control over my devices. The extraordinary battery life, increased performance, extra capabilities like tethering and so forth. If I want to delete an un-wanted app or service ( At&t navigator anyone) or try a new rom I can. With a stock rom with locked boot loaders (really an oxymoron for "open source" Android isn't it?) you have what you get, like it or not. It's sad they load these awesome devices up with so much performance killing bloat ware. It's like buying a new corvette & then attaching a loaded u-haul trailer to it. What's the point of having it if you can't use it as intended? Anyway my 2 cents worth. Choose your path wisely grasshopper, as there's no turning back.
Click to expand...
Click to collapse
I guess I've just never gotten any real good info on WHAT my rooted GS4 can do. I'd love to extend battery life and tether, but without really knowing all the possible downfalls, I've never pulled the trigger on like system apps, bloatware, etc. You know of a good resource for slightly technical people with clear definitions of what certain programs do and what can and can't be deleted?
I think at the time I rooted (I'm a MF3 S4), there was no 'unrooting' or flashing to stock, and therefore have been reluctant. I know I don't spend enough time on here learning, my 5 and 2 year old suck all my extra time away.
I'd love to maximize my phone to it's greater abilities, just overwhelmed I guess on where to start as I'm perfectly happy on 4.2 (I owned 3 iPhones before getting this one, so I have limited Android experience, but I recently also got an ASUS TF300 and rooted and ROMed my Kindle Fire almost 2 years ago to CM9).
scottiemedic said:
I guess I've just never gotten any real good info on WHAT my rooted GS4 can do. I'd love to extend battery life and tether, but without really knowing all the possible downfalls, I've never pulled the trigger on like system apps, bloatware, etc. You know of a good resource for slightly technical people with clear definitions of what certain programs do and what can and can't be deleted?
I think at the time I rooted (I'm a MF3 S4), there was no 'unrooting' or flashing to stock, and therefore have been reluctant. I know I don't spend enough time on here learning, my 5 and 2 year old suck all my extra time away.
I'd love to maximize my phone to it's greater abilities, just overwhelmed I guess on where to start as I'm perfectly happy on 4.2 (I owned 3 iPhones before getting this one, so I have limited Android experience, but I recently also got an ASUS TF300 and rooted and ROMed my Kindle Fire almost 2 years ago to CM9).
Click to expand...
Click to collapse
Hey man, no worries. The reality is I would much rather play with my kids (if I had any) than an electronic device. So it's nice to know your priorities are right. There's few picture worthy moments we get from our phones, but kids provide such memories constantly. For everyday use, stock is fine & was for me for a little while. You are doing the right thing by waiting until you know more before you do something wrong & brick your phone. This is the place where you can learn how to root, install Safestrap recovery & flash incredible custom rom on your mf3 S4 when you are ready.
While I wait for the arrival of my MXP I have some questions for the community so that I can hit the ground running. First thing, I'd like to unlock my boot loader but I was just curious if there is a way to re-lock it afterwards just in case I need to send in for repairs or something along those lines? Also wondering about VOLTE support. I see some roms that state they have it working but is this a stock feature or do I need to use a custom ROM to get VOLTE to function? Also is there any known method of rooting without unlocking the boot loader just in case re-locking it is not possible? Thanks for the help everyone.
I am coming from a g920a. That phone is torture for someone like me who likes stock Android and rooted devices. Probably the worst phone I have ever had. Can't wait to get my hands on my MXP and leaves this piece of junk behind!
I'm on Verizon and I can confirm it supports advanced calling, which is VoLTE as far as I know but it might require turning it on at the provider level.
Sent from my XT1575 using Tapatalk
I haven't messed with VoLTE yet so I can't answer those questions, but as for your others: The bootloader can be relocked, but the unlock method involves submitting an unlock request code to motorola, and they immediately email you an unlock key, along with a warning about voiding your warranty, so even relocking it does not unvoid your warranty. HOWEVER, it only voids your warranty for software issues. If it's a hardware problem unrelated to the bootloader being unlocked, they'll still handle it, and accidental drops and things are still covered if you buy an accidental damage warrenty. Also, as far as I know there is still no way to root without unlocking the bootloader.
10 characters
squallz506 said:
Volte is only available on stock roms.
Click to expand...
Click to collapse
I thought this had been fixed on AICP based ROMS?
Sent from my XT1575 using Tapatalk
countryfolk07 said:
I thought this had been fixed on AICP based ROMS?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Whoops, yeah I guess they fixed it down the line. Sorry, I've been enjoying stock+xposed too much to follow custom development.
Edit: also root without bootloader unlock will likely never happen. We have a root method already, so there's no incentive to find another method.
The answer you seek was right in the first page of this forum....
http://forum.xda-developers.com/moto-x-style/general/moto-x-style-how-to-unlock-bootloader-t3192140
That being said, I would consider waiting until after Marshmallow drops before you unlock your bootloader so as not to interfere with any OTA's. Conventional wisdom is that it is coming within the next few weeks as the "test drive" has already started and a "soak test" should follow shortly.
yeah i know it can be unlocked I already read that post. I would not have gotten this phone if the boot loader was not un-lockable. That's the whole reason I am moving away from my AT&T Galaxy s6. I was just trying to clarify if re-locking made any difference as far as the warranty is concerned. I appreciate the answers guys. Just trying to determine if I should keep it stock or use a custom ROM out of the box. Sounds like I will go stock for the time being. Now as far as unlocked boot loaders interfering with OTA's? Is this really a thing? And wouldn't somebody just post the OTA image on the forums when its ready anyway?
timde9 said:
yeah i know it can be unlocked I already read that post. I would not have gotten this phone if the boot loader was not un-lockable. That's the whole reason I am moving away from my AT&T Galaxy s6. I was just trying to clarify if re-locking made any difference as far as the warranty is concerned. I appreciate the answers guys. Just trying to determine if I should keep it stock or use a custom ROM out of the box. Sounds like I will go stock for the time being. Now as far as unlocked boot loaders interfering with OTA's? Is this really a thing? And wouldn't somebody just post the OTA image on the forums when its ready anyway?
Click to expand...
Click to collapse
Well as to it being a thing, I certainly can't say for sure. But what reason is there to unlock the bootloader if you're not going to root? And once you do that, you almost certainly will not get OTA's. What am I missing? Is there another reason you are looking to unlock?
The one thing I don't know is if there a some type of a "tamper flag" that would require something like triangle away.
You don't think you could just do a fastboot oem lock?
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
timde9 said:
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
Click to expand...
Click to collapse
I'd still recommend waiting at least a couple of weeks to see if Marshmallow shows up!
I'm coming to the MXPE from a OnePlus One which I have to say was one of the funnest phones I've ever owned. I wasiunlocked, rooted and flashing CM12.1 nightlies about twice a week.
I thought I would miss it, but so far so good on the MXPE without rooting. We'll have to see what happens after MM drops. I'd like to get it rooted, but I haven't done nearly the amount of modding you've done.
Good luck with your phone. I can honestly tell you it's a really nice device!
While its tempting to wait for marshmallow to show I cannot live without root any longer. I have already been without it for months because of this damn s6. I'm sure someone will upload the OTA as soon as it's available so I'll just flash it when the time comes.
timde9 said:
Sorry to give you the wrong impression but I fully intend to root and also install Xposed and all that good stuff. There are a lot of things I need that require these things such as BubbleUPNP's audio cast feature, and of course the all powerful AdAway and YouTube AdAway in addition to Titanium Backup and Viper4Android etc. I normally use that stuff every day and so dealing with my last phone was like living in Android Hell. All the great hardware but software that was hopelessly mangled un-rootable and just sad for such a powerful device as the s6. Being able to have these things back is my number one reason for buying this phone so you best believe that's the very first thing I will do once it comes in lol. The only reason I am so concerned about the warranty is because I have needed it in the past for several other devices and so don't want do something that is un-doable. But from the sounds of it this will only affect me if the software causes the defect and I am fairly confident I can fix anything software related all by myself. Mostly only concerned about hardware defects and if they will still be covered that is just perfect.
And already I am feeling the difference here in this part of xda. The forums for the g920-a are like calling out into the dessert, and in no time at all you guys have address my major concerns. Thanks again
Click to expand...
Click to collapse
Well if you're an xposed user you should root immediately with no concern about the 6.0 OTA, since xposed doesn't work on 6.0. I'm not moving to 6.0, myself, until xposed is released for it. I use xposed modules everyday and am not giving it up, not even for doze mode.
That's kinda how I am feeling as well. I can achieve similar results to doze with the xposed app amplify with enough tweaking so its not a big deal.
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
In case you guys haven't figured it out yet, development, Imo, is dead. There isn't stable root, no rom development outside of slightly modded stuff to change your status bar and the most recent breakthrough was substratum... Which wasn't even meant for this phone but rather the s8 but it still works. Now I use and love substratum but I really want an aosp/pixel rom and stable root and Xposed but I don't think that any of this is coming ever. I could be wrong. But I'm tired of buying locked down Samsung devices because of this. This seems more like a rant but it's more of a psa to developers who wanna help the hopeless. Ya know?
RileyIssKing said:
In case you guys haven't figured it out yet, development, Imo, is dead. There isn't stable root, no rom development outside of slightly modded stuff to change your status bar and the most recent breakthrough was substratum... Which wasn't even meant for this phone but rather the s8 but it still works. Now I use and love substratum but I really want an aosp/pixel rom and stable root and Xposed but I don't think that any of this is coming ever. I could be wrong. But I'm tired of buying locked down Samsung devices because of this. This seems more like a rant but it's more of a psa to developers who wanna help the hopeless. Ya know?
Click to expand...
Click to collapse
I purchased this phone coming from an Iphone 6Plus, thinking I could definitely obtain root on the most sold android phone still in use. Nope. Pretty disappointing as I think it may be the best phone ever made.
RileyIssKing said:
In case you guys haven't figured it out yet, development, Imo, is dead. There isn't stable root, no rom development outside of slightly modded stuff to change your status bar and the most recent breakthrough was substratum... Which wasn't even meant for this phone but rather the s8 but it still works. Now I use and love substratum but I really want an aosp/pixel rom and stable root and Xposed but I don't think that any of this is coming ever. I could be wrong. But I'm tired of buying locked down Samsung devices because of this. This seems more like a rant but it's more of a psa to developers who wanna help the hopeless. Ya know?
Click to expand...
Click to collapse
I didn't do enough research before buying S7. Coming from Nexus 6p this is really foreign to me. I saw s7 had root but didn't look into the 2 different processors, all the different carriers (it doesn't matter on Nexus devices.)
Far as Development goes...its probably not going to happen unless someone finds a way to unlock the bootloader. Next best thing might be Safe Strap but afaik there's nothing in the works.
For now I'm making the best of it. I'm having a decent experience with the Eng kernel. Currently looking into the nonrooted Rom. My hope is I'll be able to make some changes (like installing viper) then switching to the stock boot.img and trying to make those changes stick. Supposedly it's possible but I'm still trying to get some guidance. Experimenting with this phone sucks because the process for root is pretty long then setting everything up THEN it might not work so back to square one.
Especially once done with purchase plan or contract (should you have one) and out of warranty. After that point, it's mine to do with as I please! (I know, should be able to do it whenever, but I'm playing by their rules for a minute.) So it's already BS for those who bought first few months and have paid off.
Personally, what is driving me crazy is battery drain. I'm running about 144k on AnTuTu, so no major complaints with performance, but plugging it in more than once a day sucks. Power drain when I'm not doing anything: sucks. I know it's all this useless crapware running in the background, even tho I killed some with Package Disabler Pro. Just addressing that would improve my mood. If AT&T is trying to ensure we'll all look very carefully at unlocked phones next time, they are doing a bang-up job.
Hey all,
First off let me just say great work to everyone involved with rooting this now "ancient" phone, especially klabit87 and jrkruse. Additionally, I do not mean to be ungrateful with this post, nor suggest that rooting a phone is easy, especially one with a locked bootloader, or that the users here are entitled to such a feature.
With that out of the way....
I haven't looked into rooting this phone EVER until now. Haven't even peaked at XDA or Googled anything, I didn't even know it was possible until yesterday. I've re-ROMed all my previous phones but was actually satisfied with the stock S7 experience other than a Launcher swap and dealing with the always laggy Google maps. Well recently I got a new car and got fed up with the obnoxious list/action limit that Android Auto has as the voice search can be quite unreliable, the letter search is somewhat bugged on the media player I use, and in the end all it does is encourage people to just use their phone to change songs/settings and send messages, thereby completely failing at its goal of being safer. So, I really wanted to get Xposed installed to use the module that makes AA a lot more usable; however, now that I've looked back into the scene a bit, I'm not so sure I want to move forward.
To preface my question: Every Android device I've had before was essentially either rootable or not and ultimately banked on a security exploit that was eventually found. There were never really any concerns about major issues unless you were changing ROMs, kernels, or testing major CPU behavior changes. Just rooting itself was almost always issue free other than a small bug or two or the need to reapply at reboot.
From what I gather, it seems to me that they only way currently to gain root privileges on this device is to install this ENG kernel that's talked about in a lot of more recent posts. Is it truly the case that someone had to write a kernel from scratch that was pre-rooted and as of right now there is no way to root the device as it is stock? Is it that the only known exploit is how to flash another kernel, and the stock kernel is still locked up tight? It sucks that the current root seems so unstable/slow. I know there are a plethora of fixes but there really is no one major fix (other than potentially reflashing the stock bootloader that for some reason seems to work), and its a matter of installing a boat load of CPU and resource management tweaks and even then the performance/battery life isn't quite stock. Additionally it seems like its definitely a YMMV kind of thing as some users seem to still have significant battery drain or slowness/heat even after trying tons of fixes.
Since I am just now getting familiar with the "homebrew" the phone I've had for 3+ years and know nothing about the work that's been done, I genuinely just want to know the technical implications that got in the way of a cleaner root and why the current root method is stuck as sort of a work-around so to speak. The people that manage these breakthroughs rarely post about the process they went through unless its pertinent to a guide on how to root, so I was just curious why the root for this device is in the current state it is.
I would really like to root my Edge so I can be done with the AA nonsense but after just getting a new battery put in I really don't want to go through ****ty battery life again haha.
Thanks to all who weigh in.
Verizon requires most if not all manufacturers to lock the bootloaders. This is also Samsung choice as well. The T-mobile S7/edge and newer have locked bootloaders as well. Difference is T-mobile leaves it up to the OEMs whether they want to lock it or not. With some U.S. businesses and enterprises using Samsung Galaxy devices. They focus on being "enterprise ready" which makes sense from a business standpoint.
Believe it or not, Samsung used to be developer friendly when the S II came out. They even gave away Galaxy S2 devices to some XDA devs.
So, if you want a Samsung device with an unlock able bootloader. Get one that has an Exynos SoC or the Chinese Snapdragon variant.