Here is a way for us to change the SELinux status to Permissive on our ATT N3.
Prerequisites
1. Busybox must be installed.
2. Have to be on NC2 or MLG Kernel. If not then download it from here (http://d-h.st/lBR) and flash it using Odin (select PDA). (You DON'T have to upgrade your BL to NC2. Just the kernel. I'm still on MLG BL, so I can still roll back to 4.3 if I wanted).
3. Most importantly. Have to be on SuperSU 2.13 http://d-h.st/afU
Instructions: (only if you plan on applying manually after every reboot)
1. Download http://www78.zippyshare.com/v/1605705/file.html
2. Move the file to /data/local/tmp/
3. Change Permission to 0755 (-rwxr-xr-x)
3. Open up the Terminal Emulator and type the following.
Code:
su -c /data/local/tmp/SE_Status_Change_via_kmem.sh
4. Enjoy.
OR
Instructions: (to apply automatically at reboot)
1. Download http://www78.zippyshare.com/v/1605705/file.html
2. Change its name from "SE_Status_Change_via_kmem.sh" to "SE_Status_Change_via_kmem"
3. Move that file to /system/etc/init.d/
4. Change permission to 0777 (-rwxrwxrwx)
5. Reboot.
Proof.
{
"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"
}
Pardon my n00bness, but what are the benefits of this?
Face_Plant said:
Pardon my n00bness, but what are the benefits of this?
Click to expand...
Click to collapse
+1
Face_Plant said:
Pardon my n00bness, but what are the benefits of this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55912097#post55912097
dcscorpio76 said:
+1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=55912097#post55912097
Walter.White said:
http://forum.xda-developers.com/showthread.php?p=55912097#post55912097
Click to expand...
Click to collapse
Sweet! I'm not a huge fan of AOSP, but something other than TouchJizz ROMs would be a nice change.
I second that. I miss me some halo and over clocking.
Not sure what I'm missing but mine stays enforced, I've tried using terminal and it runs but remains enforced. What I'm doing wrong?
Sent from my SM-N900A using XDA Premium HD app
Face_Plant said:
Sweet! I'm not a huge fan of AOSP, but something other than TouchJizz ROMs would be a nice change.
Click to expand...
Click to collapse
You can still benefit hugely from a custom kernel
+1. Tried both methods above, and I also tried using script manager to run the script. Would love to get this working; NTFS mounting through Total Commander is a bit annoying....
Dirtburgler said:
Not sure what I'm missing but mine stays enforced, I've tried using terminal and it runs but remains enforced. What I'm doing wrong?
Sent from my SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
optimusv45 said:
You can still benefit hugely from a custom kernel
Click to expand...
Click to collapse
I never noticed a huge difference with custom kernels on my old Galaxy Nexus.
Face_Plant said:
I never noticed a huge difference with custom kernels on my old Galaxy Nexus.
Click to expand...
Click to collapse
Maybe it wasn't a good custom kernel I always have on every device I owned
optimusv45 said:
Maybe it wasn't a good custom kernel I always have on every device I owned
Click to expand...
Click to collapse
I've tried the ever popular Franco kennel and many others that I can't remember. The only BIG difference I noticed was the colors were a bit different, but that's about it.
Yo Heisenberg! I may be doing something wrong, everytime I run the shell I see the permission goes from enforced to enforced.
Sent from my SM-G900A using XDA Free mobile app
T3hPWN said:
Yo Heisenberg! I may be doing something wrong, everytime I run the shell I see the permission goes from enforced to enforced.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
+1 Same for me.
---------- Post added at 01:01 PM ---------- Previous post was at 12:05 PM ----------
I wonder if it's staying enforced because I do not have killer kat installed on the stock rom slot.
Nah, don't think that's it. I'm currently using the stock slot, and nothing has changed. Crossing my fingers that this can be straightened out...
Dirtburgler said:
+1 Same for me.
---------- Post added at 01:01 PM ---------- Previous post was at 12:05 PM ----------
I wonder if it's staying enforced because I do not have killer kat installed on the stock rom slot.
Click to expand...
Click to collapse
Ya I just booted into stock slot and tried it and got the same result.
Weird. I took a look at the script, and it mentioned busybox. It turns out that for some reason I lost busybox, and I am going to try this again and let you guys know if this is working on my end.
Dirtburgler said:
Ya I just booted into stock slot and tried it and got the same result.
Click to expand...
Click to collapse
---------- Post added at 12:50 PM ---------- Previous post was at 12:44 PM ----------
Looks like I'm seeing the script run now, but I am getting the whole SELinux has been set to Enforcing. Here's to hoping this gets fixed...
gangpe said:
Weird. I took a look at the script, and it mentioned busybox. It turns out that for some reason I lost busybox, and I am going to try this again and let you guys know if this is working on my end.
Click to expand...
Click to collapse
I tried the busybox route as well. I'm sure it is something simple that I'm forgetting.
Is there any other benefit than the possibility of flashing custom kernels when changing to "permissive"? If not, why am I changing it?
Related
I need someone to test a PA build I have built. I posted a build for the Sprint GNote 2 already and just need someone to test this before I post. Please lmk if you can help.
Once I get confirmation it boots and everything seems to be working I can post http://d-h.st/TcW and flash these gapps with it http://d-h.st/X4a
Downloading now.
Sent from my SCH-I605 using Tapatalk 2
---------- Post added at 10:51 PM ---------- Previous post was at 10:35 PM ----------
flashing fails with TWRP recovery. Gapps flash and rom doesn't
---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------
flashing fails with TWRP.
Gapps flash okay.
Rom fails.
What does it say exactly? Can you check md5?
Just shows failed.
{
"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"
}
Sent from my SCH-I605 using Tapatalk 2
Its gotta say a bit more. I appreciate all the feedback youve given me this far though.
I tried with and without the forcing of md5
Sent from my Nexus 7 using Tapatalk 2
Just to be clear, you do have a VZW GNote 2 running a VZW rom right?
Yes. Verizon gnote 2 running beans v2 with twrp recovery.
Wiped system, data, cache. Tried flashing PA a few times and gave me errors... then tried gapps for the heck of it and flashed fine.
Sent from my Nexus 7 using Tapatalk 2
Hmm ok then. I dont see why its not flashing. Ill have another build to try in the morning. Thanks for helping so far!
EDIT: If you can or whoever else, try this one http://d-h.st/TcW md5sum didnt match with first one when it got uploaded. Hoping thats why it wouldnt flash. LMK!
just throwing this out there but i bet it needs to be flashed with cwm recovery just like sbrissens cm10 build...ill give it a go!
flashed fine with CWM recovery and booted up...
droidstyle said:
just throwing this out there but i bet it needs to be flashed with cwm recovery just like sbrissens cm10 build...ill give it a go!
Click to expand...
Click to collapse
Ya, twrp does not play nice with cm builds... On top of that we don't even have the "official" twrp recovery. We are using a Sprint version and I have tried to flash the official build but it takes me back to stock recovery. I am sure you already knew that though my friend, judging by your infinite wisdom! I would definitely like to see PA on the N2 though! :good: It's too bad cause I can't stand any other recovery besides twrp...
shojus said:
Ya, twrp does not play nice with cm builds... On top of that we don't even have the "official" twrp recovery. We are using a Sprint version and I have tried to flash the official build but it takes me back to stock recovery. I am sure you already knew that though my friend, judging by infinite wisdom! I would definitely like to see PA on the N2 though! :good: It's too bad cause I can't stand any other recovery besides twrp...
Click to expand...
Click to collapse
this PA build is running damn smooth for a test!
droidstyle said:
this PA build is running damn smooth for a test!
Click to expand...
Click to collapse
OH YA!!
Alright thank you guys for testing! I'll post it up in a bit
Sent from my SPH-L900 using Tapatalk 2
Just so people know, the assert issues with TWRP are not isolated to our device, as I have seen similar issues when trying to flash CM on other devices. Not sure why.
imnuts said:
Just so people know, the assert issues with TWRP are not isolated to our device, as I have seen similar issues when trying to flash CM on other devices. Not sure why.
Click to expand...
Click to collapse
yes I ran into this on the S3 aswell...thank you for bringing us CWM!!!
So to say the least we should flash the unofficial cwm recovery if we plan on flashing CM roms at some point?
Sent from my Unlocked & Loaded Beast!
pschatz12 said:
So to say the least we should flash the unofficial cwm recovery if we plan on flashing CM roms at some point?
Sent from my Unlocked & Loaded Beast!
Click to expand...
Click to collapse
I would say any ROM that has device asserts in it. At least until TWRP can be fixed to process them properly. And truthfully, anything that gets flashed via recovery should have asserts to make sure you're flashing on the proper device, but many rarely include them if not built from source (myself included).
GPS working on this build???
Imnuts you post all over and are extremely knowledgeable! !!! Are you a developer? !
Sent from my Unlocked & Loaded Beast!
We got a tip and a screenshot of this for the N10, but I'm starting to suspect it was fake. Has anyone at all gotten the JWR66Y update today?
http://i.imgur.com/hIQjX2h.png
dunno about the n10, but the GN yakju update has been confirmed so it is likely i suppose.
http://android.clients.google.com/p....signed-yakju-JWR66Y-from-JWR66V.1b0ac7df.zip
edit: i got the link from this thread: http://forum.xda-developers.com/showthread.php?t=2414147
Saw that one, but I'm just looking for a confirmation on the N10.
Archon810 said:
Saw that one, but I'm just looking for a confirmation on the N10.
Click to expand...
Click to collapse
I got a very small system update last night on my N10. Not sure what the build number was on it. Can check later.
Just checked but still no updates for my N10, build JWR66V..I heard it's only a little security fix but I'm not sure about that
Inviato dal mio Nexus 10 usando Tapatalk 4
AleCai said:
Just checked but still no updates for my N10, build JWR66V..I heard it's only a little security fix but I'm not sure about that
Inviato dal mio Nexus 10 usando Tapatalk 4
Click to expand...
Click to collapse
Yes, JWR66Y is a very small update. There are no new features. It's purely a security update.
RogueWing said:
I got a very small system update last night on my N10. Not sure what the build number was on it. Can check later.
Click to expand...
Click to collapse
Just checked. That is the update I got last night.
nothing so far in my Nexus 10 or Nexus 4, but sounds like is real.. mostly bug fixes I guess.
Got it right now but installation failed because I had CWM touch recovery installed...
Now I can't get the update again...
Enviado desde mi Nexus 10 usando Tapatalk 2
Can you go into your /cache folder and get the name of the zip file?
I got it just now. Wouldn't update because I'd changed Velvet.apk now I can't get it again.
EDIT:
Ah, nice it was in cache like someone mentioned above. It is indeed JWR66Y
EDIT 2:
Copied it to the internal, flashed in TWRP. It said patching, removed root, but failed on flashing recovery.
I'll upload the file in a moment.
OK. If you guys get the update again, please look in your /cache folder and give us the filename before you try to install it. Once we have the filename, we can provide the link to the file on Google's server. That way, if you can't get it again, it won't matter because you can just download the file directly. Thanks!
Check above
---------- Post added at 09:45 PM ---------- Previous post was at 09:38 PM ----------
I couldn't sideload it using the stock recovery :/ It failed on "setperms"
I'll have to grab factory image and unpack it into a CWM zip at some point.
If anybody could make a zip for CWM thatd be awesome :good:
mine also fails at permissions - check this thread out seems to be figured out -http://forum.xda-developers.com/showthread.php?t=1745781&page=53
a line needs to be changed to #set_perm(0, 0, 0544, "/system/etc/install-recovery.sh"); because of the way the daemon is in supersu if somebody could whip up a manta zip like the ones they have were set
oldblue910 said:
OK. If you guys get the update again, please look in your /cache folder and give us the filename before you try to install...
Click to expand...
Click to collapse
I have JWR66Y downloaded from Google and haven't installed it yet on my unrooted N10. Do you need to be rooted to see the files in the /cache directory?
---------- Post added at 03:39 PM ---------- Previous post was at 03:14 PM ----------
Here's where the action is on this topic:
http://forum.xda-developers.com/showthread.php?t=2413535&page=15
So I ended up making my own zip for CWM, changed the line I mentioned above and removed the asserts. Worked fine here but flash at your own risk. Flashed supersu 1.51 after flashing the update and answered No to fixing the recovery.
**Only use if you are on Google's stock JWR66V odex hasn't been tested with other "stock" roms
NeoMagus said:
So I ended up making my own zip for CWM, changed the line I mentioned above and removed the asserts. Worked fine here but flash at your own risk. Flashed supersu 1.51 after flashing the update and answered No to fixing the recovery.
Click to expand...
Click to collapse
So, it appears that it's a small security update, it'll remove root, and I can expect to have problems with it with TWRP. Nice. Got it early this afternoon, will have to mess with getting it working later.
Jackietreehorn said:
So, it appears that it's a small security update, it'll remove root, and I can expect to have problems with it with TWRP. Nice. Got it early this afternoon, will have to mess with getting it working later.
Click to expand...
Click to collapse
Dude, every OTA ever in history removes root and reflashes stock recovery. This isn't news. Just flash and then re-root. It's a Nexus. You can do that.
Sent from my Xoom using Tapatalk 4
The 1.8MB OTA has arrived in UK:
{
"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"
}
NeoMagus said:
So I ended up making my own zip for CWM, changed the line I mentioned above and removed the asserts. Worked fine here but flash at your own risk. Flashed supersu 1.51 after flashing the update and answered No to fixing the recovery.
Click to expand...
Click to collapse
Will it work with twrp as well?
Sent from my Nexus 10 using xda app-developers app
Disclaimer: Flash this ROM at your own risk. I am not responsible for what you do on your device. I left this stock to provide a base for anybody that wants to use it. Mod this rom how you want. Just please remember to give credit where credit is due.
This is a pure stock rooted rom. It has items like busybox, init.d support, unsecure boot.img and so forth. No apps were added or removed. Both Odexed and Deodexed versions below.
This is using stock unmodified zImage from HTC. Kernel source can be grabbed from HTCDev when they decide to release it
Downloads
Thanks to rhcp for the dump and testing
Move along from this post (not thread) people, nothing to see here.
Vinchenzop said:
Here is a unsecured version of the boot.img I made. Either flash via fastboot, put into the rom.zip from above, or someone can make a flashable zip for it.
This kernel is unsecure for root, and adb superuser permissions (being able to mount system r/w via adb).
Again, it's only the boot.img, not a flashable zip.
http://d-h.st/gXX
Click to expand...
Click to collapse
yes these already have that included. Stock rooted roms that i make have unsecure boot included.
jmz said:
yes these already have that included. Stock rooted roms that i make have unsecure boot included.
Click to expand...
Click to collapse
The whole stock, unmodified didn't clarify that. But cool, I'll remove my post
jmz said:
This is using stock unmodified kernel from HTC. Kernel source can be grabbed from HTCDev when they decide to release it
Click to expand...
Click to collapse
Vinchenzop said:
The whole stock, unmodified didn't clarify that. But cool, I'll remove my post
Click to expand...
Click to collapse
I was speaking more specifically about zImage as technically I can't provide source because it doesn't exist. But yes, I understand how you read it and I will edit my OP. Thanks!
So what benefits does installing this provide?
ktimque said:
So what benefits does installing this provide?
Click to expand...
Click to collapse
Nothing right now really. But if you break something in /system on your device this will get you back running stockish
Sent from my HTC One using XDA Premium 4 mobile app
I have it downloaded for a just in case. Thanks for this.
EDIT: please disregard, unfortunately had to sell this device for some funds - purchased at retail to keep my unlimited data, could not get enough money out of my regular One, so I'm keeping it at least, sold the Max. The regular One feels so tiny now
Does anyone have issue with WiFi not working on these builds?
I do and havent been able to figure out why. On top of that my twrp backups seem to have disappeared. So Im not sure what to do from here
Wifi problems on odex or deodex? If both of you have problems on one try the other.
Jiggity Janx said:
Wifi problems on odex or deodex? If both of you have problems on one try the other.
Click to expand...
Click to collapse
I have flash both builds.
I have a seperate problem also. Whe I go to install and app it says I dont have enough storage which it far from true
stedrocklp said:
I have a seperate problem also. Whe I go to install and app it says I dont have enough storage which it far from true
Click to expand...
Click to collapse
wipe data on play services framework, reboot, manually start Google sync
jerrycycle said:
I have flash both builds.
Click to expand...
Click to collapse
Are you s-off? If not manually flash boot.img
Sent from my HTC One using XDA Premium 4 mobile app
jmz said:
wipe data on play services framework, reboot, manually start Google sync
Are you s-off? If not manually flash boot.img
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please never wipe play services framework. That used to be common but is now a very bad idea. There is a post from google about it recently.
Jiggity Janx said:
Please never wipe play services framework. That used to be common but is now a very bad idea. There is a post from google about it recently.
Click to expand...
Click to collapse
I have read that and understand what they are saying. But for problems with play store like that it has always fixed my problem with that... Never found the root cause of that problem
Understand that. Used to do it myself. Just recommend nobody puts out suggestions as fixes that may lead people to have deeper further issues.
I have s-off by way of rumrunner.
{
"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"
}
My screen looks just like above. I have tried flashing both roms and have no wifi. I have flashed the boot.img through fasboot and the radio in RUU via this post http://forum.xda-developers.com/showthread.php?t=2560283 with no luck.
I have pulled the appropriate libs from the OH1 update and put them in a flashable zip for those of you who want a fix for the stagefright Vulnerability, but don't want to update. I am currently on the OC5 build and I flashed the zip and the vulnerability has been fixed.
IMPORTANT: I have only tested this on the stock deodexed OC5, I can not speak on if it will work for anything else. If you're not on the OC5 build flash at your own risk!!
{
"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"
}
I am not responsible for anything that may or may not happen to your device, I am just telling you my experience. I recommend having a backup as always.
DOWNLOAD:
https://www.androidfilehost.com/?fid=24052804347798028
Sent from my note 3 running Beast Mode rom
Awesome work man..... nice job!!
Hello,
Can I use this on MJ4?
Thanks!
Sent from my SM-N900P using Tapatalk
Was this designed to be installed in recovery?
BHurst said:
Hello,
Can I use this on MJ4?
Thanks!
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Make a backup and try but since it was for lollipop base it may not.... try it and let us know.
Thanks,
Chaz187
---------- Post added at 11:22 AM ---------- Previous post was at 11:22 AM ----------
dcwashington said:
Was this designed to be installed in recovery?
Click to expand...
Click to collapse
Yes flash in recovery
Thank you @Chaz187
Sent from my note 3 running Beast Mode rom
Thank you for this JB
Hey JoHnNYBlaZE716, the binary-script removes the calendar and stuff since the script was from another package. I am not that familiar with Stagefright but I assume only the library files are needed since they seem to be the only thing in the system path.
Code:
delete("/system/app/Calendar.apk");
delete("/system/app/GoogleCalendar.apk");
delete_recursive("/system/app/GoogleCalendar");
delete_recursive("/system/app/CalendarGoogle");
delete_recursive("/system/app/Calendar");
Sorry I took a zip I had laying around, I'll fix that asap
Sent from my note 3 running Beast Mode rom
I have posted a new link for the stage fright fix that doesn't have the delete calendar script in the updater script. Thanks @dyehya for bringing to my attention and for making the new zip. I am currently without a pc at the moment so you were a great deal of help.
Sent from my note 3 running Beast Mode rom
The new fix did not work for me.
The checker still shows me as vulnerable.
TrofeoSC said:
The new fix did not work for me.
The checker still shows me as vulnerable.
Click to expand...
Click to collapse
One of the 2 apps will show as vulnerable still due to Google not catching the issue all the way. It is something on googles end that's all I know. There will most likely be another update fixing it completely. The app you're using should only show one of them in red correct?
You can read more in the article I have linked below
http://www.securityweek.com/android-stagefright-vulnerability-not-patched-properly-google
Sent from my note 3 running Beast Mode rom
Yes, only the top one in the list.
Thanks
JoHnNYBlaZE716 said:
One of the 2 apps will show as vulnerable still due to Google not catching the issue all the way. It is something on googles end that's all I know. There will most likely be another update fixing it completely. The app you're using should only show one of them in red correct?
You can read more in the article I have linked below
http://www.securityweek.com/android-stagefright-vulnerability-not-patched-properly-google
Sent from my note 3 running Beast Mode rom
Click to expand...
Click to collapse
Dude it's been a while u had shown ur OC5 custom rom on tx_dbs_tx's thread.
i guess that's what u r using right now. are you planning to release it?
Will I b able to keep stock root if I do the full update?
Sent from my SM-N900P using XDA Free mobile app
Yes i plqn on releasing my rom it should be about done soon, just touching up a few things. Amd if you take the update for the OH1 then yes you will lose root and go back to stock. You can just flash this zip for the stagefright fix if you want.
JoHnNYBlaZE716 said:
Yes i plqn on releasing my rom it should be about done soon, just touching up a few things. Amd if you take the update for the OH1 then yes you will lose root and go back to stock. You can just flash this zip for the stagefright fix if you want.
Click to expand...
Click to collapse
That's what I keep saying about my theme until I find something else that needs themed, lol.
Sent from my Galaxy Note 3 using AnaKonda Tapatalk
AnaKonda Theme
eREDicate Theme
JoHnNYBlaZE716 said:
Yes i plqn on releasing my rom it should be about done soon, just touching up a few things.
Click to expand...
Click to collapse
Man that answer hasnt changed since july end...hehe !!
I guess you are busy with ur stuff. Btw do release if u get time or else the device is as good as dead.
and any major difference betn OC5 and OH1?
and hopefully u release fix 2 soon too mate....:highfive:
I am using fre3 4.4.4 KitKat ROM and I am on OC5, flashing your zip just makes my phone get stuck on the Samsung logo. Anything special I need to do? Clearing Davik and Cache doesn't fix it.
joelstitch said:
I am using fre3 4.4.4 KitKat ROM and I am on OC5, flashing your zip just makes my phone get stuck on the Samsung logo. Anything special I need to do? Clearing Davik and Cache doesn't fix it.
Click to expand...
Click to collapse
I honestly can't answer your question, I've personally only flashed it being on a stock oc5 rom. No one has reported any issues so I don't know why it wouldn't work. The files were pulled from the oh1 update for the sprint note 3
Sent from my SM-N920P using Tapatalk
http://forum.xda-developers.com/honor-6/general/guide-workaround-running-xposed-t3338765
Thread above. Im probably gonna try it later
{
"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"
}
Sent from my KIW-L21 using Tapatalk
Faheemarif252 said:
HUGE IMG
Click to expand...
Click to collapse
Use a web browser, if u getting that message when tryna click the link
Kennii said:
Use a web browser, if u getting that message when tryna click the link
Click to expand...
Click to collapse
It opened fine.... And the method should work just fine.... Yielding no problems whatsover... Do give it a try and tell us your findings...
Ps. I wouldve tried but I'm still waiting for my unlock code
Sent from my KIW-L21 using Tapatalk
Trying this now. Just to be certain this is an ARM64 device? Can't find any info on this other than somone using 64-bit G-apps.
EDIT: Didn't work for me Using stock rom. KIW-L21
Jammo2k5 said:
Trying this now. Just to be certain this is an ARM64 device? Can't find any info on this other than somone using 64-bit G-apps.
Click to expand...
Click to collapse
Yes ARM64, and xposed work's very well
flecky22 said:
Yes ARM64, and xposed work's very well
Click to expand...
Click to collapse
Hmmm How long did it take to boot after you flashed the xposed zip?
about 5/10 minutes
flecky22 said:
about 5/10 minutes
Click to expand...
Click to collapse
Damn i din't leave it that long. Will redo now
flecky22 said:
Yes ARM64, and xposed work's very well
Click to expand...
Click to collapse
So this does work? What model do you have? Can anyone confirm it's working on l24? I've been hoping to get xposed until we get some custom rom action!
wickedesires said:
So this does work? What model do you have? Can anyone confirm it's working on l24? I've been hoping to get xposed until we get some custom rom action!
Click to expand...
Click to collapse
Yes it's work, i have a L21.
flecky22 said:
Yes it's work, i have a L21.
Click to expand...
Click to collapse
Sweet! Gonna try this in a bit. Thanks for confirmation. Any performance issues so far?
No, for me it works as before
Yeah i have another issue now... It says it's installed but not activated :/
"For Android 6.0pen build.prop and add these lines ro.config.hwtheme=0 and ro.config.hw_theme=0
For Android 5.0-5.1.1: Open local.prop (in system/emui/base/prop/local.prop) and add these lines ro.config.hwtheme=0 and ro.config.hw_theme=0
Again reboot your device (this boot won't take long)."
In honor 5x local.prop (in cust/hw/eu/prop)
flecky22 said:
"For Android 6.0pen build.prop and add these lines ro.config.hwtheme=0 and ro.config.hw_theme=0
For Android 5.0-5.1.1: Open local.prop (in system/emui/base/prop/local.prop) and add these lines ro.config.hwtheme=0 and ro.config.hw_theme=0
Again reboot your device (this boot won't take long)."
In honor 5x local.prop (in cust/hw/eu/prop)
Click to expand...
Click to collapse
Yeah i missed that bit. A combination of being a bit of an idiot, tiredness and nagging girlfriend.
Jammo2k5 said:
Yeah i missed that bit. A combination of being a bit of an idiot, tiredness and nagging girlfriend.
Click to expand...
Click to collapse
lol
Arobase40 said:
How long did it take after the first boot (after app, framework and Priv-app copying) and did you have any messages saying "optimizing apps" or such ?
It's being said to wait about 20-30 mn and I'm waiting for almost 1 hour at the Honor Logo... ^^
Click to expand...
Click to collapse
5/10 minutes and yes i have a message like optimizing apps
Test in build.prop or deactivates resource hooks in xposed settings, but then if you want to use gravity box for example, it will not work, build.prop change is the best solution.
---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------
build.prop change is enough , I just tried , no need to change local.prop .
Arobase40 said:
Hmmm, damn it !
Don't understand why it was not working the first time...
Now, I got everything installed but I couldn't modify the /cust/hw/eu/prop/local.prop file !!!
I'm in R/W, but every time I modify the file, I loose the changes when I leave it and so the Xposed framework can't activate... ^^
Click to expand...
Click to collapse
I used es file explorer (an older version) to edit the local.prop and I had to select the root of the SD card to get it to save correctly (I have absolutely no idea why lol). After that everything worked great.