Database Users

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 Storm

Hello, I have a problem with my storm. Two days ago I received it and flashed the then latest cm13 and its corresponding recovery. Everything seemed to work just fine until yesterday when there appeared to be an ota update. After the download finished, the phone rebooted itself and is since then stuck with a black flickering screen. Every attempt to start the phone using recovery or bootloader seems to fail, as the phone keeps showing me the black flickering screen, no matter the combination of keys (vol+/vol-) I use to turn it on. If during the black screen I plug the phone to the computer adb can actually see the phone but says it's not authorized to perform any command. On the other hand fastboot won't even see the device.
Is there anything else I can try before sending it back to wileyfox?
Thank you in advance

I've made some progress, I found out that the device can be forced to Qualcomm HS-USB QDLoader 9008 mode by turning it off and then connecting it to usb while holding vol+ and vol-.
I've also found the stock firmware at https://cyngn.com/support.
Now it would be great if somebody could help me, and the others in my situation, to figure the wole QFIL unbricking out, because I'm overwhelmed, and can't seem to find the right info on google.
Thanks to anyone who'll care to help, or share some info

I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.

miSAKe said:
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.
Click to expand...
Click to collapse
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.

maxxie00 said:
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
Click to expand...
Click to collapse
Sorry to hear you are still having trouble, it does sound like the same issue, was a CM13 update from the last couple of days, upon reboot I saw the wileyfox logo but when the Cyanogen logo would normally show during boot it displayed a black screen, which would flicker every few seconds. Holding vol- and power to reboot resulted in the same thing so I was unable use recovery.
When the display was black and connected via USB I was able to see the device using ADB but like you no commands were authorised.
Leaving the phone plugged in via USB and holding down vol+ and power until it rebooted I was able to enter fastboot, once the fastboot prompt was displayed on the screen I attempted using fastboot to boot from a custom recovery, unfortunately that just resulted in the same blank screen for me. I also tried booting the stock recovery with the same result, I admit I did not try many older CM recoveries, but I wanted to revert to CM12.1 anyway, as the accelerometer and gyroscope not working in CM13 at the moment is no good for me.
Only thing that worked was a stock restore, so I think something beyond the recovery got broken as you could not even boot a previously working recovery.
For the sake of sanity it may be work getting someone else try booting it into fastboot before resorting to Wileyfox support. Though your phone is really new so could claim a refund or replacement from the seller, that would probably be faster.
FYI if you do end up sending it to Wileyfox support they do flash it back to stock, I had a broken screen replaced, was repaired and back to me in just under 2 weeks.

What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot

maxxie00 said:
What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
Click to expand...
Click to collapse
Hi,
Just tried a few combinations to check timings for you.
Powered off, not plugged in, holding vol+ while plugging in phone end of usb connected to computer, keep holding vol+ -> boots straight to fastboot.
Powered on, already connected to computer via usb, holding vol+ and power, release power when vibrates to indicate reboot but keep holding vol+ -> boots straight to fastboot.
Are you seeing the black and white Wileyfox logo when first booting? When going to fastboot it should skip that. If you are not seeing the logo it might not show the fastboot screen either. You can try following the steps above and then issuing fastboot devices from a command/shell session to see if you are in fastboot mode.
I hope that is of some help.

Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...

maxxie00 said:
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...
Click to expand...
Click to collapse
No problem, I hope you have more luck with the replacement.

Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you

maxxie00 said:
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
Click to expand...
Click to collapse
Hello again,
So these 5 methods work for me, someone else may have other experiences:
Phone powered off, hold vol+ while connecting USB, other end of USB already plugged into PC, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on, already connected to USB, other end of USB already plugged into PC, hold vol+ and power until reboot vibrate, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on and in OS, already connected to USB, other end of USB already plugged into PC, debug enabled, from ADB console, adb reboot fastboot or adb reboot bootloader
Phone powered on and in OS, advanced reboot options turned on, hold power, select reboot, select bootloader, reboot
Phone powered on and in Recovery, select reboot to bootloader
Currently I am running stock everything.
Perhaps try different USB cables or ports, though I still get to fastboot without the USB cable plugged in.
My Storm was a pre-order so is one of the first releases, it is possible they have changed something since.
Edit: I have come across a thread on the Cyanogen forums which implies this may be related to encrypting your device: http://forum.cyanogenmod.org/topic/117661-bootloader-hangs/ - I see you have been there already
as reference mine is not encrypted at the moment

[Solved] Moto G4 Plus hard bricked after rooting : won't detect qhsusb

I tried rooting Moto G4 Plus and just after flashing the supersu and rebooting, it got bricked. Nothing shows except LED blink while connecting to PC/charger. Also, it won't detect in the device manager as a qualcomm device/qhsusb bulk or anything... I seriously need your help. Please help.
PS: I surfed over various related threads and all of them required the device to be detected on PC.

1) are you able to power off your device, then hold down the power and volume down keys? Does that boot you into the bootloader?
Or can you hold the power button for 1-2 minutes to force a hard shutdown, then attempt to boot into the bootloader?
2) did you flash a custom kernel before attempting to root? On stock Nougat for our device, you need a custom kernel.

The device is already in the switched off stage. When I press and hold the power button, nothing happens. When connected to USB cable, the front LED blinks. Nothing more. It doesn't return any sound or indication while connecting to PC. I tried installing various Qualcomm drivers to get it detected on PC. The Windows device manager shows nothing.
I tried this tutorial to root my device. I missed flashing the elementalx kernel during the root process. it caused the brick.

technorajeev10 said:
The device is already in the switched off stage. When I press and hold the power button, nothing happens. When connected to USB cable, the front LED blinks. Nothing more. It doesn't return any sound or indication while connecting to PC. I tried installing various Qualcomm drivers to get it detected on PC. The Windows device manager shows nothing.
I tried this tutorial to root my device.
Click to expand...
Click to collapse
That tutorial should work, provided you flashed the ElementalX kernel before rooting.
Hmm, what happens if you try to boot by holding down both the power button and the volume down key at the same time? You should still be able to boot into the bootloader (with the AP fastboot secure mode).
What TWRP and SuperSU did you try to flash?

echo92 said:
That tutorial should work, provided you flashed the ElementalX kernel before rooting.
Hmm, what happens if you try to boot by holding down both the power button and the volume down key at the same time? You should still be able to boot into the bootloader (with the AP fastboot secure mode).
What TWRP and SuperSU did you try to flash?
Click to expand...
Click to collapse
I used twrp and supersu as exactly as mentioned in the root thread (twrp-3.2.1-0-athene.img & phh's supersu).
The key combo doesn't work either. No response. Is there any way to get it detected on PC?
I previously had it happened on my Yureka and I had to short the board to get it detected as a qcomm device.

technorajeev10 said:
I used twrp and supersu as exactly as mentioned in the root thread (twrp-3.2.1-0-athene.img & phh's supersu).
The key combo doesn't work either. No response. Is there any way to get it detected on PC?
I previously had it happened on my Yureka and I had to short the board to get it detected as a qcomm device.
Click to expand...
Click to collapse
That's odd, as that key combo should get you booting to the bootloader (as in the tutorial), which should then get your device detected via fastboot. Did your bootloader look similar to this when you were flashing TWRP?
https://plus.google.com/photos/106899236533864901773/album/6441285188929274337/6441285190332216978
If your device is still on, try a hard shutdown (hold power button 1-2 minutes until shutdown, verify it's off by connecting power, you should see the charging symbol come on), then boot by holding volume down and power at the same time.
You could also try a hard reboot https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/110630/p/30,6720,9687

I just found that the volume down key is broken. I hope that's the reason it won't boot to the bootloader. Let me fix it first and try your suggestion.
And yes, the bootloader menu was the same as shown in this pic.
Thanks a lot for your time bro. Much appreciated.

echo92 said:
That's odd, as that key combo should get you booting to the bootloader (as in the tutorial), which should then get your device detected via fastboot. Did your bootloader look similar to this when you were flashing TWRP?
https://plus.google.com/photos/106899236533864901773/album/6441285188929274337/6441285190332216978
If your device is still on, try a hard shutdown (hold power button 1-2 minutes until shutdown, verify it's off by connecting power, you should see the charging symbol come on), then boot by holding volume down and power at the same time.
You could also try a hard reboot https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/110630/p/30,6720,9687
Click to expand...
Click to collapse
I just disassembled the phone and flipped the volume rockers so that the volume down should work fine. Then pressed and hold vol - & power button. Violaaa. Got into the bootloader. On TWRP, Just wiped data and flashed the ElementalX followed by SuperSU. It's working super fine now. A billion hugs for your support.

N7 (tilapia) stuck at logo - no fastboot access ...

Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad

Conrad-007 said:
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Click to expand...
Click to collapse
Hi, Conrad-007...
This is very strange - your Nexus 7 is clearly 'bootable' (sort of), with a functioning bootloader, ie., it's not hardbricked... or you wouldn't be seeing the Google logo.
In the distant past, back when I used to experiment with custom kernels on my Nexus 7, it sometimes required the POWER BUTTON+VOL DOWN buttons be pressed and held down for a good 30 seconds or more, to generate the necessary 'interrupt', and force the device into the bootloader.
My first instinct, is to suggest you may possibly have a problem with your VOL DOWN button, and maybe it's stuck somehow or not making contact.
It also occurred to me, that you might be able to access the bootloader with...
Code:
adb reboot bootloader
...or possibly...
Code:
adb reboot fastboot
...and even...
Code:
adb reboot recovery
But unfortunately, I'm pretty sure you need to be running fully booted Android or booted into a custom recovery (eg., TWRP) before you can issue ADB commands. I haven't tinkered around in this area of Android for a couple of years now, so my memory of the specifics is a little hazy.
Anyhow, here's a fairly comprehensive listing of Nexus 7 button presses/interrupts, which maybe of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
--------------------------------
Anyway, just some thoughts that might give you some clues/ideas, that may resolve your problem.
Good luck, and I hope you find something that works.
Rgrds,
Ged.

Thanks Ged for the detailed answer.
Unfortunately it seems that my Nexus is not booting complete (not finishing the booting sequence due to corrupted bootloader?) and so I cannot send to it any adb or fastboot command...
I read in the meantime that holding the VOL up button while powering up the Nexus, it will bring it in the APX mode (whatever this mean) and indeed, my computer recognize it as "APX" device.
I hope at least that this is a good sign and a first step to bring my Nexus back to life... but I have no idea what is the APX mode and what can I do in this mode to attempt to save my device...
Do you (or somebody else) have (has) an advice or tutorial for me concerning this?
Regards,
Conrad

Hi Conrad.
I'm in exactly the same situation (I've mistakenly posted a duplicate thread here https://forum.xda-developers.com/nexus-7/general/bricked-tilapia-t4005149). Let's continue here. So:
1. I spent 4 hours trying all possible button press combinations, including VERY long presses. I didn't notice any APX device or Uknown device connected to Windows. I might have missed it, you gave me hope. I will check again.
2. APX mode enables low level access to the chipset via nVidia tool nvflash. You probably came accross these threads here on xda:
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-using-t3342364
https://forum.xda-developers.com/showthread.php?t=2564615
https://forum.xda-developers.com/showthread.php?t=2455927
https://forum.xda-developers.com/showthread.php?t=2340237
I haven't so far, as I was not aware of the visibilty of the tablet in Windows. I will check again.

Well, I must have been blind not to have seen all the posts here on xda and everywhere else. I went through the threads and now I know:
1. I can see the tablet in APX mode in Windows. Possibly I could correctly set up the driver.
2. This would be totally useless, since I hadn't backed up necessary blob.
I have a new paperweight

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