yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Matt07211:
I got a few questions to ask ;)

How are you flashing the twrp image? Is it via odin and are you using the newest twrp build (3.0.2-0)

I am willing to work, read up and compile anything necessary to get the recovery working on the device, but due to it being my only phone I cant afford to mess around with it much, so are you willing to try out stuff for me e.g. flashing a custom kernel with the ability to toggle selinux modes?

I believe a fix for the "recovery is not seandroid enforcing" can be fixed if I recompile the kernel with a flag set to false (It a custom flag from samsung that disallows the changing of selinux modes, "EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=false") allowing for the twrp recovery to change "setenforce 1" to a "0" allowing the recovery to run in permissive mode. http://graemehill.ca/compiling-permissive-android-kernel/ , https://su.chainfire.eu/#selinux , https://source.android.com/security/selinux/

If you are willing to help test for me I would really appreciate it ;) And once I get the recovery working I am gonna root my phone by flashing the SuperSu.zip.
[General Questions and Answers] VolterPL:
Yes, I am using the newest Odin and the newest TWRP, downloaded from TWRP site.

I would like to help you if, and only if, there's absolutely no chance of bricking my phone as I've bought it recently for quite a lot (at least for me). I don't care about warranty, as well as triggering KNOX.
[General Questions and Answers] Matt07211:
I can't say that their is not a chance for a brick, but all I am changing is one single flag from "true" to "flase". Their is always a chance at bricking your phone when working with root, tons, custom recovery and kernels as you are messing with the system, but as long as you have either a backup (nandroid) or now how to fix it (flashing stock firmware), their is very little chance of screwing up, and if screwed up you will in almost all cases be able to fix the problem

But yea if the device stuffs up some how e.g. unable to boot you would able to boot your phone into "download mode" and flash stock firmware, although losing you data e.g. apps,. Your phone would be back in a functional state.

Once I am able to get the recovery working properly (booting and running (in permissive mode)) I will root my phone, make a nandroid backup and then I am willing to start adding custom goveners to the kernel and would be willing to share/get help devloping the kernel in the future.

I might be able to provide the kernel later this week (internet limitations are the reason for a long wait) and will post instructions on how to flash the kernel, and how to flash stock firmware (for either you stuffed up and need to fix the phone, or for testing properly with everything at stock and then working the way up, kernel and then twrp)

So if you are willing, i would appreciate the help if given :)
[General Questions and Answers] yy1:
@ Matt07211 If you need a tester. here i am. But what i need is, a step by step for flashing with heimdall on linux mint 18 in easy english. mx phone is sm-g388f with 5.1.1
[General Questions and Answers] VolterPL:
Did as you said. I have flashed the stock 5.1.1 rom, ran it once, enabled USB debugging and flashed the newest TWRP, making sure it won't reboot automatically. Then, when I tried to run the recovery it doesn't boot into stock recovery. It doesn't boot at all. :D It just shows the starting screen (the "powered by android" thing) with "RECOVERY IS NOT SEANDROID ENFORCING" in red at the top.
[General Questions and Answers] Matt07211:
If your phone wont reboot at all do as follows:

Okay, to get the phone working, do as you did with twrp which is flash via odin. Boot into download mode and flash the correct firmware, https://samsung-firmware.org/model/SM-G388F/, related to your phone. For me that would be the New Zealand Version as that is where I had got the phone E.g. I would flash this firmware as it is the correct one for me, https://samsung-firmware.org/download/GALAXY Xcover 3/9c78/NZC/G388FXXU1BOK2/G388FNZC1BOK3/.

Once that is done you should have a functioning phone again.

If it is just the recovery that isnt booting then If you want to use it any time soon, just flash like above. But I guess that the kernel with the ability to change to permissive mode is needed. I am currently in the process of doing that. I tried compiling on my ubunutu 32-bit (hoping it would work, but didn't due to it needed to be done in a 64-bit enviroment), so know I created a Virtual Machine with Ubuntu 64-bit (Created it last night), but I need to download the development tools, and I wont be able to do that untill tomorrow due to my access to the internet.

But once I have a kernel that is able to change between selinux modes, the message "RECOVERY IS NOT SEANDROID ENFORCING" should hopefully not pop-up. But it would be best to start fresh. Without that error (so flash firmware and start from scratch), flash the kernel, boot into the OS to verify it works and then check settings to see if it is using the cutom kernel. Then flash twrp like before and then SuperSu.zip (My previous post) disable the "install-recovery.sh" script and flash twrp one more time due to it being reverted back to recovery. So all together it would be a fresh install of lollipop, with a custom kernel, twrp and root.

Thanks for trying [MENTION=7690994]VolterPL[/MENTION] I really do appreciate you doing this, and I hope you are able to get the phone back to a working state (If i read your message correctly). Will appreciate if you would still continue to help, but if you dont I would understand.
[General Questions and Answers] VolterPL:
I am gonna compile the kernel myself. My phone is working, it just doesn't boot into recovery. :D Installing Linux Mint in VirtualBox right now. :D

I only have one concern:

The latest version of my stock ROM (Poland open market [XEO]) is G388FXXU1BPC3, where the latest version of open source ROM is G388FXXU1BOK2, which means my desired ROM is 4 months younger. How do I know if the older modified kernel will work with my ROM?
[General Questions and Answers] Matt07211:
First to address your concern, I believe it should be fine, as the version of the kernel is the same as the source code (I believe), it doesn't hurt ti give it a try, if it doesn't work flash you firmware via odin. So download the source code, and have a read over this guide: http://graemehill.ca/compiling-permissive-android-kernel/ and all you need to change is the flag inside this "~/android/kernel/security/selinux/Makefile" file

EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=true

All you have to do is change true to false.

Also when following the above guide remember I phone is running a 64-bit chip so modify accordingly, and also our kernel config will be found in the 64-bit folder

E.g.

$ make ARCH=arm64 pxa1908_xcover3lte_eur_defconfig
$ make ARCH=arm64

Make sure to read the Kernel Readme and adapt accordingly

Prerequisites(The above guide will tell you how to setup most stuff):

Newest Android NDK

64-bit linux install

sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2

Might have to modify above to suit linux mint(I haven't used it before)

The kernel Config says to

and the android ndk comes with the 4.9 version so we have to download the 4.9 version as below

$ git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.8/

Hope these TID-BITS of info will help you compile your kernel, and if you are gonna share it online then remember to also release the source code to compile with the GNU licence that is with the linux kernel. I am gonna release my kernel later in the week so if you fail or aren't able to complete it properly then try mine, but good luck. PM me if you need more info or help
[General Questions and Answers] VolterPL:
I can't see the mentioned line in the Makefile.

All the contents:

I am sorry. It is somewhere deeper: /security/selinux/Makefile :D
[General Questions and Answers] Matt07211:
So you've extracted the source code, Now go into ":/security/selinux/Makefile" , it should be the 7th line down. [IMG="7th Line down"]http://i.stack.imgur.com/7J0sh.png[/IMG]

You are in the above directory (/security) Makefile, you will need to go into the selinux directory (/security/selinux

Now change

EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=true

to

EXTRA_CFLAGS += -DCONFIG_ALWAYS_ENFORCE=false
[General Questions and Answers] VolterPL:
I believe you've linked a wrong version of eabi toolchain, as arm-eabi is for arm, not arm64. For arm64 we should use the aarch64-linux-android-4.8 toolkit.

git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.8
[General Questions and Answers] Matt07211:
OPs my fault, I had wasn't pay attebntion it should be https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.8/ like you said, I will edit my above post to be correct. Thanks for spotting that.
[General Questions and Answers] VolterPL:
It's making something. I am getting some make warnings, but no errors. Should I care?
[General Questions and Answers] Matt07211:
Yes, It is good practice to figure out what is making the errors.

Run the compile with only 1 core, so you are able to see what the error is when it happens and then work from their.

You doing this on a 64-bit machine?? It cannot be on 32-bit

I have update the link of the toolchain to the correct version.

Can you tell me what the errors are if you can, also google is your friend ;)
[General Questions and Answers] VolterPL:
The warnings are concerning uninitialised variables, nothing severe. :D
[General Questions and Answers] Matt07211:
Oh okay, anyway try the kernel once done, what is your progress on compiling your own kernel. Google them errors if the kernel doesn't work ;)

This mentions stuff about errors near the bottom, http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source
[General Questions and Answers] VolterPL:
I've got the kernel Image. :3
[General Questions and Answers] Matt07211:
Almost their, are you following this guide, http://graemehill.ca/compiling-permissive-android-kernel/ ?? As it has a section below creation of the kernel image creating it so you can flash via odin.

Edit: Have you flashed the kernel, if you haven't yet, start from scratch if "seandroid" error is showing (Install stock firmware) and then flash kernel, verify, install twrp, supersu, remove "install-recovery.sh" if recovery keeps getting replaced and flash twrp once more if removed the "install-recover.sh"
[General Questions and Answers] VolterPL:
Ok, I'm stuck now. I have the kernel image, but when I flash it (successfully) and try to boot it, it shows "KERNEL is not seandroid enforcing", so I can't boot to the system. I can successfully boot to the stock firmware. I can also flash the stock firmware to revert the error.
[General Questions and Answers] Matt07211:
Okay, let me reasearch this a little bit, will get back to you in a few hours as I have to get some stuff done. But hey we are making progress ;)
[General Questions and Answers] VolterPL:
I've found another approach to the problem.

We need TWRP 3.0.2 source code and then we'll be able to 'trick' Samsung bootloader into thinking the recovery IS seandroid enforcing, as seen here:

Lines 26 & 27 of bootimg.mk
[General Questions and Answers] Matt07211:
Okay, if you are willing to try it then have a go. https://github.com/TeamWin/android_device_samsung_xcover3ltexx?files=1 This the devices TWRP Recovery source code. Note it says Android 4.4 in the branch, you will have to probably build it under the Android 5.1.1 branch (https://github.com/omnirom/android_bootable_recovery/tree/android-5.1 ) with the info based off the old twrp branch. Have a good without trying your truck under the new branch and then if it doesnt work try it with the truck you mentioned
[General Questions and Answers] Matt07211:
[MENTION=7690994]VolterPL[/MENTION]

Am still searching this up, the notices like "Kernel/Recovery is not Seandroid Enforcing" will all ways show up unless signed by samsung, but as long as the desired things work then I will be happy, will post here when I find more info.
[General Questions and Answers] Matt07211:
[MENTION=7690994]VolterPL[/MENTION] This looks good, http://xdaforums.com/galaxy-note-10-2014/general/root-root-stock-kernel-t3240218/page1 gonna try this as well as manually unpacking the boot.img with a hex editor

Edit: Am having difficulties trying to manually unpack with hex editor, and when using an tool that splits he boot.img into the ramdisk and kernel their hex values are all 0, meaning they have no data and therefore when you have tried to flash the kernel back onto the device and it doesn't work is because there is nothing their to use.

So overall, the unpacking tools i have tried all zero out the data when looked at with a hex editor, therefore unable to boot when flashed. Having troubles trying to manually unpack boot.img, and the above link is a different way to achieve root without recompiling a kernel, only modifying the other file. And what toolchain are you using to compile the kernel, I am able to use the aarch64 4.9 toolchain that comes with the android ndk, but when trying to use the 4.8 toolchain (https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.8/) I get error at the begging saying unable to find the gcc compiler.

[MENTION=7690994]VolterPL[/MENTION]
[General Questions and Answers] Matt07211:
For Anyone interested I am implementing Chainfires Systemless root by hand, and will create a little script (push su.img to the device and other miscellaneous things) to get root functioning on the device once the modded boot.img is flashed. I almost have everything ready for testing by you guys, the only roadblock I am hitting is patching the sepolicy file. If anyone here has a 4.4+ device with selinux and has at least SuperSu 2.5+ installed, can you please PM me as this is the only thing I don't have and as such causing this to be delayed. Once I have a modded Sepolicy file, the systemless root should then be ready for testing.
[General Questions and Answers] AlinTecsan:
how i can root this device mine happens same what twrp need to install i try all of them
[Desire 816 Q&A, Help & Troubleshooting] NamanVishnoi12:
Hi,

I was trying to flash marshmallow ROM, but it softbricked my phone. now I can't go beyond bootloader and cwm recovery. Also, it shows a message that the phone is not rooted. What shall I do? I don't have a backup phone and it is urgent. Can somebody help?

I don't have twrp installed to restore a backup.

Is it possible that if somebody gives me a twrp img of stock marshmallow or lollipop , i can flash via fastboot?

Thanks in advance

Naman
[Desire 816 Q&A, Help & Troubleshooting] Roberto Nigel:
this is TWRP img flash it via fastboot

https://dl.twrp.me/a5/twrp-3.0.2-0-a5.img

then restore this TWRP backup .. note that its MM so you need to be updated to LP b4 to avoid wifi problems

http://xdaforums.com/desire-816/general/twrp-backup-desire-816-a5dwg-dual-sim-t3335771
[Desire 816 Q&A, Help & Troubleshooting] NamanVishnoi12:
Hi,

I am getting signature fail error. I tried flashing official RUU also but getting same error (12 signature verify fail). Also, my bootloader is relocked now:(

Naman
[Samsung Galaxy Star] BatDroid:
Here's a list of all BLOATWARES/unwanted apps that u don't need and eating up ur ram/battery in background.

This post is only for GTS5282 cyanogenmod 11 users.

Just delete this BLOATWARES and install GREENIFY/AMPLIFY to save ur battery and ram.

Here's the list ---

*** updating ***

please wait.....

Basic Daydream

Browser

Calculator

Calendar

Camera 2(optional)

Cell broadcast

Cm home

Cm walpaper

Desk clock

Documents Ui

Download provider

Email

Exchange 2

Gallery 4

Gallery 2(quickpic instead)

Holo spiral walpaper

Html viewer

Live walpaper

Live walpaper picker

Lock clock

Magic Smoke

Noise field

Phase beam

photo phase

photo table

pico tts

print spooler

sound recorder

term

user dictionary

video editor

visualisation

wap push mgr

whispered push

privs---

calendar provider

cm account

cm updater

download provider

one time initiatializer

voice dialer

walpaper cropper

(HIT THANKS)
[Samsung Galaxy Star] bvrraju:
User dictionary is bloatwear????????
[Samsung Galaxy Star] hamzaeid:
thanks pro. but when i try to remove sound recorder the warring me that i gonna delete a core app and that's gonna make the room un stable so should i deleted or what :good:
[Samsung Galaxy Star] BatDroid:
Do u think sound recorder is a core app?

u can delete all I listed here :)
[Samsung Galaxy Star] hamzaeid:
ask system app remover :D
[Samsung Galaxy Star] BatDroid:
I kill them with root explorer.

quickest way
[Android Apps and Games] jingillani:
Content removed
[Android Apps and Games] Heisenberg:
The promotion/discussion or warez and piracy are strictly forbidden on XDA, thread closed.
[XDA Assist] gouster3:
Hi, i have nokia 225, and i wanted to update my FW. I used official Nokia Software Recovery Tool, but i had bad cable and flash failed.

Product Support Tool seems only way to fix it. But i become this error:

Anyone know how to solve please?
[XDA Assist] GuestK0087:
Greetings,

Please read the sticky threads for this section. XDA Assist is not a help desk. Our purpose here is to guide new members to the proper section or to an existing thread for their issue. Senior members are expected to know how to search and find the correct section to ask for help.

Thanks.

Thread closed.
[8525, TyTN, MDA Vario II, JasJam General] Jc61990:
is there an app or a cab file that will switch the X on my device to close the running app and not minimize it? im using an 8525 and WM5
[8525, TyTN, MDA Vario II, JasJam General] AwJm:
http://www.freewarepocketpc.net/ppc-download-htc-x-button-v1-50.html
[8525, TyTN, MDA Vario II, JasJam General] DaddyGoFast:
Also, google Vbar. It is TINY and it works great. It also shows battery level right next to the X along with Memory consumption. Very cool.
[8525, TyTN, MDA Vario II, JasJam General] Jc61990:
sweet thx a lot
[Galaxy Note5 Android Development] ravian29:
ChangeLogs

8/05/2016 - v7.1

IOIO V7.1 Changes

6/05/2016 - v7

IOIO V7 Changes

24/04/2016 - v6

IOIO V6 Changes

​
[Galaxy Note5 Android Development] ravian29:
Downloads

​

Please do not make mirrors of any of the files

IOIO V7.1

IOIO V6

Stock PD2 Firmware

Bootloader(Taiwan)

Bootloader(Malaysian)

Modem(Taiwan)

Modem(Malaysian)

n9208 Kernel

​
[Galaxy Note5 Android Development] ravian29:
MODS

​

Please do not make mirrors of any of the files

3MINIT BATTERY

CSC FOR IOIO

FIXES

TIME CRASH FIX

HOME BUTTON CALL ATTEND FIX

​
[Galaxy Note5 Android Development] ly_trong_tri:
[emoji1] [emoji1] [emoji1] [emoji1]

Gửi từ SM-N920S của tôi bằng cách sử dụng Tapatalk
[Galaxy Note5 Android Development] cornelito:
Awesome job dude ! Have been waiting for MM so long now....... Downloading now and will be flashing this evening. Cross the fingers everything will go well.
[Galaxy Note5 Android Development] thereassaad:
Welcome back brotha ,
[Galaxy Note5 Android Development] ravian29:
Thanks bro, trying last time. I wish now things go fine
[Galaxy Note5 Android Development] moonspirit:
included kernel
[Galaxy Note5 Android Development] sniperyong:
is this safe for me?

i have 9208 from Philippines and carrier lock..

im on 5.1.1 rooted stock..

---------- Post added at 11:03 AM ---------- Previous post was at 10:40 AM ----------

downloading.. i will try this after 3 hours due to slow download speed
[Galaxy Note5 Android Development] ravian29:
yes stock kernel is included
[Galaxy Note5 Android Development] anmolkakkar:
Hi [MENTION=3545435]ravian29[/MENTION],

Thanks a lot for your hard work with this ROM. As i also am a user of N9208 Taiwan variant, only a few option pertain for ROMs and Kernels and having you around we dont have to worry ;)

Wanted to check with you that since I updated my N9208 yesterday to MM, how should I go about Rooting it and installing TWRP without the bootloop (unlike 5.1.1 where we needed to flash sboot.bin as well)

Also, i think you would need to rectify point #5 in "How to Install" of your Original Post to not wipe internal storage as it will also delete the iOiO ROM copied in the internal storage and not everyone will know how to adb push it (if you know what i mean ;) )

The stock Kernel seem to have addressed the Deep Sleep issue for our MM N9208 i believe coz I have my Knox tripped and I am running stock kernel with no issues till now (not jinxing it :p )
[Galaxy Note5 Android Development] ravian29:
if you are able to flash sboot (bootloader) via odin then i hope everything will work fine
[Galaxy Note5 Android Development] ravian29:
thanks bro for your feedback and helping hand. Bro what i did to get root and twrp is

1. flashed twrp straight after installing rom

2. flashed supersu 2.71 version

and after that, i did not get any problem with both. About #5 lol yes you are right, i always use otg so thats why i believed everyone else will be using usb otg lol i will modify my post. Yes bro i am also using stock kernel and so far i did not even see any problem with stock kernel, bettery life is also better than custom kernel. I only use custom kernel only to get higher sounds but now i am thinking to stick to stock kernel.
[Galaxy Note5 Android Development] jim2sad:
cant flash bootloader and modem .. failed =[ n9208 from malaysia
[Galaxy Note5 Android Development] ravian29:
Malaysian version have different bootloader. You need to wait for Samsung to release mm for Malaysian variant
[Galaxy Note5 Android Development] jim2sad:
noted. will wait again.

thanks for your hard work =]
[Galaxy Note5 Android Development] :
Thread cleaned.

Please be respectful at all times.

:good:
[Galaxy Note5 Android Development] anmolkakkar:
Hi [MENTION=3545435]ravian29[/MENTION],

Bro, is there any way of making the Kernel as Permissive for Viper/MaxxAudio to work in your ROM. I really like your ROM and want to be on Stock kernel only. Was just hoping if that was possible?

Thanks in advance. :)
[Galaxy Note5 Android Development] pratik_193:
[MENTION=3545435]ravian29[/MENTION] - if i am not mistaken, can v6 be flashed on non taiwan variant of 9208? like indian variant ? Since indian variant is still on Lolipop..
[Galaxy Note5 Android Development] anmolkakkar:
I guess not since you will need to install the bootloader and modem before proceeding to MM and those two (per the OP) are Taiwan N9208 specific only. Try flashing them through ODIN once and see if you succeed/fail. If succeeded (Luckily?), then only you can flash this ROM.

Hope it brings more clarity! :good:
[Galaxy Note5 Android Development] ravian29:
bro i am not sure if there is indian n9208 version, in my knowledge there are only 2 n9208 versions Taiwan or Malaysian but i am not saying there can not be more, and bro without device and testing i can not tell you it will work or not. You can test to find out.
[Galaxy Note5 Android Development] ravian29:
Bro i never worked on kernel, i am not sure if its possible without modifying and recompiling the kernel. I will ask my dev community about it for more guidance.
[Galaxy Note5 Android Development] anmolkakkar:
Cool! Thanks

I will definitely wait for an update on this one since I love the audio output of my Note 5 with MaxxAudio and Viper4Android. Missing that sound after coming to MM.
[Galaxy Note5 Android Development] mafijas:
I have a Malasyan model.

I have a plan to try flash first old 5.1.1 from Taiwain and after a new 6.0.1.

Without success... :)
[Galaxy Note5 Android Development] ravian29:
today malaysian n9208 is also getting mm ota update, i will recommend to hold on to get it
[Galaxy Note5 Android Development] ismani83:
Lets wait until Ravian release it for N9208 Malaysian Variant . Thanks Ravian
[Galaxy Note5 Android Development] smalldroid:
Firmware 6.0.1 for N9208 TW is ready for downloading here

https://samsung-firmware.org/model/SM-N9208/