yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] Azeedc:
Check my answer to your post , go back 2 posts and please read it. This method works for some people but not for everybody.

Loading and international i9300 in place of i747m will definitely kill the device and will not boot or worse.

If your phone is totally dead (does not turn on), no charge, red-green light or buzzing when you insert the battery,

and connect to computer, this method will probably not work and you may have to try Jtag to revive it.

.
[Sprint Samsung Galaxy S III] me_plz:
I am in the same boat as Azeedc with the boot recovery mode... on the phone and odin failing for the same reason but the link provided doesn't explain how to fix the error. Just so we're on the same page the does dl mode from the image looks exacly like dl mode on a non-bricked device or is the one that Azeedc typed what everyone else is getting?
[Sprint Samsung Galaxy S III] Azeedc:
And here lies the crux of the question.....

I asked on previous post for somebody that is going through the process to include a picture of the screen if the phone boots from SD card,

and specify if the procedure allowed them to press any buttons sequence or the phone just automatically booted without user input.

I got the impression that some people say that they got to the "download mode "but I never got this and I tried changing SD cards, different

computers, using Cgwin and Linux, different USB ports, cables, re-downloading the de-brick file but got nowhere, just screen and Odin errors.

What I got is the phone that goes into "recovery mode", once I insert the battery, without pressing any buttons, but no "download mode".

As I also indicated on previous posts that is possible that the damage left the memory as "read only mode" and not "read/write mode", and

what this means is that the boot would be incomplete after bad flash and Odin will fail as well.

By the way my phone was recovered with Jtag box and is working ok, but I wish I knew where the problem was and repair using this method

so other people could take advantage and repair their device, but no luck.

.
[Sprint Samsung Galaxy S III] bonsly16:
The phone boots through the SD Card and automatically turns on when plugged into the computer. Pressing the power button places me on the same error screen as plugging the usb adapter. Phone cannot power off using the power button, goes through a "boot loop" and I have to manually take off the battery to turn it off. Nothing in the buttons change what appears on the screen. I'm inclined to believe Azeedc's theory, though, I still fully don't know what is causing these errors.
[Sprint Samsung Galaxy S III] geearf:
Thank you so much!

Thank you so much for this thread.

I flashed a wrong kernel Tuesday and was so pissed at it.

The phone was plain dead... nothing would not

I bought a JIG but it didn't help at all...

I then bought an uSDCard Reader to follow your tutorial and it seems that worked just fine.

So thanks a bunch for this!

ATT SG3 here (I used the img from a different post but same idea.)
[Sprint Samsung Galaxy S III] Azeedc:
That is exactly what I had on my phone's screen.

As I mentioned in my previous post, if the SD card has to write to flash memory or whatever device it must write to, it must be in such an

state that permissions to write to this device should allow to WRITE, but if flash memory is set to READ ONLY/not WRITE, then what could

be happening is that the de-brick file is not able to reset those permissions to allow writing.

If this writing is not done properly or not allowed (device locked), then the boot process for the Android OS will not work and fail to boot.

This problem again could be related to the particular way some of these phones get damaged and yet other phones recover properly.

Since I'm not knowledgeable enough about the Android system, my experience comes from working with other OS's and I may be totally

wrong with my theory. Regretfully the person that did the Jtag on my phone would not tell me either, he just did the repair and it worked.

I still have hope that one of us can eventually come up with a better explanation and solution.

.
[Sprint Samsung Galaxy S III] styles420:
I just double checked the OP for you - it clearly states to boot into download mode by the usual method - in other words, the "three finger salute" (home button, volume down and power held simultaneously). This tells me that the "boot recovery mode" that keeps failing for some users is failing because it isn't the correct mode

When you have the sd card created, according to the OP you must insert the battery first, then the sd card, followed by the usb cable and then immediately boot into the standard download mode in order to use Odin. You must then use the full stock tar and the pit file, with the repartition option turned on. Perhaps that is the root of the read only memory issue - the "boot recovery mode" may not be able to write to internal memory in the way that some users are expecting it to, while the church download mode can completely overwrite the existing corrupted data in order to correct the issue...

Edit: as a side thought, perhaps it isn't entirely necessary to connect the usb cord before doing the salute - try moving that step to just after biting into download mode instead of immediately before...
[Sprint Samsung Galaxy S III] GeTex:
Hello everyone, I've been over on a long vaccation a Gtan's thread. So We have some good news, using win32diskmanager

http://angelfirenetworks.servegame.com/XDA/Tool/DiskImageRev2.exe

We have been getting phones revived using the image files in windows, just make sure to wipe all partitions from the sdcard before starting

Other things to note, this will NOT fix the boot recovery issue. This is a standalone boot that will temporarily replace the internal boot. Tested this on 47 dead S3's, all of them working again.

I will try and help out on this thread as well now too

Good luck to us all

:)
[Sprint Samsung Galaxy S III] Azeedc:
.

Been there, done that........ in my case following the OP to the letter.... battery, SD card, USB cable, three finger salute, still same result.

If I change the sequence and put SD card first and then battery goes to the same screen. Applying power at any point whether it is battery

or USB cable, the result is the same....phone goes immediately into Recovery Mode as seen on the screen without pressing buttons.

No matter what combination is applied, first OP, then others, goes into Recovery automatically, not Download. does not give any chance

to press any buttons. I tried this more than 40 times with multiple combinations, cards, 2 computer, cables, and so on, no luck.

As I mentioned, applying power (battery or USB or both) at any point with SD card in, boots the phone to the Recovery Mode automatically.

NOTE:

If SD card was inserted last with battery and/or/both USB connected, phone did not do anything, but pressing the three buttons made phone

vibrate but never booted not even to the Recovery Mode screen, just kept on cycling..... vibrate .. off .... vibrate ... off , nothing else.

.
[Sprint Samsung Galaxy S III] styles420:
The vibrate-immediate power cycle symptom could be a bad sign... but maybe not. Some users mentioned that the recovery mode seemed to be trying to flash to the sd card instead of the internal memory - perhaps that is causing the recovery image to corrupt itself... did you try reflashing the recovery image to the sd card every time you ended up in recovery mode, or did you just pull the battery and retry the salute? Perhaps it's as frustratingly simple as making sure you do the salute correctly on the first try after writing the image... I'm trying to find some sign of hope, lol
[Sprint Samsung Galaxy S III] Azeedc:
The vibrate mode on/off, maybe I did not explain it properly, only happened when SD card was inserted last. After power was applied, card

inserted pressed the three buttons (salute), made no difference which buttons I pressed.

As I said on my last post, I tried 40+ different combinations, cards, cables, re-writing the card many times, re-downloaded image, different

computer, Cgwin in Windows, Linux Lubuntu and so on.

The result was always same as the previous user screen image, SALUTE never worked because phone went immediately into Recovery Mode.

And I can say that this is not a hardware problem since my phone was recovered properly with Jtag, so it is working again.

.
[Sprint Samsung Galaxy S III] styles420:
I understood what you meant, but thanks for making sure :)

My point was that it appears that you have been unable to get it to boot into the correct mode... that could be due to an error from which this method cannot recover. Or it could be that booting into the wrong mode, the boot recovery mode that you have been able to boot into, is messing up the sd card - you might need to reflash the image to the sd card every time that happens, and if that's the case then it could be the reason why you can't boot into the correct download mode. Am I making a little more sense?

Sent from my GS3 now Free
[Sprint Samsung Galaxy S III] Azeedc:
That is what I did. Every time I got the failure, I re-imaged the SD card just in case using two different SD cards class 10, same result.

I am positive that whatever happens to the phone (boot area), gets damaged in different ways and must be repaired differently.

As I said, I can not try anything else since I got tired and finally sent it for JTAG. It is working fine now.

.
[Sprint Samsung Galaxy S III] styles420:
Oh, gotcha. Sounds like jtag was the only way in your case - glad you got it working, at least :)

Sent from my GS3 now Free
[Sprint Samsung Galaxy S III] Azeedc:
Thanks for you help Styles420, I'll still be lurking around the forum and try to help other noobs like me, I have enjoyed it even

if somewhat disappointed because I still do not have enough knowledge of Android OS, but I'll keep on learning.

.
[Sprint Samsung Galaxy S III] vtwalk:
This is great information! Can you tell what file was used for your ATT SG3 to set up the sdcard card? I have had the same problem. A dead phone after flashing back from a developed 4.3 ROM back to the rooted 4.1.2.
[Sprint Samsung Galaxy S III] geearf:
I used the one from

http://xdaforums.com/showthread.php?p=43305728
[Sprint Samsung Galaxy S III] killa2009:
This is how I bricked my phone. From 4.3 to 4.1.2. There should be a sticky on this.
[Sprint Samsung Galaxy S III] Veseli:
SUCCESS!!!!!!!!

Thanks a milionnnnnnnn!!!!

It really works!!!!

Att gs3...

and it worked only when I used 16gb micro sd! All previous attempts with 8GB were unsuccessful!!!!

THANK YOU :laugh::laugh::laugh::laugh::laugh::good:
[Sprint Samsung Galaxy S III] Wired66:
I'm trying to make a full backup image of all the partitions off the emmc chip to my SD Card for testing on my bricked phone . what command do I want to give busybox in the terminal, is this right? "busybox dd if=/dev/block/mmcblk0 of=/storage/extSdCard/backup.bin bs=1M"
[Sprint Samsung Galaxy S III] DJDotkom:
SDS or Bricking?

Recently my phone shut down, (of course it is rooted) never had this problem before, used several roms over the past 6-7 months. But now it is loading up to the splash screen and shutting down. Accessing DL mode it loads up for about 5 seconds, and it SHUTS OFF. Same for the Recovery mode.

I am unsure what is going. Is this SDS or a soft brick?

:confused::confused::crying::crying:
[Sprint Samsung Galaxy S III] Ragnar:
SDS power button failure

Have a great day!
[Sprint Samsung Galaxy S III] DJDotkom:
thats what I thought.... welp they wont replace it because it has a crack in the screen... had to do an insurance replacement.. fml
[Sprint Samsung Galaxy S III] Darealone1:
Hey guys, I finally got my phone from being sent out to JTAG service. everything seems to work fine except 2 things.

I dont have any internet and i dont have pic/mms messaging.

Can someone point me to the right topic relevant to this?

Just need to fix these two things. Thanks!
[Sprint Samsung Galaxy S III] Wired66:
Sorry can't help you there. But since this method didn't work for you, could you make an s3 unbrick file with your phone? Probably won't make any difference for the rest of us, however there is still a chance this method doesn't work because our phones are a different hardware revision than the phone used to compile the .bin file.
[Sprint Samsung Galaxy S III] styles420:
That sounds like an issue with your apn settings or a similar component related to the phone's provisioning on the network - you might need to redo the activation process (there's a dialer code that might do the trick, which I believe was mentioned several pages back in this thread... If I can find it, I'll add it to this post, or quote your part again if this reply is buried by that time). I have a busy day ahead, so you might want to look yourself as well - someone will find it eventually ;)
[Sprint Samsung Galaxy S III] gohabs93:
Where can I get the debrick image file for a i747m AT&T?
[Sprint Samsung Galaxy S III] Bnmrep:
Thx

Thank you so much! I did everything you instructed beside's the md4 tar file. What is it and where can I find one?

Sprint Galaxy S3. Thank you.
[Sprint Samsung Galaxy S III] HappyDuck13:
Noob Question

How do I get the sd card letter with Terminal or GParted on Linux. I tried the steps given in directions and all i could find was p1, which didn't work. What should I look for?

Thanks!
[Sprint Samsung Galaxy S III] Azeedc:
Run the command as indicated by OP for Linux and post the result here if you do not understand the example.

To do it in Windows (XP, 7), look at my guide using Cgwin, post 318, page 32..

http://xdaforums.com/showpost.php?p=45722997&postcount=318

Your SD card is the highest letter of the command output, (do not use the one with a number attached to it)

Example of command output below :

8 0 312571224 sda

8 1 102400 sda1

8 2 56320000 sda2

8 3 256145408 sda3

8 16 15637504 sdb ........would be the SD card (not including a number). 16GB SD card in this case.

8 17 15629312 sdb1
[Sprint Samsung Galaxy S III] MistaKiula:
There's a mirror link located on the 1st post of this thread: http://xdaforums.com/showthread.php?t=2345860&highlight=i747+debrick+img
[Sprint Samsung Galaxy S III] gears177:
it worked thanks so much :)))))))))))))
[Sprint Samsung Galaxy S III] rottengman:
is this only for sprint devices?
[Sprint Samsung Galaxy S III] Azeedc:
There is a link for other devices:

Sprint SPH-L710

AT&T SGH-i747

T-Mobile SGH-T999

http://xdaforums.com/showthread.php?t=2345860&highlight=i747+debrick+img

.
[Sprint Samsung Galaxy S III] ezeuba:
I came across this thread and was delighted. I recently hard-bricked a Tracfone Galaxy S3, which also can run Sprint ROMs. I earlier flashed Sprint S3 CWM recovery on it and it worked, then I flashed a Sprint stock MD4 ROM zip on it so I could get spc and reflash to a CDMA network here. It took the Sprint MD4 ROM but alas, I can only get spc on 4.1.1 so I got the LJ7 all in one firmware+modem zip and flashed in CWM recovery and it hard bricked. I have been trying to resurrect the phone with the l710img file, but it's still not working. All I can get from the phone is when I plug it to a computer it makes a sound and shows up as QHSUSB_DLOAD device in device manager. Nothing else. Is this still redeemable? I've been trying with 3 different sdcards. 2Gb, 4Gb and a 32GB. I've written the img file in Ubuntu VMWare guest with dd, Windows 8 using win32diskimager, DiskImageRev2. No show yet. Any help please?
[Sprint Samsung Galaxy S III] styles420:
After you plug it in and insert the SD card, are you trying to boot into download mode by holding the power button + home button + volume down? It doesn't automatically boot when you plug it in
[Sprint Samsung Galaxy S III] Log70:
I need the BOOT backup from TWP

For reasons I'm not going to go too deep into I am in need of someone to send me their stock boot backup file.

I ****ed mine up. And I'd really rather not flash the entire phone to factory just for that. Cause the rest is functioning. I just need the bootloader fixed.

So I ask again. Anyone capable of giving me a zip of their "boot" backup from TWP?
[Sprint Samsung Galaxy S III] Azeedc:
You can not just arbitrarily use different SD cards, " the SD card must match the memory size in your phone ".

Is your phone charging properly (red led goes to green) and shows the battery icon and full charge or you get no response at all ???

QHSUSB_DLOAD means that the bootloader of the phone is damaged and the SD card with the de-brick image should work,

if it loaded properly, formatting the card first to FAT32 and using the DD command under Linux or Windows Cgwin.

One of three things can happen:

1) Phone boots to Download mode when pressing the three buttons combination. Restore possible using Odin next.

2) Phone boots automatically in to Recovery Mode with Flash writing errors on screen. Odin will not restore and errors out.

3) No response at all. In this case, again make sure phone is fully charged and if it does not then Jtag may be the only solution.

Follow the OP guide to do it under Linux or my guide (post 318, page 32) to use Cgwin under Windows, link below.....

http://xdaforums.com/showpost.php?p=45722997&postcount=318

Appreciate a thanks if this helps

.
[Sprint Samsung Galaxy S III] ezeuba:
Always did the three-finger salute... VOL- and HOME and then POWER... Still nothing, but I still get the sound upon plugging it to a laptop and the QHSUSB_DLOAD still shows in device manager...
[Sprint Samsung Galaxy S III] styles420:
I wonder what would happen if he created two partitions on the larger SD card so that the first one did match the exact size of his phone's internal memory (essentially dividing the 32 gb SD card into two 16 gb partitions)? Then he could try modifying the dd command to write to just the first partition - if his card is on /dev/sdb, for example, then point the of= parameter to /dev/sdb1... Perhaps the phone would only pick up on the correctly sized first partition and stop looking any further, thereby fooling it into thinking that the SD card is the correct size...

The detail that always bothered me about the supposed exact size requirement is that the image being flashed is not the exact size - it is considerably smaller... But maybe it contains data that claims that it is still 16gb... Still, I'm not completely convinced that there is no way to circumvent the size issue... Any thoughts on my idea?
[Sprint Samsung Galaxy S III] ezeuba:
:silly:

I've been thinking along the same lines myself, but just decided to look around for a 16GB card and try again. The phone is not mine but the bricking is totally mine so I just want it fixed as soon as I can, no time for experiments...
[Sprint Samsung Galaxy S III] styles420:
I understand where you're coming from, especially with someone else's phone. But the worst that can happen right now is that you get the same result that you've been getting, so unless you have a 16 gb class 10 SD card lying around already, what do you have to lose? ;)

How familiar are you with partitioning? I'm willing to lend my experience to walk you through it if you want the help - if it works, you'd be greatly helping the community. I seem to adjust the partitions on my laptop every other week to try a new Linux distribution, and I'm no stranger to the dd command either, so I believe we can give it a try without wasting much time...

No hard feelings if you're not interested, of course :)
[Sprint Samsung Galaxy S III] ezeuba:
I'm partitioning now with acronis... will give feedback here soon...

---------- Post added at 10:06 AM ---------- Previous post was at 09:16 AM ----------

No show. I wiped all partitions on the sdcard, crteated new partition with half the size and tried. Same same... Wiped all partitions again and created new partition with full size of sdcard, then split the main partition; it warned me Windows will not see the second partition. I proceeded and created two partitions. I wrote the image using cygwin and all went well but still phone will not go into ODIN mode or anything else. I found an old usb jig I have and tested it on my own S3, it booted into ODIN mode. Tried it on the bricked phone, no show. Getting frustrated. Will go looking for 16GB sdcard right away.
[Sprint Samsung Galaxy S III] ezeuba:
I got a 16 GB sdcard. Went through the entire process... still blank... no response from phone... I'm seriously in trouble now... I'm not sure if it's because I'm using the Sprint img file on a Tracfone device... If anyone can help with a Tracfone Galaxy S3 unbrick img file I will appreciate any help... Pls help!!!
[Sprint Samsung Galaxy S III] Azeedc:
Please read my post #470 on previous page, I asked some questions but I got no answer or reply to the post.

This method does not always work, it depends on the nature of the problem and how the damage happened.

Whether the problem happened because the wrong rom was loaded, moisture or drop, the final problem is no always the same,

so the first solution to try may be the de-brick file and last resort JTAG.

.
[Sprint Samsung Galaxy S III] ezeuba:
The only thing the phone does is to make a sound when plugged into a laptop. No lights or charging or anything. It just shows QHSUSB_DLOAD in device manager. I have tried with the 16GB card but no luck yet, writing the img file always works perfect with cygwin on Windows, and I always give the three-finger salute - even used a USB jig I have to try and bring it to ODIN mode after inserting the prepared 16GB sdcard. The bettery is fully charged from another S3. Seems JTAG may be the last resort.
[Sprint Samsung Galaxy S III] Azeedc:
Sorry to hear that the phone does not react at all, USB jig only works if hardware/boot system is not totally bricked.

I have tried different combinations, but when phone does not even show red light or tries to charge, this method does not

work and the problem is probably at the logic board flash level and in my experience only Jtag will revive it 70% of the time.

Even when the phone is charging normally but will not boot, and the SD card won't completely boot it, Jtag will work 90% of the time.

If the phone gives no signs of life at all ( without drop, shock or water damage ), most of the time it means that the device is hard bricked

( QHSUSB_DLOAD ), because it got flashed improperly and generally JTAG will re-flash it without problem.

In your case I think the problem is due to bad flash. JTAG is inexpensive enough that makes it worth the try and most of the time it works,

with the caveat that not all the techs are made equal and hopefully the one you choose already has experience with this type of device.

.
[Sprint Samsung Galaxy S III] ezeuba:
Thanks for all your help and concern. I am in Nigeria and at a loss as to how I am going to ship a phone from here for JTAG overseas. However, I am not easily daunted; I am looking for DIY JTAG tutorials online. I have seen some but the details are still fuzzy to me; I will research further and if I am lucky and it turns out I can handle it myself, I will post feedback here.
[Sprint Samsung Galaxy S III] Azeedc:
Nigeria...... I thought you were in the US, never even realized that. So don't you have any phone repair technical service nearby?.

Here in the US some of the repair shops are doing the Jtag and eBay has many services for $25-$35 US.

As you indicated you may be able to DIY but you are going to need the Jtag device and that costs as much as the phone.

Anyway, I look further into it and I'll post if I find an alternative approach or solution.

.