Database Develop

[Q] 4.4 OTA bricked - fastboot inaccessible !

I had android GE 4.3 on it, rooted.
I have the original GE bootloader (that robot) installed.
I downloaded the official 4.4 update through android, rebooted for install.
Now after the install the phone does not boot up anymore, instead it goes into RECOVERY and shows that triangle robot.
I tried wipe of cache and data wipe.
Whatever i try I am not able to get this device into fastboot / bootloader anymore!
It takes longer than usual,, it is stuck in that HTC screen since I have unlocked the bootloader but it does not enter the usual menu.
Instead it just directly goes to the robot.
I tried about everything I could think about,
It seems the OTA really bricked my phone by damaging the bootloader so it does not load at all anymore.?!?!
The only USB accessible feature I see is that in the robot screen it registers a device through USB.
Sadly not ADB or fastboot, it is a volume. It even loads as volume but is inaccessible (like a CD without disk)
Windows recognizes it as WDP FileSystem.
I doubt this will help at all, just wanted to note it.
I am about to throw the phone into trash, if it had not been so expensive.. Anything that can be done to repair this brick ?

Lirezh said:
I had android GE 4.3 on it, rooted.
I have the original GE bootloader (that robot) installed.
I downloaded the official 4.4 update through android, rebooted for install.
Now after the install the phone does not boot up anymore, instead it goes into RECOVERY and shows that triangle robot.
I tried wipe of cache and data wipe.
Whatever i try I am not able to get this device into fastboot / bootloader anymore!
It takes longer than usual,, it is stuck in that HTC screen since I have unlocked the bootloader but it does not enter the usual menu.
Instead it just directly goes to the robot.
I tried about everything I could think about,
It seems the OTA really bricked my phone by damaging the bootloader so it does not load at all anymore.?!?!
The only USB accessible feature I see is that in the robot screen it registers a device through USB.
Sadly not ADB or fastboot, it is a volume. It even loads as volume but is inaccessible (like a CD without disk)
Windows recognizes it as WDP FileSystem.
I doubt this will help at all, just wanted to note it.
I am about to throw the phone into trash, if it had not been so expensive.. Anything that can be done to repair this brick ?
Click to expand...
Click to collapse
Now search for the right adb and fastboot driver. There is a .msi installer (adb + fastboot .msi) something like that. Than push the right recovery via fastboot. Voila

Alfa Kenny One said:
Now search for the right adb and fastboot driver. There is a .msi installer (adb + fastboot .msi) something like that. Than push the right recovery via fastboot. Voila
Click to expand...
Click to collapse
Hi,
I solved it.
It took about 30-50 reboots until the phone entered the fastboot menu.
The problem was that the phone kept skipping the whole fastboot menu and went into recovery instead.
A very strange firmware bug caused by the failed OTA

[Q] 1092 TWRP on 5.0 bootloop, stuck in recovery [SOLVED]

Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?

Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657

oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?

HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.

oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic

Cannot connect to fastboot through ADB

Hi guys. I've had my HTC one for a while now and it had TWRP flashed on it. About a week ago I flashed the android revolution rom, worked well but my camera went really weird if I looked back at some recordings. So I wanted to revert back to stock everything. I flashed a stock recovery for the M7, after that I had the problem of not being able to connect my device to the computer when I fastboot mode. Simply wouldn't pick it up when I typed ADB devices in cmd. My device wouldn't show up after installing stock recovery. And it doesn't want to restore any roms either in stock recovery mode. I can't even access my folders in that mode to flash any roms. I click either apply from sd card, apply from phone storage. Says for a split second check CID failed or something and reboots itself.
I cannot flash TWRP back cause my computer since it can't pick it up. I've tried everything. Changing USB ports, uninstalling my drives for htc. Changing computers, unlocking, relocking bootloader. No result. I'm screwed cause I'm stuck on this android revolution rom, rooted. Just wanna flash custom recovery. I can connect it to my computer, access folders and add things to it but soon as I turn it off and go into fastboot mode it says fastboot usb and can hear the noise when its connected but it doesn't show up in adb devices and when I flash the TWRP it starts send then comes up with FAILED. Help please, would be appreciated!

Stevo001457 said:
Hi guys. I've had my HTC one for a while now and it had TWRP flashed on it. About a week ago I flashed the android revolution rom, worked well but my camera went really weird if I looked back at some recordings. So I wanted to revert back to stock everything. I flashed a stock recovery for the M7, after that I had the problem of not being able to connect my device to the computer when I fastboot mode. Simply wouldn't pick it up when I typed ADB devices in cmd. My device wouldn't show up after installing stock recovery. And it doesn't want to restore any roms either in stock recovery mode. I can't even access my folders in that mode to flash any roms. I click either apply from sd card, apply from phone storage. Says for a split second check CID failed or something and reboots itself.
I cannot flash TWRP back cause my computer since it can't pick it up. I've tried everything. Changing USB ports, uninstalling my drives for htc. Changing computers, unlocking, relocking bootloader. No result. I'm screwed cause I'm stuck on this android revolution rom, rooted. Just wanna flash custom recovery. I can connect it to my computer, access folders and add things to it but soon as I turn it off and go into fastboot mode it says fastboot usb and can hear the noise when its connected but it doesn't show up in adb devices and when I flash the TWRP it starts send then comes up with FAILED. Help please, would be appreciated!
Click to expand...
Click to collapse
Adb only works if you'te booted to OS or custom recovery. Command you're looking for in bootloader menu is "fastboot devices"

Fala Puno. Ja sam raditi sada. I'm of Croatian decent in Australia. I'll try this later when I return home

Fixed it! I'm an idiot, I didn't realise I was flashing the m8 twrp instead of m7. That's why it failed. Lol. Anyway thanks

Fastboot Problem (Freezing, probably not drivers)

Hello,
I've got a problem when trying to load fastboot that I haven't been able to find a solution for here. I'm hoping someone else has run into this and can help. My phone (H811) seems to freeze upon entering fastboot mode. I have...
Flashed 20i using TWRP
Enabled OEM Unlock and Debugging
Uninstalled and Reinstalled drivers in every imaginable configuration over the past two days
Flashed (and completely wiped internal storage) the 20i KDZ
Continued to muck around with drivers
Everything is fine when connecting to my PC, ADB has no issues. I run into trouble when rebooting (via ADB) and the phone freezes. The power button is unresponsive and I have to pull the battery to exit fastboot. My device manager shows -something- is connected after entering fastboot, but so far I haven't been able to find a working driver for that.
Thanks

New to nokia, not android/adb/etc

So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks

jgro1976 said:
So I just got my shiny new Nokia 8 and it seems to be updated to the latest version of Pie. Reading through all the root forums/threads, I'm noticing a couple issues with my phone that I'm not seeing mentioned:
-In Dev settings, OEM unlocking is off and grayed out, I can't toggle it.
-When I try to access download mode/bootloader (volume down/plug in cable from pc) my screen does a little flashy thing and then goes straight to the battery percentage.
-I can ADB devices just fine and see the phone, when I ADB reboot bootloader, the phone gets stuck on a screen showing "powered by android'', with "download mode" in the upper left corner, and any fastboot commands return absolutely nothing.
Any tips or suggestions?
Many thanks
Click to expand...
Click to collapse
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.

Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
MDV106 said:
- you cant toggle it because you have not unlocked the bootloader. Sometimes even after you unlock it it will be greyed out, which isnt of importance. To unlock the bootloader downgrade to Oreo November update by sideloading the relevant ROM, then follow the the official HMD instructions.
- Make sure USB debugging is turned on under developer options.
- Are you attempting to boot into the OS or recovery here? Abd reboot is enough to boot into your system. To boot into recovery use adb reboot recovery. Or do it manually using the keys.
Click to expand...
Click to collapse

Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
jgro1976 said:
Ok, everything I've read so far says to make sure OEM unlock is enabled before you do anything else, so you've confused me now. And none of the guides talk about sideloading the ROM, so you've thrown a new twist with that as well.
USB debugging is enabled, and my computer sees the device via adb devices, but if I try adb reboot recovery, all I get is the little android icon with the red triangle over him, and if I try adb reboot bootloader, basically nothing happens. And I wasn't trying to boot into the OS or recovery, I'm not a noob but maybe this phone is just different enough from what I'm used to I guess.
So basically I'm stuck right now, can't boot into recovery, can't sideload a ROM, can't boot into the bootloader/download mode either.
Click to expand...
Click to collapse

Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
jgro1976 said:
Actually, thank you, you got me thinking and I was able to get downgraded to the Oreo, got my code from Nokia and unlock.key, now the only thing I'm still having a hard time with is my computer won't detect my phone in fastboot mode. Works just fine in normal ADB commands, but no fastboot...
You'd think my drivers are all fine and that since ADB sees the device, but maybe not?
Click to expand...
Click to collapse

jgro1976 said:
Bootloader, unlocked! Now if I can get the rest of my home wireless **** to work this well/easily, thank you for getting me pointed in the right direction, all good here (I hope).
Click to expand...
Click to collapse
Im guessing you finally realised they after getting the android icon with the red triangle u have to press volume up and hold it then tap the power key to enter the recovery. Good to know you managed to unlock the bootloader eventually.
A lot of people have been having issues with fastboot, especially on Windows machines . Try restarting the shell or use a different USB port on your computer?also maybe try a different driver version and see if it helps.