Related
That header should be put at the top of every post that talks about the "DEVELOPER EDITION" otherwise some sad owner of the Note 4 is going to brick their phone.
doctor-cool said:
That header should be put at the top of every post that talks about the "DEVELOPER EDITION" otherwise some sad owner of the Note 4 is going to brick their phone.
Click to expand...
Click to collapse
How are they going to brick their phone? With the locked bootloader and no root, there is no recovery to flash anything.
Trying to flash any sort CF Root or custom recovery will indeed brick a Note 4 CE
Also people running out and buying the DE not knowing that the device also only has a 30 day warranty..
deathshead said:
Also people running out and buying the DE not knowing that the device also only has a 30 day warranty..
Click to expand...
Click to collapse
If you want you can buy the Samsung Samsung Protection Plus℠ Mobile Elite* for Galaxy Note® 3 and Galaxy Note® 4 for $ 129 2 yr extended warranty coverage from the DOP . http://www.samsung.com/us/owners/protection-plus/mobile-elite/
KennyG123 said:
How are they going to brick their phone? With the locked bootloader and no root, there is no recovery to flash anything.
Click to expand...
Click to collapse
KennyG123 I appreciate what you are saying but I need to disagree with the notion that there is not a need to provide a distinction between threads that focus on mods for the retail versions of the Note 4 and those that focus on the Developer Edition of the Note 4. As you know, the Retail version and the Developer Edition of the Note 4 are identical except for one very important element...the bootloader. Mods/hacks etc. designed for one can be very detrimental to the other. They are not compatible in this respect.
I'm sure with your experience and expertise that you have seen many, perhaps hundreds, of inexperienced users, excited about taking advantage of their new Android phone and its potential for modding, do something that bricks their phone because they simply didn't know better. Distinguishing threads intended for Developer Edition phones is not intended to benefit the knowledgeable "crack flasher", developer, coder or themer, it is intended to help the "noob" or less experience user from doing something that will brick their phone or lock their bootloader.
With recovery and root now available for the Developer Edition Note 4 ROMs are not far behind. And, hopefully root and SafeStrap will be available for the retail version soon. With that/those events, the ability for new/inexperienced users (both retail owners and developer edition owners) to separate what's safe to flash and what isn't is going to get very complicated. This is only going to be compounded as OTAs begin to be released and different version of firmware start to show up for users to flash. Having a way to separate or distinguish threads intended for Retail users only or Developer Edition users only makes sense to me. Just saying. No rant intended. Thank you for listening.
Only $129? Wow, what a deal. I'll take 2.
doctor-cool said:
That header should be put at the top of every post that talks about the "DEVELOPER EDITION" otherwise some sad owner of the Note 4 is going to brick their phone.
Click to expand...
Click to collapse
I absolutely agree.
doctor-cool said:
That header should be put at the top of every post that talks about the "DEVELOPER EDITION" otherwise some sad owner of the Note 4 is going to brick their phone.
Click to expand...
Click to collapse
people should read. if they dont know that their phone is locked and doesnt have recovery not my problem if they brick their device
Personally I'd rather see a separate forum for all the Developer specific stuff. Drop it all there so there is no confusion... but that's just me.
Chuck_IV said:
Personally I'd rather see a separate forum for all the Developer specific stuff. Drop it all there so there is no confusion... but that's just me.
Click to expand...
Click to collapse
No it's not just you. There are many of us forum users, both Retail and Dev Edition users, that agree with you.
jpcalhoun said:
KennyG123 I appreciate what you are saying but I need to disagree with the notion that there is not a need to provide a distinction between threads that focus on mods for the retail versions of the Note 4 and those that focus on the Developer Edition of the Note 4. As you know, the Retail version and the Developer Edition of the Note 4 are identical except for one very important element...the bootloader. Mods/hacks etc. designed for one can be very detrimental to the other. They are not compatible in this respect.
I'm sure with your experience and expertise that you have seen many, perhaps hundreds, of inexperienced users, excited about taking advantage of their new Android phone and its potential for modding, do something that bricks their phone because they simply didn't know better. Distinguishing threads intended for Developer Edition phones is not intended to benefit the knowledgeable "crack flasher", developer, coder or themer, it is intended to help the "noob" or less experience user from doing something that will brick their phone or lock their bootloader.
With recovery and root now available for the Developer Edition Note 4 ROMs are not far behind. And, hopefully root and SafeStrap will be available for the retail version soon. With that/those events, the ability for new/inexperienced users (both retail owners and developer edition owners) to separate what's safe to flash and what isn't is going to get very complicated. This is only going to be compounded as OTAs begin to be released and different version of firmware start to show up for users to flash. Having a way to separate or distinguish threads intended for Retail users only or Developer Edition users only makes sense to me. Just saying. No rant intended. Thank you for listening.
Click to expand...
Click to collapse
The only threads that need warnings are those for root and those for recovery. There has been no issue with the S4, S5 or Note 3 sections. Again without recovery nothing will flash and no harm can come to the phones. They are exactly the same devices, just bootloader unlocked. People desperate to root will try anything in spite of the warnings. As far as I have seen on previous devices attempts to install recovery will fail and worse that happened was they had to Odin in Stock tar. As I said, unlocked developers editions are not new. They have been in use for Sammy Verizon for almost 2 years with no need for a separate section. If anything the locked edition should be confined to General and Q&A. With so many variants of the same device people will always use the wrong thing. No amount of warnings has ever stopped that. Read through the Sprint S3 sections and find all the bricks caused by flashing international ROMs. Both sections have warnings posted clearly. So we really don't need "the sky is falling" kind of thing here. We just need people to read. The information is there.
KennyG123 said:
The only threads that need warnings are those for root and those for recovery. There has been no issue with the S4, S5 or Note 3 sections. Again without recovery nothing will flash and no harm can come to the phones. They are exactly the same devices, just bootloader unlocked. People desperate to root will try anything in spite of the warnings. As far as I have seen on previous devices attempts to install recovery will fail and worse that happened was they had to Odin in Stock tar. As I said, unlocked developers editions are not new. They have been in use for Sammy Verizon for almost 2 years with no need for a separate section. If anything the locked edition should be confined to General and Q&A. With so many variants of the same device people will always use the wrong thing. No amount of warnings has ever stopped that. Read through the Sprint S3 sections and find all the bricks caused by flashing international ROMs. Both sections have warnings posted clearly. So we really don't need "the sky is falling" kind of thing here. We just need people to read. The information is there.
Click to expand...
Click to collapse
Thanks KennyG123 for your response. I totally concur, reading and researching what you have and what you want to do is the first step for any user. I came to the Note 4 from the DE5 and thankfully when ROMs started to appear the developer or OPs did specify whether the ROM was for retail or DE users. I hope this will be true for the Note 4.
jpcalhoun said:
Thanks KennyG123 for your response. I totally concur, reading and researching what you have and what you want to do is the first step for any user. I came to the Note 4 from the DE5 and thankfully when ROMs started to appear the developer or OPs did specify whether the ROM was for retail or DE users. I hope this will be true for the Note 4.
Click to expand...
Click to collapse
Unfortunately this lock down of Verizon and AT&T devices has killed development since the S4. This is the other thing to think about... If someone does crack the bootloader or finds a root and SafeStrap like method, suddenly all the DE ROMs will be usable by all.
jpcalhoun said:
KennyG123 I appreciate what you are saying but I need to disagree with the notion that there is not a need to provide a distinction between threads that focus on mods for the retail versions of the Note 4 and those that focus on the Developer Edition of the Note 4. As you know, the Retail version and the Developer Edition of the Note 4 are identical except for one very important element...the bootloader. Mods/hacks etc. designed for one can be very detrimental to the other. They are not compatible in this respect.
I'm sure with your experience and expertise that you have seen many, perhaps hundreds, of inexperienced users, excited about taking advantage of their new Android phone and its potential for modding, do something that bricks their phone because they simply didn't know better. Distinguishing threads intended for Developer Edition phones is not intended to benefit the knowledgeable "crack flasher", developer, coder or themer, it is intended to help the "noob" or less experience user from doing something that will brick their phone or lock their bootloader.
With recovery and root now available for the Developer Edition Note 4 ROMs are not far behind. And, hopefully root and SafeStrap will be available for the retail version soon. With that/those events, the ability for new/inexperienced users (both retail owners and developer edition owners) to separate what's safe to flash and what isn't is going to get very complicated. This is only going to be compounded as OTAs begin to be released and different version of firmware start to show up for users to flash. Having a way to separate or distinguish threads intended for Retail users only or Developer Edition users only makes sense to me. Just saying. No rant intended. Thank you for listening.
Click to expand...
Click to collapse
^^ This, thank you.
KennyG123 said:
The only threads that need warnings are those for root and those for recovery. There has been no issue with the S4, S5 or Note 3 sections.
Click to expand...
Click to collapse
I don't post much here as I usually find my answers with a little searching, but I'm a daily lurker and have been since the days of OG droid. I strongly disagree with your statement. There has indeed been plenty of confusion in the Note 3 threads. Also a good little bit of drama and some anger over poorly marked threads. Yes, the threads should be more clearly marked "Developer Edition" by the OP, but it doesn't always happen. In the end, I think it just makes more work for you to moderate but that's your choice.
KennyG123 said:
Unfortunately this lock down of Verizon and AT&T devices has killed development since the S4. This is the other thing to think about... If someone does crack the bootloader or finds a root and SafeStrap like method, suddenly all the DE ROMs will be usable by all.
Click to expand...
Click to collapse
Well, you'd think so, but (in the case of the S5 anyway) the number of ROMs available for the retail version out number the number available for the developer edition. You'd think that it would be the other way around. Most developers aren't releasing two versions, one for retail (SafeStrap) and one for DEs. As of last week anyway. Either way, development for the S5, either model, is pretty slim. And, the unified ROMs (AOSP) just don't seem to be ready for prime time. There is always something that just doesn't work right or not at all.
But I have faith. I hope the Note 4 will be blessed with a multitude of ROMs to accommodate a wide range of user wishes and desires...besides it's getting close to Christmas, gotta have faith, right?
jpcalhoun said:
Well, you'd think so, but (in the case of the S5 anyway) the number of ROMs available for the retail version out number the number available for the developer edition. You'd think that it would be the other way around. Most developers aren't releasing two versions, one for retail (SafeStrap) and one for DEs. As of last week anyway. Either way, development for the S5, either model, is pretty slim. And, the unified ROMs (AOSP) just don't seem to be ready for prime time. There is always something that just doesn't work right or not at all.
But I have faith. I hope the Note 4 will be blessed with a multitude of ROMs to accommodate a wide range of user wishes and desires...besides it's getting close to Christmas, gotta have faith, right?
Click to expand...
Click to collapse
That is because so few of the DE's were sold.
Adding more forums only adds to the risk of someone flashing the wrong thing. Better they see threads like this than assuming all Verizon variants are the same. There are many other variants that have no forums, US Cellular, Metro, Boost, some Chinese knock off... It is ludicrous to make a separate section for every one. Developers have usually been good about properly marking their work.
If people don't read the documentation then the only person at fault is themselves.
deathshead said:
Also people running out and buying the DE not knowing that the device also only has a 30 day warranty..
Click to expand...
Click to collapse
To those who have bought many the 30 day is well known . Don't have any issue with this. It's also voided the second that the phone is unlocked and rooted. i am buying the phone to void a warranty.
Chuck_IV said:
Personally I'd rather see a separate forum for all the Developer specific stuff. Drop it all there so there is no confusion... but that's just me.
Click to expand...
Click to collapse
I 100% agree with this.
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
I haven't been active (posting or lurking) since the S4 days, so I'm a little out of touch. I've been scouring the forum (this one and others) all night, and given the KNOX changes, locked boot-loader, non-removable battery, etc., made to the Galaxy S Series, I'm a little uncertain about the current state of affairs.
Long story short, I dropped my phone today and shattered the display. Phone still works and all, but it's hard to see anything. I, like everyone pretty much I guess, am eligible for a free upgrade. (I already paid for my current [broken] phone, so no issues there. I already called and asked.) April, or longer given the confirmed delay, is a long way off to wait for the S8 (though I probably will), but if I were to get my S7 tonight, here's my question:
If I'm not interested in new ROMs or anything and just want to root my phone so I can have full control (mainly just to delete bloat, but also to edit some various system cfg files... it's okay--I'm a professional ), is that still doable on the the S7 without much hassle?
~Zach~ said:
I haven't been active (posting or lurking) since the S4 days, so I'm a little out of touch. I've been scouring the forum (this one and others) all night, and given the KNOX changes, locked boot-loader, non-removable battery, etc., made to the Galaxy S Series, I'm a little uncertain about the current state of affairs.
Long story short, I dropped my phone today and shattered the display. Phone still works and all, but it's hard to see anything. I, like everyone pretty much I guess, am eligible for a free upgrade. (I already paid for my current [broken] phone, so no issues there. I already called and asked.) April, or longer given the confirmed delay, is a long way off to wait for the S8 (though I probably will), but if I were to get my S7 tonight, here's my question:
If I'm not interested in new ROMs or anything and just want to root my phone so I can have full control (mainly just to delete bloat, but also to edit some various system cfg files... it's okay--I'm a professional ), is that still doable on the the S7 without much hassle?
Click to expand...
Click to collapse
You can root, but it's more difficult on Bootloader 4 to root and keeo activation. It's all luck of the draw on whether the phone you get will come with a firmware on a earlier firmware. If you're on the APH firmware or below I believe, you can downgrade to APE1 and root pretty easily while keeping activation. I'd personally recommend it only if you want to root and are fairly experienced. Glad the first device I rooted was an S3 and not this.
YMNDLZ said:
You can root, but it's more difficult on Bootloader 4 to root and keeo activation. It's all luck of the draw on whether the phone you get will come with a firmware on a earlier firmware. If you're on the APH firmware or below I believe, you can downgrade to APE1 and root pretty easily while keeping activation. I'd personally recommend it only if you want to root and are fairly experienced. Glad the first device I rooted was an S3 and not this.
Click to expand...
Click to collapse
Yeah, I got my start on the S3, too. S4 was easy, too, thanks to all the hard work to some very proficient devs here, at least until that update Samsung pushed to tighten KNOX and whatnot.
Anyway, about the S7, I've seen a couple of guides here and there about rooting the S7, but more prevalent are the "OMG... I've lost all my services!" or "OMG! My phone deactivated!" follow-up replies, and then those followed up by "hacks" to maybe get things working again. All in all, though, there really isn't much internet chatter (messages, videos, guides, etc.) about rooting the S7 compared to the S3 and S4, hence why I get the feeling it's not really recommended until you are extremely determined.
~Zach~ said:
Yeah, I got my start on the S3, too. S4 was easy, too, thanks to all the hard work to some very proficient devs here, at least until that update Samsung pushed to tighten KNOX and whatnot.
Anyway, about the S7, I've seen a couple of guides here and there about rooting the S7, but more prevalent are the "OMG... I've lost all my services!" or "OMG! My phone deactivated!" follow-up replies, and then those followed up by "hacks" to maybe get things working again. All in all, though, there really isn't much internet chatter (messages, videos, guides, etc.) about rooting the S7 compared to the S3 and S4, hence why I get the feeling it's not really recommended until you are extremely determined.
Click to expand...
Click to collapse
If you're fairly experienced with android rooting, go ahead and try it. I'd recommend backing up your pit file before you try anything though. Rooting and getting activation back on bootloader 3 is quite easy, but with the new FW's it's slightly more difficult. An XDA user has rooted the latest U firmware from sprint and has everything working from voice to data to all else. I'd recommend PMing @vegoja for help with bootloader 4 rooting, but anything with bootloader 3 rooting I can help you with. Good Luck!
Hello fellow s7 users..... i was wondering if i could possible get some help on this hellish root process that ive been waiting to gain. I have successfully rooted my device via pc, odin and that other stuff. However, my root access failed to keep activation as quick as it was to gain root. I was in the middle of disabling all the unwanted bloat ware and out of no where, my phone kicked itself into a reboot and fell victim to a bootloop. I managed my way out of it and was able to boot all the way through only to find out that a majority of the stock apps would "suddenly stop" itself. Took me a min to sort out that dilemma but after doing so, i realized that i no longer had root access but my device was still rooted...?? Ive done the uninstall, reinstall and clear data steps but still haven't been able to successfully grant superuser permissions. So maybe, i missed a step or misunderstood a thread but i cant seem to work my way around this predicament....... could someone please help me??
I apologize if I'm not on the right thread to ask for help.... worth trying at least.
Thank you
Its been a long time since i posted but wanted to share this in off chance it will be helpful. Anyways i have been doing some research to try and help me decide whether i am going to get the s7 edge 935t or the international 935f, 935fd i believe are the model #'s. While reading about the locked bootloader and rooting difficulties on the 935t and other u.s. models i thought about how i was able to root and install a custom rom on my Verizon galaxy s4 with a locked bootloader and remembered using something called safestrap. i believe it just made like a separate partition but here is the link incase a similar method can be used on the tmobile version of the s7. https://forum.xda-developers.com/showthread.php?t=2441441
I used the same exploit on my Verizon S4 and S5, even wrote my first ROM for the S4, thanks to safe strap. Unfortunatly the developer of safestrap gave up a long time ago...
Our only option is flash fire. The phone is a couple years old now, the S8 and Note are most of our remaning developers priority. And without a bunch of heads being bashed against the boot loader we will never find the cracks to exploit it.
We have a PR issue with devs. They work their butts off to give us a custom created operating system with a bunch of bells and whistles for free and we brow beat and demand more from them until we push them into giving up and moving on. Just look at the ROM threads for the TMobile S7 here on XDA, @jrkruse has been helping folks like me for years here on XDA, creating ROMs for phones he doesn't even own and helping out extremley amature devs like myself when we get stumped. How do we repay him? We flash without reading, we ignore and complain, we demand fixes and updates... For a free product from a guy who creates in his valuable and minimal free time...
I know I went off script, my bad I am just disappointed with the lack of development and developers lately.
Sent from my SM-G935U using XDA Premium HD app
yeah I noticed theres seems to be a lot less going on these days compared to when I got my first android phone, the Samsung droid charge and after rooting it I was hooked. then came the s3,s4,s5 which I had till was stolen a few months ago and now deciding on what to get next. leaning towards the g955fd which I would like more if it had the physical home button(fingerprint scanner config is ridiculous) and the i.r. blaster although I think I read somewhere that it is f.m. radio capable at least on the Chinese variant. It would be cool if Samsung released a version that was a little tougher like the one that is made by att but it seems as people have become content with what the manufacturers give you these days. Seems like a waste to spend so much money on a device with so few roms and other development options. I miss getting on here and checking out the progress all the developers had made then downloading and flashing new goodies for hours on end but it looks as maybe those kinda things are history. sad