Develop Bugs

[Q] Cables always come loose?

I have had my Nexus 7 2013 pretty much since launch date and I have always had a problem with the micro usb cables coming loose (I have tried various ones). This has never really been a major issue until recently I bought a OTG Y cable to connect it, and then to connect a Wireless adapater to it for using Kali Tools on my tablet.
The problem is, the slightest touch to the cable, and I mean you only have to look at the cable and it comes loose effectively disconnecting and interrupting the power from the OTG and wireless adapter.
Is this a known problem and is there a fix?
The cables just never seem to go far enough in and wobble side to side far too easily, so although it was never a major problem for me before I am finding it extremely annoying and frustrating right now!
Thanks

Take the back cover off, use a pair of needle-nose pliers to GENTLY squeeze the connector back together, replace back.

Problems with USB connection

I had been somewhat unlucky and while charging my beloved FLO something went puf (literally). After that I don't have any USB connectivity. Charging my N7 works (very slowly), but no USB OTG or USB ADB. OK Fine and dandy if I wouldn't be total idiot and wipe system while trying to install new ROM before transferring ROM image to internal storage.
Now I have FLO paper clip able to go to TWRP but can't install nothing. As far I understand there's no way to enable wifi in TWRP.
Any ideas what would needed to be replaced to make my FLO work again so I can put some ROM on it and make it work again.
I'm not sure if USB daughter board would suffice and solve my problem. Any suggestions?

jxl69 said:
I had been somewhat unlucky and while charging my beloved FLO something went puf (literally). After that I don't have any USB connectivity. Charging my N7 works (very slowly), but no USB OTG or USB ADB.
Click to expand...
Click to collapse
Either the USB port developed "dry joints" or the wide silver cable (LCM) needs to be re-seated on both connectors.
Disconnect the battery before fixing LCM cable. Here is advice on USB port repair.
Replacing the daughterboard PCB should be the last resort because it is unlikely that the touch function will work 100%. It would work if we had access to the touch calibration software - the problems are described here https://forum.xda-developers.com/ne...rivers-to-calibrate-touch-screen-usb-t3334898

k23m said:
Either the USB port developed "dry joints" or the wide silver cable (LCM) needs to be re-seated on both connectors.
Disconnect the battery before fixing LCM cable. Here is advice on USB port repair.
Replacing the daughterboard PCB should be the last resort because it is unlikely that the touch function will work 100%. It would work if we had access to the touch calibration software - the problems are described here https://forum.xda-developers.com/ne...rivers-to-calibrate-touch-screen-usb-t3334898
Click to expand...
Click to collapse
I doubt re-seating would help or cleaning USB port, since it was something electrical happening with that *puf*. If my memory serves me right there was a smell of burnt electronics. I doubt that some shortage disconnected any cables.

jxl69 said:
I doubt re-seating would help or cleaning USB port, since it was something electrical happening with that *puf*. If my memory serves me right there was a smell of burnt electronics. I doubt that some shortage disconnected any cables.
Click to expand...
Click to collapse
Sounds like you need a new charging port and board. Easy to fit but difficult to get hold of one. Maybe purchase a broken Flo on eBay and extract the charging port board

dave457 said:
Sounds like you need a new charging port and board. Easy to fit but difficult to get hold of one. Maybe purchase a broken Flo on eBay and extract the charging port board
Click to expand...
Click to collapse
Even tho charging works? The only problem is data part of USB connection. USB OTG will not work neither will it connect to a PC for file transfer/adb. But if connected to PC or plug device charges. I believe it will not charge past 80 or 90%.

jxl69 said:
Even tho charging works? .
Click to expand...
Click to collapse
Yes

onoz ! i have twrp and boootloader, but no system files... HELP !

due to my own stupidity, i had unlocked and installed twrp with a lot of effort, as the usb is decidedly iffy
i managed to use a file manager to import the requisite lineage rom and gapps, and then in my infinite wisdom stored them somewhere volatile - one mistake i won't make again
and so when i cleaned the device prior to a "new" install, i inadvertently lost the zip files, and now the computer refuses to recognise the device
no amount of forcing the right usb driver onit works, because i presume the computer does not know it's a flo
so, is there any way i can get it connected and push the roms to storage ?
my skills at the command line are limited, but i can follow scripts
this is sad, as i was soooooooo close to completing the install, after which the usb would have become redundant (i have a wireless charger and can wifi file across with a working system)
is this thus my very first brick ?
or can i trick the usb connection into working with the computer, or somehow wirelessly transfer to such a basic installation, or rig an otg connection (i have no cables that would seem to join micro-usb to any female plug to use a memory stick or sd card in adaptor)
thanks for any suggestions :fingers-crossed:

Get an image file from Google https://developers.google.com/android/images
Try going into TWRP and go into sideloading (can't remember exact menu - only used it once to get out of a similar problem), then try to connect USB lead to PC.
Run flash-all.bat on PC and that should at least get a system on the device.
Maybe...

thanks for the suggestion, but the sideload could place the lineage.zip instead if the computer would accept a usb connection - that's the problem: sideload can't work because the usb device is not recognised
my best bet would appear to be load the zip via otg - the twrp interface appears to allow that
i'll report back here if that works (once i procure a usb otg connector)

I was in a similar position once and couldn't get a normal USB ADB connection with PC until I tried TWRP sideloading which kicked in the PC connection.
Did you try it?
OTG was the next thing I was going to suggest

scruffy1 said:
the usb is decidedly iffy
no amount of forcing the right usb driver onit works, because i presume the computer does not know it's a flo
Click to expand...
Click to collapse
As the USB port is broken there is no hope that an OTG adapter would work because it can not function without the data connections, exactly like PC-USB. Have a look at the port's soldering, it may need some re-work. If the port's connectors are damaged then a replacement is very cheap.
:good:

k23m said:
As the USB port is broken there is no hope that an OTG adapter would work because it can not function without the data connections, exactly like PC-USB. Have a look at the port's soldering, it may need some re-work. If the port's connectors are damaged then a replacement is very cheap.
:good:
Click to expand...
Click to collapse
thanks for the suggestion
i sprung the back and was going to attempt to reflow the solder in case it had a dodgy connection - but i noted that the actual usb connector looked like it had been stretched, and took to it with my favourite pliers and performed some creative metalwork by squeezing it
lo and behold! the otg connection worked, at least for long enough to transfer the custom rom
thereafter when i reassembled the case, the otg connection failed but now the usb link seems to be happy enough even though that makes no great sense seeing it is the same connector port, and the otg works on my other android devices
still, gotta take what you can get, and i am now the proud owner of a nexus 7 "flo" with lineage doing nicely
thanks for all assistances

scruffy1 said:
thanks for the suggestion
i sprung the back and was going to attempt to reflow the solder in case it had a dodgy connection - but i noted that the actual usb connector looked like it had been stretched, and took to it with my favourite pliers and performed some creative metalwork by squeezing it....
Click to expand...
Click to collapse
Ahh this explains why my N7 - used daily - has never developed any USB port problems! I thought that this USB port's construction was rather 'weak' so preemptively I applied a simple reinforcement, have a look at the attachments.
It was 4 years ago....
:highfive:

Can't get file transfer/ADB/fastboot over USB

I just bought a used Pixel 2 XL and it has the file transfer/ADB/fastboot over USB problem. I've been through every solution here and on Google Pixel support with no luck (see below).
The phone connects via USB for a second and brings up ADB debugging auth, then disconnects. Every other thing I plug into the phone works fine (thumb drive, OTG camera, charger). Wireless ADB works fine, but I can't unlock the bootloader this way (that I know of). I can't get ADB or Fastboot access in bootloader or recovery mode.
I'm guessing software/kernel problem on the phone since everything else works with the USB port. I'm currently running build RP1A.201005.004.
On the factory image page, there's a new image, RP1A.201005.004.A1, Dec 2020, that I hope is a fix, but I've got no way to install it except if I get it OTA.
If anyone has any ideas on other things to try, please LMK! Thanks!
Solutions I've tried:
Cleaned port, dozens of cables, USB 1, 2, & 3 ports on four different machines and three different OS that work with ADB on other phones, every phone ADB/USB setting on/off in all combinations, cleared data for external storage, can't clear data for media storage because it's now grayed out in this build.
I've also tried the old tricks to try and get the OTA sent, but I'm guessing those tricks don't work with Android 11.
I may try replacing the internal USB port and cable since it's only $7, but I don't think it's the problem from what I've read in other posts here.

phineous said:
I just bought a used Pixel 2 XL and it has the file transfer/ADB/fastboot over USB problem. I've been through every solution here and on Google Pixel support with no luck (see below).
The phone connects via USB for a second and brings up ADB debugging auth, then disconnects. Every other thing I plug into the phone works fine (thumb drive, OTG camera, charger). Wireless ADB works fine, but I can't unlock the bootloader this way (that I know of). I can't get ADB or Fastboot access in bootloader or recovery mode.
I'm guessing software/kernel problem on the phone since everything else works with the USB port. I'm currently running build RP1A.201005.004.
On the factory image page, there's a new image, RP1A.201005.004.A1, Dec 2020, that I hope is a fix, but I've got no way to install it except if I get it OTA.
If anyone has any ideas on other things to try, please LMK! Thanks!
Solutions I've tried:
Cleaned port, dozens of cables, USB 1, 2, & 3 ports on four different machines and three different OS that work with ADB on other phones, every phone ADB/USB setting on/off in all combinations, cleared data for external storage, can't clear data for media storage because it's now grayed out in this build.
I've also tried the old tricks to try and get the OTA sent, but I'm guessing those tricks don't work with Android 11.
I may try replacing the internal USB port and cable since it's only $7, but I don't think it's the problem from what I've read in other posts here.
Click to expand...
Click to collapse
I just installed the update using ADB from my Chromebook via Crostini Linux. I had an issue at first due to the USB cable I was using. Switched to a USB 3 cable and it worked flawlessly. Kinda weird that after the update it still says October 2020. Looks like the .A1 on the end of the build is the only difference, other than whatever security updates they pushed.

robn30 said:
I just installed the update using ADB from my Chromebook via Crostini Linux. I had an issue at first due to the USB cable I was using. Switched to a USB 3 cable and it worked flawlessly. Kinda weird that after the update it still says October 2020. Looks like the .A1 on the end of the build is the only difference, other than whatever security updates they pushed.
Click to expand...
Click to collapse
I just got the update OTA today. I still can't get a USB connection to work for longer than a second or two. I've tried dozens of cables and several computers. I'm going a little crazy here.

phineous said:
I just got the update OTA today. I still can't get a USB connection to work for longer than a second or two. I've tried dozens of cables and several computers. I'm going a little crazy here.
Click to expand...
Click to collapse
I have noticed mine is a little finicky with ADB, especially when connected via USB 3.0. Connecting with USB 2.0 with a good cable seems to always be reliable and never disconnect. Also if you haven't tried using the stock cable that came with the Pixel, I would try that for sure.

I just replaced the internal USB assembly and nothing has changed. The old connector was definitely worn though.
I'll go back to trying more cables and ports. I ordered a cable that another poster claimed worked for them, but I had no luck with it.
For anyone wanting to replace their USB ass'y, here's what I learned from doing it. The service manual on ifixit is a good guide but leaves out a couple of important steps.
Heat is your friend. I used a clothes iron adjusted to 160F. The phone dissipates heat quickly so you may need to heat it several times. Place a towel over the screen and set the iron on it. I used guitar picks to pry up the screen and keep it separated while I heated the other sides.
The screen cable connection covers are hard to remove and you'll probably need a to use a metal spudger.
Heat the back of the phone to help remove the loudspeaker ass'y without damaging it, and again to remove the old cable ass'y.
The replacement ass'y I got had adhesive applied for the center of the cable, but not the adhesive foam pad under the antenna connector, so heat and scrape between the pad and phone body to remove it intact for reuse.
My old antenna connector partially came off in the white antenna connector and it was very hard to see what was wrong even under strong magnification.
You'll need a new screen adhesive sheet to reattach the screen securely.
Both parts came from a seller on ebay. Dougsgadgets was the only one that had both parts in stock. I think I paid $11 and they shipped quickly.
Good luck!

Won't Connect to Pc?!

I recently reset my device and did a wipe with Twrp so I could install Los with it, now currently the device has nothing on it but cannot connect to my pc for whatever reason, I tried installing drivers through Restock, and it even charges with the device powered off I have also tried other cables is there something I'm missing here? I don't know how to move forward and it used to work perfectly before the reset.

This seems to be a frequent problem with our almost eight year old N7s. There is a ribbon cable connector on the motherboard, the top board inside the tablet, which is prone to lose connectivity over time. There are inserts on the inside of the rear cover which apply pressure against two ribbon connectors on the motherboard. The ribbon cable connecting the lower, USB board to the motherboard carries charging current for the battery, USB data to and from the external USB connector, touch input from the screen and for the LTE N7, SIM card data.
Remove the rear cover, connect your N7 to your PC and see if connectivity is restored when you press on the left ribbon cable connector on the motherboard as viewed from the rear. If so, you can try adding some cardboard between this connector and the back cover to increase the pressure applied to the connector once the rear cover is reinstalled.
Good luck.