Please help - Stuck on Boot loader warning screen. - OnePlus 6T Questions & Answers

Hello all,
Earlier i had ran the battery down to 0% and plugged my phone in to charge. after 10 mins i came back to the phone and I could see the bootloader warning screen;
The Boot loader is unlocked and software integrity cannot be guaranteed..... etc...
No button on the device seems to do anything and device isnt showing under ADB or Fastboot.
Any ideas other than let the device run out of battery?
Rom: OOS
Recovery: TWRP
Kernel: Stock
Root: Magisk

Yeah, that happened to me too, that's why I don't charge the phone turned off
Press the power + vol up buttons till the screen turns off once it does stop pressing them and it should boot up

It's a Magisk bug for what it's worth. Unplug the phone, hold all three buttons and it will vibrate and reboot after a few seconds. Once you see the boot logo, plug it back in and it should finish booting and also be charging.

This happened to me too. I was really worried as I waited over 20 hours for it to drain the battery. All i had to do was to hold volume Up+power button for about 15 seconds.

romracer said:
It's a Magisk bug for what it's worth. ...
Click to expand...
Click to collapse
source, mate?
@mods, perhaps you can merge this thread with https://forum.xda-developers.com/oneplus-6t/help/oneplus-6t-stucked-unlocked-bootloader-t3874178

Guys, do you have any problem using the hw buttons to boot in recovery/bootloader? I tried everytime, but the only way I could boot in there was with the advanced reboot option.

To ROMRACER: Thank you. You helped very much. It works.

not a magisk bug. answered here

OP6T
I can turn off the phone using the power button and volume up, but after rebooting again, still can't get passed the boot loader warning... any solutions?

I was in this position today.
I'd kept the charger attached whilst going into TWRP to do a NANDROID backup, when I rebooted was stuck at he bootloader warning. None of the suggested solutions above worked for me having tried them several times, each time I got the phone to reboot was again stuck at the warning.
I could get into fastboot, (but from there any method to boot came to the warning again), so connected to the pc and reflashed TWRP image and could then boot into recovery, from there reflashed Magisk and was finally able reboot normally.
Hope this might help someone else.

Related

Yotaphone 2 - another bricked phone after update

Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
pjrj said:
Hi guys,
My Yotaphone 2 is currently stuck in a boot loop (shows android logo, then black screen, repeat) after a software update. I can get to the 'Downloading...' screen via power + vol. key and so have tried adb/fastboot as suggested in other similar threads. ADB can't see the device, which I guess is probably normal since it isn't booted up, but fastboot seemingly can. I've tried flashing the TWRP recovery which seems to go through fine on the PC end but doesn't seem to do anything at all on the phone itself. Calling a fastboot reboot gets the phone back to the boot loop and power + vol. goes back to the 'Downloading...' screen.
I've also tried using the Yotaphone flashing tool to flash a full android image - this also looked like everything was operating OK on the PC end but didn't seem to change anything on the phone once the process was complete.
Is there anything I'm missing or anything else I can try? Any help/ideas much appreciated!
Cheers.
Click to expand...
Click to collapse
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
SteadyQuad said:
Do you have any idea what caused the bootloop? (maybe installing xposed or something?)
When you keep vol-up pressed at (not after) the moment the phone vibrates during power on, you will end up in TWRP recovery. There you can at least wipe->factory reset. Don't do this if you have stuff on your phone you'd like to keep though. (you can try to rescue/backup those by trying "adb pull <path_to_file>" when the phone is booted into TWRP)
Click to expand...
Click to collapse
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
pjrj said:
It was caused by doing an OS update (wasn't rooted or modified), I've only since tried installing the TWRP recovery and using fastboot to flash an official image to fix the looping. Flashing TWRP appears to work according to flashboot but holding the volume up key at the vibrate on power on doesn't do anything sadly.
Click to expand...
Click to collapse
Maybe I should rephrase: the vol-up should already be pressed once the vibrate starts. For a timing-insensitive, fool-proof (no pun intended) way you can enable bootloader (like you did before: you get the Downloading... screen). Then keep vol-up and power pressed together, after 15 seconds the device reboots hard, keep both keys pressed until you see TWRP 'curtain' screen, then release.
Did you try to use the YotaFlasher Windows application to reinstall an official ROM and restore factory defaults? You can get it from here, also download a ROM for your region here.

[BRICK] Boot screen in loop - no power off possible

Hi all,
I was really happy with Lineage OS 14.1 running on my Storm. Today, I decided to flash the latest nightly, just leaving me with a bricked phone.
What happens right now, is:
- the phone is stuck in a boot loop. I only see the Wileyfox logo screen with "powered by android", written on the bottom of the screen.
- occasionally, the screen becomes black and the device reboots, just to get stuck again.
- pressing vol+ and power, vol- and power makes the device reboot quicker (with or without usb attached), but it immediately gets stuck again.
- I can't even turn off the phone by holding power down for 30+ seconds -- the device keeps on rebooting over and over again
Can anybody tell me how to get out of here? Just turning of the phone would help in the first place ...
Thank you, best regards!
TheWater2 said:
I decided to flash the latest nightly, just leaving me with a bricked phone.
Click to expand...
Click to collapse
How did you flash it? I got this "update" via OTA and my phone became a soft-soft brick - everything loads normally but the touchscreen doesn't work at all.
In your case, I think, there is something wrong with bootloader (but how? in LOS updates they never touch this thing) or maybe the battery is totally discharged.
I've got 2 Storms and I've seen them stuck in endless bootloop when the battery was 0% and I tried to charge them with bad charger or low-quality cable. So maybe the battery drained while updating
~FNWL~ said:
How did you flash it? I got this "update" via OTA and my phone became a soft-soft brick - everything loads normally but the touchscreen doesn't work at all.
In your case, I think, there is something wrong with bootloader (but how? in LOS updates they never touch this thing) or maybe the battery is totally discharged.
I've got 2 Storms and I've seen them stuck in endless bootloop when the battery was 0% and I tried to charge them with bad charger or low-quality cable. So maybe the battery drained while updating
Click to expand...
Click to collapse
I sideloaded the downloaded nightly. There were no error messages in TWRP log, and the battery was almost completely full.
What can be done with a wrecked bootloader? It seems I can't even get into fastboot.
(this is my real account, was unable to post out of tapatalk yesterday)
The only way is playing with vol+ and power buttons. I entered TWRP after almost 20 attempts... It's really difficult to enter fastboot or recovery via button combinations.
Flashing LOS via TWRP doesn't touch the bootloader. You can see the contents of LOS update zip-archive - there is no bootlader file, only system and kernel (boot.img). So please try using key combinations once again.
Also, constant bootloop occurs when the touchscreen is cracked, but that's not your case
~FNWL~ said:
The only way is playing with vol+ and power buttons. I entered TWRP after almost 20 attempts... It's really difficult to enter fastboot or recovery via button combinations.
Flashing LOS via TWRP doesn't touch the bootloader. You can see the contents of LOS update zip-archive - there is no bootlader file, only system and kernel (boot.img). So please try using key combinations once again.
Also, constant bootloop occurs when the touchscreen is cracked, but that's not your case
Click to expand...
Click to collapse
Thank you very much for your feedback -- highly appreciated.
After some hours of trying, I still desperately get back to you. What exactly do you mean by "playing with vol+ and pwr buttons"? Holding them together infinitely? Pressing and releasing quickly? Holding one while pressing and releasing the other?
I still have not succeeded any further from the previous stage, unfortunately ;(
krustyzy said:
What exactly do you mean by "playing with vol+ and pwr buttons"? Holding them together infinitely? Pressing and releasing quickly? Holding one while pressing and releasing the other?
Click to expand...
Click to collapse
I can't understand exactly how to get into these modes, because I can enter them only after "playing" several times. I hold 2 keys together and then the phone vibrates and I have to release them immediately, and after that it enters fastboot or recovery. But not from the first time! Sometimes it reboots again and again.
Try "playing" and if there is no result - only service would help.
If your phone doesn't enter into fastboot or recovery it may mean two things. First - you press keys in wrong way, so "playing" would help. Second - bootloader is broken or some hardware problems (e.g. cracked touchscreen, broken pwr or volume key etc.)
I hope that's the first, and finally you will enter fastboot or recovery mode.
Also you may try plugging charger.
Entering bootloader :
Press togheter vol+ and power when you see wileyfox screen release power
Entering recovery:
Vol- and power same thing for release power....
If phone don't boot ( loop ) press and hold 30 sec or more power then press vol+ or -.
Try bootloader, booting twrp on ram then flash what you want.
Fastboot boot your_recovery.img, use twrp 3.0 or 3.1
Enjoy...
Inviato dal mio Wileyfox Storm utilizzando Tapatalk

TWRP's loading screen shows up but goes into normal boot afterwards

Hi,
I'm in the process of rooting my G6 (870H) but I've been running in an issue which doesn't seem to happen to other users.
I have followed all the steps (unlocking the bootloader etc), but when I flash the twrp img, reboot (I've tried numerous times both with fastboot reboot and simply by holding the PWR + VOL- ) and then select 2 times Yes when I run into the factory reset screen it shows me the TWRP loading screen (which I guess is normal ) but instead of going into the twrp options afterwards, the phone simply boots as it usually would.
Does anyone know anything about this issue ? I couldn't find any information about it.
I had this happen, make sure after the screen goes black after booting into twrp, leave it alone. So from bootloader Volume + Power then when LG logo pops up stop pressing power but quickly hold it down again. Then when the screen changes don't press anything until booted into twrp.
If this doesn't work, I remember when I first ran into a soft bricked device. It refused to boot into twrp even though I had rooted it. Just keep trying and one time you'll get lucky, I'm not sure why this happens, but it's just part of life, so keep at it and maybe try a different twrp.

Flashed the wrong Kernel version, what now? <SOLVED>

<SOLVED>
I am still pretty new to Android and modding so be gentle..............
Should have know better. Flashed the latest Omega Kernel on my 6T while watching the kiddos practice for an upcoming belt test. I know I don't mulit task!
Flashed the Android 10 version on my Android 9 phone. Realized what I did when it would go past the bootloader unlocked warning. Eventually it went to the qualcomm dump mode then rebooted.
Now I can't get it to do anything. It is stuck on that screen. Power button does nothing. My theory is if I can get into recovery I can just flash the correct previous version of Omega that is on the phone.....but without a working power button I am stuck. Computer does not even see the phone when I plug it in.
What now?
Many thanks in advance.
Use the MSM Tool method to un brick your phone. Look for the forum in the Roms, Kernels... Section.
You're going to loose all data.
I will get over losing my data. I don't have a windows machine at the house. I will have to go to our shop to use that horrible OS. Thanks for the intel.
You can fix this issue in minutes without requiring to run MSM Tool or lose any data. I faced a similar issue myself few days ago and got it running back again by doing the follows:
Boot your device into fastboot mode, download the latest boot.img (stock or any other kernel) and TWRP and type these in command line:
1) Fastboot flash boot.img
2) Fastboot boot twrp.img
3) Your device will boot into TWRP Recovery, so flash TWRP installer zip so it sticks.
4) Reboot to recovery again and flash Magisk or Full Rom OTA.
You should be fine then.
Anwar Syed said:
You can fix this issue in minutes without requiring to run MSM Tool or lose any data. I faced a similar issue myself few days ago and got it running back again by doing the follows:
Boot your device into fastboot mode, download the latest boot.img (stock or any other kernel) and TWRP and type these in command line:
1) Fastboot flash boot.img
2) Fastboot boot twrp.img
3) Your device will boot into TWRP Recovery, so flash TWRP installer zip so it sticks.
4) Reboot to recovery again and flash Magisk or Full Rom OTA.
You should be fine then.
Click to expand...
Click to collapse
Thanks, but you missed the part where my power button is not working. The phone is stuck on the 'bootloader unlocked' warning message and the power button does nothing. No way to boot into recovery or fastboot.
PattayaGlock said:
Thanks, but you missed the part where my power button is not working. The phone is stuck on the 'bootloader unlocked' warning message and the power button does nothing. No way to boot into recovery or fastboot.
Click to expand...
Click to collapse
Is your power button broken by any chance?
If it isn't, then hold volume up + power button for a few minutes and it will reboot to Fastboot screen.
Edit: Also try volume down + power button if volume up does nothing. Make sure you hold either of the combination for a few minutes until you get a haptic feedback. Google "Boot OnePlus 6T into Fastboot mode" and follow the instructions there. Once in Fastboot, follow what I wrote in my previous reply.
Anwar Syed said:
Is your power button broken by any chance?
If it isn't, then hold volume up + power button for a few minutes and it will reboot to Fastboot screen.
Edit: Also try volume down + power button if volume up does nothing. Make sure you hold either of the combination for a few minutes until you get a haptic feedback. Google "Boot OnePlus 6T into Fastboot mode" and follow the instructions there. Once in Fastboot, follow what I wrote in my previous reply.
Click to expand...
Click to collapse
Holding the power button does nothing.
Power + down volume does nothing.
Discovered power + up button WILL turn the phone off. It also just brings it back to the "bootloader unlocked" warning page. It won't bring it to fastboot mode.
Makes sense as recovery is now part of the boot.img instead of a partition. I am assuming fastboot is also part of the boot.img. If that is the case there is no way to get into fastboot with an Android 10 kernel on my Android 9 phone. ..... I think
PattayaGlock said:
Holding the power button does nothing.
Power + down volume does nothing.
Discovered power + up button WILL turn the phone off. It also just brings it back to the "bootloader unlocked" warning page. It won't bring it to fastboot mode.
Makes sense as recovery is now part of the boot.img instead of a partition. I am assuming fastboot is also part of the boot.img. If that is the case there is no way to get into fastboot with an Android 10 kernel on my Android 9 phone. ..... I think
Click to expand...
Click to collapse
Go through my reply history. I was on 9.0.17 and had flash RadioActive kernel which was based on/for Android 10 and went into crash dump mode. Doing those steps resolved it.
Both volume buttons + power for a hard shutdown [emoji6]
Anwar Syed said:
(...) Make sure you hold either of the combination for a few minutes until you get a haptic feedback.(...)
Click to expand...
Click to collapse
Minutes? [emoji50] We don't want users dislocating their fingers [emoji51]
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
Both volume buttons + power for a hard shutdown [emoji6]
Minutes? [emoji50] We don't want users dislocating their fingers [emoji51]
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Should've said seconds, my bad, but your reply is hilarious...lmao xD
Turns out holding all 3 buttons did the trick....in a weird FUBAR kind of way.
1st time it popped into fastboot. Figured what the hell, tried to reboot, nope.
2nd time just booted back to the warning screen.....okay, freaked out again.
Got back into fastboot, flashed twrp, rebooted to the warning screen. SH*T!
Got back to fastboot, flashed twrp, damn thing booted into the os as if nothing had ever happened.
Held my breath, downloaded the correct kernel, rebooted to recovery, flashed, rebooted system. Everything is good.
Guess the a/b partition maybe?
Anyway, problem solved, headache over, NO DATA LOST.
Thank you everyone!
All 3 buttons did it....in a wierd FUBAR kind of way.
1st time fastboot popped up. Figured I would try reboot, nope.
2nd time just booted back to warning screen, uh oh.
3rd time fastboot, flash twrp, booted back to warning screen.
4th time fastboot, twrp, booted into OS like nothing ever happened.
Held my breath, downloaded the correct kernel update, recovery, flashed, rebooted and I am good to go.
Thanks everyone for your help!
Sorry for the dual post, I am in BOTARD mode apparently. Didn't see the post and thought I forgot to send......missed page 1 of 2!
PattayaGlock said:
Guess the a/b partition maybe?
Click to expand...
Click to collapse
That would be my guess. It should just switch to the functional slot if the other isn't (properly) booting but I've experienced this system to behave quite erratically. I presume these are childhood diseases of a relatively new Android partitioning system.
Back in the 'old' system all you should've done was boot to recovery (which couldn't be corrupted by the OS!) and dirty flash either a working kernel or the original (stock) ROM that includes the kernel.
Anyway, glad you retained all your data! Thanks for updating the title and OP with a solved tag
PattayaGlock said:
<SOLVED>
I am still pretty new to Android and modding so be gentle..............
Should have know better. Flashed the latest Omega Kernel on my 6T while watching the kiddos practice for an upcoming belt test. I know I don't mulit task!
Flashed the Android 10 version on my Android 9 phone. Realized what I did when it would go past the bootloader unlocked warning. Eventually it went to the qualcomm dump mode then rebooted.
Now I can't get it to do anything. It is stuck on that screen. Power button does nothing. My theory is if I can get into recovery I can just flash the correct previous version of Omega that is on the phone.....but without a working power button I am stuck. Computer does not even see the phone when I plug it in.
What now?
Many thanks in advance.
Click to expand...
Click to collapse
hello
I have the same problem with my phone, I have read all your comments about how to fix it, but I didn't understand how you fixed it, only holding the 3 bottons? and waiting to get into recovery or what?
tnx
My phone is sony xperia z1. I rooted this phone. and flashed wrong kernel after that the phone was not responding. Even though I pressed the power button, nothing appeared on the screen, please help me

OnePlus 6T - Stuck in "unlocked boot loader" screen - cannot go to fastboot mode

So I was trying to flash a rom on this phone for the first time, I failed miserably...
Was following instructions from this thread: [ROM][OFFICIAL] Omnirom Q for OnePlus6T [Every Sunday]
After flashing the omnirom.zip I immediately tried to reboot in recovery and ended-up in a boot loop (see attached image).
I tried multiple times to go back to fastboot mode with vol-up-power combination, it did'nt worked. Always boot back to that screen.
I tried all imaginable combinations of buttons and timing but always ened-up on that screen... exept just one time where I finally ended-up in fast boot.
I dont know how I did it!
So then I pushed TWRP, I saw that the ROM's files were in both partitions, wiped the data and rebooted and returned to that same "unlocked boot loader" screen.
I've been stuck here for 3 days now, I want to go back to fastboot mode so I can push TWRP and restore my nandroid backup.
Anybody knows how I can do this?
Try holding power, volume up and down all at the same time without any cable plugged in to shut it down then while holding the volume up button plug the USB cable that's connected to your computer in. It should boot to bootloader screen.
DrAgNbOi said:
Try holding power, volume up and down all at the same time without any cable plugged in to shut it down then while holding the volume up button plug the USB cable that's connected to your computer in. It should boot to bootloader screen.
Click to expand...
Click to collapse
Thanks for your reply.
Thank you so much. I had'nt tried this specific combination. It worked.
ebab said:
Thanks for your reply.
Thank you so much. I had'nt tried this specific combination. It worked.
Click to expand...
Click to collapse
No worries. Glad it works as I was in the same situation before myself.
Well I'm grateful that I was able to get the device shut down without a hot dead battery. I wasn't able to get it into fastboot by the volume up and plug in. I'm thankful it's off. Do you have any other ideas Im not concerned about data at all. I just would like to get my device back up and running..
Please help me out! Thanks

Categories

Resources