Database Users

[Q] Bootloader locked after stock update?

Hey,
I got my Galaxy S4 AT&T SGH-I337 as I337UCUAMDB, and ever since then was running cyanogenmod 11.
Recently after a stupid mistake (updating to a nightly, then to M10) I had to return to stock ROM, and on a CM dev's lead installed a NB1 ROM.
Since then, I wasn't able to install TWRP (installing it would make the phone boot only into download mode), and installing CM would produce constant "com.android.phone/acore/media" errors.
Right now I'm running Google Edition for SafeStrap (v1.1 - 4.4.4), which, TBH, isn't nearly as good as CM11 and still very buggy...
I read as much as I could about the whole AT&T GS4 bootloader situation, but still haven't understood it fully:
Could my bootloader have been locked by the update?
If not, why can't I install a custom recovery and CM again?
If so, is there anyway I can downgrade back to MDB (maybe from here?) Or to anything that can allow me to install CM again?
Thanks in advance,
Yuval.
Edit: If I can still use safestrap to install any custom ROM, why can't I install CM? (I did a clean install [full wipe] a couple of times, w/ and w/o gapps, to no avail) Or did I not understand well the safestrap custom ROM options?

Your bootloader was always locked, loki just exploited it.
You have to use SafeStrap as MF3 (I think) and above closed the loki patch. That means no custom kernels and no custom recovery.
No, you can't downgrade back. Sorry.
I would highly recommend reading before you make any major changes to your phone in the future.

RAID Xero said:
Your bootloader was always locked, loki just exploited it.
You have to use SafeStrap as MF3 (I think) and above closed the loki patch. That means no custom kernels and no custom recovery.
No, you can't downgrade back. Sorry.
I would highly recommend reading before you make any major changes to your phone in the future.
Click to expand...
Click to collapse
Thanks for your comment! I understand the loki patch, but wasn't sure if it was automatic up until then (I haven't applied it manually).
No custom kernel or recovery is more than fine by me as long as SafeStrap serves as a practical replacement for one (custom recovery), but it still does not solve my problem:
I'm unable to install CM11 M10, even after multiple clean flashes with SafeStrap.
I realise this might not be a bootloader problem as I previously thought, but would still appreciate any intake as to how to solve this.
I read extensively about the SGH-I337 situation, but albeit technologically-oriented, didn't grasp it fully. Thanks for helping to clarify this up!

novikyuval said:
Thanks for your comment! I understand the loki patch, but wasn't sure if it was automatic up until then (I haven't applied it manually).
No custom kernel or recovery is more than fine by me as long as SafeStrap serves as a practical replacement for one (custom recovery), but it still does not solve my problem:
I'm unable to install CM11 M10, even after multiple clean flashes with SafeStrap.
I realise this might not be a bootloader problem as I previously thought, but would still appreciate any intake as to how to solve this.
I read extensively about the SGH-I337 situation, but albeit technologically-oriented, didn't grasp it fully. Thanks for helping to clarify this up!
Click to expand...
Click to collapse
Very simply, you can not run cm anymore. You're stuck with touch wiz based roms after you updated the firmware.
Sent from my Nexus 5 using XDA Free mobile app

You can run a Google Play Edition ROM, that's about as close to CM as you're going to get using SafeStrap.

jd1639 said:
Very simply, you can not run cm anymore. You're stuck with touch wiz based roms after you updated the firmware.
Click to expand...
Click to collapse
RAID Xero said:
You can run a Google Play Edition ROM, that's about as close to CM as you're going to get using SafeStrap.
Click to expand...
Click to collapse
Okay, I think I now fully understand this. Thank you RAID Xero and jd1639 for the help!
I guess I learnt my lesson to look into evil AT&T ROMs before updating to and from them
Also, too bad I never noticed any warning regarding this on Cyanogenmod's website (or maybe I just missed it)...
Thanks again, and unless there's a new magical way to bypass the locking, this thread may be marked as locked.

You're welcome, and happy flashing!

[Q] Phone refuses to boot with a rom

Hi, I've been trying to install a custom rom (at this point ANY custom rom) on my friend's phone. I have worked on several phones before, including my own sprint GS3, but this is my first time trying to work around a locked bootloader, and BOY is it a pain, haha. I'm no dev, but I would like to think that I'm pretty competent.
First a few things to note, are that the phone is currently on NI1 (Been too much of a sissy to go to NJ4 in case it screws something up, I don't even know why), it is the 16Gb version, I am using an external sd card to flash everything, and yes I am flashing loki-doki after everything.
So what I've done so far is:
- Try to install TWRP
- Find out that won't work and finally figure out I need safestrap
- Successfully install safestrap after using towelroot by ODIN-ing the NC1 kernel then going back to the NI1 kernel
- Try to flash Resurrection Remix and KToonsez kernel using a new rom-slot, and wind up soft-bricking (stuck on bootloader screen, can get to download mode)
- ODIN NB1 tar then ODIN NI1 update
- Repeat the last few steps several times because I'm too idiotic to realize that it JUST ISN'T GOING TO WORK!
- Finally find a reference to flashing the ATT kernel modules after the rom. That got me past the soft brick and safestrap screen, but I don't even see a boot animation
As of right now my sequence to successfully not soft-bricking (what an accomplishment) is to flash the rom>gapps>ATT kernel module>supersu>loki-doki>wipe dalvik/cache
Now, is it worth it having already spend a good 7 hours, just to get a custom rom? Of course not, it's not my phone and my friend isn't picky. He'd be just fine with rooted TW. However, It kills me that I don't know what's going on, so here I am lol.
TL;DR: Phone has safestrap, is rooted, but any time I flash a rom it gets past the boot loader/safestrap screen and never shows a boot animation, or anything past that. Can anyone help figure out what's going on please?
Thanks in advance.

You can only flash touch wiz based roms with safestrap and you can't flash kernels with safestrap. That's been your problem with soft bricking.
Edit, see this for roms you can flash http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app

http://forum.xda-developers.com/showthread.php?t=2616221

Thanks guys. I thought I read through the whole thread, but there is so much information, it's pretty scattered, I must have missed the thing about only TW roms working.
Now a few more questions:
1) Is it worth updating to NJ4? The phone is new and doesn't have any app data or anything that would be missed by updating. I see quite a few roms in 4.4.4, but it looks like most of them are AOSP based, which leads me to my next question...
2) Is there a way to get AOSP roms to work? I see all of these AOSP based roms, obviously for this phone, but it would be pointless to make them if they don't work.

Masterjuggler said:
Thanks guys. I thought I read through the whole thread, but there is so much information, it's pretty scattered, I must have missed the thing about only TW roms working.
Now a few more questions:
1) Is it worth updating to NJ4? The phone is new and doesn't have any app data or anything that would be missed by updating. I see quite a few roms in 4.4.4, but it looks like most of them are AOSP based, which leads me to my next question...
2) Is there a way to get AOSP roms to work? I see all of these AOSP based roms, obviously for this phone, but it would be pointless to make them if they don't work.
Click to expand...
Click to collapse
It wouldn't hurt to update to nj4. But it's not going to help you either. Only phones on mdb or mdl bootloader can flash non touch wiz based roms using loki. And you can't go back to those bootloaders
Sent from my Nexus 9 using XDA Free mobile app

Alright then. Hyperdrive looks pretty good, I'll try that along with Ktoonsez kernel. I'll report back later to let you know how it goes. Thanks again!

Masterjuggler said:
Alright then. Hyperdrive looks pretty good, I'll try that along with Ktoonsez kernel. I'll report back later to let you know how it goes. Thanks again!
Click to expand...
Click to collapse
Again, you can't flash a kernel in safestrap
Sent from my Nexus 9 using XDA Free mobile app

Oh, I get it now. That didn't quite register before. So just to confirm, after I flash the rom (which already has its own custom kernel included), I still need to flash the stock ATT kernel, correct?

Flash the rom, super su, and the att module for your base. Hyperdrive is a very good rom, good luck. Also the rom doesn't include a kernel, your original kernel stays put. That's why only tw roms work, because your new rom has to be compatible with the kernel already on your phone.

Just reporting in, I now have the phone up and running using Hyperdrive Rom. Thanks for the help!
I actually had a problem where it would not shut down correctly, but found out it was because I was installing the rom in a rom-slot in safestrap. As soon as I tried the stock rom slot, it worked flawlessly.

[Q]Want GPE, but can't get custom recovery - Help please! :(

Hey guys... Before I get into this, I would like to say that i'm very new to this whole rooting thing, so please forgive me for my lack of knowledge on various terms and such, and I'm a first time user here at xda.
What's written below might get a little bit complicated so i will try to make it as detailed as possible. Please bare with me here.
So I have a Samsung Galaxy S4 sgh-i337 (AT&T) running on android 4.4.4 (with touchwiz, you guys know the deal). I really wanted stock android lollipop, because I really like the look and feel to it. When I decided to root the phone, I went through many tutorials and I tried many different methods, and none of them worked. The phone still worked fine, but SuperSU was not installed and Root Checker said the phone was not rooted. After scouring the internet, I found one tutorial that had my S4 type and the same version. At that point I realized that my android version was hindering my rooting process. The tutorial used Odin to flash a kernel (NC1), root the phone using towelroot, install SuperSU, (Root Checker too to check if it worked), and then flashing the original kernel again (my original kernel was NJ4). After following this process, my phone was rooted, and everything worked fine.
As I said before, I wanted a GPE ROM, and so I needed a custom recovery. I decided to install CWM, since most GPE ROMs used this specific recovery. Again, I followed many different tutorials, and after each and every one, I would try to go into Recovery mode, and it would just launch the stock recovery. I found another tutorial on another website that involved flashing the recovery from an app in the google play store, so I decided to try it out. I now regret this as it led to more problems. I followed these instructions, and when launching into recovery mode from that point on, I get the yellow triangle with the error message "System software is not authorized by AT&T"
Sure, I could get around it by going into download mode from there, canceling, and it would reboot like normal, and the phone still worked, but I needed to get ride of that error message.
Once again doing my research, I figured out that if I flash a stock firmware specific to my phone, it will reset the phone (the only stock firmware available has android version 4.2.2, which is a really popular version, and is compatible with most custom recoveries and ROMs, so I decided to flash the firmware, as it would also change the version back, right?) When I flashed it using Odin like the directions said, it failed. i then figured out that it failed because my binary counter is not 0. I looked into resetting the binary counter for the AT&T S4, and I found Triangle Away. However, in order to reset your binary counter, you need an unlocked bootloader, and the AT&T S4 (sgh-i337) has a locked bootloader (I don't want to use Triangle Away if it's going to brick my phone, i'd rather unroot and keep touchwiz than brick). In the process of finding this out, I also figured out that the only custom recovery that you could use on a locked bootloader S4 sgh-i337 is SafeStrap. But i heard when using SafeStrap you are limited as far as ROMs go? Would I be able to get a GPE 5.0 Lollipop ROM with SafeStrap? Cause if not I might just unroot using SuperSU and software update my phone (will that fix the error when trying to get to Recovery mode?) Also, if I install Safestrap, will it fix the error message?
Again, sorry for my inexperience in all of this, and thanks for staying with me here. Any help and additional information on what I should do (or any GPE Lollipop ROMs I should use that are compatible with my phone and version and such), as well as any links to tutorials are greatly appreciated (also, keep in mind that all of the vocab I know when rooting is used in this post, I am not aware of most other terms - again, forgive me).

You wrote a lot but I'm not sure what state your device is in right now and what you want to do. But as you've found out, safestrap is the only custom recovery you can use. And touch wiz based roms are the only ones you can use. Afaik there are no 5.0 custom roms you can use at this time.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You wrote a lot but I'm not sure what state your device is in right now and what you want to do. But as you've found out, safestrap is the only custom recovery you can use. And touch wiz based roms are the only ones you can use. Afaik there are no 5.0 custom roms you can use at this time.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Oh, thanks for the help! The phone currently works fine, and it is rooted, but when I go into Recovery Mode it gives me the yellow triangle with the error... Will installing SafeStrap fix that? Regardless, thanks for the help, really do appreciate it!

jd1639 said:
You wrote a lot but I'm not sure what state your device is in right now and what you want to do. But as you've found out, safestrap is the only custom recovery you can use. And touch wiz based roms are the only ones you can use. Afaik there are no 5.0 custom roms you can use at this time.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Also, if i were to update the phone to the next version (i heard there is a way to bump the S4 up in android version) would that reset the error in Recovery Mode? And I also heard that with SafeStrap, you are limited to ROMs on the same android version as the one on your phone? I really like 5.0, but if it's not possible to get it as the moment (and I haven't found any 5.0 ROMs for the sgh-i337 yet - you were right) i might just unroot using SuperSU and just update my version, unrooted and all. I'd rather have my phone be nice and clean than to have root on it with a corrupted recovery mode, and not make use of the root at all (I've seen other ROMs and I prefer 5.0). I might just try to make the phone feel as close to stock as possible by using more google apps and such (keyboard, messages, etc.). Regardless, thanks for the help and additional input, really do appreciate it!

EvilLemon said:
Also, if i were to update the phone to the next version (i heard there is a way to bump the S4 up in android version) would that reset the error in Recovery Mode? And I also heard that with SafeStrap, you are limited to ROMs on the same android version as the one on your phone? I really like 5.0, but if it's not possible to get it as the moment (and I haven't found any 5.0 ROMs for the sgh-i337 yet - you were right) i might just unroot using SuperSU and just update my version, unrooted and all. I'd rather have my phone be nice and clean than to have root on it with a corrupted recovery mode, and not make use of the root at all (I've seen other ROMs and I prefer 5.0). I might just try to make the phone feel as close to stock as possible by using more google apps and such (keyboard, messages, etc.). Regardless, thanks for the help and additional input, really do appreciate it!
Click to expand...
Click to collapse
I would recommend you flash the nb1 tar file in Odin. That'll bring your device to like new. Then you can let it ota nj4. There are root methods for nc1 and nj4. See this
http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I would recommend you flash the nb1 tar file in Odin. That'll bring your device to like new. Then you can let it ota nj4. There are root methods for nc1 and nj4. See this
http://forum.xda-developers.com/showthread.php?p=56453100
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks so much! I followed the instructions and now my phone is back to normal, Recovery mode and all! Really do appreciate it, thanks!

EvilLemon said:
Thanks so much! I followed the instructions and now my phone is back to normal, Recovery mode and all! Really do appreciate it, thanks!
Click to expand...
Click to collapse
No problem. I'm glad you got it working again
Sent from my Nexus 9 using XDA Free mobile app

Since returning to Stock, issues with soft touch keys, particularly the back key

I've been trying some AOSP Roms and Note 5 Roms to see what kind of features I like. I've gone back to Stock, as several Apps I like don't work in Custom and I'm due for an upgrade soon. I have SM-N900W8 (Canada\Telus).
My Back Key doesn't work and my menu button is doing SFinder stuff instead in Lollipop. Here is the messed up part. If I restore back to KitKat, no issues, but even if I upgrade to Lollipop from Kit Kat, issue comes back. I've tried OTA, ODIN Flash, and Samsung Switch\Kies, nothing. If I go back to custom ROM (Most were Darklord Note 5 base, all really good work). The soft keys work.
Be aware I'm still learning the ropes here. I even used Odin to wipe my EFT and NAND my data partition, still nothing. I'm out of ideas. Can anyone point me the right way?

R2pclaw said:
I've been trying some AOSP Roms and Note 5 Roms to see what kind of features I like. I've gone back to Stock, as several Apps I like don't work in Custom and I'm due for an upgrade soon. I have SM-N900W8 (Canada\Telus).
My Back Key doesn't work and my menu button is doing SFinder stuff instead in Lollipop. Here is the messed up part. If I restore back to KitKat, no issues, but even if I upgrade to Lollipop from Kit Kat, issue comes back. I've tried OTA, ODIN Flash, and Samsung Switch\Kies, nothing. If I go back to custom ROM (Most were Darklord Note 5 base, all really good work). The soft keys work.
Be aware I'm still learning the ropes here. I even used Odin to wipe my EFT and NAND my data partition, still nothing. I'm out of ideas. Can anyone point me the right way?
Click to expand...
Click to collapse
Hey im in the same boat as you, and was doing the same things as you, have you found a fix?

lilr said:
Hey im in the same boat as you, and was doing the same things as you, have you found a fix?
Click to expand...
Click to collapse
Not Entirely, but I found a Work Around. If I get back to Lollipop, reroot (I use TWRP and SuperSU), and then install a Custom Kernel (I've tested LeanKernel and Arter97), then it works again. I'm going to now try to reflash back to Stock Kernel later this week, and test the results.
Update: Reflashed Stock Kernel provided here: http://forum.xda-developers.com/galaxy-note-3/general/direct-download-bootloaders-modems-t3258803 (Thanks to @jcadduono , very convenient) and same issue, back to Arter97 or Lean Kernel for now. Hoping someone has a fix soon.

I just made a post. Did not see this one. I'm having the same issue
Sent from my SM-N900W8 using XDA Free mobile app

Soft brick maybe?
R2pclaw said:
I've been trying some AOSP Roms and Note 5 Roms to see what kind of features I like. I've gone back to Stock, as several Apps I like don't work in Custom and I'm due for an upgrade soon. I have SM-N900W8 (Canada\Telus).
My Back Key doesn't work and my menu button is doing SFinder stuff instead in Lollipop. Here is the messed up part. If I restore back to KitKat, no issues, but even if I upgrade to Lollipop from Kit Kat, issue comes back. I've tried OTA, ODIN Flash, and Samsung Switch\Kies, nothing. If I go back to custom ROM (Most were Darklord Note 5 base, all really good work). The soft keys work.
Be aware I'm still learning the ropes here. I even used Odin to wipe my EFT and NAND my data partition, still nothing. I'm out of ideas. Can anyone point me the right way?
Click to expand...
Click to collapse
I think this might have to do with soft bricking the device, because I updated my rooted n900w8 from 4.4.3 (If im remembering correctly) to 5.0 while still rooted and ended up softbricking it. I think. But I also had to mess around with the BL, AP, and CSC to get it working again. could it be because of that ? has anyone else dealt with this as well?

I've posted my solutions here

rocked_out said:
I've posted my solutions here
Click to expand...
Click to collapse
Thank you so much, rocked_out! that worked for me!

"New" comer here, I need some help please

Hey guys, I have been out of the android world for a couple of years, I would appreciate some guidance.
I I'm currently living in US
T-mobil
Model number: SM-G935T
Android version: 6.0.1
Updated right now
So my question is, since I don't have any backup or anything, can someone provide me with the steps to get me started? Like what post to root it on this specific carrier and how everything? please
Thanks

Arturofm2 said:
Hey guys, I have been out of the android world for a couple of years, I would appreciate some guidance.
I I'm currently living in US
T-mobil
Model number: SM-G935T
Android version: 6.0.1
Updated right now
So my question is, since I don't have any backup or anything, can someone provide me with the steps to get me started? Like what post to root it on this specific carrier and how everything? please
Thanks
Click to expand...
Click to collapse
Of course we can get your started but see
But first you must answer us these question three.
Why do you want root?
Do you have a computer? (This is a must for root.)
Are you ready to be disappointed?

https://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
follow this (use odin to flash rooted kernel) ......you should search before posting things like this.....google is your friend bro.
GOOD LUCK - BTW use flash fire app in play store to make backups and flash roms

Okay okay.
A quick glance at T-Mobile Samsung Galaxy S7 Edge Guides, News, & Discussion would have led you to the "How to root the S7 EDGE" thread.
I'd take a look in there if I were you.

Binary100100 said:
Of course we can get your started but see
But first you must answer us these question three.
Why do you want root?
Do you have a computer? (This is a must for root.)
Are you ready to be disappointed?
Click to expand...
Click to collapse
Well while I was waiting I just rooted it. So what do you think that would be the next step towards installing a rom? To answer your survey questions :laugh: :
1- Because a phone without being rooted is like a bird without wins.
2- I do
3- Oh well... tell me more

Arturofm2 said:
Well while I was waiting I just rooted it. So what do you think that would be the next step towards installing a rom? To answer your survey questions :laugh: :
1- Because a phone without being rooted is like a bird without wins.
2- I do
3- Oh well... tell me more
EDIT: I just checked and the root didn't go through... even though ODIN said it was successful
Click to expand...
Click to collapse
Well then.
Rooting the phone (as I'm sure you had already found out) was fairly easy.
BUT... since we do not have an unlocked bootloader then we cannot have any custom recovery. Which means we can only (for now) use adb and Fireflash to flash any custom firmwares. And while we're on the subject of that... there is only one custom rom. Well... technically there are two but only one for you since you updated to the latest firmware.
Echoe ROM which was updated (ummm...) September 9th (not including the Verizon version which might work but with no promises)
Tekxv2 which was updated back in July. Unfortunately, that is flashed by adb (computer required) and only supports G935TUVS3APD8 which is... pretty old.
Things that you may notice with root.
Battery life may be shorter.
Strange icons on your status bar.
Might start to have random reboots for absolutely no reason.
Can't use Samsung Pay and some other apps.
Phone might be laggy.
Phone might feel hot.
Some of those can be resolved by flashing the only custom rom that we have (Echoe ROM... which is a rather nice rom) but it's not "there" yet.
Or you can use the guide in my signature to resolve issues like the lag and the strange icons. Yet even after the "fix" you might still experience both again from time to time.
You might even have the IMS force close issue which I used to get about once a month. It would piss me off because no sooner that you click the button, it'll pop up again and you don't have time to do anything. You're pretty much forced to reflash stock, wipe, re-root, restore a latest backup... which can take hours and is rather inconvenient if it happens to you while you're at work like it always seemed to happen for me.
SO...
All in all... root is okay. It's better than nothing I suppose. But until we get more developer support for this phone then in my opinion it's kinda pointless in my opinion.
Too many drawbacks. I eventually unrooted two weeks ago and I love my phone now. I'm using the heck out of Samsung Pay especially since their promotions are pretty nice right now! Plus a few members are testing the Nouget update which probably won't be getting root at all since rooting requires an engineering kernel which we don't have and might not get. Or an unlocked bootloader which we've pretty much given up on.
A lot of members that are testing the Nouget beta firmware are extremely satisfied with it so if we can't root Nouget then having a rooted S7 will probably fade away as more people update to Android 7+. That's where I see this going anyway.

Binary100100 said:
What you wrote above
Click to expand...
Click to collapse
So for what I understood the dev support for this phone is very limited... I know the issues I may encounter, I had them with the galaxy note. but any way... If something I'll unroot it but I want to try it out Thank for you time. I've rooted it.
EDIT: Damn... I really don't like the visual style of Echoe... is that one the only one I can flash??

Binary100100 said:
Well then.
Rooting the phone (as I'm sure you had already found out) was fairly easy.
BUT... since we do not have an unlocked bootloader then we cannot have any custom recovery. Which means we can only (for now) use adb and Fireflash to flash any custom firmwares. And while we're on the subject of that... there is only one custom rom. Well... technically there are two but only one for you since you updated to the latest firmware.
Echoe ROM which was updated (ummm...) September 9th (not including the Verizon version which might work but with no promises)
Tekxv2 which was updated back in July. Unfortunately, that is flashed by adb (computer required) and only supports G935TUVS3APD8 which is... pretty old.
Things that you may notice with root.
Battery life may be shorter.
Strange icons on your status bar.
Might start to have random reboots for absolutely no reason.
Can't use Samsung Pay and some other apps.
Phone might be laggy.
Phone might feel hot.
Some of those can be resolved by flashing the only custom rom that we have (Echoe ROM... which is a rather nice rom) but it's not "there" yet.
Or you can use the guide in my signature to resolve issues like the lag and the strange icons. Yet even after the "fix" you might still experience both again from time to time.
You might even have the IMS force close issue which I used to get about once a month. It would piss me off because no sooner that you click the button, it'll pop up again and you don't have time to do anything. You're pretty much forced to reflash stock, wipe, re-root, restore a latest backup... which can take hours and is rather inconvenient if it happens to you while you're at work like it always seemed to happen for me.
SO...
All in all... root is okay. It's better than nothing I suppose. But until we get more developer support for this phone then in my opinion it's kinda pointless in my opinion.
Too many drawbacks. I eventually unrooted two weeks ago and I love my phone now. I'm using the heck out of Samsung Pay especially since their promotions are pretty nice right now! Plus a few members are testing the Nouget update which probably won't be getting root at all since rooting requires an engineering kernel which we don't have and might not get. Or an unlocked bootloader which we've pretty much given up on.
A lot of members that are testing the Nouget beta firmware are extremely satisfied with it so if we can't root Nouget then having a rooted S7 will probably fade away as more people update to Android 7+. That's where I see this going anyway.
Click to expand...
Click to collapse
How are you doing with the ads? Like youtube, pandora, spotify? I just installed xposed and the phone feels very hot, and If I unroot it (which I'm thinking to do) I won't be able to get things without ads (I know about vpns and browsers). Also how can I install teaks for apps? Installing apks from pages that promise you this and you have to log in is very untruthful. Any suggestions to all this?

Arturofm2 said:
How are you doing with the ads? Like youtube, pandora, spotify? I just installed xposed and the phone feels very hot, and If I unroot it (which I'm thinking to do) I won't be able to get things without ads (I know about vpns and browsers). Also how can I install teaks for apps? Installing apks from pages that promise you this and you have to log in is very untruthful. Any suggestions to all this?
Click to expand...
Click to collapse
I just put up with them.
In all reality, I don't use my phone for the purposes that require my viewing of ads to begin with.
Sure when I was rooted I had adblocker. But honestly, I had completely forgotten all about that benefit of being rooted until now.
I suppose if you absolutely need to be rid of ads then by all means, retain root. However ads don't effect my daily use one bit.

Binary100100 said:
I just put up with them.
In all reality, I don't use my phone for the purposes that require my viewing of ads to begin with.
Sure when I was rooted I had adblocker. But honestly, I had completely forgotten all about that benefit of being rooted until now.
I suppose if you absolutely need to be rid of ads then by all means, retain root. However ads don't effect my daily use one bit.
Click to expand...
Click to collapse
Could you help me unroot it? I was following a guide here to unroot it and downloaded the firmware but when I click flash, it didn't work, I'm having travel reverting it, can you help me? The model is: SM-G935T

Arturofm2 said:
Could you help me unroot it? I was following a guide here to unroot it and downloaded the firmware but when I click flash, it didn't work, I'm having travel reverting it, can you help me? The model is: SM-G935T
Click to expand...
Click to collapse
I just flash the appropriate firmware that you had prior to rooting with ODIN.
Never had any issues. Which "guide" are you referring to?

Binary100100 said:
I just flash the appropriate firmware that you had prior to rooting with ODIN.
Never had any issues. Which "guide" are you referring to?
Click to expand...
Click to collapse
bro now I'm friking out, I followed this guide and when I click in flash it says Fail. I followed it step by step, I don't don't what's going on and when I reset the phone it says custom and doesn't even load, so tmobil would know that I rooted it...
fff.... can you give me the link, guide, whatever you used to revert it?

Arturofm2 said:
bro now I'm friking out, I followed this guide and when I click in flash it says Fail. I followed it step by step, I don't don't what's going on and when I reset the phone it says custom and doesn't even load, so tmobil would know that I rooted it...
fff.... can you give me the link, guide, whatever you used to revert it?
Click to expand...
Click to collapse
You're probably trying to flash a firmware with a V3 bootloader over G935TTMB4APK1.
If you were seriously following that (outdated) guide step by step then you tried flashing TMB_G935TUVU3APG1.zip over a PK1 firmware. Yeah... that doesn't work.
Download the latest firmware from sammmobile.
https://www.sammobile.com/firmwares/database/SM-G935T/
Try it again.
IF that doesn't work... try using Smart Switch.
I haven't done it before but I think it's the Emergency Software Recovery and Initialization.

forum.xda-developers.com/tmobile-s7-edge/how-to/odin-apk1-tmobile-tmbg935ttmb4apk1-t3494724
Odin this to return to stock firmware.

Binary100100 said:
You're probably trying to flash a firmware with a V3 bootloader over G935TTMB4APK1.
If you were seriously following that (outdated) guide step by step then you tried flashing TMB_G935TUVU3APG1.zip over a PK1 firmware. Yeah... that doesn't work.
Download the latest firmware from sammobile.
https://www.sammobile.com/firmwares/database/SM-G935T/
Try it again.
IF that doesn't work... try using Smart Switch.
I haven't done it before but I think it's the Emergency Software Recovery and Initialization.
Click to expand...
Click to collapse
You have no idea the help you gave me. I went to sammobil before but since it said that the download speed was too slow, I didn't do it through that page. Now I did it and it's working fine thanks bro.
But when I start it, it says: custom in the log in, how can I totally put it original?

tduquefjc said:
forum.xda-developers.com/tmobile-s7-edge/how-to/odin-apk1-tmobile-tmbg935ttmb4apk1-t3494724
Odin this to return to stock firmware.
Click to expand...
Click to collapse
If I want to remove everything and just leave it plain how it comes from factory when you buy it, do I just flash the AP file?

Arturofm2 said:
You have no idea the help you gave me. I went to sammobil before but since it said that the download speed was too slow, I kept it. Now I did it and it's working fine thanks bro.
But when I start it, it says: custom in the log in, how can I totally put it original?
Click to expand...
Click to collapse
Arturofm2 said:
If I want to remove everything and just leave it plain how it comes from factory when you buy it, do I just flash the AP file?
Click to expand...
Click to collapse
You should flash everything.
BL= Bootloader (which should be V4 since you updated to the latest firmware already. Anything less than V4 will fail.)
AP= Is for System, Cache, kernel, etc.
CP= Is for modems
CSC is for your HOME_CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 file.
Important! If you use the CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 (doesn't have the word "HOME" in the name) then it'll wipe your phone!
If your phone still says "CUSTOM" on it then make sure that reboot and check again. If it still says custom then make sure that you don't still have the engineering kernel. Re-flash the AP files again if so. It shouldn't though if it's 100% stock. Also note if you saw the unlocked padlock on the S7 Edge splash screen (before the bootanimation).
Good luck and happy New Year.

Binary100100 said:
You should flash everything.
BL= Bootloader (which should be V4 since you updated to the latest firmware already. Anything less than V4 will fail.)
AP= Is for System, Cache, kernel, etc.
CP= Is for modems
CSC is for your HOME_CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 file.
Important! If you use the CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 (doesn't have the word "HOME" in the name) then it'll wipe your phone!
If your phone still says "CUSTOM" on it then make sure that reboot and check again. If it still says custom then make sure that you don't still have the engineering kernel. Re-flash the AP files again if so. It shouldn't though if it's 100% stock. Also note if you saw the unlocked padlock on the S7 Edge splash screen (before the bootanimation).
Good luck and happy New Year.
Click to expand...
Click to collapse
Perfect! All I did was reboot it, and the unlocked padlock went away, thank you very much for all your help! Happy new year!