Hello,
I have some backup files in the format .img.
Most of them it is possible to extract with unaffy but for data.img I receive unaffys.ex has stopped working.
I´m running on Win7.
Problem signature:
Problem Event Name: APPCRASH
Application Name: unyaffs.exe
Application Version: 0.0.0.0
Application Timestamp: 49c0f760
Fault Module Name: unyaffs.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 49c0f760
Exception Code: c0000005
Exception Offset: 00001340
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 1053
Additional Information 1: bc2e
Additional Information 2: c8cb9f379b8ed40abf4cf05764838fce
Additional Information 3: a990
Additional Information 4: 7b7a26d9fe2af3ce2040f60a66da4947
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=501...mp;clcid=0x0409
Anyone know how to solve this?
I do have a Spritebackup also if anyone know how to extract such files (.sbf) instead.
BR
Pierre
Which version of unyaffs did you use? I've seen old versions floating around that sometimes don't work properly for some files.
Here is a version I compiled from the latest source with some unofficial fixes added. It's worth a try at least.
In the past I've used the the emulator and specified my data.img to be loaded, then used adb to pull the wanted files...
C:\temp\android-sdk-windows\tools>emulator.exe -help
Android Emulator usage: emulator [options] [-qemu args]
options:
-sysdir <dir> search for system disk images in <dir>
-system <file> read initial system image from <file>
-datadir <dir> write user data into <dir>
-kernel <file> use specific emulated kernel
-ramdisk <file> ramdisk image (default <system>/ramdisk.img
-image <file> obsolete, use -system <file> instead
-init-data <file> initial data image (default <system>/userdata
.img
blunden said:
Which version of unyaffs did you use? I've seen old versions floating around that sometimes don't work properly for some files.
Here is a version I compiled from the latest source with some unofficial fixes added. It's worth a try at least.
Click to expand...
Click to collapse
Worked with the new version.
Thanks.
pdais97 said:
Hello,
I have some backup files in the format .img.
Most of them it is possible to extract with unaffy but for data.img I receive unaffys.ex has stopped working.
I´m running on Win7.
Problem signature:
Problem Event Name: APPCRASH
Application Name: unyaffs.exe
Application Version: 0.0.0.0
Application Timestamp: 49c0f760
Fault Module Name: unyaffs.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 49c0f760
Exception Code: c0000005
Exception Offset: 00001340
OS Version: 6.0.6002.2.2.0.256.6
Locale ID: 1053
Additional Information 1: bc2e
Additional Information 2: c8cb9f379b8ed40abf4cf05764838fce
Additional Information 3: a990
Additional Information 4: 7b7a26d9fe2af3ce2040f60a66da4947
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=501...mp;clcid=0x0409
Anyone know how to solve this?
I do have a Spritebackup also if anyone know how to extract such files (.sbf) instead.
BR
Pierre
Click to expand...
Click to collapse
gunzip -c ../your-ramdisk-file | cpio -i starting from 1F8B
As the title suggests, I'm attempting to compile a (Lollipop) Nexus 5 kernel with SELinux in permissive mode by default. For reference, I am using the msm kernel source tree at commit 8a80a0e.
I have managed to accomplish this by modifying msm/security/selinux/selinuxfs.c and inserting new_value = 0; into sel_write_enforce to prevent the mode being changed:
Code:
length = -EINVAL;
if (sscanf(page, "%d", &new_value) != 1)
goto out;
new_value = 0; /* inserted this line */
if (new_value != selinux_enforcing) {
length = task_has_security(current, SECURITY__SETENFORCE);
if (length)
goto out;
audit_log(current->audit_context, GFP_KERNEL, AUDIT_MAC_STATUS,
"enforcing=%d old_enforcing=%d auid=%u ses=%u",
This method, however, doesn't seem particularly good, as it relies on the intricacies of the specific implementation of SELinux used in this kernel, and prevents the mode being changed later.
This post suggests changing the CONFIG_ALWAYS_ENFORCE flag for a Samsung device, however the Nexus 5 kernel does not appear to have such an option. Setting the default state of SELinux using various menuconfig options and kernel command line parameters does not appear to have any effect, and disabling it entirely causes the device to crash after boot, before any logcat output is produced.
I have noticed than when started with a kernel with SELinux enabled, one of the first messages from logcat is from auditd, of the form enforcing=1 old_enforcing=0 auid=... ses=..., indicating that something is setting the SELinux mode to enforcing almost immediately after boot.
Thus, I am wondering if anyone knows where this command to set SELinux to enforcing comes from, how to disable it, or another way to compile a kernel with SELinux set to permissive?
I believe you need to change the kernel config to allow command line switching of SELinux:
Code:
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
then modify the boot parameters of your boot.img adding to the cmdline:
Code:
enforcing=0 androidboot.selinux=permissive
I think that's the way. I went through all this but ended up just disabling SELinux altogether so I can't remember for sure if that's all.
Gene Poole said:
I believe you need to change the kernel config to allow command line switching of SELinux:
Code:
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
then modify the boot parameters of your boot.img adding to the cmdline:
Code:
enforcing=0 androidboot.selinux=permissive
I think that's the way. I went through all this but ended up just disabling SELinux altogether so I can't remember for sure if that's all.
Click to expand...
Click to collapse
Doesn't work. The system boots up in permissive mode, but immediately switches to enforcing, as it usually does. The first few lines of logcat:
Code:
--------- beginning of main
I/installd( 0): installd firing up
W/auditd ( 169): type=2000 audit(0.0:1): initialized
I/auditd ( 169): type=1403 audit(0.0:2): policy loaded auid=4294967295 ses=4294967295
W/auditd ( 169): type=1404 audit(0.0:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
Are you using the google boot image, or the AOSP image (they're quite different)? I just checked mine (built from source) and init has -DALLOW_DISABLE_SELINUX=1 which may not be present in the distro version of init.
Gene Poole said:
Are you using the google boot image, or the AOSP image (they're quite different)? I just checked mine (built from source) and init has -DALLOW_DISABLE_SELINUX=1 which may not be present in the distro version of init.
Click to expand...
Click to collapse
I wasn't aware there was a difference. I compiled the kernel from source, enabling the relevant config options, then got boot.img from the Nexus 5 factory image, and extracted and replaced the kernel and boot parameters as suggested by this document.
The boot.img built as part of the AOSP build (with USERDEBUG flag) is not locked down the way the factory boot image is. There may be something built-in to the init process to ensure selinux is available in the kernel and cannot be disabled.
I wish I knew more about this. My original goal was to implement the things I needed in the AOSP build and set up selinux permissions to allow it, but I gave up and ended up just removing selinux from the kernel altogether.
Hmm... I'll take a look in the initrd of the Android boot images to see if there's anything in there that might be setting the SELinux mode.
Update: Bah. It seems the AOSP source of init can be configured to accept a ro.boot.selinux parameter, but I see no indication that the code is present in the stock init binary. The code also explains why the phone immediately reboots into recovery when SELinux support is disabled in the kernel.
Update 2: After attempting to download 18GB of AOSP source code, I think my dodgy way of disabling SELinux is really the best method.
Gene Poole said:
I believe you need to change the kernel config to allow command line switching of SELinux:
Code:
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
then modify the boot parameters of your boot.img adding to the cmdline:
Code:
enforcing=0 androidboot.selinux=permissive
I think that's the way. I went through all this but ended up just disabling SELinux altogether so I can't remember for sure if that's all.
Click to expand...
Click to collapse
bootloop ¯\_(ツ)_/¯
Just disable it in the config?
Why do you need it if you don't use it?
Jo_Jo_2000 said:
Just disable it in the config?
Why do you need it if you don't use it?
Click to expand...
Click to collapse
I prefer CONFIG_ALWAYS_ENFORCE = false instead of new_value = 0
Hello,
I could not find an answer on how to preload the expected libaries so I hope anyone can help me here.
I am a complete noob In devloping with Android Studio.
I tried to write a small app and ran it with the following errors while loading th e AVD (Android 5.1 , WVGA):
Code:
Cannot launch AVD in emulator.
Output:
libGL error: unable to load driver: i915_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i915
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: GLXBadContext
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 49
Current serial number in output stream: 48
emulator: ERROR: virtual device name contains invalid characters
emulator: could not find virtual device named '3.2_QVGA_(ADP2)_API_22'
I think to get this solved will not be quiet diffcult for advanced users.
Thank you verry much for your help! :good:
Some infos that might help you:
OS: Kubuntu 16.04
Android Studio 2.2.3
used coding language: Java
Hi,
First OP, so be gentle!
Please help. I'm trying to install Remix OS Player directly in Windows 10 and I get this message. I'm using a Dell Latitude 11 tablet; m5 processor, 8GB RAM, plenty of storage.
Error message:
emulator: WARNING: userdata partition is resized from 550 M to 3900 M
Hax is enabled
Hax ram_size 0xc0000000
HAX is working and emulator runs in fast virt mode.
ERROR: resizing partition e2fsck failed with exit code 8
emulator: Listening for console connections on port: 5554
emulator: Serial number of this emulator (for ADB): emulator-5554
*** BUG ***
In create_bits_image_internal: The expression bits == NULL || (rowstride_bytes % sizeof (uint32_t)) == 0 was false
Set a breakpoint on '_pixman_log_error' to debug
Assertion failed!
Program: C:\RemixOSPlayer\remixemu\tools\qemu\windows-x86_64\qemu-system-x86_64.exe
File: /var/lib/jenkins/jobs/workspace/build-remixemu-emulator-executable/emulator/external/qemu-android/ui/console.c, Line 1276
Expression: surface->image != NULL
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Any suggestions please? Apologies in advance if I'm being stupid. Or if someone could point me in the direction of a step-by-step guide, that would be great.
Thanks.
I'm trying to get into Xposed development and went through the tutorial here: github.com/rovo89/XposedBridge/wiki/Development-tutorial
I got up to the part where it says Trying it out, and that's where I stumble. When I run my module from Android Studio and reboot, I see:
Code:
01-04 20:45:43.001 18383-18383/? I/Xposed:
Loading modules from /data/app/com.germainz.activityforcenewtask-1/base.apk
01-04 20:45:43.013 18383-18383/? I/Xposed:
Loading class com.germainz.activityforcenewtask.XposedMod
[B]01-04 20:45:43.015 18383-18383/? I/Xposed:
Loading modules from /data/app/com.almostinteractive.swypearrows-1/base.apk [/B]
01-04 20:45:43.084 18383-18383/? I/Xposed:
Loading modules from /data/app/com.danation.xposed.swypetweaks-1/base.apk
01-04 20:45:43.115 18383-18383/? I/Xposed:
Loading class com.danation.xposed.swypetweaks.SwypeTweaks
My module fails to get a "Loading class..." line. And indeed, I see no logs from:
Code:
public void handleLoadPackage(XC_LoadPackage.LoadPackageParam loadPackageParam) throws Throwable {
XposedBridge.log("-------- LOADED " + loadPackageParam.packageName);
}
I've zipped up the whole Android Studio project (minus bins) and put it up on GDrive here: drive.google.com/open?id=1eWVxxMd5Ty9OF7gNCMn_cT_E5FDOgnVI
I'm testing on a Nexus 5X running Nougat 7.1.2 and Xposed version 89.
Really, I've looked and haven't found anything sufficiently similar to help me fix this. Any help you guys could give me would be incredible.