Related
I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..
Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot
Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*
Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?
mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus
i dont have twrp and cant go into download mode,only fastboot. need to send my phone back to t mobile. is there a way to root or install twrp with the problems i have?
Still_living714 said:
i dont have twrp and cant go into download mode,only fastboot. need to send my phone back to t mobile. is there a way to root or install twrp with the problems i have?
Click to expand...
Click to collapse
Does you phone boot into your OS? If not since downloadmode doesn't work you need to push these files via fastboot.
vel0city said:
Does you phone boot into your OS? If not since downloadmode doesn't work you need to push these files via fastboot.
Click to expand...
Click to collapse
when typing adb devices my phone shows up. when i type fastboot devices nothing shows up. i installed the drivers but i still cant get it to work?!
Still_living714 said:
when typing adb devices my phone shows up. when i type fastboot devices nothing shows up. i installed the drivers but i still cant get it to work?!
Click to expand...
Click to collapse
Do you have the fastboot installed or present on your computer?
vel0city said:
Do you have the fastboot installed or present on your computer?
Click to expand...
Click to collapse
yes i do but when typing command fastboot devices it doesn't show up
vel0city said:
Do you have the fastboot installed or present on your computer?
Click to expand...
Click to collapse
when i give commands on adb like reboot it works but not fastboot devices..am i missing something?
Still_living714 said:
when i give commands on adb like reboot it works but not fastboot devices..am i missing something?
Click to expand...
Click to collapse
It should work if you have the fastboot.exe file. Your folder should look like this image with the fastboot.exe and the files you want it to push:
https://hostr.co/file/LjdhzxB/Android folder.JPG
vel0city said:
It should work if you have the fastboot.exe file. Your folder should look like this image with the fastboot.exe and the files you want it to push:
https://hostr.co/file/LjdhzxB/Android folder.JPG
Click to expand...
Click to collapse
thanks brother, got everything sorted out.
Hi guys, i want to return to stock (i.e relock my bootloader and install stock oxygenOS) but i cant get my laptop to recognise my op3 whenever i type "fastboot devices" in cmd. Ive tried multiple programmes to install the correct drivers but it just doesnt seem to work.
Has anyone had similar problems or any solutions??
Im currently running windows 10 on my computer
Thanks
Do you have fastboot / adb tools installed and phone is in fastboot mode?
What does it say when typing fastboot devices?
Thanks for the reply, I type fastboot devices and nothing follows just another line to type a command. I'm pretty sure I have adb/fastboot tools installed, I used an installer which was linked on another thread
cl0g said:
Do you have fastboot / adb tools installed and phone is in fastboot mode?
What does it say when typing fastboot devices?
Click to expand...
Click to collapse
Do I need to be on a stock version of OOS in order to get my laptop to recognise my device in fastboot?
afrolong said:
Do I need to be on a stock version of OOS in order to get my laptop to recognise my device in fastboot?
Click to expand...
Click to collapse
No. Thats independent of OS
Are you in the fastboot/adb folder, where fastboot.exe is, when typing in cmd?
The mode where you should be is called "bootloader" on the phone.
cl0g said:
No. Thats independent of OS
Are you in the fastboot/adb folder, where fastboot.exe is, when typing in cmd?
The mode where you should be is called "bootloader" on the phone.
Click to expand...
Click to collapse
Yeah that may be the problem, would you mind directing me as to where I can find this fastboot/adb folder so that I can determine if I've even installed it properly haha
Well, if the cmd does not say something like "fastboot was not found", then that might not be the problem.
In which state is the phone, when trying fastboot?
Wrong drivers... Make sure you install the right one. Preferably follow the first few steps of the unbrick guide go get the right ones.. You are probably using the ones by Windows which do not work.
Puddi_Puddin said:
Wrong drivers... Make sure you install the right one. Preferably follow the first few steps of the unbrick guide go get the right ones.. You are probably using the ones by Windows which do not work.
Click to expand...
Click to collapse
Thanks for the help got it all sorted, had to select the correct drivers in Device Manager when i plugged the phone in in different states.
first it was handy, but now it is annoying... how can i disable it? i just wanna restart my phone if i press restart.. ( this isnt a thing from a rom..)
Thanks
(i'm a noob)
just type this command via fastboot "fastboot oem fb_mode_clear"
GuzXT said:
just type this command via fastboot "fastboot oem fb_mode_clear"
Click to expand...
Click to collapse
I'm also facing the same problem, and unfortunately above said command not worked for me.
Is any alternative solution ?
All you need to do is to flash a new logo.bin via adb, however if someone as an alternative solution it will be welcome.
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
check if you have the last fastboot version - platform-tools_r33.0.1
bengoodall.raw said:
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
Click to expand...
Click to collapse
Have you checked Device Manager to see if there's any unknown devices?
bengoodall.raw said:
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
Click to expand...
Click to collapse
Assuming you're using the latest adb & fastboot versions, what happens when you type "fastboot devices"? Does it show your device?
CZ Eddie said:
Assuming you're using the latest adb & fastboot versions, what happens when you type "fastboot devices"? Does it show your device?
Click to expand...
Click to collapse
Yep, shows my device
Sometimes it does but when I unplug then replug it shows adb bootloader interface
razercortex said:
Have you checked Device Manager to see if there's any unknown devices?
Click to expand...
Click to collapse
Yep I have the latest version
GabrielSousa said:
check if you have the last fastboot version - platform-tools_r33.0.1
Click to expand...
Click to collapse
bengoodall.raw said:
Yep, shows my device
Click to expand...
Click to collapse
Does it work with ANY fastboot commands at all?
Such as "fastboot reboot"?
bengoodall.raw said:
Yep I have the latest version
Click to expand...
Click to collapse
Try running those commands on another PC and let us know if it works.
CZ Eddie said:
Does it work with ANY fastboot commands at all?
Such as "fastboot reboot"?
Click to expand...
Click to collapse
Nope, that doesn't work either
Didn't work either 🫤
razercortex said:
Try running those commands on another PC and let us know if it works.
Click to expand...
Click to collapse
bengoodall.raw said:
gives me an error.
Click to expand...
Click to collapse
Screenshot of the error?
I had similar issues and found out it was because I was executing the commands in the bootloader instead of fastbootd mode. Try running them in fastbootd mode instead?
GloriamSemper said:
I had similar issues and found out it was because I was executing the commands in the bootloader instead of fastbootd mode. Try running them in fastbootd mode instead?
Click to expand...
Click to collapse
Ermm, you're SUPPOSED to run the commands in "bootloader" mode, not fastbootD mode.
I'm kind of curious how unlocking the bootloader worked but using other commands doesn't.
ekin_strops said:
Ermm, you're SUPPOSED to run the commands in "bootloader" mode, not fastbootD mode.
Click to expand...
Click to collapse
I know wierd, right? None the less, certain fastboot commands were only successful for my 2127 in fastbootd