Related
Hello guys, as the title says..
I am unable to access a Custom Recovery Image, even though I'm rooted and have been for some time. I use ROM Manager, and recently attempted to flash a new Recovery (updated Clockwork) which didn't install, and then I tried to access the Custom Recovery to update a ROM, which didn't work, as it just went to the normal Android Recovery, highly annoying.
So I thought I'd try to access HBOOT screen, that also didn't work (when I did the button combinations), and then thought I'd access ClockwordMod Recovery via the button combination, that also didn't work.
I originally rooted my phone before Unrevoked was available for the Desire, which, I must've done it in a way in which CMR was never available when using the Recovery Image button combination from Hardboot, so I always used ROM Manager, which worked perfectly fine until today.
Any advice on how to do this? Is it possible to ADB Push the Custom Recovery Image and always have it there? It's quite frustrating in all fairness.
I'm now running Oxygen 2.0 RC3.
Dan
What happens exactly when you fail to access your custom recovery via the bootloader screen? Do you receive any errors? Have you tried re-installing ROM Manager or tried an older recovery image?
If all else fails, try flashing AmonRa recovery with unrEVOked.
Sent from my HTC Desire using XDA App
I've tried to push AmonRa with Unrevoked, and that didn't work either.
I've tried to uninstall ROM Manager and reinstall it and that didn't work, and tried to flash Clockworkmod Recovery, that also didn't work.
I don't get any errors, I just get to the Android Recovery Screen, with the Red Triangle.
from what i understand is that you are fake flashing everytrime that you use your recovery. i would recommend that you backup all your data and keep them in safe place. as long as you cannot boot into fastboot i cannot recommend you to do s-off(if fastboot was working you could try for s-off and after try to fkash recovery through fastboot). the only thing is to use an unbranded RUU and start over by using unrevoked to root and flash custom recovery(i suggest AmonRa's for the Desire) than you can restore your backed apps after flashing the desireable rom.
for the record if you boot into fastboot by pressing back button+Power on, does it go there? and if it does not go can you tell me what it say?
bigdan35 said:
I've tried to push AmonRa with Unrevoked, and that didn't work either.
I've tried to uninstall ROM Manager and reinstall it and that didn't work, and tried to flash Clockworkmod Recovery, that also didn't work.
I don't get any errors, I just get to the Android Recovery Screen, with the Red Triangle.
Click to expand...
Click to collapse
Yes, I can only use fake-flash to do everything now which gets quite annoying. I was thinking about doing that, just installing an unbranded RUU and kind of sorting my phone out fresh, which gives me a chance to partition my SD card again without having the "Format SD Card" option every time I plug my phone in.
Having the same issue here. Any clues yet on what happened?
bigdan35 said:
Yes, I can only use fake-flash to do everything now which gets quite annoying. I was thinking about doing that, just installing an unbranded RUU and kind of sorting my phone out fresh, which gives me a chance to partition my SD card again without having the "Format SD Card" option every time I plug my phone in.
Click to expand...
Click to collapse
Revert back to stock with the RUU for your phone and run unrEVOked again
Hi, sorry to ask again, i've run through a lot of tread and still cant find the answer...
i have almost similar problem, i can get access to HBOOT menu if i connect the phone through PC and removed the battery, but it only said RUU, not hboot, fastboot, recovery and usual menu... why...???
if i didnt removed the battery or start normally, i only get grey HTC logo with black background and /!\ on all the corner...
so now i can't get access to HBOOT, recovery or os, i've try to get a gold card, but adb cannot read my phone (maybe because i cant access fastboot)... GoldCardTool also didnt work...
i've ask several people, but they keep asking me to look again into all the tread available... at lease tell me what should i look for please... its been a week already...
HTC Desire (ojan) said:
Hi, sorry to ask again, i've run through a lot of tread and still cant find the answer...
i have almost similar problem, i can get access to HBOOT menu if i connect the phone through PC and removed the battery, but it only said RUU, not hboot, fastboot, recovery and usual menu... why...???
if i didnt removed the battery or start normally, i only get grey HTC logo with black background and /!\ on all the corner...
so now i can't get access to HBOOT, recovery or os, i've try to get a gold card, but adb cannot read my phone (maybe because i cant access fastboot)... GoldCardTool also didnt work...
i've ask several people, but they keep asking me to look again into all the tread available... at lease tell me what should i look for please... its been a week already...
Click to expand...
Click to collapse
you just flashed the wrong RUU and now your phone is in RUU mode (can access it through "adb shell reboot oem-78" if anyones interested), all you need to do is flash the correct RUU.
If you don't know which RUU is right for you, then you will need to make a goldcard so you can just flash the latest WWE RUU
to make a goldcard, turn on your phone and plug into usb (yes I know your phone shows triangles, ignore them, you're still in fastboot)
then type:
Code:
fastboot oem gencheckpt
This will boot you into recovery if it's there
wait for about 20 seconds, and type:
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1*/cid
NOTE: if this command doesn't work, then I can't help you.. I'd suggest trying again, maybe you didn't wait long enough for recovery to start.. or maybe recovery isn't even there anymore.
this will give you a series of letters and numbers. Copy them down VERY CAREFULLY. Once you've got that, follow this guide on making a goldcard.
Once you've done that. Flash this RUU, and you should be done.
bortak said:
you just flashed the wrong RUU and now your phone is in RUU mode (can access it through adb shell reboot oem-78 if anyones interested), all you need to do is flash the correct RUU.
Click to expand...
Click to collapse
i didnt remember i've flash RUU before, by the way, how i can flash RUU if i cant get access to hboot, fastboot or recovery... should i take RUU here...???
http://shipped-roms.com/index.php?category=android&model=Bravo
really hope you can assist me all the way bortak... i got to stay awake just to have a chat (different time zone)...
I posted the whole process for you.. when you've got the goldcard plug your phone in via usb and run the RUU from your PC, it will do it... you are in fastboot mode.. just fastboot RUU.
bortak said:
you just flashed the wrong RUU and now your phone is in RUU mode (can access it through "adb shell reboot oem-78" if anyones interested), all you need to do is flash the correct RUU.
If you don't know which RUU is right for you, then you will need to make a goldcard so you can just flash the latest WWE RUU
to make a goldcard, turn on your phone and plug into usb (yes I know your phone shows triangles, ignore them, you're still in fastboot)
then type:
Code:
fastboot oem gencheckpt
This will boot you into recovery if it's there
wait for about 20 seconds, and type:
Code:
adb shell cat /sys/class/mmc_host/mmc1/mmc1*/cid
NOTE: if this command doesn't work, then I can't help you.. I'd suggest trying again, maybe you didn't wait long enough for recovery to start.. or maybe recovery isn't even there anymore.
this will give you a series of letters and numbers. Copy them down VERY CAREFULLY. Once you've got that, follow this guide on making a goldcard.
Once you've done that. Flash this RUU, and you should be done.
Click to expand...
Click to collapse
where i should type "fastboot oem gencheckpt"...???
HTC Desire (ojan) said:
where i should type "fastboot oem gencheckpt"...???
Click to expand...
Click to collapse
in cmd.. I take it that you have android-sdk installed?
if not, just unzip the attached file into your C:\
and then type:
Code:
cd\
fastboot oem gencheckpt
then continue with the guide from the previous post.
EDIT: if you don't know how to open cmd, it can be found under "accessories" in the start menu, and it's called "command prompt"
bortak said:
in cmd.. I take it that you have android-sdk installed?
if not, just unzip the attached file into your C:\
and then type:
Code:
cd\
fastboot oem gencheckpt
then continue with the guide from the previous post.
EDIT: if you don't know how to open cmd, it can be found under "accessories" in the start menu, and it's called "command prompt"
Click to expand...
Click to collapse
ok, i've done that, but something like this pop out...
"This application has failed to start because ADBWinApi.dll was not found. Re-installing the application may fix this problem"
Should i re-install android SDK...???
HTC Desire (ojan) said:
ok, i've done that, but something like this pop out...
"This application has failed to start because ADBWinApi.dll was not found. Re-installing the application may fix this problem"
Should i re-install android SDK...???
Click to expand...
Click to collapse
yes, seems as if you don't have it... I'm pretty sure I gave you a link somewhere in those posts
okay maybe not. Here it is http://developer.android.com/sdk/index.html you don't need to worry about downloading all the revisions.. the only things you're interested in is the tools
bortak said:
yes, seems as if you don't have it... I'm pretty sure I gave you a link somewhere in those posts
okay maybe not. Here it is http://developer.android.com/sdk/index.html you don't need to worry about downloading all the revisions.. the only things you're interested in is the tools
Click to expand...
Click to collapse
yes you has gave me that link, thanks... but i didn't know how to use it... and i've installed it to my PC (it takes 5-7 hours of downloading package and installing package)... if i re-install, it surely will take another 5-7 hours...
errrmmm.... okay, go to C:\android-sdk\platform-tools and run "adb.exe", then try again
bortak said:
errrmmm.... okay, go to C:\android-sdk\platform-tools and run "adb.exe", then try again
Click to expand...
Click to collapse
something like this pop out
C:\>android-sdk-windows\platform-tools\adb
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devic
es.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
alright well adb seems to be running then try the command to get the CID then...
bortak said:
alright well adb seems to be running then try the command to get the CID then...
Click to expand...
Click to collapse
sorry, but how i can get the CID...???
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?
Looking through the menus in my ICS i've noticed the option to set "Desktop Backup Password" and thought to myself - "Well, How odd... Android does not have any desktop backup solution built in..."
It took some digging since there wasn't a lot of information online - but I ended up stumbling upon this page:
http://www.tested.com/news/feature/...-data-from-your-galaxy-nexusno-root-required/
As it turns out - Google created a mechanism in ICS to create full desktop backups for apps, data and even system apps, without the need to have the device rooted.
Keep in mind this only works on Ice Cream Sandwich... So don't ask me if this will work on GB based ROMS... It WON'T.
Make sure you have a recent version of ADB on your machine, go to the developer menu, set-up a password, and then use adb with the following syntax to create a backup of your system (taken directly from ADB's help):
Code:
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>]
-f <file> (write an archive of the device's data to <file>. If no -f option is supplied then the data is written to "backup.ab" in the current directory.)
-apk|-noapk enable/disable backup of the .apks themselves in the archive; the default is noapk.)
-shared|-noshared (enable/disable backup of the device's shared storage / SD card contents; the default is noshared.)
-all (means to back up all installed applications. This will include SD-Card backup)
-system|-nosystem (toggles whether -all automatically includes system applications; the default is to include system apps)
<packages...> (is the list of applications to be backed up. If the -all or -shared flags are passed, then the package list is optional. Applications explicitly g
iven on the command line will be included even if -nosystem would ordinarily cause them to be omitted.)
I hope this proves helpful to some of you...
This is awesome i had been wondering if google was going to release a backup tool
Thanks man
Don't have adb yet but I will after reading this, great find.
Sent from my SPH-D710 using XDA
Do you know how you would go about restoring the backup once its created?
apeironer said:
Do you know how you would go about restoring the backup once its created?
Click to expand...
Click to collapse
you would also use adb to restore...
syntax:
adb restore <file>
where <file> is, of course, the name of the backup file...
adb requires root, however
This looks like a neat idea, however installing adb itself, requires root, making this somewhat moot.
Does anyone know of an app or method to do a full Android backup to desktop (Mac, Linux or if necessary Windows) which does not require root in any way, so I can completely factory-wipe my carrier-provided Galaxy Note II and restore it, and be back up in running in minutes?
desrod said:
This looks like a neat idea, however installing adb itself, requires root, making this somewhat moot.
Does anyone know of an app or method to do a full Android backup to desktop (Mac, Linux or if necessary Windows) which does not require root in any way, so I can completely factory-wipe my carrier-provided Galaxy Note II and restore it, and be back up in running in minutes?
Click to expand...
Click to collapse
ADB does NOT require root.
You are limited to the things you can do with ADB when then phone is not rooted - you will not be able to work with the system folders, but you should still be able to create the backup.
Just make sure you go to Settings > Developers Settings, and enable Android Debugging.
Let me know if it works.
Exactly what I was looking for.
Thank You!
for noobs
Just enable developer options, enable USB debug mode, create a desktop full backup password, revoke USB debug authorizations, install ADB on your PC (link below), open CMD and cd to the folder and run "adb start-server" then "adb backup -all"... it will create a backup file in that folder (mine was 200MB) called backup.ab.
https://developer.android.com/studio/releases/platform-tools.html
Anyone using this in 2023? What are the downsides, how does it compare to Google Cloud Backups?
EDIT: okay, that explains why it's not mentioned anymore
% adb backup -all
WARNING: adb backup is deprecated and may be removed in a future release
Now unlock your device and confirm the backup operation...
EDIT2: my backup is only 7MB... doesn't seem right? What's in there?
hi
I have installed galaxy nexus toolkit . It has option of backing up my phone and I was going through few posts which allows me to backup via ADB . I have few questions regarding this.
1. Are two methods I mentioned (via toolkit and ADB different?
2. If I backup and then do restoration , will the state of my app will be restored ? Like Game scores or levels passed ?
Thanks
I would advise you to drop the toolkit, and follow this (http://forum.xda-developers.com/showthread.php?t=1830108) guide. It'll require you to install adb and fastboot, so you will be in complete control of your device and will also empower you to fix anything which *may go wrong.
To actually answer your question, 1. yes the toolkit just inputs the adb backup command for you and 2. yes that is usually the meaning of the word backup... (some apps like cut the rope do however check whether it's the same installation, and these will ignore data that have been copied directly)
But please take the time to install adb yourself and get comfortable with the commands yourself, that way you will also be able to fix any problems that may arise yourself.
Drop the toolkit.
and there is a nandroid function on the toolkit, will be a better option......................................
And once again, drop the toolkit..
http://forum.xda-developers.com/showthread.php?t=1812959
re
adb backup -apk -noshared -all -nosystem
I am trying this command to backup my app data . But it is not working it just list all the commands available. My Adb is installed perfectly . Because SD card PULL command worked
adithyavr said:
adb backup -apk -noshared -all -nosystem
I am trying this command to backup my app data . But it is not working it just list all the commands available. My Adb is installed perfectly . Because SD card PULL command worked
Click to expand...
Click to collapse
you forgot to name your backup file, which is done by the paramater -f
Code:
adb backup -f C:\name_of_your_backup.ab -apk -noshared -all -nosystem
you can name the output anything you like and put it to any folder you desire. just specify those after "-f" . don't forget to enable usb debug in your phone and i would recommend to check "stay awake" as well during the procedure.
i tried with the exact code "adb backup -f C:\name_of_your_backup.ab -apk -noshared -all -nosystem" but it still just lists all the commands there. For some reason it is not recognizing the command . It did for pull .
Funny thing is in that complete listing I cannot see backup command anywhere ? this might help but I installed adb AIO which was available . Can that cause problem ?
adithyavr said:
i tried with the exact code "adb backup -f C:\name_of_your_backup.ab -apk -noshared -all -nosystem" but it still just lists all the commands there. For some reason it is not recognizing the command . It did for pull .
Funny thing is in that complete listing I cannot see backup command anywhere ? this might help but I installed adb AIO which was available . Can that cause problem ?
Click to expand...
Click to collapse
what version of adb do you have? check with command "adb version". you need adb version 1.0.29 or newer to have adb backup and restore function.
btw, if you have the toolkit from mskip, adb has been renamed to adb-toolkit and that one is at least 1.0.29 as i recall.
oh mine is adb 1.0.26 . Can you guide me to the proper adb download . Also if I install android sdk , will I get the adb ?
adithyavr said:
oh mine is adb 1.0.26 . Can you guide me to the proper adb download . Also if I install android sdk , will I get the adb ?
Click to expand...
Click to collapse
you can grab the latest version from google. it's a big download (~390Mb) so if you only need adb or fastbook then i would just use those bundled with the galaxy nexus toolkit. unzip the downloaded file to anywhere you like, and the adb command can be found in sub-folder "platform-tools". that's all you need.
adb backup -f C:\backone.ab -apk -noshared -all -nosystem
I downloaded the latest ADB it did back up perfectly .but in C:\ there is no file called backone.ab
adithyavr said:
adb backup -f C:\backone.ab -apk -noshared -all -nosystem
I downloaded the latest ADB it did back up perfectly .but in C:\ there is no file called backone.ab
Click to expand...
Click to collapse
nothing comes up if you type the following in your computer?
Code:
dir c:\ /a:h
i can only speculate that windows recognise ".ab" file as system file and hide it. you can name your backup with any extension you like, and people often use ".bak" instead. output your backup to a folder instead of the root direction may also help (-f c:\backup\whatever_name_you_called.bak, for example).
I searched my system and found out that it is stored in Local/AppData i wonder why. Btw , I just unlocked my device . It said said it will wipe my data out . But surprisingly my device is still with same theme and apps . Had no factory reset done !. I have double checked in the fast boot and it shows my phone status as unclocked
Latest ADB and fastboot, sort of, at least i know the one i included supports adb backup..
https://www.dropbox.com/sh/p1wn5ywy6bd14hb/MvP3wpoNfx?m
adithyavr said:
Btw , I just unlocked my device . It said said it will wipe my data out . But surprisingly my device is still with same theme and apps . Had no factory reset done !. I have double checked in the fast boot and it shows my phone status as unclocked
Click to expand...
Click to collapse
This is known to happen with devices bought directly from the Google Play Store. To the best of my knowledge no one ever figured out why.
LOL
Sent from my i9250
bk201doesntexist said:
LOL
Sent from my i9250
Click to expand...
Click to collapse
Why lol ? What's so amusing ?
Sent from my Galaxy Nexus using xda app-developers app
bk201doesntexist said:
LOL
Sent from my i9250
Click to expand...
Click to collapse
I LOL'd
I'm trying to use ADB Backup and Restore, but when I try it I receive " Now unlock your device and confirm the backup operation."...however, nothing shows on the screen. Normally, a confirmation window displays on my phone, but nothing on the firestick.
I've tried single and double quotes, but nothing:
adb backup appname.ab -f com.app.com
adb backup 'appname.ab -f com.app.com'
adb backup "appname.ab -f com.app.com"
I'm trying to backup some app data and add it to another firestick, but running into some trouble. It isn't Kodi, but it is from a sideloaded app if that helps with more information.
Any ideas would be greatly appreciated! Thanks