Develop Bugs

Why "Read-only file system" message?

this is in regards to http://forum.xda-developers.com/showthread.php?t=754020
I'm ready to kick myself, it worked for everyone else, but here is what i get:
C:\and_sdk\tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i have tried - remount command and it didn't do a thing.
please help!

dialbat said:
this is in regards to http://forum.xda-developers.com/showthread.php?t=754020
I'm ready to kick myself, it worked for everyone else, but here is what i get:
C:\and_sdk\tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i have tried - remount command and it didn't do a thing.
please help!
Click to expand...
Click to collapse
You're in recovery mode right? I rooted before the tmobile update so I used the original method not the one you're using. I assume that for the most part you need to have your phone in recovery mode.
The /system/ directory is read only unless you're in recovery and I believe that's were that method attempts to write. You usually only get that message when you attempt to write to the system when not in recovery.

Thank you, but there is not a single word about puting phone into recovery mode in the instructions. Unless they mean it my default
i will try though.

Yeah, some steps are left out in certain 'common' tasks like rooting. It's assumed to be common knowledge or that if you don't know to automatically do a step then maybe you shouldn't be attempting it. At least that's the feeling I get sometimes but that's why it's important to search and ask if you don't find the answer.

Recovery mode is not necessary, nor possible at this point. The phone just needs to be on and connected with adb. No steps are left out (I've used this method), you just need to make sure you follow every step exactly.
Sent from my T-Mobile myTouch 3G Slide using XDA App

If it's under/system, you need to be in recovery. I rooted with the original method though, so I can't really tell you much.

guitarist5122 said:
Recovery mode is not necessary, nor possible at this point. The phone just needs to be on and connected with adb. No steps are left out (I've used this method), you just need to make sure you follow every step exactly.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You're kidding about recovery mode right? I really hope so or that you stated that wrong... wow...
In order to write to ./system on the mytouch 3g slide you HAVE to be in recovery. Not saying this method has to be in recovery or not because I never used it. Just thought I'd throw out the suggestion to try it just in case it needs to be.

Well, i've followed steps to the point. I have rooted my phone before, so even though i am a newbe, i do have a general idea of the process.
But i have no idea why it just won't work for me.
I have tried putting it into recovery using loop script, otherwise it just states that it's in recovery and still won't let me write to it

KCRic said:
You're kidding about recovery mode right? I really hope so or that you stated that wrong... wow...
In order to write to ./system on the mytouch 3g slide you HAVE to be in recovery. Not saying this method has to be in recovery or not because I never used it. Just thought I'd throw out the suggestion to try it just in case it needs to be.
Click to expand...
Click to collapse
Why would I be kidding? It isn't necessary to be in recovery to push files to /system. I know since I've rooted my phone twice from a fully booted state (which is necessary to toggle the wifi).
Sent from my T-Mobile myTouch 3G Slide using XDA App

guitarist5122 said:
Why would I be kidding? It isn't necessary to be in recovery to push files to /system. I know since I've rooted my phone twice from a fully booted state (which is necessary to toggle the wifi).
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Hmm... Allow me to copy and paste a few lines from that thread, written by the developer:
1:After many long hours of trying to restore my phone, I have now ported the exploid exploit to the MyTouch Slide! This means that you can gain root on any version of the Slide, INCLUDING the latest OTA! However, this isn't necessarily "easy" as in the One-Click Root program, but there are reasons for this. While Android is running we cannot write to /system and even if we force Linux to let us, the NAND protection will prevent Linux from completing the write!
2:Important: If you do nothing after step 12 then you are not "rooted." This program grants itself root permissions in a shell, that is ALL. If you want system-wide root access (what most people consider "rooted"), you MUST flash a custom ROM since the NAND protection on our device prevents us from giving global root access while inside the ROM. When following Eugene's instructions on flashing ENG, make note to NOT run the command 'su' if you already have a pound symbol (#) at your command prompt!
Basically, this 'root' method is actually a program that allows you to flash the ENG package to give you root. By itself, the program does nothing but allow you to operate inside the shell as root for a short time. Sort of like the 'sudo' command in linux - at least from what I can tell.

I'm aware of what the developer said. I'm also aware that I disregarded not having the phone booted since it would be a little tough to toggle wifi without being booted. If you don't believe it can be done, do a nandroid backup and unroot your phone and try rerooting. Pushing exploid and do the root whole process before flashing the eng-build while booted. Or just take my word. Personally I figure out for the life of me how anyone toggles the wifi (which is one of the steps) if not fully booted.
I don't argue just to be right. I just don't want people to be given incorrect info and never solve their problem. Rooting and can be frustrating on this phone if your not too familiar with rooting or using command prompt.
Sent from my T-Mobile myTouch 3G Slide using XDA App

I wan't saying the files can't be pushed while it's on, I've done that before but NAND will undo or not complete it once you reboot. It's the same reason that you can't delete a system app while the slide is booted - well you can but it will still be there, and once you reboot the delete is undone - unless you're in recovery.
All I was saying is that it's not a permanent write to the system, if that's where it's even being pushed and he still has to flash the ENG build to gain full root. I think this guy needs to just redo the steps, maybe read the old root methods to gain some insight too. It might help.
btw, I think there actually is a command to toggle wifi through adb, not sure if it does much in recovery or not. Also, not a chance in hell am I going to unroot - it was a pain in the a** catching my phone in recovery even when I used the loop.bat file

Good to know that's why my apps didn't stay deleted.
Sent from my T-Mobile myTouch 3G Slide using XDA App

I came across this thread while trying to understand why my rooted phone won't let me pull or rm from a terminal emulator. The way I rooted my phone was by flashing an update in recovery. Does anyone know of a file that would unroot by using the same method in recovery?

Thainfamous20v said:
I came across this thread while trying to understand why my rooted phone won't let me pull or rm from a terminal emulator. The way I rooted my phone was by flashing an update in recovery. Does anyone know of a file that would unroot by using the same method in recovery?
Click to expand...
Click to collapse
rm, rm -f or any other commmands will not work with terminal emulator because in order to use that program you phone has to be on, and since we can only write to the /system in recovery I'm sure you see what I'm getting at. You can still pull from the /system when the phone is on. The command isn't 'pull' though, it's:
Code:
cp <path to file> <location to copy to>
As far as the unroot thing, use the search bar [slide rom bible].

just found this thread while looking for a solution to the OP's problem (same as my own).
If my phone is ON, usb debugging ON, Charge Only, i cannot push exploid to /sqlite_stmt_journals.
this is what i did:
C:\android-sdk-windows\platform-tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i tried to follow the directions as closely as possible. can someone please tell me where i'm going wrong here?

PunkRockJesus said:
just found this thread while looking for a solution to the OP's problem (same as my own).
If my phone is ON, usb debugging ON, Charge Only, i cannot push exploid to /sqlite_stmt_journals.
this is what i did:
C:\android-sdk-windows\platform-tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i tried to follow the directions as closely as possible. can someone please tell me where i'm going wrong here?
Click to expand...
Click to collapse
Its been so long since i used that method and rooted i cant quite recall. But it does look like you need to change the path to c:/android-sdk-windows/platform-tools
Command prompt is picky about using / or \
Sent from my T-Mobile myTouch 3G Slide using XDA App

guitarist5122 said:
Its been so long since i used that method and rooted i cant quite recall. But it does look like you need to change the path to c:/android-sdk-windows/platform-tools
Command prompt is picky about using / or \
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
No, windows uses \ for local and local network file paths, it only uses / for remote locations and networks.
I'm not sure if this would work without already having root (I received my phone already rooted, never had to do it)
In command prompt, try
adb remount
You can also try this:
adb shell mount -o rw,remount /sqlite_stmt_journals
See if any of those work. Like I said, it may not, since those might be things that need root.

Any updates on this? I cannot push the file either. And "adb shell mount -o rw,remount /sqlite_stmt_journals" does nothing.

cant root this one for the life of me

This is the 5th g2 tmobile has sent me. Been having build quality issues. Anyways, I was able to root them all without any problems. But this one is a toughie. I got s off. But the latest visionary won't temp root for me after I push wpthisOTA n the hboot.img.
Even removing visionary and resetting the phone n trying gfree n rage hasn't helped. Any advice?
I have the superuser app but no su rights at all. I discovered this cuz rom manager tells me I'm not rooted hence can't flash cwr

try using the rage method instead of visionary

tazz9690 said:
try using the rage method instead of visionary
Click to expand...
Click to collapse
I tried to rage temproot then perm. But no dice

I'm helping someone with their phone that has the same problem.
What we're going to do tomorrow is downgrade the rom using this...
http://forum.xda-developers.com/showthread.php?t=831398
then redo the root with rage.
I think the problem occurs when you use visionary to root then try rage. The person I'm helping keeps having problems after code # /data/local/tmp/root, so I'll report back tomorrow.

Don't use the eng hboot. That's not necessary any more, and is quite risky (e.g. if it goes wrong your phone will be bricked).
To get S-OFF after rooting, use this - http://forum.xda-developers.com/showthread.php?t=855764
With the rage method to get root, I believe that works 100% every time, *if* you follow the instructions very carefully and look out for error messages that indicate something has gone wrong. When rage "doesn't work", it's because the instructions haven't been followed or an error message cropped up and the user didn't notice and just carried on.

I'm going to return the phone to stock hboot and wipe it. Ill try rage next
Thnx for the help... this hexeditor crap makes me nervous lol

When I try to unroot it won't creat the darn misc file....
Any ideas what I can do? My s=off but rage method n visionary aren't woorking...

sheek360 said:
I'm going to return the phone to stock hboot and wipe it. Ill try rage next
Thnx for the help... this hexeditor crap makes me nervous lol
Click to expand...
Click to collapse
Gfree does all the hex editing for you and even backs up your origonal first! Very safe way to do it.
Sent from my HTC Vision using XDA App

ok, as soon as i run
/data/local/tmp/root
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
any ideas guys?

ddgarcia05 said:
I'm helping someone with their phone that has the same problem.
What we're going to do tomorrow is downgrade the rom using this...
http://forum.xda-developers.com/showthread.php?t=831398
then redo the root with rage.
I think the problem occurs when you use visionary to root then try rage. The person I'm helping keeps having problems after code # /data/local/tmp/root, so I'll report back tomorrow.
Click to expand...
Click to collapse
That's not an option for me.
I can't #su @all =(

sheek360 said:
ok, as soon as i run
/data/local/tmp/root
i get a failed message
killall: rage: no process killed
mkdir failed for /system/xbin, file exists
cp: cant stat /system/xbin/busybox : not a directory
unable to chmod " "
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
unable to chmod /system/bin/su: no such file or directory
#
?
Click to expand...
Click to collapse
Did you reboot the phone after doing the temp root steps of rage ? Because that's kinda how it looks there.
You are also missing busybox, and an "adb push" for busybox is one of the steps in the temp root part of rage.
Also, when you did the "insmod" command, what error message did it come up with ? This is critical. It must come up with the error message shown in the procedure, if it comes up with a different error message then it hasn't worked.

steviewevie said:
Did you reboot the phone after doing the temp root steps of rage ? Because that's kinda how it looks there.
You are also missing busybox, and an "adb push" for busybox is one of the steps in the temp root part of rage.
Also, when you did the "insmod" command, what error message did it come up with ? This is critical. It must come up with the error message shown in the procedure, if it comes up with a different error message then it hasn't worked.
Click to expand...
Click to collapse
Came up with a diff error message....
Before rage I pushed wpthisOTA n the eng build. Then using visionary I tried to get perm root.
I think by using visionary I f'd up my chances of rooting. I assumed the root procedure didn't change. O well. Doesn't really matter. My camera is now taking pics backwords. Tmobile is swapping my g2 for another lol

[Q] I'm having a problem perma rooting

I can't find a solution to this from searching the forums so i'm just gonna ask.
I'm using the gfree method via adb. i'm getting all the way through it without any problems untill i get to the "lock in" root section.
I get the error message that the wiki says should get and then ignore, but i also get another message that says something like
"cp: can't stat '/sdcard/su' : no such file or directory"
any help with this would be appreciated.
also, are all the bad things i've heard about visionary true? should i go ahead and root with visionary, or keep trying this way? thanks

I just checked and it says I'm s-off. I'm very confused.
Sent from my T-Mobile G2 using XDA App

Well first ill tell u Visionary worked for me in like 10 minutes time. Very easy n very fast. Not true what they say. If u got s-off, good. Ur almost there. Have to check out gfree method quik in order to help u. Hold up
G2 with ExtraHotSauce v0.2!!

What guide are you using, the one on the Wiki doesn't have you copy (cp) anything.
is this the command where you run into the problem?
/data/local/tmp/root
Click to expand...
Click to collapse
This is running a script to lock in root, you already ran gfree while you were temp rooted so that's why you are S-OFF.
Do you have the "su" file on the root of your SD card?
You should be able to retry everything but the gfree part.
As for Visionary, some people report success but other have reported big problems. I found the gfree method to work pretty well, even though I used Visionary when I was temp-rooting (when I just got my phone) when I permarooted I used the gfree method.

raitchison said:
What guide are you using, the one on the Wiki doesn't have you copy (cp) anything.
is this the command where you run into the problem?
This is running a script to lock in root, you already ran gfree while you were temp rooted so that's why you are S-OFF.
Do you have the "su" file on the root of your SD card?
You should be able to retry everything but the gfree part.
As for Visionary, some people report success but other have reported big problems. I found the gfree method to work pretty well, even though I used Visionary when I was temp-rooting (when I just got my phone) when I permarooted I used the gfree method.
Click to expand...
Click to collapse
yes, that is the command that is giving me problems. i checked my sd card and superuser.apk is at the root of it.
when you say retry everything what exactly would i retry? i'm at work, and don't have access to adb. do i need adb to "retry"

so, there are two different guides that perm root. the first is the wiki and this is the one that i was following. the other has almost the exact same steps except it has the wpthis file. i guess when i get home i'll try the other method and see if it works. thanks for everone's help

no its a 2 step procedure maybe you should go ahead and unroot and s-on then go ahead and re root. if not you can still re run everything start off with temp root then go ahead and lock in the perma root

thenaut said:
yes, that is the command that is giving me problems. i checked my sd card and superuser.apk is at the root of it.
when you say retry everything what exactly would i retry? i'm at work, and don't have access to adb. do i need adb to "retry"
Click to expand...
Click to collapse
You should have both Superuser.apk and su on the root of your SD card. Either push it from your computer again (first command in the wiki):
Code:
adb push su /sdcard/su
Or just copy it to your SD card (be sure to unmount the card when done). Then re-run the root script in terminal.

that totally did it. I pushed the su file and re ran the script and i got root. it's wierd because i thought i pushed it the first time but i guess not. anyway, thanks

problem getting perm root

im using the rage method and everything worked up until after i used the command gfree - f.
then i input the command sync followed by /data/local/tmp/root, this is what i get
# /data/local/tmp/root
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
mkdir failed for /system/xbin, File exists
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
Unable to chmod /system/xbin/busybox: No such file or directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#

if I were you, you should use gfree method... or unfrogivens way
Sent from my HTC Vision using XDA Premium App

I used rage to get temp root, and using gfree but during the last execution, it doesn't work and that's the message I get back
Sent from my T-Mobile G2 using XDA App

This problem sounds familiar, let me look at previous threads I have participated in and see if I can find anything useful
FYI, /data/local/tmp/root is a script that copies busybox and does other root functions.
I'm guessing that the gfree part did work, you can verify this by rebooting into the bootloader and seeing if you have S-OFF
If you are only looking to flash a custom ROM you don't even need to worry about this issue (as long as you do have S-OFF), all you'd need to do is obtain temp root again (using rage or even visionary) then install ClockWorkMod Recovery (I'd recommend using this method), once you have that you can boot into recovery and flash any pre-rooted ROM you want.
Eidt: I found the post I was thinking of, seems like this guy had a similar problem running /data/local/tmp/root
http://forum.xda-developers.com/showthread.php?p=11215689#post11215689
My advice still stands, if you have S-OFF and can get CWM flashed onto your phone (should be able to with temp root) you can flash a custom ROM (which will be pre-rooted) or flash a pre-rooted stock ROM (see this thread)

Hey there,
today I tried to get perma root and followed the guide from cyanogenmod
everything runs great till step 5 in Gaining Permanent Root Access & More
when I enter:
/data/local/tmp/root
I receive the message like nguyenhoanggg described..
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
mkdir failed for /system/xbin, File exists
link_image[1995]: failed to link /data/local/tmp/busybox
CANNOT LINK EXECUTABLE
Unable to chmod /system/xbin/busybox: No such file or directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
for sure plan was to install cyanogenmod but I even want permaroot :/
thanks for any help

this was the similar problem when i rooted my desire Z
just ignore it and install clockworks recovery
your phone should actually be rooted by then~
but make sure before you do gfree command, you have already pushed all the other files into the proper location, IE busybox, SU and root
Good Luck~

I seem to be having a simmilar problem using the rage method. I can transfer everything through adb on my pc. But when i run the /data/local/tmp/rage it completes the action but after reseting the terminal and force closing the first time it will not open the second time. Any advice??

Thanks for answer,
when I have temproot and try to install clockworks it says no root-access using google search to find out how to get permaroot...

I was having same issue and realized that busybox's md5 from cyanogenmod wiki wasn't the same as the one it says. I downloaded the busybox file from this guide. Busybox is in gfree_temp-root.zip file.

Fibriso said:
Thanks for answer,
when I have temproot and try to install clockworks it says no root-access using google search to find out how to get permaroot...
Click to expand...
Click to collapse
What method are you using to install CWM? I suspect that ROM Manager will fail if ou only have temp root but I would expect that the flash_image method will work.

Do you have a guide or a good explaination for the flash_image method you talked about?

sacarino2k2 said:
I was having same issue and realized that busybox's md5 from cyanogenmod wiki wasn't the same as the one it says. I downloaded the busybox file from this guide. Busybox is in gfree_temp-root.zip file.
Click to expand...
Click to collapse
just want to bump / confirm that this worked for me. the gfree_temp-root.zip download from that link worked for me. note the underscore vs. dash from the link off the wiki.
as far as i can tell the problem was with the file named 'root' pointing to to some wrong paths but i couldnt see a difference in between the 2 in a text editor.
i'm now happily running cyanogen 6 on my HTC vision / g2 using the directions off http://wiki.cyanogenmod.com with the other root.zip file

Try again
Sent from my HTC Vision using XDA App

okay, i had this problem this morning trying to root my g2 and i got the same problem. i did get it to work after a couple of hours of trying 2 figure out why it wouldnt give me perm root.
the steps posted on the cyanogen wiki are correct. the only thing that you need to do is download the 02 version of gfree instead of the 04 version, and also download a different busybox (i think thats what i did).
i think i got the different busybox file from here.
you can just start off at the steps where it deals with pushing gfree to your phone. also, just push the gfree file (not the .cpp or whatever type it was that has a bunch of code in it. all you need 2 push is that one single file from that zipped file.
if you did it right, it will just print out one line with the failure regarding the 'file already exists' thingas stated in the cm wiki.

hierophanta said:
just want to bump / confirm that this worked for me. the gfree_temp-root.zip download from that link worked for me. note the underscore vs. dash from the link off the wiki.
as far as i can tell the problem was with the file named 'root' pointing to to some wrong paths but i couldnt see a difference in between the 2 in a text editor.
i'm now happily running cyanogen 6 on my HTC vision / g2 using the directions off http://wiki.cyanogenmod.com with the other root.zip file
Click to expand...
Click to collapse
The problem isn't in the root script. It is in busybox file. It doesn't work for some vision systems. Looks like compatibility compilation issues. So if you get errors running the root script use the busybox binary i posted before.

Fibriso said:
Do you have a guide or a good explaination for the flash_image method you talked about?
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/showthread.php?t=902493

Just to touch base on this, it is related to the busybox binary on the CM wiki.
We've gone ahead and replaced the 'bad' one about 3 hours ago from this post.
Thanks for all of you who lets us know about the compatibility issues

[Q] Rooting problems - Please help!

Hello everyone,
I've had my LG Nitro HD for about a year and a half. I've recently been disappointed with it's performance and battery live. I read rooting and adding a new rom really helps free up the phone's natural performance. I've unlocked a few phones in the past. This one seems to be giving me a lot of fits.
I downloaded a zip file called 'P930_v20e_ROOT". I do not want to share any external linking as it's usually frowned upon. Nevertheless I unzipped the folder and copied the file "LG_SystemBackupTest" to the root of my sd card. I downloaded a file manager app to execute the file. Once installed I enabled the option for unverified sources, and the option for USB under development mode. I also installed the OEM LG driver off of their website for the P930 model phone. I then ran the LG_SystemBackupTest file that was in my applications. While it ran it simply states "hello world". I powered off/restarted the phone as instructed.
Once the phone booted up I plugged in the usb cable to my Windows 8 PC. I then ran the "root_p880" file. Below is the error I get repeatedly.
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permissio
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: cannot create /data/local.prop: Permission denied
AGAIN REBOOT
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
/system/bin/sh: cannot create /system/xbin/busybox: Read-only file syste
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
/system/bin/sh: busybox: not found
/system/bin/sh: busybox: not found
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
I've tried every possible combination I can think of. I even booted up one of my old Windows XP machines, performed all the steps above, and still the same. Just now I finally reset the phone to it's factory defaults. Only to get the same results. Can anyone provide any guidance?
Kind regards,
Jeremy

Just getting root isn't going to allow you to flash a new or custom rom. You need to install cwm using the P930 unbricking guide.

Re: Rooting problems - Please help!
audit13 said:
Just getting root isn't going to allow you to flash a new or custom rom. You need to install cwm using the P930 unbricking guide.
Click to expand...
Click to collapse
Thank you for the prompt reply. I do have another guide I was following to install a custom rom. However it states I first need to root. It provided no instructions and stated to google how to do it.

LilLowEK said:
Thank you for the prompt reply. I do have another guide I was following to install a custom rom. However it states I first need to root. It provided no instructions and stated to google how to do it.
Click to expand...
Click to collapse
Did you try both guides in this forum? I believe this is the guide I used: http://forum.xda-developers.com/showthread.php?t=1784709
You need to brick the phone, revive it, root, and install cwm.

audit13 said:
Did you try both guides in this forum? I believe this is the guide I used: http://forum.xda-developers.com/showthread.php?t=1784709
You need to brick the phone, revive it, root, and install cwm.
Click to expand...
Click to collapse
Thanks. I didn't use that guide. I'll read through it. It sound kind of odd that I first need to brick the phone just to un-brick it. If anyone else has any experience or used a different guide please feel free to share.
Best,
Jeremy

LilLowEK said:
Thanks. I didn't use that guide. I'll read through it. It sound kind of odd that I first need to brick the phone just to un-brick it. If anyone else has any experience or used a different guide please feel free to share.
Best,
Jeremy
Click to expand...
Click to collapse
What room are you using? You need to unlock the boot loader and this needs gingerbread, not ICS. This is the guide I have used on two different phones.

audit13 said:
What room are you using? You need to unlock the boot loader and this needs gingerbread, not ICS. This is the guide I have used on two different phones.
Click to expand...
Click to collapse
Thanks. I sent you a PM with some details on what I was using.

Re: Rooting problems - Please help!
audit13 said:
What room are you using? You need to unlock the boot loader and this needs gingerbread, not ICS. This is the guide I have used on two different phones.
Click to expand...
Click to collapse
LilLowEK said:
Thanks. I sent you a PM with some details on what I was using.
Click to expand...
Click to collapse
Problem seems to be solved. I rooted the phone with the help of the following thread.
http://forum.xda-developers.com/showthread.php?t=1886460
Thanks everyone! Now off to hopefully get a rom installed.