Database Users

[Q] Who doesn't Loki work on MF3?

Hello everyone,
So, I've been looking into the status of unlocking the bootloader for MF3 updates (I downloaded it and read too late that they locked the bootloader in the update, sneaky bastards) and it appears this issue still hasn't been fixed. From what I understand, Dan Rosenberg waited until the Verizon update was released before he revealed the Loki exploit but, from what I've read, this exploit does not work on the MF3 update.
My question is now what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
I'm trying to understand some of the specifics as I've read a number of articles and links (both in XDA as well as others) and I'm still a bit confused as to where we're at with this. From what I can see, it doesn't appear there is any workaround in sight if the Loki exploit doesn't fix it. Am I more than likely stuck with a locked bootloader for the life of this phone?
Realistically, I am still able to get root access, so it's really not the end of the world but I'd definitely like to be able to flash custom roms if I wanted to. It sounds like I can indirectly do that via Safestrap (does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?). But as of now, I believe that's my only option, if I understand correctly.
I realize a number of these issues have been addressed probably a number of times but, due to the amount of details and updates that seem to be changing, I just want to make sure I have a good understanding of everything so I know what my options are. If anyone wants to address this, I'd appreciate it but if these have all been answered a million times in one form or another, I understand that as well.
Thanks for your help!
(I put my questions in bold just to draw attention to them so anyone reading it doesn't have to search through my message to find them to address them, I'm not trying to come off like I'm yelling).

jbrookley said:
Hello everyone,
So, I've been looking into the status of unlocking the bootloader for MF3 updates (I downloaded it and read too late that they locked the bootloader in the update, sneaky bastards) and it appears this issue still hasn't been fixed. From what I understand, Dan Rosenberg waited until the Verizon update was released before he revealed the Loki exploit but, from what I've read, this exploit does not work on the MF3 update.
My question is now what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
I'm trying to understand some of the specifics as I've read a number of articles and links (both in XDA as well as others) and I'm still a bit confused as to where we're at with this. From what I can see, it doesn't appear there is any workaround in sight if the Loki exploit doesn't fix it. Am I more than likely stuck with a locked bootloader for the life of this phone?
Realistically, I am still able to get root access, so it's really not the end of the world but I'd definitely like to be able to flash custom roms if I wanted to. It sounds like I can indirectly do that via Safestrap (does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?). But as of now, I believe that's my only option, if I understand correctly.
I realize a number of these issues have been addressed probably a number of times but, due to the amount of details and updates that seem to be changing, I just want to make sure I have a good understanding of everything so I know what my options are. If anyone wants to address this, I'd appreciate it but if these have all been answered a million times in one form or another, I understand that as well.
Thanks for your help!
(I put my questions in bold just to draw attention to them so anyone reading it doesn't have to search through my message to find them to address them, I'm not trying to come off like I'm yelling).
Click to expand...
Click to collapse
When Samsung released the MF3 update they used a two-prong attack to close the Loki exploit... those being
1. Closing the exploit in the code itself.
2. Blowing a qFuse on the board to prevent us from flashing any firmware lower then MF3.
I don't really want to get into the technical aspects of how this happened... I'll let someone else answer it if they wish.

jbrookley said:
Hello everyone,
what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
Am I more than likely stuck with a locked bootloader for the life of this phone?
does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?
Click to expand...
Click to collapse
Nighthawk gave the short answer for the first two. Also, it's possible the update mentioned may have been the MDB>MDL update or verizon equivalent.
Technically even MDL people are stuck with a locked bootloader, but they have an exploit. People are working on an exploit for MF3+, but I can't say how likely it is one will be found.
Safestrap lets you do anything a normal recovery can except flash kernels. This is why you can only flash TW ROMs, as the AOSP and TW kernels are not compatible. Kernels would trip the bootloader checks. However, to add a bit to this and the last answer, something called kexec is in progress of being implemented into Safestrap. The exploit found allows loading unsigned modules, which in turn allows loading a kexec module, which would then load a kernel over the stock kernel while in the boot process. So if this works, it would be the next best thing to a bootloader exploit in that it would give us the same result, though I don't know if kernels will require tweaks to load in kexec.

DeadlySin9 said:
Nighthawk gave the short answer for the first two. Also, it's possible the update mentioned may have been the MDB>MDL update or verizon equivalent.
Technically even MDL people are stuck with a locked bootloader, but they have an exploit. People are working on an exploit for MF3+, but I can't say how likely it is one will be found.
Safestrap lets you do anything a normal recovery can except flash kernels. This is why you can only flash TW ROMs, as the AOSP and TW kernels are not compatible. Kernels would trip the bootloader checks. However, to add a bit to this and the last answer, something called kexec is in progress of being implemented into Safestrap. The exploit found allows loading unsigned modules, which in turn allows loading a kexec module, which would then load a kernel over the stock kernel while in the boot process. So if this works, it would be the next best thing to a bootloader exploit in that it would give us the same result, though I don't know if kernels will require tweaks to load in kexec.
Click to expand...
Click to collapse
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?

jbrookley said:
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?
Click to expand...
Click to collapse
I believe the kexec exploit is being worked on for mk2? But I'm not too sure you will have to review the threads.
Sent from my GT-I9505 using xda premium

jbrookley said:
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?
Click to expand...
Click to collapse
[email protected] said:
I believe the kexec exploit is being worked on for mk2? But I'm not too sure you will have to review the threads.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
It is MK2 exclusive since the MK2 root method gives access to kernel memory and allows it. However, once on MK2 you should definitely not take any and I'm not sure whether the security policy updates are safe or not.

[Q] Please Help!

So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.

khampton_03 said:
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
Click to expand...
Click to collapse
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?

Adam Browning said:
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Click to expand...
Click to collapse
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.

khampton_03 said:
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
Click to expand...
Click to collapse
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Here is a link for the Eclipse thread: http://forum.xda-developers.com/showthread.php?t=2620723

Adam Browning said:
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Click to expand...
Click to collapse
So could I somehow unlock the bootloader??

khampton_03 said:
So could I somehow unlock the bootloader??
Click to expand...
Click to collapse
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876

Adam Browning said:
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Click to expand...
Click to collapse
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha

khampton_03 said:
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
Click to expand...
Click to collapse
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?

Adam Browning said:
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Click to expand...
Click to collapse
Ive never flashed anything and I dont know how to use odin. Lol

khampton_03 said:
Ive never flashed anything and I dont know how to use odin. Lol
Click to expand...
Click to collapse
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558

Adam Browning said:
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Click to expand...
Click to collapse
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?

khampton_03 said:
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
Click to expand...
Click to collapse
That, you don't really have to worry about honestly. I never check, though it may be good practice to. Just follow along with the video in the thread and you will be good to go. Just remember that after you install 4.4.2, you cannot flash 4.3 based ROMs. Also, there is a bug in Safestrap right now that renders the ROM slots somewhat useless, though you can attempt to use them at your own risk. If you want to flash one of the 4.4.2 based ROMs afterwards, it is suggested to back up the stock ROM, and flash the custom ROM in the stock ROM slot. All I can say is, goodluck. Lol. It is a fun process, though somewhat difficult at times. If you have anymore questions after the fact, just reply here. I'll help out as much as I can. It always puts a smile on my face to help convert an Apple fanboy/girl over to Android.

Another upgrade

Guys, my phone just told me there's another upgrade for the lg g2 D803 variant....Anybody seen this yet?
I'm wondering what the upgrade is, seeing it's 1.5 gb.
It's gonna take me to D803B20G. Not sure if the current rooting and autorec recovery method will work on this new firmware, sceptical about installing it......

rodpgfx said:
Guys, my phone just told me there's another upgrade for the lg g2 D803 variant....Anybody seen this yet?
I'm wondering what the upgrade is, seeing it's 1.5 gb.
It's gonna take me to D803B20G. Not sure if the current rooting and autorec recovery method will work on this new firmware, sceptical about installing it......
Click to expand...
Click to collapse
1. wrong place to post this.
2. general rule of thumb - if you like having root and recovery, NEVER take an OTA from the manufacturer EVER, until it's confirmed that it doens't block root / recovery /bootloader exploits (like the 4.4 ot'as blocked loki)

jakew02 said:
1. wrong place to post this.
jakew02 said:
Sorry, I wasn't sure where to put as there is no folder for 803 variant.....
Click to expand...
Click to collapse
Click to expand...
Click to collapse

jakew02 said:
1. wrong place to post this.
Click to expand...
Click to collapse
Sorry, I never seen a folder for the D803 variant so I wasn't sure where to put this.... Should it have gone in Q&A?

rodpgfx said:
Sorry, I never seen a folder for the D803 variant so I wasn't sure where to put this.... Should it have gone in Q&A?
Click to expand...
Click to collapse
Q&A if you're asking a question about it, General if you wanted to let people know about it..

yes probably in q&a or general maybe, like stated above please dont install on your phone if youre rooted with a non stock recovery otherwise you will mess up your phone big time! really not sure if its possible but if you can, switch off firmware updates as they are not compatible with the custom recoveries and whichever rom you are using will update soon enough anyway if your on stock rom the same applies if you have a custom recovery

martindar said:
yes probably in q&a or general maybe, like stated above please dont install on your phone if youre rooted with a non stock recovery otherwise you will mess up your phone big time! really not sure if its possible but if you can, switch off firmware updates as they are not compatible with the custom recoveries and whichever rom you are using will update soon enough anyway if your on stock rom the same applies if you have a custom recovery
Click to expand...
Click to collapse
I have stock Rom rooted and twrp recovery that's all.

Avoid the update.
However it has the knock knock code addon. Or, as far as I've heard, that's the only new update LG had planned for the LG G2.
Do not install it. If you REALLY want to try it, make a backup, store it on your PC, OTA. If you lose root, you can revert to stock, get a recovery, put your backup back on your phone and restore.....but that's honestly a lot of work just to possibly get the knock knock code. (I know turning on is knock on, but for the "code" you knock more than once minimum, so I call it knock knock).
You can also force supersu to keep root, but last time I tried that for an OTA I got stuck in a bootloop.
TL;DR: Might be knock on/knock knock code. Not sure what else. You can backup and try to OTA, but no one can be certain what will happen. Expect to lose root. You can force SuperSu to keep root, but you may bootloop.
I'd just wait for more info.

rodpgfx said:
I have stock Rom rooted and twrp recovery that's all.
Click to expand...
Click to collapse
twrp recovery is a custom recovery, so never update.

I'm pretty sure there is an app in /system that you can freeze to stop push updates. Sadly, that is the only info I have. It may have been carrier specific and I haven't been on stock since the first week I had the phone. Haha.

Guys I already know all what you just said......I've done this loads of times. Just wondering if I can uninstall custom recovery without re-installing stock firmware?
I know I can take my chance and try the OTA but not without recovery gone first.
It's a lot of work to just flash stock firmware, install update and if there's no big change, flash stock again.....
Thats why i was wondering if the only option is flash stock to get rid of recovery

martindar said:
twrp recovery is a custom rom so never update
Click to expand...
Click to collapse
Twrp is not a Rom it's a recovery. Hence the "recovery"
Sent from my VS980 4G using XDA Premium 4 mobile app

Esteway.619 said:
Twrp is not a Rom it's a recovery. Hence the "recovery"
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol, yeah I didn't want to say anything. He should read up before doing anything with his phone.

rodpgfx said:
Guys I already know all what you just said......I've done this loads of times. Just wondering if I can uninstall custom recovery without re-installing stock firmware?
I know I can take my chance and try the OTA but not without recovery gone first.
It's a lot of work to just flash stock firmware, install update and if there's no big change, flash stock again.....
Thats why i was wondering if the only option is flash stock to get rid of recovery
Click to expand...
Click to collapse
I think its possible, (but it should be really hard to do so) but the easiest way is to flash a .kdz file And you should not take the chance to update when you have recovery, it just isn't worth it. Anyways I would just have sticked with a custom rom which gets updated regulary..or flashed a kdz and get back to stock.
Btw can the good judger @Judge Joseph Dredd move the thread to q and a section? I think that it is even more help to get there

OP Moved out of the Development Threads, since this does not belong there....Please read the Forum Rules on posting.

Double check before I root

I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!

burgertime78 said:
I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!
Click to expand...
Click to collapse
You can't flash anything other than Touch Wiz Roms. That guide and ones like The Ultimate All in one Guide will be a starting place. No custom recoveries either.
Sent from my GT-I9505G using Tapatalk

rugmankc said:
You can't flash anything other than Touch Wiz Roms. That guide and ones like The Ultimate All in one Guide will be a starting place. No custom recoveries either.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
So what's the problem? ATT? too new a hardware version? I have the worst luck with this stuff - if I buy a router to flash a custom firmware like Tomato, it's the ONLY version that isn't supported. crazy.
I'm not sure what a custom recovery is unfortunately. That said, can I root this phone at all? I guess if I can't flash the rom I want to use, can I at least install titanium and freeze all the crapware that I don't want running?
btw - thanks for the response.

burgertime78 said:
So what's the problem? ATT? too new a hardware version? I have the worst luck with this stuff - if I buy a router to flash a custom firmware like Tomato, it's the ONLY version that isn't supported. crazy.
I'm not sure what a custom recovery is unfortunately. That said, can I root this phone at all? I guess if I can't flash the rom I want to use, can I at least install titanium and freeze all the crapware that I don't want running?
btw - thanks for the response.
Click to expand...
Click to collapse
Any build after mdl has the bootloader locked down. If you read thru those two threads OP pages you get an idea. You will also need to get familiar with SafeStrap. I am on the old build and can use an exploit called loki-doki to bypass Sammy's security check and allow kernel to flash.
There may be some new stuff on rooting NC1, but I don't keep up. Basically you had to go back to mk2 to root then go back NC1 and use SafeStrap to flash only TW roms. The SafeStrap thread will explain that. But, it creates slots on the System partition again fooling Sammy. More or less--
Like I said not an expert as I don't have the issue you have with bootloader. But that is the gist of it. Just need to read up so you don't brick--good luck.

rugmankc said:
Any build after mdl has the bootloader locked down. If you read thru those two threads OP pages you get an idea. You will also need to get familiar with SafeStrap. I am on the old build and can use an exploit called loki-doki to bypass Sammy's security check and allow kernel to flash.
There may be some new stuff on rooting NC1, but I don't keep up. Basically you had to go back to mk2 to root then go back NC1 and use SafeStrap to flash only TW roms. The SafeStrap thread will explain that. But, it creates slots on the System partition again fooling Sammy. More or less--
Like I said not an expert as I don't have the issue you have with bootloader. But that is the gist of it. Just need to read up so you don't brick--good luck.
Click to expand...
Click to collapse
DAMN! Thanks!

burgertime78 said:
DAMN! Thanks!
Click to expand...
Click to collapse
Good Luck
There are plenty of folks here to help with specifics like jd and tedusa--:good:

burgertime78 said:
I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!
Click to expand...
Click to collapse
New way to root is call towelroot. Google it or search for it around here the link is everywhere. It's an apk file made by geohot (same guy that jail broke the iphone and ps3). Once you root you can install safestrap. If you've ever owned an droid device they have something identical called boot strap. Think of it as a dual boot of sorts. Definitely keep your eyes on these threads as well as the sgs5 thread. If an exploit is discovered it'll probably be for the s5 and will be compatible with our s4 (towel root was made for the s5 but works for a whole bunch of devices)
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

burgertime78 said:
DAMN! Thanks!
Click to expand...
Click to collapse
Link: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3&nocache=1&z=8413408249616623
I was in the same boat as you 2 weeks ago, bought a NC1 and wanted CM, and used this to root. I currently use the Google Edition ROM that has been modified to work on locked bootloader phones, though it does have it's fallbacks. For someone new I'd recommend GoldenEye, just click the link on my signature to download it.
Good luck!

Oh, btw--check out GEOHOT's Towelroot thread in General for NC1. I knew I forgot one. That was the recent method I was thinking of. Not sure which of threads are best for you--depends what you want to do.
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
HaHa posted at same time.

You all are AWESOME! Thank you so much! I'll look into this and keep you posted.

rugmankc said:
Oh, btw--check out GEOHOT's Towelroot thread in General for NC1. I knew I forgot one. That was the recent method I was thinking of. Not sure which of threads are best for you--depends what you want to do.
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
HaHa posted at same time.
Click to expand...
Click to collapse
I just towelrooted. It worked! I was watching this video http://gs5.wonderhowto.com/how-to/r...nt-even-at-t-verizon-20-seconds-flat-0155617/ and I did it while I Was watching the video. On my device, it did not even reboot - i just said "should be rooted" so I loaded a root checker and sure enough, it is rooted! took all of about 8 seconds.
Now, on to a rom.
I'm confused now. Why can I not use CM? I read about SafeStrap and I understand it's sort of a dual boot setup - I get that. So, in a sense, I'm not really installing FRESH, a new rom - at least not in the sense that you format your hard disk and install a new OS. However, what ARE my choices in roms? I know the whiz touch, and now the golden eye, plus the google modified - but what else? I want something cut down, simple and battery friendly. I'm not a super power user and I don't require much. Actually, battery life is the most important thing to me.
This is my business phone - I use Gmail, SMS, maybe take a few pictures - and I listen to podcasts. very basic user. Advice?

burgertime78 said:
I just towelrooted. It worked! I was watching this video http://gs5.wonderhowto.com/how-to/r...nt-even-at-t-verizon-20-seconds-flat-0155617/ and I did it while I Was watching the video. On my device, it did not even reboot - i just said "should be rooted" so I loaded a root checker and sure enough, it is rooted! took all of about 8 seconds.
Now, on to a rom.
I'm confused now. Why can I not use CM? I read about SafeStrap and I understand it's sort of a dual boot setup - I get that. So, in a sense, I'm not really installing FRESH, a new rom - at least not in the sense that you format your hard disk and install a new OS. However, what ARE my choices in roms? I know the whiz touch, and now the golden eye, plus the google modified - but what else? I want something cut down, simple and battery friendly. I'm not a super power user and I don't require much. Actually, battery life is the most important thing to me.
This is my business phone - I use Gmail, SMS, maybe take a few pictures - and I listen to podcasts. very basic user. Advice?
Click to expand...
Click to collapse
MDL builds have an exploit that allows the kernel to flash. That is loki-doki. Bypasses the Sammy security check to allow this. There is no exploit yet for post MDL builds. Hence you can only flash stock Touch Wiz kernels, thus only roms that have them. So, no aosp based roms. In one of the threads in General that talk about MK2/NC1 etc is a list of roms for you. I forget the technical coding side of SafeStrap. But, it puts roms in System bypassing the bootloader. But, no way of doing that with aosp roms yet.
I am old and don't retain things much anymore if they are not very important to me. So, although I have read up on this stuff, and have a "45 year old" Engineering Degree, I don't need SafeStrap having the MDL bootloader. So, don't remember all that I have read. But, what I said is the basics of it.
Your roms need to have SafeStrap option in the rom thread's OP page. If not listed, it won't work. Having said all that things like Towelroot are new and more options may come along. :good:

"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!