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

[Tut] Preparing Your One X for Custom Roms (For Dummies) [Mac OS X]

Big thanks to bagofcrap24 for his great original guide here.
This one is for OS X users with an administrator account, I did it in OS X (Lion) because I haven't got the Android SDK installed on Windows at the moment and didn't want the hassle of downloading it just for the USB drivers.
If you get the [Waiting For Device] message in Windows Command Prompt and have access to a Mac instead, you might also want to try this guide.
If you get 'Permission Denied' in Terminal try this.
If I made any errors let me know and I'll correct it.
UPDATE: If you see any errors on HTC-dev such as "We are sorry, but this section of site is temporarily closed." just be patient, wait a little while and try again.
Unlocking Your Bootloader
Before we can even think about doing anything the first port of call is unlocking your bootloader.
As of the time of writing this there is currently no S-OFF method available so this is the only method of flashing a new recovery or boot image.
I'm going to keep this as simple as possible.
1. Go Here "http://www.htcdev.com/" and create yourself an account on HTCDEV.
2. Download this fastboot file for Mac.
3. Make a new folder on your desktop called 'fastboot'.
4. Extract the file 'fastboot-mac' from the .zip downloaded in step 2 to this folder.
5. Go here http://www.htcdev.com/bootloader/ and select "All Other Supported Models" and "then begin unlock bootloader".
6. Yes, tick both boxes, proceed.
7. Skip up to step 8 as we have all we need for the first 7 steps.
8. Power off your phone by holding the power button down for 10 seconds.
9. Power your phone on by holding power and volume down.
10. Highlight Fastboot with volume +/- then press power.
11. Plug your phone into your Mac and open a Terminal window.
12. Type this into your Terminal window:
sudo -s (then type your password and press enter)
cd /volumes/"your OSX drive name"/Users/your-username/Desktop/fastboot
./fastboot-mac oem get_identifier_token
Click to expand...
Click to collapse
13. Select & copy the text as per step 9 on the HTCDev website.
Terminal will add some characters to the left of the token, compare yours with the HTC example token, copy your token into the Textedit application and remove the text along the left to make them match, then copy the token again.
14. Paste your identifier token into the box at the bottom and submit.
You will receive an e-mail shortly from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached.
15. Download the "Unlock_code.bin" from the e-mail and save it to the same folder that we extracted fastboot files to in step 2.
16. Type this into your Terminal window:
./fastboot-mac flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
17. The Display Will change on your phone, press Vol + to accept and power to confirm.
Congratulations, you have successfully unlocked your bootloader.
Now to the good stuff..
Installing A Recovery
This one is very simple to do once you have your bootloader unlocked.
A thing to note; at present there is no USB-Mass Storage in recovery so if you are planning to install a custom rom i would get it put on the internal memory of your phone now rather than messing things up later and been unable to install it.
(if you have follwed my unlocking guide skip to step 4)
1. Download this fastboot file for Mac.
2. Make a new folder on your desktop called 'fastboot'.
3. Extract the file 'fastboot-mac' from the .zip downloaded in step 2 to this folder.
4. At Present The Latest Recovery is an Interim made by Paul O'Brien from Modaco, you can grab it HERE
P.S. its the top one out of the two, the bottom is stock recovery.
Update: Latest official touch and non-touch recovery versions by Koush are available here.
5. Download the custom recovery and save it in the same folder as you did the fastboot files.
6. Power the phone off by holding the power button for 10 secs.
7. Select Fastboot with volume + or - then press power.
8. Plug your phone into your Mac and open a Terminal window.
10. If you still have the Terminal window open from installing your bootloader then skip to the next step, if not then type this into your Terminal window:
sudo -s (then type your password and press enter)
cd /volumes/"your OSX drive name"/Users/your-username/Desktop/fastboot
Click to expand...
Click to collapse
11. Type this into your Terminal window:
./fastboot-mac flash recovery name_of_recovery_image.img
in my case it was ./fastboot-mac flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
Click to expand...
Click to collapse
Congratulations, you now have a custom recovery.
Flashing A ROM
1. Select reboot bootloader with volume +/- then power to select
2. Select HBOOT with volume +/- then power to select
3. Select recovery with volume +/- then power to select
You are now on your custom recovery.
4. First things first - do a Nandroid Backup of your current ROM in case anything bad happens.
5. Make sure you already have your shiny new ROM .zip on your internal memory as you cannot enable mass storage in the current recovery builds.
6. Wipe then flash your new custom ROM.
(You can flash the Super Wipe .zip from here to easily wipe your system partition and prepare it for the fresh ROM, thanks mike1986.)
OR you can download the latest SuperSU binaries from HERE and install them Via Recovery to just root the stock ROM.
Hope this helps some of you.

You can use Homebrew to install the Android tools if you want. It will also update them for you if you ask it to, via a simple command. Pretty convenient.
http://mxcl.github.com/homebrew/

thanks looking to try it but the dev web in htc it's down

Thanks for the guide....was helpful

./fastboot-mac oem get_identifier_token
'sudo ./fastboot-mac flash recovery name_of_recovery_image.img'
i use this two commands and say sudo: ./fastboot-mac: command not found

Terminal needs to be navigated to the same folder as the fastboot-mac file you extracted earlier, you can do this automatically in Lion (not sure about older versions) by right-clicking the folder and going to 'Services' then selecting 'New Terminal at Folder'.
You can navigate manually either by using the 'cd' command, for example:
cd /volumes/"OS X"/fastboot
Note the importance of quotes for a drive name with spaces.
You can also activate root before you do anything by typing sudo -s

i don't find that option new terminal at folder not showing it mmm
Sent from my HTC One X using xda premium

x.Orville.x said:
i don't find that option new terminal at folder not showing it mmm
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Just use the cd command then instead:
cd /volumes/"your OSX drive name"/fastboot
Sent from my HTC One X using xda premium

i have lion and i click it the folder and i don't see this
Services > New Terminal at Folder)
---------- Post added at 06:52 PM ---------- Previous post was at 06:29 PM ----------
i have the folder on the desktop and no here the error
No such file or directory
---------- Post added at 06:57 PM ---------- Previous post was at 06:52 PM ----------
that's my name of the hd
cd/volumes/"Orville HD"/fastboot
---------- Post added at 07:02 PM ---------- Previous post was at 06:57 PM ----------
any one can help me i put the folder on desktop or in the hd and the commands not work

Hmm it might not be there by default.
If the fastboot folder is on your desktop use this:
cd /volumes/"Orville HD"/users/your-user-name/Desktop/fastboot

i got the key but when i paste the other key on terminal have a error

When you get your key from Terminal you need to compare it with the example key HTC have on their site, theres some stuff you need to remove on the left to make them look the same.
Copy it into the Textedit app to remove them then select the whole key and paste it into the HTC site.

got it have unlocked and clockword thanks

No problem, have fun

Thank you so much for a clear guide.

Might be worth mentioning that the official CW recovery is available in basic and touch formats from here: http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Great and concise guide, by the way. Hope this helps someone.

hmm i get permission denied even after sudo.. any ideas?

visor said:
Might be worth mentioning that the official CW recovery is available in basic and touch formats from here: http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Great and concise guide, by the way. Hope this helps someone.
Click to expand...
Click to collapse
please note that there is an error in the coding of device.id on the official CW recovery and any rom that uses the aroma installer will not work at present, that is the reason i have left my guide with the links to the interim

x.Orville.x said:
i have lion and i click it the folder and i don't see this
Services > New Terminal at Folder
Click to expand...
Click to collapse
Just for the records...to get the "services" option after you right click, go to system preferences and then select keyboard and then choose "services" on left there is a option on the right panel where you can check for the "new terminal at folder" (do not remember exactly where)
{
"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"
}
EDIT: Screenshot added

MrGarak said:
Terminal needs to be navigated to the same folder as the fastboot-mac file you extracted earlier, you can do this automatically in Lion (not sure about older versions) by right-clicking the folder and going to 'Services' then selecting 'New Terminal at Folder'.
You can navigate manually either by using the 'cd' command, for example:
cd /volumes/"OS X"/fastboot
Note the importance of quotes for a drive name with spaces.
You can also activate root before you do anything by typing sudo -s
Click to expand...
Click to collapse
I keep getting denied permission, even with the password, and "operation not supported." Is this guide for use in Snow Leopard or Lion?

DPI Changed and now no Boot!!!

Hey I changed my DPI settings to 180 and the Phone only shows the Google Screen with that lock Icon
and then turns black.
What can I do to revert this? can someone please help?

You did make backup before doing that RIGHT?

It had nothing too important that I needed on it. So no, I didn't

Well I would say just reflash your current ROM on top of your setup now. You should still be able to get into recovery just fine.

NYYFan325 said:
Well I would say just reflash your current ROM on top of your setup now. You should still be able to get into recovery just fine.
Click to expand...
Click to collapse
Unfortunately the .zip file isn't on the internal memory
I tried to mount the USB to transfer a .zip rom over
But it keeps saying
E:can't mount /sdcard/
is this normal? Did the internal memory get warped?
Could ODIN be used to help me out?
I shouldnt have gone along with this post I saw that suggested that 180 DPI would send the User Interface into "Tablet mode" because I really wanted the Notification/ Status Bar in the same bar as the on screen "Back, Home and Task" buttons
And that would have been the only mod that I have done. and look what happens.

throwback1718 said:
Unfortunately the .zip file isn't on the internal memory
I tried to mount the USB to transfer a .zip rom over
But it keeps saying
E:can't mount /sdcard/
is this normal? Did the internal memory get warped?
Could ODIN be used to help me out?
I shouldnt have gone along with this post I saw that suggested that 180 DPI would send the User Interface into "Tablet mode" because I really wanted the Notification/ Status Bar in the same bar as the on screen "Back, Home and Task" buttons
And that would have been the only mod that I have done. and look what happens.
Click to expand...
Click to collapse
If you go to the bootloader and redo the command fastboot oem lock and then fastboot oem unlock it will lock and unlock your boot loader also reformatting your scard. Once you do that go back to recovery and try putting the zip file on again

throwback1718 said:
Unfortunately the .zip file isn't on the internal memory
I tried to mount the USB to transfer a .zip rom over
But it keeps saying
E:can't mount /sdcard/
is this normal? Did the internal memory get warped?
Could ODIN be used to help me out?
I shouldnt have gone along with this post I saw that suggested that 180 DPI would send the User Interface into "Tablet mode" because I really wanted the Notification/ Status Bar in the same bar as the on screen "Back, Home and Task" buttons
And that would have been the only mod that I have done. and look what happens.
Click to expand...
Click to collapse
you cant mount the sd card because there is no sd card.
use adb
adb push locationofrom /data/meda

NYYFan325 said:
If you go to the bootloader and redo the command fastboot oem lock and then fastboot oem unlock it will lock and unlock your boot loader also reformatting your scard. Once you do that go back to recovery and try putting the zip file on again
Click to expand...
Click to collapse
My apologies... I literally just got this Nexus today. again, I was just trying to make a minor tweak...
Anyhow, I don't know too much about the phone. How is the command fastboot oem lock done?
I can't use the search button right now too much

It' s very simple to fix that, I asume that you did the "tweak" in /system/build.prop right? If so just boot into recovery, if you can't then use the GNex toolkit, once in recovery connect the phone to the computer and it should see your phone as an adb device, open from the toolkit a command prompt, start adb service and pull the modified build.prop to your computer then correct whatever you mess in it (DPI) and then push the fixed build.prop to the phone and finally your GNex will boot normally.
Sent from my Galaxy Nexus using xda premium

^^^ Actually I downloaded an app from the play store to do it... does this still apply to me ?
I'm mad at myself
Sent from my HERO200 using Tapatalk 2

throwback1718 said:
^^^ Actually I downloaded an app from the play store to do it... does this still apply to me ?
I'm mad at myself
Sent from my HERO200 using Tapatalk 2
Click to expand...
Click to collapse
Yes, because all that this app did is changed the value in your build.prop. What you want to do is go to this file and change ro.sf.lcd_density from 180 to 320, save and reboot.

ok I'm having difficulty here. I can't do any of the adb functions. Again like I said, I got this phone just yesterday. So drivers and such havent been installed. Apparently when using the toolkit to install the drivers to the computer, you need to enable USB debugging. Which I can't do. Because the phone isn't booting.
So is there a work around for this? Its the damn first step and I'm stuck already.
I literally haven't done anything to this phone. Clockworkmod was installed prior to me getting the phone, and so was Fastboot.
I have been looking online for Nexus USB drivers but its difficult .... Any suggestions?

Try this and see if you can install the drivers or if your pc detect the gnex: power off the phone, press and keep pressed volume down button while you turn on the phone, this should make you boot into fastboot or odin's mode I'm not pretty sure. Try it and let us know.
Sent from my Nook Tablet using xda premium

iferlive said:
Try this and see if you can install the drivers or if your pc detect the gnex: power off the phone, press and keep pressed volume down button while you turn on the phone, this should make you boot into fastboot or odin's mode I'm not pretty sure. Try it and let us know.
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse
It goes into download mode. With "ODIN" in the top left corner.
So doing this should substitute the fact that I can't enable USB debugging because I can't boot the phone?

Ok now I'm home and I have my laptop here so I can help you more efficiently, mi computer also didn't recognized my gnex in odin mode, lets try something else, turn off your phone, and connect it to your pc and wait until you hear the windows sound of "new device attached" if so then proceed with the installation of drivers vie the toolbox, once done that and if we have look toolbox should see your device, let me know what happens, and tell me what app did you use and what density you did set so I can recreate the event in my phone
---------- Post added at 07:44 PM ---------- Previous post was at 07:01 PM ----------
Oh I got it dude, so you have already installer CWM Recovery right? ok Here is the solution so you can have adb, I assume that you have already installed the drivers wich is so simple and you don't need the phone to do that, turn off your phone and press volume up and volme down buttons keep them pressed while pressing the power button "KEEP ALL PRESSED" and you will boot into FASTBOOT Mode, if the installation of the driver was correctly made the ToolBox will detect your device in FastBoot (I recommend you to reboot your computer if it didn't recognize the phone), then use the volume keys to select "Recovery Mode" and press the power button, this will make your GNex boot into CWMR! wich means that you can use adb commands (CWMR has natively adb enabled) your pc should recognize the new device and prepare the drivers, after this just refres the ToolBox screen with option 25 and you will see your device number in the list of adb devices.
Ok once done that (that tricky part) in the ToolBox select option 14 adn select "no" to the secure image cuestion, this will reboot your phone, now put this do download the build.prop "/system/build.prop" with no quotes and hit "enter"
Now go to the ToolBox installation folder and go into the folder caller "pulled_files_are_put_here" ther will be your GNex build prop, open it with a text editor (WordPad) and edit this entry: ro.sf.lcd_density=320 you mess with this value so lets restore it to the default one which is 320, save the file.
Now move the recently corrected build.prop to the folder called "put_files_to_push_here" which is in ToolBox installation folder, and in the ToolBox windows select option 13, now put build.prop as the name of the file to push, it will say "file found" and nos put the directory where it goes which is: /system/
Reboot
And Voila! your GNex should now boot normally.
Good Look man, let me know if you could do it.

1) Reboot your device in CWM and plug into you computer.
2) Install these drivers. If you don't know how, have a read here.
3) Download the adb files from here and unzip them in to a directory.
4) Open a command prompt in that same directory.
5) In the menus on your device in CWM, mount /system.
6) In the command prompt, type: adb pull /system/build.prop
7) Open that file in a text editor and change the line that starts with ro.sf.lcd_density to have a value of 320. Close and save it.
8) In the command prompt, type: adb push build.prop /system/
9) In the command prompt, type: adb shell chmod 644 /system/build.prop
10) Reboot.

iferlive said:
Ok once done that (that tricky part) in the ToolBox select option 14 adn select "no" to the secure image cuestion, this will reboot your phone, now put this do download the build.prop "/system/build.prop" with no quotes and hit "enter"
And Voila! your GNex should now boot normally.
Good Look man, let me know if you could do it.
Click to expand...
Click to collapse
Stuck at this part. The phone tried to reboot and it didnt... Just black screen It kept saying "Waiting for adb Mode"
{
"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 it still does now. what now? I unplugged and went back to CWM but it still says waiting for adb mode.
Thanks for being patient with me BTW

efrant said:
1) Reboot your device in CWM and plug into you computer.
2) Install these drivers. If you don't know how, have a read here.
3) Download the adb files from here and unzip them in to a directory.
4) Open a command prompt in that same directory.
5) In the menus on your device in CWM, mount /system.
6) In the command prompt, type: adb pull /system/build.prop
7) Open that file in a text editor and change the line that starts with ro.sf.lcd_density to have a value of 320. Close and save it.
8) In the command prompt, type: adb push build.prop /system/
9) In the command prompt, type: adb chmod 644 /system/build.prop
10) Reboot.
Click to expand...
Click to collapse
I was looking at the instructions on installing those drivers and it appears that it requires that the phone be on and booted into Android.
I can't do that because I get no further than the black screen.

Don't panic I'm writing a new possible solution wait a few minutes

throwback1718 said:
I was looking at the instructions on installing those drivers and it appears that it requires that the phone be on and booted into Android.
I can't do that because I get no further than the black screen.
Click to expand...
Click to collapse
It can be booted in CWM instead. It makes no difference.
Sent from my Galaxy Nexus using Tapatalk 2

Simple guide to ADB/Fastboot

I've noticed an increase of users "bricking" their handsets. I use the term "bricking" in the slightest sense, as to them, it is bricked.
The main cause is simply a lack of background knowledge & experience with ADB & Fastboot, I've also noticed that the very helpful guides to recover handsets from this "bricked" state, have an assumption that the users know basic things such as using ADB/Fastboot & cmd. The very things that caused the "brick" in the first place.
Here I'm going to throw together a crash course in the very basics of ADB/Fastboot and how to implement them into your system so that they work all the time and from anywhere on your system. Then an example on how to flash a ROM.
Ensure that USB debugging is enabled on your handset. On HTC Sense it can be found under Settings > Developer Options > Check USB Debugging.
Step One - Download ADB & Fastboot - HERE
Step Two - Extract this to a folder on your C:\ - e.g. "C:\ADB"
Step Three - Add this location to your System PATH - This is important as it makes things a lot easier later
Control Panel > System > Advanced System Settings > Environment Variables...
At the bottom "System Variables" scroll down and find "Path", Click it then "Edit..."
Add to the end of the line named "Variable Value:" ";C:\ADB\" - Try not to delete anything previously in there, the ; is needed, just omit the quotes "".
Hit Ok on the menus and go back to your desktop.
Step Four - Reboot your system or just log out and back in.
Here is a image guide to follow.
{
"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"
}
-
-
Adding ADB & Fastboot to your System PATH allows you to run the commands adb & fastboot from anywhere in your system. Normally the guide you'd follow would say,
cd into fastboot folder
Click to expand...
Click to collapse
Now you don't need to.
Example usage.
You download a new ROM (CM10) plus GApps & the boot.img from the relevant thread. You copy the ROM & GApps from your computers download folder to your handset. Unmount USB storage and you do the following, making sure that your handset is still plugged in.
Open your computers default download folder.
Shift + Right Click > Open command window here
Type the following
adb devices > Serial Number should be printed
adb reboot bootloader > Device reboots into HBOOT, Fastboot is automatically selected.
fastboot devices > Serial Number should be printed again
fastboot flash boot boot.img > boot.img is sent and flashed, easy. Sometimes the boot.img maybe named different, just start typing and hit TAB, should autocomplete.
fastboot erase cache > not always needed, better being safe
Press the power button on your handset to enter HBOOT, then navigate to RECOVERY and press power.
In Recovery, make your backups as per, and wipe & flash the ROM + GApps, then reboot normally.
Profit
If you still do not understand what you are doing, don't do it. You would not attempt to change a head gasket in your cars engine, unless you knew and understood what you were doing. If you are unsure, search, read & ask until you know what your doing. Sometimes what I write looks too clinical so here's a :cyclops: smiley to lighten the post.

Andy said:
I've noticed an increase of users "bricking" their handsets. I use the term "bricking" in the slightest sense, as to them, it is bricked.
The main cause is simply a lack of background knowledge & experience with ADB & Fastboot, I've also noticed that the very helpful guides to recover handsets from this "bricked" state, have an assumption that the users know basic things such as using ADB/Fastboot & cmd. The very things that caused the "brick" in the first place.
Here I'm going to throw together a crash course in the very basics of ADB/Fastboot and how to implement them into your system so that they work all the time and from anywhere on your system. Then an example on how to flash a ROM.
Ensure that USB debugging is enabled on your handset. On HTC Sense it can be found under Settings > Developer Options > Check USB Debugging.
Step One - Download ADB & Fastboot - HERE
Step Two - Extract this to a folder on your C:\ - e.g. "C:\ADB"
Step Three - Add this location to your System PATH - This is important as it makes things a lot easier later
Control Panel > System > Advanced System Settings > Environment Variables...
At the bottom "System Variables" scroll down and find "Path", Click it then "Edit..."
Add to the end of the line named "Variable Value:" ";C:\ADB\" - Try not to delete anything previously in there, the ; is needed, just omit the quotes "".
Hit Ok on the menus and go back to your desktop.
Step Four - Reboot your system or just log out and back in.
Here is a image guide to follow.
-
-
Adding ADB & Fastboot to your System PATH allows you to run the commands adb & fastboot from anywhere in your system. Normally the guide you'd follow would say,
Now you don't need to.
Example usage.
You download a new ROM (CM10) plus GApps & the boot.img from the relevant thread. You copy the ROM & GApps from your computers download folder to your handset. Unmount USB storage and you do the following, making sure that your handset is still plugged in.
Open your computers default download folder.
Shift + Right Click > Open command window here
Type the following
adb devices > Serial Number should be printed
adb reboot bootloader > Device reboots into HBOOT, Fastboot is automatically selected.
fastboot devices > Serial Number should be printed again
fastboot flash boot boot.img > boot.img is sent and flashed, easy. Sometimes the boot.img maybe named different, just start typing and hit TAB, should autocomplete.
fastboot erase cache > not always needed, better being safe
Press the power button on your handset to enter HBOOT, then navigate to RECOVERY and press power.
In Recovery, make your backups as per, and wipe & flash the ROM + GApps, then reboot normally.
Profit
Click to expand...
Click to collapse
This is what i was looking for. I am just about to flash a ROM in a HTC vivid S-ON and i need it to flash the kernel manually.
Thank you. :cyclops:

Can you boot into recovery with a fast boot command?
Sent from my HTC One X using xda app-developers app

Tw1tchy said:
Can you boot into recovery with a fast boot command?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Fastboot works in the bootloader
ADB works in the running OS and the recovery
So fastboot reboot recovery will work in the bootloader, adb reboot recovery works in the running OS and inside the recovery (if you want to reboot it for some reason when you are already in)

Unfortunately there is no fastboot command (AFAIK) to reboot into recovery from fastboot directly. Your only fastboot reboot options are
fastboot <command>
Code:
reboot
reboot-bootloader

Andy said:
Unfortunately there is no fastboot command (AFAIK) to reboot into recovery from fastboot directly. Your only fastboot reboot options are
fastboot <command>
Code:
reboot
reboot-bootloader
Click to expand...
Click to collapse
Ah my mistake , sorry mate. So it only apply to adb .
Thanks

Mr Hofs said:
Ah my mistake , sorry mate. So it only apply to adb .
Thanks
Click to expand...
Click to collapse
if you are in ADB
"
adb reboot bootleader
adb reboot recovery.
"
but if you are in fastboot you need to navigate to recovery option using the vol up and vol down keys and power on recovery.

:facepalm:
and i was wondering why fastboot write: waiting for device, of course if i use fastboot instead adb to try to reboot my phone in OS
i had forgotten...

Hi Im desperatte trying to root my ATT HTC ONE X with 1.5 using this method http://forum.xda-developers.com/showthread.php?t=1709296
I found this tutorial and I dont know if could work.
I have one big question: After i extracted the file in step one I get a folder named fastboot, instead en adb folder U mentioned in step 2
Im feeling stupid asking so basic things but I prefer to ask and not cry later
Thanks

ErnestoD said:
Hi Im desperatte trying to root my ATT HTC ONE X with 1.5 using this method http://forum.xda-developers.com/showthread.php?t=1709296
I found this tutorial and I dont know if could work.
I have one big question: After i extracted the file in step one I get a folder named fastboot, instead en adb folder U mentioned in step 2
Im feeling stupid asking so basic things but I prefer to ask and not cry later
Thanks
Click to expand...
Click to collapse
No worries, mate. Fastboot folder contains both fastboot and adb commands, so all you have to do is open command prompt in it (something like C:/fastboot/) and then type commands.
Beforehand, you must have htc drivers installed, and the phone connected, of course.
Also, beware that this forum is for International One X with Tegra 3, so be careful with instructions found here.

Thanks man.
I undestood what u said.
My problem is with the fisrt command I should write in the root proccess: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
I copied SU as stated, then typed adb shell and then rm /data/data/com.redbend.vdmc/lib/libvd* . here I get notification about missin file or folder.
The thread Im in is: http://forum.xda-developers.com/showthread.php?t=1709296
Do U understant what should I do or. If Im missing something
Thanks
[email protected]|-|oR said:
No worries, mate. Fastboot folder contains both fastboot and adb commands, so all you have to do is open command prompt in it (something like C:/fastboot/) and then type commands.
Beforehand, you must have htc drivers installed, and the phone connected, of course.
Also, beware that this forum is for International One X with Tegra 3, so be careful with instructions found here.
Click to expand...
Click to collapse

Where did you extract your fasboot/adb commands? Is SU in the same folder? Where do you open your command prompt?
Again, I'm no expert in AT&T One X, but fastboot/adb should be the same.
I suggest you open Windows Explorer, go to your fastboot/adb folder, press SHIFT, and right click your mouse.
Select "Open command window here".
Then type "adb devices" (make sure your phone is connected with USB cable, and USB debugging is turned on).
If adb sees your phone that's good.
Type dir and see if SU inside the folder.
Then follow the steps you should.
I hope this helps.

yes It has worked . Thanks man.
So now I know Im at least oriented. Lets see If I receive more help in the root thread Im talking about.
Thanks one more time
[email protected]|-|oR;40510609]Where did you extract your fasboot/adb commands? Is SU in the same folder? Where do you open your command prompt?
Again, I'm no expert in AT&T One X, but fastboot/adb should be the same.
I suggest you open Windows Explorer, go to your fastboot/adb folder, press SHIFT, and right click your mouse.
Select "Open command window here".
Then type "adb devices" (make sure your phone is connected with USB cable, and USB debugging is turned on).
If adb sees your phone that's good.
Type dir and see if SU inside the folder.
Then follow the steps you should.
I hope this helps.[/QUOTE]

It's alright, mate. That's the whole spirit of XDA.
Take care of you and of your One X, mate! :good:

Thanks
Woot Saved me
Thanks

[Q] Can't figure out how to flash CWM via Mac OS X

Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks

Orange_furball said:
Hello everyone, I have an OUYA and I really want to get CyanogenMod on it. The first step is obviously CWM. I have tried flashing via this method http://forum.xda-developers.com/showthread.php?t=2295645 on my Windows 7 PC, I get the error message "no device found" every time, tried numerous drivers, nothing worked. So I decided to try it out on my Mac. Well its still not working. I run the .sh file and nothing happens.
My question is, how do I do this?
Im kinda new to terminal on Mac OS X, and I've barely used it in Linux, so I think I need some help here :/ I hope someone has advice.
Thanks
Click to expand...
Click to collapse
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel

Re-Mi said:
hmm,
On my MBP the script worked,
Did you navigated to the folder with the terminal ? (i'm also not a terminal hero ) and run the script ?. with Osx the "dir" fuction is "ls" so you can see the folders. Navigate to the specific MacOSX folder and with the Ouya and your MAc connected, type ./adb devices (with the ./). It should give you a line with "List of devices attached " and the line below that a long number that stands for your ouya.
Sometimes i had to do this twice or three times for the ouya to show up. If the ouya showes up. Then run type ./InstallOuyaCWMRecovery.sh (with the ./). It should work that way.
Greetz,
Michel
Click to expand...
Click to collapse
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
{
"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"
}
Ps: I'm not Paul.. The guy I bought this Mac off of left his info and I never took the time to take t off..

Orange_furball said:
I think I'm royally failing. I can't even access my downloads directory and ./adb devices renders no results
Click to expand...
Click to collapse
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file

Re-Mi said:
ok when first entering the terminal type
Code:
cd \
(then enter, you will see a > enter again)
then type
Code:
ls
( its an L )
you can scroll up but i'm pretty sure there is a folder "Downloads" to get into this folder you have to type (just like windows)
Code:
cd Downloads
As i'm not a terminal hero also i type everything Cap sensitive (this way i know it works)
do the "ls" and "cd" commands until you reach the downloaded folder and you are into the MacOSX folder, then do the
Code:
./adb devices
and if you mac sees the ouya then run the bash file
Click to expand...
Click to collapse
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/

Orange_furball said:
I feel like I'm so close! Thank you! But my Mac doesn't see the OUYA in devices attached :/
Click to expand...
Click to collapse
I pm-ed you.

Re-Mi has helped me solved my issue! Thank you so much!

Here is more detail on what I did, First of all I followed Re-Mi's instructions. Here they are:
So first things first Root
http://forum.xda-developers.com/show....php?t=2387507
Sideload the app and run the apk
second install the xposed installer (latest apk file at the end of the first post) make sure it's installed (Launch the Xposed Installer and click on "Install/Update" ,Reboot ,Done!)
http://forum.xda-developers.com/show....php?t=1574401
Then install mod collection for Ouya and install CWM from there
http://forum.xda-developers.com/show....php?t=2359390
It's a long detour but i think it will work. After that just install stockplus rom and you got everything you wanted (otherwise you would not even bother to install cwm )
Click to expand...
Click to collapse
Now let me go into more detail. What you do is type the first link into your OUYA's web browser (It is under Make>Software>Web Browser I believe) Then download the file. Now go to Manage>Settings>Advanced>Storage>Downloads and hit the file you just downloaded. Install that APK, hit open, then hit root. Now accept the SU request. After this is done repeat the steps until you have the other file downloaded. Now install that APK for the Xposed Installer and hit "Install/Update" then reboot. Now download the mod collection from the third link.
Install it and install CWM from there. It will take you to a download link, wait a few seconds, then hit install CWM again. Now it'll be installed.
Plug your Ouya into your computer, If its a Mac you will need the program from www.android.com/filetransfer . If its Windows you wont need that. Go in XDA and download whatever ROM tickles your fancy. Drag and drop that into your Ouya's storage. Now on the Ouya reboot to recovery (Via the Mods app)
Now im CWM hit the install zip from SD card, select the .zip of the ROM you chose, and install. Now wait until its all done, reboot, and enjoy!
*IF YOUR OUYA GETS BRICKED, NEITHER I NOR RE-MI NOR ANYONE EXCEPT YOURSELF ARE RESPONSIBLE!*
Good luck! If this helps be sure to thank Re-Mi!!!