Database Users

Phone wont power up after sm-935U

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

Stuck at twrp loading screen, no other boot options is working.

hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.

senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
both volume buttons + plug the wire doesn't work?

senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
I have exactly the same problem, could you solve it? I'm very worried about my phone

ale0796 said:
I have exactly the same problem, could you solve it? I'm very worried about my phone
Click to expand...
Click to collapse
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.

senny22 said:
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
Click to expand...
Click to collapse
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU

ale0796 said:
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
Click to expand...
Click to collapse
Really glad I could help

Return to stock has gone a bit Pete Tong - help!

I'm returning my 2017G as the internal gyro sensor is wonky and it's not playing well with my VR headset.
I was following a guide (I don't think it's important to state which) to return to stock. Seemed to go well until my phone started asking for a password (there wasn't one active). I put in lots of passwords thinking it would just eventually factory reset itself. Instead of resetting, it accepted a password and I then got the decryption unsuccessful screen. "The password you have entered is correct but unfortunately your data is corrupt". It gives me the option to reset my phone but nothing happens. It looks like it's going into EDL mode (black screen with red led). I can see the phone in dev manager and it lists as QUSB etc when put into EDL mode. My problem is that it isn't listed as an adb device so I cant't flash anything further.
I have removed and installed drivers using zadig. I've removed and reinstalled the QUSB drivers. I've run the minimal adb thingy. Bear in mind that I've been flashing recoveries and roms with no issue up until now. I can also access FTM.
Any words of wisdom gratefully received.

crank_girl said:
I'm returning my 2017G as the internal gyro sensor is wonky and it's not playing well with my VR headset.
I was following a guide (I don't think it's important to state which) to return to stock. Seemed to go well until my phone started asking for a password (there wasn't one active). I put in lots of passwords thinking it would just eventually factory reset itself. Instead of resetting, it accepted a password and I then got the decryption unsuccessful screen. "The password you have entered is correct but unfortunately your data is corrupt". It gives me the option to reset my phone but nothing happens. It looks like it's going into EDL mode (black screen with red led). I can see the phone in dev manager and it lists as QUSB etc when put into EDL mode. My problem is that it isn't listed as an adb device so I cant't flash anything further.
I have removed and installed drivers using zadig. I've removed and reinstalled the QUSB drivers. I've run the minimal adb thingy. Bear in mind that I've been flashing recoveries and roms with no issue up until now. I can also access FTM.
Any words of wisdom gratefully received.
Click to expand...
Click to collapse
Why did you try to get ADB while you were in EDL though? You only get the EDL connection there.
Look, two things:
-When you get the password thing you just have to format data (NOT wipe, but FORMAT). just remember that for the future.
-Since you didn't say what happened with the driver, let's see that first. Connect it, get into EDL (you can enter by key combination or by FTM then "adb reboot edl"), and when you're in EDL find the driver. If it is the Zadig driver uninstall it and "delete driver software too". After that hold all 3 keys (power and vol+-) until device manager refreshes and the phone flashes the led. After that the qualcomm driver should install itself. If it is "Qualcomm HS-USB QDLoader 9008" use MiFlash or djkuz's EDL Tool to flash a stock system.
p.s. can you actually flash something with adb??

Lots of people seem to confuse adb with fastboot. Is that what you want to use?

Thanks both for responding. I think I've gotten myself a bit confused over what is supposed to be working at any given time.
I can get the phone into EDL mode and fastboot. Fastboot devices finds my phone. MiFlash doesn't find my phone despite having the QHSUSB driver installed.
What's the easiest way to return my phone to stock? I have MiFlash and Axon7toolkit installed.
Cheers!

Choose an username... said:
Why did you try to get ADB while you were in EDL though? You only get the EDL connection there.
Look, two things:
-When you get the password thing you just have to format data (NOT wipe, but FORMAT). just remember that for the future.
Click to expand...
Click to collapse
It doesn't work. I only get the option to reset phone and if I press that the screen goes black with just a red led to indicate that it's not switched off. It hangs like that.
-Since you didn't say what happened with the driver, let's see that first. Connect it, get into EDL (you can enter by key combination or by FTM then "adb reboot edl"), and when you're in EDL find the driver. If it is the Zadig driver uninstall it and "delete driver software too". After that hold all 3 keys (power and vol+-) until device manager refreshes and the phone flashes the led. After that the qualcomm driver should install itself. If it is "Qualcomm HS-USB QDLoader 9008" use MiFlash or djkuz's EDL Tool to flash a stock system.
Click to expand...
Click to collapse
That's the other thing, my laptop doesn't communicate with the phone at all via adb.
These images might help - USBDeview showing the drivers in operation in various phone states.
First is FTM, then in fastboot, then in EDL, then when it's booted normally. Green denotes drivers that are functioning OK and pink is where it might be problematic. Can you spot any issues and have ideas on how I can put it right?
Cheers!

You have the wrong drivers.

crank_girl said:
It doesn't work. I only get the option to reset phone and if I press that the screen goes black with just a red led to indicate that it's not switched off. It hangs like that.
That's the other thing, my laptop doesn't communicate with the phone at all via adb.
These images might help - USBDeview showing the drivers in operation in various phone states.
First is FTM, then in fastboot, then in EDL, then when it's booted normally. Green denotes drivers that are functioning OK and pink is where it might be problematic. Can you spot any issues and have ideas on how I can put it right?
Cheers!
Click to expand...
Click to collapse
I tried to post yesterday and for some reason the XDA app didn't post the answer... Basically this:
-Forget ADB and that program that you're using to see the devices. EDL uses COM protocol, has nothing to do with adb at all.
-Go to Device manager and find where QUSB_BULK is. If it is in Unknown devices, either right click on it and try to install the driver automatically, or search for "Qualcomm HS-USB QDLoader 9008 drivers", download, install and try to install it on QUSB_BULK. If it is in an "USB devices" tab or on Ports "COM & LPT" simply right click, Uninstall device, Delete driver software for this device

I've done that several times over but miflash still isn't detecting it.

crank_girl said:
I've done that several times over but miflash still isn't detecting it.
Click to expand...
Click to collapse
all right. Try EDL Tool by djkuz. I don't know if the same packages work but just download another edl package

It's weird. Doesn't matter what mode the phone is in fastboot, edl, ftm, it's not detected by my laptop .
I'll try the tool you suggest.
Tbh I'm reaching the point where I'm tempted to return as is. Bootloader is locked, it just looks like a phone fault.

crank_girl said:
It's weird. Doesn't matter what mode the phone is in fastboot, edl, ftm, it's not detected by my laptop .
I'll try the tool you suggest.
Tbh I'm reaching the point where I'm tempted to return as is. Bootloader is locked, it just looks like a phone fault.
Click to expand...
Click to collapse
How come? The right driver literally appears on the last photo...

Choose an username... said:
How come? The right driver literally appears on the last photo...
Click to expand...
Click to collapse
I know, right? It's a mystery. Never had this happen before.

crank_girl said:
I know, right? It's a mystery. Never had this happen before.
Click to expand...
Click to collapse
If it doesn't work try MiFlash on another PC, it sometimes happens that it won't detect it by any means

Issues Converting From T-Mo to International ROM

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 ???

Bricked device - Buttons don't respond and USB does nothing aswell

I am try to install LineageOS 19.1 on my SM-P610 but after flashing the recovery, I accidentally wiped the system and cache partitions. After that it would only show "entering fastboot mode...". After managing to get into download mode again using the buttons, I tried flashing the recovery from their but lost the USB connection prematurely because I was using a magnetic USB cable. When I came back to it (it took a while to flash), the screen was black and none of the buttons worked. After letting it charge overnight, I still have the same issue. I am worried that I have bricked my device in a way that isn't recoverable.
After some digging I found something called an EDL cable which seems to put the device in a deep flash mode but that is just for Qualcomm devices and the Samsung Galaxy Tab S6 LIte has is Exynos instead. Is there something similar for my device or should I throw it in the can?

yes there is
https://forum.xda-developers.com/t/10-exynos-bootloader-removed.4155085
https://forum.xda-developers.com/t/...devices-with-deleted-bootloader-sboot.3573865
but you don't need
https://forum.xda-developers.com/t/...-from-ebay-and-got-this-on-his-screen.4541519

aIecxs said:
yes there is
https://forum.xda-developers.com/t/10-exynos-bootloader-removed.4155085
https://forum.xda-developers.com/t/...devices-with-deleted-bootloader-sboot.3573865
but you don't need
https://forum.xda-developers.com/t/...-from-ebay-and-got-this-on-his-screen.4541519
Click to expand...
Click to collapse
Unfortunately my tablet isn't recognized by any of my desktop or my laptop, it there anything else I can do?

use linux. check lsusb

aIecxs said:
use linux. check lsusb
Click to expand...
Click to collapse
Same thing I'm afraid. Nothing. I'm guessing there isn't much besides give up at this point.

watch YouTube how to open backcover and disconnect battery.