Database Info

[REF] Google Navigation Install on G1 (Dream) Running Cyanogen's ROM (any version)

LATEST AND LAST EDIT TO THIS THREAD:
Download the new maps from Google in the marketplace for Google Navigation. Works Android Phones running the 1.6 platform.
No need to follow these instructions anymore!
---------
#Thought I would make a thread with clarified instructions on installing the new Google navigation on a G1 running Cyanogen's ROM. There have been a lot of #problems with the instructions in the other thread since the files supplied (namely build.prop and build.trout.prop) are not correctly referencing each person's #setup correctly.
#Instead of pushing generic prop files onto your phone, you can simply edit one line in your build.trout.prop file found in the system directory on your G1. #Thanks goes to aad4321 who posted it.
#The edit is simply changing the ro.build.fingerprint line to:
#ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
#You can pull this file, edit, remount, then push back onto your phone to allow you install the new maps.apk. You can find the new maps.apk file in the #attachment. You can also find batch files to do all of the above, but is only guaranteed to work on the 4.2.5 ROM. All other Cyanogen version users can use #these files as well if they replace the build.trout.prop file with their own, and then edit the line as above.
#This method will keep all your apps intact, and not cause any problems with marketplace (protected apps not showing), google voice (force closing), facebook #(force closing), etc as reported in the other thread.
#<EDIT 1>If you get the errror "Device not found," make sure you have USB Debugging enabled in settings (thanks kizer).
#<EDIT 2>After performing a rm command, if you get a statement about the directory or file not existing, all is fine. Those rm commands are just trying to #find all possible places the old maps app could be stored, and so if it doesn't exist, you don't have to worry about it. Just go on to the next step.
#<EDIT 3>If you don't see the navigate function, install google voice.
#0) Connect phone
#1) Unzip downloaded file
#2) Run Part 1.bat
#3) When prompted to press any key, do so; the phone will reboot
#4) When your phone is running again, run Part 2.bat
#5) When prompted to press any key, the installation process is done.
#6) Make sure GPS is enabled
#7) Open Maps and press OK
#8) Press Menu
#9) Press Directions
#10) Enter an end point
#11) Click Go
#12) Just under "Show on map", click Navigate.
#13) If prompted to install the voice codec, do so.
#http://www.mediafire.com/?znzizmd1mmm

junker02 said:
Thought I would make a thread with clarified instructions on installing the new Google navigation on a G1 running Cyanogen's ROM. There have been a lot of problems with the instructions in the other thread since the files supplied (namely build.prop and build.trout.prop) are not correctly referencing each person's setup correctly.
Instead of pushing generic prop files onto your phone, you can simply edit one line in your build.trout.prop file found in the system directory on your G1. Thanks goes to aad4321 who posted it.
The edit is simply changing the ro.build.fingerprint line to:
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
You can pull this file, edit, remount, then push back onto your phone to allow you install the new maps.apk. You can find the new maps.apk file in the attachment. You can also find batch files to do all of the above, but is only guaranteed to work on the 4.2.5 ROM. All other Cyanogen version users can use these files as well if they replace the build.trout.prop file with their own, and then edit the line as above.
This method will keep all your apps intact, and not cause any problems with marketplace (protected apps not showing), google voice (force closing), facebook (force closing), etc as reported in the other thread.
0) Connect phone
1) Unzip zip to desktop
2) Run Part 1.bat
3) When prompted to press any key, do so; the phone will reboot
4) When your phone is running again, run Part 2.bat
5) When prompted to press any key, the installation process is done.
6) Make sure GPS is enabled
7) Open Maps and press OK
8) Press Menu
9) Press Directions
10) Enter an end point
11) Click Go
12) Just under "Show on map", click Navigate.
13) If prompted to install the voice codec, do so.
http://www.mediafire.com/?znzizmd1mmm
Click to expand...
Click to collapse
While I placed the files from his zip directly on my SDcard and used terminal to run the command, Junker's method appears stable. I have Google voice, protected apps in market, and functional Navigation. (can't answer for facebook, since I don't have an account.)
Note to someone who does not know shell commands...don't try and copy the ADB commands they are not the same. Know what you are doing before you do it.
Thanks for the post Junker02

i really dont get why there are like 325435412512 threads for this.
They should be condensed into 1.... and listed as separate options/ways to do it.

I had no connection then realized I didn't have USB debugging enabled.
Seemed to work fine.

krstnsn said:
i really dont get why there are like 325435412512 threads for this.
They should be condensed into 1.... and listed as separate options/ways to do it.
Click to expand...
Click to collapse
I believe the methods listed on the other threads are incorrect, or are more complicated than need to be (and possibly breaks other apps). I only found this method buried in the think-tank post, and though it was suggested for the OP to fix the first post, it never was. Hopefully others who are on Cyanogen's ROM will appreciate the info.
kizer said:
I had no connection then realized I didn't have USB debugging enabled.
Seemed to work fine.
Click to expand...
Click to collapse
Thanks for the tip! I'll add it to the first post.

junker02 said:
I believe the methods listed on the other threads are incorrect, or are more complicated than need to be (and possibly breaks other apps). I only found this method buried in the think-tank post, and though it was suggested for the OP to fix the first post, it never was. Hopefully others who are on Cyanogen's ROM will appreciate the info.
Thanks for the tip! I'll add it to the first post.
Click to expand...
Click to collapse
I agree, the other threads over complicate it and cause problems for those who don't know what they are doing. If they learned how to do it themselves there would be less questions and complication.
But then again, now this is just another thread about nav. Really, they should all be locked and something like what is in the first post should be put in the informative links thread.

wanted to thank you for instructions, possibly a better forum wiulda been q&a, as I go there to find answers and help solve some =) other than that this does clear some things up such as the ro line. Like in the other post it says almost same thing but fails to mention the line to change. Etc..etc... this did catch my eye and I was was about to try another method for my buddies phone and this saved me of searching through a thread. My penies, again ty.

junker02 said:
0) Connect phone
1) Unzip zip to desktop
2) Run Part 1.bat
3) When prompted to press any key, do so; the phone will reboot
4) When your phone is running again, run Part 2.bat
5) When prompted to press any key, the installation process is done.
6) Make sure GPS is enabled
7) Open Maps and press OK
8) Press Menu
9) Press Directions
10) Enter an end point
11) Click Go
12) Just under "Show on map", click Navigate.
13) If prompted to install the voice codec, do so.
http://www.mediafire.com/?znzizmd1mmm
Click to expand...
Click to collapse
I'm confused. Are you telling me that if I follow the steps outlined above that Google Navigation should work on my Cyanogenmod 4.2.5 ROM without any (google voice, market, etc.) problems?

scrappyabs2 said:
I'm confused. Are you telling me that if I follow the steps outlined above that Google Navigation should work on my Cyanogenmod 4.2.5 ROM without any (google voice, market, etc.) problems?
Click to expand...
Click to collapse
I had no problems, but I did it myself:
from scratch (no map mods, orig build.prop):
adb remount
adb pull /system/build.trout.prop build.trout.prop
open it with notepad and edit the line
ro.build.fingerprint=tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,release-keys
so that it reads
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0/ESD20/17572:user/ota-rel-keys,release-keys
save it
adb push build.trout.prop /system/
adb shell reboot
now reininstall google voice from market and reinstall maps with the new one

help me out here man, i dont have adb, i just use my phones terminal

bigstunta101 said:
help me out here man, i dont have adb, i just use my phones terminal
Click to expand...
Click to collapse
ok, even easier, do you have astro?
you can navagate to the /system directory, copy the build.trout file to your sdcard directory. mount your sdcard and edit the file with notepad. copy it back over to the /system directory and reboot
then install voice and maps
or try doing the same from your pc using droid explorer
http://forum.xda-developers.com/showthread.php?t=558108
haven't tried it either way way but it seems like it should work

scrappyabs2 said:
I'm confused. Are you telling me that if I follow the steps outlined above that Google Navigation should work on my Cyanogenmod 4.2.5 ROM without any (google voice, market, etc.) problems?
Click to expand...
Click to collapse
Yes, that's exactly what it will do.
bigstunta101 said:
help me out here man, i dont have adb, i just use my phones terminal
Click to expand...
Click to collapse
The ADB app is included in the download. I'm not sure if it will work without the driver installed, but you can give it try and report back. Simply run the two .bat files and it will execute all the necessary ADB commands automatically.
Worse comes to worse, you would just need to install the driver for your phone.

Ok, here are the steps I took without adb, since comps at work do not allow USB write.
I uploaded the build.prop and maps.apk and sent them to my email using yousendit.com
Downloaded both into sdcard/download
Using "Root Explorer" navigated to /system and set it R/W (there's a button on the top)
Moved the build.prop to /system
Reboot
Install Maps
Reinstall GoogleVoice
Voila!

When I run the first batch file I get this errror: Device not found.
I've never gotten this message before. ADB was working fine for me a few days ago, before I reinstalled 4.2.5. Any ideas?

scrappyabs2 said:
When I run the first batch file I get this errror: Device not found.
I've never gotten this message before. ADB was working fine for me a few days ago, before I reinstalled 4.2.5. Any ideas?
Click to expand...
Click to collapse
Is your usb debugging enabled on your device?
Settings>Applications>Development

xavina said:
Is your usb debugging enabled on your device?
Settings>Applications>Development
Click to expand...
Click to collapse
Yes, its enabled. I swear I installed this navigation app on an earlier version of CyanogenMod and ADB worked just fine. Now it won't recognize my device. Please help me.

scrappyabs2 said:
Yes, its enabled. I swear I installed this navigation app on an earlier version of CyanogenMod and ADB worked just fine. Now it won't recognize my device. Please help me.
Click to expand...
Click to collapse
If you can't get the batch files to work, edit the batch files to see what commands are performed, and execute them in a terminal. There aren't that many.

junker02 said:
If you can't get the batch files to work, edit the batch files to see what commands are performed, and execute them in a terminal. There aren't that many.
Click to expand...
Click to collapse
adb remount says "error: device not found"

Here you go guys, safe simple and so easy a caveman can do it... (insert the, "If you break it, it's your own fault disclaimer here.)
Download the file in the first post of this thread.
extract the file on your hard drive and copy the build.trout.prop file and the Maps.apk, then put them on to your SD Card.
If you can't get this far....we have a bigger issue.
Then in terminal emulator type
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/build.trout.prop /system
reboot
When the device reboots then do this one in the terminal emulator
Code:
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/sd/app/*Maps*
rm /system/sd/dalvik-cache/*Maps*
rm /system/app/*Maps*
reboot
*Note: Someone might say that the reboot at the end of this code is not needed. That maybe, but it worked just fine for me.
Now using Astro, or another file manager, install the maps.apk from the sd card.
If prompted, install the voice. I had it from other programs.
Turn on GPS
Open the drawer
Click on Maps
Let the Maps program find you
Then click menu, directions
Enter the destination, and click go.
It should show
Code:
My location
<the destination address you entered>
Show on map
[B]Navigate[/B]

Thanks for making clear instructions for the terminal emulator [email protected]
Everyone please remember that one can only use the build.trout.prop file in the first post if they are also running Cyanogen 4.2.5 on the G1, else you run the risk of app errors and force closes. If you are running a different version of Cyanogen, make a copy of your own build.trout.prop file found in your system directory, and edit it.

For extreme noobs like myself info reg rooting & clockwork recovery

About a day ago I didn't know anything about rooting and what it was but now I know to a degree from many hours of reading.
These are the steps I did.
You have to make sure that you choose the correct one click root method for the DI07 patch. Obviously you need to put the epic in debugging mode and click on the appropriate run.bat command and let the batch run. That part wasn't to hard for me, pretty much self explanatory.
Also to check for "root", to make sure your epic is rooted, download titanium backup from the android market and if it launches your epic is rooted and plus it will say root status "ok"..
The part I had issues with was with the one click clockwork recovery. Especially when people started talking about typing in commands in the dos prompt. I'm ok with doing that but it wasn't explained in full detail regarding what to do.
So first thing that I had to figure out was what they meant by c:/android-sdk-windows/tools and where was this located. I didn't have this file on my cpu on the c: drive and i was lost at this point being that I didn't know where to get it. I later found out and if im wrong please tell me you had to create your own folder on your c: drive so you can point to it from the c: prompt in dos. So I went ahead and did that.
In the tools folder from android-sdk-windows folder you would go ahead and place the contents of the clockwork recovery files in the tools folder. So wahla I now have a folder I can point to in the dos prompt. At this point I still didn't know if this is going to work or not but I felt like I was close.
Next step was to follow "open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code."
adb devices
adb shell
su
remount rw
exit
exit
first you need to type cd C:/android-sdk-windows/tools and press enter to point to that folder. And run subsequent commands from there.
If when you type in adb devices and a device does not pull up that means that the usb drivers are not installed properly for the epic phone and you need to look into that first.
After you run those commands now you can go ahead and run the run.bat file for the clock works recovery. But also make sure your still in debugging mode.
This might take a few tries but it will eventually work and if it does not work after trying to flash the recovery and the epic reboots pull the battery (reinstall battery) and then try to go into recovery by pressing the vol down--camera--and power button at the same time and you should see a green recovery screen.
I wish someone had typed something like this sooner so I wouldn't of had issues.
I hope this helps at-least one person.

Good idea except it's already been done :-\
http://forum.xda-developers.com/showthread.php?t=786305

Whosdaman said:
Good idea except it's already been done :-\
http://forum.xda-developers.com/showthread.php?t=786305
Click to expand...
Click to collapse
I know I was trying to follow that but there was parts missing that I didn't understand for ex. the part where I had to create the actual folder it never stated to create a folder but it wanted you to point to it in the dos prompt. And yes that tutorial did help out tremendously but i was still a little lost. My explanation fills in the missing gaps or parts. But thank you for pointing that out.

Maybe with noobnl latest version of the clockwork installer (version 32 with mount rw included in the script) you no longer need to go into adb?

jimmyz said:
Maybe with noobnl latest version of the clockwork installer (version 32 with mount rw included in the script) you no longer need to go into adb?
Click to expand...
Click to collapse
That is correct. Version 32 is truly one-click.

mattallica76 said:
That is correct. Version 32 is truly one-click.
Click to expand...
Click to collapse
Thats true

I'm not quite as noobish as the OP but I'm a complete noob to Android and -nix os's in general (besides a tiny bit of unix experience and a non-fear of command-line interfaces). Still, I have enough fear of the process to wait until Epic ROMs are a little further along and more refined to the degree that that's possible. If I weren't quite so noobish I'd dive right in.

[GUIDE][10/5/10]Comprehensive Guide to Rooting, Flashing, and Android Basics!

1.0 – WELCOME AND DISCLAIMER
So, it seems like a lot of people are having problems with their new Samsung Epic 4G. I thought I'd take a minute and throw together a little comprehensive guide on, well, everything. I'll be updating this periodically, so be sure to check it out.
I'll also be working on formatting it to improve readability... I'm not so good with this markup language that forums make you use, so bear with me. If I can figure out some basic tricks, we'll be in business.
And, just so you know, this is just a guide. As long as you follow it and do research, everything should go fine. That being said, I am not responsible for what happens to your phone. This is all elective and I am not forcing you to do any of this. You brick your phone, you own up to it. I'm only trying make it as easy as possible for your to avoid that.
2.0 – GETTING STARTED
New to Android? Need to root? Just got your phone? Not totally clear on everything? Start here. Even if you have experience with Android, had your Epic since day one, or whatever, you'll still want to check this section out.
2.1 – TERMINOLOGY
First of all, you need to familiarize yourself with the terminology. This is vital to understanding what you are doing, so I'll outline as many as I can.
Brick – Not a term that should be thrown around as much as it is. If you have a bricked device, it is worthless. Like, completely. It is literally as useful as a brick. You CANNOT fix a brick. Everything else is just just breakage.
Root – a)This term comes from Linux/UNIX. To obtain root access means that you have elevated privileges. Look at this like administrator rights in Windows. It's what allows you to run custom software and access administrator setting in Android.
b)The uppermost folder. Such as “/”, “C:\” , et cetera.
Rooting – Gaining elevated root admin access.
Kernel – A kernel is the base of an operating system. For Android, it's where all the drivers and system information resides. A custom kernel can contain undervolting instructions, overclocking instructions, and many other battery-saving, power-giving, phone-enhancing features. There are several options, so make sure you do your research and choose the kernel that offers what you are looking for.
Shell – The shell is the part that you see. It's the interface that interacts and allows you to interact with the kernel.
ROM – A ROM is the combination of a kernel and a shell. Think of this like an operating system.
Dev – Dev is short for developer. These are the people who spend their days and nights writing code and bug testing to bring you the ROMs you love. These guys are the reason you're here, so show your appreciation!
Chef – Chefs and devs are essentially the same thing.
Recovery – A system that allows basic phone function. You can flash from this, clear data, and do very basic debugging. As long as you can boot to this, your phone is NOT bricked.
Flashing – The act of installing a ROM or fix to your phone through recovery.
Wiping – The act of performing a factory reset or cache clear from recovery. Your settings are gone, your apps are gone, your phone is as it was when you you got (to an extent). Formats /system/. This is not reversible.
CPU – Central Processing Unit. The brain of the phone. All data travels through this at some point.
Overclocking – Pushing your CPU to its limits. The CPU has a stock clock speed (1GHz for the Epic), and overclocking is pushing it past that.
Undervolting – Making the phone use less power. This saves battery.
AOSP – Android Open Source Project. Frequently referred to as “Vanilla”. The actual people who make Android. Go here for more information.
Theme – A cosmetic change to the user interface.
One-Click – A script or program that does everything for you.
Busybox – A collection of scripts that allow deeper editing of the system while it is running.
Remount – An easy method of mounting /system/ for writing.
Stock – Samsung-released, no editing, as-is stuff. Basically, how the phone came.
OTA – Over the air. Updates that automatically come to your phone, through your service.
adb – “Android Debug Bridge” A debug program for accessing your phone.
deODEX – Combining the ODEX file and the APK files for all the items in the /system/ folder. Allows for easier theming and customizing.
FC/Force Close – When a program or app crashes.
2.2 – WHY SHOULD I ROOT MY PHONE?
Rooting offers several great things including, but certainly not limited to, access to hidden features, total customization, better battery life, and overclocking. It gives you control over the device that you paid money for in the first place. The devs here are great at finding features that the manufacturers left out or disabled and making them work.
It also is a great hobby. Even if you aren't a developer yourself, flashing ROMs and trying out new features can be a lot of fun and definitely kill boredom. And who knows? Maybe you'll end up learning something and start coding yourself.
2.3 – ROOTING
Great! Now you know some words! So, what next? Well, we need to achieve root access on your phone. There are a few ways to accomplish this on the Epic. Please note that the one-click methods are hit and miss and are affected by several factors, including computer speed, cable, USB ports, and, for all intents and purposes, random chance. I HIGHLY recommend you open the .bat files and run every command in adb manually. I'll update this guide, eventually, with how to do this.
If you're running Windows, you're going to need the drivers for this phone. Install them BEFORE connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
You'll also need to put your phone into debug mode. After you turn this on, you can just leave it on. To do this, go to settings, and then to applications, then to development, and then tick the “USB debugging” check box.
I also recommend using a cable other than Samsung's cable that came with the phone. Really, that cable is hardly good for anything more than charging. It's low quality and has caused a lot of users more than a headache. If you are unable to get another cable for whatever reason, run each command individually from adb. Check the section about adb and the Android SDK later in the guide for more information on how to do that.
2.3.1 – The Jokeyrim temporary root with noobnl's one-click script method – DO FIRST
Let it be known that I don't recommend relying on this method. It's janky and can cause problems once you get deeper into Android modification. Use it to get your remount scripts and then quickly do the kernel mods in the steps in 2.3.2.
Go here and download the .zip file. Extract the .zip contents to your desktop. Open the folder, run “run.bat” and let it go.
NOTE: This is just root, this is temporary, and this DOES NOT give you access to a recovery. All this will allow you to do is run applications that require root or busybox and adds the remount script.
2.3.2 – The rooted kernel and recovery method method – DO SECOND
I do recommend that you use this method. This gives you true, permanent root.
There are a couple of ways to do this. I actually suggest you follow both guides, too. This will help prevent you ever getting to Samsung's stock recovery, which is worthless for your purpose.
The first is noobnl's recovery method, and definitely the one you should do first. You can find it here. Download the .zip file and extract its contents to your desktop. There is an issue with this .bat file, so you're going to have to do some extra steps. With adb (go to the section about the Android SDK and adb further in the guide if you do not know what this is) and type:
Code:
adb shell
su
remount rw
exit
exit
(the two 'exits' is not a typo)
After running those commands, open your extracted folder and run the run.bat file. Should be smooth sailing.
The second is koush's method. koush's thread is here, but I that's a complicated method. After you do noobnl's method above, go to this thread and download the .zip from that. Put that .zip on the root of your SD card. Boot into the Clockwork recovery by turning the phone off, holding down the camera button, the volume down button, and pressing the power button until the phone turns on. Once in there, do this:
1. BACK UP YOUR PHONE. I cannot emphasize this enough. Backups are sooo important in your Android modding quest. Backup and do it often. (Backup and restore → Backup).
2. Go to “Flash zip from SD card”
3. Choose zip from sd card
4. Select the zip we put there earlier
5. Click “Yes”
6. Let it do its thing
Once you've done this, you need to boot into the phone, go to the market, and download “ROM Manager”. From that, click “Flash recovery” (the top option) and select the Epic. This will take a minute. From this point on, you can use ROM Manager to boot into the Clockwork Recovery.
2.3 – FLASHING ROMS/KERNELS/FIXES
This is the fun stuff. This is why you're here. Now that you have root and a recovery, we can get some work done. First, you have to select a ROM that you want. Always pick a ROM that is designed for the Epic. ROMs designed from other phones can and will brick your phone!
You can find ROMs for the Epic in the Epic 4G Android Development section of XDA. Do some research to each ROM to make sure it's what you want. If you want a kernel, make sure your ROM supports other kernels and that the kernel supports your ROM.
Once you've picked your ROM, put it on the root of your sd card and then boot into Clockwork Recovery using your method of choice, then:
1. BACKUP. I seriously cannot stress this enough.
2. Wipe everything. Factory reset and clear cache.
3. Go to “Flash zip from SD card”
4. Choose zip
5. Choose “Yes”
6. Let it run
7. -OPTIONAL- To ensure it worked, repeat steps 2-6. This is just to make sure everything worked. Problems with this can be intermittent and this helps to avoid them.
8. Reboot.
3.0 – ERRORS
Stuff goes wrong. You have to understand, EVERYTHING in this is experimental. The devs here do not have access to EVERYTHING that is required to make these phones work and have to guess at some things and, basically, just do their best (And their best is pretty damn good!).
Basically, just be sure you have backups that you can restore from, and this will all be fine.
3.1 – BLACK SCREEN
Oh no! I flashed ROM X and now my phone won't boot and I hate everything!!!
Worry not! As long as you can boot in to recovery, you have nothing to fear. Just restore the backup that I told you to make and you're back in business. Easy fix.
3.2 – CONSTANT FORCE CLOSES
You boot up your phone and are immediately greeted with force closes. Chances are that you didn't wipe OR that the ROM you're using isn't ready for show time. Again, just restore your backup from Clockwork.
3.2 – CAN'T GET TO RECOVERY, CAN GET TO DOWNLOAD MODE
Well, looks like you'll be returning your phone to stock using Odin. Read later on in the guide how to use Odin in the section about Odin.
3.4 – PHONE WON'T TURN ON AT ALL
Welcome to bricksville, population you. Sorry, but you're phone is a $500 paperweight... Probably shouldn't have flashed that GSM ROM, huh? Not even Odin can save you at this point...
4.0 – THE ANDROID SDK AND ADB
The Android SDK (Standard Developer Kit) is a tool freely available to everyone. You can find it here and it is available for Linux, Mac, and Windows.
4.1 – INSTALLING THE SDK
So, the first step is going to be how to install the SDK on your system. I have experience with Linux and Windows, so that's what I have for now. If someone with a Mac can help write the set up instructions for that, I'd be very appreciative.
4.1.1 – Windows
First, download android-sdk_r07-windows.zip from here to your Desktop. Once it has downloaded, double-click the file and extract it to the root of your C:\ drive (this is optional, but it will make things a lot easier in the future). Rename the extracted folder “android-sdk-windows” to just “android” to make your life easier.
Open the new folder, then run the SDK Manager. If you run into an error about Java, go to java.com and get the latest version of the Java JRE (pretty much just click whatever the biggest “download” button is that you first see).
Once you have the SDK open, it will ask you to install packages. Just tick the “Accept All” radio button on the bottom right and press install. Depending on your internet connection, this can take a long time. Just be patient. Once they are all installed, you're good to go.
How you use adb is simple. Open a command prompt (press the Windows key + r and type “cmd” in the box that shows up, or go to Start → All Programs → Accessories → Command Prompt) and type in “cd C:\android\tools\” and type your commands (list of common commands at the end of this section.
-OPTIONAL- This step is optional, but HIGHLY recommended. Now that we have the SDK set up, we're going to adb to the Windows paths so that you can use adb from anywhere you can open a command prompt.
First, click the start menu and then right-click “My Computer” (Just “Computer” in Vista and 7. You'll also need to click the “Advanced System Setting” on the left side of the window that appears.). Click “Properties” and the Properties window appears. Now, click on the “Advanced” tab and the the “Environment Variables” button. A new window appears with two scrollable boxes. In the lower box, scroll until you find a “path” option and select it. Click “Edit” underneath the box. Move your cursor to the very end (Press END on your keyboard, just to be safe) and type “;C:\android\tools\”” (That leading semi-colon is important and may already be there. Check to be sure).
And you're done! Open a command prompt and type “adb devices” and see what comes up. If a list of devices (phones; will be empty if your phone isn't connected in debug mode) comes up, you've succeeded! Congrats.
4.1.2 – Linux
I use Ubuntu personally, but most of this information should be universal. If anyone running anything else sees anything missing or wrong with other distributions, let me know and I'll update or fix it.
First, you need to acquire the SDK. The file is android-sdk_r07-linux_x86.tgz from this site. Once downloaded, extract the contained folder to your home folder (/home/*USERNAME*, using your username) and rename the folder “android' for later ease of use.
Use terminal and cd to the android folder your created. Use the command “tools/android update sdk” to make the SDK updater come up. Just tick “Accept all” in the bottom right and then click install. This can take a while depending on your internet connection.
Once you have all of the files installed, you're ready to use adb. Using terminal, navigate to /home/user/android/tools and type (For Ubuntu):
Code:
sudo chmod 777 adb
This will allow the adb file to be read as an executable. Note that this only has to be done once. Then, use this code:
Code:
sudo ./adb start-server
(replace 'sudo' for 'su' for distros other than Ubuntu)
This is necessary every time you use adb (in Ubuntu, at least). You only have to do it once per session, but if the adb process is ever killed during your session, you must do it again. I've just gotten into the habit of doing it every time I log into my computer. You could also create a boot script that does this for you... which I've been meaning to get around to. After you have the process running, you won't have to use su/sudo or ./ to use adb.
Note that one-click scripts written for Windows will have to be opened and run manually. There are scripts for Linux floating around, but I can't seem to find the thread.
-OPTIONAL- This isn't a needed step, but you'll probably want to do it. Here we're going to add adb to the paths folder so that after you have started the process as an administrator, you can run it from any folder.
Open terminal and use these commands:
Code:
echo $PATH (should return the directories associated with $PATH)
export PATH=$PATH:/home/user/android/tools (replace with path to your tools directory, you may need to add 'sudo' or 'su' to the beginning of this cmd)
echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
Once done, you're set. Once you have the process started, you can run adb commands from any terminal window.
4.1.3 – Mac OS
-I don't own a Mac, never have, and I have zero experience with Mac and Android... If someone else can help with this section, I'd appreciate it -
4.2 ADB COMMANDS
This isn't a complete list, but it should be enough to get you by for your purpose.
adb shell – opens a terminal on your phone. Terminal is like the command prompt of Linux.
adb push – pushes a file to the phone. The syntax is ”abd push *file location on your PC* *Location you want it on your phone*”
adb pull – pulls a file from your phone. The syntax is “adb pull *file location on the phone* *location to be placed on your PC*
adb shell rm – deletes a file from your phone. The syntax is “adb shell rm *location and name of the file to be deleted*. NOTE: adb shell rm -r is a recursive deletion and can cause damage to your ROM and phone. Make sure you know what you are doing if told to do an rm -r.
adb devices – lists all connected Android phones.​
5.0 - ODIN
(I don't have a ton of experience with Odin, so if someone can refine this section, let me know and I'll update it)
Odin is a tool that was created for previous Samsung phones. It is a powerful tool and very useful for saving your phone from many malfunctions. As long as you can boot your phone into download mode (Hold down the “1” key on the slide-out keyboard while powering the phone on) you can almost always save your phone.
That said, Odin is also fairly experimental in its implementation on the Epic. There have been several reports of failed flashes and intermittent errors. This guide will hopefully help prevent that from happening.
5.1 – SETTING IT UP
If you haven't already, you need to get the drivers for the phone. Install them BEFORE Odin and before connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
After that, you're going to need to get Odin. You can find that, as well as a basic guide and the stock files from noobnl, here (External link to SDX). Odin is the .rar file from the first link fo the post.
5.2 - USING ODIN
After you have it downloaded, extract the files somewhere (I recommend a folder on your desktop). From the extracted files, double-click “Odin3_v1.0.exe” and the Odin window opens. Have it completely ready to go before connecting your phone. Put all your files in the spots they belong (refer to the post where you got the Odin files for instructions on that... it seems to vary a lot depending on the purpose). Make sure that no other check boxes are ticked besides “Debug En.” and “Auto-reboot”. All the others can have very negative effects.
Before connecting your phone, put it into download mode by holding down the “1” key on your slide-out keyboard while powering the phone up. Once it is in download mode, connect the phone. The first box in Odin should come up as something akin to “COM4”. If it doesn't say exactly that, don't worry. Make sure all your files are placed correctly, and then click “Start”. It should take up to a few minutes, so be patient. Cutting this process off early can have negative effects. When it is finished, the phone should reboot.
6.0 – CLOSURE
I hope this guide helped you. If you have any questions, you can contact me, but I can't guarantee I can help you. Most devs are willing to help, too, so you can shoot them a PM and they'll try to get back to you.
Good luck and happy flashing!!

[Update Log]
*10-5-2010 - Added sections for Odin and adb/Android SDK. Updated sections, fixed typos and mistakes, reorganized a little. Fixed links.

None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling of the web address or search above."

Thanks a bunch, this was a very useful tutorial on the basics and for me helped out greatly with understanding where and what you need to do to be getting the best out of these awsome phones!
blasted across the interwebs by the Epic 4g!

Lonewuhf said:
None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling qof the web address or search above."
Click to expand...
Click to collapse
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?

DevinXtreme said:
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?
Click to expand...
Click to collapse
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/

dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
That is so weird... It's showing up like that for me now, too. I've checked the source, and it stills is showing the right links in my post.... It's something on XDA's end right now... I'll look into getting it to work a little later.

Good work! This should be a sticky!
Sent from my Epic 4G

dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
yeah same here, i just cleared everything before "forum" from address bar and page loaded.

You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App

mysteryemotionz said:
You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Unless whatever you're flashing messes with the recovery partition, an incomplete flash shouldn't cause a brick. As long as you can boot to recovery or download mode, you can save your phone.
And I'm working on an Odin section for my next update to this. A lot of things will be added next time I update the main post.
Sent from my SPH-D700 using XDA App

i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?

The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.

dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=770388
for the proper thread

^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App

bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.

you might wanna add how to set adb

Spunkzz said:
i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?
Click to expand...
Click to collapse
bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Vanquish46 said:
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.
Click to expand...
Click to collapse
I think I know the issue here. It's that /system/ isn't being mounted as rw. Run the jokeyrim root method and then go into adb and type this:
Code:
adb shell
su
remount rw
exit
exit
If you don't know how to use adb, just wait until a little later tomorrow. I've got a whole section about it to add to the guide, but I don't have it completed yet (did some work on my laptop in the middle of writing it, forgot to reconnect my WLAN card and was baffled for most of the day...)
dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
Sorry about that. Should be fixed now. Thanks for pointing it out
mysteryemotionz said:
you might wanna add how to set adb
Click to expand...
Click to collapse
All in the works I expect to have the guide updated early tomorrow, if not tonight.

Updated the guide with a lot of new info. Two new sections for adb/the SDK and Odin as well as a general update to the whole thing. Some of the sections changed (HARD and EASY mode are now both required, unfortunately...) and some things got a little moved around.
Also, all of the links should now work correctly. Something about the way XDA was handling quotations... So I just stripped them all from the forum code stuff...
If anyone has any experience with Mac, I could use your help for the adb/SDK section, and I could also use some help from someone more experience with Odin for that part.
Thanks, guys! I really hope this guide helps some people.

not to be a pain Devin but the two links for noobnl's programs goes to the same page for the easy and hard method don't know if that's right or not but wanted to point it out to you.
Thanks again for the great guide.
David

[GUIDE] Newbie's Step-by-Step: From Stock Cellular South Showcase 2 Kernel/ROM +

After bdemartino wrote his AWESOME thread for the Mesmerize it seemed only fitting that the Showcase get their very own... And since his Thread was Flawless, with his permission I'm mostly copy/pasting word for word.
THIS GUIDE IS SPECIFICALLY FOR THE SHOWCASE
If you're Looking For FROYO Skip down to the bottom of this post to the Section Labled FROYO!!!!!
Keep in mind there are many variations to each step, this is what worked for me the easiest.
And last but not least. There is always the disclaimer that attempting any of this can and will make your phone dysfunctional and or possibly bricked beyond repair (but most likely just dysfunctional which is a pain in the arse to deal with) if you do not follow steps completely (and of a trustworthy source such as xda - ehm and in the appropriate forum ).
So make sure you're in a comfortable environment (not a good idea to be trying to accomplish this while slamming beers at the bar), take your time, read each step that these people have taken the time to carefully write up (then follow it), and you'll be just fine. Be patient as things don't always move fast and you never want to freak out as you may screw things up bad, when it's actually just taking longer than you would expect. Always give it at least 5 minutes before you determine it's looping or crashing or whatevering, there is alot going on behind the scenes, trust me!
Steps to Customize Your Stock Showcase (For Eclair 2.1)
1) Root your phone. - Basically all this means is gaining the ability to give programs/apps and yourself SuperUser access (equivalent of being admin in windows) and also the ability to flash roms via recovery, detailed below.
The easiest way to root is through the z4root.apk. (an application that will run right on your phone)
Download Here
After download, put z4root.apk on your SD card root directory
Then make sure in Settings->Applications that the "Unknown sources" box is checked.
If you don't have a file manager, download a free one from the market, using the file manager navigate to the z4root.apk and select to install it. Note: If you need help at this step, no offense I would suggest getting someone with more experience to help you continue on. I'm serious here
Reboot your phone
After it boots, open the z4root app and press root. At this point it is going to hang, give it 2 minutes and pull the battery. Count to 10, put it back in and turn it on. - This is normal
After your phone boots open z4root again and click root, this time it will run no problems and phone will reboot.
NOTE**IF YOU HAVE PROBLEMS WITH z4root: "give Super One Click a try. It's a package you have to download to your computer, but you get to see more of what's actually going on so you know where it's at in the process. I have only used up to version 1.5.5, and I know that version is very capable for the Showcase on 2.1. It is located here."-This Information provided by phidelt82**
Once you are rooted (you will see the superuser icon in your apps, it will show apps you've given that permission to... eventually) you will need to make sure you have a file manager that can request root permissions (read/write) before you will be able to complete the next step. Search the market for "root file manager" and pick one to download and install.
I use Root Explorer
It's a few bucks, but there's hardly a day that goes by when I don't use it.. (Well worth the money)
Also at this step I would download and install RomManager and TerminalEmulator as you will need these later.
2) Install RomManager and the ClockworkMod Recovery. These will basically just give you the ability to boot into recovery where you can more easily flash kernel's/rom's and anything else you wish to push to your phone. (Recovery is basically a bios like interface - but it's different than the stock version)
I was able to install the Clockwork Mod Recovery very easily just by simply using the root file manager app I had downloaded, along with following with the instructions.
(In your file manager, MAKE SURE YOU ARE Read/Write not Read/Only, for RootExplorer there is a toggle at the top, other ones you may have to enable this through settings, others may just be R/W by default, you will just have to determine this or google the app)
Download the two Files you need from the bottom of this post
Place both files on your SD card root if you were using a computer to download them or you could always download them through your phone's browser
Using the root file explorer app, move the Redbend_ua file from the SD card to /system/xbin/
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that so that all are marked. Save and exit.
Now open TerminalEmulator
NOTE:The spaces below are actual spaces and in bml8 there is a lowercase "L" not a "1" there is also a space after cd, after redbend_ua, after restore, and after recovery.bin
TYPE THIS ALL EXACTLY AS SHOWN BETWEEN THE QUOTES
at the command line ($) type "su" (then hit enter)
Type "cd /system/xbin" (then hit enter, which changes directory)
Type "redbend_ua restore /sdcard/zImage /dev/block/bml8" (then hit enter, It will now scroll a bunch of text and reboot.)
After phone boots, open RomManager
Click on Flash ClockworkMod Recovery
Select the Samsung Fascinate your phone will still be the Showcase. This is just what works with our model.
At this point you're all stock and ready for new kernel/rom. (but now you are able to do so very easily)
Accessing Recovery!!!!!
NOTE: There are a few ways of getting into recovery mode. The easiest is to download QuickBoot.
Once installed you can install the widget to any homescreen or just use the app from the app drawer. Once you open the app, click Recovery and it automatically reboots the Phone into Recovery..
You may have to click the install update.zip (while you're on the stock kernel after Voodoo you won't have to anymore)
The other method, which you will need incase you EVER Bootloop! Is the 3 finger method (Hold down the volume up and down keys and the power button all at the same time when you're turning your phone on) Once you see the Samsung splash screen you can remove your finger from the power button, but keep holding down both volume keys!!!
Incase of Bootloop, remove the battery and do this while Rebooting...
AGAIN WHILE YOU STILL HAVE A STOCK KERNEL, YOU WILL PROBABLY HAVE TO *apply sdcard:update.zip* after you enter the FIRST RECOVERY...
The next Screen will be Clock Work Mod, this is where you will want to do your First Nandroid Backup!!!!
3) KERNEL: Install Voodoo lagfix kernel and new 5.0 sound
Now onto Installing a Voodoo Kernel
If you want speed and good battery life (and high standard marks) +unlocking the headphone amp and eq controls (it makes even the samsung headset sound killer) go here and follow those steps for using your now functional recovery mode to flash the new Voodoo 5.0 kernel.
Now you can install Voodoo Control and get new life out of those earbuds!!!
Note: Just an FYI, after installing custom kernel's you will always have an issue on start up of seeing a flashing black box in the middle of the samsung logo. This can be corrected by installing a custom boot screen (only requires root access) and you can find out how here.
4) Custom ROM : Download and install the ROM of your choice.
Right now we really only have 1 that I recommend..
It's Phidelt82's PicknPack Rom
This is a deodexed Rom which allows you to use MODS and themes. This ROM is 100% Stable, I've been running it for a WHILE with ZERO issues...
MODS/Themes/Customization
NoClock in the Status Bar
Midnight Theme
HoneyComb Digital Clock
Shutdown Animations or Images
Bootanimations with new Boot Sounds
Of course there is WAY more than these listed, but this should fill up your afternoon playing around with your new and IMPROVED Showcase!!!
FROYO FOR THE SHOWCASE = YUMMY!!!!
Yes, for those of you that didn't already know, thanks to Phidelt82 we now have Froyo!!!! I've been running it for about a week and it's Delicious!!!
I'm not going to Write as much as I did for the 2.1 b/c the directions are in the threads already.. Just follow the Directions, if you have any problems after that read through the threads and see if anyone's already figured them out...
And this will work with a Factory Showcase!!!!!
First of all you need to go to:
[Froyo-Odin] Showcase EB11 - Cellular South Update (be sure to Thank Phidelt82)
After this you will have 2.2, now you can use:
SuperOneClick to root your new Froyo Showcase (if you want)!!!
And if you plan on doing Mods/Themes/etc.. You should go ahead and Flash the EB11 Showcase Pick-n-Pack, again be sure to thank Phidelt82 for this!!!
If you flash the PicknPack Rom made by Phidelt82, then there's no need to root... It comes PREROOTED.. You only need to ROOT if you're staying on the Stock 2.2!!!
If you're flashing the picknpack do a Nandroid backup after you're done.... If you're going to stay on the Factory 2.2, do you a Nandroid backup after that...
Thanks to lmartin92, JT1134, Phidelt82, we now have a voodoo kernel with lagfix for 2.2 which can be found HERE...
If you're new to using voodoo lagfix kerenls.. Remember to always disable lagfix before doing Nandroid Backups/Restores/Flashing mods/Themes for YOUR SAFETY
I'm working on a few themes... sbrissen has already Made us the NoClock and NoAmPm mod (you have to be on the picknpack for these)
For a list of the Mods/Themes/Roms for the showcase look HERE
Always check the Mesmerize forums for new Android Development, Mods, Themes, etc...
And for help Don't be afraid to ask (after you've read this legnthy post) or drop by the #samsung-mesmerize channel at http://webchat.freenode.net/
Thanks to Phidelt82 for all of his dev support for our phone!!! If you want to donate to him click HERE
Thanks to bdemartino who wrote the AWESOME tutorial HERE that i mostly copied/pasted from!!! Be sure to click his thank you button if this helped you out...

Reserved FOR Me!!!!

Great work elijah, you are the Showcase king

bdemartino said:
Great work elijah, you are the Showcase king
Click to expand...
Click to collapse
my Kingdom sure is small lol

It is probably bigger than you think Elijah

ocs111 said:
It is probably bigger than you think Elijah
Click to expand...
Click to collapse
yeah, you just don't see much Activity out of showcase users...
btw... could you help out with this??
http://forum.xda-developers.com/showthread.php?t=945069

I will be glad to help test. I am just not much in script writing. When I read that post yesterday I thought there were problems with it. Just let me know what I can do. Right now I am rooted with Z4 and running voodoo kernel.
elijahblake said:
yeah, you just don't see much Activity out of showcase users...
btw... could you help out with this??
http://forum.xda-developers.com/showthread.php?t=945069
Click to expand...
Click to collapse

ocs111 said:
I will be glad to help test. I am just not much in script writing. When I read that post yesterday I thought there were problems with it. Just let me know what I can do. Right now I am rooted with Z4 and running voodoo kernel.
Click to expand...
Click to collapse
I'm hoping Bubbakoush will test since he has a showcase that needs to be flashed back to factory... I wouldn't recommend flashing this until after he can confirm it works

elijahblake said:
my Kingdom sure is small lol
Click to expand...
Click to collapse
Hey bro, don't think we're not around... I'm just enjoying my rooted Showcase, waiting for some more ROMs to give a try.
Thanks for all the work putting this together, and everything else you've been working on for Showcase!

Nice write up!

elijahblake said:
yeah, you just don't see much Activity out of showcase users...
btw... could you help out with this??
http://forum.xda-developers.com/showthread.php?t=945069
Click to expand...
Click to collapse
We're here... For the most part i'm waiting on a stable 2.2 or 2.3 based rom. Running pick-n-pack for now with Voodoo5.

Whenever I got to the terminal emulator and do the "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" it comes back with a permission denied and then reboots the phone...I've check my spelling/case numerous times. Following the instructions on the original post/thread where the zip file came from goes ok, but the recovery rom doesnt allow me to install the VooDoo in the next step. Any help would be great.
Thanks.

blroberts228 said:
Whenever I got to the terminal emulator and do the "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" it comes back with a permission denied and then reboots the phone...I've check my spelling/case numerous times. Following the instructions on the original post/thread where the zip file came from goes ok, but the recovery rom doesnt allow me to install the VooDoo in the next step. Any help would be great.
Thanks.
Click to expand...
Click to collapse
you more than likely are going to need to install Root Explorer onto your phone.. And use it to move the files (that's what I and many others had to do)

blroberts228 said:
Whenever I got to the terminal emulator and do the "redbend_ua restore /sdcard/recovery.bin /dev/block/bml8" it comes back with a permission denied and then reboots the phone...I've check my spelling/case numerous times. Following the instructions on the original post/thread where the zip file came from goes ok, but the recovery rom doesnt allow me to install the VooDoo in the next step. Any help would be great.
Thanks.
Click to expand...
Click to collapse
Are you typing su first to grant root permissions? You should see a # instead of a $ at the prompt.
Sent from my voodoo froyo Mesmerize

I have root manager installed and used it to move the files from the /sdcard directory to /system/xbin and I am typing su at the terminal to change from $ to #
One more question:
Do I need to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=860250
or the ones that are in the first post of this thread?

blroberts228 said:
I have root manager installed and used it to move the files from the /sdcard directory to /system/xbin and I am typing su at the terminal to change from $ to #
One more question:
Do I need to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=860250
or the ones that are in the first post of this thread?
Click to expand...
Click to collapse
Long press on the Redbend_ua file and click permissions, there should be one check missing, check that so that all are marked. Save and exit.
will Root Manager allow you to do this? If not Rootexplorer will.
if you do this:
I'm not sure if you can do this through terminal or not... I did mine from my pc... you may have to leave off adb shell and just start at su when using terminal...
This is making the file executable
adb shell
su
chmod 777 /sdcard/redbend_ua
while it's still on the sdcard (Before moving it then you don't need to worry about it)
Ok, it seems that the Mes instructions were infact different on this method... I've updated the first post... If you'll read now you'll see what you should be typing in..
sorry about that, and thanx for pointing it out

I'm sorry, I am using Root Explorer...and yes, I have all 777 permissions to the redbend_ua file under /system/xbin, the only thing that I can think of is by looking in the /sdcard directory, there is no recovery.bin file that the last terminal command is referring to...is there suppose to be, if so, it comes from the voodoo mesmerize post...am I suppose to download that?

blroberts228 said:
I'm sorry, I am using Root Explorer...and yes, I have all 777 permissions to the redbend_ua file under /system/xbin, the only thing that I can think of is by looking in the /sdcard directory, there is no recovery.bin file that the last terminal command is referring to...is there suppose to be, if so, it comes from the voodoo mesmerize post...am I suppose to download that?
Click to expand...
Click to collapse
did you also get the zImage file? it was included in the test_no_voodoo.zip
If you did that step then you need to download ClockworkMod from the market and install the fascinate version of recovery.

elijahblake said:
did you also get the zImage file? it was included in the test_no_voodoo.zip
If you did that step then you need to download ClockworkMod from the market and install the fascinate version of recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=860250
look at that thread and tell me where you're at....

Yep, ive done all of that stuff also...and whenever I take the entire zip file, rename it to update.zip and reboot into recovery it tells me that the sdcard is busy

Lg Optimus V development thread

Hopefully we get an lg optimus v section. But here goes something for starters.
These different posts will contain everything you need for now (i hope who am I kidding) Any ways here is my latest deodexed rom.
Features:
Completly de-odexed
new bootanimation
no virgin mobile apps
custom bootimage
new keylayout ( camera button opens the camera not focus, side voice control is power button, changed all the buttons to stop unlocking the screen except for the menu button)
Stagefright enabled
I'm preparing some final things but I wanted to get this going.
Download here

How to root the lg optimus v use one click root more coming soon

How to get into diag mode coming soon

How to install a custom recovery more coming soon
download here

Stock Rom with su and custom bootimage only
Download here

How to remove apps using adb
To me the best and free way to remove apps from your phone is via adb. Hopefully you have some familiarity with adb if not you should be good after reading this.
First open a command prompt and type
Code:
adb remount
this will allow you to do what we need to do if you have errors then you need flash one of the roms I provided.
then type
Code:
adb shell
cd /system/app
ls
this opens adb shell commands then opens the system directory and shows you whats in it. If you are using the deodexed rom you will have nothing but .apk files in there. But if you use the stock rom then you will have .apk and .odex files in there.
look through there and figure out what apks you want to delete and then type
Code:
rm whatever.*
replace whatever with the app you want to remove
for instance
Code:
rm googlevoice.*
then type
Code:
cd ..
cd ..
cd /data/data
pm uninstall com.googlevoice
this part here changes your directory to data/data and then it completes the uninstall. You may have to guess what the name is in data/data but usually it isn't that hard. Also you can't pm uninstall apps from data/data unless they have been removed from /system/app so don't be worried about removing the wrong thing.
check your phone and you should be good to go

I'm going to get one this week. Thaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaanks!

Are there any ROM & kernel pack with ext4 support?

r0bot said:
Are there any ROM & kernel pack with ext4 support?
Click to expand...
Click to collapse
Xiona is what I use

Xiona works really good, there are some forums with a stock VM rom with Xiona in it.

teki9 said:
Xiona is what I use
Click to expand...
Click to collapse
So Xiona has ext4 support?

Emergenscene said:
Xiona works really good, there are some forums with a stock VM rom with Xiona in it.
Click to expand...
Click to collapse
What ROMs support ext4 also?

not to bring up a dead threaad....but the optimus v really needs a home here at xda.
i just rooted my first. i tried to use a windows program called "romtools" found on the interwebz. this didnt work, though. so...after a little more searching...i found this out. maybe the opt can put this up in first post?
easiest way to root and install super user: run super one click root to obtain adb shell root. then...run z4root. neither of these two methods work on their own but if you do in that order...you will have root and super user installed. from there, you can flash a recovery using android terminal emulator...if your old school like that. i did.
after that you can flash the stock virgin with Xionia kernel and bloatware removed. get setcpu..overclock it. whatever. door is open.
hope this helps! trying to get some thank you points on the board.

back again to try to keep this thread a little bit up to date til SOME1 NOTICES THAT THIS PHONE EXISTS.
for those having the "Cell standby" battery bug....
whats that? go to setting>about phone > battery usage> if cell standby is at anywhere near 50% or over...you have this bug. antenna constantly scans even with a connection...
plugg phone into charger. toggle airplane mode. unplugg. this will clear your battery stats and will properly connect you. check your setting to see if your usage goes down.
there also seems to be a problem wil gallery. the app opens but displays nothing. no albums or anythinng. its like it cant read the sdcard. only thing i can say to do is install a 3rd party pic viewer and trash 3d gallery.
hope this helps you guys.

Awesome, thanks for this. I currently have CM7 on my Optimus V, but for some reason I can't use any adb commands with it. I can with this. Sorry if this is the wrong place to post it, but I'm still a new member. Anyone know a way to get adb working?

hey did you guys ever figure out diag mode for the Optimus V? its not like the the other Optimus devices and ive tried every key combo my little brain could come up with....im trying 2 connect it 2 QPST or CDMA..