[FAQ] GT540 Reference Thread | How-to's | Data2System method by Anton_ch ADDED!

---

~ FAQ | LG GT540 REFERENCE THREAD ~

.:: http://mygt540.com ::.

~ o ~

LG GT540 is equipped with 512Mb ROM (flash memory).
It is divided into sections:

* Boot (boot partition | 5 MB) - contains the kernel of linux system and the ram-disk image
* System (system partition | 245 MB) - contains built-in Android applications
* User (userdata partition | 138 MB) - contains custom applications / settings
* Cache (cache partition | 64 MB) - unnecesary files you need to clean often

~ o ~

START | NEWBIE

• [HOW-TO] Set up SDK/ADB/FASTBOOT on Ubuntu 11.04

• [HOW-TO] Set up SDK/ADB/FASTBOOT on Windows | Flash Android ROMs 2.1/2.2/2.3

• [HOW-TO] Create a EXT4 & SWAP partition on Windows / Linux

• [HOW-TO] Use ADB tool | Android Debug Bridge
  • [HOW-TO] Install LG IME Full
  • [HOW-TO] Change default fonts | Custom ROMs

• [HOW-TO] Use Fastboot tool | Bootloader

• [HOW-TO] Replace Files | Set permissions
  

__________________________________________________


RESTORATION | ADVANCED

• [FAQ] My Phone is bricked !!! | GUIDE

__________________________________________________

TECHNICAL TRICKS

• [TUTORIAL] Self-Assembly of Android OS Firmware

• [TUTORIAL] Data2System method by Anton_ch | Custom ROM's

• [HOW-TO] Fix MD5 mismatch | Nandroid restore

• [HOW-TO] Fix Russian Profile | Swiftdroid

• [HOW-TO] Change default low system sounds | Sound Scheme

~ Please user DO NOT POST IN HERE, LET'S KEEP THE THREAD CLEAN, PM me if you have a question or something to say. Thanks! ~

are Welcomed!!!

[HOW-TO] Set up SDK/ADB/FASTBOOT on Ubuntu 11.04

---

TUTORIAL #1

THANKS TO bloodychaos FROM XDA

I've been searching around the forums,the stickies and Google on how to install ADB in Ubuntu from scratch but I wasn't able to get a guide anywhere. What I found mostly are for Windows or little bits and pieces of info which did not cover the whole thing. Which is when I decided to grab some Tab and Mountain Dew, and Google my way through to make it work and share it to those who had trouble or no idea how to install it on Ubuntu.

When I'm writing this, I'm using Ubuntu 10.10 64bit to install and run everything. There was mentions of using Eclipse SDK while searching around, but I won't be touching on that. There's another guide for it at the end of my guide. I have yet to encounter any problems while using ADB in 64bit environment. I've tested it out on the 32bit platform as well and it works. It'll also work on SD and NAND versions of Android for the HD2, since it's my main phone. Also, this is my first time making a guide, so bear with me if there's any mistakes. I've checked the article a few times hoping that it's clear and easy to understand.

Step 1. Install JDK

You'll need to install JDK for ADB to work. If you have already installed JDK, I recommend reinstalling it again, just in case there are new updates or you have the older version.

Open Terminal and enter the following command(s), then enter your ubuntu login password followed by ‘y’ when prompted for yes/no.

$ sudo apt-get update

$ sudo apt-get install openjdk-6-jdk

Step 2. Download and Install Android SDK

Download the Android SDK. Obviously, choose the one for linux (android-sdk_r10-linux_86.tgz)

http://developer.android.com/sdk/index.html

Extract the android-sdk-linux_x86 folder from android-sdk_r10-linux_x86.tgz and put folder to your desired location. I recommend to put in home/username/ | When using the terminal the same path is described as ~/

Step 3. Choose packages to install

First of all go to ~/android-sdk-linux_x86/tools/
Right clic to android >> Properties >> Permissions
Make sure "allow executing file as a program" it's checked



In Terminal, type the following

$ cd ~/android-sdk-linux_x86/tools

$ ./android update sdk

The 'Android SDK and AVD Manager' window will appear (screencap below). If you are not a developer then just accept the first option to install and the rest reject. Once installation is finished, it will prompt you to restart the manager. Just click 'Yes' and close the manager





Step 4. Check your device's permission

Now head over to the platform-tools directory

$ cd ~/android-sdk-linux_x86/platform-tools

Check if you have permission for your device

$ ./adb devices

If you're getting the following, go on to Step 5.

List of devices attached
????????????    no permissions

If you're getting something like this or other random numbers with the word device next to it, congrats! You now could use ADB. Now go on to Step 7.

List of devices attached
0123456789ABCDEF    device

Step 5. Giving permission to your device

You'll need to create a certain udev rule. First off type the following in Terminal:

$ sudo gedit /etc/udev/rules.d/99-android.rules

Once the gedit window pops-up, type the following line

SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"

Here's a list of each vendor's ID. Source: http://developer.android.com/guide/d...ng/device.html

Save the file and exit out of gedit. Back in Terminal execute the following

$ sudo chmod a+rx /etc/udev/rules.d/99-android.rules
$ sudo restart udev
$ sudo adb kill-server

Then unplug your phone and plug it again
Now to check if it works

$ ./adb devices

You should be getting the following line or something similar:

List of devices attached
0123456789ABCDEF    device

Congrats! Now you can use ADB in Ubuntu! Now hop on to Step 6!

Step 6. Create path for ADB and Fastboot

NOTE: while using adb in Linux, you'll need to type ./adb to execute adb unless you create a path in ~/.bashrc.

$ sudo gedit ~/.bashrc

Add the following line at the very end of the file. Once you're done, save and exit.

# Android tools
export PATH=${PATH}:$HOME"/android-sdk-linux_x86/tools"
export PATH=${PATH}:$HOME"/android-sdk-linux_x86/platform-tools"

Then in a Terminal run this command to reload your .bashrc:

source ~/.bashrc

Now you can just run adb without put ./ before every command.

Step 7. Set up FASTBOOT

Download Fastboot file from here: http://www.mediafire.com/?uc8zvuoklr8qlmk

Move it to ~/android-sdk-linux_x86/tools/ folder
Right clic to Fastboot >> Properties >> Permissions
Make sure "allow executing file as a program" it's checked

Reboot in fastboot mode (bootloader), then plug your phone with USB cable to a computer
Open a terminal and type:

$ sudo -s
# fastboot devices
0123456789ABCDEF fastboot

NOTE: you must login as root to fastboot to work. If you get an error issuing the last command then most likely something went wrong while creating a path for fastboot in ~/.bashrc, then you should try with ./ statement before the command like this:

# ./fastboot devices
0123456789ABCDEF fastboot

__________________________________________________

* For more in-depth guide, try HowtoForge. Just found this guide today and I find it VERY useful and even have a good guide on Eclipse.

[HOW-TO] Set up SDK/ADB/FASTBOOT on Windows | Flash Android ROMs 2.1/2.2/2.3

---

TUTORIAL #2

HELLO I SEE THERE IS QUITE OF PEOPLE (NEWBIES) THAT ARE HAVING PROBLEMS WHILE FLASHING, MOST OF THE TIMES FROM STOCK 1.6 TO 2.1, SO I WANTED TO SHARE THIS TUTORIAL I MADE AND WOULD LIKE TO ALL OF YOU CONTRIBUTE IN SOMETHING MISSING OR NEW THINGS FOR THIS TUTO AND MAKE IT THE UPDATED AND BEST TUTO FOR DUMMIES OUT THERE . NO OFFENSE . JUST THAT THERE ARE LOTS OF PEOPLE NOT FAMILIARIZED WITH THIS KIND OF STUFFS.

THANKS TO CHKRLY FROM TARINGA! FOR THE BASIS OF THIS TUTORIAL, i added and quit some parts, translated and attached files...

WARNING: Any of these methods can brick your phone, im not responsible if that happens. READ ALL THE TUTORIAL FIRST. If your phone gets unresponsive DO NOT PANIC! we are here for HELP!

FIRST PART
(Flash from 1.6 to 2.1 with fastboot)

In this part we are going to flash an european ROM that comes with fastboot with the purpose of flash other ROMs that needs fastboot later...

1. Create a folder, download the KDZ Updater , the European ROM and the drivers for our LG GT540 and unzip them all in the same folder.
Install KDZ

Deactivate your FIREWALL and Antivirus if necessary

Install drivers:

UPDATE: Thanks to eoghan2t7 you can install LG GT540 drivers all in one:
METHOD1: NEW
LGGT540 ALL IN ONE DRIVER PACK.exe (32 bits users only)

METHOD2: OLD
Or install the drivers in the old normal way (32 & 64 bits users)

WINDOWS7 users: Right clic>> Run as administrator.
Also is very important you install the drivers inside the LG_SmartPhone folder:


2. On to the phone go to: SETTINGS >> APPLICATIONS >> DEVELOPMENT and activate the mode USB debugging , also check out this:
SETTINGS >> SD CARD AND PHONE MEMORY >> EXTERNAL ONLY MEMORY (not SECRET_, remove if), then plug you phone to the computer

3. Close all applications you do not need on the computer and run the KDZ_FW_UPD.exe (Windows 7 users: right clic>>start as Administrator)

4. Once in the program select from the TYPE list the 3GQTC option and then clic in the folder icon and select the European ROM(KDZ file) from the folder where you unziped, then press the button Launch Software Update

NOTE: It is important mention that while in the process dot not interrupt the program, unplug the phone or shutdown the computer

*If it stops in any of the processes and doesn't finish (processes doesn't get stuck for long), then unplug your phone, close the program, open it again plug your phone, and run it again.
*If that doesn't help eather, remove the battery, close the program, plug your phone to the computer, start the program and run the process again.
NOTE: various problems in the following procedure to update can occur if non of the above tips helped then try this:
Go to Device Manager in your computer>> right click on the LG Modem Android>> DISABLE / Modem>> LGE Virtual Modem>> DISABLE and then try FLASHING AGAIN

THE WHOLE PROCESS SHOULD TAKE 10 MINUTES

Once the program has loaded the ROM to the phone it will appear a leyend FINISHED, after that the phone will reboot and boot android 2.1 with fastboot.

SECOND PART
(Flash from stock 2.1+fastboot to custom 2.1/2.2/2.3...)

1. Download the following files:

- Google SDK tools, unzip and put the folder in C:\ drive

- Drivers for your computer recognize the phone in fastboot mode. Unzip and put the files inside the folder in C:\android-sdk (take a look of the 3th image)

INSTALL WITH YOUR PHONE PLUGGED:







... then next and it will install the drivers.

- Clockwork recovery (latest version) and place it in C:\android-sdk

- Download the ROM you want to flash for FASTBOOT NOT RECOVERY, UNZIP and place the .IMG FILES in C:\android-sdk

NOTE: It is RECOMMENDED that from stock 2.1 you flash to 2.2 and then to 2.3 and so on, this means not go directly to 2.3.3 as may cause your phone do not boot properly and also not login to recovery. This is not confirmed but some users have experienced this kinds of issues.

2. Shutdown your phone and Start it in fastboot mode (CAMERA+POWER BUTTON) hold the camera for 1 sec then add the power button . Wait few second you will see LG's logo then the screen will turn dark, CLEAN DARK SCREEN, just in that moment you are in FASTBOOT mode.

3. Flash rom by FASTBOOT mode:

Plug your phone to the computer and open a CMD terminal and type:

cd C:\android-sdk

4. Once inside the folder type ONE by ONE:

fastboot flash recovery recovery_clockwork_3.0.2.4_swift.img
fastboot -w
fastboot erase boot
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img
fastboot -w
fastboot reboot

THAT MY FRIEND IS A CLEAN INSTALL...

5. Once is rebooting fast login to recovery pressing POWER+HOME. Inside recovery select wipe data/factoryreset for reset the phone. Then select reboot, and that's it YOUR DONE!

NOTE: If you are flashing any ROM with data2system method then DO NOT WIPE DATA/FACTORY RESET, just reboot.

6. Set your phone as you like install all your apps and once you done reboot into recovery and go to backup & restore>> backup for create a backup of your entire phone.

[HOW-TO] Use ADB tool | Android Debug Bridge

---

TUTORIAL #3

You can find the adb tool in C:\<sdk>\platform-tools\ or C:\<sdk>\
*All the examples refers to /data/app path you can change to /system/app or any other path you need

Open a CMD terminal on Windows:
Start>>run>> type cmd>> click ok (WinXP)
Start>> in search box type cmd>> right click Run as Administrator (Win7)

Once opened type:

cd C:\<sdk>\platform-tools
adb devices
adb remount (from r/o to r/w)
-----------------------------------------------------
adb shell mount /system (if you only want to mount system)
adb shell mount /data (if you only want to mount data)

Installing an Aplication .apk

Put the .apk file into C:\<sdk>\platform-tools\ folder and type

adb install appname.apk

Uninstalling an Aplication

There is an uninstall adb commans that always shows failure!!!
So we are going to use Adb Shell:

adb shell
# cd data/app
# ls
# rm -r appname.apk
# ls
Ctrl+c to exit shell mode

You will not find this application, you just removed it!



Push & Pull commands

Pull:

adb pull /data/app/appname.apk

If you want to PULL all the files located in a folder then:

adb pull /data/app test

to pull all the .apk's located /data/app and save them into a folder that it will create in C:\Android-SDK\platform-tools named test



Push:

adb push appname.apk /data/app

If you want to PUSH all the files located in a folder then:

adb push test /data/app

to push all the .apk's located in C:\Android-SDK\platform-tools\test folder to /data/app



Close ADB

adb kill-server
exit

[How-to] Replace Files | Set permissions

---

TUTORIAL #4

When you need or would like to add or replace a file to our phone we need to set permissions.
In this tutorial we are going to use Root Explorer for this purpose, because is the "standar" file manager that comes with custom roms lately.

Apart of this, if you are having issues with applications for incorrect permissions then you might FIX permissions using ROM MANAGER application not RECOVERY (not recommended)

REPLACING A FILE:
in this example we are going to replace our old Music.apk for the newest Music.apk...
*Applies for replace any file

Before: After:


1. Backup your old Music.apk then uninstall it (I can do both with RootAppRemover.apk or Titanium Backup)
1. Plug your phone, mount your sdcard then download Music.zip
to your desktop
2. Put the Music.apk and libjumper.so into /sdcard/newmusic folder
3. Close the windows, unmount your sdcard, unplug your phone then go open Root Explorer application
4. Go to sdcard/newmusic/ >> press menu button >> Multi-select >> select Music.apk >> press copy button
5. Press back button and go to system/app/ >> press Mount R/W >> press Paste button



6. Look for the Music.apk you just pasted and press on it until a window pops up:



7. Select Permissions and change them to rw-r--r--

TO
It should look like this:


9. Repeat process from step 4-to-7 to replace libjumper.so but to /system/lib/ path

THANKS ARE WELCOMED!!!

[TUTORIAL] Self-Assembly of Android OS Firmware

---

TUTORIAL #5

* This tutorial was created for me after read from many sites and figure it out by myself and the result is a 100% fully working step by step tutorial.

* First of all you need to have installed Ubuntu then Follow this: [How-to] Set up SDK/ADB/FASTBOOT in Ubuntu 10.10

* Once everything is set and working download IMG_tools.zip then unzip in home/username/IMG_tools/

* When i mention ~/ means home/username/ but shorty

Proceed...


Extract boot. img

-To extract boot.img use extract_boot from ~/IMG_tools/boot
- Put boot.img file inside ~/IMG_tools/boot/ folder
- Open a terminal and type:

$ cd ~/IMG_tools/boot
$ ./extract_boot boot.img

- if you want to extract boot.img in another folder, for ex. in ~/ROM/ then the command is

$ ./extract_boot ~/ROM/boot.img

- You will get something like this
Page size: 2048 (0x00000800)
Kernel size: 2664916 (0x0028a9d4)
Ramdisk size: 966,485 (0x000ebf55)
Second size: 0 (0x00000000)
Board name:
Command line: mem = 214M console = tty0, 115200n8 androidboot.hardware = swift uart.mode = arm11_uart_disable crash = off
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
3210 block

Rebuild boot.img

-To rebuild boot.img use make_boot from ~/IMG_tools/boot
- Double click make_boot>> show


Compare info after cmdline with Command Line after extracted boot.img, if its different then modify the file.

- Once verified info type:

$ ./make_boot boot.img

- You will now see a boot-new.img file ready for flash

Extract system. img

-To extract system.img use unyaffs from ~/IMG_tools/system
- Put system.img and unyaffs file inside ~/IMG_tools/system/system folder
- Open the terminal and type:

$ cd ~/IMG_tools/system/system
$ ./unyaffs system.img

- Then cut system.img and unyaffs file and put them back to ~/IMG_tools/system

Rebuild system. img

-To Rebuild system.img use mkfs.yaffs2 from ~/IMG_tools/system
- Do not move mkfs.yaffs2 file
- Open the terminal and type:

$ ./mkfs.yaffs2 system system.img

Rebuild system. img [update.zip]
* works to sign .apk too

- If you have based your work on RUU file, you’ll have to create META-INF folder with the correct information and update scripts inside. If you have unpacked someone’s .zip, the META-INF folder should be already present. Update script might mention some files in the update, so if you have removed (or added new) files, the update script should be amended to reflect those changes. Please, get a few images from different developers and try to understand the correct internal structure.

Once you have something like this:



- Open the terminal and go where your <workdir> content is: META-INF, system, boot.img then type

$ zip -r9 update.zip *

-r9 tells the program to collect files recursively and use the maximum compression. If you omit “r”, the subfolders will not be included (bad, bad idea!), if you omit “9″ nothing bad will happens, but resulting file might be about 1% larger.

- Now to sign the zip file put sign folder and androsign file from ~/IMG_tools/sign/ to ~/*SDK/tools
- Go back to the terminal and type

androsign /<workdir>/update.zip

Odex Files

- What are those Odex files? Answer
- How to get rid of them?
Odex files depend on framework they are made for. To deodex an odex file use that how to
Then you may create a classes.dex file by executing the smali program on the "out" folder. You then rename it to classes.dex and add it to the .apk.
- How to create them?
Use dexopt-wrapper on device.
For deodex ODEX files, use this howto
Then you can create classes.dex file by running smali from your "out". Then rename it to classes.dex and add it to apk.

Porting another's devices ROM

Well, this part is simple smile_good.gif
- Extract system.img
- Extract boot.img
- Replace boot.img-kernel of the original Roma HTC Hero.
- Rebuild boot.img
- Collect update.zip (see how it's done in any Custom rum for Hero)
- Sign and flash.

Device should start, and even be able to call, but probably will not work WiFi, BT, trackball.

[HOW-TO] Fix MD5 mismatch | Nandroid restore

---

TUTORIAL #6

THANKS TO ihtfp69 FROM XDA!

To fix this is assuming you did not change the folder names and let Clockworkmod create them.

Checking MD5 sums... 
MD5 mismatch!

- Plug your phone to the computer
- Open a Terminal and type:

adb devices
adb shell 
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53 
# rm nandroid.md5 
# md5sum *img > nandroid.md5
# exit

* Substitute the final folder name for the backup you need to fix.

- Re-run the restore and everything should be fine.

NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.

[HOW-TO] Install LG IME Full

---

TUTORIAL #7

- Dowload LG_IME_data2system and unzip in desktop
- Open System folder and copy the 3 folders: app, lib2 and usr folders to C:\*SDK\platform-tools\
- Plug your phone to the computer
- Open a CMD terminal and type:

cd C:\*SDK\platform-tools
adb devices
adb remount
adb push app /system/app
adb push lib2 /system/lib
adb push usr /system/usr
adb kill-server
exit

- Unplug your phone
- Go to ROM Manager application and run Fix Permissions (DO NOT avoid this step, so you dont get FC's)

DONE!

[HOW-TO] Use Fastboot tool | Bootloader

---

- What is fastboot?

Fastboot tool is a program used to update the flash partitions in Android devices from a host (PC) over USB.
It allows you to perform flashing images (*.img) files to your device.
_________________________________________

- How do i get in Fastboot mode?

You can boot in Fastboot mode in two ways:

1. For 2.2 / 2.3 Android ROM:
Hold the power button until a window pops up | Select reboot >> bootloader >> OK

2. For any Android ROM
Shutdown the phone >> hold CAMERA + POWER buttons
_________________________________________

- How do i know im in Fastboot mode?

After you press the combo buttons and the phone starts you be able to see the LG logo and just after that the screen will clean and turn dark-blue, nothing else. If that happens congratulations! you are in Fastboot mode.
NOTE: it has been told that in some firmwares the fastboot mode screen turns out blank. If you experience that dont panic! you might want to try another firmware with the normal fastboot mode.
_________________________________________

- Usage of the Fastboot commands

NOTE: to start using Fastboot is assuming you already have installed SDK with all the tools

1. You need to place the *.img files you are going to flash into

C:\*SDK\tools\ (Windows)
Home/username/*SDK/tools (Linux)

2. Plug your phone with a USB cable to your computer

3. Open a Terminal (Windows|Linux) and issue the following commands:

fastboot erase recovery
------------------------------------
fastboot flash recovery recovery_clockwork_x.x.x.x_swift.img
fastboot -w
fastboot erase boot
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img
fastboot -w
fastboot reboot

* fastboot erase recovery | use when reinstalling clockwork recovery
* fastboot -w | is for wipe data/cache and make a factory reset

[HOW-TO] Fix Russian Profile | Swiftdroid

---

THANKS TO tejasdj12 FOR THIS FIX

There are 2 ways to Fix Russian Profile:

METHOD #1:

Copy the profiles.xml file to /data/system folder. Reboot.

* If the first method did not work then you have a second method

METHOD #2:

1. Open Root Explorer or any other file manager
2. Find /system/build.prop file and edit these sections:

'ro.product.locale.language=ru' to 'ro.product.locale.language=en'   
'ro.product.locale.region=RU' to 'ro.product.locale.region=US

3. Save the File
4. Reboot into recovery and wipe user data/factory reset. Reboot.