Database Info

[HOW-TO] Flashing with Odin/Heimdall

Please note that this is only a thread on HOW-TO and not a central place on where you can get your firmwares. There's several websites like SamMobile that can help you getting them.
All the Heimdall's instructions will be at the second post.
1. Q/A's (Introduction)
" I'm afraid I'll break my phone/tablet... "
1. What is download mode?
It's a special mode where the partitions are flashed into your phone. It's functionning is simillar to how fastboot works with other devices. (Nexus/HTC) It's normaly accessible by pressing the three-way button combinaison (Power + Home + Vol-) at the same time when turning on your device.
Click to expand...
Click to collapse
2. What's Odin then?
Odin, in this case, (not the mythologic one) is a windows program, a proprietary software from Samsung to flash numerous partitions. (/system, /cache, kernel etc) It is generally only used when in download mode.
Click to expand...
Click to collapse
3. If we have Odin, then why we do need Heimdall?
Heimdall is a cross-platform open source program that uses the same type of communication protocol that Odin uses to communicate with Samsung devices. It's very useful if for example you're using something like Mac OS or Linux. (in which Odin can't work natively without using some sort of Windows implementation)
Click to expand...
Click to collapse
4. Why sometimes I need to have a PIT file when I flash with either of these programs?
A PIT (Partition information table) which it's name indicates, is a file where regroups all your device's partition information. (such as name, size, offset, etc) It is possible to modify it but NOT RECOMMENDED unless you know what you're doing.
Click to expand...
Click to collapse
2. Odin Instructions for Original Samsung Galaxy S and Samsung Galaxy S II "based" devices
" Considered once before the best of Android... "
Device examples:
Samsung Galaxy S (I9000)
Samsung Galaxy S II (I9100)
Samsung Galaxy Note (N7000)
Samsung Galaxy Player/S Wifi (All)
2.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin3 v1.7
- A "pit" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.​
2.2 Little Glossary:
Left side:
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Auto-Reboot: Self-explanatory
F. Reset time: Don't know really what it is. (It looks like it can reset some counter)
Note: those 2 last boxes should always be checked
Dump: Not necessary..
Phone EFS Clear: You do not want to make this..
Phone Bootloader update: Not necessary unless you want to flash only the bootloaders. (you probably won't EVER touch this)
Right side:
PIT: Self explanatory once again, the file should normally come with a .pit extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
PHONE: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.​
2.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract the Odin3 v1.7.exe file from the zip
2. Execute Odin3 v1.7.exe
3. Put your device in download mode. To do so, press vol- while pressing the power button. The result of this combination should be this.
Note: The image is a result for the OG SGS based devices, The SGS II based ones should come with this instead after you bypassed the warning there.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms/Firmwares, Kernels, Bootloaders) (Modem: Radio/Baseband) (CSC: Csc file)
6. When you're clear with this, be sure to check throughously that the files selected were intended for your device
7. If a .pit file was selected when trying to flash, ensure that re-partition at the left is UNCHECKED!!
Note: If you're flashing Stock (Original) Samsung firmware, you MUST check the box. Failing to do so will likely brick the device...
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.​
2.4 Misc. Section:
While the Original Galaxy S isn't related, the Galaxy S II based devices have a flash counter regarding on how much time you flash while in download mode. It's count goes up everytime you flash something in this particular mode. When the number is higher than 0, you LOSE your waranty. Be Warned!!
That said, there are ways to fix those problem by either buying a USB jig, or using an app like Triangle Away made by Chainfire.
​
​​
3. Odin Instructions for the Samsung Galaxy S III "based" devices
" Designed for humans is the new way to go... "
Device examples:
Samsung Galaxy S III (I9300)
Samsung Galaxy Note II (N7100)
Samsung Galaxy Note 10.1 (N8000)
Samsung Galaxy S III Mini (I8190)
Samsung Galaxy Camera (EK-GC100)
3.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin V3.07
- The files you'll want to flash
- A "pit" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.​
3.2 Little Glossary:
Left side:
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Auto-Reboot: Self-explanatory
F. Reset time: Don't know really what it is. (It looks like it can reset a counter in older device...)
Note: those 2 last boxes should always be checked
Flash Lock: Not sure what this does
LED Control: This as well
Nand Erase All: You do not want to touch this...
Right side:
PIT: Self explanatory once again, the file should normally come with a .pit extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
PHONE: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
UMS: I'm not sure as what this section does, it is greyed out by defaut so it must have some sort of specific usage. (but not for us anyway..)
Bottom side:
Start: Self explanatory...
Reset: Reset all the values to Odin's default.
Exit: Self explanatory again...​
3.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the Odin307.zip
2. Execute Odin3 v3.07.exe
3. Put your device into download mode. The result should be like this after you bypassed the warning there.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed!
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms, Kernels, Bootloaders) (Modem: Radio/Baseband) (CSC: Csc file)
6. When you're clear with this, be sure to check throughously that the file is intended for your device
7. If a .pit file was selected when trying to flash, ensure that re-partition at the left is UNCHECKED!! (Unless if it's going back to the stock Samsung firmware)
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.​
3.4 Misc. Section:
All the Galaxy S III based devices have a flash counter regarding on how much time you flash while in download mode. It's count goes up everytime you flash something in this particular mode. When the number is higher than 0, you LOSE your waranty. Be Warned!!
That said, there are ways to fix those problem by either buying a USB jig, or using an app like Triangle Away made by Chainfire.
However be careful with the newer Knox bootloaders that came with the newer 4.3 Touchwiz updates as there's NO way of resetting the counter AND/OR downgrading it.
​
​​
4. Odin Instructions for the Samsung Galaxy S4 "based" devices
" With the increasing popularity comes more restrictions... "
Device examples:
Samsung Galaxy S4 (I9500)
Samsung Galaxy Note II (N9000)
Samsung Galaxy Note 10.1 2014 Edition (SM-P600)
Samsung Galaxy S4 Mini (I9190)
4.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin V3.07
- The files you'll want to flash
- A "pit" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.​
4.2 Little Glossary:
Left side:
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Auto-Reboot: Self-explanatory
F. Reset time: Don't know really what it is. (It looks like it can reset a counter in older device...)
Note: those 2 last boxes should always be checked
Flash Lock: Not sure what this does
LED Control: This as well
Nand Erase All: You do not want to touch this...
Right side:
PIT: Self explanatory once again, the file should normally come with a .pit extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
PHONE: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
UMS: I'm not sure as what this section does, it is greyed out by defaut so it must have some sort of specific usage. (but not for us anyway..)
Bottom side:
Start: Self explanatory...
Reset: Reset all the values to Odin's default.
Exit: Self explanatory again...​
4.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the Odin307.zip
2. Execute Odin3 v3.07.exe
3. Put your device into download mode. The result should be like this after you bypassed the warning there.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed!
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms, Kernels, Bootloaders) (Modem: Radio/Baseband) (CSC: Csc file)
6. When you're clear with this, be sure to check throughously that the file is intended for your device
7. If a .pit file was selected when trying to flash, ensure that re-partition at the left is UNCHECKED!! (Unless if it's going back to the stock Samsung firmware)
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.​
4.4 Misc. Section:
All the Galaxy S4 based devices have the Knox flash counter which is MORE PROACTIVE than the flash counter inside the GSII/GSIII based devices. Upon flashing something that has not been signed numerically by Samsung, the eFuse is burned off and there's NO possible way of reverting the counter back to 0. (because of an HARDWARE failure)
PROCEED AT YOUR OWN RISK!
​
​​

5. Odin Instructions for the Samsung Galaxy ARMv6 "based" devices
" Underpowered, they're still fighting through the end... "
Device examples:
Samsung Galaxy Ace (S5830)
Samsung Galaxy Gio (S5660)
Samsung Galaxy Mini (S5570)
Samsung Galaxy Fit (S5670)
5.1 Odin Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers
- Odin Multi Downloader v4.42
- The files you'll want to flash
- An "ops" file (Only need for when you re-partition. It can be found in your device's respective forum)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)
Note: It is recommended to plug the device in download mode before executing Odin so the computer will recognize it and do the final preparation for the first time you'll want to flash something.​
5.2 Little Glossary:
Left side:
One Package: If you have a one package firmware, (one that has every partition regrouped into one) you may check this box and take your one package file from your computer.
Auto-Reboot: Self-explanatory
Protect OPS: Need further info on that one but looks like it protects the internal OPS file from inside the device if you use a OPS while while flashing something.
Reset time: Don't know really what it is. (it looks like it can restart odin after a set number of time after having initially pressed "start")
Note: those 3 last boxes should always be checked
DEBUG ONLY: Well it is what it says. There's no option you'll really use in this part so I won't describe it as it's not necessary.
Right side:
OPS: This serves as the equivalent of PIT for some devices, it has information for the partitions from your device. it comes with a .ops extension.
BOOT: Not sure what this box is. From what I see, this box isn't even used...
Phone: This is where the Modem (Baseband) will go. It will normally contain "MODEM" in it's name. Once again, it will come with the .tar.md5 extension.
PDA: Normally this is where your firmware (ROM along with kernel) will be flashed. It contains the "PDA" name in it as well as the .tar or the .tar.md5 extension.
CSC: File that contains information from a specific network operator. (to use some special feature) You won't probably use this case if you're locked into a particular network... It does contain "CSC" in it's name and it comes with the .tar.md5 extension.
EFS: This is the file that contains the most sensible information of your phone (IMEI, S/N, MAC addresses, etc...) it comes also with the .tar or .tar.md5 extension.
One Package: If you do happen to have a "One Package" file, you can use it to flash all it's contents into your device.​
5.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Odin actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the OdinMultiDownloaderv4.42.zip
2. Execute Odin Multi Downloader v4.42.exe
3. Put your device into download mode. The result should be something similar to this after you maybe had this beforehand.
4. You should see a yellow rectangle with COM:xx and saying ready. It means that your device is ready to be flashed!
5. Depending on what you're flashing, take it to the corresponding box (PDA: Roms, Kernels) (Modem: Radio/Baseband) (CSC: Csc file) (EFS: EFS file)
6. When you're clear with this, be sure to check throughously that the file is intended for your device
7. If a .opt file was selected when trying to flash, ensure that "Protect OPS" at the left is CHECKED!!
8. Press the flash button
9. It should go through the flashing, you should see the partitions that's being flashed into device during this time.
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.
10. When everything is finished, the program should ouput that it's done with a green box and your device should reboot automatically.​
5.4 Misc. Section:
I would need more information. If you could send some, it would be appreciated!
​
​​
6. Heimdall Instructions
" At last, an alternative has been found... "
Heimdall should work at least with the following devices (I'll add more if necessary)
Samsung Galaxy S (I9000)
Samsung Galaxy S II (I9100)
Samsung Galaxy S III (I9300)
Samsung Galaxy S4 (I9505)
Samsung Galaxy Player (All)
6.1 Heimdall Prerequistes:
When you need to flash using either Odin or Heimdall (with Windows), you need the USB drivers. You can use either kies or the standalone USB drivers. (I prefer the USB drivers because Kies is not what I would take for a first choice...)
- A working brain
- A working computer
- Samsung USB Drivers (for Windows only)
- WinUSB drivers installed (From zadig.exe, once again Windows only)
- Udev rules set-up for your Samsung device (for Linux only)
- Heimdall's Official Webpage
- The files you'll want to flash
- An "pit" file (needed for Heimdall to actually flash on your device)
- A stock samsung USB cable if possible (it seems to give better result than other USB cable bought on third party sellers.)​
6.2 Little Glossary:
Load Package Tab:
We won't really use it... Unless you have an Heimdall package but you should already know how to use it...
Flash Tab:
PIT: Self explanatory once again, the file should normally come with a .pit extension. Also you have to select it in order to be able to flash (unless you're using the terminal)
Re-Partition: Actually means what it means, it re-partitions your device according to the pit file you've given. It's only necessary to check it when flashing back to fresh STOCK and doing it without any further objective will BRICK your device.
Add: Pretty simple, Adding the partition you wanted to be flashed according to the "pit" file you've selected
Remove: Pretty simple once again, this time it's to remove the partition you've selected.
No reboot: Won't reboot after all the flashing has been done.
Resume: (use after "No reboot") This is only to continue the session of "flash" as of after you've flashed something with Heimdall and you decided to press "No reboot", Heimdall stops communication with your device and you would need then to reboot it back into "download" mode to get it back working again
Create Package Tab:
Won't really explain because it's not that "much" used so it won't be useful for the purpose of this thread
Utilities Tab:
Detect Device: Obvious but for debugging purposes it can be useful.
Close Pc Screen: This affects more older Samsung devices (like the original Galaxy S) that when something went wrong with a flashing this picture would get in when you turned on your device. This button fixes it.
Download Pit: Here you can grab the .pit file from your device and save it through your computer. (Useful if you do need one but can't find it anywhere or for specific debugging purposes)
Print Pit: Here you can see the content of the .pit file from either two places: From your device or from a pit file you have on your computer. The result will be displayed on the "Output" window.
Partitions:
IBL+PBL: Primary bootloader, you mess with it, your device is a plastic brick... (Normally it should be a file named boot.bin)
SBL: Same thing as IBL+PBL. (It should be a file named sbl.bin)
SBL2: Acts as a backup of the original SBL partition. I don't really know if this could boot up when the first SBL is borked up.
PARAM: It's a file that "controls" the bootloaders on the initial device's boot. (param.lfs)
CACHE: It's actually your cache partition (The older Samsung models would have a file named cache.rfs, newer Samsung models though should be something like cache.img)
EFS: This partition is very important because all the "sensitive" data of your device is there: S/N, IMEI, MAC addresses. (Older models: efs.rfs, Newer models: efs.img)
RECOVERY: That's the recovery partition, where your recovery will be at. It serves as a unused kernel partition for the original Galaxy S. (It should be something like recovery.img for newer devices)
FACTORYFS: This is where your OS (/system) is. (Older models: factoryfs.rfs, Newer models: factoryfs.img)
KERNEL: It is what it is basically. It's where your kernel will be flashed. (Older models would be zImage/boot.img/normalboot.img where's the newer models comes more with boot.img)​
6.3 Flashing Time:
When you have finished with installing your drivers and your device has been recognized in both "normal" mode and "download" mode, you can proceed with the flashing. Here you can find a picture of Heimdall on the "Flash" tab actually running. (Can be useful if you want a landmark on what to expect)
1. Extract all the files from the from the Heimdall zip you download
2. Execute Heimdall-frontend.exe on Windows, the Heimdall executable on Mac OS or on your Linux terminal, type "heimdall-frontend"
3. Put your device into download mode.
4. Plug your device into your computer. If you go to the "Utilities" tab and press the "Detect Device" Button. If it has been detected, you can continue on.
5. Go on the "Flash" tab. From then, you need to take up a .pit file that has been saved into your computer.
6. After taking your .pit file, you'll need to add a partition. Then selecting the partition you'll need to flash from the dropdown menu.
7. Be sure to check carefully each partition so you know that each partition equals their file counterparts.
8. When that is done, depending on if you're going to stock or not, check the "Repartition" box.
9. After you've been SURE that ALL those check-ups have been made, press the "Start" button.
10. Let the program do it's things. Then when it's done, your device should reboot automatically and it's a SUCCESS!!
Note: DO NOT EVER unplug the cable as the result will probably be a pricey plastic brick in your hands now.​
6.4 Misc. Section:
- Heimdall CAN'T possibly work with every device. You mostly have to test for yourself if Heimdall works for you.
- When you install your drivers from zadig.exe, it "overwrites" Odin drivers which will make your device unusable with Odin. It's kinda like a trade. If you want to use Odin, you can't use Heimdall and vice-versa.
- If you happen you have an "Odin" flashable package and you want to flash using Heimdall, you can remove the ".md5" extension from your file and then extract the ".tar" file contents, you should get each of the partitions that can be flashable via Heimdall.
​
​​
7. Thanks
" The roots provided by them grew into this tree... "
Google
Samsung
@SamHaLeKe
@Benjamin Dobell
@Perseus71
@LuigiBull23
​

Reserved...

wow great tutorial iknow how hard to be a newbie coz i experienced of hard time flashing when i newly purchased sgs 4 .
btw ur the man, great effort! i know someday we will be crowded here because of this tutorial
keep up the good heart sir
Gonna subscribe and hit 5star.
it should be sticky thread too
Sent from my YP-G1 using xda premium

rockerblood said:
wow great tutorial iknow how hard to be a newbie coz i experienced of hard time flashing when i newly purchased sgs 4 .
btw ur the man, great effort! i know someday we will be crowded here because of this tutorial
keep up the good heart sir
Gonna subscribe and hit 5star.
it should be sticky thread too
Sent from my YP-G1 using xda premium
Click to expand...
Click to collapse
Well I think it should have been better to add it before but it's better now than never. Also I'll put all the pit files here tomorrow so if you want them when you'll flash, they will be there and you wont have to search around and around.

i think thats a good idea
keep up the good heart and work sir

Thanks for posting. I flashed TerraSilent kernel.
However, I still don't have root access. As I posted before, I cannot find a root method for 2.3.6 on the US Player 4, and this seems to still be the case (for whatever reason after flashing, About Phone now reports Android 2.3.5, but I know this is impossible, as I did not flash any ROM).
(Also, right before the TerraSilent boot logo comes up, the upper half of the display shows some lines for a split second. This is not an issue, just wondering why it is there.)

TheTehk17 said:
Thanks for posting. I flashed TerraSilent kernel.
However, I still don't have root access. As I posted before, I cannot find a root method for 2.3.6 on the US Player 4, and this seems to still be the case (for whatever reason after flashing, About Phone now reports Android 2.3.5, but I know this is impossible, as I did not flash any ROM).
(Also, right before the TerraSilent boot logo comes up, the upper half of the display shows some lines for a split second. This is not an issue, just wondering why it is there.)
Click to expand...
Click to collapse
But AFAIK, I never knew that the US player had 2.3.6. Anyway you can root with which ever GB root you can find as this kernel is insecure which means that you have a root shell by default.

zaclimon said:
But AFAIK, I never knew that the US player had 2.3.6. Anyway you can root with which ever GB root you can find as this kernel is insecure which means that you have a root shell by default.
Click to expand...
Click to collapse
Got mine rooted now, thanks. I'm used to rooting and contributing for/with devices like the Samsung Moment and other s3c6410-based devices so this stuff is all new to me.
Yep, mine shipped with 2.3.6. I might make a guide so that others in the same boat as me know what to do.

Hey I said earlier this week I would put some pit files, well it better now than never. Sorry for the delay. With school and ICS porting, I don't have really the time to do it. Anyway the pit are here now.

Posting this in a few places but I recommend you note in the OP that this will always be best accomplished using a STOCK Samsung usb cable. Depending on how close to "bricked" the device is it is very possible the device will not be recognized by the pc unless the stock cable is used. I think this little bit of information will be very helpful and may save a lot of heartache for some in the future.

Jiggity Janx said:
Posting this in a few places but I recommend you note in the OP that this will always be best accomplished using a STOCK Samsung usb cable. Depending on how close to "bricked" the device is it is very possible the device will not be recognized by the pc unless the stock cable is used. I think this little bit of information will be very helpful and may save a lot of heartache for some in the future.
Click to expand...
Click to collapse
Alright it's taking into note. Thanks!

Alright I was given the 4.0 with it running an ICS ROM. I was not familiar with Samsung devices and rooting, and in thinking it was like my DINC2, I put it into recovery and since then I have tried to read all the forums to get it to work and to put it back to a stock ROM....... I haven't found a solution, and I am not sure if I missed a step in a forum, but I can get the device into a different recovery with blue lettering and only a few select options, but as far as getting it to boot up with the actual ROM I have had 0 success on any of it.... Any help?????? P.M. me or I can give my email if it would help at all, or any help what so ever would be great. Thanks.
P.S. It is the US version if that was a question.

Brennon19968 said:
Alright I was given the 4.0 with it running an ICS ROM. I was not familiar with Samsung devices and rooting, and in thinking it was like my DINC2, I put it into recovery and since then I have tried to read all the forums to get it to work and to put it back to a stock ROM....... I haven't found a solution, and I am not sure if I missed a step in a forum, but I can get the device into a different recovery with blue lettering and only a few select options, but as far as getting it to boot up with the actual ROM I have had 0 success on any of it.... Any help?????? P.M. me or I can give my email if it would help at all, or any help what so ever would be great. Thanks.
P.S. It is the US version if that was a question.
Click to expand...
Click to collapse
Sorry for the late reply but try this:
http://forum.xda-developers.com/showthread.php?t=1531850

zaclimon said:
Sorry for the late reply but try this:
http://forum.xda-developers.com/showthread.php?t=1531850
Click to expand...
Click to collapse
Alright thank you. I will have to try it when I get home from the hospital visit.
Sent from my Incredible 2 using xda app-developers app

SGP YP-G70 International Heimdall Froyo Stock Rom with bootloaders
zaclimon said:
Heimdall Instructions
I generally prefer flashing with heimdall because it's better than odin (but less simple) and it's cross platform.
More information on Heimdall: http://forum.xda-developers.com/showthread.php?t=755265
3.1 Heimdall Prerequistes
- Samsung USB Drivers
- Heimdall
3.2 Flashing With Heimdall
3.2.1 Drivers installation (Windows)
These are a FIRST time installation only for the libusb drivers.
1. Extract the heimdall folder somewhere in your computer.
2. Go in the heimdall folder and then drivers. You should see a file named zadig.exe
3. Execute zadig.exe and then check list all devices
4. You should see a samsung device listed.
5. Install the drivers, you should have an error concerning certificate (It's NORMAL, install them anyway). You must do this in home screen and in download mode.
3.2.2 Flashing
6. When this is done, Open heimdall-frontend.exe,
7. Go in the flash section and take your .pit file according to your device.
8. Select the partitions you want to flash and take the file according to it.
9. Ensure that all the partitions you've selected are good.
10. Flash!!
11. Your device should reboot by itself and it should work!:good:
If you have more questions/suggestions, ask them in the thread and I will answer it as soon as I can.
4. Pit Files
Here's the pit files needed if you need to re-partition
4.0 Intl: 4.0 Intl Download
4.0 Us: 4.0 Us Download
4.0 Kor: 4.0 Kor Download
5.0 Intl: 5.0 Intl Download
5.0 Us: 5.0 Us Download
5.0 Kor: 5.0 Kor Download
Thanks:
Google: For such a good OS
Samsung: For making such good devices (and Odin )
Benjamin Dobell: For Heimdall
SamHaLeKe: For the USB drivers
All the uploaders of the pit files
Click to expand...
Click to collapse
Can anyone share the right file or files to flash SGP YP-G70 International (with physical home button) with Stock Froyo (or other ROM) wich inclues the bootloaders?
How should I proceed to flash it?
Despite all information we find here there is always some details we don't know how to handle. I followed the instructions with Odin and the result was: PASS (green) but SGP wont reboot or turn on. I always think there is some missed detail.
Please help me to have it working again so I will right a full restoring procedure from the begining (hard brick) until the end to help our brothers to recover their devices as well.
I thank you very much in advance

mrlightman said:
Can anyone share the right file or files to flash SGP YP-G70 International (with physical home button) with Stock Froyo (or other ROM) wich inclues the bootloaders?
How should I proceed to flash it?
Despite all information we find here there is always some details we don't know how to handle. I followed the instructions with Odin and the result was: PASS (green) but SGP wont reboot or turn on. I always think there is some missed detail.
Please help me to have it working again so I will right a full restoring procedure from the begining (hard brick) until the end to help our brothers to recover their devices as well.
I thank you very much in advance
Click to expand...
Click to collapse
Seems that you never tried with heimdall as I told you right? Also because your case is very rare, (you're the 1st or the 2nd with this particular hard brick case), I never really took the time to write down. Well first of all, is your device recognized by your computer outside of the download mode?

SGP 5.0 YP-G70 wont turn on
zaclimon said:
Seems that you never tried with heimdall as I told you right? Also because your case is very rare, (you're the 1st or the 2nd with this particular hard brick case), I never really took the time to write down. Well first of all, is your device recognized by your computer outside of the download mode?
Click to expand...
Click to collapse
I haven't tried yet cause I'm not sure how to do it. I was searching for ROMs to use in Heimdall and I found just the PIT file.
Can I use the exact same ROM I used to flash with Odin?
The device is recognized by PC just when I have it into download mode using Adam Outlers method (Unbrickable Resurrector)

mrlightman said:
I haven't tried yet cause I'm not sure how to do it. I was searching for ROMs to use in Heimdall and I found just the PIT file.
Can I use the exact same ROM I used to flash with Odin?
The device is recognized by PC just when I have it into download mode using Adam Outlers method (Unbrickable Resurrector)
Click to expand...
Click to collapse
Yeah you can use the same rom as what you used with odin. You can follow this thread instruction on how to. You may need to flash the bootloaders so here's the name of them
IPL+PBL: boot.bin
SBL: sbl.bin
PARAM: param.lfs

SGP 5.0 YP-G70 wont turn on
zaclimon said:
Yeah you can use the same rom as what you used with odin. You can follow this thread instruction on how to. You may need to flash the bootloaders so here's the name of them
IPL+PBL: boot.bin
SBL: sbl.bin
PARAM: param.lfs
Click to expand...
Click to collapse
Well I'm trying to do that. Heimdall requires a Pack and I'm trying to use the ROM (tar) files I used to flash with Odin. The matter is that Heimdall always says firmware.xls is missing from the package and maybe that the exact point wich drove me flaw (I dont know).
Can you please share with me the right package including the firmware to make me able to flash it?
I already have the PIT file and I remember that the SGP was using Froyo before all my mass (having it bricked). My SGP is 5.0 YP-G70 International with physical home button.

[SAMSUNG GALAXY S3 TOOLKIT V9] Drivers, Backup, Root, CWM, BusyBox + MORE [VZN]

INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry). If you have a GT-I9300 GSM Model then you can do this from the Toolkit but if you have an LTE device then it isn't soo easy to do. If you have an LTE device you should go to *THIS* thread by lyriquidperfection and follow the information to save your IMEI/NV Data so that you are covered if anything should happen.
----------------------------------------------------------------------------
Q. Is there currently no way to root the Samsung Galaxy S3 without voiding the warranty?
All methods of rooting will void your warranty in some way as you will have superuser files on your phone that arent supposed to be there. There is a method of rooting your phone without increasing the flash counter which involves flashing a complete rom with root files already added but if anything happens and you need to send it back under warranty you will need to flash a 'proper' Stock Rom back before returning it or your warranty will be void. Flashing a custom kernel or recovery to root will increase the flash counter and also void any warranty. There is currently no method of resetting the flash counter on Snapdragon models but im pretty sure there will be some support for it soon. If you dont want to risk it or you aren't sure then you shouldnt really be flashing your phone and should just leave it alone. Its your choice .
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.

**reserved if needed**

\o/ Been waiting for this show up on this device Much appreciated!

I feel so informed already. Even without anything in it
Sent from my SCH-I535 using Tapatalk 2

Getting ahead of ourselves.
I noticed "Reserved for future" follow up posts, which are everywhere, largely go unused. And I ignore it all the time, but right now I'm looking at a blank follow up post that's following a blank post.
;D
** Space reserved for potential future edits **
** Reserved for editing the edits **
Sent from my SCH-I535 using Tapatalk 2

RELEASE OF THE NEW UNIFIED S3 TOOLKIT V7.0.0 [10TH JAN 2013]
ChangeLog:
ToolKit v7.0 (10th January 2013)
+International and Snapdragon Toolkits have been unified into a single Galaxy S3 Toolkit
+Rewritten how the Toolkit works to keep all tasks common to other Toolkits in a seperate executable
+After model is selected the Toolkit will now download ONLY the files needed to cut down on install size
+Seperated all supported devices by model number
+Added support for new S3 variants
+Added support for latest builds on all models
+Updated all cwm and twrp recoverys to the latest version and given each model its matching recovery
+Updated SuperSU files by Chainfire to 0.99
+Added new root methods
+Added flash zip file by sideload function in recovery
+Fixed many functions and made other functions more accessible and easier to understand
+Added Instant Reply donation link to get codes out to people much quicker without waiting for a manual response
+Previous Snapdragon and International Toolkit codes will still work with the new unified version
+Soo many more changes to integration and operation I cant list them all
I have been working on this for over 3 weeks and its finally completed
This new unified S3 Toolkit brings together the International and Snapdragon models under a single Toolkit to make updating and maintenance a lot easier. This new version also is the first of my Toolkits to download the model files as needed to make the intial download smaller and avoid accidentally selecting the wrong models image which could lead to trouble. Please read the 1ST POST again as I have changed some information in it. The Toolkit also has an Information section built in so use it as there is allot of useful stuff in there.
One thing I would like to mention is that all the boot images are pure stock with just the rooting process applied to the insecure images. As some Custom Roms are built with their own kernels you may find that if you have a Custom Rom and flash the Toolkits boot image your device boots fine and will have adb root access but wifi and bluetooth don't work. There is nothing I can do about this because of the change to some Custom Roms but it is very easy to just flash the boot image that is linked to the Rom you are using after you have done what you need to. Everything 'should' work perfectly on Stock Roms.
I have had to make some of the boot image blind as no testers came forward to test. If any of the image do not work to boot your device please do not start screaming and shouting, let me know and I will do my best to fix it as soon as possible. In any case (apart from in custom roms as stated above) the stock boot image will always get your device working again. Because the model specific files are downloaded by the Toolkit, if you need to redownload the boot files because they either didnt download/extract properly or because they had to be fixed then all you have to do is to delete your model folder from the root folder in the Toolkit, restart the Toolkit and select your Model/build and it will force the Toolkit to download the model file again.
Download links in the 1st post.
Enjoy.
Mark.

First I want to say thank you Dev for all of your work on these toolkits. I was happy to donate to unlock the extra features. I'm hoping someone can help me with something though. whenever I try pull the sd contents back to my pc, I get the following... It seems to run through all the commands properly but at the end it says
": No such file or directory
An Error Occurred.
Press any key to return to the Main menu..."
All the other backup features seem to run fine. I haven't had the need to run any of the other features yet. I'll attach a printscreen. Thanks in advance for any help on this!

Trying to root Verizon s3 4.1.1. The device is recognized fine and everything is standard. When I go to root (all in one) I select the correct .tar file but Odin fails. It says "secure check failed" on my phone. No dice there. I've used this in the past on my Sprint S3 and it couldn't have been easier. I'm guessing is something is up with the TAR. I've tried a lot of other options to the same result.
I got similar results when I tried just flashing the recovery option (4). Also I have tried this on multiple computers as well with identical results. I've also re-installed the drivers, tried using "Camera mode" on the usb connection, different root files etc etc to not avail.
ODIN Results:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

big blue said:
First I want to say thank you Dev for all of your work on these toolkits. I was happy to donate to unlock the extra features. I'm hoping someone can help me with something though. whenever I try pull the sd contents back to my pc, I get the following... It seems to run through all the commands properly but at the end it says
": No such file or directory
An Error Occurred.
Press any key to return to the Main menu..."
All the other backup features seem to run fine. I haven't had the need to run any of the other features yet. I'll attach a printscreen. Thanks in advance for any help on this!
Click to expand...
Click to collapse
I have a feeling the filename is too long for windows to handle and so it crashed the procedure. Try deleting the file if it isnt important and it should complete.
Mark.

svinyard said:
Trying to root Verizon s3 4.1.1. The device is recognized fine and everything is standard. When I go to root (all in one) I select the correct .tar file but Odin fails. It says "secure check failed" on my phone. No dice there. I've used this in the past on my Sprint S3 and it couldn't have been easier. I'm guessing is something is up with the TAR. I've tried a lot of other options to the same result.
I got similar results when I tried just flashing the recovery option (4). Also I have tried this on multiple computers as well with identical results. I've also re-installed the drivers, tried using "Camera mode" on the usb connection, different root files etc etc to not avail.
ODIN Results:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you unlocked the Bootloader as stated at the start for verizon models?
Mark.

SAMSUNG GALAXY S3 TOOLKIT AUTO UPDATE V7.1.0 [22ND JAN 2013] AVAILABLE!!
Changelog:
+Added support for GT-I9300 build XXELLC
+Fixed US variants versions displayed incorrectly in Model Selection screen
+Added GT-I9300 TWRP Recovery 2.3.3.1 image to Toolkit for easy flashing
+Improved CWM NAND Backup script to make it allot more stable and robust
+Added Insecure Kernel detection to sections requiring Insecure Boot Image
+Added 'Pull Folder' to 'Pull Files' section in Main Menu
+Added 'Fix Internal Storage Permissions' to Mods Menu [folder not showing]
+Minor bug fixes and improvements
[Auto Updates are only accessible if you have donated to the Toolkit project, received an activation code and unlocked the donator features. Auto Updates are a much faster and easier way of pushing small updates that would otherwise not be worth doing. I can push a single textual change or add support for a new build without having to go through the whole process of building a full version and uploading a large file. IF you are not able to or do not want to donate to unlock the Auto Update feature (and other donator features) then all the smaller updates are collated and a full build made when I have time or if there are enough updates to warrant it. This is the easiest way to make sure all the Toolkits are as up to date as possible. IF you have any views about this please pm me about them and do not post in the open thread]
Enjoy
Mark.

mskip said:
Have you unlocked the Bootloader as stated at the start for verizon models?
Mark.
Click to expand...
Click to collapse
dang it. I swore I wouldn't be the guy that just missed the step talking about this. Yeah I see it in there now.
Now in the verizon instructions, I went to link #1 regarding bootloader info and then to link #2 regarding the process to follow. The link #2 states that it only works for 4.0.4 though and with all the "brick" talk I was hesitant to give it a try. As a note I did select the 4.1.1 option in the toolkit (a2).
Am I missing something or do I need to do something different for a Jelly Bean bootloader unlock? I want to certainly stick with your supported methods.
edit:
In your instructions it references this link (#2) for unlocking the 4.1.1 bootloader: http://forum.xda-developers.com/showpost.php?p=30274025&postcount=317
---------- Post added at 08:03 PM ---------- Previous post was at 07:39 PM ----------
I'm assuming I can just follow the method from this post and should be good to go with Root/Unlock/CWM
http://forum.xda-developers.com/showthread.php?t=2046439
Once that is out of the way I can just backup and flash away right? (I know that is how it has been for everything else but want to be sure I'm not missing something again).
BTW, me skipping over the text that asks me "to read" everything reminded me of this lol:
http://www.southparkstudios.com/clips/382791/can-it-read

svinyard said:
dang it. I swore I wouldn't be the guy that just missed the step talking about this. Yeah I see it in there now.
Now in the verizon instructions, I went to link #1 regarding bootloader info and then to link #2 regarding the process to follow. The link #2 states that it only works for 4.0.4 though and with all the "brick" talk I was hesitant to give it a try. As a note I did select the 4.1.1 option in the toolkit (a2).
Am I missing something or do I need to do something different for a Jelly Bean bootloader unlock? I want to certainly stick with your supported methods.
edit:
In your instructions it references this link (#2) for unlocking the 4.1.1 bootloader: http://forum.xda-developers.com/showpost.php?p=30274025&postcount=317
---------- Post added at 08:03 PM ---------- Previous post was at 07:39 PM ----------
I'm assuming I can just follow the method from this post and should be good to go with Root/Unlock/CWM
http://forum.xda-developers.com/showthread.php?t=2046439
Once that is out of the way I can just backup and flash away right? (I know that is how it has been for everything else but want to be sure I'm not missing something again).
BTW, me skipping over the text that asks me "to read" everything reminded me of this lol:
http://www.southparkstudios.com/clips/382791/can-it-read
Click to expand...
Click to collapse
As far as I know it will work just as well on 4.1.1. Just download the casual app, select root with DebugFSRoot and 'do it', then select 'Flash unsecure Aboot' and 'do it'.
You will then be able to flash anything to your device so be careful and do not accept OTA updates. If you want to flash roms stick with cwm zip versions.
Mark.

It's my first time flashing my VZW s3. How much do i have to donate for the donater features and how do i activate it? I want to put a custom rom on here as well. Does using this utility unlock the bootloader, give me root, and flash a custom recovery? Im sorry for the many questions, I haven't flashed since i had my HTC Sensation.
EDIT:
Do I have to go through this process first http://forum.xda-developers.com/showthread.php?t=2046439? And do I need ODIN images?

tracerman said:
It's my first time flashing my VZW s3. How much do i have to donate for the donater features and how do i activate it? I want to put a custom rom on here as well. Does using this utility unlock the bootloader, give me root, and flash a custom recovery? Im sorry for the many questions, I haven't flashed since i had my HTC Sensation.
EDIT:
Do I have to go through this process first http://forum.xda-developers.com/showthread.php?t=2046439? And do I need ODIN images?
Click to expand...
Click to collapse
EDIT 2:
I went head with that other process and I got everything done.

mskip said:
As far as I know it will work just as well on 4.1.1. Just download the casual app, select root with DebugFSRoot and 'do it', then select 'Flash unsecure Aboot' and 'do it'.
You will then be able to flash anything to your device so be careful and do not accept OTA updates. If you want to flash roms stick with cwm zip versions.
Mark.
Click to expand...
Click to collapse
Thanks for the info. I did end up just following this http://forum.xda-developers.com/showthread.php?t=2046439 and found that it was surprisingly really easy.
As a note, FYI everything I found said that DebugFSRoot doesn't work on 4.1.1 hence I moved away from the method.

I had some drivers installed before I downloaded this so I uninstalled them and installed the drivers that came with the toolkit but my serial is still not showing up...
when i go to device manager, I dont see Samsung Android Phone, I see SAMSUNG MOBILE USB Composite Device - is that right as well? I'm on JRO03C BLK3 if it matters...
thanks in advance!

So can I root using this? I just recieved a replacement S3 and I need to reroot.
Edit: Nevermind, it appears I can not

NightxFall said:
So can I root using this? I just recieved a replacement S3 and I need to reroot.
Edit: Nevermind, it appears I can not
Click to expand...
Click to collapse
If the bootloader has been unlocked (which requires root in the first place) then the Toolkit can update or change the root files.
Blame Verizon not me
Mark.

[Q] note 10.1 stuck on samsung logo

Hi guys, I need your help. I've got galaxy note 10.1 tab. I stupidly tried flashing cwm through rom manager, even though it wasn't compatible! Now, I'm stuck on the samsung logo when booting up. It is rooted via exynos abuse. Its on stock rom and no custom recovery. I can get to download mode and the android recovery. On top of that, I've been trying to install odin on my computer, but its not working, keep getting Korean message, and when I click ok, the odin window comes up for a split second, then disappears. I really need some help please.
Thanks in advance

Try googling about download mode and fastboot utilite from Android Development Bundle
With this utilite you can try to flash recovery image

Result!!!
Firstly thanks to xxxTy3uKxxx for the prompt reply to my question. It helped me look in the right direction to sort my blunder! In the end I couldn't use the above method because it required to have the tablet in "USB DEBUGGING MODE" which I couldn't do because I couldn't get the damn thing on!
So, now that I've fixed it (if I didn't my missus would have killed me) I wanted to share with all as there doesn't seem to be a lot of solutions around to fix this problem!
From the above post you can see what the problem was, I was only able to get to either download mode or the android stock recovery, and the phone was not booting past the "note 10.1" logo
- I basically had to download the "rootgalaxynote10.1" zip file from rootgalaxynote.com.
- Then, using Odin I flashed the "highonandroidCWMrecoveryGTN8000.tar" file. This gave me custom recovery (you can't flash roms with stock android recovery)
- From here I downloaded a rom for my N8010, and put in on a micro sd card. Put this in the note 10.1, then used custom recovery to flash this rom
NB. I encountered a problem with Odin, and that was I couldn't open it on my lap top! I downloaded numerous files/versions, but no luck. Some forums said to run as administrator or switch off firewall/anti-virus, but nothing worked! I then tried it on a different lap top and VOILA! I don't know why, but it worked on different lap top!
I hope this helps someone out in the future
PS. Hit thanks if I saved your back side

Biggup to u both. Almost thought id lost my tablet after I committed the very same crime

mimik1 said:
Firstly thanks to xxxTy3uKxxx for the prompt reply to my question. It helped me look in the right direction to sort my blunder! In the end I couldn't use the above method because it required to have the tablet in "USB DEBUGGING MODE" which I couldn't do because I couldn't get the damn thing on!
So, now that I've fixed it (if I didn't my missus would have killed me) I wanted to share with all as there doesn't seem to be a lot of solutions around to fix this problem!
From the above post you can see what the problem was, I was only able to get to either download mode or the android stock recovery, and the phone was not booting past the "note 10.1" logo
- I basically had to download the "rootgalaxynote10.1" zip file from rootgalaxynote.com.
- Then, using Odin I flashed the "highonandroidCWMrecoveryGTN8000.tar" file. This gave me custom recovery (you can't flash roms with stock android recovery)
- From here I downloaded a rom for my N8010, and put in on a micro sd card. Put this in the note 10.1, then used custom recovery to flash this rom
NB. I encountered a problem with Odin, and that was I couldn't open it on my lap top! I downloaded numerous files/versions, but no luck. Some forums said to run as administrator or switch off firewall/anti-virus, but nothing worked! I then tried it on a different lap top and VOILA! I don't know why, but it worked on different lap top!
I hope this helps someone out in the future
Click to expand...
Click to collapse
OMG. Thanx for your experience but I have no computer with windows now Are there any ideas how to flash a recovery with Linux?

OK. I've found an alternative to odin called Heimdall and succesfully flashed the Darkman's recovery. However it is not able for some reason to mount the /system and /sdcard partitions (which I'd like to back up first). Any ideas?

flashcactus said:
OK. I've found an alternative to odin called Heimdall and succesfully flashed the Darkman's recovery. However it is not able for some reason to mount the /system and /sdcard partitions (which I'd like to back up first). Any ideas?
Click to expand...
Click to collapse
Sorry mate, not to familiar with that. Might need one of the more experienced guys to help you out. Good luck:good:

Sorry for writing so late and in such a for dummies manner. I want this thread to be helpful for absolutely everyone who bricked his device like this.
COMPLETE SOLUTION:
First, you can try to flash your ROM (stock roms can be found here. There's another topic with more stock roms but I can't find it) with Heimdall, excluding the data partition to preserve... erm.. your data:
Install Heimdall with its graphical frontend.
Connect your device to your computer via USB cable and put it in download mode (ODIN mode) (Power+VolumeDown).
Open the Heimdall frontend, go to the Utilities tab.
Press Detect device. The device detected radiobutton to the left should be checked.
Under Print PIT check the Local File radiobutton and select where to save your device's partition data to (I named the file n8k.pit) in the browse dialog under it. Then press the Print button.
Now go to the Flash tab. Select the file you just created in the browse dialog under Options/PIT.
unpack the .zip containing your ROM. Then unpack the .tar.md5 that was inside it. You'll get several .img files.
Press the Add button. Select 'SYSTEM' from the Partition Name list. Select the system.img file you just unpacked under File (system.img).
For each entry in the following list, do the previous step, substituting 'SYSTEM' and system.img by:
BOOT and boot.img, respectively;
CACHE and cache.img, respectively
Take a deep breath and press Start.
And then you can go the hard, perverted&interesting way, and that's the way I went.
download this zipfile and unpack it. Find highonandroidCWMrecoveryGTN8000.tar among the unpacked files and unpack that. You'll get a recovery.img file.
download another version of CWM reccovery in an Odin-flashable format, unpack it to get the recovery.img
download PhilZ Touch Recovery for your device in ODIN-flashable format. Unpack and get the recovery.img.
Do steps 1-6 from the instruction above.
Press the Add button. Select 'RECOVERY' from the Partition Name list. Select your recovery.img file under File (recovery.img).
Press the Start button and wait for the operation to finish.
If you did not flash the PhilZ recovery right away, download it in CWM-flashable zip format, put on your SD card, load your new recovery and flash the zip.
Open the recovery, go to Backup and Restore => Custom Backup and Restore => Custom Backup job
Uncheck everything except backup data and optionally backup recovery, then press >> Start Custom Backup Job <<[/color].
Download a ROM of your liking, wipe data&cache, flash it, try it.
If you like it, try to restore data. Get the recovery going, go to Custom Restore job => uncheck all except data => >> Start Custom Restore Job <<[/color] => find your backup => data.ext4.tar) and reboot the device. If it doesn't bootloop, congratulations. If it does, GOTO 8.
Remember to hit the [:good:Thanks] button if this guide has saved yer arse.

flashcactus said:
Sorry for writing so late and in such a for dummies manner. I want this thread to be helpful for absolutely everyone who bricked his device like this.
COMPLETE SOLUTION:
First, you can try to flash your ROM (stock roms can be found here. There's another topic with more stock roms but I can't find it) with Heimdall, excluding the data partition to preserve... erm.. your data:
Install Heimdall with its graphical frontend.
Connect your device to your computer via USB cable and put it in download mode (ODIN mode) (Power+VolumeDown).
Open the Heimdall frontend, go to the Utilities tab.
Press Detect device. The device detected radiobutton to the left should be checked.
Under Print PIT check the Local File radiobutton and select where to save your device's partition data to (I named the file n8k.pit) in the browse dialog under it. Then press the Print button.
Now go to the Flash tab. Select the file you just created in the browse dialog under Options/PIT.
unpack the .zip containing your ROM. Then unpack the .tar.md5 that was inside it. You'll get several .img files.
Press the Add button. Select 'SYSTEM' from the Partition Name list. Select the system.img file you just unpacked under File (system.img).
For each entry in the following list, do the previous step, substituting 'SYSTEM' and system.img by:
BOOT and boot.img, respectively;
CACHE and cache.img, respectively
Take a deep breath and press Start.
And then you can go the hard, perverted&interesting way, and that's the way I went.
download this zipfile and unpack it. Find highonandroidCWMrecoveryGTN8000.tar among the unpacked files and unpack that. You'll get a recovery.img file.
download another version of CWM reccovery in an Odin-flashable format, unpack it to get the recovery.img
download PhilZ Touch Recovery for your device in ODIN-flashable format. Unpack and get the recovery.img.
Do steps 1-6 from the instruction above.
Press the Add button. Select 'RECOVERY' from the Partition Name list. Select your recovery.img file under File (recovery.img).
Press the Start button and wait for the operation to finish.
If you did not flash the PhilZ recovery right away, download it in CWM-flashable zip format, put on your SD card, load your new recovery and flash the zip.
Open the recovery, go to Backup and Restore => Custom Backup and Restore => Custom Backup job
Uncheck everything except backup data and optionally backup recovery, then press >> Start Custom Backup Job <<[/color].
Download a ROM of your liking, wipe data&cache, flash it, try it.
If you like it, try to restore data. Get the recovery going, go to Custom Restore job => uncheck all except data => >> Start Custom Restore Job <<[/color] => find your backup => data.ext4.tar) and reboot the device. If it doesn't bootloop, congratulations. If it does, GOTO 8.
Remember to hit the [:good:Thanks] button if this guide has saved yer arse.
Click to expand...
Click to collapse
So i've done all this, but its still stuck on the samsung logo, i have no recovery... only can get into odin mode.

Everything: Samsung Galaxy Note 1 [N7000] Stock ROM, Repartition, Root

:laugh::laugh:Samsung Stock ROM with no lags
Install on your own responsibility. Author of this post is not responsible for any bricked device. Author personally applied steps mentioned here on his N7000 (India) device.
Click to expand...
Click to collapse
Author tested on his Samsung Galaxy N7000 device.
Device tested for full 48 hours with no bugs.
Repartition of device is done on Samsung Galaxy Note 1 (N7000) 16GB model.
If you face any issues, those are pure stock ROM bugs.
Check Software update & register your device before you root your device with given steps in this post.
Rooting is optional, but I found that Stock ROM with it's original Kernel lags too much.
Kernel mentioned here is Optimised for Performance & Battery life.
It is a rare combination of Performance & Battery Optimisation.
I had installed many custom ROM, but the only issue that I was facing was incompatibility of those ROMs with my Samsung Camera & other phone functions. I noticed that many users wanted to move back to stock ROM but they had either faced installation issues or slower speeds for ROM package & inadequate sources to find exact ROM which is available for their device with their respective country. So, I decided to help those unlucky ones with this post, helping to get custom ROM installed on their devices & eliminate the STOCK ROM lagging issue with flashing of custom Kernel.
Click to expand...
Click to collapse
Prerequisite: ​
Latest Odin
Stock ROM respective of user's country.
PIT Files {I have only included 16GB model PIT files.}
SpeedMod Kernel zip.
Download & install Samsung Galaxy Note Drivers.
I have attached or/else provided links for all necessary files.
All STOCK ROM links are connected to Google Drive.
Okay, So we should start now!
THIS IS STRICTLY FOR SAMSUNG GALAXY NOTE 1 [N7000] worldwide.
First thing first. Download & Install Samsung Galaxy Note 1 drivers here.
Download Latest Odin here.
Download STOCK ROM respective to your country here. [All are Google Drive links, hope they will make your Stock download faster.]
Download PIT ZIP file from attachments given below.
Download Kernel ZIP from attachments given below.
Now start the flashing STOCK ROM procedure:
Install drivers that you just downloaded from above link & restart you rmachine upon successful installation of drivers.
Upon restart after successful installation of drivers run Odin as an Administrator.
Restart your phone in download mode [To start device in Download Mode, Switch off your phone, then Press following key combination simultaneously for 10 seconds. Press, "Volume Down + Home Button + Power button"] until then do not attach your phone to PC.
Load PIT file first & ignore any developer warning that Odin throws on you.
In the section of AP, load your downloaded Stock ROM which should be respective to your country.
Let Odin takes it's time & upon Leave CS warning in 'Log' section of Odin, attach your phone to computer.
Press 'Volume Up' button you should now see Downloading box on your Mobile screen.
Click on 'Start' in Odin to start flashing of ROM.
After Successful completion of Flashing you will see Green Box on top of the Odin software showing 'PASS' result.
Now let your device start normally, you should complete all setup procedure i.e. Inserting your Samsung Acct. credentials, Google Credentials etc.
Once you see your device is been running properly, you have successfully flashed Stock ROM on your device without any issues.
To root your device & install custom kernel to make your device run without any lags follow the instructions given below:
Power off your device.
Open 'Download Mode'
Run Odin as an Administrator.
Load Kernel.zip in AP section of Odin [provided in the attachments].
No need to load PIT file again!
Now attach your phone & press Volume up button to enter in download mode.
Odin should detect your Phone.
Then press Start & wait until Kernel flashes properly.
Upon successful installation device will go blank, you need to be quick & should open your device in recovery mode [To start device in recovery, Press 'Volume Up + Home Button + Power button' for 10 sec.] within that very time.
Do factory reset & wipe all cache partition in Recovery menu.
Now reboot your phone.
Your device has successfully rooted & should Run smooth with new kernel.
Kernel Features:
Fast, Optimised for Galaxy Note
Battery Optimisation has enhanced getting less juice out of battery against device's performance.
Better RAM management.
Better Thread handling.
Hope you will perform & follow instructions properly & enhance your Galaxy Note performance. Any queries, Suggestions, feedback are appreciated.

regarding repartition
hi will the pit files repartition my n7000, if so what would the partition size look like.
more app storage?
souravbhor said:
:laugh::laugh:Samsung Stock ROM with no lags ​
Author tested on his Samsung Galaxy N7000 device.
Device tested for full 48 hours with no bugs.
Repartition of device is done on Samsung Galaxy Note 1 (N7000) 16GB model.
If you face any issues, those are pure stock ROM bugs.
Check Software update & register your device before you root your device with given steps in this post.
Rooting is optional, but I found that Stock ROM with it's original Kernel lags too much.
Kernel mentioned here is Optimised for Performance & Battery life.
It is a rare combination of Performance & Battery Optimisation.
​
Prerequisite: ​
Latest Odin
Stock ROM respective of user's country.
PIT Files {I have only included 16GB model PIT files.}
SpeedMod Kernel zip.
Download & install Samsung Galaxy Note Drivers.
I have attached or/else provided links for all necessary files.
All STOCK ROM links are connected to Google Drive.
Okay, So we should start now!
THIS IS STRICTLY FOR SAMSUNG GALAXY NOTE 1 [N7000] worldwide.
First thing first. Download & Install Samsung Galaxy Note 1 drivers here.
Download Latest Odin here.
Download STOCK ROM respective to your country here. [All are Google Drive links, hope they will make your Stock download faster.]
Download PIT ZIP file from attachments given below.
Download Kernel ZIP from attachments given below.
Now start the flashing STOCK ROM procedure:
Install drivers that you just downloaded from above link & restart you rmachine upon successful installation of drivers.
Upon restart after successful installation of drivers run Odin as an Administrator.
Restart your phone in download mode [To start device in Download Mode, Switch off your phone, then Press following key combination simultaneously for 10 seconds. Press, "Volume Down + Home Button + Power button"] until then do not attach your phone to PC.
Load PIT file first & ignore any developer warning that Odin throws on you.
In the section of AP, load your downloaded Stock ROM which should be respective to your country.
Let Odin takes it's time & upon Leave CS warning in 'Log' section of Odin, attach your phone to computer.
Press 'Volume Up' button you should now see Downloading box on your Mobile screen.
Click on 'Start' in Odin to start flashing of ROM.
After Successful completion of Flashing you will see Green Box on top of the Odin software showing 'PASS' result.
Now let your device start normally, you should complete all setup procedure i.e. Inserting your Samsung Acct. credentials, Google Credentials etc.
Once you see your device is been running properly, you have successfully flashed Stock ROM on your device without any issues.
To root your device & install custom kernel to make your device run without any lags follow the instructions given below:
Power off your device.
Open 'Download Mode'
Run Odin as an Administrator.
Load Kernel.zip in AP section of Odin [provided in the attachments].
No need to load PIT file again!
Now attach your phone & press Volume up button to enter in download mode.
Odin should detect your Phone.
Then press Start & wait until Kernel flashes properly.
Upon successful installation device will go blank, you need to be quick & should open your device in recovery mode [To start device in recovery, Press 'Volume Up + Home Button + Power button' for 10 sec.] within that very time.
Do factory reset & wipe all cache partition in Recovery menu.
Now reboot your phone.
Your device has successfully rooted & should Run smooth with new kernel.
Kernel Features:
Fast, Optimised for Galaxy Note
Battery Optimisation has enhanced getting less juice out of battery against device's performance.
Better RAM management.
Better Thread handling.
Hope you will perform & follow instructions properly & enhance your Galaxy Note performance. Any queries, Suggestions, feedback are appreciated.
Click to expand...
Click to collapse

repartition of gtn7000
hi i would like to try this method, my gtn7000 16Gb variant is currently running CM10.1.3, CWM 6.0 as recovery.
The pit file attached in your post, does it increase the system partition, I am in need of a higher partition for my note as i get insufficient storage to install apps.
Also in your method is it necessary to flash the updated kernel, as I intend to expand the partition and later install CM10.1.3 or higher versions.
Will the CWM recovery be still there or do i need to flash it again.?
should i tick re-partition option , F-reset time, auto reboot in odin ?
regards
Nithin S.

Yes Exactly!
nithin1664 said:
hi will the pit files repartition my n7000, if so what would the partition size look like.
more app storage?
Click to expand...
Click to collapse
Hi Nitin,
PIT stands for Partition Information Table, it simply tells your device in what amount the internal storage is divided into Internal/ Phone memory & SDCARD0.
Difference between both the memories are, first used for app installation & later for data associated with those applications installed. So with officially N7000 comes with 2 GB Internal/ Phone memory & 12 GB of SDCARD0.
SO if you choose 8 GB PIT file for official stock ROM then you are ultimately getting 8 GB for app storage & rest 5 GB for related data storage.
You can choose between 4,6 & 8 GB of PIT file as per your needs & for ROMs other than STOCK you can extend this memory variant to (4,6,8,10 &) 12 GB Internal & 1.3 GB SDCARD0.
Hope you find this helpful & sorry for posting so late.

nithin1664 said:
hi will the pit files repartition my n7000, if so what would the partition size look like.
more app storage?
Click to expand...
Click to collapse
nithin1664 said:
hi i would like to try this method, my gtn7000 16Gb variant is currently running CM10.1.3, CWM 6.0 as recovery.
The pit file attached in your post, does it increase the system partition, I am in need of a higher partition for my note as i get insufficient storage to install apps.
Also in your method is it necessary to flash the updated kernel, as I intend to expand the partition and later install CM10.1.3 or higher versions.
Will the CWM recovery be still there or do i need to flash it again.?
should i tick re-partition option , F-reset time, auto reboot in odin ?
regards
Nithin S.
Click to expand...
Click to collapse
Hello Nitin,
Yes my method exactly intended for the very specific reason you mentioned here. "It will EXTEND your partition size " & let you install more apps!
There is no need to install custom kernel or flash any other ROM. I have tested it on all CM version ( CM 10+). Also there is no need to select F-reset time, auto reboot in odin. Go to odin Select PIT, it will pop-up some message just say Ok & proceed. Select desired PIT file from downloaded & extracted ZIP. Odin is smart enough to understand your operation & select all necessary settings automatically.
Simply, restart your phone in Download Mode, connect it to your PC & only flash the PIT file.
Hope this will help you! Any need please leave your question here.

Do I lose all data from internal sd or external sd card?

BACKUP Always!
ImN00Bpa said:
Do I lose all data from internal sd or external sd card?
Click to expand...
Click to collapse
Hello,
I first of like to advise you to backup all the data regardless How secure the procedure is. Because no one knows when some bug will come up! You better backup all your Internal data & proceed.

Hi there..sorry for late question..i have n7000 already update to 4.1.2 DXLSE XME..so do i need to flash PIT.file only or do i need to re flash stock 4.1.2 with pit.file??
And i try to root it with Philz but didnt work even supersu granted..device still official..can i just root it with this speedmod kernel?

If you need to!
halagore said:
Hi there..sorry for late question..i have n7000 already update to 4.1.2 DXLSE XME..so do i need to flash PIT.file only or do i need to re flash stock 4.1.2 with pit.file??
And i try to root it with Philz but didnt work even supersu granted..device still official..can i just root it with this speedmod kernel?
Click to expand...
Click to collapse
Flashing PIT File will change your partition table & enables device to allocate future data in similar way. I suggest re-flashing ROM would be better. Because with new partition information your device's software & other system apps will reside on proper partition. Hope you will find this information productive.
Ask freely if you have any further doubts.

A20 Repair Firmware

Repair Firmware
This site contains
1. Full repair firmware
2. Combination firmware
3. Fix dm verity
4. Root instructions and unpatched boot images
A20
https://www.full-repair-firmware.com/search?q=A20
A20e
https://www.full-repair-firmware.com/search?q=A20e
A20s
https://www.full-repair-firmware.com/search?q=A20s
All models
https://www.needromarab.com/1/122/SAMSUNG
physwizz collection
A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...
forum.xda-developers.com

Information and Guides from the above website
1. Full repair firmware
Problems Solved This Firmware
Update android version.
Fix Camera.
Fix Invalid IMEI And Baseband.
Fix Wifi and Bluetooth.
Fix custom binary blocked by frp lock.
Fix standing on the logo.
Fix storage space.
Fix slow device.
Fix sensors.
Solve the problem of high temperature.
Fix applications stop working.
Fix restarting the device.
delete pattern or password.
Fix hide Imei.
Fix baseband unknown.
Remove root.
wipe data.
wipe cache.
hard reset.
Fix sound problems.
Firmware Galaxy A20:
Important Notice: Please Inform us in case of any dead link, Or any flashing error you get when using these files, So we can check and replace, Send an Facebook with details to: Contact us
Warning: This firmware A20*** use to repair software smartphone problem and it will clean everything on your smartphone so you have to backup your data, don’t try to flash your device with this firmware if it work prefect. if you use pit file please make sure 16GB or 8GB or 32GB, Because the 8GB Pit file don’t work with 16GB or 32GB and the same for 16GB or 32GB Pit File make sure you use the Correct ROM for your device.
To flash your Samsung galaxy smartphone, you need Odin software made available to the Samsung Galaxy users for flashing a range of things including firmware, custom recovery, CF-Auto-Root and more. Odin software performs a clean install that means; it removes the old firmware and flashes a new one,Backup your data before start flashing you smartphone.
Here you find all the latest android os for the Galaxy A20 SM-A205GN, if you want to flash your device with the newest Samsung software. Before downloading, make sure you check your exact model number. You can download the most recent Galaxy A20 firmwares for free, or check out our cheap but fast download options.
Important tools to work flash android update:
Drivers: USB Samsung Galaxy
Odin
How To Flash Galaxy A20
Extract the Firmware A20*** By 7z or winrar You should get 5 files (BL-AP-CP-CSC-Home CSC).
Download Odin.
Add each file to it's respective field in Odin v3.13.3. Use CSC_** if you want to do a clean flash (lost data) or HOME_CSC_** if you want to keep your apps and data (unformat).
Reboot Phone in Download Mode (press Volume Down + Volume Up and connect the Type-C USB cable to device).
wait until you get a blue sign in Odin.
Add the files to BL - AP - CP - CSC
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC.
Now you have the latest android version
2. Combination firmware
Samsung Galaxy A20 Combination Firmware is a stable program for complex and sophisticated tasks. You can flash the device using this developer program to conduct a test that shows you the results of the phone check. It is really important that this particular firmware Samsung A20*** can:
Bypass or remove Google Account Protection
Bypass or remove Samsung Account Protection
Remove RMM Protection
Repair IMEI
Write Cert
Fix Boot loop
Enable USB Debugging
Unlock Network
Important tools:
Drives USB Galaxy
Odin Tool
How To Flash Combination File:
1-Extract the Combination By 7z or WinRAR You should get 1 file .
2-Boot your phone to Download Mode ( Volume Down + Volume Up and connect the Type-C USB cable to device ).
3-Open Odin Tool and wait to get a blue sign in Odin.
4-Add the file Combination to AP.
5-Do NOT tick any extra boxes.
6-Click the start button, wait for Odin to say 'PASS'.
3. Fix dm verity
What is the DRK or DM-Verity for device a20***
DRK Is an acronym DEVICE ROOT KEY It is an encrypted number for the device and It is positioned when manufacturing by Samsung.
When we turn on the device, the device checks this encrypted number to check if the system is original or not.
Fix DM-Verity (DRK) Galaxy A20
Reasons for the appearance of DRK problem
This problem occurs when we flash the ROM that does not match the device in terms of the version Bashband, Or when flashing a custom ROM by a custom recovery (TWRP) Or by the stock rom For example, Stock ROM but a language has been added to it In this case, the encrypted number will check the status of the system When the system does not match the number, this error will occur, A red write will appear in the recovery mode (dm-verity Verification failed).
Problems resulting from DRK / DM-Verity
-Stop at the Samsung logo.
-Automatic boot to the recovery mode.
-Restart the device.
Warning before starting
-Charge the device battery to a level above 50%.
-Download the files according to the type of device and must not differ any characters.
-Agree that all steps are at your own risk.
Important tools to fix drk
Drives USB Galaxy
Patched Odin Tool 3.13.1
How To Flash Fix DRK A20***:
1-Download Firmware and Extract by 7z or WinRAR.
2-When extracting files, rename the file AP_A205U1 Then delete the extension .md5
3-Open AP File then Extract the system file.
4-Now create an archive of the system file that we extracted previously by a program 7z.
5-Choose the file format .tar Then, create the file.
6-Download Fix Drk file.
7-Now we have two files (DRK File,SYSTEM.tar File).
8-Boot your phone to Download Mode(press Volume Down + Volume Up and connect the Type-C USB cable to device).
9-Open Odin Tool and wait to get a blue sign in Odin.
10-Add the DRK File to BL.
11-Do NOT tick any extra boxes.
12-Click the start button, wait for Odin to say 'PASS'.
13-Boot your phone to Download Mode again.
14-From odin tool Add the SYSTEM File to AP.
15-Click the start button, wait for Odin to say 'PASS'.
16-Then the device will work without problems.
17-In case of any problems please Contact us.
4. Root instructions and unpatched boot images
Root features:
1-Modify or delete files or applications of the operating system.
2-Run programs that require root permissions.
3-Change the basic fonts within the Android system.
4-Move applications from device memory to external memory.
5-Installation of Custom rom.
6-Fix errors DRK and DM-Verity.
Cons of the root:
1-Loss of phone warranty.
2-Some applications do not work due to root (bluestacks root / dr fone root).
3-Stand on the company logo as a result of misuse.
4-The operating system crashed due to deletion or modification of important system files.
important warning:
Installation and use of the root android is entirely at your own risk and we do not take any responsibility for device failure.
In older versions of the Android system such as Jelly Bean and KitKat was using apps (kingroot / kingo root / framaroot / iroot / root king / towelroot) To get root permissions either in new versions such as Lollipop, Marshmallow, Nougat, Pie and future versions of the Android system, these applications do not work.
What is the difference between SuperSU and Magisk
VS
The main difference between Magisk and SuperSU is how the root works on Android. Based on what the user wants to do.
We will first talk about supersu root how to get the root where it installs itself within the system files It changes the system files and adds new files to the system partition on the phone, but with the enhancement of Google to protect Android it has become difficult to do so that the amendment to the partition of the Android system to send an alert to applications that are trying to detect the presence of root.
Google SafetyNet monitors the operating system from any manipulation, and when it detects any manipulation in the Android operating system, most applications will not work and will not send you OTA updates.
What about Magisk is one of the most important features that does not touch system files, but modifies the boot partition instead so that it can trick safetyNet service and show that everything is normal and allows Magisk Manager to fully control the root settings.
Notes before root process
Charge the battery well before use.
Use the original USB cable that came with the device.
Use the laptop at work to avoid electricity problems.
You should focus well to protect the binary of your device.
The following protections must be disabled (FRP - OEM - RMM/KG) Follow the following article to learn How to Disbled FRP and OEM for device Samsung Galaxy.
Files required for root work
-Samsung Driver USB
-Odin Tool
-Magisk Manager
-Root A20xxx file
How To Root Galaxy A20xxx android Pie 9.0
1-Download Drivers, Odin and A20xxx Root files for Pie 9.0 Depending on your device version.
2-Install the drivers on your device.
3-Install the Magisk Manager app on your Phone.
4-Transfer the boot file to the device's memory after extracting the file.
5-The entire file name will become boot.img.
5-Open the Magisk Manager app.
6-Open the application settings and from the option Patched Boot Output Formate We choose .img.tar.
7-We return to the main interface of the application And we click on install a new window will appear we choose install too.
8-A new window will appear titled Select Patched We choose the second option Patch Boot Image File.
9-Locate the boot file and give the application access rights.
10-Patch Boot will take some time about 5 minutes.
11-After the process is finished navigate to the MagiskManager folder or Download folder you will see the file named patched_boot.img.tar (mroot A20xxx).
12-Copy the file to your computer and open the Odin tool.
13-Of the box AP We choose the file (patched_boot.img.tar).
14-Boot your device into download mode press Volume Down + Volume Up and connect the USB cable.
15-Press Start to flash the boot file.
16-After the flash is done, you will be asked to work factory reset.
17-It will take about 10 minutes to boot the Android system.
18-After the boot is complete we install the Magisk Manager application.
19-After installing the app you need to reboot your device with Magisk to get root permissions, Open the Magisk app and from the options at the top of the app we choose Modules and then we press the three points above and we choose Reboot.
20-You can check for root access through the root checker app.
21-In case you encounter any problems please feel free to contact us
22-If you want to unroot or revert to the offical firmware, you can read the following article: Full Firmware For Device Samsung Galaxy

If you find this useful please comment.

Can you please provide me the unpatched boot file for A205fxxs6ata2 so i can unlock my phone and install twrp

Maybeyou said:
Can you please provide me the unpatched boot file for A205fxxs6ata2 so i can unlock my phone and install twrp
Click to expand...
Click to collapse
Use the patched one from here
https://forum.xda-developers.com/galaxy-a20/how-to/root-a205xx-october-patchu3-t4005335

Thank you very much I will try it and post results

didn't work, odin says fail

Maybeyou said:
didn't work, odin says fail
Click to expand...
Click to collapse
Have you unlocked bootloader on developer options
Instructions here
https://forum.xda-developers.com/galaxy-a20/how-to/root-samsung-galaxy-a20-rooting-guide-t3954872

Phone: A20s - a207f
Phone: A20s - a207f
I used A207FXXS2ASL3 from full-repair-firmware.com/search?q=A20s
Issue
Secure check fail: boot.img
Skybluescreen: Security Error: This phone has been flash with unauthorized software & is locked. Call your mobile operator blah blah blah.
I could still use my phone if I flash the original AP(BL_A207FXXS2ASL3_CL17088050_QB28240904_REV00_user_low_ship_MULTI_CERT.tar.md5)(3gb+) using ODIN
Flashing the boot.tar(11.8mb) that comes from (AP->boot.img.lz4>boot.img>from magisk_patched>compressed it to tar) gives me the issue.
Anyone knows how can I bypass the "Skybluescreen: Security Error" ?

silksong23 said:
Phone: A20s - a207f
I used A207FXXS2ASL3 from full-repair-firmware.com/search?q=A20s
Issue
Secure check fail: boot.img
Skybluescreen: Security Error: This phone has been flash with unauthorized software & is locked. Call your mobile operator blah blah blah.
I could still use my phone if I flash the original AP(BL_A207FXXS2ASL3_CL17088050_QB28240904_REV00_user_low_ship_MULTI_CERT.tar.md5)(3gb+) using ODIN
Flashing the boot.tar(11.8mb) that comes from (AP->boot.img.lz4>boot.img>from magisk_patched>compressed it to tar) gives me the issue.
Anyone knows how can I bypass the "Skybluescreen: Security Error" ?
Click to expand...
Click to collapse
As far as I know, no one has been able to root the a207

Has anyone had any luck flashing the combination firmware to SM-A205YN? Using Odin 3.14.1 patched I get error on phone screen "Please get the approval to use factory binaries (PIT)"
Odin log is:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2294 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Cheers
btw my baseband version is A205YNDVU2ASF2 if that makes a difference

magnafunk said:
Has anyone had any luck flashing the combination firmware to SM-A205YN? Using Odin 3.14.1 patched I get error on phone screen "Please get the approval to use factory binaries (PIT)"
Odin log is:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2294 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Cheers
btw my baseband version is A205YNDVU2ASF2 if that makes a difference
Click to expand...
Click to collapse
Have you unlocked bootloader and ticked usb debugging

Yep sure have

magnafunk said:
Yep sure have
Click to expand...
Click to collapse
I also have 205yn
I used full firmware no probs
What are you trying to do?

I can install full firmware but not combination. I want to network unlock. Telstra are basically not answering phones at the moment and the online services don't work if Knox is tripped

magnafunk said:
I can install full firmware but not combination. I want to network unlock. Telstra are basically not answering phones at the moment and the online services don't work if Knox is tripped
Click to expand...
Click to collapse
All Telstra operations are locked down in India.,

Combination files
physwizz said:
Repair Firmware
This site contains
1. Full repair firmware
2. Combination firmware
3. Fix dm verity
4. Root instructions and unpatched boot images
A20
https://www.full-repair-firmware.com/search?q=A20
A20e
https://www.full-repair-firmware.com/search?q=A20e
A20s
https://www.full-repair-firmware.com/search?q=A20s
All models
https://www.needromarab.com/1/122/SAMSUNG
Click to expand...
Click to collapse
Has anyone tried the combination files from an has had any luck getting OEM unlock to work ?

Combination files
peter couniaz said:
Has anyone tried the combination files from an has had any luck getting OEM unlock to work ?
Click to expand...
Click to collapse
Well I guess no one has an answer for this question . Or with the locked Bootloader it just wouldn't flash I'll give it a shot . An see .

peter couniaz said:
Well I guess no one has an answer for this question . Or with the locked Bootloader it just wouldn't flash I'll give it a shot . An see .
Click to expand...
Click to collapse
If boot is locked, you can't flash any firmware except what is made for your model.

peter couniaz said:
Well I guess no one has an answer for this question . Or with the locked Bootloader it just wouldn't flash I'll give it a shot . An see .
Click to expand...
Click to collapse
long press volume up to unlock bootloader from blue screen