yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] killa2009:
ok, i rewrote the image to sd card using what you posted. it Fails in odin at the part of

message box in odin:

system.img.ext4

transmission complete

now writing please wait about 2 minutes

receive response from boot-loader

fail(erase)

all thread completed. (succeed 0/failed !)

---------- Post added at 04:55 PM ---------- Previous post was at 04:37 PM ----------

Everything goes stops working at system.img.ext4 part. something happens at that moment which causing everything to fail.
[Sprint Samsung Galaxy S III] styles420:
Interesting... I'm at a bit of a loss at the moment, since I haven't done this myself - perhaps someone who has done it successfully can provide more insight as to what they see at that point in the process... maybe the differences will contain some clue as to what is going wrong. I suppose it is possible that the write failure could be caused by faulty hardware, but since so many people have had so many failed attempts before success, it's hard to say whether yours is failing for the same reasons...

For the sake of clarification, is that error the same one that you had been seeing, or is it a new error?
[Sprint Samsung Galaxy S III] killa2009:
this is new. the only file that flash with odin is the bootchain by itself.

the stock rom tar or any other tar fails.
[Sprint Samsung Galaxy S III] styles420:
I hope I'm wrong, but it is starting to sound like part of your internal memory has gone bad - the section that normally contains the boot chain seems fine, but the part where the system partition resides might be damaged, preventing data from being written to it...

Are you willing to try heimdal? It allows you (requires, really) to select each individual component, so you could try flashing each, one at a time, to see which parts fail. If you're able to flash everything else but the system partition image, that would lend credence to the theory that part of your memory is bad.

On the other hand, doing it a piece at a time (which will require you to pull the battery and then boot back into download mode between each flash, probably using the sd card unless you can flash the download mode partition successfully) might give it a better chance of success overall - it's worth a shot, if you're willing to try to figure it out (I'm happy to help, of course - I'm not trying to send you off on your own and leave you hanging, lol)
[Sprint Samsung Galaxy S III] killa2009:
thanks, lol im willing to try anyting at this point!
[Sprint Samsung Galaxy S III] styles420:
Okay, so I need to refresh my memory on heimdal first, which won't take too long. Bear with me for a short while though, because I'm also dealing with my car randomly stalling - if you'd like to get a head start while I get my car to a safe location, Google heimdal (I think the organization that makes it is called glass echidna, which will help you find info about the program rather than the Norse God, lol) - I think there is a Windows version, which might be easier to set up than trying to get the Linux version running in a live boot, and certainly quicker than installing Linux... (If you've already installed Linux to your hard drive, then we can try either one or both, but that's up to you) so find out what you can if you're up for it, and I'll be back soon with more info and, hopefully, answers to any questions you may have come across by then. I shouldn't be too long, maybe twenty minutes or so - hang in there, we'll figure out what we can as soon as we can

---------- Post added at 01:05 PM ---------- Previous post was at 12:06 PM ----------

Okay, I found the link to the download page for heimdal version 1.4.0:

http://www.glassechidna.com.au/products/heimdall/

You will find the Windows program a little ways down the page (it's the first download link, make sure you don't accidentally grab the Mac version). You can try the Linux version if you'd like, but I think the Windows version will be your best bet because it contains the GUI and everything else needed, whereas the Linux version comes in two parts and might rely on other components that might not be installed in your Linux live boot. It looks like the interface and everything is identical, so go with whichever you feel most comfortable with.

Once you have the program downloaded (and the required visual c++ files, link is provided on the download page if you need it), you'll need to extract the contents of the tar file so you can add each component (Odin tar files are structured differently than heimdal packages, so you can't just load the tar - I still need to look for the right forum thread, but I believe someone put together a prepackaged heimdal archive of the stock rom, which would simplify much of the process).

If we find a prepackaged heimdal archive, you can simply load that and flash away. Otherwise, you will need to add each piece from the Odin tar, correctly identifying which piece is which. I am still looking for the information to identify which file goes where or the thread with pre-made heimdal packages, but the documentation included with the program (might be under help, or could be just a text document) should help.

I have more to find, but if you go ahead and download the program in the meantime then it will speed things up once I'm back again. It might even have enough information for you to figure it out from there, but we'll see how that goes. Hang in there, I'll be back again in another 30 minutes or less to see how your doing (I have to get my car across town to have it looked at... it's not my day, lol)
[Sprint Samsung Galaxy S III] killa2009:
okay thank, i downloaded program
[Sprint Samsung Galaxy S III] styles420:
Cool, have you ran it yet to make sure you have all the necessary components installed correctly? I'll be just a few more minutes, managed to get my car to a shop so once that's squared away I'll have some time to fire up my laptop and figure out the rest - I think I'd like to try flashing just one component first, to see if we can get anything to take. I'll be back momentarily with the details (which component and how to set it up to flash to the right part of the phones internal memory, etc.)
[Sprint Samsung Galaxy S III] styles420:
Alright, I had to install heimdal again (I've changed Linux distros twice since I last used it, guess I'm the Linux equivalent of a flashaholic, lol)... I realized something that hasn't crossed my mind before now - in Linux, heimdal won't be able to connect to the device correctly unless it is ran as root.

This brings me to an important question for everyone that has been having trouble with Odin: have you been running Odin as administrator? That might be necessary for it to work...
[Sprint Samsung Galaxy S III] killa2009:
yes i have tried it as administrator
[Sprint Samsung Galaxy S III] styles420:
So weird... well, where are you at with heimdall? It's a little weird when you're used to Odin, so I'll walk you through the process - if you haven't tried anything yet, start by booting into download mode (or the sd card recovery equivalent, since I'm assuming you still don't have download mode wiring from internal memory), connect the usb cord and go to the utilities tab to press "detect device" - if it doesn't give an error, we'll work on flashing one component. If you do get an error, you'll probably need to restart heimdal in administrator mode (probably best to just start out that way, I'm guessing)
[Sprint Samsung Galaxy S III] killa2009:
ok i have

device detected
[Sprint Samsung Galaxy S III] styles420:
That's a good start. I'm not expecting thus next step to work, but see if it can read the pit from the device - I think that function is also under the utilities tab. Step one is to click "save as" to choose a location and give a filename (I called mine gs3.pit, the name doesn't need to be anything specific). Then click "download" and see if it completes without errors. I recommend this because heimdal seems to generate the pit differently than the one we use for Odin, and I'm not sure if the Odin pit file will work. I want to see what data, if any, will be read from your device

(I also pulled my pit, so if yours comes out wrong or not at all then I'll send you mine - assuming we have compatible devices... mine is the 16 gb model from Sprint, so if you have a different carrier then mine might not work, and if you have the 32 gb version then mine definitely won't match)

If you succeed at pulling a pit file, the next step is to use the print pit function on the right side of the utilities tab - first, check the button next to "from file" instead of the device, then browse to the file you just created, and finally press "print" - this will display the pit information in the box at the bottom of the program window. Copy and paste that info so I can compare it to mine - if they match, then you'll be able to use your copy (and that will indicate that not all of the internal data is corrupted, which may be a good sign). I know this may seem like extraneous work when I have one from a working phone, but I'm being cautions and trying to get as much info as possible before we start writing data to your phone, since we're blazing a new trail with this venture :)
[Sprint Samsung Galaxy S III] killa2009:
ERROR: Failed to access device. libusb error:

it didnt work
[Sprint Samsung Galaxy S III] styles420:
That's the same message I got when I forgot to run heimdal as root (administrator in the case of Windows) - did you remember to run as administrator?
[Sprint Samsung Galaxy S III] killa2009:
yup and it still failed to read
[Sprint Samsung Galaxy S III] vikas.patel:
workedsc pay

I did something using fdisk in Ubuntu, now my SD card looks messed up.

this is what happens when I give the commands in Cygwin.

Darling@Darling-PC /

$ cat proc/partitions

major minor #blocks name

8 0 312571224 sda

8 1 102400 sda1

8 2 56320000 sda2

8 3 256145408 sda3

8 16 15637504 sdb

8 17 15629312 sdb1

Darling@Darling-PC /

$ dd if=cygdrive/c/t999.img of=/dev/sdb

dd: opening `/dev/sdb': Permission denied

I know sdb1 is not where I should write, but I just tried on it as sdb was not working. it went through as below but actually the sd card was "blank"

Darling@Darling-PC /

$ dd if=cygdrive/c/t999.img of=/dev/sdb1

262144+0 records in

262144+0 records out

134217728 bytes (134 MB) copied, 903.243 s, 149 kB/s

Can you help me fix my SD Card, so I can fix my S3.
[Sprint Samsung Galaxy S III] styles420:
Hmmm... have you tried installing the C++ redistributables provided on the heimdal download page?

---------- Post added at 07:12 PM ---------- Previous post was at 07:04 PM ----------

Don't use the number at the end if the device name (eg sdb1 is wrong, sdb is the right way). You probably also need to run it as root by preceding the command with sudo, e.g "sudo dd if=" and so forth...
[Sprint Samsung Galaxy S III] killa2009:
yes i installed it
[Sprint Samsung Galaxy S III] styles420:
Maybe the failure to read just means that the data is corrupted... unfortunately, I can't power up my laptop right now to send you my pit, because my car is broken down and my mom told me to spend the night in the parking lot at the service shop instead of giving me a ride somewhere... not that I'd have anywhere to go, I've lived in my car for the past year because her abusive husband won't let me into the house (he kicked me out last year while I was going to college, which is why I'm no longer in college... my computer and my phone are all I have left)
[Sprint Samsung Galaxy S III] killa2009:
that sucks im sorry to hear that. your luck will change soon.
[Sprint Samsung Galaxy S III] styles420:
I hope so, it's about twenty years overdue...
[Sprint Samsung Galaxy S III] Azeedc:
If you are using Cgwin in (windows), the syntax is slightly different, ( no sudo ) command used in cgwin.

example : type this at the cgwin prompt......

check SD card letter : cat /proc/partitions

write card : dd if=/cygdrive/debrick_sph_l710.img of=/dev/sdc ......... ( see note below *** )

*** " The name of the file and size varies with your device's model as well as the path to where you place it "

Notes: very important....

1) " debrick_sph_l710.img.xz " file is a compressed file, (20+ MB), must be extracted with 7zip to " debrick_sph_l710.img, (80+ MB) "

2) Place " debrick_sph_l710.img " inside cygdrive directory to make sure cgwin finds it.

3) Verify that your sd card name, in the example above ' sdc ' is correct, this changes depending on the particular computer.

4) Format card to FAT32 using windows GUI or 'format x: at the command prompt ( substitute 'x' with your SD card letter.

5) SD card use a letter after the ' sd ', do not use any sd with numbers, for example sdc1.

6) Card must be class 10 or better with same capacity as your phone.

7) Revise command and location of cgwin and debrick file and check for typos.

8) Run command, is everything is correct you should get no errors and the sd card should boot the phone.

9) Finally you should get a response from cgwin indicating that a certain amount of records and MBs were written to the card.

If everything fails, try new/another USB cable, different USB port and lastly, try using another computer to exclude antivirus/software or hardware problems.

Finally.... remember, and this creates confusion......

The SD card is formatted initially to FAT32, but is changed by/to the Android de-brick image file system, so Windows may think it is unformatted.

Good luck

If this helps, say thanks
[Sprint Samsung Galaxy S III] styles420:
Thanks for putting more clearly than I've been able to... perhaps I shouldn't try to distract myself by trying to solve other people's problems, at least not when I've been awake for 48 hours :-/

And sorry to vent my troubles where they don't belong... this community has been one of the few positives in my life in recent years, and I know you guys are understanding - thanks for being chill and stable :)

I'm gonna crash for a day or two to recover - at least I know I'm leaving their I've been trying to help in good, capable hands. Good luck, everyone, and have a good night
[Sprint Samsung Galaxy S III] Azeedc:
My hat is off to you for all the help, time and effort, whether the problem is solved or not, you keep on trying.

I do not know you, but the fact that you try helping people without expecting any thing in return, to me is a great thing to do.

Keep up the good work, I'm sure many people are appreciative of what you do, I'm one of them.
[Sprint Samsung Galaxy S III] jmxc23:
I am here to say that since I am on Verizon I use the Verizon debrick file that someone made and this method posted here worked for me.
[Sprint Samsung Galaxy S III] bonsly16:
Uh, someone said there was a Youtube video that described the process? Can I see that link? :fingers-crossed:
[Sprint Samsung Galaxy S III] killa2009:
thats true, do you have paypal account?

---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------

can you explain to me what to download in cygin? i see many files which one should i download?

nevermind i got it
[Sprint Samsung Galaxy S III] killa2009:
this what cygwin64 says: where should i write the img

8 0 488384323 sda

8 1 512000 sda1

8 2 40960 sda2

8 3 131072 sda3

8 4 512000 sda4

8 5 478364672 sda5

8 6 8821571 sda6

8 16 8388608 sdb

8 17 8386560 sdb1

8 32 15663104 sdc

8 33 61440 sdc1
[Sprint Samsung Galaxy S III] Azeedc:
15663104 sdc ( sdc is the SD card )
[Sprint Samsung Galaxy S III] killa2009:
phone fails to flash in odin during system.img.ext4 sg3?
[Sprint Samsung Galaxy S III] Azeedc:
Verify that you get no errors on phone screen (red text ), when booting from SD card, many people get error during booting, look at the screen.

If you get errors during booting from SD card with the relevant de-brick image for you phone, is very possible that if you try next loading the

stock rom with ODIN, it will fail with some error due to incomplete boot.

Double check that you got the proper de-brick image and stock rom-firmware for your particular phone model, for example Sprint, AT&T, etc.

Still a lot to be learned here since this procedure works for many people but fails for others, try redoing the SD card, look for errors on screen

and my advice try re-downloading the stock rom again.

NOTE: Download the original stock rom for the phone. DO NOT use any modified or rooted rom, so as not to introduce other problems

Good luck
[Sprint Samsung Galaxy S III] Hearnbiz:
I actually flashed the att version of illusion rom lol ... it's the way the roms are listed I suppose it was ez to miss the version. Luckily it ran just fine on my sprint gs3...only issue was display was inverted...vids, pics and web ect was upside down. This is a great thread though because I could of just as easily downloaded the i9 version. Glad you unbricked.

Sent from my SPH-L710 using Xparent Skyblue Tapatalk 2
[Sprint Samsung Galaxy S III] styles420:
Excellent advice about going full stock to eliminate extra variables :)

And I'm still convinced that setting a block size that is more appropriate for sd cards will improve the odds of a successful dd flash ) in addition to the already proven speed increase) - the original debrick image was created with a block size of one megabyte (bs=1m), so maybe my original suggestion of 4 kilobytes is still too small... but in truth, the internal "native" block size can vary, and I'm sure I've seen a way to find it for any given flash memory device - if I can find the technique again, maybe I can talk someone into trying it (it can't really hurt anything to try)... I may be clinging to an irrelevant detail, but I think it's worth finding out for certain - I just don't want to return to stock just to test it, and testing on a phone that isn't bricked won't really prove anything definitively, lol. But the speedup is worth it either way ;)
[Sprint Samsung Galaxy S III] vikas.patel:
Thanx for the response... If you see, I have done every thing correct in Cygwin... the only issue I am facing right now is: Cygwin is unable to write the image to "sdb" ( "b" is for my sd card as per "cat proc/partitions"), as it says "Permission denied".

Every thing was working fine until I did "kind of" deleting and writing of partitions using fdisk in Ubuntu. Now my class 10 SD card is not working fine for this job... Can you help me fix the card?
[Sprint Samsung Galaxy S III] styles420:
I'm not very familiar with cygwin, but are you running it as administrator? If not, perhaps that's why it can't write to the sd card?
[Sprint Samsung Galaxy S III] Azeedc:
" Permission denied " possibly means that Cgwin does not have sufficient rights to complete the procedure.

Right click on Cgwin and from the menu choose ' Run as administrator ', enter password if required and proceed.

Reformat the SD card to FAT32 SD again if it is necessary and write the image to the card again. When finished check for errors.

NOTE:

I mentioned this before. SD card is initially formatted to FAT32 but writing of the de-brick image possibly changes the structure

of the file system to the extent that Windows may think that it is messed up and needs reformatting.

Again, the proof is on the pudding...... if the card is able to boot the phone without errors on the screen, then the card was written properly.

If booted properly, just go ahead, download original unmodified stock rom for your particular device and use ODIN to install to phone.
[Sprint Samsung Galaxy S III] killa2009:
i do have a red message that pops up,( Flash write failure odin mode).

when i activate the phone to go in dl mode it doesnt. the phone goes into BOOT recovery mode a black sceen with words not regular recovery mode. also it hangs for about a minute then that messages pops up.
[Sprint Samsung Galaxy S III] styles420:
I think the boot recovery mode part is to be expected - you aren't booting into normal download mode. That message shows that the phone recognizes that it has booted from a location other than internal memory.

If you did get normal download mode, then you might also have the problem mentioned by another user, where Odin appears to be flashing to the sd card instead of internal memory

So I *think* that you actually want to see boot recovery mode, but without the red error message you mentioned... again, that's speculation, but it seems logical (can anyone who has succeeded at this method confirm?)
[Sprint Samsung Galaxy S III] killa2009:
thanks 4 the reponse. why does my phone show the error of: flash write failure odin mode and i havent connected it to odin?
[Sprint Samsung Galaxy S III] styles420:
Now I'm speculating even more, but perhaps the boot recovery mode immediately flashes something (without Odin) to the internal memory to prepare it for the rest of the recovery process - if that's the case, then it looks like that initial write is failing... which could indicate that the sd card image didn't flash correctly or doesn't match your phone model, or it could (unfortunately) mean that not even the initial setup can write to your internal memory - in the last possibility, it would probably mean that the internal memory or related hardware has gone bad... those are my speculations, so don't assume I'm even close to correct until someone can confirm from personal experience...

Just out of curiosity, have you tried ignoring the error and connecting to Odin anyway? (I think you may have already indicated that you have, but I'm not sure if that was before you got to this point with this error message - I'm just making sure I'm on the same page with you)
[Sprint Samsung Galaxy S III] killa2009:
yes i have, but in odin the stock rom flash all the way to the point of system.img.ext4 error message then fails.
[Sprint Samsung Galaxy S III] bonsly16:
When I use cygwin, why does it say...

0+0 records in

0+0 records out

0 bytes (0 B) copied, 0.00411838 s, 0.0 kB/s
[Sprint Samsung Galaxy S III] Azeedc:
Nothing is been written to the SD card. Re-download the de-brick file, it could be damaged or empty.

Run Cgwin as administrator, you may not have enough rights.

Re-format card to FAT32, make sure it finishes with no errors and write the image to card again.

Double check the syntax of the command you use with Cgwin. the path to de-brick file and correct SD card letter.

See my previous post for complete details on how to do the whole procedure.
[Sprint Samsung Galaxy S III] styles420:
Okay, so that's where it gets us... I think the last hope we have is that somehow the use of cygwin is getting in the way - it has worked for others, but perhaps there is a driver issue or something. If my guess is wrong, and cygwin is not the hurdle, then it sounds like your internal memory or related hardware is bad...

So it may be a long shot, but I think you should try a full-blown Linux instead of a virtual machine - do you have either a writable dvd or a thumb drive with at least 8 gb capacity? If so, I can walk you through creating a live usb or live cd, which will allow you to boot your computer into Linux in a similar fashion to the way the phone is supposed to boot into recovery mode off of the sd card - let me know if you have the tools, and I'll wall you through the use of a program called unetbootin (found at unetbootin.sourceforge.net) to create the live usb. The live cd is as simple as burning a Linux iso to disc, but I really like the live usb method because the then drive can be updated and reused... take a look at the sourceforge website I mentioned, and Google "linux live usb" if you'd like, then let me know if you want to give it a go...
[Sprint Samsung Galaxy S III] bonsly16:
Not really related but when I try to flash the Stock ROM in Odin, I'm getting a "There is no PIT partition" error? What am I doing wrong?

Also, when I plug my phone in the computer, it automatically turns on at "Boot Recovery mode" and it says in red letters, Flash Write Failure, Odin Mode