Discussion in 'Android Devices' started by GrdLock, Mar 17, 2010.
gotta unzip it
yea I think jreed is right, did you just put the file in your sdk tools folder, or did you right click and then unzip the file to the sdk tools folder??
I have a Eris, 1.5 with OTA 2.1 installed.
are the steps on the first page what i want to use for root? i want to tether my Eris to my netbook while away from home.
also, is this process reversible incase i want stock 2.1 ota?
1) Yes, you can use the process to r00t your 2.1 phone the same as a 1.5 phone.
2)You don't need r00t to tether your laptop, PDAnet works.
3) Yes r00t is reversible.
so 2.2 is out for root users...."androidandme.com" let me know how it goes
it may only be for droid tho i dk just saw a post
OK, so I've decided to root and I have a question... does the android SDK and java get downloaded to the phone or the PC?
As great as the instructions are, I'm a bit of a literalist and they are just a bit too "grey" for me...
Please be gentle...
Download those programs to the computer, NOT the phone.
I'll be with you shortly, hoping to r00t tonight when I get home from work. Get ready guys, I'm coming to IRC for help...probably around 1:00am EST
I can't get past the "update drivers manually" step of the pre-requisite to r00t. Windows says the software cannot be found. I know I'm in debugging mode. I know I downloaded the usb for SDK cuz I can see the files, but for some reason, Windows keeps giving me an error. Any ideas?
Yeah same thing on my Win 7 machine. It won't recognize the drivers.
Anyone know when we may recieve a Rom based off 2.2????
Don't hold your breath
ive got my phone drivers working but i can not get my pc command prompt to work. I could be doing something wrong here but im not sure. Anyone have any ideas.
OK... so, I think I figured something out here. I can actually root without the SDK but in order to create the recovery image I need it right? I've looked at a few "how to" videos on YouTube and nowhere in there is SDK mentioned, nor are they mentioning creating a partition for a recovery image. And I guess looking at the instructions provided here, they pretty much just say to download certain files and put them on the root of the SD card while the recovery image part is done in SDK... so I think I understand that part now. Hooray!
However, stumbling block #2 appears for me: it seems some people are having problems updating drivers; I've looked at the Windows system requirements for the SDK and they do say that are compatible with XP and Vista. Could this be a general problem for Win7 users or is it more localized?
In the end all my careful prep work will be for nothing as I'll probably end up bricking my phone due to my nearly mutant ability to disrupt any electronic devide...
Is there anyone out there working on this Windows 7 driver question?
I was hoping to root tonight when I get home from work, but if I can't get this answered...well, obviously, I won't be able to
I just had this problem, downloaded HTC sync and it looks as if it is working now
I'll try that again tonight, but last night, HTC Sync didn't work for me. In case someone else wants to try it, could you give us the link where you got HTC Sync?
Anyone? I'm almost out of work and really hoping to get this done tonight?!?
I got it rooted, found a way around the driver issue.
I'm at work again, so can't give a ton of details, but hopefully you'll catch my drift and if not, I'll give more detailed instructions when I get home.
Basically, when you right click on your device to "update driver", go to the option to do so manually, then click the option to browse on your computer, get to the point where you can click "I have a disc" and when it prompts you for the path, direct it to the folder containing your drivers (probably in your C:\androidSDK\tools folder), and select the driver from there. Windows 7 saw them that way, but not any other way...go figure. Let me know if you need the more detailed instructions.
im getting the same out of memory error when trying to make the recovery partition... im using a mac and i tried waiting a min between each command, i formatted my sd card, and i switched to a different usb wire. upon switching to the usb wire my error went from the very long one where it tries every block to just this :mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00120000 (Out of memory)
mtd: read error at 0x00140000 (Out of memory)
mtd: read error at 0x00160000 (Out of memory)
mtd: read error at 0x00180000 (Out of memory)
mtd: read error at 0x001a0000 (Out of memory)
mtd: read error at 0x001c0000 (Out of memory)
mtd: read error at 0x001e0000 (Out of memory)
mtd: read error at 0x00200000 (Out of memory)
mtd: read error at 0x00220000 (Out of memory)
mtd: read error at 0x00240000 (Out of memory)
mtd: read error at 0x00260000 (Out of memory)
mtd: read error at 0x00280000 (Out of memory)
mtd: read error at 0x002a0000 (Out of memory)
mtd: read error at 0x002c0000 (Out of memory)
mtd: read error at 0x002e0000 (Out of memory)
mtd: read error at 0x00300000 (Out of memory)
mtd: read error at 0x00320000 (Out of memory)
mtd: read error at 0x00340000 (Out of memory)
mtd: read error at 0x00360000 (Out of memory)
mtd: read error at 0x00380000 (Out of memory)
mtd: read error at 0x003a0000 (Out of memory)
lol .. what an ordeal.. a co-worker called me over to his place to help him root his Eris.
I should never have gone.. we couldn't make anything happen beyond the installation of the latest java and the sdk thing; device manager in Windows 7 wanted nothing to do with the driver in that sdk directory, yielding "the destination file is unreachable." (we both thought it was pretty funny because we were looking at the inf file right there but W7 called it "unreachable."
So, no root for Henry. It's ok, he's happy with his 2.1 as-is anyway, he's just a bit of an experimenter type of person.
Headline tomorrow will read: "Frisco inches closer to rooting his Eris!"
...there is the sound of drums in the distance...getting closer...
Heh.. well, the instructions in post #1 here are pretty clear; we were looking at that thinking we were missing something between the lines.
As it is, I haven't seen much in here in the way of reports on rooting from people using Windows 7.
That was exasperating about that driver.. there it was, and his computer could not get to it. We tried putting it everywhere from Program Files to Downloads to Desktop.. no go.
I half-rooted (yes, really (install base root ROM)) on my Windows Vista laptop and struggled with the USB drivers there.
Then I finished-out the root process (install Amon's recovery image, install custom ROM) on my son's Windows 7 desktop and I don't remember having any USB/connectivity issues there.
Ain't computers wonderful?!?
In Windows 7, what happened when you went to the Device Manager, saw the yellow icon in "others," and right-clicked it then selected "update driver?"
It is at that point that we used "browse my computer for driver software," then kept clicking folders until we were at the path to the "usb drivers" folder.. there we saw i386 and clicked it (first try) and it yielded nothing.
We then clicked the usb driver folder itself with the same result.
We then typed in the path, including the name of the driver, "android_winusb.inf," nothing except a message saying "unreachable."
At that point we began our snickering and laughter..