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
Related
I know most people are gonna tell me I should root my phone, but just hear me out really quickly...
I just got my Samsung Vibrant and I truly love the phone. It's a huge upgrade from my G1 in pretty much every way I can think of. I had my G1 rooted since like the second week I had it. I started off with JesusFreke's ROMs and then made my way to Cyanogen's ROMs with a few others that I tried here and there. I tried a bunch of different themes and I used quite a few root apps. I know my way around the rooted Android scene (or at least the rooted G1 scene) pretty well, but I'm not entirely sure if I want to root my Vibrant and here's why:
I'm afraid of voiding my warranty.
There's not really anything that I want to do with the phone that it can't already do (for example, it has plenty of space for apps without the need for A2SD).
I don't want to risk losing things like my text messages over and over again from switching to different ROMs (this happened to me quite a bit with my G1).
My G1's battery and overall performance were much much worse than my friends' G1s which were not rooted. I don't want this happening with my Vibrant.
Some people will think that these reasons are either unimportant or nonexistent, but I disagree. Again, before people start saying "these are the risks of rooting, deal with it or leave," I want to stress that I'm not a newbie at this.
Anyway, the main reason that I DO want to root the phone, regardless of the fact that I told myself I wouldn't, is because of all this junkware that T-Mobile preinstalled the phone. I didn't know the phone came with this crap (like GoGo, TeleNav GPS, Slacker, etc.). We all know that you can't remove this stuff without rooting...I've counted 11 apps that I want to remove from the phone because they're effectively advertisements and I don't want them. So before I make a decision, I'd like to ask some questions...
Would you root the phone if you were ME?
Is it possible to root the Vibrant, remove the apps, and then unroot it, thus leaving the apps gone?
If not ^^, then is it possible to root the Vibrant and keep the stock ROM? I really don't want any custom ROMs...I just want to remove the junkware.
I'm sorry if similar questions have been asked before, but I feel like my specific needs and concerns probably aren't shared by most of the XDA community so I created my own post...
Thanks,
Gerard
actually I think what most are going to say is search the forum... There are several threads on the topic.
You don't have to add any roms if you're rooted. Yes you can remove the bloatware with root. Yes its easy to take your phone out of root, but with the bloatware missing its not hard to see that you have had root at one point.
I actually did root my phone just to remove the junkware....and then used titanium backup to remove what I didn't want....it took me 3 mins to root compared to the 15 mins it took for my nexus....i say its worth it....you can't even tell its rooted so I'm pretty sure the warehouse will never catch it if a exchange is ever needed.....you ll personally make up ur mind as soon as u see the cyanogen 2.2 rom come out hopefully that will be soon....I SAY GO FOR IT
Sent from my Samsung™ Vibrant using XDA App
I'm not bothering to root while I can still return the phone (1st 30 days) and not all the HW issues are know. Once a decent custom ROM is available I'll start looking into rooting, customer recovery, etc. The only thing I'm missing a bit from not being rooted is my Wifi tethering...
Thanks for the replies, guys (and/or girl(s) it looks like lol). I'm glad I wasn't destroyed by people telling me to search the forums...
I'll probably end up doing root sooner or later with very few modifications (if any). I'll wait it out a bit, though. My questions have been answered.
Thanks again!
Gerard
I've rooted my last 3 phones, and for the longest time, considered it an essential step in the true Android experience.
But let's be honest, rooting is a bit of a PITA. You risk destroying your warranty, which worries me with a phone that I got on launch day. You have issues with OTA updates. If you load a custom ROM, you're blowing away all your settings each time you load an update. There's more, but I won't keep going.
Of course, there are a LOT of benefits, too. Most of them, however, are ways around annoying little nits that I have, and with this phone, I find fewer of those nits, and far fewer items that are larger than nits. With the improvements in Android and with a good launcher, I can completely hide away all of the annoying Sprint and Samsung apps.
If I rooted this phone, these are the benefits that I think I could realize are: Getting rid of the volume warning (nit), changing my boot animation (nit), Titanium backup (which I don't really need if I'm not constantly loading a new ROM), better ad blocking (nit), the ability to remove unwanted apps (bit of a nit, but it would be beneficial to reclaim the ram and storage space), and probably the biggest - wifi hotspot (which I rarely use, but I will miss if I don't have it).
I'm curious if anyone else thinks this same way about this phone. Are there other serial rooters who are not rooting the S6?
well, first thing I did with my S6 was to load custom recovery and custom ROM
Still on the same boat, don't want to trip knox by installing a custom recovery or custom kernel and not knowing what ping-pong root really does is a little worrisome.
When considering whether to root or not your S6, remember that there is a debloat method which doesn't require root: http://forum.xda-developers.com/galaxy-s6/general/safe-to-debloat-s6-threads-t3090383.
I agree with OP: as time passes by and Android evolves there are less and less "serious" reasons to root a phone.
Pingpong is pretty safe(warranty wise) and it's easy to reflash your stock rom. I usually never root on first day but now I saw no reason not to.
Having had a rooted phone since the days of cupcake I wasn't sure what I was getting into when I got my Xperia Z2 before it was rootable with a locked bootloader and in those few months I discovered I could live without titanium backup if I wasn't flashing roms left right and centre but I hadn't realised how pervasive ads had become in the mobile world and it was something that really bugged me, as the non-root blocking methods didn't give me much joy, so when root was finally achieved I knew I couldn't live without ad-blocking.
Fast-forward a year and I was holding off the S6 for the precise reason of not being able to root without tripping knox (which given the track record of my S2, S3 & S4 all needing to be repaired under warranty I cannot afford to do), but I ended up getting it thanks to breaking my Z2, with the hope of something like pingpong coming soon enough. This time again I found it painful dealing with the ads again but to add to that there's the frankly rubbish battery in this phone compared with my old Z2, and I was having little joy zapping all the wakelocks until I got root and greenify.
So TLDR, can't live without proper ad-blocking and greenify is essential for the S6 if you actually want to have a reasonable amount of functionality without carrying around a charger.
As for me, I like rooting so I can remove bloat, freezing an app is not the same as removing it and I can't stand ads. Do what you like, I have never had issues with warranties even with knox tripped. I have had the S, S3, S4, and now the S6 and I have never had to use the warranty, which expires after the first year anyway.
ipaq_101 said:
As for me, I like rooting so I can remove bloat, freezing an app is not the same as removing it and I can't stand ads. Do what you like, I have never had issues with warranties even with knox tripped. I have had the S, S3, S4, and now the S6 and I have never had to use the warranty, which expires after the first year anyway.
Click to expand...
Click to collapse
well, Samsung offers 2 years warranty, here in Europe anyway.
I have rooted pretty much every single android phone I have owned and with the superb debloater app I have zero need for root now and unless Samsung do something which is very invasive I cannot see any reason to root in the future,
That and the fact I have heard of stories of ping pong root tripping knox on some devices is worrying.
I rooted every phone which I had on the first day and never had problems with warranty but the phones hasn't knox. My note 3 was rooted too but there wasn't any reason sending to repair.
Now with the s6 I don't need the root.
The Rom is debloated for. There was only Microsoft and Vodafone apps. I use them both so no reason to debloat.
Thread cleaned, please keep it nice and friendly
Whiskey
Forum Moderator
I haven't and wont root this phone. I use adblock browser which gives me a perfect ad free browsing experience. I use zero apps which bombard me with annoying ads I can't ignore, I have plenty of space on my phone, and custom Rom's won't make it faster or more stable or improve battery life so personally there's no point.
I go back and forth with the idea of rooting. Right now, there's no method for my build - so, I want to root. Previously, when there was a method for build - I didn't root. I'm kinda of the similar thought as the OP...is there really a need to root anymore? The majority of the reasons/features we rooted our phones for in the first place are now part of Android. If I do root, it will be to get the maximum benefit out of using Greenify and TB.
I've rooted all my previous android devices and this is the first phone that I don't feel like I need rooting. I did go through the process with PingPong-root so that I could clean up some apps but after I couldn't get OTA's I went and restored it to factory settings. With Nova Launcher and the ability to inactivate most of the apps I don't use I don't see the need of rooting it just yet..
I decided that I couldn't live without rooting. Those "Nits" drive crazy and I like the freedom. But I have pretty much decided to not put any custom Roms on. No matter what I end up with bugs that just aren't on the Stock Rom.
I unrooted a few days ago to fix Google now (I broke it somehow) and am having a hard time redoing it. Other then modding the themes..I can't find another reason. Most of the time I break stuff anyways lol so might be better if I dont!
Sheldor1967 said:
I decided that I couldn't live without rooting. Those "Nits" drive crazy and I like the freedom. But I have pretty much decided to not put any custom Roms on. No matter what I end up with bugs that just aren't on the Stock Rom.
Click to expand...
Click to collapse
Yeah that's the only way I do it. I just root the stock rom and get rid of the ads. Backup my apps with titanium backup. All the usual things that I can't do with a non rooted phone.
With regards,
Beston94
My biggest reason I'd consider rooting is AirAudio -> Airport Express devices.
I need root as I use the automation app tasker an awful lot. I haven't purchased an s6 yet but it is something I am debating. It is between the s6 and N6 but either way I will be rooting whichever I choose
---------- Post added at 04:15 PM ---------- Previous post was at 04:14 PM ----------
Sheldor1967 said:
I decided that I couldn't live without rooting. Those "Nits" drive crazy and I like the freedom. But I have pretty much decided to not put any custom Roms on. No matter what I end up with bugs that just aren't on the Stock Rom.
Click to expand...
Click to collapse
Which method did you opt for with regards to rooting?
Flashed TWRP and the rooted from there. Knox is tripped - O-Well. I did it before the other methods were available...
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
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.