I just tried to install stang5liter note5 with FF, and now the phone will not boot. I have installed other roms with FF no problem. It has a black screen. It will not boot into recovery or download mode. I plug it into a Windows machine and it sees a QHSUSB_DLOAD, but I cannot access it.
I tried using Unified Android toolkit, and it cannot find the device. Odin cannot find it either.
How do I unbrick this?
Do you have a battery in your phone?(not sure if it matters but read something about it). Well, QHSUSB_DLOAD is really bad. I think it happened to surge1223's s4 and it was equivalent to a hard brick. Good luck
Yes, I have a battery in the phone. I have tried every button options, and none of them are working.
if you can't get into download mode i think you are bricked for sure
Sent from my SCH-I545 using Tapatalk
Yes, it is bricked. Is there a way to unbrick it?
Related
Hello everyone,
I have been trying to find a way to get out of the Vibrant screen for my phone.
This happen by me having the Obsidian 4.2 installed with Black Froyo, and I was trying to restore to get the Sims 3 and Thinkfree office because it was not available when I flashed my phone.
I have a backup using ROM Manager on my laptop. I am using a Mac, and I have Parallels installed with XP. Problem is I have ODIN installed and been trying to have ODIN recognized the Vibrant in order to start the process, but it has not recognize the device. I thought I had all drivers installed, and I would appreciate any help.
The device is recognized when I have it in the Recovery mode, but not in download mode.
Odin is super finicky but this process usually works. Plug your phone into your usb port while it's still off. Bring up odin but don't put the files you want in it yet. Now boot your phone into download mode. After the com port comes up in odin load the files into thier proper fields and install. Hope that helps.
Sent from my SGH-T959 using XDA App
if you can get to clockwork recovery, you can mount your phone to your computer (the option that says USB, like the 2nd or 3rd option). You could then move a rom with kernel to your phone and flash it.
I think your problem is you were trying to go from 2.2 to 2.1 (nandroids do not restore the kernel, hence it will hang at the Vibrant screen). Perhaps you have voodoo or another lag fix and didnt disable it?
Also, my noob version in my signature show the proper steps for ODIN, and has a video.
Thank you the process work. I had Windows running on Parallels and it messed everything up. Had to reboot only with Windows though. i just resetted everything until I become more familiar with the process.
I have been posting (and have had some nice people try to help) in the How to Recover Fascinate from any Brick thread for about a week and can't seem to find a solution. I have also searched the internet high and low looking for a solution with no success. Hopefully someone here has had the same issues and can point me in the right direction.
I rooted the Fascinate using a one click method and was able to get a Titanium backup but could not get into the proper recovery to do a system image. Stupidly, I flashed SP Recovery from within ROM Manager. From that moment on I when the phone is turned on it gets to the "Samsung" screen and locks.
I did my research and found out all I needed to do to fix is install ODIN and reflash the stock ROM again. The problem is that ODIN will not recognize the phone. I start ODIN, pull the phone battery, plug the phone into USB cable, push volume down to get the phone into download mode (Yellow Triangle). I keep getting USB Device Not Recognized errors from Win 7 (64-bit).
I tried installing Heimdall to load the correct drivers but it doesn't see the device either. I can connect my Droid or Droid 2 and Heimdall sees immediately so I know it is not a problem with the software or cable.
I have tried to install the correct USB drivers (even the ones listed on this site). I tried installing Kies and it doesn't see the phone either.
Since the phone is looping at the "Samsung" screen I can't change any settings in the phone as some have suggested. I really do not have any more ideas other that to use this phone as a very expensive door stop. Hopefully, someone here can help. Thanks in advance!!!
pscpa said:
I have been posting (and have had some nice people try to help) in the How to Recover Fascinate from any Brick thread for about a week and can't seem to find a solution. I have also searched the internet high and low looking for a solution with no success. Hopefully someone here has had the same issues and can point me in the right direction.
I rooted the Fascinate using a one click method and was able to get a Titanium backup but could not get into the proper recovery to do a system image. Stupidly, I flashed SP Recovery from within ROM Manager. From that moment on I when the phone is turned on it gets to the "Samsung" screen and locks.
I did my research and found out all I needed to do to fix is install ODIN and reflash the stock ROM again. The problem is that ODIN will not recognize the phone. I start ODIN, pull the phone battery, plug the phone into USB cable, push volume down to get the phone into download mode (Yellow Triangle). I keep getting USB Device Not Recognized errors from Win 7 (64-bit).
I tried installing Heimdall to load the correct drivers but it doesn't see the device either. I can connect my Droid or Droid 2 and Heimdall sees immediately so I know it is not a problem with the software or cable.
I have tried to install the correct USB drivers (even the ones listed on this site). I tried installing Kies and it doesn't see the phone either.
Since the phone is looping at the "Samsung" screen I can't change any settings in the phone as some have suggested. I really do not have any more ideas other that to use this phone as a very expensive door stop. Hopefully, someone here can help. Thanks in advance!!!
Click to expand...
Click to collapse
Control Panel/ User Account/ User Account Control settings- set to- Never notify- restart computer.
Should recognize phone. Reset to default when done and restart. Windows crap!
Thanks but this setting has always been set to "Never Notify"......any other ideas...please
I don't know nothing about it but the guy said " reset to default and restart (again)??
Sent from my SCH-I500 using xda premium
Followed the directions exactly. I think the OP wanted me to reset to default after I was done flashing. This is so strange....I figure if the people on XDA can't figure this out the phone is doomed.
Have you tried a different USB plug on the computer? Or a different USB cord? Or a different computer?
Sent from my SCH-I500 using XDA App
schu9120 said:
Have you tried a different USB plug on the computer? Or a different USB cord? Or a different computer?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I had to use a laptop to access my Fascinate because my desktop wouldnt even show it as unrecognized hardware, it was like it didnt even exist... I went in device manager and uninstalled all my usb devices, rebooted with everything but mouse/kb unplugged, installed SDK drivers for Nexus S, rebooted again (probably not needed but better safe than sorry) and I can now Odin into my phone... Hope this helps ya man... sucks bricking a phone
The Heimdall drivers won't work. Kies won't recognize it if it won't boot. There should be an option in Kies to install the driver. Drop down box in the top left corner. Did you try to install your driver that way?
have you installed the driver yet? samsung driver?
ok guys, first things first. YES i did search, i read threads for hours. So if your just gonna come to bash on me... get off it.
So i had a bad flash, oh no. Phone was stuck in a bootloop, got it to download mode and put it thru odin. Well odin said FAILED. now i can still get into DL mode but its no longer a bootloop, now its a lil picture of a phone linked to a computer when i turn it on.
SO heres the prob, i can get into DL mode, but odin refuses to recognize my phone. Ive tried other usb ports, other cords, unistalled and reinstalled odin and the drivers. USB debugging is off says aio toolbox. So what do i do now? any suggestions im not thinking of?
Any help is greatly appreciated and will b thanked. =)
Phone to PC screen still should be able to flash through.
Have you tried a different computer? One that your phone has never been in contact with?
What was the FAILED error when you tried to ODIN initially?
Can you get into recovery by chance?
i have tried a different computer, but not one it has never been on b4.
And toast, i actually dont know if i can get into recovery. Im about to look up how and try that
WhiteBoyAwesome said:
i have tried a different computer, but not one it has never been on b4.
And toast, i actually dont know if i can get into recovery. Im about to look up how and try that
Click to expand...
Click to collapse
Gingerbread bootloader uses this combo:
For Recovery - Lower Volume Key + Power Button
For Download - Upper Volume Key + Power Button
If you have Froyo bootloader:
For Recovery - Both Volume Keys + Power Button
For Download - Both Volume Keys and Connect USB Cable
alright, i can use the hardware buttons to get into download just fine. But when i try to get into recovery it only gives me the Phone -- ! -- Computer icon. ITs getting annoying lol
Ok. I didn't figure that would work, but it wasn't going to hurt anything to try do you have any friends with Macs? You could try it on one of them with Heimdall. That would be another option to try.
Also, check out this thread: http://forum.xda-developers.com/showthread.php?p=8149503
Read all the posts, there is some good stuff in there.
+1 on recommended thread. It sounds just like your issue. Definitely try the Heimdall AIO one click t959 for Windows.
sent from the depths of helly bean
nothin yet :/
Google eugenes froyo that does not brick, read the op carefully, because after you odin the tar file, you will have an error message, thats ok, odin eclair and you should pass.
Read it 10 times, you'll reboot in cwm with an error message, ok, reboot, download, eclair.
stupid question sorry, but do you have sdk platform tools installed?
im not sure. i downloaded something called sdk manager, but it closes the moment u open it.
SDK platform tools is a large program, But if your computer has recognized your phone up till now, you probly have the right drivers, by the way have you cleaned your usb port? toothbrush and an electronics cleaner or alcohol very lightly, never know.
ok guys. heres the update. I tried all the links you guys have kindly tossed my way. nothin. Im on a different computer even and downloaded the drivers, odin, toolbox, etc. The phone still isnt recognized. I Have no clue why, is the reason cause usb debugging is off? the only 2 screens i can get to r download and phone ! computer. Am i bricked for good??? =(
WhiteBoyAwesome said:
ok guys. heres the update. I tried all the links you guys have kindly tossed my way. nothin. Im on a different computer even and downloaded the drivers, odin, toolbox, etc. The phone still isnt recognized. I Have no clue why, is the reason cause usb debugging is off? the only 2 screens i can get to r download and phone ! computer. Am i bricked for good??? =(
Click to expand...
Click to collapse
You are putting your phone into download mode before using odin right? You must have your phone in download mode for odin to recognize it. I'm guessing you have done this but I wasn't sure after reading through this thread, hope you get up and running again.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
You are putting your phone into download mode before using odin right? You must have your phone in download mode for odin to recognize it. I'm guessing you have done this but I wasn't sure after reading through this thread, hope you get up and running again.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
yep. tried multiple combos as well
Hey I think you should follow this..
1. Connect your phone with computer without battery
2. Press volume down and power button simantaniously for getting download mod
3. After 30 or 60 second pull back battery into phon with holding buttons
4. Odin ditect your device almost surely...
Thanks..
Sent from my GT-I5510 using xda premium
Ok, I just went through this over the past weekend with a spare Vibe that I have. Odin would not recognize it at all for my. I would here the Ding and then nothing. No yellow COM box, no driver installation, nothing.
Here is what I did:
First I went into Device Manager and with the phone plugged in (needs to be plugged in so you can see the yellow!), I uninstalled everything with Samsung's name tagged to it (including my SGS3 and SGS2 drivers).
Then I went here and downloaded and installed Heimdall (take note that you have to make sure that libusb-1.0 is correctly installed). There is an exe file in there (might be in the Heimdall thread here in the Vibe section), that allows you to update the drivers. That is where you would replace the Windows with libusb-1.0.
Then I plugged in my USB to PC and to phone and put it in Download mode. Nothing. So I left it plugged into the phone still but unplugged from PC and move ports. I have 3 ports and believe it or not, the one farthest from the power source/MB was the one that work. As soon as I plugged it in, I heard the Ding and saw the box pull up auto-installing the drivers.
After that, I went to Utilities in Heimdall to make sure detected. It was and I flashed Mr_Psycho's package (no pun intended ) via the normal Heimdall instructions.
Believe me, I have spent a ton of time on this and troubleshooted everything from dead USB to dead motherboard. It was a real PITA.
Edit:: If you need any of the files, Heimdall version or Drivers, just PM me and I will send them to you. You are not Bricked, just your PC's vision is clouded a bit.
woodrube i greatly appreciate the mass amount of help. i will try all the above as soon as im home and report back to u
alright, i deleted everything, reinstalled, tried heimdall still nothing. I am in download mode but laptop wont recognize anything. it says the correct drivers are installed but then says usb device not recognized, this is killing me as i need my phone imma post a video tonight of what im doing, hopefully someone sees im doing something wrong
I tried flashing CWM recovery onto my AT&T Galaxy S4 and because my phone does not connect to my computer via USB for some reason (the phone charges and my computer recognizes that there's a device in, but I cannot actually do anything with it) I flashed it with Flashify. I rebooted into recovery mode, and I got slapped with the "Unauthorized software has been detected on your phone!" message. So I tried rebooting, and I got stuck in a recovery mode bootloop with the same message. Eventually, I realized if I just go into download mode and reboot by pressing the volume down key, it doesn't try to go into recovery mode. I have already endlessly researched my USB problem, and yes, I DO have USB debugging on. ODIN recognizes that I have an external device in as well, but I haven't tried flashing anything onto my phone with it because I don't want to brick my phone because the connection to my PC is faulty. I'm using the charger that came with the device as my USB drive, so that's not faulty either. I know rooting my phone did this, and I'm pretty sure it's because I missed a step. I used this tutorial to root my phone:
[droid views dot com] /root-att-galaxy-s4-sgh-i337-android-4-4-4-kitkat-firmware-i337ucufnj4/ (I'm not allowed to post links yet, so fix the URL if you're gonna have a look)
When I flashed the I337_NC1_Stock_Kernel, my phone refused to go into download mode and I couldn't flash the I337_NJ4_Stock_Kernel as a result. I'm pretty sure that's what caused it, but I have no idea how to fix it. I'm not an expert with my phone and, despite almost soft-bricking my phone via a corrupt CWM .zip, I'm not a newbie at this either. If I could figure out how to fix this problem, I wouldn't have to worry about throwing myself into a bootloop because I can just use ODIN. I was a sitting duck before download mode rescued me, so I'd like some help as to how I can accomplish this. Any and all help is appreciated. I am 100% certain my device is the right version for that tutorial, I wouldn't try to root my phone without checking all of the simple things first.
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Darrian said:
I have flashed my device probably 50 times at this point trying different ROMS. Yesterday I decided to give stock another shot, but now I'm stuck. I had to flash the stock recovery to update to Marshmallow after restoring my Lollipop backup. I'm not happy with it, but I cannot reflash TWRP. When I boot to bootloader the fastboot drivers no longer work. Windows device manager says it's an unknown device and the device descriptor failed. I can't even manually force it to install the driver for the device by picking it, because it says that the driver isn't for that device. I even tried resetting my crappy Windows tablet so that it would have nothing previously installed and then installed HiSuite, but the same problem there as on my desktop. I have also tried generic "universal" android drivers and sketchy Huawei drivers from a "how to unlock your bootloader" tutorial. I have unplugged it and replugged it several times, using various different USB ports (I have 10 of them, so no shortage there).
I can't flash recovery through fastboot because that isn't an option. When in normal mode the computer sees the device just fine as a MTP device and an ADB device, but when I try to run ADB commands they don't see the device either. At this point I am really trying to find any way I can root the phone, regardless of how sketchy, so I can use Flashify to restore TWRP and go back to CM13 or an AOSP. Does anybody know a working method to root besides flashing through fastboot? Thanks.
Click to expand...
Click to collapse
There is none. The only safe way to root is to flash TWRP in fastboot. Right now, you can try to force update through update.app
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Darrian said:
Thanks for the reply, but:
1. I'm not looking for a safe method, just any method. I've tried the obvious suspects already (towelroot, kingroot, kingoroot)
2. I don't need to force an update, I am on the latest firmware now. If anything I may have to attempt to force a downgrade to open up vulnerabilities, but if I go back to lollipop then I will likely have issues flashing cm13.
Click to expand...
Click to collapse
Oh. But like I said, there is none.
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Darrian said:
I have come to the same conclusion, but I'm still hoping if somebody has rooted it in another way that they will see this thread and share their method. Otherwise I may end up stuck on unrooted stock, which will kinda suck.
Click to expand...
Click to collapse
Have you tried changing the drivers.?
Yes
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Darrian said:
So, I did not figure out how to root it without fastboot, but I did solve my problem. I dug out the cable that came with the phone, and using that cable my computer finally recognized it as an Android device when in fastboot mode. I don't know why it only works with that cable, but there it is, so I will have to make sure that cable never gets broken or lost.
Click to expand...
Click to collapse
Glad you fixed it. :highfive: