TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
Related
EDIT: This information is out dated now but visit the link below for updated info.
taken from here http://www.samsungmomentforum.com/rooting/root-access-(finally-achieved!)/
1) Partition your SD Card to have first partition as fat16 and second ext3 [this tutorial assumes you have this setup exactly as stated]
2) Boot in Test Mode with Call+Center+Power
3) copy root into your tools directory of the sdk
4) adb push root /system
5) adb shell chmod 0755 /system/root
6) adb shell /system/root
7) unplug usb, remove battery, reboot into test mode when instructed
8) adb shell
9) /system/bin/btld_testmode
10) /system/root
Excellent. It work!. Just do exatly the steps above. Thanks for putting all this info together.
FYI... Samsung post the source code of the samsung moment.
Is this temp or persistent root? For temp root I don't think partitioning the sd card is necessary or at least I didn't partition it when I temp rooted my Moment.
Was a long time WinMo user, I was stuck with a Moto Q9c on sprint for way to long. I'm still stuck with sprint, but got the Moment in hopes of having a badass Android to start with.
Night and Day compared to my Q, the root is key though, custom rom's were so easy on the Q.
soooo im a newb to android, same question as johnbarry3434.
does it stick?
I've got two Moment's(thanks sprint for shipping me 2 and charging me for neither) ?maybe one for test purposes?
Anything I can do to help the rooting process, please let me know
Sorry guys but I'm very new to this android. Only had my phone for a week now. Is rooting like flashing a custom ROM for the Touch Pro?
Does this require seperate adb drivers for the Samsung phone?? If so where can I get them and are there any avaliable for Ubuntu???
Hi guys,
I have just gotten myself a Samsung Spica. Can I use this guide as well? Is there a ROM-update tool for the Spica?
I'm really n00b, so any help is appreciated
I need someone with this rooted phone to contact me, I need to get some data from it so I can work on something for it.
Please contact me at [email protected]
Thanks
hey look i am brand new to this whole root thing i just got my moment two days ago i am used to the simple jailbreak iphone stuff but this is a whole new level
i am on windows vista and i do not understand any of this at all please someone email me some simpler instructions or make a video or something just to help me out in some way please and thank you
my email: [email protected]
use the search Service people
Now that moment is rooted?
Will there be any chance of us getting a custom rom of andorid using sense ui?
i dont really see any point in rooting my phone if there is no MAJOR thing you can do with it..
I cannot get my samsung to root
I have the updated cupcake cl14 and when I boot my phone with talk+center+power, I boot into a test mode that lets me test the screen, keyboard, and so on. I did copy the root file (supplied from the instructions ) to the main part of my card on both partitions, and partitioned it just as it stated in the 1st step. I don't understand what the "adb" is and how to use it. Can this only be down with windows because I'm am using Ubuntu. I know adb is advance debugging bridge but after some google searches I still don't know how to use it. I now a little about chmod 0755 because of Ubuntu but any "hand-holding" instructions would be great thankyou to everyone who is willing to help me and others out with this problem.
Is there still no "real" benefit for root access for the Moment? As in no good reason to root the phone? My girlfriend has one and I was hoping that it was at least close behind my Hero by now in terms of root access benefits....TIA
bbv203 said:
Is there still no "real" benefit for root access for the Moment? As in no good reason to root the phone? My girlfriend has one and I was hoping that it was at least close behind my Hero by now in terms of root access benefits....TIA
Click to expand...
Click to collapse
try this
http://forum.samdroid.net/threads/13-How-to-get-Root-on-Samsung-i5700-EN-02-10-v-LK10
just got my phone and can't increase the size of the fonts was told rooting is the only way even with using spare parts.
first of what program can I use to partition the sd card I am running windows XP. and everything I have downloaded today would only see the internal drive.
For those of you still looking for how to root your Samsung Moment (you don't have to use your SDCard either) there are two HOW TOs posted at PPCGeeks under the NON-WM DEVICES>ANDRIOD>SAMSUNG MOMENT
One explains how to root phone with CJ05
The other explains how to root phones that have CL14 out-the-box or officially updated to CL14
I would post a link except I'm not permitted to post an outside link... just go to PPCGeeks(dot)com and click on their forum
So what Now!!!!
Okay I see you have this placed here.. I like... I have a Nexus and 2 Droids, wife and mine.. Nexus ALL mine.. HAHAHA..
My sister, wifes sister, she has the Moment.. I have always wanted to root this just cause of the 800mhz processor... This was the first device to almost meet up with the Nexus before it was even thought up..
Is there Roms, Themes, Kernels, etc.. I see nothing, but a root, useless, without an accommodation, thanks anyway, always good to have the key to the door first..
Somebody, PM me if not on, or reply here, I'll come back around...
cool that i made the front page but the info is out dated now.
yes this info is way outdated. just flash the kernel with speedyrabbit's or joeykrim's kernel and you'll have persistent root, plus a much faster phone.
also, speedyrabbit's kernel has wifi tether and flash_image support. you can download from www(dot)sdx-developers(dot)com.
Here is how to install 3rd party applications. I'm not going to go into detail for every step so a little more research may be required if you don't understand all the terms. Search around, it's how I learned.
1. Download and extract the Android SDK. Once it is extracted copy it to the root of your C drive and to make your life easier rename it to sdk. So in the end it should be C:\sdk.
2. Download and install HTC Sync.
3. After the install of HTC Sync is complete connect your phone to the computer and select the HTC Sync option for the connection type on your phone. It doesn't matter if it fails to connect or gives you any error. When I did it the phone told me it couldn't find HTC Sync on my PC but I just hit OK and moved on.
5. Copy whatever 3rd party apps you are looking to install to the tools folder. (C:\sdk\tools). DO NOT rename the files, I had problems after doing that.
6. Open up a command prompt on your PC (In windows it's start, run, cmd) and change to the tools directory.
cd\
cd sdk\tools
After you change to that directory the prompt should say: c:\sdk\tools.
7. Type adb devices to verify that your computer can see the phone. If everything is working you should get a response that looks something like this:
List of devices attached
HTxxxxxxxxx device
8. Once you verify that the computer and phone are connected type the following:
adb install nameofapp.apk (obviously changing the nameofapp part to whatever the file is named).
You should see it copy the app then install and at the end it will say successful. All done!
Feel free to add to this if I missed anything....
KB
Thanks KB for the update, an easy workaround that I don't mind performing at all. Now if only we can remove those pesky AT&T bloatware they slapped on it, and get a nice Root going, we'll be in business!
Heck, I'd be willing to buy an extra Aria for someone around here if they could get a quick root/2.2 update going for this thing.
trying to install swype on my aria. please help
hello, please help with step 6. i dont know what i need to do. can some one please reply really quick. all i need is to do is install swype. how do i find swype anyways
hello, please help with step 6. i dont know what i need to do. can some one please reply really quick. all i need is to do is install swype. how do i find swype anyways
Click to expand...
Click to collapse
Step 6 may seem a little unwieldy, but here is a trick I learned.
1) Create a shortcut for CMD.exe on your desktop.
2) Right click the CMD.exe shortcut and go to Properties.
3) In the Start in: bar, type in the directory for the android SDK tools folder you put on your computer. For example, my start in address is:
Code:
"I:\HTC Hero\android-sdk-windows\tools"
Now everytime you open this CMD.exe shortcut, it will start in the correct folder to perform adb commands.
As far as Swype goes, you can get an e-mail for the installer through here.
I did run into a problem, since Swype will not install correctly because it needs to download and apply another .apk, which AT&T's blocks will not allow. Swype really isn't important enough to me to get it otherwise, as I'm happy installing the other apps I've been missing out on.
Hope that helps!
KB Smoka said:
Here is how to install 3rd party applications. I'm not going to go into detail for every step so a little more research may be required if you don't understand all the terms. Search around, it's how I learned.
1. Download and extract the Android SDK. Once it is extracted copy it to the root of your C drive and to make your life easier rename it to sdk. So in the end it should be C:\sdk.
2. Download and install HTC Sync.
3. After the install of HTC Sync is complete connect your phone to the computer and select the HTC Sync option for the connection type on your phone. It doesn't matter if it fails to connect or gives you any error. When I did it the phone told me it couldn't find HTC Sync on my PC but I just hit OK and moved on.
5. Copy whatever 3rd party apps you are looking to install to the tools folder. (C:\sdk\tools). DO NOT rename the files, I had problems after doing that.
6. Open up a command prompt on your PC (In windows it's start, run, cmd) and change to the tools directory.
cd\
cd sdk
cd tools
After you change to that directory the prompt should say: c:\sdk\tools.
7. Type adb devices to verify that your computer can see the phone. If everything is working you should get a response that looks something like this:
List of devices attached
HTxxxxxxxxx device
8. Once you verify that the computer and phone are connected type the following:
adb install nameofapp.apk (obviously changing the nameofapp part to whatever the file is named).
You should see it copy the app then install and at the end it will say successful. All done!
Feel free to add to this if I missed anything....
KB
Click to expand...
Click to collapse
I'm sorry I can't be more technical, but I use an easier way to install 3rd party apps, even multiple installs at once. Everything above is the same except AFTER step 3.. go to http://de.codeplex.com/ and download droidexplorer, once you have it, connect your phone to the pc, execute droidexplorer (droid explorer can take up to 2 mins (or maybe longer) to load so be patient), select drop down menu tools either addons (-batch install) to install multiple apps.. or Manage Packages to install single app. There are lots of other functions using droidexplorer but I think most of them need the device to be root.
(it's been a while since I first installed droidexplorer, so I'm not 100% certain if I even needed the android sdk, but HTC SYNC is definitely needed, if someone wants to give it a shot without installing android sdk to verify, that would be great, let me know and I'll fix up this post.)
THIS HAS BEEN VERIFIED TO WORK ON THE STOCK ATT ARIA by myself, as I just purchased the aria on sunday and already installed over 30 apps.
hope this helps someone.. post any replies if you need help, I'll try to help in any way I can.
thanks for the instructions KB. Getting my aria soon and can't wait to ditch the iPhone
Anyone know if/how you can delete the built in AT&T apps?
hocplyr98 said:
Anyone know if/how you can delete the built in AT&T apps?
Click to expand...
Click to collapse
I'd suspect you would need root access and then you could simply use shell rm /system/app/attbull****.apk
Yup....Same thing I did with my Incredible..
Ok, I got the Swype installer onto my phone, but then it stops me again. Thoughts?
Boneshark said:
Ok, I got the Swype installer onto my phone, but then it stops me again. Thoughts?
Click to expand...
Click to collapse
To elaborate. did "install adb swype-installer.apk" Got the success message. Tried to run swype installer on my phone and it got blocked as a third party app.
So, you can just use the Incredible root and it'll work for the Aria?
hocplyr98 said:
So, you can just use the Incredible root and it'll work for the Aria?
Click to expand...
Click to collapse
No no, he was saying he was able to remove the Verizon bloatware from his Incredible after rooting the phone. DO NOT use the Incredible method for rooting on your Aria, as you will possibly brick your phone.
Boneshark said:
To elaborate. did "install adb swype-installer.apk" Got the success message. Tried to run swype installer on my phone and it got blocked as a third party app.
Click to expand...
Click to collapse
Are you sure you have the right apk? If you got success it should already be installed. Check it by going to settings then language and keyboard. You should see Swype as an option.
shark0807 said:
No no, he was saying he was able to remove the Verizon bloatware from his Incredible after rooting the phone. DO NOT use the Incredible method for rooting on your Aria, as you will possibly brick your phone.
Click to expand...
Click to collapse
Thanks for clarifying....That could have ended badly.
KB Smoka said:
Are you sure you have the right apk? If you got success it should already be installed. Check it by going to settings then language and keyboard. You should see Swype as an option.
Click to expand...
Click to collapse
yep did "adb install swype-installer.apk" Got the "success" - nothing there. The swype installer is now on my phone. Click on it, log in to it, click download - third party deny message.
Also there's no swype on my phone in the downloads, only the swype installer. I figured I might have to do the same thing for the swype installer and swype, but the file isn't there. What exactly does running "install swype-installer.apk" accomplish? I figured it would allow me to download the actual Swype program, and not just the installer.
Tried again in CMD "Install_failed_already_exists"
Boneshark said:
Also there's no swype on my phone in the downloads, only the swype installer. I figured I might have to do the same thing for the swype installer and swype, but the file isn't there. What exactly does running "install swype-installer.apk" accomplish? I figured it would allow me to download the actual Swype program, and not just the installer.
Tried again in CMD "Install_failed_already_exists"
Click to expand...
Click to collapse
I tried this too. Apparently Swype-installer.apk is an Android program for you to download and install the REAL Swype software. I was able to install the swype-installer but the next step fail since it's trying to install Swype directly. Does any have the actual swype apk file? Do you know where I can find it?
saint168 said:
I tried this too. Apparently Swype-installer.apk is an Android program for you to download and install the REAL Swype software. I was able to install the swype-installer but the next step fail since it's trying to install Swype directly. Does any have the actual swype apk file? Do you know where I can find it?
Click to expand...
Click to collapse
Found it here: http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=699705&page=2
Hi, I am looking to root my MT4G.. but I always see "root at your own risk" etc... Well, I am ready to root at my own risk, however I don't really know enough to want to attempt thsi yet.. so I am looking for a general thread explaining what this stuff is and how it is explained..(definitions for commonly used terms and acronyms..) someone please point me somewhere.... Thank you.
I have been looking for a thread that answers these questions I have and I haven't found one in about a week, so I posted this...however I literally just found one, that I think answers most of my questions @ http://forum.xda-developers.com/showthread.php?t=859446&highlight=guide sooo any MOD please close or delete my thread, and I am sorry for wasting your time.
I used grankin01's instructions...
I know there's a lot of info out there, especially if you just search for "root." It can be a bit daunting at first, especially if you're not oriented properly.
I have rooted 3 MT4G's using the following guide by grankin01...
http://forum.xda-developers.com/showthread.php?t=834225
It really can't be any easier. I started out on a G1 and rooting was not this easy back then. To paraphrase grankin01's instructions (please read his instructions carefully and do this at your own risk)...
1. Download and install VISIONary
2. Extract that root.rar file to your sdcard. This is where a lot of people got messed up. There's a 'root' folder within a 'root' folder 'cause the person who originally .RAR'd these files, RAR'd a 'root' folder. Basically, when all is said and done, you should have a folder named 'root' on your SD Card. Within the 'root' folder, will be 3 files - hboot_dhd.nb0, Root.sh & wpx.ko.
3. Run VISIONary and click Temproot now - you now have temporary root access
4. Download and run Terminal Emulator and execute the commands outlined in grankin01's post. You will be prompted to restart. Once your phone boots back up, run VISIONary again only this time, click Attempt permoot now. Your screen will go black and eventually, the phone will reboot.
On two occassions, when I was doing this on replacement MT4G's I received, I forgot to enable USB Debugging. I found that VISIONary would just spin its wheels at the Temproot portion. After rebooting the phone and trying again, VISIONary actually prompted with an error to let me know USB Debugging had to be enabled. Totally my fault, but the app just spins its wheels at first, so you don't really know what's up until you reboot and try again.
To recap:
- VISIONary temproot
- Commands outlined in grankin01's post
- VISIONary permroot
It really is quite easy to do! If anything, there are plenty of redundant posts that explain how to get root access. I hope my info above doesn't add to the mire.
shlongwoodian said:
I know there's a lot of info out there, especially if you just search for "root." It can be a bit daunting at first, especially if you're not oriented properly.
Click to expand...
Click to collapse
I think that is why I posted this... Because I have been searching but I don't know what exactly to search for, or what step to do such thinigs in...I appreciate the help. I am currently following the s=off perma root guide, however I am struggling at getting my ADB drivers installed correctly....sooo I have some tinkering to do but I am looking forward to rooting my phone, and I don't even know what that is gonna open up..CANT WAIT!!!
EDIT: I checked out your link, and I am using a guide written by him, i believe, but it is the one that is a little more complex, and causes a deeper perma root...
For the ADB drivers just look on the sdcard that came with your phone. There should be a file named HTCDRIVER.EXE. Just copy that to your windows desktop and execute it. It will install the drivers you need. As for linux, my Kubuntu 10.10 installation saw my phone without any problems or driver installations.
The new guide with the "deeper" root actually is the better one to follow. Its really not as complicated or difficult as it looks.
grankin01 said:
For the ADB drivers just look on the sdcard that came with your phone. There should be a file named HTCDRIVER.EXE. Just copy that to your windows desktop and execute it. It will install the drivers you need. As for linux, my Kubuntu 10.10 installation saw my phone without any problems or driver installations.
The new guide with the "deeper" root actually is the better one to follow. Its really not as complicated or difficult as it looks.
Click to expand...
Click to collapse
Freaking awesome...in sitting here at work not looking forward to going home to another wasted two hours trying to set the driver up you just saved my day with that info about the driver...you sure it has the adb driver though..?
Sent from my HTC Glacier using XDA App
Jaskwith said:
Freaking awesome...in sitting here at work not looking forward to going home to another wasted two hours trying to set the driver up you just saved my day with that info about the driver...you sure it has the adb driver though..?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yeah, I had to install it for adb to work on my windows installation and it has saved several other people heartache too.
Ughhhh.. just found out I work at job #2 tonight...how FREAKING lame...like I wasted ALL my freetime not being able to figure it out last night and now that I think I know what to do... I have NO time...BLAH!!
Okay, so my ADB **** is still not working... I don't know why.. I am following the guide over at theunlockr.com and it still won't work.. I installed the SDK from google... I didnt DL the archives however... and then I installed the drivers off my SD card onto my computer, and when I open the Command prompt and type cd\ cd AndroidSDK\tools\ it says the directory does not exist... it says on the unlocr guide to try installing PDAneT and that might help, and so i did that as well, still says directory does not exist...ARGH this is frustrating!
Do you need perma root to boot into recovery?
I would just follow the visionary method so you won't even have to bother with adb. Just use root explorer to copy and past the files into the right directory. Did it on the bus, took me 5 minutes. No need to get true/deep root especially for someone just starting off. I promise, for all you'll be doing (and a hell of a lot more) you'll NEVER know the difference. Just gives you more options to screw up your phone. Start with perm root (set up the easy way), flash a rom or two, mess around with some cool apps for root users, figure out adb, and then work your way up to messing with the deeper system stuff (if you still feel need).
Just my 2¢
Sent from my HTC Glacier using XDA App
It sounds like you are looking in the wrong directory. Open your file browser and do a search for adb and pay attention to what folder it is in. My installation had like two subdirectories before I could even get to the tools directory on my windows drive.
That is if you still want to try adb. It is a valueable thing to learn. Espescially if your going to be doing these kinds of things to your devices. It can take a brick and turn it back into a phone if you know how to use it.
Thank you kind sirs you are very helpful to a pour nub such as myself...well it seems like I dont havr any freaking time ever so I think I might take c_licious's advice for now and read up on adb some more...i did see that in the thread its easy to convert from the perma root to the deep perma root so think that's what ill do. Thank you grankin for the tip on finding adb drivers that will definitely come in handy when I get to that. Yayyyyy!!!!
Sent from my HTC Glacier using XDA App
I just managed to root my SCH i400 (first ever rooting of any Android device for me).
I am very surprised by how smoothly it went, despite reports & warnings everywhere about complications (like this one - which should be totally ignored if you're using SuperOneClick v2.1.1 or higher).
For the benefit of n00bs like me who may be confused by multiple sources, resources, versions and problem reports, I am posting a step by step procedure that is confirmed (by me, on Windows XP SP3) to be working smoothly, without a single hitch of complications:
Phone: Make sure setting > applications > unknown sources is checked.
Phone: Make sure phone is in debugging mode.
Phone: Make sure SD card is unmounted!
PC: Make sure Windows USB driver for this phone installed and works
PC: Make sure .NET 3.51 SP1 is installed.
PC: Unzip SuperOneClickv2.1.1-ShortFuse.zip ==> C:\Program Files\SuperOneClickv2.1.1-ShortFuse
PC: Double-click SuperOneClick.exe
PC (in SuperOneClick): Make sure you're on the Universal tab (the only other tab is Samsung Captivate, which isn't the i400).
PC (in SuperOneClick): Now click the root button and wait for the process to complete.
PC (in SuperOneClick): "BusyBox not found. Would you like to install it?" Yes!
PC (in SuperOneClick): "Root install has completed! Would you like to run a test?" Yes!
PC (in SuperOneClick): "Your device has been rooted! Would you like to donate now?"
Exit SuperOneClick, unplug phone from USB, power down phone, power on phone. -- this step might not be mandatory, I just did it to be on the safe side.
Enjoy!
Great job on this tut.
Sent from my SCH-I400 using xda premium
Nice...
I may have to sneak my wife away from her for a bit....
Sent from my DROID using XDA App
Froyo is so nice... Here's how...
Hey guys... new poster here.
Just got a (Gently used) Samsung Continuum for free from Verizon after the power button on my G Droid 1 broke.
Anyways, after rcving it and realizing that it would only support Android 2.1 - I was slightly upset.
My D1 was rooted and modded to the max many times over with just about every ROM you can get.
So after reading up about IMNUTS leaking the Froyo download for the Continuum, my hopes were raised.
It is now debinged, debloated, lightening quick and amazing!
There may not be ROMS out there yet - but I truly hope some of you geniuses decide to make a few.
Just wanted to say thanks and encourage you to do some research before rooting it.
Here's what worked for me.
Odin 1.3
Continuum PIT.pit file
froyo_modem.tar.md5
cwm_recovery_test4_adryn.tar
cyan Clockwork Mod Recovery (BLUE, not yellow) (update.zip file, which is placed on the root of your SD card - renamed to update.zip)
stock_deodexed_ec03.zip (ROM)
(Place all of these files on your Desktop for easy access)
How to do it...
1. Connect your phone to your computer and Mount it.
2. Place the cyan CWM Recovery zip file to your SD card. (rename it to update.zip & do not put it in any folders. Just drag the file to your SD card - whatever drive it is listed as. Mine is my Removeable F
3. Make a new folder on your SD card. Name it whatever you want. (Mine is named "Froyo") Place the stock_deodexed_ec03.zip file in the folder on your SD card.
4. Open Odin 1.3 on your PC.
5. While your phone is off... hold the down volume button and connect it to your computer via USB. The yellow triangle will appear and it will say "Downloading". (Some people say to take the battery out, but my Odin program would not recognize my phone without the battery. Whichever works for you is fine.)
6. In Odin - Click the PIT file button. Load the Continuum.Pit.pit file into the file field. (Just double click it once you find the file from your Desktop.)
7. In Odin - Click the PDA button. Load the froyo_modem.tar.md5 file into the file field. (same as #6. Just double click it once you find the file from your Desktop.)
8. Click Start in Odin.
It should think for a minute, then say resetting, then say PASS
Then your phone will probably turn back on - turn it off again and reconnect it to your PC in download mode as stated in #5 above.
9. In Odin - Click the PDA button again. Load the cwm_recovery_test4_adryn.tar file as you did in #'s 6 and 7 above.
10. Click Start again in Odin... same as before. (thinking, resetting and PASS)
Your phone will turn on again.
11. Disconnect your phone from the computer & turn it off.
12. Hold both Volume buttons and turn it on. It will boot into the Samsung Recovery mode.
13. Use your Volume buttons to go down to highlight "apply update.zip" Then find the place where your normal Menu softkey would be and push it. The phone should then reboot into Clockwork Mod Recovery. It will be orangish.
14. In CWM, use the Volume buttons to highlight Backup/ Restore. Use the Power Button to choose it. Then at the next field, highlight Backup and make a backup.
15. After is makes the backup, press where the softkey Back button should be to go back to the original screen. From there, do a Wipe Data/ Factory reset. Do not forget to do this part.
16. Once it does the Data Wipe - go back to the main menu and and highlight & select the "zip from SD card" choice. Find your "Froyo" folder (of whatever you named it) and apply the stock_deodexed_ec03.zip file.
17. After that, go back to the main menu again and reboot your phone.
It may take a while, but your phone should restart in Froyo.
Of course, you have to re-sign in to your Google network...
Thanks so much guys for all the posts. Without them, is nowhere near as cool.
Hanging at Step #5, Now what?
Thank you for sharing. Wish I could say it went as smoothly for me with my SCH-I400 Continuum... I'm still working on it! I followed recommendations of several different developers/rooters. I've installed .Net Framework 4.0 and the SDK developers kit (who knows, maybe I'll start a new hobby...), and now when I run Superoneclick it hangs at step #5 with this message:
link_image[1728]: 3252 could not load needed library 'libdiskconfig.so' for './zergRush' (load_library[1058]: Library 'libdiskconfig.so' not found)CANNOT LINK EXECUTABLE
I have rebooted the computer and the phone, unmounted the SD card, settings to allow unknown sources, and turned on USB debugging. I'm not sure why the config file can't be found, and I don't know where to get it...
Do I need to reinstall the SDK? Or install the additional Java developers software? Or am I over-complicating this whole thing?
Any ideas will be greatly appreciated...
-James
Perhaps the easiest way is to flash a rooted ROM through Odin (or Heimdall)... Especially if you don't use Windows. This is how I did it:
http://forum.xda-developers.com/showthread.php?t=1203597
Two topics in one thread?
Hmmm... seems we have 2 things happening hear. 1: Rooting a Samsung Continuum, and 2: Flashing a ROM...
My concern is the "hang" at step five for Rooting my Continuum SCH-I400... Cant use a ROM until the dang thing is rooted, and can't seem to figure out the hang.
Tried Z4 root from the phone rather than through the PC and it hung indefinitely... Maybe there's a related issue, and I don't care if it's Superoneclick or Z4 that gets the job done.
Has anyone gotten past the same issue?
-James
bighigmt said:
Hmmm... seems we have 2 things happening hear. 1: Rooting a Samsung Continuum, and 2: Flashing a ROM...
My concern is the "hang" at step five for Rooting my Continuum SCH-I400... Cant use a ROM until the dang thing is rooted, and can't seem to figure out the hang.
Tried Z4 root from the phone rather than through the PC and it hung indefinitely... Maybe there's a related issue, and I don't care if it's Superoneclick or Z4 that gets the job done.
Has anyone gotten past the same issue?
-James
Click to expand...
Click to collapse
That's where you are over complicating. You don't actually have to root BEFORE you flash a new rom, if the rom is 'prerooted'. I've never rooted this thing via s1c or z4. I simply flashed the kernels via odin and flashed the rom in cwm.
Either let me fly or give me death. Let my soul rest, or take my breath. - DMX
Txwolf1980 said:
That's where you are over complicating. You don't actually have to root BEFORE you flash a new rom, if the rom is 'prerooted'. I've never rooted this thing via s1c or z4. I simply flashed the kernels via odin and flashed the rom in cwm.
Either let me fly or give me death. Let my soul rest, or take my breath. - DMX
Click to expand...
Click to collapse
That's fine Txwolf, but still doesn't address the issue... Or the original reason for this thread - Rooting - which is is essential for the programs I am going to run, and that is what I have been asking about...
bighigmt said:
That's fine Txwolf, but still doesn't address the issue... Or the original reason for this thread - Rooting - which is is essential for the programs I am going to run, and that is what I have been asking about...
Click to expand...
Click to collapse
The issue seems to be that you just have to use that little search box a little better via xda or your web browser and find more information the root program your trying to use.
When you give up on that you can take txwolf1980 's advice
PS hang on step 5 in OP? Or in 3rd post? That would be getting into dl mode lol
Sent from my SCH-I400 using xda premium
Come on now...
ciscogee said:
The issue seems to be that you just have to use that little search box a little better via xda or your web browser and find more information the root program your trying to use.
When you give up on that you can take txwolf1980 's advice
PS hang on step 5 in OP? Or in 3rd post? That would be getting into dl mode lol
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
I spent 6 hours last night troubleshooting, researching, digging deep, and "using that little search box." Seems to me You guys need to "just read the thread." It's about rooting your phone, period. If a forum is out there, I've probably read it. I'm using superoneclick to do it. SDK is installed. Net framework is installed. My error message frome SOC is above. When I am finally rooted, THEN I will install several programs - starting with a wifi tether.
I see you have the same phone as I do. Is it rooted with a one-click method? I also tried Z4root and didn't like it.
bighigmt said:
...Seems to me You guys need to "just read the thread."...
I see you have the same phone as I do. Is it rooted with a one-click method? I also tried Z4root and didn't like it.
Click to expand...
Click to collapse
well i did read the thread...
ive been out of town for a week and finally back on my pc... i would love to help you yet more info is needed.
you are running dl17 stock 2.1 correct?
what OS is your pc running?
and yes i have same phone as you. i have used superone click on ec03 build once.
just for root. but then flashed a deodexed rom to use custom mods and apps.
and since have been flashing rooted kernels, imnuts and adrynalynne have released most all of them.
there are a few ways to root the device, best bet is, as always is go to IRC.
clarity and patience are key, we all got to practice both
I rooted EC09 with soc no problem. If I send someone the EC09 could they extract the apks and send them to me? I deleted some sys apps for the ticker and rss feeds and need them back now to use it.
Sent from my SCH-I400 using xda premium
Unzip factory.rfs of ec09 to grab missing apks and put them on sdcard and install from there.
Sent from my SPH-M580BST using Tapatalk 2
verizonless said:
[*]PC (in SuperOneClick): Make sure you're on the Universal tab (the only other tab is Samsung Captivate, which isn't the i400).
Click to expand...
Click to collapse
FYI, my Windows Defender threat scanner just reported this SuperOneClickv2.1.1-ShortFuse.zip file as Exploit:AndroidOS/CVE-2011-1823, more specifically pointing at a file named Exploits/GingerBreak in that ZIP file.
I am going to delete this ZIP file as I no longer need it, but I got curious: Any idea what this means?
verizonless said:
FYI, my Windows Defender threat scanner just reported this SuperOneClickv2.1.1-ShortFuse.zip file as Exploit:AndroidOS/CVE-2011-1823, more specifically pointing at a file named Exploits/GingerBreak in that ZIP file.
I am going to delete this ZIP file as I no longer need it, but I got curious: Any idea what this means?
Click to expand...
Click to collapse
It means it'll root your phone. Some applications could try to do this without permission and do shady things with your phone. Nothing to worry about if your doing it on purpose.
trailblazer101 said:
It means it'll root your phone. Some applications could try to do this without permission and do shady things with your phone. Nothing to worry about if your doing it on purpose.
Click to expand...
Click to collapse
Im assuming by now everyone is on EG04 Gingerbread?
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
WARNING!
If you dont know the slightest bit of Windows or Linux shell and never did more than USE the device, be warned... If you kill it, its dead!
emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Click to expand...
Click to collapse
I confirm it works perfectly. ICS TPT _A400_03_0070_0132_US :good:
God, this is so wonderful. CWM works, Koshu's CM10 JB Firmware, too. I LOVE THE DEVICE AGAIN!
Great news! Who might have thought that a working exploit is already out there?
This is wonderful news, a friend of mine recently lost root after he had to send his TPT in for repair and got a new board already updated to ICS.
FANTASTIC - worked on UK running OTA 3.5
Booyah! Thanks Emuandco for your diligence!
Thank you. Had lost hope of root for ICS. My TPT may finally be the tablet I paid for.
22 hours and 5 badly needed factory resets were worth it ^^
Thanks a lot :good: :good: :good:
I just rooted my ThinkPad (WE version). Works like a charm.
emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
Click to expand...
Click to collapse
wonderful!!!
Thanks a lot!!!
Just tried and it worked!!!
after some trouble installing the adb drivers it worked fine on my WE tablet..finally, awesome, thanks
Amazing how much of a difference having root on this tablet makes.:good:
Stylus and Pressure Sensitivity
Been waiting a long time for this. I had one question that I can't seem to find the answer to. I use my TPT for sketching, allot, it's why I bought the tablet. I was wondering, if I root and then upgrade to Jelly Bean, will I lose stylus and pressure sensitivity?
Can someone post the steps to get this working starting from a clean OTA 4.0.3 rom? I just started messing with the TPT. What boot options are there? I see the hold-down-rotate-and-power boot which looks like what is needed for nvflash, but I can't seem to get any other bootloaders booting here. The debugfs script seems to want to talk to a recovery boot, yes? How do I boot into recovery mode?
Sorry for the TPT newbie questions. Is there a wiki someplace with all the boot modes and other info?
First, load this one: LINK
Its the Driver needed for the TPT to communicate with the PC over ADB protocol.
Go to your TPT Settings below inside Developer Options and check USB Debugging. Attach to your PC and hand the new unknown Device in Device manager the loaded ADB Driver. Then download and unzip everything from the Exploit into a directory; then run RootDebugfs.bat from that directory. This should do it for the rooting of the Stock Firmware. You can verify it by getting "Root Checker" from Play Store. If its green, next load this one: LINK and this one LINK. Its the ClockWorkMod aka modded Recovery Mode making it possible to flash unsigned Updates and making nice Full Backups and the JB Firmware itself.
Install this way from a windows console bein inside the folder where the adb.exe from the exploit is, Step one is making a backup of your previous Recovery Mode for future reverting if you want to do so. Step two is the actual install. You need to copy the loaded recovery.img from the CWM thread to the SD in your TPT, same goes for the JB ZIP File and maybe the 3G Patch for the 3G Card you might have.
BE SURE ALL FILES ARE COPIED ON THE SD AND ITS INSIDE THE TPT AGAIN!
Code:
adb shell
su
dd if=/dev/block/mmcblk0p1 of=/mnt/external_sd/orig_recovery.img
mount -o rw,remount /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
dd if=/mnt/external_sd/recovery.img of=/dev/block/mmcblk0p1
exit
exit
This should be enough. Now reboot and while the Lenovo mini Logo shows up, push Vol UP rapidly. This should boot up CWM6, our modded recover Mode. Here Vol UP is upwards, Vol DOWN is downwards and ON/OFF is Enter. First thing, DO A FULL BACKUP TO EXTERNAL SD in "backup and restore", "backup" !!! Then let it do a "wipe data/factory reset", then select "install zip from sdcard" and in there "choose zip from external sdcard". Choose the CM10 JB ZIP first, then the 3G Patch for your Card.
Reboot and youre done.
i have updated to the latest ota and i am not rooted.. A400_03_0070_0132_US
when i run it and choose option 1 the window automatically closes after like 2 seconds
am i supposed to use the asus drivers or what? if anyone can please help...
Somebody buy that man a beer.!!!!!!
Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.
pwstein said:
Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.
Click to expand...
Click to collapse
I have already tried that doesn't work. when in cmd i write adb devices it shows the device is connected
i have put it to transfer files and MTP settings with unknown sources and debugging on ..when i run the .bat file
after the *demon started successfully* it suddenly closes after which nothing happens..what do you think is wrong?
Open a CMD prompt and run the bat file from there. then show us the output of the script please.
AAND be sure that theres not any adb.exe coming from the system path variable, like in system32 or syswow64. kill these