Hy everyone
Few days ago I've tried to update my Nexus 7 2012 model, from 4.2.2 operating system to 4.4. After few minutes, after reboot, on the screen shows the Android sign with an error mesage : No Command
The bigger problem is that in my Device Manager, my computer does not show the tablet, not even as an unknown device. This is how my Device Manger it is looks like:
I have tried all the internet tutorials, SDK Manager Drivers, PdaNet Drivers .. Nexus Toolkit .. and no results. My computer does not recognize the tablet, When i run abd devices .. returns nothing.
As i can't go inside, i'm not sure if the USB Debugging mode is activated or deactivated.
Please help me !!! I really don't know what to do
PS: When i'm trying to install the driver manually it says; Android ADB Interface - This device cannot start. (Code 10)
Can you boot into recovery or fastboot mode?
Sent from one of my 47 iPads running android C3P0
Captain Sweatpants said:
Can you boot into recovery or fastboot mode?
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
When i'm pressing power button+u up volume+down volume and chose recovery mode, after loading, i'm getting the same error, with the android sign and No Command error message.
When i am in fastboot mode, is the same problem, the device manager doesn't recognize the tablet, neither the adb or fastboot.
Is the tablet going into fastboot mode and not being recognised by the computer or is it not going into fastboot mode. If you can get fastboot mode the next stop would be to try the nexus toolkit http://www.wugfresh.com/nrt/ use the return to stock soft bricked option as far as the problems connecting to the computer did it connect before the boot loop and is it possible the port or the cable are damaged? If it goes into fast boot then it should be recognised.
Edit: I forgot to ask is your warranty still valid you get 2 years with the N7 you could send it to Asus.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:56 PM ---------- Previous post was at 09:23 PM ----------
Also read/try this
http://forum.xda-developers.com/showthread.php?t=2405740&page=4
Sent from my Nexus 7 using xda app-developers app
Captain Sweatpants said:
Is the tablet going into fastboot mode and not being recognised by the computer or is it not going into fastboot mode. If you can get fastboot mode the next stop would be to try the nexus toolkit http://www.wugfresh.com/nrt/ use the return to stock soft bricked option as far as the problems connecting to the computer did it connect before the boot loop and is it possible the port or the cable are damaged? If it goes into fast boot then it should be recognised.
Edit: I forgot to ask is your warranty still valid you get 2 years with the N7 you could send it to Asus.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 09:56 PM ---------- Previous post was at 09:23 PM ----------
Also read/try this
http://forum.xda-developers.com/showthread.php?t=2405740&page=4
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the reply. I can boot in fastboot but the PC still do not recognize the tablet. Even in fast boot Nexus Toolkit doesn't recognize the tablet .. I've tried to uninstall and reinstall the drivers but no success.
Is RMA an option? Was this an OTA update? Asus may take some responsibility for it then. Did the computer recognise the tablet before the problem we need to work out if its a software or a hardware problem that's stopping it from connecting to the computer.
Sent from one of my 47 iPads running android C3P0
Captain Sweatpants said:
Is RMA an option? Was this an OTA update? Asus may take some responsibility for it then. Did the computer recognise the tablet before the problem we need to work out if its a software or a hardware problem that's stopping it from connecting to the computer.
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
What means RMA ? .. the update was made by wireless connections. Unfortunately I'm in Romania now and the tablet was bought in USA., so I don't think Assus warranty is an option.
The computer was not recognizing the tablet before the update .. it was only charging but not recognizing. Every time I was uploading content on it over Dropbox.
The only time when my PC recognized the tablet was at the beginning, I don't know if I changed something or what I did but after that point the PC didn't recognize the tablet.. Even after that the tablet updates and everything was working perfectly.
RMA is Return Merchandise Authorisation it means Asus agreeing to accept a return. If the tablet was not connecting to the computer before the update then that is where the problem is. No Command bootloop is fixable but not without a USB connection. My advice would be to try a new USB port for the nexus you can get one on eBay UK try to find one that will ship to romania. The other option is to buy a N7 with a broken screen and use parts out of that. Its not much more expensive to buy a broken N7 than to buy the charging port. The advantage to that is you can swap the motherboard as well and you don't need to fix the boot loop.
Sent from one of my 47 iPads running android C3P0
Captain Sweatpants said:
RMA is Return Merchandise Authorisation it means Asus agreeing to accept a return. If the tablet was not connecting to the computer before the update then that is where the problem is. No Command bootloop is fixable but not without a USB connection. My advice would be to try a new USB port for the nexus you can get one on eBay UK try to find one that will ship to romania. The other option is to buy a N7 with a broken screen and use parts out of that. Its not much more expensive to buy a broken N7 than to buy the charging port. The advantage to that is you can swap the motherboard as well and you don't need to fix the boot loop.
Sent from one of my 47 iPads running android C3P0
Click to expand...
Click to collapse
Thank you for the reply. But is the tablet is charging properly both from the PC and from the wall charger. It is possible to charge properly but the data transfer to be broken because of the micro usb from nexus 7 ?
Yes it is possible to damage the data circuit while leaving the charging circuit intact unfortunately unless you know much about micro electronics I can't tell you exactly where that damage is but it definetly sounds like a hardware failure. My best guess would be the USB port. On the Nexus the USB port is separate from the motherboard and is connected by a ribbon cable. The other possibility is that the motherboard is at fault. As the motherboard is where the bootloop is happening from changing it would also make the tablet work. Either way the only way to get your nexus working again is to fix the USB connection and it sounds like that's going to mean new parts.
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Yes it is possible to damage the data circuit while leaving the charging circuit intact unfortunately unless you know much about micro electronics I can't tell you exactly where that damage is but it definetly sounds like a hardware failure. My best guess would be the USB port. On the Nexus the USB port is separate from the motherboard and is connected by a ribbon cable. The other possibility is that the motherboard is at fault. As the motherboard is where the bootloop is happening from changing it would also make the tablet work. Either way the only way to get your nexus working again is to fix the USB connection and it sounds like that's going to mean new parts.
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
Anybody know how I can test it the USB is broken ? As long is charging well both from the PC and from the wall charger too, but is the PC is not recognizing the tablet.
Thank you for the reply. But is the tablet is charging properly both from the PC and from the wall charger. It is possible to charge properly but the data transfer to be broken because of the micro usb from nexus 7 ?
Click to expand...
Click to collapse
alpinia said:
Anybody know how I can test it the USB is broken ? As long is charging well both from the PC and from the wall charger too, but is the PC is not recognizing the tablet.
Click to expand...
Click to collapse
OK, so I've changed the micro USB from my tablet, I've putted on another tablet and it works perfectly. I've tried with the other micro usb and the same problem, the PC doesn't see the tablet.
The PC saw the other tablet .. but it can't see mine.
SO the problem is not with the USB port, is with something else. Is possible to erase everything from my tablet .. so the pc cant see the tablet in fast boot mode ?
Is any option to install the operating system on my tablet without PC ? I don;t know .. with an usb stick or something ..
alpinia said:
OK, so I've changed the micro USB from my tablet, I've putted on another tablet and it works perfectly. I've tried with the other micro usb and the same problem, the PC doesn't see the tablet.
The PC saw the other tablet .. but it can't see mine.
SO the problem is not with the USB port, is with something else. Is possible to erase everything from my tablet .. so the pc cant see the tablet in fast boot mode ?
Is any option to install the operating system on my tablet without PC ? I don;t know .. with an usb stick or something ..
Click to expand...
Click to collapse
Any solutions ?
Back in November 2013, my rooted Nexus 7 took the OTA update to Kit Kat and had been in the No Command loop ever since.
I tried repeatedly to get my PC (4 of the each with multiple OS's XP, Win7, Win8.1) to recognize the N7 in connection with the Wugfresh kit. I followed the instructions step by step, still nothing. Finally yesterday after wiping an XP machine and replacing it with an up to date image (as of Oct 2013). I again started the process. 1. Downloaded and fired up Newest Wugfresh kit, allowed it to update; 2. Turned on the N7, put it into recovery mode; 3, Plug the N7 in and removed in Device Mgr whatever drivers XP opened (It found it as an Android device), looked in USBD for but found no other device matching the description in in Wugfresh. 3. Rebooted PC and plugged the N7. Loaded Wugfresh, since the N7 was essentially "dead" I skipped Step 2 and proceeded to Step 3 and loaded the recommended drivers 1 (Universal Drivers); went to step 4 and did the FULL DRIVER TEST. As per usual the klt could not find the ADB device. I was ready to pack it in, but earlier I had noticed the "safely remove device Icon" pop on the lower right hand corner of my screen when I ist plugged in the N7. It seems that XP had again recognized the device when I plugged it in. I clicked out of the driver install dialogue and went back to the Wugfresh tool kit main page and under "Back to Stock" clicked "soft-Bricked/Bootloop" and low and behold it started to work. It took a while, but unlike the numerous times I tried before, data was finally moving to the N7. I left it even after I saw "XXX not found" and then another "XXX2 file not found". It finally finished and I again had life on my N7. I Ieft Wugfresh running (even after I thought it was done, wait until it says...Done) l and followed the suggestions the Wugfresh kit made and it finally works again. It has kit kat installed and I'm leaving it unrooted......for now anyway.
Kit Kat update: longest damn update ever.
odd
alpinia said:
Hy everyone
Few days ago I've tried to update my Nexus 7 2012 model, from 4.2.2 operating system to 4.4. After few minutes, after reboot, on the screen shows the Android sign with an error mesage : No Command
The bigger problem is that in my Device Manager, my computer does not show the tablet, not even as an unknown device. This is how my Device Manger it is looks like:
I have tried all the internet tutorials, SDK Manager Drivers, PdaNet Drivers .. Nexus Toolkit .. and no results. My computer does not recognize the tablet, When i run abd devices .. returns nothing.
As i can't go inside, i'm not sure if the USB Debugging mode is activated or deactivated.
Please help me !!! I really don't know what to do
PS: When i'm trying to install the driver manually it says; Android ADB Interface - This device cannot start. (Code 10)
Click to expand...
Click to collapse
try restoring or using a custom rom!
My husbands pad is stuck in the same state, nothing irretrievable on it, so if I could get it back to factory settings, would be fine. Tried the toolkit, followed it, but not recognising it on the pc.
Can get it to display the Recovery mode, but if I try to select any of the options, it just switches off. Just keeps switching on and off if I leave it connected to pc, charges with either pc or cable.
Totally drained the battery to see if it helped, well getting to the stage to try anything.
Display when into Recovery screen
Fastboot Mode
Product Name - Flo
Variant flo 32g
HW Version - rev_e
Bootloader version - FLO-04.08
Carrier Info - None
Serial Number
Signing - Yes
Secure Boot - enabled
Lock state - locked
Related
Problem: USB driver failure for Nexus 4. The android composite USB driver loads. Portable device driver (MTP) does not.
I have the latest v7 Google USB drivers in the extras 4.2.2 SDK folder, and pointing the driver install to this folder has worked in the past. Now, I never get the portable device MTP to install. I have both windows 7 and windows 8 machines that used to recognize the phone. I suspect my phone USB firmware is corrupted ( or something else software related?), but don't know how to find or make a zip file I can flash via custom recovery to test my theory.
I've tried multiple USB cables, all which have worked in the past. Simultaneously, I can only charge at USB rate. This all started occurring a week ago.
Any recommendations?
LG-E960
A different Nexus 4 connects fine, mine has no response to USB. It will charge off the PC, but no adb device found, no fastboot device found, no portable device MTP. I think something is wrong with my USB firmware on the phone.
LG-E960
Are you sure usb fast charge is not on?
User failure in this case, install these drivers from here http://forum.xda-developers.com/showthread.php?t=1998650. Delete all excisting usb drivers and then reconnect to usb and prevent/stop windows from installing drivers. Open device manager in windows and select the N4 and install the 0.72 drivers and you`re done.
gee2012 said:
User failure in this case, install these drivers from here http://forum.xda-developers.com/showthread.php?t=1998650. Delete all excisting usb drivers and then reconnect to usb and prevent/stop windows from installing drivers. Open device manager in windows and select the N4 and install the 0.72 drivers and you`re done.
Click to expand...
Click to collapse
I'm having the same problem, ADB, MTP none of it works, I've tried every method including yours. Worst part of it is that nothing happens in the device manager when i plug in Nexus 4 so i can't update drivers manually too. It used to work great with both MTP, ADB etc. Stopped working all of a sudden...Help please anyone. The phone is pretty much useless without MTP or ADB for me.
I too,, have tried to clear all old drivers and use the universal driver, but nothing works. I went through the tedious windows 8 advanced startup to allow unsigned drivers.
LG-E960
This sucks. I still cant resolve this, and 4.3 is coming. Maybe I'll try Ubuntu.
Sent from my Nexus 4 using Tapatalk 4 Beta
Still sucks
LG-E960, Tapatalk b4
Problem with Nexus 4
Any updates about this?
I'm going through the same thing with my Nexus 4.
No response to USB, except charging.
No ADB, No Fastboot, No MTP nothing at all, it's as if the system detects only a device that uses power from the USB port and nothing else.
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
muzicfreako said:
I'm having the same problem, ADB, MTP none of it works, I've tried every method including yours. Worst part of it is that nothing happens in the device manager when i plug in Nexus 4 so i can't update drivers manually too. It used to work great with both MTP, ADB etc. Stopped working all of a sudden...Help please anyone. The phone is pretty much useless without MTP or ADB for me.
Click to expand...
Click to collapse
Any updates about this?
I'm going through the same thing with my Nexus 4.
Adeelx said:
Any updates about this?
I'm going through the same thing with my Nexus 4.
No response to USB, except charging.
No ADB, No Fastboot, No MTP nothing at all, it's as if the system detects only a device that uses power from the USB port and nothing else.
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
Any updates about this?
I'm going through the same thing with my Nexus 4.
Click to expand...
Click to collapse
It was a hardware problem at my end. My nexus 4 wasn't detected at all in any computers.
muzicfreako said:
It was a hardware problem at my end. My nexus 4 wasn't detected at all in any computers.
Click to expand...
Click to collapse
I still have the same problem as you.
LG-E960
Resolved
muzicfreako said:
It was a hardware problem at my end. My nexus 4 wasn't detected at all in any computers.
Click to expand...
Click to collapse
It was the same with my phone. Wasn't detected on other computers too.
Here's what led to the problem resolution (kinda):
1. Formatted /system, /data, /cache, and flashed CM 10.1.2: http://get.cm/get/jenkins/34261/cm-10.1.2-mako.zip
2. Restarted the phone, then I came upon this forum post which mentioned that Trickster MOD Kernel Settings should be used to test for fast charge.
3. To install Trickster Mod I had to have Play Store (and thus the GApps package), so I rebooted into recovery.
4. After flashing the GApps package and rebooting the phone got detected and I was back in business.
5. Immediately flashed the factory image JDQ39 (it was the one I had available at the time.
6. Received the 4.3 OTA update about an hour ago and the phone is again back to not functioning on USB.
(Worth mentioning here that before this fiasco started, I was on CM 10.1.2, linked above.)
-- Update --
Rebooted a few times, phone appears on USB now and is there consistently, I'm beginning to think this is a hardware issue but I cannot apply for a warranty claim until the problem is consistent enough.
I've been having the same problem the last few weeks. I am on v4.3 stock. The phone is not being detected in any computer i've tried. I've used several USB cords and none of them work. The phone can be charged, but only in USB mode, so charging is slow, even when using AC charger.
I think this problem was triggered by charging on a cheap car charger. The Nexus 7 also can get into this state from what i've been reading.
I haven't come across a fix yet, so I think I'm going to RMA it before the warranty runs out.. its to bad though, I think this is a software problem related to 4.3. I used a lot of cheap chargers without this problem coming up before upgrading to 4.3.
Just go to storage settings and just try uncheck and re check the option of USB connection . It worked !! for me
Sent from my Nexus 4 using XDA Premium 4 mobile app
krishnan.sri92 said:
Just go to storage settings and just try uncheck and re check the option of USB connection . It worked !! for me
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried that. I also replaced the USB flexible circuit card ($25 amazon) and nothing changed. I'm glad their are people like xDA member, enfrant, that provides zip files for updating the phone, else I'd be stuck with a non- updateable nexus 4, which would be a nightmare for a flash junkie.
LG-E960
Very basic step but I've seen it being missed before:
- Go to Settings
- Storage
- Menu > USB computer Connection
- Check Media Device(MTP)
If this was not checked, checking it will make your computer download the necessary drivers if not present already.
MTP not detected Nexus4
jigarbond said:
Very basic step but I've seen it being missed before:
- Go to Settings
- Storage
- Menu > USB computer Connection
- Check Media Device(MTP)
If this was not checked, checking it will make your computer download the necessary drivers if not present already.
Click to expand...
Click to collapse
Hi There, i faced same problem. No matter what i did, still my XP could not detect my Nexus 4 storage. ( I must have deleted all drivers..samsung..nexus..android..from my device Manager when trying to install Nexus driver with WUGs Nexus Toolkits.) .BEST solution.."Restore System " to the date when everything was running fine.....walla.........problem solved:good::good::good:
krishnan.sri92 said:
Just go to storage settings and just try uncheck and re check the option of USB connection . It worked !! for me
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much - it worked for me as well!
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.
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!
Ok so long story short, i have a nexus 7 2012 which a rooted and installed cyanogen mod.
I was using it as a car install and works perfect, i'm using an otg cable to mount usb sticks, triggering soft shutdown and powering the nexus etc. So usb seems to be working fine.
Basically i removed the tablet it to modify the bootloader to turn on automatically with ac power applied, if the battery runs out i have to manually power on with button, but now i'm running into a problem.
Ever since taking the tablet out and trying to connect over usb, none of my computers detect the tablet.
I've tried different operating systems, drivers, cables etc etc.
Also changed from mtp to ptp in storage and also turned on usb debugging mode. If i connect an otg cable the nexus see's the otg and i can mount usb's etc.
So i thought i might try recover the nexus back to factory, maybe there was an issue with the rom corrupted etc, I've downloaded the original 4.2.2 firmware which is currently installed.
Booted into recovery and tried re-installing the 4.2.2 zip, it keeps aborting. A guy in work tried to use sideloader and connect via adb. no luck.
I'm not very familiar with the android platform so i've no other ideas what to do and other idea's how to recover now.
The guy i work with mentioned using a usb jig, would that be the way to go or can anyone else suggest some else that might help.
Thanks
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Does adb see the device
jadesse said:
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Click to expand...
Click to collapse
I last connected the nexus to the laptop a few monts back to load some music onto it, didn't have a problem. It's only been connected to a computer maybe 3 times. once to root/rom it then another few times to load music etc.
I can't see why the usb board maybe faulty as i can read data from a usb key when the otg cable is connected.
It's a strange one. You could be right, i might try pick up a broken nexus and swap some parts. Usb board etc.
crusrod said:
Does adb see the device
Click to expand...
Click to collapse
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
foster182 said:
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
Click to expand...
Click to collapse
I am having this same problem on my (unrooted) HTC One after attempting to "convert" it from an AT&T to a Google Play Edition device with the procedure described here.
As part of the procedure, I attempted to flash the stock Google Play Edition ROM using fastboot commands, but I got an error message. The instructions say to just try the flash again, but the phone no longer connects properly via USB (error 10) while in bootloader mode. While in bootloader mode, the phone indicates there is some sort of problem (a line showing the OS version is highlighted in red), and attempting to enter recovery mode does nothing but display a phone with a big red X in it. The phone seems to operate fine and responds to ADB commands when the phone is fully booted, albeit with the old OS (not Google Play Edition) still in place.
Any Android device could theoretically get in this state. We're sort of "paralyzed", because everything we want to do to regain control of the bootloader and fix the situation seems to require issuing fastboot commands from a computer connected to the phone while it's in bootloader mode. Yet entering recovery mode or getting a computer to connect to it via USB no longer seems possible.
I wonder if there's another way to issue fastboot commands without relying on the USB connection to a computer?
Okay so i have a nexus 7 right? yes, but im fairly custom to rooting and all that stuff. Well im not a nub at this stuff but i need help once in a while XD, i just got the thing to turn on again i let it die completely and the charging bug decided that it wouldn't charge. I ended up jump starting the battery and now it turns on but now i plug it in it turns on right? yes it does but now i can get access to any data thats on it. (P.S there isnt any data on it since i had to wipe cyanogenmod 6.0.1 off it) and theres only twrp recovery on the tablet, i can access twrp and the boot loader (unlocked obviously) but i cant access fast boot or push files via adb. The charging port is still good on it i know that we had it tested on a friends tablet and it worked fine. OTG usb doesn't work either i cant seem to get data on the tablet but it turns on when i plug it in, it doesnt charge when plugged into a wall adapter or a pc it just turns on when plugged into a pc. Any and all info is appreciated. (sorry for my spelling errors if there is any, also i am on linux so i dont need drivers as far as i know, i also tried on windows and its a no go the device doesnt show up on either os)
nexus 7 2012 btw
-Loch
Eh just dont bother guys im pretty sure its dead, the nexus help forums didnt have anything.
download google usb driver, follow the instuctions to get fastboot working
then grab factory image and flash it
nguyenlucky said:
download google usb driver, follow the instuctions to get fastboot working
then grab factory image and flash it
Click to expand...
Click to collapse
Thanks for the help but sadly ive tried that...
As the device can go into fastboot and twrp with adb and otg without data transfer being possible I'd say most likely the port is broken.
Just to be sure no adb or fastboot commands work at all right? even those which don't transfer files. If they work then your partition layout is messed up which could be fixed
Gesendet von iPad mit Tapatalk
Did you try to charge the N7 via wall adpater or the pc? Did you use the genuine charger that comes with the device? What does it look like when you plug it into your pc? Did it show up as a mtp device (or any kind of device) ?
Try charging the N7 with genuine charger, or via pc. Make sure you install the driver for the N7 (go google it) before plugging in. Judging by your status, it appears that you're having a defective charging port or mainboard. Usually you'll end up sending it to the manufacturer to get them replaced (hope that it won't happen :3 ).
Have you used the push files and adb function on TWRP? To the best of my knowledge, these errors don't come about often in TWRP. If you don't know to use it, look it up on Google or the Xda threads. One more thing, losing fastboot is pretty rare with N7, so if you're not sure whether the fastboot is VANISHED, go to this link: http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
You can contact me for more insight if all that doesn't satisfy you: [email protected]
Glad that I could help.
John