Related
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
Hi all.
Overclocking for your Rooted Droid 2 and Droid X on Linux/Mac and now Windows! Before continuing, consider this alternate method.
http://www.droid-life.com/2010/10/22/how-to-overclock-the-droid-x-or-droid-2/#more-17844
If you get a permission error through adb shell, use the Terminal Emulator app and enter SU, then run the script again.
Instruction for Mac:
1. Extract files. Doubleclick the dooverclock.zip file, and drag and drop the folder to your desktop.
2. Next, open terminal, and navigate to your folder. It'll be something like cd /desktop/dooverclock or cd /Desktop/dooverclock.
3. Now you need to change permissions to the dooverclock file. Enter:
chmod 0755 dooverclock.sh
4. Make sure you are in PC Mode. USB debugging should be enabled. Don't need icon showing.
5. Run dooverclock.sh by entering:
./dooverclock.sh
6. Follow directions of the UI.
Instruction for Linux:
1. Extract files. Doubleclick the dooverclock.zip file, and drag and drop the folder to your desktop.
2. Open the folder and right click the dooverclock.sh file. Go to permissions and go down toward the bottom of the window and check the allow file to be executed or something like that. Press ok.
3. Make sure you are in PC Mode. USB debugging should be enabled. Don't need icon showing.
4. Run dooverclock.sh by double clicking it, and choosing run in terminal.
5. Follow directions of the UI.
Instructions for Windows:
How-to Video: http://www.youtube.com/watch?v=0ieaiSxamDg
1. Extract folder from zip. Open the .zip and drag and drop the folder onto the desktop.
2. Make sure phone is in either Charge only or PC Mode with USB debugging enabled.
3. Open the folder and double-click dooverclock.bat, and follow the UI
4. Hope it succeed, check with SetCPU.
How to use the custom.sh
All you have to do is edit the custom.sh file, edit your settings, and save the file. From there, just open the scripts and choose to overclock using the custom.sh file.
Downloads for Droid 2 (Will not work for DX)
Download here (Linux): http://kimete.com/droid/dooverclock/dooverclock.zip
Download here (Mac): http://kimete.com/droid/dooverclock/dooverclockmac.zip
Download (Windows): http://kimete.com/droid/dooverclock/dooverclockwin.zip
Download for Droid X (Will not work for D2)
Download for DroidX (Linux) user (Untested): http://kimete.com/droid/dooverclock/dooverclockdx.zip
Download for Droid X (Mac) user (Untested): http://kimete.com/droid/dooverclock/dooverclockdxmac.zip
Download for DroidX Windows user (Untested): http://kimete.com/droid/dooverclock/dooverclockdxwin.zip
Changelog:
Version 1.0 - first version, messy code, just made it work
Version 1.0b - added support for Windows by Requiem
Version 1.1 and 1.1b - cleaned up interface and coding, made it more efficient running, added standalone adb file.
Version 1.2 - added ability to OC to user specs using custom.sh
References
Original procedure here: http://androidforums.com/droid-2-al...d-2-overclock-kernel-module-instructions.html
Original procedure and files by FreeWell for DX and D2. WalCs helped port stuff over to D2.
More formal information coming soon! Thank you to Requiem4D for tweaking my Windows code.
LICENSE Info: License?? Everyone is welcome to use any and/or all my code in anyway you see fit. I do ask that you do credit me if you use any portion. I also provide this code FREE of charge and I hope that everyone shares the love and does the same. I encourage you to use bits and pieces of my code if possible. There is no point in rewriting code from scratch if it has already be done! It is a WASTE OF TIME, and INEFFICIENT!! Enjoy all.
-Kevin
aka DarkOnion
Donation info: Like my script, donate to me, a poor college student. Struggling with finances and what not. A few dollars go a long way. $2.18 buys me 5 tacos from Del Taco. $1.50 gets me a small chili at Wendy's! Donate to me via Paypal at [email protected]. Please feel free to share this thread by sharing the link. Suggested donation: $0.25 to $1.
Gotta be First
Added Windows version! It ain't pretty, but it'll work. I hope...
Found something on the mac side. ADB fails to run with the version you included. Works if you copy the adb binary file from your android SDK folder. :]
EDIT: Playing around with this a bit...working great so far. Running @ 1.1GHz, pretty stable. Is there any way to add more slots? For example 300/500/700/900/1100?
When you say set with setCPU, are you referring to the market app of the same name?
I answered my own question. Running nicely at 400/700/900/1200 on Epic 2.7, this is great
getting ready to dl and try... question tho... do we need to do this after each reboot, or will this stick? (or is there a simple method from the phone since you already put the files on there?)
Thanks and keep up the good work... will donate on payday!
:O!! Will have to try after class today. Nice work!
currently you have to do it after every reboot, there is a way to make it semi permanent but you still have to execute the files on every boot
Sent from my DROID2
oshigeru said:
Found something on the mac side. ADB fails to run with the version you included. Works if you copy the adb binary file from your android SDK folder. :]
EDIT: Playing around with this a bit...working great so far. Running @ 1.1GHz, pretty stable. Is there any way to add more slots? For example 300/500/700/900/1100?
Click to expand...
Click to collapse
Oops. Duh! That's what happens when you work at code at 3 in the morning.
darkonion said:
Oops. Duh! That's what happens when you work at code at 3 in the morning.
Click to expand...
Click to collapse
S'all good. Might want to add in a script that makes setscaling.sh run on the phone at startup.
kwheel596 said:
currently you have to do it after every reboot, there is a way to make it semi permanent but you still have to execute the files on every boot
Sent from my DROID2
Click to expand...
Click to collapse
Hey darkonion, if you use this overclock method with setCPU, does the "set on boot" option from within setCPU actually work? Or does this truly have to be redone every time the phone phone is power-cycled?
bladearronwey said:
Hey darkonion, if you use this overclock method with setCPU, does the "set on boot" option from within setCPU actually work? Or does this truly have to be redone every time the phone phone is power-cycled?
Click to expand...
Click to collapse
Not sure. Sorry that I can't be much help.
Added Mac version!
Nice work Darkonion.
I am trying to make this into an Android App unless someone beat me to the punch
darkonion said:
Hi all.
Overclocking for your Rooted Droid 2 on Linux/Mac and now Windows! Instructions coming soon. General instruction for Linux/Mac:
1. Extract files.
2. Chmod dooverclock.sh
3. Make sure you are in PC Mode. USB debugging should be enabled. Don't need icon showing.
4. Run dooverclock.sh
5. Follow directions of the UI.
General Instructions for Windows:
1. Extract folder from zip.
2. Make sure phone is in either Charge only or PC Mode with USB debugging enabled.
3. Double-click dooverclock.bat, and follow the UI
4. Hope it succeed, check with SetCPU.
Download here (Linux): http://kimete.com/droid/dooverclock/dooverclock.zip
Download here (Mac): http://kimete.com/droid/dooverclock/dooverclockmac.zip
Download (Windows): http://kimete.com/droid/dooverclock/dooverclockwin.zip
Download for DroidX (Linux) user (Untested): http://kimete.com/droid/dooverclock/dooverclockdx.zip
Download for Droid X (Mac) user (Untested): http://kimete.com/droid/dooverclock/dooverclockdxmac.zip
Download for DroidX Windows user (Untested): http://kimete.com/droid/dooverclock/dooverclockdxwin.zip
Original procedure here: http://androidforums.com/droid-2-al...d-2-overclock-kernel-module-instructions.html
More formal information coming soon! Thank you to Requiem4D for tweaking my Windows code.
-Kevin
aka DarkOnion
Donation info: Like my script, donate to me, a poor college student. A few dollars go a long way. $2.18 buys me 5 tacos from Del Taco. $1.50 gets me a small chili at Wendy's!
Click to expand...
Click to collapse
MotoBoy said:
Nice work Darkonion.
I am trying to make this into an Android App unless someone beat me to the punch
Click to expand...
Click to collapse
http://androidforums.com/droid-2-al...kernel-module-instructions-2.html#post1771829
Redflea had a little how-to of sorts for a script... not exactly an app, but damn close....
Good job DarkOnion it works great the Dx board appreciates you shaved off 15minutes of work......donation
This may sound like a stupid question, but what is overclocking mean? What is the benefit of overclocking?
Thanks
Sent from my DROID2 using XDA App
Wikipedia said:
Overclocking is the process of running a computer component at a higher clock rate (more clock cycles per second) than it was designed for or was specified by the manufacturer, usually practiced by enthusiasts seeking an increase in the performance of their computers
Click to expand...
Click to collapse
The definition above is for computers, but applies to phones too. Basically we are taking the 1Ghz processor and changing it to things like 1.1Ghz, 1.25Ghz, and 1.3Ghz, etc..
kwheel596 said:
The definition above is for computers, but applies to phones too. Basically we are taking the 1Ghz processor and changing it to things like 1.1Ghz, 1.25Ghz, and 1.3Ghz, etc..
Click to expand...
Click to collapse
Thanks for the definition. What is the purpose for changing the phone's clock speed? Once I deleted the bloatware on my phone, it helped to make my phone load programs and such a lot faster.
Sent from my DROID2 using XDA App
New Windows script up. Cleaner. And should run a little more efficiently. Updated Linux and Mac version as well.
Updated windows version again!
Since people continue to only download part 1, even though I've explained fully that you MUST download BOTH parts before extracting, I have now added this at the beginning of the post, so hopefully people will actually follow the directions properly. DOWNLOAD BOTH PARTS BEFORE EXTRACTING, IT WILL NOT EXTRACT PROPERLY ONLY DOWNLOADING ONE PART!!!
This is a custom stock ROM for the Samsung Conquer 4G that has many advantages over a completely stock image. It was developed by me, Brien Johnson of XHPCreations aka brienj.
The link to the files for the ROM are at the very end of this post, but I recommend you read the FULL post while downloading the files.
- Your phone will be rooted.
- The complete FC17 update that shouldn't nag you to update to FE16. (may help to delete the FE16 update in the cache if you already had it pushed to your phone)
- Clockword Mod Recovery for making easy backups and restores.
- Completely Deodexed and ZipAligned for better performance or being able to hack further.
- All bloatware removed, i.e. SprintID
- Stock Launcher replaced by ADWLauncher. (the stock Launcher could not be deodexed, but ADWLauncher is much better and more robust)
- Debuggable.
- Custom power menu that includes, reboot, reboot into recovery, and reboot into download. (Currently the reboot into download does not work, will try to get it to work if possible in the future)
- Custom battery icons that show the actual percentage of battery power left.
- ICS Fonts for better appearance of text in phone's menus.
- Memory and network tweaks for best performance and battery savings.
- Support for running scripts on boot in init.d folder. I've included one script to help sdcard performance, feel free to add any more that you want.
- Support for standard bootanimation.zip files.
Along with these tweaks I will give instructions on improving the network performance further and changing the boot sound, as well as give links to useful programs and hacks that can be added on this phone.
I suggest only using this ROM if you have not successfully applied the FE16 OTA Update to your phone. If you have a stock FE16 phone, it MAY still work however. I can not guarantee this ROM will work for you, and I am not liable for any damage to your phone if you try to install this ...
Here are the instructions to install the custom stock ROM on a Samsung Conquer 4G with the FC17 update. It is installed in two parts, the first is if you do not already have Clockwork Mod Recovery installed, in which case follow the Odin instructions. If you have installed the CWMR already from my instructions here - http://forum.xda-developers.com/showthread.php?t=1610534 then go ahead and follow the CWMR instructions.
Odin installation instructions (Use if you do not have CWMR already installed):
To enter Download Mode on the phone, make sure the phone is turned off and plugged into the wall charging. You should also make sure the phone has a good charge on it. Then turn the phone on by pressing the volume down and camera button and holding them while pressing the power button for a few seconds.
Unzip all the files on your computer and follow these steps.
1) Enter download mode on the phone and plug it into your computer.
2) Open up the Odin program in Windows, run as administrator if on a version of Windows that has such a feature, such as Windows 7. Sorry, there is no Odin for Linux based systems that I know about.
3) Press the OPS button and select the SPH-D600_FC17_CWM_XHP1.ops file.
4) Press the PDA button and select the SPH-D600_FC17_CWM_XHP1.tar.md5 file.
5) Press the Start button, the images should install and the phone reboot.
Congrats, your phone now has my Custom FC17 ROM with a CWM Recovery.
CWMR installation instructions (Use if you have CWMR installed):
Unzip all the files on your computer and follow these steps.
1) Copy the clockworkmod folder and merge it with the folder already on your SD Card. If you do not already have that folder on the SD Card, you may not have CWMR already installed, or you've never made a backup before with it.
2) Boot into CWMR by holding the volume down button and the power button while pugged into the wall charger, or by using the adb command "reboot recovery".
3) Select the menu item "backup and restore".
4) Select the menu item "restore".
5) Select the restore named "SPH-D600_FC17_CWM_XHP1".
6) Select the menu item "reboot now".
Congrats, your phone now has my Custom FC17 ROM with a CWM Recovery.
Now that the phone has the custom ROM, here are some things you can add or do to further improve performance on the phone if you wish.
First of all I recommend installing AdFree, Terminal Emulator, Titanium Backup, and if you wish ScriptManager, which can all be found on the Google Play Store. I can help you find them if needed.
For better 3G follow these steps (enter commands into Terminal Emulator or use the adb shell):
Type this command: getprop ril.MSL
It should show your MSL. Write it down.
Open the dialer and dial ##3282##
Enter your MSL
Click on "Others"
Click on "Multimedia"
Change the settings as follows:
RTSP Proxy Address: 0.0.0.0
RTSP Proxy Port: 0
HTTPPD Proxy Address: 0.0.0.0
HTTPPD Proxy Port: 0
The stock settings are:
RTSP Proxy Address: rtsp.vog.sprintpcs.com
RTSP Proxy Port: 554
HTTPPD Proxy Address: pd.vog.sprintpcs.com
HTTPPD Proxy Port: 8085
Here is how to change the boot sound:
First of all get the "poweron.snd" file from the /system/etc/ folder. It is a raw sound file which can be opened in any audio editor, such as Cool Edit Pro.
Here are the settings to select when opening it up in Cool Edit Pro for example:
Sampling Rate: 441000
Channels: Stereo
Resolution: 16-bit
Data Formatted As: 16-bit Intel PCM
Offset Input Data By: 0
Now you can listen to the boot sound in the audio editor. You can change it to your liking and save it in the same format. Remember to keep it a RAW audio file with the settings above. Replace the "poweron.snd" file with your edited audio file, retaining the same filename.
To replace the boot animation, you can find the "bootanimation.zip" file in the /system/media/ folder. Replace it with a bootanimation file of your liking. I've included a custom bootanimation that was modified to match the custom boot logo I made. I made all of it from a popular bootanimation of which I can not remember where I found it. I am not taking any credit for the original bootanimation, I just modified it to say Samsung Conquer 4G at the top and to speed up and spin faster at the end. If anyone remembers the original creator, I will add a link to it.
A great cpu tuning program that works on the phone (although won't save settings on boot for some reason), is this - http://forum.xda-developers.com/showthread.php?t=1584508. From the screenshots below you can see that the phone will last almost 3 days without this program, although the other screenshot was using the program setting of PowerSave and after 20 1/2 hours it was still at 70%, but I also didn't use the phone, I just had it locked. However, when running in PowerSave mode, the phone will be very sluggish, so is only to use if you are just waiting for phone calls or just texting.
These are all the tweaks I have for now. I hope you enjoy the ROM.
I hate to bring this up, but if you like this ROM, please consider making a donation. I don't do this just for donations, I enjoy helping everyone out, but I was in a near fatal accident over two years ago and can no longer work. If you find yourself enjoying this ROM, please click on the Donate button under my name, I would really appreciate it. I can try to improve the ROM over time, but please remember that this ROM is strictly made for performance and battery life and to give you more control over your phone. I don't plan on doing any theming, and most people do ICS themes and such. Personally I hate the look of the ICS themes and the only thing I've taken from ICS, is the fonts, which I do like and look much better than the original. If you want some fancy theme, or mods like Beats Audio, I'd suggest looking for another ROM. If you want performance and longer battery life, I think you'll enjoy mine.
Take care and thank you for trying my ROM.
You must download BOTH of these files before you can extract them. After downloading them, put them both in the same folder, and open the part1.rar file up, and you can then extract the files properly. If you only download one of the two files, the files will be corrupted or not work:
Here is the link to the first file of the ROM - SPH-D600_FC17_CWM_XHP1.part1.rar
Here is the link to the second file of the ROM - SPH-D600_FC17_CWM_XHP1.part2.rar
I apologize for having to split it into two files, but I have a maximum of 200MB I can upload, as I don't have a premium account at MediaFire.
Dude, your awesome.
So glad to see this!
bring on the flock of desperate Conquer users.
This is John Smith from Ting forums by the way.
Good job man. Gonna download asap.
DiehlC said:
Dude, your awesome.
So glad to see this!
bring on the flock of desperate Conquer users.
This is John Smith from Ting forums by the way.
Good job man. Gonna download asap.
Click to expand...
Click to collapse
Cool. I hope it works great for you.
You were able to install my other one, so you have CWMR already, right? If so, I recommend just updating that way as it's of course much easier.
Thanks for your hard work, looks great...
brienj said:
Cool. I hope it works great for you.
You were able to install my other one, so you have CWMR already, right? If so, I recommend just updating that way as it's of course much easier.
Click to expand...
Click to collapse
Sure do, so yup thats my plan.
What do you think about "Mobile Odin" Would it also work for flashing this? for information sake atleast.
DiehlC said:
Sure do, so yup thats my plan.
What do you think about "Mobile Odin" Would it also work for flashing this? for information sake atleast.
Click to expand...
Click to collapse
It probably would. Perhaps it uses the flash_image binary to flash the images properly, but I don't know for sure. You'd have to make sure you give it the correct names of the mtd partitions though, or it would know the correct names for them, but that's if it uses the flash_image binary. You can always flash these yourself with the flash_image binary using the mtd table I listed. If you have CWMR though, I'd just do it that way.
It doesn't list our phone in the compatible phones, which leads me to believe it only knows the partition tables for the phones listed. Perhaps if you gave them our partition table, they could make it work though.
john9 said:
Thanks for your hard work, looks great...
Click to expand...
Click to collapse
You're welcome. Hard work is an understatement though. When I had my accident, my head was split wide open from being struck. As a result, I have serious brain damage, although I have retained most of the smarts I had before the accident, which helps. However, it takes me months to do something like this, whereas before it would have taken maybe a week or two at the most, heck, probably a couple of days to be honest. I can not concentrate, I have to do one thing at a time, and I always forget things, even something that happened a few minutes ago. This is why I can not even work, as I can not be in a competitive work environment. Heck, even posting a post will take me close to 5 or 10 minutes, from fixing all the transposed letters, double-printing of letters, grammar, etc. The first post of the thread took me about 3 hours to finish and completely type up. It may appear from my posts, that I am smart, which I don't want to brag, but I believe I am, but because of my TBI, it's not what it appears to be, as you only see the final result after all my editing. I used to hide my problem, but I am not ashamed to admit it any more.
Thanks man this is really fast. I did a test and left my phone locked and it started out at 64 than 2 hours later it was 61!! Really good battery life.
Sent from my SPH-D600 using xda premium
Came here from the Ting forums. I just had to remember my username I created way back when I still had an XV6800. Those were the days!
Anyway, I tried downloading part 2 a few times, and every time I extract the files, it tells me the md5 file is broken. Anyone else having this issue?
bradyarz said:
Came here from the Ting forums. I just had to remember my username I created way back when I still had an XV6800. Those were the days!
Anyway, I tried downloading part 2 a few times, and every time I extract the files, it tells me the md5 file is broken. Anyone else having this issue?
Click to expand...
Click to collapse
You have to have part 1 and part 2 in the same folder, then open part1. It is a two part rar file, so uses both files. By opening just the second file, it won't all be there. But both files contain the whole package, you just need to open part 1, as long as you have part 2 as well.
I had to split the rar file up because Mediafire only allows me to upload a maximum filesize of 200MB, since I don't have a premium account. I've updated this info right before the download links.
itzdarockz said:
Thanks man this is really fast. I did a test and left my phone locked and it started out at 64 than 2 hours later it was 61!! Really good battery life.
Sent from my SPH-D600 using xda premium
Click to expand...
Click to collapse
Well that's great to hear it works ok for you and yes, the battery life, even without the cpu tuner program is FAR better than original. At least it has been for me. I can run an intensive program with WiFi and the phone would still last close to 10 - 12 hours. That was the whole goal of my ROM, was for longer battery life, since it sucks when stock, and I think I succeeded at it.
brienj said:
You have to have part 1 and part 2 in the same folder, then open part1. It is a two part rar file, so uses both files. By opening just the second file, it won't all be there. But both files contain the whole package, you just need to open part 1, as long as you have part 2 as well.
I had to split the rar file up because Mediafire only allows me to upload a maximum filesize of 200MB, since I don't have a premium account. I've updated this info right before the download links.
Click to expand...
Click to collapse
Ok, thanks. I was just a little worried because part 1 extracted fine, and part 2 always gave me an error, giving me the part 2 md5 as a 0 byte file.
I've never rooted through android before, so I want to make sure I've got everything squared away before I begin.
brienj said:
You have to have part 1 and part 2 in the same folder, then open part1. It is a two part rar file, so uses both files. By opening just the second file, it won't all be there. But both files contain the whole package, you just need to open part 1, as long as you have part 2 as well.
I had to split the rar file up because Mediafire only allows me to upload a maximum filesize of 200MB, since I don't have a premium account. I've updated this info right before the download links.
Well that's great to hear it works ok for you and yes, the battery life, even without the cpu tuner program is FAR better than original. At least it has been for me. I can run an intensive program with WiFi and the phone would still last close to 10 - 12 hours. That was the whole goal of my ROM, was for longer battery life, since it sucks when stock, and I think I succeeded at it.
Click to expand...
Click to collapse
Good to hear you are no longer ashamed, plus theres no reason to be. Especially since you can whip up great stuff like this. among other things youve done.
I havent flashed it yet, as I am backing up a lot of stuff, and trying to backup all the linux stuff I installed via opkg package manager using "BotBrew", which is getting a bit complicated. Plus I have to make a nand too beforehand.
So I should be able to get to it soon. Im excited.
But by the way, now that you have the Partitioning table layout mapped out, I wonder what we could do to further expand our internal memory/storage? I wonder if we could double partition our SD cards like some others do on other devices? They basically just format their SD with FAT32 in the first (which will be the extended internal), and the next being Ext4 for SD card storage. Seems like we should be able to do the same like anyone else, especially since you got that nice bit of info through your troubles, on the partitioning.
What do you think on this position?
Take care Brien.
DiehlC said:
Good to hear you are no longer ashamed, plus theres no reason to be. Especially since you can whip up great stuff like this. among other things youve done.
I havent flashed it yet, as I am backing up a lot of stuff, and trying to backup all the linux stuff I installed via opkg package manager using "BotBrew", which is getting a bit complicated. Plus I have to make a nand too beforehand.
So I should be able to get to it soon. Im excited.
But by the way, now that you have the Partitioning table layout mapped out, I wonder what we could do to further expand our internal memory/storage? I wonder if we could double partition our SD cards like some others do on other devices? They basically just format their SD with FAT32 in the first (which will be the extended internal), and the next being Ext4 for SD card storage. Seems like we should be able to do the same like anyone else, especially since you got that nice bit of info through your troubles, on the partitioning.
What do you think on this position?
Take care Brien.
Click to expand...
Click to collapse
I am "new" to doing all of this type of work. I used to strictly do game hacking/modding, not stuff to cheat, but to make the games better and more fun. Late last year I started getting into the Android systems and seeing what I could do. I'm sure if I looked into this stuff I could figure something out eventually, but not sure how long it would really take me. This seems like something that is similar between all phones, so maybe you should see what can be done already. If it's a phone specific thing, then one of us will have to do the dirty work. I just don't know.
i got an md5 mismatch error when trying to do the restore
New2ThaDroid said:
i got an md5 mismatch error when trying to do the restore
Click to expand...
Click to collapse
I've had that happen before. Here is the solution, but I'd try recopying it to your sdcard another time to make sure it was copied correctly - http://forum.xda-developers.com/showthread.php?t=714114
Also, are you sure you downloaded BOTH of the rar files as I said in the OP, and it did not give you any errors when extracting the files?
Also, try renaming the name of the folder to only include alphanumeric symbols.
I got an error when extracting the files too. I extracted both the files to the same folder so I don't know what the problem is and I extracted the first part first and the the second. I don't know what it is
I got it to work and the Rom on my phone. Looks good! Good job. I would like to add some themes if anyone has some or knows how I could do it myself.
Sent from my SPH-D600 using xda premium
how long
brien how long does it take the your rom to install itself using odin approximately? i ask because it took me over 40 minutes to install it and its at time of this still going
I'm going to do some themeing using UOT Kitchen
Sent from my SPH-D600 using xda premium
New2ThaDroid said:
I'm going to do some themeing using UOT Kitchen
Sent from my SPH-D600 using xda premium
Click to expand...
Click to collapse
Sure, if that's what you want. Like I said in my original post, this ROM was made to be practical, not to be fancy. It does have the ICS fonts in it, which look a bit nicer though.
This guide assumes that you are on a stock Pantech Flex P8010 running either ICS (v4.0.4). or the updated JB (v4.1.2) Please note that rooting a ICS phone has been known to cause issues when trying to run the over the air update. If you have already rooted and are looking for a way to update to JellyBean please skip to the section on updating, if this isn't you keep reading.
So at this point you have decided to continue. You shouldn't run into any issues if you follow the directions and you shouldn't mess your phone up even if root doesn't take. However, in the spirit of covering ones back side....
I am not responsible for anything that goes wrong.
Jelly Bean 4.1.2 or ICS 4.0.4
This method was found by LuneBear and has not been tested by myself so I cannot personally verify its effectiveness. I did check and it seems to work with both ICS and JB but your mileage may vary. You will need to download SRSroot and install it on a Windows machine.
SRS ROOT
SRS Homepage
Make sure that USB debugging is enabled on your phone. Connect your phone via USB and run the program. Select the button for all root methods. Then you will need to select the Legolas exploit. Once everything is done (may take some time) just reboot the phone and you should be good to go.
Ice Cream Sandwich 4.0.4 ONLY
Windows Option
This method has been tried on a number of Windows versions and some work some don't so your mileage may very. This method uses Bin4ry's Root method and was orgnially discovered by aaki_rocker and is WAY LESS COMPLICATED. However please note that some users have had issues using this method with Bin4ry's latest version of the root script. It is recommended that you download an older version if you run into any issues or the root doesn't take.
First lets get some drivers on your Windows box. To do this you will need to download the Pantech PC Suite and install it.
http://c724062.r62.cf2.rackcdn.com/PantechPCSuite_1.1.1.3437.exe
Next you will need to download and extract Bin4ry's root script.
http://ul.to/z7krermj
Once you have these two files you will need to plug your phone into the PC via USB and enable the USB type as Data Mode.
Next run the Bin4ry's script and follow the directions when in doubt about what to choose select the simplest option in all cases.
If everything goes well you will have a nicely rooted phone.
Linux Option
This is not a point and click root and is not for the faint of heart. This method of rooting is based off of Bin4ry's root for ICS/JB. Changes have been made to the srcipt to allow it to work with the Flex please follow the steps below and you will have root in just a few minutes. It will probably take you longer to download the files you need than to actually root the phone.
This method has been performed successfully using Ubuntu 12.10 64bit it may work with other versions of linux but it will not work with Windows due to the driver issues and the fact that I didn't alter the windows batch file, in fact I removed any windows related files from Bin4ry's original package.
First you will need to set up the linux machine if you don't already have it. This can be done in one of a few ways you can run a live copy using a Live CD/USB boot (this will not install linux on your computer unless you tell it to) or you can install it in the standard manner or using WUBI, the third option us setting up linux in a virtual machine. If you don't know how to do this google it, there is a wealth of information out there on these subjects and probably some you can even understand without a degree in astro-physics.
Second you will need to set your phone up so that USB debug mode is turned on [settings>developer options]. Make sure you phone isnt plugged into the USB or it won't let you change the setting.
Now plug your phone into to the (linux) computer with the USB. Next you will need to set the USB computer connection type to Media Device(MTP)
In order for the computer to communicate with the phone we will need to install Android Debug Bridge (ADB) and create a couple of files.
These files will basically trick the computer into thinking it has actual drivers for the phone.
Open a terminal window, and enter the following (this will install ADB):
sudo apt-get install android-tools-adb
Once this is done enter the following
sudo gedit /etc/udev/rules.d/70-android.rules
Gedit will open at this point copy the the following into it and then click save and close the window.
SUBSYSTEMS=="usb", ATTRS{idVendor}=="10a9:6055", MODE="0666"
In the terminal window enter this (yeah I know it looks the same just go with it)
sudo gedit /lib/udev/rules.d/70-android.rules
After the window opens paste the same line of code into the file that you did in the previous files, save and close.
Test your connection by issuing the following command in the terminal window:
adb devices
Should see something similar to:
OSCAR01111112010204 device
Your adb is now recognizing your phone and you can now move on to the next step if you are not getting this don't even bother moving to the next step it wont work. If you don't see this check your settings and go again.
Ok so you are now ready to actually root the phone. The first thing your going to need to do is download my modified Bin4ry script. See the attached file.
After you have it downloaded you will need to extract it you can do this by opening the file manager (click on the home folder icon) and going to download. Find the file called Root_Flex.zip. Right click on it and select EXTRACT HERE. After its done extracting you should see a directory called Root_Flex. In a terminal windows enter the following:
cd Downloads/Root_Flex
Your prompt should now look something like
[email protected]_name~/Downloads/Root_Flex$
From here just enter the command:
bash RunMeFlex.sh
At this point you should see a bunch of junk come up and a menu asking which way you want to try to root. Type 1 and press enter. It will give you 3 errors, ignore them. It should copy a bunch of files and ask you to press restore on your phone, do it. It should ask you to press Enter to reboot the phone, do so and the phone will reboot. It should be waiting on you to press enter again dont press enter until the phone is completely rebooted and for good measure give it an extra few seconds. The script should finish and the phone will reboot again this time you should see a little box with an update appear on the phone. At this point you should be rooted. If not try the script again.
I hope this helps out a lot of folks out there. Let me know if I need to change anything in this How to or if I made any mistakes along the way.
Updating If you're already rooted
So you rooted your phone and now you want JellyBean but when you run the update you get the dead droid image and the update fails OR you live in an area that isn't covered by AT&T and you want the update, what do you do? Well thanks to some hard work by Attn1 we have a solution and its pretty simple. First off you will need to have CWM running on the phone. Now there are a few ways to go about this but the method I used was here:
http://forum.xda-developers.com/showthread.php?t=2133857
You only need to go as far as getting CWM up an running on the phone you do not need to install it as the the update by Attn1 will take care of a full install of a better version. You will need to have a copy of Fastboot.exe and some img files. Below is a rar file that has all the necessary files to get CWM running (not installed) on the phone using windows (sorry I don't have the linux files for this one). Just unpack them into a convienent folder somewhere and follow the instructions on the link above.
http://tinyurl.com/oa2p48f
I recommend using the boot_external.img but if you do not have an external SD card and only have the internal storage just use boot_internal.img instead. This method relys on you being able to get into fast boot. If you do not have access to fastboot for what ever reason I suggest you jump ahead in the thread and read Attn1 methods for installing CWM:
http://forum.xda-developers.com/showthread.php?t=2008888&page=44
Next get the update files from this link (second post)
http://forum.xda-developers.com/showthread.php?t=2008888&page=47
Once you have all the files downloaded and copied everything to the appropriate SD cards on your phone your ready to go. If you don't know how to do this don't even think about anything else till you learn this. After this is all done follow the directions below (copied from Attn1's post)
Procedure if you ARE NOT running baseband JYUS06032013 (ICS Basebands) :
boot ICS CWM
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
restart start recovery/adb reboot recovery (JB CWM is installed - do not try to fastboot boot ICS CWM)
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
Procedure if you ARE running baseband JYUS06032013 (JB Baseband) :
get root (Instructions HERE - use GANDALF)
install CWM (Instructions HERE)
flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM
format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)
reboot to CWM
flash FLEX-JB-JYUS06032013-ROM.zip from CWM.
reboot
This ROM is Pantech stock with no mods other than CWM installation protection and all stock permissions and symlinks carefully maintained and consistent with the product of a successful OTA.
The firmware is also stock, with the exception of the open aboot allowing fastboot boot <bootimage>, and installation of JB CWM with nothing else added or changed. It runs well with nothing broken. You MUST be on JB firmware (below) to run it properly.
You can let the new CWM root it if you like when you exit - it will prompt you. It will also prompt you to disable CWM on reboot make sure this gets disabled or the phone will keep booting to CWM rather than the ROM.
Downloads:
md5: 1a0ca5f177bce2f4c428931616e0ecd1 FLEX-JB-JYUS06032013-FIRMWARE.zip
md5: 17c0e611ab6dfbca230571c1e40f3d14 FLEX-JB-JYUS06032013-ROM.zip
Make sure you check the md5sum on the files before you flash them if there wrong download them again this is vital.
If you need a program to check md5sums copy this .exe file to your c:\windows\system\ and run it from the command line.
http://tinyurl.com/l74wl9q
Thanks go to Bin4ry for the original script and all the technical help provided.
Check out the thread and give a thanks and donate a few bucks if you can.
http://forum.xda-developers.com/showthread.php?t=1886460
Thanks to Atadres for getting me going in the right direction and help testing along the way.
Thanks to Esau Silva for this post that helped get the drivers working for us in Ubutnu.
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Thanks to Aaki_rocker for coming up with the Windows version of this root method you can find his original post here.
http://forum.xda-developers.com/showthread.php?t=2141538
Thanks to LuneBear for finding the root method for JellyBean.
Thanks to Attn1 for the JellyBean update and CM 10.2 version of CWM Recovery.
jist a quick memo guys when you issue the command adb devices please cd to proper android sdk platform tools folder or else youll get an error like no command did you mean..... heres the proper way do this step before you do the adb devices step type in cd ~/android-sdk-linux/platform-tools press enter then type in ./adb devices
i am now trying to contact team win for help with porting the recovery image team win recovery so we can start roming this device and adding ports and roms
atadres said:
jist a quick memo guys when you issue the command adb devices please cd to proper android sdk platform tools folder or else youll get an error like no command did you mean..... heres the proper way do this step before you do the adb devices step type in cd ~/android-sdk-linux/platform-tools press enter then type in ./adb devices....
Click to expand...
Click to collapse
Acutally this assumes you are on a completely fresh install and did not have adb installed through the platform tools if that is the case everything I typed up will work. However you are correct too. Let me know if you think I should go ahead and rework the stuff to be a little more universal if so please PM me an update of the commands.
your right my apologies but one thing i noticed that i would like to say idk if its my experiance or universal after successfully rooting the flex the lockscreen fails to resize itself leaving a black space where the onscreen dock is usualy located no big issue though and the rooting was easy and painless once adb was set up correctly 100000+ points thanks so much
Good job guys. Respect! I have a Pantech Flex, which is an awesome device with the same specs (things that matter to me) as S3, but without big name. I like Pantech Flex because it's size is much better for me than.
The only thing now is to create a ROM! Is it difficult to make a pure Android ROM? Nothing additional, just a pure Android like in Nexus?
Again, thank you guys for your dedication! I'll definitely donate as soon as I have Jelly Bean loaded on my Pantech Flex!
Thanks, this worked great. I am gonna start on a ROM. Hope I don't get bricked.
Sent from the new Pantech Flex. Nominated best lowest priced new smartphone. U jelly I paid nothing, for a phone almost as good as the Galaxy S3?
HighCommander540 said:
Thanks, this worked great. I am gonna start on a ROM. Hope I don't get bricked.
Sent from the new Pantech Flex. Nominated best lowest priced new smartphone. U jelly I paid nothing, for a phone almost as good as the Galaxy S3?
Click to expand...
Click to collapse
lets not get ahead of ourselves here guys in order to create a rom we would need to get a custom recovery on our phone this can be achived by mapping out the devices bootloader extracting an img file of it and using koushes clockworks mod recovery creator only when we achive a port of a custom recovery can we make roms and be able to flash them if any of you have knowledge of this as i am a noob when it comes to recoveries pleasae feel free to input we need all the help we can get guys
---------- Post added at 02:03 PM ---------- Previous post was at 01:58 PM ----------
ivansana said:
Good job guys. Respect! I have a Pantech Flex, which is an awesome device with the same specs (things that matter to me) as S3, but without big name. I like Pantech Flex because it's size is much better for me than.
The only thing now is to create a ROM! Is it difficult to make a pure Android ROM? Nothing additional, just a pure Android like in Nexus?
Again, thank you guys for your dedication! I'll definitely donate as soon as I have Jelly Bean loaded on my Pantech Flex!
Click to expand...
Click to collapse
lol right now we need knowledge donations unfourtunatly we cannot start working on roms till we have a custom recovery ported over either team win or clockworks mod recovery this will take a little bit of time and knowledge and to answer your question about the stock nexus rom your talking along the terms of a cynaogen mod port? or akop port looking into it i would say untill we have mapped the bootloader we wouldnt know how diffcult it would be because the simlinks maybe difcult for a phone that has not yet caught fire in the dev world
i wish i had the time to do a recovery myself and get cwm working but with my family and my fulltime job i barely get any time. Im going to spend all my time on this amazing little phone to do what i can. props to the root method it worked flawlessly!!!
Sent from my PantechP8010 using Tapatalk 2
Awesome I'm glad im getting some good feed back on the root. I wasnt sure if I did the rightup correctly and im glad its working out for everyone.
If I get some time I will start looking into a custom CWM and all that junk I have a contact that should be a pretty good help in this just have to find the time to do it.
Yeah after coming from the LG Nitro HD I was surprised at how easy this was to root.
If you want to get together on gtalk we can work on this together. Right now I'm in the process of getting a ROM dump so we can recover our phones from stock images if we happen to mess them up, which I'm sure we will, but that's the best part! Lol.
I can smell CM9 and CM10 calling to this phone!!!
Sent from my PantechP8010 using Tapatalk 2
jSterling said:
Yeah after coming from the LG Nitro HD I was surprised at how easy this was to root.
If you want to get together on gtalk we can work on this together. Right now I'm in the process of getting a ROM dump so we can recover our phones from stock images if we happen to mess them up, which I'm sure we will, but that's the best part! Lol.
I can smell CM9 and CM10 calling to this phone!!!
Sent from my PantechP8010 using Tapatalk 2
Click to expand...
Click to collapse
Yeah I love this phone but I have to say the Pantech launcher kinda pisses me off.
donavan01 said:
Yeah I love this phone but I have to say the Pantech launcher kinda pisses me off.
Click to expand...
Click to collapse
Agreed lol im using nova
I actually don't mind the launcher, its pretty nice compared to other brand launchers. I'm probably going to try launcher pro though that's been my favorite sense I had my prepaid optimus V
Sent from my PantechP8010 using Tapatalk 2
jSterling said:
I actually don't mind the launcher, its pretty nice compared to other brand launchers. I'm probably going to try launcher pro though that's been my favorite sense I had my prepaid optimus V
Sent from my PantechP8010 using Tapatalk 2
Click to expand...
Click to collapse
I had launcher pro and hated it ... check out APEX seems like the stock ICS but with a lot of extras and without the annoying bits of the pantech that make me insane
donavan01 said:
I had launcher pro and hated it ... check out APEX seems like the stock ICS but with a lot of extras and without the annoying bits of the pantech that make me insane
Click to expand...
Click to collapse
hey guys... is there a pantech flex forum????????
also is it possible to unlock the device if you forget the log in pattern????? thanks
I don't know anything about mapping the device. So I am just going to work on a ROM for my infuse.
I will help with anything for testing. A stock image would be awesome. =-)
No flex forum yet.
_______
Sent from the new rooted Pantech Flex. Nominated best lowest priced new smartphone. U jelly I paid nothing, for a phone almost as good as the Galaxy S3?
jSterling said:
I actually don't mind the launcher, its pretty nice compared to other brand launchers. I'm probably going to try launcher pro though that's been my favorite sense I had my prepaid optimus V
Sent from my PantechP8010 using Tapatalk 2
Click to expand...
Click to collapse
sense is my fav launcher and no no forum yet ive requested and gotten no reply smh
did this thread die guys?
atadres said:
did this thread die guys?
Click to expand...
Click to collapse
Wait till after Xmas I bet you a lot of people will get this phone as presents.
donavan01 said:
Wait till after Xmas I bet you a lot of people will get this phone as presents.
Click to expand...
Click to collapse
Yeah I can see that happening. This weekend I am going to work on it to see what I can come up with. I've been so swamped with work and life bs that I haven't had a chance.
No this thread didn't die.
Sent from my PantechP8010 using Tapatalk 2
What it says on the tin. I've found lots of things about it freezing on step 7 but not step 2. I've followed the noob guide in this subforum to the T. What's going on?
Couldn't tell ya, I'm not a big fan of one clicks so I never have used them. If you would like made a quick guide on how to root without it
http://forum.xda-developers.com/showthread.php?p=40198560
Buried in this thread on like the third or so page you will find it, I've had to use this method to root countless times while I tinker with this phone, it may seem complicated but it works every time and takes me maybe 5 min from start to finish and works just fine in both windows and linux
Sent from my Nexus 7 using xda premium
demkantor said:
Couldn't tell ya, I'm not a big fan of one clicks so I never have used them. If you would like made a quick guide on how to root without it
http://forum.xda-developers.com/showthread.php?p=40198560
Buried in this thread on like the third or so page you will find it, I've had to use this method to root countless times while I tinker with this phone, it may seem complicated but it works every time and takes me maybe 5 min from start to finish and works just fine in both windows and linux
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the reply, I'm having a problem with your guide though. I get to step 7 where I have to use Heimdall but it says my phone is disconnected. I've tried reconnecting/using a different USB port to no effect.
Its probably a driver fault, but these steps (ones in red) are only if you need to restore to stock first, if you have a functioning os skip it (as the bottom of the post says, although not very clearly) if youre in download mode right now you may need to do a battery pull to get back to os, can't remember. but you can do these steps if you want. Won't hurt anything
Sent from my Nexus 7 using xda premium
Okay, I'm still having a problem though. When typing in the first line in the command prompt, it tells me adb is not a recognized internal or external command. I found that this is because I need the Android SDK which I downloaded, but it still doesn't work.
Worked around this by typing in the full path of adb.exe instead. Now Root Browser won't let me overwrite the recovery file in the system\bin folder
assuming windows, its nice to add the platform-tools into a path in enviromental variables, ill link you to a guide to do such as change directories all the time is a pain.
I use root explorer (paid app) but any root browser should work, just need to gived it read/write permissions.
Alternatively you can use a terminal emulator or adb to push the file in
Let me know if you have issues
Sent from my RubiX NonSense using xda app-developers app
http://forum.xda-developers.com/showthread.php?p=41374534