Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
recovery sideloading often fails to start on the Nexus 5 #2
Comments
thestinger
added
Type: bug
upstream
labels
Aug 17, 2015
thestinger
added this to the Beta release milestone
Aug 19, 2015
ghost
referenced this issue
thestinger
removed
the
upstream
label
Oct 14, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Nov 17, 2015
Contributor
This appears to have been narrowed down to being caused by OpenBSD malloc. Possibly a memory corruption issue that's caught by it. The issue doesn't occur deterministically so it's hard to say if using OpenBSD malloc simply makes it more likely.
|
This appears to have been narrowed down to being caused by OpenBSD malloc. Possibly a memory corruption issue that's caught by it. The issue doesn't occur deterministically so it's hard to say if using OpenBSD malloc simply makes it more likely. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
This has been worked around for now. |
thestinger
closed this
Nov 28, 2015
thestinger
referenced this issue
Nov 28, 2015
Closed
recovery sideloading doesn't work on the Galaxy S4 #3
thestinger
added
the
Nexus 5
label
Feb 8, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
thestinger commentedAug 17, 2015
Starting a sideload will often fail with a read error, so it can take many attempts before it works. Once it gets going, it works fine.