Since ATT's Bootloader is locked... ?

[Pikezer1337]

What are the chances of the device getting rooted then? I noticed the GS4's bootloader was locked but it was able to be rooted. I don't need custom ROM's just root. Any answer would be appreciated.
Thanks!

 

[Pikezer1337]

Bump

 

[mircury]

I would say the chances are pretty good that root will be achieved. You will just have to wait till an exploit is found. You could do what I did and get the tmobile version which already has a custom recovery where you can flash a rooted stock rom.

 

[lknhiayi]

I would say the chances are pretty good that root will be achieved. You will just have to wait till an exploit is found. You could do what I did and get the tmobile version which already has a custom recovery where you can flash a rooted stock rom.

Is the T-Mobile one has att LTE band ?

 

[mircury]

According to the FCC lab report, yes it does.

 

[daraj]

According to the FCC lab report, yes it does.

But there is no real world confirmation yet.

 

[mircury]

But there is no real world confirmation yet.

That is correct. No one knows for sure yet. All we know is that it has the correct radio and bands. Hopefully it will work the same as the S4.

 

[designgears]

After some more digging it looks like the write protection enabled only applies to the bootloaders and other lower level partitions, which means we might be able to flash the boot/recovery/modem partitions still. However, it WILL trip the Knox flags, which means the warranty is void and will NOT be able to run any Knox apps.

None of these things bother me since AT&T doesn't know about any of this stuff and Knox isn't useful to me.

 

[daraj]

After some more digging it looks like the write protection enabled only applies to the bootloaders and other lower level partitions, which means we might be able to flash the boot/recovery/modem partitions still. However, it WILL trip the Knox flags, which means the warranty is void and will NOT be able to run any Knox apps.

None of these things bother me since AT&T doesn't know about any of this stuff and Knox isn't useful to me.

Where you able to verify this using the att build? In other words, do u know for fact that the bootloader if locked?

 

[designgears]

Where you able to verify this using the att build? In other words, do u know for fact that the bootloader if locked?

As I stated in this thread;
http://forum.xda-developers.com/showthread.php?t=2458928

ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
WRITE PROTECTION: Enable

With that, even the Galaxy S3 shows QUALCOMM SECUREBOOT: ENABLE after it is unlocked, and WRITE PROTECTION: Enable applies to the bootloaders and other sensitive partitions.

I would assume we can flash boot/recovery/modem.

 

[daraj]

As I stated in this thread;
http://forum.xda-developers.com/showthread.php?t=2458928

ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
WRITE PROTECTION: Enable

With that, even the Galaxy S3 shows QUALCOMM SECUREBOOT: ENABLE after it is unlocked, and WRITE PROTECTION: Enable applies to the bootloaders and other sensitive partitions.

I would assume we can flash boot/recovery/modem.

Knox kernel thats new. We are screwed. Better off getting the Rogers/Tmobile version(most prbly wont be locked)

 

[designgears]

Knox kernel thats new. We are screwed. Better off getting the Rogers/Tmobile version(most prbly wont be locked)

Ya, it seems like the kernel is encrypted, I have been unable to rip it apart with any current methods.

 

[Pikezer1337]

So basically we can root the device but the possibility of flashing new ROMS and kernel's will be extremely difficult?

 

[mohan_kr]

Knox kernel thats new. We are screwed. Better off getting the Rogers/Tmobile version(most prbly wont be locked)

So basically we can root the device but the possibility of flashing new ROMS and kernel's will be extremely difficult?

Yup..if the old root exploit still works (if it does not, then pretty much toast). The bootloader *cannot* be replaced yet (even in S4), if you were lucky and had the earlier bootloader then you could "loki" run custom roms/recoveries. Otherwise the only option appears to be the "kexec" type method (safestrap), yuk..get one without a bootloader lock (hoping T-MO does not lock it and allows unsigned kernels and recoveries)..

Although I don't understand why ATT would this, the above methods for S4 has made people who didn't understand the process fully to go back to Samsung//BB service centers to reflash the stock f/w.

 

[mircury]

So basically we can root the device but the possibility of flashing new ROMS and kernel's will be extremely difficult?

Actually getting root is going to be difficult. An unpatched exploit will be needed. Rom's and kernels will be the extremely difficult part. Samsung's credibility is on the line for a secure business solution with KNOX so you better believe they are going to make it hard if carrier's like ATT decide to lock down their devices like they have.

 

[Pikezer1337]

Yeah, I'm still just trying to understand why ATT is doing this. Hopefully the old root method works then, otherwise it is a deal breaker for me.

 

[daraj]

Yeah, I'm still just trying to understand why ATT is doing this. Hopefully the old root method works then, otherwise it is a deal breaker for me.

Since we pretty much know that att version is bootloader locked(designgears confirmed) do we know If the tmobile version or the International version has this Knox kernel?

 

[mircury]

Since we pretty much know that att version is bootloader locked(designgears confirmed) do we know If the tmobile version or the International version has this Knox kernel?

I don't think it matters at this point. My understanding is that with the custom recovery already available you can flash a rom with root and with knox disabled. There is already a dev working on striping knox out in the dev section.

 

[Pikezer1337]

Geez, it's just hard imagining a phone like the Note 3 never having root access. But hey if that's what happens, I guess there's nothing you can do.

 

[mohan_kr]

I don't think it matters at this point. My understanding is that with the custom recovery already available you can flash a rom with root and with knox disabled.

That's correct. If a bootloader is unlocked and you ODIN flash a custom recovery and install su and push super su. The kernel is not SELinux permissive, then we just need to wait for the source drop, compile a new kernel. The important thing is the bootloader unlock and knox security allowing unsigned kernels and recoveries. From the S4 T-MO thread it appears that the T-MO version allows that..so it will not be a big deal..ATT ones of course you are pretty much toast.