yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 & S8+ Cross Device Development] Alcibiade:
Thanks.

I figured out what's going on wit my device. I tried from TWRP flashing magisk v14.2. Thing were ok until at some point after a reboot I end up at boot with the following message "Custom Binary(recovery) Blocked by FRP Lock

Security Error: This phone has been flashed with unauthorized software & is locked. Call you mobile opertor or aditionl support. Please note that repair/ return for this issue may have additional cost". Which is what I ended up before.

After several flash and reflash to try to get around it... I finally noticed what was screwing me: I got a message from SecurityLogAgent, "Unauthorized actions have been detected. Restart your device to undo any unauthorized changes". If delete my gmail account any reboot goes well. If I keep he gmail account I end up with the FRP lock. at restart. I suppose the @^$# SecurityLogAgent screws up something somewhere. I will try to disable it before it has time to do any damage, not sure it's easy though since I may nee rot to disable it (Of course this big pile of garbage doesn't ask you if you agree to roll back anything...). Alternatively maybe deleting my gmail account and reflashing dm-verify & magisk will be enough.

Worth noting: I get this issue with the latest ROM AQG6. It seemed ok on AQF7. This doesn't bode very well for future updates. Thank you so much Samsung for leaving us with so little freedom with the deice we purchased.... I may consider a Pixel 2 if retaining root is so annoying...
[Samsung Galaxy S8 & S8+ Cross Device Development] kjames2001:
Lol, check the twrp thread, Cameron just posted a solution to frp lock.
[Samsung Galaxy S8 & S8+ Cross Device Development] Alcibiade:
Thanks, indeed it allows to go around the FRP lock. Nevertheless the new ROM seem more nasty and actually flagging the fact it has detected something wrong. So far it's acting only on the FRP lock luckily... Not sure where it will take us next though
[Samsung Galaxy S8 & S8+ Cross Device Development] atonal:
Hi Mates...sorry for the confusion, don't know why i thought,you are jesec....

But however,my problem wasn't the viper installation (btw does it works with ah3 Firmware yet? One month ago,it won't)....

My problem was, that, if i installed jesses kernel, and viper, the Gear VR don't detect the s8 anymore then.....think, a problem of the kernel....

Now,i am on stock, without root, but i miss viper sound. But i must be sure, Gear VR will work after flashing the kernel.

In the standard instructions for flashing viper with magisk, they forgot, you need a permessive kernel to work viper. Otherwise,it won't work.

So,stock kernel, magisk and viper, will not work.

Greetz amd thx
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
Oh! You're g9500? Don't flash Cameron kernel then it is only for g9550 errmmm yeah I would try magisk and use magisk hide on gear VR.
[Samsung Galaxy S8 & S8+ Cross Device Development] kjames2001:
If stock doesn't work with viper, then there's nothing you can do at the moment. Just wait for a new kernel from Cameron, I hope he can fix this issue, if he decide to develop for 9500 that is.
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
It's not that hard really it's all the same just a different defconfig just more so finding time I have like 3 projects I wanna do at once XD plus maintaining a social life plus school and work, I typically get about an hour in every day of work on the project.
[Samsung Galaxy S8 & S8+ Cross Device Development] lifescore:
I repack kernel. Work magisk 14.2 and viper. SELinux permissive. Test

https://drive.google.com/open?id=0B96K8Q7Q3XbgMEZsRV9rQ1N0Rmc
[Samsung Galaxy S8 & S8+ Cross Device Development] boonthongw@gmail.com:
Tested. It works fine on my 9550
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
Hey mate, I tried to compile a kernel from samsung's official source code, and enable some kernel features, but always failed with a 'seandroid enforcing' error, It seems samsung doesn't want users to use their source code on their phones... I have asked about this on some threads, but still nobody can help yet. So could you please give me some tips?

Be honestly, this semi-stock kernel won't work with USB OTG, I just want a kernel with this supported.

I really have no idea right now... Thank you soo much for any help. :)

Best regards.
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
So the reason it would fail is a ramdisk edit that has to be made I'll post it tonight if I get time.
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
You mean my self-compiled kernel failed to boot is because of the ramdisk? Maybe, I actually used the files extracted from the stock kernel, and I only changed the mount options in fstab. ;)
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
these are the needed ramdisk updates to allow it to boot custom kernels https://github.com/DevriesL/SM-G950...869c9ec#diff-5c5f44ab0550487fbce8a2874ebaab6a
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
Thanks for this info, it's really new to me. But unfortunately, after changing these files, it still doesn't work.

I just wonder, why does jesec use the source files from CM, and patched some libraries on /system partition? And the ramdisk/default.prop file in that semi-stock kernel seems wasn't changed at all. I really don't think samsung's source can work directly.

Also BTW, I don't care about solving this sooner or later, just take your time. Thank you anyway.
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
How are you building the kernel? It did for me when I built at least.
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
Alright, I did more confirmation, still no luck.

My phone is galaxy s8 sm-g9500 china mainland variant, snapdragon. I got the source code from here ( http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-g9500). I tried all 3 versions except the HK one.

To compile it, I used these commands:

export CROSS_COMPILE=/home/liu/android-ndk-r14b/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android-
export ARCH=arm64
mkdir out
export OUTPUT_DIR=out
make -C $(pwd) O=$(pwd)/out KCFLAGS=-mno-android dreamqlte_chn_open_defconfig
make -C $(pwd) O=$(pwd)/out KCFLAGS=-mno-android -j16

Then I got the 'Image', 'Image.gz' and 'Image.gz-dtb' 3 kernel files. Next, use the 'mkbootimg_tools' from github to unpack the stock boot.img, edit the files in ramdisk, and repack the boot.img with one of the image files. I tried both 'Image.gz' and 'Image.gz-dtb'. The first one boot into download mode instantly, the second stuck there, both of them are shown a 'kernel is not seandroid enforcing' message. It doesn't show any hope to get work...
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
Ohhh! Did you flash cameron.zip?
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
Actually not, but I think it's already done by the 'semi-stock kernel' zip, because I checked the sha1 sum of these files:

/system/vendor/lib/libsecure_storage.so

/system/vendor/lib/libsecure_storage_jni.so

/system/vendor/lib64/libsecure_storage.so

/system/vendor/lib64/libsecure_storage_jni.so

And it seems they are the same to the files in the cameron.zip.

Sorry I haven't flashed it yet because I haven't fully backed up the data in my phone, and I want everything are undo-able now... :P

If I'm wrong, please let me know, and I will backup and try it. Thanks again. :)
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
How are you installing your boot image?
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
In twrp, select install - install image - boot.img.

And also tried to use commands in twrp terminal

dd if=/tmp/boot.img of=/dev/block/sda17
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
That's so strange... G9550 didn't have that issue but I was also using jesecs source. I'll compare the two's defconfigs later Monday and probably overlap source with his and see what was all different that he modified
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
haha, ok, good luck. thanks for your help.
[Samsung Galaxy S8 & S8+ Cross Device Development] newtamax:
Hi all , Can semi-stock support new rom QI5？Thanks
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
you mean the latest stock rom? yes, it does. I'm using the latest system on my sm-g9500 with the semi-stock kernel right now
[Samsung Galaxy S8 & S8+ Cross Device Development] newtamax:
Thanks :)
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
On your battery stats is system using a lot of battery?
[Samsung Galaxy S8 & S8+ Cross Device Development] 012345678:
My 9550 repeatly shows Smart Manager CPU Overload by a Program if i use Cameron. Can i resolve it?
[Samsung Galaxy S8 & S8+ Cross Device Development] travis82:
I was lookin at getting the 128gb model too at a second hand mobile store. You all still having issues with a kernel rom? I would think the only difference is partition sizes that twrp uses. I recall on s7 edge that I had to disable a lot of security stuff in the kernel to get it to function correctly and do a bit of ramdisk edits also. It's not to difficult just tedious.
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
So it's not so much a kernel issue as it is I think the source issue since it's a honkong rom with chn kernel so the battery is terrible with system taking up a massive amount but I've been focusing on LOS far more than any kernel stuff ATM.

---------- Post added at 12:23 AM ---------- Previous post was at 12:21 AM ----------

You work with Sean! I knew I saw your name before XD Sean's actually been helping me with the source for this for Los :3 I have vendor up and everything except inits and msm8998.mk and a few other things before building but most of the foundation is done!
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
no, I think it's same as before.
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
See on g9550 it just wrecked my system with system os of over 30% so he must of done something else in the patch of the fact that I'm using China open based kernel source and maybe he kept HK local or something
[Samsung Galaxy S8 & S8+ Cross Device Development] travis82:
Where is your device tree? Im fighting a crashy ril and audio card not wanting to be brought up but external codecs are seen on C9 maybe ill take a break from C9 and look at S8+ G9550.
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
GitHub.com/samsung-msm8998 I think
[Samsung Galaxy S8 & S8+ Cross Device Development] travis82:
Good start, device.mk needs to be filled out and your vendor tree do all those files pull when you run the extract script? Camera needs chromatix and a lot more files. Config files are missing for sensors and what not. You could probably use ril-caf to bring up ril. Just what I noticed at first glance.
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
Another weird thing, with semi-stock kernel, they're 4 extra icons,

Knox II Settings

Knox Settings

Phone

Messages

In other words, I got two 'phone' and two 'messages' icons.
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
GitHub.com/samsung-msm8998

---------- Post added at 03:04 PM ---------- Previous post was at 03:01 PM ----------

Yeah kinda left out camera and RIL just for times sake. Just kinda got burned out for a little while using all my free time towards it but I'ma start up here again soon. I highly recommend the device I love mine just need to be careful with what bootloader you flash because HK bootloader will randomly FRP lock you at like any moment and make you reset while open CHN wont.
[Samsung Galaxy S8 & S8+ Cross Device Development] travis82:
Sounds like a config issue in kernel or a .prop file. Also did you run crom.apk to unlock the bootloader? China Asia models you gotta do it. Search it on galaxy apps store and you can download it. HK FW and BL should never just random frp you out. I've had S7 Edge C9 Pro and even used a note 8 here and never ever had this happen on TGY firmwares. Your device tree is looking decent but may I suggest you check out other msm8998 devices and you can base your tree off of them for the most part. Ramdisk might give you a bit of trouble and dont forget to add in a logcat entry to post-data-fs and run logcat as a service in case when you build an ENG build you cant get access to adb. Or in MSM8998.mk you can add this in if you dont wanna add it in ramdisk

ifeq ($(TARGET_BUILD_VARIANT),eng)

# Disable ADB authentication

ADDITIONAL_DEFAULT_PROPERTIES += ro.adb.secure=0

endif

should help you out a bit. Hope you get it booting soon might persuade me to go get one :) Also make sure your fstab is right and that you remove the selinux lables on firmware and firmware-modem after you add in androidboot.selinux=permissive to the end of BOARD_KERNEL_CMDLINE or it will not load the partitions with selinux permissive.

---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------

Here are c9's ril files should be almost the same for s8+

# Radio

bin/netmgrd

bin/qmuxd

bin/radish

bin/rmt_storage

bin/tftp_server

bin/rild

etc/data/dsi_config.xml

etc/data/netmgr_config.xml

etc/data/qmi_config.xml

lib/libprotobuf-cpp-full.so

lib/libprotobuf-cpp-lite.so

lib/libril.so

lib/libreference-ril.so

lib/librmnetctl.so

lib/libsecnativefeature.so

lib/libsec-ril.so

lib/libsec-ril-dsds.so

lib/libsecril-client.so

lib/librilutils.so

lib64/libprotobuf-cpp-full.so

lib64/libprotobuf-cpp-lite.so

lib64/libreference-ril.so

lib64/libril.so

lib64/libsecnativefeature.so

lib64/libsec-ril.so

lib64/libsec-ril-dsds.so

lib64/libsecril-client.so

lib64/librilutils.so

lib64/librmnetctl.so

vendor/bin/qti

vendor/lib/libconfigdb.so

vendor/lib/libmdmdetect.so

vendor/lib/libnetmgr.so

vendor/lib/libril-qcril-hook-oem.so

vendor/lib/libxml.so

vendor/lib64/libconfigdb.so

vendor/lib64/libmdmdetect.so

vendor/lib64/libnetmgr.so

vendor/lib64/libqcmaputils.so

vendor/lib64/libril-qcril-hook-oem.so

vendor/lib64/libxml.so

But I suggest you try caf first. Some are not ril files I know I just never got around to making it pretty yet.

Also this discussion should be moved to a new thread so we dont mess up Jesecs thread kind of rude of us isn't it?
[Samsung Galaxy S8 & S8+ Cross Device Development] Cameron581:
Jesec disappeared months ago, the thread should actually be closed just been too lazy to call a mod because the g9550 kernel listed soft bricks the device.
[Samsung Galaxy S8 & S8+ Cross Device Development] travis82:
Hmm maybe I'll make a kernel for s8 + if you wanna test message me I'll see what I can do this week.
[Samsung Galaxy S8 & S8+ Cross Device Development] newtamax:
The latest stock rom is update to G9500CHC1AQJ8 ,is it ok to flash semi stock kernel？Thanks
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
Yes, it's still working on my phone with this new update, everything looks the same as before.
[Samsung Galaxy S8 & S8+ Cross Device Development] newtamax:
Thanks
[Samsung Galaxy S8 & S8+ Cross Device Development] newtamax:
I encountered a problem, after flash the latest firmware with semi-stock, the phone memory only have 16G, why?
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
I didn't get this problem...

Did you do a 'fresh' flash? (backup data - clear all data - flash - restore)

maybe some of your files still remain in some hidden places.
[Samsung Galaxy S8 & S8+ Cross Device Development] newtamax:
I solved the problem. When I flash stock rom for the first time, I get a DM error, I search google for a answer, someone say I can only flash bl and ap leave csc etc blank, I do it so I get the 16G error. Then I go into TWRP clean all data, solve the probelm. Thank you and sorry for my poor English.:laugh:
[Samsung Galaxy S8 & S8+ Cross Device Development] torhect:
Which is the latest version of jessec kernel? Im on sm-g955FD international s8+ .....
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
this thread is talking about the semi-stock kernel for snapdragon. for exynos(international) variants, you should see this

https://xdaforums.com/galaxy-s8/sam...rnel-jesse-s-kernel-galaxy-s8-exynos-t3603521
[Samsung Galaxy S8 & S8+ Cross Device Development] torhect:
Is this a closed thread?
[Samsung Galaxy S8 & S8+ Cross Device Development] kjames2001:
Not really, but it's very inactive due to lack of development.
[Samsung Galaxy S8 & S8+ Cross Device Development] torhect:
I would love to see oreo version of this kernel
[Samsung Galaxy S8 & S8+ Cross Device Development] RQYP:
Hello everyone

I have found a Chinese forum which has multiple threads on G9550 and G9500 root/custom roms. Please examine.

http://www.tomatolei.com/forum-s8-1.html

http://www.tomatolei.com/thread-137973-1-1.html
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
It seems that they compiled a newer kernel from source, but I think it's still using jesec's code. The rest modifications are only applied on /system/build.prop.

BTW, what does 'examine' mean? :D
[Samsung Galaxy S8 & S8+ Cross Device Development] iamnotexisting:
Probably not until Snapdragon Oreo is rooted.
[Samsung Galaxy S8 & S8+ Cross Device Development] torhect:
but I thought you had an exynos version! there is an exynos version of this kernel for nougat!!
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
I just wonder that if samsung has released the kernel source for oreo...
[Samsung Galaxy S8 & S8+ Cross Device Development] eddie1.tw:
I follow the steps, reset my SM-G9550, flash AQG6 OTA (didn't flash BL, otherwise "sw rev check fail, abl fused 2 binary 1" error message appears), flash TWRP, flash the kernel (I do not know What is your kernel, so I flash no-verify-opt-encrypt-6.0) and magisk v16.

After rebooting, the screen displays an "Authentication failed," error message, and it will not restart automatically after several reboots.

Can someone tell me where am I doing wrong?

Thanks and many greatful

picture here :

imgur.com/a/qPfXEN1
[Samsung Galaxy S8 & S8+ Cross Device Development] ygecesefa:
Hey how did yoıu solved The issue.Same I am trying for note 8 HK variant.
[Samsung Galaxy S8 & S8+ Cross Device Development] xdauser'17:
Haven't found any solutions yet... I've stopped the pointless trying for now, cuz it doesn't seem to work without modifications to the code or the Makefile, I think.

Right now, there're two cases that may be helpful for me - either if I can find someway to make a patch to the linux kernel to let it save the boot logs into a file, so it will show what the hell is going on; or someone may send me a boot.img for the mainland variant, which is compiled in the same way that worked for HK variant, then I will check if it'll actually work and maybe can get some new clues?

As always, ANY help would be VERY appreciated. :)
[Samsung Galaxy S8 & S8+ Cross Device Development] ygecesefa:
there are two devs tomtolei and aurora rom's devs they are compiling their own kernel from the source of these snaodragon devices.There is some kind of security or signature s check feature on the codes it prevent to boot I think .

I contacted lots of dev but they dont want to help.So I didnt contact tomatolei because he have premium rom so I dont think so If he want to help.Do you have telegram or smthg?I am keeping resaearch lets work together.My custom rom work stopped beacuse of this custom orginal kernel issue.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DragonFire1024:
Would this be the famous AppOps? See attachments. If so, should I not be able to access it through an emulator?

u0_a31@giza:/system/bin $ appops
usage: appops set [--user <USER_ID>] <PACKAGE> <OP> <MODE>
appops get [--user <USER_ID>] <PACKAGE> [<OP>]
appops reset [--user <USER_ID>] [<PACKAGE>]
<PACKAGE> an Android package name.
<OP> an AppOps operation.
<MODE> one of allow, ignore, deny, or default
<USER_ID> the user id under which the package is installed. If --user is not specified, the current user is assumed.
u0_a31@giza:/system/bin $
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DragonFire1024:
Oops wrong attachment
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DragonFire1024:
Also this: all from /system/bin

# Script to start "appwidget" on the device, which has a very rudimentary shell.
base=/system
export CLASSPATH=$base/framework/appops.jar
exec app_process $base/bin com.android.commands.appops.AppOpsCommand "$@"
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] DragonFire1024:
/system/bin/appwidget:

# Script to start "appwidget" on the device, which has a very rudimentary shell.
base=/system
export CLASSPATH=$base/framework/appwidget.jar
exec app_process $base/bin com.android.commands.appwidget.AppWidget "$@"

/system/bin/appops:

# Script to start "appwidget" on the device, which has a very rudimentary shell.
base=/system
export CLASSPATH=$base/framework/appops.jar
exec app_process $base/bin com.android.commands.appops.AppOpsCommand "$@"

Terminal Emulator:

u0_a31@giza:/ $ appops
usage: appops set [--user <USER_ID>] <PACKAGE> <OP> <MODE>
appops get [--user <USER_ID>] <PACKAGE> [<OP>]
appops reset [--user <USER_ID>] [<PACKAGE>]
<PACKAGE> an Android package name.
<OP> an AppOps operation.
<MODE> one of allow, ignore, deny, or default
<USER_ID> the user id under which the package is installed. If --user is not
specified, the current user is assumed.
u0_a31@giza:/ $

I tried to run the scripts, which appear to work, but no widget appears and emulator closes after I run the widget script. I managed to get a minimized screen cap, posted below.
[P8lite Themes and Apps] hbilalshah:
Hello...

I want to know how to customize the heads up notification style and color in EMUI by building an hwt theme.???

Any help would be appreciated.
[P8lite Themes and Apps] TheOldMan:
Try "EMUI Theme Editor" from Playstore. Maybe this helps you.

Greetings from Germany :D
[Miscellaneous Android Development] K001droid:
Reserved

Guide by SuperModerator at CPForums : http://www.coolpadforums.com/forum.php?mod=viewthread&tid=24998

Video Tutorial ( Thanks to Karthik SB ) :

https://youtu.be/Z99LYY30CK8

F.A.Q

Q: I tried the method, didn't work.

A: Well try again, it works.

Q: I bricked my phone, it is stuck at the logo.

A: Flash Stock Firmware via Fastboot or Flash Tool.

Q: Is the bootloader unlocked?

A: No, As on 19th November 2017 - Bootloader is still locked and no way to open it.

Q: Will i still get warranty?

A: Yes only if you flash Stock ROM via Flash tool again.

Coolpad Note 5 Telegram Group :

https://telegram.me/coolpadnote5sd
[Miscellaneous Android Development] tigerking1:
Good work bro.

TeamZero rocks
[Miscellaneous Android Development] sk99:
At last some dev program initiated ...thanks dev [MENTION=7174278]kuberrocks96[/MENTION]
[Miscellaneous Android Development] narenderrao:
Please List the total commands properly.

I am unable to find the commands to enter.

In cmd when i entered the command "adb reboot" it is showing that there is no recognition of adb ....is it the drivers problem ?
[Miscellaneous Android Development] K001droid:
Install Driver properly
[Miscellaneous Android Development] shail_1005:
U have done a great job but the only request to u is please post a video tutorial of rooting coolpad note 5 @ kuberrocks96
[Miscellaneous Android Development] sk99:
Did Anybody try to root with this above procedure ?
[Miscellaneous Android Development] icebreaker18:
where is su zip file?

where is the su zip file to flash from twrp

---------- Post added at 10:37 AM ---------- Previous post was at 10:27 AM ----------

after doing twrp, my phone is stuck at the power on screen. i think it is bricked. please help
[Miscellaneous Android Development] icebreaker18:
please help

My phone is totally bricked and can only get into twrp recovery mode. it cannot even open bootloader so that i can flash custom firmware. i am doomed