Search results

+1 LOS-14.1

Suggest to redo the whole flashing process BUT with 5.1.1 firmware from Singapore (XSP) --nearest to Hong Kong and revert. I think is better than trying to pluck/replace the CP or CSC from here and there.

I havent test new build yet but I think it has been updated. ro.build.version.security_patch=2019-07-05

In that case, then an update of the security patches (backporting) to this ROM will be great.

Maybe you missed this? https://lineageos.org/Changelog-22/

SM-P607T is a T-Mobile variant and there is an existing user/tester. https://forum.xda-developers.com/showpost.php?p=79778636&postcount=117

p605k = SM-P605K(orea) variant. This ROM should install if it is a "lt03lte" or "lt03ltexx" device. You can check it from a Terminal (eg., TWRP -> Advanced) window by typing/executing this line: getprop ro.product.device or getprop ro.build.product

There is an APP called Viper4Android which can enhance the audio output. I am using version 2.6.0.5 and it worked for me.

What is "los"?

Many thanks as always. Added: XDA commentary

Appreciate for your response. I understood and hopefully there is a permanent fix --cheers!

AFAIK, adoptable storage is encrypted and therefore copying from /data to /system on OS (live-patch) is only temporarily and will not "stick" on reboot. Check whether /data can be mounted in TWRP to confirm and then consider whether a recovery-patch is viable.

I was following Xprivacylua during early development stage and decided to ignore the thread due to the whim(s) of the DEV --hopefully he has stabilised. Btw, LBESM is still active with a 20190321-v2562 update (bug fixes) purely for China users.

+1 Viper4Android

At last and btw, just ignore "spoof-checker" if it shows disabled (bug) as ug self-check is the objective. Yes, Happy New Year to OP too --sorry for this microg/xposed stuffs!

Have you tried with Xposed patch?

Fyi, signature spoofing of ROM is a requirement but not deodexing. If you have the Xposed Framework installed, the following module will enable signature spoofing: FakeGApps by thermatk You can also patch your already-install ROM by flashing NanoDroid-patcher, without any computer interaction...

Just download 5.1.1 firmware from ANY country and flash with ODIN... Reboot into TWRP and re-flash this ROM. I have tried and my opinion is that TWRP can not flash "modem firmware" for p605. https://forum.xda-developers.com/showpost.php?p=73551911&postcount=637

Sorry, no idea as my device is purely for web browsing purpose only. AFAIK, both devices have the same specs.

Thanks, just wanted to compare sources. Personally, I think LineageOS users should periodically check-in with the Official Changelog for updates. Source: https://lineageos.org/blog/ In Changelog 21, device-specific development was dropped due to inactive maintainer but not 14.1 rom...

Can you provide the source?

That's what I did. Forgot to mention that I need to install the APP separately as the "magisk.apk" did not stuck during the flash --maybe you missed this part?

ROOT is possible with Magisk-v17.1 (unless you meant its other possibilities).

Yes for LineageOS rom. There is a link to flash/enable root in the OP.

I have a 2014 Samsung device (if relevant) on a LOS-14.1 rom rooted with superuser-r310-beta ZIP. I have previously tested every known phh ZIP with TWRP from v2.8.7 till v3.0.3 but always ended with errors. In my case, root is only possible with TWRP-v3.1 and the ZIP version doesnt matter, fyi.

+ [[ toto2 =~ toto ]] sh: =~: unknown operand I have this problem before and it seems to be TWRP related. Mine was solved by updating TWRP from v3.0 to v3.1. I am a LineageOS user --LOS-14.1 and yes, currently a separate addonsu ZIP is required to root it (system mode). The root ZIP...

I found it misleading that you are trying to enforce "init.d" --bootscript support, on devices with "SuperSU" or "Magisk" which ALREADY have their own bootscript implementations! Am I missing something here?

OP, ROM(s) with SuperSU or Magisk have their own bootscript support. Are there any special reason(s) to init.d them again?

I think RR development has stopped, dont know why. Check OP in RR thread.

Be patient my friend. I am sure OP will bake the current LOS patches into RR and release them shortly. It has been a while too for LOS users.

I made a clean install and can confirmed that: - the magnetic cover works fine - android security patch was updated to 20180205 As always, many thanks for your input!

Yes, naturally you should stick with sysinit because the groundwork patch to sepolicy has been done and also this is a wip "universal" tool. Sorry to hijack your thread because my posts were rom specific (CM13/LOS14) on how to regain usage of the half-baked init.d service by diy. Anyway...

The rom is, LOS14.1, provided unrooted. So, a separate flash with LOS's addonsu ZIP is required to root it. Test was setup this way: - clean flash - setup rom - copy test file to init.d - flash bootimg (with sysinit or sudaemon seclabel mods) - check for test log Btw, I just checked on the...

I got a chance today and have a shot with the "sysinit" seclabel on a Samsung device (lt03lte) running "unofficial" LOS14.1 rom. Test conditions: 1. unrooted 2. rooted by LOS addonsu 3. rooted by phh's superuser Results: No go for all test conditions although I have expected it to work with...

Fyi, On CM13/LOS14 roms with "native root", I have always mod the bootimg by adding this line to "init.cm.rc" for init.d support. # sysinit (/system/etc/init.d) service sysinit /system/bin/sysinit user root seclabel u:r:sudaemon:s0 oneshot disabled I have previously mentioned it...

Sometimes we are too engrossed with XDA, modding this and that with our android devices that we forgot this is a new year --2018! Thank you davidmueller13 for your various input and "Happy New Year" --on behalf of fellow users.

I am currently on this rom with microG. MicroG only works with a deodexed rom with signature spoofing. - To deodexed rom, search for "fulmics" - For signature spoofing, search for "tingle" or "haystack" Hope this is useful to you.

As said earlier, I am just a messenger/translator/not_creator of the app. The current version v2557 is irregular to me too as it tends to have superuser(plus) priviledge --break firewall with internet access. Try fallback to v2482 and install AfWall+ to control internet access. Additionally...

Normally, we would root device(s) with SuperSU|Phh|Magisk through a customised TWRP|CWM recovery. Currently, there's no known custom recovery available and the only root solution is through Kingroot app. * To the moderator(s), please move this to "asus zenfone go" thread per intention...

Seandroid msg should not be appearing, in my case. Not a big deal, but you can try re-flashing it. Edit: Here is my comment on david's twrp-v.3.1.1 made previously.

For android nougat, david currently have 3 wip roms. 1. Aosp 2. Lineage (unofficial) 3. Resurrection remix Resurrection remix (RR), forked from his lineage rom, have more features and, I think, most users here prefer it.

If you have already read this link and are positive of the info that you posted then you already have the necessary 5.1.1 fimware to flash this rom as required in op.

I just recalled that twrp recovery has a built-in option to run terminal session and this was the output from my rooted device. But now I am confused because the terminal emulator app on device can run getprop command with root disabled.

Yes, Terminal app would be useless if your device don't have superuser rights, ie., root.

If you're currently on this rom, the Terminal app came preinstalled but disabled (you need to unfreeze it first). Alternative app: https://jackpal.github.io/Android-Terminal-Emulator/ *Btw, root is required when running "getprop" code in a Terminal session.

Type this in a terminal window. getprop ro.bootloader If the output is the same as your baseband version or something like P605XXU1EQ??, then you're already on the 5.1.1 firmware.

The 5.1.1 bootloader + modem files can be downloaded by "SamFirm Tool". The tool still require a whole rom download but if bandwidth is a problem, I have already mentioned it HERE.

I have installed this rom-20170801 (link 4) today with personal addons: - magisk_v14 - xposed_20161125_v87.1_wanam Is it normal having the red "SEANDROID" message on boot up? Update: 20171112 Fyi, I did a clean-install again of the rom (as is) and can confirmed these: 1. SEANDROID: Answering...

I have a clean-install of latest build-20171026 today and can confirmed that the "magnetic cover" issue has been fixed.

Magnetic cover: The issue only appeared on rom(s) after build-20170803. I'm still on previous build-20170829 and can confirm it.