yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Matt07211:
Thanks for that, I will be sure to link to one of the beginging post with credit to you. I am assuming you pulled that off your device while it's rooted, if so can you please confirm the way the value edition was rooted. Since twrp for the value edition only got realeased a week ago, and I don't have the value editon I have been unable to verify if it works or if flashing SuperSu worked as well. I am unable to try twrp on the normal edition as the 2 different devices have didfferent boards inside, witht the normal using Marvell Amda pxa1908 and the value editon using an exynos variant.
[Miscellaneous Android Development] Matt07211:
Status Update: An able to boot a custom boot.img with modifications to the ramdisk (especially defult.prop). Now I have hit another road block, that is Samsung's anti-root feature is turned on the stock kernel. Simple fix, compile the kernel with it switched off, will post back here in a few hours with the results :)
[Miscellaneous Android Development] Matt07211:
Cool thanks for the verification and I have aready includes the orignal pit file you posted, onto one of the top posts of this thread, I will just have to compare the differences between the 2 files tomorrow as the both have didfferent sha1sums.

Now the only device we don't have root on is the normal version running lollipop. I can successfully boot an custom boot.img thanks to the work of [MENTION=7770482]akuhak[/MENTION] in modifying the degas umkbootimg tool to suit our phones. I am able to boot Up with a modfied ramdisk that has the necessary changes for and to run as root (like ro.secure, debuggable etc.) But know another road block has come up, due to Samsung's anti-root features being enable I am unable to use "adb root" as it does not allow any unprivlaged process to set it's suid to be root. This means I have to recompile the kernel with this setting turned off. I have tried boot.img a custom kernel earlier today, but that didn't work. And with my exams coming up in a couple of days I really can't do much for the device for a little while. But basically we are half way to attaining root on the lollipop version.
[Miscellaneous Android Development] akuhak:
can you share your modified ramdisk?
[Miscellaneous Android Development] Matt07211:
My modified ramdisk is attached at the bottom. I have already incorporated SuperSu (systemless), patched the sepolicy file (read the How-To SuperSu website for what patchs that where applied) and as well as the normal defult.prop edits, as in my above post we only have (I hope it's the last roadblock) samsungs anti-root is enabled in stock kernel. To see for your self, grab the "extract-ikconfig" script from yhe kernel sources and run it against your stock boot.img outputting it's contents to a .txt file and diff it against our defconfig or .config you will get this output below

diff ikconfig-extracted.txt .config

264,270c264,265
< CONFIG_SAMSUNG_PRODUCT_SHIP=y
< CONFIG_SEC_TIMA=y
< CONFIG_TIMA_LKMAUTH=y
< CONFIG_TIMA_PKM=y
< CONFIG_TIMA_LKMAUTH_CODE_PROT=y
< CONFIG_TIMA_UEVENT=y
< CONFIG_TIMA_LOG=y
---
> # CONFIG_SAMSUNG_PRODUCT_SHIP is not set
> # CONFIG_SEC_TIMA is not set
2124a2120
> # CONFIG_GEN_PANEL_TUNING is not set
3393,3396c3389
< CONFIG_SEC_RESTRICT_ROOTING=y
< CONFIG_SEC_RESTRICT_SETUID=y
< CONFIG_SEC_RESTRICT_FORK=y
< CONFIG_SEC_RESTRICT_ROOTING_LOG=y
---
> # CONFIG_SEC_RESTRICT_ROOTING is not set

Are you able to boot a custom boot.img with a custom ramdisk [MENTION=7770482]akuhak[/MENTION] , Cause I can but when I tried with a custom kernel as well, the phone went into a boot loop. Enjoy looking through the modifications I have done with the ramdisk. :eek:

Keep in mind that I have done the necessary modifications needed for sysyemless root in the ramdisk, we are still getting block by the kernel and it's (samsungs) anti-root feature which doesn't allow processes to set their suid to root. If you compile the kernel and with this flag disabled and you can get it to boot, tell me. To verify, you can type "adb shell suid" and you can we it's running as a normal user, if you then type "adb root", you will then be running as root and you can verify this by using the same suid command, but this time it will be running as root with the id as "0".

If you get the shell as root, tell me, I can give you the su.img, you push it to your device, and upon reboot, it will be mounted and you should have root. If it works, then we can realease it for the users.

Tl; DR compile kernel with anti-root disabled, if it boots tell me ; )
[Miscellaneous Android Development] akuhak:
Im stopping post info here cause I cant compile custom kernel in my 32bit machine.

But I have some interesting things to post.

First of all I still has knox 0x0 ))) After flashing tons of recoveries still officiwl. Funny thing.

I was succesfully modified grand prime ve TWRP recovery with xcover stock kernel and now has twrp onboard. Of course without root but its funny to see its working ))

And still knox 0x0
[Miscellaneous Android Development] Matt07211:
First, I bloody tripped Knox when flashing a boot.img and the message "SEANDROIDENFORCING" showed up in the first boot, so your lucky, but I belive your tool repack the boot.img properly so as not to trip Knox (I belive)

Secondly, I also had ubuntu 32-bit as a dual boot, but that didn't work, so I had to go to a 64but computer and use virtual box.

Third, it's cool you've got a different version of TWRP going meaning we can boot a custom recovery. But I would recommend against it for using its functions if it was designed for a different phone, reasons include that it might have different paths, meaning backup/restore might not work properly, or you could wipe the wrong thing due to it having the wrong paths etc. But it's a great proof of concept. We should propberly download the twrp source for 5.1.1 (I am gonna downlod the small version (just the stuff necessary for TWRP not the whole OMNi rom source code)when I have access to WiFi and after my exams (not my mobile data) which i believe you should be able to do all on a 32bit computer if your willing to try, if not I will :)
[Miscellaneous Android Development] kniederberger:
Well done guys. I just tried this method on a XCover3 Value Edition SM-G389F with Marshmallow 6.0.1 and it appears to have worked correctly. There were some extra steps that I had to do to get past the FRP lock on the download screen though and this might be of use to other users.

If the download screen shows FRP locked on it then the TWRP install is likely to fail. To clear it I had to delete my Google account from Accounts screen in settings and then for some reason you can't activate the download screen with Vol down + Home + Power for about an hour. So after an hour had passed I was able to start in download mode and then followed the rest of the steps in post 1 to root the phone.

Now I haven't recreated my Google account on the phone yet and would like to ask @Heledir and Matt if I am likely to encounter any problems with the phone FRP locking me out if I do?
[Miscellaneous Android Development] Matt07211:
You should be fine, once you modify the device in any way, that security feature will turn off and won't activate unless you've gone back completely to stock (flash stock firmware).

Read more here: http://m.androidcentral.com/factory-reset-protection-what-you-need-know

So yea you should be fine to log back into the Google account.

Since I didn't have a MM device I hadn't realised that it was a problem, and Heledir had made no mention of FRP. I have updated OP to include the info. I'm glad you got it working. If your trying to get Viper4Android (Viper4Audio) but it ain't working, tell me I've found a fix that I want to test, I believe it works as it patchs one rule at boot. Just since lollipop root doesn't work as of yet (why is it so much effort...) i have had a chance to verify it works.

===== [MENTION=7770482]akuhak[/MENTION] I have an stderr.log of the kernel compile process, since you seem to be proficient in "C" maybe your able to help debug and fix this errors showing up in the build process. Even if you say yes or no, I still plan to (other then just compile the stock kernel) to fix up and add features to it, this will require me to learn "C", but it may be a slightly easier if we use your knowledge of the language. All I am offering is an alternative for you since your unable to compile it on a 32-bit computer.
[Miscellaneous Android Development] akuhak:
compile it with

https://bitbucket.org/UBERTC/aarch64-linux-android-4.9-kernel

And you get no errors :)
[Miscellaneous Android Development] Matt07211:
Okay will give this a try later when I had more internet access.

The errors that are produced are coming from aarch64 4.9 that comes with android NDK, which is a x86_64 version which successfully compiles.

The make file specifies using the aarch64 4.8 that is x86, but when trying to use that version I keep getting "Exec format error" for which I'm tried installing the i386 libs, but to no avail will it work. And I am having trouble trying to locat the 4.8 x86_64 version.

The stderr logs I mentioned are attached to the bottom of this post.

What are your thoughts on this?
[Miscellaneous Android Development] kniederberger:
Hey guys, a word of warning on the XCover 3 Value Edition with Android 6.0.1 Marshmallow installed. After rooting the phone I then reinstalled my Google account. Unfortunately when I powered off the phone and tried powering it back on I got the dreaded "Custom Binary Blocked by FRP" message and the phone wouldn't boot. I had to do an emergency recovery with Smart Switch to get it going again and now it is no longer rooted. It also reinitialized the phone completely.

So it looks as though there are still some issues to by passing FRP on this phone. Has anyone successfully got it working?
[Miscellaneous Android Development] Matt07211:
I don't have the Value Edition of this phone, so I haven't had the need to look into FRP extensively (only have had a quick read up about it), so give me a couple of days to have a look at it (sorry I've got 2 exams in the next few days so can't spend much time on this.) and see what I can do about it.

Are you able to re-root and pull the boot.img off the phone and post it onto here for me to examine, please.

Sorry about you losing all the data on your phone, hopefully this should be a quick fix. Thanks for posting it here, this allows us to fix the problem.

Edit: [MENTION=7794695]kniederberger[/MENTION]

I belive this may have been a simple oversight.

- Did you have "OEM Unlock" enabled before flashing anything. (Note: Lollipop does not have this setting, so I am no sure if it's there in Marshmallow version of this phone)

If OEM Unlock is it a setting then can you provided me with some more info:

- USB Debugging enables. Also verifying it also worked.

- Did you reboot a few time after flashing twrp without the error showing.

- After flashing SuperSu, without a Google account signed in, were you able to reboot a few times succesfully?

- When you originally tried flashing twrp with your Google account signed in, did you have encryption enabled or some sort of lockscreen protection (pin/password protected)

- what does download mode say when your logged into Google account as well as when your logged out (any mention of FRP on either)

- Stock recovery, what happens when you select reboot to bootloader.

- was it systemless (I belive so) or system root? (Its alright if you don't know)

If your unable/or don't know the answers to any of the above just mention it. This is useful info in helping solve the problem.
[Miscellaneous Android Development] kniederberger:
Hey Matt, your exams are more important than this so don't avoid studying by looking into this (unless you're looking for creative avoidance ;) ). I can wait and am a little bit hesitant about trying this again just now anyway.

In answer to your questions:

1.) I didn't have OEM unlock enabled. This is an option in the Developer Options screen in Marshmallow. I have seen it mentioned in a few posts when I was recovering my phone earlier.

2.) I don't think I had USB debugging enabled but I do use this option quite a bit for adb and Android development.

3.) Yeah I did reboot a few times after flashing twrp and SuperSu and it restarted okay, without the Google account on it.

4.) When I originally tried flashing, with Google account signed in, I only had swipe to unlock set and no other security or encryption.

5.) With Google logged on, the download screen has the text "FRP lock on" on it and the download of twrp fails because of it. When I deleted the Google account, the download screen has the text "FRP lock off" on it and the download of twrp is successful.

6.) I didn't try reboot to boot loader.

7.) Not sure about whether it was systemless or system root. I just copied the SuperSU file to internal memory and ran it from twrp.

I have just noticed that in the security settings there is a Device Administrators screen that has the option "Allow Android Device Manager to lock or erase a lost device" turned on. This could be something that probably needs turning off.

But mate, you should be focusing on your exams for now and good luck for them. This can wait and if I feel a bit adventurous again I might give it another go but not just now.....

Kevin.
[Miscellaneous Android Development] Matt07211:
It alright, I'm devoting my attention to my exams first, but I had typed this up as I was on the move (I wasn't actively revising at the time of typing the above post.).

Now;

1) The OEM Unlock is probably the reason why you weren't able to keep root while logged into the device (I'm 99.99% sure this was your problem). Basically it's there for people who want to mpdify their phone, with it basically there for the following meaning, "You'll take all responsibility to what happens to your device once you've enabled this option, device security is know in your hands"

*) All the other info sounds alright

7) SuperSu will defult to Sysyemless on 6.0 and up (or 5.1.1 for samsung devices)

Also keep the android device manager enables (unless you've got a very good reason) as this let's you remotely lock,erase, track etc. From Google's android device manager, very useful if someone steals your phone.

Also when in twrp, it's good practice to back up your phone before flashing or messing around with it, saves you a lot of stress in the long run, and allows for easy installs.

Now, if your gonna try this agian, make sure OEM Unlock is enabled, then try flashing with your Google account logged in (just want to know if allows flakshing twrp without removal of Google login). If it stills says FRP with that option enable them your gonna probably have to redo what you previously did. (Basically tell me the outcome with the OEM Unlock option enabled).

Now off to revising for my exam (probably pop back onto here later in the day ;) ). Note: I haven't done any research into this yet as I waited for your response to my above post as well as exam revision.

~ Matt07211
[Miscellaneous Android Development] Matt07211:
Status Update: I have tried a handful of times in compiling a stock kernel and booting it, but with my exams I haven't really done much work on it. If anyone is currently trying to boot a custom kernel (don't think anyone else is but hey I'll still ask) and got it booting, PM me please.

What is needed to be achieved is moving the su.img to the /data partition, but adb needs root privileges, a stock kernel blocks it from achieving this, even with a modded ramdisk. So in all honesty, all I need to be able to do is move a file to the data partition, and one I have just thought about earlier today was using a script that is run at start up (boot) that moves the files and places the correct permissions, which I belive can be done with some small modifications to the ramdisk. This I am gonna try on the coming weekend :)

Feel free to ask any questions.

~ Matt07211
[Miscellaneous Android Development] Matt07211:
How stock do you need.

A stock kernel with the ramdisk patched for SuperSu. Just download the root package in OP and flash the boot.img that comes with it.

Completely and utterly stock.: Unpack the firmware.tar file or I can upload it.
[Miscellaneous Android Development] ash1970:
Yes, that I did, solved.

Wysłane z mojego SM-G388F przy użyciu Tapatalka
[Miscellaneous Android Development] IXgnas:
Download the firmware package from the list Matt provided, extract it, pack boot.img into a tar archive and flash.
[Miscellaneous Android Development] Matt07211:
Everyone, I would like to say that a ROM should be coming soon (Depending on how many errors are encountered on first build).

For anyone interested here is the source(s):

https://github.com/Matt07211/local_manifests

https://github.com/Matt07211/android_kernel_samsung_xcover3lte

https://github.com/Matt07211/android_device_samsung_xcover3lte

https://github.com/Matt07211/android_vendor_samsung_xcover3lte

I would just like to say this is my first time trying to port and build a ROM so I've tried my best to get everything correct, but with there being almost no guides on the internet it's rather difficult to do and understand without prior knowledge, so if there is any errors please tell me or create a pull request.

I just need to work through a TWRP build error, and then TWRP for the xcover3 lollipop should be built. Once that's built I know the sources work correctly and then the ROM can be built.

Things to do:

- Fix TWRP build error

- Device Tree Repo: Redo custom_mkbootimg.mk to allow for inline kernel building.
[Miscellaneous Android Development] praun:
Not to be annoying or anything. But just a question. Is it strait forward and just follow the video or is there something special to look out for?

I am getting so sick of this phone telling me that it's memory is full ?
[Miscellaneous Android Development] Matt07211:
I haven't had the chance to watch the video (also because I don't own the value editon), but the root process for the value editon is simple.

Enable developer options and enter the developer options menu and tick OEM unlock and USB debugging. Boot into download mode and flash TWRP via Odin, boot into TWRP and flash SuperSu.zip, you've got root.

Basically, have a read of the instructions in OP while you follow that users video :)
[Miscellaneous Android Development] Devhost97:
It was simillar. Just Follow S7/S7E guide.
[Miscellaneous Android Development] spalnndsstest:
i am getting a bit frustrated with MTP transfer protocol

is really slow,

is there any way to enable mass storage when connecting the USB ?
[Miscellaneous Android Development] Matt07211:
I'm not really sure, I haven't really looked into it, if you figure it out, please share here :)
[Miscellaneous Android Development] akuhak:
For android >=5.0 no way to enable mass storage for internal storage. Only for external storage (SD Card) with help of some external programs (UMS enabler for example)
[Miscellaneous Android Development] Matt07211:
I'm gonna have to disagree, a relative has a ZTE Blade q Lux on Android lollipop. They have the choice between MTP, PTP, INSTALL DRIVERS, USB MASS STORAGE (the one we want), charging and USB tethering. So it is available on lollipop though
[Miscellaneous Android Development] Fred4807:
Hello All,

Just an update on my issue regarding screen becoming black, from time to time, when doing a resource consuming operation (app installation for example, but sometimes even with MMS opening).

The phone went to an official Samsung repair center.

They changed the screen and something they described as "keyboard". I assume the touches ?

Nevertheless, the Issue was still here after that. So the phone was send a second time to that repair center.

It is now came back and seems OK.

They change the motherboard and "CI/PA/Filter ". Don't know what it is. Hope it will be ok now.

A question : as they changed the motherboard the field WARRANTY VOID (0x0304) is now back to "0".

Current ROM is XEO. If I upload an official Samsung XEF rom (not rooted), using Odin and download mode, will the field WARRANTY VOID it switch to "1" ?

Because if it is the case I prefer wait 1 or 2 month to check the repair is stable before rooting the device again.

Thanks !

Fred
[Miscellaneous Android Development] Matt07211:
I'm really not sure, you'll have to research other cases of people updating official firmware and if it triggered Knox.

In my opinion I don't believe the warranty will go void flashing official firmware, but take this with a grain of salt as I haven't any experience in that area
[Miscellaneous Android Development] akuhak:
You can install any official firmware from any region with any combination of recovery, modem, system etc without risk of triggering knox. I was able to install it even one custom TWRP recovery (with official kernel of course) without triggering it. The main thing - you cannot use custom kernels.
[Miscellaneous Android Development] Matt07211:
Thanks for confirming that.

===

We are still Currently working through build errors for both LineageOS ROM and a new TWRP recovery (The newest update), but progress is being made.

Note: This for the normal xCover3, not the value editon.
[Miscellaneous Android Development] Sonof8Bits:
For those with an XCover3 Value Edition, the official build of the latest TWRP (3.1.0.0) is out!

https://dl.twrp.me/xcover3velte/
[Miscellaneous Android Development] IXgnas:
Your profile picture matches your announcement perfectly ;)
[Miscellaneous Android Development] Sonof8Bits:
:good::D

---------- Post added at 06:36 PM ---------- Previous post was at 06:24 PM ----------

Also, there's this (unofficial) backup tool for windows users: https://xdaforums.com/android/software-hacking/tool-twrp-backup-restore-tool-pc-t3572241
[Miscellaneous Android Development] Fred4807:
:good:

Hello !

I done the change today from official Samsung XEO to official Samsung XEF.

I can confirm it didn't trigger knox.

Let's see if the repair is stable before going further...

Thanks for support & have a good day !

Fred
[Miscellaneous Android Development] Matt07211:
Just would like to say I haven't forgot about this phone, just that I have limited time to build new TWRP/LineageOS and sinceits my firsttimw prting and Rom compiling I'm having a hard time figuring out all the build errors, but anyway I am working through them as they come up.
[Miscellaneous Android Development] Devhost97:
Hello :)

Here you have the new CSC tweaks for X3VE users:

https://xdaforums.com/showpost.php?p=70776523&postcount=3
[Miscellaneous Android Development] benstyle1:
Hi there, got that update notification for my VE today. Has anybody installed it already? Is it a major update?

Thanks
[Miscellaneous Android Development] Matt07211:
Pinging for your benefit, [MENTION=7848003]Sonof8Bits[/MENTION] and [MENTION=4885288]Devhost97[/MENTION] as they both have a VE and may be able to answer.

Side note: ROM development is still happening, but slowly, LineageOS and every other custom ROM has no support for Marvell SoC's, so I'm having to do everything from the ground up, including the hardware (code) related repo (it includes the graphics source code, so you can even compile the graphics binary and even overclock, if slyou so desire).
[Miscellaneous Android Development] Devhost97:
For Germany yes.

But i am using Polish XEO and they this same changelist and baseband version but older Security Updates.

https://www.sammobile.com/firmwares/galaxy-xcover-3-ve/SM-G389F/XEO/download/G389FXXS1APK1/115479/

https://www.sammobile.com/firmwares/galaxy-xcover-3-ve/SM-G389F/DBT/download/G389FXXU1AQC1/129022/
[Miscellaneous Android Development] SmietanaTrzydziecha:
How to install xposed on 5.1.1 in G388F?
[Miscellaneous Android Development] 2535:
yes absolutely

Xposed Installer-3.0.1 by dvdandroid - 12.11.16
[Miscellaneous Android Development] Matt07211:
View Post 3 for links, basically you flash framework via TWRP and install the APK. You should be Good to go.
[Miscellaneous Android Development] SmietanaTrzydziecha:
After Flash i have bootloop. Xposed is only work on 4.4.4