My phone says S-OFF in the first two lines.
OK, that means that you succeeded with steps 1-4. You have the
beginnings of root on your phone. That's the good news.
The bad news - as you found out - is that the version of the OS that comes with the ROM that gives you a S-OFF bootloader is full of bugs - nobody uses it. It is possible to go back to 1.5, or go forward to a nice root ROM - but both of those paths are full of "techie". There isn't a click-one-button solution for getting you out of where you are. Since the effort is about the same, I recommend that you go forward (to root working well).
Here is another question I thought I was doing something wrong because my computer was not recognizing the phone, however when my g/f got home I pluged her eris in and the computer found it instantly...
Uh Oh.
Have you ever "mounted" the SD card onto your PC while attached with the USB cable?
Forget about root for a moment - I am just asking about whether or not you have evidence that your hardware is working.
I am having trouble with parts 2 steps 10 and 11 of the walkthrough, and part 3 step 2.
Let's talk about Part II, steps 9-10.
What might be a little confusing is that the way USB works, you can have lots of individual software drivers to support different functions on a hardware device. So, even though your GF's Eris can "talk" to your computer, what these instructions are trying to do is install a separate driver which will be used by the "adb" program that comes with the SDK.
- Plug the phone in to the computer, enable Debugging on the phone (Settings -> Applications -> Development -> USB Debugging), and while you are there, turn on Stay awake (Settings -> Applications -> Development -> Stay awake)
- Re-read step 9. Do you see a yellow exclamation mark, (or equivalent for Windows 7)?
For part 3 step 2, Am I supposed to transfer the file to the tools folder? because when I am in the SDK program there is no tools option within the window.
The "tools" folder is a folder inside the folder that all of the SDK files get installed to on your C: drive. I don't have a windows install in front of me, but I think that top-level folder starts right at the top of the C: drive, and has "Android" in the name. The "tools" folder will be either directly underneath this one, or one more folder down - on your PC, use a Windows file browser to locate this directory.
Yes, you should
extract the zip file into the "tools" folder once you have located it. Strictly speaking, it is not necessary to put your data files in here, if you are able to add the SDK tools folder to your PATH (step #11). but it causes no harm, and makes it possible to skip the part about modifying your PATH.
NOTE! I went and checked the Zip file (recovery.zip) that is in the XDA post you referenced. It will work correctly, but I notice that it uses an older version of Amon_RA's recovery image (the file called "recovery.img" in the Zip file). You might want to grab Amon_RA's most current recovery image directly from the download link
in his post on XDA (about 2/3rds of the way down the page under Download). His newer version (v 1.6.2) will be named "recovery-RA-eris-v1.6.2.img" and has a MD5 checksum of e3932991f097993602af3c7a4b61a4f8.
After unzipping "recovery.zip", delete the old "recovery.img" file that comes with that zip file, copy recovery-RA-eris-v1.6.2.img to the same (tools) folder, and rename it to just "recovery.img" so that it is compatible with the other instructions which follow.
Again not being very techie (or at all for that matter) means that if the instructions say "press the green button" and there is no green button I freak out, and don't have the know how to work around that....
Tell yourself, "I can do this." Don't defeat yourself before you begin. There are lots of people with exactly your skills, that can work through stuff like this - the only difference is that they don't give up, and also try to have a relaxed mind about it. No, you won't understand everything at first, but that's OK.
I am running windows 7 and the instructions are designed/written out for xp users some things tend to be a little different.
I believe that, and I have noticed that Windows 7 users seem to have more trouble with this particular step (driver installation) than other users. I'm no expert here, but I have noticed a few other people claiming "I just installed the
HTC Sync Application, and it took care of the driver install for me". You might give that a shot.
At this point, what you should work on is getting your device driver installed correctly on the phone, and concentrate on that alone.
How will you know if it is working? First, you probably won't see any of those yellow exclamation marks inside the device manager on Windows. Second, you can run a test with adb itself to see if it is "talking" to the phone. From windows,
Start... Run... (type into box) CMD (and hit enter)
(this is an example of using the "cd" command to get to the tools folder)
Code:
C:\Big Long Path Including Your User Name> cd \
C:\> cd \Android-something-or-other\tools
C:\Android-something-or-other\tools> adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9AAAAnnnn device
That last line is what you are looking for - the adb program reports that it found a phone on the other end of the USB cable.
Let me know how it goes
eu1