Koodo Community

Community

Solved

S3 I747M dead


S3 I747M dead Win7 See it as 8960 Qualcomm HS-USB QDLoader 9008 But qpst can talk to it but but cant reloadthe firmware to it tried everything no other tools will detect or chat to it i found the default firmwares for it i747m 2dcan work too but had bad flash missing boot far can tell is there a way fix it with no theres a microsd fix but dont have a sd card to use only usb and cant find the proper xml files to reprogram it to flash stock back in and no does not boot up into dl mode buttons all dead just it in dl mode qdl in pluged in windows oden or kies does not detect it or work

36 replies

Userlevel 7
Sounds like your Last option is to grab an SD card and try that fix. How Long have you had this device?
under year boot still locked so warinty should still be good but i rather have the fix so can do it myself any time hate bringing it in and waiting weeks dont have the $$ to get a 16gig microsd card there like 70-80$ here
Userlevel 7
SaintJohnPublic wrote:

under year boot still locked so warinty should still be good but i rather have the fix so can do...

Just buy a small card?
SaintJohnPublic wrote:

under year boot still locked so warinty should still be good but i rather have the fix so can do...

has to be 16gig or larger to hold the firmware to boot to restore
Userlevel 7
SaintJohnPublic wrote:

under year boot still locked so warinty should still be good but i rather have the fix so can do...

Not to be argumentative but my S2x firmware was about 385mb, even cyanogenmod firmware isn't that large.
SaintJohnPublic wrote:

under year boot still locked so warinty should still be good but i rather have the fix so can do...

but there should be some files out there to restor using the usb computer still can talk to it useing qpsd but cant find the xml files to restore it all can find or odens and kies complete garbage never worked even when was working just want the official firmware with the xml files to reprogram it
Userlevel 7
SaintJohnPublic wrote:

under year boot still locked so warinty should still be good but i rather have the fix so can do...

That's strange, with the proper drivers, windows and adb should be your friend. Odin and sammobile to flash OEM firmware should work.
SaintJohnPublic wrote:

under year boot still locked so warinty should still be good but i rather have the fix so can do...

And firmware is little over gig and 1/2 so no ota is big lol
nope windows sees it as Qualcomm HS-USB QDLoader 9008 ( QHSUSB_DLOAD ) but oden kies rest need the firmwares boot witch is not saplied publicly witch is not what windows sees it as when bootloader is working proper on phone dload is the chips hard built in witch is replaced by the firmware once loading the missing the boot but phones missing boot.img and cant reload it with out proper xml files to load the firmware
Userlevel 7
SaintJohnPublic wrote:

nope windows sees it as Qualcomm HS-USB QDLoader 9008 ( QHSUSB_DLOAD ) but oden kies rest need t...

You can get the proper firmware at SamMobile.com You're unable to get it into download mode?
SaintJohnPublic wrote:

nope windows sees it as Qualcomm HS-USB QDLoader 9008 ( QHSUSB_DLOAD ) but oden kies rest need t...

sam is for odens and its stuck in qpst bootloader mode and can not be changed phone does not turn off less bats pulled soon put it goes back to that mode and screens dead buttons dont do a thing but windows can see it qpst can talk to it only tool that can but it needs the xml to load the incription the chip uses only the tec have
Userlevel 7
SaintJohnPublic wrote:

nope windows sees it as Qualcomm HS-USB QDLoader 9008 ( QHSUSB_DLOAD ) but oden kies rest need t...

Buy a card or try sending it in for warranty, if Odin isn't seeing it then you're not going to get satisfaction otherwise.
SaintJohnPublic wrote:

nope windows sees it as Qualcomm HS-USB QDLoader 9008 ( QHSUSB_DLOAD ) but oden kies rest need t...

just dont get why so hard to get the xml files that tell the phone while files to load were it controls what firmware files goto each partion size of each ect... but guess there being to hush hush dont want people help them selfs
Badge +4
The bootloader is toast and the sdcard solution is hit and miss. The only other options are to find someone proficient with JTAG(ing) the device which will cost you money or send the device in for warranty, which would be my recommendation. The QPST bootloader files you need are supplied to the manufacturer and are not intended for re-distribution to end users.
i can get the xml for other phones easy just not the g3 it seems be way behind no ones bothering to work on them
jtag is hardware flashing ya have to buy it like the microusb dongle jig thats resets u phone to download mode but dont have that eather can make one with parts but thats a hit or miss also
Badge +4
SaintJohnPublic wrote:

jtag is hardware flashing ya have to buy it like the microusb dongle jig thats resets u phone to...

Like I said before, send it in for warranty.
Userlevel 7
SaintJohnPublic wrote:

the sim card fix is no go didnt work pooring rain out so not like making it out eat cause i have ...

Wow, well glad we tried to help you. Thanks for the insult. Plenty of people come here daily and leave with solutions so I'm going to assume its just a anomaly that we can't help you fix what YOU did to YOUR device. I'm sorry you feel that way about the help we tried to provide for your modified device. Next time leave it stock so you won't have these issues. Signed, the dumb people who tried to help you.
Badge +4
I've spent the last hour or two reading up on how to un-brick a hard-bricked S3 and nothing points to using .xml files - period. JTAG is the preferred method and I've already explained that to you. You might be able to build the jig, but you need the micro-code to access the board/chip and specialized software that rebuilds the partition structure and places the device in download mode. Cut your losses and either send your device in for warranty (I'm getting tired of telling you this now for the third time) or let this be a learning experience and buy yourself a new phone. No one at Koodo or those that volunteer their time to help out can be held responsible for your actions. Please check your attitude at the door, thank you.
Userlevel 7
Badge +4
rikkster wrote:

I've spent the last hour or two reading up on how to un-brick a hard-bricked S3 and nothing point...

Would it even be covered under warranty?
Userlevel 5
rikkster wrote:

I've spent the last hour or two reading up on how to un-brick a hard-bricked S3 and nothing point...

I highly doubt it.
Userlevel 7
rikkster wrote:

I've spent the last hour or two reading up on how to un-brick a hard-bricked S3 and nothing point...

Technically no but I suppose. It would depend on how much time a Sammy rep takes to really examine the device.
Badge +4
rikkster wrote:

I've spent the last hour or two reading up on how to un-brick a hard-bricked S3 and nothing point...

Michael claims the S3 is under a year old with a locked bootloader, the latter part of which I seriously doubt, but I have read several reports where people have fubar'd their device and Samsung issues the customer a new phone, so it could go either way.
rikkster wrote:

I've spent the last hour or two reading up on how to un-brick a hard-bricked S3 and nothing point...

i know it's been 7 months but what files do i need to download to fix my s3 with the same issue/problem as michael has/had i do have the micro sd card as well
Badge +4
rikkster wrote:

I've spent the last hour or two reading up on how to un-brick a hard-bricked S3 and nothing point...

There is an article I came across that uses a different method, though the author openly admits he has yet to test this on his phone, but it may be a starting point. The author also claims he has files for the Snapdragon S4 Dual Core 1.5 GHz Qualcomm 'MSM8960' chipset. No guarantees any of this will work and you do so at your own risk. http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html http://cellphonetrackers.org/wp-content/uploads/8x60_msimage.mbn_.txt MicroSD card method - the AT&T variant looks to be the same processor-wise, minus the 'M' designation, ask anyway to be certain. http://forum.xda-developers.com/showthread.php?t=2345860

Reply