Database Users

help motorola bravo

My motorola bravo was being updated when it became a brick. The phone comes on and puts a red M and there does not advance. You can not do the recovery. I need an idea of how to revive it. And try to install but nothing happens sbf reposition the M and there does not happen.

comeranas said:
My motorola bravo was being updated when it became a brick. The phone comes on and puts a red M and there does not advance. You can not do the recovery. I need an idea of how to revive it. And try to install but nothing happens sbf reposition the M and there does not happen.
Click to expand...
Click to collapse
did you boot into bootloader (by holding power + volume up) and then apply the sbf?

and remove your battery and reinstall it.

If I've done both and what comes out is only the red M

comeranas said:
If I've done both and what comes out is only the red M
Click to expand...
Click to collapse
your not holding the vol up earlier enough do the following:
1) take out the battery
2) press and hold down the vol up button
3) w/o releasing rhe vol up button, put the battery in.
4) within 3 seconds a black screen will come up with white text.
5) do the sbf
i have bricked the bravo so hard during development and always been able to get to a bootloader screen. one time i bricked so hard it went directly to the bootloader, so you def. can get in to sbf, unless you vol rocker is broken, then you may be screwed. in that case plug int he phone, let it bootloop and try to start the sbf, it might reboto into bootloader for you, but probably not.

bandroidx said:
your not holding the vol up earlier enough do the following:
1) take out the battery
2) press and hold down the vol up button
3) w/o releasing rhe vol up button, put the battery in.
4) within 3 seconds a black screen will come up with white text.
5) do the sbf
i have bricked the bravo so hard during development and always been able to get to a bootloader screen. one time i bricked so hard it went directly to the bootloader, so you def. can get in to sbf, unless you vol rocker is broken, then you may be screwed. in that case plug int he phone, let it bootloop and try to start the sbf, it might reboto into bootloader for you, but probably not.
Click to expand...
Click to collapse
I manage to load the bootloader and the sbf but when the phone is restarted only relocate the white with red M

comeranas said:
I manage to load the bootloader and the sbf but when the phone is restarted only relocate the white with red M
Click to expand...
Click to collapse
so then you should reboot holding vol down and then the recovety will load.
hit vol up and vol down at the same time to load options.
then wipe cache and wipe data.
wiping data is prob only way u can fix it if you already successfully flashed the sbf.

bandroidx said:
so then you should reboot holding vol down and then the recovety will load.
hit vol up and vol down at the same time to load options.
then wipe cache and wipe data.
wiping data is prob only way u can fix it if you already successfully flashed the sbf.
Click to expand...
Click to collapse
Thanks for the help.
perform the sbf file down twice again but the phone only puts the M, will not let me enter recovery, I think it is a complete brick and not know what else to do.
Too bad there is no sbf2.1 for testing.

hmmm, unless you are going straight to a bootloader screen you should still be able to enter recovery. my only guess is the update was in the middle of updating your recovery when something went wrong and the recovery image is corrupt.
sbf not working plus no access to recovery sounds like a real true brick possibly.
make sure you hold down the vol down and w/o letting go you put the battery in, when you are in this bootloop that is the only way to be sure you get in to recovery.
what happens when you hold down vol down and put the battery in? does it do anything different at all?

bandroidx said:
hmmm, unless you are going straight to a bootloader screen you should still be able to enter recovery. my only guess is the update was in the middle of updating your recovery when something went wrong and the recovery image is corrupt.
sbf not working plus no access to recovery sounds like a real true brick possibly.
make sure you hold down the vol down and w/o letting go you put the battery in, when you are in this bootloop that is the only way to be sure you get in to recovery.
what happens when you hold down vol down and put the battery in? does it do anything different at all?
Click to expand...
Click to collapse
The phone was damaged because it was downloaded in the middle of an upgrade.
when I hold the power and volume down, I put the battery and three seconds later reappears M, does not load the recovery.
I think I'm going to give up.
May be taking it to a store at & t service, can do something?

Take it to the at&t store. Since it is so badly damaged due to the update "failing" they can replace it with warranty
Sent from my X10i TripNMiUI using XDA Premium App

I'm a rep @ an AT&T corporate location. Yea, if that update failed, we take care of it. I assume you're referring to the OTA 2.2.

Reviving an old thread as where comeranas left off is where I am at.
Wife has a new phone already so I am just trying to revive this one. If not, it goes into garbage.
The screen has been powering up to the Motorola logo only. I can hold the volume up and power button to get to the bootloader/usb screen.
I cannot get to the recovery screen by holding the volume down and power button. No matter how many times I try and in what combination, it always powers up to the Motorola logo.
I ran the sbf file on it twice with RSD Lite and each time when it gets to the part of re-booting it says "Phone is being rebooted."
Then after the progress gets to a 100%, it says, "Please manually power up this phone."
The Motorola logo is on the screen and I have tried to simply push the power button, pull the battery and re-insert it and pull the battery, hold the volume button down and re-insert the battery all while still hooked up to the computer.
After a few minutes the Results box says Passed. But the phone still goes no further than the Motorola logo.
So as of now, the phone still only powers up to the Motorola logo and goes no further.
Naturally it had to start acting up 2 weeks out of warranty. Dang blang warranty timers installed in these phones. lol!

You can try sbf_flash on Linux and both the full and fixed sbf with it. I'm on phone now, so I can't give good instructions or links, but sbf_flash is around in one of the recovery threads here, and the fixed sbf is at quarx2k.ru and my rom mirror (see signature).
If you need it, I can make a Linux Live tutorial for sbf flash, only requirement would be 512mb usb stick or memory card.
I once had to flash sbf 3 times in a row to fix a brick from an accidental Defy kernel flash in cwm.

So the sbf files you are referring to are different than the 2.2.1 sbf file HERE?
I don't run Linux on my comp.
I'll look at the fixed sbf file in your sig. Maybe I just need to run it over and over again until the phone pops. lol! Thanks.

FirePro911 said:
So the sbf files you are referring to are different than the 2.2.1 sbf file HERE?
I don't run Linux on my comp.
I'll look at the fixed sbf file in your sig. Maybe I just need to run it over and over again until the phone pops. lol! Thanks.
Click to expand...
Click to collapse
The fixed sbf contains the bootloader and kernel and it for when you write to either of them and need to reflash back to stock. Handy for when you accidentally flash a Defy from with a boot.img
You don't have to install linux, just use a Live CD and place sbf_flash and the sbf files on a memory stick. Once the Live CD boots, the memory stick should be on the desktop. Open the folder and right click "Open Terminal Here". In the terminal first type:
su
then
chmod 0777 ./sbf_flash
then
./sbf_flash ./fixed_bravo_sbf.sbf
or
./sbf_flash ./p4_kobe_umts_kobe_user_3.4.2-125_KOB_FFW-4_product-keys-ATT-US_ATT-signed.sbf
Just download one of these for your pc's architecture, if you're unsure, then any of the 32-bits will work.
http://www.linuxmint.com/download.php
The reason I suggest using sbf_flash and Linux is that its supposed to fix phones that sbf flashing with RDS Lite won't fix, and it'll flash files that RDS won't like modded root sbfs. Apparently it flashes differently. Don't ask me the difference cause I don't know.
Good Luck.
You said that you couldn't get to the Stock recovery menu, your volume button isn't broke is it? And have you tried up+power and down+power? Kicking it? JK, but throwing my old razr flip phone into the couch as hard as I could used to fix it....it would freeze on boot, but a good toss and it was good as new.

Thanks, gonna give it a try.
I am kinda wondering at this point if the down volume is broke. Though if it was, she would have said something about it before it went down.
I did smack it a few times to no avail. lol!

[Q] Cant Get into AP Fast Boot!

I accidentally,... . unknowingly wiped the RED "system" button in Safestrap 3.12 on my Droid RAZR M today. (I was suppose to be wiping the cash and dalvik, but missed) I'm a retard I know. :crying:
Now I cant get into AP Fastboot to restore the phone from this hard brick!
When I press the power button along with the volume buttons, the only thing that happens is the red Motorola 'M" appears for a few seconds then the safe strap screen appears with the little sad robot, but that's it no AP Fastboot. Pressing the on screen buttons to enter Safestrap Recover do not respond. Oh boy I'm afraid I really did it this time. Its on the charger but i don't know if its even charging with out as OS?
Battery power was at 60% before i bricked it (i think). RSD Lite or my PC for that matter don't even see the phone when its plugged in.
Can this be saved? Or do I need to take a trip down to the Verizon Wireless store?
Droid RAZR M
4.1.2 OTA
Rooted
Locked Bootloader
Safestrap 3.12
Partitioned 64GB SD card utilizing Linked2SD

You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2

sloosecannon said:
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Really? Well I hope your right. It gives me some hope. lol So do you have any idea of what alternative key combo i might have to use? Thank you for the reply.

Try holding power & volume down until the screen flickers then hold power and both volume buttons. You gotta be quick
If your boot loader is locked you won't be able to fast boot back until the new fast boot files come out though if your on 4.1.2

http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:

sloosecannon said:
You need a different key combo to get into fastboot. You're not permabricked tho - that's just a really bad softbrick
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! You were right! was able to get into AP Fastboot with a different button combo like u said. :victory:

shane1 said:
Try holding power & volume down until the screen flickers then hold power and both volume buttons. You gotta be quick
If your boot loader is locked you won't be able to fast boot back until the new fast boot files come out though if your on 4.1.2
Click to expand...
Click to collapse
Shane you were right on the money brother!!! Thank you so very much. It worked perfectly. I'm up and running again.
much respect

bigrob1015 said:
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
Click to expand...
Click to collapse
It worked! I utilized the NEWER version of Mat's utility and it did it!!! Woo Hoo!! Thank you so very much. Thank you all for all the speedy help.

SARM1084 said:
Shane you were right on the money brother!!! Thank you so very much. It worked perfectly. I'm up and running again.
much respect
Click to expand...
Click to collapse
hey no prob! i try to help as much as i can !

bigrob1015 said:
http://forum.xda-developers.com/showthread.php?t=2207419&page=2
go to the last page new tools and utilities up from matt and it works just unbricked me be sure to thank him :good:
Click to expand...
Click to collapse
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min

Halp
This thread saved my life, then killed me. The suggestion about the different keys was spot on, i got into fast boot mode, then ran that utility. It totally failed me, I must have killed my phone pretty dead, and now there are no more key combos (the suggested one worked at first but now its just making the screen go blank) to try to get back into fast boot to try again. any more suggestions? on the up side verizon just pushed that update so i figure i can blame that to attempt an exchange

Did you take the update before using that utility? If you did, which version did you use? If you were already updated, then you needed to run 1.20. If you ran the wrong utility, that will cause issues. Now, since you can't boot, it sounds like your battery is dead. When you get to the blank screen, plug it in and leave it to charge for a while.

I'm no expert by any means but I'll try to help as best i can. If not me I'm confident someone else will. Now, I apologize because I didn't understand your original post.
Could you elaborate a little more please?
1. What were you trying to do with your phone prior to things going wrong, if they went wrong at all.
2. you mentioned AP Fastboot. So IM going to assume that at least you can access it. (not the same problem that I was having) that's a good thing! lol
3. Are you utilizing a utility like the one by Matt? Or are you doing something else? Like flashing firmware etc.
4. What were you in Fastboot for? What were your intentions?
I hope this doesn't come over a condescending. Just trying to get a Clearer understand of your issue so we can help.
Sent from my XT907 using xda app-developers app

Sorry double post

PartyOnINSANE said:
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Click to expand...
Click to collapse
Look at my previous post
Sent from my XT907 using xda app-developers app

Sorry, my post musnt have updated. As you can see I managed to fix my problem. If there's any issues in the future for anyone I will be sure to advise as best I can.
Sent from my XT907 using xda app-developers app

PartyOnINSANE said:
Sorry, my post musnt have updated. As you can see I managed to fix my problem. If there's any issues in the future for anyone I will be sure to advise as best I can.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No problems brother. Glad to see your up and running.
Sent from my XT907 using xda app-developers app

Stuck in a Boot Loop
PartyOnINSANE said:
New to this, i accidentally the whole phone, same problem im in AP fastboot but registers as Device Locked
run through it on windows OS but says 'Fastboot" is not recognized as an internal or external command" and doesnt reboot as said
this process took 1min
Click to expand...
Click to collapse
Could you help me please?
I changed 2 lines in my build.prop file so i could see if I could get touchless control.
After I changed it, I restarted my phone. Now it is stuck in the Red M Boot, and it stays there, dosent black screen, dosent boot. I can get to the boot selection menu, but i cant choose anything, they all end up at the Red M. I Read that I can fix it in AP Fastboot, but I can get there. Also if i force it off (with power button and volume button) It just goes back to the Red M.
Everything I do ends up at the Red M
Help fast please, its my only phone, and I just got rid of my house phone
I have a
Droid Razr M
Rooted, no custom Roms or Recovery.
Changed my build.prop from XT907 to XT1087
Changed My Boot Animation to R2D2
A: 4.1.2
8gb Sd card on it.

gjhkl said:
Could you help me please?
I changed 2 lines in my build.prop file so i could see if I could get touchless control.
After I changed it, I restarted my phone. Now it is stuck in the Red M Boot, and it stays there, dosent black screen, dosent boot. I can get to the boot selection menu, but i cant choose anything, they all end up at the Red M. I Read that I can fix it in AP Fastboot, but I can get there. Also if i force it off (with power button and volume button) It just goes back to the Red M.
Everything I do ends up at the Red M
Help fast please, its my only phone, and I just got rid of my house phone
I have a
Droid Razr M
Rooted, no custom Roms or Recovery.
Changed my build.prop from XT907 to XT1087
Changed My Boot Animation to R2D2
A: 4.1.2
8gb Sd card on it.
Click to expand...
Click to collapse
Holding the combination of buttons will only cause it to reboot, every time. Holding the power button down will make it shutdown. With that being said, what was your battery like before you started all of this? If it's below 50%, you're going to have a hard time. Shut the phone down and charge the battery ovenight, prior to attempting to fastboot.
If your battery is good, then you can fastboot. Hold all three buttons down, until you get the phone to power off. As soon as power goes off, you'll see a quick line flash at the top of the screen. As soon as you see this flash, quickly let go of the power button and then re-press it. If you got it right, you'll go into the fastboot menu. If you got it wrong, it will attempt to reboot. If it reboots, just try the button combo again. Once you get into the fastboot menu, use the vol- key to get to the option you need, and then hit the vol+ to choose that option.

RikRong said:
Holding the combination of buttons will only cause it to reboot, every time. Holding the power button down will make it shutdown. With that being said, what was your battery like before you started all of this? If it's below 50%, you're going to have a hard time. Shut the phone down and charge the battery ovenight, prior to attempting to fastboot.
If your battery is good, then you can fastboot. Hold all three buttons down, until you get the phone to power off. As soon as power goes off, you'll see a quick line flash at the top of the screen. As soon as you see this flash, quickly let go of the power button and then re-press it. If you got it right, you'll go into the fastboot menu. If you got it wrong, it will attempt to reboot. If it reboots, just try the button combo again. Once you get into the fastboot menu, use the vol- key to get to the option you need, and then hit the vol+ to choose that option.
Click to expand...
Click to collapse
I have done your steps and I get the menu up, but when I try to scroll down with the volume down button, it doesn't move. It just stays on "normal powerup". How can I fix this?

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.

Bricked my XT907

I bricked my XT907 and it won't boot. When I power it on, it goes to the red Motorola logo and after about 10 seconds or so, it disappears like it usually would, but nothing happens. I managed to figure out how to boot into one of the recovery modes...Yes there are two: The alleged universal Droid Master reset and Motorola's...or Verizon's?
Method one: I boot into the recovery screen (NOT the Droid one) by pressing and holdiung FIRST, volume up, then volume down and power. I hold all three for a few seconds and the Motorola logo comes up. I then release the power button and up comes the recovery screen which gives me the options I need to reset. I scroll to reset and press power (enter) and nothing happens. I then press volume up, according to Verizon's site and it just boots back to the red Motorola logo. I try this again and I can't select anything from the menu.
Method two: I do the same above steps until I get to the same recovery screen. I press volume up again and back to Motorola logo. Press and hold volume up and power until it boots to the Droid screen with an '!'. I AM able to select options. So I select factory reset, it goes through the steps and back to the menu. No errors. I select reboot and it does it's thing, the Motorola logo pops up then 10 seconds, disappears and again nothing.
Method three: Volume up and hold power. Screen goes to fastboot mode. I plug it into the PC and enter ADB terminal...
fastboot devices
Device and serial listed
fastboot erase userdata
Bootloader repeats itself 3 or 4 times and tells me the action isn't allowed. Then to test my patience even more, i goes through the steps of erasing the device, and tells me it's completed its task even though it really hasn't.
At this point I am pretty sure there's no recovering from this. Any advice, besides telling me to get a new phone?

DragonFire1024 said:
I bricked my XT907 and it won't boot. When I power it on, it goes to the red Motorola logo and after about 10 seconds or so, it disappears like it usually would, but nothing happens. I managed to figure out how to boot into one of the recovery modes...Yes there are two: The alleged universal Droid Master reset and Motorola's...or Verizon's?
Method one: I boot into the recovery screen (NOT the Droid one) by pressing and holdiung FIRST, volume up, then volume down and power. I hold all three for a few seconds and the Motorola logo comes up. I then release the power button and up comes the recovery screen which gives me the options I need to reset. I scroll to reset and press power (enter) and nothing happens. I then press volume up, according to Verizon's site and it just boots back to the red Motorola logo. I try this again and I can't select anything from the menu.
Method two: I do the same above steps until I get to the same recovery screen. I press volume up again and back to Motorola logo. Press and hold volume up and power until it boots to the Droid screen with an '!'. I AM able to select options. So I select factory reset, it goes through the steps and back to the menu. No errors. I select reboot and it does it's thing, the Motorola logo pops up then 10 seconds, disappears and again nothing.
Method three: Volume up and hold power. Screen goes to fastboot mode. I plug it into the PC and enter ADB terminal...
fastboot devices
Device and serial listed
fastboot erase userdata
Bootloader repeats itself 3 or 4 times and tells me the action isn't allowed. Then to test my patience even more, i goes through the steps of erasing the device, and tells me it's completed its task even though it really hasn't.
At this point I am pretty sure there's no recovering from this. Any advice, besides telling me to get a new phone?
Click to expand...
Click to collapse
see how to unbrick with RSD Lite
[INDEX] Motorola Droid Razr M (2015)
Sent from my XT1254 using Tapatalk

sd_shadow said:
see how to unbrick with RSD Lite
[INDEX] Motorola Droid Razr M (2015)
Click to expand...
Click to collapse
From what I understand, the bootloader is locked and cannot be unlocked (So long as Motorola and or Verizon hold the codes and or files hostage). So I can't flash anything unless the files I'm attempting to flash, are officially signed by Motorola.
Nonetheless, I will look at it when I get home from work and give it a shot. About the only thing I've been able to do is wipe the data through the Droid with the '!', allegedly. I'm not even sure that worked. If it did, it's been wiped twice. I guess the positive part if there is one; I have been able to keep it booted and powered on in fastboot, only connected via USB though.

DragonFire1024 said:
From what I understand, the bootloader is locked and cannot be unlocked (So long as Motorola and or Verizon hold the codes and or files hostage). So I can't flash anything unless the files I'm attempting to flash, are officially signed by Motorola.
Nonetheless, I will look at it when I get home from work and give it a shot. About the only thing I've been able to do is wipe the data through the Droid with the '!', allegedly. I'm not even sure that worked. If it did, it's been wiped twice. I guess the positive part if there is one; I have been able to keep it booted and powered on in fastboot, only connected via USB though.
Click to expand...
Click to collapse
RSD Lite works with locked bootloader
Sent from my XT1254 using XDA Labs

sd_shadow said:
RSD Lite works with locked bootloader
Click to expand...
Click to collapse
Yes. It does...well did. It took me a few tries to get it into fastboot. Hooked it up to USB as soon as the screen came on. I missed I step or two the first time I tried to flash it. When it got past step 10 during the process, I was excited. Worked perfectly. Thank you so much. As old as this one is, it's been my favorite to tweak and 'hack.' thanks very much for your help :highfive:

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