I am interested to know what tools are available to do a "diff" ( http://unixhelp.ed.ac.uk/CGI/man-cgi?diff ) between ROMs in Android and, if possible, even against the a nandorid backup or some other method to get the file on the phone.
I expect that it would be possible to to extract the content of the ROM on two different folder and then running a opendiff or some other tools (ex: http://meldmerge.org/ ) on the two folder.
I am trying to see what executable and what script changed between a stock ROM and what I have currently running on my phone or other ROMs available here.
Thank you in advance!
Related
Hey Guys,
I'm in need of some really n00b friendly advice.
When you flash a new ROM (i.e. CM9) in CWM the tutorials tell you to flash the file named Update.zip. My problem is that I can't seem to find one in the zip file I downloaded for my xperia mini.
I downloaded FXP131, and found the zip file to contain a boot.img, which will be the kernel. And 2 other folders named META-INF and System.
I know how to flash the kernel and expect it was just left in there for easy transportation.
But where in the world is 'update.zip'?
Am I meant to unpackage the kernel then re-zip the META-INF and System folder and then call that 'Update.zip'?
I've flashed roms for some of my other devices before, but they've always used flashtool or samsungs flashtool.
Please help me guys, I don't like sounding this inexperienced
update.zip
I'm wondering if the ROM I am trying to flash needs to be renamed as update.zip in order to work. It is krook's v.6 of JB for the Lenovo K1 tablet. Since the download site has to distinguish between wifi and 3G versions, as well as nvflash versions there are a number of different filenames, however does it need to be renamed after putting it on my SD card?
Generally speaking "update.zip" is used as a generic name. For example the update.zip I just flashed is actually named "rascarlo_maguro_ota_2012-11-01.zip". When you flash a custom ROM in a custom recovery you should be able to browse & flash whichever file you need.
The FXP131.zip file that contains the boot.img and 2 other folders named META-INF and System is the "update.zip"
solved
My problem was an incomplete download. I compared file sizes, and checked md5sums and determined the correct ROM and it is now in the middle of finishing the upgrade/optimization process.
Thx
I am interested to know what tools are available to do a "diff" between ROMs and, if possible, even against the a nandorid backup or some other method to get the file on the phone.
I expect that it would be possible to to extract the content of the ROM on two different folder and then running a opendiff or some other tools on the two folder.
I am trying to see what executable and what script changed between a stock ROM and what I have currently running on my phone or other ROMs available here.
Thank you in advance!
Hello everyone.
Guys, I am interested in turn the stock rom of my phone in a ready-to-install rom. I mean, roms usually are .zip files with scripts that writes the customized files to the system file, overwriting the old files. I want to know how to take the stock rom of my phone and turn it in a intallable .zip file, like a customized rom.
After a normal installing the phone would be like the phone with the original rom, without changes. Do you know what I mean?
I am interested in this for make changes and costumizations in the stock rom for then reinstall it. Normally, rom porting is made by taking a compatible rom (like CM) and taking the wished to port rom and changing directories like /system, /data, etc... Am I right? Well, if a would take the original rom of my phone and would turn it in a installable .zip, I could make ports, right?
Well, this is my doubt, how can I do this?
Up.
What's wrong? No one cares about?
Noob reporting here !
You can start by installing ADB (from android sdk).
When you have ADB correctly installed , you can "rip" your phone's complete /system partition by using the "adb pull /system system/" command.
This will rip /system to a subfolder called "system" (example c:/adb/adb.exe -> c:/adb/system)
I haven't come further myself, as i`m also in the learning (reading) phase.
you can use dsixda's kitchen for that, just use a firmware file for your phone, and extract that using the kitchen, after that you can use it to make a zip file
Good evening,
I've written a module for my smartphone and I need to compose a rom to install on my device...
I followed some tutorials, so now I know how to build an android kernel, obtaining a zImage.
Now, a friend told me that I must make a backup with clockworkmod (done!) and download on my pc, than I can recover the boot.img from there and split them in ramdisk and kernel.
Now I can compile my new kernel and merge it (the obtained zImage?) with the ramdisk to have a new rom to flash on my device... is true?
But I don't know how I can split the boot.img (maybe with dsixda kitchen?) and how to create the new rom. I tryied som weeks ago with a .zip rom and the dsixda kitchen and I split and recomposed a rom, but files contained in the .zip files was different from files that I downloaded by my device...
Someone can explain me the correct way to do this process? Thank you!
Paolo.dev said:
Good evening,
I've written a module for my smartphone and I need to compose a rom to install on my device...
I followed some tutorials, so now I know how to build an android kernel, obtaining a zImage.
Now, a friend told me that I must make a backup with clockworkmod (done!) and download on my pc, than I can recover the boot.img from there and split them in ramdisk and kernel.
Now I can compile my new kernel and merge it (the obtained zImage?) with the ramdisk to have a new rom to flash on my device... is true?
But I don't know how I can split the boot.img (maybe with dsixda kitchen?) and how to create the new rom. I tryied som weeks ago with a .zip rom and the dsixda kitchen and I split and recomposed a rom, but files contained in the .zip files was different from files that I downloaded by my device...
Someone can explain me the correct way to do this process? Thank you!
Click to expand...
Click to collapse
So many u can use
1. http://forum.xda-developers.com/showthread.php?t=1619473
2. http://forum.xda-developers.com/showthread.php?t=2036528
3. http://forum.xda-developers.com/showthread.php?t=1877807
and many more if u search
Hey all,
So I downloaded hexagon OS for mt6580 and LineaseOS13 for mt6580.. of course installing them gives me a bootlop since they are not ported for the K-touch i10... so I followed a guide to replace the files in those custom roms with the required ones from the stock rom to get them to work. zipped them up, put the zip on the phone, and twrp gives me the "invalid zip file" error when trying to flash them...
help?
@SaucemanBangorang
Isn't the error message "Invalid Zip File Format"?
0
Seppppx said:
1. You used the wrong compression method (most likely.)
You need to set the compression method to "store"
2. Don't port ROMs. Build them from source as they were intended to be. It is much easier to build them than port.
Click to expand...
Click to collapse
Thanks for replying.
I did something dumber, when it zipped, it put the files into a folder, hence the error, re-zipped so it wouldn't do that, and it installed, but the roms of course don't work despite porting them.
2. Building the rom from source sounds way beyond me. Porting meant coping files from the stock rom to the custom rom.. is building a rom easier than that? I actually hate this iteration of the i10 I was given, since it is actually weaker and less functional than my i9.. so I just wanted to see if a better rom would at least make it a usable phone.. I already spent hours flashing and rooting just to get past the stupid trojans/spyware that were installed on the phone.. irritates me that I would have to spend even more time building a rom for it.. especially when it's not a popular phone and said no rom would be of no use to anyone.