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
Related
I owe much credit to toastcfh, none of this would be possibly without his work on originally rooting the EVO.
Getting Root & Recovery Mode
(My version, dumbed down even more)
You have three options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support
3) Unrevoked Root Patch - No system access in recovery (can't remove sprint apps, etc)
To get a rooted stock ROM, you have to start with Toasts, instructions below; you can find details after.
If you want the Unrevoked Root patch, install a file browser on your EVO and install this.
1. Copy this to the root folder of the SD card, you can do this by syncing the Evo as a disc and just copying in windows.
2. Shut off the Evo, and hold the "volume down" button while powering it on until you see a white screen. Every question it asks, just answer yes. DO NOT UNPLUG, let it finish at all costs, no matter how long it takes.
3. Rename the file you copied to the SD card. (to avoid accidental re-flash and save it for later)
4. Download this and unzip to anywhere of you liking on your desktop. Run the setup, if it asks to accept and install a bunch of stuff, hit cancel, you wont be needing most of it. Select available packages and it will show a repository url, the actual url is irrelevant and will be google's be default...we want to expand the list and select SDK Platform 2.1. Accept an install the selection.
What you just did is installed the Android SDK which includes adb, a shell connector for your phone that we need to operate in recovery mode.
5. Hold the Windows key and press "R", type CMD in the run box. (Run the task with Administrative privileges if there is an option)
Type "cd " in the CMD window, do not forget the trailing space, it is important and DO NOT HIT ENTER yet.
Now, with that CMD windows open, go to the folder you installed the android sdk. There will be a "tools" folder, drag the tools folder into the cmd window.
Press enter, this will set your working directory to the tools folder.
6. If you have not installed drivers for your Evo, there is a folder that comes of the sd card called "HTC-Sync", run the setup in there and it will install sufficient drivers automatically.
After drivers are setup sync the phone using the HTC Sync mode, this will ensure we can control the phone using adb.
Go to your CMD window and type "adb reboot recovery", you will see your phone reboot...it will show a red warning icon on the screen afterwards, this is perfectly normal and good to see such.
7. Your phone should not be in recovery mode, but the filesystem will be offline. Download this to setup the shell for us before we can mount the filesystem. Run "recovery-windows.bat", if you are using Vista or Win7, make to sure right click the file and "Run as Administrator"...you will see another CMD window popup and do some work, just leave it open. You should now have the shell setup in Recovery Mode on your Evo.
8. Go back to your original CMD window we setup, type "adb shell" and hit enter, this will set all commands to work right on the phone. You should see a line with just "#", that is what we want.
Now type "mount /dev/block/mtdblock4 /system" and hit enter.
You should now have your Evo in recovery mode with a shell setup and filesystem mounted. This is where we can begin making changes.
Now that this has all been setup, you may want to go back after making some changes.
Repeat steps 5-8 to re-enter recovery mode with the filesystem mounted.
If you want to continue and do the stock update, check here.
Basically, copy that file to the SD and do steps 5-7.
Then use the onscreen (on the EVO Recovery Mode) to "Flash from ZIP" and select the rooted stock rom update.
WARNING: You must clear user data if the update creates issue, you will know right away.
so this is a third way of rooting, if i used a different way how do i get rid of it and use yours, i'm so tired and confused.
Post Removed to maintain consistancy, see 1st post in thread.
root rom and activesync?
I'm a complete noob here but: By using this method do I still retain the ability to run ActiveSync/Exchange support? (Didn't think this was in the SDK Platform 2.1)
What about Sense?
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Good noob friendly guide, kinda tldr, but what I did readlooked good!
Change ur title
Neotelos_com;
[B said:
You have two options with rooting:
1) Toasts Rooted ROM - Missing Apps in Market
2) Rooted Stock ROM - No 4G Support[/B]
....
Click to expand...
Click to collapse
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
adeyo said:
Any thought about the third option (i.e. unrevoked, new sticky, apk??) will it do the same things? i read users aren't losing full market, 4g etc.? Someone much smarter than me please weigh in.
Click to expand...
Click to collapse
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
johnsongrantr said:
What the crap is up with the title of this thread? How us this a tweak or an optimization?
Change ur title
Click to expand...
Click to collapse
I have plans for adding in tweaks, which will be delayed a bit...
Sorry for any inconvenience.
Neotelos_com said:
Yes, adding in right now...just tested and it works well.
I need to check if it allows things to be changed in recovery mode (which is important for removing the Sprint bloatware)
Click to expand...
Click to collapse
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Click to expand...
Click to collapse
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Neotelos_com said:
You can make changes like that but it will not actually save to the NAND.
So...you can remove, but it will come back after reboot.
Click to expand...
Click to collapse
Well thats all kinds of dumb..
I give it a week and there will be something better working.
Nice write up. The only problem is, I don't have the sync software on my sd card because the best buy employee knew about the evo's sd card problem and formatted it, erasing everything on the card. I checked htc's site and they had the drivers for download, but it keeps giving me an error saying it's not compatible. I'm using windows 7 64bit. Any ideas guys?
Jus10o said:
If you have root at all, and you have "rw" permissions for "system". You should be able to remove sprint apps when the phone is booted, assuming you dont have root while in recovery.
Is something different on the Evo that im missing?
can you not do this
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls
Then remove the apps like so
rm NameOfApp.apk
rm NameOfApp.odex
Not saying this will all work.. But if you have root, shouldnt this work to remove sprint apps.
Click to expand...
Click to collapse
you CAN remove apps like that, using toast's custom recovery. if you do your shell, and mount, in recovery, using adb, you can go to /system/app and rm whatever you want (be careful not to remove anything important, probably wise to pull whatever first, in case you need to push it back)
i had problems when i did an rm on a file, but that is because apparently i forgot to rm it's info in /data/data too. word to the wise
HTC Sync Torrent
http://thepiratebay.org/torrent/5609530
PLEASE SEED AFTER DOWNLOAD!
New android user here!
So to me it seems like all three have something they're not able to do. Seems best to wait for a root release that your able to take full advantage of, right?
I'm a former WM flasher , I need to learn android still. I want the free hot spot/tethering, more battery life as I need 2 batteries to make it through the day -.- (I kill apps constantly, 4g turned on rarely,ect, ect)
Any feedback is appreciated,
Sean
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
kingcliff00 said:
can someone point me in the right direction to do this using a mac not new to android just the mac os i did pretty much everything but im stuck on the htc sync part HELPPP PLZ thanks
Click to expand...
Click to collapse
Try going to Settings -> Applications on the evo and enable usb debugging...if that5 gives you adb access that's all you need
confirmed working with unrevoked root method. It can tether 3G or 4G, depends on how you connected to the Sprint network. 3G was 0.80Mbps DL, 4G was 2.63Mbps DL.
Before using unrevoked root method, I had applied the sdcard patch already. so it doesn't matter if you applied the sdcard patch or not (OTA updated).
You really shouldn't kill tasks. Just cycle the battery a couple of times and turn your antennas off and on when u need them. Especially if u are in spotty 3g coverage. There already one or two official write ups that say task killing is bad I use to do it and got forceloses and errors all the time. Its not about how many tasks you have running I.e. memory, items about cpu and antenna signal that kills you're battery I'll find the link if I can. My battery life is pretty good and I'm a heavy user.
Sent from my PC36100 using Tapatalk
i cannot get recovery bat file to work. I am at the red exclamation point screen on my evo and i run the bat file as amdmin. it pops up for a second then closes and nothing happens.
Edit: NVM I figured it out. on to the next step.
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.
First of all I noticed there is not an individual post that gives the entire root process for those that have never used ADB and probably don't have the SDK installed. In other words people that have never rooted a phone before and didn't think they ever would because they think it looks SUPER complicated.
There are several tutorial threads on this subject but I can guarantee that these are the most simple and detailed, START to FINISH, instructions regarding the root process of a HTC EVO Shift that you will find on the web. My information is compiled together from numerous sources and my own personal experience to give less confident people what they need in order to root their phone and remain at ease.
RED-REALLY IMPORTANT INFORMATION THAT YOU NEED TO READ
BLUE-Notes from my experience and further explanations
Purple-File names color coded for easy identification
NOTE: I'm not responsible if you mess up your phone, however this process worked perfectly for me and it is pretty hard these days to brick your phone unless your trying.
Rooting Process
1. First, on your computer download the program "SDK" from Here. Download the file called "installer_r10-windows.exe". Install it. When prompted for the install path paste "C:\AndroidSDK" over the default path. Once finished, open it from the Start Menu. It should be right on your "C:\" drive. Now, select "Install Packages" and make sure you install "Android SKD Platform-Tools". Once finished, close out of Android SKD and AVD Manager.
2. ONLY FOLLOW THIS STEP IF PROBLEMS INVOLVING LOADING SDK OCCURS. Next, Go to the start menu and right click on "My Computer". Select "Properties", then select "Advanced"/"Advanced System Settings", then "Environment Variables", now go to the lower box (system variables) and select "path" then "Edit". Paste the following as your path "C:\AndroidSDK\platform-tools", then select OK. This seems to have fixed most peoples problems.
3. Now, on your phone, press "Menu", then "Settings", then "Applications", then "Development". Check the box that says "USB Debugging" and press "OK" when the confirmation box appears.
4. Now, install HTC SYNC. There should be a folder on your SD card that came with the phone that has a HTC SYNC Setup in it. Just drag this to your desktop and run it. Otherwise download HTCSync. After installation, plug your phone into the computer and select "Disk drive" on your phones prompted menu.
5. Next, download the VISIONary app from Here and save it on your desktop. Once downloaded, Copy "com.modaco.visionaryplus.r14.apk" and Paste it to the SD Card root. Or in other words, drop the file in the first folder of the SD card on your phone.
6. Next, switch your phone's connection status back to "Charge Only". Use any file manager (free from the android marketplace "ES File Explorer") to install the VISIONary app on your phone. On your phone just find the visionary installer in the file manager and click to install. (Icon should look like a caution sign). Once complete, open VISIONary on your phone and click "Temproot Now". Wait for the rooting process to take place. Shouldn't take long at all. At this point your phone is rooted. However, you may noticed that your phone is running slower than normal. Go back into VISIONary and put a check next to the box that says "temp root on boot". Now power off your phone and then turn back on. This will root your phone before background apps are running, thus making it much faster.
7. Next, Download the root file Here. Once installed, connect your phone to your computer as a disk drive and right click on the "shift-root.zip", select extract here, then use browse to locate your phone, more specifically the root of your SD card. If you are having trouble extracting, download 7-Zip. Now change your connection type back to "Charge only" again.
8. Next, Open the command prompt (Start > Run > type "cmd") and paste the following...
Code:
cd C:\AndroidSDK\platform-tools
Hit enter, and type the following...
Code:
adb
If adb runs you're golden. Type this...
Code:
adb shell
Hit enter, you will see this...
Code:
$
Now type...
Code:
su
Hit enter... Now switch back to your phone. Superuser (an automatically installed program) will prompt you to "Allow" on your phone. Click it quickly to allow permissions! Now you will see this in the command prompt...
Code:
#
You have root permissions. If you didn't click allow fast enough just retype "su" and click enter again.
9. Next you have to Verify md5sum. Basically just make sure you copy and paste this EXACTLY...
Code:
md5sum /sdcard/Shift/hboot_orig.bin
Then hit enter.Your result should look like this...
Code:
386c19451e8dd18f9b98fad6b11be4c0 hboot_orig.bin
Make sure the numbers match. You may have some extra path in front of hboot_orig.bin.
If a message saying that the md5sum is not found, paste this code before verifying the md5sum. If it worked in the first place then ignore all this red...
Code:
busybox md5sum /sdcard/Shift/hboot_eng.nb0
It should work now...
Next copy and paste this exactly...
Code:
md5sum /sdcard/Shift/hboot_eng.nb0
Then hit enter.Your result should look like this...
Code:
60ec1006e6ec2e8acb370d6aad35b17e hboot_eng.nb0
Make sure the numbers match. You may have some extra path in front of hboot_eng.nbo. If these do not match do not proceed. Delete the "shift-root.zip" file on your sd card and redownload.
10. Now we're going to flash the "eng spl." This is where the unpleasant things can happen. Make sure you are in "adb shell" with superuser root permission (Granted a "#" symbol). This was explained in Step 8. If you are not in "adb shell" with root permissions (Granted a "#" symbol) then DO NOT proceed.
Now DO NOT REBOOT until you are instructed to do so!!! In the command prompt, paste this EXACTLY...
Code:
dd if=/sdcard/Shift/hboot_eng.nb0 of=/dev/block/mmcblk0p18
Hit enter. You have flashed the "eng spl." Now we need to make sure it flashed properly.
11. Run this command to pull the newly flashed "hboot" to your sdcard. Copy and paste this EXACTLY...
Code:
dd if=/dev/block/mmcblk0p18 of=/sdcard/Shift/hboot_check.nb0
Hit enter. Next you need to check the "md5" to see if it matches. In the command prompt, Copy and paste this EXACTLY...
Code:
md5sum /sdcard/Shift/hboot_check.nb0
Hit enter. It should read...
Code:
60ec1006e6ec2e8acb370d6aad35b17e
if the "md5sum" matches then congratulations its safe to reboot!! you can skip the next bit and continue on to step 12.
If you absolutely cannot get the eng hboot to flash right then copy and paste this into the command prompt...
Code:
dd if=/sdcard/Shift/hboot_orig.bin of=/dev/block/mmcblk0p18
Hit enter. Then pull it to check "md5". Copy and paste this exactly...
Code:
dd if=/dev/block/mmcblk0p18 of=/sdcard/Shift/hboot_check1.bin
Hit enter. Then check the "md5sum" by copying and Pasting this exactly...
Code:
md5sum /sdcard/Shift/hboot_check1.bin
Hit enter. It should read...
Code:
386c19451e8dd18f9b98fad6b11be4c0
If it doesn't, keep trying the previous 2 codes until it does but DO NOT!! reboot till it matches.
12. Now we can Perm root!!! First you need to reboot your phone into "bootloader". Do this by turning off phone and hold (power + volume down) till it boots into bootloader. Look at the top and make sure it says "s" off. If so, reboot the phone back into android by turning off and then back on.
13. Next Put the phone into airplane mode (hold down power and then click "airplane mode"). Go to setting, applications, manage applications and uninstall superuser.
14. Next, temp root with visionary. After you are temp rooted then attempt to perm root with visionary. Your phone will reboot and you are now officially perm rooted any changes you make will now stick on reboot. If it didn't stick, try doing steps 13 and 14 again.
YOUR PERMROOTED
Simplified Backup (with WiMax Backup!)
1. Find "ROM Manager" in the Market (free or paid) and install the app.
2. Open it and select "Flash ClockworkMod Recovery".
3. Click on "HTC Evo Shift 4G" and then give the app root permission if it prompts you.
4. Once the flash is successful, you should see a dialog box that says "Successfully flashed ClockworkMod recovery!"
5. Press OK.ClockworkMod should now be installed on the HTC Evo Shift 4G.
6. Before you backup your phone, open the ROM Manager application and select "All Clockwork Recoveries".
7. Select the most recent version, currently it is v.3.0.1.4 (If you already have the most current version skip to step 6)
8. Press OK.
9. Your phone will flash the most current recovery image.
10. Now once your phone finished, open ROM Manager and select "Backup Current ROM".
11. Press OK.
12. Your phone will begin the backup process, including backup of your WiMax Partition.
13. Once finished your phone will restart. DONE! A backup is now on your memory card.
UnRooting
1. Be sure HTC Sync is installed on your computer. (Link to download near top of first post)
2. Download the sprint RUU Download.
3. Plug your phone in to your PC, select "charge only", then run the RUU File
Sources:
More Detailed Perm Root Instructions
Beginner's Guide to Installing the SDK and Getting Started with ADB
ADB/Fastboot Easy 5 Minute Setup
All About Rooting the HTC Shift: FAQ's & How To's
IF YOU THINK ANY OTHER INFORMATION SHOULD BE ADDED FEEL FREE TO SHOOT ME A PM AND I'D BE HAPPY TO ADD IT.
ADDITIONALLY IF THIS GUIDE HELPED YOU OUT FEEL FREE TO LEAVE A THANK YOU.
There's already a guide and its pretty basic
Sent from my PG06100 using XDA App
JKILO said:
There's already a guide and its pretty basic
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
I understand there are already guides but they are not necessarily for people that have never rooted a phone before... And that is what this guide is for.
Other guides assume people have all the required software preinstalled and that they know what the guide is referring to when it says to "flash" certain things. They also assume people know how to Temp root using VISIONary and how to check the md5sum. This is for people that have done absolutely nothing to an android phone before and have no clue what the other guides are even talking about.
And yes I understand there are simplified guides that involve individual steps but this is a BEGINNING to END guide for Dummies so there is no need to jump across multiple threads.
To each their own..maybe someone will find a use
Sent from my PG06100 using XDA App
i did. thanks
nice work - seems to be the one from either androidforums.com or Androidcentral forums.
This sort of does exist, maybe not so colorfully, but here is Brando's thread
http://forum.xda-developers.com/showthread.php?t=934165
JKILO said:
To each their own..maybe someone will find a use
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
The process in the first Perm Root guide seems simple now, but when I was first looking at the guide it was a foreign language. Did my research by looking through about 6-7 other threads and finally had some idea as to what it was talking about.
Completed a successful root on my own phone and made the first draft of this tutorial along the way. More and more info has been added to this guide as I learn more and more. Now its about a month later and I've learned quite a bit about my phone and whole rooting process in general. I've once again updated the guide to make it as simple as possible with my newly acquired knowledge. This guide has over 2500 views on another thread I initially posted and numerous people have used it to root their phone so I figured I'd post it up here as well in order to help more people.
Nice A-Z guide. When I rooted mine a month ago, I needed to get info from 2 or 3 threads and tie missing pieces together. This ends that. It is a great start to finish guide. The other ones assume that you have done this before or only provide half of the entire solution needed to get everything done.
Only suggestion, clockwordmod backs up wimax after a particular version, you may want to state that as a disclaimer...else someone may grab an old version, assume they are fine, and will/could be screwed...
riggsandroid said:
nice work - seems to be the one from either androidforums.com or Androidcentral forums.
This sort of does exist, maybe not so colorfully, but here is Brando's thread
http://forum.xda-developers.com/showthread.php?t=934165
Click to expand...
Click to collapse
I initially posted it on androidforums.com
Similar, but I went one step further than Brando and explained every process in detail. For instance, rather than saying "setup adb" and "temproot your phone using visionary" I explained the process. I know that I myself looked up how to setup adb and temp root my phone when I got to those steps. Figured I'd put everything in one thread to make it easier for people that have never touched an android before.
umrico said:
Nice A-Z guide. When I rooted mine a month ago, I needed to get info from 2 or 3 threads and tie missing pieces together. This ends that. It is a great start to finish guide. The other ones assume that you have done this before or only provide half of the entire solution needed to get everything done.
Only suggestion, clockwordmod backs up wimax after a particular version, you may want to state that as a disclaimer...else someone may grab an old version, assume they are fine, and will/could be screwed...
Click to expand...
Click to collapse
Thankyou.
I stated that clockwork can backup wimax but I'll be sure to add that it is clockwork mod version 3.0.1.4 in the OP.
JKILO said:
To each their own..maybe someone will find a use
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
IF you don't have something constructive to share.....! STFU
bash78 said:
IF you don't have something constructive to share.....! STFU
Click to expand...
Click to collapse
The threads aren't for flaming..I was just pointing out it had been done but hey you go girl
Sent from my PG06100 using XDA App
Small complaint, but kinda a big deal. You need to make sure to actually list your sources especially when you're taking directions word for word out of other threads. You must give credit where credit is due. That said, it is a great writeup, though a bit overwhelming. I wrote a guide that looks very similar to this at SDX: http://forum.sdx-developers.com/evo-shift-development/(guide)-root/
Not quite as detailed as yours, but informative nonetheless. Overall, great work, just site your sources in the OP and you'll be good to go.
tambourineman86 said:
Small complaint, but kinda a big deal. You need to make sure to actually list your sources especially when you're taking directions word for word out of other threads. You must give credit where credit is due. That said, it is a great writeup, though a bit overwhelming. I wrote a guide that looks very similar to this at SDX: http://forum.sdx-developers.com/evo-shift-development/(guide)-root/
Not quite as detailed as yours, but informative nonetheless. Overall, great work, just site your sources in the OP and you'll be good to go.
Click to expand...
Click to collapse
My sources are, and always have been, at the bottom of my post...?
And basically everything has been changed rather than just taken word for word due to the fact that I wanted it to be as understandable as possible. Most of it I wrote myself using other guides as a framework but the steps are all the same...
Sorry about that. I read through the whole thing but totally missed it. I apologize profusely for missing that and the post that resulted from it. I guess I'm just used to seeing credits at the top. Again, my bad, I'll be more careful in posting criticisms in the future.
Lol. No hard feelings. I was just really confused.
Thank you !!!! Im a dummy and this helps alot!! I thought my phone wasnt getting temp root because it was running so slow using visionary,and now i know why!!!!
Soon to be shifty rooted!!!
Stuck at installing the "installer_r10_windows.exe"
I get the message of the JDK is not found. I have installed/reinstalled 3 times with only the same results.
Steps 3-7 went through without any problems at all.
Any thoughts?
Your going to need to install the Java Developement Kit (JDK) in order for the android SDK to be able to install.
Download
It will prompt you to register it and make a Oracle account after it installs.
It should have prompted you to download the JDK during the SDK install if you don't have it on your computer already?
SHMaRiM said:
Your going to need to install the Java Developement Kit (JDK) in order for the android SDK to be able to install.
Download
It will prompt you to register it and make a Oracle account after it installs.
It should have prompted you to download the JDK during the SDK install if you don't have it on your computer already?
Click to expand...
Click to collapse
I assumed that it would have been, but it wasnt. I've done it a couple of times already, but was not successful. Even after it was registered. It still keeps telling me that I need to install the JDK as it was not found.
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. as I am copying most of this from elijablake . . . so thanks this thread needs some editing, and I will be working on that in the future . . . . specifically the CWM / ROM manager which will not work. I could use some assistance in rewriting that part. TY!
BEST. ADVICE. EVER. #samsung-mesmerize on irc.freenode.net
<3<3<3<3<3
Also, read the Glossary for definitions and such. I was not the sharpest tool in the shed and it took me a while to find this . . .
Disclaimers
CSOUTH IS RELEASEING 2.2 UPDATE THIS WEEK (6/26). You may just want to wait for that to be released. This thread will be updated when the release occurs as how to flash recovery that you can flash roms with etc.
Keep in mind there are many variations to each step, this is what worked for me the easiest. READ ALOT BEFORE PROCEEDING WITH ANYTHING!!
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 ).
Steps to get to 2.2 (EB11) on your phone:
**Please note that the links were removed by CSouth for copyright (COPY WRONG *****ES) reasons. So if you can find the files somewhere (ahem . . . ) then you can follow these steps. THIS GUIDE IS PURELY FOR EDUCATIONAL VALUE, I DO NOT ADVOCATE BREAKING COPYRIGHT LAW.
I highly recommend using Heimdall rather than Odin. Don't ask me why . . . maybe because it has a command line utility and it is cross platform. So my instructions will be for using Heimdall.
After you have the downloaded files (from wherever you might have gotten them, you bad bad person) unzip and look for the following files:
-factoryfs.rfs
-modem.bin
-recovery.bin
-zImage
1) Put your phone in download mode by powering down your device, removing the battery, connecting the USB to your computer, and holding the volume down button. It shouldn't take long. You should see a little Android with a shovel.
2) In Heimdall, if using the GUI, put all of the files in their obviously appropriate spots. Don't worry if not everything is filled, just use the files that you have. (You should be using the repartition with the .pit file, the zImage with the Kernel, the recovery, and the modem)
If using the command line utility, cd to the directory where you unzipped the files and
Code:
heimdall flash --repartition --pit atlas_v2.2.1.pit --factoryfs factoryfs.rfs --kernel zImage --modem modem.bin --recovery recovery.bin
Wait for the process to finish, your phone will reboot at the end.
3. That is all, now your phone is updated to 2.2.1. Put the battery back in and boot your new shiny toy!
DO NOT DISCONNECT USB DURING THIS PROCESS AS IT COULD BE POTENTIALLY DISASTROUS!!! DON'T EVEN TOUCH IT AS I HAVE FOUND THE USB CONNECTION TO BE A BIT FLAKY!
Also, it is ok if it takes your phone what seems like forever to boot. This happens whenever you install a new kernel, just be patient.
If you have gotten the most updated batch of files, you should have the proper recovery to begin flashing. If not, well seek help . . . You should have RED RECOVERY!
See here for more information about CWM or go on irc.
To access recovery, you can use the three 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.
You should then go here to check out themes and mods.
Steps For Rooting either 2.1 or 2.2.1
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.
**NOTE: most custom roms come rooted, so if you are installing a custom rom in 2.2.1, you most likely don't have to go through these steps. Just flash to the ROM you want . . . ***
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. 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)
THE ECLAIR SECTION IS REMOVED AS CSOUTH IS RELEASING UPDATE THIS WEEK (6/27)
Hehmmmm....
nice write-up!
Upgraded the Showcase to 2.2.1 build EE25 with Samsung Kies this morning. Also had no issue rooting with superoneclick.
cpflow said:
Upgraded the Showcase to 2.2.1 build EE25 with Samsung Kies this morning. Also had no issue rooting with superoneclick.
Click to expand...
Click to collapse
Kies has 2.3 out now =)
Kies Mini have 2.3.5 out now for generic cdma showcase.
Sent from my SCH-I500 using Tapatalk
*Edit*
It seem everyone forgot about the Samsung Showcase Galaxy S Generic CDMA.
I managed to Root it flash CWMR and flash TSM TW 4.0 ROM. but then try to go back to stock and lost 3G. So I returned it and get a new one. No more mods for me I'm done no one cares about Generic CDMA.
Can someone provide directions to install a custom rom for a Showcase running stock 2.3.4? I don't have root. I'd really appreciate any help!
Script removed/Effort "canceled" (see release notes)!
Dear fellow XDA'ers, i have written a quick and simple script to tie in all of the great work done by jcase and beaups that helps you root your Moto X. This script simply follows the instructions written by jcase and beaups and automates those scripts with a simple menu.
This script should technically work for "any" Moto X on "any" carrier, provided the methods contained within have the same success rate across all carriers. I do not have the capacity, nor experience, to trap for all situations.
This script ASSUMES that you already have the Motorola drivers installed and your device has successfully connected to your computer via USB Debugging Mode. If you need the drivers, they can be found here.
Instructions:
Download and extract this script on to your Windows Desktop.
Download ALL of the following to the same folder as the GO!.CMD ("640k's Moto X Root Script" Folder). These files should NOT be unzipped:
your specific 4.2.2 factory image.and/or 4.4 factory images (if you are on 4.4, you will need BOTH images).
jcase's RockMyMoto (4.2.2) and SlapMyMoto (4.4).
beaups' MotoWpNoMo.
Saurik's Cydia Impactor
Execute Go!.CMD and follow the on-screen prompts.
Links:
Moto X Firmware Page
jcase's RockMyMoto Thread
jcase's SlapMyMoto Thread
beaups' MotoWpNoMo Thread
Saurik's Cydia Impactor Page
Disclaimers:
I make no warranties of any kind regarding the accuracy or efficiency of this script or the processes contained within. This script was tested on a single device and was written based off of the instructions provided within these forums. You can perform these steps yourself!
jcase will NOT support the use of this script. Should you run in to issues with any of the functionality/procedures written specifically by jcase, you will not be supported by jcase unless you are following his methods.
beaups will NOT support the use of this script. Should you run in to issues with any of the functionality/procedures written specifically by beaups, you will not be supported by beaups unless you are following his methods.
Because I have compiled other's hard work into a command-line script, i have decided to distribute my script uncompiled. That way, in the event of major changes, significant errors, etc., that I don't have time to address, the user community can lend a hand. If you find my work useful, please Thank Me.
WARNING
Make sure your device is fully charged before beginning!
Some people have reported an inability to flash their device, have received "unknown errors", weird partition errors and general chaos during the flashing/imaging process. If this happens to you, try a different USB port. I have read threads/seen reports where sometimes USB 3.0 ports cause failures during this process. Change to a USB 2.0 port and try again.
[*]In general, it is difficult to completely brick your device using this method. As long as you can get to the fastboot menu, your device is recoverable. If your phone will not power on, you did not follow one of the two warnings above.
TIPS:
If "Waiting for device" seems to be taking a really long time (your device is ready, but the script hasn't picked it up yet), try either turning off USB Debugging and then back on, or try removing the USB cable and re-inserting it.
If you are on 4.4, looking for root, your device will be re-imaged two times with 4.2.2. Don't input your details until the 2nd time, to avoid having to repeat your effort.
Connect to your WiFi before enabling USB Debugging Mode to avoid IP Address errors. The batch script tends to get funny on some of the retries. I've tried working out most of the bugs.
I'm confident I haven't worked out 100% of the bugs in this script, although I've tried very hard. I've only tested it with one device, the XT1060. If you have issues, please do not PM me, post them here in the thread.
If for some reason the script abnormally ends or you close out of it, without running the cleanup process at the end, ADB will remain present and cause an error in the script, which will cause the script to fail. Browse to the folder with the CMD prompt and type "ADB kill-server" (kill-server is case-sensitive). This will get the script running again.
Thanks jcase, beaups, saurik and anyone else who has contributed to this effort!
Changelog:
1/9/2014: Initial Release. Only tested on one device. Better bug management within each step, more options at advanced menu, including ADB Debug Window. Removed auto-upgrade to 4.4. I suspect this is where my woes were.
1/9/2014: Removed ADMINISTRATOR requirement. I don't think this will do any harm, but it was creating conflicts with Windows 8.
1/9/2014: Changed TELNET conditions to trap for user interaction.
1/14/2014: Adjusted initial TELNET session.
1/14/2014: Corrected a type on line 366 (would have given an error).
1/15/2014: Re-worked TELNET routine again.
1/16/2014: Simplified menu options, included automated checking for write protection. This check will skip steps once WP has already been turned off.
1/16/2014: Included additional instruction, including more messaging and better message waiting.
1/16/2014: Added additional messaging for troubleshooting purposes.
1/16/2014: Corrected a bug related to BATCH language that was ending the TELNET steps.
1/17/2014: Made another adjustment to TELNET handling.
1/17/2014: Added additional error checking.
1/17/2014: Added some wait time on the second TELNET phase.
2/28/2014: Canceled script effort (ran out of time). With 4.4.2 released, none of the current root methods are valid or work.
BEFORE YOU START WITH ANY METHOD THAT REQUIRES YOU TO WIPE YOUR DEVICE, MAKE SURE YOUR DEVICE IS 100% FULLY CHARGED!! IF YOUR DEVICE SHUTS DOWN WHILE THE SYSTEM IS FLASHING YOU WILL BRICK YOUR DEVICE!!!
heck yes!!!!!!!!!!!!!!!!!!!
Hold the phone. The script at the very last step isn't working. Can't fix right now. My personal device doesn't have root, so it failed. Will need to troubleshoot.
Appreciate the effort put into this for the community
Sent from my XT1060 using xda app-developers app
ok so the script seems to be doing what it's designed to do, which is good. but i've borked my device testing it, which is bad. but i was able to trap for more conditions and provide a better menu system, which is good.
as soon as i can figure out if i can un-bork my device, i'll post the script back up.
My device has root. Script is back online.
I really appreciate your hard work. I've had trouble getting this to work by myself. I'd love to give this a shot later today. I had a few questions though.
You said to "install the script" after it is downloaded but what exactly needs to be installed? Also you said to put all the files in the install folder, but I'm not seeing an install folder in the extracted .rar.
I want to make sure the script runs smoothly so it would be best if I could see exactly how your files are set up. Would you perhaps be able to upload a screenshot?
Thanks!
flipfreak said:
I really appreciate your hard work. I've had trouble getting this to work by myself. I'd love to give this a shot later today. I had a few questions though.
You said to "install the script" after it is downloaded but what exactly needs to be installed? Also you said to put all the files in the install folder, but I'm not seeing an install folder in the extracted .rar.
I want to make sure the script runs smoothly so it would be best if I could see exactly how your files are set up. Would you perhaps be able to upload a screenshot?
Thanks!
Click to expand...
Click to collapse
so my original intention was to distribute this as a self-extracting EXE but because i wanted to share my work and XDA's attachment policy, i changed it to a rar.
just unzip it (anywhere). you'll get a "640k's Moto X Root Script" folder. make sure your .zips from the links above are in the same folder as the Go!.CMD and you'll be good to go.
640k said:
so my original intention was to distribute this as a self-extracting EXE but because i wanted to share my work and XDA's attachment policy, i changed it to a rar.
just unzip it (anywhere). you're get a "640k's Moto X Root Script" folder. make sure your .zips from the links above are in the same folder as the Go!.CMD and you'll be good to go.
Click to expand...
Click to collapse
Thank you! That clears things up. I'll give this a try later and let you know how it went
flipfreak said:
Thank you! That clears things up. I'll give this a try later and let you know how it went
Click to expand...
Click to collapse
based on my testing, unless something goes completely wrong, it should be pretty hard to completely bork your phone. if you get into a bootloop, the advanced menu can help you restore your system files as long as you can get in to the bootloader (usually you can).
640k said:
based on my testing, unless something goes completely wrong, it should be pretty hard to completely bork your phone. if you get into a bootloop, the advanced menu can help you restore your system files as long as you can get in to the bootloader (usually you can).
Click to expand...
Click to collapse
Hmm, well I tried it but it keeps telling me that 7za.exe is not in the folder, even though it is sitting right above Go!.CMD. Any idea why it would say this? I ran it as an administrator
flipfreak said:
Hmm, well I tried it but it keeps telling me that 7za.exe is not in the folder, even though it is sitting right above Go!.CMD. Any idea why it would say this? I ran it as an administrator
Click to expand...
Click to collapse
can you screen shot the window and your folder where the files are?
thanks.
640k said:
can you screen shot the window and your folder where the files are?
thanks.
Click to expand...
Click to collapse
Sure
flipfreak said:
Sure
Click to expand...
Click to collapse
did you extract the contents to your desktop? i'm guessing it's failing because you're technically not running the cmd file in the same folder. for example, windows will allow you to run files directly from a .zip, but it caches that file in to a temp folder somewhere. if you haven't unzipped the files, the script won't see any of the files.
i'm here to help, i want this to be successful.
640k said:
did you extract the contents to your desktop? i'm guessing it's failing because you're technically not running the cmd file in the same folder. for example, windows will allow you to run files directly from a .zip, but it caches that file in to a temp folder somewhere. if you haven't unzipped the files, the script won't see any of the files.
i'm here to help, i want this to be successful.
Click to expand...
Click to collapse
Yeah, the files are all extracted to my desktop. If I run it as an administrator, it gives me the error telling me that that 7za.exe is not in the folder. If I don't run it as an administrator, it tells me that it will abort and to press any key to continue. When I press any key, it brings me to the menu where it asks me what I want to do.
I'm not sure what I could be doing wrong. Maybe we should just wait and see if anyone else has this problem. It could be on my end.
flipfreak said:
Yeah, the files are all extracted to my desktop. If I run it as an administrator, it gives me the error telling me that that 7za.exe is not in the folder. If I don't run it as an administrator, it tells me that it will abort and to press any key to continue. When I press any key, it brings me to the menu where it asks me what I want to do.
I'm not sure what I could be doing wrong. Maybe we should just wait and see if anyone else has this problem. It could be on my end.
Click to expand...
Click to collapse
ok i'm seeing the same issue. it's isolated to Windows 8. troubleshooting now.
Windows 8 is running the CMD prompt from /WINDOWS/SYSTEM32... which is the exact problem i detailed earlier. i'm going to remove the admin requirement. i don't think it's necessary.
flipfreak said:
Yeah, the files are all extracted to my desktop. If I run it as an administrator, it gives me the error telling me that that 7za.exe is not in the folder. If I don't run it as an administrator, it tells me that it will abort and to press any key to continue. When I press any key, it brings me to the menu where it asks me what I want to do.
I'm not sure what I could be doing wrong. Maybe we should just wait and see if anyone else has this problem. It could be on my end.
Click to expand...
Click to collapse
download the new file and try it again.
640k said:
download the new file and try it again.
Click to expand...
Click to collapse
That got it working. I'm now stuck at attempting a telnet session. Should I restart? Here's a screenshot
flipfreak said:
That got it working. I'm now stuck at attempting a telnet session. Should I restart? Here's a screenshot
Click to expand...
Click to collapse
i was afraid of that. open the TELNET.ERR file with notepad and show me the contents. jcase stuck some user interaction in there that only occurs one time, so i was never able to trap it again.
thanks for your help.
640k said:
i was afraid of that. open the TELNET.ERR file with notepad and show me the contents. jcase stuck some user interaction in there that only occurs one time, so i was never able to trap it again.
thanks for your help.
Click to expand...
Click to collapse
No problem.
ÿýÿý ÿûÿû
~ $ [6ndalvikvm -cp /sdcard/RockMyMoto.jar RockMyMoto
RockMyMoto 1.0
by Justin Case
PayPal Donations maybe sent to: [email protected]
Special thanks to saurik, you rock!
System is write protected...
Executing step 1...
To use RockMyMoto you most solve a
simple equation. This helps ensure
you are paying attention, and also
amuses JesusFreke and myself.
Solve for a:
a/24=70
Please type a whole number as your answer:
Click to expand...
Click to collapse