So i inadvertently flashed my unlocked Note 8 (SM-N950u1) phone with TMobile's SM-N950U locked firmware for Android Pie. it now appears that I can't flash back to the unlocked firmware. The phone has an app that allows unlocking from TMobile's network but doesn't work. And TMobile has confirmed with me that my phone doesn't appear on their servers as locked. Odin won't let me flash. It fails everytime. Any suggestions, if possible, to flash back the unlocked firmware?
skeptic612 said:
So i inadvertently flashed my unlocked Note 8 (SM-N950u1) phone with TMobile's SM-N950U locked firmware for Android Pie. it now appears that I can't flash back to the unlocked firmware. The phone has an app that allows unlocking from TMobile's network but doesn't work. And TMobile has confirmed with me that my phone doesn't appear on their servers as locked. Odin won't let me flash. It fails everytime. Any suggestions, if possible, to flash back the unlocked firmware?
Click to expand...
Click to collapse
Are they both the same bootloader? Maybe that's why you can't go back? I'd they are different bootloaders you cannot downgrade to a lower one.
Sent from my [device_name] using XDA-Developers Legacy app
Related
Hey y'all I just picked up an att go phone moto e without researching it too much and I already bricked it trying sunshine. To unbrick it, I just flashed the att system image with fastboot and it made me wonder whether I can flash any motorola firmware, use kingroot, and then try sunshine again. Does anyone know if this can brick the phone permanently or is it probably safe to try it?
EDIT: tried it didn't work lol
You would have to try it and see. The XT1527 is used in Canada, and its not bootloader locked and comes with no bloat at all (at last when setting it up with no SIM inside it). I would imagine you would have to flash everything, and not just the system image, for it to work. That is if they use the same signing key for both.
The AT&T/Cricket-branded XT1527 (as well as the Verizon XT1528) have locked bootloaders and cannot be unlocked, so you cannot flash non-carrier firmware on the device. All other models can be unlocked via Moto's bootloader unlock program.
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.
I impulsively unlocked the boot-loader on my Mate 20 Pro last night because Funky Huawei was selling the codes for $20. Today I can't really think of a good reason I actually need the bootloader unlocked since I have no interest in rooting my phone and there are update methods for manually flashing firmware that don't require an unlocked bootloader. In fact, the tool posted on XDA for updating firmware with an unlocked bootloader apparently requires that you be rooted to use it.
Is there a way to relock the bootloader?
The only mention I could find in these threads was someone who said you need to factory reset the phone and then go back into fast-boot. I don't think the person who wrote that even tried it and that he was just making a generalization.
Does anyone know if there are actual steps that relock the bootloader without bricking the phone--which the e-recovery restore method might do since it will try to install an older firmware than is currently on my phone.
I might just keep it unlocked anyway but I was curious if there was a known relock method that works on this phone.
jhs39 said:
I impulsively unlocked the boot-loader on my Mate 20 Pro last night because Funky Huawei was selling the codes for $20. Today I can't really think of a good reason I actually need the bootloader unlocked since I have no interest in rooting my phone and there are update methods for manually flashing firmware that don't require an unlocked bootloader. In fact, the tool posted on XDA for updating firmware with an unlocked bootloader apparently requires that you be rooted to use it.
Is there a way to relock the bootloader?
The only mention I could find in these threads was someone who said you need to factory reset the phone and then go back into fast-boot. I don't think the person who wrote that even tried it and that he was just making a generalization.
Does anyone know if there are actual steps that relock the bootloader without bricking the phone--which the e-recovery restore method might do since it will try to install an older firmware than is currently on my phone.
I might just keep it unlocked anyway but I was curious if there was a known relock method that works on this phone.
Click to expand...
Click to collapse
Have a look at my post in thread below .. have done this method a few times and works for me.
https://forum.xda-developers.com/ma...ocking-bootloader-magisk-root-t3885422/page22
jhs39 said:
I impulsively unlocked the boot-loader on my Mate 20 Pro last night because Funky Huawei was selling the codes for $20. Today I can't really think of a good reason I actually need the bootloader unlocked since I have no interest in rooting my phone and there are update methods for manually flashing firmware that don't require an unlocked bootloader. In fact, the tool posted on XDA for updating firmware with an unlocked bootloader apparently requires that you be rooted to use it.
Is there a way to relock the bootloader?
The only mention I could find in these threads was someone who said you need to factory reset the phone and then go back into fast-boot. I don't think the person who wrote that even tried it and that he was just making a generalization.
Does anyone know if there are actual steps that relock the bootloader without bricking the phone--which the e-recovery restore method might do since it will try to install an older firmware than is currently on my phone.
I might just keep it unlocked anyway but I was curious if there was a known relock method that works on this phone.
Click to expand...
Click to collapse
Use dload method, but pba that will erase everything like your 1st setting of your phone. Phone will be locked again, FRP will still unlocked.
Sent from my LYA-L29 using Tapatalk
does dload method altso come with recovery_ramdisk fixed? for us that have modified it for root or twrp??
So that the device becomes out of the box like new?
Yes, recovery_ramdisk back to stock with dload method
Sent from my LYA-L29 using Tapatalk
i can confirm dload method lock back the bootloader.
i had install an alternate fw but was not satisfied cause too much features were not working, i used first erecovery to download official fw but unlock bl was still present. then i try dload and phone was completly reset with bl locked.
dload method isn't working for me. I extracted the UPDATE.APP from the firmware version that is currently installed on my phone (using the update_full_base version), created a dload folder on my external card, copied the UPDATE.APP into that folder and then did the dial code and selected update from memory card. My phone reboots and then I get an error that says that the update failed.
Do I need to use the UPDATE.APP from a specific build to get this to work?
I installed firmware via the Funky Huawei method. It seems to have relocked the bootloader because the warning about the bootloader being unlocked doesn't come up when the phone boots but the data on my phone wasn't erased. Can the bootloader be relocked without erasing all the data on the phone? If so this is the first I've heard of it.
jhs39 said:
I installed firmware via the Funky Huawei method. It seems to have relocked the bootloader because the warning about the bootloader being unlocked doesn't come up when the phone boots but the data on my phone wasn't erased. Can the bootloader be relocked without erasing all the data on the phone? If so this is the first I've heard of it.
Click to expand...
Click to collapse
Go to fastboot mode and check if bootloader is locked again.
Sent from my LYA-L29 using Tapatalk
ubersapian said:
Have a look at my post in thread below .. have done this method a few times and works for me.
https://forum.xda-developers.com/ma...ocking-bootloader-magisk-root-t3885422/page22
Click to expand...
Click to collapse
Will we able to reclaim warranty after relock? Anyway the service guys would be able to know that the bootloader was unlocked before?
Soo what is the legit way to relock the bootloader and the FRP?
is the FRP from stock/defualt locked?
Verstuurd vanaf mijn LYA-L29 met Tapatalk
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..
Is it possible to reflash an unlocked OS onto my currently carrier locked phone?
Yes
butchieboy said:
Yes
Click to expand...
Click to collapse
Would doing this remove all the carrier restrictions such as the garbage apps installed by them, and prevent them from coming back in the future?
You could easily just use Adb app control to disable what you don't want. But yes flashing unlocked firmware will result in no carrier bloat
butchieboy said:
You could easily just use Adb app control to disable what you don't want. But yes flashing unlocked firmware will result in no carrier bloat
Click to expand...
Click to collapse
I have already used adb to remove bloat, but new apps are still somehow popping up, and I don't want old ones to come back after an update.
Where can I learn how to flash unlock firmware? Particularly on an s23U
From my thread. Just download unlocked firmware, extract it. You will have files BL..AP..CP..CSC..HONE_CSC. Download patched Odin to computer. On device activate developer options enable usb debugging. Put device in download mode. Open Odin on computer connect device. Odin will see device , it will show green top left if Odin. Pur BL file in BL spot..AP file in Ap spot. CP file in CP spot..Csc in Csc spot..click start.
butchieboy said:
From my thread. Just download unlocked firmware, extract it. You will have files BL..AP..CP..CSC..HONE_CSC. Download patched Odin to computer. On device activate developer options enable usb debugging. Put device in download mode. Open Odin on computer connect device. Odin will see device , it will show green top left if Odin. Pur BL file in BL spot..AP file in Ap spot. CP file in CP spot..Csc in Csc spot..click start.
Click to expand...
Click to collapse
I heard that you can no longer unlock samsung US carrier phones
You are talking about something totally different. Unlocked firmware is not bootloader unlocking or sim unlocking. All unlocked firmware means is its not carrier branded. You asked about unlocked firmware, not bootloader unlock
butchieboy said:
You are talking about something totally different. Unlocked firmware is not bootloader unlocking or sim unlocking. All unlocked firmware means is its not carrier branded. You asked about unlocked firmware, not bootloader unlock
Click to expand...
Click to collapse
Oh. What's the difference?
butchieboy said:
From my thread. Just download unlocked firmware, extract it. You will have files BL..AP..CP..CSC..HONE_CSC. Download patched Odin to computer. On device activate developer options enable usb debugging. Put device in download mode. Open Odin on computer connect device. Odin will see device , it will show green top left if Odin. Pur BL file in BL spot..AP file in Ap spot. CP file in CP spot..Csc in Csc spot..click start.
Click to expand...
Click to collapse
Is this the unlocked firmware found here what I am supposed to be downloading?
Download Samsung Galaxy S23 Ultra (SM-S918U1) Stock ROM Firmware Flash File - Samsung One UI
this post will let you download and install Samsung Galaxy S23 Ultra (SM-S918U1) ONE UI 5.1 latest stable Android 13 update Stock ROM Firmware Flash File
www.samsungoneui.com
Hold on
SM-S918U S23 ULTRA/918U1 UNITED STATES FIRMWARE FLASHING
Most of us already know how to flash firmware with Odin. Here, anyone can post available firmware for everyone to use as well as general discussion. U firmware can be flashed on a U1 device and U1 firmware can be flashed on a U device using Odin...
forum.xda-developers.com
The difference is you need a token from Samsung to unlock the bootloader. Sim unlock is usually done after device is paid off and code is given by carrier. Your just talking about firmware. Firmware doesn't unlock the bootloader or sim unlock. If you want firmware without carrier bloat you are just wanting U1 firmware instead of U firmware. I don't know why so many people buy carrier locked devices then want unlocked firmware. Just buy unlocked device.
butchieboy said:
The difference is you need a token from Samsung to unlock the bootloader. Sim unlock is usually done after device is paid off and code is given by carrier. Your just talking about firmware. Firmware doesn't unlock the bootloader or sim unlock. If you want firmware without carrier bloat you are just wanting U1 firmware instead of U firmware. I don't know why so many people buy carrier locked devices then want unlocked firmware. Just buy unlocked device.
Click to expand...
Click to collapse
In some cases, domestic riding is limited to only devices sold by the carrier. As an example, I have T-Mobile USA. If I need to to on to US Cellular, I must have a device that was sold to me by T-Mobile or domestic roaming for US Cellular will not work. The issue specifically is with US Cellular not allowing the device to roam on to their network.
butchieboy said:
You could easily just use Adb app control to disable what you don't want. But yes flashing unlocked firmware will result in no carrier bloat
Click to expand...
Click to collapse
Is adb app control different from using adb to delete packages?
Adb app control is 1 click. You don't have to type in anything. It shows what's installed on device, you check box next to the app to disable or delete. Has restore function also
butchieboy said:
Adb app control is 1 click. You don't have to type in anything. It shows what's installed on device, you check box next to the app to disable or delete. Has restore function also
Click to expand...
Click to collapse
So it simplifies the process rather than provides new features? Is this the right source? https://adbappcontrol.com/en/
Yes