I dont have access to a linux box and I think in order to flash the latest JMA firmware from samfirmware i need to extract the rfs files in order to load them up via odin...if im completely off please disregard or point me to the correct path..
if any helpful souls out there that wouldnt mind extracting the files and uploading them here?
thanks
Im just a noob trying to flash the latest JMA firmware on my JM6 tab
thanks again..
EDIT - Thank you all for explaining it:
For anyone else presented with the same issue; use the zipped JMA file in odin in the PDA box and the pit file located at the bottom of the samfirm page when flashing the latest JMA firmware.
Eltahur said:
I dont have access to a linux box and I think in order to flash the latest JMA firmware from samfirmware i need to extract the rfs files in order to load them up via odin...if im completely off please disregard or point me to the correct path..
if any helpful souls out there that wouldnt mind extracting the files and uploading them here?
thanks
Im just a noob trying to flash the latest JMA firmware on my JM6 tab
thanks again..
Click to expand...
Click to collapse
Extract them yourself by opening the file with 7Zip or WinZip. They're just archives.
Also - Should be in the General section.
knightnz said:
Extract them yourself by opening the file with 7Zip or WinZip. They're just archives.
Also - Should be in the General section.
Click to expand...
Click to collapse
thanks for the tips. I just installed both winzip and 7zip and could not extract the factory.rfs file with either.....
im guessing I have to extract the factory.rfs file and zip as a tar file for odin right?
Eltahur said:
thanks for the tips. I just installed both winzip and 7zip and could not extract the factory.rfs file with either.....
im guessing I have to extract the factory.rfs file and zip as a tar file for odin right?
Click to expand...
Click to collapse
The file you download is a zip file. Unzip it. There should be a tar file in there, tar is an archive format (similar to the way zip is, only it's uncompressed), so use 7zip or other unarchiving software to untar the file. There will be all of the JMA files including the RFS images contained in the tar file.
maniac3389 said:
The file you download is a zip file. Unzip it. There should be a tar file in there, tar is an archive format (similar to the way zip is, only it's uncompressed), so use 7zip or other unarchiving software to untar the file. There will be all of the JMA files including the RFS images contained in the tar file.
Click to expand...
Click to collapse
I see, so i downloaded a ziped file from samfirmware with the JMA firmware, unziped it down and got the pit file but there were no tar files in there for me to use in odin under the PDA box.
when flashing JMA what file do i put in PDA box? i pressume thats the only file i will use besides the pit file given that i dont want to replace the modem (phone) file...
I'm sorry if this is not making any sense
Eltahur said:
I see, so i downloaded a ziped file from samfirmware with the JMA firmware, unziped it down and got the pit file but there were no tar files in there for me to use in odin under the PDA box.
when flashing JMA what file do i put in PDA box? i pressume thats the only file i will use besides the pit file given that i dont want to replace the modem (phone) file...
I'm sorry if this is not making any sense
Click to expand...
Click to collapse
Go find the thread here that has the JMA firmware, that's where I got mine from
Eltahur said:
I see, so i downloaded a ziped file from samfirmware with the JMA firmware, unziped it down and got the pit file but there were no tar files in there for me to use in odin under the PDA box.
when flashing JMA what file do i put in PDA box? i pressume thats the only file i will use besides the pit file given that i dont want to replace the modem (phone) file...
I'm sorry if this is not making any sense
Click to expand...
Click to collapse
Use the JMA file here on XDA. Extra JMA.tar. Select that file ALONE as PDA. No repartition, PIT, Phone or CSC. It'll update PDA, Phone and CSC automatically.
If it doesn't reboot on its own after flash is complete, reboot into recovery.
You should be upgrading to JMA from JM6.
If you still need to extract/unpackage RFS->
Reffer to my guide here
Cheers
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!
Hey guys!
So I was just installing S5 Settings from balliboxer
and now I am an idiot to backup the secsettings apk and odex.
After I installed it, it gone FC.
Please somebody have an stock 4.4.2 SecSettings.apk and odex file please?
I'm running on 4.4.2 G7102 NH1.
sorry i don't have nh1 so i can't help you but what about four threads for the same thing , it's not realy serious man if you need help just post one time
if you have a pc :
domload your rom from Sam
http://www.sammobile.com/firmwares/download/36186/G7102XWUBNI2_G7102OLBBNI2_XSE.zip/
--extract it yoy will have G7102XWUBNI2_G7102OLBBNI2_XSE.tar.md5 use 7zip and extract it
--When you have completed extracting all of them, you'll find many files including many .img files. For Apps you need to extract system.img. Unlike normal nandroid backup's system.img file which in yaffs, this stock one in different. So, unyaffs tool can't unpack the system.img
--To extract the system.img, download this tool: sgs2toext4 (created by drphrozen). On extracting it you'll have sgs2toext4.jar file.
--Open a command window and set the directory where you have .jar file.
--Now type sgs2toext4.jar and press enter.
--The .jar will run in a new window & will ask you to drag & drop the system.img file there. Do the same and wait till the process completes.
--When the process completes, you'll find a file named system.ext4.img in the same folder where you had the system.img file.
--Now download ext2reader and install it. Then open the program open your system.img.ext4
--Now navigate in to find the apk you need and extract it copy to your phone
maxx35000 said:
sorry i don't have nh1 so i can't help you but what about four threads for the same thing , it's not realy serious man if you need help just post one time
if you have a pc :
domload your rom from Sam
http://www.sammobile.com/firmwares/download/36186/G7102XWUBNI2_G7102OLBBNI2_XSE.zip/
--extract it yoy will have G7102XWUBNI2_G7102OLBBNI2_XSE.tar.md5 use 7zip and extract it
--When you have completed extracting all of them, you'll find many files including many .img files. For Apps you need to extract system.img. Unlike normal nandroid backup's system.img file which in yaffs, this stock one in different. So, unyaffs tool can't unpack the system.img
--To extract the system.img, download this tool: sgs2toext4 (created by drphrozen). On extracting it you'll have sgs2toext4.jar file.
--Open a command window and set the directory where you have .jar file.
--Now type sgs2toext4.jar and press enter.
--The .jar will run in a new window & will ask you to drag & drop the system.img file there. Do the same and wait till the process completes.
--When the process completes, you'll find a file named system.ext4.img in the same folder where you had the system.img file.
--Now download ext2reader and install it. Then open the program open your system.img.ext4
--Now navigate in to find the apk you need and extract it copy to your phone
Click to expand...
Click to collapse
Thanks dude! And sorry for those 4 threads. Gonna download it!
This will take soooooo long! My Internet connection is slow and can complete in 9-10 hours!
Just be patient and people will see your thread and help you! But making FOUR posts...?
maxx35000 said:
sorry i don't have nh1 so i can't help you but what about four threads for the same thing , it's not realy serious man if you need help just post one time
if you have a pc :
domload your rom from Sam
http://www.sammobile.com/firmwares/download/36186/G7102XWUBNI2_G7102OLBBNI2_XSE.zip/
--extract it yoy will have G7102XWUBNI2_G7102OLBBNI2_XSE.tar.md5 use 7zip and extract it
--When you have completed extracting all of them, you'll find many files including many .img files. For Apps you need to extract system.img. Unlike normal nandroid backup's system.img file which in yaffs, this stock one in different. So, unyaffs tool can't unpack the system.img
--To extract the system.img, download this tool: sgs2toext4 (created by drphrozen). On extracting it you'll have sgs2toext4.jar file.
--Open a command window and set the directory where you have .jar file.
--Now type sgs2toext4.jar and press enter.
--The .jar will run in a new window & will ask you to drag & drop the system.img file there. Do the same and wait till the process completes.
--When the process completes, you'll find a file named system.ext4.img in the same folder where you had the system.img file.
--Now download ext2reader and install it. Then open the program open your system.img.ext4
--Now navigate in to find the apk you need and extract it copy to your phone
Click to expand...
Click to collapse
Unfortunately this doesn't work. When you drop the system.img.ext4 file onto the sgs2ext4 tool, no file is produced. The tool just keeps endlessly repeating:
"system.img.ext4 32 B 0 B/s"
I think that tool is too old (2.5 years old) and doesn't support the newest Samsung firmwares.
siraltus said:
Unfortunately this doesn't work. When you drop the system.img.ext4 file onto the sgs2ext4 tool, no file is produced. The tool just keeps endlessly repeating:
"system.img.ext4 32 B 0 B/s"
I think that tool is too old (2.5 years old) and doesn't support the newest Samsung firmwares.
Click to expand...
Click to collapse
witch firmware do you want to extract ?and whitch file you want ?
i 've extract my latest firmware 09/2014 so it work fine for me
maxx35000 said:
witch firmware do you want to extract ?and whitch file you want ?
i 've extract my latest firmware 09/2014 so it work fine for me
Click to expand...
Click to collapse
The T-Mobile Galaxy Note 4 (SM-N910T) NK4 firmware. I can't find any instructions online on extracting Samsung firmwares other than these, which were originally written up by rwilco12 a long time ago and reposted endlessly.
siraltus said:
The T-Mobile Galaxy Note 4 (SM-N910T) NK4 firmware. I can't find any instructions online on extracting Samsung firmwares other than these, which were originally written up by rwilco12 a long time ago and reposted endlessly.
Click to expand...
Click to collapse
you have one solution try to extract md5 file
and direct mount system.img in ubunt it work for me then copy the file you want
maxx35000 said:
you have one solution try to extract md5 file
and direct mount system.img in ubunt it work for me then copy the file you want
Click to expand...
Click to collapse
I'll try doing that in a Linux VM. I'm on Windows and the Diskinternals Linux Reader keeps saying the filesystem is invalid.
siraltus said:
I'll try doing that in a Linux VM. I'm on Windows and the Diskinternals Linux Reader keeps saying the filesystem is invalid.
Click to expand...
Click to collapse
give me a link to download the system.img i try to extract it
maxx35000 said:
give me a link to download the system.img i try to extract it
Click to expand...
Click to collapse
Thank you for your help. It's this firmware: http://www.sammobile.com/firmwares/download/39224/N910TUVU1ANK4_N910TTMB1ANK4_TMB.zip/
Anything? Is this a no-go?
siraltus said:
Thank you for your help. It's this firmware: http://www.sammobile.com/firmwares/download/39224/N910TUVU1ANK4_N910TTMB1ANK4_TMB.zip/
Click to expand...
Click to collapse
sorry i have forget to do it i download the file now
but what the files needed in ?
maxx35000 said:
sorry i have forget to do it i download the file now
but what the files needed in ?
Click to expand...
Click to collapse
I just want to find a method that works for extracting the Note 4 firmware because none I found online work.
siraltus said:
I just want to find a method that works for extracting the Note 4 firmware because none I found online work.
Click to expand...
Click to collapse
I found that the Linux method works on my Mac. Took a ton of tinkering and restarting the emulator on my machine.
sgs2ext4.jar did not work for me in Windows. It just hangs.
sbrownla said:
I found that the Linux method works on my Mac. Took a ton of tinkering and restarting the emulator on my machine.
sgs2ext4.jar did not work for me in Windows. It just hangs.
Click to expand...
Click to collapse
yes sgs2ext4.jar work with some of system.img but not all but you can mount in linux i have extracted note 4 img :good:
maxx35000 said:
give me a link to download the system.img i try to extract it
Click to expand...
Click to collapse
The SAMMOBILE firmware or the system.img? I'm not yet downloading it. Let's see if I can resume the download.
Many people find this issue while flashing stock frimware via Odin That after system.img is done Odin gets failed so I came up with a fix.
1) On pc open the firmware with winrar (or any other software like 7zip)
2)Then extarct the file named hidden.img from it to any place.
3) Rename the hidden.img file as hidden.img.tar . 4)Reflash the frimware through odin
5)You will get failed again but now flash the hidden.img.tar with odin now it will be successful and your phone will boot.
If the problem is still there or anyone needs to ask something qoute this post and not the whole first post (please)
@naimrlet mention this in the master thread too
This problem also occurs when you are flashing a different stock frimware for same device (e.g. different country firmware for same device) like people flashing aol1 for g531h to make s6/j7 mod by @ERICKONIX, work. This fix will also work that case too
waleeds1 said:
3) Rename the hidden.img file as hidden.img.tar
Click to expand...
Click to collapse
Doing this is the same as not flashing the Hidden partition. You can't just rename it, you need to tar it. Just use 7-zip for it
fabiossilva21 said:
Doing this is the same as not flashing the Hidden partition. You can't just rename it, you need to tar it. Just use 7-zip for it
Click to expand...
Click to collapse
No it involves flashing the hidden because if you rename with the extension it becomes tar. But sometimes you need to turn an option on the pc to see the extension but to know that it became tar when you rename it, the icon changes from winrar to the icon associated with tar files
fabiossilva21 said:
Doing this is the same as not flashing the Hidden partition. You can't just rename it, you need to tar it. Just use 7-zip for it
Click to expand...
Click to collapse
Nah no need to tar it just rename