I have brought this up in a couple other threads but it was suggested I start a separate question. It's a good suggestion especially because doing so may help others in the future. Here's the situation. I have a VS980 that HAD TWRP and CrDroid. In the process of trying to flash another ROM, something went haywire. When I use Vol Down/Power to get to Recovery I get the Factory Data Reset screen which unfortunately says "ROOTED" at the top. Pushing power twice which would ordinarily get me to TWRP instead gets me to a LG Logo/Reset endless loop. The button combination which would usually get me to download mode gets me the same loop. However, if I continue to hold down Vol Up, I get Android System Recovery <3e> from which I CAN get the phone into sideload mode. Sideload is thus the only connectivity I have to the phone. Ordinarily I would think I could just sideload a ROM but when I try this, I get:
assert failed: run_program("/system/bin/loki.sh") == 0
E: Error in /tmp/update.zip
(Status 7)
Installation aborted.
Likewise I tried a bumped recovery, but this time it errored with /tmp/panelfix.sh.
Yes, sideload appears to be the only choice I have but I also confess I am not entirely clear on what bumping is exactly and how to do it.
Absent reviving this phone, I am stuck returning it to Verizon for a warranty replacement but this presents a problem since the factory data reset screen clearly says rooted. One thought that came to mind is if I got the official OTA zip that gets downloaded during OTA updates, I might not be able to sideload that and whether or not doing so is advisable. Any and all suggestions are greatly appreciated. Although I prefer being able to use Windows on my PC, I do have access to an Ubuntu VM I can run if that factors in at all.
Thanks in advance...
In an effort to further troubleshoot, since I now have 1 working LG G2 and the aforementioned misbehavor I was wondering if it would be possible to adb sideload from the good phone to the bum one and if so are there any particular apps or drivers needed (besides a terminal emulator)?
gospodinwizard said:
I have brought this up in a couple other threads but it was suggested I start a separate question. It's a good suggestion especially because doing so may help others in the future. Here's the situation. I have a VS980 that HAD TWRP and CrDroid. In the process of trying to flash another ROM, something went haywire. When I use Vol Down/Power to get to Recovery I get the Factory Data Reset screen which unfortunately says "ROOTED" at the top. Pushing power twice which would ordinarily get me to TWRP instead gets me to a LG Logo/Reset endless loop. The button combination which would usually get me to download mode gets me the same loop. However, if I continue to hold down Vol Up, I get Android System Recovery <3e> from which I CAN get the phone into sideload mode. Sideload is thus the only connectivity I have to the phone. Ordinarily I would think I could just sideload a ROM but when I try this, I get:
assert failed: run_program("/system/bin/loki.sh") == 0
E: Error in /tmp/update.zip
(Status 7)
Installation aborted.
Likewise I tried a bumped recovery, but this time it errored with /tmp/panelfix.sh.
Yes, sideload appears to be the only choice I have but I also confess I am not entirely clear on what bumping is exactly and how to do it.
Absent reviving this phone, I am stuck returning it to Verizon for a warranty replacement but this presents a problem since the factory data reset screen clearly says rooted. One thought that came to mind is if I got the official OTA zip that gets downloaded during OTA updates, I might not be able to sideload that and whether or not doing so is advisable. Any and all suggestions are greatly appreciated. Although I prefer being able to use Windows on my PC, I do have access to an Ubuntu VM I can run if that factors in at all.
Thanks in advance...
Click to expand...
Click to collapse
It's looking like [APP][4.0+] Craze - ADB Toolkit may be of some use here.
gospodinwizard said:
It's looking like [APP][4.0+] Craze - ADB Toolkit may be of some use here.
Click to expand...
Click to collapse
Doubt it. That just looks like an app built ontop of ADB.
Just in case you see replies before PMs, I sent you a PM with a modified CM11 zip. I bumped the boot.img and removed the asserts in the install script. Basically, it wont check your device to make sure it's right before installing/bring forward GAPPS/or check that the OTA is correct. None of these matter in your situation, and the errors they might give would just be a nuisance.
That zip if for VS980. I saw your profile says verizon, so I assume that's the right model.
/dev/sda
/dev/sda1
/dev/sda2
/dev/sda5
Nope not mounted as a device (ls -1 /dev/sd*)
Bus 001 Device 005: ID 1004:631f LG Electronics, Inc.
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Obviously it sees the phone (lsusb)
[ 1536.349950] usb 1-1: >new high-speed USB device number 5 using ehci_hcd
[ 1536.898447] usb 1-1: >New USB device found, idVendor=1004, idProduct=631f
[ 1536.898455] usb 1-1: >New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 1536.898460] usb 1-1: >Product: LGE Android Phone
[ 1536.898465] usb 1-1: >Manufacturer: LG Electronics Inc.
[ 1536.898468] usb 1-1: >SerialNumber: 094bbeb261899279
Again, it clearly sees the phone (dmesg).
So the question remains....why can I neither mount the phone or successfully sideload to it?
Related
Hello. I bought a Fascinate on craigslist like a week ago. I plugged it into my Ubuntu laptop and nothing came up, nothing even on `lsusb`. So I figure I'd just go ahead and follow the steps. So heimdall complains it can't find any devices. Also note, I am using a generic MicroUSB cable bought on ebay. [And also, I have also tried a LG microusb cord, no luck with that either]. My generic cord works to connect my Droid X2 absoultely fine.
So then I checked my syslog, and I got USB error messages [cannot enumerate usb port, etc]. I tried it in Windows and it said "The usb device has malfunctioned and is not recognized." So I call Samsung, they say I have a warranty thru this month [December], and I say I want to send it in for repair and they say I cannot unless I have the OEM cord and then they will troubleshoot via the phone, and if it still fails, then they will arrange it so I can send it in for repair/evaluation. So I look on Amazon and I find I can get one for only $1.50, no big deal. So I ordered that on Tue. and was expecting it to come today and it hasn't. Probably will arrive Monday.
So anyway, I had found some white gunk/lint out of the Fascinate's usb port, and I was getting sick of waiting for my OEM cord to come in the mail, so I figured I might try taking a brush and gently try to clean it. I find a small dental brush and I clean the port, going in and out on both edges, in the middle, and I did that for 10-15 seconds.
The moment of truth! I plug it in, and it shows up! I was so happy. First thing I do is load up the Fascinate "full upgrade guide" on Cyanogenmod wiki. I download and untar cwm4-bml-i500.tar, then turn off my phone, plug it in holding the Vol Down button, and it goes into Download mode. `lsusb` shows a Samsung device, and so I type in heimdall flash --recovery recovery.bin. The blue bar on my device goes all the way up, and the heimdall on my terminal showed 100%, and then I think it rebooted. So I think "I have CWM installed now." So I downloaded CM 7.1 for my fascinate, transferred it to my sdcard, and try to figure out how to boot into CWM.
I failed a few times, and I looked it up and it says you have to hold both volume buttons.
So I hold both volume after turning my phone on [while plugged into my laptop, because for some odd reason it always shows an "empty battery" animation and will not boot if not plugged in] and it loads the recovery.
First I thought my CWM version was old, because I could not install a zip from the sdcard, it only let me use "update.zip". So I renamed the file on my sdcard, went back into [what I thought was CWM] and it says the signature failed, and it could not install. Then I realize I must be in the stock Recovery mode.
Next, here are the error messages:
Code:
Dec 10 15:12:53 dv6 kernel: [ 482.350279] usb 5-3: new full speed USB device using xhci_hcd and address 12
Dec 10 15:12:53 dv6 kernel: [ 482.350783] usb 5-3: Device not responding to set address.
Dec 10 15:12:54 dv6 kernel: [ 482.560668] usb 5-3: Device not responding to set address.
Dec 10 15:12:54 dv6 kernel: [ 482.770314] usb 5-3: device not accepting address 12, error -71
Dec 10 15:12:54 dv6 kernel: [ 482.770409] hub 5-0:1.0: unable to enumerate USB device on port 3
That's my 3.0 USB, on my 2.0 USB it says
Code:
Dec 10 15:17:58 dv6 kernel: [ 786.540313] usb 3-1: new low speed USB device using ohci_hcd and address 32
Dec 10 15:17:58 dv6 kernel: [ 786.960277] usb 3-1: device not accepting address 32, error -62
Dec 10 15:17:58 dv6 kernel: [ 787.130185] usb 3-1: new low speed USB device using ohci_hcd and address 33
Dec 10 15:17:59 dv6 kernel: [ 787.550167] usb 3-1: device not accepting address 33, error -62
Dec 10 15:17:59 dv6 kernel: [ 787.550233] hub 3-0:1.0: unable to enumerate USB device on port 1
Alright, thanks for reading all that. Now, here are some questions I hope someone will be able to answer.
Is CWM installed? If I send it in, will Samsung say my warranty is void because I installed a custom recovery rom? Because I can't boot into CWM so I'm thinkin it didn't install.
Next, what is the cause of the error messages? 1/2 hour ago, after cleaning the port with a brush, it worked. I was able to upload cm7 to my sdcard. Then it just quit working. Any ideas?
One last thing, I tried z4root. I clicked "permanent root" and then it got to 'acquiring root shell' and then it just quits, not force close, it just closes and I'm dumped back into my app drawer. I thought 'hey maybe it worked' so I installed ROM Manager and then it says I'm not rooted.
So if I send it in, will Samsung say I've voided my warranty? And why didn't the CWM install work? Or is it installed, and I'm just doing something wrong? Thanks!
Matt
Check out the guide by Droidstyle. It is very simple and covers everything. Good luck.
Sent from my SCH-I500 using XDA App
So recently flashed CM 10.1 FUSION. Nexus battery drains, I end up turning it back on while on the charger. Then, it shuts down on me.. so I let it charge overnight. Turned it back, and I get stuck at a boot screen (FUSION). I attempt to turn my device off, and it just restarts. I have to turn it off from the bootloader (P+Up+Down).. I tried using the toolkit, but I freeze in the bootloader when I plug my device in.
Help.
Running 4.2.1
Yes I'm aware of the common problems, none of the solutions seem to be working.
Rovon said:
Yes I'm aware of the common problems, none of the solutions seem to be working.
Click to expand...
Click to collapse
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
bftb0 said:
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
Click to expand...
Click to collapse
I tried watching a majority of the "unbrick nexus 7" vids on youtube. They didn't get me too far
Holding power for a long time
Restarting bootloader
Root toolkit
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Rovon said:
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Click to expand...
Click to collapse
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
bftb0 said:
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
Click to expand...
Click to collapse
Sorry, I meant its frozen on the fastboot screen...
I can scroll through the fastboot, but that's it. None of the commands work, unless I hit power off. The toolkit tells me "fastboot device not found", when I try the Flash Stock + Unroot button. There is no device ID I can see on the toolkit. Also, drivers fail to install when I plug it in to my computer.
Rovon said:
None of the commands work, unless I hit power off.
Click to expand...
Click to collapse
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
bftb0 said:
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
Click to expand...
Click to collapse
I should've been more specific. When I say none of the commands work, I mean they don't do what they're supposed to. So if I hit "recovery mode" it will not go into recovery mode, it just stays stuck at the Google logo when it restarts.
As for device manager, when plugged in to the computer with Fastboot, I do get "android" under other devices. However, when I'm booting the device up regularly, the computer attempts to install drivers and fails. I do get "MTP USB Device" under portable devices. I have an unknown device under portable as well.
All 3 seem to have error symbols next to them.
Rovon said:
All 3 seem to have error symbols next to them.
Click to expand...
Click to collapse
Well, if you can't communicate with the device successfully, there's no hope of doing something correctly from the PC. So, try a few simple things on that angle of the problem first. The problem you are seeing could come from any number of places:
- damaged USB (or other) hardware on tablet
- bad / cheap USB cable
- damaged USB port on PC
- driver install issues
The symptoms you describe for fastboot sound a bit like the custom recovery got damaged or erased, although more severe (and not fixable) problems are also a possibility.
Since you previously installed a ROM, I would take it to mean that at one time you had at least one driver working (fastboot at a minimum), and possibly also ADB mode (in the OS and/or in the recovery). That's why I put "driver install issues" last in the short list above. If you never touched any of the drivers after you did your initial ROM installs, I would not expect driver issues ... but I don't know what you might have tried subsequently with the toolkit (which does fool around with drivers).
Are you using the OEM cable? Some aftermarket/charger cables have a short mini-USB connector, and one dollar cables off of eBay can be poorly constructed (bad shielding or impedance control, so they cause data errors at high speeds).
If you have an 2nd cable, I would try to see if you experience a different set of symptoms with that; same goes for trying a different USB port on your PC.
If you see errors in the Device Manager associated with fastboot I certainly would not be attempting any operation from the PC until you get that resolved. Note there is a huge difference between "unknown device" and a device showing errors - the latter suggests that the OS is aware of a driver which is supposed to be loaded when the tablet shows up on the USB bus, but then some malfunction occurs. That malfunction could either be hardware or an inappropriate driver.
Drivers
http://www.asus.com/Tablet_Mobile/Nexus_7#support_Download
http://forum.xda-developers.com/showthread.php?t=1426502
Note that you should be able to use the Asus driver for every mode of your Nexus 7 (except MTP and PTP, which are handled by Windows generic class drivers), including your custom recovery by doing the following:
A) Download the Asus Driver and unzip it someplace.
B) make a backup copy of the "android_winusb.inf" file (for instance "android_winusb.inf.backup")
C) Open up the "android_winusb.inf" file with the Notepad program (Note: not Wordpad!)
D) Find the ";Google Nexus 7" stanza in the [Google.NTx86] section and add this line:
%CustRecoveryADBAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
E) Add the same line (step D above) in the [Google.NTamd64] section
F) At the very bottom of the file in the [Strings] section, add the line
CustRecoveryADBAdbInterface = "Nexus 7 Custom Recovery ADB Interface"
G) Save the file and then proceed to do a manual de-installation of the drivers for fastboot and ADB.
H) Disconnect from the internet and then re-install the Asus driver for fastboot and ADB using the "Choose Location" method.
Don't know if that will work, but it's something to try; the problem you are having might lie outside the scope of what all of the above deals with
good luck
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Rovon said:
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Click to expand...
Click to collapse
Please describe what you found out and what DID work for you. Even if it was just a simple mis-understanding. It might help others in the future.
Probably you should also alter the title of your thread to be something much more descriptive - and add the keyword "[SOLVED]" to the title as well.
I did OTA update to 4.3 of my N7 3G which was rooted and unlocked (I know now I shouldn't have done it...).
I got an error at the end of the update (when was installing radio).
Rebooted, and got stuck in the google loop...
NOW, I CAN ENTER FASTBOOT MODE, BUT THE PROBLEM IS THAT THE USB DEVICE IS NO MORE DETECTED BY THE PC (I tried Windows XP, Windows 7, Linux), so I cannot re-flash it... It's not a driver's issue, because at USB level the N7 is not even detected when connected to the PC (for instance, dmesg shows nothing in ubuntu and windows does not "beep").
Is it possible that that was corrupted only the "USB stack" of the bootloader??? I could not find a similar issue in this or other forums (??).
Is there any chance to get the USB working again?
Is there any chance to send it for repair to ASUS (I bought it one month ago) with this described symptoms and with the "unlocked" icon on power on?
Is there a payed service to flash it with JTAG?
Thanks to anyone who can give me a clue...
Same problem - updated to 4.3 OTA today, N7 not recognized as an USB device at all. Still haven't tried on a Mac but I doubt it will be any different. The device isn't detected in normal mode or fastboot
c0ldblooded said:
Same problem - updated to 4.3 OTA today, N7 not recognized as an USB device at all. Still haven't tried on a Mac but I doubt it will be any different. The device isn't detected in normal mode or fastboot
Click to expand...
Click to collapse
I solved by sending it to assistance. Excellent service by ASUS... I did not have to pay although the tablet was unlocked/rooted.
Andrea.
since the new update to 4.3, N7 requires authorization with your pc before you can use ADB. I had this issue and had to go into developer options and click on the 'Revoke USB debugging authorization'. when I connect it to the pc again and ran adb, my N7 then asked for authorization to allow pc access. That restore my ADB.
Also make sure you have the lastest SDK installed on your pc too.
If you can enter Fastboot via pc you certainly can reflash it.
dilldoe said:
since the new update to 4.3, N7 requires authorization with your pc before you can use ADB. I had this issue and had to go into developer options and click on the 'Revoke USB debugging authorization'. when I connect it to the pc again and ran adb, my N7 then asked for authorization to allow pc access. That restore my ADB.
Also make sure you have the lastest SDK installed on your pc too.
If you can enter Fastboot via pc you certainly can reflash it.
Click to expand...
Click to collapse
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
andreabix said:
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
Click to expand...
Click to collapse
Exactly the case. Unfortunately I can't send it to ASUS
andreabix said:
In my case (and probably the same for Colblooded) I got stuck with the N7 NOT BOOTING and NOT DETECTED by any USB host (tried also with dmesg on linux), so there was no chance to re-flash it. The only thing I could do was to send it to Brno for repair...
Andrea
Click to expand...
Click to collapse
you said you could boot into fastboot, did 'fastboot devices' on your pc not detect it? Does it detect it now?
dilldoe said:
you said you could boot into fastboot, did 'fastboot devices' on your pc not detect it? Does it detect it now?
Click to expand...
Click to collapse
That's the point: I could boot into fastboot but 'fastboot device' was not detected by the PC (so I could not re-flash it). Now if I boot into fastboot the PC correctly detects the device...
What I find very, very strange is that an OTA update to 4.3 caused the USB port to stop working!! From what I read googling around, even with a problem during a system update going to fastboot mode (on + volume down) should always allow a connection to the PC for reflashing, or, at least, you could enter APX mode (on + volume up), which is an even lower level mode that is detected by the PC with different drivers (for direct programming, but need encryption key and SW not yet available for Nexus 7).
Maybe it was just a coincidence: an USB hardware failure just before I did the OTA update, which I realized only afterwards, when I needed USB for reflashing...
However the ASUS Service Repair Report states:
Problem/Symptoms: Pad Battery can't be charged. OS ERROR
Replaced Part:
ME370TG BAT COSLI-POLY FPAC
ME370TG MAIN_BD.1G/T30L/NFC
The first one looks the battery (????)
The second sounds like the mainboard...
Andrea
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!
Hey all,
My trusty Nexus 10 has been acting awry as of late. Because of this, I decided the best thing to do would be to flash a stock Nexus image from Google. So I downloaded the image, put my Nexus 10 into fastboot mode and... nothing. Well, it does say something now that I think about it. It states "The last USB device you connected to this computer has malfunctioned, and Windows doesn't recognize it". When I go into device manger, it says "Unknown USB Device (USB device descriptor failed)" is the name of the Nexus 10. I've tried different USB cords, different USB ports, I've done a fresh install of Windows on my PC (for different reasons, but still). I don't know what's going on, but I'd really like to get it solved. And that is precisely why I've come to you guys. Any advice would be greatly appreciated.
Thanks
Mario119 said:
Hey all,
My trusty Nexus 10 has been acting awry as of late. Because of this, I decided the best thing to do would be to flash a stock Nexus image from Google. So I downloaded the image, put my Nexus 10 into fastboot mode and... nothing. Well, it does say something now that I think about it. It states "The last USB device you connected to this computer has malfunctioned, and Windows doesn't recognize it". When I go into device manger, it says "Unknown USB Device (USB device descriptor failed)" is the name of the Nexus 10. I've tried different USB cords, different USB ports, I've done a fresh install of Windows on my PC (for different reasons, but still). I don't know what's going on, but I'd really like to get it solved. And that is precisely why I've come to you guys. Any advice would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
it sounds like you need to reinstall your drivers. An easy way to do it is to install Wug's Toolkit. It will fetch the drivers for you. Then you can either use Wug's or adb / fastboot to access your device.