Database Users

[UPDATE 22/08/12] ROM Cooking Guide (One Package)

This is how I made ROM, I'll try to write the steps as simple as I can. For advanced users only!
Update 22/08/11:
Revised packaging steps.
Update 13/08/11:
Removed unwanted method for ROM cooking.
Update 04/08/11:
Modified extract and repack ROM guide and added extracting system.rfs guide.
Things you need:
Base firmware
Archiver software (7zip recommended)
Any Linux environment to build ROM or Cygwin
APK Manager to optimize and decompile *.apk files
MagicISO (Optional) if you want to extract system.rfs
And the last thing is... You need enough experience in android world
So, here is the steps to cook a ROM:
Flash your phone with your desired base firmware
Make required modifications
Pull system.rfs from your phone by running this command on adb shell or Terminal Emulator:
Code:
dd if=/dev/stl12 of=/sdcard/system.rfs
Extract any *.tar.md5 files from your base firmware to your working folder with 7zip
Replace the current system.rfs with your modified one
EDIT: Pack your ROM by running this code via terminal or just pack it with 7zip/WinRAR as *.tar
Code:
tar -H ustar -c * >> ROMNAME.tar
change ROMNAME to your desired, well, ROM name.
Here is (yet) useful guide to modify your ROM.
Extract system files on system.rfs to make modding easier:
Extract PDA file (*.tar.md5) files with 7zip
Open system.rfs with MagicISO
To extract it, just drag and drop
NOTE: Never edit your ROM with MagicISO because the file permissions will be ignored, use MagicISO only for extracting files from system.rfs
Deodex, and Zipalign (optimize) your ROM apk files:
Ready to use deodex + root for KPN: http://forum.xda-developers.com/showthread.php?t=1196230
Ready to use deodex + root for KPH and other firmware: http://forum.xda-developers.com/showthread.php?t=1118048
Open APK Manager
To zipalign your apk files, in apk manager folder /place-apk-here-to-batch-optimize put your:
framework-res.apk, twframework-res.apk and all system apk
but not these:
AxT9IME, Calculator, Camera, Email, MMS, Phone, Screen Capture, Settings, Swype, Thinkdroid, Voice search
Choose Choose option 15
Then choose both (zp)
Let it run and done.
Now put back the apk files where they belong in the ROM.
How to put these apk files to my ROM? Copy these files to appropriate locations, such as /system/app to your ROM's /system/app, and etc.
Another handy modification guide:
Unpack and repack boot.img - http://forum.xda-developers.com/showthread.php?t=1173427
Convert firmware filesystem to ext4 - http://forum.xda-developers.com/showthread.php?t=1202049
Overscroll glow for any firmware - http://forum.xda-developers.com/showthread.php?t=1215933"
Give thanks to all dev who made that possible!
If you have more guides to put here, please PM me.

Am I pertamax?
hehe..just kidding.
Nice Info....great share.

I would want the Fla.sh Rom :'(

Thats a gr8 share...Thank you...)

saiftheboss7 said:
I would want the Fla.sh Rom :'(
Click to expand...
Click to collapse
sorry... once again, I'm sorry, I can't continue my ROM

Helpful thread man!
Thanks!

Great job taking your time to make this! Unfortunately, i dont even know the basics but now I know where to check when I do

fla.sh said:
sorry... once again, I'm sorry, I can't continue my ROM
Click to expand...
Click to collapse
Hey!
THX man, nice thread. Very useful!
Just PM to MOD, that they close you previous thread, a bout fla.sh.ROM. Or ppl just waiting it and asking.
CHEERS!

i think the most troublesome problem i encounter is to repack system.rfs. yes it can be mounted in magiciso, but howto repack/compile it back?

an0nym0us_ said:
i think the most troublesome problem i encounter is to repack system.rfs. yes it can be mounted in magiciso, but howto repack/compile it back?
Click to expand...
Click to collapse
Just save it.

didnt work when i just save it. my device got bootloop

an0nym0us_ said:
didnt work when i just save it. my device got bootloop
Click to expand...
Click to collapse
What modification you've added to your ROM? Maybe that modification causing the problem...

fla.sh said:
What modification you've added to your ROM? Maybe that modification causing the problem...
Click to expand...
Click to collapse
As Linux, MagicISO read RFS image as a FAT filesystem. File permissions can not be maintained. A better way but need linux:
1. Mount system.rfs as FAT and mount it to /tmp/rfs
2. Make ext4 image, and mount it to /tmp/system
3. Copy /tmp/rfs contents to /tmp/system
4. Make modification inside /tmp/system
5. Fix file permissions inside /tmp/system
6. Umount both image
7. Make ODIN flashable image, contains system.rfs (now in ext4 format) and CF-Root-S5830 boot and recovery image (for ext4 support)
8. Boot to Windows and flash your new firmware using ODIN.

ketut.kumajaya said:
As Linux, MagicISO read RFS image as a FAT filesystem. File permissions can not be maintained. A better way but need linux:
1. Mount system.rfs as FAT and mount it to /tmp/rfs
2. Make ext4 image, and mount it to /tmp/system
3. Copy /tmp/rfs contents to /tmp/system
4. Make modification inside /tmp/system
5. Fix file permissions inside /tmp/system
6. Umount both image
7. Make ODIN flashable image, contains system.rfs (now in ext4 format) and CF-Root-S5830 boot and recovery image (for ext4 support)
8. Boot to Windows and flash your new firmware using ODIN.
Click to expand...
Click to collapse
I use this command to mount rfs:
Code:
mount -o loop system.rfs /some_dir
Can you share us the command?

now thats really informative. thanks

ROM unpacking and repacking gude has been corrected. Tested by me. If you have any problems, just ask here.
Thanks.

I think you should add the date of update in the title, so that everyone can know about the update...
BTW thanks for this amazing guide...
Love it!!!

After making changes to system.rfs, how to save it as .rfs again?

adiles said:
After making changes to system.rfs, how to save it as .rfs again?
Click to expand...
Click to collapse
Please take look at the first page, it's updated, you know?

After I created md5 file and selected it in odin, it says "invalid image type" and "invalid model binary". How to solve that? After that I continued, skipped these errors and flashed, my phone stopped at boot screen with text "Galaxy ACE....". Plz help me

unable to install OTA2 WE

I'm not able to install the new OTA2. A factory reset didn't fix it. I read the CWM DEV thread and updated my "old" CWM to the newest version for my Tablet (ventana64_recovery.img) (WE)
Trying to install the new OTA2 update it stops and Trying to install the OTA via the CWM i got although an Error (like before):
Installing update...
assert failed: getprop("ro.product.device") == "Indigo" || getprop("ro.build.product") == "Indigo"
E:Error in /sdcard/ThinkPatTablet_A310_02_0039_0086_WE.zip
(Status 7)
Installation aborted.
I read in an other Forum that perhaps the CWM and Voodoo RootKeeper in combination could cause some Problem, but I have no idea to solve it.
Is there a way to uninstall the CWM, install the OTA and reinstall the CWM ?
Did someone managed to install the OTA2 with CWM installed
Thanks
Antiheld

i had the same problem. solved it by restoring the original Recovery.
- you have to have superuser rights
- you should have a backup of the stock recovery in /system named recovery-from-boot.p
- put the file from the zip to /system/etc and do the following via adb:
Code:
$ su
# dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
- do a reboot and try to install the OTA2 update.
for me it worked like a charm. hope for you too.

That didn't work for me. Now I can't get into Recovery-Mode. Can someone post the stock recovery?

which tablet version do you have? i can only give you the 16 gb Wifi only version. didn't you check to have /system/recovery-from-boot.p file? maybe it is called different at your tablet?
edit: attached stock recovery for 16gb wifi only model.

Yeah I tried it. I copied your command. I have the 64GB 3G model. The file /system/recovery-from-boot.p is only 343918 bytes big. Is this alright?
I tried Quick Reboot App and the Volume-Toggle, which always worked for me. Couldn't get into recovery.
Could it be the install-recovery is the wrong one? (I really should make backups before doing stuff like install CWR )
EDIT: I checked the new OTA-zip. There is a new recovery-image and a new install-recovery.sh in there. I think I'll try these? Or do you think it's a bad idea?

the file in /system should be all right. When you fully copied my commands then you should know that the $ and the # are already in your window.
but if you have some new files take them and do the following (now you really can copy the commands )!
-put your 2 files to the destinated place and hit the following code into your command tool :
Code:
adb shell
su
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1

Hi,
I have the same problem as Noneus. After done your step, now I cannot get in to recovery mode anymore. I tried both, copy your file even copy from now OTA.zip to the destination. Anyway to solve it?
---------- Post added at 02:12 PM ---------- Previous post was at 02:03 PM ----------
OK now I'd managed to get back to CWR following this thread again http: //santafemods.com/Forum/ThinkpadForums/CWR_Port/C-TPT%20CWR%20port%20setup .pdf. But still stuck, cannot update new OTA2.5.

[Request][ROOT] Rooted GB userdata partition image (CG37)

There is apparently a new rooting method:
http://forum.xda-developers.com/showthread.php?t=1606353
But for it to work we need the userdata partition image (aka CG37) of someone with a rooted GB.
So if someone with a rooted GB can run the following:
Code:
dd if=/dev/block/userdata of=/sdcard/CG37.smg
or
Code:
busybox dd if=/dev/block/userdata of=/sdcard/CG37.smg
and upload it somewhere, it woul help us test whether this method works
Thanks in advance

post
Someone have post this....
Originally Posted by nicofff
I've just created a thread there, let's hope someone helps us
Do you think we could use the CG37 from other (similar) devices?
For example, as far as i know, the milestone 2 is very similar to the defy and the Pro looks similar too.
We just need it to boot, so we can push the needed files to system.
Have you uploaded your CG37 somewhere, so i can test in on my MS2?
Try it! http://www.mediafire.com/?aweayb68szubuci
---------- Post added at 09:56 AM ---------- Previous post was at 09:21 AM ----------
tryed...
Files is too big!!!!!

Re upping this thread..
My Milestone came back from motorola tech support with a unrootable 2.3.6 so I need ANY gingerbread userdata backup. You don't even have to use the dd command if you don't want to. A data.ext3.tar or from clockworkmod would do.
Also you can wipe data before creating the userdata backup so I won't have access to your stuff, but boot at least once so the phone can create the needed files.

[Q] md5 mismatch with the 'newer' CWM

Folks,
I had some free time on the weekend and tried some ROMs on my new Nexus. I use one of the newer versions of CWM as Recovery and of course did always a backup before flashing something new, ended up with five of them.
The problem is now that I am not able to restore any of them due to the known md5 mismatch error.
All the tutorials and videos in the inet for solving this issue are based on the ‘older’ cwm structure where you find the backup under /sdcard/clockworkmod/backup where we used to have the five files
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
system.ext4.tar
The ‘newer’ CWM is different, the backups are obviously splitted and following /data/media/clockwordmod we have the folders ‘backup’ and ‘blobs’. In the backup folder I now have:
boot.img
recovery.img
system.ext.dup
My initial idea was to use the Terminal Emulator app and to create a new nandroid.md5 with following commands:
su
cd /data/media/clockworkmod/backup/*nameofhtebackup*
rm nandroid.md5
md5sum *img > nandroid.md5
Before I continue with above procedure I thought it would be a good idea to ask you guys and experts if I am on the right track? Needs the nandroid.md5 to be in that ‘new’ backup folder at all?
And another question: as my Nexus is so new and there is only quite few stuff on it yet – maybe it would be better to start from scratch and get rid of CWM and and use TWRP instead?
Any assistance is highly appreciated!! ThX

Yes! I was about to suggest that you scrap CWM, Team Win is much more stable. And just so you know, you can actually use CWM backups with TWRP so there's no need to start over
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
---------- Post added at 07:42 AM ---------- Previous post was at 07:38 AM ----------
There's also an option in the TWRP restore menu that allows you to 'skip MD5 check' so you won't be experiencing that again.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

the easiest way is to open the .md5 file in a text editor, remove all the data from it and save it. This way CWM bypasses md5 check

same
renjithrs007 said:
the easiest way is to open the .md5 file in a text editor, remove all the data from it and save it. This way CWM bypasses md5 check
Click to expand...
Click to collapse
I also have the same problem. I used cwm touch to backup. unlike old cwm backup, the backup showed backup folder and blobs folder. when i tired to restore, it showed md5 mismatch. I have no clue how to proceed. how u guys from above solved the problem?

Rollback 3.2.7 just popped in... What can I do to help?

Hi!
I've a rollback file on my Kindle currently waiting for downgrading.
The file just popped in and waiting that I'll charge my kindle.
Is there anything I can do for the community to support with information and/or files?
I am on stock 4.5.2 with, of course, no root.
Cheers
URBANsUNITED

Well I will be first to thanks for offering to help mate as not much happening with a root at the moment so well done for coming forward ...

URBANsUNITED said:
Hi!
I've a rollback file on my Kindle currently waiting for downgrading.
The file just popped in and waiting that I'll charge my kindle.
Is there anything I can do for the community to support with information and/or files?
I am on stock 4.5.2 with, of course, no root.
Cheers
URBANsUNITED
Click to expand...
Click to collapse
With out root .no not at this point that I know of

jimyv said:
With out root .no not at this point that I know of
Click to expand...
Click to collapse
OK
I've downgrade my device now.
URBANsUNITED

URBANsUNITED said:
OK
I've downgrade my device now.
URBANsUNITED
Click to expand...
Click to collapse
let me knowif you get down graded, root
Safestrapped ..and want to try something safe to get that file

jimyv said:
let me knowif you get down graded, root
Safestrapped ..and want to try something safe to get that file
Click to expand...
Click to collapse
Pretty sure the file gets deleted right after.

I believe too as my download dir is empty now...
I am on 3.2.7 rooted now if you still want to try...

URBANsUNITED said:
I believe too as my download dir is empty now...
I am on 3.2.7 rooted now if you still want to try...
Click to expand...
Click to collapse
install safestrap
newest version and install recovery
you saw something in your downloads directly? Before your downgrade?

safestrap 3.75 installed
yep, I also had some ROMS located. Downloads dir wasn't empty before

URBANsUNITED said:
I believe too as my download dir is empty now...
I am on 3.2.7 rooted now if you still want to try...
Click to expand...
Click to collapse
Check /cache with a root file explorer, but I doubt it's still there.

EncryptedCurse said:
Check /cache with a root file explorer, but I doubt it's still there.
Click to expand...
Click to collapse
no it will be gone from there once used it deletes it
Enter Recovery and do a backup of your stock lot
next build a ROM slot any will do
restore backup to ROM slot
download a copy of ROM Toolbox lite And install on running rom slot

Nope... gone
see the attched zip

jimyv said:
no it will be gone from there once used it deletes it
Enter Recovery and do a backup of your stock lot
next build a ROM slot any will do
restore backup to ROM slot
download a copy of ROM Toolbox lite And install on running rom slot
Click to expand...
Click to collapse
Ok, installed. Whats next?

URBANsUNITED said:
Ok, installed. Whats next?
Click to expand...
Click to collapse
so currently you are running on a ROM slot not your stock slot and you have rOM Toolbox installed correct?
---------- Post added at 02:50 PM ---------- Previous post was at 02:48 PM ----------
download this file https://mega.co.nz/#!wlQl2bZD!Kk-rcWtcMPWxoEH5VcHrtZb7nOsJet9si1pm5FYhT44

jimyv said:
so currently you are running on a ROM slot not your stock slot and you have rOM Toolbox installed correct?
Click to expand...
Click to collapse
Correct! I can read and(!) follow

open rOM Toolbox,scroll right to build.prop Editer and open
Scroll left and create backup
---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------
now open root explorer or file explorer
go to SD card rOM Toolbox build.prop backup file and insert the file that you downloaded
---------- Post added at 03:02 PM ---------- Previous post was at 02:57 PM ----------
now go back to backup and restore in rOM Toolbox for build.prop and restore the file that you downloaded here's where it gets hairy
whatever you do do not let it try to install whatever it downloads if you keep touching and using the tablet it will not attempt it on its own it must be at idle.after you reboot go to settings and check version number it should have the new build.prop file and check for updates. I'm hoping it will attempt to redownload the downgrade file to cashe then you must immediately remove it from device and delete that ROM slot.
it may not even like the swap and not even boot in that case that's why we had safestrap installed. It will not work just delete the slot and move on with life

Ok! Did that, installed the downloaded file and did a reboout.
System works, but no text is visible, only icons.
Next to ask for a update? But how as i can't read anything...

URBANsUNITED said:
Ok! Did that, installed the downloaded file and did a reboout.
System works, but no text is visible, only icons.
Next to ask for a update? But how as i can't read anything...
Click to expand...
Click to collapse
ok its not going to play nice. Simply reboot into safe strap and restore to slot 1 again and we can try something else

jimyv said:
ok its not going to play nice. Simply reboot into safe strap and restore to slot 1 again and we can try something else
Click to expand...
Click to collapse
Done! Back in business

now it doesn't really matter how you want to try to do it but what we need to do is edit your file to accommodate the newer version numbers
you can either go to those backup files and swap their and restore again or use the backup file for reference and do it line by line in the prop build editor
---------- Post added at 03:37 PM ---------- Previous post was at 03:28 PM ----------
ro.build.description
ro.build.fingerprint
ro.build.lab126.project not sure if this one is there for both ones
ro.build.version.fireos
ro.build.version.incremental
ro.build.version.name
ro.build.version.number
robuild.version.release
Save
Reboot