My issue is that there doesn't seem to be any data over USB. So I can charge my phone, but i cannot access it via adb or fastboot.
I tried to factory reset the phone, various cables and computers, but no luck. I do have adb over WiFi.
So my question would be, is this a faulty pin on the USB connection (the USB port is broken) or is this some sort of kinky software thing?
I'm using the TWRP 3.0.0-1 recovery, and running a stock Google ROM build MHC19I.
I tried every way i could think off to get my pictures of the phone. I even bought a mhl adapter with a usb port so you can use a mouse and/or keyboard.... But it doesn't seem to work.
Is it possible that the firmware on the phone is to old to support a otg mouse?
Also if I flash a newer frimware over with odin will that delete the screen password or overwrite my data partition?
Do you guys have any other ideas how to get my data of the phone?
Yes, it will wipe everything.
Without USB debugging activated, the only way would be to actually get the screen replaced.
Hi all,
I'm in an interesting situation. I have a Moto G4 (athene) with a non-functional microUSB port - that is, it won't charge, connect to my PC over ADB or even MTP. The port is soldered on to the motherboard and not replaceable.
I've figured out a solution for charging, but since I'm getting into app development I need to be able to connect via ADB. I looked it up and there seems to be a way to enable ADB over WiFi without an initial USB connection - however, this solution appears to require root, and I'm currently not rooted. Normally, the way I would root is by flashing SuperSU, but since I don't have an unlocked bootloader/TWRP on this device, this isn't an option. I tried all the "one click" roots (towelroot, kingroot, kingoroot) but none of them worked.
Is there a way I can root my device, or unlock the bootloader and flash TWRP, without a USB connection at all?
I don't think there is a way to unlock or root without using a USB cable at some point in the process unfortunately. A few of the tutorials I've seen require an USB connection to initiate the ADB over WiFi session or as you've mentioned, requires root.
I think the best bet for now would be to get the micro USB port repaired, under warranty if you can. Requesting the bootloader unlock code will void any remaining warranty so if your device is still under warranty, you may want to get it fixed. Some repair shops may be able to repair the micro USB port cheaper than a motherboard repair but check their reliability before committing.
Hey guys, my phone had a fall from a height and the screen shattered and the phone has bent. Customer care is saying there's no guarantee that phone will work even after changing the display, as the phone is bent.
I can hear notifications, vibrations and alarm is also working.
But not able to connect the my phone to PC as USB debugging if not enabled, mobile to tv through hdmi will not work because of usb 2.0.
Can someone let me know how can I connect my phone to pc so that I can backup the data
Any additional details would helpful:
Is your bootloader unlocked?
Are you running stock ROM?
Are you comfortable using command line utilities such as adb and fastboot?
Welcome to XDA
In the future use a good case and always redundantly backup your data.
The chances of damage to the mobo is high.
High G impacts can internally damage chipsets and break solder joints including hard to inspect/repair BGA chipsets. This was a high G loading impact. A good case spreads out the G loading making severe impacts survivable.
Don't invest a lot of money in trying repair this device. Even if repaired future problems may occur with the original mobo. Replacing the frame, display and especially mobo are cost prohibitive.
Sorry but you're probably better writing it off.
@SMcC2 :
Is your bootloader unlocked?
No
Are you running stock ROM?
No
Are you comfortable using command line utilities such as adb and fastboot?
Not exactly, I tried installing adb command line and tried to see the devices connected using it after connecting the phone with usb cable. But I guess since the usb debugging was disabled it didn't worked. No experience with fastboot yet.
Any help in retrieving the data will be appreciated.
Thanks @blackhawk, my priority is the data retrieval, tried some softwares for days recovery but they all require usb debugging to be enabled and drive approvals on the phone which will not work as my screen is shattered and display is not working.
Buy another one and swap your board in is the only option is see. Then again, I have taken my OnePlus 6t apart many times. It's not the hardest phone to disassemble. But expect to pay about $100-200 and know the possiblity exists that your data is toast. Or find someone you are willing to trust to hook up your board, pull your data and wipe it. I should make that a service. Lol.
Edit: just for shiggles sake, how/where is it bent? A pic would definitely aide in determining the PITA level. I destroyed one OP6t I had in similar fashion, but had BL unlocked, USB debugging enabled, and custom TWRP recovery so the hardest part was paying the cost for a new one for my broken one.
gauravtomar said:
@SMcC2 :
Is your bootloader unlocked?
No
Are you running stock ROM?
No
Are you comfortable using command line utilities such as adb and fastboot?
Not exactly, I tried installing adb command line and tried to see the devices connected using it after connecting the phone with usb cable. But I guess since the usb debugging was disabled it didn't worked. No experience with fastboot yet.
Any help in retrieving the data will be appreciated.
Click to expand...
Click to collapse
Do you know what recovery you have installed?
gauravtomar said:
Thanks @blackhawk, my priority is the data retrieval, tried some softwares for days recovery but they all require usb debugging to be enabled and drive approvals on the phone which will not work as my screen is shattered and display is not working.
Click to expand...
Click to collapse
According to these articles:
Can We Enable USB Debugging using ADB Command?
Is there a way to enable USB debugging from fastboot?
It may be possible to enable ADB by modifying your build.prop and persistent_properties from recovery.
I tested and I was able to boot to recovery via physical buttons and then connect to TWRP command line and pull the files they say need to be edited.
*NOTE* Editing these files is dangerous and could cause the phone not to boot properly.
My process was:
Hold Vol+ Vol- and Power until you feel phone reboot to fastboot mode(short vibration here)
Vol -, Vol -, Power (reboot to Recovery)
Wait a minute or two...
Connect USB cable
adb shell
twrp decrypt *passcode*
*NOTE* If you're using a PIN number you can use the alphanumeric digits, if you're using a pattern you will need the details from the bottom of this link:
TWRP Commandline Guide
adb shell
mount /system_root
adb pull /system/build.prop
adb pull /data/property/persistent_properties
Open files in Notepad++, Make the edits, etc....
Back in 2014 my device stopped charging with USB. I just happened to find it the other day and put it on a wireless charger and lo and behold my Nexus is alive again. Back then I used to do a lot of flashing ROMs but I'm very rusty now. It has a custom rom called Vanir on it and is rooted and has twrp. If I just download a custom rom to the device will I be able to go into recovery and install it? My laptop just died on me and I can't use it to flash the ROM. I just want to try something different for fun.
Thanks!
Edit: the USB won't work even if my laptop hadn't died.
Download custom recovery to internal memory. Make sure it's not saved in to system directory, but internal sdcard directory. Boot in to recovery mode, wipe cache, then chose install and find your custom ROM. Press install. Make sure custom ROM is definitely made for your device and was confirmed to work without any issues. USB stops working for few reasons. First and easiest to fix is damaged USB socket. You can replace it by buying a new or second hand one. Second reason is short on OTG activation pin. If its's shorted to GND, USB charging will not work and no communication with computer possible. There is a lot of possibilities where this short could have happened. On my 3G device this happened under main processor, and the only way I managed to revive it was injecting 1V to OTG activation pin, which somehow made short disappear.