Hi,
I had unlocked my boot loader to flash TRWP. But after unsuccessful attempt of H2OS installation I tried relocking my boot loader. Now device is not starting and its just showing blank screen. White Notification LED is there but nothing on screen. Need urgent help.
You...locked it with H2OS and...what recovery? What did you even do
ming3r said:
You...locked it with H2OS and...what recovery? What did you even do
Click to expand...
Click to collapse
I had official TWRP installed. I booted device into Fastboot mode and run "oem bootloader lock" command
Why? there is no real disadvantage to having unlocked bootloader and relocking often results in problems,. I have read of people recovering from this after contacting opo CS so that would be my advice
nileshwagholikar said:
Hi,
I had unlocked my boot loader to flash TRWP. But after unsuccessful attempt of H2OS installation I tried relocking my boot loader. Now device is not starting and its just showing blank screen. White Notification LED is there but nothing on screen. Need urgent help.
Click to expand...
Click to collapse
Hi, this is my first post but I had a similar problem after flashing H2OS and relocking bootloader. I solved it by holding down the power button until the white LED went out and then I booted into fastboot (power + Vol up) . from there I unlocked the bootloader and since then the phone seems to be working fine.
I hope that helps, at least in the short term
I am using OnePlus 3 with TWRP recovery and H2OS.
Hi, There http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700 is the method to unbrick.
Method 2 i have used and it works.
Here https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/ method to restock the phone.
Best Regards.
Related
Dear Gurus, I tried to use the process described on http://forum.xda-developers.com/showthread.php?t=1644167 but after the three boot process my phone kept looping the boot sequence on and off again.
Then I tried to flash Clockwork Recevery image using FASTBOOT mode but it didn't work. I think I have a Locked bootloader but I'm not sure.
Now when I try to turn the phone on with the volume down key pressed it flashes the red status light.
I have an UK carrier unlocked unit bought from Expansys UK. Any ideas, please?
EDIT: I still can get it into FASTBOOT mode...
andrezinh0 said:
Dear Gurus, I tried to use the process described on http://forum.xda-developers.com/showthread.php?t=1644167 but after the three boot process my phone kept looping the boot sequence on and off again.
Then I tried to flash Clockwork Recevery image using FASTBOOT mode but it didn't work. I think I have a Locked bootloader but I'm not sure.
Now when I try to turn the phone on with the volume down key pressed it flashes the red status light.
I have an UK carrier unlocked unit bought from Expansys UK. Any ideas, please?
EDIT: I still can get it into FASTBOOT mode...
Click to expand...
Click to collapse
good job, you used a s4 version kit to flash a tegra version phone. WHAT WERE YOU EVEN DOING IN THEIR FORUMS. now, you can flash an official ruu, and restart the process following guides.in this forum
Sent from my HTC One X using Tapatalk 2
I've just update my firmware using my thread http://forum.xda-developers.com/showthread.php?t=2696282
I'm S-On and followed every instruction. When the phone boot (everything was succesfull), it was stuck on the HTC welcoming screen.
Then I thought because the rom installed didn't match the new firmware, so I decided to unlock the bootloader, that too was fine. But then when the phone boot up, I again got stuck on the HTC welcoming screen. Then I tried adb to boot into the bootloader to flash the TWRP custom recovery, but nothing to do, adb is not recognising the phone. But the storage of my phone is appearing on windows explorer and the drives were successfully installed automatically.
What should I do, urgent please anyone
Thanks
92davin said:
I've just update my firmware using my thread http://forum.xda-developers.com/showthread.php?t=2696282
I'm S-On and followed every instruction. When the phone boot (everything was succesfull), it was stuck on the HTC welcoming screen.
Then I thought because the rom installed didn't match the new firmware, so I decided to unlock the bootloader, that too was fine. But then when the phone boot up, I again got stuck on the HTC welcoming screen. Then I tried adb to boot into the bootloader to flash the TWRP custom recovery, but nothing to do, adb is not recognising the phone. But the storage of my phone is appearing on windows explorer and the drives were successfully installed automatically.
What should I do, urgent please anyone
Thanks
Click to expand...
Click to collapse
[Resolved]
hold up and down volume keys then power button to switch off device. Then boot into bootloader through volume down and power button. Flash recovery and install rom. Panicked for nothing
How do I relock my verizon pixel bootloader without bricking it? I'm 100% on stock X rom anyway, radios and all. I never rooted or ROM'd.
reason behind it, is I want android pay and other things to work like the android lock so if you lose your phone, kind of like icloud lock I assume?. I don't root or rom my phone anymore since galaxy nexus days, I like the stock ROM... and if Verizon is on PAR with giving OTAs immediately as google says they will be controlling OTAs, there isnt a reason for me to unlock this thing anymore. I only unlocked it strictly if Verizon was going to delay stuff.
adb reboot bootloader
fastboot flashing lock
deuce_biggins said:
adb reboot bootloader
fastboot flashing lock
Click to expand...
Click to collapse
so just command promp reboot into bootloader and then
fastboot flashing lock ??
this will not brick my phone as long as im 100% stock which i am? i'm not clean flashed stock, i have apps, etc. but on latest google X build (verizon) right from their website.
imablackhat said:
so just command promp reboot into bootloader and then
fastboot flashing lock ??
this will not brick my phone as long as im 100% stock which i am? i'm not clean flashed stock, i have apps, etc. but on latest google X build (verizon) right from their website.
Click to expand...
Click to collapse
Two things:
1) If your system is normally booting and stock 100%, relock should be fine. in case you do randomly get a red screen after "fastboot flashing lock" and cannot boot... Press power button on the red warning (to pause boot), and "fastboot continue" will allow you to boot and you would then have to unlock again and flash factory image. The "continue" command only reliably works if BEFORE you lock bootloader you can still boot.
2) Do a back up. Boot into OS. Turn on USB debugging and turn on your home screen. Then:
adb backup -all -apk -shared -f backup-Dec1.ab
And restore after locking bootloader. The reason for this is that locking bootloader will probably wipe your device just like unlocking it.
Sent from my sailfish using XDA Labs
nednednerb said:
in case you do randomly get a red screen after "fastboot flashing lock" and cannot boot... Press power button on the red warning (to pause boot), and "fastboot continue" will allow you to boot and you would then have to unlock again and flash factory image. The "continue" command only reliably works if BEFORE you lock bootloader you can still boot.
Click to expand...
Click to collapse
I never hear of this. Can you tell me more?
cam30era said:
I never hear of this. Can you tell me more?
Click to expand...
Click to collapse
It might be new to SDK api 25, but it is the advice I find given to people who foolishly lock their bootloader when not 100% stock (like me).
Basically on the pixel bootloader, it checks for corruption before booting. If you've rooted etc, you must have seen the yellow warning. If system is 1% modified (eg: unlocked), it gives the warning. Pretty sure if you lock bootloader at that point and not 100% stock, it gives red warning and cannot boot.
However, if system COULD boot, "fastboot continue" saves day from red warning.
If you would have been stuck in bootloop and then lock, may be SoL.
Trying the continue command a couple more times after getting stuck rebooting MAY work too, if lucky.
In this scenario... After you get back into OS, unlocking bootloader again is the move to make.
Sent from my sailfish using XDA Labs
nednednerb said:
It might be new to SDK api 25, but it is the advice I find given to people who foolishly lock their bootloader when not 100% stock (like me).
Basically on the pixel bootloader, it checks for corruption before booting. If you've rooted etc, you must have seen the yellow warning. If system is 1% modified (eg: unlocked), it gives the warning. Pretty sure if you lock bootloader at that point and not 100% stock, it gives red warning and cannot boot.
However, if system COULD boot, "fastboot continue" saves day from red warning.
If you would have been stuck in bootloop and then lock, may be SoL.
Trying the continue command a couple more times after getting stuck rebooting MAY work too, if lucky.
In this scenario... After you get back into OS, unlocking bootloader again is the move to make.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
So say in theory this happened, however you're able to get into Fastboot and such, how might you fix that?
Tisch22 said:
So say in theory this happened, however you're able to get into Fastboot and such, how might you fix that?
Click to expand...
Click to collapse
If you cannot boot into OS, fastboot continue won't help.
If your bootloader is locked, you can't do anything with fastboot.
The hope is "continue" gets you passed red warning, and you can unlock bootloader again. If you can't boot at that point, unlikely to have solution,
Sent from my sailfish using XDA Labs
nednednerb said:
If you cannot boot into OS, fastboot continue won't help.
If your bootloader is locked, you can't do anything with fastboot.
The hope is "continue" gets you passed red warning, and you can unlock bootloader again. If you can't boot at that point, unlikely to have solution,
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Fastboot continue does load up the OS, however once it starts optimizing the apps it goes to a black screen.
nednednerb said:
If you cannot boot into OS, fastboot continue won't help.
If your bootloader is locked, you can't do anything with fastboot.
The hope is "continue" gets you passed red warning, and you can unlock bootloader again. If you can't boot at that point, unlikely to have solution,
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Scratch that, I was able to get back into the OS via "Fastboot continue" however unlocking the bootloader again to reflash the img is becoming quite troublesome.
5x got hot and turned off. Won't turn back on. Am I screwed?
Well, hope you have your bootloader unlocked or some sort of warranty, otherwise you're gonna have a tough time flashing custom boot images.
Unknown025 said:
Well, hope you have your bootloader unlocked or some sort of warranty, otherwise you're gonna have a tough time flashing custom boot images.
Click to expand...
Click to collapse
Bootloader is unlocked and I have twrp, no warranty. I flashed but it freezes mid-boot or doesn't power on at all.
jrk190 said:
Bootloader is unlocked and I have twrp, no warranty. I flashed but it freezes mid-boot or doesn't power on at all.
Click to expand...
Click to collapse
Which images have you tried? The only ones that worked for me was the Oreo 8.1 update, after that the phone ran smoothly.
I'm going through the same problem, here are few symptoms : 1. Phone doesn't boot. It gets stuck between boot to doesn't boot at all.
2. I can access boot loader but cannot flash recovery. The phone dow not boot into recovery.
What should be done? Any help is appreciated. Thanks!
Search for 5x bootloop fix here and elsewhere. Was heavily covered when it was really bad starting around June. Too many things to try to repost, like putting it in the freezer for a while to get it to temporarily boot.
Try this fix which disables the big cores if you can.
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Phone won't start but it keeps booting to TWRP for some reason.
My one plus 5t is stuck on logo after an official update and the bootloader is locked.
Is there any way to unlock bootloader without access to OS (OEM unlock), so that I can flash any custom recovery?
Or any other solution from experts?
Use fastboot to OEM unlock.
Read up on some tutorials, this one is easy to fix.
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
That thread should get you going.
Nick502 said:
Use fastboot to OEM unlock.
Read up on some tutorials, this one is easy to fix.
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
That thread should get you going.
Click to expand...
Click to collapse
I read this but they are saying that you have to go to setting and developer option to enable oem unlock first, but i cant access to my device because my device is stuck on logo screen.
kashan69 said:
I read this but they are saying that you have to go to setting and developer option to enable oem unlock first, but i cant access to my device because my device is stuck on logo screen.
Click to expand...
Click to collapse
I would suggest you do this first:
https://downloads.oneplus.com/oneplus-5t/oneplus_5t_oxygenos_5.1.1/
Then you should be able to boot to android again. Then tick the OEM lock button
Just enter stock recovery mode and do a wipe factory reset. If it doessnt work, just falsh official oxygen os and do the factory reset again.
If the reset doeesn't work there is a cheat that will work if encrypted and your data is backed up... Open the stock recovery which will require a password. Select the dont remember button at the bottom. It will warn you that procedding will wipe your phone. Do it. The recovery will wipe and reboot your phone with the stock image you just tried to flash. You WILL lose data.
If you cant access the stock recovery or TWRP you can boot either on your PC and perform a wipe from there. You can then move a stock image over to root and flash it with the stock recovery.
I have this same issue, stuck on one plus logo on boot. Can enter fast boot menu but can not enter recovery mode.
Do you still have that problem?
kashan69 said:
I read this but they are saying that you have to go to setting and developer option to enable oem unlock first, but i cant access to my device because my device is stuck on logo screen.
Click to expand...
Click to collapse
I want to help you Do you still have that problem?
Do a factory reset in stock recovery. If it doesn't work, then use this guide
https://forum.xda-developers.com/on...5t-unbricking-tool-confirmation-t3733012
AIsmael said:
I want to help you Do you still have that problem?
Click to expand...
Click to collapse
I still have this problem. Stuck at logo and I can't get to recovery mode. Can you help me please?
I am having the same issue. After the android 10 update and after my first restart, it gets stuck on first android boot screen. Not ever the oneplus screen is shows and phone screen becomes dark with led on in grey color. I tried wiping the cache and did a factory reset too but it did not work. Help me what to do. Also where can I find android OS image list of 5T and a process to flash it through PC (ADB commands may be or something else?)
Someone pls help me. My Oneplus 5t stuck in logo screen & not moving to any further screens.
1. Switched Off the phone
2. Now turning it ON & logo screen has come
3. After 5 to 6 seconds logo screen disappears & white LED indication starts glowing.
Pls suggest what to do.
Have the same problem, MSM tool doesn't help.
farrukh.pasha said:
I am having the same issue. After the android 10 update and after my first restart, it gets stuck on first android boot screen. Not ever the oneplus screen is shows and phone screen becomes dark with led on in grey color. I tried wiping the cache and did a factory reset too but it did not work. Help me what to do. Also where can I find android OS image list of 5T and a process to flash it through PC (ADB commands may be or something else?)
Click to expand...
Click to collapse
SuryaLava said:
Someone pls help me. My Oneplus 5t stuck in logo screen & not moving to any further screens.
1. Switched Off the phone
2. Now turning it ON & logo screen has come
3. After 5 to 6 seconds logo screen disappears & white LED indication starts glowing.
Pls suggest what to do.
Click to expand...
Click to collapse
Do you have any success?
Ryav said:
Have the same problem, MSM tool doesn't help.
Do you have any success?
Click to expand...
Click to collapse
I fixed this! Disassembled, disconnected battery, inserted usb cable, got message about battery, connected battery, started!