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

[Q] Upgraded to CM10, lost all usb charge / data connectivity!

Hi,
So I upgraded from cm7.2 to 10 on my defy green lens. After a long and difficult upgrade, almost everything works - except any functionality of the usb port...
I'll jump right into the real deal: without usb connectivity, I cannot try to flash other SBFs to fix it! I can enter the bootloader screen just fine (says 09.10 on top, I believe that the last SBF I flashed was 3.4.2_179-002 , as recommended, before I rooted it, 2ndinit, and sucessfuly installed cm10) and the phone recognizes when I plug in a usb cable to it. but the computer always shows up a "usb device not recognized" error, and I tried on two machines, winxp/win7, and several different usb cables. I read some threads about crashing drivers between rsdlite and different tools motorola made; I never installed any of that junk but just to be on the safe side I removed all drivers and started fresh. still no go.
______________(That's the problem, now I'm just going to give more information about it)______________
The phone does not charge off a computer nor from a wall charger, with an assortment of different usb ports, cables and chargers. when connected to a computer (whether the phone is on or off) a "usb device not recognized" message comes up, on both windows xp/7 (different machines.) Seldom, when connected to wall charger, I can get the battery icon to show charging for about a second, (after a restart and plugging in to the pc briefly beforehand.) If I'm so lucky to make that happen, either it goes off in about one second, or it will change statues from charging to not charging several times very rapidly and then stay on not charging.
If the phone is off and I connect it, the white led sometimes come on, and then the phone comes on- presumably to go into battery charging screen, but instead it boots up normally. (this may be the correct behavior with this rom. idk.)
If you care for more information, let me elaborate about what I mean by "After a long and difficult upgrade":
I previously upgraded to cm10 (30/7/2012) CM10-20120730-NIGHTLY-mb525.zip,
but downgraded shortly after, back to 7.2. (I decided to wait for something a bit more functional)
Back then both the upgrade/downgrade went fine. This time I got into a bootloop (or stuck on bootscreen) after updating to 26/03/2013 God's version (oops I meant Quarx's version.)
Trying to use my nandroid backup for 7.2 I got a md5 mismatch and even after generating a new md5 file I couldn't restore /data.
Moving on. using CWM I tried installing some kernels (kernel-froyo-222-179.zip, and same thing but signed,),
then a fixed sbf (not full) 3.4.2_177-Fixed.NORDIC_DEBLUR.sbf,
and a very crappy sbf JRDNEM_U3_2.26.0_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB1B5TEL02A.0R_USAJORDANTELSTRA_P033_A017_M008_HWp3_Service1FF.sbf
** this one almost gave me a heart attack, after successful flash defy black screened with no LED indications. I was able to work my way into the bootloader and flash another SBF with rsdlite, without any indications from the device. lucky me.
Then I flashed the sbf I mentioned above and that's how I eventually got into cm10.
I can't even downgrade to stable cm7.2. Tried flashing a fresh install through CWM (wiping everything before and after, of course) and ended up stuck on boot screen. I don't know if it has anything to do with CG numbers or what, but I really can't figure out why CM7.2 wouldn't boot on the same SBF CM10 is booting fine right now.
I can't also share the SD card through CWM. (-> device not recognized)
I'm losing my marbles over here. Been working on it for two whole days and can't think of anything else I can try out... If I flashed the wrong rom using CWM I might get locked out because bootloader won't be any help!
:crying: cry for help... thanks :fingers-crossed:

Have you tried installing adb and the motorola drivers so you can try to communicate with the device?

Thanks for your word zero gravity!
Well, I thought that since "usb device not recognized", and since it shows up as unknown device under device manager (currently it disappears and reappears every 3 seconds, but I think this is a new behavior) I automatically assumed that I couldn't get proper communication with it! I guess I got to do some reading about adb commands any help with it would greatly be appreciated (No worries though I know how to google )

http://forum.xda-developers.com/showthread.php?t=1241935
Here's a simple guide for adb. Hopefully you can get some sort of communication to flash your stock sbf and start over again.

So, even though I have the drivers installed (Motorola_End_User_Driver_Installation_4.9.0_32bit.msi_.zip, and also installed MotorolaDeviceManager_2.3.9.exe,) Android SDK Tools installed, then I tried adb devices - nothing comes on.
by enabling ADB over network I can adb connect to the phone through wifi and go into shell. but I can't see how I can debug the buggy usb interface with network access.
Also tried starting the adb service through recovery - no go, won't show up.
(I plugged in a different Android phone (an Xperia), installed the drivers and had it running on adb usb in no time. So I'm doing it right.)
Any thoughts? are there commands to specifically listen and figure out what's coming from the usb port?
any other leads anyone may have? I'm listening!
Cheers, Shawn

The port must have suffered hardware damage. Examine the port for obvious conductivity hindrance. If not I'm afraid you'll have to get it repaired
As for cm7.2 after flashing just format to ext3 from boot menu(before this wipe dalvik cache), and after a reboot wipe data from stock recovery for good measure
Sent from my MB526 using xda premium

Well, thekguy seems to be on the right track.. I can fiddle around with the usb plug and get it to charge, So the problem seems to be mostly physical - if not completely.
I still can't get it to connect properly to the computer, but go figure which usb signal is dropping off. might be power, might be data.
After spraying it several times with contact cleaner the port is good enough for steady charge. No change about how it doesn't connect to a computer.
I feel like a dumbass, cus I already gutted the phone up a couple of days ago to try tracing conductivity paths through the port. the usb port is cast in plastic that is not removable from the pcb. There's no access to the USB pins, excepting four conducting points through the plastic right next to the port, but they are all connected to ground - they probably belong to a bracket that's holding the plastic to the pcb.
anyhow I did all that (I got closeup pictures if anyone's interested) but I wasn't able to check conductivity, and I didn't try fiddling with it after that. bah!
___________________________
Still wondering about one thing! The bootloader is locked, so that means it was never-ever changed since the phone was manufactured, correct? So no effect of writing different SBFs on the bootloader, correct? (minding the Efuse and CG numbers)
if so, than can I conclude only by that information (and that I cannot connect the phone to the computer anymore with bootloader) that there must be hardware/physical damage? I've just completely eliminated the software factor out of the equation. haven't I?
Did I miss anything? let me know.
P/S, I'm going to stick with this phone as it is. I can work around never having usb data connection.
Cheers

Can you try installing Linux and see if the you can mount /system or even /sdcard on Linux from bootmenu? Bootmenu mount only works in Linux. I've tried it in Ubuntu 10.10
Its worth a try, if Linux doesn't see it then it must be a hardware issue and would need a Motherboard replacement.
Use ubuntu live disk to make things easy and not mess your Windoze
Sent from my MB526 using xda premium

You're right, sbf flashing cannot break usb functionality. I'm not very well versed in mobile hardware but I think the port can be replaced, though I don't know how. It may be possible that a local mobile store could fix it.
Trying Linux is a good idea, though it may not work out from the looks of it(the phone)
Sent from my MB526 using xda premium

If anyone is reading this, I had some bad batteries and a usb port that is having physical problems. I'm flashing it with contact cleaner spray every now and again and it helps. I can get a usb connection to the computer and charge it with a bit of luck and while I keep it stationary.

[Q] Bootloop with no USB [Solved]

Hi,
I recently got ahold of a european XT610 which I rooted and flashed to CM7 without problem. Unfortunately I missed the warnings which said not to run bootstrap after installing cyanogenmod... and now I have the infamous bootloop. It gets to the CM loading screen, but goes on indefinitely from there. I know the answer is to restore the motorola sbf, however I can't seem to get my phone to communicate at all via usb. I installed motorola drivers and RSD and all in windows, but the phone seems to ignore the USB completely. I'm normally a linux guy, so I when I tried to plug it in there and watch the output of dmesg, absolutely nothing came up. Holding R, M and power when I plug in the usb causes a black screen after a bit of the motorola logo, but still no USB. Tried a few different cables, and checked them with other devices to confirm they're working.
So any ideas on how to recover the phone?
Update:
I discovered the main step I was missing was that the bootloader can be accessed by holding down both volume buttons and the power with the device off. For some reason I still couldn't get windows to recognize the correct drivers, even after installing the motorola driver package, but good old linux saw it without a problem. Following these instructions I was able to do a quick SBF and now all is good in the world!

same probleme for me?
ObsidianOps said:
Hi,
I recently got ahold of a european XT610 which I rooted and flashed to CM7 without problem. Unfortunately I missed the warnings which said not to run bootstrap after installing cyanogenmod... and now I have the infamous bootloop. It gets to the CM loading screen, but goes on indefinitely from there. I know the answer is to restore the motorola sbf, however I can't seem to get my phone to communicate at all via usb. I installed motorola drivers and RSD and all in windows, but the phone seems to ignore the USB completely. I'm normally a linux guy, so I when I tried to plug it in there and watch the output of dmesg, absolutely nothing came up. Holding R, M and power when I plug in the usb causes a black screen after a bit of the motorola logo, but still no USB. Tried a few different cables, and checked them with other devices to confirm they're working.
So any ideas on how to recover the phone?
Update:
I discovered the main step I was missing was that the bootloader can be accessed by holding down both volume buttons and the power with the device off. For some reason I still couldn't get windows to recognize the correct drivers, even after installing the motorola driver package, but good old linux saw it without a problem. Following these instructions I was able to do a quick SBF and now all is good in the world!
Click to expand...
Click to collapse
Can you tell me more about it please : i've made the same mistake...
I nead a real lesson !:laugh:

[Q] Bricked Updating to CM11

Hey guys any help or suggestions will be greatly appreciated on this matter. I will try to be as detailed as possible but I'm trying to fix this phone for a friend and he isn't very phone savvy. From what I understand, he was previously on CM10 and tried updating to CM11 using the cmupdater. For some reason it failed and he was stuck in TWRP. When he tried to reboot it kept kicking him back to recovery. He took his phone to a phone repair shop who then wiped his device. At this point he gave me the phone to try to fix.
First of all I have working fastboot and adb drivers for my Nexus 5 so I don't think this is a driver issue but I'm no expert on the Nexus 4 so I could be wrong. I'm also running Windows 8.1 if this is any relevance.
I can still access the devices bootloader (ver MAKOZ20i)
I can still access TWRP (ver 2.6.0.0)
When plugging the device into my USB 2.0 ports, nothing shows up in my device manager in bootloader, TWRP, or TWRP ADB sideload.
When plugging the device into my USB 3.0 ports, I see 'Unknown USB Device (Device Descriptor Request Failed)' and the Device Instance Path is 'USB\VID_0000&PID_0002\7&20F39B9B&0&2' in bootloader, TWRP, or TWRP ADB sideload.
I've never heard of a device not being seen at all in by USB 2.0 ports but showing using USB 3.0 ports so I attempted to give extra juice to the phone using a powered USB OTG cable. Still nothing shows up.
I've tried running 'fastboot device' and 'adb devices' with no luck.
I think I've covered all the bases... can anyone think of anything that could help me re-install a new rom or factory reset or his he out of luck?

I think it may be a Win8 problem. You have access to another machine with Win7 or WinXP?

Install "universal driver.exe" in win7, than connect phone while power off, I think it'll install driver...than push any custom ROM to phone via adb or just flash any official IMG..

Well I can tell you WHY it didn't work. That version of TWRP is not able to install 4.4 (CM11). if you manage to successfully push via adb and get it started again, make sure to flash the newest version of TWRP before trying that again.

Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?

mrlazyone said:
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
Click to expand...
Click to collapse
One more, when you plug into usb 3.0 you can see unknown device Right ??
If yes, download driver files from here Here.
It's a zip contains .inf files, Now click on unknown device and select update drivers then give the path to these drivers manually.
Hope this will help you out.

I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app

mrlazyone said:
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060

DrFredPhD said:
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
Awesome! Didn't realize this was an option. It didn't work using the USB 3.0 ports but the USB 2.0 actually worked for this method. Thank you!

[Work in progress] Fixing a "Hard-Bricked" Moto X

This thread is a process of how to potentially get your phone prepared for these steps:
http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057
If your device says USB Input device and then disconnects after a few seconds, There is a potential theory as to how to bypass that.
After buying a "Factory cable" for the moto X for 10$ I plugged it into my computer and nothing, So i noticed that it would 'unplug' after it "installed" the driver. So i plugged it into the USB slot in my pc and found out that the green light not only showed up, but stayed on for a constant hour! This means that the phone must somehow still be alive and charging. The reason behind this is the fact that the TV didn't install the driver, but simply sent current to the cord. The problem is that if you've already installed the driver on your pc once, it will always fetch that same driver to install the device again. The bypass to that would be finding a Windows XP computer that asks if you'd like to install the drivers first. Or a Win 7/8 Pc that hasn't been connected to the Moto X yet. Go to devices and printers: right click my computer -> Driver installations -> Never install using Windows Update. This should allow you to install your own driver which is the one stated in the thread, I'm in the process of finding a Windows XP computer or borrowing a computer from one of my friends, anyone care to try this, or confirm other methods to bypass this?

omarachs said:
This thread is a process of how to potentially get your phone prepared for these steps:
http://forum.xda-developers.com/moto-x/general/tut-resurrecting-bricked-moto-x-corrupt-t2629057
If your device says USB Input device and then disconnects after a few seconds, There is a potential theory as to how to bypass that.
After buying a "Factory cable" for the moto X for 10$ I plugged it into my computer and nothing, So i noticed that it would 'unplug' after it "installed" the driver. So i plugged it into the USB slot in my pc and found out that the green light not only showed up, but stayed on for a constant hour! This means that the phone must somehow still be alive and charging. The reason behind this is the fact that the TV didn't install the driver, but simply sent current to the cord. The problem is that if you've already installed the driver on your pc once, it will always fetch that same driver to install the device again. The bypass to that would be finding a Windows XP computer that asks if you'd like to install the drivers first. Or a Win 7/8 Pc that hasn't been connected to the Moto X yet. Go to devices and printers: right click my computer -> Driver installations -> Never install using Windows Update. This should allow you to install your own driver which is the one stated in the thread, I'm in the process of finding a Windows XP computer or borrowing a computer from one of my friends, anyone care to try this, or confirm other methods to bypass this?
Click to expand...
Click to collapse
Did it work?
I have the same problem and i want to know if it has a solution. Also, is it necessary to have a factory cable?

viversba said:
is it necessary to have a factory cable?
Click to expand...
Click to collapse
Nope. Battery can be disconnected at all
Author, why start new topic? See existing.
+ driver pack for Moto + Qualcomm in attachment, for your needs )

But does this method work?
Could you bring yout Moto x back to life with this method?

viversba said:
Could you bring yout Moto x back to life with this method?
Click to expand...
Click to collapse
Yep. 95% rate, if not a hardware issue