Related
I rooted my phone on June 16, a couple weeks ago. I had to factory reset my phone. Everything on the phone and memory card was erased other than Superuser Permissions. Superuser Permissions still shows up on my home screen.
Because SU is still there, am I still rooted? If so what do I need to put back on my memory card for everything to work properly?
I can't get into ADB Shell anymore either, I've tried all day and nothing has helped. I guess I got really lucky.
If I'm still rooted, is there an easier way to get into ADB Shell? Also if I am still rooted, how exactly to I do a NAND? And by doing this, will it make it easier to get into ADB Shell?
I know these are probably basic questions for some, but I would really like a little help to get a step in the right direction. I really appreciate anyone's help and knowledge on this.
travazz said:
I rooted my phone on June 16, a couple weeks ago. I had to factory reset my phone. Everything on the phone and memory card was erased other than Superuser Permissions. Superuser Permissions still shows up on my home screen.
Because SU is still there, am I still rooted? If so what do I need to put back on my memory card for everything to work properly?
I can't get into ADB Shell anymore either, I've tried all day and nothing has helped. I guess I got really lucky.
If I'm still rooted, is there an easier way to get into ADB Shell? Also if I am still rooted, how exactly to I do a NAND? And by doing this, will it make it easier to get into ADB Shell?
I know these are probably basic questions for some, but I would really like a little help to get a step in the right direction. I really appreciate anyone's help and knowledge on this.
Click to expand...
Click to collapse
easiest way to know if you are still rooted is to download android terminal emulator from the market and type in su on the screen... if you get a # sign then you have root... if you get permission denied then you don't.
find that out first then we can answer the other questions.
Downloaded it, typed in su, Superuser Permissions came up on my phone, I allowed it. After I typed su, # showed up underneath it
travazz said:
Downloaded it, typed in su, Superuser Permissions came up on my phone, I allowed it. After I typed su, # showed up underneath it
Click to expand...
Click to collapse
You're in good shape. If you're looking to get into adb shell, you might as well go the whole nine yards and dl the recovery installer from unrevoked, it will install custom recovery and once you get that you can boot into the custom one and adb shell from there without having to do the SD card stuff over and over again.
viccyran said:
You're in good shape. If you're looking to get into adb shell, you might as well go the whole nine yards and dl the recovery installer from unrevoked, it will install custom recovery and once you get that you can boot into the custom one and adb shell from there without having to do the SD card stuff over and over again.
Click to expand...
Click to collapse
Where do I get the custom recovery file and how do I install it/use it?
Sorry that these are really dumb questions, but now that I know I still have root, this is getting exciting again.
See the stickied thread recovery reflash tool.
-------------------------------------
Sent via the XDA Tapatalk App
Now I'm trying to follow the recovery steps and I'm having the following errors. Can anyone please help?
When I try to install the modified USB drivers I receive the following errors:
Error 0x80004005: Unspecified error on these specific dll files.
WdfCoInstaller01007.dll
WUDFUpdate_01007.dll
WUDFUpdate_01007.dll
When I go to install the reflash-bundle, everything installs, but it fails installing the reflash.exe saying that the file is corrupt.
I'm using Windows 7 Ultimate x64, if that helps out
This is a development sub-forum. Please post your questions in the General section. Thanks.
So I got an EVO when they first came out and rooted/rom'd it, but the charging port broke and they junked it out and gave me a new one
I guess i didn't think about it before i did it, but i am finding out that having the hboot2.02 and trying to root it the old way has messed me up. I now can not seem to connect to it through adb or get the RUU to find the phone.
I am in the white skateboard screen with the Fastboot, Recovery, Clear Storage, Simlock, and HBOOT usb options. If i try and reboot it, it goes to the RED EXCLAMATION POINT/Triangle.
I never got a custom recovery installed before i screwed this up somehow. The PC36IMG failed on the radio_v2 and didnt partition.
Can I load the stock or anything for that matter from where i am now?
I know this has prob been covered, but i have been on here for 3 hours now trying to get this going again. Thanks
Try this....
It's late and I have to catch up on some sleep before work so I will be brief.... Rooting Hboot 2.02 can cause a lot of headaches. I am surprised the RUU did not find your phone.
My only advice is to read up on this thread http://forum.xda-developers.com/showthread.php?t=829045
It is by far the best and safest method to root your phone at this point and if you ask I bet someone can help there.
Check out the first post there is a special recovery file that might help.
Good luck.
I think if you try to find the thread that allows you to fastboot adb push a file into your system (file like amon_ra recovery and reboot into it), but if you don't have root, I'm stuck thinking like you too. :/
Yeah, it still says s-on, so i am assuming i didn't get rooted. This is so frustrating!
I have been trying to do the steps in the thread mentioned above, but no luck so far
IzzyIsaac said:
Yeah, it still says s-on, so i am assuming i didn't get rooted. This is so frustrating!
I have been trying to do the steps in the thread mentioned above, but no luck so far
Click to expand...
Click to collapse
So what do you see currently when you run your phone?
Is there anything conflicting it?
I see a picture of my EVO on a black screen with a red triangle and exclamation point.
I was able to do all these except for the flash image
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
adb push root/rageagainstthecage /data/local/tmp
It said "C:\hboot>adb push root/flash_image /data/local failed to copy 'root/flash_image' to '/data/local/': Is a directory
Then i tried getting into adb by typing 'adb shell' and got a no such file or directory
IzzyIsaac said:
I was able to do all these except for the flash image
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
adb push root/rageagainstthecage /data/local/tmp
It said "C:\hboot>adb push root/flash_image /data/local failed to copy 'root/flash_image' to '/data/local/': Is a directory
Then i tried getting into adb by typing 'adb shell' and got a no such file or directory
Click to expand...
Click to collapse
I'm no expert at android development, but honestly It looks like you've badly bricked your phone using the old root method I have no clue xD
http://forum.xda-developers.com/showthread.php?t=829045
do you think since it isn't rooted yet(s-on) they would exchange it out at best buy since i have the black tie protection or whatever?
I don't know but try to unroot LOL http://forum.xda-developers.com/showthread.php?p=7471721#post7471721
Well, i dunno from which site i got it because i have so many PC36IMG's now, but I was able to load one up on my SD card via my buddy's droidX and it went through smooth and i'm back to stock 2.2
I am not going to touch it right now as far as rooting it. I will save that for another day, soooo tired after 6 straight hours in this chair!
Thanks for the help!
IzzyIsaac said:
Well, i dunno from which site i got it because i have so many PC36IMG's now, but I was able to load one up on my SD card via my buddy's droidX and it went through smooth and i'm back to stock 2.2
I am not going to touch it right now as far as rooting it. I will save that for another day, soooo tired after 6 straight hours in this chair!
Thanks for the help!
Click to expand...
Click to collapse
Np, Glad your phone got unrooted back to normal. Maybe wait a few days and see how the forums turn up to find a better way to root it.
Well, i just didnt realize that there was a newer hboot and a different way to root if you have this one. I might try again here in another day or two like you said after i really read up some more. That sucked hard not having a phone for 6 hours and thinking i would have to get a new one!
Trying to use the http://forum.xda-developers.com/showthread.php?t=829045
Like a Boss Hboot 2.02 root but got the $ instead of # sign after i went into the shell and its telling me "You Should see a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over.." and at the beginning it tells me to "Make sure you have the drivers installed for your phone (recommend: SDK Drivers, unrevoked hboot drivers" but im not sure exactly what that means or how to do it, i thought i was doing alright but i dont think i have it all quite figured out, anyone know the next step i should take to keep from bricking this thing?
Nothin? I ran Unrevoked3 and put everything into the C:/android-sdk-windows folder so hopefully it put the right drivers in there, if im doing this entirely wrong someone say something please!
try typing SU then enter after the $ prompt, if that gives you the # prompt proceed, also be sure to run unrevoked forever to permantly unlock nand and get s-off, ok so i just also read a little more carefully, this method listed in your OP is not unrevoked3, maybe a little more info on exactly what you did would help.
ifly4vamerica said:
try typing SU then enter after the $ prompt, if that gives you the # prompt proceed, also be sure to run unrevoked forever to permantly unlock nand and get s-off
Click to expand...
Click to collapse
Permission denied on the SU im afraid to run the wrong unrevoked because of the damn HBoot 2.02 think itll be straight if i do it regardless?
its gotta be the drivers, what am i missing here? this is driving me nuts, i spent 3 hours earlier 2 of which were to turn it back into a phone, it was a brick...
ifly4vamerica said:
try typing SU then enter after the $ prompt, if that gives you the # prompt proceed, also be sure to run unrevoked forever to permantly unlock nand and get s-off, ok so i just also read a little more carefully, this method listed in your OP is not unrevoked3, maybe a little more info on exactly what you did would help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829045 Im using this guide and ive made it up to step 6, if i go to the device manager i have Android USB Devices and when its plugged in it says My HTC and down lower i have portable devices and its just named G:/ but when i tried to update the drivers it says theyre all up to date, any idea if i need to uninstall the ones i have and use a different set of drivers? like installing HTC Sync then uninstalling it? just not sure whats going on..
Not to sure on this one, what did it do when you typed SU? Also what version of hboot do you have, are you sure it is 2.02? if not just keep trying sometimes the exploit doesnt work the first time.
Yeah def. got 2.02 when i typed SU it said Permission Denied I believe its a problem with not having all the drivers on the computer itself, should i install HTC Sync then uninstall it to get its drivers at least?
you can try that for sure, you did use adb to push all of those files in the zip to your sd card right? or did you just drag and drop them?
Used the adb push method to the absolute T but didnt figure out the right drivers at the beginning so im starting over there, what does it mean by the Unrevoked HBoot drivers, i did the unrevoked3 install and that worked out fine but dont think thats what it meant.
So now the phones labeled differently in the device manager, im supposed to delete the actual HTC Sync program before i begin but leave the driver installer and everything right? and i have all the unrevoked folders and SDK ones together in the file i pushed from like it told me to so im going to try to update all those and make sure the drivers are all correct then start the command prompt over again, its in charge only and debug mode of course.
Any idea if the DIAG drivers have anything to do with it? http://forum.xda-developers.com/showthread.php?t=766374 as said in here where you have to actually pick them through the phone?
uhh i may of been retarded by not clicking the SDK Setup.exe file and running it.. wow... snuck that one right by me >_<
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Did you do "adb shell" and then you tried more adb commands and got "permission denied" ?
If so, then that's because "adb shell" starts a command prompt session on your phone, and the adb commands need to be run on your PC, not your phone. So don't do the "adb shell" first.
So wait a second, you're saying that the wonderful wiki, either is in the wrong order, or requires me to follow the pc, and phone steps simultaneously? Because im running them from my pc. Which would be implied by my saying im following the wiki. Fyi, i meant the one on the g2, involving rooting the g2, on the xda-dev site. I've done this before, i know how to use adb. this is the first time i have rooted a g2. Don't mean to sound like a ****, but you basically didnt read anything i wrote.
The Wiki isn't in the wrong order. But IMHO it's very confusing that it shows a $ prompt when it shows "adb push" etc, because that makes it looks like it is run on the phone. But it's assuming you're running from Linux/Mac. On a PC the prompt for your adb commands would be C:\ or similar.
The Wiki doesn't tell you to run "adb shell"
So the answer to my question was yes, it works, but i had to wait 5 minutes to post this. I dont understand why there cant be a note that, unless you put adb into your path, cmd isnt going to recognize it unless its in the folder you're using. I feel no need to put a tool that i will use maybe once a year at most into path. also, when i just checked the wiki now, i noticed how the dollar signs had changed to c:/ ha ha. and sorry about the rudeness, at first it just seemed like you were making fun of me.
jenlow said:
Okay, so before i opened the adb shell from cmd, when i would type adb push, i would get adb is not recognized as an internal or external command. so, my solution of putting the adb tools into gfree, should work now once i cd to the gfree folder?
Click to expand...
Click to collapse
That's an issue with your path not being setup properly on your PC. You can adb adb's folder to the path to mean you can run it from anywhere. Otherwise you need to put the gfree tools etc in the same folder as adb, then cd to there and run the commands.
Or if the path is setup properly, cd to where the gfree tools are and start doing your "adb push" etc from there.
I have just edited the Wiki to show a "C:\" prompt for the stuff that's run on the PC, to try and avoid this confusion.
Did it work ?
jenlow said:
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Click to expand...
Click to collapse
the "permission denied" thing... from the phone? Or from the computer? You know you need to be root in order to access the hardware, or at least set the permissions on the hardware to be accessible to your user account....???
And... you DID enable adb on the phone side, didn't you?
I used the Wiki and am now perm rooted. A few tips that may help you since they helped me to get it done. I opened a command prompt and noted the default path that opened. For me it was C:\Users\Ed . I used windows explorer to navigate there and open up the Ed folder and created a new folder in Ed that I named pr. This is where I unzipped both of the gfree zip files...into that same folder. When temp rooting and perm rooting, I simply opened up the command prompt, it opened to C:\Users\Ed and then I typed cd pr then I hit enter. That set me up to input the commands in the right place both times and it worked out just fine.
Another thing that I noticed. After temp rooting, I had to ctrl alt del to open up task manager and close down adb.exe (as noted in the instructions that appeared in terminal emulator). I couldn't load adb again until I closed it down and let it restart itself. When I entered the first command in the perm root process adb started up again by itself and all went well.
Good Luck! It is well worth it. I now have Cyanogen's latest stable build loaded along with the Google apps package that I found online.
Ed
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Root my phone!!! HELP
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
mannær said:
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
Click to expand...
Click to collapse
None of those apps work with the G2 to perm root without extra steps. And in that case only Visionary. You need to check out the vision wiki page.
Ed thoroughly described how to make it work. I did the exact same thing he did and got it last night.
jenlow said:
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Click to expand...
Click to collapse
What method did you use to root your cliq, and did you still have 3G? I have stock motoblur 2.1 on it now, I have it for a backup phone (got a G2), but I would like to root it.
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Arconaught said:
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Click to expand...
Click to collapse
Having the SuperUser icon just means the app is installed, open up terminal and type 'su' to see if it throws up any errors
Sent from my HTC Vision using XDA App
I should have mentioned that I did that and got the # symbol, am I good to go?
Arconaught said:
I should have mentioned that I did that and got the # symbol, am I good to go?
Click to expand...
Click to collapse
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Click to expand...
Click to collapse
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
redpoint73 said:
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
Click to expand...
Click to collapse
This is my understanding as well, though I'd probably still use GFREE to get S-OFF if I were OP.
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
I used the wiki method myself, those that used other methods (like Visionary) and were told to root via the wiki seem to have all just started at the beginning, from what I've read.
Sent from my HTC Vision using XDA App
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
Whoa the Wiki method is completely different, looks like it was rewritten on 04/01.
You can completely ignore the temp rooting steps and concentrate on the gfree steps
From the "Necessary Files" section you need gfree, flash_image and ClockWorkMod Recovery
I would use the latest ClockWorkMod recovery rather than the one listed on the Wiki:
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img (of course it's only the latest as of the time of this writing)
From step 2 you need to use:
Code:
$ adb push gfree /data/local/tmp/
$ adb push flash_image /data/local/tmp/
From step 2.a you need to use:
Code:
$ adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
Again note that the file name for CWM will depend on the version of CWM you are using.
Skip to step 4.b you need to use:
Code:
# cd /data/local/tmp
# ./gfree -f
# ./flash_image recovery recovery.img
# sync
Continue on as normal from here.
I skipped the temp root and perm root sections as you are already perm root.
I also skipped the ENG HBOOT parts, since that's not strictly necessary and the most risky part of the whole process (one mistake can result in a brick). If you want to flash the ENG HBOOT you would need to follow steps 4.a instead of 4.b, (you would also need the necessary HBOOT of course) the only command you need to omit from 4.a or 4.b is "# ./root_psn" which is the script which establishes permanent root.
Thanks a lot so far man, but I'm still stuck. I have adb, when I open it in the SDK, it flows for a bit, then closes. This is right, right? I'm meant to do all of these prompts via the cmd window?
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Arconaught said:
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Click to expand...
Click to collapse
You say you've sorted adb, but can you be more specific please ? What works and what doesn't work exactly ?
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
There is a great write up here about getting adb working. It sounds like either you didn't set up a "path" to use those commands anywhere or if you don't want to do that make sure your files are in the same folder as your adb.
Sent from my HTC Vision using XDA App
Arconaught said:
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
Click to expand...
Click to collapse
You need to have the files (extracted from the ZIP files you downloaded) in the same folder you run the ADB commands, if your ADB is in your path you should be able to run ADB commands from any folder.
To summarize you need to extract all the zips you downloaded under necessary files, all to the same folder. The open a command prompt and CD to that folder before you start using your adb push commands.
shortlived said:
There is a great write up here about getting adb working.
Click to expand...
Click to collapse
Yeah, steviewevie wrote it:
http://forum.xda-developers.com/showthread.php?t=865685
But it looks like he is willing to give the OP some personalized help.
Right, thanks guys, I think I'm making some progress.
ADB is all set up, and as far as I'm aware, having:
program files > android sdk > platform tools
on my path should mean I can open adb from anywhere right? I have all of the extracted files in platform tools, where adb is, in my program files... is this right, or have I completely missed the point here?
I keep getting "cannot stat 'gfree':: No such file or directory"
Sorry, I seem really stupid concerning this whole thing, but I'm sure it's something equally obvious that I'm just not seeing.
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Arconaught said:
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Click to expand...
Click to collapse
Remember you are running those commands (everything in that section) from an ADB shell, not from the Windows command prompt.
Excuse my ignorance, but what exactly do you mean by that? What should I do?