To make it short, I got downloaded a corrupted ROM (only one on the phone), and with no nandroid. Is there any other way to access my "sd" card on my phone to put another ROM in? Is flashing a stock img the only way to get it back to work without losing my pictures? Thanks..
If its recognized by the computer, just "adb push" the ROM file (and anything else you need) to your phone.
martonikaj said:
If its recognized by the computer, just "adb push" the ROM file (and anything else you need) to your phone.
Click to expand...
Click to collapse
This.
Problem sorted.
Thanks for the suggestion, but can you provide some commands to push this file through adb?
if you are not familiar with adb commands, use Android Commander. Saves alot of time.
I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.
Deekayy said:
I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.
Click to expand...
Click to collapse
Is your ROM file in the Android>Platform Tools folder?
adb push rom.zip /sdcard/
You need the extension (.zip) as well.
Edit: does adb devices indicate you're connected?
Deekayy said:
I'm a bit more familiar with adb, it's just need the to be directed to the right path with the specific command to push a rom to my phone. Does anyone know?
i tried
adb push "filename"/sdcard/"filename" but it's not giving me any response.
Click to expand...
Click to collapse
you just need:
Code:
adb push ROMname.zip /sdcard/
Assuming you put "ROMname.zip" in your platform-tools folder, or another folder you're running ADB out of.
Keep in mind, not any response, aka, just hanging, means it is still working. ADB transfers are slow, so big files will take a little bit.
Nevermind.
martonikaj said:
you just need:
Code:
adb push ROMname.zip /sdcard/
Assuming you put "ROMname.zip" in your platform-tools folder, or another folder you're running ADB out of.
Click to expand...
Click to collapse
Yes I did that, and now for some reason my sdk is not recognizing my phone (funny cause i tried flashing a new recovery.img). Now i'm re-installing sdk tools.
adrynalyne said:
Keep in mind, not any response, aka, just hanging, means it is still working. ADB transfers are slow, so big files will take a little bit.
Click to expand...
Click to collapse
Thanks, gotta fix the first problem though.
Related
Sorry if this is a repost. But hopefully someone can help me out. I'm fully rooted, full nandroid unlock.full 100 yeards. Now this morning I was going to do the process for "Permanently replacing your recovery with ClockworkMod Recovery Image"
But for some strange reason, ADB doesn't see my Evo. I tried running "Command prompt" as administrator also and it wasa no go. I typed "adb devices" and my device wasn't listed like it was yesterday before I did a full nandroid Unlock.
Do anyone have any tips on how I can resolve this issue?
If this helps, I running the Bugless Beast Rom.
Thanks
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
thanks. I'll give that a try and reply back
Strange thing....before I rooted/flashed a rom I created a Nandroid backup (I think it was stock. It doesn't have Superuser Permission in my list of Apps). Well I reverted back to that nandroid backup and now ADB sees my Evo.
I will flash back to my previous rom and trywhat you posted. Hopefully tat'll work
phatalboom said:
You might have forgotten a step or two.
Open cmd
Type cd c:\android-sdk-windows\tools\ or wherever your sdk tools folder is.
Then it should work.
Click to expand...
Click to collapse
Yeah, I tried what you suggested and itstill didn't see my Evo. I guess my only option is to revert back, then do the process.
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
I'm having same issues and it's not working. My device is not being seen. Do you I have to have the Evo in charging mode or Disk Mode?
chuckhriczko said:
Sometimes you need to restart the adb server. Try the following:
Code:
adb kill-server
adb shell
If you get a '#' then you're in.
Click to expand...
Click to collapse
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
timothydonohue said:
or, you could just try
adb kill-server
adb start-server
lol
then check with
adb devices
seriously though, you may have put on a bad image. did you check the md5 hash? if not, do. there are threads around here on how to do that, if you are using windows. i don't have the link, because linux just has a command for it.
Click to expand...
Click to collapse
Thanks for trying to help me out. But it still didn't work.
toastcfh said:
Try doing:
killall adb
sudo -s
adb devices
You must run adb as root on ur pc
Click to expand...
Click to collapse
What do you mean that I must run adb as root on my pc, i don't know what that mean. Do you mean run it by using the "Command prompt" program?
Also this only happens to me on the Bugless Beast Roms. When I revert back to my 1st nandroid backup that I was using before I flashed any rom, everything worked fine.
Is USB debugging enabled?
CentroniX said:
Is USB debugging enabled?
Click to expand...
Click to collapse
Thanks ...that fixed it! I enabled it typed "adb devices" and it showed up. thanks again!
No problem, glad you got it working! When I first started out I ran in to that trap over-and-over. Now I just make it a rule of thumb to turn it on after flashing and leave it on.
Have fun!
I would have started another thread, but this is basically a similar problem to the one I had at first with adb.
Ok...I was trying to install a rosie.apk that was in a zip format. Long story short, the OP informed me that he made a mistake and provided me the wrong information as to reinstalling the rosie.apk. He was giving me steps to "push it" via adb, instead of flashing it.
No problem to Poster and thanks for help if you reading this . But anyways after all that, When I open up "Cmd" and type anything with adb in front of it...adb devices, adb shell..., i get the message that adb is not recognized as a internal or external command. Before this incident happened i was able to just type "adb devices" and my Evo would show.
Do anyone know how to fix this?
By the way I also tried typing all the commands in the previous posts...and I get the same error message.
**Update** I got it working I had to redo the path. All is good now.
Thanks much!
You need to be in the tools directory of the sdk so cmd can find the adb command.
The guides/walkthroughs seem to cover windows but I use OS X...are there any guides/walkthroughs to root a G2 using OS X?
I'm getting frustrated
Which guide are you trying to follow? Most of them require/mention adb, but the android SDK is available for Mac, so you should be able to get adb.
It should all work the same on a Mac. All you're doing on the PC/Mac end is using adb to send stuff over to your phone. The adb guide at http://forum.xda-developers.com/showthread.php?t=865685 has some stuff in there (which I still need to work on) about getting adb working on the Mac (see later replies).
dadewy said:
Which guide are you trying to follow? Most of them require/mention adb, but the android SDK is available for Mac, so you should be able to get adb.
Click to expand...
Click to collapse
I am following this guide
steviewevie said:
It should all work the same on a Mac. All you're doing on the PC/Mac end is using adb to send stuff over to your phone. The adb guide at http://forum.xda-developers.com/showthread.php?t=865685 has some stuff in there (which I still need to work on) about getting adb working on the Mac (see later replies).
Click to expand...
Click to collapse
I have got got adb working, I put the android_sdk folder at the root of my macs hard drive. I figured out I have to put "./" infront of adb to execute commands, and I have gotten it to recognise my device.
But where I am stumped is, where do I unzip the temp and perm root folders to, onto the desktop or into somewhere in the android sdk folder?
Also do need to have two terminals running, 1 navigated to adb and the other to the unzipped folders?
Or do I do something completely different?
bobbytomorow said:
I am following this guide
I have got got adb working, I put the android_sdk folder at the root of my macs hard drive. I figured out I have to put "./" infront of adb to execute commands, and I have gotten it to recognise my device.
But where I am stumped is, where do I unzip the temp and perm root folders to, onto the desktop or into somewhere in the android sdk folder?
Also do need to have two terminals running, 1 navigated to adb and the other to the unzipped folders?
Or do I do something completely different?
Click to expand...
Click to collapse
I think the common way is to unzip or move the files to your Android_sdk/tools folder so that adb and the files are in the same directory.
Another way would be to use the full path in the adb command:
adb push /users/bobby/desktop/gfree_unzipped/gfree /data/local/
you should change it to match your actual directory structure
The slick way is to add android_sdk/tools to your path so that it will work at any direectory level.
Either way, you should only need 1 terminal window (Unless you are trying to verify you have radio s-off- the last bit that starts with "stop ril-daemon")
gee one said:
I think the common way is to unzip or move the files to your Android_sdk/tools folder so that adb and the files are in the same directory.
Another way would be to use the full path in the adb command:
adb push /users/bobby/desktop/gfree_unzipped/gfree /data/local/
you should change it to match your actual directory structure
The slick way is to add android_sdk/tools to your path so that it will work at any direectory level.
Either way, you should only need 1 terminal window (Unless you are trying to verify you have radio s-off- the last bit that starts with "stop ril-daemon")
Click to expand...
Click to collapse
That helped me out perfectly, I just rooted my G2, YAY!
Thank you everyone for your help
Ok, long story short... I had to completely wipe/format my hard drive on my computer so I lost ever single thing I had.
I completely forgot everything I needed to install for my phone as far as things like ADB. I think it was Android-SDK but I really can't remember.
Can someone help get me going in the right direction again? Many [email protected]@!!
Yeah, you need the android sdk. If all you're after is adb, then I'm sure someone around here has posted a download link to just those files. If you can't find them, then download the sdk and use the sdk manager to download and install the platform tools. For a full install of the sdk with Eclipse and ADT, you'll need to consult Google's install docs on the android developer site.
myersn024 said:
Yeah, you need the android sdk. If all you're after is adb, then I'm sure someone around here has posted a download link to just those files. If you can't find them, then download the sdk and use the sdk manager to download and install the platform tools. For a full install of the sdk with Eclipse and ADT, you'll need to consult Google's install docs on the android developer site.
Click to expand...
Click to collapse
See, I can't remember what I had.
I know it was an android-sdk folder with a few sub-folders like tools in it. I had to browse to that directory when I pushed something via ADB.
So I guess I just need to find and install the android-sdk? I'm not even sure what Eclipse and ADT is..
http://developer.android.com/sdk/index.html
Download the sdk. Adb was moved to the platform-tools folder, so you can run your adb from there, or move it to the tools folder.
Thank you!
I appreciate the help guys
Rippley05 said:
Thank you!
I appreciate the help guys
Click to expand...
Click to collapse
You're welcome.
teh roxxorz said:
You're welcome.
Click to expand...
Click to collapse
I hope I'm doing it right. I unzipped the folder, clicked on tools and read where it said adb was moved. Then I clicked on the android guy (sdk and avd manager) and now it is installing a messload of stuff.
After it's done, I should be able to use ADB but instead of going to c:\android-sdk-windows\tools\ like I used to do, I'll have to change the "tools" to platform-tools correct?
EDIT: I feel liek it is downloading a lot of stuff I don't need =p
Rippley05 said:
I hope I'm doing it right. I unzipped the folder, clicked on tools and read where it said adb was moved. Then I clicked on the android guy (sdk and avd manager) and now it is installing a messload of stuff.
After it's done, I should be able to use ADB but instead of going to c:\android-sdk-windows\tools\ like I used to do, I'll have to change the "tools" to platform-tools correct?
EDIT: I feel liek it is downloading a lot of stuff I don't need =p
Click to expand...
Click to collapse
That is correct, and I also just rename the folder to android, cuz typing all that is a pain.
And you can do that, or copy the adb items from platform-tools into the tool folder itself; tis what I did.
Alright, Windows 7 is different and kinda irritating.
All the SDK stuff went into a folder "downloads" and I let everything install, but I can't seem to find it when I run the command prompt. It was much easier in Windows XP.
If anyone is using windows 7 , could you give me the commands you use to get to the directory. I get an invalid path no matter what I type.
Should I move the SDK folders out of my downloads folder and put them on my desktop?
I put it on the root of C. Then I run cd C:\android-sdk\platform-tools. I think you need HTC sync installed as well.
Rippley05 said:
If anyone is using windows 7 , could you give me the commands you use to get to the directory. I get an invalid path no matter what I type.
Should I move the SDK folders out of my downloads folder and put them on my desktop?
Click to expand...
Click to collapse
Its easier from the desktop
OK I'll install HTC sync. That should still be on my phones SDcard right?
The problem is, I don't know what commands to enter in the command prompt to get to the different directories on my computer. If I move it to the desktop, what commands will get me there?
dglowe343 said:
I put it on the root of C. Then I run cd C:\android-sdk\platform-tools. I think you need HTC sync installed as well.
Click to expand...
Click to collapse
You don't need htc sync, just the hboot drivers.
Rippley05 said:
OK I'll install HTC sync. That should still be on my phones SDcard right?
The problem is, I don't know what commands to enter in the command prompt to get to the different directories on my computer. If I move it to the desktop, what commands will get me there?
Click to expand...
Click to collapse
the commands would be:
cd desktop/android/tools
1. change android to whatever you named your sdk folder
2. change tools to wherever your adb is located.
Names are case sensitive
teh roxxorz said:
the commands would be:
cd desktop/android/tools
1. change android to whatever you named your sdk folder
2. change tools to wherever your adb is located.
Names are case sensitive
Click to expand...
Click to collapse
Sweet I got it!
I tried to do a ADB remount and got AdbWinApi.dll is missing from my computer. I don't have my phone hooked up tho so could that be it?
Rippley05 said:
Sweet I got it!
I tried to do a ADB remount and got AdbWinApi.dll is missing from my computer. I don't have my phone hooked up tho so could that be it?
Click to expand...
Click to collapse
No prob. If you got that error, you missed it from copying the files; just double check that its there in the folder.
teh roxxorz said:
No prob. If you got that error, you missed it from copying the files; just double check that its there in the folder.
Click to expand...
Click to collapse
Ahh ok, I just moved it and it started but said device not found. I assume that IS because my phone isn't connected.
One more quick question and I promise I'll leave u alone. Whenever I push something with adb I always close the box and just unhook my phone. Is that the right method? Because I see adb is still running on my pc until I end the process with my task manager.
Rippley05 said:
Ahh ok, I just moved it and it started but said device not found. I assume that IS because my phone isn't connected.
One more quick question and I promise I'll leave u alone. Whenever I push something with adb I always close the box and just unhook my phone. Is that the right method? Because I see adb is still running on my pc until I end the process with my task manager.
Click to expand...
Click to collapse
Naw you're fine; yea, it;ll show device not connected if you have nothing connected. I personally leave it open in the command prompt after opening it just in case I go back to it. It'll close once you close command prompt.
Sweet. Thanks again Rox.
I've has that stuff installed since I first got my Hero... been a long time since I had to mess with it..
I cannot figure this out to save my life. I have downloaded and installed HTC Sync. I have the folder for android-sdk setup on my local drive. I added the environmental settings so I don't have to change directories each time.
I connect my phone with USB Debugging enabled, and then open command prompt. I change directories to E:\android-sdk\tools (My "E" drive is my default drive). Anytime I try and "Adb" command, it says that ADB isn't recognized as a command. I don't know why. Cannot figure it out to save my life.
I've attached some pictures so you can get a brief idea as to what I am talking about. I am on Windows 7 32 bit, if that makes any difference.
The first thing I noticed from your screenshot that is that you dont have adb application in your sdk tools folder.
adb has moved...try the platform-tools folder instead of just tools.
*Sigh*
I would miss something as simple as that. It's working now, thank you guys.
Edit:
One more question.. I am trying to install the "com.skype.raider-all-in-one-camwidth". I am assuming I need to use ADB to push it to the system files, but how do I go about doing that from CMD? Probably incredibly simple, but I'm lost again. Lol
dpilcher said:
adb has moved...try the platform-tools folder instead of just tools.
Click to expand...
Click to collapse
I wonder if the adb_has_moved.txt file in his screenshot might have given him a clue?!?
JimSmith94 said:
I wonder if the adb_has_moved.txt file in his screenshot might have given him a clue?!?
Click to expand...
Click to collapse
Lol I admitted it was something stupid to miss, forgive me.
Can anyone help me with the file pushing though? I am trying install that Skype .zip file, and I'm assuming it has to be pushed to the system area. Any clues as to how I go about that?
If you need to get it into system apps,
Adb push filename /system/app
Make sure you put a space between the end of the filename and the /
And make sure the file is located in the platform-tools folder.
This is annoying as heck.
I have had the Droid 1, Droid X, and Charge and have always been able to root the phones and install roms and follow directions with now problem.
I have installed SDK, I have downloaded the adb platform tools. However, I have no idea how to get adb where it needs to be from there.
Does anyone know where I can find an in-depth guide?
try here:
http://developer.android.com/guide/developing/tools/adb.html
To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701
Yeah, I have seen that.
I guess the wall I am hitting is how you actually start adb. I know where the folder is. I might be overlooking something though.
Didn't see your post Mart, ill try that now.
martonikaj said:
To use ADB commands, you open a CMD prompt (or terminal in linux) and navigate to your platform-tools folder. That's where "ADB" actually lives. Once you're in that folder, you can now use associated ADB commands.
Then you can use commands like /adb push <> <>, /adb pull <> <> etc.
This is what I found for ADB guide in XDA: http://forum.xda-developers.com/showthread.php?t=879701
Click to expand...
Click to collapse
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.
Pacifik said:
An easy way to avoid the navigation through cmd is to right click in the folder that contains adb and open the command prompt.
Click to expand...
Click to collapse
Even easier is adding the folder to the system path variable.
That allows you to always run adb, no matter what folder you happen to be at.
Ok, I have effectively managed to get to adb and it is installed.
to root the nexus, do I now start at the 1st step in the "lets begin section" listed here:
http://rootzwiki.com/topic/12013-welcome-to-root-editionstep-by-step-oem-unlock-and-root/
http://wiki.cyanogenmod.com/wiki/ADB
Ohai droidstyle good to see you here
Has anyone seen John Connor?
skynet11 said:
Ohai droidstyle good to see you here
Has anyone seen John Connor?
Click to expand...
Click to collapse
Ya you too skynet! I have no gnex yet, but soon...very soon!!
I am now Bootlooped, the bootloader is unlocked, I flashed the recovery image without a problem, but now i am stuck at the constant flashing of the google logo
Did you flash a new ROM?
this is what I was flashing
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
I was just trying to get root and CWM
I have CWM, but all it does bootloop and I can't get it to detect a sd card.