Related
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
So, I used to run WinMo way back when, and I'm familiar with flashing, HardSPL, blah blah blah, whatevs. I haven't done the rooting process yet on my phone because I'm finding it hard to find a few key things that I need.
-What is the effect on my phone when I root, in regards to data? Do I need to backup? If so, can I backup on my SD card or is everything wiped? What program could I use to backup?
-Are there any crazy little tweaks or tips that anyone has to help guard against a brick?
-I've read the pros and cons list, but can I get more details from someone? Can this help with battery life, allow me to flash my radio, increase general connectivity, etc.
All help would be greatly appreciated, and I'll plan on doing a donation today. I've just been out of the loop (running WinMo 6.5 style out of the loop:/) so some advice to a rook would be great. My goal is to get out of school and come home and root and fiddle with things with little to no problems. Thanks a ton everyone.
Dig Life!
D
The process of actually rooting doesn't mess with any of your stuff.
I use Titanium Backup to restore apps after flashing roms.
In general, most of this stuff COULD help your battery life, here there are Devs that will help - with sprint you get their tech support.
Well, I DL'ed TB and it says that I have to root first? Am I missing something here? Is it ok to root or will it delete all of my apps and what not? I mean, if it does, it isn't really that big of a deal, considering I can just download them again, I'm just looking for input.
copsgottanks said:
Well, I DL'ed TB and it says that I have to root first? Am I missing something here? Is it ok to root or will it delete all of my apps and what not? I mean, if it does, it isn't really that big of a deal, considering I can just download them again, I'm just looking for input.
Click to expand...
Click to collapse
I'm pretty new, too, but I think I can answer your questions. Rooting (at least with the One Click Method I used on my Epic) doesn't destroy any data/apps on your phone. It simply gives your user root access to the underlying OS. Once that is achieved, you can modify things and tweak things. Titanium Backup will let you backup all system files and data, but only AFTER rooting.
This is not a ROM flash or anything like that from the WinMo days. I haven't gotten that far on Android, so I'm not sure what the flashing options are yet, but rooting is harmless on its own. It will let you royally screw things up though, so once it is done, be careful what you do.
Well, I tried to do a few things like listed in the One-Click root thread, but I guess I'm just not getting it. Now that I know the effects of the root, I'd like to be able to actually do it, but I don't have enough details. I haven't ever rooted before, and I'm finding it confusing. What was listed in the one-click thread wasn't specific enough for me, I don't know if I need to run from SD card, what the ADB thing is, nothing. I was a WinMo master and I'm finally coming to Android which is literally worlds away from my comfortable norm.
what os are you running? the one click comes with everything you need. theres an osx version the windows version that noobnl updates and the linux version i maintain
I'm on Windows 7 64 bit. But I still can't get any of the one click stuff to work, I don't really know what exactly to do
copsgottanks said:
I'm on Windows 7 64 bit. But I still can't get any of the one click stuff to work, I don't really know what exactly to do
Click to expand...
Click to collapse
I wouldn't exactly call root harmless..in itself it is ok..but if you give root access to a program that program has FULL access to your system..aka anything inputed on your phone or stored on your phone can be accessed by the program with root access. Though generally its not a problem..just careful which programs you allow to use root access.
Also, at what point are you getting stuck? did you install the drivers? are you getting any sort of errors or etc?
There is also some good reading over at SDX Developers.
I have hacked and rooted before, WinMo, Palm, HTC Hero, but this one was tough. It basically took me two days off and on, but it worked - finally.
Downloading drivers is a b--h, they are finicky and I needed all of them, kept
hanging on 2. They are slow, and kept looking for sources.
Search here, there is good info, then look there (above) I used OneClickExploit 2.2.4 which finally worked. It had some of the same files
in other methods, but this one worked.
I'm not changing roms, did on Hero to 2.2 because they weren't getting upgrade but I'm just going to hang and wait for Froyo.
Good luck
copsgottanks said:
I'm on Windows 7 64 bit. But I still can't get any of the one click stuff to work, I don't really know what exactly to do
Click to expand...
Click to collapse
Download and unzip the one-click archive in to a folder. Double-click the run.bat. I had some problems where it would start and then hang. I often had to kill it and rerun the batch file. Sometimes I had to end task on the adb.exe process. Eventually after rebooting the phone, etc, I was able to get it to work. Not sure what the exact problem was. I think part of it was connectivity to the phone via usb. Connect through a port on your computer, not a hub.
Also, the batch file is just a bunch of commands. You can open a command line in the folder where the batch file is and run each line in the batch file individually from the command line. That will give you some idea of what is happening and where it might be failing.
Like I said, I had to stop and restart a bunch of time before it finally got through to the end of the batch file correctly. When it did, it was fast. Not sure what was happening.
gTen said:
I wouldn't exactly call root harmless..in itself it is ok..but if you give root access to a program that program has FULL access to your system..aka anything inputed on your phone or stored on your phone can be accessed by the program with root access. Though generally its not a problem..just careful which programs you allow to use root access.
Also, at what point are you getting stuck? did you install the drivers? are you getting any sort of errors or etc?
Click to expand...
Click to collapse
When I try to install the drivers I get this message:
"The MSS InstallWizard was not Completed for SAMSUNG USB Driver for Mobile Phones V1.3.450.0
The MSS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones V1.3.450.0. Click Finish to exit the wizard.
And I'm basically stuck there. I've searched around and can't find any drivers that will work. Like I said, I'm on 64-bit Windows 7 with a clean OS and no previous negative install history. Not sure what the issue could be?
Found the drivers and everything that I needed and I'm rooted, but now I have one more question. I don't plan on flashing any roms, I'm alright with the stock rom, at least for now. I wanted to know what rooting will do in regards to over the air updates on my phone. Will I be able to OTA to FroYo when released? Any info would be great guys, thanks.
where did you find the drivers? I am having the exact same problem that you had where the installwizard cannot download finish installing the drivers for whatever reason
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
Brand new phone...can't believe i did something wrong only a few hours into it!?
To cut to it, i am not able to run anything on my PC to my Atrix bc the phone is not visible to it via usb sync. It DOES still see it if i needed to transfer files etc, just not so i can flash anything to it off the PC.
And not sure if it has anything to do with it, but it seems like i ran into my problem when i inserted and formatted my SD card. Here's what i did (and i hadn't gotten very far):
I rooted with SuperOneClick, then I installed DG's Adeo ROM and the update.
I was trying to install Gingerbread and was just putting busybox installer on my phone when i went to put my SD card in there from my old phone. i formatted the card and it seemed after i did that i lost connectivity via the USB. It could still access the phone, but everytime i run ATRIX4G_MobileTV_GBTheme.bat it hangs at "daemon started succesfully" . It also hangs if i try to run SuperOneClick again on "waiting for device."
I wasn't sure what to do to get it running right again so i did a full wipe from the settings. Still can't connect
Any help be greatly appreciated. i've literally had this phone 4 hours so sorry if i'm missing something dumb
Try running aRoot (search this forum) and then trying all that.
thanks for that suggestion, gonna try that....just as soon as the damn search function comes back!!
oh the waiting...i am not going to be able to sleep tonight till i get somethin happenin
No need to search, it's only hanging about 3-5 posts down in this section. It's also here:
http://forum.xda-developers.com/showthread.php?t=981866
Ran aRoot - seems to run through the steps without a failure, but it went VERY fast, like 3 seconds...and it hangs when i try to "unroot"
so, all in all it seems like its still not recognizing the phone as before when connected through USB
Dillsnik said:
Ran aRoot - seems to run through the steps without a failure, but it went VERY fast, like 3 seconds...and it hangs when i try to "unroot"
so, all in all it seems like its still not recognizing the phone as before when connected through USB
Click to expand...
Click to collapse
Do you have Root Explorer? If so, look in /sbin and see if you have 'adbd' showing
OR
Have you tried installing the ADB interface from the Android SDK? See if your device can be seen? If not see THIS ARTICLE (external link to addictivetips) on setting up ADB.
No, I don't have Root Explorer
I installed SDK and ADB and it does show up, but only when the USB setting is set to "Motorola phone portal." None of the other options it shows up in device mgr.
I am kinda stabbing in the dark at this point...thinking maybe it's a driver issue?
maybe if i uninstall all the drivers and start from scratch i might have some luck? i actually did unistall all the drivers thru device mgr, but they just came right back next time i connected...so maybe i need to delete them entirely?
any suggestions to trouble shoot this greatly appreciated...i know it's probably small potatos but i'm really jammed up here...
Moved as not android development
Have you tried installing the latest drivers again directly from the Motorola Mobility site? You can install Media Link or just the drivers with MotoHelper. For some reason my phone installed all of this, but there were updates available immediately.
The ADB interface should function when USB is set to None.
Sent from my Rooted Atrix using Tapatalk Pro
Yeah i actually did a system restore and reinstalled all the drivers etc.
I can see the phone now in the device mgr under ADB interface when connection is set to "None" for USB
But still hangs when trying to flash basically anything
Do you have or can you pick up a Terminal Emulator in the Market and list the files in /sbin? See if you have adbd...
From $
su
cd /sbin
ls (Lower case L, not 1)
Look through list of files for adbd.
Sent from my Rooted Atrix using Tapatalk Pro
OK, No it's not in there
See this post here: http://forum.xda-developers.com/showpost.php?p=11738847&postcount=1 and the cooresponding thread for replacing adbd. There's another post in the thread about changing the permissions so that it doesn't get lost again with a reboot. You might have to purchase Root Explorer since you cannot push anything via ADB over USB.
Sent from my Rooted Atrix using Tapatalk Pro
This seems to be the type of problem i am having, very much thanks for directing me to that other thread.
At this point i have copied ADB to the sbin folder but nothing flashing yet...need to read through that thread more and play with it.
What a PITA so far but thanks so much for the help!
No problem. I hope it works out. If you don't mind, post up and let me know if you get it going and what it took so we can try to help others.
Sent from my Rooted Atrix using Tapatalk Pro
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot (following instructions here on the forum) mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
a friendly warning
CyaN1de said:
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
dibb_nz said:
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
Click to expand...
Click to collapse
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
CyaN1de said:
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
yeh just a group of extended adb commands that allow you to do some pretty awesome stuff - like really, really bricking your tab for instance, lol. I'm unsure as to whether all the fastboot commands are available to us - i havent had enough spare time to devote to heavy duty reading in the Dev Forums!!!! You can flash everything in here so its like a supercharger;;;;Sort of like going from timmydeans EUU root to Civ's nvflash unlocking bootloaders thing, if you know what i mean.......
But heres some reading, most of it tutorial step by step stuff, mostly for other devices which may not apply to our tab but definitely apply to fastboot. AS you know, there is alot of info in our own dev forum but its hard to find a flow as the devs actually speak a different language to us!!!! So the tutorials are quite good in that respect as they use noob-ite speak
the backup and restore tute is a goody, couldnt get it going on v3 so looking forward to giving it a go on v4 (when i can find a quiet 30 mins or so, that is)
anyways happy reading be interested in your thoughts and keep us posted about what you get around to trying
rgds
Full Phone Backup http://forum.xda-developers.com/showthread.php?t=1420351
setup adb http://forum.xda-developers.com/showthread.php?t=1249798
adb http://forum.xda-developers.com/showthread.php?t=879701
adb logcat http://droid-force.com/showthread.php?tid=150&pid=573#pid573
ics BL by Skrilax_CZ http://forum.xda-developers.com/showthread.php?t=1514951
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Set up adb/fastboot for noob-ites 101
CyaN1de said:
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Click to expand...
Click to collapse
weird??? i kicked straight in to bl, fastboot drivers installed, never saw red x
u mean u arent cmd from platform tools???
in the cpuid guide I suggested extracting the just_adb.zip into C:\ so setting
up the env. var. would be easier I have been meaning to post the steps for
doing that, guess theres no time like the present
Set adb as Environment Variable or call adb direct from command prompt
............ first, copy the path to your install - in your case:
............ "Path to adb" = D:\Android\android-sdk\platform-tools
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in your case ;D:\Android\android-sdk\platform-tools
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
as you can see this makes trouble shooting so dam easy -
if you cant get a device id do not go any further in what u r doing
cos it aint gonna work....period!!!!! also since ICS has screwed
with getting our cpuid like this, for our purpose here, it is only important
that a device id is shown - not how right or wrong it is.....clear????
so getting back to it, check fastboot*.exe in same folder as adb.exe -
it came like this in my own setup not sure about the asdk setup -
remember too fastboot only has a few commands and i still havent
got round to trying them all out yet....
to anyone following this, I cannot say enough how dangerous this can be
please, please, please take a moment to read thru just one of the links i
posted earlier - they are tutorials and if you see the dev thread regarding
v4 unlock...you will not only learn something amazing but begin to
appreciate and respect the work done by these devs who laid the groundwork
that enabled civato and blakthund3r to produce what they have with the
unlocked bootloader - without this groundwork we would still be waiting
for a way to get full root access and cwm, custom roms, themes and mods......
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
CyaN1de said:
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
Click to expand...
Click to collapse
sweet m8 -
yeh whoever thought windoze would actually be useful!!!!
which i guess is freakn handy as having to go linux would spin me out....
what can i say??? I'm a child of windoze had no choice, forced-addiction
before i was born, lol - breaking the habit, but always go back, goddamit
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Trying just "fastboot reboot" (not wanting to go any farther until I get a grasp...HAHA) I get "waiting for device"
CyaN1de said:
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Click to expand...
Click to collapse
dont let windows install
choose let me choose where to install dunno exact wording
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
CyaN1de said:
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
Click to expand...
Click to collapse
Yr head hurts????
Ive updated the cpuid guide u my wanna take 5 min timeout to read it, the answers r all in there
I don't use full sdk there's a link to mini sdk zip in that post just has ad and fast boot
I've never had to use google drivers
Just plugged my tab in and its just 'worked'
DL Acer drivers if u haven't already . These are the most important ones to have installed right.
Disconnect and reboot everything
Run Acer setup.exe
Plug USB in
Go into fast boot, win doze will want to install f/b drivers let win doze do it, but if they fail, then run again and choose let me install, blah, blah, blah
What OS u got? Vista/win 7 don't normally have any probs
Acer drivers have been installed and all relevant sdk packages installed and up to date AFAIK. (USB_Acer_1.06.1500_A30HA31H_A.zip)
Had no issues installing ICS Bootloader V.3 manually through APX (no auto script) via instructions so I know I can at least do that well.....LOL
Might have to try reinstalling USB drivers and see if that helps.
Thanks
EDIT: Reinstalled USB Drivers now I can't get adb working....F#@K!!!!!!!!!
EDIT II: Re-Re-Installed Drviers and ADB working again...yay...LOL
EDIT III: Used A500_Manager.exe, clicked on "Enter Fastboot" and windows installed and recognized drivers......DBL YAY!!!!
C:\Users\username>fastboot reboot
rebooting...
finished. total time: 0.165s
Now.......to Brick this puppy.....
Thanx for your help dibb_nz....looks like all I needed in the first place was a driver reinstall...HAHA.
Hek m8 for a second or two there, I was feeling ya pain, lol
Oh but the elation when it finally happens!!!!!
I dunno why those drivers act out like that, but it always the same....
Fail, reinstall, fail, reinstall u can understand why peeps get frustrated
Glad u got it m8