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
Related
Hi Guys,
I lent my old Hero to a friend and they stuck a passlock on it. annoyingly they now say they can't remember what it is. So I've been trying to figure out what they set the passlock as, would have been something pretty easy I thought as they aren't that clever! Still can't seem to get it.
So I thought I'd go into the boot menu and try to restore the phone. Remove the battery and then turn the phone on by holding the power button and home button but I get this screen http://grab.by/9dYe which is giving me a bad feeling.
Is there any other way I could wipe the phone?
Thanks,
Charlie
Ok, from reading another thread I'm wondering if it's possible to place the newest RUU from http://forum.xda-developers.com/showthread.php?t=559622 in a .zip files named HEROIMG.zip in the root of the SD Card. I can then hold the Volume Down button on boot and use hboot to flash the phone with the new rom.
Is this correct?
Here's a video of me attempting to install the RUU via hboot.
To be honest I'm not sure if I'm doing this right. My device still has a passlock on it, so I can't run the .exe on my computer because the phone can't sync.
hmmm... as seen from the video, You can get into fastboot menu and connect your usb to the PC. then run Your RUU exe. Have you tried that? Does a passlock lock the exe from doing it's job?
You said
the phone can't sync
Click to expand...
Click to collapse
Why do you need sync? if you have drivers on your pc, then the rru.exe should do it's job...
I was doing a backup with TWRP and everything seemed to go just fine. Then after a reboot i unlocked the phone to notice that it was leaving the lock-screen icons on the bottom of the page. I still had access to my notification bar and could clear notifications. Figuring that there had just been a mistake in the boot process, I held the power button to restart the phone. Well it never brought up my power menu to restart. Also instead of making me wait ten seconds until it flashed its lights and restarted, it just restarted in like 3 seconds. Now my phone is stuck on the HTC ONE screen and will not respond to anything including hold the power button.
My phone is rooted an s-off. I know that I have not posted at all on here, but I have been rooting and know how at least the basics on adb shell. I just have never had a phone lock up to this point. If I can at least get to recovery, I should have 2 or 3 backups to run. I just don't want to have to wait for the phone battery to die just to hope I can get to recovery.
TugboatTony said:
I was doing a backup with TWRP and everything seemed to go just fine. Then after a reboot i unlocked the phone to notice that it was leaving the lock-screen icons on the bottom of the page. I still had access to my notification bar and could clear notifications. Figuring that there had just been a mistake in the boot process, I held the power button to restart the phone. Well it never brought up my power menu to restart. Also instead of making me wait ten seconds until it flashed its lights and restarted, it just restarted in like 3 seconds. Now my phone is stuck on the HTC ONE screen and will not respond to anything including hold the power button.
My phone is rooted an s-off. I know that I have not posted at all on here, but I have been rooting and know how at least the basics on adb shell. I just have never had a phone lock up to this point. If I can at least get to recovery, I should have 2 or 3 backups to run. I just don't want to have to wait for the phone battery to die just to hope I can get to recovery.
Click to expand...
Click to collapse
Are you saying volume up + power button does not restart your phone nor does any help? Check if your phone is detected in computer and if so you can issue and adb reboot command
also since there is no removable battery HTC added a reboot function press home vol down and power that should do the trick
The phone is not detected by a computer, nor will it charge. Vol down and power is not cutting it off. Right now I am waiting for the battery to die so I can hopefully boot into recovery and do a restore.
Vol up + Power was the key. I was thinking it was volume down. Thanks for all your help
TugboatTony said:
The phone is not detected by a computer, nor will it charge. Vol down and power is not cutting it off. Right now I am waiting for the battery to die so I can hopefully boot into recovery and do a restore.
Click to expand...
Click to collapse
Its volume up mate + power not volume down
pradeepvizz said:
Its volume up mate + power not volume down
Click to expand...
Click to collapse
Hi Do you have a HTC one max stock Rom I could use??
Thanks
mini88448 said:
Hi Do you have a HTC one max stock Rom I could use??
Thanks
Click to expand...
Click to collapse
There have been lots of request for this, ill upload a stock rooted ROM soon.
pradeepvizz said:
There have been lots of request for this, ill upload a stock rooted ROM soon.
Click to expand...
Click to collapse
OMG THANK YOU SO MUCH!!!
:victory::victory::victory:
Just wanted to point out I ran into this issue also (Stuck on white HTC boot screen) after wiping my ROM and Vol UP + Power did the trick for me also (and then Vol Down + Power to get back to the bootloader).
i need help, guys
so attempting to install a new rom, i must have dont something wrong because now restarting the phone will leave me on the htc logo loop and restart. i still have access to hboot and fastboot. but when attempting to load into twrp, it shows the team win logo for half a second and then restarts the phone. then i installed cwm and it does boot into it but whatever option i pick, install zip, wipe data, ANYTHING, restarts the phone.
i have no idea what to do. i tried installing a rom using adb sideload but it stops at around 80%, ive tried installing different versions of twrp and cwm and same thing. i think it is bricked. im using the verizon htc one max. the only option i see left is the ruu toolkit but ive only been able to find the sprint version and then it says that bootloader needs to be locked and i have not idea how to do that from hboot, fastboot, or cwm
attempting to install superuser also fails
if there's anyone here that can help, please, any suggestions will be appreciated. thanks =:laugh:
Sounds like you're flashing the wrong TWRP.
Sent from my Galaxy Nexus using Tapatalk
suieitori said:
so attempting to install a new rom, i must have dont something wrong because now restarting the phone will leave me on the htc logo loop and restart. i still have access to hboot and fastboot. but when attempting to load into twrp, it shows the team win logo for half a second and then restarts the phone. then i installed cwm and it does boot into it but whatever option i pick, install zip, wipe data, ANYTHING, restarts the phone.
i have no idea what to do. i tried installing a rom using adb sideload but it stops at around 80%, ive tried installing different versions of twrp and cwm and same thing. i think it is bricked. im using the verizon htc one max. the only option i see left is the ruu toolkit but ive only been able to find the sprint version and then it says that bootloader needs to be locked and i have not idea how to do that from hboot, fastboot, or cwm
attempting to install superuser also fails
if there's anyone here that can help, please, any suggestions will be appreciated. thanks =:laugh:
Click to expand...
Click to collapse
May I suggest following these instructions?
http://forum.xda-developers.com/showpost.php?p=51753483&postcount=129
If you're able to complete those instructions outlined in that post, this should set you up with the latest HBOOT, Radio and TWRP (Recovery) for the Verizon HTC One.
Make sure you read the post fully before you start, especially this part:
fastboot flash zip firmware.zip (Be sure it finishes saying 'successful', not 'please flush again immediately'. If it says the flush again, rerun the command)
If you succeed in getting that done, see if TWRP still causes the phone to reboot and get back to us.
Ok, I just want to know if my phone is hard bricked, or if I still have a chance...
I tried to install an update (121 to 170 for plk-l01) on my rooted phone, with local update. It didn't worked, twrp show errors everywhere, and after turning off know i can't access the recovery. when I press on vol+/- and power for 10-15 second, it vibrate but nothing else.
Is there anything I can do ? my phone isn't recognized by my computer, by the way...
Why you did that? You can't update rooted phone
Idiocrate said:
Ok, I just want to know if my phone is hard bricked, or if I still have a chance...
I tried to install an update (121 to 170 for plk-l01) on my rooted phone, with local update. It didn't worked, twrp show errors everywhere, and after turning off know i can't access the recovery. when I press on vol+/- and power for 10-15 second, it vibrate but nothing else.
Is there anything I can do ? my phone isn't recognized by my computer, by the way...
Click to expand...
Click to collapse
Try to boot into fastboot (phone turned off - connect with data usb to the computer - vol down + power on). Extract rom which is currently installed or higher (for your respective model) and flash from it:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
Reboot.
piskr said:
Try to boot into fastboot (phone turned off - connect with data usb to the computer - vol down + power on). Extract rom which is currently installed or higher (for your respective model) and flash from it:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
Reboot.
Click to expand...
Click to collapse
Thanks, but unfortunately, it just 'boot' as others reboots. it vibrates, doesn't get recognize and doesn't turn on...
If anyone have any clue on how to force recognizing the phone storage, it might really help ^^
That is what my phone is doing, I tried to upgrade to marshmallow though with no root!! I put the zip in the dload folder and went through the upgrade process everything went through the phone rebooted and now its dead. Blank screen and if you hold power after a few seconds it will vibrate but that is it. I presume its hard bricked? no matter what combo of buttons I press I cannot get it in to fastboot.
james194zt said:
That is what my phone is doing, I tried to upgrade to marshmallow though with no root!! I put the zip in the dload folder and went through the upgrade process everything went through the phone rebooted and now its dead. Blank screen and if you hold power after a few seconds it will vibrate but that is it. I presume its hard bricked? no matter what combo of buttons I press I cannot get it in to fastboot.
Click to expand...
Click to collapse
ok I'm looking for a solution for hours now... so I just lokked how works our phone and I think the trouble must be in the preloader, because I can't even make my phone being recognized by any computer and I can't access to recovery.
I found this :
http://www.droidgyan.com/soft-brick-vs-hard-bricked-vs-broken/
Which could help. I'll leave that topic on for some days (if it could help someone) and I'll open a new one to know if there is any easier solution ! thanks and good luck.
I sorted mine, it was only 2 days old so I got it replaced by the shop I bought it on. I would say it was something like a pre loader from what I saw. I have never bricked an Android phone and I must have had 15-20 of them since my first HTC Magic and before that Windows Mobile which again I messed with tons reloading with all sorts of ROM's!! These phones are wayyyy too sensitive to being messed with, I always remember though that you never mess with the boot loaders, but it looks like these updates do to get it bricked to that point.
Idiocrate said:
Thanks, but unfortunately, it just 'boot' as others reboots. it vibrates, doesn't get recognize and doesn't turn on...
If anyone have any clue on how to force recognizing the phone storage, it might really help ^^
Click to expand...
Click to collapse
Do you have adb debugging activated on the phone? Did you try to hold phone buttons long enough?
piskr said:
Do you have adb debugging activated on the phone? Did you try to hold phone buttons long enough?
Click to expand...
Click to collapse
Euuum..... maybe yes ? I used fastboot but I don't think it really matters now, there's nothing working on it. And I've sometimes hold the buttons for 30-40 second while praying lol
korenisko said:
Why you did that? You can't update rooted phone
Click to expand...
Click to collapse
local update
I just hard bricked my Honor 7 the same way. Is there really no solution? Other China-Phones are pretty much unbrickable, since you can always fix it via the preloader. No such luck here? Back to the shop and hope they actually replace it? While I admit it was stupid to just hastily start the OTA while having twrp and not stock recovery (no root, though), this is a terrible design flaw on Huaweis side.
Anyway... any hope or no chance?
i just hard bricked my honor 7 PLK-L01
it the same thing it is doing . not recognized by the computer
tried all the combination of buttons. but no hope
and it only vibrates when tried to turn on
Need urgent help please
@Idiocrate try to boot into bootloader mode just by pressing Vol DOWN button and simultaneously connecting it to a PC, don't press Power button, if it boots into it, then follow the method given by @piskr in third post.
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???
Hi everyone, I followed this guide here https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ to root the phone with magisk. Everything went great up to the last point. I rebooted my device and I am currently stuck at fastboot mode as my device can't normally boot into stock rom I had before I tried to root it. Should I just flash stock rom on the device? How should I do that? I am still an amateur and can't figure it out by myself. My bootloader is unlocked. Any help would be much appreciated. Flashing backup boot images doesn't help.
Just put your device in the download mode. Here are the steps for you:
1. When you are in the fastboot mode, choose to turn off the device by scrolling though the options (via volume up/down key and then pressing the power button to select).
2. After the phone is off, keep the volume up key pressed and insert the USB cable into the device. Make sure the USB cable is attached to a computer before plugging it into the phone. This will put you in the download mode.
3. From there you flash the relevant firmware using LGUP.
The case is outdated, I managed to upload the firmware via LGUP
Hi everyone.
I have a similar problem. I wanted crossflash to EU.
When I was ripping and deleting the contents of the partition, the phone lost the usb connection and after reboot it fell into a loop. It does not report for usb and I can not turn it off. Is there anything else that can be done to save him? I erased the partitions FTM, Modem_A, Modem_B, SID_A, SID_B, OP_A - not OP_B.
I have a backup of them
I'm sorry, my english is bad.
You have two options depending on which one is available to you:
1. If you get into the QFIL then try to restore the deleted partitions. It is quite possible that other partitions have also got affected due to abrupt disconnection resulting from power failure.
2. Maybe you can get into the download mode. It will be tricky. Press and hold the volume down key and the power button till the phone restarts. Once it starts, press the volume up key and insert USB cable (that is already connected to a computer). Once there, re-flash the firmware.
Thank you for your help. I was able to start the phone in download mode and upload the firmware via LGUP.
Hello! I didn’t root anything, everything is stock. at some point phone just crashed and now it is stuck in boot loop. i was able to factory reset it, but nothing changed, it keeps rebooting. LV600AM
The problem, in your case, becomes complex because AT&T does not release firmware publicly (that you could just re-flash the phone with). How were you able to factory reset the V60 phone? Did you get into the settings menu and reset it from there?
Royaltiger said:
The problem, in your case, becomes complex because AT&T does not release firmware publicly (that you could just re-flash the phone with). How were you able to factory reset the V60 phone? Did you get into the settings menu and reset it from there?
Click to expand...
Click to collapse
i was able to use power/volume down feature to get into factory reset menu, wipee everything, but nothing changed. it just keeps rebooting till battery runs out
I hope someone here could share with you a full AT&T V60 partition dump. Failing which your only option is to have AT&T restore it for you.
Royaltiger said:
I hope someone here could share with you a full AT&T V60 partition dump. Failing which your only option is to have AT&T restore it for you.
Click to expand...
Click to collapse
Thanks. Ill contact att then
at&t pretty much confirmed that it's a brick now...
Here is your answer.