Bug 20534 - ADB backup hangs at 2Gb when creating files larger than 2Gb
Summary: ADB backup hangs at 2Gb when creating files larger than 2Gb
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: David GEIGER
QA Contact:
URL: https://bugs.launchpad.net/ubuntu/+so...
Whiteboard:
Keywords:
: 20535 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-03-20 11:19 CET by apa khabar
Modified: 2018-10-07 17:04 CEST (History)
1 user (show)

See Also:
Source RPM: android-tools-4.4.2_r2-4.mga5
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description apa khabar 2017-03-20 11:19:36 CET 
Description of problem:

`adb backup' stops or hangs at 2Gb file size when creating backups larger than 2Gb from Android phone via USB cable from PC.

Version-Release number of selected component (if applicable):

android-tools-4.4.2_r2-4.mga5

How reproducible:

when trying to backup an Android phone by USB cable from PC.

Steps to Reproduce:
1. Turn on debugging option on Android phone
2. Connect Android phone with USB cable
3. In terminal as root give command `# adb devices -l' to check device is recognised
4. In terminal as root give command `# adb backup -all -f /name/of/file/on/pc
Comment 1 apa khabar 2017-03-20 11:28:32 CET 
*** Bug 20535 has been marked as a duplicate of this bug. ***
Comment 2 apa khabar 2017-03-20 11:31:35 CET 
Similarly, adb hangs on 2Gb on doing:

# adb pull /dev/block/mmcblk0 mmcblk0.img

http://android.stackexchange.com/questions/47975/is-there-a-way-to-do-nandroid-backup-directly-to-pc-and-then-restore-it-directly
Comment 3 Marja Van Waes 2017-03-20 12:10:00 CET 
Assigning to the registered android-tools maintainer.

CC: (none) => marja11
Assignee: bugsquad => geiger.david68210

Comment 4 Marja Van Waes 2018-07-12 16:05:35 CEST 
Hi apa khabar,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we were waiting for the big Plasma5 update in Mageia 6, that fixed many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

==> If you didn't reset your password after february 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==
Comment 5 Marja Van Waes 2018-10-07 17:04:47 CEST 
No reply, so closing as OLD since Mageia 5 is no longer maintained.

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.