adb backup创建0字节文件;即使我从未设置为一个,也会提示当前备份密码; “无法设置密码”桌面备份密码 -- adb 领域 和 4.4-kitkat 领域 和 backup 领域 和 samsung-galaxy-s-4 领域 android 相关 的问题

ADB backup creates 0-byte file; prompts for current backup password even though I never set one; “Failed to set password” for Desktop backup password


简体版||繁體版
50
vote

问题

中文

问题:

每次运行adb备份时,我会在主屏幕底部附近的消息说 Backup starting... ,后跟一条消息,然后是一条消息,然后是一条消息 Backup finished 几秒钟后来尽管我正在使用17 GB的设备内存,并且使用0个字节的大小创建生成的备份文件。我没有收到错误消息,没有反馈,无论是什么都是错误的,更不用说,更不用说是什么意思。它似乎工作,但太快的方式,备份文件是空的。

过程:

  1. i确认设备由adb使用 adb devices 命令识别,并接收以下输出:

      List of devices attached 8e1f368a        device   
  2. i发出adb backup命令(要关注的详细信息)。

  3. 我在命令提示符下获取以下消息:

      Now unlock your device and confirm the backup operation.   

    ...和以下提示电话:

    输入图像描述

    它没有区别我在这里做了什么(细节遵循)。

  4. i点击备份我的数据按钮(右下角)。

  5. 手机返回主屏幕并显示 Backup starting... 消息,然后是 none0 稍后几秒钟。创建一个0字节文件,命名为默认的 backup.ab 或使用 -f switch指定的任何我指定的任何我指定的。

adb backup命令(在步骤2中使用):

我已经尝试了多种选项组合,范围从简单的

  none1  

这样的东西
  none2  

我还尝试添加 none3 switch之后读取这个和 this ,这表明尝试在左右设备上包含系统备份可能会导致0字节文件,并且必须使用此开关。它没有区别,过程仍然在几秒钟内完成,我仍然得到一个0字节的文件。

"完全备份" 密码提示(步骤3):

我非常确定我以前从未设置备份密码。我从未有机会以之前以任何方式设置此密码或访问此设置。但是,我尝试了以下所有内容:

  • 留下密码空白
  • 将"当前备份密码" 留空并在第二个框中输入新密码
  • 进入当前屏幕锁定引脚和我过去使用的所有引脚作为"当前备份密码" 。
  • 输入每个密码我可以想到我将在这个设备上使用任何东西

在所有情况下,行为与步骤5中所述的行为完全相同。我没有错误或任何类型的指示,任何错误或者我的密码无效,而且没有提示它实际上是期待当前密码还是该字段是否应留空。 (屏幕拍摄于此答案我看起来似乎暗示了"当前的支持论坛如果没有当前密码,则不会显示备份密码"框,但这只是推理;没有什么可以清楚实际需要当前密码。)

我怀疑它提示的密码可能是开发者选项中设置的"桌面备份密码" :

输入图像描述

我以前从未设置过该密码。如果我尝试设置一个,我收到一条消息,说 none4

在搜索有关此错误的信息中,我至少遇到了一个其他问题的其他情况,其中有这个问题的人说这是防止他使用adb备份,但他并不具体了解他尝试时发生的事情 使用adb备份。

大多数收到此消息的人在说解决方案是将当前密码空白留空之前,但我在第一个位置和它中尝试过 我不起作用。我找到了另一个人的问题谁遇到了这个问题,并确定他在之前没有设置密码。不幸的是,它看起来不像他有一个解决方案甚至解释。

无论adb是否正在寻找"桌面备份密码" 或adb加密密码是一个单独的东西,它会令我兴奋的为什么adb将要求您输入以前的密码以启动新备份。我不是在尝试恢复,覆盖或以任何方式访问先前加密的数据,因此即使备份的加密密码先前已设置,我无法想象为什么有人会认为它是如果您不记得过去备份备份的密码,请防止您备份设备的好主意。

附加信息:

型号:三星Galaxy S4 Sch-I545
内核版本: 3.4.0
操作系统版本: 4.4.2
Android SDK工具版本: 1.16
USB调试已启用。

请注意,我使用adb备份的原因是在rooting之前将手机完整备份在安全侧*所以我可以使用itanium backup等nandroid备份工具。因此,任何涉及生根手机的建议都是Catch-22,而不是解决方案。毋庸置疑,出厂重置也不是一个解决方案,因为它会打败执行备份的全部目的。

phone 设置与我公司的Exchange服务器同步,并且服务器有一些策略。我认为当我第一次使用公司帐户设置同步时,设备是加密的,但显然它目前没有加密。事实上,这就是设置这一事件中的动作中的哪个事件:我收到一条消息告诉我我需要加密设备才能继续连接到公司服务器。我想在加密之前拍摄nandroid备份,这需要rovening,并且我想在rooting之前使用adb备份。


*是的,我知道毛巾根据称是安全的,但我宁愿不采取机会,我想解决或至少明白这个问题,以防相关问题出现 未来。

english

The problem:

Every time I run ADB backup, I get a message near the bottom of the home screen saying Backup starting..., followed by a message saying Backup finished a few seconds later despite the fact that I'm using 17 GB of device memory, and the resultant backup file is created with a size of 0 bytes. I receive no error messages, no feedback whatsoever indicating that anything is wrong, let alone what is wrong. It appears to work, but way too quickly, and the backup file is empty.

The process:

  1. I confirm that the device is recognized by ADB using the adb devices command, and receive the following output:

    List of devices attached 8e1f368a        device 
  2. I issue the ADB backup command (details to follow).

  3. I get the following message at the command prompt:

    Now unlock your device and confirm the backup operation. 

    ...and the following prompt on the phone:

    enter image description here

    It makes no difference what I do here (details to follow).

  4. I tap the Back up my data button (bottom right corner).

  5. The phone returns to the home screen and shows me the Backup starting... message, then the Backup finished message a few seconds later. A 0-byte file is created, named either the default backup.ab or whatever I specified with the -f switch.

The ADB backup command (used in step 2):

I've tried multiple combinations of options, ranging from as simple as

adb backup -all 

to things like

adb backup -all -apk -s 8e1f368a -f 'C:\Data Files\PDA\Backups\ADB\GalaxyS4_20140919.ab' 

I also tried adding the -nosystem switch after reading this and this, which indicate that trying to include a system backup on an unrooted device may result in a 0-byte file, and that this switch must be used. It makes no difference, the process still completes in a matter of seconds and I still get a 0-byte file.

The "Full backup" password prompt (step 3):

I'm quite sure I have never set a backup password before. I've never had the occasion to set this password or access this setting in any way before. However, I have tried all of the following:

  • Leaving both passwords blank
  • Leaving the "current backup password" blank and entering a new password in the second box
  • Entering the current screen lock PIN and all PINs I've ever used in the past as the "current backup password".
  • Entering every password I can think of that I would have ever used for anything on this device

In all cases the behavior is exactly the same as described in step 5. I get no errors or any kind of indication that anything is wrong or that my passwords are invalid, and no hint as to whether it's actually expecting a current password or whether that field should be left blank. (The screen shot in this answer and several other support forums I've looked at seems to imply that the "current backup password" box wouldn't be displayed if there's no current password, but that's just an inference; nothing makes it clear whether a current password is actually required.)

I suspect that the password it's prompting for might be the "Desktop backup password" set in Developer options:

enter image description here

I have never set that password before. If I try to set one, I get a message saying Failed to set backup password.

In searching for information about this error, I've encountered at least one other case in which someone who was having this problem said this was preventing him from using ADB backup, but he wasn't specific about what happens when he tries to use ADB backup.

Most people who received this message having never set the password before say that the solution was to leave the current password blank, but I tried that in the first place and it didn't work. I found a question by another person who encountered this problem and was sure he hadn't set the password before. Unfortunately it doesn't look like he ever got a solution or even an explanation.

Regardless of whether ADB is looking for the "Desktop backup password" or the ADB encryption password is something separate, it boggles my mind why ADB would require you to enter a previous password in order to initiate a new backup. I'm not trying to restore, overwrite, or in any way access previously encrypted data, so even if an encryption password for a backup had previously been set, I can't imagine why anyone would think it's a good idea to prevent you from backing up your device if you don't remember what password you used to encrypt backups in the past.

Additional information:

Model: Samsung Galaxy S4 SCH-I545
Kernel version: 3.4.0
OS version: 4.4.2
Android SDK Tools version: 1.16
USB debugging is enabled.

Note that my reason for using ADB backup is to take a full backup of my phone to be on the safe side before rooting it* so I can use nandroid backup tools such as Titanium backup. So, any suggestion involving rooting my phone would be a Catch-22, not a solution. Needless to say, a factory reset is also not a solution, since it would defeat the entire purpose of performing the backup.

The phone is set up to sync with my company's Exchange servers, and there are some policies enforced by the server. I had thought that the device was encrypted when I first set up the sync with company account, but apparently it isn't currently encrypted. In fact, that's what set this chain of events in motion: I'm getting a message telling me that I need to encrypt the device in order to continue to connect to company servers. I want to take a nandroid backup before encrypting, which requires rooting, and I want to use ADB backup before rooting.


* Yes, I'm aware that Towelroot is purported to be safe, but I'd rather not take chances, and I'd like to resolve or at least understand this problem in case related issues come up in the future.

           
     
     

回答列表

33
 
vote

简短答案

尝试使用早期版本的adb。 1.0.32对我不起作用,但1.0.31。

长答案

我刚刚在运行Cyanogenmod 11的Nexus 5上遇到了这个问题(基于Android 4.4)使用当前版本的平台工具和adb(Android调试桥1.0.32版Revision EAC51F2BB6A8-Android)。

使用 adb logcat 观看设备日志,我注意到调用 adb backup -apk -obb -shared -all -nosystem 有一些可疑的日志条目:

  V/BackupManagerService(  811): Requesting full backup: apks=false obb=false shared=false all=false pkgs=[Ljava.lang.String;@4181ffc8 W/BackupManagerService(  811): Unknown package  '-apk' '-obb' '-shared' '-all' '-nosystem', skipping   

在似乎设备正在将命令行选项解释为非选项参数,并产生错误,因为它们未安装包名称。这让我怀疑adb协议或命令/服务调用选项相对于主机在设备上更改,因此我尝试了旧版adb和voilã,它运行。

我做了一点挖掘,并在"adb backup" 中遇到了使用eascoving_arg ,现在在调用 /system/bin/bu backup 时,它会导致所有参数的所有参数都引用。这解释了日志消息中的行为和单引用的参数。但是,它似乎并不匹配您遇到错误的时间。它还会提出比似乎更广泛的问题。所以我犹豫要称之为原因,但它可能是进一步调查的良好起点。

 

Short Answer

Try using an earlier version of adb. 1.0.32 did not work for me, but 1.0.31 did.

Long Answer

I just encountered this issue on a Nexus 5 running CyanogenMod 11 (based on Android 4.4) using the current version of the Platform Tools and ADB (Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android).

Using adb logcat to watch the device logs, I noticed that after invoking adb backup -apk -obb -shared -all -nosystem there were some suspicious log entries:

V/BackupManagerService(  811): Requesting full backup: apks=false obb=false shared=false all=false pkgs=[Ljava.lang.String;@4181ffc8 W/BackupManagerService(  811): Unknown package  '-apk' '-obb' '-shared' '-all' '-nosystem', skipping 

Where it appears that the device is interpreting the command-line options as non-option arguments, and producing an error because they are not installed package names. This made me suspect the adb protocol or the command/service invocation options had changed on the device relative to the host, so I tried an older version of adb and voilxc3xa0, it worked.

I did a bit of digging and came across a change to Use escape_arg in "adb backup", which now causes all arguments to be single-quoted when invoking /system/bin/bu backup. This explains the behavior and the single-quoted arguments in the log message. However, it does not seem to match the time at which you encountered the error. It would also suggest the issue to be much more widespread than it appears to be. So I am hesitant to call this the cause, but it may a good starting point for further investigation.

 
 
         
         
16
 
vote

在Keuvoid的答案上建立,它可能取决于手机上运行的ADB版本。

您可以通过执行以下操作,了解手机本地运行的版本:

首先找出您在桌面上运行的版本

  adb version   

然后打开手机上的shell

  adb shell   

一旦shell打开,那么您可以运行

  adb version   

然后通过运行

退出shell
  exit   

我发现我的手机运行1.0.31,而不是1.0.32(这是三星注2)

我尝试使用亨特等引号或转义字符,但没有从Windows命令行工作的字符。但下坡确实修复了两个版本之间的不兼容问题。

我能够在这里找到旧版本: http://dl-ssl.google.com/android/repository / platform-tools_r20-windows.zip

其他平台:

  • http://dl-sl.google .com / android / repository / platform-tools_r20-macosx.zip

    http://dl-sl.google.com/ Android / repository / platform-tools_r20-linux.zip

 

Building on kevenoid's answer, it may depend on what version of adb is running on the phone.

You can find out what version the phone is running natively by doing the following:

First find out what version you are running on your desktop

adb version 

Then open the shell on your phone

adb shell 

Once the shell is open then you can run

adb version 

Then exit the shell by running

exit 

I found that my phone was running version 1.0.31 and not 1.0.32 (it is a samsung note 2)

I tried using quotes or escape characters like Hunter showed but none of those worked from the windows command line. However downgrading did fix the incompatibility issue between the two versions.

I was able to find the older version following the instructions here: https://stackoverflow.com/a/23022718/1741542

The download link I used was:
http://dl-ssl.google.com/android/repository/platform-tools_r20-windows.zip

Other platforms:

  • http://dl-ssl.google.com/android/repository/platform-tools_r20-macosx.zip

    http://dl-ssl.google.com/android/repository/platform-tools_r20-linux.zip

 
 
 
 
10
 
vote

有关引用的命令参数的其他答案是准确的。我发现如果你在参数之间逃脱空格,它就有效。

如下: adb backup -apk -shared -all -system

 

The other answers about the command arguments being quoted is accurate. I've found that if you escape the spaces between the arguments, it works.

Like this: adb backup -apk\ -shared\ -all\ -system

 
 
       
       
7
 
vote

没有任何替代方法在这里为我工作,我不想降级我的SDK工具。以下是我提出的:跳过<代码> ABCDEFGHIJKLMNABCDEFGHIJKLMN5 在计算机上,直接通过 adb shell

  $adb version Android Debug Bridge version 1.0.35 Revision fc2a139a55f5-android  $ adb shell shell@jflte:/ $ bu 1 backup -apk app.package.name > /sdcard/backup.ab shell@jflte:/ $ exit  $adb pull /sdcard/backup.ab [100%] /sdcard/backup.ab   

此调用 /system/bin/bu 并将备份文件转储到stdout(文件描述符#1)上。参数是相同的 adb backup <params> - &gt; adb shell 0 。输出被重定向到设备上的文件,然后可以像任何文件一样拉动。

唯一的缺点是如果您的设备超过半满缺点,则无法完成完整备份。如果您有外部SDCard插槽,则可以解决此问题。 adb shell 1 甚至可以在Android 4.4.2上写入那里,因为它是一个系统应用程序。 adb shell 2 对我的工作相同,因为 adb shell 3

 

None of the workarounds worked for me here, and I don't want to downgrade my SDK tools. Here's what I came up with: skip adb backup on the computer and go straight to device via adb shell.

$adb version Android Debug Bridge version 1.0.35 Revision fc2a139a55f5-android  $ adb shell shell@jflte:/ $ bu 1 backup -apk app.package.name > /sdcard/backup.ab shell@jflte:/ $ exit  $adb pull /sdcard/backup.ab [100%] /sdcard/backup.ab 

This calls /system/bin/bu and dumps the backup file onto STDOUT (File descriptor #1). Parameters are the same adb backup <params> -> bu 1 backup <params>. The output is redirected to a file on the device and then can be pulled like any file.

The only drawback is that you can't do a full backup if your device is more than half full. This can be worked around if you have an external SdCard slot. bu can write there even on Android 4.4.2, because it is a system app. /mnt/extSdCard/backup.ab worked the same for me as /sdcard.

 
 
4
 
vote

sigh 我真的很抱歉,如果是这种情况,你似乎要注意你的截图和命令行,但我发现了我的chagrin同样的症状和想法在未来的发现者在这里张贴。事实证明,adb是非常在其选项中有一个关于单个与双击的挑剔。对我来说,双划线重现了这种情况:手机上的相同提示,相同的0字节文件。单划线即使有长度参数名称像魅力一样工作。

如果它很重要,我的手机是一个AT&amp的三星Galaze Note 2。T SGH-I317运行Android 5.1 / Cyanogenmod 12.1。
 

sigh I'm really sorry if this is the case, and you seem to be careful judging by your screenshots and command lines, but I discovered to my chagrin the same symptoms and thought I'd post just in case future discoverers make it here. It turns out that adb is very picky about single vs. double dashes in its options. For me, double dashes reproduced this case exactly: same prompt on the phone, same 0 byte file. Single dashes even though there are long argument names worked like a charm.

In case it matters, my phone is a Samsung Galazy Note 2 AT&T SGH-i317 running Android 5.1/Cyanogenmod 12.1.

 
 
     
     
2
 
vote

您需要在adb版本1.0.31上执行adb backup命令。

对于Windows我做了:
  • 查找您的SDK文件夹(C:/用户/ ... / appdata / local / android / sdk)
  • 重命名工具&amp; platform-tools tools.bak&amp; platform-tools.bak
  • 下载 http://dl-sl.google.com / android/repository/tools_r22.3-windows.zip
  • 下载 http://dl-ssl.google .com / android / repository / platform-tools_r19.0.1-windows.zip
  • 提取zip到sdk文件夹
  • 运行adb backup命令正常

日志:

$ adb backup -apk -obb -shared -all -system -f bckp.ab

adb服务器已过期。杀戮...

  • 守护程序开始成功*

现在解锁您的设备并确认备份操作。

......然后将所有内容设置为正常。

 

You need to execute the adb backup command on adb version 1.0.31.

For windows i did:

  • find your SDK folder (c:/users/.../AppData/Local/Android/sdk)
  • rename tools & platform-tools to tools.bak & platform-tools.bak
  • download http://dl-ssl.google.com/android/repository/tools_r22.3-windows.zip
  • download http://dl-ssl.google.com/android/repository/platform-tools_r19.0.1-windows.zip
  • extract both zip's to sdk folder
  • run adb backup command as normal

Log:

$ adb backup -apk -obb -shared -all -system -f bckp.ab

adb server is out of date. killing...

  • daemon started successfully *

Now unlock your device and confirm the backup operation.

...then set everything back to normal.

 
 
1
 
vote

好的,这就是我如何修复我的。

我尝试了猎人Perrin的解决方案:

  adb backup -apk -shared -all -system   

但它刚刚立即返回没有错误,手机上没有备份屏幕。

通过试验和错误,这适用于我:

  adb backup -all   
 

OK, this is how I fixed mine.

I tried Hunter Perrin's solution:

adb backup -apk\ -shared\ -all\ -system 

But it just returned immediately with no error, no backup screen on the phone.

Through trial and error this worked for me:

adb backup -all\ 
 
 
1
 
vote

我认为我有一个使用1.0.32:

的解决方案

在Android屏幕上提示时输入密码

尽管它说它将使用默认密码如果输入无,则相信它没有,adb 1.0.32可能不允许创建未加密的备份。

输入密码为我工作,然后我最终使用了 "Android Backup Extrutionor" (警告SourceForge)和" Java加密扩展(JCE)无限的力量管辖权政策"

 

I think I have a solution for those using 1.0.32:

enter a password when prompted on the android screen

Despite the fact that it says it will use the default password if you enter none, I believe it doesn't and adb 1.0.32 perhaps does not allow the creation of unencrypted backups.

Entering a password worked for me, then I ended up using "Android Backup Extractor" (Warning Sourceforge) and "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy" to extract it into a tar file.

 
 
1
 
vote

我遇到了逆问题:1.0.31使用较新的电话(Android 7)失败。 1.0.31用途:将参数传递给手机时作为分隔符。 作为 adb logcat -s BackupManagerService 显示,手机上的较新的adb无法处理旧样式: 02-19 01:59:44.330 1100 9830 W BackupManagerService: Unknown package com.gameloft.android.ANMP.GloftPOHM:-apk, skipping 幸运的是,较新的adb也接受空间作为分隔符,因此封闭双引号中的参数工作,例如: adb.exe backup "com.gameloft.android.ANMP.GloftPOHM -apk" -f game-backup.ab

 

I ran into the inverse problem: 1.0.31 with a newer phone (Android 7) fails too. 1.0.31 uses : as separator when passing arguments to the phone. As adb logcat -s BackupManagerService shows, the newer adb on the phone can't handle the old style either: 02-19 01:59:44.330 1100 9830 W BackupManagerService: Unknown package com.gameloft.android.ANMP.GloftPOHM:-apk, skipping Fortunately, the newer adb accepts spaces as separator too, so enclosing the arguments within double quotes works, e.g.: adb.exe backup "com.gameloft.android.ANMP.GloftPOHM -apk" -f game-backup.ab

 
 
1
 
vote

对我来说,它是包名称已更改,因此 adb backup 未找到它并创建一个空备份文件,而无需报告任何错误 adb logcat 显示了错误。一旦我更新了包名, adb backup 成功。

这是使用adb版本1.0.41,启用了桌面备份密码。

 

For me it was that the package name had been changed, so adb backup wasn't finding it and was creating an empty backup file, without reporting any error. adb logcat showed the error. Once I updated the package name, adb backup succeeded.

This was using ADB version 1.0.41, with a desktop backup password enabled.

 
 

相关问题

1  如何扎根三星Galaxy S4值版I9515?  ( How to root samsung galaxy s4 value edition i9515 ) 
我的父亲给我带来了这个智能手机,当我和朋友们一起搜索互联网聊天时,我很常见,但我的I.19515是不同的,我没有想到它的想法。 我尝试了srsroot和motochopper。但没有工作 帮助我出去 ...

1  如果安全到位,则无法更改Galaxy S4锁屏壁纸  ( Cant change galaxy s4 lock screen wallpaper if security is in place ) 
如果我没有为Galaxy S4锁定屏幕使用安全性,我可以使用锁定屏幕的自定义壁纸。但是如果我使用引脚安全性,那么锁屏在进入我的针时使用带有一堆气球的孩子的默认壁纸。有人可以确认这一点吗?谢谢 ...

2  为什么我的Galaxy S4屏幕不显示任何东西?  ( Why doesnt my galaxy s4 screen display anything ) 
我的三星Galaxy S4将突然不会在显示屏上显示任何内容。它振动,诸如如果一切,但显示器有效。有时它会闪存一些看起来有点像Android家伙的一部分,但它闪烁这么快,我无法确定它是什么或者它是否只闪烁。 我已经尝试了顶级解决方案,我的谷歌搜索导致我尝试: - 介绍电池并保持音量向上和主按钮10秒钟。 - 介绍...

1  如何标记Galaxy S4主屏幕的页面?  ( How do i label a page of the galaxy s4 home screen ) 
GS4允许您有多页主屏幕。我想用它作为一种全屏,更多的可访问文件夹(例如,"实用程序" 页面)。 如何将文本标签("实用程序" )放入此页面("实用程序" ),如此? 我意识到我可以使用一个实际文件夹,但我想尝试页面的想法。 ...

9  在锁屏上显示消息  ( Show messages on lock screen ) 
我正在寻找某种方式,它将在手机被锁定时展示屏幕上的部分/所有短信,电子邮件,推文。 我只是放弃了我的iPhone,这是我真正缺少的东西。 对我来说,必须点击一条消息,以查看该人是否响应了"确定" 或可以轻松显示在屏幕上的内容。 这是消息传递的屏幕截图。我希望能够阅读文本。 ...

0  根S4 GT-I9515的问题  ( Problem with root s4 gt i9515 ) 
我有s4 i9515。我可以使用ROM或ROOT S4 I9505到我的手机吗? 我找不到手机的任何root。我甚至尝试用根S4 I9505 root我的手机root,但是当我尝试提供超级用户访问我的"root checker应用程序" 时,它给我"此设备没有正确的根访问" 。但是,如果我删除"超级用户应用程序" ,...

0  三星S4在洛莱普更新后崩溃  ( Samsung s4 crash after lollipop update ) 
我最近更新了我的三星Galaxy S4。从那时起,手机每隔几分钟就会保持崩溃。当我重新启动手机时,它会正常工作几个小时然后再开始崩溃。 ...

10  什么是神秘的“CDC串行”设备以及为什么需要它?  ( What is the mysterious cdc serial device and why do i needed it ) 
我已经建立了我在线购买的零件的自己的PC电脑,我做了一个干净的Windows 7终极64位与SP1(完整版,没有OEM Bloatware),我跑了几次Windows Update以获得Microsoft的最新和最大的更新。我很高兴看到一切正常工作,没有任何问题,而不是软硬件。接下来,我将我全新的三星Galaxy S...

50  adb backup创建0字节文件;即使我从未设置为一个,也会提示当前备份密码; “无法设置密码”桌面备份密码  ( Adb backup creates 0 byte file prompts for current backup password even though ) 
问题: 每次运行adb备份时,我会在主屏幕底部附近的消息说 Backup starting... ,后跟一条消息,然后是一条消息,然后是一条消息 Backup finished 几秒钟后来尽管我正在使用17 GB的设备内存,并且使用0个字节的大小创建生成的备份文件。我没有收到错误消息,没有反馈,无论是什么都是错误的...

0  向三星S4发送短信到电子邮件地址  ( Sending text messages to e mail addresses on samsung s4 ) 
我想使用Samsung S4上的消息传递向电子邮件地址发送短信。我以前已经在测试之前完成了,但我无法让它更长。 如何再次启用此功能? ...




© 2022 it.wenda123.org All Rights Reserved. 问答之家 版权所有