Hi All,
I flashed my HD2 ROM last night, and after that everything was working except, I could not make a call or receive a call.
I tried pulgging into my PC with windows 7 ultimate, and it's saying USB device not recognised.
ROM i used is miri HD2 ROM-v19.0 WWE
Can someone please help me with this?
First you will have to remove all references to the failed usb connection:
as Administrator,go to My Computer <Right Click> Properties <Left Click>
select tab "Advanced"
Click Environment variables
Create following Environment variables in the system section:
Code:
DEVMGR_SHOW_DETAILS
and assign it a value of 1
Code:
DEVMGR_SHOW_NONPRESENT_DEVICES
and assign it a value of 1
Click OK twice
Next: go to My Computer <right-click> Manage <Left-click>
go to device manager.
select view > show hidden devices,
then:
Remove all devices with a questionmark
Remove all devices which are greyed out and which you can relate to your mobile
Once you have done this, reboot for certainty.
Try again, making sure to insert USB connector first in your Phone, afterwards in a fast, secure way in your PC. Do not "hesitate" while connecting USB connector. (sometimes slow/not complete insertion may cause this problem too)
Wilco said:
First you will have to remove all references to the failed usb connection:
as Administrator,go to My Computer <Right Click> Properties <Left Click>
select tab "Advanced"
Click Environment variables
Create following Environment variables in the system section:
Code:
DEVMGR_SHOW_DETAILS
and assign it a value of 1
Code:
DEVMGR_SHOW_NONPRESENT_DEVICES
and assign it a value of 1
Click OK twice
Next: go to My Computer <right-click> Manage <Left-click>
go to device manager.
select view > show hidden devices,
then:
Remove all devices with a questionmark
Remove all devices which are greyed out and which you can relate to your mobile
Once you have done this, reboot for certainty.
Try again, making sure to insert USB connector first in your Phone, afterwards in a fast, secure way in your PC. Do not "hesitate" while connecting USB connector. (sometimes slow/not complete insertion may cause this problem too)
Click to expand...
Click to collapse
I'm interested if this works... Still have a Touch Pro2 with the same message, so I will try the same for that device. Thanks for showing the hidden devices!
Related
Hi,
I've just spent a few hours trying to fix a problem with Kies and Windows 7. I had just used Odin3 and download mode to download a Chainfire kernel onto my GT-I9100, and afterword when I connected my phone Windows 7 would try installing drivers and fail on the MTP driver. I tried a lot of things to fix the problem, the only information I could get on it was an error message "Device Cannot Start (Code 10)".
I had spotted that when connecting my phone in download mode to Odin3 that Windows 7 had detected and installed a driver for "Unknown Device". On a hunch that this driver was causing the issue with connecting after using Odin3 I tried to completely uninstall it.
This is what I did (the first 8 or 9 steps are just to enable Device Manager to show *inactive* device drivers so you can uninstall the Unknown device. I've nicked this these steps from another site since I'm not allowed to link it yet):
1. Go to Control Panel and double click on System. You can also right-click "Computer" on the Start menu (or on the desktop if it's shown there) and choose Properties.
Note: A faster way for opening up the System applet is to press the Windows logo key on your keyboard and then press Pause/Break at the same time.
2. Click on "Advance System Settings" link, and then click on the "Environment Variables" button.
3. In the System Variables section click on the "New" button.
4. In the New System Variable dialog box, under the Variable Name value enter devmgr_show_nonpresent_devices (just copy the value from here and paste it there) and give it a variable value of 1.
Click Ok.
5. In the Environment Variables window notice how the new variable appeared in the System Variables section. Click Ok.
6. In the System Properties window click Ok.
7. Log off and log on.
8. Open Device Manager (Control Panel > System > Hardware > Device Manager).
9. From the View menu click Show Hidden Devices and searched for Unknown Device under Portable Device and USB Devices.
10. Right click the Unknown Device and select to uninstall, making sure to select complete removal of drivers option.
11. Restart the PC.
12. Start Kies without plugging the phone in.
13. Click on Troubleshooting for USB device and continue until it repairs the drivers.
14. Reboot the PC. Open Kies and plugin the phone again and let it reinstall the drivers.
Hope this sheds some light on this pernicious issue.
Hey guys.
I have Samsung galaxy ace 5839i (stock for 5830i) and I am using it for a few years, but this problem came for the first time.
Always, when I try to connect my mobile to pc using cable, it just won't connect, it won't even show me the notification of connecting.
Before this problem, I connected it to fedora linux and it was succesful, but now? It won't show me that USB sign even in windows.
Any help?
Thanks in advance
@LiQuDiAk, basically s5839i and s5830 i are identical in many areas ,, few questions though,, did you root your device or you are on android 2.3.6 stock version / kernel 2.6.35.7 ?
when you are in your windows device manager ( while you are connected , do you see any exclamation / question marks in front of the corresponding driver), you can always uninstall your old driver, reboot , then try compiled driver in attachment , and reboot to take proper effect in your registry (tested on win xp/7 -32bit) . Also check your device settings>Application>Development > USB Debugging and make sure the option is checked. now lets check your debugging mode through ADB command and see if your device is being recognized. download platform zip attachment, unzip it and put the folder someplace like your desktop. Now open your command prompt (cmd) through whatever means you are comfortable and change directory (cd) to the unzip folder or simply open your folder and drag/drop adb.exe into your CMD to be in the right place very fast. Then type "adb devices" without quotation marks and report for more troubleshooting .Assuming your Samsung cable is not faulty of course.
@ehsanotaku Yes i did root my phone on pheonix fire rom. No i do not see any. And debugging is checked, that was my first guess why it was causing this. I was checking, whether my device is recognized in linux (only available OS in present) and it was NOT, but the cable is not faulty, because it was charging my phone... but i will do recognize process on windows, hope it will get better. But thanks so far!
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
LiQuDiAk said:
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
Click to expand...
Click to collapse
off topic though, gender discrimination is prejudice,, sorry if you are offended . Learning from each other despite your gender,does not undermine your knowledge EVER mate You might find it hard to believe, but I am quite novice in android stuff myself ( learning a great deal from some female members though ).
Back to topic at hand now,,,So let Perfectly Clear take away the time-consuming tasks and fix some stuff ..1. so you can not access your sdcard's content from either systems,, even if you try some live bootable Ubuntu disk/flash into your system and boot it up,, you can't access the mount drive content , right?
2. screenshot of your device manger while you are connected always help mate
3. those long streams of numbers and words is supposed to be your device name , it means your device is communicating with your pc ( /sdcard/ should not be corrupted). You can push (copy ) some vital files to your device with following command :
again same path >> put some file into your desktop (drag/drop to cmd)
i.e: "adb push C:\Users\ehsanotaku\Desktop\test.txt /sdcard/"
back to your device and check root of your files with whatever file explorer you got to approve the theory
4. forgot to ask , just to be on the safe side your device is not in boot loop process, stuck on samsung splash screen or something like that, right?
okay, thanks!
1. I cannot access it trough USB to mobile way, but from SD card adapter, yeah I can (it is just the weird feeling, when you always have to put out your sd and do it that way, i would like to sort this out)
2. http://s1.postimg.org/nkta50u3x/Untitleddas.png I suppose the unknown device is my phone.
3. Just a question, my phone is not connected, i cannot access it and this doesn't help
4. Nope, it is working, i can access everything, just this connecting problem i have. anything else is running smoothly.
Let's say any of this will work, do you think flashing a stock rom will help? I am not sure, if this is problem of rom or not, so...
And maybe i wasn't clear (my bad if not) but when i plug the cable in my device and pc, pc will make this sound of new device found, but it wont show me anything, so my phone. It will charge, but it wont connect, it is behaving like it is on a charger and not connected to the phone.
@LiQuDiAk, Hasty actions are done in a hurry, sometimes without the necessary care or thought. Now let's not leap to any conclusion about your Android custom Rom and flashing back to stock. lets focus on your first most obvious problems,which is driver related.
You didn't declare your flavor of windows: i.e: Windows x86 based-PC;professional 7
Not so sure of your OS Name/Version and System Type, search "system information" in your search box.
Your task manger depicted ACPI x64 ( 64-bit system, no wonder previous 32-bit compatible didn't work out for you ).
Symptoms observed so far:
1. USB cable only charges ( remember your USB cable data line might be the culprit. Just in case of only charging,checking with another set recommended. Your USB port might be problem, some dirt or faulty data line, checking with another USP port doesn't heart though.
2. Windows recognizes something more (like in your case, struggling to find proper corresponding driver), but cannot see it as a Samsung android device (cannot allocate the installed USB drivers to the device).
-If you got Kies (Samsung proprietary software) installed on your PC, delete it with a descent uninstaller program such as CCleaner free version .Kies might cause driver conflict , use it as only last resort , if all drivers failed to communicate with s5830i device.
-Also Uninstall your previous given driver same way, now restart , back to system and grab set of universal Samsung Drivers from attachment .
3.Can't see your "USB connected" in Android notification bar, so you cant click on it and mount your storage data part while you are connected to your PC.
-Normally, when you plug in your Android device, Windows will recognize it as an MTP (Media Transfer Protocol) device and quietly mount it.
However, if you’ve ever attempted to unlock your device such as to install a new ROM or root it, then such miss behaviors might be expected occasionally .
Before i go for more troubleshooting , please provide a full screenshot from your "About Phone" page in your settings . I am quite curious about this phoenix Rom you have mentioned though . I am quite familiar with at least dozen of discontinued/ported projects, but never heard of such ported Rom from other models into s5830i .
Couple of solutions :
Navigate to your settings,Storage and touch the upper-right corner for the “USB computer connection” options, if you have this part available.
make sure “Media device (MTP)” is selected. ( if you have USB Utilities section or whatever added section in your custom settings go there . Selecting that will do the trick. If it does not, then you likely have a driver problem.
Open your device manager, Right click on your unrecognized device in question,choose update driver software, choose Browse my computer,find it through given x64 drivers in your package ,Restart. ( After a successful installation, restart your PC, you must have something like the picture in attachment ) .
Problem was not resolved, Uncheck your debugging option,power off your phone. Now hold Volume(+) + Home + Power for a couple of seconds simultaneously to get to your Samsung Recovery or your Clockwork Recovery, choose Reboot( might be some process/service in your background, which interfere with your Auto USB connected feature of your device. See if the problem is being resolved .
Problems have been persisting, we might need to format your SD card, but before that, insert it into your card reader, in your file explorer window choose Tools>Folder options>select view tab> tick your select hidden file.folders. Now copy all of your SD card's contents into some folder, safe inside your PC.
We can format your card through your clockwork mod recovery console, or some partition tools such as free mini partition wizard,,
problem still persist? let me know
Hey
After some rest with this, my mobile got it solved (dunno why, just once tried to do it and it works.)
So, thank you very much with your answers!!!!
And about that screenshots, I will PM you
But, really, thanks a lot, mate!!!!
I am using a Nexus 5 running Android 5.0.1, with adb version 1.0.32, on OS X 10.10.1.
When I reboot the device, on the initial screen I see:
USB debugging connected
Touch to disable USB debugging
I swipe up to unlock and then see the dialog:
Allow USB debugging?
The computer's RSA key fingerprint is: <....>
[] Always allow from this computer
I check always allow and tap OK.
If I reboot the device, I see the exact same thing again. I assume I should not be asked again and again to trust the same computer after a simple reboot.
Can anyone point me to a detailed description of how this system works so I can determine what is going wrong?
I believe the key identifying the computer is stored in the device in the data directory. I assume that a key would be stored on the computer as well. What is this location?
Is there anything else I can check?
Has anyone seen this before? If so, what was done to resolve the problem?
Hi!
I have recently bought an F1 and I can't connect it to PC (Windows or Linux). I turned Developer options on and enabled USB debugging. I tried every option in "Select USB configuration". The adb devices command always give empty list. The PCs are OK because they work with every other phones. On Windows I even tried to install USB drivers but didn't help. Could you help?
Did u give administrator rights when opening your adb programm?
Ziegenjupp said:
Did u give administrator rights when opening your adb programm?
Click to expand...
Click to collapse
I tried "sudo apt kill-server", "sudo apt start-server" and "sudo apt devices" but didn't help.
bartatamas said:
Hi!
I have recently bought an F1 and I can't connect it to PC (Windows or Linux). I turned Developer options on and enabled USB debugging. I tried every option in "Select USB configuration". The adb devices command always give empty list. The PCs are OK because they work with every other phones. On Windows I even tried to install USB drivers but didn't help. Could you help?
Click to expand...
Click to collapse
Once you enable Usb debugging in phone. Restart the phone and connect to pc. A pop up appears to Authorize the pc. Once done you can check the ADB list. It will be displayed only after you add the pc to the trusted device in the pop up.
Hope this helps. Thanks
sssyraj
sssyraj said:
Once you enable Usb debugging in phone. Restart the phone and connect to pc. A pop up appears to Authorize the pc. Once done you can check the ADB list. It will be displayed only after you add the pc to the trusted device in the pop up.
Hope this helps. Thanks
sssyraj
Click to expand...
Click to collapse
I hardly believe but it worked! thanks
sssyraj said:
Once you enable Usb debugging in phone. Restart the phone and connect to pc. A pop up appears to Authorize the pc. Once done you can check the ADB list. It will be displayed only after you add the pc to the trusted device in the pop up.
Hope this helps. Thanks
sssyraj
Click to expand...
Click to collapse
I can now see my device and transfer files, but for some reason, I `sudo adb devices` still doesn't see my phone.
bartatamas said:
Hi!
I have recently bought an F1 and I can't connect it to PC (Windows or Linux). I turned Developer options on and enabled USB debugging. I tried every option in "Select USB configuration". The adb devices command always give empty list. The PCs are OK because they work with every other phones. On Windows I even tried to install USB drivers but didn't help. Could you help?
Click to expand...
Click to collapse
If u r running on windows 10, try this method to fix "adb issue" :-
Before fixing ADB not recognized error, you should confirm that Android SDK has been saved on your computer and you know its location.
Step 1: Right-click "Computer" and choose "Properties" on pop-up menu.
Step 2: Click "Advanced system settings" on the left panel in new window.
Step 3: In System Properties window, under "Advanced" tab, click "Environment Variables".
Step 4: Environment Variables is open now. You can edit or delete existing variables in list, or create new environment variables.
Under "User variables for isunshare", click "New" button to create a new variable for running ADB on computer.
Step 5: Type Variable name and Variable value. Click OK.
Variable name: Path
Variable value: C:\Users\isunshare\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools
Step 6: You would see the new variable you just created in "User variables for isunshare". Click OK at the bottom.
Step 7: Open Command Prompt and type "adb", you would see ADB detailed information.
Now you have successfully fixed error "adb" not recognized as an internal or external program or batch file.
I've the same probelm during debloating my poco f1. Solved that by using this method.
who_i_am said:
If u r running on windows 10, try this method to fix "adb issue" :-
Before fixing ADB not recognized error, you should confirm that Android SDK has been saved on your computer and you know its location.
Step 1: Right-click "Computer" and choose "Properties" on pop-up menu.
Step 2: Click "Advanced system settings" on the left panel in new window.
Step 3: In System Properties window, under "Advanced" tab, click "Environment Variables".
Step 4: Environment Variables is open now. You can edit or delete existing variables in list, or create new environment variables.
Under "User variables for isunshare", click "New" button to create a new variable for running ADB on computer.
Step 5: Type Variable name and Variable value. Click OK.
Variable name: Path
Variable value: C:\Users\isunshare\Downloads\android-sdk_r24.4.1-windows\android-sdk-windows\platform-tools
Step 6: You would see the new variable you just created in "User variables for isunshare". Click OK at the bottom.
Step 7: Open Command Prompt and type "adb", you would see ADB detailed information.
Now you have successfully fixed error "adb" not recognized as an internal or external program or batch file.
I've the same probelm during debloating my poco f1. Solved that by using this method.
Click to expand...
Click to collapse
These instructions are for systemwide installation of adb. The OP's issue is not that. The correct advice has already been given and it has worked.
sssyraj said:
Once you enable Usb debugging in phone. Restart the phone and connect to pc. A pop up appears to Authorize the pc. Once done you can check the ADB list. It will be displayed only after you add the pc to the trusted device in the pop up.
Hope this helps. Thanks
sssyraj
Click to expand...
Click to collapse
In my case I am unable to do so as my phone is completely wiped clean. Tried updating the adb interface manually everytime I try to boot fastboot boot twrp.img I get a blank slightly lit-up screen.
Also adb devices shows nothing
C:\Users\shal1018\AppData\Local\Android\Sdk\platform-tools>adb devices
List of devices attached
C:\Users\shal1018\AppData\Local\Android\Sdk\platform-tools>adb shell
adb.exe: no devices/emulators found
sssyraj said:
Once you enable Usb debugging in phone. Restart the phone and connect to pc. A pop up appears to Authorize the pc. Once done you can check the ADB list. It will be displayed only after you add the pc to the trusted device in the pop up.
Hope this helps. Thanks
sssyraj
Click to expand...
Click to collapse
In my case My Phone is not accessible as its wiped clean..what do I do?
noahshines said:
In my case I am unable to do so as my phone is completely wiped clean. Tried updating the adb interface manually everytime I try to boot fastboot boot twrp.img I get a blank slightly lit-up screen.
Also adb devices shows nothing
C:\Users\shal1018\AppData\Local\Android\Sdk\platform-tools>adb devices
List of devices attached
C:\Users\shal1018\AppData\Local\Android\Sdk\platform-tools>adb shell
adb.exe: no devices/emulators found
Click to expand...
Click to collapse
This happened to me too. Recently with 12.0.2.0 modem, I did the wipe of system and data partition along with it I tried to update the twrp to latest using old twrp. With this, even fastboot can't be reachable ie. Lighting up but no image in fastboot and phone won't respond in even miflash. I had took it to Xiaomi service center and they put the software for a nominal price of 2.5 USD in India. There after we can change to whatever firmware we like.
So, try reaching the Xiaomi service center. Thanks
sssyraj said:
This happened to me too. Recently with 12.0.2.0 modem, I did the wipe of system and data partition along with it I tried to update the twrp to latest using old twrp. With this, even fastboot can't be reachable ie. Lighting up but no image in fastboot and phone won't respond in even miflash. I had took it to Xiaomi service center and they put the software for a nominal price of 2.5 USD in India. There after we can change to whatever firmware we like.
So, try reaching the Xiaomi service center. Thanks
Click to expand...
Click to collapse
Thanks for the respose..I was thinking of doing the same!
sssyraj said:
This happened to me too. Recently with 12.0.2.0 modem, I did the wipe of system and data partition along with it I tried to update the twrp to latest using old twrp. With this, even fastboot can't be reachable ie. Lighting up but no image in fastboot and phone won't respond in even miflash. I had took it to Xiaomi service center and they put the software for a nominal price of 2.5 USD in India. There after we can change to whatever firmware we like.
So, try reaching the Xiaomi service center. Thanks
Click to expand...
Click to collapse
Xiaomi service centre said the couldn't... would you mind telling me which state in India.. did you take it to?
noahshines said:
Xiaomi service centre said the couldn't... would you mind telling me which state in India.. did you take it to?
Click to expand...
Click to collapse
I got it serviced at Chennai, Tamil Nadu. My phone shown boot logo and loops due there isn't system as I wiped it. So they took it as Software issue and have done the software update for Rs 180. Sometimes we might need to pretend as novice to leave something to Professionals. Thanks.
Cheers
sssyraj.
Same with my POCO M3. Mi PC Suite device not detected, I can't unlock it too because can't be detected. I'm tired to follow multiple methods online, reinstalling, uninstalling vise versa even disabling antivirus, and reinstalling again and again with adminisrator rights. Thank you for any help will rise in soon to easily fix these issues.
Background:
I have a rooted SM-G900V (Verizon Galaxy S5) running Lollipop with a broken screen. I have Titanium Backup installed and it was supposed to be running weekly but wasn't. I have recovered my photos, contacts, etc. by connecting to my PC and copying the internal storage and from my gmail restore to a new GS5. I want to recover app data from a couple apps. The phone has USB debug turned on and I can connect with ADB.
I thought I could just run an ADB backup, but apparently in order for the backup to initiate I have to press a button on the lower right of the screen...which is broken. I suppose if I could connect via WiFi and then use a MHL cable I could use a keyboard/mouse to click the button on the phone but I don't have a MHL cable right now and I don't know if that would work anyway (WiFi ADB hasn't worked for me to this point).
THE QUESTION:
I've done a lot of reading and found a number of ADB options that sounded viable, but have not been successful. I have TitaniumBackup installed and thought that I could launch the "backup all" batch process but don't see how to make that happen. I have a new GS5 that is identical setup so I could record some actions on that one and play them on the broken one potentially.
I'm open to any suggestions.
bkenobi69 said:
......... THE QUESTION: I've done a lot of reading and found a number of ADB options that sounded viable, but have not been successful..........
Click to expand...
Click to collapse
The only thing I can think of is to guide you to the following thread that should, hopefully, be what you need.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
I really appreciate the suggestion. FWIW, I sort of came up with a similar approach myself that I almost have working. I turned on ADB WiFi on the device and then plugged in my wireless USB mouse/keyboard. I set up a script that performs a screen capture every 2 seconds and downloads it locally. With Windows7 image viewer, it automatically updates when the image changes so I get a slide show of what's happening on screen. The only issue I have is that the SD card isn't set up for TitaniumBackup apparently since I get an error when I select the backup action. If I can get TitaniumBackup set up correctly, I should be golden!
Thanks for posting that link. Ironically, the solution I developed was very similar in concept. I will give a short description for others who may need to recover data from a phone with a broken screen.
Prerequisites:
* TitaniumBackup - This can be installed from the Play store even if the phone is not functioning
* USB debug mode enabled - Without this, you are stuck. The only issue here is newer phones don't always enable MTP on connection. My old on did but the new one does not. If it doesn't connect via MTP, you will need to install MTPEnabler or similar.
* USB keyboard/mouse combination
* USB cable
* Charged fully functional phone sans screen
* ADB software - You must have the same version on the phone and PC. If not, it won't work reliably/at all. I went with fastboot_adb(1.0.32)_071114_r21 since I have 1.0.32 on my SM-G900V.
Basic steps:
1) Unpack the ADB software on your PC in a convenient location (C:\ADB)
2) Connect phone to PC via USB
3) Send command to enable WiFi ADB connection
4) Disconnect phone from USB
5) Connect ADB via WiFi
6) Run following batch script:
:loop
adb shell screencap /sdcard/screen.png
del screen.png
adb pull /sdcard/screen.png
echo captured
timeout /t 2
goto loop
Click to expand...
Click to collapse
This will dump a screen shot every 2 seconds
7) Open screen.png in Windows image viewer. It should automatically update when the image is refreshed.
8) Type "launch titaniumbackup" and press enter on wireless keyboard.
9) Using either tab or mouse, select the check box to launch TB.
10) Using either tab or mouse, select "menu" from upper right.
11) Using mouse, select "batch actions" from the list.
12) Using mouse, select "RUN" next to "Backup all user apps" from the list.
If all went well, you now have your phone backup up all application data to your SD card which can be easily used on a new phone to restore data.
NOTE:
It may be possible to also use the built-in ADB backup function. I attempted this at one point, but it requires selecting a button in the lower right on the phone. Since I was using ADB over USB at the time, I could not click the button on the phone since I only had one device connected (no hub). If you have a hub it may be possible to use that approach. Alternately, if you use ADB over WiFi, it should also work. However, be aware that there is no way to see where you are clicking or confirm that it worked other than looking at the files on the SD card as ADB backup doesn't appear to give any feedback. Also, this isn't as easy as TB when it comes to restoring as you either have to backup every app one at a time or all together. When restoring, it's also a one shot deal so you can't select specific apps to restore from a larger set.