Related
So Mike has posted deodexed stock ICS roms for both sensation and sensation xe, a long time ago in the dev section, but not for sensation 4G .
I am looking for such a rom (deodexed stock ICS) that works for sensation 4G as well.
I am sure a lot of other ppl would also be happy to have this
Here you go man, just what you requested.
T-Macgnolia said:
Here you go man, just what you requested.
Click to expand...
Click to collapse
Thanks a lot!
Im on the exact same ROM but odexed, do you think flashing this in recovery would flash my dada (i.e. erase everything)?
alireza_simkesh said:
Thanks a lot!
Im on the exact same ROM but odexed, do you think flashing this in recovery would flash my dada (i.e. erase everything)?
Click to expand...
Click to collapse
You will have to look in the updater-script in META-INF/com/google/android. If the updater-script has thecommands to erase and format data then yes it will. But if it does not it will not remove your data.
T-Macgnolia said:
You will have to look in the updater-script in META-INF/com/google/android. If the updater-script has thecommands to erase and format data then yes it will. But if it does not it will not remove your data.
Click to expand...
Click to collapse
Thanks!
Can you pls tell me where the META file is again? i extracted rom.zip from RUU but there is no folders inside rom.zip, just image files....
alireza_simkesh said:
Thanks!
Can you pls tell me where the META file is again? i extracted rom.zip from RUU but there is no folders inside rom.zip, just image files....
Click to expand...
Click to collapse
If you extracted the Rom.zip from the RUU then if I remember right that is just the system.img in the zip or the system.img and boot.img in it. You will have to put the Rom.zip in a kitchen and let the kitchen convert the system.img into a system folder and also let it generate the META-INF folder. Or just place the boot.img with a META-INF from a Sense ROM an then package the three into a zip. The META-INF is in the zip file you download for a ROM or the zip file the kitchen makes when you build the ROM.
T-Macgnolia said:
If you extracted the Rom.zip from the RUU then if I remember right that is just the system.img in the zip or the system.img and boot.img in it. You will have to put the Rom.zip in a kitchen and let the kitchen convert the system.img into a system folder and also let it generate the META-INF folder. Or just place the boot.img with a META-INF from a Sense ROM an then package the three into a zip. The META-INF is in the zip file you download for a ROM or the zip file the kitchen makes when you build the ROM.
Click to expand...
Click to collapse
OK so installed your stock ICS deodexed rom, then i restored my Data from Nandroid backup that i made earlier, but now the rom is odexed again....I didnt restore the System (just Data)...is there anything else that i can do?!
alireza_simkesh said:
OK so installed your stock ICS deodexed rom, then i restored my Data from Nandroid backup that i made earlier, but now the rom is odexed again....I didnt restore the System (just Data)...is there anything else that i can do?!
Click to expand...
Click to collapse
any thought?...
Hey guys,I am a starter in Galaxy Fit development(sry to be noobish).I used a stock 2.3.6 dxkt7 rom and built a custom rom without any changes to the apks or anyother things even the bootanimation but when i try to install the rom i get status 0 error.I read what a status 0 error is but not able to rectify it can someone pls help.Thanks in advance
hmm..
yeshwanthvshenoy said:
Hey guys,I am a starter in Galaxy Fit development(sry to be noobish).I used a stock 2.3.6 dxkt7 rom and built a custom rom without any changes to the apks or anyother things even the bootanimation but when i try to install the rom i get status 0 error.I read what a status 0 error is but not able to rectify it can someone pls help.Thanks in advance
Click to expand...
Click to collapse
hmm.. have you changed something in the Uppdate-Binary?
Use this recovery. Still facing problem then copy meta-inf folder from any custom rom for fit
FurFur_ said:
hmm.. have you changed something in the Uppdate-Binary?
Click to expand...
Click to collapse
no didnt make any changes to anything just extracted system.rfs and boot.img using kitchen made the system and boot.img files and added superuser and bulit the rom thatz all the edits i did
MajinSaiyan4 said:
Use this recovery. Still facing problem then copy meta-inf folder from any custom rom for fit
Click to expand...
Click to collapse
yes this ver of cwm only am using too :cyclops: yes and i tried meta inf of others but that aso not working(used razordroid,jana rom,hyperdroid,creed's rom-meta inf files)....others meta infs wont work bcoz the stock works on ext4 i think :crying:
can anyone give the updater-script of a stock rom that has root function only pls
do this zip aliign evertyhing add busybox via kitche(deodex if you want to)
then copy all the files from working folder to folder x
pick up meta inf and boot.img from any custom rom and copy it to folder x zip it via winzip or any other soft and flash the zip ....
speed_bot said:
do this zip aliign evertyhing add busybox via kitche(deodex if you want to)
then copy all the files from working folder to folder x
pick up meta inf and boot.img from any custom rom and copy it to folder x zip it via winzip or any other soft and flash the zip ....
Click to expand...
Click to collapse
Thank u mate it works now.The update-binary file was corrupted that is why it didnt install.Thanks a ton
FurFur_ said:
hmm.. have you changed something in the Uppdate-Binary?
Click to expand...
Click to collapse
The android kitchen auto generated a update-binary that did not match my mobile that was why i encoutered this issue thanks a lot mate
thats because kitchen converst update script into edify and other crap
[TUT] How to extract .ftf file to make custom rom - Flashable ZIP [2012 Xperia]
This tutorial is for developers who want to make their own custom rom based on official firmware. OK, let's start.
Explanations:
Inside every flashable zip file there are two folders - system and META-INF:
1) system folder - That is actually your ROM and all it's content (If you ROOT your device you gain access to this folder in your device).
2) META-INF folder - That folder gives instructions to your device (ClockWorkMod) how to flash ROM, sets permissions...
This is method to get Stock/Official system folder that you need to edit to make custom ROM.
You will need to find/make yourself contents of META-INF folder - You may took it from another ROM and (maybe) edit.
NOTE: If you use this method your ROM will work for both Locked/Unlocked bootloaders, and it will require that you have firmware your ROM is based on already installed before flashing.
Click to expand...
Click to collapse
How to get contents of stock/official system folder - Extract .ftf file:
1. Download .ftf file for your device.
2. Extract .ftf file using 7Zip.
3. You will get system.sin and other files. You only need system.sin file so delete others.
4. Open flashtool and inside flashtool open SIN Editor to dump data from system.sin - you will get an ext4 file.
5. Open ext2Read and extract ext4 file.
6. Done.
Click to expand...
Click to collapse
How to put CWM into your ROM:
OK, Now you ask - Why do I have to put CWM into ROM? Let's explain:
CWM is custom recovery that you use to flash zip files to your device. There are two types of CWM:
1. For both Locked and Unlocked bootloaders - Recovery is in the system folder of the ROM.
2. Only for Unlocked bootloaders - Recovery is somewhhere else (You don't need that).
Because your ROM is based on official firmware it will be for both Locked/Unlocked bootloaders.
Therefore, you will flash your ROM in CWM for both Locked/Unlocked bootloaders.
And if you flash you will replace system folder of previous ROM. Because CWM was in that folder of previous ROM - You will lose CWM.
That is why you need to put CWM.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Find CWM for both bootloaders for your device.
1. Copy sh file inside files folder to system/xbin.
2. Copy other files inside files folder to system/bin.
3. Go to META-INF/com/google/android/ and you will find updater-script.
4. Add the following lines to it
Code:
set_perm(0, 0, 0755, "/system/bin/recovery.tar");
set_perm(0, 0, 0755, "/system/bin/battery_charging");
set_perm(0, 0, 0755, "/system/bin/battery_charging_help");
set_perm(0, 0, 0755, "/system/xbin/sh");
Thanks srl3gx for tutorial.
Click to expand...
Click to collapse
How to add ROOT into your ROM:
Want your custom rom to be rooted? Here is how:
1. First you need to choose from two great root management apps: Superuser (choose ARM one) and SuperSU(I prefer SuperSU).
2. Download zip file.
3. Go to "system" folder in downloaded zip and copy files within their folders to its place in your rom (same directory - if was "app" then copy in "app".
4. Edit updater-script to set correct permissions - Find that on someone elses rom, it should look just like for CWM, but for those files.
5. Done.
Click to expand...
Click to collapse
Useful notes:
1. Don't edit any file in zip with Windows Notepad or else you will get an error in CWM - you need Notepad++.
2. When you put system and META-INF folders into zip set compression to - Store.
Click to expand...
Click to collapse
thanks.....
very helpful :good:
Option58 said:
[TUT] How to extract .ftf file to make custom rom - flashable ZIP [2012 Xperia]
This tutorial is for developers who want to make their own custom rom based on official firmware. Note that as of 2012 our Xperias use ext4 file system so other tutorials won't work.
Inside every flashable zip file there are two folders - system and META-INF...System folder is ROM content...and META-INF gives instructions to CWM how to flash ROM Content....This is method to get contents of SYSTEM folder, you must find META-INF yourself....
1. Download .ftf file for your device.
2. Extract .ftf file using 7Zip.
3. You will get system.sin and other files..You only need system.sin file so delete others...
4. Open flashtool and inside flashtool open SIN Editor to dump data from system.sin - you will get an ext4 file.
5. Open ext2Read and extract ext4 file...
6. Done...you will get contents of system folder that you need to modify...
7. IMPORTANT - When you later make zip choose compression - Store
PS: Don't edit files with Windows Notepad or else you will get an error in CWM - you need Notepad++...
Maybe later I will make Screenshots
Click to expand...
Click to collapse
any idea on how I can edit boot.img? the one used for this device are different from what I know.. I am trying dual boot..
you can pack and repack boot img with Android kitchen i think
Great tut
Sent from my Xperia Tipo using xda app-developers app pro
I already knew this method. However I congratulate you for your initiative. :highfive:
Well I learned something else. Before it only used to extract some files. I did not know we could do this way the custom roms.
I'll try to make a custom rom.
However verified that the file size of system.ext4 is 665,654 KB. Once extracted using ext2read, is only 467 MB.
It is normal for this situation? Instead of decreasing, should not increase after extracted?
Kind regards,
Jorge Moreira
drummer1839 said:
you can pack and repack boot img with Android kitchen i think
Click to expand...
Click to collapse
nope.. you cant.. It says android magic header not found. researching a bit, found out that this is a cpio archive.. I did manage to extract it to get 2 .gz files.. but they cannot be opened..
Jorge Moreira said:
I already knew this method. However I congratulate you for your initiative. :highfive:
Well I learned something else. Before it only used to extract some files. I did not know we could do this way the custom roms.
I'll try to make a custom rom.
However verified that the file size of system.ext4 is 665,654 KB. Once extracted using ext2read, is only 467 MB.
It is normal for this situation? Instead of decreasing, should not increase after extracted?
Kind regards,
Jorge Moreira
Click to expand...
Click to collapse
That was my problem too I ended up with an ext2read error and less size
But ext4 is Linux system partition and not zip file. Maybe flashtool made partition that big so every file could go there easily and it couldn't set exact size.
There is no other tool on internet, only ext2read.
Option58 said:
That was my problem too I ended up with an ext2read error and less size
But ext4 is Linux system partition and not zip file. Maybe flashtool made partition that big so every file could go there easily and it couldn't set exact size.
There is no other tool on internet, only ext2read.
Click to expand...
Click to collapse
Anyway I will try this weekend, make a custom rom lighter and functional.
Kind regards,
Jorge Moreira
Jorge Moreira said:
Anyway I will try this weekend, make a custom rom lighter and functional.
Kind regards,
Jorge Moreira
Click to expand...
Click to collapse
OK, don't forget to add CWM and root into your ROM. Actually I will rewrite my post in few days.
OK, the tutorial is rewritten. But it is not done. I will finish the rest later.
i did these steps[even without adding CWM ,just making a flashable stock rom(not included cwm) from cwm] ,but while want to install zip (my custome rom) from recovery ,installation after 2 seconds facing with error("installation aborted")
what is it's reason?
thanks
Jamal_RS said:
i did these steps[even without adding CWM ,just making a flashable stock rom(not included cwm) from cwm] ,but while want to install zip (my custome rom) from recovery ,installation after 2 seconds facing with error("installation aborted")
what is it's reason?
thanks
Click to expand...
Click to collapse
There's some error in updater script, upload it...
Have you edited with notepad or Notepad ++
Option58 said:
There's some error in updater script, upload it...
Have you edited with notepad or Notepad ++
Click to expand...
Click to collapse
i didn't edit updater script
Jamal_RS said:
i didn't edit updater script
Click to expand...
Click to collapse
And you took it from who?
Option58 said:
And you took it from who?
Click to expand...
Click to collapse
oh understood!!
i want to combine your tutorial and this thread
to make a rooted and included cwm custom rom
so i used from "META-INF folder and ROOTING files" that presented on that thread
i think this is my fault!
is it right?
thanks
Jamal_RS said:
oh understood!!
i want to combine your tutorial and this thread
to make a rooted and included cwm custom rom
so i used from "META-INF folder and ROOTING files" that presented on that thread
i think this is my fault!
is it right?
thanks
Click to expand...
Click to collapse
I understand now.
First that zip should only make use to you to learn a little bit more about development. To install that you need already to be rooted with CWM installed.
Second it doesn't install because our devices use a little bit different things. Edit and change every MTD to EMMC and every yaffs (or similar) to ext4. (Notepad ++)
I have only one recovery, from this thread : http://forum.xda-developers.com/showthread.php?t=2034639
Where I need to put it? in zip file or in system folder?
lozohcum said:
I have only one recovery, from this thread : http://forum.xda-developers.com/showthread.php?t=2034639
Where I need to put it? in zip file or in system folder?
Click to expand...
Click to collapse
Read my tut again, that recovery wont do the job.
Does anybody want help me about the new project. Extract ftf. Look at Q&A section.
I read it several times and still can't get it. So please explain. And can You reupload flashtool?
So I am running CROMI and I want to try some different boot animations. I found a few of them embedded in the ROM zip as zip files themselves. Can I just extract these to a directory and install the directly through TWRP? If not, are there any custom boot animation out there that can be flashed?
Thanks
Jeff
gixxer340 said:
So I am running CROMI and I want to try some different boot animations. I found a few of them embedded in the ROM zip as zip files themselves. Can I just extract these to a directory and install the directly through TWRP?
Click to expand...
Click to collapse
Even easier, just copy the bootanimation.zip you want into /data/local.
_that said:
Even easier, just copy the bootanimation.zip you want into /data/local.
Click to expand...
Click to collapse
Thanks very much for the tip
Jeff
gixxer340 said:
So I am running CROMI and I want to try some different boot animations. I found a few of them embedded in the ROM zip as zip files themselves. Can I just extract these to a directory and install the directly through TWRP? If not, are there any custom boot animation out there that can be flashed?
Click to expand...
Click to collapse
Try the ROM Toolbox Lite app. You need your phone to be rooted (a custom ROM will have your phone already rooted for you), and this app makes it a breeze to install a new boot animation. The app has a collection of boot animations ready to install, or you can make your own and use this app to install it.
Hi,
I have tried developing a Lollipop rom using CM 12, but after the build it didn'd form a .zip file but i have got system.img, userdata.img, ramdisk.img, recovery folder and others. Then later i have created the zip file by creating boot.img, update-script and signed it.
The problem is why it didn't create a zip file and boot.img by itself (I have given the kernel path in boardconfig.mk and I'm using Java 1.7). When I tried to install my rom, it got installed (I used aroma installer) and I was able to see the files copying into the memory, but when I rebooted, "SAMSUNG" image displayed and it started rebooting again and again. Whats the problem and how to correct these.
Someone help me out, so that I can bring out a ROM with the new Lollipop version.
Thank you
I wish I could help...but I dont have any experiane in developing ROM's:crying:
all developers are busy in making their Roms...
they should collaborate on the real thing....
Vignesh Prasad said:
Hi,
I have tried developing a Lollipop rom using CM 12, but after the build it didn'd form a .zip file but i have got system.img, userdata.img, ramdisk.img, recovery folder and others. Then later i have created the zip file by creating boot.img, update-script and signed it.
The problem is why it didn't create a zip file and boot.img by itself (I have given the kernel path in boardconfig.mk and I'm using Java 1.7). When I tried to install my rom, it got installed (I used aroma installer) and I was able to see the files copying into the memory, but when I rebooted, "SAMSUNG" image displayed and it started rebooting again and again. Whats the problem and how to correct these.
Someone help me out, so that I can bring out a ROM with the new Lollipop version.
Thank you
Click to expand...
Click to collapse
can i look at your device/kernel tree?
please I want one thing
I want please Android (5. 0) for Samsung galaxy core prime
any updatets regarding this roam
Any Updates?
Vignesh Prasad said:
Hi,
I have tried developing a Lollipop rom using CM 12, but after the build it didn'd form a .zip file but i have got system.img, userdata.img, ramdisk.img, recovery folder and others. Then later i have created the zip file by creating boot.img, update-script and signed it.
The problem is why it didn't create a zip file and boot.img by itself (I have given the kernel path in boardconfig.mk and I'm using Java 1.7). When I tried to install my rom, it got installed (I used aroma installer) and I was able to see the files copying into the memory, but when I rebooted, "SAMSUNG" image displayed and it started rebooting again and again. Whats the problem and how to correct these.
Someone help me out, so that I can bring out a ROM with the new Lollipop version.
Thank you
Click to expand...
Click to collapse
Any progress?
Vignesh Prasad said:
Hi,
I have tried developing a Lollipop rom using CM 12, but after the build it didn'd form a .zip file but i have got system.img, userdata.img, ramdisk.img, recovery folder and others. Then later i have created the zip file by creating boot.img, update-script and signed it.
The problem is why it didn't create a zip file and boot.img by itself (I have given the kernel path in boardconfig.mk and I'm using Java 1.7). When I tried to install my rom, it got installed (I used aroma installer) and I was able to see the files copying into the memory, but when I rebooted, "SAMSUNG" image displayed and it started rebooting again and again. Whats the problem and how to correct these.
Someone help me out, so that I can bring out a ROM with the new Lollipop version.
Thank you
Click to expand...
Click to collapse
please help him ....anybody so we can have rom for our PHONE.....
I'm working on the prime for verizon. If you open BoardConfig.mk there are a few lines to change. I'm not sure what yours will look like but one of them is the TARGET_BOARD_PLATFORM line. You also need to check the locations and block sizes for the partitions. Should work then. I'm still working on mine so don't quote me.