Hello guys i tried to install rfa but it gives this error"<stdin>Error only Position Independent executables are supported" can any one help me is there linker patcher ZIP for marshmallow?:crying:
Related
I’m trying to run the dumpxip.pl perl script..
I Installed activestate Perl (maybe you recommend a better perl?)
I also downloaded the win32 patch at http://www.xs4all.nl/~itsme/projects/perl/Win32-API-0.41-wj2.tar.gz
And ran makefile.pl
Then nmake
I get several errors saying it cant find API.pm struct.pm etc etc
I put the files in the places it expects and I get:
Can't locate loadable object for module Win32::API in @INC (@INC contains: C:/Perl/lib C:/Perl/site/lib .) at C:\DOCUME~1\ADMINI~1\Desktop\N1 sw\dumpxip.pl line 9
Compilation failed in require at C:\DOCUME~1\ADMINI~1\Desktop\N1\sw\dumpxip.pl line 9.
BEGIN failed--compilation aborted at C:\DOCUME~1\ADMINI~1\Desktop\N1 sw\dumpxip.pl line 9.
I’m sure I’m not installing it properly.
Any ideas? Has anyone else sucesfully run this?
Sorry, I originally posted this into the wrong category.
Hi all,
I have searched Google and this forum but cannot find a solution to a problem that I thought would be a little more common.
I have created an application from a guide in a book I am reading but when I try to run the app in the AVD I receive the following error:
Code:
The application ****** stopped unexpectedly. Please try again. FORCE CLOSE
This is not much help so I looked into logcat and found the following error:
Code:
E/dalvikvm( 493): Unable to open stack trace file '/data/anr/traces.txt': Permission denied
I don't know if this is the cause of my problem or maybe a second problem. I am running the AVD on Linux and there is no /data directory in the root of the filesystem. I (relucantly) created the directories in questions and set the permissions to 777. However this has not resolved the problem.
Is anyone able to help me understand what these errors mean?
Thanks.
Dear Friends,
I have Samsung Galaxy A7 (2018). I changed its pattern lock few days back, and Restarted the phone and realized that i forgot the pattern lock COMPLETELY.
I Googled the problem, and found most authentic post below:
RecoveryMode
I tried all methods on this post, but none could resolve my problem.
The first post said Download Aroma file manager on sd card and opt Update from SD card option to install Aroma Filemanager and delete the gesture.key file
I tried installing various versions of the Aroma File Manager app, but all installation aborted with Signature verification failed error having error code:
Code:
"E: failed to verify whole-file signature" "E: signature verification failed" "installation aborted."
I have some precious family pics inside the mobile, that why I want to recover it,
Please guide me how can i install the Aroma File Manager
I also tried the "adb" option from linux machine, where "adb devices" command didnt list my phone, i tried creating the file in /.android/somefile name but above command didnt list my file
Kernel compilation error '"aarch64-linux-android-gcc" is not allowed to be used.'
I'm building the kernel with LineageOS 17.1 / Android 10 r31 however the build process errors out during kernel compilation.
Specifically with:
Code:
"aarch64-linux-android-gcc" is not allowed to be used. See https://android.googlesource.com/platform/build/+/master/Changes.md#PATH_Tools for more information.
make[3]: *** [/home/saltoin/android/lineageos-17.1/kernel/samsung/universal8895/scripts/Makefile.build:153: scripts/mod/devicetable-offsets.s] Error 1
Following the link says that any host tools in PATH won't be allowed to be used during compilation. However, `aarch64-linux-android-gcc` is not from my path but supplied by the build tools. Unless I'm mistaken in that assumption.
Regardless, exporting TEMPORARY_DISABLE_PATH_RESTRICTIONS=true allows aarch64-linux-android-gcc.
Unless I'm missing something, I don't believe I should be getting this error.
Thoughts?
Hello there, have you found any solution?
TEMPORARY_DISABLE_PATH_RESTRICTIONS=true doesn't work in the config file. What do you mean by export? Thanks in advance for help.
Build System Changes for Android.mk Writers
As a temporary measure, you can set TEMPORARY_DISABLE_PATH_RESTRICTIONS=true in your environment to temporarily turn off the error checks and allow any tool to be used (with logging).
Hi Folks,
I am new to rooting and struggling with a problem. I have an old zenfone 5(ASUS_T00J) model. I am using custom rom BlurOS found in the below thread:
https://forum.xda-developers.com/zenfone-5/development/rom-bluros-version-1-0-zenfone-5-t3619058
I am trying to flash Magisk from TWRP recovery but it's failing with below error:
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Invalid Block device on '/dev/block/zram0
none
swap
defaults
zramsize=67108864
', 'swap', 36
Updating partition details..
...done
Full SELinux support is present.
MTP Enabled
Installing '/sdcard/Download/Magisk-v20.4(20400).zip'..
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
**********************
Magisk 20.4 Installer
**********************
- Mounting /system
- Target Image: /dev/block/by-name/boot
- Device platform: x86
- Constructing environment
- Adding addon.d survival script
E: Error executing updater binary in zip '/sdcard/download/Magisk-v20.4(20400).zip'[/QUOTE]
Error flashing zip '/sdcard/download/Magisk-v20.4(20400).zip'
Updating partition details...
...done
Updatrer Scripts are in below Google Drive Location:
https://drive.google.com/file/d/1SdtXdgB-iCB1X5PL3OCsZLrcUT6WlRzX/view?usp=sharing (Updater Script)
https://drive.google.com/file/d/1X2lupRfMUj-n5pRx2c0h0NQHUvfOXJAP/view?usp=sharing (Updater Binary)
Steps followed by me:
1. Installed latest Magisk manager from GitHub
2. Downloaded the latest zip file prompted by Manager
3. Reboot in TWRP recovery
4. Flashed the newly downloaded zip file
Appologies in advance if this is not the right forum or I have violated any guidelines. Let me know if you need any more details from my side. Thanks in advance.
Update
The issue still remains. Tried to find solutions online. Below methods were suggested. Since, I am new to this, might have tried something silly in the process.
Method 1:
Flash the Rom boot image via TWRP
Result: Did not prompt to provide any partition but Failed with error 'No Partition selected for flashing'. Updated the TWRP to 3.2.3 and tried the same thing again. This time prompted for a partition but no option was available that I could provide there and failed with the same error.
Method 2:
Patching the Boot image of my ROM through magisk patch
Result: Extracted the boot image for BlurOS Custom rom and tried to patch it through magisk Manager. Installation failed with 'Unable to repack boot image'.
Since I updated the TWRP, tried to flash the magisk zip file hoping for some other error (at least). It failed with below error message:
Installing zip file '/sdcard/Download/Magisk-v20.4.zip'
Checking for digest file...
Skipping Digest check: No digest file found
*************************
Magisk 20.4 Installer
*************************
- Mounting /system
! Unable to detect target image
- Unmounting partitions
Updater process ends with error: 1
Error Installing zip file
Updating partition details...
... done
Kindly let me know if you guys have any pointers. Any leads will be appreciated.
Magisk is unable to patch x86 boot.img's, so you have to use "android image kitchen"
Magisk patches Ramdisk file so you have to do:
move x86 ramdisk to ARM boot.img
Patch it via magisk
move patched ramdisk back to x86 boot.img
You can try boot.img's that I made for RR and Lineage in my thread. They are pre-patched with magisk 20.4
Anyways, is BlurOS better than lineage or RR ?