I was using a Mi Note 3g and it has gone into a soft brick and i cannot open the recovery mode. I need to extract my app data from the internal storage. Someone mentioned ADB to me and I have managed to make the phone be read in the list of devices attached when i enter "adb devices" command
I just need the commands to go on further from here,
I tried adb backup but it apparently needs permission from the phone.
I also tried adb pull, but I dont know the exact directories to pull. It only shows a skipping a bunch of files with no files pulled. A 0 kb .ab file is created in my local directory.
I have bought a new device so I dont exactly have any use for the Note 3g, just need to extract the data. The device is rooted, has developer and ADB permissions granted.
Related
Sorry about the post but I cannot find the post were it tells me how to install custom boot animations. I also need to be able to do the sounds. As far as I understand I have to put it in the media folder. I found the original one but it does not allow me to move it. I'm assuming I have to do it from recovery but I don't know how. Detailed instructions would be appreciated. I have a cold and the old brain is doing so well. Thanks
s-off your dinc and you can do it while booted
I was trying to avoid that because they do not have a way to undo s-off yet. Just incase my phone dies I dont want verizon to say I voided the warranty. Any way to do it without?
You can flash some of them from rom manager...that's how I did mine.
If you have rooted your phone, which you must have in order to install a custom ROM, you've already voided your warranty.
Adding S-OFF wouldn't change anything in the eyes of Verizon, and you can always drop your phone until it's physically broken if you need to take it in.
rom manager -> download rom -> Ihtfp69 -> boot animations -> download -> pick one
thats where i got mine from
MMBosstones86 said:
rom manager -> download rom -> Ihtfp69 -> boot animations -> download -> pick one
thats where i got mine from
Click to expand...
Click to collapse
When I try to install from Rom manager it doesn't load it says verification failed or something. Does anyone know how to manually install Droid 2 boot screen.
HTC incredible
SR sense 2. 5. 2
Radio 2. 15
Sent from my ADR6300 using XDA App
Did mine 'manually', since I'm rooted I have clockwork mod installed.
1. Boot into recovery (clockwork mod)
2. launched android SDK adb daemon
3. moved file from 'tools' folder of sdk to the proper destination on the phone.
4. Done.
Doctor Butts said:
Did mine 'manually', since I'm rooted I have clockwork mod installed.
1. Boot into recovery (clockwork mod)
2. launched android SDK adb daemon
3. moved file from 'tools' folder of sdk to the proper destination on the phone.
4. Done.
Click to expand...
Click to collapse
I'm not sure how to do step 2 your referring to. If you have a link to a thread that explains how to do that, it would be greatly appreciated.
Sent from my ADR6300 using XDA App
Well, you have to go to the android website and download the android SDK. Install it somewhere on your computer that's easy to access, preferably put the folder at the root of one of your hard drives.
You'll go into command prompt after that to do a lot of the work to transfer files.
So, make sure USB debugging is enabled (just in case) and boot your phone into cwm recovery. Connect the phone to your computer via USB.
in command prompt, cd to the android sdk's tools directory. From there, you can use the adb commands to transfer files.
So, for me, after connecting the phone I do the following in command prompt:
cd G:
cd androidsdk/tools
and then I use ADB to communicate with phone, first by verifying the phone is connected:
adb devices
(if adb is on your pc, it will auto run the daemon if it is not running)
If your phone shows up in recovery mode, you're set.
You may need to go into cwm and mount your system/sd card before transferring the file.
From there, you use adb shell to acess the phone's file systems.
If you put the boot animation to the phone you'll do something like (while in shell) mv bootanimation.zip system/somethingorother/bootanimation.zip
But don't take the above line as gospel. I dont remember the exact command line to use. Check the thread on "How 2 - ADB, Rooting...." for a list of commands in ADB shell and search for a webpage that gives basic linux commands.
Doctor Butts said:
Well, you have to go to the android website and download the android SDK. Install it somewhere on your computer that's easy to access, preferably put the folder at the root of one of your hard drives.
You'll go into command prompt after that to do a lot of the work to transfer files.
So, make sure USB debugging is enabled (just in case) and boot your phone into cwm recovery. Connect the phone to your computer via USB.
in command prompt, cd to the android sdk's tools directory. From there, you can use the adb commands to transfer files.
So, for me, after connecting the phone I do the following in command prompt:
cd G:
cd androidsdk/tools
and then I use ADB to communicate with phone, first by verifying the phone is connected:
adb devices
(if adb is on your pc, it will auto run the daemon if it is not running)
If your phone shows up in recovery mode, you're set.
You may need to go into cwm and mount your system/sd card before transferring the file.
From there, you use adb shell to acess the phone's file systems.
If you put the boot animation to the phone you'll do something like (while in shell) mv bootanimation.zip system/somethingorother/bootanimation.zip
But don't take the above line as gospel. I dont remember the exact command line to use. Check the thread on "How 2 - ADB, Rooting...." for a list of commands in ADB shell and search for a webpage that gives basic linux commands.
Click to expand...
Click to collapse
THANK YOU SIR. MUCH APPRECIATED.
Sent from my ADR6300 using XDA App
I posted this in another thread but got no response, this thread (http://forum.xda-developers.com/showthread.php?t=502010&page=35)
maybe a new thread will help.
So this is my first venture into the whole ABD thing. I am trying to install the framework mod from Tazz for the HTC music player (as listed here: http://forum.xda-developers.com/show...5594&page=1277 post 12768).
Tazz mentions to “push this http://www.multiupload.com/1WWHXAUN6W
to system/ect/permissions then download and install htc music”
So, running my trusty Win7 machine I downloaded the SDK from the android development site, inserted the correct line in the path and viola, I can enter the CMD prompt and run the adb command successfully. Adb and adb shell both seem to work.
I followed the instructions from here: http://androidforums.com/developer-1...-commands.html and here: http://forum.xda-developers.com/showthread.php?t=502010 for the install.
My problem comes in when I try to push the file to the phone.
Fisrt dumb question is: what phone mode should I be in when running the adb? Standard running mode or booted to recovery? (I thought I read something about being in recovery but at that point it was all a blur).
I have the USB Debugging turned on so I think I am ok there.
I installed the SDK to my C:\Android directory.
I saved Tazz’s file to my C:\Android\Tools directory.
Here is my cmd text (maybe this is where I went wrong):
In the cmd window I CD’d to the C:\Android\Tools directory
adb push com.framework.htc.xml system/ect/permissions
After making sure that I was in the correct dir and all files were also located in the correct dir I am still getting an error, file or directory not found, or something like that.
Sorry for the long post. I figured this would be a good first step (my first adb experience) as it seems pretty benign in terms of me bricking anything but offering a good learning opportunity.
I am running a rooted Eris (KaosFroyo v36).
In looking things thru maybe I need a USB driver for the Eris?
any help is appreciated,
oh, my cmd prompt looks like sh-2# (or something like that)
Thanks
While it may be that you still need to download the appropriate drivers, it seems you are able to get root access so, this is likely not the case.
There are two things which stand out as potential issues in the steps you described. Fortunately, both are super easy.
First and foremost, make sure you have mounted the phone as "read-write."After you have cd'd to the tools folder type "adb remount" (without the quotes) and press enter. If successful, it should respond with "remount succeeded." Congrats, you have now mounted the phone as read-write.
Next, I see errors with your command. There should be a "/" before "system" and it should be "etc" not "ect." Specifically, your command should be:
adb push com.framework.htc.xml /system/etc/permissions/
[The above command of course, assumes that the name of the file you are pushing is indeed named "com.framework.htc.xml" and is in your tools folder.] You'll know it worked if the response in your command prompt indicates the speed and time it took for the push to take. For example, "1234kbps in 3.4 seconds". If you see something resembling that you should be all set. At this point you can reboot your phone and your changes should be in effect. Either unplug and reboot manually or just type "adb reboot" (without the quotes) and press enter.
In regard to your question about whether the phone can be in standard running mode or recovery... It depends on the level of root of the phone but, fully rooted and nand unlocked phones can be adb'd while in standard running mode. My EVO can and it is very likely your Eris can too.
I see
thanks OK.
typo's aside in the thread, my command was missing the / as you have described it. I also did not know about the remount thing. In my reading I thought that was just for the sd card. I will try and put all the pieces together when I get home tonight.
You are correct in that is the name of the file and I do have it in the /tools directory.
Thanks for the help, baby steps (I am learning)
No problem. We are/were all noobs at one point in our lives.
The term "mounting" has slightly different contextual meanings which can be confusing. First off, the /system/ folder is already "mounted" while using adb, however, it is mounted as read-only. So, if you are ever trying to push something to the phone and get an error back that says "mounted as read-only" you'll now know what went wrong. Simply type "adb remount"
and it puts the /system/ folder into read-write mode.
Bear in mind that upon phone reboot the /system/ folder automatically remounts into read-only mode so if you reboot and try to push another file you'll need to remember to "adb remount" again.
With regard to the sdcard "mounting" refers to whether the phone (sdcard) is mounted as a disk drive on your computer. You'll find that if this is the case many adb commands won't work because the sdcard can't be accessed by the phone while mounted on the computer. Therefore, always remember to connect your phone as "Charge Only" when adb'ing.
got it
That did the trick, worked like a charm. Thanks for the help and pointers. I have now pushed my first file...yeah for me!!
Thanks for your help and time.
glad your push worked
I am still trying to get SDK/ADB to connect to my Milestone XT720 phone. Have no idea of why they won't. Have tried all the usual suspects but nothing as of yet. NEED HELP!
Hi, recently I broke my samsung captivate inner lcd screen and now everything is just black. I can't do anything but only physical and capacitate button. I'm from malaysia so i can't send this phone for a repair. I've tried to send this to my local repair shops and sadly they dont have the parts. Well, what matters to me now are the information that I have saved on my phone.
I have a rooted phone, so basically what I want to do is to copy all of my phone data into my computer through usb connection, well the thing is i cant press anything on the screen and that makes me not able to connect phone my to my computer.
So I just want to know is there anyway for me to access my phone through my computer or something. I know it may sound silly but I do have some important files in there. A help would really make me feel better and i do really need help on this.
Edit: Found the solution here
Code:
http://forum.xda-developers.com/showthread.php?t=1164598
Thanks!
Go get the Android SDK, and with that you'll get ADB. Once you have it installed, navigate to where you have ADB installed (usually [directory of installation]\android-sdk-windows\platform-tools) and create a folder called "backup" inside that same directory. Once you've done that, open a command prompt, and navigate to the platform-tools directory. Then, connect your phone to the computer, make sure it is recognized, and then try this:
adb pull / \backup
That will make a copy of everything that's on your phone from the root directory down into the "backup" folder you created. If that command doesn't work right, try deleting the \backup portion. It will mean that all the files will be dumped into the "platform-tools" folder, but you should at least have them.
If for some reason it won't let you do it, type "adb reboot recovery" first, then try the pull command. That usually lets me get around any restrictions.
jmtheiss said:
Go get the Android SDK, and with that you'll get ADB. Once you have it installed, navigate to where you have ADB installed (usually [directory of installation]\android-sdk-windows\platform-tools) and create a folder called "backup" inside that same directory. Once you've done that, open a command prompt, and navigate to the platform-tools directory. Then, connect your phone to the computer, make sure it is recognized, and then try this:
adb pull / \backup
That will make a copy of everything that's on your phone from the root directory down into the "backup" folder you created. If that command doesn't work right, try deleting the \backup portion. It will mean that all the files will be dumped into the "platform-tools" folder, but you should at least have them.
If for some reason it won't let you do it, type "adb reboot recovery" first, then try the pull command. That usually lets me get around any restrictions.
Click to expand...
Click to collapse
Ya, got it done. Thank you so much!
Hey guys, My friend brought me a Xtreamer Q mobile phone with broken screen, clockworkmode is working, but USB debugging mode is disabled, I found some posts about how to enable it from adb i tried them and none of them worked.
here :
http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
and from this tutorial i learnt how to edit build.prop file.
http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
the commands i have used are: adb pull, adb remount, adb push.
While i was under clockworkmode i mounted system and i pulled build.prop then i added this line to it persist.service.adb.enable=1, used remount then pushed the file after that reboot, but i couldn't find the device in adb when it have booted normaly.
Next i tried to set adb_enabled to 1 in /data/data/com.android.providers.settings/databases/settings.db by following some steps from here
http://forum.xda-developers.com/showthread.php?t=774507.
and it also didn't worked "The device was not listed".
Also i have tried this zip file from clockworkmode it didn't work too...
http://android.stackexchange.com/questions/54487/install-adb-enabled-setting-from-zip
My files after editing are attached, wish somebody can help me to enable it.
The phone do not support USB OTG cable
ThElitEyeS said:
Hey guys, My friend brought me a Xtreamer Q mobile phone with broken screen, clockworkmode is working, but USB debugging mode is disabled, I found some posts about how to enable it from adb i tried them and none of them worked.
here :
http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
and from this tutorial i learnt how to edit build.prop file.
http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
the commands i have used are: adb pull, adb remount, adb push.
While i was under clockworkmode i mounted system and i pulled build.prop then i added this line to it persist.service.adb.enable=1, used remount then pushed the file after that reboot, but i couldn't find the device in adb when it have booted normaly.
Next i tried to set adb_enabled to 1 in /data/data/com.android.providers.settings/databases/settings.db by following some steps from here
http://forum.xda-developers.com/showthread.php?t=774507.
and it also didn't worked "The device was not listed".
Also i have tried this zip file from clockworkmode it didn't work too...
http://android.stackexchange.com/questions/54487/install-adb-enabled-setting-from-zip
My files after editing are attached, wish somebody can help me to enable it.
Click to expand...
Click to collapse
What do you want to make with the phone if adb is working?
LS.xD said:
What do you want to make with the phone if adb is working?
Click to expand...
Click to collapse
I want to install a program to on it to control it from my computer
My Pixel 2 took a dive on a few days ago and I've been trying to get it operational ever since. The things i've tried are
1. Waiting it out
2. Force restart
3. Force restart more than 7 times in a row to get it to revert back to another version
4. ADB sideload the proper system image to get it to begin working
But none of these has worked. Right now all I'm really concerned about is trying to salvage my data and create a backup file for all my apps and data but when I try to do the backup through the adb using 'adb backup -apk -shared -all -system -f Direction:\filename.ab' it gives me an error that says "adb: unable to connect for backup: closed" And there's no other way around it.
Side note, I've only been able to get my phone to show up on the adb devices list when i say to do a recovery through adb, otherwise it simply doesn't show up there and only shows up under fastboot devices.
I would love some help here, anything you all can do to point me in the right direction would be fantastic.
@Otonirez
It seems the Android version doesn't support the ADB backup-interface. AFAIK in spring 2019 Google announced to remove the ADB backup feature.
jwoegerbauer said:
@Otonirez
It seems the Android version doesn't support the ADB backup-interface. AFAIK in spring 2019 Google announced to remove the ADB backup feature.
Click to expand...
Click to collapse
So what you're telling me is, that as far as you know, there is no real way for me to backup my data at this point?
Otonirez said:
So what you're telling me is, that as far as you know, there is no real way for me to backup my data at this point?
Click to expand...
Click to collapse
You know "ALL / DIFFERENT WAYS LEAD TO ROME", hence you simply pull the data off the phone - of course utilizing the ADB driver provided by phone's OEM: The format of the pull request is simple, you start with the command adb pull, then add the file/folder you are pulling and the location you want it to go.
Example:
Code:
cmd
mkdir C:\PHONE-BACKUP
adb devices
adb pull /data/ C:\PHONE-BACKUP
move /Y C:\PHONE-BACKUP PHONE-BACKUP-%DATE%
jwoegerbauer said:
You know "ALL / DIFFERENT WAYS LEAD TO ROME", hence you simply pull the data off the phone - of course utilizing the ADB driver provided by phone's OEM: The format of the pull request is simple, you start with the command adb pull, then add the file/folder you are pulling and the location you want it to go.
Example:
Code:
cmd
mkdir C:\PHONE-BACKUP
adb devices
adb pull /data/ C:\PHONE-BACKUP
move /Y C:\PHONE-BACKUP PHONE-BACKUP-%DATE%
Click to expand...
Click to collapse
I really wish I would have seen this a few minutes ago because I did a factory reset on my phone like right before i saw this. I doubt there's anything I can do at this point to reclaim my stuff