yashsingh1/xdaforums huggingface dataset:
[MTCB Android Head Units General] TiberiusGavier:
[MENTION=8888674]lorrys[/MENTION]

I'm glad that fixed it for your system - I will look for an update to the Ownice unit but I don't believe they have one to go to Android 7.1.2

I did find a solution that essentially makes the problem almost disappear. If you have an Ownice C500+ unit, go into Settings, enter 1260 as password to go to hidden settings, enter the volume area, make all of those values as low as they can possibly go. Some of those will be in the negative. When you reboot the system, the sound is essentially inaudible and that solves the problem.
[MTCB Android Head Units General] NeoConker:
I have the same issue but with Toyota version of the unit. Can you share the update?
[MTCB Android Head Units General] veriluxxxx:
i think the issue is the am/fm antenna, get a noise filter antenna adapter, might solve the issue
[MTCB Android Head Units General] An92:
hi, I have an eonon ga8161, it would be hct px3 7.1 if I'm not mistaken.

I also have the background volume problem, but it is almost inaudible.

the most obvious problem is a rustling metallic type rustling noise, which is heard when there is processing from a USB device, both pendrive and USB dashcam ... someone has had this problem, because it is very annoying
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Unofficial release -TWRP recovery for the Galaxy A3 - SM-A300F/FU/G/H/M, Qualcomm MSM8916

https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html

*SEANDROID warning fix

*Recovery reboot fix

*MTP fix

*Modem, APNHLOS, EFS and Recovery partition backup

You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.

Instructions:

Flash with ODIN 3.10.7 in the AP slot:

Uncheck Auto reboot.

Load the respective file below into the AP slot and hit start.

After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.

As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.

You should now see TWRP recovery.

Flash with TWRP:

Extract the recovery.img from the tar archive then in TWRP select Install>>Install image.

twrp_3.0.2-1_sm-a300

twrp_3.3.1-2_sm-a300x_101119

PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST

To Root:

I suggest using Magisk as its a currently up to date project. Supersu is no longer maintained:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

DEVICE TREE: soon

NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:

Settings -> Developer Options -> OEM unlocking

AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.

Credits: Me, Teamwin and my testers- icesehman, -CALIBAN666-, jimbomodder

Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.

FEEDBACK IS APPRECIATED PLEASE.

THANKS.

DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

.

.
[Galaxy A3, A5, A7, A8, A9 Android Development] King-V:
Hmm... could this maybe be flashed with Flashify?
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
It could, but better to flash it with TWRP or ODIN.
[Galaxy A3, A5, A7, A8, A9 Android Development] King-V:
Wait... what? Flash this version of TWRP, using an older version of TWRP? Does that really work?
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Of course it does, it's been that way since about version 2.8.6.0
[Galaxy A3, A5, A7, A8, A9 Android Development] King-V:
Never knew that; it sounds quite handy... Thanks a lot!
[Galaxy A3, A5, A7, A8, A9 Android Development] PlutoDelic:
Well, i wish we had 5.1.1...

Thanks a lot btw.
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
You don't need 5.1.1.
[Galaxy A3, A5, A7, A8, A9 Android Development] PlutoDelic:
Obviously.

I stumbled on an issue. TWRP boots fine, but no touch input. Reboot issue seems to remain IF one "reboot to recovery" from the system. Everything works find under the hood, connected through adb without any issue.
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Which device model?

Can you post the recovery.log file?
[Galaxy A3, A5, A7, A8, A9 Android Development] Duke2010:
hi community,

first of all very big thanks to [MENTION=4899305]ashyx[/MENTION] to support our device and port the new twrp :highfive:

i can confirm that the recovery start without problems after flashing with android 5.0.2 but sadly maybe the touchdriver not loading. touch have for now no function :confused:

my device is the a300fu with touchwiz stockrom and baseband boj4.

[MENTION=4899305]ashyx[/MENTION], please fix the problem with touch and maybe all will be good :cool::highfive:

best regards and thank's for support our community :highfive: :good:
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Yes I'll fix the issue, but I need someone to upload the recovery log from cache/recovery/last_log
[Galaxy A3, A5, A7, A8, A9 Android Development] PlutoDelic:
A300FU

Attached.

Reflashing the .tar weirdly gets rid of the reboot to recovery issue, wonder if any flag is being reset...
[Galaxy A3, A5, A7, A8, A9 Android Development] Duke2010:
hi folks,

i send my logfile too. well done :highfive:

best regards :good:
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Does this fix the touchscreen and reboot issue?

https://www.androidfilehost.com/?fid=24499762636004631
[Galaxy A3, A5, A7, A8, A9 Android Development] Duke2010:
sorry, no my device stuck into boot recovery process. it is not possible to booting up into recocery. :crying:

try again please :highfive:

thank you and best regards :good:
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Please post your device model.
[Galaxy A3, A5, A7, A8, A9 Android Development] Duke2010:
Hi mate,

My device is the a300fu with boj4 bootloader and boj5 touchwiz stockrom ;)

Best regards :good:
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
First of all Thanks for your work!

I´m also on the A300FU Device :rolleyes:

With the TWRP from OP, I confirm TWRP starts but Touch is not working (Log old)

With the "Fix" it stuck bevor TWRP Screen should appear (Log new) btw. flashed both with Odin
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Looking at the recovery log it seems there is an issue loading the graphics, so I have reverted one of the flags that I think is causing the issue.

https://www.androidfilehost.com/?fid=24499762636004909

NOTE: I will not support any posts related to flashing with Flashify, this app has issues with some devices. ODIN(prefered), TWRP and the DD method is fine.

.
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Yep, but it won't mount it as there is no kernel support and I don't intend to add it.

For what reason do you need f2fs support?
[Galaxy A3, A5, A7, A8, A9 Android Development] carlos974:
I would have liked as for my other two devices to use f2fs for Data and Cache (faster write)

Decompiling I saw that the fstab.qcom file was missing.

Thank you for the information and your excellent job :good:
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Tbh I used to add it, but dropped support for it as it was causing issues, particularly where root was concerned.

Patches were needed to get it to work properly and in the end I couldn't be bothered messing about.

The gain is so small, if any, it just wasn't worth the hassle.
[Galaxy A3, A5, A7, A8, A9 Android Development] Beatz106:
Can I install it over the current TWRP, or some app like Flashify or must be directly from PC???
[Galaxy A3, A5, A7, A8, A9 Android Development] carlos974:
Yes in current twrp: install image --> recovery
[Galaxy A3, A5, A7, A8, A9 Android Development] Beatz106:
Great, thanks
[Galaxy A3, A5, A7, A8, A9 Android Development] Hyperhamster534:
I'm very late to the party here but recently dug out my old A3, did anyone ever solve this bootloop issue short of just reflashing TWRP? For me it takes effect any time you enter recovery - including factory reset from android (LOS 14.1 in this case).
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
With this new File it Boots into Recovery but Touch still not Working.
[Galaxy A3, A5, A7, A8, A9 Android Development] Duke2010:
hi,

yes now all is how in your first release. the recovery start but no touch work :confused:

i have attach the logfile...

well done ;)

best regards :good:
[Galaxy A3, A5, A7, A8, A9 Android Development] PlutoDelic:
As others reported, no touch yet. I think graphically everything is right as it locks properly with the power button and the initial effect of the slider animates.

Also, after cold rebooting with Power + Vol Down from recovery, it boots to the system, so the reboot back to recovery bug is definitely gone. :)

log attached.
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
This touch issue has me a little perplexed. I have come across this issue once before and it was a dtb issue. However as far as I know I have the correct kernel and dtb for the FU.

Does anyone not using an FU model have this issue?

Also could someone perform a test and boot to recovery then leave it for a couple of minutes or at least until the screen times out and see if the touch screen starts working?
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
I used your last TWRP Display out after ~45 Sec and i wait ~5 Min before i touched the Device, but no change.

Edit: I shared your last Post in the Everything Samsung a3 Thread :p
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Hopefully this one fixes it: https://www.androidfilehost.com/?fid=24499762636005290
[Galaxy A3, A5, A7, A8, A9 Android Development] Duke2010:
yes mate, you are the hero of the day, congratulations :highfive::good::highfive::cool::D

your ported twrp-recovery boot up and work famous, touch works flawless . i have tested the recovery and the most important features works like a charm but only one thing is failed.

sadly the MTP-mode is not right work, i hear the usb-connection sound into the twrp recovery but the device is not shown in the pc explorer.

whatever mate, thank's for your fantastic work :highfive::good::highfive:

please support our community again, it's a honor for us :cool: ;)

maybe you are be interested and want invest sparetime to port the newest RR to our device A300(FU) ;)

best regards and thank's a lot :good:

cheers
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
This is my New Recovery it´s Nearly perfect!

Tested, Flashing CM12.1 & CM13, Recovery & Backup, Partition SDCard all work Perfect

The only thing i missing is MTP in TWRP, at Mount -> Disable and Enable MTP

MTP Enabled didn't show anything and Disable show me a SAMSUNG_Android device but PC found no Driver also the Samsung Drivers didn't help, any advice?

btw. this will also not work in TWRP 2.8xx & 3.0.0.0
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Yes I know what the reason is. I can fix that, but I just wanted to get the recovery working good first.

MTP disabled puts it into ADB mode that's what SAMSUNG_Android device is.
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
Now you are the hero of the day for me too :D
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Does this fix MTP?

https://www.androidfilehost.com/?fid=24499762636006091

.
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
No it's not different to Previous build

Tested with Win7 Driver update and Samsung Drivers

Did you need log?

Edit: Attached Log
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
MTP is working according to the log. The issue is with your PC.

You need to make sure you have the MTP driver installed in device manager.

Enable MTP then reboot your device to recovery.

Look under portable devices in device manager, you should see your device listed.

If not you dont have the drivers installed correctly. If you see a device with an exclamation mark then you will need to manually install the MTP driver.

Right click the device and manually install from the driver list. Look for MTP USB device.

If it's listed as a Samsung USB device then it is using the ADB driver instead of MTP.

Again you need to change the driver manually.
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
That´s it!

It was showing a Google Nexus ADB Device, I have changed it Manually and bingo

Perfect

many many thanks you are Great :good:
[Galaxy A3, A5, A7, A8, A9 Android Development] Duke2010:
hi [MENTION=4899305]ashyx[/MENTION],

i can confirm with your newest release the MTP-mode work now flawless. i flash it and connect my device to pc with Windows 10 Pro. immediately displayed on the screen that my device is connectet and i can see my phone on the explorer with internal and sdcard memory.

i have test the whole recovery and all work's perfect :cool::D:):o

thank you again for your glorious work :highfive:

now the way is free to flash ( i hope soon ) CM13 ;)

the MPT-mode over the recovery is currently a good workaround for the buggy Galaxy A300 CM12.1 + RR ( usb ) and storage mounting procedure :good:;)

well done [MENTION=4899305]ashyx[/MENTION]

hope we see you next time again in our A300(FU) forum with further good news :highfive::)

best regards :good:
[Galaxy A3, A5, A7, A8, A9 Android Development] King-V:
Works great now. Thanks a lot!
[Galaxy A3, A5, A7, A8, A9 Android Development] zuhaibsarwar:
Any guide how to fix touch input in latest twrp3.0.2.1 in a3 h variant
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Are you saying you saying touch isn't working on the a300h?
[Galaxy A3, A5, A7, A8, A9 Android Development] zuhaibsarwar:
Ya on latest twrp 3.0.2.1
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Please post your recovery.img
[Galaxy A3, A5, A7, A8, A9 Android Development] Intel777chanel:
I have A300H too and everything works fine(im not tested MTP and Sideload yet).
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Make sure you have the latest build.
[Galaxy A3, A5, A7, A8, A9 Android Development] Intel777chanel:
A300H, MTP/Sideload not works. It's not works on any custom rom, others twrp versions, it seems that a3h and a3f have different usb devices. Pc even don't see target device.

>lsusb output:

root@debian:/home/intel# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
It will, follow the instructions in post 33.

You need to go into device manager and install the MTP driver manually then the PC will detect it.

It works on every Samsung device I have built TWRP for.

MTP needs to be disabled for Sideload to work.

Can you post your recovery.log?
[Galaxy A3, A5, A7, A8, A9 Android Development] Intel777chanel:
Debian doesn't have something called "Device manager" as well as no needed an any driver to MTP works.

I posted output of lsusb command to show you that it even no recognized as device at all.

View attachment recovery.log
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
This is more related to the PC than the device.

I have seen that MTP error in the recovery.log on both Windows and Ubuntu.

It's a USB descriptor malfunction which is why you don't see the device listed with lsusb.

Connect your device to the PC then reboot into recovery with MTP already enabled.

That usually fixes it.

If not then disable then quickly re-enable MTP.
[Galaxy A3, A5, A7, A8, A9 Android Development] manfredo16:
Not work infinity bootloop :( in samsung logo in my A300H with Lollipop 5.0.2 is the dual sim version
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Not working for you but working for intel777chanel. Doesn't make sense.

How did you flash?

Can you send me the recovery.img for your device.
[Galaxy A3, A5, A7, A8, A9 Android Development] PlutoDelic:
dont mind him actually, samsung has been uberweird with A Series phones and their variants meaning. Just look at A300F and A300FU, FU has more RAM, and is a single sim solution, where as the F is meant for dual sim. But recently, we had someone with A300FU Duos, two sims. The person reported to be incompatible with the usual FU stuff share here.

Now seriously, it's just Samsung being Samsung.
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Samsung are weird full stop. There doesn't seem to be any consistency in anything they do.
[Galaxy A3, A5, A7, A8, A9 Android Development] Josehp7908:
Twrp 3.0.2.1 sm-a300m duos

I not speak english....

Sorry.

my question is if this serves the sm-a300m duos
[Galaxy A3, A5, A7, A8, A9 Android Development] MpandAUS:
No bugs reported for A300Y/A300FU as far I'm concerned, downloaded the latest one and it works well without any bootloops. I flashed the recovery.IMG through TWRP recovery. Cheers [MENTION=4899305]ashyx[/MENTION]
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
I found 2 more bugs for the FU Device

First i can't Install CM12.1 Resurrection Remix the unofficial CM12.1 and CM13 are installing flawless

Patching system image unconditionally...

could not detect filesystem for /dev/block/

platform/soc.0/by-name/system, assuming ext4

mount: faild to mount /dev/block/platform/soc.0/

by-name/system at /system: No such file or

diractory

unmmount of /system faild; no such volume

Flashing SuperSU...

could not detect filesystem for /dev/block/

platform/soc.0/by-name/system, assuming ext4

mount: faild to mount /dev/block/platform/soc.0/

by-name/system at /system: No such file or

diractory

unmount of /system faild; no such volume

Script succeeded; result was [0.200000]

Updating partition details....

....done

Second is OTG is not Working if i tab OTG (with conected Device) nothing happens, also the USB Stick is not Blinking
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
OK 2 things. It is the installation script that is at fault not the recovery.

Number 2. The kernel needs to support OTG for OTG to work.
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
Hi you are replying so fast :)

ok i can install RR with TWRP 2.8.7.0 so it´s no Problem

Can you Fix the Kernel? In TWRP 3.0.0-0 is OTG Working or is the Kernel for 3.0.2-1 so different?

Sorry for that Noob Question :)
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Try this first.

Disable MTP. Reboot to recovery, plug in OTG device. What happens?

Post the recovery.log.
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
Tried a few restart from Recovery to Recovery with Device Plugged, unplugged always with MTP disabled ,nothing happens USB stick did´n Start Blinking and i can't choose OTG

Thanks for your Support :)
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
I have rebuilt the kernel and added a flag for OTG support. See how this works? https://www.androidfilehost.com/?fid=24533103863139517

Also are you saying that it works in TWRP 3.0.0-0?

What do you mean by this statement?:

The mount path in the install script is completely wrong, so it won't install.

It should be: /dev/block/bootdevice/by-name/system
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
If the above doesn't work try this one out. https://www.androidfilehost.com/?fid=24533103863139553
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
Sorry it wasn't offensive meant, RR is for the FU Device atm the Best working ROM, and i don´t have to install everyday the ROM so i can switch easy to 2.8.7 to Install the ROM and back to use your realy nice Recovery,and i can only tell you the install process is working in the other Recovery.

I´m not a Dev i´m just curious ;)

GOD you are faster than Light :p

trying out now ^^
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
No Change Sorry

Tryed both Builds with Reboot from Recovery to Recovery with MTP disabeld
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
There's something odd going on here.

The link to Twrp 3.0.0-0 that you posted is using the kernel and ramdisk from the A5 :confused:

I will build twrp 3.0.2-1 with that kernel for you to test, but you will lose mtp support.

Don't worry I wasn't having a go I was just confused when you said it works in twrp 2.8.7.0.

Tbh that should be impossible, the mount points the install script is using are completely wrong.

You can't install to a non existent location.

Any chance you could pull the installer-script from the Meta-inf folder and post it to pastebin.com?

I need to see this for myself.
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
Hmmm OK that explane a lot :D

Very kindly thanks a lot

Edit:

If you tell me how to pull the installer-script (or link me a guide) i will do it
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Here you go, built with the A5 kernel: https://www.androidfilehost.com/?fid=24533103863139631

To pull the updater-script. Install 7-zip, right click the installer zip, select open archive, navigate to META-INF\com\google\android\updater-script then just drag it out.
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
Yes OTG is working BUT i can only Install CM13 same bug like in TWRP 3.0.0-0 look here and your Response

and the updater-script from RR

btw. Update 7-Zip I Read this hint in a German Blog yesterday
[Galaxy A3, A5, A7, A8, A9 Android Development] ashyx:
Wow this gets crazier by the minute!

A kernel for a different device allows it to support OTG, but its own kernel doesn't? wtf?:confused:

Ok I can fix the device properties.

I will compile the a500fu kernel and use that in TWRP.

As a side note does OTG work when booted to the OS on your device?

Also I have looked at the updater script. There is no way that RR is installing on your device using either 2.8.7.0 or 3.0.0.-X. Are you absolutely certain it installs and you can boot to it?

The script uses the wrong mount points. It would be totally impossible for the script to mount the system partition using those mounting points. Are you absolutely sure that RR actually installs as even in the image you posted of the install of RR with 2.8.7.0 it flags a mounting error at the end?

See below, these are the mount points for your device from the stock recovery:

/dev/block/bootdevice/by-name/boot /boot emmc

/dev/block/bootdevice/by-name/recovery /recovery emmc

/dev/block/bootdevice/by-name/system /system ext4

/dev/block/bootdevice/by-name/userdata /data ext4

/dev/block/bootdevice/by-name/cache /cache ext4

These are the mount points in the script which are incorrect:

mount("ext4", "EMMC", "/dev/block/platform/soc.0/by-name/system", "/system", "");

mount("ext4", "EMMC", "/dev/block/platform/7824900.sdhci/by-name/userdata", "/data", "");

There is even a conflict with the mount points for system and data, they should both be the same!

If you type the following into an adb shell or terminal app you will see the partition mounts.

su

mount

Also if you type the following it should list the block mount points:

su

ls -l /dev/block/bootdevice/by-name/

If you could post the output then we can see for sure.
[Galaxy A3, A5, A7, A8, A9 Android Development] Jonny_Hood:
Edit: Ohhh in OS not but it was Working promt while booting up Recovery

but it does start working (USB Stick starts Blinking) while Booting up in [MENTION=6446790]mygalaxya[/MENTION] (same Dev from TWRP 3.0.0-0) CM13 but the ROM is still alpha for the FU Device and Crashes after boot

Sure a few people using it, actually it is atm the Best CM ROM for the FU Device xD

I have zero coding skills, the most of it is like chinese for me sorry (I wished i had some skills)

I didn't find a quick solution to printed as text so i made 2 screenshots