An error appears on the HOMEGROWN CHANNEL about youtube-webos

[Informatic]

https://github.com/RootMyTV/RootMyTV.github.io#i-quickly-turned-my-tv-on-and-off-and-its-really-angry-about-failsafe-mode

[Informatic]

Uncheck failsafe mode, press reboot in homebrew channel, it should be gone.

[Informatic]

Also:

1. This is a wrong repository for that, Homebrew Channel or RootMyTV repo would probably make more sense.
2. We don't speak Russian, please try to write your messages in English, or look for support in Russian-speaking communities.

[dryna2017]

I have the slider disabled as seen in the photo and not how this problem does not go away and I rebooted and pulled it out of the socket and still this sign pops up every 10 seconds give some command so that you can get rid of it

[Informatic]

Does it come back immediately when you press "System reboot" now? Or does it happen randomly later when using the TV?

[dryna2017]

The slider is turned off and this sign still pops up, but not as it does not want to disappear, can you help with what command to get rid of it23.01.2022, 16:32, "Piotr Dobrowolski" ***@***.***>: Uncheck failsafe mode, press reboot in homebrew channel, it should be gone. —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Informatic]

You need to press "System reboot" after sliding "Failsafe mode" off. Did you do it?

[dryna2017]

Yes, it does not disappear at all and after rebooting and after disconnecting from the outlet and everything that can be tried and reset was done three times and immediately after installation it pops up, I don't know what else to do, help, there was an old version of this was not23.01.2022, 16:56, "Piotr Dobrowolski" ***@***.***>: Does it come back immediately when you press "System reboot" now? Or it happens randomly? —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you authored the thread.Message ID: ***@***.***>

[dryna2017]

Is it possible to get rid of this annoying sign in some other way so that something does not pop up, because you can do whatever it is, please help me, there is nothing that does not come out

[Informatic]

OK. If you do webOS Factory Reset it no longer pops up, correct?

Then, when you go to https://rootmy.tv and let it install, then press "Reboot now" does the message show right away, or do you need to reboot it multiple times?

[dryna2017]

If I do a factory reset, this plate does not appear since the root is removed, when I install the root, this plate immediately pops up in the settings disabled and still pops up, I tried to turn on restart and turn off again and restart it still pops up

[Informatic]

OK. Connect to the TV using telnet and run these commands and show me their results:

cat /media/cryptofs/apps/usr/palm/services/com.palmdts.devmode.service/start-devmode.sh

cat /mnt/lg/cmn_data/wam/extra_conf.sh

cat /var/lib/webosbrew/startup.sh

ps aux | grep -i startup

[dryna2017]

Still climbs out

[Informatic]

I have no idea what you did,but that can't be an output from any of the commands I've sent above.

[Informatic]

You should have cat at the beginning

[dryna2017]

I typed one command and pressed enter

[Diniboy1123]

Each line should be one command from above. But the output we can see there @Informatic is probably due to the built-in busybox grep doesn't have the -i flag on that TV. The same happens to me as well. So the last command can be:

ps aux | grep startup

Also, you should copy the output from the terminal after every single command (you can simply select the text using your mouse from PuTTy and it will place everything onto your clipboard) then save those to a txt file and upload it here as an attachment or use pastebin. So we can see all output you have, not just the text that fits into your terminal window.

[dryna2017]

I did it on one command

[Informatic]

OK. This is what I was looking for.

Please run and show result of this command:

grep -h -E '"(hardware_id|core_os_release|product_id|webos_manufacturing_version|board_type)"' /var/run/nyx/*

In order to fix your bug you need to run:

rm /mnt/lg/cmn_data/wam/extra_conf.sh
reboot

This is an issue we haven't got from anyone and we will need to research it further.

[Informatic]

Please copy and paste the command I've sent above, not write them by hand. You put in unnecessary spaces between ' and " and between / and *.

In the second command it needs to be rm instead of ??

[Diniboy1123]

No, it's not. Please put this command onto your clipboard:

grep -h -E '"(hardware_id|core_os_release|product_id|webos_manufacturing_version|board_type)"' /var/run/nyx/*

Then navigate back to PuTTY, press right click with your mouse and finally hit enter.

Then you do the same steps with first

rm /mnt/lg/cmn_data/wam/extra_conf.sh

and finally reboot. Don't attempt to type that in manually or pay attention that it's the same.

[dryna2017]

[Informatic]

Yes. Now reboot and you should be fine. If you run https://rootmy.tv the issue will happen again probably (but you don't need to root multiple times since it should be persistent...), until we figure out what was the cause and fix the bug in the exploit itself.

[dryna2017]

And that it was necessary to insert one command at a time, so what, and then the enter, it seems to have disappeared while I look, I will unsubscribe, and if I pull it out of the socket, it will not appear back

[dryna2017]

So it turns out that everything was decided by this one team, so it turns out. Thank you for your help!!! rm /mnt/lg/cmn_data/wam/extra_conf.sh

[Kollega90]

Yes. Now reboot and you should be fine. If you run https://rootmy.tv the issue will happen again probably (but you don't need to root multiple times since it should be persistent...), until we figure out what was the cause and fix the bug in the exploit itself.

So what was the problem, did you find it?

[Informatic]

Did you happen to have that same issue as well? (ie. both start-devmode.sh and extra_conf.sh existing)

We have a summary plus some workaround (not specifically for that issue but should also fix this one...) we'll integrate soon in this issue:
RootMyTV/RootMyTV.github.io#27

[Kollega90]

Did you happen to have that same issue as well? (ie. both start-devmode.sh and extra_conf.sh existing)

We have a summary plus some workaround (not specifically for that issue but should also fix this one...) we'll integrate soon in this issue: RootMyTV/RootMyTV.github.io#27

No, I'm fine)) I was just trying to help in solving this problem)

[Informatic]

Generally - I am suspecting something very weird was happening and downloading our jumpstart script to the "original" path (start-devmode.sh) was returning an error while still the file was created there, which caused us to fall back to creating a second jumpstart file (extra_conf.sh), that would lead to the startup script being executed twice on boot.

There's a chance factory reset didn't remove any of these files (but... I don't think so, since it removes essentially everything on the filesystem?), or this was something more reproducible for that specific hardware/software pair. We didn't get any reports like this for ~a couple thousands installs of v2 we got so far, so this makes it especially weird.

[Kollega90]

Generally - I am suspecting something very weird was happening and downloading our jumpstart script to the "original" path (start-devmode.sh) was returning an error while still the file was created there, which caused us to fall back to creating a second jumpstart file (extra_conf.sh), that would lead to the startup script being executed twice on boot.

There's a chance factory reset didn't remove any of these files (but... I don't think so, since it removes essentially everything on the filesystem?), or this was something more reproducible for that specific hardware/software pair. We didn't get any reports like this for ~a couple thousands installs of v2 we got so far, so this makes it especially weird.

In the webos chat, this is still an isolated case

[Kollega90]

Generally - I am suspecting something very weird was happening and downloading our jumpstart script to the "original" path (start-devmode.sh) was returning an error while still the file was created there, which caused us to fall back to creating a second jumpstart file (extra_conf.sh), that would lead to the startup script being executed twice on boot.

There's a chance factory reset didn't remove any of these files (but... I don't think so, since it removes essentially everything on the filesystem?), or this was something more reproducible for that specific hardware/software pair. We didn't get any reports like this for ~a couple thousands installs of v2 we got so far, so this makes it especially weird.

rm /mnt/lg/cmn_data/wam/extra_conf.sh -Is this command for deleting a file extra_conf.sh?

[Informatic]

Yeah, this will just remove a file. In general we want to have either /media/cryptofs/apps/usr/palm/services/com.palmdts.devmode.service/start-devmode.sh or /mnt/lg/cmn_data/wam/extra_conf.sh to exist, definitely not both. Which one depends on whether the TV has been upgraded to "patched" (against RootMyTV v1) software version. (ie. extra_conf.sh is generally used on TVs with webOS TV 4.x+ with software released after 2021/06, and start-devmode.sh should be present on every other older model/software)