Develop Bugs

[HOWTO]- Performing a Nandroid Restore Manually using ADB

[HOW TO] Perform a Nandroid Restore via the Android Debug Bridge (ADB)
(This guide assums that you have already installed and set up adb tools on you PC)
1. Start phone in recovery mode, by turning it on while holding "Home" and "Power" buttons.
2. Plug the phone into the PC with a USB cable
3. Start Windows Command Prompt on your PC, by pressing Start on your PC and typing CMD into the run or search bar depending on your operating system. Then selecting Command Prompt.
4. Within the command prompt window, change the directory to the one your adb tools are by typing the following:
cd c:\sdk\tools
Click to expand...
Click to collapse
The path you put in may be different to this example, as it depends where on your PC your adb tools are kept.
5. Then type:
adb shell
Click to expand...
Click to collapse
6. Now type:
mount /sdcard
Click to expand...
Click to collapse
7. Now you need to change directory again to the one holding your nandroid back-up data, so first type
cd /sdcard
Click to expand...
Click to collapse
8. Then type:
cd nandroid
Click to expand...
Click to collapse
9. Now you need to find the specific name for the folder that holds your Nandroid Backup images, so type:
ls
Click to expand...
Click to collapse
and view the list that appears.
10. Now to enter the folder you want to back up to type
cd HT**********
Click to expand...
Click to collapse
obviously replacing the *s with your numbers and letters. FYI the number string is your Device Serial number.
11. Again type
ls
Click to expand...
Click to collapse
and view the list that appears.
12. Now to enter the folder you want to back up to type
cd BCD***-********-****
Click to expand...
Click to collapse
obviously replacing the *s with your numbers and letters. FYI the format of these digits is BCDXYZ-YYYYMMDD-HHMM from when the back up was created.
13. Now type:
nandroid-mobile.sh restore
Click to expand...
Click to collapse
14. Just press enter to select default.
15. Double check that the Default backup that is found is the one you want then press enter again.
Your selected backup will now be restored. When your CMD window looks like the one below you can reboot your phone and it will be as you remember it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A big thanks goes to Pulser, without whom I would still be stuck, and this guide wouldn't have been written.

Nice. But are steps 6-12 really necessary? When in shell it should enough enter nandroid-mobile.sh -r, press enter to get you the list of available backups, pressing enter once again restores the last backup, or if you want an older just type the full name of that backup.

Install apk
Hello Fellow Androids!
If this is off topic, please accept my apologies. I am searching through all of XDA for a simple solution to adding apk. Now before you start bashing, please keep in mind that I am well aware of the "search" options + google + XDA etc.
Long story short, I have:
1) Rooted
2) Fashed many Roms (currently on Stock 2.1)
3) Lag Fixxed (see signature)
4) Removed Bloatware
5) I am familiar with ABD and commands
Problem:
All I'm trying to do is install certain "apk"s using ADB. I am well aware of the Program that installs/ pushes apps automatically that are found in G1 + Vibrant + HTC + Droid Forums without having to do any typin......BUT.....I would like to know my way around ABD <----Main reason why i dont want the easy way out.
I have been here:
http://forum.xda-developers.com/showthread.php?t=716806
as well as here:
http://forum.xda-developers.com/showthread.php?t=743457
even been here:
http://forum.xda-developers.com/showthread.php?t=740545
I know what you are thinking, why not use them? As i said before, i would like to be efficient with ADB. So...
I have tried methods found here:
http://forum.xda-developers.com/showthread.php?t=517874
As well as:
http://forum.xda-developers.com/showthread.php?t=532719
The problem I am having is:
Whether i navigate to my folder (desktop with all my apps) and use either
"adb push app /system/sd/app
adb push app-private /system/sd/app-private"
or simply
"adb install <path to file> - Example: adb install c:/apps/apps2sd.apk"
I always get the error: "cant find <whatever apk> to install"
No matter which directory i have it, i get that message.
Note:
1) I have debugging on
2) I mounted sd <----also tried Without mounting
3) I have used the same command when I removed bloatware but i understand Adding apks are slightly different.
4) I have all the drivers installed + Microsoft's .net framework + etc
What am i doing wrong?
All Critics, input, education bashing (just not hating) lol are welcome. Thanks!

put adb in your path... cd to the apk directory and run adb push *.apk /system....

TylerDurdenK said:
[HOW TO] Perform a Nandroid Restore via the Android Debug Bridge (ADB)
(This guide assums that you have already installed and set up adb tools on you PC)
and view the list that appears.
12. Now to enter the folder you want to back up to type
obviously replacing the *s with your numbers and letters. FYI the format of these digits is BCDXYZ-YYYYMMDD-HHMM from when the back up was created.
13. Now type:
MD window looks like the one below you can reboot your phone and it will be as you remember it.
http://farm3.static.flicn.[/QUOTE]
I get the error "nandroid-mobile.sh not found" after step 13. please help.
Click to expand...
Click to collapse

Dont use this, use jordfaz's clockworkmod, if you really need to use this adb script then you need to get nandroid-mobile.sh script somewhere

[Q] Adb is not recognized as an intern or extern command

Hi, so i'm very new to Android and while attempting to do the gfree permaroot for my desire Z, i came across a problem. When I type the commands, it says that adb is not and intern or extern command. I have adb file in platform-tools (400ko). When i open it, it make a cmd screen for about 2 seconds then shuts down. Can someone help me with this problem
I just installed HTC sync and my computer cannot find any device attached. It says: the htc vision htc port does not repons.
Thanks
Vince

are you doing CD C:/location of adb/adb?
You must direct your command line to the directory of adb.
also run cmd as administrator if you're on vista or win7.
If you're not a command line pro I suggest you just rename your folder to whatever you want in C:/folderhere
For example heres the folder renamed to "android"
then just do CD C:/android
Then type "adb" and hit enter
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and boom! you're in adb!
Hope this helps
I'm no adb pro but I'm ok at cmd. Maybe I should make a video or something on the basics to getting adb running if there isn't one already?

Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it

Vincethedevil said:
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Click to expand...
Click to collapse
Nah, you still aren't getting it
How did you install ADB? If you search in Windows for the file "adb.exe" what does it tell you?

it's in the platform tools folder in the sdk

Vincethedevil said:
Thanks for the quick reply! It helped me figure out that you need to open adb before using the adb command but the same error occurs (is not an intern/extern command) when i try it
Click to expand...
Click to collapse
I'm not quite sure what you mean by this, I wonder if you're doing something wrong. Have you followed this guide ? http://forum.xda-developers.com/showthread.php?t=865685
If you have added the correct folders to your path, as explained in the guide, it should find adb ok.
If it's finding adb ok, then if you run "adb devices", is that not showing your phone ? Are you using the original HTC cable to connect to your phone ? Third-party ones sometimes will not work.

Yeah i'm using the original Htc cable. I have downloaded Htc Sync and it appears as "my htc" in device manager. Although, Htc sync doesn't recognize any plugged in phone.
For adb, i go in cmd, change the path with cd to the path where is the adb.exe, then type adb. A series of text follow. Then, i switch to the folder where is gfree (with cd) and type the first line for temp root. That when it says that adb is not recognized as an intern or extern command

Since adb.exe is not located in your gfree directory, it's not a recognized command. You either need to run the commands directly from your platform tools directory (and use the full directory paths for the gfree commands) or place the path for adb in your environment variables so that adb can be called from any directory (step four in the ADB for noobies linked earlier). This is the easier method.

I tried it but it's not working. I'll take pictures tomorrow so my obvious noob error can be spotted

Adding adb to your path
Hey there,
Here's a quick guide to fix your problem (basically, you don't have adb added to your path). Btw, this guide was made on Windows 7, but the principle should be the same for Vista and XP (though the steps are different).
Step 1: Right click "Computer" or "My Computer"
Step 2: On the left side find "Advanced system settings" and click it.
Step 3: On the Advanced tab, click "Environment variables"
Step 4: In the bottom part of the window, scroll until you find the row that starts with "Path" and click "Edit"
Step 5: At the end of the existing line, add a semicolon ( ; ) and the path to your android toolkit. If the path contains spaces, don't forget to enclose it in quote marks ( "C:\path to adb\tools\" )

Vincethedevil said:
For adb, i go in cmd, change the path with cd to the path where is the adb.exe, then type adb. A series of text follow. Then, i switch to the folder where is gfree (with cd) and type the first line for temp root. That when it says that adb is not recognized as an intern or extern command
Click to expand...
Click to collapse
You haven't set the Path up so that it can find adb, as has been said, and that's all covered in the guide that I previously linked to. But the previous poster has provided you with an excellent step-by-step solution.

Thanks alot, my adb problem is now solved! I just have one more question, when i plug my phone, htc sync cannot recognize it. Although, when i write adb devices in cmd, my phone appear. Am I still gonna be able to permaroot or should i mess with the drivers.
Thx
Vince

It's not a driver problem, it's an HTC Sync problem. Your phone has to be in Sync mode and you have to wait a few minutes (mine takes up to 20 mins) for HTC Sync to recognize it.

sounds like you'll be able to root just fine if it recognizes and responds to adb.
Not sure about htc sync, I don't even know what that is...lol

not able to root
i am using this procedure
http://forum.xda-developers.com/showthread.php?t=1601038
as i am running runme.bat i am getting this screen please help

Need to set up adb, there are tons of guides on xda and the web to do this properly, follow one of them and then try your whatever you're doing again
Sent from my Nexus 7 using xda premium

demkantor said:
Need to set up adb, there are tons of guides on xda and the web to do this properly, follow one of them and then try your whatever you're doing again
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
thanx for reply/..
not able to to set up adb.. please help if you can
should i uninstall existing drivers and again install it

You may need to reinstall drivers but first make sure you have the right ones as well as adb.exe download from the sdk or whereever you get it
See the third post. In this thread
http://forum.xda-developers.com/showthread.php?p=31899577
If you're still having issues let me know and ill help ya
Sent from my MyTouch 4G Slide using xda premium

Lost RSA key but did make a backup using RA but can't restore.

Hi,
I don't know how but my RSA key is missing from Winmax RSA key checker. no wonder I couldn't connect to my 4G network. I did make a backup using RA a while ago just to backup the Winmax key and nothing else. I located the folder on my SD and could view it from my RA recovery. But when I try to restore it...it says opps something went wrong and check your log file.
I don't know where is my log file and I don't know how to restore this key..any help would be greatly appreciate.
Thank you

place the wimax.img file on the root of your sdcard, open terminal, type
su
then type
flash_image wimax /sdcard/wimax.img
reboot, check for keys

Hi,
I did place the image file on my root under the sdcard and type "flash_image /sdcard/wimax.img"
but it says not found
i also created another folder called wimax and copy and paste my wimax.img in there as well and tried "flash_image /sdcard/wimax/wimax.img"
its also not found
i'm using terminal emulator if that helps
thank you

the file is named wimax.img? it is caps specific so if its named Wimax.img it will error
either change the name or type its exact name with caps etc

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PC36100 using Tapatalk

your second flash attempt the flash_image wimax /sdcard/wimax/wimax.img you had the file in the folder then?

It looks like you don't have the flash_image command on there.
See if this helps, it's instructions on getting flash_image onto your phone: http://wiki.cyanogenmod.com/index.php?title=Flash_image
Clarification: the "not found" error you're getting is in reference to flash_image. Notice that you got the same "Not found" message when you typed "dir", since there is no dir command in that shell.

NewZJ said:
your second flash attempt the flash_image wimax /sdcard/wimax/wimax.img you had the file in the folder then?
Click to expand...
Click to collapse
YES and still not found

jesuspgt said:
It looks like you don't have the flash_image command on there.
See if this helps, it's instructions on getting flash_image onto your phone: http://wiki.cyanogenmod.com/index.php?title=Flash_image
Click to expand...
Click to collapse
I downloaded the flash_image.zip from the site above..can i flash it via recovery to install it to my phone? thanks

hmm. used to have flash_image included. when did it change?

TommyNgo215 said:
I downloaded the flash_image.zip from the site above..can i flash it via recovery to install it to my phone? thanks
Click to expand...
Click to collapse
You really should follow the instructions on that link, they tell you exactly how you need to do this.

NewZJ said:
hmm. used to have flash_image included. when did it change?
Click to expand...
Click to collapse
Not really sure, I kinda figured it would be included within busybox. But I guess it might depend on the rom. Or it could just be a one-off weird scenario here.

jesuspgt said:
Not really sure, I kinda figured it would be included within busybox. But I guess it might depend on the rom. Or it could just be a one-off weird scenario here.
Click to expand...
Click to collapse
oh i don't have busybox i'm using Terminal Emulator. may that's why?

FIXED
download android terminal emulator, jack palevich author
it works in that one
Edit: not fixed

NewZJ said:
FIXED
download android terminal emulator, jack palevich author
it works in that one
Click to expand...
Click to collapse
Yea thats why i have...i downloaded that one Android Terminal Emulator by Jack Palevich but it doesn't work for me for some reason ((

TommyNgo215 said:
oh i don't have busybox i'm using Terminal Emulator. may that's why?
Click to expand...
Click to collapse
busybox isn't a terminal, it's the name given to the collection of command applications (for lack of a better term), that are used in a linux shell (terminal). Here's a wiki about it: http://en.wikipedia.org/wiki/BusyBox

If you don't want to use ADB, you can try just unzipping http://cyanogen-files.carneeki.net/flash_image.zip
It should just be flash_image in there. Stick flash_image into the root of the sdcard. after that, you should (hopefully) be able to begin using that command.
Edit: that zip file is not one that is flashed via recovery. It's just a plain old zip file. You just need to extract the file inside of it to the root of your sd card

its not that I don't want to use ADB but my knowledge is very limited. I got so confused from reading it and more confused from reading it again. SDK i don't have SDK i don't know what it is and then ADB i'm stupid. its crazy that i have an image here but i can't flash it using RA recovery.

ok i extracted..and still not found..it didn't install that to the phone. oh my what have i done

ADB is really not as complicated as it seems at first.
To get the SDK, go here: http://developer.android.com/sdk/index.html and install whichever flavor applies to you.
Assuming you're in Windows, just load up command prompt and navigate to the folder that the SDK installed to.
Plug your phone in, make sure that debugging is enabled in the USB settings on the phone, and then just follow the instructions step-by-step from that link. Those instructions focus at the end towards flashing a recovery image, but you will just need to substitute wimax in instead.

Backup and Restore Galaxy Nexus without root (Mac)

UPDATED 2/3/12
Thanks to @copkay for writing this! http://forum.xda-developers.com/showthread.php?t=1420351 (windows version)
copkay said:
Like a lot of you, I have been putting off unlocking the bootloader on my Nexus because I didn't want to have to go through the hassle of backing up everything manually and restoring individual application data; logging back into apps; saving settings; etc. I found an undocumented (at least as far as my googling was able to find) feature in the latest version of the ADB platform tools (for Android 4.0+) that allows you to create a full system backup, including app apks, their respective data, as well as the internal storage.
This guide assumes you have already installed the Android SDK, and updated the Android SDK Platform Tools to the latest version (currently Rev 10) using the SDK Manager.
Click to expand...
Click to collapse
1. Connect your device via USB, and open Terminal.
2. In Terminal, type "cd " with the space and then drag your "platform-tools" folder in the android sdk where the space is, it should look like this "cd /where ever you put the folder/name of you computer/android-sdk-mac-osx/platform-tools". Drag and drop will do this for you, then hit enter.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. In the same terminal window, type "./adb" and hit enter. A lot of stuff with come up that you really dont need to worry about.
4. Optionally, type the command "./adb devices" to ensure that your device is properly recognized. If you're comfortable with ADB already, just skip this.
The command parameters format is:
./adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|nosystem] [<packages...>]
Click to expand...
Click to collapse
The most basic command you can use is simply:
./adb backup -all
Click to expand...
Click to collapse
This will use the defaults to backup only app and device data (not the APKs themselves) to the current directory as 'backup.ab'
To explain the parameters:
./adb backup -f <file>
Click to expand...
Click to collapse
Use this to choose where the backup file will be stored, e.g. '-f /backup/mybackup.ab', which will save it at the root of your drive (C:\ for Windows, etc.) in a folder called backup, as a file named 'mybackup.ab'. I recommend using this flag to set a location manually, as with my first backup test, it said that it completed successfully, but I was unable to locate the backup file. I have no idea where it was saved, but it wasn't where it should have been located.
./adb backup -apk|-noapk
Click to expand...
Click to collapse
This flags whether or not the APKs should be included in the backup or just the apps' respective data. I personally use -apk just in case the app isn't available in the Market, so that I don't have to go hunt it down again. The default is -noapk.
./adb backup -shared|-noshared
Click to expand...
Click to collapse
This flag is used to "enable/disable backup of the device's shared storage / SD card contents; the default is noshared.", which for the Nexus I would certainly flag to -shared, but from my test, it did not restore all of the contents of my internal storage, so I recommend backing up music, pictures, video, and other internal storage items manually, just to be on the safe side. The default is -noshared.
./adb backup -all
Click to expand...
Click to collapse
This flag is just an easy way to say to backup ALL apps. The packages flag (further on) can be used to choose individual packages, but unless you're just wanting to backup a specific application, use -all for a full system backup.
./adb backup -system|-nosystem
Click to expand...
Click to collapse
This flag sets whether or not the -all flag also includes system applications or not. I used -system, but this is probably unnecessary, and I would almost guess that it is safer to use -nosystem, but use your own judgment on this. The default is -system.
./adb backup <packages...>
Click to expand...
Click to collapse
Here you can list the package names (e.g. com.google.android.apps.plus) specifically that you would like to backup. Use this only if you're looking to backup a specific application.
3. Once you've made your decision on how to perform the backup, simply type the command as you would like it; in my case, this is the command that I used:
./adb backup -apk -shared -all -f /c/backup20111230.ab
or
./adb backup -apk -shared -all -----------and then just search for it in finder.
Click to expand...
Click to collapse
4. You will see a screen like the following:
5. Enter a password (if desired) for encryption of the backup file. RETAIN THIS PASSWORD FOR RESTORING LATER.
6. This process will take several minutes to complete, depending on the settings you've chosen, but when completed, you should get a toast on-screen saying 'Backup Complete', or if you miss that, you'll know once your command line has returned.
7. Now go unlock your bootloader (not going to go into the process for this guide, but you probably know how already, and if not, there are several guides a search away).
8. Once you're booted back into Android, you can choose to add your account now, or skip that for later. I skipped it for later, but I think it might make the process more smooth to sign in before the restore. YMMV.
9. To restore, with your device connected open your command prompt again, and type:
./adb restore /backup/mybackup.ab
Click to expand...
Click to collapse
replacing '/backup/mybackup.ab' with the location of your backup file.
10. You will see a screen like the one below:
11. Simply type in your current encryption password (if you've set one), and the password with which the backup was encrypted (if you chose to set a password), and the restore will begin. It again will take several minutes depending on the size of the backup and the options chosen.
12. You're back to normal, short of possibly some widgets on the home screen. My wallpaper was even restored, my app folders remained just as I had them before, my alarms remained, and for most applications, I didn't even have to log back in; it kept everything.
________________________
NOTE: I did have an issue with not all files being restored to the Internal Storage; in particular, the Gallery still displayed all the folders and files that it had cached (which it expected to be there) as only gray boxes, and would not display the images, nor would it rescan the media. I simply copied the files back to the Internal Storage directory manually, and all was well again. Again, YMMV.
NOTE : Also to note, this will not back up SMS messages, so if you're concerned about those, you may want to look into an alternative application to back up SMS.
Hope this is able to help! If so, give me a thanks )) and let me know how your experience goes.
- Sean

Worked
I couldn't get it to work no matter how much I tried. I could connect and see the device but when I ran the command, all I would get was a list of commands. I finally found a way upgrade the sdk by:
./android update sdk --no-ui
Then it worked perfectly!!

bosshoss16 said:
I couldn't get it to work no matter how much I tried. I could connect and see the device but when I ran the command, all I would get was a list of commands. I finally found a way upgrade the sdk by:
./android update sdk --no-ui
Then it worked perfectly!!
Click to expand...
Click to collapse
Ya in the beging when I said you need the sdk package, I forgot to say for all to be updated, whoops. Was that your problem?

Hipe0ples555 said:
Ya in the beging when I said you need the sdk package, I forgot to say for all to be updated, whoops. Was that your problem?
Click to expand...
Click to collapse
Yeah, after I updated the sdk, it worked perfectly! Thanks!!

I'm completely new to this. I downloaded the SDK manager and the Platform tools.
Terminal opened automatically with the manager. Then I did number 2 which worked fine.
After that when I type the commands from number 3 and 4 nothing happens when I hit enter. Any help would be appreciated.
Is it possible my Mac doesn't see the Nexus. Is the Nexus supposed On or Off by the way, I had it On.

ivoniko said:
I'm completely new to this. I downloaded the SDK manager and the Platform tools.
Terminal opened automatically with the manager. Then I did number 2 which worked fine.
After that when I type the commands from number 3 and 4 nothing happens when I hit enter. Any help would be appreciated.
Is it possible my Mac doesn't see the Nexus. Is the Nexus supposed On or Off by the way, I had it On.
Click to expand...
Click to collapse
Code:
./adb devices [enter]
Will tell you if its connected (per #3).
If #2 works properly and it navigates to your platform-tools folder, then you should be able to type ./adb [enter] and have all of th ADB commands come up. If not, you haven't properly updated/installed the SDK, or you haven't navigated to the folder properly.

martonikaj said:
Code:
./adb devices [enter]
Will tell you if its connected (per #3).
If #2 works properly and it navigates to your platform-tools folder, then you should be able to type ./adb [enter] and have all of th ADB commands come up. If not, you haven't properly updated/installed the SDK, or you haven't navigated to the folder properly.
Click to expand...
Click to collapse
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.

ivoniko said:
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.
Click to expand...
Click to collapse
when you type ./adb , does it run a long command line?

Hipe0ples555 said:
when you type ./adb , does it run a long command line?
Click to expand...
Click to collapse
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.

ivoniko said:
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.
Click to expand...
Click to collapse
Probably not, I would just try to delete the whole android_sdk folder and re-download it, even though it may take some time, it will be worth it if it works!

ivoniko said:
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.
Click to expand...
Click to collapse
Probably not, just delete the whole Android_SDK folder and re-install everything! You know to go into the folder, go to tools and click android to updated all 6 things right?

Probably not, just delete the whole Android_SDK folder and re-install everything! You know to go into the folder, go to tools and click android to updated all 6 things right?

ivoniko said:
No matter what I type nothing runs. Even when I try the update command from the SDK Readme.txt that came in the ZIP - "tools/android update sdk --no-ui" nothing happens.
Could there be something wrong with my Terminal.
Click to expand...
Click to collapse
Did you see my other post, it is not showing up for some reason, is it working yet?

ivoniko said:
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.
Click to expand...
Click to collapse
One thing that I noticed, I had my Nexus plugged in through a USB hub, and I was seeing the same behavior you described. I then plugged it in directly into my laptop and I was able to see it. May or may not apply to your situation.

Alright so an update to my previous comment.
I was able to follow this guide and create a backup, unlock the boot loader and root the phone successfully. I am now in the process of restoring my backup, however when I type in:
./adb devices
in the terminal, nothing is listed. Therefore, I am unable to restore my back up. Any ideas on what may be going on?
EDIT: Figured it out, I forgot to re-enable USB debugging after my phone was wiped

Hipe0ples555 said:
Probably not, just delete the whole Android_SDK folder and re-install everything! You know to go into the folder, go to tools and click android to updated all 6 things right?
Click to expand...
Click to collapse
Yes, I went to tools, clicked on android, updated 6 things and after that when I entered the commands nothing happened.
In any case I will listen to your advice and download everything again.

Entering commands in terminal doesn't work. Even before having to conect the phone just entering the update commands in terminal doesn't do anything. I have no clue.
Here it is how it looks -
Last login: Tue Jan 31 00:53:34 on ttys000
/Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
Name-MacBook-Pro:~ name$ /Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
tools/android update sdk --no-ui
./android update sdk --no-ui

ivoniko said:
Thanks for the fast reply. I've no idea what to do. I did install it, I'm not sure what - navigate properly means. I just did what it says.
Neither ./adb [enter] nor ./adb devices [enter] work, just nothing happens. Here is copy for the Terminal:
cd /Users/name/Desktop/android-sdk-macosx/platform-tools
./adb
./adb devices
If you have any ideas please let me know.
Click to expand...
Click to collapse
Ok, so it is not literally; cd /Users/name/Desktop/android-sdk-macosx/platform-tools if thats not where it is; in terminal just type "cd " then just drag the platform-tool folder into the terminal and you should get something that LOOKS like cd /Users/name/Desktop/android-sdk-macosx/platform-tools but if thats not where it is, it will have a different path. Does that help?

ivoniko said:
Entering commands in terminal doesn't work. Even before having to conect the phone just entering the update commands in terminal doesn't do anything. I have no clue.
Here it is how it looks -
Last login: Tue Jan 31 00:53:34 on ttys000
/Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
Name-MacBook-Pro:~ name$ /Users/name/Desktop/android-sdk-macosx/tools/android ; exit;
tools/android update sdk --no-ui
./android update sdk --no-ui
Click to expand...
Click to collapse
You forgot to type cd*space*, "cd " before draging the folder into the terminal.

Just updated everything! Does the change help?

[Q] Soft bricked htc one m8 no OS

Looked all day for a similar situation and all the ones i found didnt help so this is my last resort.So today i decided to root my phone. I had great succsess and was eager to flash a new rom. My recovery is TWRP. I downloaded Android revolution hd to my external sd. I went into recovery mode swiped my rom, tried to flash Android revolution, the file was there but the image wasnt. Now i have no rom on my phone and cant figure out how to flash one using adb on terminal. The commands ive tried arent working and i get different results from others in similar situations. In fastboot it says 'fastboot usb' so i know its connected and the cables fine. Im definitely a noob at tech hence the reason i managed to make a stupid mistake like this but i could really use the help. Im a US Marine and need my phone by tomorrow. Sorry if this thread is in the wrong spot im new to forums. Thanks a lot guys.

What do you mean by "the file was there but the image wasnt" ?
Is it the zip file is on your external sd but can't see it in TWRP recovery ?
Make sure that you select Micro SDcard on storage option.
When you have an external sd, you don't really need those ADB commands ... just take it out and connect to a PC then put in a ROM.zip on your external sd

ckpv5 said:
What do you mean by "the file was there but the image wasnt" ?
Is it the zip file is on your external sd but can't see it in TWRP recovery ?
Make sure that you select Micro SDcard on storage option.
When you have an external sd, you don't really need those ADB commands ... just take it out and connect to a PC then put in a ROM.zip on your external sd
Click to expand...
Click to collapse
yes it was on my external but the image wasnt. But now i think my sd is broken theres a crack in it, and my computer doesnt pick it up anymore. convenient i know. Before i could see the whole file but the img. was missing. now none of its there. I can get a new sd and put a rom on like you said but i wouldnt be able to do that right now and was wondering if there was another way?

zacks94 said:
.... i wouldnt be able to do that right now and was wondering if there was another way?
Click to expand...
Click to collapse
Push the ROM.zip to internal sdcard
How-to :
Put a ROM.zip in your adb/fastboot folder
Put your device in TWRP recovery mode
Then adb push it to internal sdcard
command : adb push ROM.zip /data/media/0/
Once complete, select install - make sure the Storage selected is Internal Storage - you should see the ROM.zip

i will try this and get back to you. I appreciate the help.

zacks94 said:
yes it was on my external but the image wasnt. But now i think my sd is broken theres a crack in it, and my computer doesnt pick it up anymore. convenient i know. Before i could see the whole file but the img. was missing. now none of its there. I can get a new sd and put a rom on like you said but i wouldnt be able to do that right now and was wondering if there was another way?
Click to expand...
Click to collapse
If it's not picking up your phone in adb try redownloading the drivers, this website worked for me (http://www.andromods.com/download-files/get-htc-one-m8-usb-drivers-newest-all-models.html). Then try to adb push a stock rom to your device and redownload it in your recovery.

this is what i got and have gotten multiple times with different zips.

zacks94 said:
this is what i got and have gotten multiple times with different zips.
Click to expand...
Click to collapse
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/

1163
ckpv5 said:
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/
Click to expand...
Click to collapse
This is what i got while trying to push. Am i supposed to be on adb sideload, or bootloader? Sorry im dumb

ckpv5 said:
There's a space between ROM.zip and /data which is omitted in your command
wrong : ./adb push One_M8_2.22.401.4_deodexed.zip/data/media/0/
correct: ./adb push One_M8_2.22.401.4_deodexed.zip /data/media/0/
Click to expand...
Click to collapse
woops. Ths...

zacks94 said:
This is what i got while trying to push. Am i supposed to be on adb sideload, or bootloader? Sorry im dumb
Click to expand...
Click to collapse
No need to select adb sideload or whatever ... just enter recovery, check mount - data is ticked then do what I mentioned before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

zacks94 said:
woops. Ths...
Click to expand...
Click to collapse
I don't know much about Mac, usually the different in command is only put the ./ infront of adb or fastboot
do you get your serial no and the word recovery when you run
./adb devices (put your device in recovery)
this is mine
View attachment 2913050
I tried to adb push HTC_One_(M8)_-_MaximusHD_7.0.0.zip /data/media/0/
(because I don't have the same ROM.zip as yours)
View attachment 2913055
And it is a successful effort

ckpv5 said:
No need to select adb sideload or whatever ... just enter recovery, check mount - data is ticked then do what I mentioned before.
View attachment 2913038
Click to expand...
Click to collapse
holy crap it worked. Thanks a lot.I really appreciate it.

zacks94 said:
holy crap it worked. Thanks a lot.I really appreciate it.
Click to expand...
Click to collapse
No problem ... glad that I could help

NO os. stuck in htc logo with CWM but device not recognized adb
ckpv5 said:
No problem ... glad that I could help
Click to expand...
Click to collapse
on mac. when i go to terminal and type fastboot devices it keeps coming with the message. "-bash: fastboot: command not found" i can boot into bootloader and into CWM but thats all. I have no OS. i have a few roms stored but when i flashed them it just stays stuck in the htc logo.
on my pc, i go to cmd and i downloaded android sdk. I placed a rom into platform-tools folder and when i do "adb sideload <filename>" it comes up with error: device not found.
I dont know what else to do. any help would be very appreciated regards
Raul

rauliroo said:
on mac. when i go to terminal and type fastboot devices it keeps coming with the message. "-bash: fastboot: command not found" i can boot into bootloader and into CWM but thats all. I have no OS. i have a few roms stored but when i flashed them it just stays stuck in the htc logo.
on my pc, i go to cmd and i downloaded android sdk. I placed a rom into platform-tools folder and when i do "adb sideload <filename>" it comes up with error: device not found.
I dont know what else to do. any help would be very appreciated regards
Raul
Click to expand...
Click to collapse
Your command is wrong.
On Mac .. you type
./fastboot devices
there is extra character needed ---> ./
when do adb command, it is ./adb
Note : I'm not familiar with CWM ... only TWRP ... all those I wrote here are based on TWRP recovery but should be the same

ckpv5 said:
Your command is wrong.
On Mac .. you type
./fastboot devices
there is extra character needed ---> ./
when do adb command, it is ./adb
Note : I'm not familiar with CWM ... only TWRP ... all those I wrote here are based on TWRP recovery but should be the same
Click to expand...
Click to collapse
It didn't work. I genuinely don't know whats missing. if device its not recognized. could be a driver issue on mac??
have a look at the screenshots
many thanks
Raul

Yep .. driver looks ok but you don't have fastboot & adb files ?
See this to get them : .http://forum.xda-developers.com/showthread.php?t=2390995
You mentioned you downloaded sdk, you need to run the command from platform-tools folder.
Check the screenshot how the directory looks : http://forum.xda-developers.com/showpost.php?p=55062969&postcount=10
You should have something like Rauls-MacBook-Air: platform-tools~Raul$ ./fastboot devices
BTW this is M8 forum ... why don't you post your problem in M7 forum ?
Maybe there are more people who familiar with Mac ... I never use one, I know only some basic.