Hi all,
My MotoG had a bath in water, and as a result of it, its touchscreen is not functioning.
I am getting incoming calls (though, i couldn't attend them :crying: ), notifications sounds, popups in display and almost everything except touchscreen functionality. As a result i am not able to access my phone.
I have approached Moto Care, and the budget they have quoted is almost same as the price of he new phone. So i though why don't I use this phone by controlling it using PC using the methods mentioned in various post in this forum. But i am facing some problems here.
1) My phone is locked with a PIN. Moto G not letting to detect PC unless device is unlocked by entering PIN.
2) I have unlocked the boot-loader, rooted my phone. But, when i am trying to run ADB shell my phone is not getting detected. I am pretty sure USB debugging is enabled.
3) I have tried to get into recovery, and run ADB; but again phone is not detected. ( Fastboot commands are working though )
4) I haven't done the factory reset. Since my phone is running stock android i doubt it will make USB debugging option disabled after reset(that's what i understood, correct me if i am wrong).
5) If USB debugging is not activated at worst case, i am confused about selecting and flashing custom ROMs available for motoG in which developer Mode and USB debugging are enabled by default.
So can you guys help me to make my MotoG get in to action. also guide me through selecting and flashing a custom ROM having Developer Mode and USB debugging enabled by default via PC.
:good::good:
Get a USB otg cable, and attach a pc usb mouse (or wireless mouse dongle) . It should work (I've tried it before and it works)
any luck?
Related
I'm wondering if anyone has run into this problem before?
I'm trying to unlock the bootloader on my friend's Photon Q, I downloaded the SDK and installed the Motorola drivers. But when I put his phone into Fastboot mode, the "fastboot oem get_unlock_data" command does not work and CMD just says waiting for devices.
Yes I'm shift+right clicking on the platform-tools folder in the SDK to run the Command Prompt and I did download the correct Fastboot file. The command "adb devices" shows nothing when his phone is plugged in, but it shows my own phone (A Motorola Droid Bionic) when it's plugged into the USB cable. RSD Lite also recognizes both phones when powered on or in Fastboot mode.
I have no idea what to do at this point, we just need to get that unlock data to plug into the Moto site. Would it be possible to use someone else's unlock key or is each one randomized individually for the device? Or would that even work because my computer can't do the command for the unlock data, so maybe it couldn't push the unlock key onto the phone?
quick thought: did you enable usb debugging on the device?
edit: i guess that wouldn't make any difference in fastboot mode...
anyway, yeah, i'm pretty sure each device has it's own unique code. it's odd that fastboot recognizes the device, but the command isn't working. i bet you will get it somehow tho. a similar thing actually does happen to me sometimes, and in my case, it is because my usb ports are going bad and the computer loses connection with the phone.
Man nobody has anything eh? That's a crying shame. I tried using a different computer and went through the same course and still nothing.
I did try USB debugging on and off on both machines, didn't change a thing.
In order for the drivers (and therefore adb) to pick up the phone, I needed usb debugging *and* the phone not to be in charge only mode. Maybe that will help?
If not, when you reboot to fastboot and connect the cable, look at the devices installing list (if win 7) or device manager, and confirm the pc sees the fastboot device. If not you may need to reinstall the driver. Strange I know, but I needed to after getting my unlock data, holding off on unlocking due to the warranty voiding note, then trying again a couple days later where it wouldn't recognize. Seems to be finicky drivers to match a finicky device. But I do love this keyboard lol...
Sent from my XT897 using Tapatalk 2
We've only ever tried it in MTP mode and USB debugging enabled. This is day three of plugging it in and pulling it out and still no go. This is a royal pain, that is for sure.
Download Motorola Device Manager from the website, install, plug in phone. Place the phone into mass storage mode WITHOUT debugging enabled, then other modes, then back into bootloader mode then into fastboot mode. This will install EVERY driver, I didn't see that as one of the things tried.
Once you are in those modes, Android ADB device driver will install.
Hope that helps...
Sent from my XT897 using xda premium
Hi Guys,
I've had a few problems with my N5 recently...
If I plug my N5 into my PC via the stock USB cable and boot into the Bootloader (PWR+VOLDN) then it will allow me to flash the original N5 firmware, located here: https://developers.google.com/android/nexus/images, this would indicate to me that there is no issue with the actual devices ability to transfer files via USB connection... Right?
No!
For some strange reason my phone will allow me to push a full factory image to it and will also process any Fastboot commands that are sent to it but as soon as you boot into something like TWRP and try to control the phone's ADB functionality it will not find the device at all! The new MTP option in TWRP 2.8 will allow my computer to see my phone's MTP connection for about 1 second and then will immediately disconnect, the same happens when trying to connect to MTP from within Android too.
USB debugging doesn't show that it is connected when my phone is plugged into my PC and Windows makes the 'device connected' sound and then straight after makes the 'device disconnected' sound...
Any ideas? I am certain that this is an issue with my handset's hardware or software rather than any of the computers or cables... I have tried 3 different cables (including the stock cable) and also three different computers (Windows 8.1 @ Work, Mac OS X @ Work and my own personal PC running Windows 8.1 & Ubuntu @ Home)... All OSs and all computers run into exactly the same issue, device connects briefly and then disconnects.
I have troubleshooted issues relating to the driver. This is not the issue... Device Manager cannot even see the hardware after the disconnect.
Thanks for any help in advance,
Lewis
Also:
-Android does not detect that the USB is charging the device unless the device is booted with the cable attached (if it's not attached before the 'Google' screen then it can't see the USB input at all, within android or TWRP, of course...).
Having the exact same problem. Did you find a solution?
EvilBetty said:
Having the exact same problem. Did you find a solution?
Click to expand...
Click to collapse
It's most likely a driver issue.
Elluel said:
It's most likely a driver issue.
Click to expand...
Click to collapse
Not a driver issue.
3 different Nexus 5s, 5 different workstations. Other two Nexi are fine on all 5 PC's.
1 PC used for ADB forensics, 2 used for ADB development work, one known working for ROM'ing / rooting.
Phone has been factory reset, factory ROM'd from Fastboot. Connects fine on Fastboot. Will not connect on ADB / MTP.
On a fresh PC / phone reboot, the PC will detect the phone for just a second and then it will not reconnect until process is completed.
-EB
What's your adb version?
Went on for about 2 weeks, then suddenly went away on its own. I have no idea what the problem was or the solution. Sorry.
i have a nexus 5 which has stock ROM and blu spark kernel . i locked the bootloader while on the same kernel and again unlocked it . . the phone is bootlooping into twrp and the google logo . in twrp it says unable to mount data . i can access twrp . . i am unable to flash anything . it says unable to mount data/ . please the attachment
Hello,
my problem is that I´ve got a Nexus 4 Smartfon and the sceen is broken, so I´m not able to enter my pattern. because of this I also am not able to save my data because without entering the pattern, my computer doesn´t alowe the access to the memory.
I tried two different ways to get access to memory by using ADB:
1) I tried to delet the pattern (gesture.key) file.
I tride this first with my rooted Samsung Galaxy S3 mini and it worked perfectly. it also has USB debugging turnt on.
But my Nexus 4 hasn´t USB debugging turn on. I tried in on my S3 mini with and without and without USB debbuging it also didn´t work out.
Also my Nexus 4 isn´t even recognized as an ADB device, only in sideload mode or fastboot mode. I also think this is because of the not turnt on USB debbuging.
2)i tried to turn on the USB debbuging, so my device will be detected as an ADB device, or i can you a programm to mirror my smartphone on my computer and insert the pattern via computer.
I´ve found a pretty good tutorial on the internet but this didn´t work out. Also on my S3 mini it did´t work
So my last idea is, to us a little programm/application which i can transfer via sideload to my device and which will delete the pattern on the phone. my problem is that I´m not a programmer so I can´t do this myself.
so i would like to ask what do you think about my idea, if you could help me or do you have any other suggestions what i can do to save my data.
i´m ver thankful for any help :good:
Kaktus! :angel:
Kaktus621311 said:
Hello,
my problem is that I´ve got a Nexus 4 Smartfon and the sceen is broken, so I´m not able to enter my pattern. because of this I also am not able to save my data because without entering the pattern, my computer doesn´t alowe the access to the memory.
I tried two different ways to get access to memory by using ADB:
1) I tried to delet the pattern (gesture.key) file.
I tride this first with my rooted Samsung Galaxy S3 mini and it worked perfectly. it also has USB debugging turnt on.
But my Nexus 4 hasn´t USB debugging turn on. I tried in on my S3 mini with and without and without USB debbuging it also didn´t work out.
Also my Nexus 4 isn´t even recognized as an ADB device, only in sideload mode or fastboot mode. I also think this is because of the not turnt on USB debbuging.
2)i tried to turn on the USB debbuging, so my device will be detected as an ADB device, or i can you a programm to mirror my smartphone on my computer and insert the pattern via computer.
I´ve found a pretty good tutorial on the internet but this didn´t work out. Also on my S3 mini it did´t work
So my last idea is, to us a little programm/application which i can transfer via sideload to my device and which will delete the pattern on the phone. my problem is that I´m not a programmer so I can´t do this myself.
so i would like to ask what do you think about my idea, if you could help me or do you have any other suggestions what i can do to save my data.
i´m ver thankful for any help :good:
Kaktus! :angel:
Click to expand...
Click to collapse
Hello,
Try one of the methods stated here https://forum.xda-developers.com/showthread.php?t=2620456
Regards
Vatsal,
Forum Moderator.
Model Name: ROG 3 trncent edition( ZS661KS)
Firmware Version:WW-17.0823.2012.131
Rooted or not: yes ( was trying to root)
Frequency of Occurrence: Got<HARDBRICKED>
APP Name & APP Version (If your issue relates to the app): no app used.(magisk or anything else)
In addition to information above, please also provide as much details as you can, e.g., using scenario, what troubleshooting you've already done, screenshot, etc.
========================================
My rog phone 3 (tencent), which i brought about 6 months ago. I never had any issues like this.
The other day i opened my camera and suddenly the front camera was not working. I restarted the phone, did factory reset, cleared camera data, but nothing solved the issue. I thought i have to upgrade the firmware. So i downloaded the new firmware (2012.143) and connected the usb c cable with my laptop ( lenovo ideapad 320) , but it did not recognize. i tried both ports. I never had this problem before. I unlocked the bootloader, i thought it might help. I also turned on the developer option and selected FTP protocol and USB debugging. But it still didn't connect. while i was trying to enter bootloader recovery mode I accidently put the phone on EDL mode and now its bricked . The indicator light is flashing when i connect to the pc but the PC isn't recognizing the port ( i downloaded the qualcomm EDL driver on my laptop also, but the port option is not showing at all). Is it hardware problem, But the phone was charging just fine.
please help, gaming is my life
Hey guys,
I am Currently attempting to unlock the bootloader on my Pixel 6a, but when I attempt to connect via fastboot in the bootloader my PC shows nothing connected? I can push commands through ADB while the device is booted and have full functionality, but as soon as I reboot the device into the bootloader I lose connection to my PC. OEM Unlocking is enabled in the settings and I have toyed with updating it to the latest update and factory resetting the device. It shows correctly in device manager as 'Pixel 6a' while USB Debugging is disabled and as 'android composite ADB interface' while it is enabled.
To clarify as I am sure many have seen this issue before I do not believe it do be a driver issue as the device will not show up at all in device manager, not even showing with the incorrect driver (No ding to indicate a device has been connected). I have tried using 2 different USB C -> A cables in all slots of two entirely seperate PC's (Both running Windows 10). When I enter fastboot with OEM Unlocking disabled it acts no different to when it is enabled.
I appreciate any help or insight any of you folks can give me.
Device is currently running Android 13 Build number TQ2A.230505.002 if you need anymore info please let me know.
The OEM Unlocking toggle does not affect whether USB function works. It is only a "safety" that allows unlocking the bootloader.
Have you ensured you've installed the correct drivers? Google USB Drivers
I have spent a long time looking at drivers, but I have no device to install the drivers to as the connection drops out once I eneter the bootloader. I have used Zadig in the past to install the correct drivers for devices but when I reconnect the device while I have it open it cannot even detect a new device being connected to the PC. (Also no audible tone which would be heard even with incorrect drivers) I actually only recently used Zadig to install the correct WinUSB drivers for my S10e in which I connected it to my PC in download mode (Queue audible ding) and used Zadig to overwrite the incorrect driver with the correct one. It's almost as if the device will not communicate while it is in Bootloader mode?
I assume you have checked with the 'fastboot devices' command to see if your device is connected when in fastboot mode?