yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] Matt07211:
My previous post, was somewhat on par. What I mean by this is yes, the ramdisk was a reason why it was not boot, but not for any reasons like permissions, ownership or the like, it was in fact that when unpacking and repacking the cpio archive increase the size, and from what I have reduced from my trial and errors is when the boot.img size is changed by even one byte in size it won't boot. But you are able to modify its contents with a hex editor, E.G. Zeroing out the word SEANDROIDENFORCING at the bottom of the raw image file, would still let the phone boot fully with the text show "KERNEL is not SEANDROIDENFORCING" and it showing up as a custom binary in Download more. I belive it may be becuse of some outside security verifying the boot.img. maybe download mode (it's in secure mode, haven't looked into it yet) or some script, I am not sure. And its all most impossible to get any errors logs or dmesg via adb or otherwise, with my only way to read them is via stock recovery, which is a bit impractical and inelegant reading as it speeds past lines you want to read when trying to scroll down (if anyone knows how to pull these logs from cache without a custom recovery or root, please tell me.

Now when I try to replace the ramdisk in boot.img via hex editor the size increase and thus unable to boot. When I try to repack it with various versions of mkbootimg, including Google's python script, other bi nary compiled versions of it by various people and mkbootimg's binary modified to also with with Device Tree Files which get appended onto the boot.img. I have analysed and reverse enginered the boot.img file, and analyzed the other files included with the stock firmware downloadable from sites like sammobile, sam-firmware etc.

I will be updating one of the is original post with all the information that I have uncovered, I'm great detail and when my internet situation allows (my mobile data is running low, lol), upload the reversed enginered files of boot.img for anyone else to inspect and have a crack at creating their own custom kernel/boot.img.

TL;DR: Uploading detailed information and reverse enginered files of boot.img. Any of my custom boot.img's won't boot if the size changes at the minimum one byte from the original boot.img, but the phone can boot a custom version if the size of the file size deos not change a single byte.
[Miscellaneous Android Development] Heledir:
Hi;

TWRP is ready for SM-G389F :

https://twrp.me/devices/samsunggalaxyxcover3ve.html
[Miscellaneous Android Development] Matt07211:
This currently only works for Kit Kat, after I unpacked it I read the files at it was aimed at android 4.4.4. I am, after I have my exams in the next few weeks I am gonna try and get TWRP working on lollipop (after I got root ;) )
[Miscellaneous Android Development] Heledir:
Software for Samsung Galaxy Xcover 3 VE (SM-G389F) is Android 6.0, so I think it's for MM. The links:

- Device Tree / files

https://github.com/TeamWin/android_device_samsung_xcover3velte

Say its Android 6.0 branch.

I've install it yesterday with Odin and it works fine on my SM-G389F.

But i haven't find root for SM-G389F and MM.
[Miscellaneous Android Development] proguru:
Hi,

I checked the poll, but unfortunately I have not much understanding what those things mean in the real life. Kernel is only for booting , so it doesn't bring any features to Android, right? So modded (or custom) firmware means more changes in features, right?

Anyway, modifications I would like to see in xCover3 are fixes to the following issues:

1) The lack of ambient light sensor makes it unable to see anything on the screen in bright daylight, if the screen was left on darker setting before.

I would fix this annoyance by having the brightest settings as a fixed default. So, in principle, the brightness could be adjusted, e.g. for a night time websurfing, but it would forget the brightness setting immediately after locking the screen and would resume with the full brightness.

2) The camera API in xCover 3 really rarely updates the GPS location (geotagging) for photos, that means photos taken at different locations show the GPS coordinates of the exactly same location, that may be kilometers away from the real location due to the slow update frequency. This applies both the built-in camera app and also all other camera application from Play Store, so it is not an app specific issue but a feature in xCover's Android version.

Would it be possible to change the camera operation to force GPS position poll everytime a photo is taken?

3) When opening the camera from the lock-screen (lower right corner) without unlocking the phone the GPS coordinates are not stored in photos at all.

4) SD-card permanent write permissions for all apps.

5) Automatic screen rotation doesn't work when the device in upside down in vertical position.

6) Silent camera hack (can be done with the app https://sites.google.com/site/enforcedstreamsilencer/)

7) I don't fully understand how the multitasking in Lollipop works, or is this a Samsung specigic thing. I have some background apps (CPU- and network-monitoring) which work just fine in Nexus 7 (marshmallow), but in xCover 3 (lollipop) those apps keep running for some time but then they are automatically closed.
[Miscellaneous Android Development] Sonof8Bits:
I simply replaced the camera shutter sound files with silent versions. You want them?
[Miscellaneous Android Development] proguru:
That's a simple solution :)

No need to send files, thanks, I can easily make my own if needed. The location of system sounds seems to be "/system/media/audio/ui/"
[Miscellaneous Android Development] Matt07211:
Some mods seem like they will be automatically on, but looking at some of the screenshots they are able to toggle the options. I'll make sure to put as many good mods in without change the phone drastically.

I'll try an be as sensible as I can be ;)

Sorry for a late reply [MENTION=5716433]proguru[/MENTION], I was almost finowshed typing this up and dropped my phone, meaning I had to start typing again.

What use is a custom kernel? When you hear people saying they overclocked or underclocked their phone, they are using a custom kernel. When you hear people say they put their govenrr onto something like smartassv2, on-demand, conservative etc. (Some are stock kernel) but this means the custom goveners are from a custom kernel. A custom kernel allows you to add/drop different filesystem support I.e. NTFS, ORG Cable support etc.etc. are able to be achieved via a custom kernel.

Know into your wanted modifications.

1) I believe I had seen quite a few different guides for ambient display, so gotta see them. For the moment I am using CF.Lumen for my screen.

2)I never use my location unless needed (I.e. Maps) so I haven't experienced this problem (I also have Google photos strip geolocation). But I'll see if the big list has anything for that.

3) Same as above, will have to look.

4) Simple fix, only requires editing one file. You can get a playstore app to do it for you, or you can look for it in the list (use search function) and manually do it your self. Simple one line edit.

5) Full 360¤ rotation correct? The big list has that fix in their.

6) Am debating it. Sonof8Bits suggested a simple fix (that would never have worked on my previous phone ;) )

7)Xcover3 has way less RAM then a nexus, so it will have to kill off task more sooner then the nexus does. As well as the fact that marshmallow has better RAM management then lollipop.
[Miscellaneous Android Development] Matt07211:
Guys keep your eye on this post. This post will be edited as I prwofess in developing the modded firmware.

Modded Firmware (Progress/Features):

- I'm going for deodex over odex. Reasons are HERE and HERE . Basically allows for easier themeing and modification. And other then a slow first few (couple) of boots, boot time will be almost the same as odex (current on the phone).

- To be added.
[Miscellaneous Android Development] akuhak:
About custom kernel.

Governors can be ported from here, cause this is almost the same Marvell board

Overclocking can be adjusted by porting changes from this branch

BTW almost all requests are adjusted by Wanam Xposed, and all others by other Xpsoed modules...
[Miscellaneous Android Development] Matt07211:
I'll have a look at those github links when doing the custom kernel, but I hope you know that I have a set of limitations to work around/in. These limitations severly limit my speed, ability to produce stuff (No 64 bit computer or unlimited data etc.) and overall what I am able to produce for this device.

As for your second part of your post ibaint gonna stop you using exposed and I ain't gonna make youbuaebthe missed firmware either, all I'm merely doing is offering users a choice.

I myself would rather cut a middle man like exposed out of the picture (especially the optimising 1 app at boot every boot). Some of the exposed modules are severly outdated and don't work, or any other modules don't work a Touchwiz device, so our choice of items is limited (even then some of the features still don't work I.e. Wallpaper Scrolling). You can still use exposed even if your using my modded firmware. But my modded firmware will be able to bring what wanams module does and more with out as much overhead.

I am merely just offering an alternative.
[Miscellaneous Android Development] Matt07211:
Just thinking out loud here, but I was thinking if I implemented multi-rom, we can dual boot Kit-Kat and lollipop.It would only be for ****s and giggles (unless more roms are made). Other than that it would provide a safe playground for me to build and test my modded firmware.

I'll either have to rebase the current Kit-Kat TWRP or Build from scratch (first option more feasible for me at the moment). But this would probably just be a side idea/project.

/End Rant.
[Miscellaneous Android Development] Devhost97:
How you deleted the Google Apps from ROM ?
[Miscellaneous Android Development] akuhak:
There are tons of programs that can do it. Personally, I use LuckyPatcher for program removing and Titainum Backup for integrating updates into system. BTW LuckyPatcher has funny feature - Integrate Updates into /system on the fly.

This means when some built-in software is updated (for example Google Play Market) it doesn't copied into /data, but directly in system with app replace (like user apps do). It can save space and a lot!!! for about 700 Mb free in /data with stock rom apps integrated (all apps without removing). You will loose feature "Restore original version of app" but who are using this? )) Unfortunately LuckyPatcher cannot integrate already updated app, so Im using Titanium Backup who has this option built-in
[Miscellaneous Android Development] Sonof8Bits:
If feasible I'm willing to compile. Just tell me what compiler and toolchain I need to install and what command(s) to throw at it and I'll send you the results.

Edit:

If the phone would fit 2 operating systems, would it fit Marshmallow? Especially after debloating there might be enough room to update. Or is the different chipset in the VE variant of the phone too big an obstacle to overcome?
[Miscellaneous Android Development] Matt07211:
I will take you up on that offer about compiling, it's rather simple, hit a few commands then let it to its thing. Upload the result. Proguru did this for me once. Was rather quick and painless.

Probably do that for kernel (and maybe TWRP).

Now with your second part. Multirom has 3 different locations where you can boot off from (Internal, SD Card and USB (Via OTG Cable)) meaning space wouldn't be a problem, just the read and write speed.

Although I would just use multiboot (why do I need 2 versions of android running), whem I'm testing and debuging (This phone is my daily driver).

As for MM I can always try and backport it, but as you said I am not sure how big of a problem the different boards/chipsets will be untill I do it. The other option is if a user compiles a MM/NOUGHT Rom(s).

I am currently (at this very moment (like right now)) rebasing the kitkat TWRP (The one linked in OP) to reflect Lollipop changes and run Lollipop Kernel (Hopefully it will work.) So I can do a nandroid more safely.

I'll have to compile TWRP from source to do Multirom.
[Miscellaneous Android Development] IXgnas:
Hi!

I saw that you use boot.img to root 5.1.1. May I know what software did you use for image extraction?
[Miscellaneous Android Development] akuhak:
https://github.com/AKuHAK/android_img_repack_tools/releases/tag/1st
[Miscellaneous Android Development] Matt07211:
The orginal is ANDROID_IMG_REPACK_TOOL
(Original Thread: http://xdaforums.com/showthread.php?t=2600364) which

[MENTION=7770482]akuhak[/MENTION] has modifed ( https://github.com/AKuHAK/android_img_repack_tools ) it to build tools specifically for the device (the 5.1.1 branch only, value editon can use xaluo's tools).

I'll write up a proper guide to unpacking and repacking boot.img/recovery.img and system.img (as well as the other files, all sparse files) if your interested as I've put it off as no one else has interest at the device at the moment. I'll happily go and write it up if there is interest on your end. :)
[Miscellaneous Android Development] IXgnas:
[MENTION=7770482]akuhak[/MENTION] Thanks for your quick response! However, ./configure 'ing gave me quite a few errors at the end of the process, and compiling wasn't successful either :(.

[MENTION=6318002]Matt07211[/MENTION] thank you! It would be nice to have one, but please don't make it unless you really feel like you should ;).
[Miscellaneous Android Development] Matt07211:
It was a planned thing to do, I've just put it off since no one else but me at the mkmwnta has needed to do stuff like unpack and repack boot, recovery and system etc.

So if your planning on doing development or just want proper instructions on messing with the device then I am happy to write up the rest of the instructions when I have free time this afternoon.

Are you still having the problem and compiling? If you looked at the original thread I linked it's got a couple of dependices to be installed so I suggest you install them if you have yet to. The configure command should download and get everything set up for the make command.
[Miscellaneous Android Development] IXgnas:
Sadly, the compiling errors still persist, but this time, I managed to get a lot further.

This is the make command error (only the error, not the whole build log. I'll keep the terminal on just in case I need to provide more info):

Building libpcre...
ar: pcre/*.o: No such file or directory
Makefile:130: recipe for target 'libpcre' failed
make: *** [libpcre] Error 1
[Miscellaneous Android Development] Matt07211:
Is the android Image repack folder you should see a folder called pcre. Which version you using?

I originally had the Android Image repack from tbe original thread and downloaded, then akuhak realeased his tools so I overwrite the 4 files and re-didnthe configure and make. No problems.

If it still persists later today contact me via PM.
[Miscellaneous Android Development] Matt07211:
My I ask any user of this thread, please do not do what this user has done HERE. We ask you not to re-upload or plagerize out work please, as it I'll help make us a better community (and I really don't want to report another user again)
[Miscellaneous Android Development] IXgnas:
Could "traditional" rooting method work on 5.1.1, considering the fact that TWRP now works on this version of Android?
[Miscellaneous Android Development] Matt07211:
Put it simply. No. Akuhak had tried flashing supersu when he used his hacked together TWRP, but it didn't work. I have implemented exactly the samething his script does but by hand (it took many attempts before I got it working).

But I'm guessing your talking about placing su into the system partition, am I correct? Although you can still do that it still, it now requires you to unpack the boot.img and patch the ramdisk. This is to help get around selinux, and is a required step.

So yes you can place the files into system but youlk still need to patch the boot.img.

I went with systemless becuse it was easier on users to get set up into their device and is easier to cleanup and unroot the device.

If you got any other questions feel free to ask :)
[Miscellaneous Android Development] benstyle1:
Hi,

i installed TWRP on my Xcover VE as described in the first post using odin. It worked, directly after flashing twrp i was able to boot into recovery to flash supersu. However, when i try to boot the rom, it stucks at boot logo. Can somebody tell me what to do?

Thanks!
[Miscellaneous Android Development] Matt07211:
Boot into TWRP and wipe Dalvik Cache and Cache and Reboot. If problems still appear then I'll help you when I wake up.

I'm going to sleep, it's late here, but report back here if success or failure ;)

Edit: Did you allow TWRP system modification permission? You should click yes, then flash SuperSu directly after to disable the security lockout.

Did you enable OEM unlock?
[Miscellaneous Android Development] benstyle1:
I already tried wiping Caches, without success. I allowed system modification and flashed supersu right after. I also enabled OEM unlock before flashing twrp.

While booting into the recovery,

"Recovery is not seandroid enforcing" is displayed in the upper left. Maybe thats relevant.

Thank you!
[Miscellaneous Android Development] Palawan-Taucher:
Please edit the Useful Links ...

Hello all,

in the useful links is an link to the TWRP for Samsung xCover3 (Kit Kat)

what is not for Lollipop useable at all

Useful Links:

My Github (Matt07211) containing kernel source code, to keep with the GPL licenses.

Samsung Kernel Source Code 4.4.4/5.1.1 and 6.0.1

Firmware Samsung xCover 3 and Samsung xCover 3 Value Edition

TWRP for Samsung xCover3 (Kit Kat)

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

SuperSU​

please chanche to the useable link from this page there ...

TWRP:

KitKat: Working

Lollipop: Not Working (I'm looking into it) The is a hacked together version of TWRP HERE, in case people want to flash files. I wouldn't recommend it for anything else other then flashing, as i would perfer to build a proper working TWRP for lollipop.

Note: You'll have to hold, Volume Up + Home + Power buttons straightafter flashing from Odin, keep hold of the key combo untill you see the TWRP logo (2 reboots).

Marshmallow: Working​
[Miscellaneous Android Development] marcdu30:
Xposed install

Hello,

does anyone have a link for the application "xposed install"? I'm in 4.4.4 on my xcover3

Thanks :)
[Miscellaneous Android Development] IXgnas:
It's right here, on XDA-Devs. Just use the search feature, and you'll find it without much effort ;).
[Miscellaneous Android Development] marcdu30:
Thank you ... But I did not find one that works. I found a xposed "sdk19" on google, but the function "wifi direct" no longer worked with this one on my Xcover3. Thank you for your mutual aid.
[Miscellaneous Android Development] IXgnas:
What did you mean by saying "WiFi Direct no longer worked with this one"?

---------- Post added at 06:47 PM ---------- Previous post was at 06:41 PM ----------

Also, I've found this thread. Maybe that'll help you: http://xdaforums.com/xposed/xposed-framework-doesnt-galaxy-nexus-t3275699/page1
[Miscellaneous Android Development] marcdu30:
It was impossible to connect in wifi my two phones (xcover and note2) after research, I identified that it was my xposed that posed this problem. So I uninstalled it and that's why I'm looking for another one.
[Miscellaneous Android Development] IXgnas:
I also faced this problem while I had KK. Sadly, the only way I know to get working is to update to LL :(.
[Miscellaneous Android Development] marcdu30:
I have already tried this link. Alas without success: "not compatible with sdk19" ... I do not despair to find.

---------- Post added at 07:10 PM ---------- Previous post was at 07:00 PM ----------

If that is the only way out I will. It will just be necessary that I re-read this thread to learn how to route on LL.

:confused:
[Miscellaneous Android Development] IXgnas:
Hate to tell your this, but there might be no solution. Although I saw that certain kernel mods can damage the WiFi driver or something like that, but I doubt that might happen. I'll PM you the link in case I find a post with such info, as it had the solution
[Miscellaneous Android Development] marcdu30:
Thanks :good:
[Miscellaneous Android Development] Matt07211:
Can you tell me what download more days (preferably providing a screenshot/image).

Now if you want a working phone again (feel free to try rooting again afterwards), flash

Samsung xCover 3 Value Edition
forms are back to your phone. Choose the firmware that matchs your phone/region. Your /data (apps) and internal storage will remain untouched. You'll just be going back to stock.

Are you able to provided the SuperSu logs, which I believe can be found under /data

The difference between the recovery a is 2 of them have been compillied from source and the other one is a mutilation of a different roms recovery.img. if your willing to test all functionality (E.g. Backup and Restore etc.) Then I'll update op. I'm currently linking that recovery so people can flash zips (E.g. xposed).

Me and [MENTION=7848003]Sonof8Bits[/MENTION] are trying to compile TWRP for lollipop from source, but we are stuck at TW_THEME error and sonof8bits hasn't been online in the last few days so I've been unable to finish it.
[Miscellaneous Android Development] Matt07211:
For your WiFi direct problem, I'm not sure how to fix it (plus I've never used it or even what it does lol). But other then trying a newer version of android with wanams unofficial xposed.

Sorry for a late reply, I had to go to work. Please report of your successful in getting WiFi direct to work.
[Miscellaneous Android Development] marcdu30:
thank you for your reply. For the moment I made a restore of my backup (without xposed)
[Miscellaneous Android Development] Matt07211:
...or you could have used the exposed uninstaller. Hehehe.

Either way the end result is achieved ;)
[Miscellaneous Android Development] benstyle1:
Matt, thanks for your help. I finally got i i working; it seems, there was a problem with supersu. After i flashed the latest beta from chainfires website (SR5-SuperSU-v2.78-SR5-20161130091551.zip) via sideload, it booted without any issues. The version i tried before was BETA-SuperSU-v2.49.zip.

Now everything is working as it should, including wanam's xposed.
[Miscellaneous Android Development] Matt07211:
Glad you got everything working properly I believed I mentioned a minimum version of SuperSu to be used at OP (If i didn't then I'll update it tomorrow)

You using wanam's exposed module (Marshmallow version?), have you got wallpaper scrolling to work, it seems to not work on my lollipop device.
[Miscellaneous Android Development] Matt07211:
Just would like to give everyone here some early Christmas news :)

I've recently come to realize that I'm able to use Google Cloud/Microsoft Azure free trials. This will allow me to build some ROMS for the xCover3 (Normal Edition).

So few the next week or so I'll be reading up a lot, setting up the github repository correctly (cause at the moment they are only partially up and unorganized), then around the begging of the new year I'll start commencing on ROM building.

Hopefully by then me and [MENTION=7848003]Sonof8Bits[/MENTION] can get TWRP compiled for the device (keeps throwing TW_THEME error when's itbalreadu be defined anyway, so if you got a fix Pease PM me), if we don't then that'll be the first thing to be done.

The Rom will be based of OMNI sources and be either Marshmallow or Nougat (depending on the device requirements), if anyone would like to aid in this endeavour please contact me.

Note: I'm still planning to do the modded firmware ;)

Merry Christmas everyone and I hope you will enjoy the idea of a custom Rom dimming your way in the near future.
[Miscellaneous Android Development] Sonof8Bits:
Busy weeks ahead, but I will get back to building ASAP. Hopefully we can get everyone a late christmas gift in the form of a working TWRP.