I am trying to install the Samsung USB driver from Samsung Galaxy S3 ToolKit but it insists the mobile phone is in use. It says "The mobile phone is in use. To install normally, you need to remove the device and restart the computer. Please run the SAMSUNG USB Driver for Mobile Phones installer again after restarting." I have tried restarting but it still shows that stupid error message. Using Windows XP. How do I install the drivers?
vpwrf said:
I am trying to install the Samsung USB driver from Samsung Galaxy S3 ToolKit but it insists the mobile phone is in use. It says "The mobile phone is in use. To install normally, you need to remove the device and restart the computer. Please run the SAMSUNG USB Driver for Mobile Phones installer again after restarting." I have tried restarting but it still shows that stupid error message. Using Windows XP. How do I install the drivers?
Click to expand...
Click to collapse
You could try this.
Kangburra said:
You could try this.
Click to expand...
Click to collapse
Still the same error.
vpwrf said:
Still the same error.
Click to expand...
Click to collapse
Is the phone stuck in Device manager? Remove it and try again, do not plug the phone in while installing the drivers.
Kangburra said:
Is the phone stuck in Device manager? Remove it and try again, do not plug the phone in while installing the drivers.
Click to expand...
Click to collapse
What does it appear as in the device manager that needs removing? I tried removing a couple of things that appeared when I plugged it in but still shows that error.
Uninstall everything Samsung from the PC.
Reboot the phone and the PC.
Follow the guide in the link above, then when finished plug the phone in.
Kangburra said:
Uninstall everything Samsung from the PC.
Click to expand...
Click to collapse
How do I do that? I have made sure nothing Samsung is in the device manager and restarted again but still can't install the driver.
vpwrf said:
How do I do that? I have made sure nothing Samsung is in the device manager and restarted again but still can't install the driver.
Click to expand...
Click to collapse
You are going to need help with the PC, it is not a phone problem. Take it to a PC shop near you.
It's the stupid mistake I made by plugging the phone in before installing the drivers. It looks like the only way now is by doing a clean Windows installation unless someone can help me properly remove the failed drivers.
vpwrf said:
It's the stupid mistake I made by plugging the phone in before installing the drivers. It looks like the only way now is by doing a clean Windows installation unless someone can help me properly remove the failed drivers.
Click to expand...
Click to collapse
You just need someone who can do remove the device for you. Don't you have computer shops where you live? No need to wipe the whole machine over a single device.
I think it's a waste of money taking it to a computer shop. It will cost at least £20
SOLVED
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
gregorypeck said:
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
Click to expand...
Click to collapse
Thank you very much. I had the same error and your method worked for me
----
Here are my observations:
In my log, the error had been exactly the same.
I searched my registry for the key Vid_04e8&Pid_6860.
I found it in the following locations:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB\VID_04E8&PID_6860
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\USB\VID_04E8&PID_6860
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_04E8&PID_6860
I think it is only necessary to modify CurrentControlSet, the other keys are just backups.
I had to right-click VID_04E8&PID_6860, change the permission settings to full access and then I deleted the whole key named VID_04E8&PID_6860.
Finally the driver installer worked.
gregorypeck said:
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
Click to expand...
Click to collapse
Worked perfectly for me too, with one exception - at first I was not able to delete some of the keys. I had to right click on them, click permissions, and then give Everyone full access so I could delete them.
Hello, i have the same problem on windows 7, and cant connect my galaxy s4
- The mobile phone is in use. To install normally, you need to remove the device and restart the computer. Please run the SAMSUNG USB Driver for Mobile Phones installer again after restarting.
that hint will work on win7?
thank you
and i try it, and cant delet key, runs regedit as admin and cant change permision.
ty
Try this one Universal ADB Driver
gregorypeck said:
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
Click to expand...
Click to collapse
Thank you very much, worked for me too
gregorypeck said:
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
Click to expand...
Click to collapse
Works like a charm, thanks for the solution.
gregorypeck said:
After several hours I finally have solved this problem.
go to the C:\Documents and Settings\All Users\Application Data\Samsung\Device Error Recovery
open the file: default-0.log
scroll to the end of this file, you will find something like:
"2014/02/01 22:00:26 0625 [setup(dll) ][RemoveAllDriverDeviceKey:656 ] Delete Driver & Device Keys Failed1(-536870396)... USB\Vid_04e8&Pid_6860&Rev_0400"
Now, open regedit and find all keys with "Vid_04e8&Pid_6860" in their names. Delete them all.
If you have a problem with deleting, change the permisions for the key (right-click on key and add yourself to the user group).
And now you can install new USB driver.
Regards
Click to expand...
Click to collapse
Can't get autorisation to delete, can you help me please ?
samsung usb drivers
question to anyone: hi i am very new to technology and am self learning about android, rooting, and about my devices. i am learning this stuff on my old samsung galaxy s3 gt-i9305t 4g telstra, which rus kitkat 4.4.4. i have been trying to download samsung usb drivers since i am frugal i would like to do all this for free which i am constantly reminded by other members thats the way to go . could anyone point me to a good website for the drivers, also if you know of a good tutorial website or you tube link i ill be forever greatful to you. thank you for your time
Related
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment Rockusb.rar
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
Thanks for the info. Will be giving it a go later today
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
when in doubt go back to the forums. I can not get the inf in the rockusb to install. "Installation for this file type not permited" . So I'm stuck, the program will not complete. I'm on windows 7 so maybe the driver is for another system. If you can provide futher help, Thanks in advance.
New approach
Ok I cannot get the drivers to install on my computer. Window 7 seems to default to its own driver and will not let me install the rockusb drivers.
With that said, I have the system Update.img and was wandering if the img itself can be rooted and then updated to the tablet. If this is possible and anyone with the knowledge is willing I will upload it. Or if someone is really patient and would like to walk me through the process and I will attempt to do this myself
No Help
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
Can't tell your level of PC knowledge so if you already know this don't get offended. The .inf is editable and there are areas in there that allow manufacturers to prevent installation on some OS's to prevent conflicts. Make a system restore point or better yet a backup and then post the contents of the INF somewhere and point the folks here to it and they may be able to help you edit it to install. Regardless, you'll have to use the "have disk" option instead of letting windows search for a driver even if you get the edits right. And the usual disclaimers about me not being responsible for any issues with your equipment as a result of this are in effect.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
I was able to root using the instructions above although i don't think you need the rockusb drivers. You just need the usb drivers that come with the android sdk. I am on Win 7. Thanks for the above info for rooting.
I was able to install ROM manager and now proceeding to backup ROM and upgrade using this guide: cant post link as forum is preventing, but search for rom flash guide on androidpolice com.
Hope this helps.
Big thanks to this thread to get me going...!!!
?
could someone please, Barney style, Explain how I am supposed to select the android_winusb.inf because my steps are as follows. Right click on device p771a in device manager, browse my computer, let me pick from a list of device drivers, have disk, point to the google usb driver (C:/Android/android-sdk/extras/google/usb_driver) select the android_winusb.inf open. Hit ok, (The folder you specified doesn't contain a compatible software driver for you device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems). Hope this helps explain my troubles. Glad that my thread is helping others to root this device but it does not work for me.
Could it really be that simple?
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
tannerjames said:
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
Click to expand...
Click to collapse
Glad you could figure it out...
I was not able to use the ROM Manager to backup the ROM since the device is not supported on this tool, but see below for how you can obtain the stock image.
I've tried to flash multiple different ROMs using RKAndroid to the tablet, spending days on this, with no success. The tool itself works great and I am able to flash the ROMs since it supports the RK29 chipset which I believe this tablet has. The stock ROM for this device is available from the manufacturers web site (the link is available when you go to Settings => About Device => System Update, hkcdigital dot com slash update slash update.img), if anyone would like to take the stock rom and upgrade it to Android 4.2/JB.
I was able to unpack/repack the stock image using the wendal image tools and modify / cook the ROM using Android kitchen method described elsewhere in this forum. Rockchip Batch Tool is another great utility to flash custom ROMs to this device. Also, If you put the ROM as update.zip or update.img file on the microSD card, the tablet will take it and flash the image as long as it is in the right format. Ofcourse you can put the tablet into recovery and restore from there as well. I've found that the stock image (update.img) has the following file/folder format when unpacked: /RK29xxLoader(L)_V2.27.bin, /package-file, /parameter, /recover-script, /update-script, /Image/boot.img, /Image/system.img, /Image/recovery.img and /Image/misc.img.
Is it possible to upgrade this tablet to Android 4.2 or atleast Jelly Bean? Would be very helpful if someone is able to do this. The most success I've had so far is with the custom ROM Oma_Odys_Loox_JB_4.1.1_v1.2.2a flashed using RKAndroid. It flashed the tablet fine, updated the boot etc. On tablet boot I am able to see the new logo, but then the it doesn't go anywhere from there. I think customizing this ROM or the stock ROM we should be able to get the new OS on to the HKC tablet. I've given up for now since I don't have the time to spend on this anymore. If someone is able to do this, please post the instructions or upload the custom ROM, as I am sure it will benefit a lot of people and will be much appreciated. Happy cooking!
Thanks!
jawadshaik- rom manager
If you have successfully flashed rom manager on this device could you post the steps you took to do so. What version? Manual flash? The program itself says there is no recovery for this device.
Sorry jumped the gun on that last post. Thanks for the info
What's the secret to keeping the battery from draining so quickly while it's idle? I just got this and see it drained about 40% in about 2 hours I think and I wasn't using it.
tannerjames said:
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
Click to expand...
Click to collapse
@jawadshaik
Just out of curiosity, when you were flashing that Rom that brought up the boot screen, did you do a wipe/factory reset from recovery mode before flashing? I have no idea if that would help or not, but most if not all roms require a data wipe before flashing... Just curious if you had tried this as I have heard of this happening on other devices because a data wipe wasn't done first. Might be worth a shot if you haven't tried it already, just a thought
Sent from my Huawei u8651s using xda app-developers app
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
So after doing working on this a while, I've finally figured it out. Here are some caveats:
1. You can't do this on a Mac or Linux box. Don't ask me why, you just cant.
2. You have to turn on USB debugging, change the Security to allow Unknown sources and MOST IMPORTANT: when you plug it in, you have to change it to "Connected as a Camera". Putting it in storage mode doesn't work!
HOW TO INSTALL THE PROPER DRIVER & ROOT THE DEVICE:
1. Follow the steps quoted above and download the Google Android SDK, and the Java JDK (from oracle.com/java).
2. When you first plug it in (use the USB plug labeled USB not the HOST one), it complains and will discover a P771A device. When it does, right click on your computer, choose Manage my computer, go to the device manager and then right click on the P771A device. Click "Update Device Driver". Choose "Browse my computer for Driver software". Then choose, "Let me pick from a list of drivers on my computer". Browse to the \adt-bundle-windows-x86_64\sdk\extras\google\usb_driver folder which you would have if you had downloaded and installed the Google Android SDK. A list of 3 drivers will appear when you click OK. CHOOSE THE "ANDROID BOOTLOADER INTERFACE" as the driver. None of the others work.
3. Run the root script batch file mentioned above which can be found here at: sourceforge.net/projects/androidroot
4. The root script isn't really great at explaining so I'll try. When you first run it, make sure your device is unlocked and on the home screen.
5. The first thing it will do is reboot your machine. Don't press enter until your machine comes back up.
6. After your machine boots unlock it and then press Enter again. Your machine will reboot. This time it won't seem to come up but the backlight will remain on.
7. Wait about 30-45 seconds then press enter again. You should get: uid=0(root) gid=0(root) in the command prompt window.
8. Press Enter. You should get:
remount succeeded
727 KB/s (22364 bytes in 0.030s)
Removing changes except ROOT...
Installing superuser...
2288 KB/s (843503 bytes in 0.360s)
9. After about 30-60 seconds, your device should reboot. You'll see a box briefly saying "Android is Upgrading" and you'll arrive at the lock screen. Press Enter to exit the command prompt.
Your device is now rooted and you should see "SuperUser" installed. I promptly installed "root uninstaller" to get rid of Facebook, Skype, and Youtube which my little kids don't need access to. This device doesn't have a bootloader or recovery mode so rooting it doesn't get you much besides the ability to uninstall the system software. Have fun.
This may help someone but on step 2 of the guide on the second page, after you right click your device and go to "Let me pick from a list of drivers on my computer". You then click "Show All Devices" then "Have Disk..." Direct it to the root of the adt-bundle folder you downloaded then you can select from the three drivers. I'm on windows 7 32bit and the drivers didn't show up for me like how it was suppose to..
I also could NOT get any of the drivers in the "manufacturer USB" packet to install... I WAS able to install the google drivers, but that also would not allow ADB to see the device... So still stuck with everyone else...
P771A possible problem
I'm having a similar problem where the USB driver downloaded through Android SDK's -> Extras -> Google USB Driver, tells me that the file contains no information about my device. I noticed in the Sources of SDK, there wasn't an API for 4.0.4, only 4.0.3 then 4.1, so i downloaded 4.0.3 repo.
============================================
my devices is on 4.0.4, and my Kernal is as follows:
3.0.8+
[email protected] #8
Wed Aug 29 09:59:19 PDT 2012
Build Number:
P771A-user 4.0.4 IMM76D user.v402.007 release-keys
============================================
I've also made sure weather Unknown Sources is on, as well as USB debugging.
Might the Kernal be the problem? Also, does it matter weather its MTP or CTP?
Now HKC is telling me that they don't support the ability to jail break their devices
Sent from my P771A using xda app-developers app
Hello;
This was my first time installing a Rom. I was fed up with my phone responding slowly and in time jams.
1-The first thing I did was install cwm recovery v6.0.2.7.
2-Then use the S3 tool kit available in xda to make a backup of all except system apps and internal storage data and it was stored in a .bak file. So that games and other apps keep their info as it is a hassle to start from the beginning.
3-Installed CM 10.1 nightly used in the instructions provided here.
All is okay up to here.
4-Tried to restore apps and app data through S3 tool kit but it won't display the data in the phone. I did enable the usb debugging on the cm10.1 (by pressing 7 times on the build name to enable the developers option and enabling usb debugging). I had the same problem when trying to do the backup in step 2, but it connected through the adb mode. This problem is that when ever I connect a device via usb windows installs the driver so every time I connect my phone windows installs the drivers.
5- When step 4 did not work I tried to restore using Holo Backup but no use no able to connect through to adb mode.
I can access the phone storage but I believe the appropriate drivers are not running when using the restore programs even though they are installed.
So the questions are:
1- Is there a way to fix the connection to be able to use S3 unified tool kit or if any one has dealt with the same problem?
2- Is there a way to restore the .bak file via cwm recovery?
3-For future use; An app or program that can be stored in the phone to avoid the use of a PC. The app or program would back-up contacts, sms text, apps and app data into the virtual sd or cloud to avoid deletion when "wipe data/ factory reset" after installing a rom.
I look forward to your replies.
Thank you.
What drivers do you have? Have you tried Universal Naked Driver? That's the only way I could get adb to work on mine when running CyanogenMod
wststreet said:
What drivers do you have? Have you tried Universal Naked Driver? That's the only way I could get adb to work on mine when running CyanogenMod
Click to expand...
Click to collapse
The image below shows the Drivers I currently have.
I used to have a lot more but a majority of them were copies of the same driver.
I had 2 other Samsung drivers but I also deleted them. According to an article that stated a fix to the problem is to uninstall all usb drivers except mouse and keyboard and reinstall the usb drivers of the device desired, but no success.
sub-80 said:
The image below shows the Drivers I currently have.
I used to have a lot more but a majority of them were copies of the same driver.
I had 2 other Samsung drivers but I also deleted them. According to an article that stated a fix to the problem is to uninstall all usb drivers except mouse and keyboard and reinstall the usb drivers of the device desired, but no success.
Click to expand...
Click to collapse
I tried to install the universal naked driver but no success. I followed the instruction went into the device manager and under the samsung android phone was the samsung android ADB interface which I uninstalled and checked the delete part. The pc requested to restart which I forgot to turn off the the internet which resulted in the driver being installed once it restarted. Tried a second and third time with no internet but when I uninstall and check the delete marker the pc does not ask to reboot. And if I try to update the driver with VND it notifies me that it is up to date.
Any solutions?
sub-80 said:
I tried to install the universal naked driver but no success. I followed the instruction went into the device manager and under the samsung android phone was the samsung android ADB interface which I uninstalled and checked the delete part. The pc requested to restart which I forgot to turn off the the internet which resulted in the driver being installed once it restarted. Tried a second and third time with no internet but when I uninstall and check the delete marker the pc does not ask to reboot. And if I try to update the driver with VND it notifies me that it is up to date.
Any solutions?
Click to expand...
Click to collapse
Tried ADB wifi but no success the pc says that there are no adb devices.
Also tried PDANet+ to install the drivers but software does not see the s3.
s there a way to restore the .bak file via cwm recovery
tried changing the file name by removing the .bak
jje
JJEgan said:
s there a way to restore the .bak file via cwm recovery
tried changing the file name by removing the .bak
jje
Click to expand...
Click to collapse
removed the .bak extension and placed it in the download folder of my virtual sd folder and pressed restore on cwm but nothing happened.
Could be because the backup is password protected?
Also tried to restore the file via titanium backup through the extract simple adb with and without the extension but only says analyzing file and remains that way for hours.
So I have a Samsung Vibrant(just got it recently) and I'm having problems when i connect it to the computer. It gives me an USB device not recognized on my windows 8 computer. I have spent all morning searching and reinstalling drivers and trying my old pc and new cables and i found out that my old windows 7 computer with 4GB of ram and an overloaded hard drive will detect my device the problem there is it not my main computer and i dont want to have to connect all the vga cables boot it up connect mouse and ect to use this computer just to be able to copy files, and do other things from my computer to my phone I dont know why my main computer dell inspiron windows 8 will not work when it was a couple of days ago when i had a problem with conectivity and had to flash back to stock but now it wont connect. could someone help me? Here's a list of things i've tried
installing kies
installing adb again
aoi tool and then drivers
a bunch of diffrent drivers found on the fourms
diffrent usb cable
i would like to be able to do it on my main computer but its not working if someone could help that would be great
also please dont hate on me for having windows 8 jk i dont care :good:
I'd have to say that your drivers are all scrambled. Look up "android SDK" here on xda and install that for a bigger variety of drivers. Or just download Google's USB driver and manually install it through device manager which always works for me. Windows 8 is new and very complicated.
Vono123 said:
I'd have to say that your drivers are all scrambled. Look up "android SDK" here on xda and install that for a bigger variety of drivers. Or just download Google's USB driver and manually install it through device manager which always works for me. Windows 8 is new and very complicated.
Click to expand...
Click to collapse
I will try this when I get home from school this afternoon but i have tried downloading android SDK(adb correct?) and then going into device manager and then going to downloads/adb/sdk/exstras/google/usb drivers and it never finds anything.
apples723 said:
I will try this when I get home from school this afternoon but i have tried downloading android SDK(adb correct?) and then going into device manager and then going to downloads/adb/sdk/exstras/google/usb drivers and it never finds anything.
Click to expand...
Click to collapse
Android SDK is installed in the main drive right? local disk c?
You have to click the folder (usb_driver) and then click update.
In the android sdk folder there should be and exe file called SDK manager. There you will be able to download all the drivers for your current android version also the latest Google drivers and SDK tools etc.
I was stuck on this process for a long time because it allways works different for everybody. Just keep me posted on what you do I'm more than glad to help.
Vono123 said:
Android SDK is installed in the main drive right? local disk c?
You have to click the folder (usb_driver) and then click update.
In the android sdk folder there should be and exe file called SDK manager. There you will be able to download all the drivers for your current android version also the latest Google drivers and SDK tools etc.
I was stuck on this process for a long time because it allways works different for everybody. Just keep me posted on what you do I'm more than glad to help.
Click to expand...
Click to collapse
everything is up to date in the sdk manager do i need to reinstall it? also it still wont find the drivers i have atatched some png files take a look the picktures and it will show you the where the drivers are and what im selecting
EDIT****
I forgot to mention i tried it at school on a windows 8 computer and it worked fine its my crappy computer thats only five months old
apples723 said:
everything is up to date in the sdk manager do i need to reinstall it? also it still wont find the drivers i have atatched some png files take a look the picktures and it will show you the where the drivers are and what im selecting
EDIT****
I forgot to mention i tried it at school on a windows 8 computer and it worked fine its my crappy computer thats only five months old
Click to expand...
Click to collapse
So what exactly happens when you click update? What does it say?
Is your PC up to date? (update wise)
Do you have the the drivers for the phone itself like samsung drivers?
And did you try rebooting your PC after installing your drivers? <-- that is important. You should always reboot after install or uninstalling drivers otherwise you'll end up scrambling them.
From the pictures it shows you have the drivers but I'd also try going deeper than usb_driver, try clicking on i386 or amd64.
Vono123 said:
So what exactly happens when you click update? What does it say?
Is your PC up to date? (update wise)
Do you have the the drivers for the phone itself like samsung drivers?
And did you try rebooting your PC after installing your drivers? <-- that is important. You should always reboot after install or uninstalling drivers otherwise you'll end up scrambling them.
From the pictures it shows you have the drivers but I'd also try going deeper than usb_driver, try clicking on i386 or amd64.
Click to expand...
Click to collapse
i have the latest update from microsoft and yes i have the drivers for my phone itself and i rebooted a right after i installed the drivers and then unisntalled and i have gone into i386 and amd64 give me a second and i upload a picture of the error
EDIT
i uploaded the pictue of the error im getting
apples723 said:
i have the latest update from microsoft and yes i have the drivers for my phone itself and i rebooted a right after i installed the drivers and then unisntalled and i have gone into i386 and amd64 give me a second and i upload a picture of the error
EDIT
i uploaded the pictue of the error im getting
Click to expand...
Click to collapse
OK make sure there are no HTC drivers on your PC. When you hook up your phone does USB storage work or anything like that?
Check those out and then I want you to go to Google, download pdanet latest version via pc (dont install yet) and go to the play store and install on your phone turn on USB debugging and the install non market apps and hook your phone up to the computer. Then install pdanet via PC and see if that works. HTC drivers get in the way of Samsung's BTW.
Vono123 said:
OK make sure there are no HTC drivers on your PC. When you hook up your phone does USB storage work or anything like that?
Check those out and then I want you to go to Google, download pdanet latest version via pc (dont install yet) and go to the play store and install on your phone turn on USB debugging and the install non market apps and hook your phone up to the computer. Then install pdanet via PC and see if that works. HTC drivers get in the way of Samsung's BTW.
Click to expand...
Click to collapse
you want me to install pdanet on my phone too and by the way there is no htc drivers that are on my computer
apples723 said:
you want me to install pdanet on my phone too and by the way there is no htc drivers that are on my computer
Click to expand...
Click to collapse
OK good and yes its in the play store for free but I don't think you have to install it but it makes the process more easy for ya.
You do have usb debugging and install non market apps checked right? You need those on.
Vono123 said:
OK good and yes its in the play store for free but I don't think you have to install it but it makes the process more easy for ya.
You do have usb debugging and install non market apps checked right? You need those on.
Click to expand...
Click to collapse
still giving me the error i think its my computer because it works on our family laptop school computer and basment computer how do i totally unistall drivers not from device manager theres a difrent way i think not sure
apples723 said:
still giving me the error i think its my computer because it works on our family laptop school computer and basment computer how do i totally unistall drivers not from device manager theres a difrent way i think not sure
Click to expand...
Click to collapse
I want you to uninstall all your Samsung drivers(not android SDK) under control panel/uninstall programs. If you see something like Samsung kies definitely uninstall it. Reboot your computer and follow this guide for windows 8:
http://forum.xda-developers.com/showthread.php?t=2038555
After this if it doesn't work I'd recommend pulling out your old computer for android modding lol. I'll still look up some threads for your problem. Let me know what's going on after that. Make sure when you follow that guide your phone can not be plugged in the computer. And when you plug your phone into the computer after everything is done and after you reboot your computer for the second time, USB debugging has to be off and when phone is done unplug and turn back on USB debugging and plug back in and wait for that. Adb should work.
[Edit] you can also try running your drivers in windows 7 compatibility. Sorry I couldn't help much.
Vono123 said:
I want you to uninstall all your Samsung drivers(not android SDK) under control panel/uninstall programs. If you see something like Samsung kies definitely uninstall it. Reboot your computer and follow this guide for windows 8:
http://forum.xda-developers.com/showthread.php?t=2038555
After this if it doesn't work I'd recommend pulling out your old computer for android modding lol. I'll still look up some threads for your problem. Let me know what's going on after that. Make sure when you follow that guide your phone can not be plugged in the computer. And when you plug your phone into the computer after everything is done and after you reboot your computer for the second time, USB debugging has to be off and when phone is done unplug and turn back on USB debugging and plug back in and wait for that. Adb should work.
[Edit] you can also try running your drivers in windows 7 compatibility. Sorry I couldn't help much.
Click to expand...
Click to collapse
ive tried so many things i give up it makes me mad that any other computer even ones with windows 8 on them it works fine with out any sepecial installation but on my current computer it doesnt
apples723 said:
ive tried so many things i give up it makes me mad that any other computer even ones with windows 8 on them it works fine with out any sepecial installation but on my current computer it doesnt
Click to expand...
Click to collapse
I think I know what the problem is. Make sure you uninstall all the previous drivers, then have the correct drivers ready.
What you have to do is to disable driver signature enforcement.
Step 1. Go to the right bottom corner of the desktop and wait for the side menu to appear. When it's there click on the gear icon with the title "Settings".
Step 2. Now click on the entry "More PC Settings", then click on the entry "General".
Step 3"Restart now" (under "Advanced start up ") and click it.
Step 4. Now click "Troubleshoot", then "Advanced Options" and after that click "Windows Start up Settings".
Step 5. Click on "Restart" and wait, then on the next screen press F7.
You will now reboot, and try now to install the drivers (by manually selecting the folder in device manager).
I'm not sure what is the correct drivers for you.
But try this. It's still worth a shot.
binaryfalcon said:
I think I know what the problem is. Make sure you uninstall all the previous drivers, then have the correct drivers ready.
What you have to do is to disable driver signature enforcement.
Step 1. Go to the right bottom corner of the desktop and wait for the side menu to appear. When it's there click on the gear icon with the title "Settings".
Step 2. Now click on the entry "More PC Settings", then click on the entry "General".
Step 3"Restart now" (under "Advanced start up ") and click it.
Step 4. Now click "Troubleshoot", then "Advanced Options" and after that click "Windows Start up Settings".
Step 5. Click on "Restart" and wait, then on the next screen press F7.
You will now reboot, and try now to install the drivers (by manually selecting the folder in device manager).
I'm not sure what is the correct drivers for you.
But try this. It's still worth a shot.
Click to expand...
Click to collapse
didnt make a difrence still getting error i think its something with my system so i guess without a full diagonostic it wont work
**New** Root Access is Now Required!
Download:
- G900T_OF6_Batch_Debloater_&_App_Freezer
Instructions:
1. Extract the G900T_OF6_Batch_DeBloater & App Freezer folder onto your desktop.
2. Turn on USB Debugging from Developer Options and connect your device to your *PC.
3. Double-click DeBloater.bat to launch the program.
4. Select "Light," "Medium," "Extreme", or "Freeze Apps"**and press "Enter."
5. Grant Root Access if prompted by your device and press "Enter" to begin.
6. Once complete press "Enter" to return to the Main Menu and select ***"Reboot Device."
7. Last, select "Exit" from the Main Menu to end your session. Done!
* Make certain that you have Samsung Drivers installed.
** Use notepad++ or other text editor to view/edit the lists of affected apps in the debloater.bat file.
*** It is normal for apps to begin force closing prior to rebooting your device.
muniz_ri said:
Download:
- G900T_OF6_Batch_DeBloater
Instructions:
1. Extract the G900T_OF6_Batch_DeBloater folder onto your desktop.
2. Boot into *TWRP, Press "Mount" and make certain that "system" is checked.
3. Connect your phone to your **PC while still in TWRP and double click on the DeBloater.bat file.
4. Select "Light," "Medium," or "Extreme" debloating (see DeBloater.bat file for list of removed apps).
*I used TWRP 2.8.6.0 (could not get TWRP 2.8.7.0 to connect to PC).
** Make certain that you have Samsung Drivers installed.
Click to expand...
Click to collapse
The Tmobile my account app shows up in my installed apps but no where to be found in system/app or priv_app any ideas ?
Sent from my SM-G900T using XDA Free mobile app
dzhowandai said:
The Tmobile my account app shows up in my installed apps but no where to be found in system/app or priv_app any ideas ?
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Its likely under a different name. I used the extreme option and its no longer installed.
It's a no go fir me with same result. Is your rom deodexed or does it make any difference?
Sent from my SM-G900T using XDA Free mobile app
dzhowandai said:
It's a no go fir me with same result. Is your rom deodexed or does it make any difference?
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Not deodexed.
Not working for me either:
I just get:
" rm: can't remove '/system/app/xxxx': No such file or directory"
poncespr said:
Not working for me either:
I just get:
" rm: can't remove '/system/app/xxxx': No such file or directory"
Click to expand...
Click to collapse
To clarify does the PC recognize the device while in twrp and the tool runs successfully? But you get one or a few of the above error msg's or an extensive list of apps that it cannot remove? Are you on a completely stock rom that is not already debloated?
muniz_ri said:
To clarify does the PC recognize the device while in twrp and the tool runs successfully? But you get one or a few of the above error msg's or an extensive list of apps that it cannot remove? Are you on a completely stock rom that is not already debloated?
Click to expand...
Click to collapse
I went to far as to reinstall samsung drivers, google drivers.
I can check adb devices and see it is there.
Also, this is without any modification to your batch file.
poncespr said:
I went to far as to reinstall samsung drivers, google drivers.
I can check adb devices and see it is there.
Also, this is without any modification to your batch file.
Click to expand...
Click to collapse
Did the tool delete any apps? The extreme option includes over 90 apps. How many "could not find" msgs did you see? Also, which twrp version did you use?
muniz_ri said:
Did the tool delete any apps? The extreme option includes over 90 apps. How many "could not find" msgs did you see? Also, which twrp version did you use?
Click to expand...
Click to collapse
I chose extreme debloat and could not see any app succesfully removed.
I ended up using a debloater for the G900F via recovery, but it does not remove the Tmo bloat.
Anyway, I thank you for sharing your work.
poncespr said:
I chose extreme debloat and could not see any app succesfully removed.
I ended up using a debloater for the G900F via recovery, but it does not remove the Tmo bloat.
Anyway, I thank you for sharing your work.
Click to expand...
Click to collapse
The tool will not show successfully removed apps only failed apps.
Glad you found another method. I am just trying to understand why it works for me but not for you and another user so that I can either modify the tool or provide additional instructions.
muniz_ri said:
The tool will not show successfully removed apps only failed apps.
Glad you found another method. I am just trying to understand why it works for me but not for you and another user so that I can either modify the tool or provide additional instructions.
Click to expand...
Click to collapse
I tried quite a few times. Installed TWRP 2.8.6.0.. I re-downloaded drivers. I did a system restore on my windows 7 64 PC to make sure no other programs were conflicting.
Might give it a try again later on. I really want to get rid of Tmobiles useless app.
Edit:
Reinstalled drivers once more, used a different USB port, and selected minimal debloating (since I already removed most of the stuff I did not want)
and it finally worked. No more Tmobile branded bloat on my GS5.
Thank you again.
poncespr said:
I tried quite a few times. Installed TWRP 2.8.6.0.. I re-downloaded drivers. I did a system restore on my windows 7 64 PC to make sure no other programs were conflicting.
Might give it a try again later on. I really want to get rid of Tmobiles useless app.
Edit:
Reinstalled drivers once more, used a different USB port, and selected minimal debloating (since I already removed most of the stuff I did not want)
and it finally worked. No more Tmobile branded bloat on my GS5.
Thank you again.
Click to expand...
Click to collapse
I suspected that was the case so I have modified the tool to not run unless the device is recognized by the PC.
I can use "adb devices" to get adb to recognize my device when it's booted normally and usb debugging is checked (also checked always allow authorization), but when it booted to TWRP 2.8.6.0 and Mount system adb cannot recognize it ("adb devices" returns empty list) and thus the script cannot run (stops at the "waiting for device" part) . Any help?
Im having an issue with MTP not installing on Windows 7, tried many fixes and nothing is working. Really want to use this thing! Has anyone had this issue and know a possible fix?
Master619 said:
I can use "adb devices" to get adb to recognize my device when it's booted normally and usb debugging is checked (also checked always allow authorization), but when it booted to TWRP 2.8.6.0 and Mount system adb cannot recognize it ("adb devices" returns empty list) and thus the script cannot run (stops at the "waiting for device" part) . Any help?
Click to expand...
Click to collapse
Only thing that comes to mind are samsung drivers, try install or reinstall.
Edit: played around with it....connect your phone while in recovery to your PC and run Windows Update. It should give you the option of installing Android ADB Driver.
MortTheBeast said:
Im having an issue with MTP not installing on Windows 7, tried many fixes and nothing is working. Really want to use this thing! Has anyone had this issue and know a possible fix?
Click to expand...
Click to collapse
What I did is I disabled MTP in TWRP.
You disabled in TWRP and windows installed MTP? Because I tried that and windows won't even attempt to install MTP and phone doesn't get recognized.
MortTheBeast said:
You disabled in TWRP and windows installed MTP? Because I tried that and windows won't even attempt to install MTP and phone doesn't get recognized.
Click to expand...
Click to collapse
I tried Samsung drivers first, then used Google drivers. Still after a coulple of seconds I would always get an error 10 saying "This device could not start".
Tried downloading MTP drivers from microsoft somewhere, and that did not work either so finally decided to disable MTP on TWRP.
But, the ABD device was still recognized after disabling ATP.
poncespr said:
I tried Samsung drivers first, then used Google drivers. Still after a coulple of seconds I would always get an error 10 saying "This device could not start".
Tried downloading MTP drivers from microsoft somewhere, and that did not work either so finally decided to disable MTP on TWRP.
But, the ABD device was still recognized after disabling ATP.
Click to expand...
Click to collapse
I got nothing... here's crossing my fingers that someone is working on a root method, or else I will have to dump 5.1.1 and go with 5.0. :good:
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.