Disclaimer: I am not responsible for anything bad that may occur from the use of this zip, but I will take all the credit you can give if it works for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ExtSD Fix
Download latest stable - MD5 checksumDownload latest dev - MD5 checksum
In KitKat, Lollipop and Marshmallow, policies on writing permissions for external SD cards have been changed. This flashable recovery file automatically appends the correct permissions to the file as explained in many tutorials on the web (here or here) or as what many apps do (here).
Advantages
The advantage of this flashable zip over the other methods is that:
you don't need to install any apps,
you can revert by reflashing (not tested for marshmallow),
it does not require you to have root (needs to be confirmed),
[*]you don't need a custom recovery (needs to be confirmed).
Installation
It can insert and remove the permission to write on the external sdcard. To install follow these steps:
Turn off phone,
Boot into recovery,
Backup your system and data partition,
Flash this zip file once,
Reboot phone normally.
To revert the changes, follow the same steps again. This means that flashing it twice will have no effect.
Marshmallow is not supported yet, implementation is in progress.
Note: On Marshmallow, busybox will be installed if not already present. It can also be installed as a standalone app. You should an also add init.d support to your phone if not already available using an app.
How to report a bug
Check if someone else reported that it did/didn't work,
Backup, clean flash, reinstall all apps and then flash ExtSD Fix,
Submit a bug report here with both the original and modified packages.xml and the recovery log file as suggested here.
Changelog
v2.9b - 2016-06-09
Added double flashing revert for MM.
v2.8b - 2016-06-09
Added more logging to:
during flashing: /data/ExtSD_Fix_RW_inst.log
during boot: /data/ExtSD_Fix_RW_initd.log
v2.7b - 2016-06-08
Renamed script,
Changed permissions.
v2.6b - 2016-06-07
Changed permissions.
v2.5b - 2016-06-07
Changed permissions,
Added support for limited backup files.
v2.4b - 2016-06-05
Corrected bugs.
v2.3b - 2016-06-02
Included debug messages.
v2.2b - 2016-06-02
Corrected bugs. "ERROR:2" should be fixed.
V2.1b - 2016-05-19
Implemented solution from here and here.
V1.9b - 2016-05-04
Implemented solution from here. PLEASE TEST AND REPORT.
V1.8b - 2016-02-04
Corrected bug for Marshmallow.
V1.7b - 2016-02-02
Added support for Marshmallow.
V1.6b - 2016-01-27
Added revert on second run.
V1.5b - 2016-01-26
Corrected bug in check for API version.
V1.4b - 2016-01-26
Changed format of backed up filename.
Added check for API version ( 19<= API <= 22 ).
V1.3b - 2016-01-22
Backed up file is renamed with time and date.
V1.2b - 2016-01-21
Moved code into update-binary.
V1.1b - 2016-01-19
Removed testing commands.
V1.0b - 2016-01-18
Initial submission
XDA:DevDB Information
ExtSD Fix, Tool/Utility for all devices (see above for details)
Contributors
rufus.wilson
Version Information
Status: Testing
Current Beta Version: v2.9b
Beta Release Date: 2016-06-09
Created 2016-01-18
Last Updated 2016-06-15
Tested devices and systems
When you have tested it could you report your experience with the device model and the android version you used.
I will summarize here the success and failures.
Success
OnePlus X - CM 12.1
N4 w/TW 6.0.1 MM
sony z3c concept rom(mm)
Samsung Galaxy Express 2 with CM13
Xperia M with CM13
Sony Z3 .570 stock
asus zenfone 2
Asus ZenFone 4 - Stock v7.4.4 (Lollipop) (all opened apps had FC on reboot)
asus zenfone 5 XOSP rom
Sony Xperia Z3 (Sometimes is overwritten)
SM-G910F Rom ALEXNDR COJ3 Deodexed
Samsung galaxy s5 g900f stock marshmallow
z3c with rom slimm 1.5
Galaxy S7 SM-G930FD 6.0.1 Rooted Xposed
Xiaomi Redmi 1S RR 5.6.8 which is a CM13(R28)
Sony Z3 D6653 running on RXSW Marshmallow Edition [3.0.0] [12/04/16] [6.0.1]
LG L90 D415
Redmi 1s using OctOS M ROM
xt907 JBBL- cm13, 01-05-2016
Redmi 2, CM 13.1-20160417-SNAPSHOT
z3 570 rxsw
LG G3 VS985 variant running CM 13 6.0.1 nightlies. Using 777 Kernel & TWRP 3.0.2
z3 dual d6633 running marshmallow 6.0.1 official
Oppo find 7a x9006 on 6.0.1 rooted with twrp 3.0
Failure
LG D855 32 Gb with CM13 2016-05-10 and TWRP 3.0.0.0 recovery
Sony z3 MM
g900f blisspop 6.01
Samsung N7105T, unofficial wilson3q cm 13
Reserved
not work with my device
zenfone 4
here is my recovery log
hiimpig1 said:
not work with my device
zenfone 4
here is my recovery log
Click to expand...
Click to collapse
Thank you for coming back to me.
Do you have CWM recovery or TWRP?
rufus.wilson said:
Thank you for coming back to me.
Do you have CWM recovery or TWRP?
Click to expand...
Click to collapse
im using twrp 2.8.7.0
hiimpig1 said:
im using twrp 2.8.7.0
Click to expand...
Click to collapse
I have uploaded a new version. Could you test that one?
rufus.wilson said:
I have uploaded a new version. Could you test that one?
Click to expand...
Click to collapse
i flashed, after that all my apps got FC
but its worked
I have a proble with titanium backup: no space, but i have more than enough
Is this also working?
Galaxy s5, cm13 (MM)
hiimpig1 said:
i flashed, after that all my apps got FC
but its worked
Click to expand...
Click to collapse
Was a reboot enough to solve the problem?
phoberus said:
I have a proble with titanium backup: no space, but i have more than enough
Is this also working?
Galaxy s5, cm13 (MM)
Click to expand...
Click to collapse
It should be working. You can always go back by copying back the file in a rooted shell command with the system partition mounted:
Code:
cd /system/etc/permissions
cp platform.xml-201*.bak platform.xml
chmod 0644 platform.xml
rufus.wilson said:
It should be working. You can always go back by copying back the file in a rooted shell command with the system partition mounted:
Code:
cd /system/etc/permissions
cp platform.xml-201*.bak platform.xml
Click to expand...
Click to collapse
Hey @rufus.wilson
Flashed v1.3b, but it didn't work. And then I I restored the file with this two commands. After that, almost all the apps crash (FC) when I want to start it and when I can open an app, it hasn't any internet connection.
Can I fix this or must I wipe /system and /data?
(cache and dalvik cache already wiped)
I have noew zero permission, I can't even take a screenshot :/
Galaxy s5 (G900F) => CM13 (MM)
rufus.wilson said:
Was a reboot enough to solve the problem?
Click to expand...
Click to collapse
no its not
phoberus said:
Hey @rufus.wilson
Flashed v1.3b, but it didn't work. And then I I restored the file with this two commands. After that, almost all the apps crash (FC) when I want to start it and when I can open an app, it hasn't any internet connection.
Can I fix this or must I wipe /system and /data?
(cache and dalvik cache already wiped)
I have noew zero permission, I can't even take a screenshot :/
Galaxy s5 (G900F) => CM13 (MM)
Click to expand...
Click to collapse
I edited my answer as I forgot to add a command to change the permissions of the file.
Code:
chmod 0644 /system/etc/permissions/platform.xml
hiimpig1 said:
no its not
Click to expand...
Click to collapse
Can it be a permission problem? Look here.
rufus.wilson said:
I edited my answer as I forgot to add a command to change the permissions of the file.
Code:
chmod 0644 /system/etc/permissions/platform.xml
Click to expand...
Click to collapse
Didn't work for me, but I have a backup :good:
phoberus said:
Didn't work for me, but I have a backup :good:
Click to expand...
Click to collapse
Which version of android do you use?
hiimpig1 said:
no its not
Click to expand...
Click to collapse
Which ROM are you using?
rufus.wilson said:
Which ROM are you using?
Click to expand...
Click to collapse
im using stock rom 7.4.4 from asus
hiimpig1 said:
im using stock rom 7.4.4 from asus
Click to expand...
Click to collapse
Do you still have the FC?
Related
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://docs.google.com/uc?id=0B5c3gpyMBJusXzRfRWg4TXhZdVE&export=download
aromafm_cooper.zip (v1.91)
http://www.upload.ee/files/3959191/aromafm_cooper.zip
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Ace, Tool/Utility for the Samsung Galaxy Ace S5830
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07
:FAQs:
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.
NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
Very nice... will try it soon... :good:
Wow this should be great
I tried the recovery and it works. Installation is quick and simple and works just as described. Installing, wiping, backups, touch (up and down) and everything else works just as said. Kudos to you OP!
The last thing I wanna know:
After installing/restoring anything, can you successfully reboot to system?
You should also try Aroma File manager, it's the best part of this recovery.
Gonna Try...
@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and then boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk
nizar.nasani said:
@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and the boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
Expect a fix soon!
I was understanding the problem for last few days (because same happens to other two devices also) and finally got the solution and I'll be re-compiling recovery as soon as I get some time.
UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.
Am I dreaming? Thanks for revive my old Ace
Sent from my Nexus 5 using XDA Premium 4 mobile app
Bhargav97 said:
UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.
Click to expand...
Click to collapse
swipe left and right dont work for me ????
Rhievaldo said:
swipe left and right dont work for me ????
Click to expand...
Click to collapse
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.
Bhargav97 said:
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.
Click to expand...
Click to collapse
always read it,, but forgot about that. Sorry... cause read it at 23 march, and try at 30 march..
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing
everything seems to be working for me
---------- Post added at 06:43 PM ---------- Previous post was at 06:34 PM ----------
actually, all features work butkeeps rebooting into recovery,, not sure if its a problem restoring a back up ill try installing a new rom
edit,, yes it reboots into recovery no matter what,, damn,, nearly close to perfect
Bhargav97 said:
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing
Click to expand...
Click to collapse
yes right when i reboot to system it reboot to recovery, the same as the previous time.
There was a little bug which caused issue for rebooting to system. I just fixed it and asked @chraso to compile. So, now finally it's done! Updated first, second and third posts.
Report back for the download link put up on first post.
i've test almost everything and i can say this is the best recovery ever made for ace ✌
thanks for bring it to our ace
sent from my kitkat ACE
Fix found and released:
http://forum.xda-developers.com/showthread.php?p=60454547
Downloads & instructions: http://forum.xda-developers.com/showthread.php?t=3034811
Discussion & Q&A:http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I asked moderator to close this thread as issue was fixed by releasing new version of Xposed framework. Please send your further questions and post to respective thread.
This thread is about workaround found for bootloops of Xposed in XPERIA family Lollipop. Because of development progress, I have decided to remove historical development, you can see it here:
LATEST VERSION will be always posted at the END of this post
PLEASE READ INSTRUCTIONS .... The attachment IS NOT flashable!!! For flashables see EDIT 5 and bellow...
I hope I can present some good news for users with locked bootloaders who are getting bootloops with Xposed and Lollipop.
This is still continuous WIP. Know what you do, this is a development thread.
For time being, most complete solution by my opinion was made by @mionica, see EDIT 6 and hist post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123? and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
As you may already know, we have find out, that some undetected error is causing system to bootloop, if too many applications are installed.
Exact numbers are varying between different ROMs and devices, generally the maximum number of apps is about 320-330.
Debloating (uninstalling unnecessary apps) helps, but remains limiting and for many frustrating. After a research, we have found out,
that there is probably a bug, that is causing many files being left open when booting Lollipop with Xposed.
Users on unlocked bootloader may modify certain kernel parameters to raise number of open files. This can not be done on Locked Bootloader.
After some research and hours of experiments, I found a way, how to change the filelimit for Zygote and subsequent processes. Therefore every child of zygote (hence every app etc.) will inherit raised open files limit from 1024 to 4096.
This change should work on all 5.0 compatible system, not only XPERIAs, however I only tested it on Z3 D6603 fw 690. But the modification
is done on Linux system level, therefore it should teoretically work just everywhere... It should work also on Locked bootloaders as well.
The principle is easy, however implementation was a tricky, because of lack of native linux utils support on Android and fact that we can not
easily modify booting behaviour. But gladly enough we have XZDualRecovery (gret thanks @[NUT])....
XZDualRecovery enables to call init scripts on startup. I have created a startup script that waits for zygote process to come up, and calls
external program that changes open file limits for that process. This external program is compiled by me from source provided by http://lzone.de/cheat-sheet/ulimit
Prerequisities: Functional XZDualRecovery or other form of init.d support.
Installation:
Extract downloaded ZIP file, it contains:
flimit-binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
remount /system rw (mount -o remount,rw /system)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
test run installation:
Code:
su
/data/flimit/flimit $(pgrep zygote)
output should be:
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=1024; hard=4096
New limits: soft=4096; hard=4096
If not, check permissions etc.
Check script by running:
Code:
su
sh /system/etc/init.d/01_flimit
it should now give output (if you succesfully ran /data/flimit/flimit....):
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=4096; hard=4096
New limits: soft=4096; hard=4096
reboot
Thats all. Now you can install and update lot more applications. Now I have about 455 packages reported by pm list packages and no bootloop.
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
EDIT:Please let me know, if you had to modify the script or instructions to work on your device, so I can perhaps make better or more universal version. Thank you guys.
EDIT 2:While this workaround makes it possible to run Xposed on untouched vanilla Stock ROM, you may still consider debloating it, as debloating will make run your device more smoothly and saves battery. Guys who made debloating scripts made significant efforts in identifying which apps can be safely removed without harming any significant functionality.
EDIT 3:The ZIP is NOT flashable, follow instructions ^^^^ --- buddy @McBane87 is developing flashable version.
EDIT 4:Buddy @nurps found a bug causing Opera browser to quit upon starting. @mionica proposed lowering softlimits for open files to 2048 from 4096 in first version of script. Version 1.1 is released.
EDIT 5:Buddy @McBane87 created customized flashable version of this workaround, so you can flash it from recovery if you struggle with bootloops, dont like to wait fro 300apps to optimize after Dalvik wipe and mess with adb/terminal..
http://forum.xda-developers.com/showthread.php?p=60276913
EDIT 6:Buddy @mionica published another flashable zip. It is complete installer for the workaround, so far most sofisticated workaround from system point of view. The uninstaller completely removes Xposed if you are too tired of it and forgot to make backup Files are bellow, for instructions etc. check it out on http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123 and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
Changelog:
v1: Initial release
v1.1: Changed limits to 2048 from 4096 as high limits caused Opera Webbrowsers to crash
v2.0 Reference script - for production please flash @mionica version of flashable, my script is published for educational purposes. added mionicas mod to detect only changed limits and subsequently remove only those that are child of zygote
***************************************
I would like to thank mainly to @[NUT] and to guys who made significant effort with debloating, made other discoveries or were an inspiration
for me, including but not limited to @serajr @moly82 @AndroPlus (for his work on file limits in kernel) @redincali and of course to @rovo89
for his Xposed framework. My apologies if I forgot someone, PM me, its 2 o'clock in morning
or in this post http://forum.xda-developers.com/showpost.php?p=60349914&postcount=354
While I have developed initial version (see history), other guys (mainly @mionica and @McBane87) greatly enhanced and redeveloped whole thing.
Current development version and downloadable files you can always find in @mionica post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123
@mionica managed to analyze boot process on both ROMs with and without Xposed and came to conclusion that leaks are caused by Xposed process leaking open file handles, see here http://forum.xda-developers.com/showpost.php?p=60373854&postcount=417
There is a current version of the workaround fix (see above), that seems to be the last possible, before Xposed will be released with patch addressing that issue. Good news is that thanks to @mionica precise analysis, @rovo89 - developer of Xposed is already aware of the problem nad it´s cause.
Recommended installation steps:
by @mionica
Anybody who is still having any kind of issues, for whatever reason, please do the following:
get into TWRP;
install, in this order, without rebooting:
xposed-uninstall-v1.1.zip
If you don't have an sd card, you'll need to reboot once after the uninstall .zip, boot the system normally, then get back in the recovery and install the other 3. This only applies to people who don't use an SD card
xzdr-busybox-enable-v1.0.zip
xposed-sdk21-arm-date.zip
xposed-leakplug-v1.2.zip
copy the logs to the PC, over USB:
uninstall_xposed.log
install_busybox.log
install_leakplug.log
each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard)
reboot to system
Thanks in advance for not asking any questions about whether you have to do any of these steps; yes, you have to.
Click to expand...
Click to collapse
If you follow other instructions than provided by @mionica please get then support from someone else than him.
The basic idea behind is that Xposed bootloops because of it exhausted resources available due to probably internal bug. The workaround basically provides higher limits for open files during boot and restores previous limits after device has booted. The latest flashable installer is very advanced and automates the installation, including necessary checks for proper XZDR configuration, busybox etc.
When you experience bootloops after installing Xposed, or you had Xposed working and it started to bootloop after you have installed new app or upgraded a system app, simply reboot to recovery and flash the zip. No need to wipe anything.
When installing new, I recommend flashing this zip first, then install Xposed usual way (flash, wipe, reboot, install Xposed apk, install modules).
Be aware that while the workaround works for about 80% of cases, there are people who have lots of applications or heavily modified system, experiencing random reboots. Cause is under investiogation, but most probably is in Xposed itself.
Excellent work friend @ondrejvaroscak. Congrats! Awesome
Was waiting a long time for this! Thanks man! working perfectly.
Working perfectly on D6603, thanks
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Thanks Bro , Very Nice !!
Perfect Work !!
Z1, C6903
Thank you for this great solution, works on Z1.
NetSkill said:
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Click to expand...
Click to collapse
Unless I will be blessed with some debugging skills, I have no clue... I think limit is just much higher. Once you reach limit you can simply edit script and change two numbers...
Yes, now regular reboot works.
Sent from my D6603 using XDA Free mobile app
norti said:
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Click to expand...
Click to collapse
I think it will take time, because first @rovo89 would probably want to investigate, how much is it a bug, a constellation of coincidences and so on. I am not sure, if the same bootloops appear only on XPERIAs or it is a phenomenon on other brands as well... And given the fact, that big number of Samsungs can not run Xposed at all, maybe he will try to solve that Samsung puzzle as priority. But that is only guess..
Working on fully setup 5.02 on Z2 thanks.
ondrejvaroscak said:
Installation:
Extract downloaded ZIP file, it contains:
flimit - binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
Click to expand...
Click to collapse
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
hispanico957 said:
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
Click to expand...
Click to collapse
Any recovery that supports init.d and byeselinux. So if you find this two settings in your XZDR.prop, you just enable them by setting "true".
I tested with 2.8.12,
XZDR.prop is located in /sdcard1 so its External SD card. If no SD card, then its located in /cache.
/data/limit you create absolutely, it means in / is folder data (that already exists) and you create flimit in /data, so:
Code:
adb shell
su
mkdir /data/flimit
byeselinux you enable by setting "dr.keep.byeselinux=true" in XZDR.prop (it may be set to false by default depending on version fo XZDR you have).
Ok fine... for verify all you said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dont find ? where i wrong ??? the folder and file are present
Thank
Hispa
P.S.
Whe you said :
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
Click to expand...
Click to collapse
i mean to pu dr.initd.active=false ??
and last after all i can install xposed over .726 odexed ?
hispanico957 said:
Ok fine... for verify all you said:
su
/data/flimit/flimit $(pgrep zygote)
this command from ADB ?
Thank
Hispa
Click to expand...
Click to collapse
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Great thanks
ondrejvaroscak said:
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Thank solved but see please my post #14
Hispa
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Pandemic said:
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Click to expand...
Click to collapse
+1 i too cannot find thet line
hispanico957 said:
Ok fine... for verify all you said:
dont find ? where i wrong ??? the folder and file are present
Click to expand...
Click to collapse
can you run "ls -l /data/flimit/*" and paste output to reply?
Whe you said :
i mean to pu dr.initd.active=false ??
Click to expand...
Click to collapse
Exactly, when you put dr.initd.active=false and have full stock, it should again bootloop. Then you replace the XZDR.prop file with version with init.d enabled and it should boot normally again.
and last after all i can install xposed over .726 odexed ?
Click to expand...
Click to collapse
I think without any problem. Deodexing has nothing to do with working Xposed, but it is may be necessary for some modules (Gravitybox?)?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
I noticed that old init.d enabling methodes aren't working anymore with latest firmwares on the Xperia Z5
I tried many of available traditional methodes (that relies on init.qcom.post_boot.sh, install-recovery.sh ... I believe they stopped working because a lot of them used SuperSU ), also tried many magisk init.d emulators but none of them worked as well. My mod uses simpler and modern method I thought I'd share it with you to help those who still have troubles activating init.d especially newbies
What is init.d ?
Init.d plays an important role in the world of Android development and customization It allows users to install scripts and mods to be run at boot—everything from battery tweaks to performance tweaks..
Click to expand...
Click to collapse
Compability
Code:
- Any device
- Tested with Magisk v14 but should work on all V12+
Bugs
Code:
- You tell me
Downloads
Second post
Credits
@topjohnwu for making this possible
RXSMB Team
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2017-09-27
Created 2017-09-23
Last Updated 2017-07-29
[MOD][Magisk][Universal] A simple init.d enabler (system-less) [Fixed*]
Downloads
Please use remover before updating to new versions
Make sure you read the notes above carefully before downloading !
Magisk 14+
https://www.androidfilehost.com/?fid=962021903579480972
Magisk 15+
https://drive.google.com/open?id=1bzT5Uu2jIZDJpcaBvSMYqF11M-YYz5SJ
Remover UPDATED 27.09.2017
https://www.androidfilehost.com/?fid=889964283620753913
How to make sure it's working ?
Code:
- Go to [B]/data/[/B] if you find the file [B]"initd_test.log" then congrats it's working [/B]
Changelog
Code:
2.2 | 29/09/2017
- Bug fixes for some devices
2.1 | 27/09/2017
- Removed sleep for 30 sec post boot (to avoid conflicts with some scripts)
2.0 | 24/09/2017
- Changed permissions from 777 to 755 (standard)
- Added writing permissions to init.d folder too
1.0 | 23/09/2017
- First release
DO NOT STEAL MY WORK!!
FEEL FREE TO USE MY MOD IN YOUR ROM, JUST GIVE PROPER CREDITS !
Flashed buh phone stuck at bootlogo, had to flash uninstaller zip before phone boots up.....
Flashed the mod in Magisk and rebooted, the mod made the fingerprint option unavailable in Settings. (stock 7.1.1 140)
Disabled the mod Magisk and rebooted, fingerprint appeared again.
Can you look into it?
P/s: flash the mod directly in TWRP will get you stuck at boot logo.
whalesplaho said:
Flashed buh phone stuck at bootlogo, had to flash uninstaller zip before phone boots up.....
Click to expand...
Click to collapse
colorado48 said:
Flashed the mod in Magisk and rebooted, the mod made the fingerprint option unavailable in Settings. (stock 7.1.1 140)
Disabled the mod Magisk and rebooted, fingerprint appeared again.
Can you look into it?
P/s: flash the mod directly in TWRP will get you stuck at boot logo.
Click to expand...
Click to collapse
Please update to new fixed version I updated the link now for second time nothing hardcoded it's working perfectly for me on 32.4.A.0.160 should do same for all roms/devices
Do not forget to use remover before updating .. enjoy
New version works now ?
Fingerprint works now too.
I still dnt have tha log file.... But test file inside init.d folder!!
Woooooooppppppssss......
colorado48 said:
New version works now
Fingerprint works now too.
Click to expand...
Click to collapse
good bro enjoy
whalesplaho said:
I still dnt have tha log file.... But test file inside init.d folder!!
Woooooooppppppssss......
Click to expand...
Click to collapse
how is that, what kernel/rom you are using.. working fine on stock here
Also note that you might need to wait 30sec at least after boot before init.d takes effect
So try to refresh in your file manager and check the result in /data/
korom42 said:
good bro enjoy
how is that, what kernel/rom you are using.. working fine on stock here
Also note that you might need to wait 30sec at least after boot before init.d takes effect
So try to refresh in your file manager and check the result in /data/
Click to expand...
Click to collapse
Im on crdroid lineage os and using stock kernel too brov.. 30secs? Okay will try again.
New version is up ! .. minor changes but better update
2.1 | 27/09/2017
Code:
- Removed sleep for 30 sec post boot (to avoid conflicts with some scripts)
Bro @korom42 there is no initd_test.log in the data folder on my XZ
Verstuurd vanaf mijn F8331 met Tapatalk
This works but breaks both safetynet checks for me on a Z3C LOS 14.1 with Universal safetynet fix 10.1.
@korom42, first of all, thanks for this awesome work. I can confirm that this mod is working on Xperia Z5 Premium E6833, 7.1.1 stock rom with magisk 14.2 beta.
BUGS:
1) the test file present in the /system/etc/init.d namely "00test" is undeleteable. I tried remounting the system as R/W but still get the message "Device or Resource Busy".
2) When I create my own scripts (which is just another test script or any other) in the /system/etc/init.d folder, it gets saved successfully with permissions rwx-r-x-r-x. But when i restart the device, my created scripts get deleted automatically without execution.
Is their something I'm doing wrong???
P.S: I have attached the script I'm using for your consideration....
Regards
Adil
@korom42, i figured out the problem.
EVERYONE FACING PROBLEMS WITH THIS MODULE SHOULD PLACE THIER SCRIPTS IN THE FOLLOWING PATH:
/magisk/simple_initd/system/etc/init.d
DON'T PLACE THE SCRIPTS IN:
/system/etc/init.d
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Thanks alot for this extremely awesome module @korom42
Regards
Adil
Adil Tariq said:
[MENTION=5033594]
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Click to expand...
Click to collapse
However the module breaks safetynet immediately after installing. Is it because of the test output file created in /data or otherwise?
I'm using this init.d link module instead now with a small mod and workaround. I've written my experiences in that thread. It's not straightforward but it's the only semi-working safetynet init.d for me.
Adil Tariq said:
@korom42, first of all, thanks for this awesome work. I can confirm that this mod is working on Xperia Z5 Premium E6833, 7.1.1 stock rom with magisk 14.2 beta.
BUGS:
1) the test file present in the /system/etc/init.d namely "00test" is undeleteable. I tried remounting the system as R/W but still get the message "Device or Resource Busy".
2) When I create my own scripts (which is just another test script or any other) in the /system/etc/init.d folder, it gets saved successfully with permissions rwx-r-x-r-x. But when i restart the device, my created scripts get deleted automatically without execution.
Is their something I'm doing wrong???
P.S: I have attached the script I'm using for your consideration....
Regards
Adil
Click to expand...
Click to collapse
Adil Tariq said:
@korom42, i figured out the problem.
EVERYONE FACING PROBLEMS WITH THIS MODULE SHOULD PLACE THIER SCRIPTS IN THE FOLLOWING PATH:
/magisk/simple_initd/system/etc/init.d
DON'T PLACE THE SCRIPTS IN:
/system/etc/init.d
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Thanks alot for this extremely awesome module @korom42
Regards
Adil
Click to expand...
Click to collapse
Alright, if you managed to use the mod while keeping SafetyNet bypass working than that's great
but I won't change anything since it's not a reliable way because the user will have to move his files each time adding new scripts
- for deleting the 00test file did you try a different file manager .. root browser works fine here
Infy_AsiX said:
However the module breaks safetynet immediately after installing. Is it because of the test output file created in /data or otherwise?
I'm using this init.d link module instead now with a small mod and workaround. I've written my experiences in that thread. It's not straightforward but it's the only semi-working safetynet init.d for me.
Click to expand...
Click to collapse
- Just disable the module from Magisk Manager whenever you need SafetyNet bypass back .. will try to make it SafetyNet compatible in next versions if possible
@korom42 i just want to report that safety is now also broken on my Xperia Z5 Premium E6833 Stock Rom (LOL) after just 2 reboots. Uninstalling this module fixes the issue. Hope you will find a way to make this module work with safetynet....
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
As for safety net, there is the very easy way to fix it. Just reinstall busybox version 27.2 after each reboot that will return safetynet back to pass state. I use meefik and that helps.
Click to expand...
Click to collapse
Download the app here
Altenative by Stephen (Stericson)
korom42 said:
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
Download the app here
Altenative by Stephen (Stericson)
Click to expand...
Click to collapse
Great! it's working!
Thanks!
korom42 said:
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
Download the app here
Altenative by Stephen (Stericson)
Click to expand...
Click to collapse
crisout said:
Great! it's working!
Thanks!
Click to expand...
Click to collapse
Did you find out another fix to safetynet? It's not working anymore
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the Dolby Atmos ported from BQ Aquaris X5 and Lenovo K6 stock Nougat ROMs. Like with @guitardedhero's ZTE Axon 7 Dolby Atmos Oreo port, it requires the stock audioserver from the roms. This greatly limits it's compatibility and likely won't work on devices/roms with a lot of audio customization. However it should work on most
Huge thanks to @ahrion who taught me everything I know about app porting
These installers utilize my Unity installer that will install the mod to magisk or system depending on the device setup and will prepare it for any root solution (for anything other than magisk, supersu, and phh superuser, you will need init.d support)
Troubleshooting:
Audio Mod Troubleshooting Guide
Installation/Upgrade:
Flash the zip and your done! If your flashing a newer version of this mod, the installer will detect the old one and perform an upgrade
Uninstallation:
Just flash the zip again and it'll detect the current install and uninstall it. Pretty easy huh?
Magisk Version Compatibility:
v15.3 - v18.1
DOWNLOAD
Credits of Originality:
- Dolby
- BQ
- Lenovo
XDA:DevDB Information
Collective Dolby Atmos® Nougat Port Thread [Unity], App for the Android General
Contributors
Zackptg5
Version Information
Status: Stable
Current Stable Version: v1.8
Stable Release Date: 2019-01-16
Created 2019-01-24
Last Updated 2020-01-01
Great work , the new UI is awesome , and the dynamic mode is a very good addition to the old modes
Thanks ?
Sent from my X5 Plus using XDA Labs
:highfive:
Sorry but not work on my Redmi 4x RR 5.8.5 7.1OS. FC.
repey6 said:
Sorry but not work on my Redmi 4x RR 5.8.5 7.1OS. FC.
Click to expand...
Click to collapse
Can you go over the troubleshooting section of the op?
Zackptg5 said:
Can you go over the troubleshooting section of the op?
Click to expand...
Click to collapse
Sorry.Not other mod . Clear installation. Log maybe later. And can't unistall it.
@Zackptg5, flashed this Dolby-BQ-X5-v1.0.zip in twrp_3.0.2-1_sm-a310 (Samsung exynos SM-A310F) on clean stock nougat 7.0, no boot even when restoring original audioserver. Only exit is restoring system. Recovery.log and system space screenshot attached.
mohand06 said:
@Zackptg5, flashed this Dolby-BQ-X5-v1.0.zip in twrp_3.0.2-1_sm-a310 (Samsung exynos SM-A310F) on clean stock nougat 7.0, no boot even when restoring original audioserver. Only exit is restoring system. Recovery.log and system space screenshot attached.
Click to expand...
Click to collapse
The recovery log outlines the problem: you have no space left in your system partition. The tricky thing with audioserver is that it requires proper permissions and chcon set or you won't be able to boot. When you flash this mod again to uninstall it, it restores stock audioserver and sets those permissions but since the install itself never finished, there's no telling what would happen. I recommend switching to magisk as it stores all of its mods on your /data partition which would avoid this problem
Zackptg5 said:
The recovery log outlines the problem: you have no space left in your system partition. The tricky thing with audioserver is that it requires proper permissions and chcon set or you won't be able to boot. When you flash this mod again to uninstall it, it restores stock audioserver and sets those permissions but since the install itself never finished, there's no telling what would happen. I recommend switching to magisk as it stores all of its mods on your /data partition which would avoid this problem
Click to expand...
Click to collapse
The attached screenshot of system partition shows that there's 206.08Mb space available. Restored audioserver with 0755 permissions. Thus the issue is elsewhere. Fyi, I used to flash each of gh's Dolby Atmos™ for Oreo test builds and I always manage to get out of the no boot issue by the audio server restoring trick.
As for using magisk, which I tried and have sometimes the issue of no apps in drawer though modules present in magisk, I still feel more comfortable with supersu. Thanks for your reply.
mohand06 said:
The attached screenshot of system partition shows that there's 206.08Mb space available. Restored audioserver with 0755 permissions. Thus the issue is elsewhere. Fyi, I used to flash each of gh's Dolby Atmos™ for Oreo test builds and I always manage to get out of the no boot issue by the audio server restoring trick.
As for using magisk, which I tried and have sometimes the issue of no apps in drawer though modules present in magisk, I still feel more comfortable with supersu. Thanks for your reply.
Click to expand...
Click to collapse
That's not enough. You need to do this:
Code:
chown 0:2000 /system/bin/audioserver
chmod 0755 /system/bin/audioserver
chcon u:object_r:audioserver_exec:s0 /system/bin/audioserver
The no space error actually referred to the /system/vendor folder so I'm not sure how you're partition layout is. The only time modules won't show up in magisk is when there's a bad post-fs-data script that errors out and/or takes too long to finish. Magisk is easier because you can just delete the module folder and be done with it
Perfectly work with redmi note 4(mido) on official miui beta rom with magisk..The Ui is fantastic...but i wonder what demo actually do..i just see the slideshow but none of any sound.. @[email protected] ..nah but i dont care much about it as long the mod work . 1 more things is when i install it alongside with ainur sauron...the dolby atmos will crash.... But without ainur it works like charm.
Zackptg5 said:
That's not enough. You need to do this:
Code:
chown 0:2000 /system/bin/audioserver
chmod 0755 /system/bin/audioserver
chcon u:object_r:audioserver_exec:s0 /system/bin/audioserver
The no space error actually referred to the /system/vendor folder so I'm not sure how you're partition layout is. The only time modules won't show up in magisk is when there's a bad post-fs-data script that errors out and/or takes too long to finish. Magisk is easier because you can just delete the module folder and be done with it
Click to expand...
Click to collapse
OK that's fine, I understand that I can't install the new dolby on my system by flashing the zip in recovery as I don't intend to switch to magisk for now.
I used to manually install v4a, what about manually installing dolby? Would you direct me what to install and where. I know for the permissions. Thanks
Nightdemon1999 said:
Perfectly work with redmi note 4(mido) on official miui beta rom with magisk..The Ui is fantastic...but i wonder what demo actually do..i just see the slideshow but none of any sound.. @[email protected] ..nah but i dont care much about it as long the mod work . 1 more things is when i install it alongside with ainur sauron...the dolby atmos will crash.... But without ainur it works like charm.
Click to expand...
Click to collapse
Sound doesn't work? Works for me. In order to use multiple audio mods like sauron and dolby together with magisk, you need to flash audio modification library (it's also on magisk repo)
mohand06 said:
OK that's fine, I understand that I can't install the new dolby on my system by flashing the zip in recovery as I don't intend to switch to magisk for now.
I used to manually install v4a, what about manually installing dolby? Would you direct me what to install and where. I know for the permissions. Thanks
Click to expand...
Click to collapse
If you unzip the installer, all of the files are in the path they would be normally installed into (system folder) so just copy that layout. Although unless you cleared up some space, it won't work. In which case if you do clear some space, you're better off just flashing the zip. It also installed boot scripts and addon.d script which are generated by the installer depending on your device setup so an alternative to the scripts would be setting selinux to permissive
Zackptg5 said:
Sound doesn't work? Works for me. In order to use multiple audio mods like sauron and dolby together with magisk, you need to flash audio modification library (it's also on magisk repo)
Click to expand...
Click to collapse
Okay after im tried again it did not work..after first reboot..but after second time reboot both ainur and dolby working ..tq for u help :good:
Help, please! My phone samsung J710FN can't boot stuck at samsung logo after install via Magisk.
Tung Lam said:
Help, please! My phone samsung J710FN can't boot stuck at samsung logo after install via Magisk.
Click to expand...
Click to collapse
Are you on stock samsung? Not surprised this doesn't work. Audioserver keeps crashing due to it not containing some stuff needed for some other libraries present on your device. There's not much I can do about it so it's just not compatible with your device unfortunately. You can flash the zip again and it'll uninstall it
Zackptg5 said:
Are you on stock samsung? Not surprised this doesn't work. Audioserver keeps crashing due to it not containing some stuff needed for some other libraries present on your device. There's not much I can do about it so it's just not compatible with your device unfortunately. You can flash the zip again and it'll uninstall it
Click to expand...
Click to collapse
I'm on a custom touchwiz ROM.
Hello,Zackptg5
Is there a solution for this sound module to work on my Nexus 7 2012 aosp rom 7.1.2
The installation runs without worries but I have got force close by opening the application Dolby Atmos...
Thanks for help...
laugeek57 said:
Hello,Zackptg5
Is there a solution for this sound module to work on my Nexus 7 2012 aosp rom 7.1.2
The installation runs without worries but I have got force close by opening the application Dolby Atmos...
Thanks for help...
Click to expand...
Click to collapse
Can you run through the troubleshooting guide and see if any of the listed solutions solves it? Try setting selinux to permissive too
Zackptg5 said:
Can you run through the troubleshooting guide and see if any of the listed solutions solves it? Try setting selinux to permissive too
Click to expand...
Click to collapse
Selinux to permissive again force close any solutution ?
*It only works on ROMS with no SafetyNet that has "root debugging" in developer options, ex: LineageOS
**Also refer to post #10 if you would like a flashable version of this method. Credits to @huskydg
Requirements:
download OP8.zip
Stock OxygenOS Build Fingerprint and Model Number
ADB and Fastboot Drivers
*This step is for non-T-Mobile OnePlus 8, if you have a T-Mobile OnePlus 8 (IN2017) skip step 1 and 2.
Step 1: Get OxygenOS Build Fingerprint and Model Number
Be on OxygenOS 11 and Enable Developer Options
Enable USB Debugging and Allow USB Debugging? to ALWAYS
On your PC, go to your ADB folder and type in CMD/Powershell:
Code:
adb shell
On adb shell (OnePlus8:/ $), type and enter
Code:
adb shell
OnePlus8:/ $ getprop ro.build.fingerprint
You would then get your build fingerprint (keep in mind, build fingerprints differ from each Model Number) and store it in Notepad. For Example:
Code:
OnePlus/OnePlus8_EEA/OnePlus8:11/RP1A.201005.001/2012102310:user/release-keys
Find your Model Number in this table and store it in the same Notepad as the build fingerprint: For example, for T-Mobile is IN2017
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*AGAIN this step is for non-T-Mobile OnePlus 8, if you have a T-Mobile OnePlus 8 (IN2017) skip this step because the OP8.zip is already configured for T-Mobile OnePlus 8 (IN2017).
Step 2: Configuring the OP8.zip
Extract the OP8.zip
Open the extracted folder and go to "etc" folder
Edit ih8sn.conf using Notepad
Replace the BUILD_FINGERPRINT with the build fingerprint you did in Step 1 and the PRODUCT_NAME with the Model Number your OnePlus 8 has
Step 3: Installing it on LineageOS or Other
Fresh Install LineageOS and GApps
Go to Settings and Enable Developer Options
Enable USB Debugging and set Allow USB Debugging? to ALWAYS
Enable Rooted Debugging underneath USB Debugging
Now plug in OnePlus 8 to PC and extract OP8.zip if you haven't yet.
Open extracted folder and open CMD/PowerShell from the folder
Now run these commands one by one:
Code:
adb wait-for-device root (Allow Yes to USB Debugging? to ALWAYS)
adb wait-for-device remount
adb wait-for-device push etc/60-ih8sn.sh /system/addon.d/
adb wait-for-device push ih8sn /system/bin/
adb wait-for-device push etc/ih8sn.rc /system/etc/init/
adb wait-for-device push etc/ih8sn.conf /system/etc/
After each and every command is done, reboot device. AND KABOOOOOOM!!! DONE!!!
If SafetyNet didn't pass:
Try changing Model Number in PRODUCT_NAME=
For example: IN2017 -> OnePlus8TMO, IN2013 -> OnePlus8EEA=not sure about this one if its the same model number or not
CREDITS:- Huge thanks to @ihfandicahyo on Twitter for helping me pass it!
- Huge thanks to @_LuK1337_ for ih8sn
RESERVED
RESERVED
I am still trying this on a Motorola One Action "Troika XT2013-2" with latest 19.1 Lineage but it is not working. Double checking every thing. All files look OK, checked for weird markups and linefeed/cariageR but I cant see anything wrong.
When booting it first shows "OS Fingerprint: NA" shortly and then continues to boot. Debugging with root enabled.
Is the string for _SECURITY_PATCH_DATE and _VERSION_RELEASE relevant? What do I enter?
CK0y0TE said:
I am still trying this on a Motorola One Action "Troika XT2013-2" with latest 19.1 Lineage but it is not working. Double checking every thing. All files look OK, checked for weird markups and linefeed/cariageR but I cant see anything wrong.
When booting it first shows "OS Fingerprint: NA" shortly and then continues to boot. Debugging with root enabled.
Is the string for _SECURITY_PATCH_DATE and _VERSION_RELEASE relevant? What do I enter?
Click to expand...
Click to collapse
I have only tested this on 18.1 because no build no 19.1 build yet for OnePlus 8, however, try putting these values BUILD_SECURITY_PATCH_DATE=2021-11-02 and for BUILD_VERSION_RELEASE=11 (if latest firmware is Android 11) or BUILD_VERSION_RELEASE=12 (if latest firmware is Android 12) hope this helps
CK0y0TE said:
I am still trying this on a Motorola One Action "Troika XT2013-2" with latest 19.1 Lineage but it is not working. Double checking every thing. All files look OK, checked for weird markups and linefeed/cariageR but I cant see anything wrong.
When booting it first shows "OS Fingerprint: NA" shortly and then continues to boot. Debugging with root enabled.
Is the string for _SECURITY_PATCH_DATE and _VERSION_RELEASE relevant? What do I enter?
Click to expand...
Click to collapse
Also replace your product name with this, PRODUCT_NAME=XT2013-2
Can this method works with bootloader unlock oxygen os?
[email protected] said:
Can this method works with bootloader unlock oxygen os?
Click to expand...
Click to collapse
If there is toggle that says Root Debugging in Developer Options it might. So far as to what I am aware of, OxygenOS 11 doesn't have it.
thattechguy_69 said:
If there is toggle that says Root Debugging in Developer Options it might. So far as to what I am aware of, OxygenOS 11 doesn't have it.View attachment 5644695
Click to expand...
Click to collapse
With Magisk Root?
I have forked ih8sn repo and make flashable zip for it. You can take a look here:
injectprop
Inject Android system properties
huskydg.github.io
[email protected] said:
With Magisk Root?
Click to expand...
Click to collapse
No this method does not require root. In LineageOS, there is an option in developer settings called "Root Debugging". You can also find this option in some roms, from what I am aware of besides LineageOS that has it is HavocOS. But HavocOS already has safetynet so no need to do this guide.
huskydg said:
I have forked ih8sn repo and make flashable zip for it. You can take a look here:
injectprop
Inject Android system properties
huskydg.github.io
Click to expand...
Click to collapse
Yo this is nice man
thattechguy_69 said:
Yo this is nice man
Click to expand...
Click to collapse
As far as i knew, ih8sn is basically reset props / override read only props
huskydg said:
As far as i knew, ih8sn is basically reset props / override read only props
Click to expand...
Click to collapse
Does this work for any custom recovery or only twrp?
thattechguy_69 said:
Does this work for any custom recovery or only twrp?
Click to expand...
Click to collapse
Any Custom Recovery should work
Thanks for the work,
I tried the injectprop, I used /zFM to update the props ( I also set `inject_props=1`)
I sideload the zip using the lineage recovery and adb: it looked like it worked (it said "all done" without error message but the signature issue)
BUT
when I run Safetynet test (2022) it does find the pervious fingerprint
any idea of what could have failed ?
----
Phone; oneplus6 A6003
Rom: lineage-19.1-20220830-nightly-enchilada-signed
recovery: lineage-19.1-20220830-recovery-enchilada
props
note: the last oxygenOS is on Android 11 (so I copied the verison 11 in the props) but lineage is version 12
```
BUILD_FINGERPRINT=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys
BUILD_DESCRIPTION=OnePlus6-user 11 RKQ1.201217.002 2111252325 release-keys
BUILD_SECURITY_PATCH_DATE=2021-11-01
BUILD_VERSION_RELEASE=11
BUILD_VERSION_RELEASE_OR_CODENAME=11
MANUFACTURER_NAME=OnePlus
PRODUCT_NAME=A6003
BUILD_TAGS=release-keys
BUILD_TYPE=user
DEBUGGABLE=0
```
pati--patou said:
Thanks for the work,
I tried the injectprop, I used /zFM to update the props ( I also set `inject_props=1`)
I sideload the zip using the lineage recovery and adb: it looked like it worked (it said "all done" without error message but the signature issue)
BUT
when I run Safetynet test (2022) it does find the pervious fingerprint
any idea of what could have failed ?
----
Phone; oneplus6 A6003
Rom: lineage-19.1-20220830-nightly-enchilada-signed
recovery: lineage-19.1-20220830-recovery-enchilada
props
note: the last oxygenOS is on Android 11 (so I copied the verison 11 in the props) but lineage is version 12
```
BUILD_FINGERPRINT=OnePlus/OnePlus6/OnePlus6:11/RKQ1.201217.002/2111252325:user/release-keys
BUILD_DESCRIPTION=OnePlus6-user 11 RKQ1.201217.002 2111252325 release-keys
BUILD_SECURITY_PATCH_DATE=2021-11-01
BUILD_VERSION_RELEASE=11
BUILD_VERSION_RELEASE_OR_CODENAME=11
MANUFACTURER_NAME=OnePlus
PRODUCT_NAME=A6003
BUILD_TAGS=release-keys
BUILD_TYPE=user
DEBUGGABLE=0
```
Click to expand...
Click to collapse
Try this one ... https://forum.xda-developers.com/t/rom-official-hotdogb-12-lineageos-19.4509251/post-87666693
huskydg said:
I have forked ih8sn repo and make flashable zip for it. You can take a look here:
injectprop
Inject Android system properties
huskydg.github.io
Click to expand...
Click to collapse
Can it work on Samsung S4 GT-I9515/L Lineage 18.1? What should I edit in injectprop.sh if I have s4?
Bried said:
Can it work on Samsung S4 GT-I9515/L Lineage 18.1? What should I edit in injectprop.sh if I have s4?
Click to expand...
Click to collapse
It should work on any phone
thattechguy_69 said:
It should work on any phone
Click to expand...
Click to collapse
Do I need to edit anything in injectprop.sh if I have s4? Or should I leave everything as it is?