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,
It's my first Android tablet... so pls be gentle.
I got the Transformer last night and I rooted it based on the guide :
[GUIDE] ROOT for ASUS eee pad transformer (TF101)
http://forum.xda-developers.com/showthread.php?t=1035197
I got it working with BLOB_V5.
But I just found out my back camera is not working (front working fine)
I think the reason is my Build number HRI66.US_epad-8.2.2.6.1-20110325.
I didnt update to the latest one which is 8329.
So, I would like to know how can I update it to 8329?
I tried just put the zip file in and ran it, then it reboots and goes into the CWM Recovery. And seems like it wont allow me to update...
So, my guess is to remove CWM and unroot it.
BUt how can I get back to the stock?
It's my first time rooting... so I am not sure what should I do next...
Thanks in advance
Bump
10 characters
I believe you have to download the official update off the asus site push the blob included in the update and run the dd command using the asus blob instead of the cwm blob
Also the easiest way to fix the camera is to just flash a rom (prime or titx) my camera and bluetooth were shot after i rooted. Flashing prime fixed and is running great
lordgodgeneral said:
I believe you have to download the official update off the asus site push the blob included in the update and run the dd command using the asus blob instead of the cwm blob
Click to expand...
Click to collapse
^This and I just did it.
Sent from my HTC Eva 4G using Tapatalk
toni8284 said:
Hi,
It's my first Android tablet... so pls be gentle.
I got the Transformer last night and I rooted it based on the guide :
[GUIDE] ROOT for ASUS eee pad transformer (TF101)
http://forum.xda-developers.com/showthread.php?t=1035197
I got it working with BLOB_V5.
But I just found out my back camera is not working (front working fine)
I think the reason is my Build number HRI66.US_epad-8.2.2.6.1-20110325.
I didnt update to the latest one which is 8329.
So, I would like to know how can I update it to 8329?
I tried just put the zip file in and ran it, then it reboots and goes into the CWM Recovery. And seems like it wont allow me to update...
So, my guess is to remove CWM and unroot it.
BUt how can I get back to the stock?
It's my first time rooting... so I am not sure what should I do next...
Thanks in advance
Click to expand...
Click to collapse
hmm... Maybe, you can try reset to default of TF101 as following step.
settings -> Privacy -> personal data -> factory data reset
Just to be clear...
lordgodgeneral said:
I believe you have to download the official update off the asus site push the blob included in the update and run the dd command using the asus blob instead of the cwm blob
Also the easiest way to fix the camera is to just flash a rom (prime or titx) my camera and bluetooth were shot after i rooted. Flashing prime fixed and is running great
Click to expand...
Click to collapse
I just want to be clear before I attempt to unroot. If I understand the above post correctly, I would modify the instructions to read:
Code:
Return to the shell from step 6 and do the following commands:
11. run “dd if=/data/local/blob of=/dev/block/mmcblk0p4″
12. reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob”
That is, of course, after downloading the zip from Asus and unzipping it to get to the actual blob named "blob" and pushing that to /data/local with adb. Am I correct? And someone has done this successfully? I just want to be 100% clear.
Buee said:
I just want to be clear before I attempt to unroot. If I understand the above post correctly, I would modify the instructions to read:
Code:
Return to the shell from step 6 and do the following commands:
11. run “dd if=/data/local/blob of=/dev/block/mmcblk0p4″
12. reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob”
That is, of course, after downloading the zip from Asus and unzipping it to get to the actual blob named "blob" and pushing that to /data/local with adb. Am I correct? And someone has done this successfully? I just don't want to be 100% clear.
Click to expand...
Click to collapse
Yup. That's exactly what you do.
seshmaru said:
Yup. That's exactly what you do.
Click to expand...
Click to collapse
I purchased a previously rooted transformer and wish to unroot it. This is my first android device so I have read up and done my homework and now I believe I am ready to un root the device. These questions may be redundant, but all I have to do is push the blob from the most recent asus firmware update to the transformer, and then run it as outlined in step 11? Or do I have to follow steps 6 through 11 to a T in order for it to un root properly. I am fairly sure I can disregard the steps 1-5, correct? I just need a little (lot) of clarification since I am an Android virgin so to say.
edit: deleted because it's not working
followed it to a tee and it is boot looping now what?????/
Oh No!
fullthrottleenergy said:
Yup. First thing is download the asus firmware and extract the blob and then push it to data/local
7. run “adb push blob /data/local”
This takes about 5-10 minutes as it's a pretty big file.
Once that's complete type in adb shell and you should be in root (#). then just type or copy and paste from below and reboot.
11. run “″
flashing of the “blob”
Optional but I did it. After it reboots I reset it to factory (in settings). Then I copied the Asus folder (newest firmware) and placed it on my microsd card and let it do its thing. Remember to back up anything on the internal memory as it's going to get wiped when you do a factory reset.
Click to expand...
Click to collapse
I pushed the blob with no problem then typed "adb shell" to get to root and copied and pasted "dd if=/data/local/blob of=/dev/block/mmcblk0p4" and pressed enter. Upon reboot, I saw the progress bar fill up and then the Transformer rebooted. Now it is in a continual loop where it restarts (and my windows xp recognizes it), makes a click noise, shows the EEE Pad with the ASUS below start up screen, then after about ten seconds restarts to the home screen all over again. If i try to start in recovery mode it attempts it enter it, then I get the triangle with the exclamation point in it next to the android logo. I seriously think I'm fuc*ed. I knew I shouldn't have tried this. AND I REALLY NEED HELP! please I'm begging anyone. I've only had the thing for a week!
this is how I fixed mine.
same issue.
put on your micro sd card in the root of the card the update normally found in the asus/update/ folder you download from asus. I used the .9 us update worked fine, you must then rename it to EP101_SDUPDATE make sure you leave it a zip dont change the extension make sure it is on the root of the card.
then put your card in your transformer, hold the down volume and power till it prompts you in the upper left let go and push down on the volume again, which will load the factory recovery and will begin to flash the update do not bother it. it will restart and your good.
For anyone else that wants to unroot, the step mentioned previously work, I've done it myself and my Transformer no longer has root or CWM and it kept all of my information intact. You just download the firmware from Asus, extract to the point that you get a large file (mine was ~500MB) named 'blob', push that to your SD card, run the dd command swapping out the name of the file. My dd command if section looked like this "if=/sdcard/blob" and change nothing else of that command, reboot and it'll do its thing. Not sure about the bootloops. That is the ONLY command I modified and issued, nothing else from the tutorial, just that command.
My phone was in ED2, Vodoo kernel, and this is what I did
I wanted to put it in simple steps, hope it helps others:
1.-disable vodoo from CWM
2.-you will hear the sexy voice converting the file system back to EXT2, let it finish.
3.-verify you disabled vodoo, i used adb shell mount command in my windows machine, but you can run quadrant, if you get about 900, you dont have vodoo anymore.
4. download ED1 File and use odin to flash it, the file is stockrootedED1-20110517.tar.md5 http://www.multiupload.com/MU_JWDLBJO4B2
5-Once you finish flashing reboot, and you will need to setup your phone again, once you finish, you will get the prompt about the system update, EE4, Accept it, and let the phone install the update
6- when it finishes updating you can verify that it updated by going to settings, about phone, it will have in baseband, Two lines, the first one will be I510.06 v. EE4
7. at this point I advise to download and copy this file to your sd card: http://www.androphiles.com/files/android/sdcard_patch_by_kejar31.zip is a patch to fix an issue that makes the sdcard only readable.
8. download, extract and put in your computer this file: http://www.androphiles.com/files/android/EE4dxvodo_DXC.tar.rar
9. flash with odin the CWM, From here : http://www.mediafire.com/?qgy4pm23xp67usj
10.Flash with odin EE4Xvodo_DXC.TAR.
11. reboot your phone to CWM, install the file sdcard_patch that you put in your sdcard in step 7,
12. Restart your phone, you should listen to the sexy voice conveting the file system to ext4, once finished, you are done.!!. If you dont hear the sexy voice look in hour vodoo folder.and delete disable_lagfix file and reboot. Then you will hear the sexy voice
13. you can verify you have root by installing titanium backup, it will ask you for root permission.
hope it helps.
you forgot to add imnuts debloat v4.2.1 in there, although not everyone wants/chooses to debloat.
Thanks for the post. That's the route I did as well. Heck, I think I'm the first to go that route.
yeah, you are right, I just installed the stock EE4, but after all this you can install any rom you want. thanks for pointing that out.
After all this I won't have Voodoo lag fix anymore , right ?
what if I want it back after updating ?
yeah, you will have vodoo, look in step 10, you will hear the sexy voice converting the file system to EXT4, (vodoo)
Thanks,
Downloading,will report back !
BTW you have 2 step 10 !!!
ups, thanks for noting
I have voodoo but there is no disable_lagfix file in its folder !
would that be an issue ?
then just go to CWM, and disable vodoo from the vodoo menu
Thanks ,
this might sound stupid but the only way i can boot into CWR is to use rom manager and then when I get the error on boot I pull out the battery and kepp pressing vol up/down while pressing power !!!
is there any other way to boot straight into CWR ?
Update:
figured it out forgot about the home bottom !
sure, go to this page http://developer.android.com/sdk/index.html and install the sdk for windows, follow the steps, once you are done, you will end up with a folder in your c:\program files called android, inside, will be a folder called android-sdk, inside a folder called platform tools, which contains a program called adb, right click in computer, click properties, click on advanced system settings, click the environment variables button, below system variables scroll down to find path, select it and click edit, click to the end of the line, put a semicolon ; and put the path to the platform tools folder, something like C:\Program Files (x86)\Android\android-sdk\platform-tools, note I have x86 because I have a 64bit windows , if you dont have a 64bit windows, then it will be C:\Program Files\Android\android-sdk\platform-tools.
once you do this, go to your phone settings, and enable debuggin in settings, applications, developement, connect your phone and open a command prompt (click start, and type CMD, press enter, then type adb, if you see adb responding with help, then you are good to go, press adb shell rebot recovery this will reboot your phone into recovery.
i just diabled voodoo and installed gummy charge 1.5 (since i was on gummy charge 1.0 already) and then installed most current cwm is that right?? i believe im on ee4 because the build prop says ee4...Am i all wrong?
yeah, you are, some people reported issues when installing EE4 without downgrading first, I just did it this way and it worked perfectly because I installed the update straight from verizon.
i have the new CWM ,
the only thing is everytime that i try to flash VooDoo, I get the yellow CWM nad I press restart and it doesn't install VooDoo !
Any suggestion ?
Look in the voodoo folder and see if you have.the.disable lagfix file if you do delete it
that's it I guess but even though I have flashed Kejar31 sdcard patch my sdcard seems to be read only !
Working on it, will report back !
brandonaspencer said:
i just diabled voodoo and installed gummy charge 1.5 (since i was on gummy charge 1.0 already) and then installed most current cwm is that right?? i believe im on ee4 because the build prop says ee4...Am i all wrong?
Click to expand...
Click to collapse
In Settings> About Phone, Baseband Version should be i510.V6 V.EE4, if not, you don't have the full EE4 update.
Sent from my SCH-I510 using Tapatalk
Just wanted to thank you, everything seems to be working fine...
just the market is not showing some of the apps and the fix is not working for me !
What rom did tou install?
Sent from my SCH-I510 using XDA Premium App
GummyCharged 1.5
the market fix worked after 5 tries !
Everything seems to be working fine now, Thanks jorge3687...
Here are the files and instructions to get root and CWM on a Samsung Conquer 4G with the FC17 update. 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.
Here are the files you will need -
CONQUER-ROOT.zip
Unzip all the files on your computer and follow these steps.
1) Enter download mode on the phone and plug it into your computer. Open up the Odin program. Then press the OPS button and select the SPH-D600_FC17_CWM.ops file. Then press the PDA button and select the SPH-D600_FC17_CWM.tar.md5 file. The press the Start button, the images should install and the phone reboot. Congrats, your phone now has a stock FC17 image with a CWM Recovery.
2) Next, copy the Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip files to the root of your SD Card after booting up.
3) Once the phone boots up, go into settings, select Applications, then Development, then turn on USB debugging. Now you can restart the phone into recovery mode with adb. If you don't want to use adb, you can plug the phone into the wall and turn it on while holding the volume down and power button. Either way is fine, as long as you now get the phone into recovery mode.
4) The phone should now go into CWM recovery. Go to install zip from sdcard and select the Superuser-3.0.7-efghi-signed.zip file you put on the sdcard and install that. Next select the su-bin-3.0.3.2-efghi-signed.zip file from your sdcard and install that.
5) Congratulations, you now have a rooted phone with the FC17 update. If you had CWM installed before, you can now do an advanced back-up, and just restore the data from your most recent backup and get all your data back.
I've created a new custom ROM here - http://forum.xda-developers.com/showthread.php?p=29369141
You can just download the new files and follow those instructions if you haven't installed this yet.
it work like charm thank you very much sir very good job done..........
---------- Post added at 04:47 AM ---------- Previous post was at 04:38 AM ----------
there is any custom rom kool one ...
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
AestenD said:
I know on the E4GT, sfhub is able to make tar's that do not wipe user data. The file difference between the 2 images are
removed: boot.bin, sbl.bin, param.lfs, cache.img, data.img
intact: recovery.bin, hidden.img, factoryfs.img(largest file) modem.bin and zImage(contains the kernel)
The Question I'm posing to you is which of the files in the conquer tar.md5 might be the counterparts to the above files, making them the ones to strip out in order to make it not wipe data?
My wife never wanted me to root her phone until recently, so no cwm backup that's pre-OTA, and there are some apps that don't work when re-installed (a security key-gen app)
Any help would be much appreciated.
Click to expand...
Click to collapse
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
brienj said:
Take out userdata.yaffs to retain your data, BUT you will have to rebuild the tar file and remake the OPS file by removing the line that reads -
Code:
9,userdata
If you need the Linux commands to rebuild the image, let me know.
Click to expand...
Click to collapse
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
AestenD said:
Crap, and me with no Linux box lol
I'll figure something out, I have a live CD around here somewhere.
Click to expand...
Click to collapse
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
tar -H ustar -c adsp.mbn amss.mbn appsboot.mbn boot.img cache.yaffs mibib osbl recovery.img system.yaffs > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Click to expand...
Click to collapse
You can replace each package_name with whatever you want it called.
brienj said:
Just install Cygwin and use that and then extract all the files out of the .md5 file, it's just a regular tar file with md5 sums in it. WinZip, WinRAR, etc. will easily extract the files from it. Then use these commands to rebuild the image without the userdata.yaffs file.
You can replace each package_name with whatever you want it called.
Click to expand...
Click to collapse
Thanks for your help, took me a bit, because I mistakenly flashed the non-CWM image first, and the bootloader version just wasn't letting me in. Luckily I have a jig for my SGS2, and I'm up and running now. Hopefully just the fact that it's the full image, rather than OTA upgraded will fix some of the issues she's been having. If not, then having root gives me so many more troubleshooting options.
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
"known issue" just keep going, it'll work just fine.
Sent from my SPH-D710 using Tapatalk
sromero619 said:
give me an error says the SPH-D600_FC17_CWM.tar.md5 is invalid image type please help
Click to expand...
Click to collapse
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
i did all the step but when i hit start on the odin it says please connect phones what can else can i do. loaded the drive from super one click because my laptop running windows seven wasn't reading my phone. Its reading my phone I downloaded the usb driver from this link http://r2doesinc.bitsurge.net/leaked/
now when i run odin now it say """an unnamed file was not found""" whats to do please help
brienj said:
It says this, even with an official Sprint Odin image. It will still work, like AestenD mentioned.
Click to expand...
Click to collapse
i got the phone to be read but now when i hit the start button a window pops out says "unnamed file is not found"
It worked for me.
Question
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
roofus1812 said:
I have been reading up on this phone since I ordered it from my new provider. I should get the phone sometime later today and wanted to get everything ready to root it as soon as I get it. I've read JWhip804's tutorial on how to root the Conquer. I've also been keeping up with chrystal0925's efforts at making a working themed ROM.
My question is, if I want to have a recovery of my stock phone just in case I have to send it back to my carrier, should I use the method described in this thread or use JWhip804's thread?
I have a brand new Samsung Conquer SPHD600BKS on the Sprint network using a new provider to my area called Ting.
Android Version: 2.3.4
Baseband Version: S: D600.12 x.EG15
Kernel Version: 2.6.35.7-perf
Build Number: GINGERBREAD.EG15
Hardware Version: D600.12
Thanks.
Click to expand...
Click to collapse
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Finished
brienj said:
Super-One-Click only works on EC15, and you can not do an OTA update to FC17 with root, and once you do update to FC17, Super-One-Click will no longer work to root your phone, so you must use the method I have made in this thread, or a similar one to it. You MUST get a stock FC17 image with the CWM recovery to push root onto your phone, as the OTA update has recovery updating scripts, etc. in it, and it's just easier to use the FC17 image and not bother with making the OTA able to be rooted. In order to get the phone back to a stock image, you can easily find the stock Odin image that is floating around, or change the recovery image in the Odin file I have in this thread, with a stock recovery image.
Click to expand...
Click to collapse
I just finished backing up my Conquer using this guide. It was really easy. Thanks.
Hi guys. Anyone use tethering with this? I had tethering working on the old rom fine and another unrooted phone with the ota update. I got a replacement phone and tethering does not work. It only works for google sites - with any tethering app i tried. Is it the hardware or maybe its the stock fc17? I tried reflashing and clearing everything and the problem persists.
I tried using Odin today to root my Samsung Conquer and had a bit of trouble. When I attached the .tar file it gave me an error but as I read this thread I just kept going as if there was no issue. About half way through the Odin installation my phone just rebooted, I tried again and it rebooted it the same spot. I tried putting my phone back into download mode and continue the process, which it did, and I got a "Pass" message at the end. But I don't have CWM and I'm almost positive its still not rooted. Any suggestions?
Any chance of an update with the new OTA included?
Sent from my SPH-D710 using xda premium
There is a new ota fe17. Does anyone know if it will break root? Will it install?
Sent from my SPH-D600 using XDA
Hi people. Ive just bricked my Relay by installing Chainfire3D(dont laugh at me I know im stupid)))). So can anyone do a backup the system by Recovery mode and send me to my email [email protected] or attach it here, I will put it in my SD and do a restore from recovery mode(i didnt brick it fully, I guess its called softbrick).
I would really appreciate anybodies help. Please people I really need help...Thanks in advance)))
Just flash a new ROM in recovery, or if you plan to just do a restore of a system partition you would need to give out more information as to flash the correct one as each ROM will have a different system partition
the cavaca
Hey, just emailed the stock ROM, and the stock Recovery. You will need to install the stock Rom first, then flash the stock recovery. Hope it helps.
SuddenGun007 said:
Hey, just emailed the stock ROM, and the stock Recovery. You will need to install the stock Rom first, then flash the stock recovery. Hope it helps.
Click to expand...
Click to collapse
Thanks man, really appreciate your help.
HaykKarapetyan said:
Thanks man, really appreciate your help.
Click to expand...
Click to collapse
To install I need to know a couple of things, are you using a computer with Windows? Also do you have a custom recovery on your phone? Hold onto the Volume up key+Home+Power, when it vibrates and shows "Recovery Mode" in little blue letters on the screen let go of the buttons and it will boot into recovery mode. If it looks like the picture here [cdn.droidviews.com/wp-content/uploads/2013/01/android-recovery-on-galaxy-s3.jpg], this is stock recovery. If it has "ClockworkMod Recovery" you are off to a good start. Let me what you have.
SuddenGun007 said:
To install I need to know a couple of things, are you using a computer with Windows? Also do you have a custom recovery on your phone? Hold onto the Volume up key+Home+Power, when it vibrates and shows "Recovery Mode" in little blue letters on the screen let go of the buttons and it will boot into recovery mode. If it looks like the picture here [cdn.droidviews.com/wp-content/uploads/2013/01/android-recovery-on-galaxy-s3.jpg], this is stock recovery. If it has "ClockworkMod Recovery" you are off to a good start. Let me what you have.
Click to expand...
Click to collapse
So my computer runs Windows Vista and i have ClockworkMod Recovery. At the bottom in the Recovery mode it says CWM- based Recovery v6.0.1.2
HaykKarapetyan said:
So my computer runs Windows Vista and i have ClockworkMod Recovery. At the bottom in the Recovery mode it says CWM- based Recovery v6.0.1.2
Click to expand...
Click to collapse
So to get back to stock, on your recovery there should be an option to sideload a file using ADB. Your going to have to use these instructions to get ADB onto your Windows install.
1. Make sure Java is installed on your system go to.....www.java.com/ and install their version, and restart computer if necessary.
2. Then go to http://developer.android.com/sdk/index.html to download the SDK for android allowing use of ADB. You will need to extract this folder to your C: drive. 1-Create a folder on the root of your C: called Android, then unpack the SDK you downloaded into this folder, and open up sdkmanager.exe and install updates and packages. The main one you want is called "platform-tools" which holds the ADB.exe file you will need.
2.A) Make sure you clear/format your cache/dalvik cache/ and data before you flash the zip in the instructions below.
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you.
4. Now it will be waiting for the program you just installed to "push" the zip to your phone. So go to the Start menu, and type in the search box cmd and hit enter.
5. Now type in "CD C:\Android\(**whatever SDK file you have**)\platform-tools\" and hit enter. When typing you can hit the TAB key to autocomplete the folder name. Now your directory should of changed, and you should be able to type "adb sideload (you will need to type in the full path of the file where you stored the Stock JB image at (the one I emailed you). and hit enter. Once it sideloads you should be able to reboot and it will bootup regularly, after this I would suggest flashing philz touch recovery which has a few more features.
SuddenGun007 said:
So to get back to stock, on your recovery there should be an option to sideload a file using ADB. Your going to have to use these instructions to get ADB onto your Windows install.
1. Make sure Java is installed on your system go to.....www.java.com/ and install their version, and restart computer if necessary.
2. Then go to http://developer.android.com/sdk/index.html to download the SDK for android allowing use of ADB. You will need to extract this folder to your C: drive. 1-Create a folder on the root of your C: called Android, then unpack the SDK you downloaded into this folder, and open up sdkmanager.exe and install updates and packages. The main one you want is called "platform-tools" which holds the ADB.exe file you will need.
2.A) Make sure you clear/format your cache/dalvik cache/ and data before you flash the zip in the instructions below.
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you.
4. Now it will be waiting for the program you just installed to "push" the zip to your phone. So go to the Start menu, and type in the search box cmd and hit enter.
5. Now type in "CD C:\Android\(**whatever SDK file you have**)\platform-tools\" and hit enter. When typing you can hit the TAB key to autocomplete the folder name. Now your directory should of changed, and you should be able to type "adb sideload (you will need to type in the full path of the file where you stored the Stock JB image at (the one I emailed you). and hit enter. Once it sideloads you should be able to reboot and it will bootup regularly, after this I would suggest flashing philz touch recovery which has a few more features.
Click to expand...
Click to collapse
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions
HaykKarapetyan said:
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions
Click to expand...
Click to collapse
605 MB I should have said......what I meant was that in your first reply you told to install rom and then flash recovery and I dont think all that is done by only these 5 steps
HaykKarapetyan said:
While my drivers are installing I wanted to ask abot this:
3. Now connect your phone to your computer via usb, and boot into recovery, you will need to choose install zip/sideload with adb (these are generic instructions since I have a different recovery than you. How should I chooseinstall zip/sideload with adb? 5) should I use recovery.img??? And what about that huge mb thing that you sent to me, what shiold I do with that....I should have warned you that I dont have a lot of experience in all this stuff and I need stepbystep less technical instructions
Click to expand...
Click to collapse
Since you have ClockworkMod you won't be needing the "stock-recovery.zip" I sent you. You will only need the "JB-stock-system.zip". Now when the drivers install make a checklist and make sure you have Java installed...and then the Android SDK. It really is a 3 step process, but since you soft-bricked your phone you can't simply copy the stock-system.zip to your sdcard and flash that in recovery. You will need adb to communicate with your phone while in recovery.
SuddenGun007 said:
Since you have ClockworkMod you won't be needing the "stock-recovery.zip" I sent you. You will only need the "JB-stock-system.zip". Now when the drivers install make a checklist and make sure you have Java installed...and then the Android SDK.
Click to expand...
Click to collapse
So in 5th step I should locate to that 605mb.zip,without extracting it
stimuli erpio
HaykKarapetyan said:
So in 5th step I should locate to that 605mb.zip,without extracting it
Click to expand...
Click to collapse
Yes that is correct, the recovery when it installs will unpack it for you.
SuddenGun007 said:
Yes that is correct, the recovery when it installs will unpack it for you.
Click to expand...
Click to collapse
Alright man, thanks. Still installing the freaking drivers)))
HaykKarapetyan said:
Alright man, thanks. Still installing the freaking drivers)))
Click to expand...
Click to collapse
I am using Linux, otherwise I would try to send you the drivers.
You might be able to use this http://www.solvusoft.com/en/update/drivers/mobile-phone/samsung/t-mobile/sgh-t699/model-numbers/
SuddenGun007 said:
I am using Linux, otherwise I would try to send you the drivers.
Click to expand...
Click to collapse
Naah thanks its fine, the computer's too old and tries to find some sort of update every single time I plug my phone in and takes hours to just say that the drivers are ip to date and im good to go, before all that ipdate stuff it doesnt let you to use the phone......well thats what you get from (at least) 6 year old Vaio Sony laptop))))
HaykKarapetyan said:
Naah thanks its fine, the computer's too old and tries to find some sort of update every single time I plug my phone in and takes hours to just say that the drivers are ip to date and im good to go, before all that ipdate stuff it doesnt let you to use the phone......well thats what you get from (at least) 6 year old Vaio Sony laptop))))
Click to expand...
Click to collapse
Oh crap I didnt see you had a link there, let me check that one out
This isn't probably the best thread to suggest this, but I recommend you look into a linux distro to install on your laptop. Before I had my current one, I was on a 7 year old HP compaq, and I put Lubuntu on it, and made it pretty much brand new. The only thing is getting used to the Linux filesystem,and commandline. Might take a few weeks of using it, but it really helped me out when XP was terribly slow. It also installs ADB and can interface with android phone. Maybe try a liveUSB so you don't have to install it.
SuddenGun007 said:
This isn't probably the best thread to suggest this, but I recommend you look into a linux distro to install on your laptop. Before I had my current one, I was on a 7 year old HP compaq, and I put Lubuntu on it, and made it pretty much brand new. The only thing is getting used to the Linux filesystem,and commandline. Might take a few weeks of using it, but it really helped me out when XP was terribly slow. It also installs ADB and can interface with android phone. Maybe try a liveUSB so you don't have to install it.
Click to expand...
Click to collapse
Thanks for advice... I guess I'll be getting a brand new computer in two months so and I was thinking of what I should do with this one, now I know)))), thanks....Can you believe it still tries to find and update something, I mean its horribly slow......anyway so one question just arose, if luckily, hopfully I get my phone back will it be still rooted or will I have to root it???
HaykKarapetyan said:
Thanks for advice... I guess I'll be getting a brand new computer in two months so and I was thinking of what I should do with this one, now I know)))), thanks....Can you believe it still tries to find and update something, I mean its horribly slow......anyway so one question just arose, if luckily, hopfully I get my phone back will it be still rooted or will I have to root it???
Click to expand...
Click to collapse
With the stock I gave you, you will not be rooted, it will appear as if you just turned it on for the first time, if you want to be root and use Cyanogenmod, I suggest instead of sideloading the image I gave you, go here and download this and sideload this rom (this is stable 10.2)
http://download.cyanogenmod.org/?type=stable&device=apexqtmo
Also here is awesome instructions (stepbystep) to install everything on it.
http://wiki.cyanogenmod.org/w/Install_CM_for_apexqtmo
SuddenGun007 said:
With the stock I gave you, you will not be rooted, it will appear as if you just turned it on for the first time, if you want to be root and use Cyanogenmod, I suggest instead of sideloading the image I gave you, go here and download this and sideload this rom (this is stable 10.2)
http://download.cyanogenmod.org/?type=stable&device=apexqtmo
Also here is awesome instructions (stepbystep) to install everything on it.
http://wiki.cyanogenmod.org/w/Install_CM_for_apexqtmo
Click to expand...
Click to collapse
Ok so if I download this and lets say put this zip in c:\Android what command should I run in cmd???