Related
Can any body post tutorial for building a custom rom for G1 and Hero?
wrong area to post this... probably should take it off.
were should i put this thread then
Q&A buddy.
I wrote a few how-to's on compiling your own android build from source, i recommend starting here:
http://robblue2x.blogspot.com/2009/07/how-to-set-up-ubuntu-virtual-machine.html
it is a bit out of date now because android moves so fast, its incredibly hard to keep up to date!
robblue2x said:
I wrote a few how-to's on compiling your own android build from source, i recommend starting here:
http://robblue2x.blogspot.com/2009/07/how-to-set-up-ubuntu-virtual-machine.html
it is a bit out of date now because android moves so fast, its incredibly hard to keep up to date!
Click to expand...
Click to collapse
Just visited this link But how do modify the existing files of android OS ?
If you have to ask how to change the files then you probably shouldn't be messing with the code for an OS. There is alot to it. You need to know how to set up linux, Git, repo, sdk, emulator, learn java,maybe some C++, edit xml files, and compile the edited code just to name a few.
read this
If you get that working then all you need is a text editor to start changing code.
Good luck!
What about modding existing roms?
Here is what I know so far...
system apps are not individualy signed
Rom must be packaged in zip having 3 root directories.
data (holds apps normaly)
META-INF (holds some kind of build files... and android manifest)
system (holds the OS and scripts and such.)
Also boot.img in the root dir.
The update.zip needs to be resigned if repackaged.
=) that is it all that I have gathered after hours of searching.
I dont want to recompile a kernel as I dont need to modify one. I would rather leave that to the more experienced DEVs. All I want is to remove/replace few apps...
My questions:
How do you sign a file... (tried the sign java thing in ubuntu and I get some king of error... could not find library and what not...)
There is a windows batch file floating around I have not tryed that.
I have some basic understanding of code language and I can flollow instructions even if I have to find my way around some stuff... but this rom building is like black magic... Everyone is doing it no one wants to explain how its done... If its too damn hard then so be it. I can modify it on the back end after installing. I just believe in clean simple installs.
What generates the META-INF directory and the files in there. Seems like there is some instructions on setting permissions for certain files and (manifest) seems like signiture keys..
Is that generated when the file is signed?
is it manualy generated?
is can those files be modified?
I know if this is answered it would be helpful in letting people optimize the builds for their own needs.
Sorry for the long post. I hope this gets explained or I dont care if I have to read, give me a bunch of homework (links).
zambezy said:
What about modding existing roms?
Here is what I know so far...
system apps are not individualy signed
Rom must be packaged in zip having 3 root directories.
data (holds apps normaly)
META-INF (holds some kind of build files... and android manifest)
system (holds the OS and scripts and such.)
Also boot.img in the root dir.
The update.zip needs to be resigned if repackaged.
=) that is it all that I have gathered after hours of searching.
I dont want to recompile a kernel as I dont need to modify one. I would rather leave that to the more experienced DEVs. All I want is to remove/replace few apps...
My questions:
How do you sign a file... (tried the sign java thing in ubuntu and I get some king of error... could not find library and what not...)
There is a windows batch file floating around I have not tryed that.
I have some basic understanding of code language and I can flollow instructions even if I have to find my way around some stuff... but this rom building is like black magic... Everyone is doing it no one wants to explain how its done... If its too damn hard then so be it. I can modify it on the back end after installing. I just believe in clean simple installs.
What generates the META-INF directory and the files in there. Seems like there is some instructions on setting permissions for certain files and (manifest) seems like signiture keys..
Is that generated when the file is signed?
is it manualy generated?
is can those files be modified?
I know if this is answered it would be helpful in letting people optimize the builds for their own needs.
Sorry for the long post. I hope this gets explained or I dont care if I have to read, give me a bunch of homework (links).
Click to expand...
Click to collapse
my advice for signing files would be to read through this thread. stericson says that JF's autosigning tool will work in linux. if you still can't get it pm stericson, he is a very nice member and should be able to help you
Thanks... That worked in windows.
Im getting some FC's but I can at least work on that now...
I did remove everything from the MANIFEST before signing just in case something did not get overwriten correctly.
I don't mess with the manifest files, so try not touching them and see if that helps
Can any body describe what does these files do while building a theme and how to edit these files:
android.policy.jar
framework.jar
services.jar
build.prop
build.sapphire.prop
build.trout.prop
sabin123 said:
Can any body describe what does these files do while building a theme and how to edit these files:
android.policy.jar
framework.jar
services.jar
build.prop
build.sapphire.prop
build.trout.prop
Click to expand...
Click to collapse
the prop files are configuration files and should NOT be replaced if your making a theme.
the .jar's should only be messed with if your adding stericsons lockscreen. you will have to decompile them for it to work
How to decompile the services.jar files?
Check out my theme thread. It's from when I was porting Android but most of these questions are explained in pretty good detail with links for more info. That should help you out quite a bit:
http://forum.xda-developers.com/showthread.php?t=578421
Go to the second post
Thanks for the link..
Stericson have a new Metamorph App.
It uses xml theme control files instead of the old thm files.
danation from the ModMyMoto forum has made a program, that updates the thm file to the new xml format.
It works very very well.
Please at all themers:
Use the Pro Version, use the new Metamorph with xml. Upgrade your Morphs with the xml files. Its not many work for you, but you can help us themers and users if you do this.
Download
http://www.4shared.com/file/5l0E6t76/ThemeControlFileUpgrader.html
Original Post at ModMyMotoForum
http://www.modmymoto.com/forums/showpost.php?p=3917253&postcount=10
Thanks, danation, thanks stericson! Great work!
Ummm, do you themers not use the pro version?
Only a question. I think, this app from stericson is every buck worth!
I've upgraded my themes all for Metamorph xml files.
Now all themes have an xml AND a thm file, so everybody could use them.
Today is the day.
I hope, you themers out there have changed your theme control files to the new one (*.xml)
Today, stericson has released the new Metamorph free version which supports only the xml file.
Please update your themes. We dont want to have some chaos in the theming community, isn't it so?
Stop getting angry at Stericson for moving Metamorph into a safer environment for the user (giving more information as to what is being changed).
HTCClay put it best:
@Stericson you can't update...where do you get off making things better? How dare you...
Click to expand...
Click to collapse
This utility is VERY easy to use and will convert any .thm file to .xml in seconds.
JAguirre1231 said:
This utility is VERY easy to use and will convert any .thm file to .xml in seconds.
Click to expand...
Click to collapse
Thanks I've updated it, in case anybody still needs some converting to do. This is the final version, unless there are any bug fixes needed.
Included in the download is an executable JAR file that will work on any operating system that has the Java Runtime Environment installed (version 6 or later.) Windows, Mac, and most Linux Distros will be able to run this program.
An equivalent EXE file was also added for the convenience of Windows users.
Original download location at M3 is here.
Download from XDA here.
-1.3-
* Drag and drop directories - All .thm files in the directory and all subdirectories will be converted. Other files are ignored. You can convert all of your themes at the same time
-1.2-
* Drag and drop feature added (I borrowed some public domain code found here.) Tested on Windows 7 and Ubuntu. Should work on Mac and Kubuntu as well.
* Option to disable dialogs
-1.1-
* Fixed bug that always warned about duplicate files
* When errors are found, it finishes writing all valid data before terminating.
-1.0-
* Ignores single blank lines
* Captures notes after double blank lines
* Adds functionality to enter in header information
* Prevents file overwriting
* Puts framework at the bottom no matter where it is in the .thm file
I'm still not clear on how you actually *use* this converter. Could someone post a step-by-step breakdown? Right now, I have the thing sitting on the root of my SD. Do I need to move it to the Android Themes?
No, not using with your mobile phone.
Copy it to your pc.
Open the Programm and take your *.thm file you want to convert to an *.xml file.
Thats all.
FlashMOD is a tool for creating and applying themes on Android. FlashMOD resolves the difficulties in applying MetaMorph themes by applying the themes to the ROM or update zip file instead of on the live phone. It takes less than a minute to apply a large theme to a ROM. You can then flash the ROM and you will have the theme up and running quickly and painlessly. If your ROM has a separate package for the gapps, then you will need to apply the theme to both the ROM and the gapps package.
FlashMOD should be compatible with any any Android Phone, ROM, or update zip, but I have only tested it on the Eris and with the following ROMs:
-Conap's CELB/gapps package.
-KaosFroyo
-TazzFroyo
For developers, the program also includes many more features for batch compiling, decompiling, compressing, resizing, signing, zipaligning, and extracting NAND .img files. For more information, please read the pdf documentation I bundled with the program.
Always make a nandroid backup before applying ROMs themed with FlashMOD.
Credits:
icbeer - FlashMOD
Cheezo - DotNetZip Library
Brut.all - apktool
Android Open Source Project - aapt, draw9patch, zipalign, media.pk8 media.x509.pem, platform.pk8, platform.x509, shared.pk8, shared.x509.pem, testkey.pk8, testkey.x509.pem, signapk.jar
Oracle - swing-worker-1.1.jar
Cosmin Truta - OptiPNG
Jean-loup Gailly - zlib
Mark Adler - libpng
ImageMagick Studio LLC - ImageMagick
Everaldo Coelho - Crystal Project icons
Kai Wei - I ported his unyaffs program to C#
Change Log:
1.1.2 - (2010-11-22) Fixed an issue when modifying the update script for the ROM. I was adding the wrong line endings.
1.1.1 - (2010-11-22) Minor tweaks. Looks like I have a bug in this version that shows the version number incorrectly in the title bar. I'll have that fixed in a bit.
1.1.0 - (2010-11-22) Added the ability to directly apply MetaMorph themes. Added ability to extract all the different .img files from a NAND backup (data.img, system.img, and boot.img). This was pretty cool because I ported/implemented the entire thing in C# code.
1.0.1 - Fixed bug in signing form. Pem and pk8 keys were reversed for certain radio buttons. Also modified theme application process. Apks are no longer signed, but are still zipaligned. KaosFroyo didn't like it when I signed certain apks with the test key even though this was OK in CELB.
Downloads:
- FlashMOD 1.1.2 (SHA1:207bda5d7cb9f3185ff01d9188f1c75e0f3bb47e)
FlashMOD runs on .NET FrameWork 3.5 on Windows and Mono on other platforms. There is 1 distribution for all platforms. FlashMOD also requires Sun Java JRE 6. To run on Windows you double-click on FlashMOD.exe. To run on mono you type "mono FlashMOD.exe" from the command prompt. Most linux tools are bundled or preinstalled under Ubuntu. I have never tried this on a Mac, but it should work. If you use any of the tools besides applying themes on a platform other than Windows you will need to change the file "FlashMOD.exe.config" and change the path of the external tools to point to their location on your system. It's been a while since I tested FlashMOD on Linux and I hope to start looking at that again soon.
- FlashMOD 1.1.2 Source Code (SHA1:1b524c0301027a98097c1f4a1f2a4db1b94c04a2)
FlashMOD is open source licensed under the GPL v3. FlashMOD is written in C#.NET and was developed in Visual Studio 2010.
Themes:
Buuf Theme 1.0.0 for FlashMOD.
This is a port of the Buuf theme by petsasj on the hero forums. This theme also installs the Buuf ADW theme in your /data/app folder. Make sure to select this theme in ADW to get the best experience.
[Reserved]
This looks cool. I will see if I have time to play around with it soon. I have been having problems with metamorph and it can be very slow with framework files. Hopefully I can get it working in the mac terminal.
synesthete said:
This looks cool. I will see if I have time to play around with it soon. I have been having problems with metamorph and it can be very slow with framework files. Hopefully I can get it working in the mac terminal.
Click to expand...
Click to collapse
I'm sure it will work under emulation. I'm curious whether it would work natively on the Mac under Mono. I tried it a little under Mono on Linux and it seemed to work fine for applying themes, but I never tried any of the other features. It's kind of surprising, but the same exe that works under windows should work on Linux and Mac like a Java application. Mono is binary compatible with windows. You just type "mono FlashMOD.exe" from the command line to run it. Mono supports Windows Forms on Windows, Linux, and MacOSX. I do not have all the external tools bundled for Mac, so you would have to round those up, but they are all open source. There is a config file that sits alongside the exe that tells it the path of the executables. I have it setup for Windows, so you would need to change it for other platforms.
If anyone wants to help me provide Mac and Linux support I would appreciate that.
cool mod! gonna use it asap
Let me know if it works for you. This is pretty much in the beta phase at the moment. It definitely works nicely for me on Conap's CELB ROM. Hopefully later today I will have time to test this on Kaos Froyo and some of the others.
Oops, found a couple bugs in the signing utility. I had the pem and pk8 keys reversed in the hardcoded values when selected from the radio buttons. I have corrected this in version 1.0.1. Also there was a compatability problem with KaosFroyo that I have resolved in version 1.0.1. It looks like Conap's ROM has different signing requirements than Kaos. According to logcat, KaosFroyo was complaining that I didn't sign certain apks with the shared keys. Rather than dealing with all that, I'm just going to take the more common approach of not resigning the apks. This will cause header mismatch warnings in zipalign, but I have suppressed these warnings internally. I just built the releases and will be posting them shortly.
Here's a crazy idea I just thought of...would it be possible to make a nand of whatever ROM you're currently running, zip it up, and apply a zipped theme using your method? My thinking behind this is that I'd rather not go through setting up all the mundane stuff such as email, relocating certain apps to system/apps, deleting apps I don't use/duplicate apps, ringtones, and the countless other modifications. If this is just a ridiculous idea, please ignore. Otherwise, any thoughts on this?
hoovnick said:
Here's a crazy idea I just thought of...would it be possible to make a nand of whatever ROM you're currently running, zip it up, and apply a zipped theme using your method? My thinking behind this is that I'd rather not go through setting up all the mundane stuff such as email, relocating certain apps to system/apps, deleting apps I don't use/duplicate apps, ringtones, and the countless other modifications. If this is just a ridiculous idea, please ignore. Otherwise, any thoughts on this?
Click to expand...
Click to collapse
There are other way of reapplying your customizations such as using a Titanium Backup restore. My application does not require that you apply the theme to a ROM either, just a flashable zip file. You can apply it to an update.zip file instead with only the apps you want themed included in the file (and probably framework-res). It's pretty easy to set that up, but it is a manual process. Automatation is a beautiful thing
What you are suggesting is not impossible to do...nand backups are images of the partitions on the phone in yaffs format. There is a program called unyaffs that I have compiled that can extract these. The program could then generate an update.zip file for you to reapply the system apps/framework. This is something I have been considering, although I was thinking of doing it a different way. I was thinking of pulling the apps with adb and then generating an update.zip from that. The problem with the way I was thinking of doing it is that it would require everyone to have the android sdk installed. I like your idea because it would remove the adb requirement. This sounds like a good addition to the next version. I'll look into this. Thanks for the suggestion.
Wonderful job =) works like a charm! Much better than metamorph.
Has anyone tested this on froshedyo v5?
Sent from my FroShedYo.V5 using XDA App
I tried in on CELB. Why don't you just try it on FroyoShed? Just do nand backup before you do it.
danielahl137 said:
Has anyone tested this on froshedyo v5?
Sent from my FroShedYo.V5 using XDA App
Click to expand...
Click to collapse
I haven't tried his ROM out yet. His ROM is compiled with the source code for CELB though if I remember correctly, so it will probably work. I'll try it out after I get off work.
Major accomplishment tonight! FlashMOD is now the first C# application to natively extract all the types of NAND img files, including data.img, system.img, and boot.img. I even created a CPIO archive decompressor to extract the ram disk in the boot.img file. This will all be available in 1.1.0, which I'll try to release this weekend.
icbeer said:
Major accomplishment tonight! FlashMOD is now the first C# application to natively extract all the types of NAND img files, including data.img, system.img, and boot.img. I even created a CPIO archive decompressor to extract the ram disk in the boot.img file. This will all be available in 1.1.0, which I'll try to release this weekend.
Click to expand...
Click to collapse
Very nice! Will test when you post it.
Sent from my FroyoEris using XDA App
Thx, for your help. I will try to post tonight if I have the energy after seeing Harry Potter in the IMAX.
Sent from my ERIS using XDA App
The new release sounds awesome. Nice job icbeer
Sent from my Eris using XDA App
Thanks for the support guys. It's nice to feel like other people appreciate what I'm doing. I didn't make it to post things tonight. I wanted to change part of the implementation to lower memory requirements. I also need to write up all the acknowledgements and round up all the licenses, from anyone I borrowed code from. It's actually kind of tedious to build a release that doesn't violate any licenses.
I'm trying to bundle all these little tools into one package. I'm not adding anything you couldn't do already, but you'd have to compile a C application to extract the unyaffs volumes and you'd have to run a perl script followed by extracting the cpio volume with 7z or cpio (on linux) to do it. By getting them into C# I can now provide a cross platform method for doing this and a graphical interface. It will also allow me to incorporate these utilities into the progress bar at some point.
For now, this is mostly going to be for curiosity sake, or in case you need to pull stuff out of your Nandroid backups. It's pretty interesting to look at the boot.img file and some of the config files in there. The next step will be to generate themed update zip files from the system apps and the framework in the nandroid backups as requested. That was really the whole reason I did this.
I'm trying to port all the external tools to C# to simplify things and give me more control over everything. The real challenge now is signapk and zipalign, because those are the 2 external tools involved in applying themes. Signapk is tricky, because I have to port portions of the Java security library to C#. It looks like the BouncyCastle crypto library may provide a lot of what I need. Zipalign looked a little more straight forward to port.
Sorry I didn't post again today, my internet has been down since this morning. However I added the ability to apply MetaMorph themes, so hopefully that makes up for my lagging. I'll go build the release now so I can post it when I get to work tommorow.
Sent from my ERIS using XDA App
Ughh, took me like 3 versions to get it right, but it is now correctly updating the update script for the ROM in case the theme needs to copy items to the data folder or sdcard. I am very curious to hear from anyone trying MetaMorph themes with this tool. Let me know if things are working out for you.
This guide will help you in porting ROM's to different devices. Although it my not work 100% of the time, it should you show the steps involved in porting a ROM but also which files are important to a device's functionality.
Some handy tools to have before starting:
- The Android SDK, this contains ADB logcat which is a hugely important tool in ROM development. It lets us know what is perhaps causing an app to F/C or a ROM to bootloop. See our guide on how to set this up HERE
- Notepad++ , very useful for altering scripts.
- Patience, getting ports to boot can sometimes take a lot of effort and time but hopefully this guide will show you the quickest and easiest way to get your ported ROM booting.
Okay first decide which ROM you would like to port, don't port HDPI ROM's to MDPI devices or vice versa it just won't work.And it's best to start with the easy and simple ports to get some experience behind you before you go off porting Sense 3.0 to your X10.
Let's get started...
Porting is fairly easy and requires only some folders, files and a boot.img to be replaced.
Now because this is a universal guide I can only tell you how to get the basic hardware working on your port. AOSP ROMs are fairly easy to figure out so you won't have much trouble figuring out what needs replacing. Manufacturer specific ROMs such as Sense 3.0 ROMs are bit more difficult to figure out but the basic skills you will be taught here can be applied in principle to those ROMs.
1. First off lets start with the biggie, the kernel. Those of you familiar with linux will know how important the kernel is a to system, I won't go into detail here but if your kernel isn't specific to your device then your ROM won't boot. The kernel is contained within the boot.img of your ROM's zip (or zImage if it's a Samsung). During flashing it is unpacked and wrote to the system.
To replace the kernel we need to decompile it and no this isn't as easy as opening it winzip. The best way to do this is using Linux; we can use a combination of both perl scripts and terminal commands.
In order for us too see the kernel files contained within the boot.img, we need to first unpack it and this will extract the kernel binary and the ramdisk. What you need at this point is the split_bootimg.zip. This contains a perl script which will extract both files and display the boot.img header, the kernel command line and the board name (if specified).
An example of the output would be:
Page size: 2048 (0x00000800)
Kernel size: 1388548 (0x00153004)
Ramdisk size: 141518 (0x000228ce)
Second size: 0 (0x00000000)
Board name:
Command line: no_console_suspend=1
So how to use this perl script you ask? Well...
First open a terminal and cd to the directory which contains the perl scripts you just downloaded. Next, type this command: "perl split_bootimg.pl boot.img" and that will extract the kernel to your current directory.
Now, we need to extract the ramdisk, the ramdisk has been unpacked from the boot.img and is sitting your current directory with the file name "boot.img-ramdisk.gz", at the moment this still isn't useful to us so we need to un-gzip and then un-cpio it.
So for that we need the Linux terminal. So again from the terminal or using the same terminal enter these commands:
mkdir ramdisk < Creates a directory where we can store the ramdisk
cd ramdisk < Changes our current directory to that of the ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i < Will un-gzip and un-cpio ramdisk
Okay so now we can see all the ramdisk files:
./init.devicename.rc
./default.prop
./proc
./dev
./init.rc
./init
./sys
./init.goldfish.rc
./sbin
./sbin/adbd
./system
./data
So what's important here is the "init.devicename.rc" and "unvented.device.rc". This is the target devices .rc files contained within the ramdisk, now all we have to do here is rename this .rc file to that of the device you are porting to, e.g: "init.trout.rc" > "init.hero.rc"
Some devices ramdisk differ and may not contain "unvented.device.rc" so if this is case for you,then begin by renaming the init.device.rc to your model id and leave it at that. If you get problems well.. that's what the live support is for.
The other file which may be of use to us here is "init.rc", this contains all the system wide kernel properties which we can change to our liking but we'll leave as it is for now.
So now we've edited the ramdisk, we need to change the kernel so that the one the ROM uses is actually specific to our device, when we used the split_bootimg perl script it also unpacked the kernel and that is also in our current directory with the filename "boot.img-kernel".
Easiest way to replace the kernel is to take a kernel update zip for your device, un-zip it and rename the zImage file to "boot.img-kernel" and copy and replace the file of the same name in your directory.
Okay, now that's all done, we need to pack this back up into something that android can understand when it's being flashed. So we need to make a new boot.img from the files we have in our current directory.
First, we need to pack the ramdisk back up into it's original state, so again we need to use the Linux terminal. The command that will do this is this:
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
Remember the ../ is the path to the directory of your ramdisk, remember to remove anything that won't be used by the kernel as cpio will include EVERYTHING in the working directory.
Okay now that the ramdisk is back in it's original format we need to repack the kernel and ramdisk into the boot.img.
So back into the terminal we go and this time we're going to use the "repack-bootimg" perl script (as if that wasn't obvious enough). The command you will ise here is esentially the same to the one we used to split it, so:
"perl repack-bootimg.pl ../path to kernel ../path to ramdisk directory ../path to outfile"
And the boot.img is complete!
So if we look back to the ROM we are porting we can see that we need to put the boot.img into the root of the zip, this will hold true for almost every Android ROM. Next we need to replace some of the files which allow the hardware and keys to work. This is the easy part.
Go into the root of the zip and follow this path to the kernel modules; "/system/lib/modules" Delete all the files you find here.
Now take the kernel modules which came along with the kernel you added to the boot.img and copy them there. Next follow this path to the propietary hardware files;
"/system/lib/hw" Delete all the files you find here.
Again this as simple as taking the files from a ROM meant for your device and copying them into this directory. So what we've done there is added the kernel modules that we can set symlinks to in the updater-script and contain the modules needed for things like WiFi, bluetooth etc. The "/hw" directory as you can see contains the files which control the sensors and lights such as GPS and the accelerometer.
Next, we can look at making sure the hard and soft keys work, the files which contain the layout of your device keys can be found in;
"/system/usr/keylayout" and "/system/usr/keychars"
Touch only those 2 directories.
Delete all the files in here and copy the ones from your device (following the same directory) here.
Okay now to finish off we need to copy over the mount point information for your device and the WiFi drivers.
Follow this path; "/system/etc" and delete only these files and directories.
- vold.fstab
- /wifi
- /ppp
Now follow the same path in a ROM for your device and copy over these files.
Okay we're done!
Before flashing take a look and some guides which show you how to write updater-scripts, incase you need to create important symbolic links.
Happy Porting!
**mod edit** credits to JieeHD from the VillainROM team for this guide! original thread here: http://www.freeyourandroid.com/guide/porting-android
reserved for future......
Hey,how did i help in this?
PS:i m thinking of buying this phone.....is it any good?
i have both the galaxy sl and spice mi 410 i copied from your thread so had to give you credit even though you are not the original poster
spice mi 410 competely outshines galaxy sl so much so that i hardly use sl hooked to this at i.6ghz its lightning fast great plays any game hardly random reboots though average camera galaxy sl better
side note :if you could build succh a nice rom with sl god knows what good you can do with mi 410 please buy it haha
cranium rocks
oh cool............i had forgotten about that thread
2nd hand for 9999 only.................
Hey that's my tutorial... Hope it helps someone....
Sent from my SAMSUNG-SGH-I777 using xda premium
rdannar said:
Hey that's my tutorial... Hope it helps someone....
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
than credit to you i am just sharing with everyone "hope it helps someone"
Thank you!!! Will try too port a gt-I9100 rom to a gt-I9100G.
Hope it will be easy with this guide.
Dear Preyesh1.... Could you add the credit to the creator of this guide or at least you mention the url source because I've seen this guide just exactly as in this thread somewhere in the internet.
Except if this guide is pure of yours.
Just to remind...
Edited: Never mind... The creator has been here after all...
I have some questions:
so this means you can take the U9000 android 2.2.2 kernel and merge with ICS?
or does this only works with kernel coming from a GB build to another GB build?
It will help me cause I'm gonna use it soon
Sent from my Triumph using XDA
ziggy46 said:
It will help me cause I'm gonna use it soon
Sent from my Triumph using XDA
Click to expand...
Click to collapse
Hey are you going to port your rom to your device this will be great...!!
I wanna try this great tutorial
Sent from my Droid using Tapatalk
Nice plagiarism.
I mean look at that OP. You've selected the entire article, hit copy, hit new post here, hit paste then hit submit. That's plagiarism of the laziest kind you could have at the very least put some effort in, formatted the text, used code blocks etc.
My word.
edit:
preyesh1 said:
See our guide on how to set this up HERE
Click to expand...
Click to collapse
Hahahahaha.
I know this is very late, some of us might not use LG device anymore. Even LG is no longer in smartphone business. Sorry in case of double post, not checking out xda as much these days. This is not my work (credits to OP) but I stumbled across this site and it's probably unwise not to share the finding. So, here's the address:
h**ttps://m.cafe.naver.com/ca-fe/web/cafes/optimuslteuser/articles/838504?useCafeId=false
It provides you with what you need to create your own font to be used on LG device, and the good news is, it works!
Things worth mentioning :
1. You need JDK 8 installed, anything newer won't work. If you know the workaround using newer jdk, please be kind enough to share.
2. You can use G Translate (the site is in Korean) but it won't be very helpful other than give you a bit of background and so on. So basically you just :
a. Extract the folder, then put the font inside the folder
b. Run the .bat file
b. Type 'agree'
c. Type in 'the name of the font with the ttf extension. Then press enter
3. Rename the font because the ttf is included in naming
4. The preview won't work but applying will get the job done.
That's it, enjoy!
It is not wotking for lg g7
Hi, make sure you are on JDK 8, attached is a font created using the tool. If it works then make sure to follow above mentioned steps.
Thanks for sharing., works as expected!