Tre 2.1 rom-builder's mod 0.0

[Guest twrock]

For anyone who is still interested in 2.1 rom modding, but is held back by what seems like a complicated process to get started, here is another option: U8220B822 0.0 ROM (Tre 2.1 mod).

The link is to a signed rom that can be flashed and used as-is. But I don't really recommend that. There are already other modified roms out there that work really well and have a lot of added features. This is not intended to replace any of those. Instead, it is intended to be modified to become whatever you might want to make it. So unless you are interested in doing some rom modding yourself, this will likely be of little interest to you.

Toward that end, this rom has "only" the following modifications to the original Tre 2.1 rom (build 822):

• "0.0" added to the end of the name in build.prop to distinguish it from the original
  
• Swap kernel (thanks to flibblesan) added to the Tre boot.img
  
• Superuser 2.3.6.1
  
• DT Apps2SD 2.7.5.2
  
• Busybox
  
• /data/apps enabled
  
• Alternate boot animations enabled
  
• Removed SwedishPack.apk to make space for Superuser.apk
  
• build.prop and local.prop modified to have language=en and location=US
  
• local.prop modfied to make all locations available
  

All other apps in the original rom have been unchanged. No apps have been added to /data/app.

Notes:

Of course you need to have updated with the Tre updata.app before you try to flash this rom.

If you install this rom without modifying it, it runs very poorly on the first boot. The two biggest reasons are that it has live wallpaper set by default, and the swappiness settings are not optimized. Since Terminal Emulator has not been pre-installed, you'll need to do that as soon as possible and set the swappiness to something reasonable (15 has been suggested by others, but that's a whole different topic). Also, I'd recommend dumping the live wallpaper as soon as possible to avoid some terrible lag issues in the Canvas Launcher. (You can comment out the line in build.prop that references the live wallpaper as another alternative to help with that first boot.)

One known bug is that you can not run "Fix permissions" in the Clockwork ROM Manger 2.5.0.4. I don't know if this is a ROM Manager or Superuser problem or what. Other than that, ROM Manager seems to be working fine.

Ok, that's all I can think of at the moment. I hope it is of use to someone besides me. This is the base rom upon which I built the latest version of the rom I'm currently using for myself, and I'm very happy with the results. As always, YMMV.

Enjoy.

Download: U8220B822 0.0

Edited October 23, 2010 by twrock

[Guest protocold]

Thx so much. Really appreciate your work.

I have a noob question again, how do you take it to the next step exactly? do I need to setup some environment or?

[Guest twrock]

Thx so much. Really appreciate your work.

I have a noob question again, how do you take it to the next step exactly? do I need to setup some environment or?

Using this rom to build your own is relatively "easy". No special environment is needed. All of that kind of work is already done.

If I am thinking clearly (always questionable), all you really need at this point is the ability to unzip and rezip that rom. But if that is all you do, you haven't modified it. So here are some things you can do to start modifying it:

1. Unzip the whole rom, maintaining the directory structure.

2. Delete whatever apps out of /system/app that you know are safe to delete and that you don't want.

3. Add whatever apps (*.apk files) into /system/app that you want to have permanently installed in the rom. Where can you get those APK's? I get them by using AppMonster to backup my apps to my SD card. Caution, you can not go overboard here. Most original roms have full /system/app folders and you can't go over that limit. That is why I had to delete something (SwedishPack.apk) out of the rom to get it to work as-is.

4. Add whatever apps you want to the /data/app folder. These apps can be deleted or overwritten by new versions. However, here is one place you need to be careful, because you want to make sure those are in the "installed" state and you might need to include some special files copied into other places in the rom. For example, Terminal Emulator needs to have a file copied into the /system/lib folder. Basically, you need to know a bit more about how to make sure you have everything you need when putting apps into /data/app. Have a look at some other "complete" rom like one of the TWeak roms to see what is in the /data/app folder. That will help you get started in your understanding. Where can you get those installed apps? I copy them out of my ext partition on my SD card using my Linux computer. (I don't know how to do that in Windows, but I'm sure there is a way.)

5. Add a custom boot animation into the /system/media folder if you want to.

6. Edit the /system/build.prop file (it is a text file) to make all the modifications you want to include. There have been some threads on this site with good suggestions to what can be done there. Again, you can also open up the build.prop file in some other complete rom to see what that person did. Here is where you might want to change the rom name so as not to confuse yourself in the future.

7. There are some other things you can do, but for now, that will probably be plenty to keep you busy.

Note: you don't have to do all of that. Just do as much as you want and test it.

After you are done with all of that, zip the whole thing back up into a new file. If you are using Clockwork Recovery, you do not have to go through the process of learning how to "sign" your rom (that does require installing something else onto your computer). Your rom should be ready to go. Copy it to your sd card, reboot into recovery, and make a backup (be sure you have enough space for the backup because CWR will not tell you you have a bad backup). Do a full wipe and then try to install your new rom.

If your install fails, one of common problem is that you overfilled the /system folder. Delete some stuff and try again. Actually, it's probably not a bad idea to just make incremental changes to your rom at first until you are sure you understand what you are doing. Then you can make more significant changes when you feel comfortable.

Have the original Tre /dload folder on your sd card. It might be necessary to reflash that to get out of some really badly failed attempt to install a faulty rom, but usually doing a wipe and installing a good rom is sufficient.

Feel free to ask more questions. If I don't know the answer, I'll just make something up. :D :P :D

No, seriously, please ask questions if you have them. If people are too busy or too bothered, they can just ignore you. But someone else might have the knowledge and time to help you out. You won't know if you don't ask.

Enjoy.

Edited October 23, 2010 by twrock

[Guest margariins]

Using this rom to build your own is relatively "easy". No special environment is needed. All of that kind of work is already done.

If I am thinking clearly (always questionable), all you really need at this point is the ability to unzip and rezip that rom. But if that is all you do, you haven't modified it. So here are some things you can do to start modifying it:

1. Unzip the whole rom, maintaining the directory structure.

2. Delete whatever apps out of /system/app that you know are safe to delete and that you don't want.

3. Add whatever apps (*.apk files) into /system/app that you want to have permanently installed in the rom. Where can you get those APK's? I get them by using AppMonster to backup my apps to my SD card. Caution, you can not go overboard here. Most original roms have full /system/app folders and you can't go over that limit. That is why I had to delete something (SwedishPack.apk) out of the rom to get it to work as-is.

4. Add whatever apps you want to the /data/app folder. These apps can be deleted or overwritten by new versions. However, here is one place you need to be careful, because you want to make sure those are in the "installed" state and you might need to include some special files copied into other places in the rom. For example, Terminal Emulator needs to have a file copied into the /system/lib folder. Basically, you need to know a bit more about how to make sure you have everything you need when putting apps into /data/app. Have a look at some other "complete" rom like one of the TWeak roms to see what is in the /data/app folder. That will help you get started in your understanding. Where can you get those installed apps? I copy them out of my ext partition on my SD card using my Linux computer. (I don't know how to do that in Windows, but I'm sure there is a way.)

5. Add a custom boot animation into the /system/media folder if you want to.

6. Edit the /system/build.prop file (it is a text file) to make all the modifications you want to include. There have been some threads on this site with good suggestions to what can be done there. Again, you can also open up the build.prop file in some other complete rom to see what that person did. Here is where you might want to change the rom name so as not to confuse yourself in the future.

7. There are some other things you can do, but for now, that will probably be plenty to keep you busy.

Note: you don't have to do all of that. Just do as much as you want and test it.

After you are done with all of that, zip the whole thing back up into a new file. If you are using Clockwork Recovery, you do not have to go through the process of learning how to "sign" your rom (that does require installing something else onto your computer). Your rom should be ready to go. Copy it to your sd card, reboot into recovery, and make a backup (be sure you have enough space for the backup because CWR will not tell you you have a bad backup). Do a full wipe and then try to install your new rom.

If your install fails, one of common problem is that you overfilled the /system folder. Delete some stuff and try again. Actually, it's probably not a bad idea to just make incremental changes to your rom at first until you are sure you understand what you are doing. Then you can make more significant changes when you feel comfortable.

Have the original Tre /dload folder on your sd card. It might be necessary to reflash that to get out of some really badly failed attempt to install a faulty rom, but usually doing a wipe and installing a good rom is sufficient.

Feel free to ask more questions. If I don't know the answer, I'll just make something up. B) :unsure: :angry:

No, seriously, please ask questions if you have them. If people are too busy or too bothered, they can just ignore you. But someone else might have the knowledge and time to help you out. You won't know if you don't ask.

Enjoy.

Is it possible to modify so that it is compatible with u8220-6?

most of udates that fail show that oembsl mismatches in log file. Oembsl is some kinf of pre-boot state?

[Guest twrock]

Is it possible to modify so that it is compatible with u8220-6?

most of udates that fail show that oembsl mismatches in log file. Oembsl is some kinf of pre-boot state?

I am completely ignorant of the issues specific to the u8220-6. So I personally can offer no help. Hopefully someone else who knows that device can offer help.