Develop Bugs

i747 Hard Bricked: QHSUSB - DLOAD : Needing a debrick.img

SGH-I747 (4.1.2 i747's please)/ SGH-i747m( If you have a official 4.3 i747m, please post a debrick.img) only:
Hi, I recently hard bricked my phone into QHSUSB DLOAD and I am going to attempt repairing it through the SD Card boot method.
http://forum.xda-developers.com/editpost.php?do=editpost&p=47431259
I need a debrick.img to flash to the SD card in a Linux OS.
I would have gotten it myself but my phone is obviously dead. I found one before on XDA, but it did not work on my device and it gave me an error in the Linux terminal when it should not have.
-snip-
The end of the 3rd boot-loader stage in mmcblk0 is at 77.3 megabytes. If you are going to help out using your device, try to refrain from uploading an image with a different ROM other than root.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=2m count=81054925
The count is the amount of bytes. I am not sure if it is meant to be 1000 bytes=kilobyte or 1024 bytes=kilobyte. The count above is for 1024.
I need someone to install the Galaxy S III unified toolkit, and pull the first 7 partitions from mmcblk0 ,which is where the third bootloader stage ends.(Don't upload a heavily modified device please) http://www.skipsoft.net/?page_id=213 Once you get the files, PM me.
If anyone has a link to a working one, please post that. If you want to get your own image to help me, go ahead.
Thanks guys.

Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.

99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
what happened?

winosxbuntu said:
what happened?
Click to expand...
Click to collapse
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.

99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
99ytrewq9111 said:
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.
Click to expand...
Click to collapse
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:

winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Thanks for that link! It looks very promising, and I can probably find a stock boot.IMG in there. I will work on tomorrow. If I succeed, I'll edit the OP and make a debrick guide for this drvice forum. A word of advice, try not to mess with your bootloader or you end up like me

winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Hi, the toolkit didn't fix my phone, but its defiantly a step up. Since I'm assuming you have the toolkit installed that you suggested it, could you do me a favor?
It will be a bit easier using the toolkit to extract the partition files. If you could pull the first 7 partitions from "mmcblk0" of your device through the toolkit, it will probably set the next step to fix my phone. (Assuming you have a 16g i747... I don't really know)
You don't have to do this of course.
Thanks man.

Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app

99ytrewq9111 said:
Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome

winosxbuntu said:
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome
Click to expand...
Click to collapse
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.

99ytrewq9111 said:
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.
Click to expand...
Click to collapse
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172

I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.

Bradkirk said:
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172
Click to expand...
Click to collapse
Did you use an i747 or a i747m device?
If a i747m image works on an i747, it will basically fix all of my problems.

spensa said:
I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.
Click to expand...
Click to collapse
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367

I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Bradkirk said:
I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately that's the download I found that didn't work.
Thanks for trying though

damn! the only other help I can offer then, is that there is a pretty good thread on this over in the d2tmo section. someone there wrote a little tool to easily download the relevant data. might help you on your quest. or at least make it so you could ask someone that doesnt know ADB. best of luck!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

99ytrewq9111 said:
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367
Click to expand...
Click to collapse
when connected to the computer written QHSUSB-DLOAD,

spensa said:
when connected to the computer written QHSUSB-DLOAD,
Click to expand...
Click to collapse
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.

99ytrewq9111 said:
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.
Click to expand...
Click to collapse
I took it to a service to repair

[Q] EZ-Unlock & friend bricked my phone, help needed

My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?

omeadsthename said:
My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
Click to expand...
Click to collapse
yes, take him outside and beat the crap out of him. Then take his money and go get a new phone.
Other than that, I don't know.
Can you access download mode or recovery?

jack man said:
yes, take him outside and beat the crap out of him. Then take his money and go get a new phone.
Other than that, I don't know.
Can you access download mode or recovery?
Click to expand...
Click to collapse
No I cannot, my friend(parklane79) and I actually found a method, it seems promising but i need to try it out first.
im not afforded the link rights yet but the title is "Fixing a bootloader-bricked Galaxy S3 using an SD card (Qualcomm SGS3 variants)" and a more simpler guide for n00bs(although not a complete n00b been doing this for a few years now :good: ) like myself, "[GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG)" but for the second guide you need to grab the i747 debrick.img off the first page of the first guide.

omeadsthename said:
No I cannot, my friend(parklane79) and I actually found a method, it seems promising but i need to try it out first.
im not afforded the link rights yet but the title is "Fixing a bootloader-bricked Galaxy S3 using an SD card (Qualcomm SGS3 variants)" and a more simpler guide for n00bs(although not a complete n00b been doing this for a few years now :good: ) like myself, "[GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG)" but for the second guide you need to grab the i747 debrick.img off the first page of the first guide.
Click to expand...
Click to collapse
Yea tried with a class 10 16g micro sd like a million times and it wont work.and i think its because i dont have the 4.4.2 img if some one could help me out by uploading it. u et the img via busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70

So the phone won't power on at all? Can't get into download or recovery?

are you %100 certain it's the AT&T 4.3 debrick.img? did you put it on the SD card using win32diskimager?

audit13 said:
So the phone won't power on at all? Can't get into download or recovery?
Click to expand...
Click to collapse
The phone won't even vibrate. Wish i could get to DL/Recovery mode. :/
yowski said:
are you %100 certain it's the AT&T 4.3 debrick.img? did you put it on the SD card using win32diskimager?
Click to expand...
Click to collapse
im 100% sure. the issue is tho that i was on 4.4.2 and dont know it an i747(AT&T) 4.3 debrick.img has the same handshake/protocol whatever you want to call it as a 4.4.2 debrick.img I tried it out tho anyways. but in short yes im 100% sure it was a 4.3 debrick img. And yes I did use win32diskimager. I tried once on linux mint but i believe the file corrupted so i just ended up using win32DM. I mean they are supposed to do the same thing, if im not mistaken

omeadsthename said:
The phone won't even vibrate. Wish i could get to DL/Recovery mode. :/
im 100% sure. the issue is tho that i was on 4.4.2 and dont know it an i747(AT&T) 4.3 debrick.img has the same handshake/protocol whatever you want to call it as a 4.4.2 debrick.img I tried it out tho anyways. but in short yes im 100% sure it was a 4.3 debrick img. And yes I did use win32diskimager. I tried once on linux mint but i believe the file corrupted so i just ended up using win32DM. I mean they are supposed to do the same thing, if im not mistaken
Click to expand...
Click to collapse
when you plug it into the computer does anything come up? also, when you plug it in with no battery do you get a red LED?

yowski said:
when you plug it into the computer does anything come up? also, when you plug it in with no battery do you get a red LED?
Click to expand...
Click to collapse
Yes my comp tries to install that one qualcomm driver. and when i plug in without battery a red LED comes on.

omeadsthename said:
Yes my comp tries to install that one qualcomm driver. and when i plug in without battery a red LED comes on.
Click to expand...
Click to collapse
Then you should be able to use a debrick.img. are you using an sd card the same size as your phone's internal memory? if you had it on 4.4.2 then you might need a debrick.img from someone with the same phone on the same network running 4.4.2?

yowski said:
Then you should be able to use a debrick.img. are you using an sd card the same size as your phone's internal memory? if you had it on 4.4.2 then you might need a debrick.img from someone with the same phone on the same network running 4.4.2?
Click to expand...
Click to collapse
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.

omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
sounds like you're stuck until you get that .img file. If you know someone with the same phone you could maybe get them to install 4.4.2 and get the file from them? otherwise keep asking around or wait until 4.4.2 is released for the s3, which might take a while.

yowski said:
sounds like you're stuck until you get that .img file. If you know someone with the same phone you could maybe get them to install 4.4.2 and get the file from them? otherwise keep asking around or wait until 4.4.2 is released for the s3, which might take a while.
Click to expand...
Click to collapse
Unfortunately kids at my high school are afraid of rooting, so xda is basically my only bet. Im just surprised that some sr member hasnt added a debrick img to their threads. I mean its 4.4 and this is android central!

omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
i would help you out but my S3 is currently hard bricked on stock 4.3 and im sending it back to the insurance company once my S4 arrives tomorrow.

yowski said:
i would help you out but my S3 is currently hard bricked on stock 4.3 and im sending it back to the insurance company once my S4 arrives tomorrow.
Click to expand...
Click to collapse
Cant they find out that you are root and hard bricked? like doesnt that void warranty. and if its a 4.3 h brick cant u just use the sd method?

omeadsthename said:
yes i am using same size card. and i have been asking all over for a 4.4.2 debrick img but no one has uploaded.
Click to expand...
Click to collapse
I did, it was on CM 10.2 when i had flashed improper bootloaders and bricked it. I used the sd card to install 4.3, unroot+ reset flash counter then took it out so it went back to bricked. My only fear is that they may some how get it into download mode instead of just replacing the board and see the warranty bit: 1 which isnt able to be reset as it is an e-fuse which is blown when you install firmware without knox.

yowski said:
I did, it was on CM 10.2 when i had flashed improper bootloaders and bricked it. I used the sd card to install 4.3, unroot+ reset flash counter then took it out so it went back to bricked. My only fear is that they may some how get it into download mode instead of just replacing the board and see the warranty bit: 1 which isnt able to be reset as it is an e-fuse which is blown when you install firmware without knox.
Click to expand...
Click to collapse
Are you using the samsung warranty of AT&T? And also if the sd card is working for u cant you just use odin to flash? Or does the sd card not fix any bootloader issues?

omeadsthename said:
Are you using the samsung warranty of AT&T? And also if the sd card is working for u cant you just use odin to flash? Or does the sd card not fix any bootloader issues?
Click to expand...
Click to collapse
im sending in it through bell mobility. it was a replacement phone that i paid the $150 deductable on and has a 90 warranty. I said it was having issues/defective so they sent an s4 as free replacement on the 90 day. I prefer it to be bricked to fit the defective description as well as to decrease the chances of them finding out i had messed with it, the only real sign being "warranty bit: 1" in red on the download screen. I did use odin to flash the current 4.3 stock that it has right now, and i might be able to get it to boot without the card if i flash the bootloaders some more despite having done it twice and the card still being required. Like i said though, i prefer it hard bricked and i've erased every sign other than warranty bit: 1 that i messed with it by installing stock, unrooting, and resetting flash counter.

yowski said:
im sending in it through bell mobility. it was a replacement phone that i paid the $150 deductable on and has a 90 warranty. I said it was having issues/defective so they sent an s4 as free replacement on the 90 day. I prefer it to be bricked to fit the defective description as well as to decrease the chances of them finding out i had messed with it, the only real sign being "warranty bit: 1" in red on the download screen. I did use odin to flash the current 4.3 stock that it has right now, and i might be able to get it to boot without the card if i flash the bootloaders some more despite having done it twice and the card still being required. Like i said though, i prefer it hard bricked and i've erased every sign other than warranty bit: 1 that i messed with it by installing stock, unrooting, and resetting flash counter.
Click to expand...
Click to collapse
hmm i wish i could do that to my phone too. i mean, i dont even know how i would unroot without getting my phone on. but if im this hard bricked they probs cant tell anyways. im guessing?

uz unlock HARD BRICKING S3'S
omeadsthename said:
My friend decided to use the EZ-Unlock app(link below) that unlocks the bootloader for the verizon galaxy s3 on my i747 and well it is now a brick, is there anything i can do to fix this without a JTAG?
Click to expand...
Click to collapse
I DID THE SAME THING ! but i used debrick (i535 vzw 4.3 ) and it pattially worked at least it will recovery and odin but i think it needs to be the 40 mbps type card the black micro would not work for me , then i flashed the wrong recovery and am starting all over but the debrick still getting me into odin thats ware you will sideload the right recovery and firmware ,rom what ever hope ( i even paid for cdma work shop and it aint did jack ) debrick then odin sideload look it up thats the best i got

bricked my i747. calling all pros

Hello people, I randomly tried to flash internation model rom on my i747 model s3
it gave wrong model error so i went and modified asserts in the update file and made it pass the check. but phone wont turn on now. i do get red led when charging it. I know it sounds stupid but i just wanted to give a try (was assuming I would unlock the phone :laugh
anyways i do know that 16gb sd un-brick method. but i was wondering if there's a possible different method.
thanks for your time.

Only paying for a jtag service

looks like SD Unbrick method isn't working either, it's not turning on with unbrick sd. i did do a backup before all this. can anyone help here?

Dont give up. Many people have to run through the sd creation process several times before it worked.
It could also be the sd card you are using.

DocHoliday77 said:
Dont give up. Many people have to run through the sd creation process several times before it worked.
It could also be the sd card you are using.
Click to expand...
Click to collapse
the thing is, all debrick img's posted on threads are for 4.3 and up. my phone was on 4.1.2 with an i747 bootloader.
going to order a usb jig (since diy's failed)

If you are on pre-4.3 firmware, it shouldn't matter what debrick.img you use. But if you do get it to boot it will not let you flash anything older than what the image is.
---------- Post added at 03:31 AM ---------- Previous post was at 03:31 AM ----------
Of course it wouldn't hurt to have a 4.1.2 image.....

troolplay1 said:
the thing is, all debrick img's posted on threads are for 4.3 and up. my phone was on 4.1.2 with an i747 bootloader.
going to order a usb jig (since diy's failed)
Click to expand...
Click to collapse
It is a good idea to have a jig handy. But you many not even need it for that one. The exact same thing happened to me (I747m - Fido).
Just make sure the SD card is the same size as your phone for the image.
I am assuming you already found all the steps? You can pm me if you need the necessary files.

distorsun said:
It is a good idea to have a jig handy. But you many not even need it for that one. The exact same thing happened to me (I747m - Fido).
Just make sure the SD card is the same size as your phone for the image.
I am assuming you already found all the steps? You can pm me if you need the necessary files.
Click to expand...
Click to collapse
I have tried many many debirck img's. both for t999 and i747, for 4.3 and whatnot. today i got the jig in the mail but the try failed, still wont turn on. i lost hope and i feel like sending it to ebay service is my only resort. the sd card i was using was a pixar class 10 16GB. idk what would go wrong with that.
the reason that i bricked it, again, is flashing wrong bootloader.
any help would be appreciated.

Idk bro the international s3 is a whole nother phone, it has a quad core exynos processor while we got a dual core snapdragon, it's got a gig of ram we got 2.... That's too name a few differences.....I think the only way to fix it is by a JTAG.......sorry bout the luck bro

O don't think he's got an international version. Thought he mentioned having an I747 before??
Sent from my SAMSUNG-SGH-T999 using Tapatalk

If you don't mind shipping to Canada I have a riffbox and could fix the issue for you.

The debrick method should work though. If it were me I wouldn't give up just yet. I'd at least try a few more times on every sdcard I could get a hold of. Often doesn't work on the first couple of tries, and AFAIK there's no way to know which sdcards will or won't work. Just gotta keep trying.
It is possible that for some reason this method simply won't work, but it has worked in the past for similar types of bricks.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Any Suggestions? - Bricked AT&T GS3 i747

Hey all, Was wondering if anybody had some time to help me troubleshoot why I cannot for the life of me get this method to work and maybe explain to me a few things that are confusing to me...
Basically my phone is hard bricked:
Samsung Galaxy S3 SGH-i747 (AT&T)
- Began with Stock 4.1.2 (almost %100 positive)
- Attempted flash to 4.4.4 Task650's AOKP ROM (Flashed ok but stuck at boot animation) via CWM
- Attempted reverting back to stock with the file below via Odin but I must have missed a step...
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5
Now I am hard bricked and don't know where to go from here. I've tried several solutions:
- Homemade Jig (didn't work)
- 3 button combo / download mode (doesn't work)
- Odin does not read phone
- Connected to a pc (red power light appears but nothing else)
- SD card method - Using Win32DiskImager to write images to a 16gb class 10 micro sd
- Debrick images used: 4.1.2, 4.1.1, (should i try 4.0.4, 4.3, or even 4.4?)
- How do I tell if the image is writing correctly and partitioning the drive right?
- When the sd card is seen in the computer I see a folder on it named "image" with several files inside it but I don't know how to see partitions
I have screenshots too if you'd like to see them. Let me know if you have any suggestions or have seen anyone with this same issue able to fix it. I'd appreciate it. Thanks.
- Chris

not very knowledgeable about this stuff , but here is a thread (hardbricked 4.1.1) with link to debrick images 4.3/4.4.
http://forum.xda-developers.com/showthread.php?t=2880002
thanks to @DocHoliday77
hopefully someone will come along with some real help.
good luck.
err on the side of kindness

If that firmware was the full firmware, and it appeared to flash, you'll probably need to use the 4.3 debrick.img. also try different sd cards. Many just don't work, where others will.
Look at Tmobiles debrick thread stickied in the development section there. It tells you how to use a Linux liveCD to partition and check the card. The method will work, just use the files from here if you try it.
Chances are, if it doesn't work with the 4.3 image, you'll need a different sd card though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
If that firmware was the full firmware, and it appeared to flash, you'll probably need to use the 4.3 debrick.img. also try different sd cards. Many just don't work, where others will.
Look at Tmobiles debrick thread stickied in the development section there. It tells you how to use a Linux liveCD to partition and check the card. The method will work, just use the files from here if you try it.
Chances are, if it doesn't work with the 4.3 image, you'll need a different sd card though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok thanks. I'm going to attempt this again tonight using an SD card adapter instead of using another mobile device as the adapter to see if that makes a difference. If that doesn't do the trick I will try the LinuxLiveCD method. I'm using a Lexar 16gb Class 10 micro sd card so I don't think it that is the issue but I guess it wouldn't hurt to try a different brand.
Just curious, has anybody here successfully debricked their phone using another mobile device as the sd card adapter?

Not sure about using the mobile device, but you'd be surprised about the sd cards! I've seen Samsung 16GB Class 10 fail for some people, but work for others. It's really odd as there is no rhyme or reason to it. More of a crap shoot than anything from what I can tell.
I've seen generic 32GB class 4 cards work for people who couldn't get a name brand class 10 one to work at all.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Not sure about using the mobile device, but you'd be surprised about the sd cards! I've seen Samsung 16GB Class 10 fail for some people, but work for others. It's really odd as there is no rhyme or reason to it. More of a crap shoot than anything from what I can tell.
I've seen generic 32GB class 4 cards work for people who couldn't get a name brand class 10 one to work at all.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Good to know, but just to clarify when you say it "fails"... what exactly fails - writing the image file, partitioning the card, or does it write everything to the card ok and then just not boot up? I'm just asking so I know what to look for if it ever happens.
Thanks for the responses as I'm still new to this process and this phone and every little thing helps!

It usually appears to create the debrick sd card just fine. It just doesn't work when you try to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
It usually appears to create the debrick sd card just fine. It just doesn't work when you try to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
So, it appears that the issue was using the mobile device as the sd card reader. After writing the debrick file to the same sd card with an actual sd card reader, I am able to boot into the stock recovery. From here, I should just be able to flash a stock ROM to it correct or no?

Ok, which debrick.img did you end up using? If you used 4.3, you must flash the MJB firmware. If it was an older image, you will have a choice.
Either way, if you're ready to update to 4.3, and the recovery you are able to boot into is Twrp or cwm, you can flash this:
https://www.androidfilehost.com/?fid=23269279319197285
It is the full mjb base firmware. does not include recovery or system. After flashing this, you should be able to boot at least recovery and download mode without the sd card. If your rom is intact, you'll be able to boot it as well. If not, choose one and flash it.
If you are not ready to update to 4.3, we will have to find another, older version of what I linked above. Or I can make one if required.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Ok, which debrick.img did you end up using? If you used 4.3, you must flash the MJB firmware. If it was an older image, you will have a choice.
Either way, if you're ready to update to 4.3, and the recovery you are able to boot into is Twrp or cwm, you can flash this:
https://www.androidfilehost.com/?fid=23269279319197285
It is the full mjb base firmware. does not include recovery or system. After flashing this, you should be able to boot at least recovery and download mode without the sd card. If your rom is intact, you'll be able to boot it as well. If not, choose one and flash it.
If you are not ready to update to 4.3, we will have to find another, older version of what I linked above. Or I can make one if required.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok, after playing with the phone for awhile I have found out that I can boot into download mode now. After rebooting, I was able to boot into the stock 4.3 ROM but I noticed I lost root access. Now the problem is I cannot enter the recovery to even flash the file you mentioned above (I flashed CWM via Odin but I can't boot into it). The phone can be seen in Odin now as well. I've done a little bit of research on achieving Root access again but I came across a post that mentioned I could ruin my IMEI number by flashing a "CF-Autoroot" file, should I be worried about doing this now that I'm on 4.3 or am I ok since I didn't use the OTA 4.3 ??
Again, thank you so much for the advise! I'm so glad this phone isn't a brick anymore.

Ok. Since you can get download mode, that changes things.
Boot download mode, remove the sdcard and flash the MJB firmware in Odin. Download here:
http://forum.xda-developers.com/showthread.php?t=2722660
Then, use Towelroot to root the device. (I posted a good guide for this. It should be on page 1 in the Tmobile General section: http://forum.xda-developers.com/showthread.php?t=2793071)
Towelroot is by far the easiest root you'll ever use! Just make sure you read the first two posts before starting!
At this point you should be fully recovered and running stock rooted MJB.
Now before anything else, since you mentioned the imei, backup your NV Data. Very easy!
Install and open Terminal Emulator from the store and enter this:
Code:
su
reboot nvbackup
It'll reboot and create a hidden, permanent, on device backup of your NV data. If corruption is ever detected it'll auto restore during boot, so it essentially protects you from ever losing your imei!
After that, you can do as you wish! If you want to update to 4.4.2 though, I recommend doing that before you root. After flashing MJB, reboot and you should be able to get the official OTA. Then continue with the rest if the instructions above.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Ok. Since you can get download mode, that changes things.
Boot download mode, remove the sdcard and flash the MJB firmware in Odin. Download here:
http://forum.xda-developers.com/showthread.php?t=2722660
Then, use Towelroot to root the device. (I posted a good guide for this. It should be on page 1 in the Tmobile General section: http://forum.xda-developers.com/showthread.php?t=2793071)
Towelroot is by far the easiest root you'll ever use! Just make sure you read the first two posts before starting!
At this point you should be fully recovered and running stock rooted MJB.
Now before anything else, since you mentioned the imei, backup your NV Data. Very easy!
Install and open Terminal Emulator from the store and enter this:
Code:
su
reboot nvbackup
It'll reboot and create a hidden, permanent, on device backup of your NV data. If corruption is ever detected it'll auto restore during boot, so it essentially protects you from ever losing your imei!
After that, you can do as you wish! If you want to update to 4.4.2 though, I recommend doing that before you root. After flashing MJB, reboot and you should be able to get the official OTA. Then continue with the rest if the instructions above.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I flashed the files from the link you posted in Odin and now I am golden! I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs. After seeing that, I checked the system status and it says "OFFICIAL" so I don't really understand why I can't upgrade OTA. I noticed that something I've done has tripped the warranty bit But whatever, I am perfectly fine with staying on 4.3 for now - I didn't see too much to really need to upgrade to 4.4.2 quite yet... although I might try to upgrade again tomorrow and see what happens. I don't really need root at the moment but if I attempt to flash to anything else in the future, I'll give towelroot a shot.
Again, thanks for your help - I owe ya one DocHoliday

CornfedChris said:
.... I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs.
... although I might try to upgrade again tomorrow and see what happens.
Click to expand...
Click to collapse
I've seen reports of this more than once where someone going back to stock initially receives the no updates available msg and then after 24 hrs or so it becomes available. So, your plan sounds good.

CornfedChris said:
I flashed the files from the link you posted in Odin and now I am golden! I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs. After seeing that, I checked the system status and it says "OFFICIAL" so I don't really understand why I can't upgrade OTA. I noticed that something I've done has tripped the warranty bit But whatever, I am perfectly fine with staying on 4.3 for now - I didn't see too much to really need to upgrade to 4.4.2 quite yet... although I might try to upgrade again tomorrow and see what happens. I don't really need root at the moment but if I attempt to flash to anything else in the future, I'll give towelroot a shot.
Again, thanks for your help - I owe ya one DocHoliday
Click to expand...
Click to collapse
Right on! Glad to hear you got it all fixed up! If that update does become available later, please let us know. I've been telling several people to wait a day, but I haven't heard if it actually came through for any of them yet.
If you do decide to root in the future, just don't forget about that backup!
Sent from my SAMSUNG-SGH-I747 using Tapatalk

So tonight while I was watching TV I looked down at my phone and noticed it decided to just go ahead and update itself to 4.4.2, haha. So apparently there's an auto-update defaulted in the settings somewhere. I haven't really noticed too many differences yet but I'm liking it so far. :good:

Gt-i9190 hard brick

Hey guys, my friend gave me this S4 mini in order to flash it turn out it's hard bricked can't turn on or go download/recovery mode. Can't be detected by Odin or adb, my pc detect it as "qhsusb_dload" so i did some researches on this and other forums and figuered it's not yet dead, i found the debrick.img method and it didn't work for me.
Is there any other method if so please help me.
Btw this is my first post here and i'm not native english so sorry for any mistakes.

Bambinou said:
Hey guys, my friend gave me this S4 mini in order to flash it turn out it's hard bricked can't turn on or go download/recovery mode. Can't be detected by Odin or adb, my pc detect it as "qhsusb_dload" so i did some researches on this and other forums and figuered it's not yet dead, i found the debrick.img method and it didn't work for me.
Is there any other method if so please help me.
Btw this is my first post here and i'm not native english so sorry for any mistakes.
Click to expand...
Click to collapse
Try other debrick images, even if you have the right one it may take several attempts before boot. Try battery pulls too ...
Sent from my Galaxy S4 Mini using XDA Labs

IronRoo said:
Try other debrick images, even if you have the right one it may take several attempts before boot. Try battery pulls too ...
Sent from my Galaxy S4 Mini using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply, can you please send me a debrick image for the i9190 because i can't find it anywhere, i found only one i tried multiple time doesn't seem to work.

Bambinou said:
Thanks for the reply, can you please send me a debrick image for the i9190 because i can't find it anywhere, i found only one i tried multiple time doesn't seem to work.
Click to expand...
Click to collapse
Sorry I don't have a I9190 debrick as I have a I9195.
Have you seen the one linked to on Valentel I919x debrick thread by @ReachStacker from kitkat 4.4.2
Link is
https://drive.google.com/file/d/0B1fY3aAlMnLUMWk4bDZvZ2xSNEU/view
Also are you using a 16Gig series 10 SD card, some have found it's the only card that works ....... Through others have got 32Gig till work
Sent from my Galaxy S4 Mini using XDA Labs

IronRoo said:
Sorry I don't have a I9190 debrick as I have a I9195.
Have you seen the one linked to on Valentel I919x debrick thread by @ReachStacker from kitkat 4.4.2
Also are you using a 16Gig series 10 SD card, some have found it's the only card that works ....... Through others have got 32Gig till work
Click to expand...
Click to collapse
Thank you so much for the link, i think i'm not so great in searching :silly:
I tried with a 32g card -the first time- not sure which class it's not mine, i'll get a 16g class 10 soon and see how that works out.

Bambinou said:
Thank you so much for the link, i think i'm not so great in searching :silly:
I tried with a 32g card -the first time- not sure which class it's not mine, i'll get a 16g class 10 soon and see how that works out.
Click to expand...
Click to collapse
the size and the class of the SD are probably not so important but some people have found success following this. More often, eg on the S3 debrick thread, they say they had to try the whole process ie incl set up SD card multiple times before it worked, in some cases. You must have a debrick image that has the same or newer boot loader than the one on your phone. AFAIK
But there is no guarantee it will work even if you do everything right.....
Sent from my Galaxy S4 Mini using XDA Labs

Bambinou said:
Hey guys, my friend gave me this S4 mini in order to flash it turn out it's hard bricked can't turn on or go download/recovery mode. Can't be detected by Odin or adb, my pc detect it as "qhsusb_dload" so i did some researches on this and other forums and figuered it's not yet dead, i found the debrick.img method and it didn't work for me.
Is there any other method if so please help me.
Btw this is my first post here and i'm not native english so sorry for any mistakes.
Click to expand...
Click to collapse
I almost have the same thing,you should use odin installing that serrano thing.then it will open..worked for me.