I have a Motorola Droid 4. I installed SafeStrap recently on it and installed CM11 to the stock rom (mistake I know). I kept running into issues and I finally sorted all of them out and I decided I wanted to restore back to stock and then install CM11 to a rom slot. I come to find out that I am unable to restore my stock backup as it keeps failing. So I then decide I am going to just go ahead and restore my CM11 backup to rom slot 1 and make it the active boot rom, but that turned out to fail to for whatever reason. I reboot my phone several times and received the Motorola logo followed by the dreaded Android on his back with his chest opened up and the exclamation point/triangle coming out of it.
So I gave in and decided to just go ahead and use the Droid Razr Utility that I have used before to reinstall the stock ROM and start all over. During this process everything seems to be going fine. I am able to boot into Fastboot, the PC recognized the phone and can see it. I then start the recovery by doing option "2" to wipe and install. My phone reboots a couple of times and then comes to the point of another reboot but the phone never turned back on. I've tried many button combinations to get this to boot up but nothing seems to respond. I have attached a screenshot of what the Droid Razr Utility showed when the phone was attempting to restart but never did.
I purchased a Fastboot cable to hopefully get me to the point of my PC recognizing the phone but that does not seem to work. When I plug in my phone Windows never detects anything. I removed all the drivers and nothing. If I plug the phone into a charger the Green light flashes for a split second. If I plug my phone into the computer the Green LED light will stay solid. According to Motorola this indicates that the battery is fully charged. I've tried reseating the battery to no avail.
So based on the information above and the attached screenshot, is my Droid 4 bricked and unusable now?
After doing a bunch of research I think I indeed bricked my phone. Since the ROM I tried flashing to my phone was not for the Droid 4 but rather the Droid RAZR, it looks like my phone is dead. I was hopeful and assumed that this would be able to be reversed by hooking up to a PC but apparently that is not the case. Perhaps I tripped the eFuse or something which is causing the boot loader to not initiate. I guess I need to get a new phone now unless someone has a nifty trick up their sleeve to get the phone accessible via a computer.
You are going to need a Team Black Hat cable, aka fastboot cable. Then plug it in, and run RSD Lite using the DROID 4's fastboot files. You can find the fastboot files at this website below. Download the one that matches the version of Android you have.
LINK: http://sbf.droid-developers.org/phone.php?device=11
Ordered a factory cable on eBay; we shall see; thanks for the information
Even though my computer does not seem to recognize my phone when I plug it in. For example, I plug it in using the Fastboot cable and I never heard a sound from my computer like it knows something was just plugged in?
I did buy a fastboot cable from bluvector on amazon but that didn't seem to do anything for me. My Droid 4 still has a black screen and plays dead:crying:
bean1975 said:
Ordered a factory cable on eBay; we shall see; thanks for the information
Click to expand...
Click to collapse
Are you having the same problem as me? Your Droid 4 will not turn on and just sits at a black screen when you push the power button?
@sd_shadow you out there? I would love to hear your advice on my issue to see if there is any hope for my phone.
I received a FastBoot Cable but when I plug it in nothing happens. I also have a Kindle Fire HD and plugged the fastboot cable into it and powerd it down and back on and it boots normally. I'm wondering if the fastboot cable is faulty? Also I think my droid 4 may be completely shot since pushing the power button does nothing for me so I don't know how I could get back into Fastboot mode, unless a confirmed working fastboot cable will force the phone to boot and enter fastboot mode?
BigPapaGotti said:
@sd_shadow you out there? I would love to hear your advice on my issue to see if there is any hope for my phone.
I received a FastBoot Cable but when I plug it in nothing happens. I also have a Kindle Fire HD and plugged the fastboot cable into it and powerd it down and back on and it boots normally. I'm wondering if the fastboot cable is faulty? Also I think my droid 4 may be completely shot since pushing the power button does nothing for me so I don't know how I could get back into Fastboot mode, unless a confirmed working fastboot cable will force the phone to boot and enter fastboot mode?
Click to expand...
Click to collapse
Motorola Devices will be powered by the Fastboot/Factory cable, when you connect the Droid 4 to pc via a fastboot cable, it should power on but you may need to select fastboot mode in bootmenu options.
Not sure about the kindle HD, but an Original Kindle Fire 1st gen, will boot direct to fastboot mode, when connected to a Fastboot cable
Both require Hardware cable and device to be working correctly.
sd_shadow said:
Motorola Devices will be powered by the Fastboot/Factory cable, when you connect the Droid 4 to pc via a fastboot cable, it should power on but you may need to select fastboot mode in bootmenu options.
Not sure about the kindle HD, but an Original Kindle Fire 1st gen, will boot direct to fastboot mode, when connected to a Fastboot cable
Both require Hardware cable and device to be working correctly.
Click to expand...
Click to collapse
According to the description on the amazon site that I bought this cable from it shows the cable as being able to support Kindle Fire HD, that is why I am thinking that this cable is faulty, since it is not working on my droid nor is it working on my Kindle Fire.
I am thinking on buying a different one and returning my current one but i'm hesitant to do so. I have my doubts that this will allow my Droid 4 to boot up and/or be recognized by my computer. Since I get no response with the Vol-, Vol+, Power button combinations i'm thinking this is hard bricked because of the wrong files I flashed to it.
Before I made this mistake the phone was at least responsive showing the android/exclamation point screen. Then my dumbass ran the wrong flashing utility and that was all she wrote.
Do you think there is hope for my my phone even though the power button yields no response? If the fastboot cable will at least allow my phone to be recognized by my computer then I think i could save it, but that is where i have my doubts, but would love to try.
BigPapaGotti said:
According to the description on the amazon site that I bought this cable from it shows the cable as being able to support Kindle Fire HD, that is why I am thinking that this cable is faulty, since it is not working on my droid nor is it working on my Kindle Fire.
I am thinking on buying a different one and returning my current one but i'm hesitant to do so. I have my doubts that this will allow my Droid 4 to boot up and/or be recognized by my computer. Since I get no response with the Vol-, Vol+, Power button combinations i'm thinking this is hard bricked because of the wrong files I flashed to it.
Before I made this mistake the phone was at least responsive showing the android/exclamation point screen. Then my dumbass ran the wrong flashing utility and that was all she wrote.
Do you think there is hope for my my phone even though the power button yields no response? If the fastboot cable will at least allow my phone to be recognized by my computer then I think i could save it, but that is where i have my doubts, but would love to try.
Click to expand...
Click to collapse
If you flashed Droid Razr firmware, yes it's bricked. or haven't seen anyone recovery from that yet.
@bean1975, did you have any luck with getting the fastboot cable to recover your phone?
Related
Hi, I have 2 bricked KFHD's 7" after trying to Root them, I have just received my SKORPN Factory Cable, followed the instructions as sent by the man himself and nothing, any ideas????? I was under the impression that the battery does not need to be charged and that connection would put the Kindles into Fastboot to allow me to flash the devices, I am at a loss as to what to do, i know my ADB drivers are installed correctly as it shows in Device Manager on my PC when I connect my wifes' KFHD.
Please Help - failing my efforts does anyone know of anyone who repairs these devices?
FatedBoot said:
Hi, I have 2 bricked KFHD's 7" after trying to Root them, I have just received my SKORPN Factory Cable, followed the instructions as sent by the man himself and nothing, any ideas????? I was under the impression that the battery does not need to be charged and that connection would put the Kindles into Fastboot to allow me to flash the devices, I am at a loss as to what to do, i know my ADB drivers are installed correctly as it shows in Device Manager on my PC when I connect my wifes' KFHD.
Please Help - failing my efforts does anyone know of anyone who repairs these devices?
Click to expand...
Click to collapse
Other than "bricked", what state are the devices in? Better yet...What were the instructions that Skorpn gave you?
Both Kindles are totally unresponsive, have tried previous Factory cables but no use. I bought the SKORPN cable as it has such good reviews and the instructions are as follows, sent with the cable;
1) Turn OFF the Kindle Fire and wait 30 seconds or so, (mine don't even turn on so no problem there).
2) First, plug the USB Micro-B end into the Kindle Fire.
3) Then plug the standard Type-A end into the computer.
4) Profit...
Exactly as typed on the accompanying paperwork.
FatedBoot said:
Both Kindles are totally unresponsive
Click to expand...
Click to collapse
Totally unresponsive, how? Unresponsive as in...there is nothing on the display and nothing happens when you press the power button? Do you mean that kind of "totally unresponsive"?
Exactly that, nothing happens with the power button pressed, nothing on the screen
Your device is lost, unfortunately. What exactly did you do to it before this happened?
Just tried rooting them, all seemed to be going well until the reboot process and they never turned on again - never mind, off to the bin they go - cheers for your help
FatedBoot said:
Just tried rooting them, all seemed to be going well until the reboot process and they never turned on again - never mind, off to the bin they go - cheers for your help
Click to expand...
Click to collapse
Yet another "Kindle fire utility" Victim!
I'll assume you used kindle fire utility since this is the only tool that tries to install a 2nd bootloader along with root (flashing the wrong bootloader is the only thing that causes a device to not even power up), What you need to do now is contact amazon and send it back to them they'll most likely give you a replacement!
Or you can send it to prokennexusa At
Xerocomm, Inc
Attn: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954
He'll fix it for you and you can always thank him by giving him a small donation!
I have searched around for a couple days, but there doesn't seem to be anyone who has posted about this issue with a Droid 4. So here is what I have.
I rooted my Droid 4 using the RazrBlade method without incident. Afterwards I wanted to flash Cyanogenmod onto it, but did not have a custom recovery like ClockworkMod or TWRP set up yet. So, looking around led me to download the latest safestrap .apk so I would have a recovery capable of flashing Cyanogenmod. The latest version of safestrap would not work for me because of a parsing error, I looked around and found that some people were having the same issue and fixed it by downloading an earlier version of safestrap to their Droid 4. So, I found a safestrap 2.x.x version, downloaded that and followed the directions accordingly. I now had a functional (to my knowledge) recovery that would allow me to flash CyanogenMod. So I downloaded the .zip file from the CyanogenMod website for Droid 4, and attempted to flash it using the recovery that safestrap 2.x.x set up.
Everything looked okay for the install, no errors were reported, phone was at least at 80% battery, but once the phone rebooted, after the Motorola spash screen, there was a blank screen. The phone is on, evidenced by the backlight being visibly seen, but otherwise there is no evidence that it is trying to boot up any ROM. There is no loop whatsoever, just a blank screen.
First, I thought it was a bad install, afterall, it wouldn't be the first time. But when I turned it off (only possible via PWR&Vol.- button combo) it did not give the option to go into the safestrap recovery mode upon booting back up.
But I am not without a working knowledge of how to pull a phone out of a softbrick state, so I quickly connected my phone to a computer set up to take adb commands and tried to reboot my phone into the recovery mode. I connected my phone to my PC, left it on the blank screen mode and typed the adb command [adb devices] to confirm that it was acknowledged by my computer, it was, and attempted to reboot it into the recovery mode with the command [fastboot reboot-recovery]. It responded by rebooting, but led back to the backlit blank screen. I thought that this might be an issue with the wires or drivers or something to that effect, so I reattempted with a usb cord that was supplied by Motorola, and reinstalled all the appropriate drivers. Nothing worked, so I moved everything to a new computer freshly set up to take adb commands. I connected my phone and it was immediately recognized by the new computer, but it still would not respond to any adb commands. Attempting to reboot into recovery yields a blank screen still.
By this point I do not care if my phone is rooted or if I have to restore it to factory settings. So I look up solutions that flash it back to the stock 4.1.2 ROM. I find one that does this, but it requires that I am in AP Fastboot Flash Mode. I put it in the aforementioned mode, but it is not recognized by the adb terminal. It is listed as an adb device if it is in "blank screen mode" but not while in AP Fastboot Flash Mode. Shortly after this the battery is too low to program anyway, so I turn it off and set it to charge. But instead of a "battery charging" screen, I am greeted with the Motorola splash screen for as long as the phone is connected to the charger. Every time the phone is removed from the charger it, immediately and without pause, loses power and cannot be powered on until placed back on a charger.
Looking around some more, because I am increasingly desperate to solve this problem, I find something called RSD Lite, which will reflash the stock firmware to the phone and it will behave as if it was reset to factory settings. I plug the phone up to the computer, it powers on, I boot it up to the AP Fastboot Flash Mode and RSD Lite sees the phone as a fastboot device, and is ready and willing to fix it, but the battery is too low to program.
The battery is incapable of being charged by a wall outlet by any means that I have tried (will list below), BUT... If I connect my phone to a computer, and after the phone is connected, turn the phone off, a little green LED light appears at the top left and stays for at least 15 minutes until the Motorola splash logo appears and my phone connects to the computer. The phone recieves power in this mode evidenced by the fact that it does not instantly power down after it is disconnected from the power source. But at this point in time, the battery does not charge enough to cause a change in the AP Fastboot Flash Mode to allow it to be OK to Program.
Here is some misc info that might be needed:
Modes that I have access to
1.) Motorola Splash Screen + "Blank Screen Mode": This mode connects to the computer and is registered by the device number XT894. After the Moto Splash Screen there is a backlit blank screen I call "Blank Screen Mode". This mode is recognized by adb commands but not by RSD Lite. Any time an adb command is used apart from rebooting, command prompt says <waiting for device> and the device does not respond.
2.) Motorola Splash Screen Only: This mode is only accessible by connecting the phone to a wall outlet. This mode does not charge the phone and if the phone does not have any power otherwise, will power down without warning upon being disconnected from the power source.
3.) Boot Mode Selection Menu: This mode provides various options that appear to do nothing. The "Recovery" option that is supposed to bring me to the default android recovery mode instead brings me to the Motorola Boot Logo and then to a green android laying down with a red triangle over it (with an exclamation point). I am able to access AP Fastboot Flash Mode from here.
4.) AP Fastboot Flash Mode: In this mode, the device is recognized by the computer as an adb fastboot device (not as an XT894 device). It does not respond to adb commands, and the adb terminal does not acknowledge the phone in this mode. RSD Lite does acknowledge the phone in this mode, but trying to begin the process to reflash the stock firmware causes the "Low Battery/ No Program" text on the phone to flicker and result in a failure in the RSD Lite program. It lists the reason as: Phone return(ed) Fail.
5.) Computer Charging Mode: When connected to a computer, and immidiately powered off, a green LED light turns on. After leaving the phone for some time, the phone can be disconnected and stands on it's own power without needing to be connected to a power source to remain on. In this mode, the screen is not on, and the phone is not recognized by the computer at all.
Methods I Have Attempted to Use to Charge Phone
1.) Plugging Moto Stock USB charging cable to computer and leaving it: This causes the 1st mode listed above to occur, and no charge is held. After 10 minutes of "charging" upon disconnecting cable, phone shuts off abruptly, and without any warning.
2.) Plugging Moto Stock USB into USB to Wall Outlet Plug: This causes 2nd Mode listed with similar results to above.
3.) Plugging Motorola Wall Outlet Charging Cable to Phone: See above
4.) ALL Above Methods + Boot Mode Selection Menu BD Tools Mode: I read that if you were to connect your phone to a wall outlet after booting it up into the Boot Mode Selection Menu, and selecting BD Tools, the phone would boot up to the Motorola Boot Logo screen, then show a battery charging similarly to how one does if you charge your phone after it shuts down from having 0% Battery. This was not the result I received. Similar results to #1
I apologize if there is some blatant simple answer here, but I have looked everywhere to find a solution to no avail. I included everything that occured between then and now so as to facilitate this process, and hope that I am not stepping on any toes with the wall of text I just posted.
Thanks in advance, if more info is needed (or if the post needs to be formatted in an easier to read way) just say so.
Sounds like you will need a motorola factory cable. I think that's what they are called. It provides power directly to the phone allowing you to fastboot. I know you can find them on ebay. I believe team black hat also sells an adapter to turn your regular OEM cable into a factory cable.
Your other alternative would be to sacrafice a usb cable and attach to the battery terminals directly to charge the battery. If you google it you should be able to find directions for how to do this. I believe someone posted a how to on youtube for the razr which should give you a good idea of what you would be getting into.
Good luck!
Droid 4 - Avatar
Fixed It
Thanks for the help.
I didn't feel like paying $12 dollars and waiting several days to purchase one of those special factory cables, so I ended up taking a non-USB charger, spicing it, and hooking it directly to the battery terminals like you said. After I did that, it automatically said that it was "OK to Program".
The only problem I had was that RSD Lite wasn't able to fix it, I had to download some other app that ran things through command prompt while the device was in AP Fastboot mode. But the end result was the same.
I found out that the problem that caused all this was me not flashing the CyanogenMod firmware into ROM Slot-1 while in the safestrap recovery mode. I flashed it to the "Stock" ROM Slot instead.
Thanks again for the help, I learned a lot, and I am glad I didn't have to shell out money for a new phone. :laugh:
My attempt to root my stock Jelly Bean Droid 4 two night was inadvertently interrupted (cable was accidentally disconnected mid-process) and now I can't get it to do anything. It won't charge or boot into any mode at all.
I ordered a factory adapter from Team Black Hat, which arrived today (California to NY in two days, not bad USPS). I attached the adaptr, plugged it into my phone, and then connected it to my computer using the USB cable that came with the phone. Nothing happened. I left it a few minutes, and then tried the power button and the power + volume to try and get it into recovery mode. Still nothing. I've also tried a few different cables, to the same result.
When I remove the adapter and just plug in the cable, the green LED turns on and stays on, but only when connected to my PC. Plugging into the wall charger does nothing.
Have a missed a step some place or is my phone completely knackered?
Which program did you use to root?
Sent from my Amazon Kindle Fire using Tapatalk
sd_shadow said:
Which program did you use to root?
Click to expand...
Click to collapse
Razr Blade. I had rooted using this method once before, but unrooted to get the OTA update that came out in January. I was in the process of trying to re-root when the cable was disconnected.
Some more info that might be helpful - my PC does not recognize that anything is plugged in (tried in different ports on two different computers).
I did some deeper digging and I fear I might have accidentally started flashing the wrong firmware, rather than running the exploit. In any event, the process was interrupted before anything could complete and I recall seeing a failed message twice, although I can't unfortunately recall what that error referred to.
I'm assuming at this point that I've hard bricked it and need to get a new phone.
If you were using [SCRIPT] DROID RAZR Utility XT912 Jellybean -- Windows + Mac + Linux (All In One!)
instead of the Droid 4 utility or just the original razr blade root by Dan Rosenberg
and selected flash firmware, yes the Droid Razr firmware will brick the Droid 4.
I had a different ROM and tried to go back to stock so i can sell my kindle. I wiped everything using twrp, transfered rom file from pc using 'adb sideload' and restarted kindle without flashing new rom (i know, i'm idiot). Now i'm stuck at the Kindle Fire logo screen, and my pc cant detect kindle (it doesn't show anything in device manager)
I also bought factory cable from ebay seller 'connekt', but results are the same like with ordinary micro usb cable.
Now i want to try this: http://forum.xda-developers.com/showthread.php?t=1430038
I opened my kindle but i dont know where i should do shorting . Please help
Thanks in advance
nik011 said:
I had a different ROM and tried to go back to stock so i can sell my kindle. I wiped everything using twrp, transfered rom file prom pc using 'adb sideload' and restarted kindle without flashing new rom (i know, i'm idiot). Now i'm stuck at the Kindle Fire logo screen, and my pc cant detect kindle (it doesn't show anything in device manager)
I also bought factory cable from ebay seller 'connekt', but results are the same like with ordinary micro usb cable.
Now i want to try this: http://forum.xda-developers.com/showthread.php?t=1430038
I opened my kindle but i dont know where i should do shorting . Please help
Thanks in advance
Click to expand...
Click to collapse
Ok since that's from the kf1 forum i'm going to say this now, do not bother with the shorting trick as it does not work on the 2nd gen kindles. We would need a signed aboot for that. You are going to need a fastboot adapter to fix it, go for the blackhat one since they are reputable and your ebay one doesn't work. http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
I thought at first you were attempting to short the usb from the board to get to fastboot but i don't suggest that method as you are liable to short something out if you hit the wrong spot.
Omg, you were right. I just cut 'factory' cable i got from ebay (also cut my finger) and it is just a regular 4 pin micro usb cable.
Haha, i wont try to short usb from the board i already have enough problems Will just order that factory adapter you mentioned.
Thanks for the fast answer
My fire 5th gen tablet worked for the longest time with gow but I was gonna change the boot screen with a boot animation changer and now I cant get my computer to recognise that its hooked up while it is now stuck in a boot loop although i can still get to fast boot and stock recovery but with the computer not pickup when I hook it up how can I do anything please help asap the last rom that was on it before I flashed to amazon nexus by gow was 5.3.10 fire os.
Crashoverride1993 said:
My fire 5th gen tablet worked for the longest time with gow but I was gonna change the boot screen with a boot animation changer and now I cant get my computer to recognise that its hooked up while it is now stuck in a boot loop although i can still get to fast boot and stock recovery but with the computer not pickup when I hook it up how can I do anything please help asap the last rom that was on it before I flashed to amazon nexus by gow was 5.3.10 fire os.
Click to expand...
Click to collapse
Reboot PC. Try changing the USB cable; amazing how often this is the culprit. Also try a different USB port, preferably USB2. Avoid external hubs which can block tethered communications. If all else fails try a different computer.
Davey126 said:
Reboot PC. Try changing the USB cable; amazing how often this is the culprit. Also try a different USB port, preferably USB2. Avoid external hubs which can block tethered communications. If all else fails try a different computer.
Click to expand...
Click to collapse
is it possible for 3 Diffrent USB cables to be bad all at once one of them is relatively new and if this was not enough I tryed on my desktop and it too is not seeing the tablet If I had been the one that had the funds to by it I would have gotten a much more hackable tablet but this one was a christmas gift.
Crashoverride1993 said:
is it possible for 3 Diffrent USB cables to be bad all at once one of them is relatively new and if this was not enough I tryed on my desktop and it too is not seeing the tablet If I had been the one that had the funds to by it I would have gotten a much more hackable tablet but this one was a christmas gift.
Click to expand...
Click to collapse
Probably not. Possible device has a problem with USB port. Open Windows Device Manager; look for any activity while tethering/untethering while device is in recovery mode (specifically the option that permits reloading FireOS).
Davey126 said:
Probably not. Possible device has a problem with USB port. Open Windows Device Manager; look for any activity while tethering/untethering while device is in recovery mode (specifically the option that permits reloading FireOS).
Click to expand...
Click to collapse
I got it recognising it in fastboot but not adb can I restore it with fastboot somehow
Crashoverride1993 said:
I got it recognising it in fastboot but not adb can I restore it with fastboot somehow
Click to expand...
Click to collapse
Unfortunately, no as fastboot environment is crippled on this device.
Davey126 said:
Unfortunately, no as fastboot environment is crippled on this device.
Click to expand...
Click to collapse
I dont know why it dosent see the device when booted into adb but it dosent but it see's the device booted as fast boot so what could be wrong Also the adb sees it when its constantly rebooting from the boot loop but its only temporary because when it reboots it temporarly disconnects so any thing else I really want to fix this thing but dont know what else to do.
Crashoverride1993 said:
I dont know why it dosent see the device when booted into adb but it dosent but it see's the device booted as fast boot so what could be wrong Also the adb sees it when its constantly rebooting from the boot loop but its only temporary because when it reboots it temporarly disconnects so any thing else I really want to fix this thing but dont know what else to do.
Click to expand...
Click to collapse
Assume you are selecting "apply update from ADB" in recovery *prior* to adb connection attempt. While a long shot also try the two wipe options although I'd be surprised if either changed the situation.
Good chance irreversible damage occurred when you tried to change the bootloader (vs ROM) boot animation. As the bootloader is locked on this device little more can be done beyond the steps previously outlined.
yes I tried the wipe options nothing changed as for adb update I tried while connected and when I tried that app I thought it was gonna change the ROM animation I dont think the bootloader was quite touched as it still says amazon and then shows the custom boot screen then reboots without actually booting the rom but yes the the rom boot screen was my intended change Good news I think however is I belive now that my cable is faulty because When messing with it it seems while in adb mode I get unknown device
Crashoverride1993 said:
yes I tried the wipe options nothing changed as for adb update I tried while connected and when I tried that app I thought it was gonna change the ROM animation I dont think the bootloader was quite touched as it still says amazon and then shows the custom boot screen then reboots without actually booting the rom but yes the the rom boot screen was my intended change Good news I think however is I belive now that my cable is faulty because When messing with it it seems while in adb mode I get unknown device
Click to expand...
Click to collapse
That was the first thing mentioned and is often the primary culprit. Add your experience to countless others who dismiss or underweight potential cable issues. Also look for a loose USB connector (rare) which can exhibit similar symptoms.
Davey126 said:
That was the first thing mentioned and is often the primary culprit. Add your experience to countless others who dismiss or underweight potential cable issues. Also look for a loose USB connector (rare) which can exhibit similar symptoms.
Click to expand...
Click to collapse
Its weird that the cable is the problem cause it seems 3 did nothing and one says unknown device buying another cable though Im not sure when I can do.
Crashoverride1993 said:
Its weird that the cable is the problem cause it seems 3 did nothing and one says unknown device buying another cable though Im not sure when I can do.
Click to expand...
Click to collapse
Just giving an update I bought a brand new actual amazon usb cable and got it running again no sweat even rerooted and blocked ota updates