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.
Related
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.
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.
Hi,
Does anyone know how to relock the bootloader after I unlocked it and had a custom rom on it?
I want to use services like Google Pay without Magisk and it dosnt work with the bootloader unlocked.
I tried to switch the "OEM unlock" option in Developer option back off, but it looks like it is off, although below the switch it says: Bootloader alredy unlocked.
If i switch it, it'll just go trought the unlocking process as if the BL wasnt locked (Factory reset and BL still unlocked)
Im using the SM-G965F DualSIM bought in Germany (CSC is DBT) on CSG8 Firmware.
I unlocked the BL on CSE3 Firmware.
dzik_ said:
Hi,
Does anyone know how to relock the bootloader after I unlocked it and had a custom rom on it?
I want to use services like Google Pay without Magisk and it dosnt work with the bootloader unlocked.
I tried to switch the "OEM unlock" option in Developer option back off, but it looks like it is off, although below the switch it says: Bootloader alredy unlocked.
If i switch it, it'll just go trought the unlocking process as if the BL wasnt locked (Factory reset and BL still unlocked)
Im using the SM-G965F DualSIM bought in Germany (CSC is DBT) on CSG8 Firmware.
I unlocked the BL on CSE3 Firmware.
Click to expand...
Click to collapse
If you flashed custom recovery and afterwards custom ROM, KNOX is tripped so bootloader (OEM) is permanently unlocked. There is no way to bypass that.
A One-Way Street..
dzik_ said:
Hi,
Does anyone know how to relock the bootloader after I unlocked it and had a custom rom on it?
I want to use services like Google Pay without Magisk
Click to expand...
Click to collapse
melendi said:
If you flashed custom recovery and afterwards custom ROM, KNOX is tripped so bootloader (OEM) is permanently unlocked. There is no way to bypass that.
Click to expand...
Click to collapse
Co-Signed... You're Done.
There Is No Turning Back....
Let This Be A Lesson To Anyone That Reads This Thread:
You Need To Weigh Out If Rooting And Tripping Knox is worth loosing Samsung Pay & Google Pay. Even though there may be "Backdoors" to allow you to use Google Pay without Security...
But Why Would You Use Google Pay When Your Phone Is No Longer Secure??? and leave yourself Vulnerable to having your info violated?
Once You've Crossed The Line... You Have To Live With That Choice... No Matter How Unpalatable It Becomes..
Hi everyone, I've just got a G-900T running 5.1.1 yesterday. This phone is unlocked, but I am not sure what method did the former user use to unlock. I want to install another ROM (maybe 6.0.1 firmware or other custom ROM), but I am afraid that it will be carrier-locked again, can anyone confirm this for me? Thanks for the help.
To be locked again, you'll have to lock it from developer options, which is not available on AOSP ROMs, and hidden from Stock-based ones. You may consider yourself safe.
There are two types of locking - 1) carrier, and 2) Boot loader. To flash a custom ROM, the boot loader has to be unlocked. That would have been the case if it had a custom ROM installed when you bought it. But if it has a stock ROM, you will have to check the security lock level (About Device) to confirm that the security level is low enough to allow unlocking the boot loader. Otherwise, you may brick your phone.
outlaw0703 said:
Hi everyone, I've just got a G-900T running 5.1.1 yesterday. This phone is unlocked, but I am not sure what method did the former user use to unlock. I want to install another ROM (maybe 6.0.1 firmware or other custom ROM), but I am afraid that it will be carrier-locked again, can anyone confirm this for me? Thanks for the help.
Click to expand...
Click to collapse
I have the GLOBAL version of POCO X3 GT (chopin) 8GB/256GB and its a good device but the Google Dialer is making the whole phone unusable becuase of its Call Recording.
1) It does not have Automatic recording for all calls
2) Even after manually recording calls it takes ages to search for recorded files as there is no way to access them.
I do not want to root my phone for security reasons however I came across some posts which mention that the INDONESION firmware has MI Dialer & Contacts instead of Google which is enough incentive to void my warranty and try to change firmwares.
It has been a couple of years since I last played with custom roms, bootloader, fastboot flashing, etc. So I would appreciate if you guys can help me with a few questions:
1) Bootloader unlocking: Whats the best method for Poco X3 GT
2) Method to flash different region stock firmware
3) Is it safe to re-lock the bootloader after the new region firmware is flashed? or do I need to leave the bootloader unlocked?
1. use the official xiaomi bootloader unlock tool
2. Easy, just download the region fastboot rom you want and extract them. Flash via MiFlash -- pay attention to tick clean all in the corner of the screen if you don't want your device to be bricked
3. don't relock, if you lock the bootloader on other region firmware, you will be bricked
Longtn said:
1. use the official xiaomi bootloader unlock tool
2. Easy, just download the region fastboot rom you want and extract them. Flash via MiFlash -- pay attention to tick clean all in the corner of the screen if you don't want your device to be bricked
3. don't relock, if you lock the bootloader on other region firmware, you will be bricked
Click to expand...
Click to collapse
thanks
Worked like a charm.
however it seems that 5Ghz wifi is not working after the Indonesian firmware flash.
hi, i want to use indonesia rom too. are you still using it? would you recommend? thanks.
Longtn said:
3. don't relock, if you lock the bootloader on other region firmware, you will be bricked
Click to expand...
Click to collapse
Oddly enough, this was not my experience. I unlocked my bootloader, flashed the Indonesia version 13.0.5.0 fastboot image using MiFlash using the clean all option. Then after booting and setting up the phone, it offered the update for version 14.0.1.0. I let the phone complete the update. Once the update finished and the phone had booted up again I rebooted it to bootloader mode and ran the command fastboot oem lock. The phone went through a factory reset and then booted successfully to the new phone setup dialogue.
Also to mention that I did also experience problems with 5GHz WiFi with version 13.0.5.0 but these problems were resolved after the version 14.0.1.0 update.
abubasim said:
Oddly enough, this was not my experience. I unlocked my bootloader, flashed the Indonesia version 13.0.5.0 fastboot image using MiFlash using the clean all option. Then after booting and setting up the phone, it offered the update for version 14.0.1.0. I let the phone complete the update. Once the update finished and the phone had booted up again I rebooted it to bootloader mode and ran the command fastboot oem lock. The phone went through a factory reset and then booted successfully to the new phone setup dialogue.
Also to mention that I did also experience problems with 5GHz WiFi with version 13.0.5.0 but these problems were resolved after the version 14.0.1.0 update.
Click to expand...
Click to collapse
Even after update to 14.0.1.0 my 5Ghz wifi did not work. After waiting months I have just flashed back to global 14.0.2.0.TKPMIXM firmware yet still 5Ghz wifi is not working. Can someone guide how to fix it? Have I messed up its baseband or something during flashing?
Still unlocked bootloader?
As a comparison, whenever I unlock the bootloader on my Nokia 7 Plus and flash a custom ROM, I am not able to use 5GHz WLAN. It only works after relocking the bootloader and flashing stock firmware.
I am not sure if this was the same with the X3 GT and I cannot test it anymore as my wife took the phone and I am now using a X4 GT.
Longtn said:
1. use the official xiaomi bootloader unlock tool
2. Easy, just download the region fastboot rom you want and extract them. Flash via MiFlash -- pay attention to tick clean all in the corner of the screen if you don't want your device to be bricked
3. don't relock, if you lock the bootloader on other region firmware, you will be bricked
Click to expand...
Click to collapse
I relocked after flashing to ID rom from Global and it seems to work fine but 5Ghz WiFi still not working.
surfturtle said:
abubasim said:
Still unlocked bootloader?
As a comparison, whenever I unlock the bootloader on my Nokia 7 Plus and flash a custom ROM, I am not able to use 5GHz WLAN. It only works after relocking the bootloader and flashing stock firmware.
I am not sure if this was the same with the X3 GT and I cannot test it anymore as my wife took the phone and I am now using a X4 GT.
Click to expand...
Click to collapse
Not working even after locking bootloader, on both original Global ROM and ID ROM
both times I relocked the bootloader but no luck
Click to expand...
Click to collapse