Related
All,
I have a big problem. When I try to start my phone I get the black screen with google and the unlocked padloack, after which the screen goes dark and nothing happens anymore.
What I did before this are two things. I had been mukking around with the screen resolution (I had it set at 240 and 280, as some apps did not show up in the market) also downloaded LCD density to solve the market issue.
I then rebooted the device and entered CWM to do a backup which as far as I knew succeeded. unfortunately after rebooting, see the above.
I have tried a couple of reboots, tried restoring the nandroid (the above was the only one I had). that didn't work, so tried to connect to the PC to load a new ICS rom (original 4.0.4 by google), unfortunately my device can not go into USB mode in CMW (it comes up with UMS lunfile missing....)
so I am woring in circles. can't start the device to download a rom, can't open USM to load a ROM to start the device again.....
any help would be appriciated
thanks
Patrick
hey
flash a new ROM via fastboot then, there are enough guides
-Syn
Edit: Alternatively, flash the stock Google ROM via GNex toolkit and go from scratch.
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
Click to expand...
Click to collapse
To flash stock images the files are on your PC, not the phone.
If you can get the phone to boot into fastboot (via vol up + vol dn + power) and get your PC to recognize it you're good to go.
thats the issue. pc cannot recognize the phone, so cannot get any files from the PC to the phone (ie. cannot get a rom file to the phone...)
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
Either directly from Samsung or download the GNex Toolkit (You might want to use it anyways to flash the stock image), the drivers come with it.
After you installed the drivers and have you phone plugged in, go to the device manager to check if it is connected properly.
pwvandeursen said:
[snip]
thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
I had a similar issue with regard to my PC recognizing the drivers. I googled around and found that people were having success with installing the PdaNet drivers, so maybe you can try that too. I had installed the Android SDK as well as the PdaNet drivers, and I eventually got mine to work.
I would probably follow Efrant's links first though - if that doesn't work for you, then maybe you can try PdaNet drivers and/or installing the SDK.
Good luck.
Why not just do a factory reset from within recovery?
¢ £®0π π€XU$ |||
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
pwvandeursen said:
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
Click to expand...
Click to collapse
Good to hear you got it.
Hi Everyone,
I seem to have bricked a nexus 2013 wifi. At first, it was having movie playback issues so I restored it to lollipop using factory image on the google site. I decided to get OTA up to the latest MM. So far so good. But I though about putting a custom rom to it. So I installed TWRP 3.02 for flo and flashed PN MM with the recommended GAPPS. Kernel was what came with it. It worked fine until this morning when I realized that the touchscreen was not responding. I went to BL mode and into recovery. TWRP came up but touch was not responding as well.
So, I connected the device to my PC. It now shows unrecognized device. It still charges and all that but It is now stuck on the google logo. when I go to TWRP, touch wont work. I have tried another cable, still the same. My N6 is detected without issues using the same PC and cable. Since there are no drivers, I cannot reflash anything...
Any thoughts? Or am I just lucky to have bricked it? Appreciate any inputs that will be thrown in this direction. Cheers!
Hi, N7 motherboard gets touch, USB, accelerometer and compass data via the wide silver cable which often suffers from poor contact. Please try this first. If it is still not fixed, then in fastboot mode run and post the output of the following commands:
Code:
fastboot getvar all
fastboot oem gpt-info
fastboot format cache
Thanks for the help. hmm.. i pressed that part and it booted up to PN, touch is working as well. Not sure if that fixed it but if it happens again im gonna try to press that area. however, its still not detecting the device. I see it in Device manager, it says unknown device and will not take any driver, so fastboot is not an option for me atm.
so just an update. when I was able to boot up, it will not go landscape no matter what. I downloaded check my android and it the tests for compass and sensors were not responding. I decided to open the back cover, it was fairly easy. The thing is I have not the right tools to reseat the silver flex cable and I fear I might damage it, so I tried putting folded paper on to where it connects to on both ends. Now the thing works with landscape and so far, have not experienced touch issues or no boot issues.
I still do not have access to fastboot, though, as it still isnt detected by my computer. so I may have to stick to putting stuff to it over the air. Or should I just reseat that cable? Does it just slide out?
welxiii said:
I still do not have access to fastboot... should I just reseat that cable?
Click to expand...
Click to collapse
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
k23m said:
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
Click to expand...
Click to collapse
I'm also having issues with the sensors not working, I re-seated the cable multiple times already and that fixes it temporarily but it keeps coming back. I even tried to use loads of tape to make sure it never comes off but it still stopped working after about a week
noahvt said:
I'm also having issues with the sensors not working, I re-seated the cable multiple times already and that fixes it temporarily but it keeps coming back. I even tried to use loads of tape to make sure it never comes off but it still stopped working after about a week
Click to expand...
Click to collapse
The next step:
disconnect the ribbon cable from both the mobo AND daughterboard
spray the cable's and PCB connectors' contacts with Electronic Cleaner
reconnect and relock
k23m said:
Yes, re-seat the cable, but be careful, disconnect the internal black battery plug first and watch this video about ribbon cable connector handling.
As your main N7 problem is now resolved, we don't need the fastboot commands anymore. The USB detection issue may have something to do with the custom OS you flashed. Also note that N7 has several USB modes of operation with distinct IDs:
Code:
Qualcomm HS-USB Diagnostics 9006 - USB\VID_05C6&PID_9006
Qualcomm HS-USB Diagnostics 9008 - USB\VID_05C6&PID_9008
Android Bootloader Interface - USB\VID_18D1&PID_4EE0
Android ADB Interface - USB\VID_18D1&PID_D002
Android ADB Sideload - USB\VID_18D1&PID_D001
MTP or charging mode - USB\VID_18D1&PID_4EE1
PTP mode - USB\VID_18D1&PID_4EE5
MIDI input - USB\VID_18D1&PID_4EE8
What's the VID/PID of the non-detected device?
Does ADB work if you start TWRP?
Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it?
Is an OTG flash drive recognized?
Maybe Windows has a driver problem - does it work from live Linux?
Click to expand...
Click to collapse
Hi,
I really appreciate the assistance. Well, here's what I found.
[*]What's the VID/PID of the non-detected device? USB\VID_0000&PID_0002\6&688A3B8&0&2
[*]Does ADB work if you start TWRP? I don't think it does. In TWRP, I still get a message on my computer that the device has failed. DM shows the device as unknown usb device (device descriptor request failed)
[*]Have you actually put your N7 in fastboot mode (when off press power+vol.dn)? Does PC detect it? no it doesnt. same error as above.
[*]Is an OTG flash drive recognized? yes it does.
[*]Maybe Windows has a driver problem - does it work from live Linux? I'm still working on this. btw the same setup works on my phones and they are detected just fine.
update:
Suddenly its now detected by my pc. I connected my usb otg. At first,. It wasnt detected so I tried the usb on my nex6 and it worked. I connected it back to the 7 and voila! No error and DM now shows it as an android device. Whew!
But I have one question, is it safe to leave the folded papers i placed on both ends of the silver connector?
welxiii said:
Suddenly its now detected by my pc...
...is it safe to leave the folded papers i placed on both ends of the silver connector?
Click to expand...
Click to collapse
Yes.
As I mentioned earlier, the silver cable also connects USB data, so if you experience USB detection problems again, then do full re-seating with clean-up.
Cheers :highfive:
Thanks again for the assistance. Hopefully, it doesn't come to that.
unbricked my google nexus 7 tablet
if anyone has bricked there nexus 7 wifi tablet.....you can now unbrick it with the skipsoft toolkit. my tablet was bricked for awhile (it was stuck on the google logo and when I tried to boot into the twrp recovery it showed the android bot with an exclamation point so I was screwed big time) so I just brought another one (different version). after awhile I gave up hope, but today I decided to unbrick it (or atleast try to). at first I was using the nexus toolkit like I did before and I was having problems with it being recognized via adb and it wouldn't flash the stock recovery.img. than I remembered that I also had the skipsoft toolkit installed on my computer and the nexus 7 tablet was also supported on that toolkit so I decided to give it a try. at first, since I had it plugged in, it wouldn't recognize that it was plugged in not realizing that I had to download all the images and recoveries it needed to be able to root it and return it to stock if necessary so I did that and when I finished installing everything it detected that my device was in fastboot mode. I flashed the stock recovery image and it booted up like it was suppose to. I'm writing this just incase so one has bricked there device and has lost all hope in fixing there mistake. I love android and recently have a lg nexus 5x that's rooted with a custom rom on android 7.0 nougat. android is awesome
who ever developed the skipsoft toolkit....your awesome and thankyou for making this possible.
Hi, I got this bugger for way too big price (40 bucks for non-working piece of garbage), but I needed it because nobody helped me with reflashing original Nexus 7 I botched up while flashing (can't even get to fastboot mode).
I need to resurrect it from death. Apparently, somebody was tinkering inside, one antenne lead is broken, USB port seems replaced with very wrong one (it fits, it sits, but clearly it is not original) and the main, biggest problem is that the OS is corrupted.
All I keep getting is Google logo, can't boot into normal mode, can't boot into recovery mode. Can get to fastboot interface though. But there is one problem - the USB debugging was never activated, so when I plug it into computer in fastboot mode, all I get is "Unknown USB device (device descriptor request failed)". When I try to manually install Universal Naked Driver, it keeps *****ing about wrong driver version or not compatible hardware. What I have to do to get it working except sending it to Asus and pay 5 times the tablet's price to get it fixed?
It was going to be replacement for that botched Nexus 7, but now it seems that it will cost way more...
Have you not tried the Nexus Root Toolkit by Wugfresh? I reckon you should give it a try good luck.
Yeah, that came around my mind too, but there is one problem. USB debugging was never turned on and now when I plug in the tablet, it shows in device manager as Unknown USB device (device descriptor request failed). And because there is no working communication (it doesn't show up as tablet), I cannot ADB DEVICES it, returns me empty list.
krivulak said:
Can get to fastboot interface though. But there is one problem - the USB debugging was never activated, so when I plug it into computer in fastboot mode, all I get is "Unknown USB device (device descriptor request failed)"
Click to expand...
Click to collapse
USB debugging on/off is relevant only in ADB mode and has no impact whatsoever in fastboot mode. Please boot it in fastboot mode, connect to PC and quote USB device descriptor number from device manager.
If it is 18D1:4EE0 then you have to resolve driver issues on your PC
If it is 0000:000x then you have to fix hardware problem in your Nexus
I posted more info in this and this thread.
USB Device Tree Viewer shows it as vid_0000&pid_0002, so there is hardware problem with the tablet.
So, if I understand it correctly, it can be caused either by badly seated cable or bad USB port. Sice the one that is there is clearly changed for the wrong one, I will try to order proper one and see what will it do.
By the way, I already tried to reseat the ribbon cable, no luck there.
I flashed a rom yesterday that would not boot so I was going to flash a different rom and when I accessed recovery the files are not accessable -I see some file names but they all look different with numbers for file names - not the names they should have. I thought maybe my data was corrupt.
So - I attempted to flash a stock image (February) and when I attempt to flash via Platform Tools the it says "Waiting for Device" and doesn't seem to want to fully connect. I have the most up to date platform tools - I have changed USB Cords and tried different ones - and nothing I do works. To make sure I downloaded the most recent power tools (even though I successfullyy updated February Image when it first came out) and WIndows Powershell says "Waiting for Device" and I can't get it to recognize my phone.
I have flashed stock images before and never had an issue - but right now, I don't know what else to do. Any suggestions?
I went thru all the possible steps again and unfortunately, my PC does not recognize the phone and despite being able to get into Bootloader mode, I can no longer access recovery and PC does not connect via ADB.
I contacted GOOGLE and have started the warrenty replacement process.
Damn.....
Geekser said:
I went thru all the possible steps again and unfortunately, my PC does not recognize the phone and despite being able to get into Bootloader mode, I can no longer access recovery and PC does not connect via ADB.
I contacted GOOGLE and have started the warrenty replacement process.
Damn.....
Click to expand...
Click to collapse
Sounds like it could be a driver issue. Does anything show up in device manager when your device is connected to the pc?
Geekser said:
I went thru all the possible steps again and unfortunately, my PC does not recognize the phone and despite being able to get into Bootloader mode, I can no longer access recovery and PC does not connect via ADB.
I contacted GOOGLE and have started the warrenty replacement process.
Damn.....
Click to expand...
Click to collapse
You have some drive issue, find another pc and install the latest version of Platform Tools
TheMorpheus said:
You have some drive issue, find another pc and install the latest version of Platform Tools
Click to expand...
Click to collapse
I tried that - downloaded drivers - installed latest version of Platform tools on my desktop pc and it still doesnt work. Also - when I plug phone into charger, there is no indication that phone is charging at all. I tried Four different USB cords and battery would not charge for any of them.
I called Google and they are sending a replacement - (warranty replacement)
Geekser said:
I tried that - downloaded drivers - installed latest version of Platform tools on my desktop pc and it still doesnt work. Also - when I plug phone into charger, there is no indication that phone is charging at all. I tried Four different USB cords and battery would not charge for any of them.
I called Google and they are sending a replacement - (warranty replacement)
Click to expand...
Click to collapse
If that's the case it probably is a bad USB connector on the phone. Glad your getting a warranty replacement without a lot of hassle.
Strange issue. After applying the Feb 2019 security patch over air, my phone is no longer recognizing when it is plugged into a PC. I plug into my PC and I get a charge symbol on my battery but no pull down option to switch from charging to USB mode. Things I've tried:
1. New Cable although the wife has a Pixel 3 (standard) that works with this cable and computer just fine.
2. Different PC
3. Toggling USB debugging
4. Changing the USB setting in developer mode to transfer
5. When I plug a USB stick into the phone using the USB-C to USB-A adapter, the phone recognizes the stick and I can browse files
6. "Cleaning" the USB-C port
7. Also booted into safe mode (which I would assume should be like a factory reset) but no USB.
8. Switched between USB 3 and USB 2 ports on the PC.
It seems to me that there's a software issue with the Feb update that messed with the usb settings. I called google and they just want me to factory reset my device before they will transfer me to tech support. I'm avoiding that because I don't want to go back through the time/trouble of resetting up my phone. Any tips/tricks I've missed here?
If you have a Google variant with the BL unlocked, flash the factory image with the -w removed from the flash-all batch file. That way, you won't lose data. If you are on the Verizon variant or don't want to unlock you BL, sideload the OTA from stock recovery. See if it cleans up your issue. Also, sounds like you might have a driver issue on your PC. Easier to fix that first if it is the issue.
I have the February update over the air and I had no issues connecting to my Chromebook (crouton) via USB to pull an APK with ADB. I did have to turn USB debugging back on (not sure if I turned it off or if it was turned off from an update) and change the connection type, it was set to charging only.
More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.
copekyle said:
More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.
Click to expand...
Click to collapse
Try putting the phone into Fastboot mode and use the command "fastboot devices" to see if it is recognized. If it is, then the problem is on the ADB side, which is part of the Android system.
If it can connect via Fastboot, it's less likely to be a driver issue. You can try "adb devices" too with the phone booted to see if it is recognizing it all. May need to toggle through the various connection modes, I believe I used PTP the last time, but not certain.
As for sideloading, you will need the phone to be recognized by either ADB or Fastboot. You can sideload an OTA update from Recovery with a locked bootloader or as @sliding_billy said you can unlock the bootloader and flash the factory image which is done via Fastboot.
I would also verify that you have the latest version of the Android SDK installed just to cover that base.
copekyle said:
More info this morning. I have an Android based car stereo that when I plugged my phone into this morning, I did get the USB drop down. So it seems to be a windows 10 problem. I have both a Surface pro 4 and a desktop running windows 10 that are fully up to date that show the same symptoms. I don't know how I'm going to sideload an update if I can't connect it to my computer.
1. What I don't understand is why the Pixel 3 would work and the Pixel 3 XL would not. Same driver set, no?
2. Also, PC with Windows 7 also has same issue.
Click to expand...
Click to collapse
You don't need to be in file transfer mode to connect via fastboot. Check connection from there after using the combo keys to get into fastboot (power/vol down) for the factory image or one step further into recovery for sideload.
Neither Fastboot devices or ADB devices lists a device. When put in fastboot and recovery, my device manager on either computer does not register that there is a device connected.
copekyle said:
Neither Fastboot devices or ADB devices lists a device. When put in fastboot and recovery, my device manager on either computer does not register that there is a device connected.
Click to expand...
Click to collapse
Sounds like you have attempted everything... New cable (but rereading I don't see where you tried using a C>A cable instead of a C>C and that definitely needs tried). New computer/port/OS. Direct connect to fastboot. I think you are going to need to backup to the cloud (at least you have a functional device with internet) and factory reset the device.
P.S. I just thought about this, but do you have the current platform tools (ADB/Fastboot)? https://developer.android.com/studio/releases/platform-tools.html
sliding_billy said:
Sounds like you have attempted everything... New cable (but rereading I don't see where you tried using a C>A cable instead of a C>C and that definitely needs tried). New computer/port/OS. Direct connect to fastboot. I think you are going to need to backup to the cloud (at least you have a functional device with internet) and factory reset the device.
P.S. I just thought about this, but do you have the current platform tools (ADB/Fastboot)? https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Sadly I don't have a computer with a USB C port. I have been using only cables with C>A. I downloaded the latest platform tools yesterday before trying fastboot/adb. I'm waiting for a call back from Google tier 2 tech support within 72 hours. If anything comes of it, I will report back here.
copekyle said:
Sadly I don't have a computer with a USB C port. I have been using only cables with C>A. I downloaded the latest platform tools yesterday before trying fastboot/adb. I'm waiting for a call back from Google tier 2 tech support within 72 hours. If anything comes of it, I will report back here.
Click to expand...
Click to collapse
Good luck!