pre Requisites:
- All the data present in your Galaxy FIT needs to be backed up ONLY by following the below mentioned steps so as to ensure that just in case if the data gets lost or corrupted.
- Charge left in the device should be minimum 60% so as to make sure that the phone doesn’t get turned Off in the middle of firmware update. Enable the USB Debugging in your device from the path “Settings > Applications > Development > USB debugging”
So,assuming that you have followed all the instructions mentioned above you now need to proceed further for procedure.
Procedure to Update
- Download Gingerbread 2.3.6 Package & odin-beni-ss.dll for Fit.zip in your computer after which you need to extract the same.If Promted For Password then You Should Enter Password as “sampro.pl”.
For 2.3.6 Update Package- http://hotfile.com/dl/140199372/0b98375/GT-S5670_INU_S5670DDKT1_S5670ODDKT1_S5670DDKT1.rar.html
- Match the extracted files from the below shown screen capture, even if single file is missing then you need to check with the extraction or download process.
- From extracted files, open Odin executable file and turn Off the phone so as to enter the device in the download mode.
- Now, you need to enter the by holding the Volume Down button + the Home key button (the middle button). While holding these both buttons, you need to switch ON your device. Just in case if the device boots in the normal mode then you will have to again try the process of entering into the download mode
- After entering the phone in the download mode, connect the device to the computer while keeping the Odin opened. Within a minute, the ID : COM section will turn yellow which will mean that all the drivers have been successfully installed and you are now ready to proceed to the next step.
- Click on the “OPS” option in the Odin to select the below mentioned file, tick on “One Package” option and then select the One Package option as mentioned below.
OPS – BENI_v1.0.ops
One Package – S5670DDKT1_S5670ODDKT1_S5670DDKT1_HOME.tar.md5
- Click on Start and then wait for the device to get restarted. Once the device gets restarted, you will be asked to enter the Google Account credentials. Once you see the home screen in your phone, disconnect the connected phone.
Congratulations!!! You have successfully update ur android with 2.3.6 Gingerbread Firmware
_______________________________________________________________
Press THANKS button If I help U in any manner
Hi!
Does this firmware includes greek language?Thanks!
may be no...
Because DD is for india:thumbup:
Sent from my GT-S5670 using xda app-developers app
Do you know where i can find or what is the name for the firmware to search?Also i have a greek galaxy fit with 2.3.6,do you know how to make a full backupo of this firmware?Thanks!
i guess everyone knows this
zafisinl said:
Do you know where i can find or what is the name for the firmware to search?Also i have a greek galaxy fit with 2.3.6,do you know how to make a full backupo of this firmware?Thanks!
Click to expand...
Click to collapse
http://www.sammobile.com/firmware/
In search write s5670.
password
what is the password for this file????
It's witten over there on sammobile
Sent Via XDA™ Premium
Password
rajmi said:
what is the password for this file????
Click to expand...
Click to collapse
Read the first post carefully
Pasword : sampro.pl
The rar file just has the md5 file, where can I find the other files? I tried manually downloading the files from different locations but it just sits at downloading mibib and doesn't do anything. The flashing process just sits at downloading MIBIB and doesn't go anywhere, I have tried waiting for as long as 30mins, now the mobile doesn't even start with the previous firmware. When started it shows an icon like connection problem between a computer and mobile right after the initial samsung logo and sits there.Please help
zafisinl said:
Hi!
Does this firmware includes greek language?Thanks!
Click to expand...
Click to collapse
Most probably it does.I flashed mine with a stock russian rom.the phone started in russian but you can easily navigate through the icons to settings and change the language.I turned it to greek
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.
What is This Guide:
This guide will give you the complete and easy steps to follow when you want to update the firmware version of your Samsung Galaxy Star Duos S5282, The main goal of this guide is to update your Galaxy Star Duos by yourself and by using Free tools and files only, No need to buy or pay for anything at all, We bring you everything you need to perform the update so all you should do is reading the guide and start working.
Important Steps:
- Backup any wanted data before starting the update process, Read our online guide (How to Backup your Samsung Mobile Phone).
- Charge your mobile phone to be at least at 70% of its charging level.
- Write down the current firmware version of your mobile phone, You may need it in case of anything happen during the update process.
Tools, Files and programs:
- Stock official firmware of Samsung S5282 Galaxy Star Duos (Download and extract the package).
- USB drivers for your S5282 ( Download and install it, Then restart the computer).
- Odin flasher (Download and extract).
- Suitable USB cable for Samsung S5282 Galaxy Star Duos.
- A computer with Windows OS installed.
Samsung S5282 Galaxy Star Duos Firmware Update Steps:
- Turn off the phone.
- Take out any SIM cards or memory card of it.
- Run Odin.exe program.
- Check the following settings: Auto Reboot, F.Reset Time, Nand Erase all.
- Click Bootloader button and select: BOOTSPL_S5282xxxxxx_..._REV03_user_low_ship.tar
- Click PDA button and select: CODE_S5282xxxxxx_1127854_REV03_user_low_ship.tar
- Click PHONE button and select: MODEM_S5282xxxxx_REV03.tar
- Click CSC button and select: CSC_Oxx_S5282Oxxxxxx_1127854_REV03_user_low_ship.tar
(In-case you'd like to re-partition, check "re-partition" and select the mint.pit file)
- Put your Samsung S5282 Galaxy Star Duos device into Download Mode:
Press and Hold Volume Down key + Home key + Power key, When you see the warning message release all keys, And press Volume Up key to enter the phone into Download Mode.
- Connect the device to your PC using the USB cable.
- Wait for Windows to install the needed USB drivers.
- Look at Odin's window and check if the COM port of your device is detected (0:[COMxxx]).
- Click on Start button.
- Odin will install the new firmware files into your Galaxy Star Duos, Just wait for it to be done.
- The device will be rebooted after installing the new firmware.
- Look at Odin's window and if you see PASS! Word then the update was successful.
- Disconnect the USB cable from phone.
- Wait for the device to be fully on and check the new firmware version bu this code *#1234#
- Now you can turn the mobile off, Insert SIM Cards, Memory card, Then turn it on again.
- When the device is on again you are free to customize it and restore your backup (In case you have made one), Then enjoy your perfect work.
IMPORTANTNotice: When you have a firmware package with one file inside, Then no need to check Re-Partition option, And never use PIT file too, All you should do is selecting the one file as PDA file, and perform the other explained steps.
Boot loop occurs
Can you give me the link ???,I goolged always getting.. a sigle flashable file. When i flash with that, always boot loop occurs..
Any advise pls...
subinkoovery said:
Can you give me the link ???,I goolged always getting.. a sigle flashable file. When i flash with that, always boot loop occurs..
Any advise pls...
Click to expand...
Click to collapse
Use single one in pda download from samsung-updates.com
Sent from my Micromax A58 using XDA Free mobile app
Please Help Me
After installing stock rom in galaxy star (GT-S5282) , I got something on my screen showing some details like pda, etc (picture attached with this post). and it is staying forever. Also when i long press power button, it is directly sutting down without showing any menu. screen is not locking.And also showing internal memory as 0. When I try to install any custom rom, device is going into boot loop. PLEASE HELP ME!!!
Yes same here please help my friends wanna need my help
Hello!
Please please help me!!!!
My Problem:
After factory reset (even before) without any installation I have only 541MB from 639MB of Phone memory free, when I connect it to the PC.
SD Card memory is OK.
So I had always problems with installing for example Navigon or other programs, because the phone says alwas: Less memory, please add new memory.
So I want to root it, OR MAYBE THERE IS AN OTHER WAY TO EXENT THE MEMORY.
Because inside the phone, when I check the memory via android 5.1.1 there are more GB free.
But I cannot root it, because odin and kies cannot find the J700F Model.
So I trtied different drivers.
Please Please help, or give me some comment what I could try!!!
Best regards
Hook
There android 6.0.1 available for the j700f. If you google search... updato archives, on youre computer or laptop then type in j700f in the firmware search bar and the firmware will show up. Id try a fresh install of the firmware and see that helps. Id post a link but i havent reached 10 posts yet.. id try to update the firmware to 6.0.1 marshmallow and see if that fixes it.
Here you go ....
http://updato.com/firmware-archive-select-model?q=j700f
Thanks!!!
Ifibreakitwillyoufixit said:
There android 6.0.1 available for the j700f. If you google search... updato archives, on youre computer or laptop then type in j700f in the firmware search bar and the firmware will show up. Id try a fresh install of the firmware and see that helps. Id post a link but i havent reached 10 posts yet.. id try to update the firmware to 6.0.1 marshmallow and see if that fixes it.
Click to expand...
Click to collapse
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Many many Thnaks for helping!!!!!!!!
Yes, I read about it, but my Problem is that I also cannot use Odin.
See Post:
I have an really big problem with my phone: "SM-J700F"
I am not able to connect via odin or kies to this one.
But in windowes explorer (Win7 64bit) everything is visible.
In MTP Mode, Usb-Storage and PTP mode.
Also I can acess to the phone via the explorer.
But not with odin and/or Kies.
I tried to installit several times (Kies also Kies3)
Then I tried another win7 computer, but with same result.
The reason is, i wont to root the phone, because of low memory, even after reseting to factory.
I hope really a lot that there is an solution!!!!
--------
And additional Information:
When I connect my Samsung Galaxy S5 Neo, everything is working.
So I compared the used driver for both phone (S5 is OK), (J7 is not) in the device manager of windows.
So below you see the entries when the phone is connected:
S5 Neo - OK:
-Modem: Samsung Mobile USB Modem
-Samsung Android Phone: Samsung Android ADB Interface
-Tragbare Geräte: Galaxy S5 Neo (translated means: carryable device)
-USB Controller: Samsung Mobile USB Composite Device
Same with J700F - Not OK:
- Modem: entity is not existing ---> difference
-Samsung Android Phone: Samsung Android ADB Interface ---> is equal
-Tragbare Geräte: full_tangxun6572_we_I ---> different, is the Name whitch is visible in windows explorer
-USB Controller: USB Verbindungsgerät (translatet: USB Connection Device) ---> different (this Entity is already existing, even when no phone is connected)
So I tried to update exactly this driver with the downloaded one from Samsung. For this I had to use no compactible hardware.
When I select almost all INF driver, the right driver was visible during installation, but it could not start (code 10)
I think this is somehow the problem.
With the driver "USB Verbindungsgerät" on the windows side everything is OK. Copy to phone, explore,...
But I think that Kies and Odin don't find the acces point to the USB samsung device....the bridge to this device.
Maybe there is an possibility go give odin an additional command, where odin connect to the right port (_#0006) and HUB (_#0004) which I see in the USB Verbindungsgerät....
1. Usb debugging on
2. Oem Unlock enabled if its in dev settings,
3. Connect usb to phone and computer
4. Boot into download mode
5. Open odin
6. Select pda
7. Select the firmware file
8. Click start
9. Wait a little bit for the firmware to load
8. Firmware flashes
9. Profit
If the firmware fails to load in odin after 1 minute then you must decompress the zip file and extract the firmwares tar and then flash the tar instead of zip.
Not sure what happened to youre phone but it sounds more like at one time it was rooted and some system modifications have caused it to mess up things.. if you havent done any system modifications then its a strange bug..
In odin it will have a blue box up in the com area up at the top left of odin if its blue then you are connected. If its blue and file fails to load it must be decompressed and extracted so its just the tar file..
Look and see does even a blue box show in odin when youre connected?
Not working --- what is wrong?
Ifibreakitwillyoufixit said:
1. Usb debugging on
2. Oem Unlock enabled if its in dev settings,
3. Connect usb to phone and computer
4. Boot into download mode
5. Open odin
6. Select pda
7. Select the firmware file
8. Click start
9. Wait a little bit for the firmware to load
8. Firmware flashes
9. Profit
If the firmware fails to load in odin after 1 minute then you must decompress the zip file and extract the firmwares tar and then flash the tar instead of zip.
Not sure what happened to youre phone but it sounds more like at one time it was rooted and some system modifications have caused it to mess up things.. if you havent done any system modifications then its a strange bug..
In odin it will have a blue box up in the com area up at the top left of odin if its blue then you are connected. If its blue and file fails to load it must be decompressed and extracted so its just the tar file..
Look and see does even a blue box show in odin when youre connected?
Click to expand...
Click to collapse
Hi!
I tested it again (same prozedure on 2 computers)
1. Usb debugging on -> done!
2. Oem Unlock enabled if its in dev settings, -> done!
3. Connect usb to phone and computer -> done!
4. Boot into download mode -> done!
5. Open odin -> done!
The Problem is, that ODIN cannot find the phone.
There is nothing below "ID:COM" no entity!
So I cannot go forward.
I treid on 2 PCs. Same result.
But interesting ist that from windows I can acces to the phone.
But not via odin and Kies.
Maybe you can give me information whitch driver should be used in the device manager?
Interesting is that Samsung Galaxy S5 Neo is working with this procedure....
I am really sad, and I hope so much that you can help!!!
BR
Hook
ODIN Screenshot - not working
Hello!
Appended there is an screenshot of ODIN.
One of my S5 Neo - called S5 Neo.jpg -> Odin is working
Please Note:
The ID: 0/003 is the phone Samsung Galaxy S5 Neo.
One of my J700F - called J700F.jpg -> Odin is not working (connecting)
On the other computer I tried Odin3 v3.12 also.
I think maybe there is an driver Problem?
Whitch one I need for J700F.
I downloaded more times the Samsung Galaxy USB driver kit...
BR
Robert
Sorry, but in this tread I would like you to ask about the memory points.
Why I have so less memory in the J700F?
Is it normal?
Br
Robert
Can anybody support me
Hello
Is any possibility for helping?
BR
Robert
Some news?!
What I found out:
When I use *#0808#
There is SP selected and RNDIS+ACM+DM+ADB
Bit when I select MTP+ADB the other one is not deselected and I cannot continue?
Means with OK - no function and Reboot - no function (then both are selected....!)
Do you can support me here?
BR
Hook