yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Android Development (Exynos)] yuniantori:
Greeting mdpalm2

I just try this rom, so far is no issues are so annoying for me, accept about this Photo Studio FC when I try to edit a picture using a pencil.

You said that installing spen app will solve the problem, well I have tried so many s pen app... but no luck, could you please give us specific about the spen app, what's is it actually ? :D

Thanks for your kindly reply :)
[Galaxy S 5 Android Development (Exynos)] weedvn1:
Googy max stweaks?

What does it do? And are there anyway to uninstall it?
[Galaxy S 5 Android Development (Exynos)] manikandan143g:
does theme work's on both notification and dial pad ????

:confused:
[Galaxy S 5 Android Development (Exynos)] TheDarkSithLord:
Nope this tread is dead use Aj's full s7 port
[Galaxy S 5 Android Development (Exynos)] feelmylove1438:
Hello,

I've been using this rom for G900H since about an year till now... It is amazing and iam still using it.

All i wanted to know is, is there going to be Marshmallow full port rom to s7 for G900H?

There are many other custom roms in Internet.. But i like this ladesar rom so waiting for an update.. :)
[Galaxy S 5 Android Development (Exynos)] TheDarkSithLord:
Dev sold his phone development fully stoped ( recomend you for daily usage wanted rom 5.1
[Galaxy S 5 Android Development (Exynos)] feelmylove1438:
Thanks for your reply.... Can you suggest me best marshmallow port for s5 g900h.

Thank you in advance.
[Galaxy S 5 Android Development (Exynos)] TheDarkSithLord:
Well if you need s7 port the best one for now wanted rom 6.0
[Galaxy S 5 Android Development (Exynos)] manishkunkana:
Downlaod link is not Working Please Help me Out
[Galaxy S 5 Android Development (Exynos)] pranksterpamit:
download

I could not get the download link.
[Galaxy S 5 Android Development (Exynos)] hussains345:
no download link?
[Galaxy S 5 Android Development (Exynos)] Chinhai:
This project is stopped for a long time. Try S7e Ported ROM

https://xdaforums.com/galaxy-s5/gal...ynos/rom-yash92duster-mm-6-0-1-stock-t3411527
[Galaxy S 5 Android Development (Exynos)] wrenjf:
Unable to download the ROM !! from MEGA - file not available - deleted by user.

please provide the link to download v5.0
[Galaxy S 5 Android Development (Exynos)] Phuc98:
link rom dead
[Galaxy S 5 Android Development (Exynos)] amir215909:
why s6 port while we have s7 port?
[Galaxy S 5 Android Development (Exynos)] Phuc98:
I do not know what you are talking about
[Galaxy S 5 Android Development (Exynos)] GearXghoul:
its not there

just when i thought that i found a great rom
[Galaxy S 5 Android Development (Exynos)] smnmasoud:
hi bro...this link not found...plz insert other link

tnx

hi bro

can u refresh download link for that rom "

[ROM][G900H][5.0][TW] Ladesar Rom For S5 V4.5 {Full S6 Port}​
[8525, TyTN, MDA Vario II, JasJam ROM Development] finisterre:
Anyone got a link to one that runs on XP?

Thanks.
[8525, TyTN, MDA Vario II, JasJam ROM Development] goestoeleven:
SOTI Pocket Controller works great on both XP and Vista

http://www.soti.net/
[8525, TyTN, MDA Vario II, JasJam ROM Development] finisterre:
Thanks. I should have specified I would prefer a free one. I used one a couple of years back, but I forget what it was called, and couldn't turn it up with Google.
[8525, TyTN, MDA Vario II, JasJam ROM Development] larsuck:
Workaround

I use PHM Regedit on the PPC and MyMobiler on XP http://www.mtux.com/ . MyMobiler is kind of a scaled-back (and freeware) version of (overpriced)SOTI PocketController, but has a lot of cool features that SOTI doesn't. For example, you can drag-and-drop cabs from the PC to the mobile screen and it will auto-install them.
[8525, TyTN, MDA Vario II, JasJam ROM Development] finisterre:
Looks nice. Just installed it. However, the one I used before let you view/search/edit the PocketPC registry using a PC-based GUI rather than just remote controlling the PPC in a window.

Sorry for the confusion.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Dr Puttingham:
I also use PHM Regedit on my PDA but I use Mobile Registry Editor to access my PDA's registry from my laptop.

Not perfect but badass none the less.
[8525, TyTN, MDA Vario II, JasJam ROM Development] finisterre:
Cheers Doc. I use PHM too but Mobile Registry Editor by Breaksoft is the one I was looking for.

Thx.
[8525, TyTN, MDA Vario II, JasJam ROM Development] DisTreSs:
Hi guys, I found MRE thx to you guys but when I use it on my Trinity and try to delete some keys it always gives me access denied...

Anybody any ideas?
[8525, TyTN, MDA Vario II, JasJam ROM Development] Dr Puttingham:
See if changing HKLM\Security\Policies\Policies\00001001 = 1 (RAPI) and

HKLM\Security\Policies\Policies\00001005 = 40 (Cert) help

The MRE FAQ has more info regarding this.

PS (Sept 23, 2007) I had to setup a WM5 Samsung i830 the other day and created this security settings cab... enjoy!
[8525, TyTN, MDA Vario II, JasJam ROM Development] chunkymonkey:
If you download CorePro or UltimateCore they have some great remote regedit software included - saves hunting about.

There's a tool to run a complete dump (to .txt file) of your PPCs registry and one to edit it as if you were using PHM, Resco or even Regedit on your desktop - but in WinXP.
[8525, TyTN, MDA Vario II, JasJam ROM Development] larsuck:
Just found this one. It is quick and looks to have more options than Mobile Registry Editor
[8525, TyTN, MDA Vario II, JasJam ROM Development] cyphol:
This is a good one.
[8525, TyTN, MDA Vario II, JasJam ROM Development] petervbeck:
CE Regedit

There's also a project here on xda: CERegedit or it is the same as in post 11 ?!

Cheers
[8525, TyTN, MDA Vario II, JasJam ROM Development] Dr Puttingham:
Just saw this one floating around, TorchSost Registry Workshop, looks interesting.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Runit1:
That's the one I was looking for. I had used it once but could not find it. Was on my old computer.
[Galaxy Note5 Original Android Development] garyd9:
NOTE: This thread is for the discussion of kernel development. If you don't recompile kernels, please don't post/reply.

After a couple years playing with nexus devices, I'm coming back over to Samsung (until I get bored) and I'm seeing that no one has managed to root a Note 5 device without a recompiled kernel. Why? Because using the stock kernel seems to result in just boot loops.

From what I've been able to observe, the custom kernels all have one thing in common in regards to allowing root to work: They are all changing sepolicy to run permissive instead of making modifications to allow 'su' to work in enforcing mode.

Why?

I have to be honest in saying that I haven't studied how [MENTION=631273]Chainfire[/MENTION] had managed to get su working on the nexus devices while retaining sepolicy in enforcing mode, but it seems that this would be a far better solution than just neutering sepolicy all together.

Has anyone yet attempting to get a sepolicy enforcing kernel working with root? If so, are you willing to share what you tried and how things worked out?

My end-goal is probably to throw together a "as stock as possible" kernel that's root-able. If at all possible, I'm hoping that just some modifications to the ramdisk would be enough to get things working. However, I'd like to take advantage of any previous work done (if any) to get this working.

Thanks

Gary

Edit:

FOR CLARIFICATION. THIS THREAD IS NOT FOR GENERAL USER DISCUSSION. THIS IS FOR DEVELOPERS TO DISCUSS SELINUX, THE NOTE 5 KERNEL, AND METHODS BY WHICH ROOT CAN BE ACHIEVED WITHOUT CHANGING SELINUX TO PERMISSIVE.
[Galaxy Note5 Original Android Development] :
Reminder,

Read the OP and stay on topic.

Thanks.

The_Merovingian

Forum Moderator
[Galaxy Note5 Original Android Development] DAGr8:
I have to ask my friend. Since I'm back to Samsung at the same time as you it seems. I see very little advantage of running root atm but I see none of running Selinux non permissive. Also these devices being exynos you will not find much support for it.

I may be wrong but Selinux non permissive has been a problem on samsung custom roms from day one guys just disabled it and be done with I've never seen anyone complain ;p
[Galaxy Note5 Original Android Development] garyd9:
I'm in the process of trying to modify the sepolicy in the stock boot image ramdisk to see if that allows root to work with the stock kernel (modified ramdisk.)

Wish me luck. ;)

Dammit - all of my tools are out of date. Have to recompile mkbootimg, unpackbootimg, etc.
[Galaxy Note5 Original Android Development] garyd9:
Okay, so I'm finding out all kinds of Fun Things that Samsung has done with this device...

First, at least some versions of this phone (mine is a 920i) have something in the stock firmware kernel(?) that restores factory recovery on first boot. This is my first sammy device in several years, but I seem to remember reading that other samsung devices have done this as well. (This is the reason that people are having to not allow ODIN to auto-reboot the phone.)

What's really pissing me off, however, is that if I allow TWRP to modify the system partition (based on the prompt on the initial boot) and don't actually make any system changes, the normal stock kernel won't boot... it gets stuck in a boot loop. (pre-bootanimation)

This is similar to the reports people are having of boot loops if they install root without changing the kernel. I'm starting to think it has nothing to do with actually being rooted, but that ANY system partition change is causing the bootloop. (Surprise!)

So, I decided to try something a bit different: I restored stock firmware (tar.md5 via odin) and after the reboot, I went back into ODIN mode. This time, I flashed TWRP and rebooted immediately back into ODIN and a flashed kernel with a modified sepolicy in the ramdisk. I then booted normally. My kernel loaded. I used adb to reboot to recovery. TWRP loaded. From TWRP, reboot normally.. it worked. Good start. adb reboot recovery, and this time I uncheck the option to "only mount system R/O." (It's in the "mount" section of TWRP.) Reboot system... and... BOOTLOOP.

(This has nothing to do with root. I'm not installing root... )

Time to start digging in the kernel ramdisk to try and figure this one out...
[Galaxy Note5 Original Android Development] garyd9:
Tried the same as above, but with Philz compiled by [MENTION=4898097]arter97[/MENTION]. This time, I was stuck in a bootloop after the first time recovery ran. I'm guessing that this particular recovery will ALWAYS touch the system partition without first asking? Not sure... Philz did ask if I wanted to install root when I chose the option to reboot, but I declined.
[Galaxy Note5 Original Android Development] garyd9:
Note to self:

http://xdaforums.com/showpost.php?p=61542104&postcount=433

I have NFC what "support_scfs" is, but I'll have to spend some time with google to figure it out. Perhaps a bit of SourceDiving. Won't have a chance to test this until tomorrow evening.
[Galaxy Note5 Original Android Development] garyd9:
I love replying to myself. The truth is, I'm probably one of the few people who could stand talking to me. Of course, even I feel like killing me every now and then. It gets complicated.

Oh.. anyway.. I got it. A stock kernel with a modified ramdisk running selinux in enforcing mode and root-able. I want to spend a day running tests, but will post results of the results in about 20 hours. (assuming I get to sleep tonight...)

As well as gaining the enforcing selinux security (somewhat degraded by being rootable), this also ensures all hardware is working even if samsung "cheats" in posting source code.

(see attached screenshot... it's really the stock kernel and still enforcing SE for Android. :))

Edit:

Then again, there's no harm in posting the boot image now. This is from a n920i device using the N920IDVU1AOH6 firmware. I'm attaching a file that can be unzipped and flashed with ODIN (AP slot.) Someone fluent should be able to pull the boot image out of the tarball and flash it directly with TWRP or even via 'dd' (assuming you're already rooted.)

(If you try to flash the .zip file directly, you deserve whatever horrible things happen to your phone.)

THIS IS NOT A RELEASE. THIS IS FOR DEVELOPERS WHO KNOW WHAT THEY ARE DOING TO FIND FLAWS WITH IN REGARDS TO ROOT AND SELINUX. I can't claim this would work for any device without the above mentioned firmware. If you don't know exactly how to recover from Bad Things, don't even download the attachment.

No support. No help. If you have to ask how to flash this or anything of the sort, this isn't for you.
[Galaxy Note5 Original Android Development] garyd9:
Changes from stock ramdisk:

1. Modify sepolicy as [MENTION=631273]Chainfire[/MENTION] documented (ironically using an unrooted note 5) to allow supersu to work it's magic.

2. Modify fstab to remove support_scfs,verify from the mount options for the system partition. (this solves the boot loops)

That's IT.

One warning, though: This is using supersu beta 2.51. That's not released. Actually, I think it's flagged as a work in progress.
[Galaxy Note5 Original Android Development] svadev:
Please, publish original boot.img from N920IDVU1AOH6
[Galaxy Note5 Original Android Development] garyd9:
Did you not bother to read any of the posts in this thread? There are known locations for stock images. This thread isn't one of them.

Read the very first line in the first post.
[Galaxy Note5 Original Android Development] svadev:
I made it for my SM-N9208, and it is really works with supersu 2.50 .

Thanks!
[Galaxy Note5 Original Android Development] geek78:
Hi

Could you please post a more detailed guide ? I want to do it myself for my n920c.

Thanks ;)
[Galaxy Note5 Original Android Development] garyd9:
yeah. well, at least assuming you know how to unpack and repack boot images... (Because this stuff is very experimental at this point, and still very much a work in progress, you should have a certain level of proficiency before mucking with it. I can't and won't hold anyone's hand for this stuff at this point.)

you need to unpack the boot image. Get the boot.img and unpack. Open the ramdisk. In the ramdisk is a file called 'sepolicy.'

Start with this post to figure out how to change it:

http://xdaforums.com/showpost.php?p=63190351&postcount=2071

Find the reply to that post from Chainfire to see how it can be done without a "reference" device.

You'll also have to change the proper fstab as I documented already in this thread.

Then pack up the ramdisk and repack the boot image.
[Galaxy Note5 Original Android Development] geek78:
Thanks. Perfect !
[Galaxy Note5 Original Android Development] garyd9:
I'm trying to place your name. Do I know you from SGS2 days or Note2 days?

Anyway, I'm not happy with settling. Never have been...

Edit:

Note or Note 2. Must have been Note2. You were doing smali edits for enabling tablet mode. That was pre-xposed days.

Edit 2:

To answer the question: enforcing selinux adds a layer of security on the device and blocks many security infractions. Basically, if you haven't been given permission to do something, you can't do it. Even as root. In theory, selinux could block the stagefright security issues. When a device is in "permissive" mode, selinux is there, but isn't actually blocking anything. It just logs violations and then ignores them.

In other words, permissive mode completely negates having the se extensions at all. Permissive was a mode that devs could run in to see what might break and what might not.

"root" access is, of course, a hole in the scheme. Chainfire, with supersu, has done quite a bit to ensure that the hole is controlled, but it's still a hole. However, a rooted device with an enforcing selinux kernel is still significantly more secure than a non-rooted permissive selinux kernel.

Another edit:

Here's some links:

https://su.chainfire.eu/#selinux

http://linux.die.net/man/8/selinux
[Galaxy Note5 Original Android Development] garyd9:
<sarcasm> Wow, I almost forgot how much JOY and FUN it is working with Samsung sh!t kernels. </sarcasm>

So, in testing this (yes, I really DO test things.. imagine that) I found that my device wasn't going into deep sleep. Wow. How interesting. Oh, and not a single wakelock. WTF?!

Instead of google'ing first, I reverted to being a kernel dev (that is now trying to debug a kernel that he hasn't even compiled.) The first thing a kernel dev looks at: "dmesg" So, I copy dmesg to a file and transfer it my PC. (BTW, Notepad++ is God's gift to windows editors.) I search for various strings like "error" and "fail" and "suspend." What I end up seeing is a crapload of messages like this:

[0: system_server: 3858] PM: Device 0:0:0:x failed to suspend: error -5

(replace x with 1, 2, or 3)

Huh? So, before I dive into the code (because I really don't believe that samsung actually shares the kernel code that they use for themselves), I decided to google around a bit. I finally had enough search terms to hopefully narrow down the search results.

Guess what I found? People having the exact same problem on another samsung device: the S6 (and edge.) Here's the best of the threads:

http://xdaforums.com/galaxy-s6-edge/help/deep-sleep-t3079705

It gets into some interesting detail around page 4 and 5. You'll have to skip past all the clueless people preaching about turning off wifi, downloading snake oil, and worshipping recycled NiCad batteries.

To make a long story short, the stock kernel (or perhaps the bootloader? That shouldn't be possible...) marks a few block devices as read-only if you're using a modified device. (If it's rooted, it's modified. If KNOX is tripped, it's modified, etc.) The kernel from Sammy is trying to flush caches to those devices (which is ironic when you consider they are marked read-only) before going into the suspend. The flush fails, so the entire suspend process fails. It seems that on the SGS6, there were only two devices like this. On the Note5, it seems to be 3 (everything except sda)

In that thread, [MENTION=2266182]HomerSp[/MENTION] not only tracked down the problem there, but also (thankfully) figured out that writes to a file in the /sys tree could work around the issue. Thankfully, because the entire point of THIS thread is to use the stock compiled kernel (with a modified ramdisk) to make life Happy. With 3 writes to the /sys tree, magically the device goes to sleep.

(Yes, I'll be taking care of it... and documenting it better...)
[Galaxy Note5 Original Android Development] garyd9:
What a pain... for some reason, I couldn't write to the cache_type files from within the init.rc structure. No clue why not. Ended up having to add a "service" to the init structure

Anyway...

If you're following along at home, add the following lines to the bottom of init.rc:

service fix_cache_types /system/bin/sh /sbin/fix_cache_types.sh
class core
user root
oneshot

Then add a new file in the ramdisk's sbin directory called (I bet you guessed this already): fix_cache_types.sh

That file should have perms of 0750 and contain the following:

#!/system/bin/sh
echo 'temporary none' > /sys/class/scsi_disk/0:0:0:1/cache_type
echo 'temporary none' > /sys/class/scsi_disk/0:0:0:2/cache_type
echo 'temporary none' > /sys/class/scsi_disk/0:0:0:3/cache_type

If you're using the same kernel as I am (n920i), I've attached an updated image. Same rules, conditions, instructions as the last one I posted earlier in this thread. Except this one lets the device take naps. It helps the battery life. ;)

Tomorrow (or Sunday) I'll see if this all works with xposed or not. (I seem to remember something about xposed not working with selinux enforcing kernels, but I could be wrong.) After that, if nothing prevents it (or me), I'll repackage this stuff again, and also throw together an n920c kernel (based on N920CXXU1AOH6) for general use.

BTW, at least on my n920i, I've confirmed that I don't reboot when getting a call (or making one), that NFC works, that bluetooth works, that I can wirelessly charge and quick charge. I'm trying to ensure all the "common" complaints with non-stock boot images are non-issues before giving this out... The whole purpose of using the stock kernel is to retain enforcing selinux and retain completely functional hardware.
[Galaxy Note5 Original Android Development] geek78:
Hi

I have unpacked my boot.img. So I can see my sepolicy file in ramdisk/, I have patched it with my rooted Nubia Z9 but I don't understand next steps. Do you have time to explain a little more ?

For the fstab mods I have done it in fstab.samsungexynos7420 and fstab.samsungexynos7420.fwup. Is it ok ?

Thanks.
[Galaxy Note5 Original Android Development] garyd9:
Need I say more?
[Galaxy Note5 Original Android Development] garyd9:
I've locked this thread down. Despite the fact that I've posted over and over in the thread asking people to no post/reply unless they are going to contribute... There are still those who ignore me. Over and over. And then they get nasty when I don't stop everything I'm doing to spoon feed them.
[Verizon Samsung Galaxy Note5] tunx:
Hi all

I have noticed something odd on my lockscreen lately. Slight discoloration on the top of the screen all across the status bar which immediately disappears after I unlock the device. Please see the attached screenshot of the same. I have tried different wallpapers but nothing seems to make a difference. I have revisited settings and searched everywhere but cant figure it out.

Please help.
[Verizon Samsung Galaxy Note5] BluT00th:
That appears to just be a Gradiant mapping to the lock screen. I wouldnt worry about it.
[Galaxy S6 General] godutch:
Time to hit the update buttom 78MB COI9 is out, nothing special in the changelog except generic bug fixes and may contain new features; still 5.1.1
[Galaxy S6 General] bcik:
The keyboard problem did you have?

http://xdaforums.com/galaxy-s6/help/swiftkey-slowly-due-to-ram-problems-t3174834
[Galaxy S6 General] godutch:
I was using stock, so I don't really know (stock used swiftkey engine too btw) and I just did the update
[Galaxy S6 General] DT84:
Camera shutter speed or RAW support?
[Galaxy S6 General] bcik:
Okay. Thanks.
[Galaxy S6 General] johanbiff:
nop
[Galaxy S6 General] Razvan:
Please continue discussions about this specifically update to existent thread opened earlier.

http://xdaforums.com/galaxy-s6/general/sw-update-to-s6-g920fxxu3coi9-t3219995

Razvan

Forum Moderator
[Moto G Q&A, Help & Troubleshooting] weezerao:
How to Flash Stock rom using Ubuntu ?
[Moto G Q&A, Help & Troubleshooting] satanas17:
Hi, in first..

Go to Ubuntu market and install fastboot and adb if they are not already on it...

Take a look on fastboot and adb tutorials, you'll find answers...
[Xperia Z3v General] Tigerhoods:
So some of you like me don't like the drop down status bar and notifications being grey. you can edit this in the system ui by putting in number codes that represent the color of the drop down panel. Or the easy way is to download (blurred system ui lp) on xposed. it makes your panel clear with a blurred background and it looks amazing with the theme I have. Enjoy.
[Xperia Z3v General] shashikiran:
ya fine interface
[Galaxy S6 General] johanbiff:
The update brings some battery optimization ft.. Samsungs doze? :)
[Galaxy S6 General] johanbiff:
Using Samsungs keyboard. . No problems
[Galaxy S6 General] bcik:
Okay. Thanks. Conspicuous so what else is new?
[Galaxy S6 General] johanbiff:
Dont know, just got it but it seems like one more ft was added "autorestart"..or atleast I havent noticed it before (see attach)
[Galaxy S6 General] bcik:
Automatic startup had before.
[Galaxy S6 General] bamse84:
Hi! I see that your phone language is Swedish.. I have one question is the ota update for NEE? Thank you
[Galaxy S6 General] godutch:
XEF (France)
[Galaxy S6 General] bamse84:
Ok.. I see. That means that he already had the french version.. Thanks
[Galaxy S6 General] johanbiff:
XEF France. . I put The french firmware in using odin so I could get faster updates