Hi @All,
maybe, there is a Thread bout this HOWTO, but I found nothing to use...
There are now different unofficial Firmwares, I flashed JM6-JMI, I cant remember, which CSC, PDA or PHone is really good, some FW dont have all these three things, so I want to extract this Files to have the ability testing JM6 up to the newest JMI....
My really problem is, how to extract these files and got it accurate!
jammysunny
It seems, there are no person to tell me how.....
This has already been answered.
http://forum.xda-developers.com/showthread.php?t=879569
This will help. Galaxy S forum also has extra quality knowledge.
(Extract JMA.tar (for example) using 7zip to a directory. Then use MagicISO to open the cache.rfs to find a folder called "Recovery" Inside are two files. One says "command" and one says "sec_csc.zip")
jammysunny said:
Hi @All,
maybe, there is a Thread bout this HOWTO, but I found nothing to use...
There are now different unofficial Firmwares, I flashed JM6-JMI, I cant remember, which CSC, PDA or PHone is really good, some FW dont have all these three things, so I want to extract this Files to have the ability testing JM6 up to the newest JMI....
My really problem is, how to extract these files and got it accurate!
jammysunny
Click to expand...
Click to collapse
if i get you right then roto backup is what you need.
Can someone skilled please explain in detail how to create a non-wipe version of a given stock rom?
I know that the data.img has to be removed from the according .tar.md5 file (see picture), in order to do that you have to open the file with a zip program (remove the .md5 or open it with "open with").
The problem is, after removing the data.img the .tar.md5 file want flash proper with odin. I guess this is due to a wrong md5 sum which was not changed during this process, and therefore is no longer valid!
I remember that I read once that you have to use a specific packer for that (winrar for example is not able to do this), but I cant find this source again!
Can someone please illuminate us in regard to that?
Thank you very much in advance!
ps.:
I posted this in development section because I think this is more development related as Q/A! If this violates the forum rules any mod should feel free to move this thread into Q/A...
You don't have to keep the .md5 extension to flash via odin, and thus skip the md5 checksum check.
But I don't know if it will flash properly after you removed the data.img
I have never tried that. Maybe you still have to modify a script or something...
I thought of using Mobile Odin and not selecting the Code.tar.md5 through the open file dialog, but rather selecting every part to flash individually and NOT selecting anything for data.
Too scared to try...
thanks latoc!
can someone with experience confirm that is it enough to remove the data file from the tar, repack it and don't add .md5?
I tried the mobile odin method and it wiped my phone even though nothing was selected in the data part.
There must be a script somewhere that tells the phone to wipe...
I made a backup before so no problem for me
Sent from my GT-N7000 using XDA App
Use peazip, it can create working tar images that can be flashed. Winrar corrupts tar. Some say 7z also does a good job. I haven't tried it as I was happy with peazip. You can even use gzip. Hope it helps.
You can even extract all the contents, remove add files, then use paezip or gzip to make a tar. Works perfectly. MD5 is not a necessity. If you want, you can create a MD5 hash for the new tar that you have created. Google it. Its easy.
ragin said:
Use peazip, it can create working tar images that can be flashed. Winrar corrupts tar. Some say 7z also does a good job. I haven't tried it as I was happy with peazip. You can even use gzip. Hope it helps.
You can even extract all the contents, remove add files, then use paezip or gzip to make a tar. Works perfectly. MD5 is not a necessity. If you want, you can create a MD5 hash for the new tar that you have created. Google it. Its easy.
Click to expand...
Click to collapse
thanks for the answer!
peazip uses 7zip via console, so its the same!
anyway, the tar from peazip wont flash! odin (1.83 and 1.85) stops with an error (could not write) with the boot.bin (from my modified tar), after that the phone wont boot and give the message: firmware update failed, use kies recovery mode blabla
only way to get it back to life without kies is to flash a proper boot.bin (sbl.tar), which is the software boot loader.
did you experience anything like that before?
No one with an idea?
There must be enough people with this knowledge around here...
Sent from my GT-N7000 using xda premium
I didn't try it myself but someone else post this link to this thread in the SGSII forums about what you're asking about, I want to try when I get home and get the latest LA3 firmware but here it is:
http://forum.xda-developers.com/showthread.php?t=1132724
matius44 said:
I didn't try it myself but someone else post this link to this thread in the SGSII forums about what you're asking about, I want to try when I get home and get the latest LA3 firmware but here it is:
http://forum.xda-developers.com/showthread.php?t=1132724
Click to expand...
Click to collapse
And this supercomplicated procedure achieves what exactly?
A non-wiping rom update?
I think he just wanted to delete the data image, repack and flash with odin.
Just needed the correct packer. Right?
legion1911 said:
And this supercomplicated procedure achieves what exactly?
A non-wiping rom update?
I think he just wanted to delete the data image, repack and flash with odin.
Just needed the correct packer. Right?
Click to expand...
Click to collapse
right, it should be enough to delete the data.img!
it looks like the problem is the packer, although i'm in contact with intratech (who is a xda-mod who did this a few times @sgs2 forums, besides he's really great in what he is doing!) and he meant that there could also be a wipe instruction inside the cache.img!
when i know more i will post it here!
TML1504 said:
right, it should be enough to delete the data.img!
it looks like the problem is the packer, although i'm in contact with intratech (who is a xda-mod who did this a few times @sgs2 forums, besides he's really great in what he is doing!) and he meant that there could also be a wipe instruction inside the cache.img!
when i know more i will post it here!
Click to expand...
Click to collapse
Great! Will be waiting for you're simpler procedure as I found that way hard myself!
Sent from my GT-N7000
TML1504 said:
thanks for the answer!
peazip uses 7zip via console, so its the same!
anyway, the tar from peazip wont flash! odin (1.83 and 1.85) stops with an error (could not write) with the boot.bin (from my modified tar), after that the phone wont boot and give the message: firmware update failed, use kies recovery mode blabla
only way to get it back to life without kies is to flash a proper boot.bin (sbl.tar), which is the software boot loader.
did you experience anything like that before?
Click to expand...
Click to collapse
I think you can safely remove boot.bin from the tar file. You should verify this before trying.
PS : If the bootloaders havent changed, why do you want to flash them? They are already there.
That packer could be used to easily install anything.
So if you find that packer, please let us know.
ragin said:
I think you can safely remove boot.bin from the tar file. You should verify this before trying.
PS : If the bootloaders havent changed, why do you want to flash them? They are already there.
Click to expand...
Click to collapse
it would be ok to remove the boot.bin as well, but then the flash would fail on the next (first) file odin tries to flash!
in case of not deleting boot.bin, this would be the first and therefore damage the boot partition, a reboot is not possible. that's the reason i hat to reflash sbl.bin!
the reason for this is again the packer, if the .tar would be ok, so would be the flash procedure!
intratech suggests to use linux and the following command to create a odin flashable tar:
Code:
tar -c boot.bin cache.img factoryfs.img hidden.img modem.bin param.lfs Sbl.bin zImage >> [Name of the desired file].tar
i will look far a tar executable for win32 and report!
done!!!
found a working packer: tar for win32
this was a little bit tricky, because the download from http://gnuwin32.sourceforge.net/packages/gtar.htm did not work, i always get the error message "The procedure entry point libiconv_close could not ..."
searching in google about that i discovered the following:
in the download from sourceforge is an old dll, the "libiconv-2.dll" which causes this error! you have to download a newer version from diffutils 2.8.7-1, which can be found here!
then, simple rename the inside libiconv2.dll to libiconv-2.dll and overwrite the one in the \bin dir from the C:\Program Files\GnuWin32\bin!
then add "C:\Program Files\GnuWin32\bin" to the path variables of your system, then you can use the tar command from the whole shell!
lol, until now this was all to get the tar program running! all people running linux won't need this steps, as tar should be fully functional for them!
then simple extract the rom files with whatever packer you like, you should see a file named "CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5" or whatever your original rom is. remove the .md5 and extract again, then you should end up with some more files:
boot.bin
cache.img
data.img
factoryfs.img
hidden.img
param.lfs
sbl.bin
zimage
now, tar the files you want to flash into one file with the shell command from intratech, for example:
tar -c boot.bin factoryfs.img hidden.img param.lfs sbl.bin >> filename.tar
you can also add whatever kernel you wish, add a zimage then!
DO NOT ADD CACHE.IMG, AS IT CONTAINS THE WIPE COMMAND!!!
now flash this file (and perhaps the proper modem.tar.md5) with odin as PDA (modem as phone) and you are done!
upgraded with this method from KL7 to LA3 without wipe and without any problems. once you have tar for win32 up and running it's really simple!
big thanks to intratech for aiding me about the cache.img and the tar syntax!!
ps.: i don't care about the yellow triangle nor the flash counter, as it is very easy to reset: use the sbl.bin from the sgs2, flash it, remove battery, use usb-jig, remove battery, flash sbl.bin from note, remove battery, done! no triangle, counter at 0
TML1504 said:
done!!!
found a working packer: tar for win32
this was a little bit tricky, because the download from http://gnuwin32.sourceforge.net/packages/gtar.htm did not work, i always get the error message "The procedure entry point libiconv_close could not ..."
searching in google about that i discovered the following:
in the download from sourceforge is an old dll, the "libiconv-2.dll" which causes this error! you have to download a newer version from diffutils 2.8.7-1, which can be found here!
then, simple rename the inside libiconv2.dll to libiconv-2.dll and overwrite the one in the \bin dir from the C:\Program Files\GnuWin32\bin!
then add "C:\Program Files\GnuWin32\bin" to the path variables of your system, then you can use the tar command from the whole shell!
lol, until now this was all to get the tar program running! all people running linux won't need this steps, as tar should be fully functional for them!
then simple extract the rom files with whatever packer you like, you should see a file named "CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5" or whatever your original rom is. remove the .md5 and extract again, then you should end up with some more files:
boot.bin
cache.img
data.img
factoryfs.img
hidden.img
param.lfs
sbl.bin
zimage
now, tar the files you want to flash into one file with the shell command from intratech, for example:
tar -c boot.bin factoryfs.img hidden.img param.lfs sbl.bin >> filename.tar
you can also add whatever kernel you wish, add a zimage then!
DO NOT ADD CACHE.IMG, AS IT CONTAINS THE WIPE COMMAND!!!
now flash this file (and perhaps the proper modem.tar.md5) with odin as PDA (modem as phone) and you are done!
upgraded with this method from KL7 to LA3 without wipe and without any problems. once you have tar for win32 up and running it's really simple!
big thanks to intratech for aiding me about the cache.img and the tar syntax!!
ps.: i don't care about the yellow triangle nor the flash counter, as it is very easy to reset: use the sbl.bin from the sgs2, flash it, remove battery, use usb-jig, remove battery, flash sbl.bin from note, remove battery, done! no triangle, counter at 0
Click to expand...
Click to collapse
Bravo, Wiener, Bravo!
Btw I found another way and just did it.
I used dsixda kitchen to deodex, root, zipalign and make a non-wipe version and it was easy!
Thought I might share it with you guys
Sent from my GT-N7000
thx for the info, but i personally dislike most deodexed roms!
besides it could cause unknown troubles (remember tha smali baksmali issue) it generally runs less smooth! the reason? simply speaking odexed is optimized (the o in odex), deodex trades this optimizations for the advantage of being simpler to skin, modify etc.
this means deodexed may be acceptable for people who want to skin and modify a lot, therefore almost all custom roms are deodexed. it makes it simpler for the cook!
you as an enduser would almost always prefer odexed roms. also lots of quality mods are available for odexed too...
just my opinion, and i used to use custom roms a lot!
Sent from my GT-N7000 using xda premium
Ok I just upgraded from KKA to LA3 without wiping using nothing but the stock files and mobile odin:
Launch mobile odin, and fill each line one by one, selecting the correct firmware file, except data and cache.
Select ever root if you didn't select a rooted kernel, and flash that baby! !!
Sent from my GT-N7000 using XDA App
Latoc said:
Ok I just upgraded from KKA to LA3 without wiping using nothing but the stock files and mobile odin:
Launch mobile odin, and fill each line one by one, selecting the correct firmware file, except data and cache.
Select ever root if you didn't select a rooted kernel, and flash that baby! !!
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
also thx, for me this didn't work from KL7 to LA1, got bootloops! but generally fine if this was only my fault, and the odin method works fine!
Here is the PIT file for a SM-N915A for those who may need it.
Click "PIT" and select the PIT file associated with the Android ROM you're flashing with ODIN. Click "PDA" and select the TAR file for the ROM. Click "Start" to add this ROM to your Samsung phone. The installation is complete when your phone automatically reboots.
MaHo_66 said:
ODIN buttons explanation:
BL refers to the bootloader
AP refers to the build version of the software/firmware
CP refers to the baseband/modem version
CSC is the consumer software customisation and is specific to geographical region and carriers. it contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider
CSC has nothing to do with what languages the firmware supports and it will not add keyboard language support either
PIT refers to the Partition Information Table you only need it if you screw up your partition table or if the firmware specifically requires it because of a change in the partition table layout. its very likely you may never have to use this, at least i hope so however KEEP IN MIND there is a HIGH chance of bricking your device with a bad partition table if you do this wrong!! dont forget to check the box re-partition if youre gonna use it!
if the package only contains one .tar md5 file then it will have everything, AP+BL+CSC+CP, in one file
a stock firmware downloaded from sammobile or samsung updates will contain all of these in one .tar md5 file
if it has multiple .tar md5 files then:
the .tar md5 with modem/CP in the name is the phone/baseband part of the package
the .tar md5 with CSC/multi-csc in the name is the csc part of the package
the .tar md5 with code/AP in the name is the AP part of the firmware package
the .tar md5 with BL in the name is the bootloader part of the package
if this is the case you will need to put these .tar md5 files in the specific areas of odin to flash the update/stock rom
Click to expand...
Click to collapse
Hit the Thanks if this is helpful
Yo, where did you get this?? Any chance you could get a Sprint N915P pit??
z31k said:
Yo, where did you get this?? Any chance you could get a Sprint N915P pit??
Click to expand...
Click to collapse
Sent you a reply to your pm [emoji2]
there is no root file available for N915A. Will update the article, once it’s released by the official developers.
Hi! sorry for my question, im new in this... The PIT file needs to be flashed with the firmware associated, so... what is the version of the firmware associated with this PIT?
Thanks.!
My Emmc just started freezing up, so I did some research & one of the most effective method indicate that if we rapartition the emmc in such a way that it it will skip the bad sectors, then problem can be resolved, while looking at partition map for note 4, I saw all small partitions including system are within first 5gb, so I was thinking if we can create a pit file that can start the partition from 5gb onward, leaving first 5gb useless, maybe device will be usable, I created the pit, but Odin won't let me flash it , saying " Secure check fail : Pit", any ideas or if anyone can modify the pit file that would be great.Here is the attachment containing original pit file.
I have the same problem and your suggested logic might be the solution we need. Let's c who can help
How to extract zip64 archive?
I have j510fn nougat firmware, but while extracting it stuck on 90%. I/O device error ?
My operating system win7 32bit
What are you trying to do? Extracting prom phone to pc (so as a backup) o like downloading the file from the web and extracting the content to flash it?
BlackJack67 said:
What are you trying to do? Extracting prom phone to pc (so as a backup) o like downloading the file from the web and extracting the content to flash it?
Click to expand...
Click to collapse
Extracting the firmware to flash it
sorry late reply
ivan'z said:
Extracting the firmware to flash it
sorry late reply
Click to expand...
Click to collapse
I never saw someone uploading a zip64 file as a rom, are you sure about what you're doing? ?
Anyway, try extracting it onto the pc hdd/ssd making sure you have enough space to do it, then put the rom on the phone's sd card via usb cable, that should do it :good:
Btw, what rom are you trying to flash?
BlackJack67 said:
I never saw someone uploading a zip64 file as a rom, are you sure about what you're doing? ?
Anyway, try extracting it onto the pc hdd/ssd making sure you have enough space to do it, then put the rom on the phone's sd card via usb cable, that should do it :good:
Btw, what rom are you trying to flash?
Click to expand...
Click to collapse
I'm trying to flash nougat firmware, but cannot to extract the firmware, always stuck on 90% (can't read I/O device error). When I see the firmware info on winrar it seem that use zip64 archive format (zip64 library), because the content after extracting is 3gb, I think that's the problem while extracting. My laptop is low specification, also I'm trying to transfer to another pc using usb flashdisk but I got stuck while transferring, transfer failed. I never seem like this before , cannot to transfer unable to extract, wtf? Firmware corrupted? I think not.
ivan'z said:
I'm trying to flash nougat firmware, but cannot to extract the firmware, always stuck on 90% (can't read I/O device error). When I see the firmware info on winrar it seem that use zip64 archive format (zip64 library), because the content after extracting is 3gb, I think that's the problem while extracting. My laptop is low specification, also I'm trying to transfer to another pc using usb flashdisk but I got stuck while transferring, transfer failed. I never seem like this before , cannot to transfer unable to extract, wtf? Firmware corrupted? I think not.
Click to expand...
Click to collapse
Since I never had to deal with zip64 format (I always ended up downloading only zip file ready to flash), can you share the link where you downloaded the firmware? Let's see if it's a hardware problem or a bad file
BlackJack67 said:
Since I never had to deal with zip64 format (I always ended up downloading only zip file ready to flash), can you share the link where you downloaded the firmware? Let's see if it's a hardware problem or a bad file
Click to expand...
Click to collapse
The firmware is downloaded from samsung-firmware.org, region asia INS. I was download marshmallow firmware too and flash it to my phone but I don't see any problem while extracting the firmware, I'm using another pc with operating system window 10 64bit. I think the problem is my pc can't handle/read zip64 format even using winrar or 7-zip with latest version. The dialogue show error mssg "problem read file, I/O device error".
ivan'z said:
The firmware is downloaded from samsung-firmware.org, region asia INS. I was download marshmallow firmware too and flash it to my phone but I don't see any problem while extracting the firmware, I'm using another pc with operating system window 10 64bit. I think the problem is my pc can't handle/read zip64 format even using winrar or 7-zip with latest version. The dialogue show error mssg "problem read file, I/O device error".
Click to expand...
Click to collapse
On the site you linked, every firmware is in zip format, so ready to flash. I can't find any zip64 archive.
If you still face the problem, try looking up the firmware on sammobile
BlackJack67 said:
On the site you linked, every firmware is in zip format, so ready to flash. I can't find any zip64 archive.
If you still face the problem, try looking up the firmware on sammobile
Click to expand...
Click to collapse
I'm not sure is the firmware in zip format or zip64 format, but while repairing the firmware it detect as zip64, don't know. Maybe the firmware is brocken, damage, cause trying to extract many times. Anyway thanks for help.
Maybe the file is corrupt.Changing compression method won't help.You can't repair an archive.Just download it again.