yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Governor_666:
Hello all.

I have been following this site and this thread for a quite a long time and i have read the chain twice at least.

I'm what you call a noob with this rooting and customizing a android device, some terms are strange for me and some not so strange.

By the way, i want to thank you all, how took your time and figured out how to gain root access to xcover 3. (specially for basic g388f model)

The thing i'm wondering is, i have gained the root access and succesfully flashed twrp recovery(thanks to akuhak), can i now get a custom rom in my device?

I've been trying to read and learn about cyanogenmod but it seem's to me that those "applies to every androind device videos and how to's", doesn't concern my device.

So, can i download a some version of cyanogenmod and flash it for my device and after that, have an usable device?

And if, are there any restrictions what version?

Can i do flashing with Flashity, or somekind of app like that, without pc?

After i gained root access, i downloaded

-terminal emulator

-rom toolbox

-titanium backup

-root checker

-wakelock detector

-f-droid

-busybox

-link2sd

I just don't know if i have the knowledge to use all the potential of those app's.

I made a backup with TB and when i got this device to boot into a recovery mode i made a backup in there too, so i guess i have enough of backup's.

With rom toolbox i changed the fonts of the device and modified swappiness and cache pressure settings.

I am afraid of deleting some bloatware but i did delete some of those with TB.

So the question is, if it's possible, what is the most easy and idiot proof way to do that?

Sorry about all the questions in one post.

---------- Post added at 04:20 PM ---------- Previous post was at 03:40 PM ----------

I found out the hard way that this version of twrp didn't work in my sm-g388f.

With this, i got a working recovery. https://xdaforums.com/showpost.php?p=69813173&postcount=135

Before that i tried flashing twrp-3.1.1-0 about a dozen times and got a error of "recovery is not seandroid enforcing", and could not boot to recovery. Phone worked properly else but i couldn't boot to recovery mode.
[Miscellaneous Android Development] Governor_666:
Do i have to try this or is there someone who has done this already?
[Miscellaneous Android Development] IXgnas:
This is not a good idea. Even if you do manage to find a device with a matching SoC, you'll still have a variety of driver problems requiring solutions.
[Miscellaneous Android Development] akuhak:
I can tell that i was trying to find any custom rom on our soc and there is simple answer. There is no such a rom ((( but if you want try to search some. There is devices that matched our soc.

https://github.com/topjohnwu/Magisk/pull/340#issuecomment-324461182
[Miscellaneous Android Development] Governor_666:
In my level of knowledge, i'll have to stay in stock.

Having root causes enough head scratching for me sometimes.

Is there some kind of tweaks and tips that i could do now that it is possible?

This device seem's to be searching gps almost all the time and i found a video of gps.config on youtube, made by xda developers, and that did the trick for this device very well, no problem on that field anymore.

So those kind of tweaks and tips would be very welcome, if there are any?

As i stated in my previous post i did some adjustment for swappiness and cache pressure and in my opinion that was a good tweak to do.

I'm not experiencing any battery drainage, quite the opposite.

So this post may tell you professional's that there are some quite complicated things i do understand about how these things work but there are some so obvious and basic stuff that i don't have a clue about.

I know what a kernel does( because i use linux). Would there be a real use in everyday usage in battery life or some else usability of the device if i flashed the custom kernel that already exists?
[Miscellaneous Android Development] kaigara_online:
Root done but no ROMs

I followed the OPs steps and i rooted my 388F.

From what i read here, there are no custom ROMs, right? :(((
[Miscellaneous Android Development] Governor_666:
Thats what i've been told about custom rom's.

Has anyone tried how things turn out if you use rom toolbox for downloading a custom bootimage, reboot to a twrp recovery and install the zip file?

Twrp shows a warning that you may render your device to a brick if the file is incompatible and that scared me to think twice and ask for help.

Has to be a pretty hazard zip file if you can't even boot to download mode afterwards?
[Miscellaneous Android Development] Governor_666:
My xcover is now pretty much modified like akuhak's.

I am now wondering if this, https://github.com/AKuHAK/xcover3ltexx_custom_kernel/releases , had any benefits?

I tried to find some info of it's features but didn't find any.

Is it better than stock kernel?
[Miscellaneous Android Development] akuhak:
Im just too lazy to publish it here :)

Yes it has benefits: updated to latest kernel sources, more stable, all vulnerabilities fixed, added zzmoove governor, it has 2 version: one with SuperSu integrated, second without. As for me I didn't have any issues with both kernel versions, someone says that SuperSu version drains battery a lot (not for me). But since yesterday magisk supports Xcover 3 G388F so in nearest future it will be possible to use it in our devices (next beta will support it so set reminders).
[Miscellaneous Android Development] Governor_666:
Thanks for replying so quickly.

I already have supersu installed so is it ok to try the "without" version?

Is there a freshly updated link somewhere for download?
[Miscellaneous Android Development] akuhak:
no 'without' version will not work cause supersu does not support clean pxa kernel.

For now I have only one release which you already found.
[Miscellaneous Android Development] Governor_666:
Well, i flashed your kernel.

It's good, behaves like it should and no battery drain.

Something else seems to be messed up, perhaps in partitions. (just a guess)

I did the xposed flashing with twrp and it flash the zip just fine but it kept giving me:

unable to mount '/nvm'

Why? What is that?
[Miscellaneous Android Development] Governor_666:
If i understood correctly, latest release of magisk, supports sm-g388f model.

But it's still a beta version of magisk, so has anyone tried how it works?

I have absolutely no clue about debugging so is it better to wait for a stable version?
[Miscellaneous Android Development] akuhak:
Im using this version (https://github.com/kantjer/MagiskFiles) of Magisk with clean kernel from my github repo. Works like a charm :)
[Miscellaneous Android Development] martin5martin5:
I am stuck:

"RECOVERY IS NOT SEANDROID ENFORCING" HELP!!!!!!﻿

I followed this:

https://www.youtube.com/watch?v=kf27dCER-OA
[Miscellaneous Android Development] IXgnas:
What's your device? G388F or G389F? Trust me, there is a very big difference between those two, big enough to require different installation approaches.
[Miscellaneous Android Development] martin5martin5:
TWRP for Samsung xCover3 Value Edition

link 404 not found!

https://twrp.me/devices/samsunggalaxyxcover3ve.html

help.. :( I need working TWRP for Samsung Galaxy Xcover 3 SM-G389F.

---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------

hello. I trust you that.

sticker under battery says G389F.

I would need a working TWRP.. after that a working SU also :)
[Miscellaneous Android Development] IXgnas:
Are you telling me you installed TWRP for G388F? If so, you'll have to look up TWRP for G389F.
[Miscellaneous Android Development] martin5martin5:
I went to TWRP.me

typed to devices searchbox: xcover

https://xdaforums.com/attachment.php?attachmentid=4430472&stc=1&d=1519571268

selected Samsung Galaxy Xcover 3 VE (SM-G389F) (xcover3velte) (I have this on sticker in phone)

ODIN = green, PASS

but I got error message on phone screen:

"RECOVERY IS NOT SEANDROID ENFORCING"

also I noticed in topic start entry:

TWRP for Samsung xCover3 Value Edition

link 404 not found!

https://twrp.me/devices/samsunggalaxyxcover3ve.html

so my question remains the same:

I need working TWRP for Samsung Galaxy Xcover 3 SM-G389F.
[Miscellaneous Android Development] IXgnas:
You should've followed Matt's tutorial, as it includes all the links necessary.
[Miscellaneous Android Development] martin5martin5:
I gladly would have followed, but the link to TWRP is dead.

TWRP for Samsung xCover3 Value Edition Credits: [MENTION=884555]Heledir[/MENTION] for the link

https://twrp.me/devices/samsunggalaxyxcover3ve.html 404 Not Found.

so my question remains the same:

I need working TWRP for Samsung Galaxy Xcover 3 SM-G389F. which one shoild I select from https://twrp.me/Devices/ ?
[Miscellaneous Android Development] IXgnas:
https://twrp.me/samsung/samsunggalaxyxcover3ve.html

Learn to scour the internet for the things you need.
[Miscellaneous Android Development] martin5martin5:
exactly that I installed with odin, => "RECOVERY IS NOT SEANDROID ENFORCING".

maybe I should try older versions there? worth a try I guess.
[Miscellaneous Android Development] IXgnas:
You tell us.
[Miscellaneous Android Development] martin5martin5:
I dont understand this:

IXgnas has quoted you on xda-developers!

Here is the message that has just been posted:

I gladly would have followed, but the link to TWRP is dead.

TWRP for Samsung xCover3 Value Edition Credits: Heledir for the link

https://twrp.me/devices/samsunggalaxyxcover3ve.html 404 Not Found.

Not only does the link work for me, but it also let me download the file. You should try again.

=> pls, if you could download that, would you pls share it with me/ us?

thx.
[Miscellaneous Android Development] martin5martin5:
I have this phone:

SM-G389F. please see attached photo.

TWRP can be found here:

https://twrp.me/samsung/samsunggalaxyxcover3ve.html TWRP for Samsung Galaxy Xcover 3 VE (SM-G389F)

I can upload all versions with ODIN.

last most recent= totally not working, phone hangs "RECOVERY IS NOT SEANDROID ENFORCING"

only the oldest version works (TWRP), but I am UNABLE to put a checkmark to mount DATA partition. unable to select it, can not put check mark.

so, at this moment I am unable to run any TWRP.

I reuploaded all TWRP, none is working now,

unable to mount DATA, invalid argument (pls see photos)

https://photos.app.goo.gl/yH44I8R4lBu6Zem83

another question: what does it means, FRP lock= OFF, varranty void = 1 ?

thx.
[Miscellaneous Android Development] IXgnas:
I'm running out of ideas... Unless you have a really unique G389F that is not compatible with TWRP, I don't see why it shouldn't work. Maybe this FRP lock (whatever it is) is the culprit?

"Warranty void = 1" is pretty self explanatory. If it's 0 (false), it means that your warranty is intact. Likewise, a value of 1 means it's void, which means that you can no longer get free repairs.
[Miscellaneous Android Development] martin5martin5:
I guess I can NOT mount the DATA because it is encrypted. I try to re install the oldest TWRP and see if I can root.
[Miscellaneous Android Development] IXgnas:
Data NEEDS to be decrypted as soon as TWRP is launched. How did you encrypt it? Via a pattern? If so, weren't you presented with a pattern unlock screen on TWRP boot?
[Miscellaneous Android Development] martin5martin5:
IT IS WORKING NOW

TWRP is on and working, SU also okay, rooted.

only the oldest TWRP worked after many attempts.
[Miscellaneous Android Development] IXgnas:
Have you tried installing the newest TWRP after rooting?
[Miscellaneous Android Development] xTerraH:
Came here to say that version 3.2.3 of Twrp doesn't work for the Xcover VE, even when updated via an older twrp version. However, version 3.1.1 Appears to work fine.
[Miscellaneous Android Development] Jack Skog:
Managed to root XCover 3 G389F

Hi. Acquired XCover 3 G389F VE awhile back as used/leased company-phone from nearby "cheap-mart". Use it as backup-phone pay-as-you-go -mode. Hence, do not want much data usage/leakage to unnecessarily use my balance.

So, needed root to implement firewall, greenify etc.

Used older TWRP-version (twrp-3.1.1-0-xcover3velte.img I think it was.) and latest SuperSU. Gave me hiccups with "recovery not seandroid" a few times but once somehow managed to boot into TWRP and was able to root. (Sry, do not know what I did. If it was the interval between battery removal and boot-procedure or what.) :(

Anyways. Not smooth sailing. I think I went through almost all TWRP-versions to get it done.

Otherwise, did as usual in earlier posts. OEM unlocked, ODIN (1.31.1)... Nothing peculiar there.

Thanks Matt, Heledir, kniederberger and others who gave their input and insight.

Edit: A irritating nagging occurrs now. "Unauthorized actions, reboot device..." I swipe it aside for now. I'll check later if something could be done.
[Miscellaneous Android Development] ex-xt:
ROM and time

HI everybody., and anyway greetings to the work done here . :)

Some points

I am not a real developer, had just been able to flash cyanogen 10.2 on a XCOVER 2 through linux and create a usable SD . To make the point it was not so easy for me but I had enjoyed it ...at the end .

I do not use it to play and a very little time on internet . My first goal is phone calls :laugh:and the second is GPS off connexion and mapping, riding tracks with OSMAND .

Unfortunately the cynanogen is not so stable and no more followed AND the battery time is too short for the purpose .... Sorry to be so long .

:laugh:

Here are the real specialists of the XC0VER 3 ..

so in one time ; IS it accurate to buy a " 3" : time, possible ROM ?

Can find on here around 50 euros .
[Miscellaneous Android Development] Nemirtingas:
Is there still someone using this phone ?
[Miscellaneous Android Development] reptakos:
oh yea... still working fine and I have no intention to replace it soon: screw the latest android crap

my typical usage: txt/calls/gps on gmaps/emails ,
[Miscellaneous Android Development] loograk:
HI,

I would like to root Samsung Xcover 3 (SM-G389F)

Android version

6.0.1

Baseband version

G389FXXU1ARC1

Kernel version

3.10.9-9531242

dpi@SWDG5311 #1

Wed Jun 13 11:13:09 KST2018

Build number

MMB29K.G389FXXU1ARF1

SE for Android - status

Enforcing

SEPF_SECMOBILE_6.0.1_0031

Wed Jun 13 11 32 39 2018

I tried to install TWRP with the manual from your thread:

OEM unlock on + Usb debbuging on, latest TWPR form your link.

I used odin (auto reboot off). After successfull flashing when I try to reboot the phone by taking out batterry, when I go to recovery mode (home + vol up+ power) the phone is getting stuck at "Recovery is not Seandroid Enforcing"

In your youtube video the same message is visible but recovery starts after a little while.

What am I doing wrong?
[Miscellaneous Android Development] eetteri:
hiya from new user

Hello,

this old beard started playing with this old G389F of mine and finally after four times jamming this I managed to keep it rooted w/o any flaws. Just to rply earlier post I could say I tried to use wrong TWRP many many times.. I guess 3.1.1.0 is the newest supported?

I've jammed this phone several times so far but now I've managed to make working image of working rooted setup :victory:

The first that I've been thanking many times is that I took a photo of one the screens during TWRP-flashing and that way I knew what is my original rom to download (in case of emergency, which came a lot...). After several faux stock roms I found a working one (from getdroidtips I remember...) and that has saved me four times so far :D

Now that I have managed to gt root and installed Magisk, what do You suggest here? What to do or try next? This is my first rooted phone and there seems to be so much on tap. Already jammed my phone with incompatible frameworks etc.. Would love to try another Android so is it LineageOS? Is it supported? Paranoid Android?

I continue to read this topic but is there any other place that offers more info about this phone and its tweaking?

...and sorry :o
[Miscellaneous Android Development] ex-xt:
from 2 t o3 maybe

hello guys.

I was on a way of changing my XCOV2 for something else , all I found was crap or expensive or pure google mess :cool:

So maybe the 3 could be a good solution IF it worked at least as well as the 2 .

Mine is under cyanogenmod ( some bugs sometimes but working anyway) , and the use is mostly phone calls, OSMAND for offroad motorcycle, and a few internet .

Here it is possible to get a used one for 40 or 50 €. It might be also a backup asi will ride towards ALMATY not far from chinese border and close to Russia too.

Some RR about gps and glonass accuracy as battery time ( weak point of the 2 ) will help.

thanks
[Miscellaneous Android Development] kipphebel3:
Can you please share what you did for the benefit of others? I have an old Xcover3 here that I intend to reinstall. What version of Odin did you use? What version of twrp? What version of LOS?
[Miscellaneous Android Development] eetteri:
what I did

Sure!

I made (for myself) a document where is all needed steps... and now that I haven't played for a while I need to think it a bit ^^

First I got all needed software:

•	USB-driver for samsung

•	Odin v3.13.1

•	TWRP zip (twrp-3.1.1-0-xcover3velte.img)

•	Magisk zip (v19.3) this has updated at least once after installation..

And now to get TWRP to phone there should be settings allowing USB debugging and OEM unlock (this I'm not sure?)

Then:

1.	Download-mode, Pow+Home+VolDown and in the blue screen VolUp

2.	Open Odin

3.	AP-field TWRP-image

4.	Start

Should go green on success. Few times I have messed this up but serveral times succeeded.

I installed Magisk:

1.	Boot to recovery -->TWRP, Pow+Home+VolUp

2.	Install button, search Magisk zip, should transfer this from computer to sd or other.

3.	Install

4.	Reboot

The I checked if I had root and w00t I did.

Yet I made another help in case of emergency:

1.	If TWRP/recovery works, Wipe as wanted (done it few times)

2.	Boot to download-mode, Pow+Home+VolDown --> VolUp

3.	Open Odin

4.	AP-field phones rom-image (esim G389FXXU1ARF1), takes few minutes. (this is where I needed the information what my rom image was, I found it on that blurred image.... link below, I'm not allowed to post links yet ^^

5.	Start
[Miscellaneous Android Development] kipphebel3:
When is Magisk actually needed? On the two phones I have tried, an S2 and S5 they ran just fine without installing Magisk. From what I have read Magisk is needed for certain Google apps, none of which I use.
[Miscellaneous Android Development] eetteri:
..and so far I have not installed any different OS, would like to try if there's any?

---------- Post added at 10:32 PM ---------- Previous post was at 10:29 PM ----------

:laugh: I really don't know...

...well I guess the purpose of Magisk is that it can grant superuser rights to apps I want.
[Miscellaneous Android Development] budgies:
Download link for G388F TWRP 2.8 in quoted post is dead, so I uploaded it here:

https://anonfile.com/p7K42cy4oa/G388F_Lollipop_Hackish_TWRP_2.8_7z

And btw i just successfully installed Magisk v19.4 and Magisk Manager 7.3.4 from here, so you don't need SuperSu:

https://github.com/topjohnwu/Magisk/releases

EDIT: Download Link updated 2020-04-22
[Miscellaneous Android Development] czuges:
budgies! Please make this link alive again!

Edit:

Yesterday it Wasn't working - now it's fine.

I made backup and restore it - everything looks good - Xposed works.

Thank you so much!
[Miscellaneous Android Development] Jack Skog:
XCover 3 - 389F VE

Been wondering about Custom Rom. Apparently in vain. Or?

Any thoughts of this? -> https://cyanogenmod-roms.apk.cafe/samsung/galaxy-xcover-3-value-edition

Anybody?

Preface: I like this phone as a navi-phone plus a backup phone. Pay-as-you-go -mode.
[Miscellaneous Android Development] k00b:
Hi,

i have an old xcover3. as someone with basic (old, but very basic) understanding of IT, i wanted to root the phone to have a device open for every carrier, stripped down of some pre-installed apps by my old network. as an emergency spare-phone or/and as an experimental ground.

i really tried to follow the procedures described at the beginning of the thread. I installed Odin, ADB bridge, got into debugging mode, basically done everything that i could, because apparently some things don't exist in the way described anymore.

as far as my understanding goes, basically a need to flash the phone with the correct file. i'm struck. i found a twrp file (twrp-3.1.1-0-xcover3ltexx.img.tar) which i can put on the device via odin, but that doesn't really change anything. there seems to be several possibilities about which way to go and i'm stuck.

any help od hint into the right direction to achieve the above in a "for dummies afap"-way would be greatly appreciated.

sorry for the inconvenience.

greets, kub
[Miscellaneous Android Development] budgies:
Hi, I updated my previous post with a new download link for what's referenced in this thread as "Hackish TWRP" (the official TWRP is worthless for Android 5.1 on the first Xcover 3 variant, the G388F):

https://xdaforums.com/showpost.php?p=80402513&postcount=510

So if your's is a G388F:

Make sure to have the newest Samsung Update installed, that will restrict the open security vulnerabilities to the last 3 and a half year or so..:D

If you're currently running some crippled ISP branded fimware, better get a "clean" (no ISP name in brackets on this list: androidsage dot com/2017/07/12/list-of-samsung-galaxy-country-specific-product-code-csc-and-country-region/ [linking this page is not allowed?! whatever..]) Samsung one for your country from: https://samfrew.com/model/SM-G388F/ (slow free downloads sucks, but I don't know any better way to get it).

Then flash the Hackish TWRP with Odin, the tricky part is to boot into TWRP directly after that, becaus otherwise it will be overwritten by the stock recovery again. IIRC there's a kind of "reboot after flash" checkbox in Odin, so untick it. That will give you enough time to press the button combination for recovery boot: Home+VolUp+Power.

Once you successfully booted TWRP once, it should remain there permanently.

To root it get the latest Magisk, there's a link to the official github releases page in my post mentioned above. As of today you want to download those:

Magisk-v20.4.zip, MagiskManager-v7.5.1.apk and, just in case but not really needed, Magisk-uninstaller-20200323.zip.

Put the files on you phone, install Magisk zip from TWRP, reboot to system, install Manager APK, done.

To clean up all the Samsung bloat and Google crap I used Batch Uninstaller from Fdroid: https://f-droid.org/en/packages/com.saha.batchuninstaller/

I found Lucky Patcher to be useful, too. It let's you integrate the changes you made back into the system image to really get rid of bloat apps even after a factory reset: https://www.luckypatchers.com/download/

But make a full backup from TWRP before you play around with those two, it's easy to delete things you need for a working phone.. ;)
[Miscellaneous Android Development] ppargc1a:
Hi. I have a Samsung Galaxy Xcover 3 that is currently locked, it asks for google authentication even after factory reset (don't worry I didn't steal the phone).

What can I do with the phone? Can this google restriction be removed? I've been looking into postmarketOS and it would be cool to make it run that. Has anyone tried to do this?
[Miscellaneous Android Development] k00b:
a big THANK YOU, it seems i managed to successfully root my phone following your links & suggestions! at least, that's what the extremely annoying SuperSu app says (5 ads in 4 seconds is really impressive).

i'll play around with the f-droid apps you recommend, and i hope to get along by myself from here. for now. haha.
[Miscellaneous Android Development] jodeka:
link to hackish twrp not working again

link is dead again... would be nice if you could fix that :=)
[Miscellaneous Android Development] budgies:
Updated, hope new hoster keeps it online for a longer time now..:confused: