Hey there guys, so as the title suggests, i'm having a bootloop problem on my m30s sm-307f, i can't access recovery mode, and i'm unable to start the flashing process because i can't even install the usb driver, i've tried several drivers, using several cables, on several systems (windows 7 / windows 10 / windows 11), and i always get that infamous yellow triangle on the SAMSUNG Mobile USB CDC Composite Device in the Universal Serial Bus Controllers section in the device manager, the phone was operating normally one day, and the next day when i try to power it on, i get this, i'm absolutely certain that i did nothing to the phone, not even an update, and it most definitely didn't fall to the ground, please respond, i have really important data there, and it would devastating to lose it, and thanks a lot.
Can you access Download Mode?
UniX1803 said:
Can you access Download Mode?
Click to expand...
Click to collapse
Yes i can.
Ok. Can Odin detect your phone?
UniX1803 said:
Ok. Can Odin detect your phone?
Click to expand...
Click to collapse
No, unfortunately it can't, which is to be expected since windows itself can't detect it.
Is your USB Cable connected when you try to boot to Recovery Mode? when the screen goes black, press Vol+ & Power until Samsung Logo appears, Release Power, hold Vol+ until Recovery Mode appears.
UniX1803 said:
Is your USB Cable connected when you try to boot to Recovery Mode? when the screen goes black, press Vol+ & Power until Samsung Logo appears, Release Power, hold Vol+ until Recovery Mode appears.
Click to expand...
Click to collapse
I do know how to get to download mode, i did of course try, and although it does appear on the phone that it's working, the computer doesn't detect the latter as i explained, and as such, odin doesn't detect it as well.
I was talking about Recovery Mode.
UniX1803 said:
I was talking about Recovery Mode.
Click to expand...
Click to collapse
Sorry, i didn't notice that, i'm unable to access recovery mode either because the phone just keeps rebooting.
I had the same problem but following the mentioned steps did worked for me. It's that short moment when the screen turns black, where you have to push that buttons. USB Cable needs to be plugged in!
If this solution is not working for you, try searching the web. I found more than one potential solution. Good luck.
UniX1803 said:
I had the same problem but following the mentioned steps did worked for me. It's that short moment when the screen turns black, where you have to push that buttons. USB Cable needs to be plugged in!
If this solution is not working for you, try searching the web. I found more than one potential solution. Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help, i really appreciate it, some people are saying that it's a motherboard problem, what do you think ?
Could be, but i'm not sure. I would try to find a software solution, until you are sure it's not to get fixed on this way.
UniX1803 said:
Could be, but i'm not sure. I would try to find a software solution, until you are sure it's not to get fixed on this way.
Click to expand...
Click to collapse
You're right, again, thanks a lot for your help.
Try uninstalling the device in device manager and try those before plugging it in again.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
treety said:
Try uninstalling the device in device manager and try those before plugging it in again.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Click to expand...
Click to collapse
I've already tried them, they didn't work as intended unfortunately, thanks for the reply though.
Were you ever able to solve this? Is it a hardware issue? I think that may be the correct determination. I'm going to take this one apart and see if I find anything that would corroborate.
stoag said:
Were you ever able to solve this? Is it a hardware issue? I think that may be the correct determination. I'm going to take this one apart and see if I find anything that would corroborate.
Click to expand...
Click to collapse
Unfortunately, i wasn't able to, but i think it's most likely hardware related.
Related
So recently flashed CM 10.1 FUSION. Nexus battery drains, I end up turning it back on while on the charger. Then, it shuts down on me.. so I let it charge overnight. Turned it back, and I get stuck at a boot screen (FUSION). I attempt to turn my device off, and it just restarts. I have to turn it off from the bootloader (P+Up+Down).. I tried using the toolkit, but I freeze in the bootloader when I plug my device in.
Help.
Running 4.2.1
Yes I'm aware of the common problems, none of the solutions seem to be working.
Rovon said:
Yes I'm aware of the common problems, none of the solutions seem to be working.
Click to expand...
Click to collapse
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
bftb0 said:
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
Click to expand...
Click to collapse
I tried watching a majority of the "unbrick nexus 7" vids on youtube. They didn't get me too far
Holding power for a long time
Restarting bootloader
Root toolkit
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Rovon said:
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Click to expand...
Click to collapse
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
bftb0 said:
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
Click to expand...
Click to collapse
Sorry, I meant its frozen on the fastboot screen...
I can scroll through the fastboot, but that's it. None of the commands work, unless I hit power off. The toolkit tells me "fastboot device not found", when I try the Flash Stock + Unroot button. There is no device ID I can see on the toolkit. Also, drivers fail to install when I plug it in to my computer.
Rovon said:
None of the commands work, unless I hit power off.
Click to expand...
Click to collapse
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
bftb0 said:
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
Click to expand...
Click to collapse
I should've been more specific. When I say none of the commands work, I mean they don't do what they're supposed to. So if I hit "recovery mode" it will not go into recovery mode, it just stays stuck at the Google logo when it restarts.
As for device manager, when plugged in to the computer with Fastboot, I do get "android" under other devices. However, when I'm booting the device up regularly, the computer attempts to install drivers and fails. I do get "MTP USB Device" under portable devices. I have an unknown device under portable as well.
All 3 seem to have error symbols next to them.
Rovon said:
All 3 seem to have error symbols next to them.
Click to expand...
Click to collapse
Well, if you can't communicate with the device successfully, there's no hope of doing something correctly from the PC. So, try a few simple things on that angle of the problem first. The problem you are seeing could come from any number of places:
- damaged USB (or other) hardware on tablet
- bad / cheap USB cable
- damaged USB port on PC
- driver install issues
The symptoms you describe for fastboot sound a bit like the custom recovery got damaged or erased, although more severe (and not fixable) problems are also a possibility.
Since you previously installed a ROM, I would take it to mean that at one time you had at least one driver working (fastboot at a minimum), and possibly also ADB mode (in the OS and/or in the recovery). That's why I put "driver install issues" last in the short list above. If you never touched any of the drivers after you did your initial ROM installs, I would not expect driver issues ... but I don't know what you might have tried subsequently with the toolkit (which does fool around with drivers).
Are you using the OEM cable? Some aftermarket/charger cables have a short mini-USB connector, and one dollar cables off of eBay can be poorly constructed (bad shielding or impedance control, so they cause data errors at high speeds).
If you have an 2nd cable, I would try to see if you experience a different set of symptoms with that; same goes for trying a different USB port on your PC.
If you see errors in the Device Manager associated with fastboot I certainly would not be attempting any operation from the PC until you get that resolved. Note there is a huge difference between "unknown device" and a device showing errors - the latter suggests that the OS is aware of a driver which is supposed to be loaded when the tablet shows up on the USB bus, but then some malfunction occurs. That malfunction could either be hardware or an inappropriate driver.
Drivers
http://www.asus.com/Tablet_Mobile/Nexus_7#support_Download
http://forum.xda-developers.com/showthread.php?t=1426502
Note that you should be able to use the Asus driver for every mode of your Nexus 7 (except MTP and PTP, which are handled by Windows generic class drivers), including your custom recovery by doing the following:
A) Download the Asus Driver and unzip it someplace.
B) make a backup copy of the "android_winusb.inf" file (for instance "android_winusb.inf.backup")
C) Open up the "android_winusb.inf" file with the Notepad program (Note: not Wordpad!)
D) Find the ";Google Nexus 7" stanza in the [Google.NTx86] section and add this line:
%CustRecoveryADBAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
E) Add the same line (step D above) in the [Google.NTamd64] section
F) At the very bottom of the file in the [Strings] section, add the line
CustRecoveryADBAdbInterface = "Nexus 7 Custom Recovery ADB Interface"
G) Save the file and then proceed to do a manual de-installation of the drivers for fastboot and ADB.
H) Disconnect from the internet and then re-install the Asus driver for fastboot and ADB using the "Choose Location" method.
Don't know if that will work, but it's something to try; the problem you are having might lie outside the scope of what all of the above deals with
good luck
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Rovon said:
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Click to expand...
Click to collapse
Please describe what you found out and what DID work for you. Even if it was just a simple mis-understanding. It might help others in the future.
Probably you should also alter the title of your thread to be something much more descriptive - and add the keyword "[SOLVED]" to the title as well.
When trying to download an OTA for my LG-D800, I flashed TWRP but then flashed Stock Recovery, but when I tried to update it, it powered down then stayed on the LG boot up screen, and stays there, there is no white text in the corner, no download mode, and of course no recovery. Also now my laptop can't see my phone. Please help me. Thank you!
bryantx24 said:
When trying to download an OTA for my LG-D800, I flashed TWRP but then flashed Stock Recovery, but when I tried to update it, it powered down then stayed on the LG boot up screen, and stays there, there is no white text in the corner, no download mode, and of course no recovery. Also now my laptop can't see my phone. Please help me. Thank you!
Click to expand...
Click to collapse
This thread should Help you
http://forum.xda-developers.com/showthread.php?t=2582142
with this procedure i revived my G2 after nearly he same problem
Skolotaie said:
This thread should Help you
http://forum.xda-developers.com/showthread.php?t=2582142
with this procedure i revived my G2 after nearly he same problem
Click to expand...
Click to collapse
I tried this already, but my computer does not show the phone at all.
bryantx24 said:
I tried this already, but my computer does not show the phone at all.
Click to expand...
Click to collapse
Do you tried different Usb Ports ?
If you have the Chance you should try it on a other Pc
+ I had to Use my Usb 2.0 Ports the Usb 3 ports never wanted to Recognize the phone
Its a Tricky Process and took me also a while but hey its worth it right
Skolotaie said:
Do you tried different Usb Ports ?
If you have the Chance you should try it on a other Pc
+ I had to Use my Usb 2.0 Ports the Usb 3 ports never wanted to Recognize the phone
Its a Tricky Process and took me also a while but hey its worth it right
Click to expand...
Click to collapse
I tried and I don't have another computer
bryantx24 said:
I tried and I don't have another computer
Click to expand...
Click to collapse
Aw Damn :c
Wish i could Help more but lets wait
I bet somone here can help you dont give up the Hope
Maybe the only thing wich keeps the Phone from beeing recognized is a Driver Problem
Skolotaie said:
Aw Damn :c
Wish i could Help more but lets wait
I bet somone here can help you dont give up the Hope
Maybe the only thing wich keeps the Phone from beeing recognized is a Driver Problem
Click to expand...
Click to collapse
I wonder why it won't show up at all? I am going to reinstall the drivers.
bryantx24 said:
I wonder why it won't show up at all? I am going to reinstall the drivers.
Click to expand...
Click to collapse
UPDATE:Nothing has worked yet.
I literally had to try 2-3 usb CORDS to get my cpu to see my lg g2
Danokan said:
I literally had to try 2-3 usb CORDS to get my cpu to see my lg g2
Click to expand...
Click to collapse
I used a couple none of the worked.
I was able to connect the device to the phone, but no ADB and its called: Unknown USB Device (Device Descriptor Failed), but it does not show up in Ubuntu.
bryantx24 said:
I was able to connect the device to the phone, but no ADB and its called: Unknown USB Device (Device Descriptor Failed), but it does not show up in Ubuntu.
Click to expand...
Click to collapse
I could never get my cpu to recognize my phone while in recovery.
I used two different computers and couldn't get anything.
When the ROM is working.. I can.
Are you positive you can't get it into download mode?
Try this.
Power off phone completely.
Attach usb cord WHILE holding the VOL up button.
See if that gets it into download mode.
If you can... then you can do the KDZ or TOT "unbrick back to stock" method.
I tried both of those.. but none worked for me.
This one worked for me though:
http://forum.xda-developers.com/showthread.php?t=2448960
Danokan said:
I could never get my cpu to recognize my phone while in recovery.
I used two different computers and couldn't get anything.
When the ROM is working.. I can.
Are you positive you can't get it into download mode?
Try this.
Power off phone completely.
Attach usb cord WHILE holding the VOL up button.
See if that gets it into download mode.
If you can... then you can do the KDZ or TOT "unbrick back to stock" method.
I tried both of those.. but none worked for me.
This one worked for me though:
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
No, I can't get into download mode, I have no recovery and I have an ATT LG G2
Hey guys im trying to back to a fresh stock rom. (VS980)I downloaded all the necessary files, drivers, lgflash tools etc etc. however my computer still cannot recognize my phone. under ports there is not an ANDROID port for my phone. (since we need to change it to COM41)
any ideas or suggestions?
daimonmustdie said:
Hey guys im trying to back to a fresh stock rom. (VS980)I downloaded all the necessary files, drivers, lgflash tools etc etc. however my computer still cannot recognize my phone. under ports there is not an ANDROID port for my phone. (since we need to change it to COM41)
any ideas or suggestions?
Click to expand...
Click to collapse
what comp/ operating system are you on?
plug directly into the computer, not a hub.
Gabriel51 said:
what comp/ operating system are you on?
plug directly into the computer, not a hub.
Click to expand...
Click to collapse
its a pc, wins7 64 bit
daimonmustdie said:
its a pc, wins7 64 bit
Click to expand...
Click to collapse
Do you find it in the device manager?
Gabriel51 said:
Do you find it in the device manager?
Click to expand...
Click to collapse
it shows up when its showing the LG logo, but when its on download mode, its blank.
daimonmustdie said:
it shows up when its showing the LG logo, but when its on download mode, its blank.
Click to expand...
Click to collapse
When it's in the download mode it may show up in a different location in the device manager and be listed only as "android".
Do you hear any sound from the computer when you plug it in when in download mode?
What does your download screen look like?
Once these questions are answered, there may be a solution. Hopefully a CDMA device won't be different
Gabriel51 said:
When it's in the download mode it may show up in a different location in the device manager and be listed only as "android".
Do you hear any sound from the computer when you plug it in when in download mode?
What does your download screen look like?
Once these questions are answered, there may be a solution. Hopefully a CDMA device won't be different
Click to expand...
Click to collapse
Hi i just got my phone back from a cell phone repair shop, they had no luck either.
to answers your questions:
i hear no sound from the computer when i plug it in to turn on download mode.
my download screen says Firmware Update on top, "do not unplug the USB connecton...." 0%. in the bottom it says b17 and ROOTED in red.
daimonmustdie said:
Hi i just got my phone back from a cell phone repair shop, they had no luck either.
to answers your questions:
i hear no sound from the computer when i plug it in to turn on download mode.
my download screen says Firmware Update on top, "do not unplug the USB connecton...." 0%. in the bottom it says b17 and ROOTED in red.
Click to expand...
Click to collapse
there are two possibilities.. First, your phone is already hard bricked.. second is, your battery is absolutely dead with no power left...
Well, Have you tried to check the battery itself?
Rei Zazie said:
there are two possibilities.. First, your phone is already hard bricked.. second is, your battery is absolutely dead with no power left...
Well, Have you tried to check the battery itself?
Click to expand...
Click to collapse
hmmmm hardbricked? i can get into download mode and stock recovery. I messed around with adb sideload last night trying to flash a custom recovery but it kept saying installation aborted on the phone. i even tried adb push but it keeps saying error:closed in the cmd prompt.
how can i check the battery? its non removeable.
thanks for helping, any ideas is appreciated!
daimonmustdie said:
hmmmm hardbricked? i can get into download mode and stock recovery. I messed around with adb sideload last night trying to flash a custom recovery but it kept saying installation aborted on the phone. i even tried adb push but it keeps saying error:closed in the cmd prompt.
how can i check the battery? its non removeable.
thanks for helping, any ideas is appreciated!
Click to expand...
Click to collapse
ok, so have you tried it using different PC or laptop?
(last option if nothing else to try) if you want to check the battery :
DIY remove the case ( there are several tutorials in youtube, but of course, do it with your own risk)
daimonmustdie said:
Hi i just got my phone back from a cell phone repair shop, they had no luck either.
to answers your questions:
i hear no sound from the computer when i plug it in to turn on download mode.
my download screen says Firmware Update on top, "do not unplug the USB connecton...." 0%. in the bottom it says b17 and ROOTED in red.
Click to expand...
Click to collapse
It's not hard bricked/
Getting into download mode proves this.
You must get your computer to recognize your device in order to communicate with it. So I would not consider anything else until that is accomplished. PERIOD!
1. Are you using a USB 2.0 port? usb 3.0 will not work a lot of the time. (Important)
2. Have you tried another usb cable?
3. I think we discussed the drivers, I have them if needed
What operating system are you using?
If nothing here helps we can we can use "TeamViewer 9" which will give me control of your computer to help resolve this issue...
Gabriel51 said:
It's not hard bricked/
Getting into download mode proves this.
You must get your computer to recognize your device in order to communicate with it. So I would not consider anything else until that is accomplished. PERIOD!
1. Are you using a USB 2.0 port? usb 3.0 will not work a lot of the time. (Important)
2. Have you tried another usb cable?
3. I think we discussed the drivers, I have them if needed
What operating system are you using?
If nothing here helps we can we can use "TeamViewer 9" which will give me control of your computer to help resolve this issue...
Click to expand...
Click to collapse
when i turn on my phone, and the LG logo is on the screen, my computer recognizes the phone, it will say LGE androidnet...but when i go to download mode the computer will not recognize. its weird
1. 2.0 ports
2. ive been trying the original LG cable and a motorola cable. no success
3. as for drivers. installed as of now are the LG verizon united driver 2.14.1 and LG united mobile driver 3.12.3.0
4. win 7 64 bit
daimonmustdie said:
when i turn on my phone, and the LG logo is on the screen, my computer recognizes the phone, it will say LGE androidnet...but when i go to download mode the computer will not recognize. its weird
1. 2.0 ports
2. ive been trying the original LG cable and a motorola cable. no success
3. as for drivers. installed as of now are the LG verizon united driver 2.14.1 and LG united mobile driver 3.12.3.0
4. win 7 64 bit
Click to expand...
Click to collapse
That is weird
will it go into recovery?
Gabriel51 said:
That is weird
will it go into recovery?
Click to expand...
Click to collapse
stock recovery.
daimonmustdie said:
stock recovery.
Click to expand...
Click to collapse
Will it boot into recovery?
Gabriel51 said:
Will it boot into recovery?
Click to expand...
Click to collapse
yes it will
daimonmustdie said:
yes it will
Click to expand...
Click to collapse
can you do a factory reset from there? I sold my g2 so i can't check for myself
Gabriel51 said:
can you do a factory reset from there? I sold my g2 so i can't check for myself
Click to expand...
Click to collapse
yes i can
daimonmustdie said:
yes i can
Click to expand...
Click to collapse
what happens when you do a factory reset?
Gabriel51 said:
what happens when you do a factory reset?
Click to expand...
Click to collapse
nothing, it reboots and the LG logo appears and thats it..no O.S.
Hi there, the title explains most of it, I'm trying to control the phone with k.janku1's control tool, here : http://forum.xda-developers.com/showthread.php?t=2786395
The phone has USB debugging enabled, is in MTP mode and ADB will find the device fine when I'm in recovery but when I reboot the device ADB won't find the device when it's turned on. I don't know if I'm being stupid or not! I also have all the drivers installed etc
Prydar said:
Hi there, the title explains most of it, I'm trying to control the phone with k.janku1's control tool, here : http://forum.xda-developers.com/showthread.php?t=2786395
The phone has USB debugging enabled, is in MTP mode and ADB will find the device fine when I'm in recovery but when I reboot the device ADB won't find the device when it's turned on. I don't know if I'm being stupid or not! I also have all the drivers installed etc
Click to expand...
Click to collapse
Never used that tool (I did not even heard of it before) but I do rely and suggested to all of my mates to test Chrome extension Vysor, so you could give it a try.
anawim said:
Never used that tool (I did not even heard of it before) but I do rely and suggested to all of my mates to test Chrome extension Vysor, so you could give it a try.
Click to expand...
Click to collapse
I can't get Vysor to detect the device, I have USB debudding enabled but I'm not able to use the device at all as the digitizer is broken
anawim said:
Never used that tool (I did not even heard of it before) but I do rely and suggested to all of my mates to test Chrome extension Vysor, so you could give it a try.
Click to expand...
Click to collapse
Ah, I've just read Vysor's troubleshooting guide, it says to be on PTP but I'm on MTP
Is there a known way to change to PTP from MTP with a broken digitizer? I can still see everything on the screen as it's just the digitizer thats broken so I can use recovery via using the volume buttons & power button
Prydar said:
Ah, I've just read Vysor's troubleshooting guide, it says to be on PTP but I'm on MTP
Is there a known way to change to PTP from MTP with a broken digitizer? I can still see everything on the screen as it's just the digitizer thats broken so I can use recovery via using the volume buttons & power button
Click to expand...
Click to collapse
There is no problem with MTP, only changing the mode may help to detect some devices. If you are on Windows I strongly suggest you to download latest USB drivers. Eventually check your setup with another android phone.
anawim said:
There is no problem with MTP, only changing the mode may help to detect some devices. If you are on Windows I strongly suggest you to download latest USB drivers. Eventually check your setup with another android phone.
Click to expand...
Click to collapse
I do have the latest drivers, the device is detected in recovery mode but not when the phone is on
Prydar said:
I do have the latest drivers, the device is detected in recovery mode but not when the phone is on
Click to expand...
Click to collapse
I'm sorry to know that and I would suggest you to try and contact the developer as I can't help further except for checking with another phone to be sure the computer side is OK.
Seems I've hit the jackpot, my phone's a potato. I had just installed king of nougat v9 and it worked fine until I rebooted into recovery by holding the power button and selecting recovery. At first it was in a boot loop and wouldn't open recovery or get recognized by odin, I read somewhere here to disconnect the battery so I opened the back cover and disconnected it which apparently ****ed the phone a step further now it's dead unless it's connected to a power source and after disconnecting it stays on samsung logo/download mode for a bit then dies.
On my old rom it was working fine except for the fact that I couldn't connect the phone to pc as storage, and it couldn't recognize usb devices I plugged in using the adapter. I took the phone to a repair shop and they said they replaced the micro usb assembly and it still didn't show up on odin, then a few days later they said it's a problem with the power IC and they replaced that then the guy said it worked once on odin then stopped again.
Idk what to do lol, phone's bricked or should I try a different repair shop incase these were idiots.
note: it says device descriptor request failed when connected to pc
Have you tried to reboot to the bootloader by holding down the power button, home button and volume down when your phone is at the android logo?
TheSproker said:
Have you tried to reboot to the bootloader by holding down the power button, home button and volume down when your phone is at the android logo?
Click to expand...
Click to collapse
yeah it gets into download mode but it doesn't show up on odin
HNDRXX said:
yeah it gets into download mode but it doesn't show up on odin
Click to expand...
Click to collapse
Then it means you must install Samsung drivers, so that the computer would recognize your phone. Try downloading smart switch or kies and that should also install the drivers.
or try different ver. of odin
TheSproker said:
Then it means you must install Samsung drivers, so that the computer would recognize your phone. Try downloading smart switch or kies and that should also install the drivers.
Click to expand...
Click to collapse
yaro666 said:
or try different ver. of odin
Click to expand...
Click to collapse
tried both of the above
Try clean install Samsung Drivers and other version of Odin. It should be (have to be) show in Odin after all of these.
hacklesss said:
Try clean install Samsung Drivers and other version of Odin. It should be (have to be) show in Odin after all of these.
Click to expand...
Click to collapse
no luck there's definitely a hardware issue.
HNDRXX said:
no luck there's definitely a hardware issue.
Click to expand...
Click to collapse
Is pc respond when you plug usb cable ? (In download mode)
hacklesss said:
Is pc respond when you plug usb cable ? (In download mode)
Click to expand...
Click to collapse
it says device descriptor request failed when connected to pc
"device descriptor request failed when connected to pc" sounds like a windows problem not android. You can check in the "computer management" device manager to see if the phone is recognized. I am going to assume not.
Try this link for possible solutions. https://www.drivereasy.com/knowledg...ice-descriptor-request-failed-for-windows-10/
surfer3000 said:
"device descriptor request failed when connected to pc" sounds like a windows problem not android. You can check in the "computer management" device manager to see if the phone is recognized. I am going to assume not.
Try this link for possible solutions. https://www.drivereasy.com/knowledg...ice-descriptor-request-failed-for-windows-10/
Click to expand...
Click to collapse
I agree with that %100 percent ?
HNDRXX said:
no luck there's definitely a hardware issue.
Click to expand...
Click to collapse
Hey, do you figured it out what problem it is? I've the same problem and tried all of the PC/Windows tips and tricks.