Related
Hi guys,
I am still new to this phone and I am trying to read as much as possible. but there is a lot of terminology to absorb. And I definitely want to make sure my phone is OK before the 14-day period when I can exchange it..
So, I unlocked my phone using one of the posted methods on here. i tried it with an AT&T sim card and it works.
Now, I read that there is something like a "hardware lock" which is bad .. because.. I wont be able to root or put rom or update my phone? I tried to go to a recovery mode, but could not, is my phone hardware locked?
Thanks in advance!
azsamsancho said:
Hi guys,
I am still new to this phone and I am trying to read as much as possible. but there is a lot of terminology to absorb. And I definitely want to make sure my phone is OK before the 14-day period when I can exchange it..
So, I unlocked my phone using one of the posted methods on here. i tried it with an AT&T sim card and it works.
Now, I read that there is something like a "hardware lock" which is bad .. because.. I wont be able to root or put rom or update my phone? I tried to go to a recovery mode, but could not, is my phone hardware locked?
Thanks in advance!
Click to expand...
Click to collapse
Did you do the correct way to recovery?
-Phone off, both volume keys held down
-Hit and hold power button while holding down volume keys
-The word vibrant will come on, and then it will go black again and reboot (still holding down all three buttons)
-When you see the word vibrant THE SECOND TIME let go of the power button but keep the volume keys down until you boot into recovery.
If not, most likely you are hardware locked. I don't have this problem but I think there's threads around for hardware locked users for workarounds and such.
yeah, i did exactly that:
1) power phone off
2) hold both volume buttons
3) hold power button
4) vibrant comes on, wait, vibrant comes on 2nd time
5) release power button, still holding both volume buttons
6) Vibrant starts in a normal way, i do not see anything different, so I assume i am in a regular mode, not recovery mode
azsamsancho said:
yeah, i did exactly that:
1) power phone off
2) hold both volume buttons
3) hold power button
4) vibrant comes on, wait, vibrant comes on 2nd time
5) release power button, still holding both volume buttons
6) Vibrant starts in a normal way, i do not see anything different, so I assume i am in a regular mode, not recovery mode
Click to expand...
Click to collapse
Make sure your Vibrant is hardware locked.
If you suspect that it is, you can read this thread HERE.
That will help you get your hardware locked phone working.
Unless you want to go get a new one.
I tied the following ways to test if my phone is hardware locked
1) vol up+ down + power
2) volu up + power
3) vol down + power
Nothing worked How would my phone would be hardware locked? I have not rooted, installed roms, nor apps.. Everything is stock, except that I unlocked the phone. that's all..
And it will be a huge pain to ship the phone back + wait for a new one, which there is no guarantee it wont be hardware locked ..?
Would I be able to install any rom if I am hardware locked? It seems like bionix mod is pretty popular..
Hardware lock is simply a boot loader issue. The phone has software the runs when you turn it out which in turn boots up the operating system. In hardware locked phones, the boot loader is not looking for the key combo to access recovery or download mode. If you go to the link provided, it tells you how to flash your phone to update the boot loader so that it is no longer hardware locked.
Hi guys, thanks for taking the time to read this. My brother's tablet is 'softbricked'. It hasn't been modified in any way, no unlocking, no custom ROMs etc. All he did was try to install the Jellybean update from Asus' site. I'm not quite sure what went wrong but the tablet won't get past the the Asus splash screen.
I've been googling around for solutions, of which I have found http://forum.xda-developers.com/showthread.php?t=1916952, going to the bootloader and factory resetting, or wiping the SD card and replacing the update. The problem is every attempt to get to the bootloader just leaves me at the Asus splash screen. Even holding volume down + hitting the reset slot button doesn't work. All of these fixes require access to the bootloader.
It was the correct SKU, nothing has been done to the tablet, so this shouldn't be TOO difficult to reverse right? I also assume that this isn't the only person this has happened to, but my google searches haven't proved fruitful.
extraneousleopards said:
Hi guys, thanks for taking the time to read this. My brother's tablet is 'softbricked'. It hasn't been modified in any way, no unlocking, no custom ROMs etc. All he did was try to install the Jellybean update from Asus' site. I'm not quite sure what went wrong but the tablet won't get past the the Asus splash screen.
I've been googling around for solutions, of which I have found http://forum.xda-developers.com/showthread.php?t=1916952, going to the bootloader and factory resetting, or wiping the SD card and replacing the update. The problem is every attempt to get to the bootloader just leaves me at the Asus splash screen. Even holding volume down + hitting the reset slot button doesn't work. All of these fixes require access to the bootloader.
It was the correct SKU, nothing has been done to the tablet, so this shouldn't be TOO difficult to reverse right? I also assume that this isn't the only person this has happened to, but my google searches haven't proved fruitful.
Click to expand...
Click to collapse
Try powering off the device by holding down the power button for 10 seconds. Now hold volume down and the power button both together and keep holding them for about 5 - 10 seconds. Do you get icons appear on the screen ?
flumpster said:
Try powering off the device by holding down the power button for 10 seconds. Now hold volume down and the power button both together and keep holding them for about 5 - 10 seconds. Do you get icons appear on the screen ?
Click to expand...
Click to collapse
Nope still goes straight to the Asus splash screen. Samsung phones have ODIN that basically is a godmode tool. Does Asus have anything?
He's accepted that all data will be lost. We just want it to work
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
hiveNzin0 said:
Hi guys,
I tried to unlock the bootloader of my Nexus 10 before rooting it. Unfortunately, it didn't work and I can't use it anymore (I either have the "Loading X" forever or a dead droid while trying to go to the recovery mode).
I'm used to do that kind of modifications (only on Samsung Galaxy S and S3 though) and I don't know what I did wrong (but I usually flashed with Odin).
Anyway, I used this tool (after enabling the usb debug and allowing unknown sources) : http://forum.xda-developers.com/showthread.php?t=2001868
I installed the drivers on my PC (menu 1 in the tool), then I could see my device in ADB MODE (in the tool menu). I tried to unlock the bootloader (3rd option in the menu) and it was written completed. My device reboots and nothing happens. I can access the fastboot mode (is it the download mode ?).
I have Odin.
Can someone help me to get a working device ?
Thank you very much.
Click to expand...
Click to collapse
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Okay, thank you very much. I didn't know I had to press the 3 top buttons again after the dead droid screen, I thought it failed loading the Recovery Mode.
I have to setup my account etc again so I guess it is safe to say it worked.
Additionally, I tried this method after the recovery : http://forum.xda-developers.com/showthread.php?t=2015467
and it worked fine. My device has an unlocked bootloader and is rooted.
hey if someone could help me im stuck myself, after i had the dead android in recovery mode i tried to flash software with the toolkit in fastboot and now when i go to recovery its just a blank screen till i hold the bottom combo again and it takes me back to fastboot
Blueback22 said:
Easy fix. Get to the dead droid recovery menu and then press all 3 buttons on the top. You will get into the blue recovery options. Choose factory reset.
Sometimes unlocking the bootloaders scrambles a few things on this device and it goes into boot loop. After the factory reset, you'll be fine. PM me if you still have issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
maximepull said:
Hey,
I'm having the same problem. I get to the dead droid instead of recovery and tried hitting all three buttons again but it's just looping again.
Any ideas?
Click to expand...
Click to collapse
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
sharksfan7 said:
It sounds like you didn't actually perform a factory reset. The key combination to get into stock recovery from the dead android screen is Power + Vol-Up. That will bring up the option to factory reset.
So if your powered off or bootlooping, hold the Power + Vol-Up + Vol-Down until you're back in the Bootloader. Use Vol buttons to select Recovery Mode and tap Power. When the droid w/ the Red "!" appears, hold the Power button and quick press the Vol-Up button. This should take you into stock recovery. Select Factory reset. Reboot. After a few minutes, the device should boot normally.
Good luck.
Click to expand...
Click to collapse
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Sorry. I don't know enough about these things to give more in depth troubleshooting advice. I just recently got my N10 & unlocked it and based on your original post, I thought that's where you needed help. But it sounds like you got past that and got it unlocked.
Have you tried downloading a factory image directly from Google and installing that? If it's locking up on a fresh install of any ROM, it very well may be a hardware issue. You may have to file a warranty claim if possible.
maximepull said:
Ok found a video showing that when you get to that part where there's the dead droid (the red !), you don't press hold hold all three buttons but tap them until the recovery screen shows up.
So finally did that but I still have the same problem.
My initial problem was, I received my N10, open the box, turned it on and it started freezing and rebooting. Can't get past the wifi step.
Tried hard and many times to finally get to enter my gmail account, etc
Updated to 4.3, problem persisted so I figured, maybe the factory flashed a bad rom?
So I unlocked it, rooted it and tried flashing older stock versions, same problem.
Tried flashing CM, same; PA, same...
Tried deactivating location service as suggested elsewhere: same; uninstall chrome: same
Even CM withouf GAPPS wouldnt work
So basically, I have a $500 brick. Completely useless as it freezes every 30 seconds.
Decided not to return the device because although I am Canadian, I live in SE Asia and had a visiting friend bring it to me. Way past the return period and the overall experience would be a real pain in the butt... Don't know what to do. Really hoping Kit Kat will solve it but I have doubts.
What do you think?
Click to expand...
Click to collapse
sharksfan7 said:
Have you tried downloading a factory image directly from Google and installing that?
Click to expand...
Click to collapse
^ that's your solution. If you dont know how to just pm me
Sent from my Galaxy Nexus using XDA Premium HD app
Hi All,
I have an HTC One that is stuck in a bootloop and have no idea how to fix it.
Unfortunately, there was a screen lock and after failed attempts, it started to delete the data. Stupidly, I tried to reset the phone at this point. As a result, it is stuck in a bootloop.
I have tried holding power and volume down button, volume down button by itself, both volume buttons and still can't get it to fastboot screen.
I am using Mac OSX.
Also, nothing had been done to the phone prior to this. All stock.
Any help would be greatly appreciated.
You have a few options, though it would be helpful if you had access to a PC, because then you could just use the RUU program to set everything right. You will need to know which variant of the One you have as in from which carrier or region, if it is an international version, as well as the system update that it was on as you can not downgrade while stock. The phone will eventually reboot if you just hold the volume keys and power together for like 30 seconds.
Option 1) Find a Windows PC and download the RUU exe, put the phone in bootloader mode, and follow the directions of the RUU.
Option 2) Unlock the bootloader at htcdev.com, install a custom recovery such as TWRP, and use a custom rom to get going. (This one you should be able to do on a Mac - voids warranty if you have one)
Option 3) Find a way to extract the rom.zip from the RUU exe and use fastboot to flash it. (Might be able to do on a Mac, though not familar with it to tell you what tool you could use to extract files from an exe on OS X)
es0tericcha0s said:
You have a few options, though it would be helpful if you had access to a PC, because then you could just use the RUU program to set everything right. You will need to know which variant of the One you have as in from which carrier or region, if it is an international version, as well as the system update that it was on as you can not downgrade while stock. The phone will eventually reboot if you just hold the volume keys and power together for like 30 seconds.
Option 1) Find a Windows PC and download the RUU exe, put the phone in bootloader mode, and follow the directions of the RUU.
Option 2) Unlock the bootloader at htcdev.com, install a custom recovery such as TWRP, and use a custom rom to get going. (This one you should be able to do on a Mac - voids warranty if you have one)
Option 3) Find a way to extract the rom.zip from the RUU exe and use fastboot to flash it. (Might be able to do on a Mac, though not familar with it to tell you what tool you could use to extract files from an exe on OS X)
Click to expand...
Click to collapse
Thanks for replying.
It is the HTC6500L that was originally used with Verizon in the US. Not sure if it matters but it is currently unlocked and using Optus sim in Australia. I'm not sure what system update it was on
I am going to try and get it working on my Mac first but it is good to know that there are options for me with a windows PC.
So you say that the phone will eventually boot if I hold both the volume buttons and power button down for about 30 seconds?
The phone is currently off as the battery has drained. If I charge it, it automatically goes to the HTC logo and into the boot loop. In order to get anything fixed, I need to get to the recovery screen right?
Nick2910 said:
Thanks for replying.
It is the HTC6500L that was originally used with Verizon in the US. Not sure if it matters but it is currently unlocked and using Optus sim in Australia. I'm not sure what system update it was on
I am going to try and get it working on my Mac first but it is good to know that there are options for me with a windows PC.
So you say that the phone will eventually boot if I hold both the volume buttons and power button down for about 30 seconds?
The phone is currently off as the battery has drained. If I charge it, it automatically goes to the HTC logo and into the boot loop. In order to get anything fixed, I need to get to the recovery screen right?
Click to expand...
Click to collapse
You'll need to get it to the bootloader screen at least. It definitely should be able to. I have had to deal with similar issues before.
es0tericcha0s said:
You'll need to get it to the bootloader screen at least. It definitely should be able to. I have had to deal with similar issues before.
Click to expand...
Click to collapse
So, I just tried to hold the power button and both volume buttons down for a good couple of minutes and nothing happened. Is that method hit and miss or you are sure that it will work eventually?
Try this http://forum.xda-developers.com/showpost.php?p=41795693&postcount=5
I was thinking of a way to block the bootloader, and I came up with something very basic, so please who can try the method, share whether it works or not. (This method was checked and it WORKS !!)
Warning: I am not a super developer, just one more user who wants to help the community
Warning 2: This Process will erase everything in its path, remember to make a backup of your internal memory.
This series of steps is aimed at inexperienced users, if you think you are missing or there are many steps, this guide is not for you.
Without more to say, let's start.
How to re-lock bootloader:
1. Turn off your device.
2. Press Bixby Volume down and connect your device to a PC to start the download mode (now you can release both buttons)
3. Read the text below on the Download Mode screen
to block or unblock the Bootloader.
4.- Long press the vol (- or +) button as best suits you.
LOCK BOOTLOADER:
5. Long press the volume up button ( ) until the computer is restarted (this will erase your data and restart automatically). :fingers-crossed:
Ready! Now you have a device with an OEM lock.
Good luck my friends!!!
chalofito said:
I was thinking of a way to block the bootloader, and I came up with something very basic, so please who can try the method, share whether it works or not. (This method was checked and it WORKS !!)
Warning: I am not a super developer, just one more user who wants to help the community
Warning 2: This Process will erase everything in its path, remember to make a backup of your internal memory.
This series of steps is aimed at inexperienced users, if you think you are missing or there are many steps, this guide is not for you.
Without more to say, let's start.
How to re-lock bootloader:
1. Turn off your device.
2. Press Bixby Volume down and connect your device to a PC to start the download mode (now you can release both buttons)
3. Read the text below on the Download Mode screen
to block or unblock the Bootloader.
4.- Long press the vol (- or +) button as best suits you.
LOCK BOOTLOADER:
5. Long press the volume up button ( ) until the computer is restarted (this will erase your data and restart automatically). :fingers-crossed:
Ready! Now you have a device with an OEM lock.
Good luck my friends!!!
Click to expand...
Click to collapse
Thank you for posting this. I've had this method work once before but i am in a bit of a pickle at the moment.
I no longer get the options to 'long press vol up' which i think is the key to re locking the bootloader. Have you or anyone else got any idea why that would be?
akkaria said:
Thank you for posting this. I've had this method work once before but i am in a bit of a pickle at the moment.
I no longer get the options to 'long press vol up' which i think is the key to re locking the bootloader. Have you or anyone else got any idea why that would be?
Click to expand...
Click to collapse
This was tested once and it worked, it was not tried for the second time .. What version of Compilation do you have?
chalofito said:
This was tested once and it worked, it was not tried for the second time .. What version of Compilation do you have?
Click to expand...
Click to collapse
It has definitely worked before but not having much luck now. Maybe the latest software update has blocked this method?
This is my current version. I'm in Australia.
View attachment 4767541
akkaria said:
It has definitely worked before but not having much luck now. Maybe the latest software update has blocked this method?
his is my current version. I'm in Australia.
View attachment 4767541
Click to expand...
Click to collapse
It's a shame, I'm sorry that this happens to you, we hope that in the future this will be solved, for the moment we have to wait. someone will come who finds a definitive solution.
chalofito said:
It's a shame, I'm sorry that this happens to you, we hope that in the future this will be solved, for the moment we have to wait. someone will come who finds a definitive solution.
Click to expand...
Click to collapse
Thanks for your help. Yes, hopefully soon someone will find a method.
akkaria said:
Thanks for your help. Yes, hopefully soon someone will find a method.
Click to expand...
Click to collapse
Can you tell what exactly you already did with your phone? Did you unlock bootloader, re lock bootloader, then unlocked it again and then actually rooted it? And now after you unrooted your phone you can not re lock bootloader?
I am asking because I suspect that you can not re lock you bootloader again after you actually have rooted your phone once. I am suspecting I only read a post from a guy who managed to re lock is bootloader but he never actually rooted his phone once. So in other words after you tripped knox (which seems to only happen when you install magisk) you may not be able to re lock you bootloader (ever) again.
SakazukiAka said:
Can you tell what exactly you already did with your phone? Did you unlock bootloader, re lock bootloader, then unlocked it again and then actually rooted it? And now after you unrooted your phone you can not re lock bootloader?
I am asking because I suspect that you can not re lock you bootloader again after you actually have rooted your phone once. I am suspecting I only read a post from a guy who managed to re lock is bootloader but he never actually rooted his phone once. So in other words after you tripped knox (which seems to only happen when you install magisk) you may not be able to re lock you bootloader (ever) again.
Click to expand...
Click to collapse
Yes!! You hit the nail on the head!! So i was able to re lock bootloader once before but i wasnt successful in rooting the phone. After i then successfully rooted the phone with Magisk i restored back to normal and no i cannot re lock the bootloader.
It seems as though a few people have said you can't re lock it after successfully rooting! Quite frustrating!!
akkaria said:
Yes!! You hit the nail on the head!! So i was able to re lock bootloader once before but i wasnt successful in rooting the phone. After i then successfully rooted the phone with Magisk i restored back to normal and no i cannot re lock the bootloader.
It seems as though a few people have said you can't re lock it after successfully rooting! Quite frustrating!!
Click to expand...
Click to collapse
I see. There is another method, that seems to work, tested by @robbo1947 that he explained here.
robbo1947 said:
Assuming you had the standard Samsung ROM (you hadn't flashed a custom ROM)
Change OEM switch while rooted, exit settings, no need to flash stock firmware.
Power off phone.
Press and hold Bixby and Volume down, whilst holding connect with USB cable to computer. Release buttons when Download screen appears.
Long press the Volume up.
At this stage, the phone will wipe the data and overwrite the Magisk modification then reboot.
You should now have an S10, standard boot screens, stock ROM and no root.
Click to expand...
Click to collapse
I did not check it myselff yet, but it worked for robbo1947. All credits goes to @robbo1947 !! Please let us know if that worked for you or not.
SakazukiAka said:
I see. There is another method, that seems to work, tested by @robbo1947 that he explained here.
I did not check it myselff yet, but it worked for robbo1947. All credits goes to @robbo1947 !! Please let us know if that worked for you or not.
Click to expand...
Click to collapse
I am going to have a go again in the next few days to prove to myself and others that it is possible to relock the bootloader after rooting. Will let you know.
Watch this space.
robbo1947 said:
I am going to have a go again in the next few days to prove to myself and others that it is possible to relock the bootloader after rooting. Will let you know.
Watch this space.
Click to expand...
Click to collapse
I look forward to your findings. As i am running my phone as my daily driver now i am hesitant to re root it if this method wont work. I have my fingers crossed though
samsung doesn't allow you to unlock and then lock back the device multiple times. It only works once, then your bootloader stay unlocked for ever.
I I had root and twrp on my s10 + but I quietly put the last nobrand ASE7 firmware back and I re-locked the bootloader without any difficulty I no longer have any warning messages at startup and in the developer options I have the oem option working like new.
akkaria said:
I look forward to your findings. As i am running my phone as my daily driver now i am hesitant to re root it if this method wont work. I have my fingers crossed though
Click to expand...
Click to collapse
Lebrun213 said:
samsung doesn't allow you to unlock and then lock back the device multiple times. It only works once, then your bootloader stay unlocked for ever.
Click to expand...
Click to collapse
OK, sorry for delay in getting back to this question of locking and unlocking the bootloader on the Galaxy S10.
During the last few days I have locked, unlocked, locked and unlocked again, probably 15 or 20 times to test various scenarios.
Please remember, each time you lock or unlock the bootloader all of your data is wiped.. any Root will also be gone. You will also be needing your current firmware.
This is for the Galaxy S10 without TWRP.
Scenario 1. Your phone is rooted with Magisk.
Go into Developers options and check OEM options, the switch must be ON (to the right). If it isn't turn it ON.
Turn off your phone. Press and hold the Bixby and Volume-down button, then connect with USB to your computer. (The cable shouldn't be connected until after you press the buttons).
Within seconds of USB connection the Download screen will appear. You will see 3 optiions, choose and Long press volume up and hold button until you see the 2 options at bottom of screen. Choose and hold volume up until screen goes off. Then the S10 logo screen will briefly apppear, before it flicks back to the Download screen with the words 'VBMETA: Error verifying vbmeta image etc' at the top, as the image below.
This is all good so far. Leave the phone exactly as it is with this screen showing and make sure the phone is still connected to the computer.
On your computer, fire up Odin3_v3.13.1, you can leave the Reboot option in Odin ticked. Locate your firmware on your computer and put the 4 file parts (BL, AP. CP and CSC) into Odin.
Let Odin finish.
The phone will reboot ready for setup.
The Unlocked bootloader warning screen will be gone.
Scenario 2. Your phone has been rooted but isn't now, and the greyed out OEM switch is ON
Easy, turn off your phone and proceed from the 2nd paragraph of Scenario 1.
Scenario 3 Your phone has been rooted but isn't now, and the greyed out OEM switch is OFF
Sorry, but in this situation, you are going to have to root your phone with Magisk as the OEM switch will only be available when rooted.
When rooted, proceed as Scenario 1.
Scenario 4 Your phone has never been rooted, and the greyed out OEM switch is ON i.e. you unlocked the bootloader but never proceeded to root the phone
Turn off your phone and proceed from the 2nd paragraph of Scenario 1.
If you want proof that I have locked and unlocked time and time again see HERE
:victory:
robbo1947 said:
OK, sorry for delay in getting back to this question of locking and unlocking the bootloader on the Galaxy S10.
During the last few days I have locked, unlocked, locked and unlocked again, probably 15 or 20 times to test various scenarios.
Please remember, each time you lock or unlock the bootloader all of your data is wiped.. any Root will also be gone. You will also be needing your current firmware.
Scenario 1. Your phone is rooted with Magisk.
Go into Developers options and check OEM options, the switch must be ON (to the right). If it isn't turn it ON.
Turn off your phone. Press and hold the Bixby and Volume-down button, then connect with USB to your computer. (The cable shouldn't be connected until after you press the buttons).
Within seconds of USB connection the Download screen will appear. You will see 3 optiions, choose and Long press volume up and hold button until you see the 2 options at bottom of screen. Choose and hold volume up until screen goes off. The S10 logo screen will briefly apppear, before it flicks back to the Download screen as the image below.
With the phone still connected to your computer, fire up Odin3_v3.13.1, you can leave the Reboot option in Odin ticked. Locate your firmware on your computer and put the 4 parts into Odin.
Let Odin finish. The phone will reboot and the Unlocked bootloader warning screen will be gone.
Scenario 2. Your phone has been rooted but isn't now, and the greyed out OEM switch is ON
Easy, turn off your phone and proceed from the 2nd paragraph of Scenario 1.
Scenario 3 Your phone has been rooted but isn't now, and the greyed out OEM switch is OFF
Sorry, but in this situation, you are going to have to root your phone with Magisk as the OEM switch will only be available when rooted.
When rooted, proceed as Scenario 1.
Scenario 4 Your phone has never been rooted, and the greyed out OEM switch is ON i.e. you unlocked the bootloader but never proceeded to root the phone
Turn off your phone and proceed from the 2nd paragraph of Scenario 1.
Click to expand...
Click to collapse
No dramas, thanks heaps for your reply.
So it seems I am in scenario 3 meaning I'll need to re root my phone which is fine. However, when I hold down the bixby and volume up and plug in I don't get the option to long hold volume up which I previously did. I only have press volume up or down. Is this because my bootloader is already unlocked? I should still be able to re root my phone in this scenario shouldnt i?
akkaria said:
No dramas, thanks heaps for your reply.
So it seems I am in scenario 3 meaning I'll need to re root my phone which is fine. However, when I hold down the bixby and volume up and plug in I don't get the option to long hold volume up which I previously did. I only have press volume up or down. Is this because my bootloader is already unlocked? I should still be able to re root my phone in this scenario shouldnt i?
Click to expand...
Click to collapse
Yep, your bootloader is unlocked.
When you have re-rooted and you go into Developer options you will be able to control the OEM switch and ensure it is ON.
Then when you get into Download mode you will see that option of LONG press Volume-up.
I've just added video proof to original post.
robbo1947 said:
Yep, your bootloader is unlocked.
When you have re-rooted and you go into Developer options you will be able to control the OEM switch and ensure it is ON.
Then when you get into Download mode you will see that option of LONG press Volume-up.
I've just added video proof to original post.
Click to expand...
Click to collapse
Awesome. Will give it a go in the next day or two and report back but given your success I'm hoping I'll have the same.
Cheers
akkaria said:
Awesome. Will give it a go in the next day or two and report back but given your success I'm hoping I'll have the same.
Cheers
Click to expand...
Click to collapse
Don't forget the :good:
robbo1947 said:
Don't forget the :good:
Click to expand...
Click to collapse
You sir, are my hero. It all worked perfectly and i no longer get the bootloader warning screen and my bootloader is now relocked!!
For anyone else having this problem, i too can confirm that this method works. The only issue i had was that for some reason, i was stuck on the Samsung flashing boot screen for nearly half an hour. A simple reboot into recovery(hold power and volume down for 7 seconds to shut down and then quickly hold power, vol up and bixby) and wipe factory data then system reboot fixed it.
I can also confirm that after doing this and re locking the bootloader, i now have access to all apps that i was previously having issues with and my google play store recognises my devices as certified.
I now have a fully working and functional device. Thank you again.
if i revert to stock rom after root and samsung status says official and relock bootloader will be able to get otas again???