Develop Bugs

Lg L Manager [Win] [Unix] [L3] [L3 II] [L5] [L7]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LG L Manager​
With Crazy Mode too​
Lg L Manager is your new Pc suite for your Lg L3, L3 II, L5 and L7!!​
Features
Code:
#Supported Os:
--> Windows (Xp, Vista, 7, 8.x)
--> Unix based os (Os X too)
--> Linux distros (Ubuntu, Debian, Suse, Fedora, Linux Mint, etc..)
#Common Fetures:
-->Backup & Restore
-->Adb Shell
-->Install roms (Not fully automatized due to wipe /data)
-->Install Gapps or any mod (automatizated)
-->Install apk
-->Import Camera photos
-->Push and Pull files
-->Crazy mode
#Device Specific
-->Full Unlock (Bootloader+Recovery+Root) [L5] [L7] [L3II -> WIP]
-->Full Unlock (Recovery+Root)

Sources
Sources: https://github.com/ionolinuxnoparty/Lg-L-Manager
Branches :
Master > Windows
Master-unix > Unix and Linux
Click to expand...
Click to collapse
Download
Windows
Unix / Linux
Click to expand...
Click to collapse
Bugs
-Windows > dunno what's working and what not cuz I own no windows PCs and I wrote it with no test
-Unix > Crazy mode will make you crazy [cannot fix this]
Check commits to see if I've fixed something
Click to expand...
Click to collapse
How to run
Unix / Linux : browse into the folder where you have to place files ( ~/Lg-LManager), and run
./Start.sh 0 [Select device manually]
./Start.sh 1 [Lg L3]
./Start.sh 2 [Lg L5]
./Start.sh 3 [Lg L7]
./Start.sh 4 [Lg L3 2]
Click to expand...
Click to collapse
Windows: execute start.bat

Dev notes
Full Unlock,
it was pretty easy, everyone used stupids toolkit that may work or not. Adb and fastboot are the most useful and powerful tools.
I've changed the order to unlock device that everyone used. Why first root, then recovery and then bootloader?? Do you need the keys to change a car engine? Nope, so it's the same thing for an android device. Fist I boot a recovery to get adb root (stock kernel doesn't allow it, but a recovery automatically give adb root acces even if phone is not rooted), then I'll push file to unlock bootloader to sdcard and then unlock it. After this I flash recovery, then flash any root package. Done! And it works with any rom.
Click to expand...
Click to collapse
About Lg L3 II,
apparently this device has no bootloader to imput fastboot commands needed for the full unlock, read notes inside bat file
Click to expand...
Click to collapse
About Lg L3,
this is the only device I own of the four I support... Now there's no recovery that allow both adb shell and sideload so I've to push every file to sdcard. When there will be a recovery where both adb shell and sideload are working I'll change a few lines of code and it will be OK.
Click to expand...
Click to collapse
About Crazy Mode,
it's made for crazy users that may brik their devices and make strange things with their pc. When crazy mode is enabled there's no way to quit it and it may lag your pc like hell (until reboot) so you won't be able to do anything because you're crazy and you may destroy something.
Click to expand...
Click to collapse

Seems so good!
Well I guess I need to run su before i execute it on unix because of the permission errors I get , it will work fine I guess
If you need any help or testing for Unix , message me on Hangouts

I discovered how to enable PIXEL gestures on Global ROM (v1.16)

Hey guys, I was perusing the internet when I came upon a setting to enable the PIXEL gestures on the OnePlus 6 so on a whim I tried the ADB command on the Red Magic 3 and IT WORKED!
The command is as follows:
Code:
adb shell settings put secure swipe_up_to_switch_apps_enabled 1
For reference I'm running the v1.16 global rom (with ROOT [Magisk]).
Just incase any of this had any affect on it, my current Magisk modules are:
QuickSwitch (with Lawnchair V2)
Substratum (with FLUX theme)
Viper4Android FX (v2.7.1.0).
--
I don't see any reason why this would NOT work on a non-rooted phone though. You just need ADB with Developer Options enabled and USB Debugging to run the command.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Whoops! It turns out you DO need root to enable this.
I wiped the user storage partition of the device and tested the command and it had no effect until I installed Lawnchair v2 and used the Quickstep Magisk module to designate it the recents provider.
So again steps to enable this:
1) Root device via Magisk
2) Install Quickstep Magisk module.
3) Install Lawnchair v2 and set as default home.
4) Use Quickstep to set Lawnchair v2 as recents provider.
5) Run the adb command in the post above.

Whoops #2. There is a setting in Lawnchair once you have the recents provider setup to enable or disable the swipe up. No ADB needed.

Can you make a video tutorial. thank you very much
sevnsevn said:
Hey guys, I was perusing the internet when I came upon a setting to enable the PIXEL gestures on the OnePlus 6 so on a whim I tried the ADB command on the Red Magic 3 and IT WORKED!
The command is as follows:
Code:
adb shell settings put secure swipe_up_to_switch_apps_enabled 1
For reference I'm running the v1.16 global rom (with ROOT [Magisk]).
Just incase any of this had any affect on it, my current Magisk modules are:
QuickSwitch (with Lawnchair V2)
Substratum (with FLUX theme)
Viper4Android FX (v2.7.1.0).
--
I don't see any reason why this would NOT work on a non-rooted phone though. You just need ADB with Developer Options enabled and USB Debugging to run the command.
Click to expand...
Click to collapse
Can you make a video tutorial. thank you very much. plz

sevnsevn said:
Hey guys, I was perusing the internet when I came upon a setting to enable the PIXEL gestures on the OnePlus 6 so on a whim I tried the ADB command on the Red Magic 3 and IT WORKED!
The command is as follows:
Code:
adb shell settings put secure swipe_up_to_switch_apps_enabled 1
For reference I'm running the v1.16 global rom (with ROOT [Magisk]).
Just incase any of this had any affect on it, my current Magisk modules are:
QuickSwitch (with Lawnchair V2)
Substratum (with FLUX theme)
Viper4Android FX (v2.7.1.0).
--
I don't see any reason why this would NOT work on a non-rooted phone though. You just need ADB with Developer Options enabled and USB Debugging to run the command.
Click to expand...
Click to collapse
Can you share how to use the viper4android? I want to boost the speakers a bit..

souma_rox said:
Hey guys, I was perusing the internet when I came upon a setting to enable the PIXEL gestures on the OnePlus 6 so on a whim I tried the ADB command on the Red Magic 3 and IT WORKED!
The command is as follows:
Can you share how to use the viper4android? I want to boost the speakers a bit..
Click to expand...
Click to collapse
Install magisk module and reboot. Version should be 2.7

(Root/Bootloader Unlock) Spreadtrum Rearview Smart Mirror (TZ108, Media_Sleep Roms, etc) - Temp/Semi-Permanent

This isn't the ideal root solution for it but I have managed to get root on my Quidux TZ108 smart mirror to work. Now, this method requires that the adb root code I provide works on your devices, or that you have access to adb root. This should work on any smart rearview mirror using a Spreadtrum (SPD) processor and firmware with "media_sleep" in it.
First, I would like to thank @Crypto90 for providing the adb root code for the device.
Crypto90 said:
ADB root pin is: 2846
Click to expand...
Click to collapse
Bootloader Unlock (probably not necessary)
** I don't believe this is necessary for the root method below since the system.img is unprotected. **
Use a computer with Linux or Linux Terminal
Go to Settings>System>About phone>Build Number and Tap it until Developer Options are enabled.
Now go back to About Phone and click on Developer Options
Open ADB on computer and type ./adb devices or adb devices depending on your adb
If it doesn't give you an "Allow this computer" prompt and/or there isn't any adb devices listed
(Method 1) Enable ADB and Enable ADB Root Privileges (code is 2846) -- This seems to make ADB work every time on mine.
(Method 2) Download "Terminal emulator" or "Termux" and follow next step in it
Type "adb reboot bootloader"
Now follow the steps here: https://forum.hovatek.com/thread-32287.html
When it asks to confirm bootloader unlock (volume up/volume down options):
Get a small pin or screwdriver
There is a small button hidden in the AV port.
Press it and it will (luckily) confirm it for you.
Congratulations, your bootloader should now be unlocked.
Root (KingoRoot)
Steps:
Plug Mirror into Windows computer with ADB installed (or one with the ability to run .exe)
Go to Settings>System>About phone>Build Number and Tap it until Developer Options are enabled.
Now go back to About Phone and click on Developer Options
Enable ADB and Enable ADB Root Privileges (code is 2846)
Accept the prompt for "Allow this computer'" after selecting the "Always" box.
Now download KingoRoot.exe and run it.
Click Root on it.
Let it run and when it finishes it should open Kingo SuperUser and have root.
Now, this seems to be unreliable when it comes to reboot. Sometimes it remains after reboot but you have to go into SuperUser and press on the root checker part if it says "No Root." It mostly doesn't work anymore after reboot. However, you are able to replace the bootanimation, system apks, system files, etc. and they will remain when root is inactive. I'm still working on a more permanent solution. I haven't been able to get Magisk to work. Flashing patched boot.img, flashing patched recovery.img, creating signed vbmeta, creating signed boot.img, direct install.. all fail to boot.
I'll update this when I come up with a better solution.
Drivers, Flash Tool, and Firmware (for Quidux TZ108) can be found here:
GDrive

Hi!
Thanks for the amazing guide, it helped me with my smart mirror.
Did you found any way to get a stable root? Adding a swap file to the system would make it greatly more stable since more complex apps (like sygic for instance) just quit after loading due to ram being full.
I've also noticed that kingoroot guides states that BL should be unlocked to make the root stable however, I did not try since i don't have linux currently installed on my machines.

Hi.
Did you have discord or server?
Can you make one server and write there about this mirror and we can talk all there.
Can you add me: Jack8#4142

Any updates?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Faciula said:
[ALLEGARE=completo]5565633[/ALLEGARE]
Click to expand...
Click to collapse
Buon fine settimana. Il mio dispositivo è bloccato durante il ripristino al tentativo di nuovo!!!!!!!!!!!Premo a lungo su riprova e il pulsante di accensione ma il dispositivo non carica Android e riprova di nuovo!!!!I Netd Eseguo i dati di fabbrica reset!!!!come farlo????Dispositivo Adas mirror Android 8.1 Marca SZKJ D30 . CPU sl8541e ma con marchio IMEI OTL mod 8A

i can't Access device why in bootloop avvio and ended in recovery.thank you .help me!!!!!

Question MIUI 12.5.6 killed gestures for third party launchers

MIUI 12.5.6 killed gestures for third party launchers, I have been using Fluid.N.G to bypass full screen gestures erlier problems, but now system doesn`t allow to switch to gestures when third party launcher is selected. Does anyone know how to get it work?

Yeah purchase LADB and run the command after any reboots, it is on sales now cause I requested for. Hurry up.

italodance said:
Yeah purchase LADB and run the command after any reboots, it is on sales now cause I requested for. Hurry up.
Click to expand...
Click to collapse
What command should I enter? I've enabled USB debugging and granted rights for FNG, but despite this, the option to remove control keys doesn't work. How to do it with a manual command? I'd love to see if it works via PC, and then possibly buy a LADB to do it from phone. BTW I have a ABD Shell for Tasker already

malykazio said:
What command should I enter? I've enabled USB debugging and granted rights for FNG, but despite this, the option to remove control keys doesn't work. How to do it with a manual command? I'd love to see if it works via PC, and then possibly buy a LADB to do it from phone. BTW I have a ABD Shell for Tasker already
Click to expand...
Click to collapse
settings put global force_fgs_nav_bar 1

@italodance Thank you good man! Not without some probems with the configuration, but it worked!

malykazio said:
@italodance Thank you good man! Not without some probems with the configuration, but it worked!
Click to expand...
Click to collapse
What problem? If it is statusbar theme, just switch between gestures once then back to homescreen menu and run the command again. you won't lose your theme.

italodance said:
What problem? If it is statusbar theme, just switch between gestures once then back to homescreen menu and run the command again. you won't lose your theme.
Click to expand...
Click to collapse
I was referring to the LADB configuration, I couldn't get the pairing to work properly at first, but I used the hint about two windows and then it worked. It would be nice to force Tasker to work this way, so that using its ADB plugin it automatically enters this command after a reboot. When I find time I might look into it, for now I'm happy. Thanks again.

.

.

malykazio said:
I was referring to the LADB configuration, I couldn't get the pairing to work properly at first, but I used the hint about two windows and then it worked. It would be nice to force Tasker to work this way, so that using its ADB plugin it automatically enters this command after a reboot. When I find time I might look into it, for now I'm happy. Thanks again.
Click to expand...
Click to collapse
LADB is really painful to use...
Tasker allows you to set this global var after each boot via a Custom Setting (no need for ADB plugin)
Create a Profile > Event > System > Device Boot
Add a new Task
Add a new Action > Settings > Custom Setting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mellow971 said:
Tasker allows you to set this global var after each boot via a Custom Setting (no need for ADB plugin)
Click to expand...
Click to collapse
Interesting option - is it working without root?

Yes, you just need to grant Tasker WRITE_SECURE_SETTINGS permission via ADB

Question Disable bloatwares on COS 13 in ADB does not work?

Hi anyone has a clue on how to disable some apps in ColorOS 13, been trying but failed because the state of the app does not change. My main concern is to redirect app links (eg. from ecommerce app to payment app, which usually lands into App Market and said "app not available"). These are things I have tried and not successful:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Package name directly extracted:
cmd I followed:
shell pm uninstall --user 0 com.oplus.ota
Failure [DELETE_FAILED_INTERNAL_ERROR]
shell pm disable-user --user 0 com.oplus.ota
Package com.oplus.ota new state: default
shell pm disable com.oplus.ota
[Error]:failed to disable com.oplus.ota
Click to expand...
Click to collapse

A couple of suggestions:
-Remove the -k keyword while uninstalling the app
-Add the adb keyword before the shell pm uninstall command

binary**# said:
A couple of suggestions:
-Remove the -k keyword while uninstalling the app
-Add the adb keyword before the shell pm uninstall command
Click to expand...
Click to collapse
thanks but does not work

rockmaster said:
Hi anyone has a clue on how to disable some apps in ColorOS 13, been trying but failed because the state of the app does not change. My main concern is to redirect app links (eg. from ecommerce app to payment app, which usually lands into App Market and said "app not available"). These are things I have tried and not successful:
View attachment 5862107
View attachment 5862109
Package name directly extracted: View attachment 5862111
cmd I followed:
Click to expand...
Click to collapse
Or use adb app Control
For easy debloat

ChrisFeiveel84 said:
Or use adb app Control
For easy debloat
Click to expand...
Click to collapse
I will try, just additional question do I have to reboot into bootloader or it's ok to just enable debugging and stay within the OS?

rockmaster said:
I will try, just additional question do I have to reboot into bootloader or it's ok to just enable debugging and stay within the OS?
Click to expand...
Click to collapse
Adb only works when you in system
On bootloader only fastboot no adb

ChrisFeiveel84 said:
Or use adb app Control
For easy debloat
Click to expand...
Click to collapse
Same I dont think the app state changes because after refresh it still show enabled, and task 0/1
any clue ?
Edit:
Somehow this market is not disabled, tried a few things but market
Edit2:
A few others failed to be disabled too, not sure if this is common on COS13

rockmaster said:
View attachment 5862123 Same I dont think the app state changes because after refresh it still show enabled, and task 0/1
any clue ?
View attachment 5862125
Edit:
Somehow this market is not disabled, tried a few things but market
View attachment 5862129
Edit2:
A few others failed to be disabled too, not sure if this is common on COS13
View attachment 5862133
Click to expand...
Click to collapse
Not with the comand go to application and from here disable the apps

ChrisFeiveel84 said:
Not with the comand go to application and from here disable the apps
Click to expand...
Click to collapse
uhmm how do you mean ser? The app can't be disabled, I tried also revoking its permission as well from ADB but failed too.
Workaround anyway to set Play Store as default app store?

I guess no one facing the issue like this, only my device then :/

So you have to disable permission monitoring in colorOS to be able to run adb commands. It's in developer options.

rockmaster said:
I guess no one facing the issue like this, only my device then :/
Click to expand...
Click to collapse
me too... there are some packages like com.oplus.ota that you can not disble/uninstall....
i've searched everywere in forums but there are no solutions :-(

Same issues here with Realme 10 Pro+. Uninstalled several bloatware apps but App Market, Browser and Wallet resist unistallation and disabling.