I hard bricked my Galaxy S II but when I take the battery out hold both volume buttons and plug into USB I can get my computer to recognize it was a "Qualcomm HS-USB QDLoader 9008" Device
Odin can see the phone but it can't flash any roms it won't get past "
<ID:0/003> SetupConnection.."
Is there any hope?
Tynen said:
I hard bricked my Galaxy S II but when I take the battery out hold both volume buttons and plug into USB I can get my computer to recognize it was a "Qualcomm HS-USB QDLoader 9008" Device
Odin can see the phone but it can't flash any roms it won't get past "
<ID:0/003> SetupConnection.."
Is there any hope?
Click to expand...
Click to collapse
how the hell did you manage that?
death1246 said:
how the hell did you manage that?
Click to expand...
Click to collapse
I put a .pit in odin
Tynen said:
I put a .pit in odin
Click to expand...
Click to collapse
u might need one of these little guys to hopefully unbrick your phone.. it might just get you back into download mode.
http://forum.xda-developers.com/showthread.php?t=1526600
Where are people finding these pit files??
Sent from my SGH-T989 using xda premium
Teo032 said:
Where are people finding these pit files??
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
thats what im trying to figure out. there are not pit files posted anywhere in the t989 section.... must be something from another samsung phone like the vibrant.
did other popular samsung devices gain cwm thru .pit files? ours uses a .tar file.
Sent from my SGH-T989
jordanishere said:
thats what im trying to figure out. there are not pit files posted anywhere in the t989 section.... must be something from another samsung phone like the vibrant.
did other popular samsung devices gain cwm thru .pit files? ours uses a .tar file.
Sent from my SGH-T989
Click to expand...
Click to collapse
Yeah, from what i read the older models did use a pit file... But i don't remember seeing any for our model
Sent from my SGH-T989 using xda premium
I've had a vibrant since it came out and every time you odined the Vibrant you needed a pit file. I had a pit in the odin directory and I wasn't really thinking and used it... *facepalm*
In hindsight it was a very stupid thing to do, but my softkeys weren't working and I was frantically trying to figure out what was going on...
I can repair both your brick and the soft keys if you need it done.
Sent from my Galaxy Nexus using xda premium
Mobile Tech Videos unbricked my device. I believe it was the first one they did. The service was excellent. I put my faith in them even when no solution existed and they stepped up to bat. Communication was awesome. I would recommend the service to anyone. If amyone was going to fix it they were... and did!
syale said:
Mobile Tech Videos unbricked my device. I believe it was the first one they did. The service was excellent. I put my faith in them even when no solution existed and they stepped up to bat. Communication was awesome. I would recommend the service to anyone. If amyone was going to fix it they were... and did!
Click to expand...
Click to collapse
I sent my phone to them, I'm waiting to get it back.
All of a sudden in the last few weeks I've had several emails asking me if a JIG will fix this exact error.
Looks like we need someone to try a JIG on their device with this error message.
---------- Post added at 06:39 PM ---------- Previous post was at 06:34 PM ----------
connexion2005 said:
I can repair both your brick and the soft keys if you need it done.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey bud please let me know if I can send peeps your way. I keep getting emails asking me who does JTAG on the SGSII lol or if my JIG will fix there phone... Id rather just refer peeps to someone who can JTAG instead of trying to guess if a JIG will fix this situation or not.
I'm sending a JIG today to a customer with this exact error message to let me know if it works or not. Thanks
If you download the stock rom from (can't remember site but password is sampro.pl) it comes with a pit file. That's what bricks the phone. Don't use it
blackerwater said:
If you download the stock rom from (can't remember site but password is sampro.pl) it comes with a pit file. That's what bricks the phone. Don't use it
Click to expand...
Click to collapse
YES THIS!
This is what bricked my phone
@connexion2005, I have the same problem with my T989. I (stupidly) attempted to flash Siyah kernel on it, CWM said everything went okay, but afterwards the phone never booted up again, just appears as a raw Qualcomm device. Been looking for someone who can do JTAG in the Austin area. I would be happy to bring it by (or send it to you) if you can resurrect it for me.
Alternately, I'm wondering if it's possible to software unbrick one of these, but I can't seem to get my hands on a copy of MPRG8660.HEX to use with QPST. I keep downloading ZTE firmware images but despite all of the mentions of this file, none of them seem to contain it. I still have access to a working T989. Can someone post or PM me this file, by chance?
This site gives me hope: http://www.anyclub.org/2012/05/how-to-generate-8660msimagembn.html
EDIT: Found a copy of the programming hex file and put it on my server: MPRG8660.HEX - can't wait to get home and try it out with QPST!! For the record, it was located in the ZTE firmware package known as "VDF_ES_V11AV1.0.0B07.zip".
Now I'm trying to track down a copy of QPST 2.7.369 or higher.
--W5i2
If you still need a copy of qpst, let me know. i have 2.7.xxx and i think i have qpst 3.x or something like that.
i hard bricked my t989 a couple nights ago using teamwin recovery. i have jtagged embedded systems before, but not a cell phone. would not know what to flash, where to flash it, and what program to use. i could never get qpst to recognize my phone (listed as qualcomm qhusb_dload or whatever) or the COM port it was using.
what does that HEX file do?
thanks
frescoraja
QPST 2.7.374! Haven't tried it yet though.
http://weasel.net/QPST_2.7.374.zip
The HEX files contain special bootloader code (I think) which allows QPST to speak to specific types of hardware. I may be mistaken on this, though.
--W5i2
weasel5i2 said:
QPST 2.7.374! Haven't tried it yet though.
http://weasel.net/QPST_2.7.374.zip
The HEX files contain special bootloader code (I think) which allows QPST to speak to specific types of hardware. I may be mistaken on this, though.
--W5i2
Click to expand...
Click to collapse
weasel,
Would you please be kind enough and explain what you did to get your phone back from the dead? I just hardbricked my phone using Odin (I know, I know) and am trying to bring it back from the dead. My phone is in the special Qualcomm download mode (not to be confused with the Samsung one) and would not power on.
Thanks in advance!
Any updates on this. I borked a loaner T989 trying to flash a ROM I later realized was meant for i9100. Note-to-self: ALWAYS SEARCH FOR ROMS BY MFG's PRODUCT CODE, NOT MOBILE OPERATOR'S PRODUCT NAME.
Current status: A Windows 7 (x64) system detects the T989 Qualcomm HS-USB device and the correct drivers are installed. Odin detects the device on the COM port, but hangs on any flashing attempts at the "SetupConnection" step. "Download Mode" doesn't seem to be accessible by any button-pressing, head-patting, belly-rubbing methods i've tried. In 7 years of flashing hundreds of ROMs on dozens of devices this is the first potentially fatal hard-brick i've done.
Any tips or pointers for self-repair would be appreciated. Otherwise I'll send it for 3rd party JTAG. . .
What you describe sounds painfully familiar. I spent a lot of time trying to bring my phone back from the phone heaven. Unsuccessfully. Phone was dead. Ultimately I sent it in for repair as it was still under warranty. It came back with a new logic board and relocked to its original carrier.
Problem you have is not how to flash it back to life, problem is what to flash. Your bootloader is dead and you need it recovered. This is what JTAG does. There was a reference in the thread to somebody being able to do that. I talked to him and he said he charges $50 for it, if I remember correctly.
Related
So, I went through the instructions and odin told me flash failed, the phone reported back that it had no partition structure in the download screen. Now the phone is stuck at a completely black screen regardless of what I do. Odin wouldn't recognize it at first till I tracked down the missing driver (Qualcomm HS-USB QDLoader 9008), now Odin picks it up again but never moves past <ID:0/003> SetupConnection.. Any ideas? I can't seem to get it to take any flashes whatsoever... I'm currently trying various drivers to see if that is the issue...
Seifer48 said:
So, I went through the instructions and odin told me flash failed, the phone reported back that it had no partition structure in the download screen. Now the phone is stuck at a completely black screen regardless of what I do. Odin wouldn't recognize it at first till I tracked down the missing driver (Qualcomm HS-USB QDLoader 9008), now Odin picks it up again but never moves past <ID:0/003> SetupConnection.. Any ideas? I can't seem to get it to take any flashes whatsoever... I'm currently trying various drivers to see if that is the issue...
Click to expand...
Click to collapse
are you putting the phone in download mode before you start the flash process?
EDIT: why did you make a new thread for this here when you already asked the same question in another thread? This isn't development talk please use proper forums next time thanks.
go here...
http://forum.xda-developers.com/showthread.php?t=1311229
that should fix it
Mainly because I didn't want to highjack that thread. Regardless, I felt this was development related hence the post in this forum. Yes, I've put it into download mode (vol up+down+power)
movieaddict said:
go here...
http://forum.xda-developers.com/showthread.php?t=1311229
that should fix it
Click to expand...
Click to collapse
That was actually my first idea. I haven't been able to even attempt this yet though, my issue is that Odin will not progress past "SetupConnection".
It sounds like you don't have all the drivers....
Sent from my GT-I9100 using xda premium
daddymatt said:
It sounds like you don't have all the drivers....
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yea, that was my first thought as well. Would you mind putting yours into Download Mode and checking to see which driver it uses in Device Manager? I'm sure that would be a great help!
Seifer48 said:
Yea, that was my first thought as well. Would you mind putting yours into Download Mode and checking to see which driver it uses in Device Manager? I'm sure that would be a great help!
Click to expand...
Click to collapse
Install Samsung Kies & that will give you all the correct drivers. You can find it by doing a google search.
Sent from my SGH-T989 using XDA App
I actually installed the kies package before I initially tried flashing. I've tried just about every driver package I can think of now.... Random errors are frustrating, especially since its beginning to look like I need a jtag to fix this. I really don't wanna have to build one again.
its not volume up and down plus power. Its pull battery, hold volume up and down, insert usb and then put battery in. a screen will come on the phone that says its dangerous to do this press volume up to confirm. Then make sure phone is recognized by odin and id.com space in odin turns yellow.
At this point I've been pulling the battery, volume up+down+power and plugging in USB. It will be detected by windows, but the device stays at a black screen. I haven't tried pressing volume up after windows detects it though, due to never seeing more than a black screen. Ill go try that and hopefully get somewhere.
Also, Odin has always detected it regardless of what I do.
odin will detect it no matter what but are you using a tmobile version because ive noticed your carrier is att in you sig and youve also posted in the att sg2 forums. if you are trying to use our method to flash an att sg2 guess what my friend you are bricked. It is a different method of rooting.
No luck, when I press volume up nothing happens. Odin detects it regardless.
The particular driver I'm using is "Qualcomm HS-USB QDLoader 9008", I'd love it if someone could plug their device in while in download mode and let me know which driver is in use under device manager. The kies package never installed the download mode driver for me and I had to hunt this one down using a google search for similar issues.
mongo41 said:
odin will detect it no matter what but are you using a tmobile version because ive noticed your carrier is att in you sig and youve also posted in the att sg2 forums. if you are trying to use our method to flash an att sg2 guess what my friend you are bricked. It is a different method of rooting.
Click to expand...
Click to collapse
Lol, yea I know. I have a lot of devices. I am indeed using a TMobile Galaxy S2, SGH-T989. I actually have a phone line with each of the 4 major US carriers. I just use my AT&T line as the primary.
Seifer48 said:
I'd love it if someone could plug their device in while in download mode and let me know which driver is in use under device manager.
Click to expand...
Click to collapse
Not sure if this is what you're looking for, but I see "SAMSUNG Mobile USB CDC Composite Device"
Seifer48 said:
Lol, yea I know. I have a lot of devices. I am indeed using a TMobile Galaxy S2, SGH-T989. I actually have a phone line with each of the 4 major US carriers. I just use my AT&T line as the primary.
Click to expand...
Click to collapse
Does Adb recognize your device?? If so, to make sure you are in download mode run "adb devices" on cmd to see if your device pops up and if it does run "adb reboot download".... This should get you to download mode Then i want you to delete your current .tar file and Re-Download the .tar file!
Ps: both commands run WITHOUT quotation marks
Pss: If odin recognizes your device... Drivers are not the problem
Seifer48 said:
So, I went through the instructions and odin told me flash failed, the phone reported back that it had no partition structure in the download screen. Now the phone is stuck at a completely black screen regardless of what I do. Odin wouldn't recognize it at first till I tracked down the missing driver (Qualcomm HS-USB QDLoader 9008), now Odin picks it up again but never moves past <ID:0/003> SetupConnection.. Any ideas? I can't seem to get it to take any flashes whatsoever... I'm currently trying various drivers to see if that is the issue...
Click to expand...
Click to collapse
When you make a post like this, you should reference EXACTLY which instructions you are talking about. Referring simply to "the instructions" is pretty useless - which instructions?
Normally, a black screen means you are dead and hardbricked - however the T989 is not a normal device, so what has happened to you is completely unknown. Especially since no one has any clue how you got to where you are.
If Odin is actually recognizing your device, that's good news.
BTW, process is not to insert battery after plugging in USB usually.
It is:
Ensure your device is off (may need a battery pull and reinsert)
Hold VolUP+DN
Insert USB
Entropy512 said:
When you make a post like this, you should reference EXACTLY which instructions you are talking about. Referring simply to "the instructions" is pretty useless - which instructions?
Normally, a black screen means you are dead and hardbricked - however the T989 is not a normal device, so what has happened to you is completely unknown. Especially since no one has any clue how you got to where you are.
If Odin is actually recognizing your device, that's good news.
BTW, process is not to insert battery after plugging in USB usually.
It is:
Ensure your device is off (may need a battery pull and reinsert)
Hold VolUP+DN
Insert USB
Click to expand...
Click to collapse
Sorry, wasn't thinking that well, I was tired lol. Anyways, it was the Root via Odin instructions that Slayher posted. I was mainly posting to see if anyone had encountered anything like that and if so how they fixed it. I've got a black screen that is unresponsive to everything! At this point I'm just gonna say f it and use a jtag. I appreciate everyones help!
Bricked T989 when rootimg with odin
i got the same problem today.
When using ODIN to implement CWM, ODIN stopped
with failure: "could not complete write"
After this i tried to load the stock Rom with odin.
But i get always the same error.
Does anyone have an idea what is going wrong?
Is there a possibility to rebuild the ROM from SDcard?
Thanks for any help
I was installing a kernel with odin and pulled out the battery by mistake. now it wont boot or go into download mode.
I cant seem to find anything relating to bricked epic touchs that wont boot or go into download mode. most people who have problems can at least still go into download mode.
is this GG for me?
---------
Does this guide apply to my epic touch? I dont see the "two copper pins"...
I cant post youtube link but here is the youtube video code.
D0aoabVtPJ8
If there is no solution, I would like to sell my phone 'as is' on ebay but some personal information is on it. should i even worry since it is bricked?
endofwed said:
I was installing a kernel with odin and pulled out the battery by mistake. now it wont boot or go into download mode.
I cant seem to find anything relating to bricked epic touchs that wont boot or go into download mode.
possibly screwed?
Does this guide apply to my epic touch? I dont see the "two cooper pins"...
youtube link
D0aoabVtPJ8
Click to expand...
Click to collapse
A jig will get I into download mode then you can flash Back to stock....it is not bricked unless you were flashing international ROM....http://lmgtfy.com/?q=Samsung+USB+jig
Sent from my SPH-D710 using xda premium
similiar problem
I tried to upgrade to 4.03. but i realized ( at the worse possible time) that the pit and other files for it were for another phone. Now I can't connect to usb or start my phone. It says there was an issue upgrading the firmware. But I can however get into Odin/Download mode on my phone still. Is there anyway to fix this through an SD card install?
http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
I accidentally flashed the t989 pit. Hard bricked where it wouldn't even power on. These guys were able to jtag my device back to life. Had my phone back within a week. They have a forum on XDA somewhere if you want more feedback. If you decide to sell "as-is" PM me.
Deleted
Delete post
mortalitas91 said:
I tried to upgrade to 4.03. but i realized ( at the worse possible time) that the pit and other files for it were for another phone. Now I can't connect to usb or start my phone. It says there was an issue upgrading the firmware. But I can however get into Odin/Download mode on my phone still. Is there anyway to fix this through an SD card install?
Click to expand...
Click to collapse
Unfortunately my friend your phone is bricked. I have seen this numerous times in the last couple of months and the only way to recover your device is a jtag service, as someone mentioned above. The ROM you flashed is most likely an international version which is definitely NOT compatible with our device. The bootloader disables the usb port which in turn causes for you to not be able to connect to your computer. You can test this by going into download mode, and if you do not hear any dings when you plug into the computer, there is no chance. Most likely, your bootloader has either been corrupted or usb has been disabled.
I purchased a jig tool off ebay, that wont solve the problem?
endofwed said:
I purchased a jig tool off ebay, that wont solve the problem?
Click to expand...
Click to collapse
Hey endofwed, my last post was for mortalitas91 he has a different set of circumstances than you. A jig should work in your case. Do you have the link to which file you tried to flash?
Both OP's and the second guy's phones are fukt. Sorry for the bluntness but Jtag is the only hope for both. Mobiletechvideos. Google search.
---------- Post added at 08:27 PM ---------- Previous post was at 08:26 PM ----------
endofwed said:
I purchased a jig tool off ebay, that wont solve the problem?
Click to expand...
Click to collapse
Purty sure the answer is a no.
Sup Indrid!!!! Hey endofwed I have to ask, how did you accidentally pull out the battery in the middle of the flash by mistake.
It was on my first Vibrant didn't pull it fell out. Kernel flash also, No boot no download no lights = brick.
Sup Jason.
---------- Post added at 11:22 PM ---------- Previous post was at 11:16 PM ----------
I sofar have totally bricked at least one of all versions of Phones I've had in the past. But sofar this phone is rock solid. And I consider myself a abuser. Power using is for pussys.
Is it just me or does it seem like alot of people are brickin their devices lately.
Sent from my SPH-D710 using XDA Premium App
From what I've noticed is most,no offense, are plp coming from HTC. It is quite different. Slight learning curve. Ya just gotta read read and read some more.
thanks guys..
mortalitas91 said:
I tried to upgrade to 4.03. but i realized ( at the worse possible time) that the pit and other files for it were for another phone. Now I can't connect to usb or start my phone. It says there was an issue upgrading the firmware. But I can however get into Odin/Download mode on my phone still. Is there anyway to fix this through an SD card install?
Click to expand...
Click to collapse
When you say you can get the phone into download mode does the computer recognize it then? If so it is most definitely NOT bricked. I had the same situation happen to me when I first rooted I flashed a rom for the galaxy I9100 thinking it was my phone because thats what it says when you turn it on. Turned out to be wrong and I couldnt connect through usb when the phone was booted either and couldnt acess my sd card. I could however get into recovery and acess the internal storage but that didnt do me any good because I had no roms on there. I was also able to get into odin mode so I just flashed back to stock through that. If you can connect through odin you are golden!
i think that is what i did. i flashed the ICS rom for the GT-i9100 . I can get it into odin mode (power button volume down) and factory mode with my usb jig. but it won't connect through usb. I saw something earlier about some king guy fixing that. but i haven't found out the instructions for it. ~ Mortalitas91
mortalitas91 said:
i think that is what i did. i flashed the ICS rom for the GT-i9100 . I can get it into odin mode (power button volume down) and factory mode with my usb jig. but it won't connect through usb. I saw something earlier about some king guy fixing that. but i haven't found out the instructions for it. ~ Mortalitas91
Click to expand...
Click to collapse
Unfortunately my friend your device is definitely bricked. You are not the first person to flash this ROM, it has been happening alot lately. The only solution is to jtag the phone or head on over to sprint.
Sent from my SPH-D710 using XDA Premium App
Indrid Cole said:
From what I've noticed is most,no offense, are plp coming from HTC. It is quite different. Slight learning curve. Ya just gotta read read and read some more.
Click to expand...
Click to collapse
That's me, for sure. HTC user for years, and the difference is minor, but Incredibly important.
Best thing I did was to spend at least a week learning the difference between the two, browsing the f*ck out of this forum, before flashing Anything. Qbking77 was a Huge help with his videos.
Sent from my calculator watch.
kingdazy said:
That's me, for sure. HTC user for years, and the difference is minor, but Incredibly important.
Best thing I did was to spend at least a week learning the difference between the two, browsing the f*ck out of this forum, before flashing Anything. Qbking77 was a Huge help with his videos.
Sent from my calculator watch.
Click to expand...
Click to collapse
And that my friend is exactly what you should do before you start flashing!
kingdazy said:
That's me, for sure. HTC user for years, and the difference is minor, but Incredibly important.
Best thing I did was to spend at least a week learning the difference between the two, browsing the f*ck out of this forum, before flashing Anything. Qbking77 was a Huge help with his videos.
Sent from my calculator watch.
Click to expand...
Click to collapse
Ya same here and it definitely does seem like allot of people are bricking lately! It is because of samsungs tricky model numbers. Like I said in a previous post I almost bricked my phone too I flashed a rom for the GT I9100 but luckily Odin recognized my device still! Also Qbking is the man even though now I am at the point where I am 100% sure I know how to flash I still just watch his videos before I do just to be 110% sure. He DEF is the man!
I have been running several rooted roms on my gs3 for a while and have been enjoying the phone very much. Today I decided I would switch from cm10 to slim. I booted into twrp and flashed the incorrect rom (I flashed the i9300 and I should have flashed the d2att, though it claimed the flash was successful)
I know that was stupid and I am aware that I should have read more carefully, etc.
So after searching a few threads it looks like I just bricked my phone and will have to send it in.
But just for completion sake, here is what I see.
-The phone will not boot up
-if I plug the phone into my computer I see a device called "qhsusb_dload" under device manager
-if i hold down+home+power when booting up, the phone does not go into download mode
Any help? advice?
scales11 said:
I have been running several rooted roms on my gs3 for a while and have been enjoying the phone very much. Today I decided I would switch from cm10 to slim. I booted into twrp and flashed the incorrect rom (I flashed the i9300 and I should have flashed the d2att, though it claimed the flash was successful)
I know that was stupid and I am aware it was stupid and I should have read more carefully, etc.
So after searching a few threads it looks like I just bricked my phone and will have to send it in.
But just for completion sake, here is what I see.
-The phone will not boot up
-if I plug the phone into my computer I see a device called "qhsusb_dload" under device manager
-if i hold down+home+power when booting up, the phone does not go into download mode
Any help? advice?
Click to expand...
Click to collapse
I'm very sorry to report that you are bricked...
On a side note, that qhsusb_dload is some type of download we haven't been able to communicate with... Possibly in the future, unbrick methods will surface using that connection... You need Jtag repair...
Quasimodem said:
I'm very sorry to report that you are bricked...
On a side note, that qhsusb_dload is some type of download we haven't been able to communicate with... Possibly in the future, unbrick methods will surface using that connection... You need Jtag repair...
Click to expand...
Click to collapse
Does this site offer any relevant info?
http://smyl.es/samsung-galaxy-iii-s...ocument-how-to-repair-soft-bricked-galaxy-s3/
EDIT:
Also, are there QHSUSB_DLOAD drivers or is that just the GS3's way of saying "nice job idiot, you screwed me over"? I cannot seem to find them if they do exist...
scales11 said:
Does this site offer any relevant info?
http://smyl.es/samsung-galaxy-iii-s...ocument-how-to-repair-soft-bricked-galaxy-s3/
EDIT:
Also, are there QHSUSB_DLOAD drivers or is that just the GS3's way of saying "nice job idiot, you screwed me over"? I cannot seem to find them if they do exist...
Click to expand...
Click to collapse
That's for the I9300, but with the right files, I747 files, and that method, it's probably able to bring it back... Unzip a stock .tar and see if all of those exist...
There's got to be drivers for it, but none that have surfaced... Most likely internal Samsung stuff, and they just click a couple buttons to unbrick...
Try installing QPST version in the IMEI thread, it may install a driver... If it does, you can establish a COM port connection, and POSSIBLY, through methods not been done already bring it back...
And this is all hypothetical....
---------- Post added at 01:17 PM ---------- Previous post was at 01:12 PM ----------
revised my post some
Quasimodem said:
There's got to be drivers for it, but none that have surfaced... Most likely internal Samsung stuff, and they just click a couple buttons to unbrick...
Click to expand...
Click to collapse
Well I found some drivers and now the device appears as a usb to serial (COM3) titled "Qualcomm -HS-USB QDLoader 9008". Seems promising?
scales11 said:
Well I found some drivers and now the device appears as a usb to serial (COM3) titled "Qualcomm -HS-USB QDLoader 9008". Seems promising?
Click to expand...
Click to collapse
Nope. This was a problem even at the Nitro HD forums, you got QHSUSB_DLOAD you're screwed. I remember one of us could make a connection, but it was raw RAM write/read; we'd have to locate the exact address for the boot image and system IMG in order to revive it. Better off JTAGging, I think Samsung may do it for free. I know LG did.
Sent from my SGH-I747 using xda premium
I see. Well I also found this thread:
http://forum.xda-developers.com/showthread.php?t=1727443&page=3
but it seems like most are able to get their phone to download mode. I have tried to boot with buttons held, but have not had luck, just see a black screen. I could try making a jig.
scales11 said:
I see. Well I also found this thread:
http://forum.xda-developers.com/showthread.php?t=1727443&page=3
but it seems like most are able to get their phone to download mode. I have tried to boot with buttons held, but have not had luck, just see a black screen. I could try making a jig.
Click to expand...
Click to collapse
That's for if you can get into bootloader mode... go and get a stock ODIN for your phone and use 7zip to unpack it... see if it has all those files, boot, csc, phone, etc...
Quasimodem said:
That's for if you can get into bootloader mode... go and get a stock ODIN for your phone and use 7zip to unpack it... see if it has all those files, boot, csc, phone, etc...
Click to expand...
Click to collapse
I see...
aboot.mbn
boot.img
cache.img.ext4
NON-HLOS.bin
recovery.img
rpm.mbn
sbl2.mbn
sbl3.mbn
system.img.ext4
tz.mbn
Those files could possibly get u going with JTAG...
Not sent from your phone...
Quasimodem said:
Those files could possibly get u going with JTAG...
Click to expand...
Click to collapse
Nope, and they dont. Any other suggestions?
Quasimodem said:
Not sent from your phone...
Click to expand...
Click to collapse
???
scales11 said:
Nope, and they dont. Any other suggestions?
???
Click to expand...
Click to collapse
So u performed JTAG but had a warranty?
Not sent from your phone...
Quasimodem said:
So u performed JTAG but had a warranty?
Not sent from your phone...
Click to expand...
Click to collapse
I do not have the equipment to perform a JTAG. I dont know what you mean by warranty.
Then u can't bring it back without jtag
Not sent from your phone...
hi, i was reading about bootloader that it has to be unlocked in order to flash custom roms
i did download ez unlock from play store and did unlocked the boot loader but it was not recognizing at status even after the operation (status unknown)
i have i747M rooted
now i powered off the phone wanting to save the rom(again) thru CWM but it wont boot for nothing even pluged charger is not recognized
i have saved once the image so i have it on my sd
what can i do to get my phone back to life?
thanks for your help
Well, if you would have read anything, ez unlock is for verizon only. So, unless your phone shows any sign of life, you need to jtag.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
i realized after read some more but never thought it will die after reboot
anywaw phone is totally dead no sign at all
were do i find some step by step to debrick
i found some info but not for i747m
i wanna do it right this time
thanks
JTAG is best left to the pros unless you are familar with it. I believe user AdamOutler does it as well as mobiletechvideos.com
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
my friends anybody can tell me i can flash the bootloader with odin ?
i have a copy of the bootloader i guess i did before installing CWM only thing is on the phone internal storage that i cant acces
is there a way of accesing the internal storage of my phone as bricked?
if i plug the phone thru usb it gives me the qhusb dload driver missing
can i use odin to flash the bootloader if i can retreive it from my internal storage?
or is there a file i can download for i747m?
or if the only way is jtag i can do it myself just cant find my way to info
thanks for any info
adika9 said:
my friends anybody can tell me i can flash the bootloader with odin ?
i have a copy of the bootloader i guess i did before installing CWM only thing is on the phone internal storage that i cant acces
is there a way of accesing the internal storage of my phone as bricked?
if i plug the phone thru usb it gives me the qhusb dload driver missing
can i use odin to flash the bootloader if i can retreive it from my internal storage?
or is there a file i can download for i747m?
or if the only way is jtag i can do it myself just cant find my way to info
thanks for any info
Click to expand...
Click to collapse
If you can't boot into download or restore, and if odin doesn't recognize, I can almost guarantee you that you have hard-bricked your s3. Your bootloader is messed up, and can only be restored through JTAG. For you to de-brick it yourself, you'll need to shell out a couple hundred dollars to buy the equipment, or you can send it to someone who offers the service for a smaller fee. If you need some suggestions, pm me.
i found driver for the phone so i guess it communicates with odin 1.85
i would like to try flashing a boot image for my phone I747MVLALH1 i think this is for virgin(bell)
anybody have one ?or know were i can download one?
i really have to try anything to get my phone back to life as i have some important data that i need asap
thanks
seriossly nobody have a solution for my problem other than buyng a riff box or sending it for repair?
im really interested to try things
thanks
adika9 said:
i found driver for the phone so i guess it communicates with odin 1.85
i would like to try flashing a boot image for my phone I747MVLALH1 i think this is for virgin(bell)
anybody have one ?or know were i can download one?
i really have to try anything to get my phone back to life as i have some important data that i need asap
thanks
Click to expand...
Click to collapse
So your phone shows up in odin?
adika9 said:
seriossly nobody have a solution for my problem other than buyng a riff box or sending it for repair?
im really interested to try things
thanks
Click to expand...
Click to collapse
Can you put your phone in download mode or in Clockwork mode? If yes you can download firmware HERE. Good luck
adika9 said:
seriossly nobody have a solution for my problem other than buyng a riff box or sending it for repair?
im really interested to try things
thanks
Click to expand...
Click to collapse
I don't see how you don't understand after all the replies... If your phone shows NO sign of life, (I.e. no download mode) You MUST either JTAG or wait for the SD/Hardware hack one of the Devs is working on.
That's it. End of story.
Sent from my SGH-I747 using xda app-developers app
im not sure if having the qualcomm driver installed will communicate with odin
only odin that recognizez the phone is version 1.85 and the port is with yellow but it wont go past msg "setup connection" when trying to flash
so i know that jtag is the sollution but im wondering if there is other solution than jtag
i found a post in the i9300 section that it could be unbricked with a procedure but im not sure its aplicable to i747m
anybody tryed to unbrick a hardbrick i747m other than jtag with riffbox ?
thanks
RPelham said:
I don't see how you don't understand after all the replies... If your phone shows NO sign of life, (I.e. no download mode) You MUST either JTAG or wait for the SD/Hardware hack one of the Devs is working on.
That's it. End of story.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
well i do understand a lot of things but if the replyes were :"u cannot solve it without JTAG or there is a fix in the works but not done yet" it would be better understood
the fact is i really wanted to try things that maybe other members dont even wanna touch
I'm assuming you have but doesn't get explicitly stated. But you have tried pulling batter. Putting back in then hold down the volume down key, home button and power but then after 2 seconds phone should vibrate so u let go of power button but continue holding the other 2.
Or the same method but holding power up.
To get you into either download or recovery mode.
Sent from my SGH-I747 using xda app-developers app
zerogood said:
I'm assuming you have but doesn't get explicitly stated. But you have tried pulling batter. Putting back in then hold down the volume down key, home button and power but then after 2 seconds phone should vibrate so u let go of power button but continue holding the other 2.
Or the same method but holding power up.
To get you into either download or recovery mode.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
thanks for this info but my phone got hardbricked because i unlocked the bootloader by mistake and it got corrupt i guess, and none of those actions work
try this http://forum.xda-developers.com/showthread.php?t=2549068
i was looking to fix unkown baseband on my phone i flash it with baseband file using odin but no luck, after i flash with stock fimware and modem and then root the phone with cfroot and then i try restoring efs folder, idecide to restore it back to stock fimware and pull the battery out to put phone in download mode but it wont power on only appear as Qdloader 9008
What device are we talking about, and what modem did you flash?
t-mobile m919 i flash the modem from http://forum.xda-developers.com/showthread.php?t=2282342
damond said:
i was looking to fix unkown baseband on my phone i flash it with baseband file using odin but no luck, after i flash with stock fimware and modem and then root the phone with cfroot and then i try restoring efs folder, idecide to restore it back to stock fimware and pull the battery out to put phone in download mode but it wont power on only appear as Qdloader 9008
Click to expand...
Click to collapse
Hi. It's a little difficult to follow you with the run on sentences, so let me start with the basics.
I'm not sure what you have installed on your phone at the moment regarding Firmware, modem and ROM.
If you can power up and look in Settings, you can tell me. If not, follow these steps:
- download the following Samsung Stock Firmware, if you have not done so already.
http://samsung-updates.com/device/?id=SGH-M919&details=Galaxy_S_4_T-MOBILE
- verify the MD5 Checksum to see you have a match.
- open up ODIN on your pc.
- place device in ODIN mode, connect via usb cable (make sure the cable is a good cable) and that ODIN 'Com' recognizes device.
- place the Samsung tar md5 file in the PDA box.
- check Auto reboot & time reset (I forgot what it exactly says) boxes.
- press Start and wait till install completes, and S4 Reboots.
See how that goes.
The above will get you back to stock, then you can install custom recovery and root afterward if you want.
Use Triangle Away if you want to reset your counter, but you must be stock and rooted to do so. Usually resetting counter is not necessary unless you are sending your device back for warranty, etc.
odin not reconizing the phone , the com port appears as Qualcom HS- USB QDLoader 9008
If it won't turn on, your gonna have to send it in for service. Same thing happened to me last month, the replaced the pcm board I believe on mine
Sent from my SGH-M919 using xda premium
damond said:
odin not reconizing the phone , the com port appears as Qualcom HS- USB QDLoader 9008
Click to expand...
Click to collapse
I came across this thread:
http://forum.xda-developers.com/showthread.php?t=1536354
While it is not about your device, the discussion in the linked thread is about an issue that may be similar to yours. You can read it to see if there is a relationship.
I've read all 4 pages.
There is a file below:
QHSUSB
Which I think you need to find for your device. I believe it is a Driver that you are missing. If this is what you need, you need the correct driver. I'm uncertain if the file linked in page 4 is the one you need. But googling QHSUSB and bricked Samsung S4, etc. may help you.
Again, I think the above may set you down the right path to help with your issues, but I'm not 100% certain, but I'm just researching to try to help you out.
This may avoid you having to jtag your device, but again, research the above, and see where it leads.
Edit:
Just in case it's needed.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair/
You may also want to read this to get a better idea of what your issue probably is:
https://developer.qualcomm.com/comment/6221#comment-6221
well it seems to be my solution is jtag, so im going to order a jtag
damond said:
well it seems to be my solution is jtag, so im going to order a jtag
Click to expand...
Click to collapse
You'll have it back before you know it
Does the device turn on at all? Mine was hard bricked, and Samsung fixed mine without issues
Sent from my SGH-M919 using xda premium
damond said:
well it seems to be my solution is jtag, so im going to order a jtag
Click to expand...
Click to collapse
Don't order J Tag call Samsung tell them your S4 is not turning off they will send u shipping label on your email ship phone in 4 business days u will get your phone back. It happen to me 3 times 2 on my S3 by flashing wrong roms by my brother. and s4 for modem
i allready fix the phone using jtag, but i found this software if anyone have this issue they can try with this