yashsingh1/xdaforums huggingface dataset:
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] hahmad78:
dear which kdz you are flashing with lg up?

flash your regions kdz with refurbish option complete. you will loose root but your mobile will be in working again.than you can downgrade to nougat and re root and flash any rom again.

do you have backup of your EFS in twrp? if yes than flash it and than flash kdz with lg up.

in case of any confusion, do tell and tell your mobile current state briefly
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] hahmad78:
i will recommend to flash nougat kdz of your model. it will smoothen out everything
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] angilinmago:
i tried everything, spending yesterday and today, whole two days at it, flashing kdzs, all versions, back and forth, root again, flashing this and that, still can't fix the modem problem. do have 4g internet, but very unstable 3g call situation, for 1 sec can make calls and for another second, can not.

i am just on the verge of giving up

---------- Post added at 08:41 PM ---------- Previous post was at 08:38 PM ----------

you sure it fixed your modem problem for good? how is your call signal, no issues at all? and did it restore your imei?

i tried twrp terminal commend, no use

also tried adb

just showed /system/bin/sh: dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1: not found

also trief fastboot method, no use

i have tried everything!!!!!!

---------- Post added at 08:43 PM ---------- Previous post was at 08:41 PM ----------

i didn't back up efs, biggest mistake, i deserved all this

---------- Post added at 08:45 PM ---------- Previous post was at 08:43 PM ----------

anyone has a h990n dual sim efs firmware backup? i can restore efs and firmware to my phone?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] hahmad78:
check pm
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] angilinmago:
mikekote666 canyou send me your efs as your are using h990n dual?

i will see if it works?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] mikekote666:
I have H990DS you must have done something wrong on twrp tho no other chance the way I told you worked for many people that faced this problem
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] angilinmago:
i have given up on v20, that was my last ditch effort to make this junk work a little longer/better, and that was a complete failure, thanks to everyone for sending me helpful messages, especially hahmad78. I have bought and switched to huawei p30 pro, so so much happier. this is the end for me on replaceable batteries.

word of warning to anyone who has H990N (hongkong version), don't try upgrading to rooted oreo, you won't be able to get dual sim function working, (i think the phone is hardware locked on that aspect), if you flash a different efs/firmware, you will end up with some sort of problem with phone's radio (in the end I managed to get both sims working, but sim 1 is just very temperamental, for 1 second it is working perfectly, another second it is lossing signal or getting stuck on switching between 4g to 3g, hence getting stuck on making a simple phone calls). H990DS, on the other hand, has none of those issues, I believe.

it's a rabbit hole that you won't be able to get out, stick with rooted nougat, or get a huawei
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] hahmad78:
Very sad to hear that you could not recover the phone. I have h990ds, i do mess up like 100 times in last 2 years, but not faced a issue, many times, corrupted efs and imei, but still got it working, with very easy steps.

P30 pro a very solid set spec wise,

But sad that you could not recover phone and gave up.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jl10101:
I agree - I've also made huge mistakes and corrupted / locked / soft-bricked but have never had anything permanent happen.

It's very strange that a call can be made but then issues appear. It mostly works or it doesn't.

Beginning to think it is pointing to something more sinister.

But, the P30 Pro is a super nice device! Hope he enjoys it!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] mikekote666:
Can you try at least once more?

1-Go back to stock nougat (Use LGUP patched and choose partitions menu so you can flash cust,modem and everything cause just by choosing upgrade doesn't do that)

2-Re-root

3-Type again that code i sent you in twrp terminal(maybe doing it from nougat will help you)

4-Reboot.

You may have better luck with this method
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Toriko:
I own an LGV20 h990DS ON STOCK Oreo (no root).

The procedure :

1) Flash Nougat, get root ,TWRP and flash kernel mk2000 Oreo;

2)Flash official Oreo kdz (apart from recovery/TWRP) and backup Efs and firmware from Twrp;

3)Follow the procedure of this post.

Is correct? At step 1), flashing an Oreo kernel on Nougat will do any harm?

Thanks.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] hahmad78:
it will not boot
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] pspablo:
zip the latest H990N on F800L

Can this soft be used with a rooted V20 F800L?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jl10101:
Unfortunately not. I would not try it. Sorry.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] ccdgs:
Stock nougat to rooted oreo

How would one go from stock nougat (7.0) to rooted oreo? I put off rooting due to not having an sd card but now there seems to be rooted oreo roms. And is there any way to backup unlinked game accounts during the process?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] jl10101:
You would have to root in early versions of Nougat as there is a vulnerability exploited for root. Only then can you flash an Oreo ROM that "supports" root (ie. leaves the exploit and particular partitions intact).

Not sure about the game accounts though, sorry!
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Randomuser666:
Hi everyone,

a quck question: I'm on a non-rooted h990ds, however I have not received the security patch yet.

And I seem to not be able to find the update (file) anywhere online.

Any ideas how I could update to the latest patch level without rooting?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] karkand:
I think you can get it without rooting by not flashing magisk. since the root itself is unnecessary for running a rom, but kernel. don't forget to flash the mk2000 kernel, or it won't boot up.

cmiiw.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] Randomuser666:
Thanks for the suggestion.

So basically I'd need to flash the mk2000 kernel first and then flash the kdz?

I'm not using magisk anyway..

Does anyone here know, why some of us have received the official update and others didn't?
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] stingbandel:
are u saying that we can install mk2000 kernel without rooting the phone?

if yes, can we just go to the stock recovery and install the kernel?

thanks
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] karkand:
No, you need to flash the kdz first..

It just my opinion. But it should.

Stock recovery? I think no. You should use twrp.
[LG V20 ROMs, Kernels, Recoveries, & Other Developm] stingbandel:
ok thanks for the info. anyway, is it the latest security update right now? if not, can we get an update to the latest security update?

thanks
[Samsung Galaxy S10 Questions & Answers] kezzuki:
So we dont have a notification light/LED/Indicator on this device huh?

Any substite?

I would like something that AUTOMATICALLY starts blinkling/showing ONLY when there are unread notifications.

Tried setting AOD like that, but it can not satisfy my requirements lol

Anyone?

Thanks!
[Samsung Galaxy S10 Questions & Answers] kezzuki:
Currently using Always on Edge, totally fits my needs. But a bit concerned aboit battery consumption lol:eek:
[Samsung Galaxy S10 Questions & Answers] iteam:
Read my thread: https://xdaforums.com/galaxy-s10/help/camera-notification-light-t3908240/page2#post79060494

:fingers-crossed:
[Samsung Galaxy S10 Questions & Answers] kezzuki:
hopefully they release the update soon:svetius:
[Google Pixel 2 XL Questions & Answers] ChrisDos:
I'm still coming to grips with how ROMs are working with Pixel devices and the A and B storage slots. Just recently came from the Nexus 6, but I've been flashing ROMs since the G1 (Dream).

I'm currently running Pixel Dust and I just dirty flashed for the first time. Got a error about the vendor image not matching and after searching for a bit I found that I had to download Googles March factory image and flash the vendor image to both slots. So that successfully worked and I got it it upgraded.

For me, the A and B slots make sense and I quite like the intended design. I deal with this all the time when working on routers, firewalls, etc. But I'm not understanding how ROM creators are using it. Shouldn't the custom ROM be on both A and B, and when an update becomes available, it updates automatically in the non active slot and then a reboot to the updated slot and you're current. I believe that is how the Google Factory image works.

Pixel Dust relies on the Google Factory image. I thought that was just for the original install. But Pixel Dust seems to need it for the updates as well. I've read that some are using Dueces script. But doesn't Dueces script erase the system? So it will be a clean flash each time? Baring using Dueces script, is there another script that will just update the radio, vendor, and other necessary images? If not, I suppose I can modify Dueces script. Is Pixel Dust the only ROM that relies on the factory image or do most ROMs work in that regard?

I don't know how some people can deal with clean flashing for every upgrade. I don't have time to deal with a clean flash for each update. It takes me hours to set up my phone. (Install ROM, restore Titanium, reconfigure all settings, etc).

For me, I choose a ROM that gives me a lot of custom options along with working with an encrypted phone and one I can stay on until the next major Google release. Pixel Dust delivers in the custom features, but upgrading takes a few more steps. I'm liking the Pixel Dust ROM right now.

Is there a feature rich custom ROM that uses both A and B slots and works with encryption and allows online upgrades in the way that the Google Factory image does?
[Google Pixel 2 XL Questions & Answers] simplepinoi177:
There might be a key & important detail you might not be aware of that might change your whole outlook...

when you say...

I can only assume you have never come across the whole "...remove the '-w' attribute from the flash-all.bat script" before...

"Flashing" the "factory images" given from Google for the Pixels (there may be others, but at least for the Pixels) aren't as conventional as past "flashing the factory images" to other (older) devices...

In most other devices, flashing the "factory image" wipes the whole device and essentially resets it and is usually done as an extreme and last resort. What's nice that Google has done/set up with their own proprietary device is to offer the option without wiping your apps, data, and settings by merely removing the "-w" attribute in the script that takes care of the "flashing"; no need to re-"set up", reconfigure, or restore anything -- all the while re-initializing a new(er), possibly more stable, less-buggy system, radio, boot, vendor, and other partition(s).

It's only for this reason what we "...can deal with clean flashing for every upgrade." It's once a month, and without the need to restore/reconfigure anything, it's usually done in 15 minutes or less (of course, I use the opportunity to make a nandroid backup so it takes considerably longer...)

Maybe this might change your mind to the whole updating thing, or at least give you a better understanding as to why others do it "...for every upgrade", every month...

Hope this helps...
[Google Pixel 2 XL Questions & Answers] ChrisDos:
That does help quite a bit. A lot actually. To me this would kinda be a normal flash while a clean flash would be everything except internal storage. So my Pixel Dust upgrade is just going to downloading the latest factory, removing the -w from Dueces script and flashing the factory, then flashing the latest Pixel Dust.

Are there any ROM builders that are using the A/B in the manor that Google Factory Image runs?
[Magisk] Geofferey:
I have Magisk v18.1 installed on my OG Pixel running PixelDust ROM and noticed every so often it loses root access. When entering the Magisk Manager app it also shows Magisk Not Installed. I did some investigating and found that magiskd (magisk daemon) gets terminated at some point randomly. Further testing revealed I could restart it manually by issuing "magisk --daemon" via SSH/ADB root shell.

I wrote a simple module to keep the daemon running and haven't noticed the "Magisk Not Found" error since. The module is just a simple bash script executed as service on boot that checks every minute for the daemon and runs the "magisk --daemon" command as root if not running. I am just posting it here to see if it can help anyone else who's root access disappears randomly on v17-19.3.

Please be aware that this is my first module ever. It was also originally started via an init.d script instead of the service hook in magisk, though it should work exactly the same. I have also noticed it is not possible for my module to restart magiskd yet if it was killed manually by the user.

GIt Repo:

https://github.com/Geofferey/mgkdhelper

Magisk Repo Submission:

https://github.com/Magisk-Modules-Repo/submission/issues/404

Release:

UNINSTALL INITIAL v1.0.0 RELEASE BEFORE INSTALL!!!

If you fail to do so you will have the old version and current version running at same time.

Download:

Current Release v2.1.0

Major thanks to [MENTION=4487388]jcmm11[/MENTION] & [MENTION=3491538]char101[/MENTION] whose

contributions

are now officially included in this module.
[Magisk] Brian23MAC:
I just wanna say God bless you for this module, my man. I was frustratingly having my Magisk daemon getting killed 2-3 times a day On my LG V20. Since installing your module for the past 4 days ive yet to encounter such an issue. I greatly appreciate you coming up w/a solution to a problem that was frustrating me to the max
[Magisk] xXx:
Thanks for that module. Very good idea and it's working perfectly fine. :good:
[Magisk] char101:
Hi,

There is no /data/local/run directory by default on my phone (OP6 Pie). So I suggest that either you create it first or simply uses /data/local/tmp to store the pid. Also creating the directory first might be a good idea. If you add -q to the grep command there is no need to redirect the output.

#!/system/xbin/bash

PIDFILE=/data/local/tmp/magiskd-helper.pid
LOGFILE=/data/local/tmp/magiskd-helper.log

is_magisk_running() {
ps -a | grep -q [m]agiskd
}

if [ ! -d /data/local/tmp ]; then
mkdir -p /data/local/tmp
fi

if [ -f $PIDFILE ]; then
kill -9 `cat $PIDFILE`
fi
echo $$ > $PIDFILE

RETRIES=0
while true; do
sleep 60
if ! is_magisk_running; then
echo `date` >> $LOGFILE
echo 'Magisk daemon appears to have crashed' >> $LOGFILE
echo 'Restarting magiskd...' >> $LOGFILE
/sbin/magisk --daemon
if is_magisk_running; then
echo 'Success!' >> $LOGFILE
RETRIES=0
else
echo 'Failure!' >> $LOGFILE
((++RETRIES))
if (( $RETRIES > 10 )); then
echo 'Giving up' >> $LOGFILE
break
fi
fi
echo >> $LOGFILE
fi
done
[Magisk] char101:
When first run, /system/bin/ps is linked to magisk builtin busybox, which don't have the -u option

ps: invalid option -- u
BusyBox v1.30.1-topjohnwu (2019-04-30 01:01:15 EDT) multi-call binary.

Usage: ps [-o COL1,COL2=HEADER] [-T]

Show list of processes

-o COL1,COL2=HEADER Select columns for display
-T Show threads
[Magisk] Rom:
Try again after having install the 'Busybox for NDK' Magisk module (from osm0sis), maybe that the -u arg for ps command will works i ddon't remember me having testing it recently so idk if it will works but i think yeah :)
[Magisk] char101:
I have the GNU coreutils module installed so it is not the problem.

Also the original module redirect stderr to /dev/null so unless you modify it you won't see the error like I posted before.

My modifications

service.sh

#!/system/bin/sh
# Do NOT assume where your module will be located.
# ALWAYS use $MODDIR if you need to know where this script
# and module is placed.
# This will make sure your module will still work
# if Magisk change its mount point in the future
MODDIR=${0%/*}

# This script will be executed in late_start service mode
$MODDIR/common/magisk-monitor > /data/local/tmp/magisk-monitor.log 2>&1 &

magisk-monitor

#!/system/bin/sh

is_magisk_running() {
ps -A | grep -q [m]agiskd
}

sleep 300
echo `date`
echo 'magisk-monitor running'
echo

RETRIES=0
while true; do
sleep 60
if ! is_magisk_running; then
echo `date`
echo 'Magisk daemon appears to have crashed'
echo 'Restarting magiskd...'
/sbin/magisk --daemon
if is_magisk_running; then
echo 'Success!'
RETRIES=0
else
echo 'Failure!'
((++RETRIES))
if (( $RETRIES > 10 )); then
echo 'Giving up'
break
fi
fi
echo
fi
done
[Magisk] Didgeridoohan:
I doubt it... From busybox.net:
[Magisk] char101:
It is better to just use 'ps -A' which will work on busybox ps and coreutils ps.
[Magisk] Rom:
I'm agree with u, but it was already happen for me that some other args works too, i had never know why.
[Magisk] thunderteaser:
I came across your module while looking for the same issue affecting many users on different devices (although it seems to be affecting Pie only). Magisk GitHub is also full of reports by people losing root and solving with a reboot. I don't know how impactful it is on the battery since it checks for Magisk every 60 seconds (I have just installed it) but so far your module is the only blessing we can get to avoid rebooting once/twice per day. I think you should definitely submit your module to the official repository!

P.s i had to create /data/local/run first for the pid
[Magisk] thunderteaser:
[MENTION=289981]Geoffrey[/MENTION] another quick correction: in my case on MIUI 10 based on Pie, ps -a does not show the same output as ps -A. So I had to replace the -a in your script with an upper case A.
[Magisk] jcmm11:
Coreutils doesn't have a ps applet. If you want to use -u just use the full path /system/bin/ps to force the toybox applet.
[Magisk] jcmm11:
[MENTION=289981]Geoffrey[/MENTION]

First of all nice workaround. I did some cleanup and a few modifications if you want to post it to the Magisk repository (and I think you should).

Changed over to the current template.

Removed all the PID stuff, it's really not needed.

Replaced ps -a -u with pgrep. That eliminates any busybox vs toybox issues (at least the way it's being used here)

Removed bash. There's nothing here that requires a bash shell as opposed to the default shell.

Moved the script to it's own directory instead of xbin. Not all phones have xbin, and trying to use it on those that don't is problematic. Plus there's no reason the script needs to be in the PATH.

Added nohup to the script startup command in service.sh

Also always create the log file, with a "started on" line in it. That at least gives an indication that the script started.

So what we're left with.

mgkd-helper (in a script directory)

#!/system/bin/sh

LOGFILE=/data/local/tmp/magiskd-helper.log

rm -f $LOGFILE
echo "Started " $(date) >> $LOGFILE
echo "-----------------------------" >> $LOGFILE
echo >> $LOGFILE
while true; do
sleep 60
if ! pgrep magiskd >/dev/null; then
echo $(date) >> $LOGFILE
echo "Magisk daemon appears to have crashed" >> $LOGFILE
echo "Restarting magiskd..." >> $LOGFILE
if magisk --daemon; then
echo "success!" >> $LOGFILE
else
echo "failure!" >> $LOGFILE
fi
echo >> $LOGFILE
fi
done

service.sh

#!/system/bin/sh
# Do NOT assume where your module will be located.
# ALWAYS use $MODDIR if you need to know where this script
# and module is placed.
# This will make sure your module will still work
# if Magisk change its mount point in the future
MODDIR=${0%/*}

# This script will be executed in late_start service mode
#Magisk Daemon Helper
# Copyright (C) 2019 Geofferey @ XDA
# License: GPL V3+

nohup $MODDIR/script/mgkd-helper > /dev/null &

If you do decide to place it in the repository you need to do something with README.md

You should also replace META-INF/com/google/android/update-binary with the attached version. The included version is for standalone installs. Repository versions should use the alternate one. (Remove the ".txt")

Last note: tested this and it does work. I killed the running magiskd and a new one was started, with the appropriate log entry created
[Magisk] Macusercom:
I wasn't able to start magiskd with "magisk -- daemon" via adb. It always says "No daemon found" instead of starting it. I seem to have lost root with the original script and I had to restart again. Any idea? I just enabled root via adb in Magisk. Not sure if that was the issue that I couldn't restart it.

And it seems like magiskd is killed in OxygenOS 9.0.5 on my OnePlus 6. Not sure if it is due to out of memory reasons but I can't get any logcat as I don't have root. Super annoying.
[Magisk] martyfender:
Will this be added to the magisk module repository? If it is there I couldn't find it. I do know there are links and a revision at the end of the thread by [MENTION=4487388]jcmm11[/MENTION]. I don't need the module, just curious if the revision will be put there eventually. I have had others with that problem that I have helped.

Thanks
[Magisk] jcmm11:
I think it should be but it's up to [MENTION=289981]Geoffrey[/MENTION]. It's his module. I cleaned it up a bit that's all. Most of the work is done. Biggest thing left to do is modify README.md
[Magisk] kryshnakishore:
Should we directly flash zip in twrp recovery
[Magisk] jcmm11:
You can flash it in recovery or via Magisk Manager, modules section, big + button at bottom of screen.
[Magisk] _litz:
I've been looking for a solution to this since v17 ... started happening on 17, kept happening on 18, is even worse now on v19 ... :-/
[Magisk] Geofferey:
Wow, I did not think this module would be so important to others! Honestly, I thought my work was crap, haha. Thank you [MENTION=4487388]jcmm11[/MENTION] & [MENTION=3491538]char101[/MENTION]. I really appreciate you guys for the modifications and and re-sharing the work. [MENTION=4487388]jcmm11[/MENTION] You did good and I could tell you weren't trying to exclude me in any way (in regards to other thread).

Since there is so much interest I will make a .git repository for this module and work on publishing it to the Magisk repo. I will also include proper accreditation in repo README.md/Module :).

As promised...

GIt Repo:

https://github.com/Geofferey/mgkdhelper

Module Submission:

https://github.com/Magisk-Modules-Repo/submission/issues/404

BTW:

You guys were tagging me wrong lolol. That's why I never received notifications for this thread. Don't forget the extra "e" in my name [MENTION=3421557]Geofferey[/MENTION]. My mother worked very hard to make sure nobody would spell it right! Damned auto correct don't help either.
[Magisk] jcmm11:
Good job so far. Just 2 comments

1) change module.prop

There have been enough changes to warrant a 2x version so I recommend 2.0.1, or 2.1 so that it's greater than the one I previously posted.

More importantly bump the versionCode to 3. Mine was set to 2 and this is the number Magisk uses to see if there's an update (version is strictly descriptive).

2) I hope you realize that the retry logic currently isn't functioning. For starters you have the increment statement commented out. Not sure if you really need retry logic. As it stands now if it fails it's just going to try again a minute later.

If you do want to incorporate retry logic then I recommend that after x retries you exit the entire program rather than break.