Database Users

[Q] Black screen, plugged into PC, keeps disconnecting/reconnecting. Bricked to Hell?

Just like the title says. At first when I plugged my Kindle Fire in it showed up as the processor name. I installed the drivers by just using that hoping to get some sort of PC connection.
Im on Windows.
TWRP was messed up and wouldnt boot for me. (when screen worked.)
Had ICS beta. (When screenworked)
Would like to get back to stock.
Could anyone help me out?

maybe out of battery ? charge for an hour with the wall plug (pc loads very slowly)
some more information would be helpful:
what exactly have you done ?
os/bit of your computer ?
do you have newest kfu available ?
if yes please move and rename to c:\kfu (win7 64bit drivers will not install with spaces and it's easier to help cause in the tools folder are all necessary commands)

b63 said:
maybe out of battery ? charge for an hour with the wall plug (pc loads very slowly)
some more information would be helpful:
what exactly have you done ?
os/bit of your computer ?
do you have newest kfu available ?
if yes please move and rename to c:\kfu (win7 64bit drivers will not install with spaces and it's easier to help cause in the tools folder are all necessary commands)
Click to expand...
Click to collapse
Usually it charged through the USB port on my computer but currently I put it on the wall charger to see if that would be the problem.
Well the history is this: Rooted 6.2.1, installed ICS, but after messing with TWRP my Kindle Fire arrived at a point where ICS was the ONLY OS, no backup available and TWRP being stuck at the logo not proceeding. I used the KFU to try to install a new TWRP on it but I think that might of messed it up. Im not sure to be honest theres been a lot done on this and its been a week til I had time to resolve my issue.
Windows 7 64bit
EDIT: Btw the green light from the power button never comes on. Ill plug the device in and nothing will happen until I hold the power button down for a while.
It shows up in the device manager, but only for a second to be disconnected, then the cycle repeats constantly.

Bricked to hell....I got a chuckle out of that.... Good luck man, hope you can get it fixed.
Sent from my Kindle Fire using xda premium

Okay. So at this point you are unable to power the device on? Even after charging it off of the wall port? (PC charging my android devices never personally worked for me)
Also have you loaded a custom kernel on? And have you checked if ADB can recognise the device?
Sent from my Kindle Fire using xda premium

Ok, all you have to do if twrp is messed up is to reflash it in fastboot. You can never Really brick a device.... See if you have adb.

http://forum.xda-developers.com/showpost.php?p=21715022&postcount=9

Zomboogz said:
Okay. So at this point you are unable to power the device on? Even after charging it off of the wall port? (PC charging my android devices never personally worked for me)
Also have you loaded a custom kernel on? And have you checked if ADB can recognise the device?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Well I know its on cause how would the PC be able to recognize it? It keeps going on and off so I cant time it correctly or its just too fast I cant tell.

b63 said:
http://forum.xda-developers.com/showpost.php?p=21715022&postcount=9
Click to expand...
Click to collapse
Im going out to dinner but I will try that and let you know how it works after

Recovery only works when USB is plugged in

Hey guys,
I've been noticing something unusual with my tablet. The stock hard-reset recovery(as well as CWM) only works with USB plugged in. When it is not plugged on the computer, it hangs on the black screen with the Google logo(when it is oem locked, there's a lock on the bottom). I am also a Galaxy S2 user so I know that I didn't need the USB plugged in, in order to enter the recovery mode.
Is this normal for the N7 tablet? or is there something wrong with it?
Thank you

kaywoo said:
Hey guys,
I've been noticing something unusual with my tablet. The stock hard-reset recovery(as well as CWM) only works with USB plugged in. When it is not plugged on the computer, it hangs on the black screen with the Google logo(when it is oem locked, there's a lock on the bottom). I am also a Galaxy S2 user so I know that I didn't need the USB plugged in, in order to enter the recovery mode.
Is this normal for the N7 tablet? or is there something wrong with it?
Thank you
Click to expand...
Click to collapse
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.

cheami said:
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
Click to expand...
Click to collapse
Yeah it's weird. Even after coming back to stock, unrooted, the hard-reset via stock recovery doesn't work unless USB is plugged in. Maybe some files are missing

Wow, I'm glad I stumbled on this thread, I was going nuts trying to figure out why I couldn't boot back into CWM after going back to the stock image and applying the OTA .zips.
Confirmed, I can get it to boot into CWM from fastboot only if I have the USB cable plugged in. Otherwise it just hangs on the Google splash screen.
Weird.

I've been able to boot into recovery using the app "quickboot" which had an option to reboot into recovery. My usb cable isn't plugged in.
Sent from my Galaxy Nexus using Tapatalk 2

This sounds a bit like my Nexus S i9020. It will only go into bootloader without the usb, and only go into download mode with USB attached (although it doesn't have to be powering it). This is the same on both handsets I've used. Maybe not a 'flaw' and more a nod to using fast boot/adb?
Sent from my Nexus S using xda app-developers app

I am currently having the same problem. Did anybody come up with a fix for this?

I'm having the same issue with the nexus 7. I've found out that you can boot into recovery if you have ROM Manager installed and select reboot into recovery.
Does anyone know if this is an OS issue or recovery issue?

Interesting. Was wondering why I couldn't get into Recovery from the Bootloader.
Another bug for me is that if I boot into Bootloader with the USB connected, I cannot make any selection using the volume keys. Only works if I boot in first without USB connected, then connect once I'm booted.

Its a bug, guys learn to search in the Development threads, I'm sure its being worked on,personally I've been able to get into recovery without have to connect via USB, if all else fails you can enter recovery via USB and ADB, by issuing the command adb reboot recovery in terminal/cmd

I had the same issue last week. Not sure what changed but now I'm able to get into recovery using the reboot menu or good mngr/rom mgr. No need for usb. I'm on modaco rom and used both clockwork and twrp.
Sent from my PG86100 using xda app-developers app

I have one more problem...
When I connect USB, the keys don't work in bootloader so can't try recovery with USB cable on.
Any solution for this?

cheami said:
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
Click to expand...
Click to collapse
I have the same problem.
LTE Galaxy Nexus
Nexus 7 (16gb)

Miracle.vl63 said:
I have one more problem...
When I connect USB, the keys don't work in bootloader so can't try recovery with USB cable on.
Any solution for this?
Click to expand...
Click to collapse
There are two different versions of CWM- one uses the power and vol-up/down buttons for keys- the other used the tablets touchscreen for button press functions.
You may have installed the touch(screen) version of CWM- try using the touchscreen for controls.

Same issue here. I can get to recover either connected or via rom manager.
Sent from my MIUI Motorola Star Tac

omegajester said:
Same issue here. I can get to recover either connected or via rom manager.
Sent from my MIUI Motorola Star Tac
Click to expand...
Click to collapse
I too can get into recovery via ROM Manager. I read somewhere that pulling the battery might help. I know that's a bit of a pain on the Nexus 7, but I'm going to try that when I get home later to see if that helps.
LTE Galaxy Nexus
Nexus 7 (16gb)

Trikkenut said:
I too can get into recovery via ROM Manager. I read somewhere that pulling the battery might help. I know that's a bit of a pain on the Nexus 7, but I'm going to try that when I get home later to see if that helps.
LTE Galaxy Nexus
Nexus 7 (16gb)
Click to expand...
Click to collapse
Nope, disconnecting the battery didn't change anything. Wug Fresh (Nexus Root Toolkit developer) informed me on Google + that it's a Google issue and it should be fixed in a future update. For now i'll be either plugging in USB to computer or ROM Manager.

I can't even get into the boot loader with my usb plugged into a charger not a computer

askho said:
I can't even get into the boot loader with my usb plugged into a charger not a computer
Click to expand...
Click to collapse
Try Quick Boot
Free, easy to use, will boot to bootloader, recovery, reboot etc... requires root of course, you already have that.

i dont't have root because it was screwed up right fromt he get go

[Q] Is my Defy dead/bricked?

Is my Defy dead?
I was messing around in recovery mode and formatted internal memory by mistake now my defy is completely dead. See below for symptoms;
It doesn't turn on, no bootloader, no recovery..
No function Power + Vol+/-.
LED does not light with or without usb.
Only when I connect it to my PC (windows 7 x64) and insert the battery, is there any kind of response makes the same sound as it does when a plug and play device is connected, but off again at 2-3 seconds. Tries to install OMAP3630 drivers but fails saying device is unplugged. (see attached image) Have installed latest Latest Motorola Handset drivers to no avail.
RSD Lite 5.5 (ran in adminstrator mode) does not show device, not even a white LED as mentioned in other posts.
Tried using the Macgyver method to 'jump start' in order for RSD Lite to detect phone no difference.
Any help would be greatly appreciated ?
Chris

R.I.P
No way to fix it
Sent from my MB526 using xda premium

Charge ur battery with external charger OR Change ur Battery.

jalal-jap said:
Charge ur battery with external charger OR Change ur Battery.
Click to expand...
Click to collapse
Thanks for the reply, doesn't the macgyver hack offer a workaround to not having the battery fully charged?

Yes, it does
Just to confirm, before this unfortunate incident you were able to flash sbfs right?
Sent from my MB526 using xda premium

I assume so. Although I didn't have any need too at the time but do now.

I'm asking the question since there may be a driver problem. Although another person like you had mistakenly formatted internal memory and was unable to resurrect it. So you have really slim chances, if any at all.
Sent from my Nexus 7 using XDA Premium HD app

[Q] Cannot get PC to see Nexus (2012) is connected (Code 10) on driver. Help please!!

I have tried many options. My Nexus died shortly after a KitKat update, but it may have been frazzled by a faulty car charger.
Cannot access recovery mode.
Cannot get PC to see ADB device
Would replacing the USB board help?
Out of warranty so willing to try almost anything.

Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app

xateeq said:
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I was only ever stock. Unrooted, but had USB debugging.
I sideloaded KitKat when it came out and installed the Google Experience launcher. Received an OTA a day later that was only 1-2Mb.
The sideloading worked perfectly using the adb sideload kitkat.zip.
The evening after the OTA and the unit died. It is possible that it was a car charger, but I think highly unlikely as it never affected a Kindle or Xperia Z. But now I cannot get the PC to even see that the device is connected and neither can I get Recovery Mode to fully start. I select Recovery Mode and all I see is the Google logo. I have tried all sorts of button presses to get the android on its back with the red triangle. I may have missed something obvious so any suggestions would be a help.

Connect to wall charger if u cant get it to charge then it is ok,
try changing ur data cable that ur using to connect it to pc.
if ur tablet was not connected to charger when it dies then it is not the carger. OTA usually mess things up on modified/ rooted devices.

Hi, Thanks for the response.
I've tried all my cables. I can get the unit to charge no problem. It is just that I cannot get it to recover itself.
Powering on freezes on the Google logo and the CPU overheats like a really good overheating thing.
I go into the bootloader and if it doesn't freeze I can select all the various top level options. I have tried selecting Recovery mode and I cannot get that to work either. If I select Recovery mode and hit the power button it once again freezes on the Google logo. I have tried holding the volume up and pressing the power, but nothing happens. The only option I have is to power off again.
I had hoped that the nexus Root toolkit would help, but as it is never seen or recognized by the laptop I think I am totally screwed. I am thinking that my best hope is to sell it for spares. Unless there is a way of resetting the machine without a computer or being able to access recovery mode. I haven't seen anything like this.

[Q] Boot Loop - what happened?

I was on Google+ and I checked out a youtube video, it was about a 3d printed engine. After watching the video I shut the screen off and I went to bed. When I woke up in the morning my tablet was displaying the Google logo and then restarting. What did I do?? The tablet was fully charged and wasn't plugged into anything. I could understand if I was tinkering with it but I hadn't done a thing. Now I don't know what the heck to do. I've tried Wug but I can't seem to get the ADB drivers to be recognized on my laptop, Windows 7 64bit. I'm at a loss as to what I should do next. Any help would be appreciated.
It was running 4.4.2 (KOT49H) for about a week.
**I should clarify the drivers thing. Windows says everything is installed and running correctly (Android Composite ADB Interface) but Wug is saying that ADB cannot be found.
**and for whatever reason the word Composite is throwing me off with the driver thing because nowhere in Wug's tutorial is that label for the driver but my laptop only seems to find that driver.

Leave it for 1 day to charge and then try to turn it on without unplugging till boot finish...let us know what happened
Sent from my GT-N7100 using Tapatalk 2

Go into recovery mode and wipe cache and reboot and see if that fixes it.

GRG13 said:
Leave it for 1 day to charge and then try to turn it on without unplugging till boot finish...let us know what happened
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I have it charging now. It's been plugged in since 7:30 this morning. So are we talking 8 hours, 24 hours?
iBolski said:
Go into recovery mode and wipe cache and reboot and see if that fixes it.
Click to expand...
Click to collapse
I don't have the ability to go into recovery mode. All that happens is the Google logo comes up and then reboots. I can get into the fastboot screen but nothing else. I can power it off and it'll charge but reboots before it can go into recovery.

BrokenLegGuy said:
I have it charging now. It's been plugged in since 7:30 this morning. So are we talking 8 hours, 24 hours?
I don't have the ability to go into recovery mode. All that happens is the Google logo comes up and then reboots. I can get into the fastboot screen but nothing else. I can power it off and it'll charge but reboots before it can go into recovery.
Click to expand...
Click to collapse
are you sure you have the correct drivers installed? I'm on Windows 7 64-bit and it works just fine.
You might want to go into device manager and remove the device completely from Windows 7 and then try reinstalling the device drivers.
Worse comes to worse, get the Nexus 7 toolkit from Skipsoft.net. It contains all the correct drivers. That's what I use.
Try that. If you can get into fastboot mode, then you will be able to reflash everything back as long as you had USB debugging enabled. You can choose to keep data or do a complete wipe of everything with the N7 toolkit.
I never used wug as I've always had great results with the N7 toolkit.

try this
I ran into a similar situation go to wig fresh put your device into fastboot. Then click softbrick reboot it will wipe your device but it will fix it make sure you select the same software you want to install. K

iBolski said:
are you sure you have the correct drivers installed? I'm on Windows 7 64-bit and it works just fine.
You might want to go into device manager and remove the device completely from Windows 7 and then try reinstalling the device drivers.
Worse comes to worse, get the Nexus 7 toolkit from Skipsoft.net. It contains all the correct drivers. That's what I use.
Try that. If you can get into fastboot mode, then you will be able to reflash everything back as long as you had USB debugging enabled. You can choose to keep data or do a complete wipe of everything with the N7 toolkit.
I never used wug as I've always had great results with the N7 toolkit.
Click to expand...
Click to collapse
After deleting all the drivers I knew were Android I also deleted all the generic usb drivers as well, which I didn't think to do earlier, and then wug could see the correct ADB drivers.
I tried Skipsoft last night and it is far more feature rich but I had the same results. Still bootlooping. On the plus side I was able to re-lock the bootloader, which I couldn't do in wug from the fastboot screen, so I can have it covered under warranty if nothing else.
Rmontoya83 said:
I ran into a similar situation go to wig fresh put your device into fastboot. Then click softbrick reboot it will wipe your device but it will fix it make sure you select the same software you want to install. K
Click to expand...
Click to collapse
wugfresh is what I was originally using and no dice. I have a second tablet I used to determine what build I wanted to use. because both tablets where updated and everything at the same time.