i know most of you guys are angry about posting this.but i use the search button can't find anything about this.
My question is i downloaded jm8 from "samfirmware . com",i unpacked it and only i got CODE_I9000XWJM8.tar and MODEM_I9000XXJM4.tar. What is CODE.tar.??is that pda file and there is no csc file.i found a multi csc from jm9 thread.can i apply this csc??
mertkan said:
i know most of you guys are angry about posting this.but i use the search button can't find anything about this.
My question is i downloaded jm8 from "samfirmware . com",i unpacked it and only i got CODE_I9000XWJM8.tar and MODEM_I9000XXJM4.tar. What is CODE.tar.??is that pda file and there is no csc file.i found a multi csc from jm9 thread.can i apply this csc??
Click to expand...
Click to collapse
CODE is PDA,MODEM is PHONE,CSC is CSC.Yes you can apply csc from JM9.
Regards
Its not the question but the section which is not correct.
We have a special section called Q/A for these questions. Please use it next time.
ANSWER: http://www.youtube.com/watch?v=PpWcM44On88
Any of you guys who's got the files for flashing back to jm8? I downloaded the file from samfirmware.com but it seems to be corrupt and winrar only gives med a attention message teeling me that the file doesn't work. I need JM8 and also I would need the working files for jpa. When I downloaded JPA I only seemed to get one .tar-file
Thanks for any help you could give me
Does anyone know how to use these files to flash an R800a? Or is there some kind of tool to convert them to an ftf? I recently used an online service (DivinciTeam) to flash my phone back to a Rogers 2.3.2 firmware, these are the files that were used. I'd like to do a bit more experimenting with my phone but would like a way to go back to the Rogers 2.3.2 firmware (to keep root) without having to pay for the service every time. I know there is a generic UK 2.3.2 firmware, but that didn't seem to work for me (phone was constantly roaming when used that firmware). If anyone has any ideas, please let me know. Thanks.
Use flashtool and do a bundle creation and it should make the ftf out of those files but I'm not 100% I've only ever done it a couple times with my x10
* if that is gonna be the Rogers 2.3.2 upload it to the dev section please and thank you!*
Sent from my R800i using XDA App
sin_file_set can be unzipped with 7-Zip. Inside you'll find standard .sin files.
I've tried using flashtool to package it into an ftf, it goes through the decrypting but I end up with no files.
I will give 7-zip a go to see if I can get the .sin files out of it.
Yes, it is the Rogers 2.3.2. I will upload it if I get it working (don't have enough posts to post in the dev section).
UPDATE: Tried 7-zip, didn't work. Gave an error about it not being an archive.
SanGai said:
I've tried using flashtool to package it into an ftf, it goes through the decrypting but I end up with no files.
I will give 7-zip a go to see if I can get the .sin files out of it.
Yes, it is the Rogers 2.3.2. I will upload it if I get it working (don't have enough posts to post in the dev section).
UPDATE: Tried 7-zip, didn't work. Gave an error about it not being an archive.
Click to expand...
Click to collapse
Strange. You should be able to open sin_file_set with 7-Zip, unless Davinc Team uses special encryption on sin_file_set - I wouldn't be surprised if they did.
I guess thats always a possibility.
Anyway to get it directly off the phone? It still on 2.3.2.
Ok, I've uploaded the .SIN_FILE_SET if anyone wants to see if they can create an ftf out of them.
http://www.megaupload.com/?d=RNJMLOGS
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!
First of all - There isnt any thread about Extracting The Complete Stock ROM from the phone, and then Creating a flashable Odin file ( Tar.md5 )
So heres my Question that can any of the XDA People give a procedure to extract the STOCK ROM from the Phone ( CSC, Modem, PDA etc ) and creating a Md5 file which can be later used.
The xda people already have procedure for you sire
http://forum.xda-developers.com/showthread.php?t=1777579
Thanks a Lot !
rvalvekar said:
Thanks a Lot !
Click to expand...
Click to collapse
You are welcome! Happy to be of help
Some questions ;
I have a CDMA Galaxy Y phone - so what all should i be dumping to create a tar file. Also Do i need to create separate csc pda and modem files ? or in Single Package i can Make a flashable tar file ?
So if i have to create separate csc pda and modem files for odin, how can that be done ?
and also if a single file - how to do that
Thanks
rvalvekar said:
Some questions ;
I have a CDMA Galaxy Y phone - so what all should i be dumping to create a tar file. Also Do i need to create separate csc pda and modem files ? or in Single Package i can Make a flashable tar file ?
So if i have to create separate csc pda and modem files for odin, how can that be done ?
and also if a single file - how to do that
Thanks
Click to expand...
Click to collapse
make sure the radio is correct (phone.csc) since that contains the telephony device drivers and you must exersise extra care,
remember most SGY roms are built for GSM/Intl. Version,
try and asking anyone with a CDMA version if they have successfully flashed a custom rom with it
http://forum.xda-developers.com/showthread.php?t=1777579
From the link above - there are several dump codes fro example system , recovery, modem etc.
I want to know
is PDA = SYSTEM ?
Modem = Modem ?
then Which dump to take as CSC ?
delete
Good Morning,
Can someone please tell me if its possible to split the Roms from Samfirmware into their component parts,(ie pda,csc etc) and rebuild with different componetnts. I want to be able to use the XEO rom with the H3G modem (csc)
(Should have made it clearer,it's the system image in the package i want to split)
Any help appreciated
Bill
billd2439 said:
Good Morning,
Can someone please tell me if its possible to split the Roms from Samfirmware into their component parts,(ie pda,csc etc) and rebuild with different componetnts. I want to be able to use the XEO rom with the H3G modem (csc)
(Should have made it clearer,it's the system image in the package i want to split)
Any help appreciated
Bill
Click to expand...
Click to collapse
The package from Sammobile breaks down into an MD5 file using 7zip. Then the MD5 breaks down into the components. You can replace the parts like modem but then you need to recompile - on Win PC's that means something like cygwin to do it. Search for cygwin and you should find threads about how to do what you want.
Hope that helps - you are right, your request is a little confusing. (as in you don't need to alter system.img.ext4 to change the modem)