Hello, dear visitors.
In this FAQ I will try to write about how to port the stock firmware within a family of Galaxy Tab 2 7.0. Tab 2 10.1 family might just as portable. About porting between 7.0 - 10.1 and forth until there is no manual)
WARNING:In any ported disconnect FOTA firmware-update and do not update it via kies, Only through repackaging and ODIN.
The most simple porting the firmware at P3110, let's start with him.
If the original firmware from the P3100.
1.Extract the firmware from p3100 with samsung-updates.com to a separate folder, there will be files
System.img
Sbl.bin
recovery.img
param.lfs
modem.bin
MLO
hidden.img
cache.img
boot.img
2.Delete files:
MLO
modem.bin
3.Replace with the files from the P3110/delete files:
recovery.img
Sbl.bin
4.Repack by total commander received the contents of a folder in the archive tar.
5.(Optional) sign the resulting file with a program for a signature. Tar archives (that turned out. Tar.md5 never hit counter custom roms)
6.Getting firmware can easily sew through odin / mobile odin / heimdall
If the original firmware on the P3113 ...
1.Extract the firmware from p3113 with samsung-updates.com to a separate folder, there will be files
System.img
Sbl.bin
recovery.img
modem.bin
hidden.img
cache.img
boot.img
2.Replace with the files from the P3110/delete files:
recovery.img
Sbl.bin
3.Repack by total commander received the contents of a folder in the archive tar.
4.(Optional) sign the resulting file with a program for a signature. Tar archives (that turned out. Tar.md5 never hit counter custom roms)
5.Getting firmware can easily sew through odin / mobile odin / heimdall
Now comes the portable to P3113:
If the original firmware from the P3100.
1.Extract the firmware from p3100 with samsung-updates.com to a separate folder, there will be files
System.img
Sbl.bin
recovery.img
param.lfs
modem.bin
MLO
hidden.img
cache.img
boot.img
2.Delete files:
MLO
modem.bin
3.Replace with the files from the P3113/delete files:
recovery.img
Sbl.bin
4.Repack by total commander received the contents of a folder in the archive tar.
5.(Optional) sign the resulting file with a program for a signature. Tar archives (that turned out. Tar.md5 never hit counter custom roms)
6.Getting firmware can easily sew through odin / mobile odin / heimdall
If the original firmware on the P3110 ...
1.Extract the firmware from p3110 with samsung-updates.com to a separate folder, there will be files
System.img
Sbl.bin
recovery.img
modem.bin
hidden.img
cache.img
boot.img
2.Replace with the files from the P3110/delete files:
recovery.img
Sbl.bin
3.Repack by total commander received the contents of a folder in the archive tar.
4.(Optional) sign the resulting file with a program for a signature. Tar archives (that turned out. Tar.md5 never hit counter custom roms)
5.Getting firmware can easily sew through odin / mobile odin / heimdall
Now comes the hard part: porting to P3100.
1.Extract the firmware from p3110/P3113 In a separate folder, there are files:
System.img
Sbl.bin
recovery.img
modem.bin
hidden.img
cache.img
boot.img
2.Add the firmware files
modem.bin
MLO
3.Replace with the files from the P3100/delete files:
recovery.img
Sbl.bin
4.Repack by total commander received the contents of a folder in the archive tar.
5.(Optional) sign the resulting file with a program for a signature. Tar archives (that turned out. Tar.md5 never hit counter custom roms)
6.Getting firmware can easily sew through odin / mobile odin / heimdall
7.Install the application to work with a 3G module (dialer, etc.)
Enjoy!
what is the different between boot.img and boot.bin I use WindowsLGFirmwareExtract-1.2.1.0-Release extact kdz file got boot.bin?
Nothing. Rename boot.bin to boot.img. Same thing
Sent from my LG-D801 using Tapatalk
Ok, in my case I had already upgraded to an MLD baseband, and after messing around with some ROMs, couldn't get back into safestrap recovery. I don't know if this will work if you've upgraded to NB1 or NC1, maybe someone else can chime in.
1. Install heimdall. It's in the ubuntu repositories. Also, put the towelroot and safestrap (I used v. 3.72) apks, as well as a kitkat ROM (no need for it to be pre-rooted). Also get the Deadly Venom safestrap kit, version 2 MLD/MK2 and save to your computer. Get the mldmodules.zip file and place on your SD card as well.
2. Download the appropriate firmware. In this case, you're looking for stock MK2/ I337. I got it from this link, and used the 4 separate files in post #1.
3. Untar the files. You can either rename the *.md5 files, removing the md5 extension, or just tar -xvf each file. You should end up with boot.img, cache.img.ext4, hidden.img.ext4, JFLTE_USA_ATT_16G.pit, modem.bin, NON-HLOS.bin, persdata.img.ext4, recovery.img, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn, system.img.ext4, and tz.mbn.
4. Put your device in download mode by pressing volume down + power, then letting go of power button. Connect your USB cable.
5. Run the following commands, which I got from here.
Code:
sudo heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img --no-reboot
I added the no-reboot option because I was able to see the errors on the device screen. I then rebooted back into download mode.
Code:
sudo heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
At this point I rebooted again, and it booted, but hung at the AT&T logo. I rebooted and it started normally. I didn't actually use the next step.
Code:
sudo heimdall flash --CACHE cache.img.ext4
And Poof! You're back to stock. At this point, go to My Files, and find the towelroot apk, and install it. Then install safestrap. Reboot to recovery (power + vol up), wipe everything except your SD under advanced wipe, and install your ROM. Don't reboot here--install the mldmodules.zip file. Now reboot back into download mode.
Unrar (or whatever, I forget how it was compressed) the Deadly Venom kit. You should end up with an MLD directory. Go to the MLD Odin Files directory, and untar the md5 files there. Again, you can rename them first or not. You should end up with:
modem.bin, recovery.img, sbl1.mbn, sbl3.mbn, ap_mld_safestrap.tar, bl_mld_safestrap.tar, boot.img, cp_mld_safestrap.tar.md5, NON-HLOS.bin, rpm.mbn, sbl2.mbn, and tz.mbn.
Ok, so here's where I did some guessing. I don't know how to use Heimdall, and I couldn't make sense of the front end. I did some trial and error, and here's the command that I ended up with that worked:
Code:
sudo heimdall flash --RECOVERY recovery.img --BOOT boot.img --ABOOT aboot.mbn --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --TZ tz.mbn --RPM rpm.mbn
Now reboot, and you should be in business. You may need to run towel root again. Oh, and I was getting a lot of weird errors when I was trying to flash with heimdall--I think it ended up being a flaky USB controller on my computer (or maybe a bad USB cable). The install kept hanging. Changing to a different computer solved the problem.
I stumbled through a lot of this, so if there is any redundancy, or if someone wants to improve on this, please do. But hopefully this helps someone...
Hey guys. I don't have a windows computer anymore and I'm trying to restore my wife's i9505 back to stock. Is there a one click file for heimdall I can use. I've been searching everywhere and can't find one. Thanks
Sent from my GT-N7100 using Tapatalk
Goneeuro said:
Hey guys. I don't have a windows computer anymore and I'm trying to restore my wife's i9505 back to stock. Is there a one click file for heimdall I can use. I've been searching everywhere and can't find one. Thanks
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Use this for reference:
http://andmod.blogspot.nl/2013/02/tutorial-flashing-i9000-i9100-or-i9300.html
You need to get the correct .pit file for the I9505.
You can also do it from the command prompt:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --ABOOT aboot.mbn
heimdall flash --BOOT boot.img
heimdall flash --HIDDEN hidden.img.ext4
heimdall flash --MDM modem.bin
heimdall flash --RECOVERY recovery.img
heimdall flash --RPM rpm.mbn
heimdall flash --SBL2 sbl2.mbn
heimdall flash --SBL3 sbl3.mbn
heimdall flash --SYSTEM system.img.ext4
heimdall flash --TZ tz.mbn
heimdall flash --CACHE cache.img.ext4
Click to expand...
Click to collapse
You can also do it one command: "heimdall flash --ABOOT aboot.mbn --BOOT boot.img" etc etc
Thanks. Hope all goes well tonight.
Sent from my GT-N7100 using Tapatalk
I have totally messed up my phone trying to flsah twrp its a samsung a300 fu
and now will only boot into twrp nothing else ive tried flashing a new rom from there but with no joy.
Im attempting to put a stock rom back on the phone im using A300FXCU1BOK3_A300FOJV1BOI1_A300FXXU1BOK3_HOME.tar.md5 which as im on linux im trying to flash using heimdall
so i have the following files / partitions
File Partition
aboot.mbn ABOOT
boot.img BOOT
cache.img.ext4 CACHE
hidden.img.ext4 HIDDEN
hyp.mbn
modem.bin MODEM
NON-HLOS.bin APNHLOS
recovery.img RECOVERY
rpm.mbn RPM
sbl1.mbn SBL1
sec.dat sec
system.img.ext4 SYSTEM
tz.mbn
Click to expand...
Click to collapse
So i am left with two files tz.mbn and hyp.mbn wihch i have no idea where to put in Heimdall can any oe gibe me a heads up as to where
therse two should go and if im even on the right track.
Cheers Dunryc
sure every one knew the answer but putting it here just oin case
aboot.mbn ABOOT
boot.img BOOT
cache.img.ext4 CACHE
hidden.img.ext4 HIDDEN
hyp.mbn QHEE
modem.bin MODEM
NON-HLOS.bin APNHLOS
recovery.img RECOVERY
rpm.mbn RPM
sbl1.mbn SBL1
sec.dat sec
system.img.ext4 SYSTEM
tz.mbn QSEE
Click to expand...
Click to collapse
Flash through windows if possible
If not then:
Open the tar.md5 file using any archiver.
Extract recovery.img
Put it into your sd card
Put sd card in phone
Boot into twrp
Go to install.
Where it is written images tap so it changes to zip
Navigate to your sd card where file is placed
Install recovery.img
Reboot
Sent from my SM-A500F using XDA-Developers mobile app
In TWRP go to "Reboot" and then "System".
My galaxy A3 always boot to twrp by itself but from TWRP I can boot normally.
EDIT: Works on TWRP 2.8, not 3.0