Database Develop

[solution] couldn't install app in usb and sd card in 4.4. Kitkat roms

To all KITKAT ROM USERS having problems in installing apps from play store:
If you have tried to install an app and got an error message: COULDN'T INSTALL IN USB STORAGE OR SD CARD,
1. DOWNLOAD and INSTALL SELINUX MODE CHANGER from play store. (Make sure that you have supersu installed and your phone rooted obviously). Grant permission access to SELinux mode changer when supersu prompts you.
2. OPEN SELINUX MODE CHANGER AND CHANGE SELINUX permission to PERMISSIVE.
3. INSTALL THE APP which you wanted for your phone.
Enjoy.
N.B. You can change the permission to ENFORCING after installing the app you wanted.

Thx very much. Gonna try this after work.
Sent from my fat iDevice using Tapatalk HD

This is also how to get Cydia Substrate working on 4.4
Sent from my GT-I9100G using Tapatalk 4

ottomatteseo said:
Thx very much. Gonna try this after work.
Sent from my fat iDevice using Tapatalk HD
Click to expand...
Click to collapse
Hi ottomatteseo. Did it work?

Omni rom don't have selinux
so how i install the app?

Fighting Dreamer said:
Omni rom don't have selinux
so how i install the app?
Click to expand...
Click to collapse
HI Fighting Dreamer. Omnirom has SELinux. But its mode in Android 4.4 is set to ENFORCING by default. I suspect that this is one of the reasons why we get the error message upon installing some apps which worked for previous android versions and rom.
Anyway, just download SELinux mode changer from playstore and follow the above instructions then install the app which gave you the error message. Update me if it worked for you. Good luck

rarjonillo said:
Hi ottomatteseo. Did it work?
Click to expand...
Click to collapse
Hi, sorry for the late reply. Im on omnirom and it works perfectly. I can install all apps without any error
Sent from my fat iDevice using Tapatalk HD

ottomatteseo said:
Hi, sorry for the late reply. Im on omnirom and it works perfectly. I can install all apps without any error
Sent from my fat iDevice using Tapatalk HD
Click to expand...
Click to collapse
Glad it worked for you.:good:

worked
thanks

alkasser011 said:
worked
thanks
Click to expand...
Click to collapse
Great.

This worked before the 4.4.1 is implanted. I'm not sure if it's just me but on the latest build of Omni rom this solution didn't work out.

Mll4eveR. said:
This worked before the 4.4.1 is implanted. I'm not sure if it's just me but on the latest build of Omni rom this solution didn't work out.
Click to expand...
Click to collapse
Sorry to hear that. But in my case, the app which gave problem in omni 4.4 did not disappear in 4.4.1. In case it helps, I remember updating the rom to 4.4.1 it with SE Linux mode in "permissive".

rarjonillo said:
Sorry to hear that. But in my case, the app which gave problem in omni 4.4 did not disappear in 4.4.1. In case it helps, I remember updating the rom to 4.4.1 it with SE Linux mode in "permissive".
Click to expand...
Click to collapse
Well I guess I'll try to install 4.4 and enable "permissive" mode and update to 4.4.1 to see if it works. Thanks for the tip.

rarjonillo said:
Sorry to hear that. But in my case, the app which gave problem in omni 4.4 did not disappear in 4.4.1. In case it helps, I remember updating the rom to 4.4.1 it with SE Linux mode in "permissive".
Click to expand...
Click to collapse
Well I just flashed 4.4 and set SE Linux mode in "permissive" and updated to 4.4.1. The mode appeared to be "permissive" indeed in 4.4.1 but somehow the "couldn't install app in usb and sd card" error persisted.

I have the same problem... CM11 4.4.1, SELinux is permissive, but still have the problem with SD
---------- Post added at 01:31 PM ---------- Previous post was at 01:06 PM ----------
In logcat I see errors like this:
Failed to create secure container smdl2tmp1
Error creating imagefile (read-only file system)
ASEC image file creation failed (Read-only file system)
Failed to create container smdl2tmp1
No content provider found for permission revoke
Installation error code: -18

Mll4eveR. said:
Well I guess I'll try to install 4.4 and enable "permissive" mode and update to 4.4.1 to see if it works. Thanks for the tip.
Click to expand...
Click to collapse
colorprint said:
I have the same problem... CM11 4.4.1, SELinux is permissive, but still have the problem with SD
---------- Post added at 01:31 PM ---------- Previous post was at 01:06 PM ----------
In logcat I see errors like this:
Failed to create secure container smdl2tmp1
Error creating imagefile (read-only file system)
ASEC image file creation failed (Read-only file system)
Failed to create container smdl2tmp1
No content provider found for permission revoke
Installation error code: -18
Click to expand...
Click to collapse
I think it's high time to report this to ryuinferno and jiangyi (developers of the CM11 and omni roms respectively).It may be caused by either the rom or still the specific app since there are some which are still not working with the 4.4 structure http://forums.androidcentral.com/google-nexus-5/331321-apps-do-not-work-currently-n5-4-4-a.html.
I'll report this. Thanks!

This can be resolved if to remount the /storage folder to r/w with Root Explorer.
But after reboot it will not work again. So it should be fixed in the firmware...

colorprint said:
This can be resolved if to remount the /storage folder to r/w with Root Explorer.
But after reboot it will not work again. So it should be fixed in the firmware...
Click to expand...
Click to collapse
Please see this. https://www.xda-developers.com/android/android-4-4-kitkats-art-and-app-compatibility/. Thanks.

[P905 LTE ONLY!][KERNEL][ODIN] STOCK RELOADED | su | busybox | init.d | permissive !

I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!!!
STOCK RELOADED v1 fix 1
Kernel base: stock XXUANC3 (kernel 3.4.0-1131235)
Kernel ramdisk: modded
Features: a few...
Security level: low!
Purpose: giving everyone who loves free exploring of Android secrets and who doesn't consider security as an absolute priority and who wants to put some life in this, indeed, awesome device, a possibility of playing with his device without disturbing restrictions, forced by Samsung, at least until fully-custom kernels, compiled from sources, appear (and that may take some time, as source code available atm seems to be broken, causing all the compiled kernels to stuck at boot screen).
Features working out-of-the-box:
- su binary from SuperSU by Chainfire @ /sbin/su (binary only for scripting purposes! Flash cf-root to use SuperSU app!)
- busybox 1.22.1 binary compiled by Stericson @ /sbin/busybox
- init.d support - just put your favorite scripts into /system/etc/init.d using any file manager and chmod 755 (not 777! it's NOT smart to permit write access for "world" to any system file), chown root:root, they will run on every boot. Well, to be honest, above permissions are given to all the scripts automatically during boot, but it has not yet been tested
- SELinux: Permissive - Samsung's most recent policy of forcing SELinux Enforcing mode by pre-compiling it into a kernel binary part, found in latest KitKat builds since at least a few months, HACKED FOR THE FIRST TIME EVER using innovative method of injecting an information directly into kernel memory space and forcing overwriting potentially-persistent kernel symbol value on-line during boot!)
- unsecure adb access (not tested yet)
- ext4 tweak: 20 sec (instead of stock 5 sec) write commit delay for /data partition (significantly increases IO performance!)
- some further, minor modifications
WARNING!!!
- flashing this WILL undoubtly trip KNOX, avoiding your warranty (which atm cannot be reverted! in any way)
- flashing this WILL cause a warning message of avoided warranty to be displayed on every boot (ofc it disappears right after reverting to stock boot.img)
- flashing this WILL disable some of the very important security features provided with stock firmware!!!! For advanced and experienced users only!!! Use at your own risk!
Known issues:
- AllCast Share mirroring not working (typical for all Samsung devices running not-exactly-stock kernels since S3). WORKING FIX AT POST #16!!!
http://forum.xda-developers.com/showpost.php?p=54516532&postcount=16
Please consider solution from post #3 as not-always-working and depreciated!
Installation:
- compatibile with XXUANC3 firmwares but probably also with other (past and hope future too...) KitKat 4.4.2 Samsung branded firmwares;
- rooting by Chainfire's CF-Root first recommended as it will install SuperSU app in Android (this kernel contains su binary only giving su access without any policy settings!);
- enter download mode and plug the tablet via USB...
- ...select provided file in PDA section (and NOT touch anything except that)...
- ...and flash with Odin in a same way as CF-Root or like anything else...
- enjoy.
DOWNLOAD HERE:
Current version - STOCK RELOADED v1 fix 1
http://www63.zippyshare.com/v/87557346/file.html
FIXED: file name changed so it can be flashed directly by Odin without renaming! Sorry for this silly mistake!
=======
Changelog:
v1 fix1:
- fixed permissive mode due to trivial error;
- delayed init.d execution to a moment AFTER init process set cfq scheduler so it is not overriding mmcblk0 tweaks (if put in init.d) anymore;
- minor code cleanups
v1:
- initial release
- init.d support
- SELinux permissive
- unsecure ADB
- ext4 delayed commit for /data
=======
Stock XXUANC3 kernel (to revert changes)
http://www65.zippyshare.com/v/32441894/file.html
Revert using Odin, in the same way you've installed a Reloaded Version....

Awww man,...I wish i could flash this, but I'm on the exynos =(
Sent from my SM-P900 using Tapatalk

rgolnazarian said:
Awww man,...I wish i could flash this, but I'm on the exynos =(
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Sorry pal, Qualcomm only, not even a chance to run this same way as the devices (and mostly important: provided software, ie. system structure) DIFFER A LOT between themselves.
Update 1: uploaded fix #1 which is resolving some trivial issues found in initial version; sorry for that, now we can say that every described feature has been included hope for some feedback... thank you...
Update 2: FIX FOR NOT WORKING SCREEN MIRRORING CAN BE DOWNLOADED HERE:
http://www67.zippyshare.com/v/25492738/file.html
I have personally modified a library that is being used by screen mirroring feature, which forces video encryption using keys from stock kernel, and which prevents to run mirroring at all . This is an issue of any modified kernel, on any Samsung device. Attached library fixes this, by disabling HDCP at all. It has been reported that the library resolves the issue for any Qualcomm based Samsung device running 4.4.2 KitKat and for any custom kernel. It will NOT work for Exynos devices...
Installation:
- download attached libwfdsm.so file
- overwrite genuine one in/system/vendor/lib (important! NOT /system/lib!!!!)
- chmod 644 libwfdsm.so ||| chown 0.0 libwfdsm.so ||| restorecon -R /system/vendor/lib
- mirroring will work again after reboot!!

YAY!
Beautiful, absolutely beautiful. You made ma a very happy man with this. I'll flash this as soon as I get home from work. Can't wait to try it out, the stock kernel is giving me SOD and frozen wifi issues sometimes.

esgie said:
Sorry pal, Qualcomm only, not even a chance to run this same way as the devices (and mostly important: provided software, ie. system structure) DIFFER A LOT between themselves.
Update 1: uploaded fix #1 which is resolving some trivial issues found in initial version; sorry for that, now we can say that every described feature has been included hope for some feedback... thank you...
Update 2: FIX FOR NOT WORKING SCREEN MIRRORING CAN BE DOWNLOADED HERE:
http://www67.zippyshare.com/v/25492738/file.html
I have personally modified a library that is being used by screen mirroring feature, which forces video encryption using keys from stock kernel, and which prevents to run mirroring at all . This is an issue of any modified kernel, on any Samsung device. Attached library fixes this, by disabling HDCP at all. It has been reported that the library resolves the issue for any Qualcomm based Samsung device running 4.4.2 KitKat and for any custom kernel. It will NOT work for Exynos devices...
Installation:
- download attached libwfdsm.so file
- overwrite genuine one in/system/vendor/lib (important! NOT /system/lib!!!!)
- chmod 644 libwfdsm.so ||| chown 0.0 libwfdsm.so ||| restorecon -R /system/vendor/lib
- mirroring will work again after reboot!!
Click to expand...
Click to collapse
I was literally just about to post in the old thread with bad news about the modified "libwfdsm.so" file & screen mirroring with a custom kernel...if u remember i confirmed that the file u altered would work with a custom recovery on the 8.4 lte & i just assumed that it would work with an altered boot.img as well but unfortunately thats not the case after testing the other night (unless something else is wrong with my setup). So...my question is have u changed something else since then to allow it to work again & have u personally tested this yourself?
sorry to hijack the thread...didnt know if i should pm or post in the older thread

THEDEVIOUS1 said:
I was literally just about to post in the old thread with bad news about the modified "libwfdsm.so" file & screen mirroring with a custom kernel...if u remember i confirmed that the file u altered would work with a custom recovery on the 8.4 lte & i just assumed that it would work with an altered boot.img as well but unfortunately thats not the case after testing the other night (unless something else is wrong with my setup). So...my question is have u changed something else since then to allow it to work again & have u personally tested this yourself?
sorry to hijack the thread...didnt know if i should pm or post in the older thread
Click to expand...
Click to collapse
No problem, anyway, thanks for pointing the issue out! This may be an important information for mirroring users!
Since then I didn't change anything, yet. Really, I am also not sure if I have tested it with modified kernel, as the one posted here is the first kernel for P905 at all, and it's not even "fully" customized, as the kernel binary base was left unchanged.
So, I'd like to be sure: you are saying that modded lib:
- fixed the problem for custom recovery, but...
- ...didn't fix it for custom kernel
right?
I was looking for a solution to persistent enforcing mode since some time, so I was flashing test boot.imgs from time to time, then reverting to stock again, meanwhile I created above lib, I can't really be sure about if it is working when both bootimg and kernel are customized (this would also be an opposite to previous Sammy's Android releases, where a single fix was solving all the issues related to customizations of both kernel and recovery!).
We also have to be aware that the issues may not be a result of flashing different kernel at all, but a result of the changes themselves, ie. disabled knox, disabled encryption of i-dont-really-know-what, etc, etc.
And the most important thing! Since I have heard of AllShareCast/Screen Mirroring for the first time (it probably appeared for the first time in S3/Note2/Note10.1), it always required resetting the flash counter - which could be viewed in download mode and which is NOT the same as Knox flag - to ZERO and that requirement AFAIR remained totally independent from the requirement of having stock boot/kernel (or lib patch). Have you checked the counter state? Did you reset it to zero again using Chainfire's Triangle Away after flashing non-stock kernel (which, obviously, TRIPPED the counter)? Can you check if it is working? Note that at least on my P905, Triangle Away still works flawlessly and resets the counter without any problems and even without a need of reboot!
Please check above info and try if the issue is fixed after running Triangle Away. I am leaving for a short business trip soon, so I'll perform my own tests with AllShare cast until next of the week, however, neither today nor tomorrow...

I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.

cavkic said:
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
Click to expand...
Click to collapse
Argh possibly too many dots in filename... will correct it tomorrow.

cavkic said:
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
Click to expand...
Click to collapse
same here...

Hi,
I have a problem with screen mirroring.
Installed the patch and mirroring connects to the dongle, but the TV screen turns just black.
The dongle works perfect with HTC One M8, it must be a softwareproblem?
Thanks for help!!!

Will this work on the P905V (Verizon Variant)? I need to downgrade the permissions in my Security in order to use Towelroot, because they're set to Medium and I believe that prevents Towelroot to work properly. Most of the other Note 12.2 variants have been rooted....except the Verizon version.

Can anyone give me some advice please. When I enter the command in terminal emulator I get an error saying "Unable to open chown. No such file or directory". Am I missing something obvious lol.

Will this work on p907a AT&T version of note pro 12.2?
Sent from my SAMSUNG-SM-P907A using XDA Premium 4 mobile app

cnote74 said:
Will this work on p907a AT&T version of note pro 12.2?
Sent from my SAMSUNG-SM-P907A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On the topic name it says [P905 LTE ONLY], and your device is some different..

tdetroit said:
Will this work on the P905V (Verizon Variant)? I need to downgrade the permissions in my Security in order to use Towelroot, because they're set to Medium and I believe that prevents Towelroot to work properly. Most of the other Note 12.2 variants have been rooted....except the Verizon version.
Click to expand...
Click to collapse
I would like this answered as well. I also have the "v" variant. Maybe saying LTE includes many? See my link I attached, found while investigating this specific question.
http://www.usatoday.com/story/tech/2013/07/07/sprint-att-verizon-phones-network-carriers/2486813/
Ever since I rooted my tablet it goes on random reboot kicks. I want to start over. Also TWRP will not stick when I try to flash it.
I have many issues which I'm currently posing in their appropriate forums. It would be nice to wipe to a rooted stock.

Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!

Thanks. The Galaxy is connecting to theTV, but the screen is only turning black - no Display...
Any idea?
Thank you.
esgie said:
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Click to expand...
Click to collapse

esgie said:
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Click to expand...
Click to collapse
I tried both methods and still get no devices found when I turn on screen mirroring.

ColBill said:
I tried both methods and still get no devices found when I turn on screen mirroring.
Click to expand...
Click to collapse
Hm.
This is weird, as the problems with allshare cast + custom kernels is not that "no devices are found" but that devices ARE found without any problem but the connection process fails after a few secs. This solution may help with the issue i described, but it will surely not solve the problem with no peers detected at all.
No peers detected = problems with wifi direct (are you able to send files between wifi direct between devices?)
Can you tell me what is your exact device config? And are you using allsharecast dongle or other third party hardware?
@fokus
Only one: also reset flash counter with Triangle Away and then try again. And make sure you spell the value in the command as "disable" not "disabled" - it's tricky and one can miss it...
Well, there are two additional things to add.
Guys, make sure you have updated Samsung's ScreenMirroring firmware update app to the latest version. And check out the samsung mirroring fix app in google play, which solves some issues for various devices (dunno which ones exactly as i have never been in need of using it).

The fix half worked for me lol. The tablet now connects fine to the Netgear PTV3000 but all I get is black screen. Step in the right direction though as at least it connects now. Just need to get a picture to show lol.

Booting .4.5.2 Kernel (Apollo - Old Bootloader)

@Cpasjuste,
In the image headers I noticed that the ramdisk and tag addresses have changed.
ramdisk addr: 0x02000000 -> 0x01000000
tags addr: 0x01e00000 -> 0x00000100
Please correct me if I'm wrong...
The bootloader (lk) loads the ramdisk and kernel tags (device tree) at these physical RAM locations.

@ggow
Yes i saw that but it have no effect. I'm focusing on the .dt part because I found a few things :
- The DT images can correctly be extracted with a tool named "mkboot".
- When using the DT image from kk kernel, the bootloader complains about DT not found (fastboot boot boot.img)
- Opened both DT image in hex editor, noticed some differences in the headers. I switched kk DT headers by jb DT headers, the bootloader don't complain
anymore so I guess it can now found it. But the kernel will just hang immediately.
- The DT syntax seems to have changed (arch/arm/boot/dts/thor.dtsi), this may be the problem for our old bootloader ?!
- Now I'd like to use compiled dt from kk kernel, but has you may have noticed the DT compilation fail about "fb_mem" not declared. I think I need to fix this, then maybe use old jb tools ( $KERNEL_OUT/scripts/dtc/dtc -p 2048 -O dtb -o thor-v1.dtb arch/arm/boot/dts/thor-v1.dts) to compile them, unlike kk kernel which now compile them with the kernel.
From what iv read dt, kernels and bootloaders are linked together, so there is also maybe some changes to be done in the dt sources. But this start to be out of my knowledge.
I asked to hashcode for that but I guess he is very busy.

Cpasjuste said:
@ggow
Yes i saw that but it have no effect. I'm focusing on the .dt part because I found a few things :
- The DT images can correctly be extracted with a tool named "mkboot".
- When using the DT image from kk kernel, the bootloader complains about DT not found (fastboot boot boot.img)
- Opened both DT image in hex editor, noticed some differences in the headers. I switched kk DT headers by jb DT headers, the bootloader don't complain
anymore so I guess it can now found it. But the kernel will just hang immediately.
- Now I'd like to use compiled dt from kk kernel, but has you may have noticed the DT compilation fail about "fb_mem" not declared. I think I need to fix this, then maybe use old jb tools ( $KERNEL_OUT/scripts/dtc/dtc -p 2048 -O dtb -o thor-v1.dtb arch/arm/boot/dts/thor-v1.dts) to compile them, unlike kk kernel which now compile them with the kernel.
From what iv read dt and kernels are linked together, so there is also maybe some changes to be done in the dt sources. But this start to be out of my knowledge.
Click to expand...
Click to collapse
I noticed the "fb_mem" not declared error and couldn't find any reference to it anywhere. I switched the dt.img header also and got to the point where the kernel was not dumping out to fastboot any more, but instead bootloops.
I have messaged amazon once again to post the source code for apollo and thor for update .4.1.1 .

Hehe we are at the same point it seems (nowhere)

Today I did spent a lot of time on this. After a lot of dt hacks/test I'm unable to resolve this problem for now. So I had another idea and started to port kexec hardboot for our device. I'm at the point where is successfully load kernel and DT (something is different for our device, the msm_id struct, which I solved) and reboot but will hang or restart just after a few seconds of the reboot. I think I'm almost there but I may have some problem to find correct memory addresses which are not overwritten by the boot loader. Let me know if you want to take a look I'll upload patches. But well even if we succeed we may still encounter the same DT problem.
In the "dt.img" there is 3 dtb files in, which are scanned by the bootloader for the correct hw revision. I did find that our device use the "thor-v2-apq.dts/.dtb" dt file for booting (not the thor-v1 nor v2) which correspond to our hardware revision. This is in correlation to the 4.1 kernel which only compile this dtb.
When loading the 4.1 dt image with kexec I was able to debug and see that while the header of each dtb parts have changed, there's still the correct hw revision included (of course!?). This one is correctly loaded by kexec and so probably by the bootloader (but in the new dt.img we still need to modify the img header for our bootloader to find it). By the way, I wonder how this final dt.img is built !?
I just don't know yet what is the thor.dtsi file in the 4.1 kernel, the one missing the fb_mem def. This is not included in the dt.img so should it be modified to match our old thor-v2-apq.dts instead the new one ?
By the way manual compilation (and decompilation!) does work with the dtc utility (apt-get install device-tree-compiler).

Yes, upload the the patches for kexec. Definitely interested in taking a look. I have configured a kernel last night with kexec config enabled (great minds think alike)
This DT problem is troubling me. Perhaps not everything is included in this kernel for Apollo or Thor to boot.
I received a reply from amazon, they said they will post the missing source for the last 3 updates very soon (no idea of time frame).
Sent from my Full Android on C6603 using Tapatalk

I don't think the sources are the problem as we have it on stock 4.1 boot.img. I'll upload the patches tomorrow with a little briefing.

@ggow : 4.1.1 kernel booted (not from sources. As you noted this sources may be incomplete).
I'll post the kernel this night, with a clean 4.1.1 system if i have the time.

Cpasjuste said:
@ggow : 4.1.1 kernel booted (not from sources. As you noted this sources may be incomplete).
I'll post the kernel this night, with a clean 4.1.1 system if i have the time.
Click to expand...
Click to collapse
Good News, well done

ggow said:
Good News, well done
Click to expand...
Click to collapse
Finally, sorry for the delay So here is the modded 4.1.1 boot image. In short : binary extract correct dts from 4.1.1 stock dt image and happend it to 4.1.1 stock zImage.
Didn't had the time to finish my gapps rom based on 4.1.1 but should not be too long
http://android.mydedibox.fr/hdx/boot-4.1.1.img

Cpasjuste said:
Finally, sorry for the delay So here is the modded 4.1.1 boot image. In short : binary extract correct dts from 4.1.1 stock dt image and happend it to 4.1.1 stock zImage.
Didn't had the time to finish my gapps rom based on 4.1.1 but should not be too long
http://android.mydedibox.fr/hdx/boot-4.1.1.img
Click to expand...
Click to collapse
Good work looking forward to testing it out.
Sent from my Optimus G using XDA Free mobile app

cdub50 said:
Good work looking forward to testing it out.
Sent from my Optimus G using XDA Free mobile app
Click to expand...
Click to collapse
This is a wip for you. You need to wait for a root exploit on 4.1.1 for using it !

Cpasjuste said:
This is a wip for you. You need to wait for a root exploit on 4.1.1 for using it !
Click to expand...
Click to collapse
Ah gotcha. Hopefully that will be sooner than later.
Sent from my Optimus G using XDA Free mobile app

Cpasjuste said:
Finally, sorry for the delay So here is the modded 4.1.1 boot image. In short : binary extract correct dts from 4.1.1 stock dt image and happend it to 4.1.1 stock zImage.
Didn't had the time to finish my gapps rom based on 4.1.1 but should not be too long
http://android.mydedibox.fr/hdx/boot-4.1.1.img
Click to expand...
Click to collapse
Thanks for that
Which number dts is the correct one (there are 3). I need to do the same for Apollo...

ggow said:
Thanks for that
Which number dts is the correct one (there are 3). I need to do the same for Apollo...
Click to expand...
Click to collapse
From what i remember this is the third (which is thor-v2-apq.dtb)

Well, cm is still a ***** to get ported :/, tree days on it without success.
Else the new odex framework is not deodexable by baksmali. If you ever have a solution let me know (You may not need that but I'm in a dead end).

So @ggow, did you made some progress on resurecting your device ?
In the meantime i did get msm aosp up and running ! (but no wifi, qcmediaplayer not found for no apparernt reason which prevent some audio to work, slow ui transitions and probably more stuff to fix).

Cpasjuste said:
So @ggow, did you made some progress on resurecting your device ?
In the meantime i did get msm aosp up and running ! (but no wifi, qcmediaplayer not found for no apparernt reason which prevent some audio to work, slow ui transitions and probably more stuff to fix).
Click to expand...
Click to collapse
So far no...
What I think could have happenned is the synaptic dsx firmware and configuration has been updated or corrupted by the new kernel.
I am in the process trying to figure out exactly what I need to do to fix it. I have found a utility which can be used to force an update to an older version of synaptic firmware.
I might have to write a utility to extract the firmware and configuration area from a working device.
Will let you know what I find.
Sent from my Kindle Fire HDX 7 using Tapatalk

ggow said:
So far no...
What I think could have happenned is the synaptic dsx firmware and configuration has been updated or corrupted by the new kernel.
I am in the process trying to figure out exactly what I need to do to fix it. I have found a utility which can be used to force an update to an older version of synaptic firmware.
I might have to write a utility to extract the firmware and configuration area from a working device.
Will let you know what I find.
Sent from my Kindle Fire HDX 7 using Tapatalk
Click to expand...
Click to collapse
Yep i was just going to talk you about this. I'm trying to fix wifi on the aosp build and discovered this lines in dmesg :
<6>[ 6.404807] synaptics_dsx_i2c 2-0020: fwu_start_reflash: Requesting firmware image Synaptics.3.B.thor.img
<6>[ 6.414184] synaptics_dsx_i2c 2-0020: Firwmare size 45056, config size 512
<6>[ 6.421216] synaptics_dsx_i2c 2-0020: Device firmware id 1509905.
<6>[ 6.427045] synaptics_dsx_i2c 2-0020: Device config ID 0x13, 0x07, 0x00, 0x02
<6>[ 6.434233] synaptics_dsx_i2c 2-0020: .img config ID 0x13, 0x07, 0x00, 0x02
<6>[ 6.441127] synaptics_dsx_i2c 2-0020: Nothing needs to be updated
<6>[ 6.447230] synaptics_dsx_i2c 2-0020: fwu_start_reflash: No need to do reflash.
Click to expand...
Click to collapse

Thank you for your work! I hope your problem will spill over into different firmware for our device. With the support of LTE I hope.

[FIX] SCRFIX, a fix for DT2W/Sw2W lock screen freeze

The included file is a binary that runs a daemon that fixes the lockscreen freeze that happens with dt2w/sw2w kernels. It requires busybox to be installed on your device. If your screen is still unresponsive the first time you attempt to wake your device; shut your screen off, wait a couple seconds, and try again and it will usually work.
The executable will do nothing on its own, so you must either have it start on boot with an init.d script or manually in terminal. It has to be ran as root.
To install the zip boot into recovery and install it using your recovery's standard install method, like installing a kernel or ROM.
To install the binary simply put the file in /system/bin and give it executable permissions
Recovery installer zip:
https://docs.google.com/file/d/0B_hgNZE_j5sVd0Itb1V4RGhhOGc/edit?usp=docslist_api
Binary:
https://docs.google.com/file/d/0B_hgNZE_j5sVLU9wdDEzamFUV0U/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

What this app does? How did you find it?

and after put in system/bin what to do next? how to run it?

Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.

I use SManager , give to scrfix su and boot privs it will work?

I haven't used that app personally, but it sounds like it should. Its normal for the program to seem like it exits because it spawns a child process that runs in the background that is owned by init (PID 1)
Or if you want to launch it manually, you can launch it in Terminal Emulator, but it will need started again on each reboot.

There is now a link to an installer zip for installation from recovery mode that comes with an init.d script included, for anyone using this method, please let me know if you encounter any issues with it. You may need to enable "trust system user" in your su application for it to work. The recovery installer was made with the ZipMe application.

Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk

imranaryan said:
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
If you will read the title, you would realize that this mod is a fix for a very common problem faced by dt2w users. If you want dt2w, flash a custom kernel like optimus.

I just tried this on my Moto E 2015 and I ended up flashing a zip I modified when I tried it on my Moto G some time ago. I've found that it does not work when applying dt2w with an app such as Kernel Adiutor. It does work if you apply dt2w with an init.d script, and make it so the scrfix script is ran before the dt2w script. You just have to change the numbers in the beginning of the script name to something like 01 and 02 with the scrfix script having the smaller number.

Thanks for the info, I may upload an updated zip that has the name change to make sure it runs first. Some times too (on my phone atleast) when the screen isn't responsive I'll turn the screen off for 3-5 seconds and try again and it'll usually respond.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!

elrod16 said:
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
Click to expand...
Click to collapse
i know this is an old forum but I just found it. How can I call it in an init.d script?

Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!

elrod16 said:
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
Click to expand...
Click to collapse
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs

V-Droid said:
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------

amarc78 said:
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
Click to expand...
Click to collapse
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs

V-Droid said:
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Try Root Explorer or ES File manager. As long as your rooted it should work.

amarc78 said:
Try Root Explorer or ES File manager. As long as your rooted it should work.
Click to expand...
Click to collapse
Still no luck, I tried root browser, root explorer and es file explorer all of them gave me the same error.
I also tried moving the file from the external SD card into the internal memory.
By the way, the way I create the scripts is in a .txt file, is this correct?
Sent from my Moto E 2015 using XDA Labs

V-Droid said:
Still no luck, I tried root browser, root explorer and es file explorer
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
You need to put them in /system/etc/initd not on your sdcard.

amarc78 said:
You need to put them in /system/etc/initd not on your sdcard.
Click to expand...
Click to collapse
Thank you very much for all of your help, finally managed to change the permissions :laugh:
Sent from my Moto E 2015 using XDA Labs

EFIDroid for the Samsung Galaxy Note 4/Note Edge (Snapdragon Variants)

I have ported EFIDroid (developed by @m11kkaa) to the Snapdragon variants of the Samsung Galaxy Note 4/Note Edge.
@m11kkaa's original EFIDroid thread here: https://forum.xda-developers.com/android/software-hacking/efidroid-t3447466.
This is an unofficial port of beta software. I am not responsible for anything that may happen to your device. Use at your own risk.
Note: This has been tested with Samsung stock ROM, EmotionOS 7.1.1, and TWRP 3.0.2-0 on an SM-N910V/trltevzw. All other configurations are untested by me, but should work.
Confirmed working on:
- SM-N910V (trltevzw) (my device)
- SM-N910T (trltetmo) (thanks @viewsfromthepi)
- SM-N910G (trltedt) (thanks @Preet Juneja)
- SM-N910P (trltespr) (thanks @carlosggb)
- SM-N910W8 (trltecan) (thanks @d3multimedia)
- SM-N910F (trltexx) (thanks @cod_r) (possibly some issues with multiboot)
- SM-N915FY (tbltebtu) (thanks @jpearn)
- SM-N915F (tbltexx) (thanks @Juank2007)
I believe this works on all Snapdragon variants. If you're willing to test a variant not listed above, follow the instructions below, and post below if you had success, or if you encountered any issues.
Warning: There have been reports of the app failing to backup the boot/recovery partitions on other devices, leaving the device unable to boot to the OS and/or recovery. I have no way of testing whether this happens on the Note 4, so be ready with a working recovery/boot img on your computer...
I believe this issue does not affect the Note 4, as there have been successful installs with the app. However, I am leaving the related info on how to recover below, just in case this happens to one of you.
Installation
Install the attached EFIDroid Manager apk. Since this is an unofficial port, the EFIDroid Manager app from the Play Store won't work.
Open the EFIDroid Manager app, open the menu (at the top left), and click "Install/Update".
Click the big orange Install button.
And voila, you're done in 3 easy steps! Reboot to see your new 2nd-stage bootloader!
Post below with your variant/installed ROM if you have success.
To update EFIDroid, just repeat step 2, and the click the big orange Update button.
The app won't automatically check for updates, so I'll post an announcement on this thread whenever an important update is available.
Multibooting
You can use EFIDroid as a multiboot manager. To add a multiboot ROM, do the following:
Open the EFIDroid Manager app. Press the plus button at the bottom right side of the screen to start adding a multiboot slot.
Under "Location", there should be a couple paths. Select the one containing "/data/media/0" if you want the new slot to reside on the internal SD card (recommended for speed). Select the one containing "/mnt/media_rw/" if you want the new slot to reside on the external SD card.
You can give the slot a name/description by using the appropriate fields.
Press the checkmark at the top right side of the screen to create the multiboot slot.
Reboot. When EFIDroid comes up, select TWRP, then select the newly created slot.
Go to the "Wipe > Advanced Wipe" menu. Select "System", then swipe to wipe.
Install all the zips you want on that slot.
Reboot, and when EFIDroid comes up, your new slot should automatically be selected. Press the power button to boot, and enjoy!
Migrating from Dual Boot Patcher
Coming soon!
Troubleshooting
If you are unable to boot the OS/recovery from EFIDroid, do the following (you do have a working boot.img and recovery.img, right?)
This assumes you have fastboot properly setup.
In EFIDroid, use the volume keys to navigate to "Fastboot", the press the power key to select it.
There should only be one entry in the Fastboot menu. Press the power key to select it.
Connect your phone to your computer with a USB cable. Run the following (on the computer), one line at a time:
Code:
fastboot flash boot <path/to/boot.img>
fastboot flash recovery <path/to/recovery.img>
fastboot oem exit
In EFIDroid, use the volume keys to navigate to the back button at the top of the screen. Press the power key to select.
Use the volume keys to navigate to "Reboot", then press the power key to select.
If Maintenance Mode comes up, press the home button to reboot.
You should be able to boot the installed OS/recovery now. If this doesn't work, you can always Odin a TWRP tar, and then flash your original boot.img from inside TWRP, to get back up and running again.
Known Bugs
Aroma installers in TWRP may flicker, rendering them unusable.
Again, all credit goes to @m11kkaa for doing all the hard work in developing EFIDroid.
XDA:DevDB Information
EFIDroid, Kernel for the Verizon Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-19
Last Updated 2017-07-03

I have the Sprint model. Is it safe to try?
Anyone try this yet.?

aaron74 said:
I have the Sprint model. Is it safe to try?
Anyone try this yet.?
Click to expand...
Click to collapse
I believe the Sprint variant is similar enough hardware-wise to the Verizon variant.
As with everything, make sure you backup, and store the backup somewhere other than your phone.
That being said, I believe there are no risks, other than possibly an hour or so of downtime (if something goes wrong with the installation). Since EFIDroid only modifies the boot and recovery partitions, if something goes wrong, you can always flash TWRP via Odin, and then in TWRP flash the boot.img from whichever ROM you're currently running to get back up and running.
If you're willing to wait, I have a friend who has volunteered to test this out on his Sprint variant in a week or two (when he gets his daily driver back).

There is my error now ... what boot and recovery img are you talking about??

Neuken69 said:
There is my error now ... what boot and recovery img are you talking about??
Click to expand...
Click to collapse
Trying clearing the data of the EFIDroid Manager app.

abraha2d said:
Trying clearing the data of the EFIDroid Manager app.
Click to expand...
Click to collapse
Same error
---------- Post added at 10:54 PM ---------- Previous post was at 10:16 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 11:14 PM ---------- Previous post was at 10:55 PM ----------
If you have devices.json in that folder and your running a n910v ... can you share that file?

Neuken69 said:
Same error
---------- Post added at 10:54 PM ---------- Previous post was at 10:16 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 11:14 PM ---------- Previous post was at 10:55 PM ----------
If you have devices.json in that folder and your running a n910v ... can you share that file?
Click to expand...
Click to collapse
Is Noble ROM or Aurora ROM a Note 5/7 port? Because that may be the issue. The app might be getting confused.
I have another user who's having the same issue, with a Note 7 port ROM... I'll have to debug on my end, and see what the problem is... The app is supposed to be downloading that file from the OTA server...

abraha2d said:
Is Noble ROM or Aurora ROM a Note 5/7 port? Because that may be the issue. The app might be getting confused.
I have another user who's having the same issue, with a Note 7 port ROM... I'll have to debug on my end, and see what the problem is... The app is supposed to be downloading that file from the OTA server...
Click to expand...
Click to collapse
Being on Note 7 port, as you said I've changed product code.
I'm really sorry that I can't test right now by flashing stock firmware but I promise I'll do it sooner.
If anybody else is on stock, please report!

Im downloading paulpizz stock rom ... will be testing within 45 min

Neuken69 said:
Same error
---------- Post added at 10:54 PM ---------- Previous post was at 10:16 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 11:14 PM ---------- Previous post was at 10:55 PM ----------
If you have devices.json in that folder and your running a n910v ... can you share that file?
Click to expand...
Click to collapse
Preet Juneja said:
Being on Note 7 port, as you said I've changed product code.
I'm really sorry that I can't test right now by flashing stock firmware but I promise I'll do it sooner.
If anybody else is on stock, please report!
Click to expand...
Click to collapse
Guys, can you install the attached debug apk, clear data, grant storage permission, and then try again? If it still errors, can you send me a logcat?
@Preet Juneja There's a way to get logcat without a computer, using the Matlog app from the Play Store. See this for details:
https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
You don't need to do the adb part if you're rooted...

abraha2d said:
Guys, can you install the attached debug apk, clear data, grant storage permission, and then try again? If it still errors, can you send me a logcat?
@Preet Juneja There's a way to get logcat without a computer, using the Matlog app from the Play Store. See this for details:
https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
You don't need to do the adb part if you're rooted...
Click to expand...
Click to collapse
All logs related to EFIDroid attached:

Preet Juneja said:
All logs related to EFIDroid attached:
Click to expand...
Click to collapse
Did you just search for all lines containing EFIDroid, or did you actually filter by app? Because these logs seem incomplete...
Sent from my Samsung Galaxy Note 4 using XDA Labs

abraha2d said:
Did you just search for all lines containing EFIDroid, or did you actually filter by app? Because these logs seem incomplete...
Click to expand...
Click to collapse
Logs: (From launching EFIDroid app to pausing logs on Matlog app)

Preet Juneja said:
Logs: (From launching efidroid app to pausing logs on matlog app)
Click to expand...
Click to collapse
Did you put anything into the "Override OTA Server" dialog? From the logs, either there's something wrong with the app, or you put "samsung/trltevzw" into the dialog...

abraha2d said:
Did you put anything into the "Override OTA Server" dialog? From the logs, either there's something wrong with the app, or you put "samsung/trltevzw" into the dialog...
Click to expand...
Click to collapse
Oh. I put it when I didn't edit build.prop (when it was Noblelte). I already tried clearing data due to which it should've removed. Well if it didn't, how can I remove it?
I'm sure it's problem from my side and not yours... it's all because I'm using custom ROM.
UPDATE:
YES IT OPENED!
I emptied that override OTA server and the app finally asked for Root access!
Thank you so much, I'll sooner report what will be the next.

Preet Juneja said:
Oh. I put it when I didn't edit build.prop (when it was Noblelte). I already tried clearing data due to which it should've removed. Well if it didn't, how can I remove it?
I'm sure it's problem from my side and not yours... it's all because I'm using custom ROM.
Click to expand...
Click to collapse
No problem, it should probably be clearer. That dialog is for entering a different URL for the OTA server, not a different device codename. Just remove what's in there, and press Ok. That will clear it. :good:
EDIT: Just saw your edit. Nice to hear it's working.

abraha2d said:
No problem, it should probably be clearer. That dialog is for entering a different URL for the OTA server, not a different device codename. Just remove what's in there, and press Ok. That will clear it. :good:
Click to expand...
Click to collapse
Thank you so much.
Will update you soon.

Ok now what???

Neuken69 said:
Ok now what???
Click to expand...
Click to collapse
Just reboot your device to see changes!
Perfectly working, please add N910G support as 'confirmed' in 1st post.
Also, you can add instructions for custom ROM user to edit build.prop as required.
I was able to boot into TWRP and ROM without use of fastboot.

abraha2d said:
I believe the Sprint variant is similar enough hardware-wise to the Verizon variant.
As with everything, make sure you backup, and store the backup somewhere other than your phone.
That being said, I believe there are no risks, other than possibly an hour or so of downtime (if something goes wrong with the installation). Since EFIDroid only modifies the boot and recovery partitions, if something goes wrong, you can always flash TWRP via Odin, and then in TWRP flash the boot.img from whichever ROM you're currently running to get back up and running.
If you're willing to wait, I have a friend who has volunteered to test this out on his Sprint variant in a week or two (when he gets his daily driver back).
Click to expand...
Click to collapse
Thanks! So this allows you to dual boot 2 different roms?
One is primary installed as normal, i take. Now the second one, how is it installed? How is it saved?
Thank you. I'm just curious. This sounds convenient to have your daily driver as primary, and be able to test other roms without constantly backing up and restoring. Am i correct in thinking this way?