When I first received my S5, I believe I saw the option to unlock the bootloader via the settings menu. I thought it was a build that the device came with on either 5.0 or 4.4.2. I was wondering because I was wanting to download to it to see if the option was still available and if it still supported it's desired function. I just want an unlocked bootloader to be honest
Playb3yond said:
When I first received my S5, I believe I saw the option to unlock the bootloader via the settings menu. I thought it was a build that the device came with on either 5.0 or 4.4.2. I was wondering because I was wanting to download to it to see if the option was still available and if it still supported it's desired function. I just want an unlocked bootloader to be honest
Click to expand...
Click to collapse
The T-Mobile version of the S5 (SM-G900T) comes with an unlocked bootloader. I point this out, since you posted this on the T-Mobile forum.
Do you have a phone other than a SM-G900T?
Rob
rlichtefeld said:
The T-Mobile version of the S5 (SM-G900T) comes with an unlocked bootloader. I point this out, since you posted this on the T-Mobile forum.
Do you have a phone other than a SM-G900T?
Rob
Click to expand...
Click to collapse
I do, SM-G900T, but I'm not so certain my bootloader is unlocked, if it was, I would have the unlock symbol on the first boot splash screen.
Playb3yond said:
I do, SM-G900T, but I'm not so certain my bootloader is unlocked, if it was, I would have the unlock symbol on the first boot splash screen.
Click to expand...
Click to collapse
It comes with an unlocked bootloader, if you're asking for the purpose of flashing a custom recovery or kernel you're all set you can do so automatically
thisisapoorusernamechoice said:
It comes with an unlocked bootloader, if you're asking for the purpose of flashing a custom recovery or kernel you're all set you can do so automatically
Click to expand...
Click to collapse
Okay, so that explains how you can flash a custom recovery / kernel without the need to root first. Makes sense.
Related
Hey all,
I'm fairly new to unlocking/rooting (I'm from the simple iPhone jailbreak world).
I have my Atrix 4G rooted with no issues and ClockworkMod installed... that was the easy part it seems.
Where I am struggling is to figure out IF I can unlock my Atrix 4G and if it is safe to do.
I am running Android 2.3.6 on the Bell network. I see a bunch on unlocks for bootloader 2.3.4 and am confisued if that bootloader version has any relation to the android version? How can I figure out what bootloader I have? Would it also be 2.3.6?
If it is indeed 2.3.6, is it possible to unlock, I see no specific unlocks for that version.
Thanks,
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
Sorry should have been a little more clear, I have installed ROM Manager and choose the CWM install, but I cannot boot into it, I get a boot error 2 (I think). Sorry phone is at home now so I can't recall exact error will post later.
I got phone 6 month ago, was used phone. I am fairly certain its not unlocked because I cannot boot with CWM, hence cannot install custom ROM.
Thanks for the reply.
Random Canadian said:
You cant install a different recovery with out being unlocked. so if you can boot into CWM then your phone is already unlocked.
Where did you get the phone? was it new?
Its possible if its used that it was already unlocked and someone RSD back to stock for sale purpose, if its new and you havent unlocked yet then you dont have CWM installed.
Click to expand...
Click to collapse
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
cerps said:
You don't need to be unlocked to have CWM on your Atrix. I had it on at least 1.83 if not the original stock firmware. I know it was possible with only root on 1.83 because that was what I was running up until a month ago and I had CWM on it with a locked bootloader.
Click to expand...
Click to collapse
Locked or it just didnt say unlocked at the top? two very different things.
avalanche333 said:
Right, my phone is rooted so I have CWM, just can't boot it. My understanding is because I need to unlock, but I don't know how to unlock because I don't know how to figure out what bootloader I have.
Click to expand...
Click to collapse
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
Yes I see what your saying, but I am saying that I cannot run CWM. I can only install onto my SD card. But the boot in recovery does not work (ie it will not run CWM). I'll post the error little later tonight when I try at it again.
I realize there is lots of info on unlocking bootloader and I am not concerned about doing the unlock, once I find a way to verify my bootloader version. Ive seen a few posts warning that bootloader must be v 2.3.4 or you can brick the phone.
So I guess ultimately my question is, how can I figure out my bootloader version? Have not seem this answers after some googling.
http://forum.xda-developers.com/showthread.php?t=1136261
Read that and your version will be in settings and then about phone. although I do believe that 234 and 236 unlock via the same method.
If you are going to install Custom roms CM7/9/10 or a blur based then you dont need to even worry about root. otherwise there are instructions in that thread to root that SBF
Random Canadian said:
Locked or it just didnt say unlocked at the top? two very different things.
dur im pretty sure that unlocking the boot loader allows unsigned code to run at boot, I could be wrong but I think you two are out to lunch on installing CWM with just root.
That or you can install it but you cant run it because the boot loader wont allow something with out motorolas signature to execute. making the point of if it is or is not, installed, a moot one. Aside from the fact you no longer have any sort of a functional recovery mode.
There is a LOT of info on how to unlock the bootloader and its not exactly hidden. I dont know if its even still done with RSD but that would be a place to start as that is how I did mine in sept of last year.
Click to expand...
Click to collapse
I'm positive it was locked, running 1.83, and had CWM on it. I bought the phone at an AT&T store myself. I rooted it and put CWM on it. The early version of CWM for the Atrix only was accessible by turning the phone on while plugged into the wall charger that came with the phone.
I was wondering if the S6 on Vodafone in the UK came with a locked bootloader, and if so how difficult was it to unlock? I have an S7 Edge on pre-order, and presume that would come locked too if the S6 did. I can't live without root. Cheers.
No one has an S6 Edge on Vodafone?
Beefheart said:
I was wondering if the S6 on Vodafone in the UK came with a locked bootloader, and if so how difficult was it to unlock? I have an S7 Edge on pre-order, and presume that would come locked too if the S6 did. I can't live without root. Cheers.
Click to expand...
Click to collapse
Seems so, as I have had the same problem by installing MM 6.0.1 firmware with the UK csc code VOD (appearing as BTU on phone). The bootloader wouldn't let me flash TWRP through ODIN (sorry, could flash, but not boot into TWRP, stuck on bootloader).
So i took the provided MM 6.0.1. bootloader from Carotix CarHDRom, flashed it together with at the same place provided TWRP for
MM (the old 2.8.7.0/2.8.7.1 or even new TWRP 3.0 provided on the homepage of TWRP.me , won't work on MM) throught ODIN.
Within TWRP flashed hybridmax's S5E-AELKernel_MM...kernel 1.5 and superSU beta 2.67 (previosly stored/copied to the mobile device) and rebooted - rooted and all working fine.
Take a look at : http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519
coco722 said:
Seems so, as I have had the same problem by installing MM 6.0.1 firmware with the UK csc code VOD (appearing as BTU on phone). The bootloader wouldn't let me flash TWRP through ODIN (sorry, could flash, but not boot into TWRP, stuck on bootloader).
So i took the provided MM 6.0.1. bootloader from Carotix CarHDRom, flashed it together with at the same place provided TWRP for
MM (the old 2.8.7.0/2.8.7.1 or even new TWRP 3.0 provided on the homepage of TWRP.me , won't work on MM) throught ODIN.
Within TWRP flashed hybridmax's S5E-AELKernel_MM...kernel 1.5 and superSU beta 2.67 (previosly stored/copied to the mobile device) and rebooted - rooted and all working fine.
Take a look at : http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519
Click to expand...
Click to collapse
Did you have the OEM Unlock toggle in dev options?
Beefheart said:
Did you have the OEM Unlock toggle in dev options?
Click to expand...
Click to collapse
Do not know if or not.
Just flashed first the original VOD 6.0.1 fw and then tried to have a working TWRP recovery, but could't boot into TWRP recover, the original bootloader did not let me... this for, bootloader and twrp from carotix (and eventually his provided kernel and/or rom) , and everything goes fine.
coco722 said:
Do not know if or not.
Just flashed first the original VOD 6.0.1 fw and then tried to have a working TWRP recovery, but could't boot into TWRP recover, the original bootloader did not let me... this for, bootloader and twrp from carotix (and eventually his provided kernel and/or rom) , and everything goes fine.
Click to expand...
Click to collapse
My understanding of a locked bootloader is that you can't flash anything that isn't official, including a replacement bootloader, which you indicate you did successfully. Otherwise Verizon Samsung customers would simply flash a new bootloader over their locked one. Ever TWRP wouldn't have flashed, it would have kicked out an error in Odin as you made the attempt because the bootloader wouldn't have allowed it. It sounds like your attempt at flashing it finished successfully, but just wouldn't boot into it. I'm wondering if this was caused by something other than the bootloader being locked.
Beefheart said:
My understanding of a locked bootloader is that you can't flash anything that isn't official, including a replacement bootloader, which you indicate you did successfully. Otherwise Verizon Samsung customers would simply flash a new bootloader over their locked one. Ever TWRP wouldn't have flashed, it would have kicked out an error in Odin as you made the attempt because the bootloader wouldn't have allowed it. It sounds like your attempt at flashing it finished successfully, but just wouldn't boot into it. I'm wondering if this was caused by something other than the bootloader being locked.
Click to expand...
Click to collapse
All possible. However, sometimes we'll just have to give it a try, by using the information and software available. I do have to mention, that my mobile is/was provider-free (not locked to a specific provider). But even a locked mobile can be handeld to get
in free and unlocked. In such case, this should be done first and after that the upgrade to rooted MM and ROM, etc.
No worries, cheers for the reply. I'll wait until I receive it then simply return it and cancel the contract if it's locked.
Hi, i had the same problem. I flashed TWRP, but i could not boot to TWRP. I found that I also have locked bootloader. No OEM Unlock toggle in dev options.
Login on this site
https://findmymobile.samsung.com/login.do
and try Disable Reactivation lock if you can.
vrzy007 said:
Hi, i had the same problem. I flashed TWRP, but i could not boot to TWRP. I found that I also have locked bootloader. No OEM Unlock toggle in dev options.
Login on this site
https://findmymobile.samsung.com/login.do
and try Disable Reactivation lock if you can.
Click to expand...
Click to collapse
I've not received my phone yet, but this doesn't look good. Were you able to disable the reactivation lock on your S6? Or, alternatively, like coco722, were you able to simply overwrite the bootloader? I'm not concerned with Knox or Vodafone's warranty, as long as I'm able to overcome the locked bootloader and root.
My device: Verizon Samsung Galaxy S4 (SCH-I545),Android version 5.0.1, Baseband version I545VRUGOF1, Rooted with Kingroot
I've spent some time trying to find out whether I can get Cyanogen on this phone, and it seems like the answer is no, but I think I might have an unlocked bootloader for some reason. Whenever I start the phone, it shows an unlocked padlock and the text 'custom'. I've also booted into Odin mode. Does this mean that my bootloader is unlocked? If it is, does this mean that I can install a custom recovery and then a rom such as Cyanogenmod 13?
No, sorry. Only 4.2.2 MDK was unlocked, the custom start screen appears because you rooted your phone and you have modified something at system (like debloat or changed build.prop)
On the latest t mobile software, dev mode enabled, but I dont see "OEM UNLOCK" anywhere...does anyone have that option on their note 8?
thanks
wase4711 said:
On the latest t mobile software, dev mode enabled, but I dont see "OEM UNLOCK" anywhere...does anyone have that option on their note 8?
thanks
Click to expand...
Click to collapse
I think you use that TMO device unlock app.
I thought that was just for carrier unlock, NOT OEM unlock...have you used that app?
thanks
wase4711 said:
I thought that was just for carrier unlock, NOT OEM unlock...have you used that app?
thanks
Click to expand...
Click to collapse
No, I disabled it. Been with TMO too long, I'm not going anywhere and neither are they. Thanks for teaching me the difference, lol! This bootloader is locked.
there are a few different "locks" to deal with on this phone; the bootloader, which is currently locked, carrier lock, meaning you are locked to tmobile, and the OEM unlock, which allows you to flash roms, both stock and custom, assuming you have an unlocked boot-loader
On most other phones, in the developer options, there is a OEM Unlock entry you activate if you plan on flashing anything...
wase4711 said:
there are a few different "locks" to deal with on this phone; the bootloader, which is currently locked, carrier lock, meaning you are locked to tmobile, and the OEM unlock, which allows you to flash roms, both stock and custom, assuming you have an unlocked boot-loader
On most other phones, in the developer options, there is a OEM Unlock entry you activate if you plan on flashing anything...
Click to expand...
Click to collapse
The OEM Unlock option doesn't appear until 7 days after the device was first booted on the Exynos version. That might not be the case with your version because the bootloader is locked so the OEM Unlock toggle is redundant.
Have a read through this thread:
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
I've had many phones with locked bootloaders in the past where the OEM unlock appeared in the dev options, so unless this is something new with the note 8. im not sure why its not there..
wase4711 said:
I've had many phones with locked bootloaders in the past where the OEM unlock appeared in the dev options, so unless this is something new with the note 8. im not sure why its not there..
Click to expand...
Click to collapse
All the OEM unlock toggle does is allow you to flash a custom recovery so you can then flash custom ROMs only if the the bootloader is unlocked. If the bootloader is locked like on US snapdragon N8s having the toggle is pointless.
If you check out the thread linked above you'll see that a bunch of people with exynos versions that do have unlocked boot loaders are missing the toggle which later appears & disappears. No one knows why yet, all just speculation.
The N8 is the first to have this happen. What a big headache. Hopefully they figure it out. I'm one of the lucky with an exynos N8 without that issue.
yeah, its not a big deal, especially since there is no way to unlock this bootloader at this point anyways...weird that it comes on and off on the Exynos though..
Torquemada288 said:
The OEM Unlock option doesn't appear until 7 days after the device was first booted on the Exynos version. That might not be the case with your version because the bootloader is locked so the OEM Unlock toggle is redundant.
Have a read through this thread:
https://forum.xda-developers.com/galaxy-note-8/help/info-note-8-exynos-n950f-fd-oem-unlock-t3673140
Click to expand...
Click to collapse
Correct, for our t mobile USA ones, we will never get that OEM Unlock option in any amount of days.
Well if we can. Get root we can oem toggle
smiley45 said:
Well if we can. Get root we can oem toggle
Click to expand...
Click to collapse
We already have a root, it just wasn't released yet and it seems to be the same as S8, so with similar disadvantages. Expect to be out any day now.
smiley45 said:
Well if we can. Get root we can oem toggle
Click to expand...
Click to collapse
Even if you get the OEM unlock toggle to appear it doesn't mean anything. If you have a locked bootloader the OEM unlock won't unlock it. OEM unlock is just a safety switch.
shouren04 said:
Even if you get the OEM unlock toggle to appear it doesn't mean anything. If you have a locked bootloader the OEM unlock won't unlock it. OEM unlock is just a safety switch.
Click to expand...
Click to collapse
Yes that maybe so.. but I will feel better when I add that option to my note 8... I'm just waiting on root and it on form there
Sent from my SM-N950U1 using Tapatalk
Oem needs to be unlocked before u can us cf autoroot or any other means of root I have j7 metro no oem unlock option tried to use Odin and cf auto root it failed because the bootloader is locked and can't be unlocked. I know this is for the n8 but I seem to be suffering from the same problem.
Lost without root
XxdeadhatexX said:
Oem needs to be unlocked before u can us cf autoroot or any other means of root I have j7 metro no oem unlock option tried to use Odin and cf auto root it failed because the bootloader is locked and can't be unlocked. I know this is for the n8 but I seem to be suffering from the same problem.
Lost without root
Click to expand...
Click to collapse
Does having an engineering bootloader help?
How do I test if the bootloader is unlocked?
Sent from my SM-G892U using Tapatalk
reukiodo said:
Does having an engineering bootloader help?
How do I test if the bootloader is unlocked?
Sent from my SM-G892U using Tapatalk
Click to expand...
Click to collapse
Its not plain and simple.
sent from my Pixel 2 XL or Note FE
so i cant root or put twrp on my j727U ? SEEN PEOPLE DO IT WITH J727p so why not the U ? no oem toggle on a galaxy how is this, should all come together and never buy phones from a company that goes against what customers want.
so i cant root or put twrp recovery on my galaxy j727U ? ? how has a phone tech not beat this by now even without oem toggle , it should still be beat by now.. this is why i liked htc cause they unlock bootloader for you and allow it on there own page, anyone wanna trade a htc for a new galaxy j7 ?
lol i think this thread needs to be closed
Yes there is an OEM unlock option. I know because I discovered It! Simply flash the K2 combination file, when factory binary loads go into the left hand screen, with apps. Click on the settings icon, then enable dev options the usual way. OEM unlock should be there. You may need to toggle it off and on a few times before you get the popup security message.
It makes a change in the system as it should. If you do a factory reset, then reload the factory binary, you'll see that Dev Options are already enabled (saved from last time you unlocked) AND OEM will already be toggled. This means that the unlock sticks!
So there you go. It even changes the OEM line in the .prop.... that being said...
DO NOT TRY TO FLASH TWRP AFTER DOING THIS!!!
(I already tried, the secure boot still is in effect, and you'll have a softbrick until you can re Odin your recovery. )
The OEM unlock may be one part of this, but there's more. Hopefully we are making progress toward the goal of a bootloader unlock!
I have access to an engineering bootloader for the Tmo Note8 and I would like to know how to test if it is unlocked.
Is there a specific process to determine if the bootloader is locked? Are there steps to permanently unlock the bootloader from an engineering bootloader?
I've searched all the Note8 forums and haven't found any answers.
Sent from my SM-G892U using Tapatalk
reukiodo said:
I have access to an engineering bootloader for the Tmo Note8 and I would like to know how to test if it is unlocked.
Is there a specific process to determine if the bootloader is locked? Are there steps to permanently unlock the bootloader from an engineering bootloader?
I've searched all the Note8 forums and haven't found any answers.
Click to expand...
Click to collapse
Flashing it and then checking if you can unlock it would be how to go about it. Except you can't flash unsigned images without unlocking so it's a catch 22 really. And it may just brick your phone even if you flashed it successfully. No way of knowing if that bootloader will even boot your device or play nice with the other partitions.
Gizmoe said:
Flashing it and then checking if you can unlock it would be how to go about it. Except you can't flash unsigned images without unlocking so it's a catch 22 really. And it may just brick your phone even if you flashed it successfully. No way of knowing if that bootloader will even boot your device or play nice with the other partitions.
Click to expand...
Click to collapse
The eng bootloader is signed, so there is no problem flashing the eng bootloader. I just do not know how to test if it is unlocked, as I can't find a recovery image to flash, and I do not know how to create one myself.
Sent from my SM-G892U using Tapatalk
reukiodo said:
The eng bootloader is signed, so there is no problem flashing the eng bootloader. I just do not know how to test if it is unlocked, as I can't find a recovery image to flash, and I do not know how to create one myself.
Sent from my SM-G892U using Tapatalk
Click to expand...
Click to collapse
probably just the combo files that are used for samfail imo. if you want to upload and have me check them lmk but more then likely all you have is the combo firmware we have been using since day one
Team DevDigitel said:
probably just the combo files that are used for samfail imo. if you want to upload and have me check them lmk but more then likely all you have is the combo firmware we have been using since day one
Click to expand...
Click to collapse
https://drive.google.com/file/d/1PIVZs-uB8kKb9YbY_fAcYJCGIfdb27W5/view?usp=drivesdk
This might only work on the T-Mobile version.
reukiodo said:
https://drive.google.com/file/d/1PIVZs-uB8kKb9YbY_fAcYJCGIfdb27W5/view?uk
This might only work on the T-Mobile version.
Click to expand...
Click to collapse
Do you have the boot.img that matches this?
Unable to check the rest without as it won't boot the combo img.
Yes it is a eng img.
We are on multi csc devices so all are same for flashing sake, as long as it's not the exynos.
Please remove the public link and we can move to pm/telegram and speak further
Team DevDigitel said:
Do you have the boot.img that matches this?
Unable to check the rest without as it won't boot the combo img.
Yes it is a eng img.
We are on multi csc devices so all are same for flashing sake, as long as it's not the exynos.
Please remove the public link and we can move to pm/telegram and speak further
Click to expand...
Click to collapse
I disabled the link, though not sure why I should? I haven't gotten telegram yet. I just want to know if it is unlocked for flashing custom recovery such as TWRP.
reukiodo said:
I disabled the link, though not sure why I should? I haven't gotten telegram yet. I just want to know if it is unlocked for flashing custom recovery such as TWRP.
Click to expand...
Click to collapse
No one has compiled twrp for snapdragon because we dont have a unlocked bl. Removing link is primarily to avoid people flashing this or reposting it with incorrect info and causing confusion.
If I can get the boot.img as well that is compiled for this bootloader I can get a running system and see if it can be unlocked. Otherwise without it there's no way to determine some of the important factors here. Just flashing against device to test is quite risky.
The bl is compatible with all snapdragon and does install correctly but it won't boot with the combo imgs we use for samfail or a stock img.
Link is still active fyi and I've sent you a pm with telegram info. It's a group for us and a few other devs that can work with us to get things sorted.
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
DroidisLINUX said:
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
Click to expand...
Click to collapse
I'm wondering if after flashing this engineering bootloader we can root phone just by simply using command prompt and sideloading root files. Any ideas? I don't know enough to do this.
Sent from my [device_name] using XDA-Developers Legacy app
Eudeferrer said:
I'm wondering if after flashing this engineering bootloader we can root phone just by simply using command prompt and sideloading root files. Any ideas? I don't know enough to do this.
Click to expand...
Click to collapse
I don't believe so, until we can get it unlocked, when in download mode it says the boot loader is still locked and says system secure in red and official binaries but if we can get the boot loader to say unlocked then I believe it will probably be possible. At least it says eng boot loader and tells us it's locked and that means it can be unlocked it's just a matter of time until someone gets it unlocked now
I am glad I haven't updated to boot loader 3 now, this is bootloader 2 so if you go to oreo you won't be able to use this when and if it's unlocked
DroidisLINUX said:
I don't believe so, until we can get it unlocked, when in download mode it says the boot loader is still locked and says system secure in red and official binaries but if we can get the boot loader to say unlocked then I believe it will probably be possible. At least it says eng boot loader and tells us it's locked and that means it can be unlocked it's just a matter of time until someone gets it unlocked now
I am glad I haven't updated to boot loader 3 now, this is bootloader 2 so if you go to oreo you won't be able to use this when and if it's unlocked
Click to expand...
Click to collapse
Has anyone tried the same procedure/comands used to unlock the Pixel XL? Would they even work I this phone if it had this eng bootloader? I wish I knew enough about this stuff to try it out or even know if it would work.
Sent from my [device_name] using XDA-Developers Legacy app
DroidisLINUX said:
I used the engineering bootloader with Odin, after it flashed showed it as an eng boot loader not user, says Samsung official and is still locked. I booted with a binary .img booted and oem option from the settings was there, showed the same unlocked img on boot as samfail also. But I didn't do much other than check those things. I tried to load samfail system but it didn't load I figured as much seeing samfail boot.img is user-test not user-release and has custom binary but I don't know that much
I am wondering if we don't have to leave the eng boot loader on and oem toggled for a week like exyos versions before we can flash custom binary
Click to expand...
Click to collapse
you could test,
but if you look under the info on the boot up screen, secure boot is still set to : enabled
IE: each and every boot it checks for a modified boot.img and if found it fails secure check.
I never tested the oem unlock options etc, or waiting any time frame, just mostly seeing what we could use with it.
The phone wont boot a modified system as well. has to be unrooted stock system + stock boot.img to boot with the eng bootloader.
Unfortunately i havent heard anything back, was hoping we could get the boot.img that is ENG so we can boot the entire setup and go.