So, I came across this today. I'll try to explain exactly what this is.. I work as a repair tech in a sprint store. I have a somewhat universal tool that can theoretically "rescue" any (and I mean ANY) bricked phone by reloading the firmware (I realize this already exists for this phone, but this one seems unique).
In this tool, I noticed there was a non-working entry, D-700. Looking within the folder, I found a .tar copy of the DG27 firmware, including the following files (in order of filesize, smallest first):
boot.bin
param.lfs
Sbl.bin
cache.rfs
datafs.rfs
recovery.bin
zImage
modem.bin
factoryfs.rfs
It seems the .rfs files are bit-for-bit dumps of the stock firmware, although I could be (and probably am) wrong.
Anyway, it looked like it might be useful for an experienced dev, so I zipped the whole thing for you guise.
http://www.megaupload.com/?d=81ITRU09
benjio12 said:
So, I came across this today. I'll try to explain exactly what this is.. I work as a repair tech in a sprint store. I have a somewhat universal tool that can theoretically "rescue" any (and I mean ANY) bricked phone by reloading the firmware (I realize this already exists for this phone, but this one seems unique).
In this tool, I noticed there was a non-working entry, D-700. Looking within the folder, I found a .tar copy of the DG27 firmware, including the following files (in order of filesize, smallest first):
boot.bin
param.lfs
Sbl.bin
cache.rfs
datafs.rfs
recovery.bin
zImage
modem.bin
factoryfs.rfs
It seems the .rfs files are bit-for-bit dumps of the stock firmware, although I could be (and probably am) wrong.
Anyway, it looked like it might be useful for an experienced dev, so I zipped the whole thing for you guise.
Uploading now.. I'll update with a link in about 40 mins.. I'm at work on a slow connection!
Click to expand...
Click to collapse
Thanks but its already been released.
while this was released a while ago, thank you very much for the tip. its always good to have an insider
now about froyo
Guess I'm out of the loop again lol.. I saw the system dump a bit ago and the samsung open source stuff a few days later, but that's about it. Didn't dig too deep into the open source stuff, but I figured maybe this had something new in it somewhere.. oh well..
PS, I'm hearing froyo is scheduled for late october..
benjio12 said:
So, I came across this today. I'll try to explain exactly what this is.. I work as a repair tech in a sprint store. I have a somewhat universal tool that can theoretically "rescue" any (and I mean ANY) bricked phone by reloading the firmware (I realize this already exists for this phone, but this one seems unique).
In this tool, I noticed there was a non-working entry, D-700. Looking within the folder, I found a .tar copy of the DG27 firmware, including the following files (in order of filesize, smallest first):
boot.bin
param.lfs
Sbl.bin
cache.rfs
datafs.rfs
recovery.bin
zImage
modem.bin
factoryfs.rfs
It seems the .rfs files are bit-for-bit dumps of the stock firmware, although I could be (and probably am) wrong.
Anyway, it looked like it might be useful for an experienced dev, so I zipped the whole thing for you guise.
http://www.megaupload.com/?d=81ITRU09
Click to expand...
Click to collapse
SN-RMS? Cause I use that
Related
i need to know i9003 full partition table for make tar stock rom (2.2.1 TUR is not anywhere as odin file)
like;
if=/dev/block/bm17 (it only for example)
i will take from phone that files (for froyo 2.2.1)=
boot.bin
recovery.img
normalboot.img
sbl.bin
param.lfs
system.rfs
cache.rfs
userdata.rfs
modem.bin
and i ll make it tar for odin. is it possible for froyo?
thanks for help...
I know that i9000 is different from i9003, but this could be helpful: http://forum.xda-developers.com/showthread.php?p=8768644#post8768644
If you open a latona.pit file with a text editor, you'll find in the same things posted by sztupy in the same order and I don't think is just a coincidence. However I never made a rom and I'm not sure of what I'm saying, so don't blame me if you do something wrong .
Probably this other thread will be helpful in your investigation if none can't help you: http://forum.xda-developers.com/showthread.php?t=1271416 (post #7)
i ll try it. thanks a lot
I have spent several weeks working on this (reading thread after thread) on modifying stock firmware and im running into a problem. I more or less want to know if what i want to do is actually possible. I have downloaded the original .tar.md5 firmware image, opened with 7zip and "extracted" the .tar file (more or less just removed the hash) and then extracted the .img files from the .tar file. I have unpacked/mounted/modified/repacked using several methods (dsixda kitchen -which havent been able to work around adding the java path since after i add the path cygwin thinks im missing clean app until i remove the path in which case i get an error saying it cant find java/ i have tried mounting using ext4_utils in ubuntu) my issue arises when i take my modified and repacked system.img file i cant get it to work either by 1. zipping it in a .tar with the other .img files and flashing with odin, 2. zipping system.img alone into a .tar and flashing with odin, 3. installing cwm/root and flashing the system.img)
More or less my question is
1. is it possible to modify the stock firmware and load it onto the tablet without rooting
2. can system.img be flashed by itself or does it need the other .img files in the same .tar
3. does the tar file require being signed before flashing even with CWM recovery and root already on the tablet?
I have used these forums for a while to find answers, but i am new to posting, i havent needed to post a question until now since i spend as much time researching as i can before bothering people with a question (i like to figure stuff out and hate to admit defeat) Thanks in advance for the help despite my noobishness
Deleted
Can you tell me, what is the function of PIT file? sorry i'm noob
freshtanto said:
Can you tell me, what is the function of PIT file? sorry i'm noob
Click to expand...
Click to collapse
These 2 XDA threads offer information on PIT files:
http://forum.xda-developers.com/showthread.php?t=816449
http://forum.xda-developers.com/showthread.php?t=999097
Basically, I'd only ever use a PIT file if Odin threw up an error relating to it, 99% of the time these are not needed when using Odin unless you've screwed up your devices partitions.
It's handy to have this file saved as a backup though just in case that ever happened
okey i got it now, thanks it's really hepful :good::good::good:
invalid pit for t310
This file is also necessary to build packages for Heimdall. FYI
This file is also necessary to build packages for Heimdall. FYI
Your pit-file kill my tablet..............
MNKF said:
Your pit-file kill my tablet..............
Click to expand...
Click to collapse
How, a little more information would be nice?
What model did you use it on; T310, T311 or T315?
What options did you tick in ODIN?
I compared the same PIT file to one extracted with heimdall on my T310, all entries/contents were the same, it came from a T311 firmware package but T310 firmware packages also have the same file. T315 uses a different named PIT file hence why I was uncertain.
Just now I've even compared it to another PIT file off the SamMobile forums that a Moderator posted for the T310, everything is the same, ODIN will reject it if it isn't signed as well.
https://www.diffchecker.com/cta675hS
I didn't force you to use the file, nor was this a guide in anyway, your device must have been in a bad way for you to consider using it.
In any case I've now removed the file.
Im still expirmenting with different ways of possibly, hopefully, someday over the rainbow, getting my S7 successfully downgraded. Ive taken so much time waiting for things to copy and paste, and convert, and made a custom firmware hours later, only for odin to either freeze or straight up shut down after reaching file analysis... so im exploring other ways. im not sure if its a good idea to flash only parts of the firmware? like just the AP files?
I wish samsung would allow us to say "I dont care if my phone isnt as secure" and then their butts are covered cuz we consented and we can still downgrade the bootloader and android version as desired.
i cant find any information on how to make a disk image into an lz4 file (as in oreo) since that one system file from the marshmallow stock is simply a disk image, so i went about it the other way and removed the lz4 from all of the oreo files, making them all either plain .bin or plain .img files except leaving the pit file and the meta data folder alone, and then repackaged them back into the same categorized tar.md5 files. odin checks them as legit, but just wont actually *DO* anything with them... so i got looking into my old s5 neo rom and saw that it was a 1 file version and wondered.... maybe i can make a 1 file version with a combination of the files i need/want, all into one custom tar.md5 and then maybe *that* will at least attempt a flash..... has anyone else tried this? or has already been thought about and failed?.... I only want that oreo rom with the marshmallow system image... is it really so impossible??
So glad I have an Appsung device... theyre locking their stuff down just as hardcore so... why not merge the names. Sampple is another option. heh.
Hello y'all.
I got this SM-A530F/DS, a galaxy A8 (2018), from a relative that got a problem. I am not sure about specifics, but it was never tampered with or rooted, I believe that things start to go bad after an unsuccesful OTA update. The phone does not boot, it just stays on samsung logo screen indefinetly, I can put the phone on download mode though so I think this is fixable by flashing the stock rom anew.
Now I got the stock firmware from sammobile and it seems good, but it is on a format for Odin, unfortunately I dont have access to a Windows computer, just Linux. So I got heimdall and read through whatever info I could find and I think I grok the fundamentals.
TLDR:
I have the following questions about the process:
1) Inside the stock files there is a .pit file that I assume is tailored to the stock ROM being distributed, should I use this .pit or should I use the one that I can extract from the phone with Heimdall?
2) The .img files seem to be lz4 compressed so should I first decompress those, or can I pass the compressed file to heimdall?
3) Inside the tar file for Odin {AP, BL, CP, CSC} there are a meta-data folder with a fota.zip file, does this file in any way influence heimdall flashing process?
p.s. I not sure if this should be moved to the device subforum as the questions mainly deal with the Samsung devices and heimdall in general and I could not find a Samsung sub forum to post this to
So I got the situation sorted.
1) The .pit file in the stock rom was the same as the phones, so I didnt have to do anything about that
2) The .img, .bin files must be decompressed first, not a great deal just had to 'lz4 -d' those
3) Those fota.zip didnt matter for heimdall, I just followed the phones .pit file to match partition names to partitions file and did a single 'heimdall flash' command