I pretty much give up on this, and it's not all that important, but it's bugging me.
How do you, or even CAN you, dump the radio/modem from this device? The best I've been able to do is scour the web and end up with a 512KB .bin file that essentially contains nothing but 0xFF bytes in it.
(If context is required, I'm learning how to make an ODIN image from a device ... and so far this is the only partition that's really killing me)
Just download one of the complete Odin tar files and use something like winrar to extract all the bin files from it.
Sent from my SCH-I500 using XDA Premium App
you cant dump the modem...its like the only thing that cant be....if making a full odin package, pack in one of our existing ones
nitsuj17 said:
you cant dump the modem...its like the only thing that cant be....if making a full odin package, pack in one of our existing ones
Click to expand...
Click to collapse
That's what I figured, since it seems to be something you can't do with the Epic either. Do we know if it's because of CDMA? Something that needs to be secured from dumping perhaps? Meh, doesn't matter
Thanks guys!
Related
Does anyone know where I can find a copy of this? I've done a search and all I can find is one from the international version and that's based on the 2.3.1 build.
TIA
check here http://forum.xda-developers.com/showthread.php?t=1286432
daraj said:
check here http://forum.xda-developers.com/showthread.php?t=1286432
Click to expand...
Click to collapse
Nothing there about stock system dump.
BigBolo said:
Does anyone know where I can find a copy of this? I've done a search and all I can find is one from the international version and that's based on the 2.3.1 build.
TIA
Click to expand...
Click to collapse
Entropy512 started with a stock system dump that someone, (maybe Jivy26), made after installing a custom kernel. But I don't remember he ever posted a link to it. He may still have it hanging around, though. That's what he used to make his stock plus root package.
BigBolo said:
Nothing there about stock system dump.
Click to expand...
Click to collapse
Um, what do you think a flashable stock system image is? (Other than being a sparse ext4 image, if you want something loop-mountable use simg2img...)
Seriously - spend just a LITTLE more time reading before you post in a Development thread. This device has been out for only 2 weeks so it's not like the Dev forum has tons of threads.
There's also a dd-derived system dump in page 5 of codeworkx's CWM kernel thread. I used jivy26's tar dump, although I should probably do a consistency check against seattleboi1982's dump.
Entropy512 said:
Um, what do you think a flashable stock system image is? (Other than being a sparse ext4 image, if you want something loop-mountable use simg2img...)
Seriously - spend just a LITTLE more time reading before you post in a Development thread. This device has been out for only 2 weeks so it's not like the Dev forum has tons of threads.
There's also a dd-derived system dump in page 5 of codeworkx's CWM kernel thread. I used jivy26's tar dump, although I should probably do a consistency check against seattleboi1982's dump.
Click to expand...
Click to collapse
I'm actually looking for the system dump in a zip where I can extract it into folders. Not as a image. I want to basically get the media files. I did do a search in several forums trying to find it but came up with nothing.
Maybe I should of been more detailed and specific in my OP.
BigBolo said:
I'm actually looking for the system dump in a zip where I can extract it into folders. Not as a image. I want to basically get the media files. I did do a search in several forums trying to find it but came up with nothing.
Click to expand...
Click to collapse
Can't you just extract the stock system image?
eep2378 said:
Can't you just extract the stock system image?
Click to expand...
Click to collapse
I don't know how to do that...
Then you probably don't belong in android development (yet).
Use 7zip to extract the zip/tar/whatever.
In general, you're not supposed to put requests in Development. This should have been posted in General.
And a stock system dump IS an image dump. Zip files don't preserve permissions, and tar files only do if you prepared them carefully (good thing jivy26 did). The only way to be sure is to dd the partition.
If you want a nice easy to use zip, use paylyhoffman's stock deodexed CWM zip.
Entropy512 said:
In general, you're not supposed to put requests in Development. This should have been posted in General.
And a stock system dump IS an image dump. Zip files don't preserve permissions, and tar files only do if you prepared them carefully (good thing jivy26 did). The only way to be sure is to dd the partition.
If you want a nice easy to use zip, use paylyhoffman's stock deodexed CWM zip.
Click to expand...
Click to collapse
Thanks for clearing it up. My bad I thought this was the section to post requests like that.
Also folks before jumping on the guy, what he is asking for (at least with the .7z file posted) isn't as straightforward as everyone thinks.
If you first extract the 7z file, you'll get a PDA.tar file. Extract that and you'll get the kernel (zImage) and the lovely factoryfs.img.
Try extracting factoryfs.img with your favorite tools and see what happens.
Extracting the factoryfs.img is a real pain unless you are pretty hardcore -- in fact, there was another thread going on the in international SGS II forum with some pretty well known devs (who know their stuff) trying to figure out how to extract that bad boy.
So before everyone starts throwing rocks...you know the story.
Does this look easy to you?
http://forum.xda-developers.com/showthread.php?t=1054836 (relevant discussion starts around post #7)
and another solution (which also is not as simple as "right-click and extract")
http://forum.xda-developers.com/showthread.php?t=1081239
Now -- with that said, if one was really looking for an easy way to pull some media files from a ROM, you best bet would be to try and find a CWM flashable ROM (in a zip format) and do a regular extract on those, and you may find it much easier. They may not be stock, but if it's close, you may get lucky and find some of the stock media in them.
pinoymutt said:
Also folks before jumping on the guy, what he is asking for (at least with the .7z file posted) isn't as straightforward as everyone thinks.
If you first extract the 7z file, you'll get a PDA.tar file. Extract that and you'll get the kernel (zImage) and the lovely factoryfs.img.
Try extracting factoryfs.img with your favorite tools and see what happens.
Extracting the factoryfs.img is a real pain unless you are pretty hardcore -- in fact, there was another thread going on the in international SGS II forum with some pretty well known devs (who know their stuff) trying to figure out how to extract that bad boy.
So before everyone starts throwing rocks...you know the story.
Does this look easy to you?
http://forum.xda-developers.com/showthread.php?t=1054836 (relevant discussion starts around post #7)
and another solution (which also is not as simple as "right-click and extract")
http://forum.xda-developers.com/showthread.php?t=1081239
Now -- with that said, if one was really looking for an easy way to pull some media files from a ROM, you best bet would be to try and find a CWM flashable ROM (in a zip format) and do a regular extract on those, and you may find it much easier. They may not be stock, but if it's close, you may get lucky and find some of the stock media in them.
Click to expand...
Click to collapse
Thanks for clarifying that pinoymutt. Yea basically I know a lot of people don't like the finished charging notification but I don't mind it and I figured it's as simple as just placing the ogg file back in the ui folder. I'm on DG's Cog X2 and he had removed that.
BigBolo said:
Thanks for clarifying that pinoymutt. Yea basically I know a lot of people don't like the finished charging notification but I don't mind it and I figured it's as simple as just placing the ogg file back in the ui folder. I'm on DG's Cog X2 and he had removed that.
Click to expand...
Click to collapse
Doubt it's that simple. I removed the notification by modifying code. I would bet dg did the same.
So I've pulled apart an SBF file, and I can see the contents inside, but I'm not seeing a boot.img or anything I can play with, trying to see about putting a different kernel into it. Anyone have any ideas? Figured I'd try my hand at it though it isn't going so well. Haha.
xTMFxOffshore said:
So I've pulled apart an SBF file, and I can see the contents inside, but I'm not seeing a boot.img or anything I can play with, trying to see about putting a different kernel into it. Anyone have any ideas? Figured I'd try my hand at it though it isn't going so well. Haha.
Click to expand...
Click to collapse
What are you using to dissemble it? I saw an app somewhere that would pull it appart, but not really into anything that is useful.
But they layout of the file should be well known since we have a linux version of rsd (sbf_flash)
That being said, it shouldn't be impossible to rip apart one and put it back together.
apparently sbf_flash supports a -x param which will extract the contents of the SBF.
Basically I am trying to change the kernel. And replace it. And I will let you know what the program is called next time I get on the comp.
Sent from my MB855 using XDA App
xTMFxOffshore said:
Basically I am trying to change the kernel. And replace it. And I will let you know what the program is called next time I get on the comp.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
The software is sbf depacker. The thing is you'd have to hex edit the kernel into the file. I think in the process of extracting you lose the headers rendering it useless after you repack it.
I can't seem to edit the files with said program. So I can't test it sadly.
Sent from my MB855 using XDA App
When you unpack the sbf files with unpacker, you will get a bunch of smg files. When you try to hex edit these smg files, you will lose the vital header info. So I don't know how you would be able to just write in a kernel, repack, and have it work. I have the files already unpacked if someone wants me to upload it, it's more than 2 gb though.
No worries Man. I have it unpacked too. The problem I have is I don't know how to edit the SMG files. You said hex edit, but I'm not totally certain how to do that. To be honest, I figured I'd try my hand at this for ****s and grins, but I'm not totally sure what I'm doing, so any input is appreciated.
I'm trying to edit some of the files in the ROM before flashing so I can have my defaults settings in place. I could do this just fine with EVO 4G ROM files, but when I try to open...say...build.prop, it says the archive is corrupt and that there are no files to extract. However, the ROM will flash onto my phone just fine.
Do I need a different version of WinRAR? Different program? Anyone else having that problem? Thanks for any answers.
Holyrolla said:
I'm trying to edit some of the files in the ROM before flashing so I can have my defaults settings in place. I could do this just fine with EVO 4G ROM files, but when I try to open...say...build.prop, it says the archive is corrupt and that there are no files to extract. However, the ROM will flash onto my phone just fine.
Do I need a different version of WinRAR? Different program? Anyone else having that problem? Thanks for any answers.
Click to expand...
Click to collapse
Update winRAR, or try 7zip. Redownload the file if you still get the error.
Maybe the ROM is signed that will keep you from making changes without extracting it first..
Id have to say use 7zip. Free app that's a 1000 x better for using when doing rom and theme building. IMO of course
Papa Smurf151 said:
Id have to say use 7zip. Free app that's a 1000 x better for using when doing rom and theme building. IMO of course
Click to expand...
Click to collapse
7zip does not care if the .zip is signed or not. Don't know if I would agree that its a 1000x better but thats just me. This is why I don't sign my ROMs anymore. Just encase someone wants to delete or add something before they flash.
zone23 said:
7zip does not care if the .zip is signed or not. Don't know if I would agree that its a 1000x better but thats just me. This is why I don't sign my ROMs anymore. Just encase someone wants to delete or add something before they flash.
Click to expand...
Click to collapse
It doesn't matter if a rom is signed or not. Its just a zip file. With 7zip u should be able to edit what ever you want. You won't be able to view any PNG files unless they are extracted but if you edit the rom or the apk it will usually break the signature which isn't a huge issue. You can always resign an apk or flash a rom without a signature. I can't stand win zip or winrar. They take forever and always have to extract crap. With 7zip its drag and drop and never an issue.
Thanks guys. I'll give 7-zip a try. That must mean that none of the EVO 4G roms I've ran (CM7 and MIUI) were ever signed...
Holyrolla said:
Thanks guys. I'll give 7-zip a try. That must mean that none of the EVO 4G roms I've ran (CM7 and MIUI) were ever signed...
Click to expand...
Click to collapse
Probably not most DEVs stopped signing ROMs a while ago.
What I'd like to do is to pull off all the files (keeping the structures intact) and either create an image file (.bin/.img) or something along those lines.
I know of DDMS and Android Commander, but I don't think they have the full power to get everything and I also understand the phone has to be rooted (which is not a big deal). Has anyone had any luck/expertise in this area?
If I can get this to work it then it would help out with some of the research that I am doing since it'll be easier to mount the image file in linux and go from there.
Alternate idea, does anyone know if when making a backup of the rom with CWM or BM does it hold the same type of data? If so where is the boot.img located?
Thanks for the help in advance!
I think there're a couple of threads in the development section regarding the images dumped from this phone.
sspa said:
I think there're a couple of threads in the development section regarding the images dumped from this phone.
Click to expand...
Click to collapse
Thanks I'll keep digging around to see what I can find.
Climber Ty said:
What I'd like to do is to pull off all the files (keeping the structures intact) and either create an image file (.bin/.img) or something along those lines.
I know of DDMS and Android Commander, but I don't think they have the full power to get everything and I also understand the phone has to be rooted (which is not a big deal). Has anyone had any luck/expertise in this area?
If I can get this to work it then it would help out with some of the research that I am doing since it'll be easier to mount the image file in linux and go from there.
Alternate idea, does anyone know if when making a backup of the rom with CWM or BM does it hold the same type of data? If so where is the boot.img located?
Thanks for the help in advance!
Click to expand...
Click to collapse
You can use an app called App2card at below for your need. It has the data tools for backing up any file/folder on any kind of storage (internal flash, fat32, ext2/3/4...) and ability to restore them in original structure as they were when backing up
http://205.196.123.32/fgqe9rc69leg/iln88jii0g81e05/App2Card_2.9.85_30Oct2011.apk
Sent from my MB860 using xda premium
Look for samcripps fruit cake maker it takes your /system folder and creates an. Img out of it.
Sounds like exactly what your after. Thank samcripp if it works for you too.
Sent from my MB860 using XDA App
I use android commander to pull system folder from phone.
Sent from my MB860 using XDA Premium App
stevendeb25 said:
I use android commander to pull system folder from phone.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Thanks, I tried that last night but the init.rc and other imortant files cannot be copied due to permissions access.
I eventually used CWM to make a backup of the phone and pulled the files that way. I just wonder if it has all the files on the phone (haven't had time to root through it yet)?
Climber Ty said:
Thanks, I tried that last night but the init.rc and other imortant files cannot be copied due to permissions access.
I eventually used CWM to make a backup of the phone and pulled the files that way. I just wonder if it has all the files on the phone (haven't had time to root through it yet)?
Click to expand...
Click to collapse
I think you can post your question in RomRacer's recovery thread; it's in dev section
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
waldojim said:
Ok, this may be answered elsewhere, I don't know. "Search is temporarily unavailable" I am trying to understand how I am supposed to work with the backup from CWM. I understand that I should have a System image that I can work in, but what I have is 3 files in its place. System.ext4.tar, System.ext4.tar.a, and System.ext4.tar.b. All three files are broken to some degree.
System.ext4.tar is a zero byte file.
System.ext4.tar.a appears to be a spanned tar file that 7ZIP/WinRAR simply think was cut-off (never asks for the second file, and complains of unexpected End of Archive)
System.ext.4.tar.b appears to be the second part of the archive, but nothing will open it.
So, how do I get to a point I have a complete archive that I can edit? Or do I need to use different software than CWM to back up the phone?
Thanks for the help guys.
Click to expand...
Click to collapse
Well, I found a solution for now. Fire up Linux, use cat to combine all three files, then use tar to extract the contents. Not sure why this needed split in the first place, but at least the files can be extracted.
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
waldojim said:
I have managed to remove the APKs I do not want, and made a new system.ext4.tar file (all in Linux), but need to know what else I have to do to make the system image usable.
I found several guides on making a ZIP file, but I didn't want to necessarily go through all that. I backed up everything, so what I would like to know, is what all needs to change so that I can use the separate files as they are, and simply do a CWM "restore" function?
I know I sound like a complete noob at this point, and will deal with the related comments. However, please understand, I don't want the heavily modified rom packs. I simply wanted a rom VOID of all the Verizon bloatware, and have the Verizon tethering restraints removed. I have them all disabled now, and 3rd party tethering is working quite well. So I would rather not have that garbage wasting space. Right now, it looks like I may save 250MB or so.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
Backups really aren't meant to be unzipped and played with. Usually bloat removal is done while booted into the system or you can unpackage a Rom and remove the bloat there and then repackage it and flash it then make your backup that doesn't contain any bloat. Using the xda kitchen tools from dsxda I believe is the name
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
waldojim said:
I think this is where some of my confusion comes from - it was never zipped. There was a group of tarred files, an MD5sum and a few other items. But nothing there was zipped.
Click to expand...
Click to collapse
I guess what I meant to say by "zipped" was just in general they are compressed by the recovery in a way that it knows how to go and use them to restore data to the device.