Related
I've read elsewhere that the new S4 bootloader has locked.
Can someone verify this?
How does it affect the usage of the device?(i.e CM,AOSP etc)
So far only on the AT&T and Verizon models.
They'll have root for now but no custom recovery/roms.
ChronoReverse said:
So far only on the AT&T and Verizon models.
They'll have root for now but no custom recovery/roms.
Click to expand...
Click to collapse
I just want to know a bit more about it...I've got the I9505 model,which is definately not AT&T or Verizon.
But it's not confirmed yet,isn't it?
hunhool said:
I just want to know a bit more about it...I've got the I9505 model,which is definately not AT&T or Verizon.
Click to expand...
Click to collapse
The AT&T and Verizon bootloader is locked, which will restrict flashing roms and kernels but not root for those devices until the bootloader is unlocked. The international versions seem to be not locked so that does apply to all the octa versions.
Sent from my SPH-L720 using xda app-developers app
short story: the international isn't the carriers are
effect on dev gives them a extra work to do
inlineboy said:
The AT&T and Verizon bootloader is locked, which will restrict flashing roms and kernels but not root for those devices until the bootloader is unlocked. The international versions seem to be not locked so that does apply to all the octa versions.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Is there any simple way to find out whether is locked or not?
hunhool said:
Is there any simple way to find out whether is locked or not?
Click to expand...
Click to collapse
There isn't sadly. People were saying if you boot into download mode and it said Write Protection: Enabled that the bootloader was locked, as is the case for atnt and verizon, but the it says the same thing for sprint and our bootloader does not seem to be locked- it's a bit more complicated to actually know and I don't have the tech knowledge to explain it as well as someone else probably could. Probably should find others with your exact phone in the forum and just read what they have said cause this has been a huge topic over the last few days that everyone has been asking.
Sent from my SPH-L720 using xda app-developers app
Hello everyone, I just get ATT galaxy S4, It is so fancy, but ATT's craps sucks.
Does ATT S4's bootloader already been hack by XDAs?
If so, how to unlock it?
I just have the TWRP installed in my ATT galaxy S4, could I flash customized ROM and customized kernel now? Or I have to wait until the bootloader is unlock?
puamystery said:
Hello everyone, I just get ATT galaxy S4, It is so fancy, but ATT's craps sucks.
Does ATT S4's bootloader already been hack by XDAs?
If so, how to unlock it?
I just have the TWRP installed in my ATT galaxy S4, could I flash customized ROM and customized kernel now? Or I have to wait until the bootloader is unlock?
Click to expand...
Click to collapse
you should search or look in the developers section
Dude you didn't even try to look in the other forums
Sent from my SAMSUNG-SGH-I337 using xda premium
Search is your friend.
Sent from my GT-N7100
I highly suggest you read...read...and read again
To start you off in the right direction though, read up on Loki as that is our bootloader bypass method...basically anything that has been lokid can be flashed...
But seriously read!!! Don't want to waste a headache and trouble shooting on a soft brick
Sent from my HTC PH39100 using Tapatalk 2
go here http://forum.xda-developers.com/showthread.php?t=2297900
sent from xda app
The Loki thing still has me confused and curious what folks think... I've been through many of flashes and had good and bad issues over the years but unsure how I feel about flashing up a ATT S4. I've been leaning towards getting a Tmobile S4 with a unlocked bootloader and getting that unlocked since I feel like it will be a bit more bulletproof. Is that paranoia or is Loki close enough to a unlocked bootloader that I can basically do everything with as little risk as would be expected with normal device flashing?
puamystery said:
Hello everyone, I just get ATT galaxy S4, It is so fancy, but ATT's craps sucks.
Does ATT S4's bootloader already been hack by XDAs?
If so, how to unlock it?
I just have the TWRP installed in my ATT galaxy S4, could I flash customized ROM and customized kernel now? Or I have to wait until the bootloader is unlock?
Click to expand...
Click to collapse
THIS INFO IS EVERYWHERE! READ MAN. useless thread here serious.
hey there bud, sorry everyone feels the need to repeatedly tell you to search instead of ending the thread with an explanation. im also sorry everyone else feels like this information is readily available, when its the furthest from that. you will require some digging and deduction skills to acquire all the information needed to fully utilize the loki function.
Since att took it upon themselves to lock the bootloader, the kernel has to be properly provisioned before it will allow it to boot (if the kernel is not set up correctly, you will receive an error about unapproved software on the device and will have to restore sans odin....yuck), so our awesome drjbliss and the infamous adamoutlers have provided a tool called "loki" which will allow bypassing of the locked bootloader and allow us to run the custom firmware.
please ensure that whatever ROM you are running has been previously provisioned with loki, or you are flashing a custom kernel that has loki baked in. Alternatively, there is an auto loki tool floating around called "loki doki" that can be flashed after any ROM to pre-loki it before boot.
You can PM me with any specific questions, and all you trolls should learn to help instead of complaining. In the amount of posts it took to complain about the OP not searching, it would have only taken one post to clarify and then this thread would have simply got buried.
---------- Post added at 06:11 AM ---------- Previous post was at 06:09 AM ----------
Screwbal said:
The Loki thing still has me confused and curious what folks think... I've been through many of flashes and had good and bad issues over the years but unsure how I feel about flashing up a ATT S4. I've been leaning towards getting a Tmobile S4 with a unlocked bootloader and getting that unlocked since I feel like it will be a bit more bulletproof. Is that paranoia or is Loki close enough to a unlocked bootloader that I can basically do everything with as little risk as would be expected with normal device flashing?
Click to expand...
Click to collapse
Loki is close enough to an unlocked bootloader, no worries my friend. Flash away and enjoy!
So, if my phone is unlocked and rooted, do I still need to unlock the bootloader?
ShowMeMo said:
So, if my phone is unlocked and rooted, do I still need to unlock the bootloader?
Click to expand...
Click to collapse
What? You can't unlock the bootloader. The i337 never had and never will have a bootloader that can be unlocked
Sent from my Nexus 5 using XDA Free mobile app
Lol jd
Bored and just browsing my old S4 threads and see you still get a post in a 7 month old thread about bootloaders which was already answered. [emoji19]
Sent from my iPhone 6 Plus using Tapatalk
rugmankc said:
Lol jd
Bored and just browsing my old S4 threads and see you still get a post in a 7 month old thread about bootloaders which was already answered. [emoji19]
Sent from my iPhone 6 Plus using Tapatalk
Click to expand...
Click to collapse
Some things never change. How have you been?. The iPhone still working?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Some things never change. How have you been?. The iPhone still working?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Been doing fine jd, thanks. Hope you are too.
Yes, I really like it. Not gonna Jailbreak, but my bank just started accepting Apple Pay. So, going to play with it. Something for an old man to have fun with.
It's just picking up steam as far as number of merchants, so ordered and will mess with the LoopPay FOB where AP isn't used yet. A year ago I would have sworn I would never use this techy stuff for banking. Must be getting soft.
The Verizon Note 3 variant N900V has had it's bootloader bypassed by @Hashcode and custom recovery has now been achieved on that device. I talked to @bajasur who is running their bounty thread and he believes that the same safestrap method could possibly be used on the N900A (our version). If @Hashcode can get this to work on the N900A I am sure development will move quickly so get over to our bounty thread and make your bounty pledges now!!! http://forum.xda-developers.com/showthread.php?t=2493369
See @bajasur's N900V Bounty Thread here...
http://forum.xda-developers.com/showthread.php?t=2473918
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Awesome!
Sent from my SAMSUNG-SM-N900A using Tapatalk
slidesear said:
Awesome!
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Definitely great news!!!
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I don't mean to be a downer, but I'm still on the fence whether I can get this working on the AT&T variant.
So let's hold off on any specific donations. :/
Fingers crossed! this would be great news!!!
Hashcode said:
I don't mean to be a downer, but I'm still on the fence whether I can get this working on the AT&T variant.
So let's hold off on any specific donations. :/
Click to expand...
Click to collapse
Pledges....meant pledges. Will update the OP...sorry @Hashcode.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
That would be pretty sweet
Sent from my SAMSUNG-SM-N900A using Tapatalk
Does this trip knox
Sent from my SM-N900W8 using Tapatalk
Canadoc said:
Does this trip knox
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
At this point we will just have to wait and see what happens. I would imagine it doesn't but since it is currently being worked on and not confirmed we will have to just be patient...which I clearly wasn't with this thread.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Isn't this the same thing that happened with the s4? Bootloader exploited on verizon variant, didnt know if it would work for anyone else and it did?
Sent from my VS980 4G using Tapatalk
MrPlNK said:
Isn't this the same thing that happened with the s4? Bootloader exploited on verizon variant, didnt know if it would work for anyone else and it did?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
The difference is ATT in addition to a locked bootloader made SELinux Enforcing. The VZW has permissive from what I've read.
mircury said:
The difference is ATT in addition to a locked bootloader made SELinux Enforcing. The VZW has permissive from what I've read.
Click to expand...
Click to collapse
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
kennonk said:
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
Click to expand...
Click to collapse
Normally it doesn't have anything to do with the bootloader but in this case since we can't crack or modify the bootloader we have to hijack the real /system into loading a recovery on a special partition along with a fake /system located on the internal sdcard. Whether or not SELinux enforcement policies prevent this or causes problems later if it does boot, we don't know yet. What it does do for sure is make it more difficult.
Same
kennonk said:
I am probably completely wrong as Android is a different beast than regular Linux but, in the Linux OS world SELinux has little to do with the bootloader. It is a set of modules that load once the OS begins to boot up as part of the kernel in runlevel 1. So by the time the SELinux modules are loading you are already "booted". I hope this is the case for Android as well as I am past my 14 days on this phone and love the hardware I just would really like to be able to run some custom kernels and load AOSP based roms if I choose to. This is certainly the last phone I will be buying from AT&T regardless, so disappointed.
Click to expand...
Click to collapse
Same here. I hate that AT&T is doing this. It's crazy how the tables have turned, as it used to be (As with the S4) we would get a way to flash a recovery before the VZW variant, but now it seems that has changed. Is the Knox option only on our variant or is it on VZW too?
I got super excited when I first saw this but then depressed when I found out that it hasn't fully been achieved... what is the difference from the way that the s4 was cracked? It had knox too didn't it?
Sent from my SAMSUNG-SM-N900A using Tapatalk HD
I have verizon and no it doesn't trip knox
tropazr said:
The Verizon Note 3 variant N900V has had it's bootloader bypassed by @Hashcode and custom recovery has now been achieved on that device. I talked to @bajasur who is running their bounty thread and he believes that the same safestrap method could possibly be used on the N900A (our version). If @Hashcode can get this to work on the N900A I am sure development will move quickly so get over to our bounty thread and make your bounty pledges now!!! http://forum.xda-developers.com/showthread.php?t=2493369
See @bajasur's N900V Bounty Thread here...
http://forum.xda-developers.com/showthread.php?t=2473918
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
SunnyOK said:
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=48555170
We have Safestrap now. Read up on it!
Sent from my SAMSUNG-SM-N900A using Tapatalk
SunnyOK said:
Any progress on unlocking bootloader of N900A?
We highly expect this.
Thank you.
Click to expand...
Click to collapse
Have you not looked in the development forums?
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Agent said:
Have you not looked in the development forums?
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Click to expand...
Click to collapse
Unfortunately the bootloader is still locked and hasn't been bypassed. What safestrap does is hijack the boot process once it reaches the /system partition. That is after the bootloader. It then runs a modified recovery. This is why you can't run custom kernels on it yet. The /boot partition is still protected. Don't get me wrong though it's a huge step in the right direction.
The past pretty much says it all, is the a Cyanogen 11 ROM I can use for my AT&T S5 with safestrap maybe?
Simon Hammers said:
The past pretty much says it all, is the a Cyanogen 11 ROM I can use for my AT&T S5 with safestrap maybe?
Click to expand...
Click to collapse
There are no roms for 900a afaik.
Lock boot loader?
from SM-G900F / SM-N9005
CM/AOSP roms will not be working on the ATT variant until the bootloader is unlocked. For now you only get to use TW roms via SafeStrap
androidfilesharing said:
CM/AOSP roms will not be working on the ATT variant until the bootloader is unlocked. For now you only get to use TW roms via SafeStrap
Click to expand...
Click to collapse
You say until the bootloader is unlocked. Do you truly believe that Samsung and AT&T are gonna get off their money making high horse and actually allow an unlocked bootloader? That's why the "developer version" is there. I hate this crap. I have rooted and flashed roms for every damn phone I've ever owned. Sigh..
Bl33dingskullz said:
You say until the bootloader is unlocked. Do you truly bla bla bla rant
Click to expand...
Click to collapse
He's talking about the community. Until someone in the android scene unlocks it. It's not up to Samsung, it's up to AT&T.
Good day all,
I noticed several cluttered threads in Q&A that are becoming more of a discussion than question and answer format.
I wanted to make this thread as a one stop shop for all things Root and Bootloader related for the G-930T (Tmobile Galaxy Note 7).
Please discuss root, bootloader and work with each other in here.
Please do not discuss the bounty in here, and do not clutter the bounty thread with casual conversation about root.
Cheers,
Baja
Sent from my SM-N930T using XDA-Developers mobile app
Well we know the Bootloader is locked and can only be unlocked by Samsung( That's not gonna happen).
Based on what happened and is continuing to happen with the S7 there is a possibility of achieving Root on the N7(ENG) which I will not be a guinea pig and try. I'm sure others will if and when it's available.
SBERG117 said:
Well we know the Bootloader is locked and can only be unlocked by Samsung( That's not gonna happen).
Based on what happened and is continuing to happen with the S7 there is a possibility of achieving Root on the N7(ENG) which I will not be a guinea pig and try. I'm sure others will if and when it's available.
Click to expand...
Click to collapse
I second this. Just wish we could keep samsung pay after root. Not gonna happen but wishful thinking.
Sent from my SM-N910T3 using Tapatalk
Just want to note that you may not want to take any updates if you plan on rooting in the future (if an exploit is available).
dirtymindedx said:
I second this. Just wish we could keep samsung pay after root. Not gonna happen but wishful thinking.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Not true on my Nexus 6 we could not use Android pay with root. But someone came up with a walk around systemless root and it worked.
Sent from my SM-N930T using Tapatalk
jason504 said:
Not true on my Nexus 6 we could not use Android pay with root. But someone came up with a walk around systemless root and it worked.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
he said Samsung pay...two separate paying system
Chord_Hugo87 said:
he said Samsung pay...two separate paying system
Click to expand...
Click to collapse
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
jason504 said:
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
not possible if you trip knox and in order to get root you need to trip knox.
jason504 said:
No I know what he said but if there can be a walk around for one (should) be able to do one for the other.
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
One of them is from Google and doesn't care about Knoxx and the other is from Samsung and does care about Knoxx. Two completely different things. The Samsung Pay not working after Knoxx is tripped has been going on for a year as of tomorrow. The systemless root that doesn't trip Knoxx is one thing but as soon as you start flashing, kiss Samsung Pay goodbye.
Yep, and worst of all. Once it's tripped, Samsung pay will never work again on that device
Sent from my SM-N930T using XDA-Developers mobile app
Luckily for me, if root becomes available its a no-brainer. Samsung pay doesn't support my bank, and I won't have a credit card. Even if Samsung Pay would work for me, it would still be an easy choice to have root instead. I would like to play around with altering the speaker volume, deleting bloatware, making tweaks, ad blocking, etc.
Did anyone ever get the files that Beans asked for over to him?
Why can't those of us with t variants just flash the unlocked w8 bootloader? Seems like we've been left an out? Yes?
Sent from my SM-N920T using Tapatalk
Rx8Driver said:
Why can't those of us with t variants just flash the unlocked w8 bootloader? Seems like we've been left an out? Yes?
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
In order for you to flash anything to any bootloader, it needs to be unlocked. With it locked Odin says it can't. So till the note 7 gets unlocked (in time) we have to wait. Phone only few days old, be work around soon.
drum747 said:
Did anyone ever get the files that Beans asked for over to him?
Click to expand...
Click to collapse
Good question
@BeansTown106 did you ever get a Tar?
Sent from my SM-N930T using XDA-Developers mobile app
It appears this guy is in the process of getting the stock firmware uploaded
http://forum.xda-developers.com/showthread.php?t=3444003
Sent from my SM-N930T using XDA-Developers mobile app
ethanscooter said:
Just want to note that you may not want to take any updates if you plan on rooting in the future (if an exploit is available).
Click to expand...
Click to collapse
That is true. Android 7 Nougat will have more security features that Samsung is going to take advantage of with the Galaxy Note 7. That may make unlocking bootloader and rooting even more difficult.
-
It looks like the sprint guys have obtained an engineering bootloader/kernel. Someone may be able to do something with this for us..
Sent from my SM-N930T using XDA-Developers mobile app
I got the stock n930t boot.img but im wondering is how would i go by making a kernel "engboot". I also removed dm-verity but that didn't work. All i get is a failed message through odin. Another testing i have done is I even just modified one simple thing in the stock kernel say in default.prop ro.secure=1 to =0 and i still get a failed messsge. Once i flashed the stock unmodified version of the kernel i would get a success message and works which means any modification to the kernel will cause it to fail i just have to see what in the kernel checks for md5 changes or it may be something else if more devs can help together, then we can get this working.
jovy23 said:
I got the stock n930t boot.img but im wondering is how would i go by making a kernel "engboot". I also removed dm-verity but that didn't work. All i get is a failed message through odin. Another testing i have done is I even just modified one simple thing in the stock kernel say in default.prop ro.secure=1 to =0 and i still get a failed messsge. Once i flashed the stock unmodified version of the kernel i would get a success message and works which means any modification to the kernel will cause it to fail i just have to see what in the kernel checks for md5 changes or it may be something else if more devs can help together, then we can get this working.
Click to expand...
Click to collapse
Bro, please stop trying. This is obviously far above your skill level.
1. There is no way to convert a kernel to an "engboot."
2. The bootloader is LOCKED, so anything you do to the kernel's ramdisk will obviously not work because the whole point of dm-verity and a locked bootloader, among other things, is to stop the modification of system images, including the kernel ramdisk. Surely you didn't think it would be as easy as unpacking the boot.img, changing the ro.secure value from 1 to 0, then repacking..... did you?
3. The kernel doesn't "check" for anything MD5 related.
4. The bootloader is rejecting your changes, not the kernel.
5. Nothing you do to the boot.img, no matter how many devs you have, will do any good.
Hang tight, guys. We're trying everything we can.