Related
After I flashed or upgraded to the leak Android 2.3.4 from this guy http://forum.xda-developers.com/showthread.php?t=1232703 I tried to root my phone and I found one suggestion that calls Fugu Root, but it doesn't work for me. And then I try to figure out other way to do, And I have to thank you this guy to give me a kernel StocKH3 Kernel with Clockwork Recovery (http://forum.xda-developers.com/showthread.php?t=1242533) while I was looking for StockH3 kernel. And now are you ready to take a risk with me? If so, here we go....
1. open your Captivate phone that's running the leak Android 2.3.4 I897UCKH3, and go to android market then download superuser and install it on your phone, make sure that you have done this step.
2. Go to download StocKH3 kernel with Clockwork Recovery from this guy or download here to make sure you have the right one.
3. Do you have Odin3 1.81? if not, download here if you already have then skip this step
4. once you downloaded everything and installed superuser, go to download su-2.3.2-efgh-bin-signed.zip for gingerbread and here a link
5. Now turn off your phone and open odin3 1.81 as administrator, then connect your phone into usb cable while you'are connecting press the volume up and down together to get into download mode (you can do another way to get into download mode it doesn't matter).
6. make sure that your phone connected to computer, you will see the yellow on the box, when you connected.
7. now put put the boog_kh3_kernel3.tar into the PDA section, then click on Start button and wait until you finished and your phone will reboot.
8. go to upload file u-2.3.2-efgh-bin-signed.zip into your micro SDCard, or your internal storage. then reboot into recovery mode, the best way to do this is "adb reboot recovery" you will see Clockwork Recovery mode
9. Now, Go to select Install zip from sdcard >> toggle signature verification >>> Choose zip from sdcard.
10. then go to select one the one you've uploaded on your sdcard or wherever you uploaded to (u-2.3.2-efgh-bin-signed.zip). then select yes to install it.
after you finished install u-2.3.2-efgh-bin-signed.zip from the recovery mode, reboot your phone and you are now rooted.
have a good luck, it worked as well. sorry about my english also.
Thanks.
I cannot get Odin to 'recognize', no COM port displayed, my phone, which is in download mode; steps 5 & 6.
I can get Odin, and 'adb devices' to 'see' my phone when turned on, but not in DL mode.
mabovalu said:
Thanks.
I cannot get Odin to 'recognize', no COM port displayed, my phone, which is in download mode; steps 5 & 6.
I can get Odin, and 'adb devices' to 'see' my phone when turned on, but not in DL mode.
Click to expand...
Click to collapse
Does your computer have a driver of your phone? Have you done anything about Odin before, you can try another version of odin, it might work. But I don't know why you computer doesn't recognize your phone. If you never done anything about odin, I would suggest you to download Kies which is the updater firmware management for your phone, then you will have driver after you install this software.
december30 said:
Does your computer have a driver of your phone? Have you done anything about Odin before, you can try another version of odin, it might work. But I don't know why you computer doesn't recognize your phone. If you never done anything about odin, I would suggest you to download Kies which is the updater firmware management for your phone, then you will have driver after you install this software.
Click to expand...
Click to collapse
Yes, I have used Odin many times. ODIN and ADB 'see' (yellow COM port, adb devices = attached device) my phone when it is in normal mode, but as soon as I enter download mode (jig, 2-button) it loses the connection.
I suspect I am missing something, like maybe bootloaders, but not really sure.
I used UCKH3 Heimdall-One-Click [beta] to recover my semi-stoned phone. It (I897UCKH3/2.3.4) works pretty well: voice, SMS, 3G (DL is great: ~ 5 Mbps, UL just OK, previously ~ 2 Mbps, now ~ 500 Kbps, so maybe not the best modem for my provider?), but still un-rooted.
sounds too simple to be a solution but have you restarted your computer? I've had some odin issues like that and a simple reboot fixes the problem. The other fix that I've personally seen is to change your USB port. If you're connected in the front of the PC, move it to the back and see if that helps.
mabovalu said:
Yes, I have used Odin many times. ODIN and ADB 'see' (yellow COM port, adb devices = attached device) my phone when it is in normal mode, but as soon as I enter download mode (jig, 2-button) it loses the connection.
I suspect I am missing something, like maybe bootloaders, but not really sure.
I used UCKH3 Heimdall-One-Click [beta] to recover my semi-stoned phone. It (I897UCKH3/2.3.4) works pretty well: voice, SMS, 3G (DL is great: ~ 5 Mbps, UL just OK, previously ~ 2 Mbps, now ~ 500 Kbps, so maybe not the best modem for my provider?), but still un-rooted.
Click to expand...
Click to collapse
I used this method ( http://forum.xda-developers.com/showthread.php?t=1232703 ) to upgrade to the leak I897UCKH3. I don't think that is the problem about boot loader
I think the standard drivers from Samsung that are used for Odin and the Heimdall drivers conflict. Try removing the Heimdall drivers if you want to use Odin.
gibson3659 said:
I think the standard drivers from Samsung that are used for Odin and the Heimdall drivers conflict. Try removing the Heimdall drivers if you want to use Odin.
Click to expand...
Click to collapse
^ What he said. If you are on windows Heimdall drivers will conflict with Odin
Thank you december30, nyydynasty, gibson3659, prbassplayer .
I am rooted.
I de-installed the Heimdall Drivers per the directions (below), re-booted, de-installed the Samsung USB Drivers, re-booted, re-installed the Samsung usb_drivers_GalaxyS_x64 (different drivers than I had used previously), re-booted.
Then I could 'see' my Captivate, when in Download Mode, with both ADB and ODIN.
I guess my next question is, which ROM should I use? (I only ended up with this 'stock' ROM as a result of trying to recover my phone from a persistent soft-brick situation.)
I found these Heimdall Driver un-install instructions:
Driver Uninstallation Instructions:
1. Put your Samsung Galaxy S into download mode by holding Volume Down + Home + Power.
2. Plug your phone into your PC.
3. Open up Device Manager on your PC (Control Panel -> System -> Device Manager).
4. Under "Libusb (WinUSB) devices" right click on "Samsung USB Composite Device" and chose Properties.
5. Go to the Driver tab and select Update Driver.
6. Chose to browse your computer for the driver.
7. Chose to pick from a list of devices drivers on your computer.
8. Pick the original Samsung Composite driver, press next and then follow the prompts.
9. Done
Well did you press thanks button yet. By the way congratulate on this point
Sent from my SAMSUNG-SGH-I897 using XDA App
december30 said:
Well did you press thanks button yet. By the way congratulate on this point
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes during my Thanks post above, the THANKS buttons no longer appear, but I did miss gibson3659 originally and corrected that oversight. Also rated the thread 5 stars.
Thanks again.
Any recommendations on a ROM?
In my opinion i would stuck in this rom. Until the official one cone out.
Sent from my SAMSUNG-SGH-I897 using XDA App
mabovalu said:
Thanks.
I cannot get Odin to 'recognize', no COM port displayed, my phone, which is in download mode; steps 5 & 6.
I can get Odin, and 'adb devices' to 'see' my phone when turned on, but not in DL mode.
Click to expand...
Click to collapse
Sounds stupid, but this happens to me when I plug my phone into the front USB ports on my PC. Plugging it into the back (directly to the pc) works.
Thanks for this...I am on (now rooted!) stock kh3 and find I prefer this method rather than the whole kernel swap! I will be sure to hit the THANKS button when I can get to a pc!
Sent from my SAMSUNG-SGH-I897 using XDA App
It was easy right? You can do like this with other devices just change kernel or recovery mode
Sent from my SAMSUNG-SGH-I897 using XDA App
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Are you sure the ADB driver was installed for the device? Try reading through this:
http://trevorsullivan.net/2012/07/03/forcibly-installing-the-android-usb-driver-in-windows-7/
couple things to try
As silly as it sounds with modern computers, but make sure you are plugging into the back of your PC rather than a a usb port on the front.
Also, even if fastboot devices comes back blank, try typing the fastboot oem unlock anyways. 9/10 times my computer comes up empty when I query for the device but then am able to flash recovery, unlock etc with no prob
Blueback22 said:
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Click to expand...
Click to collapse
Blueback22 said:
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Click to expand...
Click to collapse
As mentioned in the above post... I've had a handful of devices that won't return a fastboot id, however they except commands just fine.
dannymac77 said:
As silly as it sounds with modern computers, but make sure you are plugging into the back of your PC rather than a a usb port on the front.
Also, even if fastboot devices comes back blank, try typing the fastboot oem unlock anyways. 9/10 times my computer comes up empty when I query for the device but then am able to flash recovery, unlock etc with no prob
Click to expand...
Click to collapse
Thank you to everyone for your help.
First thing I did was force the driver. It was showing up under mobile devices as Nexus 10, but I pushed the Google USB drivers anyway
This didnt help show the device ID when using fastboot devices, but I followed the above instructions anyway and it unlocked.
It's now at the X boot screen and taking a while. I hope I'm not in a boot loop. I dont know why I would be as all I did was unlock the bootloader and going to give it another minute before I reboot.
OK. It did boot loop. To fix this, follow this video to do a factory reset:
http://youtu.be/T1Se7Hr9Cww
I had the same issue as you with my Galaxy Nexus recently, and force installing the USB drivers does the trick every time. I think it has to do with Windows seeing the device as a media device (external MP3 player, or similar), rather than as an ADB interface. That's why you have to tell it to forcefully install the ADB driver, so it can talk ADB, rather than treating it as a media device.
Glad you got it working. Cheers
OKay I cannot for the life of me get this to work at all. I have never had a problem unlocking an HTC device, but anytime it comes to a samsung it doesn't work. I've tried the steps listed here, I've watched a video guide on unlocking from another post, I have the SDK updated, it sees the device as Android Bootloader Interface in Device Manager, I've rebooted straight to bootloader on the tablet, I've tried two different USB ports in the rear, fastboot will not read this device or give it commands at all. No reboot, no unlock, nothing. I'm seriously starting to freak out here. Been at this for 2 and a half hours now.
Varekai said:
OKay I cannot for the life of me get this to work at all. I have never had a problem unlocking an HTC device, but anytime it comes to a samsung it doesn't work. I've tried the steps listed here, I've watched a video guide on unlocking from another post, I have the SDK updated, it sees the device as Android Bootloader Interface in Device Manager, I've rebooted straight to bootloader on the tablet, I've tried two different USB ports in the rear, fastboot will not read this device or give it commands at all. No reboot, no unlock, nothing. I'm seriously starting to freak out here. Been at this for 2 and a half hours now.
Click to expand...
Click to collapse
I'm sure you did this right, but let's walk through the steps again anyway...
1) turn on tab and plug into USB do windows can install drivers
2) force ADB drivers according to link at the beginning of this thread
( it wouldn't hurt to reboot windows between steps 2 and 3)
3) shutdown tab and lead into boot loader
- do this by holding down all buttons while tab is off. When it vibrates, let go of power button until boot loader comes up
4) make sure USB is connected to back of PC and to tab
5) open terminal by going into start menu and typing CMD
6) change directory to location of fastboot
7)type fastboot devices
8) if ID comes up, you're home free. If nothing comes up, try step 9 anyway
9) type fastboot OEM unlock
10) follow instructions on tab screen
Let us know if any step failed.
Sent from my Galaxy Nexus using Tapatalk 2
pcgeek86 said:
I had the same issue as you with my Galaxy Nexus recently, and force installing the USB drivers does the trick every time. I think it has to do with Windows seeing the device as a media device (external MP3 player, or similar), rather than as an ADB interface. That's why you have to tell it to forcefully install the ADB driver, so it can talk ADB, rather than treating it as a media device.
Glad you got it working. Cheers
Click to expand...
Click to collapse
I had to do this with the Nexus 10, as well, after messing with it for a while.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
I'm sure you did this right, but let's walk through the steps again anyway...
1) turn on tab and plug into USB do windows can install drivers
2) force ADB drivers according to link at the beginning of this thread
( it wouldn't hurt to reboot windows between steps 2 and 3)
3) shutdown tab and lead into boot loader
- do this by holding down all buttons while tab is off. When it vibrates, let go of power button until boot loader comes up
4) make sure USB is connected to back of PC and to tab
5) open terminal by going into start menu and typing CMD
6) change directory to location of fastboot
7)type fastboot devices
8) if ID comes up, you're home free. If nothing comes up, try step 9 anyway
9) type fastboot OEM unlock
10) follow instructions on tab screen
Let us know if any step failed.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've done every one of those steps to the T. Rebooted multiple times, tried different USB cables, tried every port in the back, plus both up front just for extra measure. USB port works on the tab because I'm transferring media files to it right now, it recognizes as an ADB device, drivers were also force installed from SDK Toolkit, but it won't take commands, not reboot, not ID, and certainly not unlock. The only other thing I can try is using my fiance's laptop and see if for some reason it's just an issue with my PC, because if not then it's an issue with the tablet, for whatever reason, and not being able to root this is not an option for me.
Varekai said:
I've done every one of those steps to the T. Rebooted multiple times, tried different USB cables, tried every port in the back, plus both up front just for extra measure. USB port works on the tab because I'm transferring media files to it right now, it recognizes as an ADB device, drivers were also force installed from SDK Toolkit, but it won't take commands, not reboot, not ID, and certainly not unlock. The only other thing I can try is using my fiance's laptop and see if for some reason it's just an issue with my PC, because if not then it's an issue with the tablet, for whatever reason, and not being able to root this is not an option for me.
Click to expand...
Click to collapse
If you'd like, I can remote into your computer and walk through it with you to see if I can help in anyway. Let me know.
I will PM you my phone number so you can text me if you want to try this.
I am presently having the EXACT same problem. I have a Mac mini (mountain lion) and Windows 8 (vmware). Under osx I follow all the steps and similarly I can't get fastboot to give me the ID or recognize the unlock command. In Windows it recognizes the tablet when it's booted up normally. But with fastboot in the cmd prompt I get the exact same results as in osx.
P.s. I also had the same issue with my Samsung galaxy 3. Wound up having to root it at a friend's house.
Sent from my SPH-L710 using xda premium
Blueback was able to solve all my woes, thanks!
verusevo said:
I am presently having the EXACT same problem. I have a Mac mini (mountain lion) and Windows 8 (vmware). Under osx I follow all the steps and similarly I can't get fastboot to give me the ID or recognize the unlock command. In Windows it recognizes the tablet when it's booted up normally. But with fastboot in the cmd prompt I get the exact same results as in osx.
P.s. I also had the same issue with my Samsung galaxy 3. Wound up having to root it at a friend's house.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I just fixed this for the other guy. What is the file path of your fastboot.exe file?
Its in user/downloads/root. on both my osx/windows drives.
Sent from my SPH-L710 using xda premium
verusevo said:
Its in user/downloads/root. on both my osx/windows drives.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
In your windows VM, is it inside of the Android SDK/Platform-Tools/ folder?
Sent from my Galaxy Nexus using Tapatalk 2
No its on the virtual C: drive in the downloads/root folder. Root being the folder I created to extract all relevant unlocking rooting files to
Sent from my Nexus 10 using XDA Premium HD app
verusevo said:
No its on the virtual C: drive in the downloads/root folder. Root being the folder I created to extract all relevant unlocking rooting files to
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Download and install the Android SDK. Use the fastboot tool that is inside of the Android SDK/platform-tools/ folder. I can almost guarantee success.
My win 7 didn't recognize my n10 fastboot too, so I went into device manager and updated the android 1.0 or something by selecting the main SDK folder in the android SDK as an update source
Same for adb
Sent from my Nexus 10 using XDA Premium HD app
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?
I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.
Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung
I cant boot my one plus two. I have nothing installed (OS) when i try to boot it up only the boot logo shows up (because theres no OS). So the thing is my one plus two also doesnt show up on my PC when in adb mode or fastboot. I already tried the Hardbrick mode and the softbrick but nothing seems to work. what can i do that my Phone shows up on my PC.
felix.egger33 said:
I cant boot my one plus two. I have nothing installed (OS) when i try to boot it up only the boot logo shows up (because theres no OS). So the thing is my one plus two also doesnt show up on my PC when in adb mode or fastboot. I already tried the Hardbrick mode and the softbrick but nothing seems to work. what can i do that my Phone shows up on my PC.
Click to expand...
Click to collapse
Did u try booting into recovery?
Also do u have the proper and and fastboot drivers installed?
I had problem the past few days that my bootloader locked for no good reason so I did second method from here:
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
And it worked.
Note u need to get the drivers installed properly before proceeding.
Sent from my ONE A2005 using Tapatalk
i can boot in recovery. i saw this method too but my phone doesnt show up as unknown device or qualcomm in the device manager. My windows has driver signature off. i could fix the problem but i cant make my device show up in device manager.
felix.egger33 said:
i can boot in recovery. i saw this method too but my phone doesnt show up as unknown device or qualcomm in the device manager. My windows has driver signature off. i could fix the problem but i cant make my device show up in device manager.
Click to expand...
Click to collapse
So u powered off device then hold the volume + for 10-15 seconds while connecting to PC.
This boots the phone in edl mode but the screen remains blank.
It should show in device manager as unknown device.
If the drivers are installed automatically, it will be under Ports (COM & LPT).
Sent from my ONE A2005 using Tapatalk
Yep i did that but nothing showed up or changed thats my main problem.
felix.egger33 said:
Yep i did that but nothing showed up or changed thats my main problem.
Click to expand...
Click to collapse
Well sadly it's the only way to Unbrick the phone.
Try on other pc, see if shown up.
Sent from my ONE A2005 using Tapatalk
Try procedure on different pc
Sent from my ONE A2005 using Tapatalk
Hello. In general, I have a problem connecting the phone to the computer, the text shown in the topic and unknown device, the phone does not show the option only charging and in general, met someone and handled it? help
Tejoxdd said:
Hello. In general, I have a problem connecting the phone to the computer, the text shown in the topic and unknown device, the phone does not show the option only charging and in general, met someone and handled it? help
Click to expand...
Click to collapse
Hey,
1. What version of Windows are you using?
2. Did you try connecting to different devices?
3. Did you try changing the USB Cable? Are you using the one provided with the phone?
4. Did you install the correct drivers?
5. In your dialer, type in *#*#2846579#*#* then select in Background>USB HiSuite, to see if anything happens.
1. Windows 7
2. Yes, on the same thing.
3. Yes, I tried 2 others
4. Previously everything was working properly
5. Nothing.. :c
Tejoxdd said:
1. Windows 7
2. Yes, on the same thing.
3. Yes, I tried 2 others
4. Previously everything was working properly
5. Nothing.. :c
Click to expand...
Click to collapse
Also, are you using a stock or custom ROM? What version?
Try let Windows install the generic drivers and then see if it helps you to fix the issue.
a) Open Device Manager by clicking the Start button, then Device Manager in the search box.*
b) If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
c) Look for the device under USB [Universal Serial bus] host controller, right click on it and select Uninstall.
d) Reboot the computer.
e) On reboot, Windows 7 should re-install the drivers automatically.
Stock B610
Still nothing..
Same thing happened to me once, but on custom ROM
You may try my solution and report if it works
For me the solution was an option in "developer options" called "select USB configuration" I had to manually select MTP..
IDK if the this option present in the stock ROM.
There is an option, but it also does not help ..
The other roms also do not work.
Tejoxdd said:
There is an option, but it also does not help ..
The other roms also do not work.
Click to expand...
Click to collapse
Bump.
Could it be that you dropped your phone and the port got some damage? Does you phone charge properly?
Also, if you install de ADB drivers and HiSuite, does the PC recognize the phone?
It puzzles me that you tried different cables, different PCs and different ROMs and the issue still persists so perhaps you have some hardware issues or incorrect drivers.
yes, it fell to me. yes, it loads properly.
does not recognize anymore.
Tejoxdd said:
yes, it fell to me. yes, it loads properly.
does not recognize anymore.
Click to expand...
Click to collapse
Sorry for not replying sooner.
Have you tried to boot into recovery via ADB?
adb reboot recovery
Does not work