[8.1] EDOs Oreo (Prerooted and Debloated)

[snowbird30ds]

Doh missed that bit.
I'm having trouble trying to copy it into system/etc folder, any useful hints? adb push has failed and adb shell keeps crashing out on me.

 

[snowbird30ds]

Managed to get mixer_paths.xml into /system/etc through shellafter messing about with permissions but still no sound through headphones, plays fine through speaker and cuts out when headphones are plugged in, any ideas where I'm going wrong?

Edit:
After reboot no sound at all from anything, not even phone calls, now restored to previous through twrp but still no headphones.

 

[fetaiharbin]

Managed to get mixer_paths.xml into /system/etc through shellafter messing about with permissions but still no sound through headphones, plays fine through speaker and cuts out when headphones are plugged in, any ideas where I'm going wrong?

Edit:
After reboot no sound at all from anything, not even phone calls, now restored to previous through twrp but still no headphones.

Just move it with a file manager, Solid Explorer for example.

 

[snowbird30ds]

Just tried it again and all seems to be working fine, obviously an afternoon in the pub is what was missing in the original instructions...
Thanks to all for the help.

 

[Alvin50]

A weird behaviour

Hi all,
I have to report a weird behaviour after installing the january path version (EDOs_J5_J7_OREO_withJanuaryPatch) on my J530F.
Before (and presently) I'm using a M1AJQ.J530FXXU4BSC2 , armv8I, kernel 3.18.14-14928722-QB22612223, with TWRP 3.2.3, rooted and with Magisk Manager 7.32 and Magisk v.19.3, that I partially debloated myself.
Before installing the aforementioned firmware I made a backup of my present system and then wiped out all to factory.
After flashing the zip all went flawlessly, it rebooted normally and I could enjoy that new firmware but... BANG! Some minutes later, as I pushed the power button to recall the time-turned off display, it came on with a wrong frequency setting, giving a two-three times reproduced jumping image of the normal screen, That, of course, also involved the touchscreen, and I had troubles to shut off the phone. But things got worse when I tried to restart with TWRP recovery: it was nearly impossible to swipe. At last I succeeded in restoring my backup, and after a pair of resets the damn thing ceased and the display reverted to normal behaviour. I have to stress that I didn't apply the other suggested operations, as that time I was only aware of the discontinued page on this subject that did not mention those operations, and discovered this new thread only later. I'm not afraid to say I got into panic to the point to not remember the simple procedure to use Odin (I forgot to put it into download mode...) as it appeared I had lost any control on the phone... Now I would retry, so I ask if the subsequent suggested operations like flashing HeliosPro_Kernel_V2.7-TW and mixer_paths could cure this issue.
Thanks in advance for your help

 

[Jens956]

Hey. Will this support an update to android 9 whenever it comes out for my samsung j530F?

I dont want to lose all my data if i have to go back to stock/differend ROM which would support android 9..

 

[Alvin50]

Hi all,
I have to report a weird behaviour after installing the january path version (EDOs_J5_J7_OREO_withJanuaryPatch) on my J530F.
Before (and presently) I'm using a M1AJQ.J530FXXU4BSC2 , armv8I, kernel 3.18.14-14928722-QB22612223, with TWRP 3.2.3, rooted and with Magisk Manager 7.32 and Magisk v.19.3, that I partially debloated myself.
Before installing the aforementioned firmware I made a backup of my present system and then wiped out all to factory.
After flashing the zip all went flawlessly, it rebooted normally and I could enjoy that new firmware but... BANG! Some minutes later, as I pushed the power button to recall the time-turned off display, it came on with a wrong frequency setting, giving a two-three times reproduced jumping image of the normal screen, That, of course, also involved the touchscreen, and I had troubles to shut off the phone. But things got worse when I tried to restart with TWRP recovery: it was nearly impossible to swipe. At last I succeeded in restoring my backup, and after a pair of resets the damn thing ceased and the display reverted to normal behaviour. I have to stress that I didn't apply the other suggested operations, as that time I was only aware of the discontinued page on this subject that did not mention those operations, and discovered this new thread only later. I'm not afraid to say I got into panic to the point to not remember the simple procedure to use Odin (I forgot to put it into download mode...) as it appeared I had lost any control on the phone... Now I would retry, so I ask if the subsequent suggested operations like flashing HeliosPro_Kernel_V2.7-TW and mixer_paths could cure this issue.
Thanks in advance for your help

Well... in my opinion, if one would have to reply, I think that waiting three days long were enough...
So I have to conclude that the lack of a reply is caused by:
a) my question is so irrelevant that never minds
b) no one knows the answer
c) no one is interested in answering that
Consequently I'll manage to solve it myself at my own risk and then post what happened.

 

[Alvin50]

Well... in my opinion, if one would have to reply, I think that waiting three days long were enough...
So I have to conclude that the lack of a reply is caused by:
a) my question is so irrelevant that never minds
b) no one knows the answer
c) no one is interested in answering that
Consequently I'll manage to solve it myself at my own risk and then post what happened.

Update: after a new retry, performed identically as before, and adding HeliosPro_Kernel_V2.7-TW.zip immediately after flashing EDOs_J5_J7_OREO_withJanuaryPatch.zip and then rebooting, also moved new mixer_paths.xml to etc, the problem stays unchanged. Display vertical frequency appears unlocked, spanning to 3-5 times its correct value every time the display comes back after a timeout. very difficult to hit the "reboot" or "shutdown" symbols, as they jump happily all over the screen... Anyway, after a reset, the isssue disappears until the first screen timeout.
This time, despite the initial jumping screen, the display then stabilized once entered into TWRP, allowing a more comfortable restore than the previous time. Anyway, when restore completed and was necessary to swipe to unlock the screen and reboot, there was again a touch issue that lent to a nightmare of false hits very difficult to control and finally end up to boot. After finally restoring my backup, I feel very frustrated. Never faced such problem before. There shall be somewhere a piece of code that jumps on when there is a screen recovery from timeout that uses incorrect values for vertical frequency. Is there a way to determine whether the applied parameters are for J530-F or for something else?
I did my homework...

 

[Shahin Sharukh]

Does It support on J5O0G version?

 

[snowbird30ds]

Any news on updates or security fixes for this version?

 

[snowbird30ds]

Can this version do wifi calling? I think the phone supports it but can't find a setting.

 

[wavedevice]

Please someone have a mirror of this ROM?
All the links are broken

 

[Nikkerston]

Any news on updates or security fixes for this version?

No because its Android 8.1 and Samsung experience 9.5 so it will never get anymore security patches after One UI was released for this phone

 

[Remix os user]

the link does not work...

 

[Nikkerston]

the link does not work...

hasnt for probably YEARS