[GUIDE] Fix an unflashable or soft bricked GSII (I9100G/M/P/T VERSION INCLUDED!)

Search This thread

Phistachio

Senior Member
Oct 22, 2011
1,475
1,026
24
Belgium, BE
Hello everyone! :D

This is a guide dedicated to noobs, so if you're not one, I would advise to stop reading now! (altough feedback would be great! :))

Yes, there have been quite a few threads about fixing a soft brick. But what I'm writting now is another solution to a different kind of problem : unflashable GSII (which also works with a soft brick of course ;)), which is a soft brick and a corrupted NAND rw (read/write) function.

Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, regarding NAND rw (NAND's read and write function being the corruption) it means that it is an issue deeper than a soft brick.

It is obvious when you can flash a kernel, but you can't flash a ROM, because it can't properly read the NAND, but can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple", so when flashing, ODIN will say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.

__________________________________________________

IF YOU ONLY HAVE A BOOTLOOP​

Wipe data/factory reset and wipe cache. IF THAT DOESN'T WORK, MOVE ON WITH THE GUIDE :)

__________________________________________________

VERY IMPORTANT ANNOUNCEMENT


I would like to first apologize for my absence. My past months have been super busy, and they don't seem to be ending anytime soon. And "anytime soon" meaning in a couple of years. And I'm actually glad that this is happening, since I've been working pretty hard to achieve the state I'm in.

This thread has evolved into something I've never imagined. Only because of YOU guys, we managed to turn a normal thread into a pretty popular and well used Guide, and it made me so happy and joyous of being apart of the XDA community. I feel proud in being a XDA nut. This whole success is just because of YOU guys. :)

As painful as it is to say this... I believe that I will be dropping support on this thread after the New Year, because a) I lost my Galaxy S2 in Paris in a taxi with no hope of getting it back when I went there 3 weeks ago and b) I'm probably getting a Galaxy Note 2 in the New Year, so this thread will be most likely ported and maintained over at the Note 2 forums.

I'm extremely sorry it has come this way, and I hope you guys will understand. In the following days I'll be updating the files to their latest versions, and will try to find new bootloaders and kernels, but without sources, I'm unable to do so. I'll update whatever I'll be able to :)

Regards and thanks to all of you that have supported me,

Rafael K.

__________________________________________________

IMPORTANT ANNOUNCEMENT #2

Please welcome neerajganga, your new thread maintainer (along with me)! He has been of great help, so I think he deserves this kind of announcement!
__________________________________________________


Okay, so apparently people that come from ICS and try to recover it with the GB files make their phones nearly unrecoverable. So, now I've divided the guide in 2 sections : the GINGERBREAD VERSION and the ICS VERSION.

Due to popular demand, I have also added an I9100G Version, which is here!

I have also added the I9100 M/P/T versions. Now I support ALL I9100 variants.


But for the moment, I do not have the G/M/P/T .PIT, kernels or Bootloader, so if you have any of those version, only flash what is in the provided package.


__________________________________________________

Let's start with the basic files, downloads and requirements

GINGERBREAD VERSION

1) You have to know the basics of ODIN and flashing (duh :p)

2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers

3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

4) Download the necessary files : the Recovery Package/ROM (password is samfirmware.com), the Kernel (password is [email protected]) and the Bootloader.

5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano :)

ICS VERSION

1) You have to know the basics of ODIN and flashing (duh :p)

2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers

3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

4) Download the necessary files : the Recovery Package/ROM [THIS PACKAGE ALREADY INCLUDES THE BOOTLOADER] (password is samfirmware.com) and the Kernel.

5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano :)

I9100G VERSION

1) You have to know the basics of ODIN and flashing (duh :p)

2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers

3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

4) Download the necessary ROM (they are Gingerbread 2.3.6) : Africa (Iraq), Asia (Malaysia), Europe (Open Austria), Middle East (Saudi Arabia). (password is samfirmware.com)

5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano :)

I9100M VERSION

1) You have to know the basics of ODIN and flashing (duh :p)

2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers

3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

4) Download the necessary files : the Recovery Package (Open Canada) (password is samfirmware.com).

5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano :)

I9100P VERSION

1) You have to know the basics of ODIN and flashing (duh :p)

2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers

3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

4) Download the necessary files : the Recovery Package (UK - Orange) GINGERBREAD VERSION / Recovery Package (UK - Orange) ICS VERSION (password is samfirmware.com).

5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano :)

I9100T VERSION

1) You have to know the basics of ODIN and flashing (duh :p)

2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers

3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

4) Download the necessary files : the Recovery Package (Australia - Telstra) GINGERBREAD VERSION / Recovery Package (Australia - Three/Vodafone) ICS VERSION (password is samfirmware.com).

5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip, as sugested by jermitano :)

And that is it! Let's get down to business :)

__________________________________________________

If your GSII has the folowing symptoms :

  • Bootloop
  • Stuck on GSII logo, but already removed the battery to try to fix it
  • Enters Download mode and Recovery mode

It means that you are soft bricked and is easy to solve.

But if your symptoms are the mentioned above, PLUS the symptoms below

  • Enters Download mode but does NOT enter recovery mode (usually means a NAND rw corruption)
  • Doesn't flash
  • Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)

Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.

It's time to open up ODIN and start reviving your phone!

__________________________________________________


First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :

ojgokk.png


As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way. And the red one is well... Where you SHOULDN'T touch :p



ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
THAT THE FLASH WILL SUCCEED.

Which means that you CANNOT have a damaged USB, corrupted drivers and such.


When recovering from a soft brick, it is recommended, not mandatory, to have Re-partition ticked with a .PIT file. So you must be extra careful when you are using a .PIT and Re-Partition. And obviously, the red box is the one where you can't and don't want to mess with ;)

But where are the files going, you say?

.PIT -> PIT
APBOOT -> BOOTLOADER (or PDA if flashed alone)
CODE -> PDA
MODEM -> PHONE
CSC -> CSC


***If you have a 1 file .tar package, then flash it in PDA***​

There is only 1 way to recover a soft bricked phone. How to recover from a NAND corruption? We'll get on that later on ;)

__________________________________________________

Recovering a soft bricked phone

1) Grab the Recovery Package, and you'll see a bunch of .tar files. Take a look at the names. You'll see CODE, MODEM, CSC and .PIT. Put each one in its place.

2) Turn off your phone. Enter Download mode by presing Volume Down + Home + Power button.

3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9)

Now here, take a breath

First try flashing WITHOUT the .PIT and re-partition. And only if it DOESN'T WORK OR FIX then you flash with the .PIT and Re-Partition ticked.

4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.

Have you done everything correctly until now? Then...

Congratulations on recovering your phone!

You deserve some cake afterwards, and some rest :D

Now, if your problem is the NAND rw coruption, and wasn't fixed by the above fix, then follow these steps :

5) Download the Kernel. Flash it in PDA. Without ticking Re-Partitioning

6) Successful? Nice, hope is still present.

7) Flash the recovery package, following steps 1-4 This should fix your issue. If it does not, then :

WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.

8) Download the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partitioning

9) Flash the Kernel, as in step 5

10) Flash the recovery package, like in steps 1-4 And that will fix any of your issues :D

11) After you have recovered your phone, I advise you to have your phone completely up to date by browsing and downloading the firmware for your version through SamMobile!

I hope that this guide was helpful, and if it was, hit the thanks button! :)

Credits mainly go to Intratech, for his amazing gallery of ROMS and files :)

_______________________
Disclaimer

This is to be used as educational information. I am not liable of any damage that may occur to your phone.
 
Last edited:

jermitano

Senior Member
Oct 8, 2011
1,302
884
Manila
very nice! was looking for this to post to our threads on my home country...

btw...may i suggest 7zip as well...i guess its the best unzipper for packages from xda

---------- Post added at 07:26 PM ---------- Previous post was at 07:26 PM ----------

Good work, should be stickied.

Our Mutual Friend should thank you, but he'll probably rant at you for not posting this before;)

nyahahaha...i think it makes the 3 of us...was that the tool?:D
 

B3311

Senior Member
Feb 16, 2011
2,413
1,046
Gelderd End, 1974
very nice! was looking for this to post to our threads on my home country...

btw...may i suggest 7zip as well...i guess its the best unzipper for packages from xda

---------- Post added at 07:26 PM ---------- Previous post was at 07:26 PM ----------



nyahahaha...i think it makes the 3 of us...was that the tool?:D

He was, is and always will be;)

Good call for 7zip.
 

Phistachio

Senior Member
Oct 22, 2011
1,475
1,026
24
Belgium, BE
Good work, should be stickied.

Our Mutual Friend should thank you, but he'll probably rant at you for not posting this before;)

Thanks! I'm gonna post this in Q&A section, because it's where I've found that this would be of bigger use, and so I'd like to have it stickied :)
Our mutual "friend"... lol, that guy... :p

very nice! was looking for this to post to our threads on my home country...

btw...may i suggest 7zip as well...i guess its the best unzipper for packages from xda

---------- Post added at 07:26 PM ---------- Previous post was at 07:26 PM ----------



nyahahaha...i think it makes the 3 of us...was that the tool?:D

Alright, adding 7zip to the OP :)
 

Lennyz1988

Senior Member
May 15, 2009
3,274
644
Amsterdam
Hopefully this thread will save a lot of questions.

Feedback:

This is a really dangerous advice:

When recovering from a soft brick, it is recommended, not mandatory, to have Re-partition ticked with a .PIT file. So you must be extra careful when you are using a .PIT and Re-Partition. And obviously, the red box is the one where you can't and don't want to mess with

Sometimes people can't flash because they have a damaged usb cable, corrupted drivers etc. When they use .pit and re-partition, they have a great chance of really bricking their device. People should never use those, unless they are certain the flash will succeed! And the problem is, noobs won't know if they can flash or not. I think you should delete that part because people that come here, have no idea what they are doing.
 

Phistachio

Senior Member
Oct 22, 2011
1,475
1,026
24
Belgium, BE
Hopefully this thread will save a lot of questions.

Feedback:

This is a really dangerous advice:



Sometimes people can't flash because they have a damaged usb cable, corrupted drivers etc. When they use .pit and re-partition, they have a great chance of really bricking their device. People should never use those, unless they are certain the flash will succeed! And the problem is, noobs won't know if they can flash or not. I think you should delete that part because people that come here, have no idea what they are doing.

I see. Then, I can add this :

ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
THAT THE FLASH WILL SUCCEED.

Which means that you CANNOT have a damaged USB, corrupted drivers and such.


What do you think? Or is a delete better?

Thanks for the feedback tho!
 

mwatson

Senior Member
Oct 16, 2007
1,128
229
Basingstoke
I see. Then, I can add this :

ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
THAT THE FLASH WILL SUCCEED.

Which means that you CANNOT have a damaged USB, corrupted drivers and such.


What do you think? Or is a delete better?

Thanks for the feedback tho!

Didn't do me any harm. I realised I had a duff USB cable that wouldn't flash. Swapped for a new one and all ok. I've also had damaged drivers too. Big thanks to the OP phistachio for helping me out at Xmas this year by bringing my phone back from the dead!
 
  • Like
Reactions: rockrl

Coentje44

Senior Member
Nov 14, 2010
450
881
Can anyone help me here? whenever i flash an Samsung ICS rom like XXKP8/LP2 pressing the power button turns off my device and pressing the home button does nothing.lockscreen isnt working aswell. hope anyone can help me fix this.


cheers.
 

Phistachio

Senior Member
Oct 22, 2011
1,475
1,026
24
Belgium, BE
Can anyone help me here? whenever i flash an Samsung ICS rom like XXKP8/LP2 pressing the power button turns off my device and pressing the home button does nothing.lockscreen isnt working aswell. hope anyone can help me fix this.


cheers.

That's a widely reported bug of ICS. You'll have to wait for another release of ICS to have it fixed ;)
 

Uvaavu

Senior Member
Sep 13, 2006
139
32
Second circle of Hell
Thanks for the post Phistachio, I've tried this and its not working, infact I'm in the exact same situation as this guy : http://forum.xda-developers.com/showthread.php?p=21430756 , however mine was caused by a series of ICS/CWM Recovery Backup/Restore screw ups.

I can only enter Download mode, via Jig or [Home]+[Vol Down]+[Power] both are fine, no other function currently works (no recovery).

Odin allows me to flash a bootloader, but not a kernel/modem/code etc - it stops at 'NAND Write Start!' and the blue bar never appears on the phone screen.

After attempting to flash a kernel above, but failing, it DOES however increment the 'CUSTOM BINARY DOWNLOAD' counter.

I did get Heimdall to work, and extracted the current PIT (see end for Heimdall's pit output), at which point I tried to flash a kernel in Heimdall, giving the following:

Any ideas? Note I have not tried re-partitioning at all yet - wanted to save that as a last resort.

Heimdall Kernel flash:
Code:
Initialising connection...
Detecting device...
      Manufacturer: "SAMSUNG"
           Product: "Gadget Serial"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 021B
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 83
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 02
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 131072

Downloading device's PIT file...
PIT file download sucessful

Uploading KERNEL
0%
File Part #0... Response: 0  0  0  0  0  0  0  0 

1%

File Part #1... Response: 0  0  0  0  1  0  0  0 

3%

File Part #2... Response: 0  0  0  0  2  0  0  0 

4%

File Part #3... Response: 0  0  0  0  3  0  0  0 

6%

File Part #4... Response: 0  0  0  0  4  0  0  0 

7%

File Part #5... Response: 0  0  0  0  5  0  0  0 

9%

File Part #6... Response: 0  0  0  0  6  0  0  0 

10%

File Part #7... Response: 0  0  0  0  7  0  0  0 

12%

File Part #8... Response: 0  0  0  0  8  0  0  0 

14%

File Part #9... Response: 0  0  0  0  9  0  0  0 

15%

File Part #10... Response: 0  0  0  0  A  0  0  0 

17%

File Part #11... Response: 0  0  0  0  B  0  0  0 

18%

File Part #12... Response: 0  0  0  0  C  0  0  0 

20%

File Part #13... Response: 0  0  0  0  D  0  0  0 

21%

File Part #14... Response: 0  0  0  0  E  0  0  0 

23%

File Part #15... Response: 0  0  0  0  F  0  0  0 

24%

File Part #16... Response: 0  0  0  0  10  0  0  0 

26%

File Part #17... Response: 0  0  0  0  11  0  0  0 

28%

File Part #18... Response: 0  0  0  0  12  0  0  0 

29%

File Part #19... Response: 0  0  0  0  13  0  0  0 

31%

File Part #20... Response: 0  0  0  0  14  0  0  0 

32%

File Part #21... Response: 0  0  0  0  15  0  0  0 

34%

File Part #22... Response: 0  0  0  0  16  0  0  0 

35%

File Part #23... Response: 0  0  0  0  17  0  0  0 

37%

File Part #24... Response: 0  0  0  0  18  0  0  0 

39%

File Part #25... Response: 0  0  0  0  19  0  0  0 

40%

File Part #26... Response: 0  0  0  0  1A  0  0  0 

42%

File Part #27... Response: 0  0  0  0  1B  0  0  0 

43%

File Part #28... Response: 0  0  0  0  1C  0  0  0 

45%

File Part #29... Response: 0  0  0  0  1D  0  0  0 

46%

File Part #30... Response: 0  0  0  0  1E  0  0  0 

48%

File Part #31... Response: 0  0  0  0  1F  0  0  0 

49%

File Part #32... Response: 0  0  0  0  20  0  0  0 

51%

File Part #33... Response: 0  0  0  0  21  0  0  0 

53%

File Part #34... Response: 0  0  0  0  22  0  0  0 

54%

File Part #35... Response: 0  0  0  0  23  0  0  0 

56%

File Part #36... Response: 0  0  0  0  24  0  0  0 

57%

File Part #37... Response: 0  0  0  0  25  0  0  0 

59%

File Part #38... Response: 0  0  0  0  26  0  0  0 

60%

File Part #39... Response: 0  0  0  0  27  0  0  0 

62%

File Part #40... Response: 0  0  0  0  28  0  0  0 

64%

File Part #41... Response: 0  0  0  0  29  0  0  0 

65%

File Part #42... Response: 0  0  0  0  2A  0  0  0 

67%

File Part #43... Response: 0  0  0  0  2B  0  0  0 

68%

File Part #44... Response: 0  0  0  0  2C  0  0  0 

70%

File Part #45... Response: 0  0  0  0  2D  0  0  0 

71%

File Part #46... Response: 0  0  0  0  2E  0  0  0 

73%

File Part #47... Response: 0  0  0  0  2F  0  0  0 

74%

File Part #48... Response: 0  0  0  0  30  0  0  0 

76%

File Part #49... Response: 0  0  0  0  31  0  0  0 

78%

File Part #50... Response: 0  0  0  0  32  0  0  0 

79%

File Part #51... Response: 0  0  0  0  33  0  0  0 

81%

File Part #52... Response: 0  0  0  0  34  0  0  0 

82%

File Part #53... Response: 0  0  0  0  35  0  0  0 

84%

File Part #54... Response: 0  0  0  0  36  0  0  0 

85%

File Part #55... Response: 0  0  0  0  37  0  0  0 

87%

File Part #56... Response: 0  0  0  0  38  0  0  0 

89%

File Part #57... Response: 0  0  0  0  39  0  0  0 

90%

File Part #58... Response: 0  0  0  0  3A  0  0  0 

92%

File Part #59... Response: 0  0  0  0  3B  0  0  0 

93%

File Part #60... Response: 0  0  0  0  3C  0  0  0 

95%

File Part #61... Response: 0  0  0  0  3D  0  0  0 

96%

File Part #62... Response: 0  0  0  0  3E  0  0  0 

98%

File Part #63... Response: 0  0  0  0  3F  0  0  0 

99%

File Part #64... Response: 0  0  0  0  40  0  0  0 

100%

ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.

ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!

Heimdall pit list:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 131072

Downloading device's PIT file...
PIT file download sucessful

Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img


--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin


--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img


--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin


--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename: 


--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs


--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage


--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: 


--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 204800
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img


--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 311296
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin


--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 344064
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img


--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 1392640
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img


--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 5586944
Partition Block Count: 24133632
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename: 


--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 29720576
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img


--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: 
Filename: 

Ending session...
Rebooting device...
 

Phistachio

Senior Member
Oct 22, 2011
1,475
1,026
24
Belgium, BE
Thanks for the post Phistachio, I've tried this and its not working, infact I'm in the exact same situation as this guy : http://forum.xda-developers.com/showthread.php?p=21430756 , however mine was caused by a series of ICS/CWM Recovery Backup/Restore screw ups.

I can only enter Download mode, via Jig or [Home]+[Vol Down]+[Power] both are fine, no other function currently works (no recovery).

Odin allows me to flash a bootloader, but not a kernel/modem/code etc - it stops at 'NAND Write Start!' and the blue bar never appears on the phone screen.

After attempting to flash a kernel above, but failing, it DOES however increment the 'CUSTOM BINARY DOWNLOAD' counter.

I did get Heimdall to work, and extracted the current PIT (see end for Heimdall's pit output), at which point I tried to flash a kernel in Heimdall, giving the following:

Any ideas? Note I have not tried re-partitioning at all yet - wanted to save that as a last resort.

Heimdall Kernel flash:
Code:
Initialising connection...
Detecting device...
      Manufacturer: "SAMSUNG"
           Product: "Gadget Serial"

            length: 18
      device class: 2
               S/N: 0
           VID:PID: 04E8:685D
         bcdDevice: 021B
   iMan:iProd:iSer: 1:2:0
          nb confs: 1

interface[0].altsetting[0]: num endpoints = 1
   Class.SubClass.Protocol: 02.02.01
       endpoint[0].address: 83
           max packet size: 0010
          polling interval: 09

interface[1].altsetting[0]: num endpoints = 2
   Class.SubClass.Protocol: 0A.00.00
       endpoint[0].address: 81
           max packet size: 0200
          polling interval: 00
       endpoint[1].address: 02
           max packet size: 0200
          polling interval: 00
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 131072

Downloading device's PIT file...
PIT file download sucessful

Uploading KERNEL
0%
File Part #0... Response: 0  0  0  0  0  0  0  0 

1%

File Part #1... Response: 0  0  0  0  1  0  0  0 

3%

File Part #2... Response: 0  0  0  0  2  0  0  0 

4%

File Part #3... Response: 0  0  0  0  3  0  0  0 

6%

File Part #4... Response: 0  0  0  0  4  0  0  0 

7%

File Part #5... Response: 0  0  0  0  5  0  0  0 

9%

File Part #6... Response: 0  0  0  0  6  0  0  0 

10%

File Part #7... Response: 0  0  0  0  7  0  0  0 

12%

File Part #8... Response: 0  0  0  0  8  0  0  0 

14%

File Part #9... Response: 0  0  0  0  9  0  0  0 

15%

File Part #10... Response: 0  0  0  0  A  0  0  0 

17%

File Part #11... Response: 0  0  0  0  B  0  0  0 

18%

File Part #12... Response: 0  0  0  0  C  0  0  0 

20%

File Part #13... Response: 0  0  0  0  D  0  0  0 

21%

File Part #14... Response: 0  0  0  0  E  0  0  0 

23%

File Part #15... Response: 0  0  0  0  F  0  0  0 

24%

File Part #16... Response: 0  0  0  0  10  0  0  0 

26%

File Part #17... Response: 0  0  0  0  11  0  0  0 

28%

File Part #18... Response: 0  0  0  0  12  0  0  0 

29%

File Part #19... Response: 0  0  0  0  13  0  0  0 

31%

File Part #20... Response: 0  0  0  0  14  0  0  0 

32%

File Part #21... Response: 0  0  0  0  15  0  0  0 

34%

File Part #22... Response: 0  0  0  0  16  0  0  0 

35%

File Part #23... Response: 0  0  0  0  17  0  0  0 

37%

File Part #24... Response: 0  0  0  0  18  0  0  0 

39%

File Part #25... Response: 0  0  0  0  19  0  0  0 

40%

File Part #26... Response: 0  0  0  0  1A  0  0  0 

42%

File Part #27... Response: 0  0  0  0  1B  0  0  0 

43%

File Part #28... Response: 0  0  0  0  1C  0  0  0 

45%

File Part #29... Response: 0  0  0  0  1D  0  0  0 

46%

File Part #30... Response: 0  0  0  0  1E  0  0  0 

48%

File Part #31... Response: 0  0  0  0  1F  0  0  0 

49%

File Part #32... Response: 0  0  0  0  20  0  0  0 

51%

File Part #33... Response: 0  0  0  0  21  0  0  0 

53%

File Part #34... Response: 0  0  0  0  22  0  0  0 

54%

File Part #35... Response: 0  0  0  0  23  0  0  0 

56%

File Part #36... Response: 0  0  0  0  24  0  0  0 

57%

File Part #37... Response: 0  0  0  0  25  0  0  0 

59%

File Part #38... Response: 0  0  0  0  26  0  0  0 

60%

File Part #39... Response: 0  0  0  0  27  0  0  0 

62%

File Part #40... Response: 0  0  0  0  28  0  0  0 

64%

File Part #41... Response: 0  0  0  0  29  0  0  0 

65%

File Part #42... Response: 0  0  0  0  2A  0  0  0 

67%

File Part #43... Response: 0  0  0  0  2B  0  0  0 

68%

File Part #44... Response: 0  0  0  0  2C  0  0  0 

70%

File Part #45... Response: 0  0  0  0  2D  0  0  0 

71%

File Part #46... Response: 0  0  0  0  2E  0  0  0 

73%

File Part #47... Response: 0  0  0  0  2F  0  0  0 

74%

File Part #48... Response: 0  0  0  0  30  0  0  0 

76%

File Part #49... Response: 0  0  0  0  31  0  0  0 

78%

File Part #50... Response: 0  0  0  0  32  0  0  0 

79%

File Part #51... Response: 0  0  0  0  33  0  0  0 

81%

File Part #52... Response: 0  0  0  0  34  0  0  0 

82%

File Part #53... Response: 0  0  0  0  35  0  0  0 

84%

File Part #54... Response: 0  0  0  0  36  0  0  0 

85%

File Part #55... Response: 0  0  0  0  37  0  0  0 

87%

File Part #56... Response: 0  0  0  0  38  0  0  0 

89%

File Part #57... Response: 0  0  0  0  39  0  0  0 

90%

File Part #58... Response: 0  0  0  0  3A  0  0  0 

92%

File Part #59... Response: 0  0  0  0  3B  0  0  0 

93%

File Part #60... Response: 0  0  0  0  3C  0  0  0 

95%

File Part #61... Response: 0  0  0  0  3D  0  0  0 

96%

File Part #62... Response: 0  0  0  0  3E  0  0  0 

98%

File Part #63... Response: 0  0  0  0  3F  0  0  0 

99%

File Part #64... Response: 0  0  0  0  40  0  0  0 

100%

ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.

ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!

Heimdall pit list:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...

Beginning session...
Session begun with device of type: 131072

Downloading device's PIT file...
PIT file download sucessful

Entry Count: 15
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0


--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 0
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: GANG
Filename: emmc.img


--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: BOOT
Filename: boot.bin


--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 8192
Partition Block Count: 40960
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: efs.img


--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 49152
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL1
Filename: Sbl.bin


--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 53248
Partition Block Count: 2560
Unknown 2: 0
Unknown 3: 0
Partition Name: SBL2
Filename: 


--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 57344
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs


--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 73728
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: KERNEL
Filename: zImage


--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 90112
Partition Block Count: 16384
Unknown 2: 0
Unknown 3: 0
Partition Name: RECOVERY
Filename: 


--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 106496
Partition Block Count: 204800
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHE
Filename: cache.img


--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 311296
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: MODEM
Filename: modem.bin


--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 344064
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: FACTORYFS
Filename: factoryfs.img


--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 1392640
Partition Block Count: 4194304
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: data.img


--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 2 (R/W)
Unknown 1: 0
Partition Block Size: 5586944
Partition Block Count: 24133632
Unknown 2: 0
Unknown 3: 0
Partition Name: UMS
Filename: 


--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 1 (R)
Unknown 1: 0
Partition Block Size: 29720576
Partition Block Count: 1048576
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img


--- Entry #14 ---
Unused: Yes
Partition Type: 1 (Unknown)
Partition Identifier: 9
Partition Flags: 0 (R)
Unknown 1: 0
Partition Block Size: 0
Partition Block Count: 0
Unknown 2: 0
Unknown 3: 0
Partition Name: 
Filename: 

Ending session...
Rebooting device...

Mmm... You do have to use re-partition when using a PIT...

Let's try this :

Flash the NEW bootloader, the one which you can't use a JIG : http://www.multiupload.com/5LNOCL7KPV, and then repeat the whole process again.

I would advise you to flash CWM Recovery to overwrite the old one, but unfortunately you can't use your phone, thus you can't use adb to push the file... :(
 
Last edited:
  • Like
Reactions: developermauro

Uvaavu

Senior Member
Sep 13, 2006
139
32
Second circle of Hell
Mmm... You do have to use re-partition when using a PIT...

Let's try this :

Flash the NEW bootloader, the one which you can't use a JIG : http://www.multiupload.com/5LNOCL7KPV, and then repeat the whole process again.

I would advise you to flash CWM Recovery to overwrite the old one, but unfortunately you can't use your phone, thus you can't use adb to push the file... :(

Ok, have tried this again tonight and its not now allowing me to flash a bootloader either - I assume from all the various attempts to flash over the last couple of days, or perhaps after i uploaded the last bootloader? :(

I tried a few times in Odin, but it just hung, regardless of what I chose, so I moved to Heimdall.

In Heimdall I keep getting the same error: ERROR: libusb error -7 whilst sending packet. Retrying...

And it times out eventually. It's like the phone isn't responding correctly to the flash commands?

EDIT: If I do not attempt to try and repartition (either using the downloaded pit, or one taken fromthe phone itself) I can get all the way to 'Uploading 100%' in heimdall, before it gives the same error above.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 272
    Hello everyone! :D

    This is a guide dedicated to noobs, so if you're not one, I would advise to stop reading now! (altough feedback would be great! :))

    Yes, there have been quite a few threads about fixing a soft brick. But what I'm writting now is another solution to a different kind of problem : unflashable GSII (which also works with a soft brick of course ;)), which is a soft brick and a corrupted NAND rw (read/write) function.

    Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, regarding NAND rw (NAND's read and write function being the corruption) it means that it is an issue deeper than a soft brick.

    It is obvious when you can flash a kernel, but you can't flash a ROM, because it can't properly read the NAND, but can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple", so when flashing, ODIN will say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.

    __________________________________________________

    IF YOU ONLY HAVE A BOOTLOOP​

    Wipe data/factory reset and wipe cache. IF THAT DOESN'T WORK, MOVE ON WITH THE GUIDE :)

    __________________________________________________

    VERY IMPORTANT ANNOUNCEMENT


    I would like to first apologize for my absence. My past months have been super busy, and they don't seem to be ending anytime soon. And "anytime soon" meaning in a couple of years. And I'm actually glad that this is happening, since I've been working pretty hard to achieve the state I'm in.

    This thread has evolved into something I've never imagined. Only because of YOU guys, we managed to turn a normal thread into a pretty popular and well used Guide, and it made me so happy and joyous of being apart of the XDA community. I feel proud in being a XDA nut. This whole success is just because of YOU guys. :)

    As painful as it is to say this... I believe that I will be dropping support on this thread after the New Year, because a) I lost my Galaxy S2 in Paris in a taxi with no hope of getting it back when I went there 3 weeks ago and b) I'm probably getting a Galaxy Note 2 in the New Year, so this thread will be most likely ported and maintained over at the Note 2 forums.

    I'm extremely sorry it has come this way, and I hope you guys will understand. In the following days I'll be updating the files to their latest versions, and will try to find new bootloaders and kernels, but without sources, I'm unable to do so. I'll update whatever I'll be able to :)

    Regards and thanks to all of you that have supported me,

    Rafael K.

    __________________________________________________

    IMPORTANT ANNOUNCEMENT #2

    Please welcome neerajganga, your new thread maintainer (along with me)! He has been of great help, so I think he deserves this kind of announcement!
    __________________________________________________


    Okay, so apparently people that come from ICS and try to recover it with the GB files make their phones nearly unrecoverable. So, now I've divided the guide in 2 sections : the GINGERBREAD VERSION and the ICS VERSION.

    Due to popular demand, I have also added an I9100G Version, which is here!

    I have also added the I9100 M/P/T versions. Now I support ALL I9100 variants.


    But for the moment, I do not have the G/M/P/T .PIT, kernels or Bootloader, so if you have any of those version, only flash what is in the provided package.


    __________________________________________________

    Let's start with the basic files, downloads and requirements

    GINGERBREAD VERSION

    1) You have to know the basics of ODIN and flashing (duh :p)

    2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
    Just in case you don't have them, here are the Samsung USB drivers

    3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

    4) Download the necessary files : the Recovery Package/ROM (password is samfirmware.com), the Kernel (password is [email protected]) and the Bootloader.

    5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
    You can also use 7zip, as sugested by jermitano :)

    ICS VERSION

    1) You have to know the basics of ODIN and flashing (duh :p)

    2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
    Just in case you don't have them, here are the Samsung USB drivers

    3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

    4) Download the necessary files : the Recovery Package/ROM [THIS PACKAGE ALREADY INCLUDES THE BOOTLOADER] (password is samfirmware.com) and the Kernel.

    5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
    You can also use 7zip, as sugested by jermitano :)

    I9100G VERSION

    1) You have to know the basics of ODIN and flashing (duh :p)

    2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
    Just in case you don't have them, here are the Samsung USB drivers

    3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

    4) Download the necessary ROM (they are Gingerbread 2.3.6) : Africa (Iraq), Asia (Malaysia), Europe (Open Austria), Middle East (Saudi Arabia). (password is samfirmware.com)

    5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
    You can also use 7zip, as sugested by jermitano :)

    I9100M VERSION

    1) You have to know the basics of ODIN and flashing (duh :p)

    2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
    Just in case you don't have them, here are the Samsung USB drivers

    3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

    4) Download the necessary files : the Recovery Package (Open Canada) (password is samfirmware.com).

    5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
    You can also use 7zip, as sugested by jermitano :)

    I9100P VERSION

    1) You have to know the basics of ODIN and flashing (duh :p)

    2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
    Just in case you don't have them, here are the Samsung USB drivers

    3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

    4) Download the necessary files : the Recovery Package (UK - Orange) GINGERBREAD VERSION / Recovery Package (UK - Orange) ICS VERSION (password is samfirmware.com).

    5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
    You can also use 7zip, as sugested by jermitano :)

    I9100T VERSION

    1) You have to know the basics of ODIN and flashing (duh :p)

    2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
    Just in case you don't have them, here are the Samsung USB drivers

    3) Download ODIN, the tool that we'll use to flash all the things into our beloved Galaxy S II ;)

    4) Download the necessary files : the Recovery Package (Australia - Telstra) GINGERBREAD VERSION / Recovery Package (Australia - Three/Vodafone) ICS VERSION (password is samfirmware.com).

    5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
    You can also use 7zip, as sugested by jermitano :)

    And that is it! Let's get down to business :)

    __________________________________________________

    If your GSII has the folowing symptoms :

    • Bootloop
    • Stuck on GSII logo, but already removed the battery to try to fix it
    • Enters Download mode and Recovery mode

    It means that you are soft bricked and is easy to solve.

    But if your symptoms are the mentioned above, PLUS the symptoms below

    • Enters Download mode but does NOT enter recovery mode (usually means a NAND rw corruption)
    • Doesn't flash
    • Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)

    Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.

    It's time to open up ODIN and start reviving your phone!

    __________________________________________________


    First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :

    ojgokk.png


    As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way. And the red one is well... Where you SHOULDN'T touch :p



    ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
    THAT THE FLASH WILL SUCCEED.

    Which means that you CANNOT have a damaged USB, corrupted drivers and such.


    When recovering from a soft brick, it is recommended, not mandatory, to have Re-partition ticked with a .PIT file. So you must be extra careful when you are using a .PIT and Re-Partition. And obviously, the red box is the one where you can't and don't want to mess with ;)

    But where are the files going, you say?

    .PIT -> PIT
    APBOOT -> BOOTLOADER (or PDA if flashed alone)
    CODE -> PDA
    MODEM -> PHONE
    CSC -> CSC


    ***If you have a 1 file .tar package, then flash it in PDA***​

    There is only 1 way to recover a soft bricked phone. How to recover from a NAND corruption? We'll get on that later on ;)

    __________________________________________________

    Recovering a soft bricked phone

    1) Grab the Recovery Package, and you'll see a bunch of .tar files. Take a look at the names. You'll see CODE, MODEM, CSC and .PIT. Put each one in its place.

    2) Turn off your phone. Enter Download mode by presing Volume Down + Home + Power button.

    3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9)

    Now here, take a breath

    First try flashing WITHOUT the .PIT and re-partition. And only if it DOESN'T WORK OR FIX then you flash with the .PIT and Re-Partition ticked.

    4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.

    Have you done everything correctly until now? Then...

    Congratulations on recovering your phone!

    You deserve some cake afterwards, and some rest :D

    Now, if your problem is the NAND rw coruption, and wasn't fixed by the above fix, then follow these steps :

    5) Download the Kernel. Flash it in PDA. Without ticking Re-Partitioning

    6) Successful? Nice, hope is still present.

    7) Flash the recovery package, following steps 1-4 This should fix your issue. If it does not, then :

    WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.

    8) Download the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partitioning

    9) Flash the Kernel, as in step 5

    10) Flash the recovery package, like in steps 1-4 And that will fix any of your issues :D

    11) After you have recovered your phone, I advise you to have your phone completely up to date by browsing and downloading the firmware for your version through SamMobile!

    I hope that this guide was helpful, and if it was, hit the thanks button! :)

    Credits mainly go to Intratech, for his amazing gallery of ROMS and files :)

    _______________________
    Disclaimer

    This is to be used as educational information. I am not liable of any damage that may occur to your phone.
    6
    Awesome guide! Thanks for taking the time to put this together! :)

    Thanks! :) I think I'll post this in Q&A... I feel it's more appropriate there.

    @Robotapocalypse Thanks for the headsup! :)
    4
    @Nands_2012

    Uninstall USB drivers using Revo uninstaller (PC), reboot.

    Find Samsung USB drivers (tap my sig, navigate back) v.1.5.27.0., install them, reboot.

    Find XXLSJ 4.1.2. ROM (tap my sig, navigate back, LSJ, extract it from zip, flash CODEI9100XXLSJ.tar as PDA in Odin, check md5 sum)
    1. Take your battery out from your phone for 5 minutes.
    2. Put it back, enter download mode
    3. Connect to PC
    4. Launch Odin, flash that XXLSJ.tar.md5 (don't try PIT, bootloaders or anything)
    5. All good?
    3
    Download mode is Volume Down. I think you miswrote that. Thanks for the write up.
    3
    Where is the OP?!?! :eek: :confused:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone