Related
Could someone help me on this issue. When i connect my phone via usb to my laptop and on other different laptops/computers i've tried so far, it only charges the phone without mounting sd card or allowing data transfer. I'm using an O2 branded stock htc desire running on froyo. i want to root my phone and install install a custom rom. i don't know how or if possible to make a goldcard without using a usb connection cable to a laptop/pc and for the other processes of rooting and installing a custom rom.
I took it for repairs and a new port was put in and still same problem persists.
You know that you have to manually select mount sd. Also have you tried to connect it via adb, not to transfer files but to see if i usb connection works?
Sent from my HTC Desire using XDA App
For the adb connection, I think this will require USB cable connection or it's there a way to do this without USB cable connection.
Sent from my HTC Desire using XDA App
scorror said:
Could someone help me on this issue. When i connect my phone via usb to my laptop and on other different laptops/computers i've tried so far, it only charges the phone without mounting sd card or allowing data transfer. I'm using an O2 branded stock htc desire running on froyo. i want to root my phone and install install a custom rom. i don't know how or if possible to make a goldcard without using a usb connection cable to a laptop/pc and for the other processes of rooting and installing a custom rom.
I took it for repairs and a new port was put in and still same problem persists.
Click to expand...
Click to collapse
Once you plug in your USB cable, you have to pull the top bar down and manually select to use it as a usb 'disk'...only then will you be able to load it with custom ROM.
As for rooting, I think you need to enable USB debugging for the UnRevoked method....
Evil_Cid said:
Once you plug in your USB cable, you have to pull the top bar down and manually select to use it as a usb 'disk'...only then will you be able to load it with custom ROM.
As for rooting, I think you need to enable USB debugging for the UnRevoked method....
Click to expand...
Click to collapse
when i select it to use as usb disk, the laptop doesn't see it, same for usb debugging.
i tried using a usb hub with four ports to connect my phone to the laptop, the message i get is that '' this usb device is not recognised''. Pls why that message
Any help on this issue. I've been reading on usb brick phones and how to unbrick it. The problem is even when phone is connected via usb in fastboot mode, it still say device is not recognised. i was trying to get the CID number of the phone. i've never rooted or flash a custom rom yet. i started experiencing this when the phone fell on a concrete floor. i don't know if this is hardware related problem or software related.
I know my way around fastboot, adb, command line pretty well, but I just got my N7(2013) last night, so in that sense, I'm a Noob.
Questions:
Can I just root with SuperSU without TWRP? Or will the stock recovery not let me do that? i.e. is there a signed SuperSU? I would rather keep my stock recovery, if possible.
After I root, do USB storage devices connected via an OTG cable "Just Work"? Do I have to manually mount them? Does it enable a Menu?
Is there any way to enable USB Storage (The other way, when N7 is connected to PC) once I root? Is anybody working on this?
Linuxslate said:
Can I just root with SuperSU without TWRP? Or will the stock recovery not let me do that? i.e. is there a signed SuperSU? I would rather keep my stock recovery, if possible.
Click to expand...
Click to collapse
Suggest you do
fastboot boot twrp.img
instead of flashing twrp onto the tablet's recovery partition
This will run twrp temporarily to install SuperSU's update.zip but will leave stock recovery on your tablet untouched.
Linuxslate said:
After I root, do USB storage devices connected via an OTG cable "Just Work"? Do I have to manually mount them? Does it enable a Menu?
Click to expand...
Click to collapse
Recognition is automatic. Mounting is not. So yes, you need to mount them. Whether you do that manually or through a helper app like stickmount is up to you
Linuxslate said:
Is there any way to enable USB Storage (The other way, when N7 is connected to PC) once I root? Is anybody working on this?
Click to expand...
Click to collapse
Doubtful. N7 doesn't have a real sdcard partition formated fat32. It has a simulated sdcard kept in the /data/media folder. MTP/PTP are the only ways Google wants to support storage going forward.
Thanks, sfhub;
Great trick about running twrp once.
That way I can have root, and my stock recovery.
Thanks for the other info, too.
No MTP or Storage show on PC
I am running windows 7 64 bit and I have managed to get root on my new Nexus 7, but now when I plug my tablet into the PC it says on the tablet connected as media device, but it never shows up anywhere on my pc so that I can transfer files on to it. The nexus 7 never shows up as an extra drive or as an media device. Please help. can not seem to find any info on this problem. the usb icon at the bottom of the screen does say eject nexus 7 when I click on it, and if I have usb debugging turned on it says ADB device connected but I still can not see it anywhere on the pc. Please help
Are you running stock or custom ROM?
If you running stock, you can try disabling USB debugging or try this:
http://forum.xda-developers.com/showthread.php?t=2391236
If you are on custom ROM, it appears there may be an MTP issue with some ROMs.
Yes I am using the stock rom .all I did was root it and I have tried with no success with usb debugging turn Off as well. I have even tried to uninstall the drivers I used to root the tablet , but can not find them to uninstall or delete them
In devmgmt.msc the device is either listed under
Android Phone
Imaging device
Portable device
Unknown
Do you see any ? or unknown devices?
In Devices and Printers in the control panel its listed under Unspecified as Nexus 7 but you can not do anything with it there but right click on it and hit eject or properties and it says Google Nexus ADB interface ___ Android Device ___ status working properly and that's it .In Device manager it listed as Android Device ___ Google Nexus ADB Interface.
I Got it Thank you Thank you. I was able to uninstall the drivers there in the Device manager, unpluged the Nexus 7 plugged it back in it install the correct drivers and I am now able to mount my device as a MTP device and transfer files. Thanks again for the Help.
I put Android File Transfer on my Macs:
http://www.android.com/filetransfer/
and gmtp on My Ubuntu Ultrabook, and on my old Xubuntu desktop.
I put the SD card in the Ultrabook, and copied everything I wanted to the N7(2013).
In all cases, it worked pretty much plug and play, but I still consider it a work-around.
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!
Hey gals and guys,
my girlfriend dropped her Xiaomi A2 lite and no the touchscreen doesn't respond. The phone has the stock Android One and I can only access fastboot.
Code:
fastboot devices
recognizes the phone.
The recovery is the stock recovery.
Code:
adb devices
won't recognize the phone and gives me an empty line as output
I also can't access the phone via usb with my filebrowser. If I try, the phone makes a "bing"-sound and the filebrowser gives me:
Code:
unable to open MTP device
I am using archlinux and I also have a windows device available.
Is there any chance on getting pictures etc from the phone?
Any suggestions besides getting a replacement for the touchscreen?
Thank you so much.
Connecting via USB probably needs you to click something.
I'm guessing developer mode is not enabled...
If you've got a micro USB OTG cable, you could plug a mouse in.
If you boot TWRP (fastboot boot twrp-3.3.1-dees-troy.img) you should be able to get adb and usb transfers working. Don't need to install it, just boot it. Not sure if that works without unlocked bootloader.
If you've got a micro USB OTG cable, you could plug a mouse in.
Click to expand...
Click to collapse
This did the trick.
Thank you
I unlocked the bootloader, I did a wipe data and now the firestick is stuck on the firetv black screen, cant access the menu, cant connect through adb with the computer connected via usb.
I can access TWRP with otg cable and mouse, but I dont have any rom to flash on device, so I cant reflash it, I dont have access to adb to push it either.
If I connect a usb hub to the otg, and connect the mouse and a usb stick at the same time, can I access the usb stick memory to flash the rom zip file?
Help
Update:
Problem solved I did the unlock bootloader process again as Pretoriano80 advised and it worked, I got access again to TWRP, used adb to push the rom and flashed the rom again.
Thank you.
rodainas said:
I unlocked the bootloader, I did a wipe data and now the firestick is stuck on the firetv black screen, cant access the menu, cant connect through adb with the computer connected via usb.
I can access TWRP with otg cable and mouse, but I dont have any rom to flash on device, so I cant reflash it, I dont have access to adb to push it either.
If I connect a usb hub to the otg, and connect the mouse and a usb stick at the same time, can I access the usb stick memory to flash the rom zip file?
Help
Click to expand...
Click to collapse
Yes, if you connect a mouse + usb stick (fat32) you will be able to flash a stock rom. In TWRP you will have to switch from internal memory to the OTG stick.
Thank you for the answer thats good news.
So any usb hub should work right, i will have to buy one.
Sent from my iPhone using Tapatalk
rodainas said:
Thank you for the answer thats good news.
So any usb hub should work right, i will have to buy one.
Click to expand...
Click to collapse
If TWRP works, then you can push a stock firmware from PC to the FireTV Stick with ADB. Just make sure that your stick is connected to your pc with the original USB cable (not OTG).
I already tried.
When connecting directly to pc, no otg cable, I cant use adb, looks like after I wiped data the device lost the adb.
I tried adb shell it says no devices/emulators
I tried adb devices, none listed
So I cant connect through adb, I cant access recovery nor I can push the flashable rom.
The only way I can access is with otg cable + mouse.
That leaves me with only one option, use the hub to connect mouse + stick to the otg cable and flash through otg usb in TWRP.
Sent from my iPhone using Tapatalk
rodainas said:
I already tried.
When connecting directly to pc, no otg cable, I cant use adb, looks like after I wiped data the device lost the adb.
I tried adb shell it says no devices/emulators
I tried adb devices, none listed
So I cant connect through adb, I cant access recovery nor I can push the flashable rom.
The only way I can access is with otg cable + mouse.
That leaves me with only one option, use the hub to connect mouse + stick to the otg cable and flash through otg usb in TWRP.
Click to expand...
Click to collapse
TWRP's ADB should work, but probably you can't boot into TWRP without OTG. The solution is to do the unlock procedure again so after the last step it should boot to TWRP automatically.
If that fails, then you can buy an USB hub.
Thank you for helping really appreciate that.
I will run the procedure again, will keep you posted about the results.
Ok tried it
No response from device
After ./bootrom-step.sh it says waiting for bootrom, I do the short connect the device but the computer doesnt recognize it, keeps saying waiting for bootrom no matter what I do.
So I think theusb hub is the only resource now.
Sent from my iPhone using Tapatalk
Ok Tried again, it works, am on TWRP with adb, pushing the flashable now, will keep updated.
Update:
Good news
Firetv fixed, thank you very much!
rodainas said:
Ok Tried again, it works, am on TWRP with adb, pushing the flashable now, will keep updated.
Update:
Good news
Firetv fixed, thank you very much!
Click to expand...
Click to collapse
Great! No problem, it happened to me once and has been the only that worked for me (without the need of an usb hub, of course), so i was pretty sure that it would work for you too.