Develop Bugs

[GUIDE] Using ADB & FASTBOOT in OSX / Mac

Hi,
I thought I'd add this here because I've recently starting using OSX after building my own hackintosh out of PC parts. I got very fed up with Windows and the need for drivers all over the shop so I'm moved over now.
I've also just got into flashing my HTC Desire and it was made very easy by lots of the guys here. One thing that will always be useful when rooting and flashing your phone is ADB. There are lots of guides out there for ADB on Windows but I wanted to run in natively in OSX.
After a lot of research and a few failed attempts .... I've now worked out how to run ADB in OSX.
What you will need:
A Mac
USB cable
Android SDK for OSX- http://developer.android.com/sdk/index.html
At the time of writing this the version was "android-sdk_r08-mac_86" so please have a look at the above link and let me know if you can't find that same version.
So download the zip file and I would extract it to a folder where you are happy to keep it such as within your user home folder i.e. Macintosh HD/Users/{Your User Name} and for my mac it is Users/siedkins which is how I have my OSX set up.
Then open then still in Finder, open "android-sdk-mac_86" then "tools".
Now launch Terminal - ⌘ + space then type Terminal or Applications>Utilities>Terminal
Now drag and drop the file called "android" in the "tools" folder into your terminal window and you should see something like:
/Users/siedkins/android-sdk-mac_86/tools/android
Then hit enter - this should load Android SDK
Next go to Available Packages on the left and Android Repository > Android SDK Platform-tools, revision 1 -tick the box and hit "Install Selected"
It should download and install the Platform Tools which includes ADB !!!!
Now quit Android SDK after it has downloaded and go back into Finder. Now you should see a new folder "platform-tools" in the "android-sdk-mac_86" folder. Open that and you can now see a file called adb.
Now .... I am going to show you how to make your life a lot easier in Terminal to run ADB without having to navigate to the folder every time you want to launch it.
Go back to your Terminal window and type (or copy & paste):
Code:
cd ~
The screen should then look like
NAME_OF_YOUR_MACHINE:~ USERNAME$
For me I have:
Mac-Pro:~ siedkins$
Next, type
Code:
touch .bash_profile
to create your new bash / path file
Next, type
Code:
open -e .bash_profile
to open it in TextEdit.
Now into Text Edit please copy:
Code:
export PATH=${PATH}:
Then go into Finder and navigate your your "android-sdk-mac_86" folder. Then click on the "platform-tools" folder and drag and drop this into TextEdit at the end of the code above that you copied. Mine looks like:
export PATH=${PATH}:/Users/siedkins/android-sdk-mac_86/platform-tools/
Yours should look like:
export PATH=${PATH}:insert your path to the "platform-tools" folder in your Android SDK here
All you need is that one line. Then Save and exit TextEdit and then very importantly QUIT TERMINAL.
***** If you have issues being able to save the file at all then please jump to the bottom of the post*****
Now ........ to turn on USB Debugging in your handset Settings > Applications > Development > USB Debugging - ticked and also go to Settings > Connect to PC > Default connection type > Charge Only and also UNTICK "Ask me ..." there also. You can always go back here and change these settings back.
Now plug in your phone to a USB port. I noticed that if I plugged my phone into one of the standard USB ports on the front of my machine I couldn't see the phone further down the line and if I plugged it into a powered USB port on the front (I have an "akasa AK-ICR-08" which has a powered connector behind the 5 USB ports. But you guys will probably be using a MacBook or MacPro and there shouldn't be any issues with the power to your USB ports.
Now to launch ADB - re-open terminal (remember that you had quit it - very important!) then type in:
Code:
adb devices
And you should see:
List of devices attached
HXXXXXXXXXX device
where XXXXXXXX is your unique phone ID.
Now you can run all of your favourite ADB commands straight by typing:
adb shell
etc straight into Terminal. I won't go into that here as there are plenty of guides about what to do with ADB once it's installed!
Now you have ADB setup on your Mac and can run it without the need for installing HTC Sync - un-installing it - loading some modified drivers over the top !!!!
It all just works !!!!!!
Please drop me a line if you have any queries about this !
******************
If you are have user account issues such as Terminal or TextEdit says that you can't do anything then try adding "sudo" to the front of your terminal command as this will allow you to execute the account as a superuser or root user for OSX! ROOT!!! Note that you will have to enter your password to enable the superuser access rights and you won't see anything as you type in your password.
i.e. try:
Code:
sudo touch .bash_profile
then
Code:
sudo /Applications/TextEdit.app/Contents/MacOS/TextEdit .bash_profile
(slight change in the coding here to ensure that TextEdit opens
Or you could do:
Code:
sudo pico .bash_profile
This will open up the Pico text editor instead of TextEdit. Here you will have to type out all of the text then you press "ctrl+x" to exit and then you can save on the next screen. To check that has worked you can then open the file in terminal again and check it with the normal command:
Code:
open -e .bash_profile
******************
Please see post #37 for How To Use ADB Over WIRELESS !!!!
************************************************************************
EDIT - 27th JAN 2010
FastBoot
I've now found you all a precompiled version of Fast Boot:
http://developer.htc.com/adp.html
Please download and unzip the precompiled version for OSX to your "SDK/platform-tools" folder.
Rename the unzipped file from "fastboot-mac" just to "fastboot". You need to fix the permissions of the fastboot file using CHMOD in Terminal.
In Terminal navigate to your "SDK/platform-tools" folder and then type:
Code:
ls
You should see all of the files in your "platform-tools" folder such as adb, aapt, fastboot, etc.
Then type:
Code:
chmod 777 fastboot
PLEASE NOTE THAT I AM ASSUMING THAT YOU HAVE CHANGED THE FILE NAME ABOVE !
Now with the permissions fixed you should be able to run fastboot.
Connect your phone via USB and set to "charging only". Then turn off your phone and leave the USB in. Then hold the back key and then turn your phone on again. You will have a white screen with 3 skateboarding androids on.
Now in Terminal type:
Code:
fastboot devices
And you should see your unqiue phone ID! (Note that you have to be at that white screen with the skateboarders for the "fastboot devices" code to run!
Now you have a fully working fastboot !!!
Sorry this explanation is a bit short - I did write out a longer one but my browser crashed and I lost it all. However if you cannot follow the above then I think it's maybe best that you don't use fastboot as you could seriously brick your phone.
NOTE - I HAVE NEVER USED FASTBOOT TO FLASH A RADIO OR PHONE SO I PROBABLY WON'T BE ABLE TO HELP IF YOU GET ERRORS IN USING FASTBOOT OR FLASHING YOUR DEVICE ! The above information is how to shortcut the navigation to the folder. Please don't blame me if you break the recovery image of your phone!

Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks

dhoshman said:
Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks
Click to expand...
Click to collapse
which last step ?

dhoshman said:
Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks
Click to expand...
Click to collapse
What version of MacOS? Also are you sure your device is properly rooted? I'm assuming you are getting the error when typing "adb devices"?
EDIT: That's what I get for being distracted while typing this.. ;-)

The easiest way to get the sdk is by using homebrew, which is an amazingly useful tool. https://github.com/mxcl/homebrew
Code:
brew install android-sdk
It doesn't add adb to your path however, you have to do that manually by adding /usr/local/Cellar/android-sdk/r8/platform-tools to your path.
Hope that makes it a little bit easier.

I found that on my mac using terminal I have to always start the adb commands with a ./ otherwise it wouldn't work right. This might be common knowledge for some, but I'm a terminal newbie
So, for example:
./adb devices

Thanks for the walk through
This work great. I put the the SDK folder on the root of Macintosh HD and renamed it to AndroidSDK. Then in the .bash_profile my path was /AndroidSDK/platform-tools/ . I then made a backup of my SD card with adb pull from /mnt/sdcard to my local machine.

mun-key said:
I found that on my mac using terminal I have to always start the adb commands with a ./ otherwise it wouldn't work right. This might be common knowledge for some, but I'm a terminal newbie
So, for example:
./adb devices
Click to expand...
Click to collapse
Kind of weird. To me that would mean that you're path variable isn't setup correctly. Usually the ./ before a command means to run the command from the current directory and ignore the path variable.

It doesn't even have to be this complicated. Download the sdk, whatever files you want to push to your phone put it in the same folder. Then do the commands (./adb push). Simple.

Great and easy tutorial! Got it working in 5min ^_^

madj42 said:
Kind of weird. To me that would mean that you're path variable isn't setup correctly. Usually the ./ before a command means to run the command from the current directory and ignore the path variable.
Click to expand...
Click to collapse
Ok - that makes sense now. And reading Krisrk's reply, that's exactly how I did it.
On my device I only needed to push a single file. Don't really need adb anymore. Your post was like 12-hours too late for me though. I spent 3 hours trying to figure out why it wouldn't work, then saw the ./ in a youtube video. After that I was rooted with a new rom in minutes
thanks for all the great info guys

Just wanted to thank you! I already had ADB working on my Mac OSX but didn't have the "environment variables" in the .bash_profile. So now I can just use adb commands directly without going into the finder and find the adb!
Also, kudos for the very detailed guide with your own examples, that reads very well!

Thanks for the comments guys.
I know that you can navigate to the SDK folder and just run it from there but I thought that people might like the above guide to do the shortcut once and then never have to jump around folders again in terminal which is a bit of a pain. Plus my method removes the need for the "./" prefix.
anyways I'm easy I'm sure that everyone will have their own preferred method if you already use adb on OSX

i cannot get beyond the command:
touch .bash_profile
the terminal returns permission denied. what do i need to add or what am i doing wrong?

What type of user account do you have set up in OSX?
System Prefs > Accounts
Also what about trying the following in Terminal
Code:
sudo touch .bash_profile
And then enter the password for your user profile?
Any better?

Thanks for this!!!!!
Nobody ever shows macs love.
Sent From My HTC Evo 4G Using Tapa Talk Pro!

siedkins said:
What type of user account do you have set up in OSX?
System Prefs > Accounts
Also what about trying the following in Terminal
Code:
sudo touch .bash_profile
And then enter the password for your user profile?
Any better?
Click to expand...
Click to collapse
it popped up and asked my password, then it said i entered the wrong one and i never was asked this again. this is incredibly frustrating as i cannot even get it to work in windows
edit: ok got to the part where i bring up text edit, but it will not let me save. states i do not have permission to save. is there a way i can turn off this password crap for the time being? all i want to do is push files to my phone, i can't even get this far

Ok...
I'm trying not to look stupid, but for gods sake, im stuck at the first command. I copy paste cd~ and nothing happens. press enter nothing. I've been reading up on terminal and i still feel quite stupid considering how im stuck on step one
edit: got it! I got lost going back into the same terminal and not closing the android sdk window. there fore I was still in the sdk and not telling the computer anything. a dur. Opening a new terminal and doing all of the steps did the trick. Thanks for this btw!

thanks for the detailed guide. i've been looking all over the web for a guide to setup adb for MAC. followed the steps here and now, i'm able to use ADB on my macbook. YAY!!

monstereo said:
thanks for the detailed guide. i've been looking all over the web for a guide to setup adb for MAC. followed the steps here and now, i'm able to use ADB on my macbook. YAY!!
Click to expand...
Click to collapse
Hey just a random note, nice prof pic stig ftw

[CWMR ZIP] ICS Keyboard backlight fix

First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff.
This also fixes force-close related freezes by setting the default.prop to insecure and debuggable.
manual method
Now with CWM goodness!
DOWNLOAD LH2 file for official ICS RELEASE

Awesome!

does not work for me...

Worked perfect here, that fixes my only serious issue with the ICS rom.

I'm glad i was of some help . My first significant contribution to android. Will have to get back home to test it.

does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing

The_Bizzel said:
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
Click to expand...
Click to collapse
Overwriting the file won't work in my opinion. As these files are part of the boot.img and resides inside the ramdisk. So even if you change something in the ramdisk and then reboot you'll return to the original version.
I guess the only way is to flash the boot.img with the files inbuilt in to the ramdisk. So the boot.img posted by "Nardholio" should work.

Mhh just copying the .so file does not work for me to, even after wiping the caches.
I'm going to try this boot.img thing later this day.

Nardholio said:
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff. To fix it, just copy the version from Gingerbread over the ICS version and reboot. Note this requires root. The attached post contains the file you need and an optional boot.img mod that will fix force-close related freezes and will enable the keyboard light to be controlled by third party utilities.
http://forum.xda-developers.com/showpost.php?p=30591025&postcount=42
Click to expand...
Click to collapse
Didn't work for me at first either after I copied and pasted it. But when I went through and opened up a Terminal on my phone to install everything (I always thought I had to use Ubuntu on my computer for it. I don't know why I never even thought of using a Terminal on my phone to do editing on it and all...) and went through the steps on the link (didn't clear my cache), and it all works. Just a heads up for anyone who might be as slow as I was

Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium

Nardholio said:
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
confirmed working after both files were pushed. warning to others, do not wipe /dev/block/mmcblk0p9 if you have not verified that boot.img is on /sdcard via terminal emulator or adb shell:
Code:
cd /sdcard
ls
goodluck!

Can anyone help me with this via step by step?

I could use a little help as well
Sent from my SGH-I927 using xda app-developers app

Yea, i could use some help too, after re-writing over the existing file didn't work

OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.

Copying the boot.img worked for me
For those who having trouble, look at the Link, posted in the OP
How I did it:
Copy files to sdcard: Use a network enabled file manager or email or drop box (or, or, or) to get boot.img and lights.n1.so to /sdcard
Setup ADB: Google "xda setup adb"
Boot into CWMR: Reboot phone, holding power down (Link: Get CWMR)
Choose in CWMR:
Mounts > Mount sdcard
Mounts > Mound system
Execute Commands on pc
Open Shell/Cmd
Type: adb shell
Type: ls
you should geht a file listening of your root file system
Type: dd if=/dev/zero of=/dev/block/mmcblk0p9
Type: dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
Type: cp /sdcard/lights.n1.so /system/lib/hw/lights.n1.so
Choose in CWMR:
Wipe Cache
Advanced > Wipe dalvik cache
Reboot system
That was the steps as I remember, no guarantee don't brick your device if you do: use one-click-ics-leak-tool and start from scratch

ninthsense said:
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Click to expand...
Click to collapse
Worked! thanks abunch man

LuckRocks said:
Worked! thanks abunch man
Click to expand...
Click to collapse
You are welcome. I also did it just before posting the steps and glad that the biggest bug for the leaked ROM is now fixed.
I see that the lights go off very quickly unless you keep pressing something. It's related to "Touch Key Light Duration" under "display" in the settings. But i see only 1.5 seconds which is set currently and 6 seconds. If i change to 6 it's too much.
Does somebody know how to modify this value according to whatever we need ?

Hello ninthsense,
perfect tutorial, keyboard light is working now.
Thanks,
Mister.Knister

Hummm is their gonna b a flashable zip for this ?

[HOW-TO] ADB / ADB setup / APP Pushing / More coming [WIP][UPDATED 8/13/13]

HOW-TO
**Easy ADB / APP Pushing / More Coming Soon**
**DISCLAIMER** I accept no responsibility if you brick, blow up or burn up your device, you are choosing to follow this and making your own decision**​
I have been a long time android user and forum user. The goal here is to create a simple How-To guide for some of you new to android or just new to flashing. This stems from myself being on these forums and helping users fix and troubleshoot things. My goal is to give you some basics to help with testing or troubleshooting and to teach you a thing or two. There will be several sections and updates along the way. The Note 2 will be used as the device, but these can be done on most other devices as well.
Click to expand...
Click to collapse
**Easy ADB**​Thanks @kennyglass123, @CNexus and @gruesomewolf
Code:
This was thought of the other night when kennyglass123 and CNexus
were trying to get recovery to mount storage. I had a idea, Why not
make a simple way to get a ADB log when trouble shooting, instead
of using an app from the market. Plus it will pull a log upon boot, ever
had it where your testing something and it wont boot and the Developer
wants you to get a log, but you either don't have ADB or know how to
use ADB. This is for you!! Thanks goes to Kenny Glass, CNexus for the
idea and Gruesomewolf for the bat file edit.
What you need
Windows PC
Android device
Easy ADB.zip attached to this post
Whats included
Your basic ADB parts to be able to run without needing the SDK installed
LOG.bat file
Reboot.bat (Reboots device)
Recovery.bat (Sends device to recovery)
Download mode.bat (Sends device to download mode (ODIN mode))
How to record log cat using LOG.bat
You will download the zip
Extract to your desktop for easy access
Plug your device in to your PC
Open the ADB folder
Right click the LOG bat file, select run as admin (might not need to)
It will open a command window
Select ANY key to continue or control-c to quit
Wait for it to return to press any key to continue
Now you will have a text file called LOG, that is you LOG cat using ADB
You are now done and can send it to whomever or read it over yourself.
**Pushing system apps (Root Needed) (Will be posting screencasts of this also)**​
Have you come across someone posting something or telling you to push this app? I know I push them all the time. This can be used for MORE than just apps!! You can push just about everything. This will cover pushing a system app to the /system/app folder AND pushing a framework.jar to /system/framework folder. I will cover this using Root Explorer (paid) and ES File (free)
Click to expand...
Click to collapse
Code:
What you need
Android device
A file explorer with root access (Root Explorer, ES File or any others)
Whatever file, apk or etc you need to install
How to push a system app
Download Root Explorer or ES File from the store
(Root Explorer Instructions)
Open Root Explorer
Grant SU permissions
Navigate to the app you are going to be pushing (click + at bottom of screen to add EXT SD card tab)
Long press apk
Select copy
Top left tab says root, click and scroll to system folder, click and then click app folder
Bottom of screen says copy here, select that
Now scroll to the apk you just copied there and long press it
Select permissions, change them to only having the first vertical row and top of middle row checked (Attached Screenshot)
Click OK
Press home button
Now reboot to recovery and wipe cache and dalvik cache, then reboot.
(ES File Instructions)
Open ES File
Top left is a device/globe icon
Select tools, root explorer, Mount R/W
Grant SU permissions
Click device/globe
Select Local and then the SD card where the apk your wanting to install is located
Go to the folder when the apk is
Long press it and select copy
Now press the device/globe again and select local and then device
Scroll to system folder, click it
Now click app folder
Bottom of the screen, select paste
Scroll to the apk you just copied and long press it
Bottom right is more, select that then properties
Now you will change permissions to first vertical row and top middle checked only (attached Screenshot)
Click OK
Press home button
Now reboot to recovery and wipe cache and dalvik cache, then reboot.
Code:
Pushing System framework and other system files (Root Needed)
[Notice you will move to system folder and change permissions there, So if the device reboots or things lockup, you have already changed permissions and can just go to recovery and do your wipes]
(Root Explorer Instructions)
Open Root Explorer
Grant SU permissions
Navigate to the file you are going to be pushing (click + at bottom of screen to add EXT SD card tab)
Long press the file name
Select copy
Top left tab says root, click and scroll to system folder
Bottom of screen says copy here, select that (Place file here fist so you can change permissions now)
Now scroll to the file you just copied there and long press it
Select permissions, change them to only having the first vertical row and top of middle row checked (Attached Screenshot) (or if there is different permissions change accordingly)
Click OK
Scroll to the file you installing
Long press and select MOVE
Now open the folder or folders the file belongs in (framework for framework.jar for example)
Bottom left click move here
Press home button
Now reboot to recovery and wipe cache and dalvik cache, then reboot.
(ES File instructions)
Open ES File
Top left is a device/globe icon
Select tools, root explorer, Mount R/W
Grant SU permissions
Click device/globe
Select Local and then the SD card where the file your wanting to install is located
Go to the folder where the file is
Long press it and select copy
Now press the device/globe again and select local and then device
Scroll to system folder, click it
Bottom of the screen select paste
Scroll to the file you just copied and long press it
Bottom right is more, select that then properties
Now you will change permissions to first vertical row and top middle checked only (attached Screenshot)(or if there is different permissions change accordingly)
Click OK
Scroll to the file your installing
Long press it and select cut
Now open the folder or folders the file belongs in (framework for framework.jar for example)
Bottom of the screen select paste
Press home button
Now reboot to recovery and wipe cache and dalvik cache, then reboot.
**Coming Soon**
Code:
How to remove system apps before flashing (Debloating)
How to add your own apps to a rom before flashing
Some of you know me and that I have ported "Goodness Noteworthy" to Verizon, T-Mobile and AT&T on the Note 2, So I may do a guide on porting roms from or to other carriers. Although I have not tried a International rom yet.
If you have suggestions or things you would like to see here, please post or PM me.​

[HOW-TO] ADB / APP Pushing / More coming [WIP]
Setting up JDK and SDK for ADB use.
Whats is ADB?
ADB or ANDROID DEBUG BRIDGE is a command-line utility that is often used to communicate over the debug channel with a connected phone or virtual device (emulator). ADB can control your device over USB from a computer, copy files back and forth, install and uninstall apps and more...
Click to expand...
Click to collapse
What is needed
Windows PC (using Win7 64bit as example)
Java JDK HERE
Android SDK HERE
Android device
Click to expand...
Click to collapse
**Setup for Java JDK**
Download the Windows x86 or x64 .exe from HERE . Run the exe and let it install to default location​
**Error that SDK does not see Java installed**​
Code:
I and many others have had to create a Enviroment Variable so the Android SDK will see the Java JDK.
After java has installed
Click start menu
Right click computer
Select properties
Top left at the bottom of the list is Advanced System Settings, select that
System properties will open and bottom right will be a Enviroment Variables button, select that
A popup will apper (Enviroment Variables)
Select New System variables (bottom section)
Variable name will be JAVA_HOME, case sensitive
Variable value will be C:\Program Files\Java\jre7
Select OK
Select OK again and it will close Environment Variables window
Now in the System Properties window, if the apply button on bottom right is not clickable, we need to make it clickable
So what I do is make a small change to the computer name tab, I just delete one letter from the name and the type the
same letter (you do not actually need to change the name) and the apply button is now clickable, do so.
Now you might want to reboot your PC
Now that's set for when you go to install SDK it will see Java.
**Now to install Android SDK**​Download the SDK from HERE. Towards the bottom of the page is "Download other platforms", select that. Scroll to "SDK Tools Only" section and in the Windows section select the installer.exe. Now you double click and run the installer​
**Setup Android SDK**​
Code:
Open this file path C:\Program files (x86)\Android\android-sdk and double click SDK Manager
It will open, top left is a Tools folder which has "Android SDK Tools" and "Android SDk Platform-tools" in it, check mark all 3 boxes
Bottom right is Install packages button, click it and accept liscences
Now you can navigate to the platform-tools folder and you will see adb now
Make sure you have you device drivers installed which I hope you would have already
Open settings on your device, scroll to Developer options and enable USB debugging
Plug device into PC and let drivers update/install
Now in the window where adb is, press shift+right click and select "Open command window here"
Type adb devices, if you have a device connected and it does not return a device, you need to install again.
If it does return a device you now can use adb for a veritey of functions, some of which I will cover.
***Tomorrow I will add some ADB commands along with what their functions are***​

Nice Thread, we be a huge help to many. :good:

Yea buddy good looking out
Sent from my SPH-L900 using Tapatalk 4

Nice...thx for sharing I also use android commander but will definitely give this a go.
Sent from my SPH-L900 using Tapatalk 2

Whoa, how did I miss this? Thanks for sharing.

Going to try to add some ADB commands tomorrow as is my next day off. I'll get the screen shots and screen casts done tonight.

Has anyone even used the easy adb or linked someone on how to push a apk?

Post 2 has been updated with how to setup ADB and going to add some commands and what their functions are.

Nice work BTR! Thanks for putting this together!

Awesome now even I can do it Thanks BTR
Sent from my SPH-L900

great resource
Thanks for a very helpful resource especially a newbie like me can use

Sir... where can I get the commands you talked about earlier???

[SS/DS] Deodex 4.3 Firmware on LOCKED BOOTLOADER (NOOB FRIENDLY)

Hey guys this is a noob-friendly tutorial on how to deodex stock 4.3 Firmware on a locked bootloader. This tutorial is for windows only, im sorry, that's what i have.
Requirements:
1. A fully rooted xperia M.
2. Busybox installed
3. Winrar
4. A brain
5. Time and patience.
BEFORE WE START, MAKE SURE YOU HAVE INSTALLED BUSYBOX:
1. Go to playstore.
2. Search busybox
3. Download the one by stericsson, not busybox x, not anyother busybox. If you are using busybox x or something else. This app will replace the one you downloaded so do it anyway.
4. Open the app
5. Click normal install
6. After installation, reboot.
PART 1:
Here i will show you how to setup adb as a variable. This is NOT optional.
1. Go to this website: http://developer.android.com/sdk/index.html
2. Scroll down
3. Click download for other platforms.
4. Go to the sdk tools only list and download the zip for windows 32&64 bit. NOT THE EXE, THE ZIP.
5. After downloading is finished, right click on the file and click "extract files..."
6. Click the "C:\" directory and the extract.
6.1. Download this file: http://www.mediafire.com/?d5wj9bslikmf53d
6.2. Extract it into the root of the android-sdk-windows folder, in the "C:\" directory.
7. After thats done, Right click on "Computer" ("my computer" for windows xp)
8. Click "properties"
9. Click on the advanced tab
10. Click environment variables
11. double click on the text entry named "Path" in the lower list box
12. At the end of it, add: ";C:\android-sdk-windows\platform-tools" (without quotation marks)
13. Click on OK to exit out of the dialog
14. then OK again to get out of My computer's properties
15. Reboot computer.
PART 2:
Here i will show you how to deodex your firmware.
16. For both single sim download this: http://d-h.st/VWr
For C2004 download this: https://www.dropbox.com/s/90qbypc36kde8y9/deodex_c2004_dual.zip
For c2005 download this: https://www.dropbox.com/s/mkzfnt05vhwjcta/deodex_c2005__Latest.zip
17. Extract to anywhere, the file for you from the above links.
18. In the extracted folder open system
19. Take both app and framework folders and paste them onto your desktop.
20. Rename the app folder to done_app
21. Rename the framework folder to done_framework.
22. Connect your phone to computer via usb
23. Copy the done_app and done_framework folders to the root of your external sd card. So these files can be found at /ext_card/done_app and /ext_card/done_framework.
24. disconnect phone
25. On phone, go to settings
26. Click developer options
27. Enable usb debugging
28. Click revoke usb debugging authorisation, then ok
29. Connect phone to pc again
30. On pc, Click start
31. Click run
32. Type cmd in the box, then ok
33. A command prompt window should open up.
34. Type adb shell, and hit enter. If it says that your phone is unauthorised, then check your phone, grant the computer permissions to use adb.
35. Type adb shell and hit enter again if you got the unauthorised error. This should start daemon. If you didn't get the unauthorised error, dont type it again.
36. Now type these commands line by line, hitting enter as you type each line, NOT all of them at the one go. Copy and paste would be better than typing them.
su
stop
mount -o rw,remount /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /ext_card/done_app/* /system/app/
cp /ext_card/done_framework/* /system/framework/
mount -o ro,remount /system
reboot
39. When you're phone reboots itself, you will have a fully deodexed
Stock firmware.
TROUBLESHOOTING (MUST READ THIS!!!!) :
1. If you got an error like system is busy when typing in the second last command, wait a minute then retype it. If it happens again after you retype it then run the STOP command again and retry.
2. If settings app force closes after you deodex, download this on your phone: http://www.mediafire.com/?ygyuln0heu25qb9. Extract it using a file manager. In the extracted folder, open system then app then move all three files there to /system/app overwriting the old settings app. Set all three files' permissions to rw-r-r. Reboot. It should now work fine.
3. If any other of your apps give a force close, then uninstall and reinstall them. This is very unlikely though, none of your apps should give a force close error.
CREDITS: @paper13579 for creating this thread and editing the code a little bit. A big thanks to @gamer649 who showed me the method to deodex. @arshh19 for providing deodexed files for single sim. @stalin.sk2 for providing deodexed files for C2004 and C2005. @ansebovi for creating the moddified settings.apk
Sent from my C2004 using xda app-developers app

thks bro but one Mistake = brick So until ı hava à Lots öf money., i cant RİSK that.
...... Bull**** this SwiftKey Keyboard ı cant close auto Fix.
Sent from my C1905 using XDA Premium 4 mobile app

abuzer3 said:
thks bro but one Mistake = brick So until ı hava à Lots öf money., i cant RİSK that.
...... Bull**** this SwiftKey Keyboard ı cant close auto Fix.
Sent from my C1905 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Bro, i gave you this guide step by step, you don't need to figure anything out yourself. It's all done for you. It works, trust me, i used that exact procedure on my permanently locked bootloader and ut worked. Same for other people
Sent from my C2004 using xda app-developers app

Thanks for this thread it's very helpfull but It's not so noob friendly. ADB won't work with your setup guide because adb.exe is placed in different location. In my case proper location is: C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools but it's sdk version/os type related.

iks8 said:
Thanks for this thread it's very helpfull but It's not so noob friendly. ADB won't work with your setup guide because adb.exe is placed in different location. In my case proper location is: C:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools but it's sdk version/os type related.
Click to expand...
Click to collapse
You downloaded the wrong package
Is you read it properly, you would have realised that this is what i wanted you to download it from here http://developer.android.com/sdk/index.html#download. Scroll down. Click download for other platforms. Scroll down to sdk tools only. Click the first windows zip package. It says all of that in the guide
Sent from my C2004 using xda app-developers app

paper13579 said:
You downloaded the wrong package
Is you read it properly, you would have realised that this is what i wanted you to download it from here http://developer.android.com/sdk/index.html#download. Scroll down. Click download for other platforms. Scroll down to sdk tools only. Click the first windows zip package. It says all of that in the guide
Sent from my C2004 using xda app-developers app
Click to expand...
Click to collapse
Yes, you're right. Sorry xD

iks8 said:
Yes, you're right. Sorry xD
Click to expand...
Click to collapse
No problem bro.
Sent from my C2004 using xda app-developers app

When i download the zip you said to download, there is no adb in folder \tools, just a txt file saying that adb has been moved to an other directory. Do you have a direct link where i could download the right zip ?
PS : Sorry for my bad english

krarche said:
When i download the zip you said to download, there is no adb in folder \tools, just a txt file saying that adb has been moved to an other directory. Do you have a direct link where i could download the right zip ?
PS : Sorry for my bad english
Click to expand...
Click to collapse
This is the .zip what you are told to download. I've just had a look in my SDK folder and it is the same, have you got a platform-tools folder?

No, no platform-tools folder

krarche said:
No, no platform-tools folder
Click to expand...
Click to collapse
Download the .zip I'm attaching to this post and then extract it in the root of the SDK folder. So you can choose between going to platform-tools and tools. Once you have done that edit the path so instead of it finishing with /tools it will finish with /platform-tools.

That worked ! Thanks for your help

krarche said:
That worked ! Thanks for your help
Click to expand...
Click to collapse
Not a problem, I have the entire ADT and SDK so I have every file Remember to hit the thanks button for me and paper13579.

Sorry, i just saw your comments. did i miss something in my guide that i should add?
Sent from my C2004 using xda app-developers app

paper13579 said:
Sorry, i just saw your comments. did i miss something in my guide that i should add?
Sent from my C2004 using xda app-developers app
Click to expand...
Click to collapse
In the zip you're saying to download in your guide, adb is missing in the folder \tools

Hi bro can make tutorial for unlocked bootloader to.thx

YsfIsma said:
Hi bro can make tutorial for unlocked bootloader to.thx
Click to expand...
Click to collapse
Bro there is already a tutorial for unlocking bootloader, here it is(for dual Sim) http://forum.xda-developers.com/showthread.php?t=2484622
For single sim- http://forum.xda-developers.com/showthread.php?t=2650510
Sent from my C2004 using Tapatalk

paper13579 said:
Hey guys this is a noob-friendly tutorial on how to deodex stock 4.3 Firmware on a locked bootloader. This tutorial is for windows only, im sorry, that's what i have.
Requirements:
1. A fully rooted xperia M.
2. Winrar
3. A brain
4. Time and patience.
PART 1:
Here i will show you how to setup adb as a variable. This is NOT optional.
1. Go to this website: http://developer.android.com/sdk/index.html
2. Scroll down
3. Click download for other platforms.
4. Go to the sdk tools only list and download the zip for windows 32&64 bit. NOT THE EXE, THE ZIP.
5. After downloading is finished, right click on the file and click "extract files..."
6. Click the "C:\" directory and the extract.
6.1. Download this file: http://www.mediafire.com/?d5wj9bslikmf53d
6.2. Extract it into the root of the android-sdk-windows folder, in the "C:\" directory.
7. After thats done, Right click on "Computer" ("my computer" for windows xp)
8. Click "properties"
9. Click on the advanced tab
10. Click environment variables
11. double click on the text entry named "Path" in the lower list box
12. At the end of it, add: ";C:\android-sdk-windows\platform-tools" (without quotation marks)
13. Click on OK to exit out of the dialog
14. then OK again to get out of My computer's properties
15. Reboot computer.
PART 2:
Here i will show you how to deodex your firmware.
16. For both single sim download this: http://d-h.st/VWr
For C2004 download this: https://www.dropbox.com/s/90qbypc36kde8y9/deodex_c2004_dual.zip
For c2005 download this: https://www.dropbox.com/s/mkzfnt05vhwjcta/deodex_c2005__Latest.zip
17. Extract to anywhere, the file for you from the above links.
18. In the extracted folder open system
19. Take both app and framework folders and paste them onto your desktop.
20. Rename the app folder to done_app
21. Rename the framework folder to done_framework.
22. Connect your phone to computer via usb
23. Copy the done_app and done_framework folders to the root of your external sd card. So these files can be found at /ext_card/done_app and /ext_card/done_framework.
24. disconnect phone
25. On phone, go to settings
26. Click developer options
27. Enable usb debugging
28. Click revoke usb debugging authorisation, then ok
29. Connect phone to pc again
30. On pc, Click start
31. Click run
32. Type cmd in the box, then ok
33. A command prompt window should open up.
34. Type adb shell, and hit enter. If it says that your phone is unauthorised, then check your phone, grant the computer permissions to use adb.
35. Type adb shell and hit enter again if you got the unauthorised error. This should start daemon. If you didn't get the unauthorised error, dont type it again.
36. Now type these commands line by line, hitting enter as you type each line, NOT all of them at the one go. Copy and paste would be better than typing them.
Su
Stop
mount -o rw,remount /system
rm /system/app/*.odex
rm /system/framework/*.odex
cp /ext_card/done_app/* /system/app/
cp /ext_card/done_framework/* /system/framework/
mount -o ro,remount /system
Reboot
39. When you're phone reboots itself, you will have a fully deodexed
Stock firmware.
TROUBLESHOOTING (MUST READ THIS!!!!) :
1. If you got an error like system is busy when typing in the second last command, wait a minute then retype it. If it happens again after you retype it then run the STOP command again and retry.
2. If settings app force closes after you deodex, download this on your phone: http://www.mediafire.com/?ygyuln0heu25qb9. Extract it using a file manager. In the extracted folder, open system then app then move all three files there to /system/app overwriting the old settings app. Set all three files' permissions to rw-r-r. Reboot. It should now work fine.
3. If any other of your apps give a force close, then uninstall and reinstall them. This is very unlikely though, none of your apps should give a force close error.
CREDITS: @paper13579 for creating this thread and editing the code a little bit. A big thanks to @gamer649 who showed me the method to deodex. @arshh19 for providing deodexed files for single sim. @stalin.sk2 for providing deodexed files for C2004 and C2005. @ansebovi for creating the moddified settings.apk
Sent from my C2004 using xda app-developers app
Click to expand...
Click to collapse
I did as indicated but I'm not getting through the Su command!

pedroj666 said:
I did everything you say but I'm not getting through the point 30!
I downloaded the SDK Tools Only for other platforms and platform-tools. Unzipped the sdk and moved the "android-sdk-windows" folder to the root of pc c: \.
After that unzipped platform-tools folder and moved into android-sdk-windows.
After that I went to "environment variables" and added the "Path" in the lower box the list you have indicated (C: \ android-sdk-windows \ platform-tools).
did the remaining steps in sony M but when I get to step 30 nothing appears on the pc!
Click to expand...
Click to collapse
Ok, first of all, don't quote the full thread from he OP. Second, step 30 is telling you to press start. What do you mean y don't know his to get past this step. It's as basic as it can get
Sent from my E15i using xda app-developers app

paper13579 said:
Ok, first of all, don't quote the full thread from he OP. Second, step 30 is telling you to press start. What do you mean y don't know his to get past this step. It's as basic as it can get
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
Ya sorry xD!
I have noticed this but now my probelema is not this! I can not run the command Su. Give me the error "not found".

[GUIDE] Unlock LS980 ZVD (KK 4.4.2) [UPDATED 8/10/14]

Ok I successfully unlocked ZVD (KitKat 4.4.2) and thought I should share my steps in case anyone else was having the same issues as me which was mostly the systemui and home processes crashing on a loop.
First insert the SIM card you would like to use in the LS980. Then download and flash the stock firmware LS980ZVC_12.zip with the LG Tool -> http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Download the ZVD update - > http://www.mediafire.com/download/s5dqwo1cbe68ckb/LS980ZVC_12-LS980ZVD_19_update.zip (Do not flash this OTA update from a rooted rom or custom recovery!)
After flashing ZVC, set the phone to charge only and enable USB debugging by becoming a developer. Go to About Phone->Software Information and keep clicking "Build number" until it says you are a developer. Then go back to the main settings and you will now see "Developer options" and can enable USB debugging in there.
After enabling USB debugging choose charge only and when the RSA Key fingerprint window pops up make sure you check "Always allow from this computer" and then click OK.
Next using the ADB tools, reboot into recovery mode to apply the ZVD update.
Code:
adb reboot recovery
Select "apply update from ADB" with the volume buttons then press the power button. Wait 5 seconds then enter the following command.
Code:
adb sideload path_to_file/LS980ZVC_12-LS980ZVD_19_update.zip
After the update finishes select "reboot system now".
Next turn on airplane mode and root the phone using IO Root -> http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Next install SuperSU and BusyBox. Make sure you open SuperSu to update the SU binary and open BusyBox and install the busybox files.
*OPTIONAL INSTALL TWRP*
Next use ADB to install AutoRec -> http://forum.xda-developers.com/showthread.php?t=2715496.
Code:
adb install path_to_file\LS980_AutoRec.apk
Open AutoRec and flash the new patched kernel and recovery and then reboot. If you get white lines after rebooting, read the warning the OP has posted for the fix. I suggest here you take the time to make a backup and copy the EFS to your computer just in case.
*knock code feature will no longer work
*flash this kernel to enable knock code again and much more - > http://forum.xda-developers.com/showthread.php?t=2725023
*OPTIONAL END*
Now using ADB again, enter the following commands.
Code:
adb pull /system/build.prop
adb shell
su
After entering "su" check your phone to grant SuperUser permission to ADB. Aftering granting su to ADB, exit adb shell.
Code:
exit
exit
Next using Total Commander and the files from here -> http://forum.xda-developers.com/showthread.php?t=2655133 copy all the contents of the "carrier" folder to your phones "/carrier/" directory and choose "overwrite all". I like to delete the "legal.db" first this way I know the copy was successful when I see the new file listed. Do not delete any other files before copying the files over since we want to keep the file and folder permissions and owners of the originals. If Total Commander fails to copy the files over to the phone then you can use a root explorer app to do so.
Now edit the build.prop that you pulled from the phone with a program like Notepad++ since it will save the file for use with linux and not windows. Do not edit the build.prop or copy it back to the phone with any apps on the phone, this is what was causing the crashes for me.
Change the following lines
Code:
ro.carrier=unknown
ro.build.target_operator=SPR
persist.service.crash.enable=0
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
to
Code:
ro.carrier=spr
ro.build.target_operator=spr
persist.service.crash.enable=1
ro.telephony.default_network=0
telephony.lteOnCdmaDevice=0
*ro.carrier and ro.build.target_operator can bet set to "TMO", "ATT", or "spr".
*"TMO" and "ATT" do not correctly display the signal strength in the status bar.
Save the build.prop and use ADB to push it to the sdcard.
Code:
adb push build.prop /sdcard/
Now here is where we have to manually mount the system partition as RW and copy the build.prop over since all the root explorer apps seem to also cause the crashing issue.
Code:
adb shell
su
mount -o remount,rw /system
cp /sdcard/build.prop /system/
mount -o remount,ro /system
reboot
After the phone reboots it should be unlocked. Verify with Radio Switcher that your preferred network type is "WCDMA preferred", if not then change it to "WCDMA preferred". Now add your APN using Tweakker APN INTERNET MMS. If your APN doesn't stick, delete /data/data/com.android.providers.telephony/databases/telephony.db and reboot then add your APN again.
*To remove Bloatware add ".bak" to the following system applications names located in /system/app/ and /system/priv-app/ folders.
Activation.apk
OmaDmclient.apk
SPR_Skyfire_Observer.apk
SPR_Skyfire_Toolbar.apk
SprintExtensionProvider.apk
SprintID.apk
SprintTouch.apk
Vtt-Sprint.apk
xtra_t_app.apk
Zone-Sprint.apk
WIFIOffloader.apk
Click to expand...
Click to collapse
*To fix the issue of the com.android.phone process crashing when you don't dial a 1 in front of the number edit the /data/data/com.android.providers.settings/databases/settings.db file with a SQLlite editor and change in the "system" table "assist_dial" and "assist_dial_init_db_check" to "0". If you don't see those 2 rows then you can add them instead.
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db
exit
exit
adb pull /sdcard/settings.db
sqlite3 settings.db
UPDATE system SET value='0' WHERE name='assist_dial';
UPDATE system SET value='0' WHERE name='assist_dial_init_db_check';
.exit
adb push settings.db /sdcard/
adb shell
su
cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
chown system:system /data/data/com.android.providers.settings/databases/settings.db
reboot
*To disable OTA updates and notifications rename the following files
/etc/security/otacerts.zip
/system/app/LGFOTA.apk
Click to expand...
Click to collapse
to
/etc/security/otacerts.zip.bak
/system/app/LGFOTA.apk.bak
Click to expand...
Click to collapse
*To replace the Sprint boot/shutdown animations and sounds with the LG default ones download these files -> https://www.mediafire.com/folder/cmb6jn7z7osmf/LG_G2_Boot_Animation
copy and overwrite the following files to /system/media/
bootanimation_sprint.zip
shutdownanimation_sprint.zip
Click to expand...
Click to collapse
copy and overwrite the following files to /system/media/audio/ui/
PowerOff_Sprint.ogg
PowerOn_Sprint.ogg
Click to expand...
Click to collapse
*LG G3 Theme for G2 -> https://play.google.com/store/apps/details?id=com.lge.launcher2.theme.rocketg3&hl=en
Thanks to all those people who contributed to this. :victory:

Thanks for the guide, working find for me and LS980, mms msg not working, propably i have error on APN settings, and signal bar min or max signal is 1 bar only....

MakisPgr said:
Thanks for the guide, working find for me and LS980, mms msg not working, propably i have error on APN settings, and signal bar min or max signal is 1 bar only....
Click to expand...
Click to collapse
Info and fix about the 1 signal bar bug is located in the guide above. Your mms issue is most likely a APN mistake. Make sure your data is working.
Sent from my LG-LS980 using XDA Premium 4 mobile app

This method worked on my ATT sim card I dont need to dial a 1 in front of #. but didnt work on my Lycamobile simcard and pageplus. still need to dial 1 infront of nuber.
thanks.
来自我的 LG-LS980 上的 Tapatalk

Can you attach a logcat of it crashing when you dial please
Sent from my LG-LS980 using XDA Premium 4 mobile app

jsergio123 said:
Info and fix about the 1 signal bar bug is located in the guide above. Your mms issue is most likely a APN mistake. Make sure your data is working.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes you are right about 1 bar signal, didn't notice, and i fix my mistake settings on APN and mms now works perfectly ... Thank you very much

jsergio123 said:
Can you attach a logcat of it crashing when you dial please
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry, I dont know where is it.

ahqiu said:
sorry, I dont know where is it.
Click to expand...
Click to collapse
adb logcat > logcat.txt
Sent from my LG-LS980 using XDA Premium 4 mobile app

Updated the OP for latest ZVD update from Sprint.
Added SQLite instructions.
Also confirmed working myself.

Updated the OP to include the files and instructions to replace the sprint boot/shutdown animations and sounds

Do you know if I would be able to install a custom rom after this? Also, I had the issue before with cloudys rom that would cause app force closing and restarts, should I expect the same this way?
Thanks a bunch

If you want to use a custom asop rom don't follow my guide instead just follow this guide after flashing your rom of choice.
http://forum.xda-developers.com/showthread.php?t=2827043

@jergio123
Do you think this would work to unlock additional bands on the Sprint LGG2 LS980 for T-Mobile USA?
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269

I guess the only way to find out would be to attempt it. I only quickly looked through the thread but good find.

Is there suppose to be a custom folder inside the carrier folder I copied over to root directory? After rebooting my device I've notice this custom folder that's not inside the original carrier folder I extracted ?

There should be a "cust" folder, I'm not sure if that is the folder you're referring to.

Will cloudys g3 ROM work with this unlock method?

I'm pretty sure cloudys rom is already unlocked and only requires you to change the radio with radio switcher and add your APN

Don't work
Hello, i can't unlock with this method. In the end, when i turn on the phone unlocked, the phone give me an error and always appear "com.android.phone".
I don't understand this part:
"Now edit the build.prop that you pulled from the phone with a program like Notepad++ since it will save the file for use with linux and not windows. Do not edit the build.prop or copy it back to the phone with any apps on the phone, this is what was causing the crashes for me."
I need edit "built.prop" or not? How?
I'm using the phone in Portugal (gsm carrier), i need to do this part?
Sorry but i really confused.
Thank you

Follow the guide step by step, I don't know how much clearer I can make it.
If you're getting process crashes then you must either restore the system partition from backup or start fresh by re-flashing with the LG tool.