I don't know what's going on, and I've been searching for an answer to this for the past 2 hours. I have the latest SDK installed. I'm running the cm7 alpha build, latest one. ADB seems to work just fine. I just typed
adb reboot bootloader
bam, my mt4g is in fastboot mode.
I then typed
fastboot flash splash1 splash.img
and fastboot is not a recognized internal or external command, operable or batch file.
Seriously getting frustrated. I'm gonna smoke a bowl and come back a little more calm. lol
http://dl.dropbox.com/u/11228290/fastboot
Put that in c:\windows\system32
then try your command again.
And then ship the bowl this way.
I'm about to try this. If it works I'm gonna kiss you. Its been hell and a half trying to find this answer. lol
Sent from my HTC Glacier using XDA App
No go. Still the same error.
Sent from my HTC Glacier using XDA App
/b/rotherJudas said:
No go. Still the same error.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
oh. My bad, thats the linux version. You need the windows version. I have a .bat for that.
Just run the file called adbonly.bat
and feel free to look through the file if you get scared that it asks for admin rights. Just needs to be elevated to write to system32. Then you can run your command from anywhere.
I actually made this as part of a seperate project, but it comes in handy if you need adb and fastboot quick and convenient like.
I finally figured this out. When the sdk updated (changing ADBs location from \sdk\tools\ to \sdk\platform-tools\ it didn't move fastboot.exe or any other files. All I had to do was cut all the files from \tools\ and paste to \platform-tools\
Hopefully this wont cause more problems down the line, which it ALWAYS does with winblows. Lol.
Sent from my HTC Glacier using XDA App
/b/rotherJudas said:
I finally figured this out. When the sdk updated (changing ADBs location from \sdk\tools\ to \sdk\platform-tools\ it didn't move fastboot.exe or any other files. All I had to do was cut all the files from \tools\ to \platform-tools\
Hopefully this wont cause more problems down the line, which it ALWAYS does with winblows. Lol.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yeah that happens. But I swear my .bat would have worked too. lol.
I'm sure it would have. After running your cm7 rom I have total faith. I just didn't want to edit too many system folders on this craptop. Its my 4 year old sisters. Lol.
Sent from my HTC Glacier using XDA App
Thank you so much. I spent an hour last night trying to get clockwork on my friends MT4G and had the same problem.
Looked at my comp when I read this post this morning and that was it, fastboot was still in the old tools folder.
Don't you love how "correcting" our state of mind can change how we see things.
Thanks again.
Sent from my HERO200 using XDA App
pdug said:
Thank you so much. I spent an hour last night trying to get clockwork on my friends MT4G and had the same problem.
Looked at my comp when I read this post this morning and that was it, fastboot was still in the old tools folder.
Don't you love how "correcting" our state of mind can change how we see things.
Thanks again.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Yeah, lol. I knew it would be something stupid like that. I'm not sure if my environmental variable was set up wrong or what. I have it set to C:\AndroidzSDK\
Should I set it to C:\AndroidSDK\tools\
Or maybe
C:\AndroidSDK\platform-tools\
?
Sent from my HTC Glacier using XDA App
Please post questions in Q&A section.
So I'm just now installing the SDK on my gf's computer and it puts ADB in /tools and Fastboot in /platform-tools. Fastboot refuses to run.
Code:
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.
What's this about?? I downloaded the sdk.zip (the installer exe wanted me to install the java jdk, which I definitely don't need) and extracted it to C:\android-sdk-windows. Then I ran the SDK manager and installed the platform tools. Should I copy the platform-tools contents into tools or the other way around?
And why would they give me an SDK with a non-working fastboot? Kinda pissed right now...
EDIT - Copied contents of \platform-tools into \tools (DID NOT REPLACE ANY FILES!) and now everything works.
I would still like to know what was going on with this, and is there any advantage to adding the environment variable? I'd like to be able to run commands from any directory if possible, instead of having to cd all over the place.
Related
Long story short is that yesterday I rooted my HTC Glacier and everything seemed to work fine. I was able to obtain admin privileges by opening a Android terminal and typing "su". Today after deleting a few files from my phone which I thought were junk (face palm) I go into terminal to check if the "su" command still works and I get the message "link_image[1995]: failed to link su CANNOT LINK EXECUTABLE".
I've checked and my s=off is still in place so it's not that that's causing the error message. I'm new to Android so I'm stumped as to what steps to take next in order to regain my admin privileges.
Thanks for any and all advice XDA Community.
Cheers!
Lazerfingers said:
Long story short is that yesterday I rooted my HTC Glacier and everything seemed to work fine. I was able to obtain admin privileges by opening a Android terminal and typing "su". Today after deleting a few files from my phone which I thought were junk (face palm) I go into terminal to check if the "su" command still works and I get the message "link_image[1995]: failed to link su CANNOT LINK EXECUTABLE".
I've checked and my s=off is still in place so it's not that that's causing the error message. I'm new to Android so I'm stumped as to what steps to take next in order to regain my admin privileges.
Thanks for any and all advice XDA Community.
Cheers!
Click to expand...
Click to collapse
Try re-running visionary. It won't hurt anything and it installs su, busybox, and superuser.apk when you run it. It won't mess up anything you already have installed and it might fix your problem.
Also, I'm sure Whosdaman will tell you and move the thread when he sees this but make sure you post questions in the Q&A section.
Ran Visionary and no dice. Thanks for the tip though and sorry for posting in the wrong forum.
Any other ideas?
Try going into xbin (cd /system/xbin) and typing ls and see if su is in there. If it is you could try running rom manager and "fix permissions" if it will let you.
Good deal. I'm actually out fixing someone else's desktop computer at the moment. I'll attempt your advice later tonight.
Thanks again.
Sent from my HTC Glacier using XDA App
Ok, had a free moment and was able to run ls, su was there but unfortunately I wasn't allowed the super user access needed to fix permissions.
Sent from my HTC Glacier using XDA App
Please post questions in Q&A section.
1. Go into settings-applications-manage applications and try clearing superusers cache/data. See where that takes you.
2. If that did not work - isntall a fresh copy of superuser app from the market and once more see where that takes you.
Sorry about that. All future posts of these sorts I'll be sure to put there.
Sent from my HTC Glacier using XDA App
Tried both of your tips but unfortunately am still getting the same error when I run the "su" command.
Any other thoughts?
Sent from my HTC Glacier using XDA App
Update: Superuser automatically downloaded a new binary and told me to unzip it in recover mode.
I went into recover move and attempted to unzip the binary and was greeted with an error message that said the file couldn't be unzipped because it was "bad".
Sent from my HTC Glacier using XDA App
Can you get su in adb?
The more I think about it, You're s-off so you can fastboot new recovery image and then flash new rom with all the goodies preinstalled. May be the easiest route.
To be honest I've had my pocket computer for all of a week, so I'v still not had a chance to play around with adb.
The whole reason I rooted in the first place was so that I could flash custom roms. You think I'll be able to flash even though "su" privileges don't seem to be working properly in my current rom?
Sent from my HTC Glacier using XDA App
Update: It's clear from reading around these forums that the way to get to know your phone and thus be able to fix it is via adb. So I'm installing the Android SDK now. Thanks for all of your help Borodin1 and Grankin01
Idk if its because im using android terminal emulator and not the regular one"wouldnt open kept force closing" but when I root using visionary 11 and atu, when I input last code "sh root.sh" it roots my phone but everytime I power down to check if the s is off it is still on.. Ive master reset and everything. Since I got the phone two days ago should I return for a new one and try to root that one??? Is there something im doing wrong.. Usb debugging on, fast boot off, on visionary last option checked.. Somebody...anybody.. Please help
Sent from my HTC Glacier using XDA App
Does usb debugging have to be on with that method?
Sent from my HTC Glacier using XDA App
yes turn debugging on and turn off fast boot
jstew6260 said:
Idk if its because im using android terminal emulator and not the regular one"wouldnt open kept force closing" but when I root using visionary 11 and atu, when I input last code "sh root.sh" it roots my phone but everytime I power down to check if the s is off it is still on.. Ive master reset and everything. Since I got the phone two days ago should I return for a new one and try to root that one??? Is there something im doing wrong.. Usb debugging on, fast boot off, on visionary last option checked.. Somebody...anybody.. Please help
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Are you 100% sure that you have it extracted and set up as sdcard/root/root.sh
I've seen a lot of people not pull the folder out and it it'll be set up such as sdcard/root/root/root.sh
Yea ive extracted root from androzip.. Im sure because the first time I did it but didnt extract the root file the root didnt go through from term emulator.. Error message like cant find root file
Sent from my HTC Glacier using XDA App
I'm having this exact problem with my t-mobile replacement I just got.and its not me because I re rooted my bad phone with the same files and method and works fine... I'm very worried that htc or google may have locked us out... Please help guys I need to send my old phone I'm on now back and want to sort this out first... Mine haas dust under the screen.... In h-boot the info is identical to my old phone only difference is the part number on the phone. I'm very worried!
Also my replacement came with 2.2.1 from the box if that helps.I have pulled the battery and retried several times and no luck at all. Root.sh goes through like but when I reboot I always have so-on. I've done this several times on my old phone with no issues.
Soo I just got a new 4g.. since its within my 30 days.. and Ima use the same method... hopefully it works... ill keep y'all posted
Sent from my T-Mobile G1 using XDA App
2rz_taco_sr5 said:
Also my replacement came with 2.2.1 from the box if that helps.I have pulled the battery and retried several times and no luck at all. Root.sh goes through like but when I reboot I always have so-on. I've done this several times on my old phone with no issues.
Click to expand...
Click to collapse
I'm having the same issue with my replacement phone. The process goes through smoothly until I restart and find out that I'm still not rooted.
We might need a new root method... I hope not
Same issue here, gents. Tried a bunch and still showing s=on. Bum.
I pmed the mod to se ifeel we can post something up in the dev section to get this better noticed. Hope he agrees!
Dud you run visionary the second time?
Sent from my HTC Glacier using XDA App
Hey man. Thanks for the tip. Ran multiple times and its still showing as s=on. Tried multiple methods with same results.
Sent from my HTC Glacier using XDA App
dodgepot said:
Hey man. Thanks for the tip. Ran multiple times and its still showing as s=on. Tried multiple methods with same results.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Did any of you have usb debugging check?
i promise its not a user error. i can root and unroot one phone and my new one WILL NOT root. i had already unrooted my phone to be returned and rooted it back in less than a min. but my new one will not root no matter what i try...
i feel dumb for taking so long to look at this method but this worked like a charm for me guys.
http://forum.xda-developers.com/showthread.php?t=858996
if you just want s-off do these steps (from the link only simplified for s-off only which is all i cared about)
this uses adb so if you want you can try the method explained right after step 4 that uses only the phone.
Make sure you have visionary installed on your device. (If you were already permarooted w/s=off ignore this step.)
Download this file:
http://www.mediafire.com/?s7afymwe2wb3x60
md5sum: b73c56ca0e21664c5756d4ad295063c5
1. Now unzip the file into your SDK tools directory. (just put the files that are in the zip right into the tools folder that is in your sdk folder)
2. Plug your device into your computer. (have debugging on!)
3. Now go to your sdk folder and while holding shift down right click on the tools folder. Select open command window here. If you are in linux (ubuntu) right mouse click on your SDK tools folder, choose actions, and choose open command window(or whatever it's called). Otherwise, open a command prompt and cd your way to your SDK tools directory.
4. Type "adb push gfree /data/local" and hit enter.
Optionally, for those without sdk knowledge you could dl the file to your phone use androzip or something like it to unzip the file and then use root explorer to move the file named gfree to /data/local. Not the gfree.h file. All the other files are source code inlcuded for the gnu license. This would skip the first 4 steps.
5. Now unplug your device from the computer.
6. Run visionary to gain temp root.
7. Open terminal emulator on your device, type "su", and hit enter to gain root privileges.
8. Type "cd /data/local" and hit enter.
9. Now type "chmod 777 gfree" and hit enter to make the program executable.
10. Type "./gfree -f" and hit enter.
11. now to turn security off and set super CID the command is "./gfree --secu_flag off --cid 11111111" + enter.
reboot and s should be off again all credit to the link above this is just a simplified version for people like us who just want s-off. this is what i did and worked great. look at the thread for a list of things you can do with gfree like simlock off etc.
big nu said:
Did any of you have usb debugging check?
Click to expand...
Click to collapse
Yeah, I had that option selecteed.
Edit: trying that way now, 2rz
any luck? i tried to simplify it as much as possible for those of you just starting out...
Just one question, the section about downloading the file directly to the device, it says copy to /data/local, the local directory doesnt exist. Do I create that dir? I may have to sdk from my windows machine. Sorry for tbe trouble.
2rz_taco_sr5 said:
any luck? i tried to simplify it as much as possible for those of you just starting out...
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
Hey xda I have sdk ver.12 also jre 6....but its not detecting my device this is my 4th time trying to use adb I have windows 7...what I wanna do is use fastboot to flash a cm7 splash screen..please help..thanx
sent from my rooted mt4g running cm7.0.3...u jealous?
Download a program called usbdeview. Open up the program (run as administrator) and delete all of the drivers associated with your phone. Make sure USB Debugging is turned on in your settings/applications and plug your phone back into your computer. This should download the drivers necessary to run ADB.
Just use this
http://forum.xda-developers.com/showthread.php?t=956434
Sent from my Google Nexus 12! yup I'm from the future
I would recommend setting up adb this way if you cant get it to work with Android SDK.
<<< http://forum.xda-developers.com/showthread.php?t=928370 >>>.
I couldnt get Android SDK to work on my win7 machine either. Wish my comp just came with xp or something, new OS are a pain to get things like this working on.
Thanks guys appreciate the help the like u provided @eqjunkie829 did the trick....thanx
sent from my rooted mt4g running cm7.0.3...u jealous?
I got it to work wit win7 u must follow everything wit out flaw
Sent from my HTC Glacier using XDA App
Only thing now is flashing a new splash screen anyone know the fastboot method?
sent from my rooted mt4g running cm7.0.3...u jealous?
Chuchave said:
Only thing now is flashing a new splash screen anyone know the fastboot method?
sent from my rooted mt4g running cm7.0.3...u jealous?
Click to expand...
Click to collapse
I have flashed a couple of splash screens through terminal emulator method and it seems to be very easy. Should be a link in resource bible.
Sent from my HTC Glacier using XDA Premium App
Thanx eqjunkie
sent from my rooted mt4g running cm7.0.3...u jealous?
@eqjunkie the method that I have adb set up in using the drewblue way there's no ask tools folder so how would I push a splash screen thru? I tried a terminal emulator way by typing first such to get # then dd if=/mnt/sdcard/custom.img of=/dev/block/mmcblk0p19 I also had the custom image the right size 480*800 that I converted to a image using ez splash screen flasher tool renamed it custom.img put it on the root of my sdcard but got a cannot open for read no such file or directory error....I just don't know what to do so im guessing fastboot is maybe my last option...
sent from my rooted mt4g running cm7.0.3...u jealous?
Chuchave said:
@eqjunkie the method that I have adb set up in using the drewblue way there's no ask tools folder so how would I push a splash screen thru? I tried a terminal emulator way by typing first such to get # then dd if=/mnt/sdcard/custom.img of=/dev/block/mmcblk0p19 I also had the custom image the right size 480*800 that I converted to a image using ez splash screen flasher tool renamed it custom.img put it on the root of my sdcard but got a cannot open for read no such file or directory error....I just don't know what to do so im guessing fastboot is maybe my last option...
sent from my rooted mt4g running cm7.0.3...u jealous?
Click to expand...
Click to collapse
Try using one of splash screens that are on this site already so you can tell if there is something wrong with the file that you are using or if you are missing a step. You can always replace it later once you know what the problem is. I'm thinking that if it's saying that there is no such file that may be the problem with the file. Did you unzip the file from the folder and put it on the root of the sdcard?
Sent from my HTC Glacier using XDA Premium App
Actually I created the image usin the ex splash Creator and the other one I got from somewhere else but I put it on the root of my memory card I don't know I could be missing followed the steps to the t....ill try again....and thanx
sent from my rooted mt4g running cm7.0.3...u jealous?
my phone has the 2.3.4 update, want to go back to 2.2.1 to root, i downloaded jdk , and sdk is not detecting java . i'm on windows 7 is that the reason? my phone was rooted before using z4root i think. the one click method, so this is a frustrating. if someone could help id appreciate it. thanks
dirtyreturn said:
my phone has the 2.3.4 update, want to go back to 2.2.1 to root, i downloaded jdk , and sdk is not detecting java . i'm on windows 7 is that the reason? my phone was rooted before using z4root i think. the one click method, so this is a frustrating. if someone could help id appreciate it. thanks
Click to expand...
Click to collapse
There is a post in development section under stickies on how to downgrade to froyo.
Sent from my HTC Glacier using XDA Premium App
I am having a problem with rooting my n7 recently I decided that I would flash back to stock clean wipe sd card and reroot, well it didnt work out that way, flashed back to stock without a problem, then rerooted ok, but then was prompted to install 4.2.1 from google, well I did and here I am cant get rerooted after installing update. I use wugs tool kit and has always worked on my GNex and until now my N7, any ideas anyone?
It seems to see ADB, but no Fastboot? very strange, could I need a fastboot file or something?
Yup, better not to use a toolkit.
Need adb.exe and fastboot.exe in the platform-tools folder of the android sdk and the proper drivers.
It is nice (but not neccesary) to add a path in enviromental variables so you don't have to have files in the same directory always.
Sent from my HTC Vision using Tapatalk 2
demkantor said:
Yup, better not to use a toolkit.
Need adb.exe and fastboot.exe in the platform-tools folder of the android sdk and the proper drivers.
It is nice (but not neccesary) to add a path in enviromental variables so you don't have to have files in the same directory always.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
could you send me more info, or links I am kind of new to this and would like to know what I did and how to avoid/fix it in the future Thanks.
demkantor said:
Yup, better not to use a toolkit.
Need adb.exe and fastboot.exe in the platform-tools folder of the android sdk and the proper drivers.
It is nice (but not neccesary) to add a path in enviromental variables so you don't have to have files in the same directory always.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Nice to see you around.
I cannot forget the tremendous help you and Frankdrey gave me to discover, learn, and use an Android system on my G1.
Without both guidance I would, maybe, use now a toolkit and learn nothing.
@gunner - anytime, I love to help, now you can help others as well! Nice to see ya in the n7 forum too!
@flb
Google search android sdk, download appropriate package for your pc.
Open sdk and download all the tools in it.
To add a path I need to know what platform you are in... actually let me know when the above is finished and what platform your pc is and ill give you the rest of the steps
Sent from my HTC Vision using Tapatalk 2
demkantor said:
@gunner - anytime, I love to help, now you can help others as well! Nice to see ya in the n7 forum too!
@flb
Google search android sdk, download appropriate package for your pc.
Open sdk and download all the tools in it.
To add a path I need to know what platform you are in... actually let me know when the above is finished and what platform your pc is and ill give you the rest of the steps
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
adb for dummies.. http://www.mediafire.com/?qrjo6bi8ayblj1r
this includes everything that is needed so you dont need to grab the whole sdk. easy access to adb and to fastboot.
demkantor said:
@gunner - anytime, I love to help, now you can help others as well! Nice to see ya in the n7 forum too!
@flb
Google search android sdk, download appropriate package for your pc.
Open sdk and download all the tools in it.
To add a path I need to know what platform you are in... actually let me know when the above is finished and what platform your pc is and ill give you the rest of the steps
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
First of all thank you for the help, I'm currently running win7 64 bit. Ill check this post tomorrow and give it a try.
Sure thing, simms22 posted a nice link to just get the adb.exe and fastboot.exe, feel free to download those instead of the sdk as that is larger and you may or may not ever use a lot of the other stuff.
Sent from my HTC Vision using Tapatalk 2
demkantor said:
Sure thing, simms22 posted a nice link to just get the adb.exe and fastboot.exe, feel free to download those instead of the sdk as that is larger and you may or may not ever use a lot of the other stuff.
Sent from my HTC Vision using Tapatalk 2
Click to expand...
Click to collapse
Thank you guys for you efforts, Ill try it today.
You can just copy and paste the fastboot and adb .exe and .dll into c:\Windows instead of adding a variable.
Fast and easy lol just like I like 'em
Success! Thanks guys. I think Ill stay rooted and skip unroot rerooting.
Accidental OTA on custom rom. I have tried other posts but nothing works so far. Can someone please help.
Does the phone turn on and show LG?
Sent from my LG-VS980 using Tapatalk
lilxman said:
Does the phone turn on and show LG?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
What happens when you use anything in CWM?
SmurFFF said:
Accidental OTA on custom rom. I have tried other posts but nothing works so far. Can someone please help.
Click to expand...
Click to collapse
the link below will allow you to revert back to stock unrooted 11A.
after that you can take the OTA to 12B, reroot via IORoot and then use FreeGee to install recovery of your choice.
This has saved my phone a couple times from me getting too cocky with screwing around with things i don't fully understand but think I do.
http://forum.xda-developers.com/showthread.php?t=2448960
no download mode
WolfmanJack said:
the link below will allow you to revert back to stock unrooted 11A.
after that you can take the OTA to 12B, reroot via IORoot and then use FreeGee to install recovery of your choice.
This has saved my phone a couple times from me getting too cocky with screwing around with things i don't fully understand but think I do.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse
cant boot into download mode
lilxman said:
Does the phone turn on and show LG?
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
it boots straight into cwm usually, sometimes stuck in lg logo
Hmm OK. At work now, I will look into it when I get home. Just throwing this out there cause it caught me, you just press the volume up button, hold it down, then plug in the USB cable with the LG flash tool open and configured. I kept holding the power button down as well.
Sent from my LG-VS980 using xda app-developers app
staticx57 said:
What happens when you use anything in CWM?
Click to expand...
Click to collapse
i tried flashing new rom but says loki not supported or something
WolfmanJack said:
Hmm OK. At work now, I will look into it when I get home. Just throwing this out there cause it caught me, you just press the volume up button, hold it down, then plug in the USB cable with the LG flash tool open and configured. I kept holding the power button down as well.
Sent from my LG-VS980 using xda app-developers app
Click to expand...
Click to collapse
how do i log into flash tool
SmurFFF said:
how do i log into flash tool
Click to expand...
Click to collapse
Reread the thread there is a file you need to replace that corrects that. Uninstall it, reinstall, replace the file and then attempt to open.
WolfmanJack said:
Reread the thread there is a file you need to replace that corrects that. Uninstall it, reinstall, replace the file and then attempt to open.
Click to expand...
Click to collapse
still no download mode
SmurFFF said:
still no download mode
Click to expand...
Click to collapse
Ok man here ya go, did some digging around here and found these two threads that may help you.
First is a means of pushing TWRP via ADB, not sure if that is the answer for you by you never know till you try.
Second is a means of using Ubuntu or a VM to replace the corruption caused by OTA
http://forum.xda-developers.com/showthread.php?t=2449670
http://forum.xda-developers.com/showthread.php?t=2582142
If those do not work either the only other thing I could think to do would be to get on the lg-g2 IRC channel and request help from a dev that is online.
WolfmanJack said:
Ok man here ya go, did some digging around here and found these two threads that may help you.
First is a means of pushing TWRP via ADB, not sure if that is the answer for you by you never know till you try.
Second is a means of using Ubuntu or a VM to replace the corruption caused by OTA
http://forum.xda-developers.com/showthread.php?t=2449670
http://forum.xda-developers.com/showthread.php?t=2582142
If those do not work either the only other thing I could think to do would be to get on the lg-g2 IRC channel and request help from a dev that is online.
Click to expand...
Click to collapse
i have never done an adb before is there any way u could help
SmurFFF said:
i have never done an adb before is there any way u could help
Click to expand...
Click to collapse
There is a pretty detailed guide somewhere on the forum. I will locate it, read through it and add to it if need be bro.
WolfmanJack said:
There is a pretty detailed guide somewhere on the forum. I will locate it, read through it and add to it if need be bro.
Click to expand...
Click to collapse
thanks sorry about all the questions
SmurFFF said:
thanks sorry about all the questions
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2141817
No worries on the questions man, here is the guide I was talking about. It is pretty straight forward but some areas you may have questions I will let you know what I did.
At one point it talks about setting up system variables or something to that effect. I did not perform this step.
When you open the SDK manager and look at all the packages that are listed it can get a little confusing, for me I just selected all and let the install run it's course. ( took about 20mins ).
Once the install is good it talks about moving a copy of command prompt to the platform tools folder. Not trying to insult your intelligence but it is that simple. Just locate where the .exe for command promt on your computer is, copy it and paste in the platform tools folder.
Once that is done turn your phone on and then plug the phone into your computer. Open the command prompt from the platform tools folder and then type the following:
adb devices
it should populate some brief info about your phone. If not then usb debugging is not enabled on the device. This is why I think this one may not work for you because if it isn't already enabled not sure if there would be a way for you to enable it with the state your device is in, but there are two other ways in the TWRP guide that i already posted about that may work plus the second thread talking about using ubuntu.
WolfmanJack said:
http://forum.xda-developers.com/showthread.php?t=2141817
No worries on the questions man, here is the guide I was talking about. It is pretty straight forward but some areas you may have questions I will let you know what I did.
At one point it talks about setting up system variables or something to that effect. I did not perform this step.
When you open the SDK manager and look at all the packages that are listed it can get a little confusing, for me I just selected all and let the install run it's course. ( took about 20mins ).
Once the install is good it talks about moving a copy of command prompt to the platform tools folder. Not trying to insult your intelligence but it is that simple. Just locate where the .exe for command promt on your computer is, copy it and paste in the platform tools folder.
Once that is done turn your phone on and then plug the phone into your computer. Open the command prompt from the platform tools folder and then type the following:
adb devices
it should populate some brief info about your phone. If not then usb debugging is not enabled on the device. This is why I think this one may not work for you because if it isn't already enabled not sure if there would be a way for you to enable it with the state your device is in, but there are two other ways in the TWRP guide that i already posted about that may work plus the second thread talking about using ubuntu.
Click to expand...
Click to collapse
Ive done everything it said but i cant get it to recognize adb as a command
SmurFFF said:
Ive done everything it said but i cant get it to recognize adb as a command
Click to expand...
Click to collapse
Does it say:
"adb" is not recognized as an internal or external command, operable program or bath file
If so the command promt isnt executing from the platform tools.
attatched is a screenshot of two CMD windows, look at the location listed before where what you type in shows up.
the location on the left is from the cmd opened from the platform tools folder, the one on the right is from opening up command prompt from where it is originally located on my computer. when you open yours compare the locations and let me know what you got.
WolfmanJack said:
Does it say:
"adb" is not recognized as an internal or external command, operable program or bath file
If so the command promt isnt executing from the platform tools.
attatched is a screenshot of two CMD windows, look at the location listed before where what you type in shows up.
the location on the left is from the cmd opened from the platform tools folder, the one on the right is from opening up command prompt from where it is originally located on my computer. when you open yours compare the locations and let me know what you got.
Click to expand...
Click to collapse
im on windows 8 and when i try to find the cmd application i only get a shortcut?
not sure if it differs in windows 8 or not but I know i 7 and older versions it is located C:/windows/system32
also when you copied it did you select paste shortcut or just paste? If you selected paste shortcut that may be your issue, i selected paste and it populates as its own .exe not a short cut. Let me know what you get.