Database Info

[Q] KFHD7 Bootloop with pc not recognizing device

Any help appreciated. I was trying to install second bootloader to my kfhd7 and HAD twrp working and when trying to complete the process upon reboot when the red triangle recovery screen showed up(i thought nothing of it) and it asked to restore device or something else, i believe i chose the restore option. ever since i have been stuck at the splash screen with orange kindle fire replaying over and over. I made a flimsy fastboot cable(which is now broke, I ordered a skorpn one) and was able to get into fastboot but i absolutely cannot get the device recognized in fastboot or adb. Mind you i had the drivers/adb working previously. I fear that without FB recognition on my pc I will be SOL... running windows 8 and FB cable should be here tomorrow or next day. wanna be prepared when they arrive. In advance thank anyone who helps for your help.
psver the last week im pretty sure i've read almost every kfhd7 post out there and haven't found one exactly like this. do not seem to find anyone else having some much trouble getting ADB/Fastboot to see device as me when in this situation(used to be the easiest part for me).

Bricked, stuck in TWRP and adb issues also

Hello there, recently I tried to get TWRP for my LG G2, and I kept trying over and over again to where my phone's booting got stuck in a loop and began making a lot of drives. Luckily, I found http://forum.xda-developers.com/showthread.php?t=2582142 and got to the point where I could get into TWRP. The problem is, now I can't boot up into the normal rom, which I'm guessing has been erased through TWRP and my own stupidity. So I have no roms to flash either, and in addition, my screen is screwed up, and while I can navigate TWRP, I have a very hard time doing it. Also, whenever I plug my phone in to my computer, it just shows up as 'g2' in the device manager, and is an unknown device. I have tried adb sideloading a rom but it always gives me 'error:closed'.
So let's round that up since I kinda rambled there.
Screwed my phone up by trying to get TWRP and it ended up booting in a loop and making a ton of drives.
Was able to fix this and am now able to get into TWRP, but the touch screen is going crazy and I have a hard time navigating TWRP
Whenever I try to use adb with my phone, command prompt says 'error:closed'
The device manager calls my phone 'g2' and thinks it's an unknown device.
I swear, if anyone here can help me get this phone to where it's booting up correctly again, you are incredible.
Thanks!

whynottry said:
Hello there, recently I tried to get TWRP for my LG G2, and I kept trying over and over again to where my phone's booting got stuck in a loop and began making a lot of drives. Luckily, I found http://forum.xda-developers.com/showthread.php?t=2582142 and got to the point where I could get into TWRP. The problem is, now I can't boot up into the normal rom, which I'm guessing has been erased through TWRP and my own stupidity. So I have no roms to flash either, and in addition, my screen is screwed up, and while I can navigate TWRP, I have a very hard time doing it. Also, whenever I plug my phone in to my computer, it just shows up as 'g2' in the device manager, and is an unknown device. I have tried adb sideloading a rom but it always gives me 'error:closed'.
So let's round that up since I kinda rambled there.
Screwed my phone up by trying to get TWRP and it ended up booting in a loop and making a ton of drives.
Was able to fix this and am now able to get into TWRP, but the touch screen is going crazy and I have a hard time navigating TWRP
Whenever I try to use adb with my phone, command prompt says 'error:closed'
The device manager calls my phone 'g2' and thinks it's an unknown device.
I swear, if anyone here can help me get this phone to where it's booting up correctly again, you are incredible.
Thanks!
Click to expand...
Click to collapse
Hey Pal try -> http://forum.xda-developers.com/showthread.php?t=2663369 but you will wipe everything on your phone but at least you can start with a 100% working G2 D800!

Crap I forgot to mention I can't go into download mode. Sorry about that..
atmxpert said:
Hey Pal try -> http://forum.xda-developers.com/showthread.php?t=2663369 but you will wipe everything on your phone but at least you can start with a 100% working G2 D800!
Click to expand...
Click to collapse

[Q] Nexus 5 died in the night. Fastboot works, but recovery is a black screen.

Hi all, first time posting here.
Last night my Nexus 5 turned itself off while charging. Today it won't boot past the white Google logo. I had an unlocked bootloader, but was stock with no root and no custom rom, 5.1.1. I've had the phone for over a year, and bought it from a high street UK phone chain on contract, not from the Play Store.
I've spent the last 6 hours learning, trying, reading, trying again, watching videos, trying not to punch things, but nothing works.
Here's what I know:
I can boot into fastboot mode
bootloader is unlocked
recovery mode is a permanent black screen
"adb devices" cmd in platform-tools does not find the device
I've tried tweaking Windows 7 drivers (driver for fastboot etc.) but to no avail (including using clockwork)
"fastboot devices" returns the serial code for my phone
flashing using fastboot commands gives me "flash write failure" on bootloader-hammerhead xxx .img
even "fastboot erase boot" does not work ("failed to erase partition")
"fastboot reboot-bootloader" simply turns the phone off (does not attempt even a normal reboot)
Unless I'm in some weird driver quandary, I fear my phone may be beyond help as even simple commands do not work. Any help is much appreciated.

I should mention that "flash-all" doesn't work within platform-tools.
The reboot doesn't actually work. When it says "waiting for device" I manually restart the phone into fastboot myself. And then I get write errors, when it's starts pushing the radio file.
imgur . com / eBk4KnX.png

Pete.D said:
Hi all, first time posting here.
Last night my Nexus 5 turned itself off while charging. Today it won't boot past the white Google logo. I had an unlocked bootloader, but was stock with no root and no custom rom, 5.1.1. I've had the phone for over a year, and bought it from a high street UK phone chain on contract, not from the Play Store.
I've spent the last 6 hours learning, trying, reading, trying again, watching videos, trying not to punch things, but nothing works.
Here's what I know:
I can boot into fastboot mode
bootloader is unlocked
recovery mode is a permanent black screen
"adb devices" cmd in platform-tools does not find the device
I've tried tweaking Windows 7 drivers (driver for fastboot etc.) but to no avail (including using clockwork)
"fastboot devices" returns the serial code for my phone
flashing using fastboot commands gives me "flash write failure" on bootloader-hammerhead xxx .img
even "fastboot erase boot" does not work ("failed to erase partition")
"fastboot reboot-bootloader" simply turns the phone off (does not attempt even a normal reboot)
Unless I'm in some weird driver quandary, I fear my phone may be beyond help as even simple commands do not work. Any help is much appreciated.
Click to expand...
Click to collapse
Did you try locking the bootloader, and then unlocking it again?

Oh god , I think you have a hard bricked nexus .

Schoat333 said:
Did you try locking the bootloader, and then unlocking it again?
Click to expand...
Click to collapse
Good idea! Just tried it (which it let me do) but still getting write errors running flash-all.

Given the sudden shutdown and corruption on your phone along with failure to write and to erase sounds like your internal memory has gone bad.
If that's the case you won't be able to to anything. I had the same occur with a Galaxy S3 last year and the nand memory went bad. Unfortunately it does happen, but not often. My guess is you now have a paperweight

Not prompted for ADB RSA key

I have search XDA, and the net as a whole, and I have found many people with this same problem, and a few that were able to fix it -- however none of the fixes have helped me.
The problem is that once the boot loader is unlocked, I am no longer prompted to allow a connection from ADB so the RSA key doesn't get installed. If I do an adb devices, it shows as unauthorized.
This isn't a huge issue since I can still use any terminal program and execute the same commands on the phone itself, however, that is not ideal. I would really like to be able to use adb and fastboot to pull images, dump files, etc to my PC. As it stands now, I have to use a wireless KB / mouse, execute the commands in a terminal, and then transfer the files to my laptop.
I have tried taking the key that gets generated in %appdata%\.android and copying it to /data/misc/adb/adb_keys, and /adb_keys and /data/adb/adb_keys. I have also tried setting the build.prob variable ro.adb.secure to 0 -- no luck.
If anyone has any other ideas, it would be greatly appreciated. Again, this only happens once I unlock the boot loader (which is needed to root MM). Stock MM gives the prompt on the phone, and I can communicate just fine with adb and fastboot (obviously, need fastboot to unlock the bootloader ).
EDIT: I have an MS631 -- not sure if H631 has this same problem.
-- Brian

So I had a brilliant idea during lunch just now (yea, that is a whole lot of sarcasm).
I figured I would just lock the boot loader back, use adb and then then unlock it. So I boot into fastboot mode, do an oem lock, and then it dawns on me that I kinda need that unlocked bootloader to boot back into the OS. Well, unfortunately my fingers were typing a little faster than my brain was thinking and a fastboot reboot had already happened... LMAO. So, Now I get to sit here and install the LP KDZ, and root / install twrp, then install MM, and root / install TWRP, then restore the backup (that luckily I made right before being a moron) *sigh*. Prime example of why finding a way to boot MM without unlocking the boot loader is so important ....
-- Brian

Pixel 3 Brick issue.

So I unlocked the bootloader no problem. TWRP no problem, then something happened with the magisk flash. Phone tried to boot, as normal, then it went to recovery, then to a boot loop. I can get it to the fastboot screen, but ADB won't recognize the phone, I have chased around different USB drivers for two hours, thrown every command at it that I can think of, but nothing is working. Any suggestions? I literally picked the phone up (bought off of swappa locally), drove home and bricked it lol.
edit: The phone is recognized by my computer, just not ADB.

jerseymk2 said:
So I unlocked the bootloader no problem. TWRP no problem, then something happened with the magisk flash. Phone tried to boot, as normal, then it went to recovery, then to a boot loop. I can get it to the fastboot screen, but ADB won't recognize the phone, I have chased around different USB drivers for two hours, thrown every command at it that I can think of, but nothing is working. Any suggestions? I literally picked the phone up (bought off of swappa locally), drove home and bricked it lol.
edit: The phone is recognized by my computer, just not ADB.
Click to expand...
Click to collapse
So you put the phone in fastboot mode and ADB won't recognize the phone? That is normal, ADB works when the phone is booted normally. In fastboot mode you only use fastboot commands.
Fastboot devices

Just need to "fastboot flash boot boot.img" with the stock boot.img.

jsauder2 said:
Just need to "fastboot flash boot boot.img" with the stock boot.img.
Click to expand...
Click to collapse
Sorry I work for the railroad and was away for the last few day. I am aware of that, the issue I was facing was that the phone was not communicating with the laptop when I booted fastboot. I was able to get it this morning after about what felt like 900 attempts. I knew what needed to be done, I was having severe connectivity issues, I played the game of switching cables, switching usb ports etc... finally it had connectivity. Thank you again for your help though.