Tried using the 935U firmware Odin said it installed correctly but the phone wont power back on ive tried just powering on, holding home power up nothing is turning it on. any suggestions?
Are you able to get back into download mode?
t12icky0 said:
Are you able to get back into download mode?
Click to expand...
Click to collapse
no idea...i hook the usb up to pc it makes noise but screen black. I can hold the power buttons and only way i know it resets or does something is because windows will make the disconnect noise. but it wont let me see anything at all. when i go to device manager is shows the phone as Qualcomm HS-USB QDLoader 9008 (com3) ive tried changing that as well but nothings working. pc recognizes the phone but as that and not the actual phone
Kielbasa99 said:
no idea...i hook the usb up to pc it makes noise but screen black. I can hold the power buttons and only way i know it resets or does something is because windows will make the disconnect noise. but it wont let me see anything at all. when i go to device manager is shows the phone as Qualcomm HS-USB QDLoader 9008 (com3) ive tried changing that as well but nothings working. pc recognizes the phone but as that and not the actual phone
Click to expand...
Click to collapse
Try holding volume down, home and the power key. See if you can access the download mode that way.
t12icky0 said:
Try holding volume down, home and the power key. See if you can access the download mode that way.
Click to expand...
Click to collapse
tried it itll make noise on pc but the screen wont come on at all
What files did you try flashing into the phone?
t12icky0 said:
What files did you try flashing into the phone?
Click to expand...
Click to collapse
Cant flash anything into it cause odin doesnt recognize it now. i been downloading Drivers hoping i can luck out and maybe install it to into Qualcomm HS-USB QDLoader 9008 under device manager cause thats only thing that pops up when the phone is connected to the pc now. shows up as well unspecified but i think as a hub i think i can download firmware and install the drivers individually hopefully might work
Kielbasa99 said:
tried it itll make noise on pc but the screen wont come on at all
Click to expand...
Click to collapse
tried flashing the G935U thought that it was compatible
So download mode or recovery NEVER come up?
Sent from my SAMSUNG-SM-G935A using Tapatalk
smknutson said:
So download mode or recovery NEVER come up?
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
nope i think its hardbricked nothin works to be able to get it to boot into either modes
Related
Can anyone tell me a way so that the pc detects my bricked OPT? I have tried all combinations but its not getting detected at all
phorcus said:
Can anyone tell me a way so that the pc detects my bricked OPT? I have tried all combinations but its not getting detected at all
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Rebel7022 said:
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
finally it got detected but when i run MSM8994DownloadTool.exe as administrator and click on start nothing happens
https://1.bp.blogspot.com/-ZZ-sHUBv...ExaIdiLCYRNQCLcB/s1600/Screenshot+%284%29.png
this is where i am stuck please help guys i am in a fix :'(
Are you sure you disabled driver signature enforcing in Windows? You can't install the qualcomm 9008 serial interface driver without doing this, as this driver is not signed by Microsoft.
pitrus- said:
Are you sure you disabled driver signature enforcing in Windows? You can't install the qualcomm 9008 serial interface driver without doing this, as this driver is not signed by Microsoft.
Click to expand...
Click to collapse
yes i did still it doesn't work, any help would be appreciated
If you power up your phone using volume up in fastboot/bootloader mode and then run fastboot devices, does it list your phone? Just making sure the cable connection works.
If yes, then power down your phone by holding power button until screen goes black (making sure you disconnected usb cable first). Then hold volume up while connecting usb cable (don't touch power button), you should hear Windows detecting a new device, check device manager to see that the qualcomm 9008 usb serial port has been successfully installed and with no warning exclamation mark on it. If all is good, you should now be able the launch the download tool and push the download button to start downloading the file partitions to the phone.
pitrus- said:
If you power up your phone using volume up in fastboot/bootloader mode and then run fastboot devices, does it list your phone? Just making sure the cable connection works.
If yes, then power down your phone by holding power button until screen goes black (making sure you disconnected usb cable first). Then hold volume up while connecting usb cable (don't touch power button), you should hear Windows detecting a new device, check device manager to see that the qualcomm 9008 usb serial port has been successfully installed and with no warning exclamation mark on it. If all is good, you should now be able the launch the download tool and push the download button to start downloading the file partitions to the phone.
Click to expand...
Click to collapse
Thanks a lot for writing out to me, but the thing is that my phone is already dead and i had given up all the hope that i had but luckily it got detected and i cannot boot into fastboot mode or bootloader mode the screen is already black, do you think i still have hope? the phone has been detected as qualcomm 9008 in ports in device manager
phorcus said:
Thanks a lot for writing out to me, but the thing is that my phone is already dead and i had given up all the hope that i had but luckily it got detected and i cannot boot into fastboot mode or bootloader mode the screen is already black, do you think i still have hope? the phone has been detected as qualcomm 9008 in ports in device manager
Click to expand...
Click to collapse
Could it be that the actual screen is dead on your phone? But still, since the PC detects the debug port, it should start restoring the phones partitions when you start downloader tool and press the download button up to the left.
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.
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
ibphantom said:
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
Click to expand...
Click to collapse
Last time i checked, edl mode was volume up and down and power button together. Then wait till light flashes three times and you're in edl mode.
Waancho said:
Last time i checked, edl mode was volume up and down and power button together. Then wait till light flashes three times and you're in edl mode.
Click to expand...
Click to collapse
I tried that, and I can hear it disconnect and reconnect again, but still can't get windows to see it in adb. Device manager shows it as Qualcomm HS-USB QDLoader 9008(COM6)
ibphantom said:
I tried that, and I can hear it disconnect and reconnect again, but still can't get windows to see it in adb. Device manager shows it as Qualcomm HS-USB QDLoader 9008(COM6)
Click to expand...
Click to collapse
If I'm not mistaken, that in fact means you're in edl mode. Edl and adb are two different modes.
Waancho said:
If I'm not mistaken, that in fact means you're in edl mode. Edl and adb are two different modes.
Click to expand...
Click to collapse
Okay, well even from there it's not showing up in XiaoMiFlash's device list
ibphantom said:
Okay, well even from there it's not showing up in XiaoMiFlash's device list
Click to expand...
Click to collapse
Did you try the edl tool AND different cables? I always test cables just to be sure.
Waancho said:
Did you try the edl tool AND different cables? I always test cables just to be sure.
Click to expand...
Click to collapse
I've tried 3 different cables. I'm stuck at the Axon7Toolkit option "#11 : RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)"
I am able to select stock firmware, but then it tries to pass the flash off to XiaoMiFlash and that program cannot see my phone for some reason.
ibphantom said:
I've tried 3 different cables. I'm stuck at the Axon7Toolkit option "#11 : RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)"
I am able to select stock firmware, but then it tries to pass the flash off to XiaoMiFlash and that program cannot see my phone for some reason.
Click to expand...
Click to collapse
Did you try flashing a full edl image for your phone?
Waancho said:
Did you try flashing a full edl image for your phone?
Click to expand...
Click to collapse
I've been trying to, but XiaoMiFlash tool doesn't see my device in edl
ibphantom said:
I've been trying to, but XiaoMiFlash tool doesn't see my device in edl
Click to expand...
Click to collapse
Have you tried using the EDL Tool?
ibphantom said:
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
Click to expand...
Click to collapse
Stupid question, did you take the SD card out?
Hey everyone.
I recently got a TMO 6T and tried to convert it to the international ROM, but ran into some problems. The device would not show up in the Device Manager, even after installing the OP and Qualcomm drivers multiple times. I watched several videos just in case, and restarted both the phone and computer. The phone shows up normally for file transfer, but won't appear when in Fastboot Mode.
Thank you
FastAssassin101 said:
Hey everyone.
I recently got a TMO 6T for my birthday and tried to convert it to the international ROM, but ran into some problems. The device would not show up in the Device Manager, even after installing the OP and Qualcomm drivers multiple times. I watched several videos just in case, and restarted both the phone and computer. The phone shows up normally for file transfer, but won't appear when in Fastboot Mode.
Thank you
Click to expand...
Click to collapse
Have you tried this tool: https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307/page109
Caltinpla said:
Have you tried this tool: https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307/page109
Click to expand...
Click to collapse
That is what I am trying to do but the MSM tool won't recognize the phone is plugged in.
FastAssassin101 said:
That is what I am trying to do but the MSM tool won't recognize the phone is plugged in.
Click to expand...
Click to collapse
Turn off the phone, press and hold both volumes down then connect to your computer using the stock USB cable. You might need to turn your computer volume up so you can hear when they're connected then run the .exe app.
Caltinpla said:
Turn off the phone, press and hold both volumes down then connect to your computer using the stock USB cable. You might need to turn your computer volume up so you can hear when they're connected then run the .exe app.
Click to expand...
Click to collapse
I've done this exact procedure several times, and hear the sound of a device connecting, but it won't show in MSM. I tried our desktop instead of my laptop, and the phone appeared in Device Manager for a little bit, but then disappeared again.
I'll try once more when I get home tonight, thanks!
FastAssassin101 said:
That is what I am trying to do but the MSM tool won't recognize the phone is plugged in.
Click to expand...
Click to collapse
the one thing you can't do is expect your phone screen to be on when you're doing the conversion.all you have to do is hold the volume up and down button at the same time plug it in and when you hear it connect on the computer run the MSMdownload tool. Your phone screen will be black. You shouldn't be in fastboot mode
Flash1959 said:
the one thing you can't do is expect your phone screen to be on when you're doing the conversion.all you have to do is hold the volume up and down button at the same time plug it in and when you hear it connect on the computer run the MSMdownload tool. Your phone screen will be black. You shouldn't be in fastboot mode
Click to expand...
Click to collapse
Oh wow, this worked! Thanks so much. For some reason I thought it had to be in Fastboot https://cdn-cf-3.xda-developers.com/images/smilies/victory.gif
FastAssassin101 said:
Oh wow, this worked! Thanks so much. For some reason I thought it had to be in Fastboot https://cdn-cf-3.xda-developers.com/images/smilies/victory.gif
Click to expand...
Click to collapse
I thought the same thing too.? we don't learn anything if we don't make mistakes ???
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.