yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] ash1970:
Śmietana - wpisz i ściągnij xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125.zip i tylko taki chodzi na 5.1

Wysłane z mojego SM-G388F przy użyciu Tapatalka
[Miscellaneous Android Development] Matt07211:
Did you check the 3 post like mentioned? Because I've linked to the needed file there.

This is what you need to flash:

https://xdaforums.com/xposed/unofficial-xposed-samsung-lollipop-t3180960

I am running it successfully

Please follow XDA rules and post it in English. Your still welcome to keep your text in your original language but please use Google translate and pasted it with the original text.

E.g.

Native Language

English (use Google translate of needed)
[Miscellaneous Android Development] SmietanaTrzydziecha:
Dzięki ash już chodzi
[Miscellaneous Android Development] yy1:
Tried to Build Lineage OS for SM-G388f

I'm follow this http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html.

I have do the repo sync. Can anyone tell me what's the next step to make al Lineage OS for our nice sm-g388f?:D

---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------

I'm follow this http://www.lineageosrom.com/2017/01/...m-for-any.html.

I have do the repo sync. Can anyone tell me what's the next step to make al Lineage OS for our nice sm-g388f?
[Miscellaneous Android Development] IXgnas:
Me and Matthew are trying to figure out the very same thing. Ask him to add you to our IRC channel.
[Miscellaneous Android Development] drzhf9:
for those customized phone images, any updates, bug fixes or changes to wlan driver/firmware?

thanks!
[Miscellaneous Android Development] IXgnas:
What "customized phone images"?
[Miscellaneous Android Development] drzhf9:
The links in this thread to downloadable "phone's firmware"
[Miscellaneous Android Development] IXgnas:
To answer your previous question, I could not find a changelog anywhere. The only thing that I know is that these updates upgrade your phone's OS from Kit Kat to Lollipop.
[Miscellaneous Android Development] drzhf9:
my phone is 6.0.1 now, experienced a wlan issue with some specific AP, so I want find if any solution to solve it, which might need to change the wlan driver, or wlan's firmware.

another question, any instruction to build the AOSP for this phone? thanks!

or any way to build the kernel/driver and to replace the original one? thanks a lot!
[Miscellaneous Android Development] IXgnas:
We (Matt and me) are currently trying to build AOSP. As for kernel, you need a Linux distro, a set of tools (Google it, their names aren't easy for me to remember) and the kernel from opensource.samsung.com
[Miscellaneous Android Development] drzhf9:
Thanks for your quick response. I saw your instruction to build AOSP, and failed to build the libpcre, migith be automake version issue, my OS is ubuntu 16.04 with automake-1.15, looks like need a lower version 1.14, is it true?
[Miscellaneous Android Development] IXgnas:
I'll PM you the invite to our Discord IRC. We'll discuss things there.
[Miscellaneous Android Development] Tomdroid77:
Unable to switch wifi on

Hi,

Have had a SM-G389F for just over a year and have been following this thread. Succesfully rooted my phone and also used Dev's kernel. All was going well till a week ago when I was suddenly unable to get the wifi to switch on. Have put stock firmware back on, tried deleting cache, tried everything including smacking the back of the phone as suggested in many forums. No success. Any ideas?
[Miscellaneous Android Development] IXgnas:
It's quite possible that your chipset's gone bust.
[Miscellaneous Android Development] Tomdroid77:
I can still use bluetooth. Would I be able to of the chipset had gone?
[Miscellaneous Android Development] IXgnas:
If the whole chipset went bust, then you wouldn't be able to use your phone in the first place. Probably the WiFi module is not contacting/fried/etc.
[Miscellaneous Android Development] thra1982:
Hi.

I've got the G389F and loaded TWRP on it.

Is the MyKernel flashable via TWRP or is Odin needed?

And for Xposed, 32bit or 64bit?

Thanks for the good work!

I know, rule number one no ETA's, but how is the custom ROM coming along? :o
[Miscellaneous Android Development] IXgnas:
Can't help you with XC3VE, but I can tell you that we slowly make our way to the proper compilation of the ROM. ETA: unknown ;).
[Miscellaneous Android Development] Oswald Boelcke:
If I read the following two posts by @Devhost97 correctly, a TWRP-flashable zip is available:

https://xdaforums.com/showpost.php?p=70815895&postcount=13

https://xdaforums.com/showpost.php?p=71338483&postcount=14

I don't own (yet) a G389F therefore unable to check myself, but when you to Settings => "About the phone", the telephone status contains a row called "CPU" and below its architecture.

armeabi & armeabi-v7a are 32-bit, arm64-v8 is 64-bit.

(https://developer.xamarin.com/guides/android/application_fundamentals/cpu_architectures/)
[Miscellaneous Android Development] thra1982:
Regarding the kernel, that would be my assumption too. But the zip doesn't contain any scripts, therefore my doubt. :confused:

Thanks.
[Miscellaneous Android Development] Oswald Boelcke:
The MyKernel1.2_r22.zip contains a .tar-file that again contains a boot.img

I don't know if it's sufficient as I'm obviously unable to try it (and I'd personally be quite suspicious) but I know you can flash .img-files through TWRP.
[Miscellaneous Android Development] IXgnas:
Discontinuation

After a short discussion with [MENTION=6318002]Matt07211[/MENTION] we are sad to announce that our efforts to port newer Android versions to this device are officially discontinued due to the lack of free time, not making any progress for a long period of time and devices' SoC having virtually no support or significance. I might still play around with porting (very improbable), but otherwise this project is pretty much dead. We're sorry :(.
[Miscellaneous Android Development] Matt07211:
Just to add onto this, I'll be cleaning up my this thread (My posts), making it more concise and to the point, and making it less confusing.

I'll also compile all the info of this device into a single place for anyone else interested :) All my sources are already online but I'll link it here.

Anyway there will be enough info and source code available, that once you ready what I've written you should just be able to pick up where I left off and continue if you so desire.

Expect to see these changes in a few days. I may push a few code changes, to fix the bugs that I have a decent idea on fixing, but don't expect anything.

I sadly never got to a finished compile, all the errors I encountered where so obscure that there wasn't any/much info on them.

I feel sad that I didn't finish but I have a lot less free time then when I started, and the task just started to get away from me.

SM-G389F - Samsung Exynos chipset, fully 32-bit

SM-G388F - Marvell PXA1903 chipset, chip but is 64 bit, but running a 32-Bit instruction set, you can verify this by running the "File" command on a system file/library as well as running "cat /proc/cpuinfo"

$ cat /proc/cpuinfo
Processor : ARMv8 Processor rev 2 (v8l)
processor : 0
processor : 1
processor : 2
processor : 3
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 half thumb fastmult edsp tls vfp vfpv3 vfpv4 neon idiva idivt
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 2

Hardware : PXA1908
Revision : 0007
$

And to be honest this tripped me up when trying to root the device as I was trying to use 64-But files when I really should have used 32-bit versions. This also increased the complexity of ROM compiling (You should see way in a few days once I've written up all the info)

Edit: Sorry for not checking this thread and keeping it updated, I just haven't been in XDA in a long time
[Miscellaneous Android Development] Matt07211:
I know I haven't delivered on the ufno I promised in my last post, mainly because my computer's been playing up on me, and losing what ever I was typing out when ever it freezes and requires a hard boot is very discouraging.

That being said, I'll be updating to the newest offical exposed since it should work with TouchWiz devices properly now, yay!
[Miscellaneous Android Development] pgunning1:
Hi everyone great thread this for a good phone, I've got TWRP installed ok and boot to it ok but when I flash SU I get and error as not verified :rolleyes: is this the google software preventing SU install or just incompatible SU Ive used the following to no avail...

SuperSU-v2.82-201705271822.zip

SR5-SuperSU-v2.82-SR5-20171001224502.zip

BETA-SuperSU-v2.49.zip

Feel I'm nearly there but just cant get SU installed using TWRP install, interestingly I tried to not reboot after TWRP fresh install but it wont let me comes up with not seandroid enforcing :p after reboot into system it'll allow into TWRP.

Any help get root would be much appreciated, just want to get rid of the junk samsung apps that are so memory hungry on this lovely little phone.

ATB
[Miscellaneous Android Development] pgunning1:
Hi I am really struggling with the SU install I keep getting signature failed with SR5-SuperSU-v2.82-SR5-20171001224502.zip the SU file is off the link at the start stating download from the SU link, is there an proper file thats compatible with the G388F on Lollipop 5.1.1. Didnt think this bit would be so tricky.

Any help appreciated.

ATB
[Miscellaneous Android Development] akuhak:
SuperSu and Magisk isn't compatible with Marvell PXA devices. The only way to get rooted - it is by using rooted kernel.

For example you can use mine kernel:

https://github.com/AKuHAK/xcover3ltexx_custom_kernel/releases
[Miscellaneous Android Development] pgunning1:
Ok thats fantastic, but does it matter if its for the LTE as mine is the normal Xcover3 G388F. If compatible I assume I flash with Odin or through TWRP, if by Odin are there any parameters like reboot only ect. if doing so.

Thank you for your advise it is much appreciated
[Miscellaneous Android Development] akuhak:
Its for old G388F. It is not compatible with VE and anyway SuperSu can be easily installed in value edition so I assume you have G388F. Just flash over odin: no wipes needed, all settings remain default :)
[Miscellaneous Android Development] Matt07211:
You can't flash SuperSU for the SM-G388F as it's unable to unpack the boot.img (I have requested support and all but Chainfire never got back). So you will have to make do with the provided boot.img I made where I setup all the stuff necessary by hand. Follow the instructions in the first page, look at the lollipop root section, it'll have all the instructs and files needed

Edit: [MENTION=7770482]akuhak[/MENTION] Does your custom Kernel drain the battery? Any compiled kernel I've made in the past bhas crazy battery drain, I think it's in relation to DVFS.
[Miscellaneous Android Development] akuhak:
I don't know why but battery drain dissappear after I removed imsservice.apk :) I think that this is not kernel issue but root issue or xposed framework issue...
[Miscellaneous Android Development] pgunning1:
Hi and thank you Matt07211 for the info I have tried the rooting method suggested on the front page but I am having trouble with pushing the files across through ADB it says it needs java to run, Ive installed java on a Win 10 pc but ADB wont run as it says Java not installed - but it is. So I can't push SU files across to the phone, this i why I was trying the Odin root.

Great question ...

Edit: [MENTION=7770482]akuhak[/MENTION] Does your custom Kernel drain the battery? Any compiled kernel I've made in the past bhas crazy battery drain, I think it's in relation to DVFS.

If flashing this wont cause hardware issues then thats brilliant but if its going to drain battery life then I cant go with that method.is imsservice.apk an important app??? as its been removed from this kernel I assume battery life is unaffected, but what does this apk do then. :confused:..

Any confirmation the the above would be fantastic or how to push those files ADB on a stupid Win 10 pc would be great.

ATB
[Miscellaneous Android Development] pgunning1:
It appears that imsservice.apk is the texting app which I cant do without,so I'm a bit stuck with trying to get Java working so I can push the ADB files across as the phone isnt recognised through the dos prompt search.

Any thoughts or help on this appreciated

ATB
[Miscellaneous Android Development] akuhak:
I removed imsservice.apk and I didnt get any problems with phone: I can sms and make calls and whatever I want.
[Miscellaneous Android Development] Matt07211:
You shouldn't need java :(

Download the appropriate package from here, https://developer.android.com/studio/releases/platform-tools.html

Unzip the file, go to the directory that adb.exe is in, hold shift and right click "Open Command Prompt Here" now you should be able to run ADB commands from the current directory.

E.g. adb.exe devices

Mind telling me what you try and give me the specific error messages, even a screenshot would help.
[Miscellaneous Android Development] pgunning1:
DONE managed to get root thank you all so much a few issues on route as win 10 needs cmd line admin rights to run and detect phone, the phone needs to be on, and hadnt realise that when adb called on the phone it needed permission from the phone to write to it, so had to click ok on the phone, never had that before. Got that sorted got root, but security on the phone says threat found unauthorised actions have been detetced... on the phone reboot to fix, when I do so, android icon comes up and does a system update then boots up. The phone works fine but this message keeps coming up ??? Anyone else have this...

Also slightly off topic I know, can I remove S Calendar without issue and launcher3 is 200mb can this be taken out to as I use smart launcher pro or is it an intregal part of android, cause its massive on a memory limited phone.

Big thank you again for helping with root, hopefully I may be able to assist with my experiences in getting there with others also. :)
[Miscellaneous Android Development] pgunning1:
Does anyone else have the security warning come up once the phone is rooted? And can launcher3 be removed or does it kill the standard rom.

Any help again appreciated with this.

ATB
[Miscellaneous Android Development] Matt07211:
I personally only had it come up once when I was experimenting with stuff. But in my normal use I haven't had it trigger (I think it was because I was Flashing between official and unofficial)

Quick and simplest fix is to disable Smart Manager
[Miscellaneous Android Development] yuyumen:
Many thanks. I have been desperately searching in many forums and this solution is the only one that has worked for me. Congratulations for your work and thanks again.
[Miscellaneous Android Development] Palawan-Taucher:
my SM-G388F turns off randomly after upgrade to 5.1.1

Hello,

after some tests last year, i stayed in 4.4.4, becorse low Speed and low RAM on my SM-G388F.

Now this year i have to change for a app ... all like page 1 , no problems , root, Google Apps deactivated or deleted ...

But some times the device turns off randomly, and i cant ON again. Have to take out the accu and the to reboot ...

After 1 week with OFF's every day and more then 3 times a day ... i give a other Kernel a chance ... not good.

Back to the root-Kernel of Page 1 , i dont have until now no OFF's anymore. ????:silly::silly::silly:
[Miscellaneous Android Development] Matt07211:
I really couldn't make sense of this paragraph.

Sounds like a hardware problem.

The boot.img (kernel) attached to the root package on the first post is the stock untouched kernel, so you shouldn't see any more battery drain then normal
[Miscellaneous Android Development] Palawan-Taucher:
Hello Matt07211,

i am playing with the 5.1.1 stock-ROM and try to minimise the used storage, not so easy.

Using the 4.4.4 i never had OFF's , some reboot's from time to time , yes.

But a complete OFF and not starting again, i never had, but maybe it is a "sleep and freeze" with the 5.1.1 ?

I have to take out the battery, to start again, with 4.4.4 i can restart with Power Button ...

With 5.1.1 i also suffer some times the "TouchWiz-Start stopped" Error ... on 4.4.4 never ...

but the battery drain is ok, other kernel i tryed for the self OFF problem, not becorse the drain, with stock Kernel is the drain ok...
[Miscellaneous Android Development] KenSt.Mich:
Hello,

I am writing because I ran into a serious problem trying to flash firmware onto a SM-G389F.

I think I forgot to tick "allow USB debugging" before the process.

Odin failed to copy the .md5 (always right before completion).

On boot up, the phone goes to a blue screen with an error message to use smartswitch for emergency recovery.

I've tried to use smartswitch and kies (also odin a few more times) but to no avail.

Smartswitch and Kies will report error there is no such recovery number when using the code SM-G389F.

For now I am stuck with a bricked phone.

Any help will be much appreciated
[Miscellaneous Android Development] Palawan-Taucher:
Hello KenSt.Mich,

you dont need USB debugging for Odin Mode, (Volume down + Home + Power)

Be sure, to have a perfect downloaded and the right file,

i have this case before flashed a corruped file in to a brick ...

only the "Auto Reboot" and "F. Reset Time" set in Odin Options,

select your file under the "AP" , after this, it have to look in the Log like this:

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

now you can flash ... good luck,

You must go in the recovery with (Volume up + Home + Power)

and you have to wipe cache and wipe data/ factory reset !!! to clean your phone !!!
[Miscellaneous Android Development] KenSt.Mich:
Thanks!

I'll try another firmware when I get home.

(Might have gotten one for a different area. Could this be the cause of the failure?)

You said I'll have to wipe cache/ clean data and do the factory reset.

How/ where can I do this?

The phone doesn't give any options but downloading/ flashing firmware or rebooting (with the according error message).

Thanks again
[Miscellaneous Android Development] Palawan-Taucher:
Hy,

first of all, you have to bring your phone in to the Odin Mode .... https://youtu.be/L2WwR0qzK7E

You have to OFF the phone ( take out the battery and push Power for 1 minute, if it not work well ),

then push the "Volume Down" button

together

with the "Home" button and keep them pushed togeher !!!

now push the Power button for some seconds,

until it shake ... keep pushing the Volume Down + Home ... release the Power buttun

ATTENTION now release first the Volume Down , after this the Home, else you jump forward ... wrong way

push now the Volume Up for the Odin Mode (also called "Downloading ..." , dont know why ...)

now you can connect your phone by USB to your PC and it should be vissable in Odin

it have to look somehow like this, depending to your phone and ROM file

For Reset and Factory Wipe look here : https://youtu.be/kkNEv3SAZSE

You can try this before flashing new ROM, but if it is bricked, flash before Wiping ....
[Miscellaneous Android Development] KenSt.Mich:
Thanks again.

I´ll do that with another Firmware later.

(Did everything with Odin before exactly as in your instructions)

Will flashing and wiping data this way make sure there are no software backdoors (other than Samsung´s...) or spyware apps on the phone?

This is the reason, I tried flashing firmware in the first place, as the phone is has been given to me by a company (and due to the sensitivity of my work, I want to be sure.)
[Miscellaneous Android Development] Matt07211:
Sounds like you had a corrupted download and ignored the errors and decided to proceed Anyway.

Simple fix, I've ran into the same problem before, all I could do was access the emergency screen and Kies was no help. So I did something simple and flashed the stock firmware package from Samsung and it booted up. Emergency mode is just Odin mode with a slightly different look Basically, so you should be able to flash stock firmware fine

In think I get what you say. Samsung basically didn't put in any effort to optimise Lollipop for the phone, so you are going to have degraded performance over KitKat. And I to have also suffered a full lockup as well, I believe it happens when available ram runs really low. I believe lollipop was known for horrible memory leaks when it was released
[Miscellaneous Android Development] KenSt.Mich:
Hello Matt,

WinRar and Odin did not give any error reports on the file.

The problem was just the "download" resp. file transfer onto the phone stopped right before completion.

I think it might be because the firmware was for a different area and service provider than the phone. Is that possible?

Anyways, I´ll try to flash an original firmware for the according area and provider but so far the (internet) downloads keep failing. I can´t seem to find a reliable source:crying:

(That´s why I did not post so far...)
[Miscellaneous Android Development] Matt07211:
Hmm, where are you downloading it from?
[Miscellaneous Android Development] Palawan-Taucher:
... reliable source ...

try to take a look here :

https://samsung-firmware.org/

select your right modell, also your region, and take a look ... maybe they have some thing for you ... :fingers-crossed:

I found out, than there are 1 ROM / Firmware 4.4.4 and 2 Versions of 5.1.1 for my region

maybe i will have a next try for the newer one ... :confused::silly:

good luck :good:

edit: my 5.1.1 version from 2016 is more then 1 year older then the newer from 2017, i have try this !!! wish me luck ...

PDA/AP Version G388FXXU1BQC2

CSC Version G388FDDX1BQD1

MODEM/CP Version G388FXXU1BPJ1

Region DDE — Germany

Build Date 2017-03-24

Changelist 986472

OS Lollipop

OS Version 5.1.1

946.82MB
[Miscellaneous Android Development] Palawan-Taucher:
Hello all,

so i give a try for 5.1.1 on my SM-G388F again ..

I flashed a new clean stock ROM 4.4.4

then i let XCover3 update him self by

over the Air updates, 3 times before finish.

edit: Then i found out that the OTG is not working. / edit

OTG works, maybe a reboot problem ...

BUD ... i still have from time to time a strange self OFF, the phone off's by self and cant be ONed again.

i have to take out the accu ....

some one else have this too ???
[Miscellaneous Android Development] Palawan-Taucher:
Hello all there !

I need help.

I still have this "OFF" problem.

My SM-G388F with "stock" 5.1.1

is going OFF by him self.

Have it made like on page 1. Rooted.

Battery is 90%, "no" app is runing,

charging or not , same same ... off ans out.

No Charge when pluged, no reaction at all.

All Apps , i dont need, are taken away.

No running out off space. ...

When it is "off", i can not ON it,

using the Power button,

i have to take out the battery.

And i do not think, that it is a hardware problem

(exept the Xcover3 him self is already one !!!)

becorse with 4.4.4 this is never happen

for the last years i let it run

without the update to 5.1.1 .... :crying:

So, and now you tell me, what is going on ... ;)
[Miscellaneous Android Development] Matt07211:
I'm having trouble trying to understand what your saying, can you try explaining it differently or provide a video?
[Miscellaneous Android Development] IXgnas:
Download the good old KitKat firmware, back up all the data that matters and flash the ROM. Next time, try to be clearer about your problem ;)
[Miscellaneous Android Development] akuhak:
I think he means deep sleep issue, when phone cannot wake up. Probably kernel issue try to use newest firmware. Or better flash mine xustom kernel.
[Miscellaneous Android Development] Alexr00t:
5.1.1 Root with new TWRP 3.10

surely there has to be some progress on getting root with Lollipop on this device? i have the original model that is locked to Vodafone UK. I seriously need to use DriveDroid which requires root and i use it for booting ISO's. i found a new version 3 TWRP recently released has anyone tried it?

twrp-3.1.1-0-xcover3ltexx.img.tar is the new version i found.