If I down load a rom and open the zip file can i just goto system/apps and delete and install .apks and then flash that rom? I was wondering so i don't have to delete them after install.
Neo31697 said:
If I down load a rom and open the zip file can i just goto system/apps and delete and install .apks and then flash that rom? I was wondering so i don't have to delete them after install.
Click to expand...
Click to collapse
Depends on what your deleting and adding, if your just deleting and adding apks to the system/app dir you should be ok (normally) . If you want it to stay as an update type zip it'll need to be resigned.
Neo31697 said:
If I down load a rom and open the zip file can i just goto system/apps and delete and install .apks and then flash that rom? I was wondering so i don't have to delete them after install.
Click to expand...
Click to collapse
U can Add and delete what u like but if u do u have to resign the rom before u can flash it.
If u download avabox2 (can be found on xda via a search...its free) it has a folder in there called autosign. Put the rom in there rename it update the click on the sign file. It will sign it for u automatically. Then u can rename the signed rom whatever u like. Just no spaces in the name. Then it can be reflashed.
sweet thanks. Just thinking about starting to make my own roms and this seemed like a good place to start
Neo31697 said:
sweet thanks. Just thinking about starting to make my own roms and this seemed like a good place to start
Click to expand...
Click to collapse
Some tools for you to get started:
For People Willing To Learn
Everything Android
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Rycon33 said:
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Click to expand...
Click to collapse
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
gregbradley said:
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
Click to expand...
Click to collapse
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Rycon33 said:
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Click to expand...
Click to collapse
wait, let me boot into linux and I will check
gregbradley said:
wait, let me boot into linux and I will check
Click to expand...
Click to collapse
mate, btw I'm only using cygwin in win7 if that matters on my issue
Rycon33 said:
mate, btw I'm only using cygwin in win7 if that matters on my issue
Click to expand...
Click to collapse
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
gregbradley said:
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
Click to expand...
Click to collapse
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
gregbradley said:
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
Click to expand...
Click to collapse
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Rycon33 said:
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Click to expand...
Click to collapse
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
gregbradley said:
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
Click to expand...
Click to collapse
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Rycon33 said:
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Click to expand...
Click to collapse
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
gregbradley said:
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Click to expand...
Click to collapse
asterix005 said:
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
ok mates, thank you very much, I managed to de-odexed my stock ROM:good:
This is what I did. Using flashtool, I dumped my system.sin file to get a ext4 file. Then I open it with ext4 reader and extracted the contents. I then placed it in a folder called 'system' and proceed with the android kitchen.
Humans have evolved to be smarter, but there's one thing we can't get rid off. It's human stupidity.
If you still want to deodex playstationcertified.odex rename it to com.playstation.playstationcertified.odex.
That did the trick for me in earlier firmware versions.
Sent from my phone using XDA Premium
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
lucky92 said:
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
Click to expand...
Click to collapse
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
gregbradley said:
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
Click to expand...
Click to collapse
i tried extract thee system.sin into ext4 and rename it to sysmtem.img but no luck
update: after re-dump system.sin and press countinue, it's seem ok, maybe my fault.
Thank you anyway :laugh:
Sorry but I have another question, after i make a flashable zip and flash through CWM, it always stuck at Sony logo, any idea ?
I am a complete noob in phones and androids and crap.
I'm not sure what on earth this thing is, it is a .7z file and has a folder called system.
It has all the files in the system folder and even as build.prop.
Does anyone know what a .7z file is and what can I do with the file in it.
And also I'm not sure what a deodex is...
Do I copy and replace the whole system file in my xperia SP?
I got it off here: (First post, highlighted with (NEW!)
http://forum.xda-developers.com/showthread.php?t=2452139
Link to the .7z file that I'm curious with:
https://docs.google.com/file/d/0ByYxifSPiyiMVGNqZmsydWpJVFE/edit
nobu1106 said:
I am a complete noob in phones and androids and crap.
I'm not sure what on earth this thing is, it is a .7z file and has a folder called system.
It has all the files in the system folder and even as build.prop.
Does anyone know what a .7z file is and what can I do with the file in it.
And also I'm not sure what a deodex is...
Do I copy and replace the whole system file in my xperia SP?
I got it off here: (First post, highlighted with (NEW!)
http://forum.xda-developers.com/showthread.php?t=2452139
Link to the .7z file that I'm curious with:
https://docs.google.com/file/d/0ByYxifSPiyiMVGNqZmsydWpJVFE/edit
Click to expand...
Click to collapse
odex file means the system keep in a bundle... it does not allow adv custamization.. some mod flash need deoxed yr system first or u maybe end up in bootloop... u need to deodex yr firmware before flashing the file... check the android development for proper guide...
the file u posted does not need to deodex... but it always a good things to deodex first... cheers :laugh:
flash the bootanimation(720x1280).zip one... i think that one for our xsp
Need the update center apk. I downloaded one from here, But nor work, copied into system/app and with proper permisions But no icon, cant install. Can someone please upload other apk. For 257 firmware to test. Múltiple apk very apreciated, to test.
Cleviojr said:
idk what you want but, you can search FTF something like that, hope i helped
Click to expand...
Click to collapse
i accidentally deleted the original apk, tried reinstalling ftf, and the apk is not restored, i for that i need manually copy the apk into system/apps.
fjoel said:
i accidentally deleted the original apk, tried reinstalling ftf, and the apk is not restored, i for that i need manually copy the apk into system/apps.
Click to expand...
Click to collapse
or a help to extract the apk myself from firmware ftf 257.
Please, help!
Hello guys!
I'm a developing the AOXP ROM for our lovely Z3Cs. But I do not know how to deodex the stock rom.
Can I deodex the prerooted firmware zip created with PRFCreator??? It is based on the latest .291 firmware.
If any of you experienced developers can help me I would be grateful!
Thank you!
If you need any new information, I will add it to this post.
Deodexer for Pc running Windows Os.
You have to install lastest .Net Framework and Java too.
I dont know how to repack the system.ext4 partition into prerooted.zip, but i know how to deodex this partition.
6.0.1 rom .291:
Copy /framework, /app, /priv-app, build.prop, odex.framework.sqsh, odex.app.sqsh, odex.priv-apk.sqsh from /system to /*Work space* folder, use lastest 7zip to extract .sqsh files, then copy all .odex files to /apk/*apk name*/oat. make sure correct .apk and .odex name.
then running SVAdeodexer, choose /*Work space* folder and check /apk, /priv-apk, /framework to deodex.
all deodexed apps will be placed in /SVAdeodexer folder (the folder containing deodexer app)
*** app file (.apk) from /framework wont be deodexed, u should copy that app to /apk, after deodexed, copy that app back to /framework.
then delete /framework, /app, /priv-app, odex.framework.sqsh, odex.app.sqsh, odex.priv-app.sqsh, /odex.framework, /odex.app, /odex.priv-app from system.ext4 partiotion and copy /framework, /app, /priv-app deodexed back to system.ext4
xtbtvd12399 said:
Deodexer for Pc running Windows Os
You have to install lastest .Net Framework and Java too.
Click to expand...
Click to collapse
Thank you so much for replying... Will this work with sony roms? I mean, the structure of sony roms is different(system.sin etc) ???
panzerox123 said:
Thank you so much for replying... Will this work with sony roms? I mean, the structure of sony roms is different(system.sin etc) ???
Click to expand...
Click to collapse
you can use Flashtool converting sytem.sin into system.ext4
xtbtvd12399 said:
you can use Flashtool converting sytem.sin into system.ext4
Click to expand...
Click to collapse
But can I convert it back to system.sin after that?
panzerox123 said:
But can I convert it back to system.sin after that?
Click to expand...
Click to collapse
I never try it before. May not...
xtbtvd12399 said:
I never try it before. May not...
Click to expand...
Click to collapse
Hmmm... I'll try using Slimm Roms files, with permission ofcourse
panzerox123 said:
Hmmm... I'll try using Slimm Roms files, with permission ofcourse
Click to expand...
Click to collapse
Slimm Rom contain a system.ext4 file, isnt a .sin file
xtbtvd12399 said:
Slimm Rom contain a system.ext4 file, isnt a .sin file
Click to expand...
Click to collapse
Oh wait! I remember now...
Can I convert it back to a system.ext4 file after altering.. not system.sin.... :good:
panzerox123 said:
Oh wait! I remember now...
Can I convert it back to a system.ext4 file after altering.. not system.sin.... :good:
Click to expand...
Click to collapse
Try this. Required Cygwin (emulate Linux on Windows)