Hi guys!
I'm writing this thread to anyone who is considering rooting his own S6. Well I wasn't sure for 5 month because I was afraid of losing my warranty. Like 3 days ago I decided to end with bloatware. This was one of the best thing I did in my life with my phone. Flashed XtreStoLite and custom kernel (arter97) and this device is now crazy fast... Damn I didn't expect these results. Also my battery is now much improved than it was before.
I know it's XDA forum, but maybe there are people like me, who are still waiting to root their phones. This thread will help them to take their decision.
Also you guys with rooted phones - write your feelings when you did it.
I've always rooted my phones and used custom ROMs, but I've become more and more reliant on my mobile banking apps recently. As they don't work on rooted phones, my S6 is staying unrooted.
Is Samsung Pay the only function you lose when rooting and/or installing a custom TW ROM?
HKSpeed said:
Is Samsung Pay the only function you lose when rooting and/or installing a custom TW ROM?
Click to expand...
Click to collapse
Hmmm... In my country Samsung pay is not available yet. So I don't care about this one. Also I don't know about any other disadvantages of root or custom ROM.
HKSpeed said:
Is Samsung Pay the only function you lose when rooting and/or installing a custom TW ROM?
Click to expand...
Click to collapse
You also lose Knox, warranty (depending upon your country) and OTAs.
I've always rooted my phones starting back when the galaxy s fascinate came out, been on this forum a long time and rooted lots of tabs and phones thru here. You can always flash back to stock if you don't like root.
I actually rooted my Nexus 5 but don't feel the need to root my S6. The only thing i used it was to change the dpi on nexus but with the screen grid option i don't even need to on S6. Phone is working perfectly fine and unrooted gives me peace of mind of safety and OTA updates.
Since Adblock Fast is available for M6.0.1, I don't need to root my SGS6. Web advertisements and banners was main reason for rooting my phone, because i was using Adaway, which is "root only" app. Adblock Fast is working like Adaway (except adcvertisements in free apps, of course - i don´t mind of that, I'm willing to pay for good app) and without root. Yes, with root I can have more functionality (exposed framework, tweaking stock apps, ...), but I can live without that. And I'm happy that my Knox is not tripped and have automatic OTAs.
I'm incredibly glad I didn't jump straight into rooting mine... The camera started to occasionally play up after a month, sometimes making a noise when focusing. This progressed over the months to becoming more frequent, and sometimes I'd have to literally shake the phone to get it to focus.
Two months in I handed it in but they couldn't find anything wrong with it. Five months in it was so bad that they couldn't deny it and repaired it there and then when I read the newspaper with a coffee (kudos to Samsung: only some stores offer that service).
So yeah, I wouldn't root my phone again within six months for that reason.
I'll still root it though - I'm just waiting for official TWRP compatibility at the moment.
As a side note, I asked the guy who handed my phone back if they check KNOX routinely. He told me yes for software issues, and occasionally for hardware issues (especially for screen issues). He didn't bother checking mine apparently.
2ZE said:
I'm incredibly glad I didn't jump straight into rooting mine... The camera started to occasionally play up after a month, sometimes making a noise when focusing. This progressed over the months to becoming more frequent, and sometimes I'd have to literally shake the phone to get it to focus.
Two months in I handed it in but they couldn't find anything wrong with it. Five months in it was so bad that they couldn't deny it and repaired it there and then when I read the newspaper with a coffee (kudos to Samsung: only some stores offer that service).
So yeah, I wouldn't root my phone again within six months for that reason.
I'll still root it though - I'm just waiting for official TWRP compatibility at the moment.
As a side note, I asked the guy who handed my phone back if they check KNOX routinely. He told me yes for software issues, and occasionally for hardware issues (especially for screen issues). He didn't bother checking mine apparently.
Click to expand...
Click to collapse
Just so you know there is official twrp support
552eden said:
Just so you know there is official twrp support
Click to expand...
Click to collapse
Not for MM bootloader. TWRP on MM at the moment can only be installed via Chainfire's or Arter's modified version
Big_Rich_1983 said:
I've always rooted my phones and used custom ROMs, but I've become more and more reliant on my mobile banking apps recently. As they don't work on rooted phones, my S6 is staying unrooted.
Click to expand...
Click to collapse
Rootcloak fixes this.
I rooted mine mainly for adaway and xposed, but I have to say that not getting OTA is annoying - however Samsung is too slow with the updates that I don't care anymore (still no marshmallow in my country).
I had problems with mine I was on 5.1.1 rooted updated to marshmallow my phone came up with emergency calls only back on 5.1.1 after repair funny thing is the repair shop rooted my phone to make sim work again weird
Hi guys (and gals)
I've always rooted my phones because I wanted to have more powerful, flexible device. I did this with my old HTC Wildfire, HTC Desire HD and Nexus 4 but with S6 I don't feel I need this anymore. The device is just as good as-it-is – without root, Xposed, mods and so on. And 6.0.1 update gave it new shine and powers. Of course it's my personal opinion only but I must repeat – Galaxy S6 is the first Android phone I'm pleased to use without any modifications (maybe except for Nova Laucher ).
Have a great day!
I am happier with my marshmallow now that it's 6.0.1 rooted with xposed mods to tweak with it. I'll always root if I can just because I can't stand not messing with it, lol.
Hoccco said:
Rootcloak fixes this.
I rooted mine mainly for adaway and xposed, but I have to say that not getting OTA is annoying - however Samsung is too slow with the updates that I don't care anymore (still no marshmallow in my country).
Click to expand...
Click to collapse
I got Marshmallow 6.0.1 about 2-3 weeks ago, and I've had two minor updates (around 13-15Mb each) since then. Can't fault Samsung in my country.
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
If Verizon users are still intrested, just take a look here:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
This guy J4NN is a genius!
Maybe for a bounty he will do it for your device. ?
Inerent said:
If Verizon users are still intrested, just take a look here:
https://forum.xda-developers.com/xp...devonly-exploits-temp-root-to-backup-t3795510
This guy J4NN is a genius!
Maybe for a bounty he will do it for your device.
Click to expand...
Click to collapse
I got a PM about Temp root for Verizon Google Pixel 2 XL, I guess it was due to this post of you, @Inerent.
It seems that instead of exchanging PMs, it would be better to post it here, to clarify the situation.
Hopefully this is ok with @trabadura, who contacted me.
trabadura said:
j4nn said:
trabadura said:
Hi j4nn, i see your post in xda for temp root Sony XZ1c with Snapdragon 835 and I figured you could help us for temp root Verizon Google Pixel 2 Xl for Unlock Bootloader?
Click to expand...
Click to collapse
Hi, I am not sure about that - I do not have that phone and cannot get/borrow it for testing either.
Do you know if it is possible to downgrade it's firmware?
Can you point me to earliest fw for download that it can be downgraded to?
What exactly the problem is - bootloader is not possible to unlock because Verizon (is it a mobile network operator?) disabled bootloader unlock possibility while on general not Verizon variant google allows it?
Is it also sim locked to Verizon operator only?
And how do you know that getting temp root would help you?
Click to expand...
Click to collapse
Hi, аs far as I know, it can not downgrade firmware with locked bootloader. With unlocked bootloader no problem.
The problem is in mobile operator. They lock option "OEM Unlock" (stay grayed out) in developer option. In general not Verizon variant no problem option is active and no problem to unlock bootloader. No sim locked only bootloader. Тhere is a lot of writing about the topic I can give a few links in the forum.
Links:
https://forum.xda-developers.com/pixel-2-xl/how-to/temp-root-bounty-verizon-users-t3710652
Click to expand...
Click to collapse
I am sorry, but in my opinion, you are out of luck.
At least if google/verizon delivers FOTA updates and most users accept them instead of staying at the version they bought the phone with.
You could get temp root only with some completely new not fixed kernel vulnerability which would not get patched for longer period of time and that's not happening very often.
If someone starts working on an exploit while most users upgrade in short time closing the bug being worked on, it does not make sense to put an effort into it.
To consider porting my work for other targets, you need to make sure you can run kernel which is still vulnerable to CVE-2017-7533 (race between inotify and rename) and few other CVEs that are needed to overcome android oreo mitigations. Google has patched the mentioned CVE which is the primary one with 2017-12-05 security patch level.
How many users do you think stay on older patch level than that? And would continue staying on it?
I am afraid nobody would help you no matter how much you promise with the bounty.
And so you know, working on it, only because of the bounty mostly is not worth it - at least in my case if I compare the lost time and what is promised in xperia xz1 bounty thread I would be better working any low paid job. That means if I did not want to get it done for myself, I would not work on it!
And even though Google Pixel 2 XL bounty is lot higher, the difficulty (due to no downgrade possibility) is extremely high and gets higher with each update.
I am afraid you need to get used to the fact that there never be a root for it, I am sorry.
You all should have probably bought the open (not Verizon locked) variant instead or be satisfied with the product as bought (I guess it must have been a great deal, right?).
Or at least educate all users here not to allow any upgrade at all since beginning (if that's even possible to disable the updates).
j4nn said:
I got a PM about Temp root for Verizon Google Pixel 2 XL, I guess it was due to this post of you, @Inerent.
It seems that instead of exchanging PMs, it would be better to post it here, to clarify the situation.
Hopefully this is ok with @trabadura, who contacted me.
I am sorry, but in my opinion, you are out of luck.
At least if google/verizon delivers FOTA updates and most users accept them instead of staying at the version they bought the phone with.
You could get temp root only with some completely new not fixed kernel vulnerability which would not get patched for longer period of time and that's not happening very often.
If someone starts working on an exploit while most users upgrade in short time closing the bug being worked on, it does not make sense to put an effort into it.
To consider porting my work for other targets, you need to make sure you can run kernel which is still vulnerable to CVE-2017-7533 (race between inotify and rename) and few other CVEs that are needed to overcome android oreo mitigations. Google has patched the mentioned CVE which is the primary one with 2017-12-05 security patch level.
How many users do you think stay on older patch level than that? And would continue staying on it?
I am afraid nobody would help you no matter how much you promise with the bounty.
And so you know, working on it, only because of the bounty mostly is not worth it - at least in my case if I compare the lost time and what is promised in xperia xz1 bounty thread I would be better working any low paid job. That means if I did not want to get it done for myself, I would not work on it!
And even though Google Pixel 2 XL bounty is lot higher, the difficulty (due to no downgrade possibility) is extremely high and gets higher with each update.
I am afraid you need to get used to the fact that there never be a root for it, I am sorry.
You all should have probably bought the open (not Verizon locked) variant instead or be satisfied with the product as bought (I guess it must have been a great deal, right?).
Or at least educate all users here not to allow any upgrade at all since beginning (if that's even possible to disable the updates).
Click to expand...
Click to collapse
You are completely right. And that is the difference between Android and iPhone communities. Every Android user prefer to stay aside of this problem, naively thinking that they would not be affected. In Oreo Google has already put all the Root CAs into the System storage. So Nobody knows what kind of data the phone uploads every day to 3rd party servers. Verizon is just an example there are many companies who do the same. iPhone community is great because everybody know that some day under certain circumstances they can lost their JB. I hope one day some mid-range iOS developer will buy Android phone and start developing a great root tools. Sure it will be quite easy because all the source code is available.
I appreciate your work. Thank you and good luck.
First they came for the socialists, and I did not speak out—
Because I was not a socialist.
Then they came for the trade unionists, and I did not speak out—
Because I was not a trade unionist.
Then they came for the Jews, and I did not speak out—
Because I was not a Jew.
Then they came for me—and there was no one left to speak for me.