Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,771,588 Members 47,228 Now Online
XDA Developers Android and Mobile Development Forum

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

Tip us?
 
jbrookley
Old
#1  
Member - OP
Thanks Meter 5
Posts: 31
Join Date: Sep 2011
Question [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).
 
NighthawkXL
Old
#2  
NighthawkXL's Avatar
Senior Member
Thanks Meter 236
Posts: 267
Join Date: Mar 2013
Location: Florida

 
DONATE TO ME
Quote:
Originally Posted by jbrookley View Post
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).
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.
My Devices
Samsung Galaxy S4 (SGH-I337)
  • ROM - Purified [4.4.2]
  • Baseband - NC1
  • Root - Yes
  • Recovery - SafeStrap 3.72
----------------------------------------------------------
Enjoying my help? Feel free to help feed this broke college student.
The Following User Says Thank You to NighthawkXL For This Useful Post: [ Click to Expand ]
 
DeadlySin9
Old
#3  
DeadlySin9's Avatar
Senior Member
Thanks Meter 620
Posts: 1,240
Join Date: Sep 2012

 
DONATE TO ME
Quote:
Originally Posted by jbrookley View Post
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?
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.
Current Device: ATT Samsung Galaxy S4 (i337)

Past Devices:
Droid Bionic (GSM Hacked)
HTC Inspire 4G (Desire HD)
Nexus One
Motorola Backflip
HTC Dev Phone 1 (Dream/G1)
The Following User Says Thank You to DeadlySin9 For This Useful Post: [ Click to Expand ]
 
jbrookley
Old
#4  
Member - OP
Thanks Meter 5
Posts: 31
Join Date: Sep 2011
Quote:
Originally Posted by DeadlySin9 View Post
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.
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?
 
hovax615@hotmail.com
Old
#5  
hovax615@hotmail.com's Avatar
Senior Member
Thanks Meter 309
Posts: 1,480
Join Date: Jan 2009
Location: Corona, CA - Murfreesboro, TN
Quote:
Originally Posted by jbrookley View Post
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?
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
 
DeadlySin9
Old
#6  
DeadlySin9's Avatar
Senior Member
Thanks Meter 620
Posts: 1,240
Join Date: Sep 2012

 
DONATE TO ME
Quote:
Originally Posted by jbrookley View Post
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?
Quote:
Originally Posted by hovax615@hotmail.com View Post
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
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.
Current Device: ATT Samsung Galaxy S4 (i337)

Past Devices:
Droid Bionic (GSM Hacked)
HTC Inspire 4G (Desire HD)
Nexus One
Motorola Backflip
HTC Dev Phone 1 (Dream/G1)
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


MacroDroid Update Brings Android Wear Automation

A few months ago, we talked about MacroDroid. For those who don’t remember, MacroDroid … more

Droid X Receives KitKat Port, Upcoming Google Glass Firmware Improvements – XDA Developer TV

Android 4.4.3 lands on the European HTC … more

Calc+ is a Smart and Beautiful Android Calculator

As we’ve said inthe past, there are quite a few calculators available on Android. … more

Get Better Debug Data with Crash Report SDK

Developing an application is a hard and often times ungratifying task. It also requires quite a … more