Related
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.
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...
OK, I've read a lot of comments about people having trouble installing MoDaCo clockworkmod, or even turning their devices S-off. But my guide is going to go step though step of how to turn your device into a lean, mean killing machine. It took me days to accomplish this when i first got my device, hopefully this will take you under 30 minutes! I'm a junior member, i know, so cut me some slack, PLEASE.
WARNING AND DISCLAIMER: I AM NOT RESPONIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE. FLASH AT YOUR OWN RISK, EVEN IF IT FALLS APART IN YOUR HAND, OR BECOMES GODLY FAST!
1. The first thing we need to do is turn S-OFF for your mytouch 4g slide. It is probably the easiest thing to do, other then installing a rom on your device.
a. You will need to download the usb drivers for your phone, DON'T SKIP THIS STEP, or you'll wonder why your phone isn't discovered by the software. You can find those drivers at this website right here:
http://www.htc.com/managed-assets/support/software/htc-sync/setup_3.0.5579.exe
After you have that software installed, plug in your phone, and give it a couple minutes to install all the correct drivers for your device, then make sure you go to the bottom right of the computer and exit out of that software, it can't be running when your trying to S-OFF your device. Now I dont think you have to have the fastboot drivers installed either, but why not, lets go ahead and download those files and get those installed too.
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
After you have those installed, its now time to move on.
b. Now thanks to unrevoked and AlphaRev and their team, you will go to their site at http://revolutionary.io/ and you will scroll down and click on Download for Windows (If you can take everything I'm saying and do the linux version, right on!) at that moment a download box will appear, but do not download those files, download the files from this website http://www.megaupload.com/?d=BP2E3ZQ3 .But you will need to enter some information in the box below after you click on windows download, just remember, you don't need those files. Your operating system, device, HBOOT version, and serial number. Your HBOOT version can be found by taking your device, going to apps, settings, power, and uncheck fast boot, then power it off, i always power it off and then pull the battery out, makes me feel safer...and soon as its off, holding the volume down button, camera button, and power button all at the same time. You'll then see a screen with the android bots on the bottom are rolling on skateboards. At the top should be your HBOOT version, and there is only one option on the site, so hopefully your in luck! For your serial number,take the battery out from this screen, don't push any buttons, and on the sticker under the battery, your serial number will be there starting with HT--- or power your device back on, then go to apps, settings, about phone, phone identity, and wala, your device serial number. After you enter all that information into the site, it will generate you a beta key, YOU NEED THAT IN ORDER TO S-OFF AND ROOT YOUR DEVICE!! So write it down somewhere, copy and paste in word, do what you do
c. Now we have everything downloaded, we have our beta key, its time to get to work!
d. The file you downloaded from megaupload, "MT4GS-ADB-WINDOWS" you need to extract that file into a folder on your desktop. Make sure you open the folder mt4gs-adb, and extract the files out of the folder, so you should have 12 items in your folder on the desktop, not just a folder in a folder! I created a folder called "root mt4gs". You want all the files in one location. After there all extracted, open your folder on the desktop. On your phone, go to apps, settings, applications, development, and click on usb debugging and make sure the check mark is blue on the right. Now plug your phone into the computer.
Now in your "root mt4gs" folder, double click on revolutionary. At that moment it should ask you for that beta key i told you to save. Go ahead and enter that now (its case sensitive). Let the software run for a couple minutes....
Now after it says S-Off, your halfway there!! Your HBOOT will now say 1.44.1107. That way you know its done! It will ask you to install clockwork recovery mod, say NOOOO, it has hella problems. It gave me problems when i said yes the first time, i'll show you another way.
e. At this moment, we're going to install clockwork recovery v4.0.0.9, thanks to Paul O'Brien/MoDaCo, the gods lol. First, turn your device off/pull the battery out, thats what i do. Then hold volume down button, camera button, and power button at the same time. It should show you the skateboarding androids, and at the top it should say -Revolutionary- in purple. If it doesn't, don't continue, retry all steps or message me. Then plug your phone into the computer, and using the power button as the selection button, push the power button as your highlighted over FASTBOOT. It should say FASTBOOT USB at the top in red now.
Now believe it or not you already have the file you need in your "root mt4gs" folder. Your now going highlight all the files in your "root mt4gs" folder to the root of your hard drive. Click on My computer, double click on your c: drive, and paste those files right on there, do not copy the folder, or put these files in a folder!! Now your going open a command prompt. {Hold the windows key and tap r}. Then type "cmd" without the parenthesis and it should open up a black box.
Now type cd\
Your command prompt should now just say c:\> thats what you want it to say
Now your going to type adb.exe
You should see a whole bunch of words flash on the command prompt, the last couple words should say "bug tags are printed." That means your right on track.
From here, you are going to type in fastboot devices
it should have the serial number of your device and the word fastboot right next to it!
Now, here comes the tricky part that i got stuck at, but i know you can do it! Now this will work if you put the files exactly where i told you to put them. you now will type fastboot flash recovery c:\clockworkmod.4.0.0.9.img
it should say " sending 'recovery'
okay
writing recovery'
okay
finished. total time: (mine is 10.400s)
Now to make sure it's intalled, on your phone, click power button and you should now see fastboot, recovery, factory reset, simlock, and imagecrc as options, use your volume button to go down to recovery, and click power button.
You should now see clockworkmod recovery 4.0.0.9.
f. Now lets put superuser on your device so you can be free!
click on this file and download it, DO NOT EXTRACT IT
http://downloads.androidsu.com/superuser/su-2.3.6.3-efgh-signed.zip
Now after you have downoaded that file, on your phone, use your trackpad, and scroll down to "mounts and storage"
then scroll down to mount usb storage. now you should be able to put files on your sd card, make sure you put it on the root of your sd card, not in a folder, it doesn't matter, but i prefer it!.
Now unmount on your phone by clicking the option, click go back, and then scroll down to "install zip from sdcard" and click on it, then click "choose zip from sdcard". Find that file we just put on there "su-2.3.6.3-efgh-signed.zip", and click on it, then click yes. Now click on go back, and click reboot system now!
Now if you want to stay stock, your done, your rooted, so now just install root checker, and busybox, and your good to go, if you want to do some roms, keep on reading.
Now you cross your fingers, and grab a soda, because we're 75% done!
g. Now is the easy part, all you do now is download the roms from other developers, copy them to your sdcard, then turn off the phone, hold volume down, camera and power button, go into recovery with using vol up and down buttons as the selector, and the power button to confirm your option. As you enter clockwork mod, you can then go follow the directions of the developer as to wipe certain sections, and how to install there roms/patches. YOUR DONE
If you have any questions, please let me know, also I didn't make ANY of this software, this guide just has every link to get you everything you need at one spot. I also have the original file to make your phone completely stock, so if you need that, let me know and I'll upload that and send the link out.
If you want to donate to me, donate to all the other og's first!
Thanks to
jdmarko
unrevoked
alpharev
paulobrien
MoDaCo
and if I forgot you, let me know. thanks!
Now this is how you give a tutorial!!! If i had some extra cash i would totally donate bro! I was trying to install 4.0.0.9 for two days from the dude that made its site and his directions were not thorough enough. Thanks dude.
Oh dude no worries, a thanks is just as good. I appreciate it, it took me days, so I'm happy I could help brotha!
Sent from my MyTouch 4G Slide using xda premium
Going to try! :-D fingercross tor me!
Thank you very much, very good write up.
Geko90 said:
Going to try! :-D fingercross tor me!
Click to expand...
Click to collapse
Fingers are crossed, the tutorial has proven effective so far, so hope all goes well, tell me how it goes!
poken1151 said:
Thank you very much, very good write up.
Click to expand...
Click to collapse
Thanks! I'm assuming it worked then?!
Superuser wont install for me, Error in /sdcard/su-2.3.6.3-efgh-signed.zip
Status 0
I wiped cashe/ dalvic downloaded several times No good.
correct hboot, s=off
just wont flash SU ???
phil0sophic said:
Superuser wont install for me, Error in /sdcard/su-2.3.6.3-efgh-signed.zip
Status 0
I wiped cashe/ dalvic downloaded several times No good.
correct hboot, s=off
just wont flash SU ???
Click to expand...
Click to collapse
Ok let's figure this out.. on step f, you did unmount your sd card, right? I haven't dealt with this problem before so if I ask a stupid question, I'm just trying to solve this. Also you don't need to wipe anything to install superuser, so that could be the problem also, so reboot ur fone, and let's try step f again! Keep me updated please!
phil0sophic said:
Superuser wont install for me, Error in /sdcard/su-2.3.6.3-efgh-signed.zip
Status 0
I wiped cashe/ dalvic downloaded several times No good.
correct hboot, s=off
just wont flash SU ???
Click to expand...
Click to collapse
It took a lot of us several attempts to flash the superuser zip. The 4.0.0.8 recovery isn't the greatest. Keep trying until it installs and you get root. Then upgrade to the modaco 4.0.0.9 recovery right away. It's not perfect either but it fixes a LOT of the issues known with 4.0.0.8.
And a comment to the OP, this is an incredibly helpful walkthrough! If only people would actually search and find this before posting new threads like "how do i root" and all that crap.
Thank you.
Great job on this and thanks for your work. I wish I would have had this tutorial when I did mine.
Sent via my talk enabled Galaxy Tab using XDA premium.
Techlvr said:
Great job on this and thanks for your work. I wish I would have had this tutorial when I did mine.
Sent via my talk enabled Galaxy Tab using XDA premium.
Click to expand...
Click to collapse
Thanks, I had a lot of trouble doing mine the first time, and I went back to stock, typed this and gave my wife my phone and she went step by step and completed it. So it can't be that hard!
Does this add an app to reboot from as the standard cwm does?
phil0sophic said:
Does this add an app to reboot from as the standard cwm does?
Click to expand...
Click to collapse
An app to reboot from? Not understanding the question throughly... In this cwm, it has the option to reboot system as every other cwm that I've used has. But an app... I do not have an app though...hope I answered your question!
numbaoneforeva said:
An app to reboot from? Not understanding the question throughly... In this cwm, it has the option to reboot system as every other cwm that I've used has. But an app... I do not have an app though...hope I answered your question!
Click to expand...
Click to collapse
OK ill reexplain is there an icon in the apps drawer for CWM to select to reboot etc. because it didnt install one on the MT4Gslide as on my MT4G.
I know something is goofy as SU wouldnt flash, I had to install the new version from the market.
phil0sophic said:
OK ill reexplain is there an icon in the apps drawer for CWM to select to reboot etc. because it didnt install one on the MT4Gslide as on my MT4G.
I know something is goofy as SU wouldnt flash, I had to install the new version from the market.
Click to expand...
Click to collapse
Oh, now i understand. No there isn't. I don't have one at all, as soon as I installed clockworkrecovery, and superuser, I flashed undeads rom on there. And I've been reading that superuser is being buggy when installing it on this phone through cwm...I'll look into that tonight, see if i can find the root cause.
Thanks...This is my wifes phone, she just upgraded from a CLIQ (one of the two people that loved blur)she likes my MT4G and wanted a KBD so here we are....
I want to change the lock ring so need root for the wonderful majic you dev's do....
phil0sophic said:
Thanks...This is my wifes phone, she just upgraded from a CLIQ (one of the two people that loved blur)she likes my MT4G and wanted a KBD so here we are....
I want to change the lock ring so need root for the wonderful majic you dev's do....
Click to expand...
Click to collapse
Well your at the right forum to get you started. And thanks! This is my first post so I'm trying!
Sent from my MyTouch 4G Slide using xda premium
phil0sophic said:
OK ill reexplain is there an icon in the apps drawer for CWM to select to reboot etc. because it didnt install one on the MT4Gslide as on my MT4G.
I know something is goofy as SU wouldnt flash, I had to install the new version from the market.
Click to expand...
Click to collapse
You probably just have to download ROM Manager from the market, I think that's what you're referring to. There isn't a whole lot of support for our device in ROM manager right now, however, and I haven't checked to see if the "reboot into recovery" works. Go into settings > power > and uncheck fastboot. Then, shut down your phone, wait 10 seconds, hold down the volume down button and turn your phone back on. That'll get you into recovery. Did you get superuser to install? Are you rooted?
Mine won't switch from "revolutionary" in purple at the top to "fastboot" at the top.
It says fastboot USB about 6 lines down, but that's it.
When I type "fastboot devices" it errors and says:
'fastboot' is not recognized as an internal or external command, operable program or batch file.
anyone know what's up?
To outline my situation, I have installed CWM to my phone, and flashed version 2.5.1.2 of Galaxy S i9000 (but the recovery boot doesn't show as CWM) on a Samsung InFuse 4G (this part I managed to find by scouring the forums) with Firmware version 2.2.1, Kernel 2.6.32.9, with Build FROYO.UCKH1. This is as far as I have gotten because I cannot seem to get a backup of my phone's ROM made. So, my question is can someone explain (without jargon, I haven't quite learned it yet) in simple steps how to resolve this issue and help me continue my way to flashing a custom ROM? I've checked and read so many other guides, but they are confusing because the steps aren't (sad to say) dumbed down for me. Here's an example of what I read:
1: dl CWM (actually had to go look this up and figure out what it was)
2: flash CWM (my phone model wasn't on the list, but after an extensive search found out that I could use the Galaxy S i9000 [supposedly])
3: boot into CWM Recovery (can't do it, for some reason it won't load on my phone.)
4: perform backup with CWM (as before, can't do it, read I could use Titanium backup but no depth was given)
5: dl a rom and place it on your sd card (this one is understood, short and to the point)
6: boot into CWM and flash rom
Unfortunately, when I start out on a new OS (already owning Windows and getting good at Linux) I tend to not even understand these so-called "Dummies Guides." I need something filled with minimal jargon that is short and sweet. Any information would be helpful
Also, I would like to know the likelihood of bricking my phone (based off of its specs) if it is possible to find out...
I'm a little bit confused here. How come you've flashed an i9000 (Galaxy S) firmware onto an Infuse? I think we can work out your backup problems though
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
DeltaOps said:
I mean that I flashed the Galaxy S i9000 version of CWM Recovery to my phone because there wasn't an InFuse option. (according to one thread, it said that the i9000 version was compatible with the InFuse)
However, I flashed the Recovery, but when I booted into recovery mode, I was still in the stock recovery. Any explanation for this and everything else?
I don't really know anything about the Android system yet, but I hope to be good enough to become a developer one day.
Click to expand...
Click to collapse
Gotcha. Sounds like the recovery hasn't flashed properly. Did you have the phone rooted before flashing the recovery?
Here is an awesome thread with video guides on just about everything you could need. Here is another. I take it you've already followed at least one of these to get the recovery flashed, so it might pay to try the 3E recovery instead and see if that works.
You may need to go right back to stock and start over. If you do, AdamOutler has got you covered right here.
I'll stay subscribed in case you need anything else, best of luck mate
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
DeltaOps said:
My phone was rooted with SuperOneClick. Superuser was still intact. I read on a thread that the CWM Recovery could "fake flash" and that it would still be accessible by selecting "boot into recovery" but it doesn't show.
It says 3E in my recovery mode, is that the modified or is it actually stock?
I downloaded CWM from the market (method 2) but for some reason have update.zip on my phone (method 1). Any explanation? I don't exactly remember downloading a .zip file...
Click to expand...
Click to collapse
It may have 'fake flashed' and not worked at all. Both stock and modified recovery will say 3E, the difference is in the version numbers although I can't picture them off the top of my head. If CWM had worked, you would not be seeing 3E, you would see the typical array of CWM options. The modified 3E does not give you the same options CWM does, it just gives you the option to flash an 'unsigned' image from Recovery.
I have never had any luck with ROM Manager personally, although a lot of people swear by it. I found it especially flaky flashing recoveries to any device, very hit-and-miss. I personally prefer, and recommend, flashing recoveries manually via ADB. A little trickier, but a lot more trustworthy.
That said, try flashing recovery through RM again before taking any further steps. Flashing a recovery over a recovery won't hurt
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
DeltaOps said:
I've tried three separate times to install the CWM recovery, but all were unsuccessful. What's this about ADB? I remember seeing the ADB Daemon in the SuperOneClick rooting process. And how tricky is it exactly, does it require code?
I have the Titanium Backup app on my phone, and I have backed up all the system and app data, but they are all separate files instead of a single (what, .md5?) file. I remember reading another thread that said you could back up a ROM via TB but I can't find a back up ROM option. Is there a particular way to do this or do I have to have the Premium/Pro version of TB? Or have I pretty much done all I can do with TB?
Click to expand...
Click to collapse
ADB is a command-line interface between your PC and your phone. You enable USB debugging and connect the phone via USB to the computer. Once you have the correct drivers installed, you can then use ADB (part of the Android SDK available for download) to send commands to your phone, as well as push and pull files. This requires full root, which you already have.
For example you can grab the recovery.img for CWN on the Infuse and tell ADB to 'flash recovery recovery.img' and actually ensure it flashes.
There are some excellent ADB tutorials floating around, this one in particular got me started. Make sure you do a bit of reading first though: the wrong command can royally screw you.
After you're familiar, you should be able to use ADB to push a recovery to your phone, whether it be unsecured 3E, or CWM.
I'll stay subscribed for any queries you may have
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
DeltaOps said:
How close is the ADB interface to other command-line interfaces like Linux or Windows? I use both operating systems on my laptop and I have familiarized myself with both of them (mostly). What am I supposed to be expecting when I use it? Also, I can't seem to find the recovery.img file, what folder would that be under?
Click to expand...
Click to collapse
Don't know about Linux, but ADB works through a Windows command prompt so its pretty much the same. You will need to have ADB, Fastboot plus whatever you wish to flash (recovery.img) in a 'working' directory, then run a command prompt from that directory.
You will probably need to download the recovery.img file.from XDA. It may be zipped up (they usually are).
Sent from my Galaxy Note using XDA Premium
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
DeltaOps said:
I've successfully got ADB started in the command prompt (not that bad :]) but when I try to pull the directory map from my phone, it says: remote object "xxxxxxxxx" does not exist. And what's this about Fastboot? Edit: Did a bootloader command test, worked just fine. No success on pulling directory
Command I used: "adb pull -s xxxxxxxxxxx C:\"
Click to expand...
Click to collapse
I don't think that's the correct format to pull directory structure. I'll have to read up on that one
Fastboot is another tool you can use to flash bootloaders, radios, recoveries etc through the command prompt.
Sent from my Galaxy Note using XDA Premium
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
DeltaOps said:
You're right, tried using the <remote> variable as a file instead of the device serial. Typed:
adb pull .. files
prompt skitzed out after that. I know it won't damage anything since it's a copy procedure but I'm looking for the file and it's not there. it said it's pulling everything after skipping "special files"
Edit: It just finished, said it couldn't create the file because for some reason it was trying to copy the files from the phone to the phone
Click to expand...
Click to collapse
Yeah, you'll have to give it a target directory, I think it's like this '.\sdcard' to write them to the SD card?
Sent from my Galaxy Note using XDA Premium
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
DeltaOps said:
If that's the case, then how do I make the file copy to my HDD? The drive doesn't show up on my computer (does it)?
Click to expand...
Click to collapse
I'm sure that with the correct command, you will be able to pull the structure to your hard drive. I'm not sure if it's .\C:/ or not, I'll have a look when I'm on a proper rig and can do a proper search
Sent from my Galaxy Note using XDA Premium
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
DeltaOps said:
Thanks! You've been great so far
That noob video was right, XDA is full of awesome people!
Edit: Got it Thanks for the pointers. Now I need to find out how to back up the entire ROM... :/
Click to expand...
Click to collapse
Glad you got it and glad to help. There are a hell of a lot of good people here If there's anything else you need, feel free to PM me.
Good luck buddy!
Sent from my Galaxy Note using XDA Premium
Is there perhaps any way to perform a ROM backup with ADB?
DeltaOps said:
Is there perhaps any way to perform a ROM backup with ADB?
Click to expand...
Click to collapse
Ooh good question. I don't think so, but I'm not sure. I know you can pull directories like /system/ and whatnot, but as for repackaging them into a working backup, that may be a bit more involved. I would use ADB to.push a working CWM and do it that way, but it sounds.like you're a bit better at the command-line stuff than I so you may be able to work it!
Sent from my Galaxy Note using XDA Premium
ALL:
It has been a long time since I posted to this thread. Back then, the Samsung Exhilarate had just come out, and there was no way to root it. Thanks to several other members, most notably j3r3goss and shabbypenguin, I was able to get root on this phone. As of now, this post is very old. The instructions here, are not needed for you to root your Samsung Exhilarate anymore. You are free to read through them, but you should pay attention to the last page (currently page 3). There, j3r3goss posted a link to the the TWRP or CWM recovery files, that you can now use to get root, without following the step-by-step instructions I posted below. I'm leaving the thread up, but for all intents and purposes, consider it closed.
Here's the link to the section you need in order to root your phone:
http://forum.xda-developers.com/show...php?p=32520094
It has been fun, and I've been using my Exhilarate for nearly two years. Because I've been extremely busy, I haven't had time to keep up with the latest changes - but others have. I hope that you found these instructions useful.
In any case, take care and ROOT ON!
Everything past this point is old and no longer applicable
==========================================
IMPORTANT NOTE: If you have UPDATED your phone to ICS, and want to root it, these instructions will work. You will not need to do the last part where you need to update the firmware keys!
Do you plan to update your phone from Gingerbread (Android 2.3) to Ice Cream Sandwich (Android 4.0). Do that first! Otherwise, you'll just have to root again (not that that's a problem, but why???)
I) How to update to ICS:
1) Download Samsung Kies from here: http://www.samsung.com/us/kies/ if you haven't already, and install it, and then run it
2) Put your phone into ODIN (Download mode - see section II below).
3) When Kies detects you phone (your computer will need to install drivers, and then Kies will say it's connecting to your phone, and it will take about 3-4 minutes and finally connect to it), it should let you know that there is an update. Just follow the instructions on Kies and be patient. The phone will update, and once it reboots into normal mode, you'll know it's updated by going to "Settings" and if they are grouped into different sections, then you have ICS. Otherwise, you probably still have GB.
II) How to enter ODIN Mode:
For the Exhilarate I've found it's best to use this sequence:
1) Power phone down
2) Plug the USB cable into your computer (do not plug the phone into the USB cable yet).
3) While pushing and holding both the vol up and vol down buttons, plug the phone into the computer. As soon as you see "SAMSUNG" flash and then dissappear, release the buttons.
4) Phone should boot into ODIN mode.
III) How to Root
What you need:
1) Samsung Galaxy Exhilarate phone (unrooted)
2) microSD Card (any size of 1GB or larger will work)
3) USB cable to connect your phone to your computer
4) Files below
First, download all the files...
1) Download the latest version of ODIN here: ODIN.
2) Download the drivers here: Samsung Galaxy Drivers and run the setup program after unzipping.
3) Download the tar file here: www.Shabbypenguin.com/OUDstuff/Blaze4G/Clockworkmod-Blaze-4G.tar Don't mess with it, just download it somewhere where you can find it later
4) Download SuperUser here: SuperUser Save it somewhere where you can find it later.
Second, conduct the root:
1) Put your phone into Odin (Download mode - see Section II above).
2) With phone in ODIN mode, run Odin.1.85.exe (it's in the folder where you unzipped ODIN too).
3) Odin will launch on your computer. It should show, in the first box under ID:COM, a port in yellow. Mine was Port 5. This means you have successfully connected to your phone.
4) Click the button in ODIN labeled "PDA", and then browse to the .tar file you downloaded above and then select "Open". The file will show up next to the PDA button.
5) Make sure that "Re-Partition" is NOT checked!;
6) Click "Start" and wait till your phone reboots. It should reboot into normal mode. If it doesn't, just power down and reboot into normal mode.
7) Copy the SuperUser.zip file you downloaded above to your phones microSD card.
8) Reboot the phone into recovery mode: While pushing and holding both the vol up and vol down buttons, push the power button. As soon as you see "SAMSUNG" flash, release the buttons. You shouldn't need to have the phone connected to the computer this time. The phone will boot into CWM recovery.
9) using either: the "menu" button to move down and the "home" button to move your selection up; or alternately the volume down button to move down, and the volume up button to move up: highlight "install zip from sdcard". Use the "search" button or power button to select/enter.
10) highlight "choose zip from sdcard" and press the "seach" button to select it.
11) browse to the directory which you copied SuperUser to and select it.
12) scroll down to "Yes - Install Superuser" and select it.
13) Once done, reboot your phone into normal operating mode.
14) If rooting Gingerbread, see Section IV below.
15) If rooting either Gingerbread or ICS, see section V below.
16) If having issues with Root, see section VI below.
IV) Rooting Gingerbread?:
Last: Finish up (Steps 1-4 are ONLY needed if you are still using GingerBread and not Ice Cream Sandwich):
NOTE: Your buttons (the four at the bottom) WILL NOT work at this point. You need to do the following:
======
1) Push your phone dialer as if you were going to make a call.
2) Dial *#*#2663#*#*.
3) You will see the attached thumbnail below on your phone (stolen from j3r3goss).
4) press the bottom button that says "Touch key FW update". Wait. Once it's finished, your bottom row of buttons will work again!
Note: If you are on GB, and not ICS, every time you boot into recovery and then back into operational mode, you will need to do the four steps in this section above!
======
V) Using either GB or ICS:
You do need to do these last steps (I believe):
5) ADDENDUM/UPDATE: At this point, there is one last thing you need to do!: You must go to "Settings/Applications/Development" and Enable USB Debugging! If you don't do this, you will NOT be able to get root access! Also, if for any reason you turn off USB Debugging, make sure you turn it back on! If you lose root access, check this FIRST! If you still can't get root access, boot into recovery mode and wipe the Dalvik Cache, the regular Cache, and "Fix Permissions". Then double check to make sure USB Debugging is ENABLED!
6) You're done! Your phone is now rooted and you can do whatever you want! :highfive:
VI) TROUBLESHOOTING:
If you run into problems
1) Check to make sure that SuperUser is installed on your phone. Check the apps section first, and then, use RootExplorer and check the System/bin folder. If you see SuperUser is in the system/bin folder, then you are very close to being rooted.
If it is not installed:
a) make sure that you copied the superuser.zip file to the EXTERNAL sdcard.
i) Boot the phone up normally
ii) plug the phone into your computer, pull the notification bar down, select USB connection, and tap the "Connect USB storage" button.
iii) Using Winbloze explorer, copy the SuperUser.zip to the external sdCard (on my computer, it is drive F:, and the Internal is drive G.
iv) disconnect once the copy is finished and use any file explorer on your phone to check the contents of the external sdCard (look in the "sdcard/external_sd" folder)
v) if it's not there, then you are doing something wrong. If it is there, shut down the phone, and boot into CWM recovery.
vi) Use CWM recovery to install the superuser.zip file on your phone.
vii) reboot into normal mode
viii) check to make sure that you have enabled USB Debugging
viii) check again to see if SuperUser is now in your apps, and in the system/bin folder.
ix) Run SuperUser 1x, and then close it out.
x) Run ANY app that requires Root Permissions. You should get a request from SuperUser to "Allow" or "Deny" the app root access. Make sure you allow root access. If you make a mistake, you'll need to launch superuser again and completely remove the app from the denied list.
2) Make sure USB Debugging is enabled.
3) if you still can't get root, boot into CWM Recovery, and try clearing the cache and the Dalvik cache, and resetting permissions, then reboot and check everything again. You may need to do this last step several times.
Beyond that, I don't know what else might be causing you to not gain root access, so keep trying.
If anyone has any questions, feel free to PM me.
V/R
BlackWolf
Thanks for the write-up Black-wolf.
I wasn't aware that the touch key fw needed to be updated each time after booting recovery,hopefully that is something that will be fixed when Shabbypenguin gets his hands on the stock recovery.
Personally I find the easiest, works every time method to get into Download mode is to have the usb cable plugged into the pc, then while holding the volume up/down buttons, plug the cable into the phone, continue holding vol up/down buttons until download mode boots.
Sent from my Liberty using xda premium
j3r3goss said:
Thanks for the write-up Black-wolf.
I wasn't aware that the touch key fw needed to be updated each time after booting recovery
Click to expand...
Click to collapse
Yeah, I figured that out when I went to boot recovery to check something, and then came out of it and the keys weren't working again... :/ At least there's a work around. I suspect, that this is something that an automated app could handle if Shabby or someone else doesn't come up with a permanent fix.
V/R
BlackWolf
Can someone update the links??.....
Fixed
JUSMEJOSE said:
Can someone update the links??.....
Click to expand...
Click to collapse
Links are all working now. There was only one broken one that I'm aware of. Let me know if there are others.
BlackWolf
Any update on getting the stock recovery? I blew through rooting my Exhilarate before I noticed the request for help or I would have offered.
The root seems to be working OK for me. JuiceDefender is working great with it to throttle the CPU clock speeds and has really improved my battery life. Also worked OK in blocking all the bloatware apps with the Gemini App Manager. So I don't really have a reason to unroot and go back to stock firmware, but it would be nice to have the option available should I ever hit a problem.
Thanks for all you guys hard work!
DK
I just needed this tutorial!, Good job.
Thanks!
Dream_Killer said:
Any update on getting the stock recovery? I blew through rooting my Exhilarate before I noticed the request for help or I would have offered.
The root seems to be working OK for me. JuiceDefender is working great with it to throttle the CPU clock speeds and has really improved my battery life. Also worked OK in blocking all the bloatware apps with the Gemini App Manager. So I don't really have a reason to unroot and go back to stock firmware, but it would be nice to have the option available should I ever hit a problem.
Thanks for all you guys hard work!
DK
Click to expand...
Click to collapse
domobile said:
I just needed this tutorial!, Good job.
Thanks!
Click to expand...
Click to collapse
Dream_Killer: No, we have not gotten a stock recovery. I've had several inquiries into it, but so far as I know, Shabby has not been able to help out in this regard. I am willing to try myself, but I'll need an un-rooted (and it must never have been rooted) phone.
domobile: Glad it worked for you.
V/R
BlackWolf
Black-wolf said:
Dream_Killer: No, we have not gotten a stock recovery. I've had several inquiries into it, but so far as I know, Shabby has not been able to help out in this regard. I am willing to try myself, but I'll need an un-rooted (and it must never have been rooted) phone.
domobile: Glad it worked for you.
V/R
BlackWolf
Click to expand...
Click to collapse
To get into stock recovery you...
1. open a command terminal on your computer.
2. type cd (where ever you have your ADB located on your computer) for example my is located in desktop/platform-tools so the command would be "cd desktop/platform-tools"
3. type "adb"
4. type "adb reboot recovery"
Presto you are in stock recovery.
ChefAnt said:
To get into stock recovery you...
1. open a command terminal on your computer.
2. type cd (where ever you have your ADB located on your computer) for example my is located in desktop/platform-tools so the command would be "cd desktop/platform-tools"
3. type "adb"
4. type "adb reboot recovery"
Presto you are in stock recovery.
Click to expand...
Click to collapse
We know how to boot into the stock recovery. What we need is to pull the stock recovery image off of the phone so that we can restore the phone to stock.
Btw.. pressing both volume keys while turning on the phone will get you there also.
I rooted the exhilarate. Loaded the t mobile blaze cm7 rom. And all works like a charm. The only thing is you can't make a call. You can,you just can't hear. I called my other phone and it went through. The speaker doesn't work. Mms and all works. Just not the speaker...... why? This wud. Be a awsome rom for this phone.. think we can find a fix?
harley1rocker said:
I rooted the exhilarate. Loaded the t mobile blaze cm7 rom. And all works like a charm. The only thing is you can't make a call. You can,you just can't hear. I called my other phone and it went through. The speaker doesn't work. Mms and all works. Just not the speaker...... why? This wud. Be a awsome rom for this phone.. think we can find a fix?
Click to expand...
Click to collapse
I'm not exactly sure but it might be just as simple as replacing the audio libs on the blaze rom with the ones from the exhilarate. I'm not sure which files though.
I'm curious if by coming together (blaze and exhilarate users) if there would be enough interest to get official cm support. if the only major diff is audio they could basically support 2 devices for the price of one.
Sent from my SAMSUNG-SGH-I577 using xda premium
If i knew/or had the kno how,shoot id do it. Is there a program u need to change the libs?. This is a pretty sweet device.
i think you just need root explorer, and copy the new ones over the old ones. I'll look to see if i can find out which files need swapped. Should be able to make a zip to flash through CWM recovery.
Sent from my SAMSUNG-SGH-I577 using xda premium
Man,im good at alotta things,buildin houses,workin on diesels,and flashin roms to my s3 and note,what i cant figure out is building roms. Im sure gettin this speaker workin has somthin 2 do with dismantling blaze cm7 rom and find the fix.
Another words,im good,but not that good. If som1 held my hand thru it,i cud do it. Or just show me
NFC for Exhilarate!
All: rodracruz found a thread for enabling NFC on AT&T phones. Apparently, the Samsung Exhilarate does have NFC - but why the hell AT&T has it disabled, I have not idea... In any case, check out this thread and follow the instructions to enable it on your phone: http://forum.xda-developers.com/showthread.php?t=1545751
There are even links as to some of the things you can do with NFC.
V/R
BlackWolf
Black-wolf said:
All: rodracruz found a thread for enabling NFC on AT&T phones. Apparently, the Samsung Exhilarate does have NFC - but why the hell AT&T has it disabled, I have not idea... In any case, check out this thread and follow the instructions to enable it on your phone: http://forum.xda-developers.com/showthread.php?t=1545751
There are even links as to some of the things you can do with NFC.
V/R
BlackWolf
Click to expand...
Click to collapse
Sweet, I was wondering, especially since this phone was released after the skyrocket.
Wolfman
Worked beautifully. You the man!
Thx
j3r3goss said:
I'm not exactly sure but it might be just as simple as replacing the audio libs on the blaze rom with the ones from the exhilarate. I'm not sure which files though.
I'm curious if by coming together (blaze and exhilarate users) if there would be enough interest to get official cm support. if the only major diff is audio they could basically support 2 devices for the price of one.
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
I'm pretty sure it wouldn't have anything to do with the audio lib files. More so most likely a kernel, modem, or APN problem.
Edit: not to mention the build.prop is completely written for the blaze. I'm working on some things. I'll let you guys know tonight. I wish there was source for this damn phone.
ChefAnt: There is a stock file from Samsung... read my post (about 2/3 of the way down):
http://forum.xda-developers.com/showthread.php?t=1828426
ChefAnt said:
I'm pretty sure it wouldn't have anything to do with the audio lib files. More so most likely a kernel, modem, or APN problem.
Edit: not to mention the build.prop is completely written for the blaze. I'm working on some things. I'll let you guys know tonight. I wish there was source for this damn phone.
Click to expand...
Click to collapse