Database Develop

Can't get into Flashmode or Fastboot, Can get into recovery

So I bought this Xperia SP off a friend, It had the ExistenZ 3.0.0 Rom and I updated it to the 3.3.0 OTA version. Obviously this means I can get into both recoveries that come with the ROM TWRP and Philz. I want to go back to stock now but I can't flash the stock .tft with flashtool or SUS because I can't get into Fastboot or Flashmode. When I plug the cable in and hold Vol + to get into Fastboot it does nothing and just boots normal. When I hold Vol - the main green led comes on like it should, I get an error on the PC saying the device cannot be recognised and it has malfunctioned before it could be connected and then the Green LED goes off after around 5 seconds and then it restarts and continues to boot normally. However once the main boot sequence has started I can get into the recoveries using the Vol +/- and I can flash ROM's. Is this a kernel issue ? Also I think there maybe a loss of baseband because I keep getting that no sim can be recognised but I'm unsure which is why I want to go back to stock. I also can't see if my bootloader is locked or not because the service menu app crashes when I try to see :/ It never actually gets into fastboot or flashmode.
What I'm asking is, How and if I should try and flash the stock kernel to see if I can get the FastBoot and FlashMode back.
I have Windows 8 and have installed the correct drivers by disabling signature enforcement.
Edit: I can see that it is actually trying to get into flashmode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks in advance guys

Ricehead said:
Snip
Click to expand...
Click to collapse
Solved after repeating the driver installation process etc on a different PC (My samsung tablet :/ ) Please Close

[Q] [q&a] htc one mini 2 bricked bad

First sorry for my bad english, I´m new here, but I have flashed a TRWP Recovery for this device and I have rooted it, but when the device runs out off the battery, It get stuck in this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The device doesn´t start, don´t turn off, and when I tried to start it into the bootloader mode the adb says that it is unauthorized.
Please some help.

yulian6766 said:
First sorry for my bad english, I´m new here, but I have flashed a TRWP Recovery for this device and I have rooted it, but when the device runs out off the battery, It get stuck in this...
The device doesn´t start, don´t turn off, and when I tried to start it into the bootloader mode the adb says that it is unauthorized.
Please some help.
Click to expand...
Click to collapse
it seems you recovery its corrupted. flash it again.
charge device for a while them remove USB cable before power on. (TRWP bug)
power and vol+ for 10s to restart device.

kativiti said:
it seems you recovery its corrupted. flash it again.
charge device for a while them remove USB cable before power on. (TRWP bug)
power and vol+ for 10s to restart device.
Click to expand...
Click to collapse
It works! but you are right the recovery image were corrupted, and fix it flashing again, thanks a lot.

OPO stuck on recovery mode loop and PC won't recognise it in order for me to flash it

So recently I did a stupid and accidentally switched off my OPO during an update installation and completely screwed it all up. I tried switching it back on only to find that it was stuck in a recovery mode loop. I then hit factory reset in a last ditch attempt to save the poor bugger without flashing it and even that didn't work.
I've then had to resort to flashing it using the OPO toolkit software on my PC however when connecting to the PC, my OPO only shows up as an MTP USB Device and nothing else. I have tried installing recommended Samsung drivers for the phone but I wasn't able to as it the "update drivers" button was greyed out on the MTP USB Device properties window.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically, the OPO toolkit will not work as no android devices are recognised by the PC even though an android device is showing up in the control panel.
There is no way I can currently access the settings on my phone due to recovery mode loop obviously.
The last thing I want to do here is end up with being forced to use the OnePlus support which I hope most of you understand why.
Thanks for any suggestions!

Hi,
This thread is being moved to your own dedicated forum , where the experts may be able to help you better.
Good luck!

Put it in downloading mode and then use adb to use the toolkit since bow u don't have a os on the OPO happened with me too but I fixed it this way
Sent from my A0001 using Tapatalk

Question Fastboot stuck on "waiting for device". Whatever OS I use.

Hi there,
I have just purchased a Zenfone 8, the bootloader is unlocked (I have the ugly message saying that the phone can"'t be trusted because bootloader is unlocked bla bla bla at startup).
However, while adb works, I can't get fastboot to recognize my device.
I tried on W10 and 11, also on Linux Mint.
Other phones are recognized properly by fastboot, but not the zenfone 8. And of course, fastbootd doesn't work.
Anyone faced this issue?
Thanks,
Anghi

Look inside here:
Fastboot Mode ASUS Zenfone 8, how to - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I can get into fastboot mode. Using combo key or even "adb reboot bootloader". But on this screen, then fastboot does not recognize the device
And I have tried both bootloader (in principle fastboot) and fastbootd (the one within the recovery) screens. Fastboot commands don't work under both screens.

I think to get fastboot working I had to install the Asus specific driver on my pc

Ok thanks. Let me try.

Okay, solved by trying several USB C wires.
Thanks for the advices and help!

ADB can't find my device in fastboot

Hi,
I want to flash TRWP onto my REDMI 8. However, as soon as I boot into fastboot, adb shell can't find my device anymore.
I've tried everything, installing new Fastboot drivers in Device Manager, new USB cable, other USB port, nothing works. ADB finds my phone in normal mode, but not in fastboot mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try waiting a little longer for it to register your device also make sure that usb debugging is on and that all the latest drivers for your phone are installed on your pc

Na, it won't register, it doesn't find the device.
USB debugging is on.
I've even installed the Xiaomi Tool V2, which supposedly has all the right drivers.

in fastboot mode, its fastboot devices and not adb ;P
if that also fails, try clockwork mod (cwm) universal adb drivers. worked for me for all these years including this phone
also, there are still plenty of roms available iirc, in case they dont show up for olive, you might be able to try mi439

Since you're in Windows, when you plug it in it might/should "bong".
Then you have to find out what is there and whether it has a driver.
ADB and fastboot are usually mutually exclusive.
You might try looking deeper with UsbView.exe https://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBView
Or you could look in Device Manager C:\>devmgmt.msc
Or you could shell out >$1000 for a hardware USB protocol analyzer.

I got it to work now, thx. Starting from ADB into Fastboot didn't work, but manually booting into FB and the installing twrp did the trick.