yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] lowtiertrash:
Right, ok, there's nothing that the log will show because I'm not even able to begin the extraction. There are no kdz's (backups) showing in the root/salt_backup folder for me to extract. They are invisible.

However, the log I posted is clearly storing the backup into root/salt_backup.

This is where I'm stumped. Sorry for the confusion.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Still confused:

"There are no kdz's (backups) showing"

KDZ is a LG file.

There is no "kdz backup".

I still have the feeling that you are completely doing things wrong.

Check the screenshot and verify that you do it that way and ensure the target dir is e.g. /tmp and not /root

-
[Android Software/Hacking General [Developers Only]] lowtiertrash:
I think I am, I took a screenshot myself.

There must be something I've missed.

[IMG="attempt"]https://i.imgur.com/3N8XdSr.png[/IMG]
[Android Software/Hacking General [Developers Only]] steadfasterX:
yes... Assuming that you have downloaded the KDZ in your Downloads folder:

when you open a KDZ choose on the left site "Other locations" -> home -> android -> Downloads

.
[Android Software/Hacking General [Developers Only]] lowtiertrash:
Ok, I think that I confused kdz's and backup as being synonymous with each other. Hence, I think the confusion.

I need to extract my modem.img from my salt backup.

Because cell service was lost during UsU. However, I can't find my backups. Nor do I know how to extract the MM modem.img to flash back onto my device.

for reference, if you'd read the last portion.
[Android Software/Hacking General [Developers Only]] tim455:
[android@fwul ~]$ ps aux | grep xdg
android 713 0.0 0.0 19088 3272 ? Ss 02:55 0:00 /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc
root 2428 0.3 0.5 226376 28472 ? S 03:17 0:00 /usr/bin/yad --center --window-icon=/home/android/programs/SALT/icons/salt_logo.png --width=1000 --image=/home/android/programs/SALT/icons/salt_logo_128x128.png --title=SALT - 3.17-7:TESTING - MOUNT --text= Image file:\n\t<b>/run/media/android/SD/salt_backup/userdata.bin</b>\n\n has been mounted to\n\t<b>/mnt/salt_mnt</b>\n\n --form --field=Browse Image:FBTN sudo -u root xdg-open /mnt/salt_mnt --field=Browse Image (root):FBTN xdg-open /mnt/salt_mnt --field=Unmount Image:FBTN bash -c 'F_UMNT /mnt/salt_mnt' --button=Close:0
android 2464 0.0 0.0 16124 2336 pts/0 S+ 03:17 0:00 grep --colour=auto xdg
[android@fwul ~]$

further; for whatever reason, now I cant get the phone into download mode. Or rather, it just isnt recognized anymore once in download mode. showing [633A B99] at firmware update screen. not sure if that makes any difference. (trying to figure out how to unlock and apply 4corefix, but i realize this isn't really the place to ask)
[Android Software/Hacking General [Developers Only]] steadfasterX:
The ps aux command seems to happen too early

.. Do you had clicked the button for browse image(root) and THEN the command???

These connection issues happens when you are using VirtualBox so ensure the USB settings are correct, try to set USB to v2 or v3 depending on what it is now and if it's true that you're using VirtualBox consider to use the recommended way and flash FWUL on an USB stick instead of using VirtualBox.

Also when you can't get it connected with SALT wait 1 min minimum and press retry on the connection window when starting SALT. Try it at least twice and if it's not working press skip and upload the debug log.
[Android Software/Hacking General [Developers Only]] tim455:
Ill have to check it a little later, but ill get back to you.

Also, not really salt related, but when salt can see the device, is there a reason why simple-adb (adb or fastboot) cannot find the device?
[Android Software/Hacking General [Developers Only]] steadfasterX:
adb mode is not fastboot mode, fastboot mode is not adb mode and both are not download mode.

Every mode is different.

When using VirtualBox (which I do

not

recommend to use) you have to add for every mode the corresponding USB filter.

.
[Android Software/Hacking General [Developers Only]] sdembiske:
Download the

latest

firmware from here: https://lg-firmwares.com/lg-us991-firmwares/firmwares/

and then direct SALT to the shared folder (on your PC/laptop where you place the kdz) for the extraction.

You have to put a check mark each time in the VirtualBox USB for your device to be recognized. Refer to post # 529 in the FWUL thread - it's a bit of a checklist I have to run through sometimes myself. Make sure you have Developer Options enabled on your device - it has to be done on every flash of a custom rom.
[Android Software/Hacking General [Developers Only]] lowtiertrash:
Is this achievable without using virtual box?
[Android Software/Hacking General [Developers Only]] sdembiske:
This is specifically for Virtualbox. I have done this myself in Virtualbox with no issues.
[Android Software/Hacking General [Developers Only]] brito11:
I'm running into some issues with getting SALT to mount the backup BIN files. This is my first time using Linux so I may be just too inexperienced. I did search this thread for similar issues but no luck.

I have a LG K371 that cannot be unlocked, so I wanted to make a backup. I mounted FWUL (forgetful) on a USB and booted it on my Windows machine. My backup was completed successfully, with the caveat that "Your device/firmware does not support verification of the backup sorry."

When I click the Advanced button and attempt to mount my backups, I get the message that it cannot be mounted. The salt.log has:

2018-07-25 18:55:46: F_MOUNTPARTS: started

2018-07-25 18:56:04: returned: /root/salt_backup/tzbak.bin|/mnt/salt_mnt|

2018-07-25 18:56:04: IMGFILE = /root/salt_backup/tzbak.bin, MNTPNT = /mnt/salt_mnt

2018-07-25 18:56:04: F_MOUNTIMG: started with /root/salt_backup/tzbak.bin

2018-07-25 18:56:04: F_MSGE: started

2018-07-25 18:56:06: ERROR: system image could not be mounted to /mnt/salt_mnt.

How do I proceed from here? Thanks in advance!
[Android Software/Hacking General [Developers Only]] steadfasterX:
you can mount only image files which contains a filesystem. tz,rpm, etc does not contain a filesystem.

examples for mountable image files are userdata, system, modem, cache, ...

EDIT

and for completeness: It makes no sense to just provide parts of the debug log. When you encounter issues the full log is needed (its just a click in advanced menu -> debug log -> upload ).

-
[Android Software/Hacking General [Developers Only]] steadfasterX:
SALT v3.17 released

Checkout the FAQ #9 for howto update to this brand new release

Legend of summary topics:

New (SALT): Enhancements of the SALT main application - what you see and work with

Fix (SALT): Fixes of the SALT main application - what you see and work with

New (lglaf): Enhancements of the USB communication backend which SALT uses under the hood

Fix (lglaf): Fixes of the USB communication backend which SALT uses under the hood

v3.17-9

Released: 2018-07-31

Full changelog (SALT): at github (this version compared with the previous release)

Full changelog (lglaf): at github (this version compared with the previous release)

Summary changelog:

New (SALT): Force Challenge/Response mode available for devices where the automatic detection fails (PERMISSION DENIED in SALT debug log)

How it works and where to find >click here<

New (SALT): provide feedback while detecting the ARB of a KDZ

New (SALT): completey re-worked "Convert an image (ZIP)" in the advanced menu. SALT is now able to mount any image file instead of just system (e.g. vendor,...)

New (SALT): some KDZ extract enhancements (like cleanup etc)

New (SALT): a lot of changes for the upcoming direct flashing function (not enabled by default)

Fix (SALT): ARB detection of KDZs in some cases

New (lglaf): added CR force-on, force-off (details)

Fix (lglaf): disable direct flashing on laf > 100001 again (was accidentally still enabled)

Fix (lglaf): When direct flashing failing raise a real error including a non zero returncode

Have fun

sfX
[Android Software/Hacking General [Developers Only]] steadfasterX:
Gksu / gksudo are deprecated. In FWUL I switched to pkexec

https://github.com/Carbon-Fusion/build_fwul/issues/67

It sounds like a permission issue but not sure. I fear I cannot help on that part much. Maybe it's just a package issue so you will likely have more current package versions (as you use pure arch) as in FWUL which is based on Manjaro Linux.

It sounds definitively not like a SALT specific one though.

Besides that FWUL is a deep modified Linux to run as smooth as it includes all the stuff around. So basically it may be just something you do not have or I made different then you in your installation...

You could also try to run SALT from a terminal - maybe there is output we do not see in the log..

Otherwise you can just try to compare the package versions or simply try Manjaro Linux ;)
[Android Software/Hacking General [Developers Only]] sdembiske:
OK - thanks. Please remember to correct the commands for the ARCH requirements.

Will try running SALT from a terminal & see if anything different. Had a problem previously when installing Manjaro and couldn't figure where the issue was, so stayed with Arch - no problems until now.
[Android Software/Hacking General [Developers Only]] sdembiske:
[MENTION=5545101]steadfasterX[/MENTION]

OK, think I've discovered where the issue is arising at least and have a workaround when using SALT in Arch Linux in Virtualbox.

If I just select the general host shared folder as the extraction directory, it creates a folder 'extractedKDZ' or some such name in that general folder and the extraction does seem to proceed.

That clued me in to perhaps add the specific sub-folder I wanted to extract to (within the general host shared folder), as an additional shared folder in the Virtualbox settings. It seemed to work as I could select the specific sub-folder then directly for the extraction directory instead of just the general host shared folder.

Don't know why it was able to be done in FWUL in Virtualbox and not Arch Linux.

I would appreciate knowing how to use implement or use pkexec in lieu of gksu.

Regards,

S.
[Android Software/Hacking General [Developers Only]] ThePiGuy:
I believe pkexec is a drop in replacement for gksu except it also needs a policy to allow it to run

Have a look on Google for examples (sorry, I would provide one myself but I'm on my phone right now :D)
[Android Software/Hacking General [Developers Only]] sdembiske:
Re: 'Google for examples' - do you not think that was the first thing I did? I didn't become a member today.

Re: 'I believe pkexec is a drop in replacement for gksu' - try it, see if it works for you. Didn't work for me.

- Also, with respect to the policy to enable to run it: it looks like polkit may have to be installed but Authentication agent(s) are used to make the user of a session prove that the user of the session really is the user (by authenticating as the user) or an administrative user (by authenticating as an administrator). The polkit package contains a textual authentication agent called 'pkttyagent', which is used as a general fallback. If you are using a graphical environment, (you have to) make sure that a graphical authentication agent is installed and autostarted on login.

Cinnamon, Deepin, GNOME, GNOME Flashback, KDE, LXDE, LXQt, MATE, theShell and Xfce have an authentication agent already. Reference: https://wiki.archlinux.org/index.php/Polkit

I am using LXDE so I presume a specific policy is not required ... ?
[Android Software/Hacking General [Developers Only]] ThePiGuy:
Sorry. I didn't mean to offend you.

Why would I suggest it if it didn't work for me. I have it set up for SALT on my Ubuntu 18.04 and it works fine (gksu is no longer available in 18.04)

Ok I'm not sure about all the above. What I do know is something like https://stackoverflow.com/questions/21990213/replace-gksudo-with-pkexec-using-a-individual-message helped me
[Android Software/Hacking General [Developers Only]] steadfasterX:
https://github.com/Carbon-Fusion/build_fwul/commit/8dadd2edb688f9b6f60e01aa7192dc01a843c503

Whoa... Pls calm down we all wanna help each other. [MENTION=8699949]ThePiGuy[/MENTION] just told you to Google as he has no access to his pc atm and so can't show you some examples. My above link gives you such an example for starting SALT but ofc you need an authentication daemon running as you found out already. FWUL uses xfce and you lxde but both should have the daemon included. So you need either a generic policy (something with gksu in its name in /usr/share/polkit-1/actions/) or a specific one like mine.

Anyways that goes too far away from the topic now..
[Android Software/Hacking General [Developers Only]] smzubair:
Is there a way to extract .tot file in SALT? I can't find mm kdz for h810 10o, but a tot downloaded, I need to verify it and use it to upgrade to mm. (Renaming from tot to kdz is not working)
[Android Software/Hacking General [Developers Only]] steadfasterX:
Tot and kdz are different file formats and no you can't extract that one with salt. use the Windows Tool LG Firmware Extractor instead but you have to ensure that you do not increase the ARB! Once extracted compress all Bootloader files and upload them somewhere so I can check the ARB

Well and by the way you mentioned the version 10o and this is for sure not MM but LP . as far as I know there is no file available for you model with mm and arb of 2 or lower
[Android Software/Hacking General [Developers Only]] smzubair:
Yes you r right, I spend days on searching that mm kdz but no avail. At some link I find that tot file but not mentioned the version in there. In comments there were written that is mm for att, so I need to try it but actually I'm losing hope to find it. Lp on my phone after UsU is working fine since 15 days but in UsU unlock thread u mentioned on LP sooner or later we'll find problems, thats y daily I keep searching. I'll upload files and post link here. Thankx
[Android Software/Hacking General [Developers Only]] smzubair:
Hi here is the gdrive link

https://drive.google.com/open?id=179nROAls2DPJz9RmcyDnNpa1SLrsevNV

I think I includes all files u needed to check but if any remains than pls let me know. Thankx
[Android Software/Hacking General [Developers Only]] sdembiske:
v3.17 backup errors: H812 UsU Lineage15.1 (latest)

v3.17 backup errors: H812 UsU Lineage15.1 (latest)

In Arch - CR not forced: https://pastebin.com/XrjcshcT

In FWUL - CR forced: https://pastebin.com/mRqXYXxP

Result in FWUL with CR not forced same.

Backup goes immediately to 100% with nothing backedup.

Hasn't happened before on my device.

S.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Thx for the report.

There is no need to change CR unless you have permission errors. Just start SALT and leave it at auto and do the backup. Changing the CR is needed in very very rare cases only.

Nevertheless you found a bug :p

The CR mode is missing on backup so that's why it is failing there..

EDIT:

https://github.com/steadfasterX/SALT/issues/19
[Android Software/Hacking General [Developers Only]] asakman:
Cant take backup with salt

Hello,

I have a 815tr version of g4.

I try to take backup with salt. It quickly gets %100. But no backup is taken.

I copied the debug log. But xda doesnt allow me to put external links. So i copy the error related lines.

2018-08-09 11:51:19: F_BACKUP: choosen target directory was /root/salt_backup

2018-08-09 11:51:19: F_CHKFREE: started with this args: /root/salt_backup

2018-08-09 11:51:19: F_CHKFREE: valid dir specificed

2018-08-09 11:51:19: F_CHKFREE: ended.

2018-08-09 11:51:19: F_BACKUP: TFREE 11189 vs. 673

2018-08-09 11:51:19: F_BACKUP: choosen backup type was 2, Basic, 266240 KB, backup size: 673, backup path: /root/salt_backup

2018-08-09 11:51:19: F_BACKUP: Target directory has enough free space!

Traceback (most recent call last):

File "/root/programs/lglafng/extract-partitions.py", line 90, in <module>

main()

File "/root/programs/lglafng/extract-partitions.py", line 75, in main

comm = lglaf.autodetect_device()

TypeError: autodetect_device() missing 1 required positional argument: 'cr'

2018-08-09 11:51:31: F_MSGE: started

2018-08-09 11:51:32: ERROR: Backup incomplete! Check the log.

2018-08-09 11:51:32: 0

ownership of '/root/salt_backup' retained as root

Thanks.
[Android Software/Hacking General [Developers Only]] steadfasterX:
without a full log no help.

do not write http:// in front and instead of dots write e.g. "|" like bpaste|net/moo
[Android Software/Hacking General [Developers Only]] asakman:
Here you go.

bpaste.net/show/1f58783fd949
[Android Software/Hacking General [Developers Only]] steadfasterX:
SALT v3.18-0 released

Checkout the FAQ #9 for howto update to this brand new release

Legend for the summary topics:

New (SALT): Enhancements of the SALT main application - what you see and work with

Fix (SALT): Fixes of the SALT main application - what you see and work with

New (lglaf): Enhancements of the USB communication backend which SALT uses under the hood

Fix (lglaf): Fixes of the USB communication backend which SALT uses under the hood

v3.18

Released: 2018-08-10

Full changelog (SALT): at github (this version compared with the previous release)

Full changelog (lglaf): at github (this version compared with the previous release)

Summary changelog:

Fix (SALT): Backup function now allows to use paths with spaces within its name

Fix (lglaf): Backup was not working since 3.17 (*) (CR function was not implemented for the backup function)

(*) thanks to [MENTION=6302635]sdembiske[/MENTION] who first reported the issue (while i thought it was a forced CR issue there)
[MENTION=9358486]asakman[/MENTION] updating to v3.18 will fix your issue
[Android Software/Hacking General [Developers Only]] asakman:
Update has resolved backup problem. Thanks.
[Android Software/Hacking General [Developers Only]] autorun:
[android@fwul ~]$ git clone http s ://github.com/steadfasterX/SALT.git

Cloning into 'SALT'...

remote: Counting objects: 1283, done.

remote: Compressing objects: 100% (47/47), done.

remote: Total 1283 (delta 58), reused 79 (delta 46), pack-reused 1190

Receiving objects: 100% (1283/1283), 871.04 KiB | 355.00 KiB/s, done.

Resolving deltas: 100% (804/804), done.

[android@fwul ~]$ cd SALT

[android@fwul SALT]$ bash install-desktop.sh

install-desktop.sh: line 6: gksudo: command not found

ERROR: Please install gksudo!

[android@fwul SALT]$

use virtualbox 5.2.16 and run FWUL v2.7 , but cannot run the "bash install-desktop.sh"........

Thanks.
[Android Software/Hacking General [Developers Only]] steadfasterX:
You may should take a look on whats included in FWUL?! There is no need to install SALT in FWUL.

https://xdaforums.com/android/softw...-fastboot-driver-issues-t3526755/post70272684
[Android Software/Hacking General [Developers Only]] sdembiske:
Thank you for the link to the examples. I installed Manjaro with the XFCE display manager and then added the /usr/share/polkit-1/actions/it.binbash.pkexec.salt.policy file to my /usr/share/polkit-1/actions/ folder as the root user. With respect to the airootfs/root/customize_airootfs.sh, I was stumped on where exactly to put it - just in the root folder logged in as root user or ... ?

In any event, I am able to run SALT with the terminal command but when it comes to installing the SALT execute icon on the desktop, it throws up the error that I have to install gksu. OK, hmm ... I say 'what the hell', I'll give it a try again on this new install. So I put in the suggested install requirements for Manjaro

as per the OP

, sudo pacman -Sy gksu - and - much to my surprise, it immediately installs gksu-polkit 0.0.3-1. So, I presume this is an arch linux policy for using pkexec in lieu of gksu? So, i try to put the SALT execute icon on the desktop and again it tells me to install gksu ... I then try doing a policy up but have no clue how to somehow get gksu associated/replaced in a generic use sense with pkexec ... and no examples (endless research) seem to help ... in this regard. Yes, I'm definitely SALT install on other systems challenged ...

I then check FWUL and note there is no gksu-polkit 0.0.3-1 package installed. So, I then wonder if it perhaps should/could(?) be incorporated such that it makes SALT more versatile and user friendly to use other than only in FWUL? Don't get me wrong, I think FWUL is a great tool and as you know I have been a big continuing supporter of it with respect to installing and using it in Virtualbox, but at this point in time I only really have need for the SALT function and long as you offer the option for installing and using it in systems other than FWUL, I would appreciate some further research into the issues that are being presented now on new installs in other systems to make it a little more installation user-friendly.

Thank you again,

S.
[Android Software/Hacking General [Developers Only]] ThePiGuy:
Now I am back home and at my PC I can show you what I did to get mine working

1) get the polkit file from here (https://github.com/Carbon-Fusion/bu...olkit-1/actions/it.binbash.pkexec.salt.policy) and place it in /usr/share/polkit-1/actions

2) Edit the above file so this line (https://github.com/Carbon-Fusion/bu...t-1/actions/it.binbash.pkexec.salt.policy#L14) points to the salt file in your salt directory

3) Remove these lines (https://github.com/steadfasterX/SALT/blob/master/install-desktop.sh#L6-L8)

4) Replace gksudo with pkexec on this line (https://github.com/steadfasterX/SALT/blob/master/install-desktop.sh#L18)

5) Now execute the install-desktop.sh as usual and enjoy

Hopefully this helps - sorry I was brief before, I was on my phone and wasn't able to provide any more info

Edit: improve instructions
[Android Software/Hacking General [Developers Only]] steadfasterX:
The installer does not handle the new auth way in FWUL and you're right guys this should change.

https://github.com/steadfasterX/SALT/issues/20

Any further thoughts for implementing can go there - the discussion can stay here ofc
[Android Software/Hacking General [Developers Only]] sdembiske:
[MENTION=5545101]steadfasterX[/MENTION]

Thanks for the effort. All suggested file edits were implemented and while these changes did get the icon on the desktop, it failed in executing the program. See attached .png - it matters not whether it is marked executable or launch anyway, it simply does nothing - no spinning wheel, no error thrown up etc., simply nothing. Not sure where the problem is arising, I've double-checked all the file edits and they seem good. The SALT program resides in /home/sxxx/SALT and the execution command shows as pkexec /home/sxxx/SALT/salt.

Could it be a folder/file permissions issue or the need for an additional package to be installed? Keep in mind I've installed the latest Manjaro-XFCE version with all packages currently fully up-to-date with the most recent versions..
[Android Software/Hacking General [Developers Only]] ThePiGuy:
That popup is (sort of) normal. I get the same but mine is marked as executable.

What is the contents of your install-desktop.sh?

Edit: pkexec is obviously working to an extent - that popup will only appear if your policy is correct so no issues there (I think) ;)
[Android Software/Hacking General [Developers Only]] sdembiske:
Re: contents of install-desktop.sh - as below:

#!/bin/bash

##################################################################################

HERE="$(pwd)"

cat > ${HERE}/SALT.desktop <<EOFDSK

[Desktop Entry]

Version=1.0

Type=Application

Terminal=false

Name=SALT

Icon=${HERE}/icons/salt_icon.png

Comment=SALT - teadfasterX [A]ll-in-one [L]G [T]ool

Exec=pkexec ${HERE}/salt

EOFDSK

chmod +x ${HERE}/SALT.desktop

echo -e "\nStart icon created!"

if [ -d ${HOME}/Desktop ];then

cp ${HERE}/SALT.desktop $HOME/Desktop \

&& echo -e "\n\tStart icon installed to your desktop successfully!"

else

echo -e "\n\tOops - I cannot find your desktop..\n\tThis can happen when you installed Linux in your language.\n\tCopy it to your desktop like this"

echo -e "\n\tcp ${HERE}/SALT.desktop $HOME/<your-desktop-folder>/\n\n"

fi