Related
Galaxy
claudiudanila said:
Hi everyone, I have a big problem on my phone (SM-N910F) does not start even in download / recovery mode, the screen is off. I think it's a "hard brick."
All I can see now in device manager is Qualcomm HS-USB QDLoader 9008 (COM7).
Is there any possibility to bring my phone back into download mode? Please help me !!!
Click to expand...
Click to collapse
Well lets start by telling us what you did to the phone to get you where you are. And, what model is the N910F?
EDIT: is the "F" version for Europe?
Galaxy
What happens when you try to enter download mode?
Galaxy
claudiudanila said:
Thank you, I own a Samsung Galaxy Note 4, model SM-N910F for Europe.
I used a zip package to run a script via TWRP. The script was erasing some applications(bloatware) from rom. After the script was executed, I forgot to execute a wipe data/cache/factory and my phone was started to boot. After touchwiz was initialised, 3 seconds later my phone froze. Then I removed the battery and...here I am.
My computer is able to detect the phone(i can see in device manager Qualcomm HS-USB QDLoader 9008 (COM7) but Odin is unable to see any phone connected.
I've already tried an USB JIG but nothing...
I found an interesting thing, I can connect to the phone using QPST, please find attached a screenshot(Capture1.png). Here I found an option named Software Download. I've clicked this option and i can see: COM7 Phone in Download Mode. Please look at the attached picture Capture3. Here I can see two options: Phone Image and Boot image. Can I upload some specific boot image to unbrick my phone?
Click to expand...
Click to collapse
Not sure I can help you but you may be using a corrupted program, QPST. See here: http://forum.xda-developers.com/showthread.php?t=2263391
When the phone is hooked up to the charger do you get a charging indication on the LED? Is the battery charged or at least have some charge left on it?
Have you removed the battery and then tried to boot. If not give that a try. The only other recommendation I can offer since I've never used QPST and I don't know what script you ran to remove bloatware so I can't tell what it potentially did is to try to recover your phone through Kies (Samsung software). I seldom recommend Kies and have never used it myself since I have an unlocked bootloader, but if Kies recognizes your phone there may be hope. Good luck.
claudiudanila said:
Nothing...the screen is black, i cannot see anything, also Odin is unable to see the phone.
Click to expand...
Click to collapse
well it is weird that QPST shows you are in download mode but odin cannot see it.
Galaxy
Galaxy
claudiudanila said:
No led..no indicator..nothing...Kies is also unable to see the phone.
Click to expand...
Click to collapse
Sorry claudiudanila, based on what you've told us I have no other ideas.
claudiudanila said:
Hi everyone, I have a big problem on my Galaxy Note 4 phone (SM-N910F) does not start even in download / recovery mode, the screen is off. I think it's a "hard brick."
All I can see now in device manager is Qualcomm HS-USB QDLoader 9008 (COM7).
Is there any possibility to bring my phone back into download mode? Please help me !!!
Click to expand...
Click to collapse
I hope you are using windows pc not mac for odin.
jdomadia said:
I hope you are using windows pc not mac for odin.
Click to expand...
Click to collapse
Judging by the screenshots i would say its windows.
That said, I don't think I have any more ideas to add to the solutions already suggested.
You might wanna try your luck with z3x box or visit samsung service center.. that's all there's left to add.
maksharma231 said:
Judging by the screenshots i would say its windows.
That said, I don't think I have any more ideas to add to the solutions already suggested.
You might wanna try your luck with z3x box or visit samsung service center.. that's all there's left to add.
Click to expand...
Click to collapse
Using windows in mac parallel creates problem for flashing.
Galaxy
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Anyone?! There has to be someone who can help me out here....
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Root is definitely not what you need to fix this device, root would be something to access the system on a fully functional device to begin with. Maybe try the Odin carrier switch method and see if that recognizes the device.
Where did you buy the device and what did they say was wrong with it? Do you have no option of returning it because it very well my have been messed with and have Knox tripped anyways.
Bisquit-02 said:
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
Display is in like new condition, not even a blemish. No image upon power or on the wireless charging pad, the battery does get a bit warm when charging for few hours.
Yes, I have tried that exact combo for a good 60 seconds but nothing.
Either the battery is dead or a loose connection on the charger outlet.
Either way, it doesn't charge.
Verstuurd vanaf mijn SM-G955F met Tapatalk
whoamanwtf said:
Root is definitely not what you need to fix this device, root would be something to access the system on a fully functional device to begin with. Maybe try the Odin carrier switch method and see if that recognizes the device.
Where did you buy the device and what did they say was wrong with it? Do you have no option of returning it because it very well my have been messed with and have Knox tripped anyways.
Click to expand...
Click to collapse
The reason I commented about root was then someone can get a backup of the eMMC or a backup of the bootloader, so I can flash that, if that possibly fixes it. From what I can understand, something got corrupted and for that reason the device will not boot at all (nothing on the screen), so Odin is out of the question, since the device has to be in the Download mode for Odin to recognize it.
What I have found from further reading is that I can use QFIL (Qualcomm Flash Image Loader) to flash stock firmware since it recognized the S8 on COM port 3 when connected and QFIL recognized "Qualcomm HS-USB Qloader 9008" message, but what I have seen is people using MBN files (firehose.MBN) and an XML file to revive the phones. I've tried looking for those files even within the S8's stock firmware (AP, BL, CSC) but nothing.
Is there anyone who has experience working with QFIL who can guide me or provide with the files I need to flash this device back to stock.
Bisquit-02 said:
Either the battery is dead or a loose connection on the charger outlet.
Either way, it doesn't charge.
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
Appreciate your input but it does charge
taj786 said:
Appreciate your input but it does charge
Click to expand...
Click to collapse
If u can return it go do it, thats not a issue that can be solved here im guessing is a hardware conection/display issue. If u cant reach download mode then i think u cant get help here
This is not hardware issue or anything like it. What youve done, same as I have, is wiped the download and recovery partitions of the phone. QFIL can fix this, but same as you I have not found the required files. I did find the programmer firehose but its an efl. I can not find the meta file it apparently needs. Did you ever fix this
taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Click to expand...
Click to collapse
No no no, display is fine, odin will not help you. Your phone is in a mode called edl. This happens when your bootloader is corrupt or unbootable for some reason. The bad news is this typically called a hard brick, as it requires special software to recover from that isnt available typically to the public.
Absolutely agree with the poster who said try and return it. This mode is very difficult to recover from, if its at all possible. There are tools that some of us have that might be able to recover it, but they havent worked on v2 bootloaders so far. The sdcard stuff doesn't work with the s8 as it was turned off due to security issues.
Let me know if you cant return it and I'll see what i can do, but no promises
partcyborg said:
No no no, display is fine, odin will not help you. Your phone is in a mode called edl. This happens when your bootloader is corrupt or unbootable for some reason. The bad news is this typically called a hard brick, as it requires special software to recover from that isnt available typically to the public.
Absolutely agree with the poster who said try and return it. This mode is very difficult to recover from, if its at all possible. There are tools that some of us have that might be able to recover it, but they havent worked on v2 bootloaders so far. The sdcard stuff doesn't work with the s8 as it was turned off due to security issues.
Let me know if you cant return it and I'll see what i can do, but no promises
Click to expand...
Click to collapse
Looks like I've done the same thing with S8+ G955F. I was trying to fix an FRP issue and flashed a mixture of Nougat 7.0, combination and CRED BL and now it just shows black screen, can't get to download mode. This was all done with Odin.
Bisquit-02 said:
Display broken? For not getting an image when you plug in the power?
Have you tried pressing volume-down+bixby+power button for a full 10 seconds?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Click to expand...
Click to collapse
taj786 said:
Guys need help....I recently bought a Samsung S8 (t-mobile version) without knowing much of its history thinking it had a deeply discharged battery, but after a good 10 hrs on the charger it still won't turn on, no LEDs, no vibration, nothing, a complete black screen so it will NOT boot into recovery or download mode. However, it does seem to take a charge as the back side does get a bit warm when charged. When plugged into the PC (Win 10) it does not get recognized under My PC but I hear the USB plug-in chime and under the Device Manager, I get "Qualcomm HS-USB QDloader 9008" on COM port 3. From what I've found online, seems like I will need the original S8's complete eMMC image and load it onto the sdcard and recover it that way, even if it's possible.
Can anyone help/guide me in the proper direction? Really hoping to recover this device. This might even help others who may have or will brick their S8's. Hope we can find root soon if that's what's needed to fix this. Thanks a lot in advance
Click to expand...
Click to collapse
Good morning, my S8 and the same happened to me, to downgrade the oreo to the nougat; I did a JIG with resistors; When you download the keys, the JIG does not work on time, then after; I do not know how to say why.
then it means im doomed.. im experiencing the same shiiit
\
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
S8 Hard bricked
A_Bad_Marksman said:
Hey
So I was flashing android 7.0 to an S8 and it completely died, this is how completely:
- No screen/LED/vibration motor
- No safety/recovery/download mode (and don't ask about button combos, I've tried them all)
- No USB recognition from device manager (not even as exynos in other devices, just nothing)
- USB jig does nothing
- It is however recognised by wireless chargers (but I doubt that has any real significance)
At this point my question is would a JTAG even work on it? Or is my only hope a complete motherboard replacement?
Click to expand...
Click to collapse
hello!
same happened to me ......dont worry i will help u....
i think u flashed aosp rom
phone is not hard bricked its still not turned off believe me........
do the following:
donot charge phone for atlesat 24 hours .......
after 24 hours try to boot into download mode press button for like a minute it will work in multiple tries,,
immediately flash twrp and when flashed successfully suddenly press vol down + bixby + power it will boot into recovery
charge for 1 -2 hours , clear system and every thing if you have backup thats good other wise flash firmware......donot turn in till flashing the system and data in recovery mood......boot into download mood from recovery and there you go....if still a problem inbox me
Thanks, I'll give it a shot
ok let me know then
Jtag dead phone to life and rewrite IMEI
I had the same thing, sent it to Fonefunshop in England, they said they could fix it, the didn't even open it as discovered by the guys who fixed it and is necessary to use jtag.
Fonefunshop said eMMC chip was bad, which is not true, but that led me to search for someone to replace the chip. I found A2Z cellular in Ottawa, Canada. They got the phone to boot up, but IMMEI was null( I did this trying to flash back to stock after TWRP screwed up). They rewrote original IMEI , now phone works like new. These guys are amazing.
http://a2zcellular.com/
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
A_Bad_Marksman said:
Thank you all for the advice.
But I have now managed to unbrick and reflash the firmware. khawarjaved's advice turned out to be what fixed it in the end.
That was close, nearly lost £30
Click to expand...
Click to collapse
I have been through that situation man.... So always ready to help, ??
Hi pros
I'm in kind of a similar situation....I think I flashed MY 950U PIE with wrong BL
This phone is dead....Doesn't boot...no download mode....No recovery mode....
When connected to pc....device manager Recognises device as QUALCOMM HS USB 9008
Any way to brig it back to life...?
Your phone is connected in edl download mod. It will accept special files which will allow it to boot to download mode and let you flash stock firmware
The tool used for this is emmcdl.exe
It has to come with phone specific files
No idea where to get it. Ask people here, those who root phones. They know.
i bricked my redmi note7.
AND i have DEEP/ENGINEER FLASH CABLE. Bought it from store.
BUT in pc, it is not recoigen as 9008 while connected... of course i pressed only THE deep flash cable button
now, if i am missing anything, plz provide... (drivers?)
I HAVE ALSO A IMPORTANT QUESTION
--- suppose, my device got inturrouption, while FLASHING. so, that means - my device is dead? or I CAN BRING IT BACK TO LIFE WHENEVER (multiple) I WANTED BY @Deep FLASH [email protected]
somebody PLZ REPLAY fast & IF YOU KNOW ABOUT THESE STUFF!
hi, everyone , i m tring to revive my hard bricked oneplus 8 pro but without any luck i m getting "firehosecheckrsp failed errno 258" error , i tried every possible solution a did find (Drivers, Cable, USB 2 , other pc) , i m convinsed tha i shoud start search for a motherboard replacements (even that i coudnt find on the internet)
so please if anyone could help me (Phone stuck on EDL mode - recognised by pc but buttons combination doesn't work )
If you're in edl mode, have you attempted to MSM back to stock?
That's about as low level as you can get, so from a recovery perspective if that doesn't work then nothing will.
Also have you tried holding all the buttons for a long time? Say 30 seconds?
Bare in mind that EDL mode will not remain on for very long, you have to have the MSM tool open and ready for the connection, then with the phone off. Connect it to pc and hold volume up and down, you'll hear the windows ding and it'll say connected on the MSM tool, then and only then click start, flashing should commence and it'll remain locked in EDL until complete.
Lastly you're in warranty so you shouldn't need to buy or replace anything.
dladz said:
If you're in edl mode, have you attempted to MSM back to stock?
That's about as low level as you can get, so from a recovery perspective if that doesn't work then nothing will.
Also have you tried holding all the buttons for a long time? Say 30 seconds?
Bare in mind that EDL mode will not remain on for very long, you have to have the MSM tool open and ready for the connection, then with the phone off. Connect it to pc and hold volume up and down, you'll hear the windows ding and it'll say connected on the MSM tool, then and only then click start, flashing should commence and it'll remain locked in EDL until complete.
Lastly you're in warranty so you shouldn't need to buy or replace anything.
Click to expand...
Click to collapse
Thanks for you're replay , but the phone is always on EDL mode even if i unplug the battery (open phone) when i plug again the phone goes automatically to EDL mode and MSM tool show the phone as connected , but when i try to pass the flash, i got the 258 error
ahmadOnePlus said:
Thanks for you're replay , but the phone is always on EDL mode even if i unplug the battery (open phone) when i plug again the phone goes automatically to EDL mode and MSM tool show the phone as connected , but when i try to pass the flash, i got the 258 error
Click to expand...
Click to collapse
Did you make sure you changed the target device?
Also, what model 8 pro? Are you using correct msm for that model? And it almost sounds like you aren't using correct drivers. Qualcomm USB drivers are needed
jamescable said:
Did you make sure you changed the target device?
Also, what model 8 pro? Are you using correct msm for that model? And it almost sounds like you aren't using correct drivers. Qualcomm USB drivers are needed
Click to expand...
Click to collapse
+1 to this
You need these so the phone is detected correctly in windows. Here is a link.
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com
I have the same problem. I have a 7T but stuck with the same error firehose check rsp failed, errno:258
gcf81 said:
I have the same problem. I have a 7T but stuck with the same error firehose check rsp failed, errno:258
Click to expand...
Click to collapse
Hey, I think you reached out to me on YouTube. Do you know for sure which model of OnePlus 7T you have? There are two common versions in North America HD1907 (T-Mobile) and HD1905 (international unlocked)
Nick-Henkey said:
Hey, I think you reached out to me on YouTube. Do you know for sure which model of OnePlus 7T you have? There are two common versions in North America HD1907 (T-Mobile) and HD1905 (international unlocked)
Click to expand...
Click to collapse
Hey Nick, thanks for responding. It was bought unlocked North America version but then ATT customer support went into the phone while trying to fix something and I think they locked it right before it crashed.
gcf81 said:
Hey Nick, thanks for responding. It was bought unlocked North America version but then ATT customer support went into the phone while trying to fix something and I think they locked it right before it crashed.
Click to expand...
Click to collapse
Looking around, the North America version should be running international firmware (HD1905):
OnePlus 7T hardware variants
I was curious about the different hardware variants of the 7T and decided to ask support once EU launch went over and they kindly answered. HD1900: China HD1901: India HD1903: Europe HD1905: North America HD1907: T-Mobile USA
forum.xda-developers.com
I presume that you're using this MSM tool - https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/
Did you try all of the steps suggested by OP, yet?
Install drivers
Change to factory cable
Different USB port
Different Windows computer?
The only thread I could find where this problem was solved was on the OnePlus forum. The user completely removed and reinstalled the Qualcomm drivers (a different PC should handle that) - https://forums.oneplus.com/threads/solved-closed-trying-to-unbrick-op5t.956810/