[TOOL][LOCKED/UNLOCKED] SALT - The LG(up) revolution (begins)

Search This thread

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
Dear steadfasterX,

I have no encrypted device, so I tried to switch to develop version of SALT, following your FAQ at point 10).

I’ve launched SALT and done the update (that seemed ok) and at the request to restart SALT I’ve obtained
a windows pop up saying “SALT 3.22.11 : TESTING – ERROR”
“ERROR: FATAL ERROR!! Missing requirement python cryptography module (Python3) Read the SALT thread for how to install and try again !”

After then It was impossible to start again SALT, so I have been constrained to flash again FWUL (FWUL_v3.1_x86_64_8GB.zip)
over the USB pen-drive and I've tried again the same procedure , but obviously the result was the same.

What did i get wrong?
Thanks for you support

you can solve that by flashing mAid (fka as FWUL) --> nightly. it has everything on board already.
If you wanna do the same with FWUL 3.1 pls do the following command in a terminal:
sudo pacman -Sy python-zstandard

only if the above does not solve the issue:
sudo pip3 install cryptography

if none of them solves the issue, install the latest mAid nightly instead (see FWUL OP).


.-
 

verbage

Senior Member
Aug 12, 2014
161
74
Blah, bitten yet again by the LG G4 boot loop bug... This is the third time, yup... Though the first two times taught me to backup regularly, I was a bit more than two weeks out from my last backup on this newly failed G4 H811. And so I have now lost a series of important recordings, SMS text messages, and other data bits that have accumulated over the last two weeks. Or have I? I am thinking of a scheme to potentially recover it before any physical intervention like hot air reflowing, directed pressure, or whatever. Here is my thought.

With the bootlooping G4 H811, I was able to get into Download mode, and backup all 56 partitions totaling about 29 GB total. And I have available two more identical G4 H811s that are still available and functioning (yeah, what can I say--I am glutton for punishment...). So my thought was to write the 24 GB userdata partition that I salvaged from the now failed G4, and use TWRP to write it to the userdata partition of one of a functional G4.

If I were to do this, on booting the still functional G4, would I essentially be able to grab the two weeks of important data I mentioned above?

I guess I would also clone over the system partition because the G4s are running slightly different versions of steadfasterX's LOS16.

Any other salvaged partition images that I should clone over to the still functional G4 to make this all work?

Many thanks in advance for any guidance you might have!
 

verbage

Senior Member
Aug 12, 2014
161
74
With the bootlooping G4 H811, I was able to get into Download mode, and backup all 56 partitions totaling about 29 GB total. And I have available two more identical G4 H811s that are still available and functioning (yeah, what can I say--I am glutton for punishment...). So my thought was to write the 24 GB userdata partition that I salvaged from the now failed G4, and use TWRP to write it to the userdata partition of one of a functional G4.

So I've run into some hiccups in my potential strategy above, but I am hoping they are not insurmountable.

First issue was that my full userdata partition image made by SALT is about 24 GB in size as mentioned above. So it is too big for a FAT32 filesystem on MicroSD or as common on most USB drives (which could be accessed as OTG in TWRP). No problem, I simply prepared a spare MicroSD with an exFAT filesystem to deal with this. And so I went on my merry way to the still functional recipient G4 with this new MicroSD filled with boot, system, and userdata images expecting to be able to flash them via TWRP. But alas, it seems TWRP only allows flashing of boot and recovery partitions, not userdata. So even though I can access the 24 GB image under TWRP, there is no way to flash it. I looked around TWRP for advanced options that might let me override this, but no luck.

But then it occurred to me I could just put the G4 into download/fastboot mode, and use fastboot to flash over the 24 GB userdata partition. Seems logical--of course, I have used fastboot to flash smaller partition images like recovery on other systems, but I have never attempted to flash a huge, 24 GB like this. Any comments about this strategy before I give it a go?

BTW, I have been able to mount the 24 GB userdata partition under FWUL, and I can see the whole contents no problem. So I could directly grab system-level data like SMS and my fitness tracker data (another important thing I forgot about!). I am not talking about normally accessible user stuff under the emulated IntSD user space storage like Downloads, DCIM, etc. Maybe this is a solution, but how would I restore this under a functional G4???
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
So I've run into some hiccups in my potential strategy above, but I am hoping they are not insurmountable.

First issue was that my full userdata partition image made by SALT is about 24 GB in size as mentioned above. So it is too big for a FAT32 filesystem on MicroSD or as common on most USB drives (which could be accessed as OTG in TWRP). No problem, I simply prepared a spare MicroSD with an exFAT filesystem to deal with this. And so I went on my merry way to the still functional recipient G4 with this new MicroSD filled with boot, system, and userdata images expecting to be able to flash them via TWRP. But alas, it seems TWRP only allows flashing of boot and recovery partitions, not userdata. So even though I can access the 24 GB image under TWRP, there is no way to flash it. I looked around TWRP for advanced options that might let me override this, but no luck.

But then it occurred to me I could just put the G4 into download/fastboot mode, and use fastboot to flash over the 24 GB userdata partition. Seems logical--of course, I have used fastboot to flash smaller partition images like recovery on other systems, but I have never attempted to flash a huge, 24 GB like this. Any comments about this strategy before I give it a go?

BTW, I have been able to mount the 24 GB userdata partition under FWUL, and I can see the whole contents no problem. So I could directly grab system-level data like SMS and my fitness tracker data (another important thing I forgot about!). I am not talking about normally accessible user stuff under the emulated IntSD user space storage like Downloads, DCIM, etc. Maybe this is a solution, but how would I restore this under a functional G4???
1. Correct you just need system, boot and userdata to "clone" your old device . Any other partition has the potential to brick your working phone

2. You CAN use TWRP to do this but you need a shell and use the dd command

3. fastboot is the easiest way and there is no size limit in pushing files there. So give that a go for all the mentioned partitions of 1. It should work pretty fine.



Sent from my OnePlus 6T using XDA Labs
 
  • Like
Reactions: verbage

verbage

Senior Member
Aug 12, 2014
161
74
Thank you, steadfasterX, for the response!

I went into fastboot/bootloader mode on the recipient G4, and using FWUL, attempted to flash these three partitions, but ran into an error with each one at the end of each operation (see below). The phone was definitely in the correct bootloader mode as it was recognized with the "fastboot devices" command as per below. I tried it with Windows version of fastboot after FWUL, but the same error. So close to potential victory, but not quite yet.

To make the three partition images with SALT, I used the Backup option which was pretty straightforward. And as mentioned previously, I was able to mount the userdata partition image to browse it, and is contains seeming good data. So I don't think the images are the problem.

I must be missing something...

Code:
[[email protected] ttt]$ fastboot devices
61b3114b	fastboot
[[email protected] ttt]$ fastboot flash boot boot.img
target reported max download size of 536870912 bytes
Sending 'boot' (40960 KB)...
OKAY [  1.334s]
Writing 'boot'...
FAILED (remote: unknown command)
Finished. Total time: 1.440s
[[email protected] ttt]$ fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magic
Erasing 'system'...
FAILED (remote: unknown command)
Finished. Total time: 4.809s
[[email protected] ttt]$ fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magic
Erasing 'userdata'...
FAILED (remote: unknown command)
Finished. Total time: 26.277s
[[email protected] ttt]$
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
Thank you, steadfasterX, for the response!

I went into fastboot/bootloader mode on the recipient G4, and using FWUL, attempted to flash these three partitions, but ran into an error with each one at the end of each operation (see below). The phone was definitely in the correct bootloader mode as it was recognized with the "fastboot devices" command as per below. I tried it with Windows version of fastboot after FWUL, but the same error. So close to potential victory, but not quite yet.

To make the three partition images with SALT, I used the Backup option which was pretty straightforward. And as mentioned previously, I was able to mount the userdata partition image to browse it, and is contains seeming good data. So I don't think the images are the problem.

I must be missing something...
Ok your fastboot mode is pretty limited , say thx to tmo. Anyways just switch to TWRP then and assuming you have all 3 partitions directly on your external sdcard these are the cmds to flash them:

adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot
sync
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=512
sync
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=1024
sync

After that reboot and it should be fine.



Sent from my OnePlus 6T using XDA Labs
 
  • Like
Reactions: verbage

verbage

Senior Member
Aug 12, 2014
161
74
Ok your fastboot mode is pretty limited , say thx to tmo. Anyways just switch to TWRP then and assuming you have all 3 partitions directly on your external sdcard these are the cmds to flash them:

Thanks so much for your help with this, steadfasterX! In the long run, I might not have to use it because I started some intensive freezer therapy with the wonky G4 last night, and was able to backup the two critical things I wanted, and then restore them to the new surrogate G4. Whatever the case, I am pleased to see how flashing full partition images can be done directly with dd in TWRP since TMo seems to have crippled fastboot mode on the H811 :mad: Indeed, given my luck with the G4, I can certainly see it coming in handy in the future.

By the way, thank you for the FWUL+SALT combo--it works great!
 
  • Like
Reactions: steadfasterX

LuKePicci

Member
Apr 30, 2014
22
5
Trying to make my first backup. Running FWUL in virtualbox. I can confirm phone is in Download Mode. SALT is not detecting the phone, even if lsusb shows it. I also updated SALT (it was on latest master already).
Here is the debug log from SALT: https://pastebin.com/PkvAFBSQ

I can't find the info about running FWUL into virtualbox, the link about "doing critical things in virtualbox" is broken. FWUL can see the device in adb shell, USB filter for the VM matches everything from LG. (id 1004)
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
Trying to make my first backup. Running FWUL in virtualbox. I can confirm phone is in Download Mode. SALT is not detecting the phone, even if lsusb shows it. I also updated SALT (it was on latest master already).
Here is the debug log from SALT: https://pastebin.com/PkvAFBSQ

I can't find the info about running FWUL into virtualbox, the link about "doing critical things in virtualbox" is broken. FWUL can see the device in adb shell, USB filter for the VM matches everything from LG. (id 1004)
Do you have USB 2 or 3 configured in VirtualBox ? Try switching to the other. When doing this you might need to set the USB filter again . This is (just) one reason why I recommend usb stick boot..
You can also try to put your phone into Download Mode first and then boot FWUL. for this you need you have Auto USB filtering enabled of course.



Sent from my OnePlus 6T using XDA Labs
 

LuKePicci

Member
Apr 30, 2014
22
5
Will try, at least I know it should work. It would be a little of a problem to boot FWUL natively on my device as it has secure boot and bit locker enabled on the tpm, so I usually keep all live iso I would need to boot into a secure-boot enabled USB drive with Grub, booting other live ISO in turn. Also my device has no integrated keyboard, if something goes wrong in arch with the mobile keyboard or the touchscreen or the docking station interface it would be quite annoying. AFAIK we have touch-capable bootloaders/recoveries for both windows and Android but not for Linux.
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
Will try, at least I know it should work. It would be a little of a problem to boot FWUL natively on my device as it has secure boot and bit locker enabled on the tpm, so I usually keep all live iso I would need to boot into a secure-boot enabled USB drive with Grub, booting other live ISO in turn. Also my device has no integrated keyboard, if something goes wrong in arch with the mobile keyboard or the touchscreen or the docking station interface it would be quite annoying. AFAIK we have touch-capable bootloaders/recoveries for both windows and Android but not for Linux.
at least for secure boot there are good news if you are using the nightlies: they support that ;)
https://code.binbash.rocks:8443/mAid/build/wiki/Secure-Boot

.-
 

_bobby_tables_

New member
Mar 4, 2020
1
0
US991 to H811 to gain VoLTE capabilities?

This is probably a stupid question, but...

I have an LG G4 US991 that is facing obsolescence due to lack of VoLTE support. The H811 model does have VoLTE support. Can I flash my US991 with an H811 ROM to gain VoLTE? Are there physical differences between the LG G4 models that would prevent such a ROM switch? Thanks.
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
This is probably a stupid question, but...

I have an LG G4 US991 that is facing obsolescence due to lack of VoLTE support. The H811 model does have VoLTE support. Can I flash my US991 with an H811 ROM to gain VoLTE? Are there physical differences between the LG G4 models that would prevent such a ROM switch? Thanks.
Is VoLTE worth it? Imho no but maybe that's a personal thing.
Anyways converting a device is EXTREMELY risky. Not because of hardware diffs (all g4 models are identical, ok besides the h818 which has a diff panel) but because of the PBL (primary bootloader) which sits in a protected area and verifies the area which can be flashed (i.e. what you flash by kdz). It's all about signatures (we can leave out ARB for the moment) . The thing is without the PBL (which you can't pull) nobody else then the us991 OEM can say if you can convert without a hard brick.

You can though (depends on your ARB): unlock with UsU, flash boot , modem and system of a stock h811 (must match your current ARB!!!) and you might can get VoLTE ( your provider must support that as well, often needs then a manual activation too). No guarantees here as well but the chance for a hard brick are at 1% if you follow the guide . And as you have a fusing model you could even revert UsU so if that didn't worked and you wanna still risk a hard brick you could try a convert then (chance for a hard brick are here 80:20).

You can recover from hard bricks by using qfil but you need proper qfil files for your model and ARB (which could be a real issue for your model )!!! Or by using a box but those work usually only up to ARB 2.



Sent from my OnePlus 6T using XDA Labs
 
Last edited:

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
New Release

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

Legend for the summary topics:
Fix/New (SALT): Fixes & Enhancements of the SALT main application - what you see and work with
Fix/New (lglaf): Fixes & Enhancements of the USB communication backend which SALT uses under the hood
Fix/New (kdztools): Fixes & Enhancements of the KDZ extraction backend which SALT uses under the hood

v3.22
Released: 2020-03-09
Full changelog (SALT): at github (this version compared with the previous release)
Full changelog (lglaf): at github
Full changelog (kdztools): at github
Summary changelog:

  • ATTENTION FOR FWUL (v2.x, v3.x) users:
    Upgrading to this Version WILL BREAK SALT without doing a FULL system upgrade (which can take hours, downloading multiple GB, may even break on low RAM systems)
    Instead it is highly recommended to use the new mAid nightlies which are in RC phase already and so reasonable stable.

  • Fix (kdztools): some fixes for KDZ extractions
  • Fix (SALT): UsU and ARB detection in rare cases
  • Fix (SALT): no output for several lglaf based operations
  • Fix (SALT): backup (custom) progress bars
  • Fix (SALT): when a folder or filename contained a space SALT failed to parse and extract
  • Fix (SALT): several things around ARB and ARB detection
  • Fix (SALT): screwed part listing
  • Fix (SALT): log upload
  • New (SALT): added a pre-check after the user selected a directory: when the path exists and containing image files the user get prompted to either retry or continue.
HINT:
Newer devices using UFS storage (e.g. G5, G6, ..) still need to switch to the DEVELOP/TESTING branch (see FAQ)
 
Last edited:
  • Like
Reactions: cheloz and nebulac

hbtariq123

New member
Mar 31, 2020
4
0
LG g5 H820n11 att

i upgraded my lg g5 att H820n11 with lgup to oreo 8.0 with a tot file and after completion my phone turned off and then it is dead. and in device manager there is com 18 lge androidnet usb serial port. what i do now...plzz help me.. thanks
 

xda-yup

Member
Dec 8, 2019
18
12
Having SALT issues while trying to do initial backup before trying UsU on my H815. 3 issues:

1. I tried the 15GB FWUL version of FWUL 3.1 and this worked fine to boot via usb, but SALT got "fatal error- missing phyton cryptography module" error on trying to update SALT.

2. Because of error 1, wiped USB drive and installed latest mAid nightly mAid_v2020-04-07. Booting and the mAid OS are fine, SALT recognises device fine, but SALT gives error on trying to do full backup, same error as comment 819, i'm backing up to a 4TB NTFS drive with about 3.9TB free on it.
---so followed steps from comment 819, backup of everything else works fine except for userdata.img, which always 'succeeds' but then fails md5 check. this happened on both SALT - 3.22-12:STABLE. (all 3 branches stable per faq) and
SALT - 3.23-0:TESTING (all 3 branches develop per faq). Tried again after factory reset H815 phone (it's still unmodified) and with same results. Any ideas why userdata.img is always failing md5 check? Is userdata even important to backup, or is it just photos and stuff which i've already deleted anyway from factory reset? If not important i'll just skip userdata backup as i have everything else backed up via SALT now.

3. When i go to SALT > Advanced > debug log, i am unable to export the log to provide here, get "Error in module 'haste' while uploading logfile..." among others.

My device is H815 20e TWN, on MM fully stock (no modding at all yet) if it helps. I've really tried to follow all threads and FAQs so sorry if i've missed something.
 
Last edited:

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
Having SALT issues while trying to do initial backup before trying UsU on my H815. 3 issues:

1. I tried the 15GB FWUL version of FWUL 3.1 and this worked fine to boot via usb, but SALT got "fatal error- missing phyton cryptography module" error on trying to update SALT.

2. Because of error 1, wiped USB drive and installed latest mAid nightly mAid_v2020-04-07. Booting and the mAid OS are fine, SALT recognises device fine, but SALT gives error on trying to do full backup, same error as comment 819, i'm backing up to a 4TB NTFS drive with about 3.9TB free on it.
---so followed steps from comment 819, backup of everything else works fine except for userdata.img, which always 'succeeds' but then fails md5 check. this happened on both SALT - 3.22-12:STABLE. (all 3 branches stable per faq) and
SALT - 3.23-0:TESTING (all 3 branches develop per faq). Tried again after factory reset H815 phone (it's still unmodified) and with same results. Any ideas why userdata.img is always failing md5 check? Is userdata even important to backup, or is it just photos and stuff which i've already deleted anyway from factory reset? If not important i'll just skip userdata backup as i have everything else backed up via SALT now.

3. When i go to SALT > Advanced > debug log, i am unable to export the log to provide here, get "Error in module 'haste' while uploading logfile..." among others.

My device is H815 20e TWN, on MM fully stock (no modding at all yet) if it helps. I've really tried to follow all threads and FAQs so sorry if i've missed something.

userdata "just" contains your photos, apps etc. it is not a critical part when it comes to e.g. unbricking a device so if you can live with loosing your data (which you already have due to the factory reset) you can skip that. no without the log I cannot say why the md5 is failing here. will check why uploading failing.

.-
 
  • Like
Reactions: xda-yup

wantpizza

Senior Member
Nov 3, 2007
98
6
Naperville
Reading between the lines.

Ok your fastboot mode is pretty limited , say thx to tmo. Anyways just switch to TWRP then and assuming you have all 3 partitions directly on your external sdcard these are the cmds to flash them:

adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot
sync
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=512
sync
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=1024
sync

After that reboot and it should be fine.

Sent from my OnePlus 6T using XDA Labs

Let me just say 1000 apologies for interrupting this thread. But I am in a tough spot.

TL/DR - Can I use TWRP to dd my old user data from a LGUP backup (from Nougat) into a fresh install of Lineage 17.1? Just temporarily to recover some improperly backed up userdata? I am willing to downgrade or almost anything to get there - just looking for simple, safe and no risk to my newly unlocked bootloader :D:D.

Long version: Okay - again - 1000 apologies. I hate when others bust into a thread... but this stuff looks the closest to what I am imagining my solution to be.

I had -
LG V20 - AT&T version H910
Software version - H91010p
Android Security patch level: August 1, 2017
Kernel Version: 3.18.31
TWRP version 3.3.1-0

Before doing anything - I did a full LGUP dump - INCLUDING MY USER DATA
I also installed LG Switch and did a full backup.
Next - I followed this DirtySanta post to Unlock the bootloader etc.

I am now running LOS17.1 - an Android Q ROM
Android Security patch level = April 5, 2020

So - I am looking for a way to get back some accidentally lost user data.
I tried LG switch and it just wants to backup my new install. Not sure how you get it to restore data...
I tried LGUP and no where does it say anything about restoring...
I am willing to try a dd trick in Linux (currently running Pop_OS and have Manjaro too) or Win 10 if need be.
I am willing to fubar my current LOS17 install. I will just reinstall after extracting my data.
I am willing to downgrade to Nougat or.... anything.
As long as I don't lose my root & unlocked boot loader, TWRP.

BTW - I tried just mounting the lgup file in linux and get some sort of bad superblock error.

I have the LGUP dump on the external at /LGUP...

So in TWRP do I just go to Advanced/Terminal and

dd if=/external_sd/LGUP/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=1024
sync

Do I need to restore anything else? I don't care if I get ForcedClose of some programs as long as FX File explorer works long enough to fetch my data? Oh and - will this work? My userdata is 52.2 GB...

Risks? Thinking of just trying it.

Is there another way?
Thanks in advance for any tips, tricks, breadcrumbs or best of all ANSWERS!!
Best Regards!!

---------- Post added at 04:50 PM ---------- Previous post was at 04:44 PM ----------

I might have already found a gotcha... /data/media on the phone shows 39 GB free of 51 GB... So even if I delete everything - not sure how to get 52.2 GB into that partition? Hopefully someone smarter than me will explain how...
Thanks.
 

wantpizza

Senior Member
Nov 3, 2007
98
6
Naperville
Hold everything!!
I was able to recover my missing data.
I reverted back to Nougat and then LGSwitch was able to restore my data.
I grabbed it up onto a SD card and flashed forward to Pie.
Sorry for the interruption. It is still a very interesting thought question.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    open a terminal (square black icon in the panel)
    type:
    sudo ./programs/SALT/salt --experimental

    but beware even when there is a "KDZ flash" button this is not yet fully implemented. you have to use "flash folder" instead. the reason is that when choosing kdz flashing with LGup not all partitions get flashed. e.g.
    I just want to thank you for your SALT tool. It helped me a lot.

    My LG G2 D802 was really in a strange stage. I tried to flash to stock firmware with various tools runing on Windows but nothing worked.
    With this experimental mode of salt I was able to flash my LG G2 to stock firmware and then move on to LineageOS 18.1 and everything is working nice and smooth.

    I almost gave up on my phone but your tool saved my good old phone from ending up at the recycling depot!
  • 84
    Before reading any further


    This thread is best viewed in a browser!
    Mobile apps may parse the XDA formatting not correctly and may screw things up.


    About

    salt_pre.png


    steadfasterX's All-in-one LG Tool (SALT)



    SALT is able to communicate with your device while in download mode and provides these features:

    Detects your:
    • ARB
    • device model
    • firmware version (short)
    • firmware version (full)
    • country of firmware
    • Secure device state
    • Battery Level

    Is able to:
    • working completely without any LG dll (no more issues with replacing LGUP_xxxx.dll anymore!)
    • backup your device (predefined modes: full & basic and since v3.20 even a custom mode)
    • extract KDZ files
    • display your partitions (including what each partition is like bootloader etc!)
    • open a shell on the device*
    • ERASE (HOLY SH*** this is DANGEROUS!) one or multiple partitions
    • verify a taken backup (read all about this here)
    • self-update

    In development (already working on LP firmware! NOT on MM or N! read the Note):
    • Flashing a folder (e.g. from a previous backup)
    • Flashing a KDZ
    IMPORTANT NOTE: Do not use the underlying code backend (lglaf /partitions.py) to RESTORE image files (yet)!
    Reason:
    LG has changed the mechanism in MM and later for writing to a partition! It seems that the reason is that each write must be authenticated differently or at least another one for the fsync.




    Requirements

    mAid (fka as FWUL) (recommended)

    No requirements as SALT and everything needed is included there!
    Highly recommended: booting mAid from USB stick to avoid any connection issues.
    Ensure you use the latest mAid release and start SALT by opening the LG folder on the desktop.
    Now just click the update button once SALT is started to ensure you have the latest and greatest SALT version!

    Linux:
    I recommend mAid (fka FWUL) in general but SALT is made to be run on any Linux (if you can set it up).
    Requirements to install before beginning:
    yad, git, python3, python3-pyusb, python3-crypto, python-zstandard (python3), python-pip (python3) and pkexec/policykit
    (instead of pkexec/polkit gksudo will work too but this has been removed from many distributions)

    Examples:

      • On Arch: sudo pacman -Sy polkit git xterm python-pyusb python-crypto python-pip
        and trizen -Sy yad python-zstandard (hint: you may need to install trizen first) - and you need to manually do this until it has been fixed upstream: workaround
        and sudo pip3 install cryptography
      • on Manjaro: sudo pacman -Sy polkit yad git xterm python-pyusb python-crypto trizen python-pip python-zstandard
        and you need to manually do this until it has been fixed upstream: workaround
        and sudo pip3 install cryptography
      • on *buntu, Debian, Mint and on all derivates of those: sudo apt install policykit-1 yad git xterm python3 python3-usb python3-crypto python3-pip
        and sudo pip3 install zstandard and sudo pip3 install cryptography
    you may need to setup your udev rules as well: android-udev-rules thats another reason why I recommend mAid ;) this is all implemented there out of the box..


    Windows:
    Windows users should use SALT in mAid which is highly recommended for many operations with Android devices. Also read & follow the above topic "mAid (fka FWUL) (recommended)".


    Installation (not needed on mAid! Just open the LG folder and start SALT)


      • open a terminal
      • type:
        git clone https://github.com/steadfasterX/SALT.git
        cd SALT
        bash install-desktop.sh
      • read the output and if required copy the SALT.desktop file manually to your Desktop.
      • double click the SALT icon or while in a terminal start SALT with: sudo ~/SALT/salt
      • When starting SALT the first time you will be prompted to install necessary backend tools.
        Choose YES to install them!

    Note:
    Even when the downloads tab in this project will contain releases the most up-to-date code can be fetched via the above way only.
    Nevertheless you can download the tar file from the Downloads tab but ensure that you're using the latest code by starting an update (Update button in SALT) afterwards.


    Usage

    Start the device in download mode and connect it to the PC.
    Start SALT.
    Usually the download mode should be fully ready in 20 - 60 seconds after you see the cycling arrow screen.
    But some devices needs up to >= 90 seconds until SALT can detect your device.
    If you still get trouble connecting boot the device in download mode and let it connected that way while rebooting mAid (fka FWUL) or your personal Linux.


    Known Issues

    A current list of all known issues can be found at the bugtracker



    Support / IRC Channel / TG Group
    IRC means Internet Relay Chat and you will get best support there only.
    Personally I'm only online there from Mondays to Fridays only but there are maybe others (maybe YOU too) who can help as well.

    Choose how to get in:
      • mAid (fka FWUL): just click the IRC hexchat icon on the desktop
      • PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
      • Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
      • Web (KiwiIRC-Web,Freenode-Webchat])
      • When you have to choose a channel it is: #carbonfusion-user
      • When you be asked for a server network choose: freenode
      • It wouldn't hurt to read this as well when you are new to IRC: beginners guide (for a quick one read just: "Etiquette")
        Simplified said: be polite, don't ask to ask, be patient(!), respect the timezones, help others.

    Like mAid (fka FWUL) SALT has now a Telegram Group which is bridged with my above IRC channel as well.
    Many ppl are feeling more comfortable with TG theses days and as I now have a bridge between I am ok with it...

    Feel free to join
    LGLAF+SALT Users TG Group


    Credits (without them no SALT)

    SALT is based on:
      • YAD (yet another dialog) -> GUI
      • the awesome LGLAF code and reverse engineering by Peter Wu & friends ;)
        -> general communication with the device like: flash, dump, getinfo, erase, list partitions, ...
      • kdztools by Elliott Mitchell -> extracting KDZ files
      • MANY enhancements by steadfasterX -> bring all together plus much more :)

    SALT's own sources:

    Special credits:
      • @runningnak3d for his incredible reverse engineering skills which makes SALT better and better each day :) it's great to have you in the community !
      • tuxuser for making LAF communication on Nougat possible and for his great support!




    XDA:DevDB Information
    SALT - teadfasterX's [A]ll-in-one [L]G [T]ool, Tool/Utility for the LG G4

    Contributors
    steadfasterX
    Source Code: https://github.com/steadfasterX/salt


    Version Information
    Status:
    Stable
    Current Stable Version: 3.22
    Stable Release Date: 2020-03-09

    Created 2017-12-11
    Last Updated 2020-08-26
    33
    FAQ - Frequently Asked Questions

    • 1) How can I get into the download mode?

      Boot your phone into download mode --> the following guide is 100% working and bulletproof:
      1. take out battery and unplug USB cable
      2. plugin USB cable to your PC (while battery ist still out)
      3. wait until you see the missing battery icon (question mark within a battery symbol)
      4. press Volume up and while keeping it pressed put battery in (take care that you do not press the power button)
      5. keep pressing Volume up until you see "Download mode"

      If that does not work for you try it this way instead:
      1. unplug USB cable
      2. power down device or pull out battery
      3. put battery back
      4. press Volume up and while keeping it pressed plugin USB cable to your PC (take care that you do not press the power button)
      5. keep pressing Volume up until you see "Download mode"
      Your phones screen should look similar to this afterwards:
      View attachment 4284063

    • 2) Does SALT work on LOCKED devices ?
      Oh what a great question ;) YES it DOES. :)
      But keep in mind.. even when you can flash/erase partitions with SALT this still requires either valid/untouched pure LG files or an unlocked device.

    • 3) Can I unlock my LG G4 device with SALT?
      Holy moly --- NO! YES! ( https://bit.do/unlockg4 for the guide)

    • 4) What is the meaning of ARB?
      Anti-Roll-Back a stupid mechanism to brick your device. Read on here

    • 5) Do I need a specific ARB version to work with SALT?
      You can start and use SALT with any ARB version. Later when flashing is fully implemented you will be warned when your ARB is lower then then one you want to flash.

    • 6) Which firmware versions does SALT support?
      Any of lollipop, marshmallow and nougat

    • 7) Which devices does SALT support?
      In theory ANY LG device supported by the lglaf backend.
      Confirmed devices are:
      - G2
      - G3
      - G4 (H810, H811, H812, H815, H818, H819, VS986, LS991, F500)
      - G5: unknown may only work with modifications like mentioned in the Release Notes for v3.20
      - G6 (H871) only with modifications: see Release Notes for v3.20. Please help in making this fully working! OP -> topic "Support"
      - V10 (H900)
      - V20 (H910) only with modifications: see Release Notes for v3.20. Please help in making this fully working! OP -> topic "Support" OP -> topic "Support"
      - yours ;) -> report your device by uploading the debug log from the advanced menu and share the bpaste link!
      - again: in theory any LG device will work with SALT . All newer devices (G5 and later) will just need the mentioned modification: see Release Notes for v3.20. Please help in making this fully working! OP -> topic "Support" OP -> topic "Support"
      .. this will change in one of the next versions as I will implement an automatic detection , of course!

    • 8) SALT is prompting me after a backup for verification. I have many Warnings|Errors what does that all mean?
      Read on here about he verification feature in SALT: MD5 verification

    • 9) I have installed SALT already. Is it possible to just update it?
      Of course thats one of the awesome features in SALT.
      Since v3.7 SALT will check for a new version on startup automatically and prompt you to update if necessary.
      If it ever fails just click the update button at the bottom.

    • 10) I have installed SALT already. Is it possible to switch between STABLE and TESTING channels?
      Note: TESTING may have issues, brick your device, let your phone or PC explode. so use it with care.
      So if you wanna still switch the channels click the update button at the bottom first.

      If you want to be on/switch to the STABLE channel choose:
      Code:
      SALT branch => [B]master[/B]
      kdztools branch => [B]master[/B]
      lglaf branch => [B]master[/B]
      Click update and restart SALT afterwards.

      If you want to be on/switch to the TESTING channel choose:
      Code:
      SALT branch => [B]develop[/B]
      kdztools branch => [B]develop[/B]
      lglaf branch => [B]develop[/B]
      Click update and restart SALT afterwards.

    • 11) I have a partition file with the extension: [ bin | image | img | mbn ]. How can I convert this?
      The extension is not important. The way how you extract files - is. That's why I say all the time use SALT.
      On Windows the file extension matters a lot which is not the case for Linux/Android.
      So if you see a guide mentioning to use a "bin" file and you have the file but with an extension of "image" (or vice-versa) it does not matters.
      There is no need to convert anything as they all are just raw image files.

    • 12) I want to backup but SALT says I have too less space for that! How can I get more disk space in FWUL (or my VM)?
      Read FAQ #5 in the FWUL thread (yes even when you are using Windows and do not run FWUL but any other Linux + SALT) and setup a shared folder with enough disk space as described.
      Point to that new shared folder (ensure you do not use spaces in the foldername and that you have created a new folder in the start of the shared folder) when asked for a backup location in SALT.

    • 13) I do *NOT* use FWUL because I have my own Linux running and you told me to install tmate. How?
      Current instructions can be found here: https://tmate.io/
      Ensure you create a SSH key as that is needed to start tmate later:
      Code:
      ssh-keygen -b 4096 -f ~/.ssh/tmate -N ''
      (note: the characters '' are 2 single quotes)

      Install tmate on Arch Linux / Arch variants like Manjaro, ..:
      Code:
      trizen -Sy tmate
      or: yaourt -Sy tmate (yaourt is [U]DEPRECATED[/U]!)

      Install tmate on Ubuntu / Ubuntu Variants like Kubuntu, Linux Mint, ... :
      Code:
      sudo apt-get install software-properties-common
      sudo add-apt-repository ppa:tmate.io/archive
      sudo apt-get update
      sudo apt-get install tmate

    • 14)Is there a Windows version of SALT available or planned?
      No. NEVER. Just use FWUL which has SALT already included and everything setup to manage your Android device.
      If you have issues in running FWUL report them in the FWUL thread.

    • 15)What is GPT compability (LG G4 only)?
      I saw people often confused about that option and here is what it is and does:
      1) This is only valid for the LG G4 models. If you have another one ignore it.
      2) If you have a LG G4 and not UsU'd (so an official unlockable model) - just ignore it.
      3) If you have a LG G4 and UsU'd your device (or planning to do so) this option is for you.
      Background:
      SALT checks the partition table (GPT) to find out what ROM model is compatible with an UsU'd device. The reason is quite easy: all G4 models have the same hardware (except the h818 but thats another story). Due to the incredible amount of country specific models not many ROMs exist for every model so I checked what's needed to bring a ROM meant for another model to an UsU'd device. I recognized quickly that the partition table is different on several models and even on a same model with another firmware (e.g. between LP and MM it changed for some models). The only thing we need on custom ROMs for the G4 is a correct sized system partition as that one differs for some. Another thing needed on some (mostly US models) is a carrier partition instead of a cust one. Basically that's all SALT checks at the end as if a ROM expects to mount the carrier partition it must be there.
      TL;DR
      The GPT compatibility shows what ROM you can install on an UsU'd device - if there is none for your specific model.

    • 16) Is it possible to extract TOT files with SALT?
      No but you can use this windows tool to extract TOTs: https://forum.xda-developers.com/showthread.php?t=2600575

    • 17) I want to backup/extract my user data (internal storage) with SALT and my device is encrypted. Is that possible and can SALT unencrypt that data?
      SALT is doing 1:1 copies of your partitions which is really 100% identical to what is on your phone. If your data is encrypted SALT will backup that in the current state which means encrypted because within the download mode your userdata partition does not get mounted. So what does that mean? Yes you can backup your userdata but .. you can NOT mount it afterwards as it is just encrypted data. afaik there are no tools available to unencrypt but I may be wrong (let me know if you are aware of any).
      Does it makes sense to backup encrypted data? Depends on what you want to get. If you want to have a really full 1:1 copy of the current phone it might be useful if you are able to restore that data (e.g. via TWRP). Keep in mind though that encryption usually needs more partitions to be restored (e.g. persist or others) which contain information/keys,... as well.
      TL;DR
      You can but it is usually not very useful.



    • 1000a) I have an issue not listed here - what should I do?
      1000b) Is there a SALT logfile and how can I share it?
      Advanced Menu -> SALT Debug log -> Upload button -> right click the link or open it in a browser and copy from there
      Picture guide:
      screenshot_001.jpg
    18
    Changelog

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

    Legend for the summary topics:
    Fix/New (SALT): Fixes & Enhancements of the SALT main application - what you see and work with
    Fix/New (lglaf): Fixes & Enhancements of the USB communication backend which SALT uses under the hood
    Fix/New (kdztools): Fixes & Enhancements of the KDZ extraction backend which SALT uses under the hood

    v3.22
    Released: 2020-03-09
    Full changelog (SALT): at github (this version compared with the previous release)
    Full changelog (lglaf): at github
    Full changelog (kdztools): at github
    Summary changelog:

    • ATTENTION FOR FWUL (v2.x, v3.x) users:
      Upgrading to this Version WILL BREAK SALT without doing a FULL system upgrade (which can take hours, downloading multiple GB, may even break on low RAM systems)
      Instead it is highly recommended to use the new mAid nightlies which are in RC phase already and so reasonable stable.

    • Fix (kdztools): some fixes for KDZ extractions
    • Fix (SALT): UsU and ARB detection in rare cases
    • Fix (SALT): no output for several lglaf based operations
    • Fix (SALT): backup (custom) progress bars
    • Fix (SALT): when a folder or filename contained a space SALT failed to parse and extract
    • Fix (SALT): several things around ARB and ARB detection
    • Fix (SALT): screwed part listing
    • Fix (SALT): log upload
    • New (SALT): added a pre-check after the user selected a directory: when the path exists and containing image files the user get prompted to either retry or continue.
    HINT:
    Newer devices using UFS storage (e.g. G5, G6, ..) still need to switch to the DEVELOP/TESTING branch (see FAQ)


    Older releases

    v3.21
    Released: 2018-12-21
    Full changelog (SALT): at github (this version compared with the previous release)
    Full changelog (lglaf): at github (this version compared with the previous release)
    Full changelog (kdztools): at github (this version compared with the previous release)
    Important Note:
    From this release on the system requirement have changed!
    You need to ensure you install the python module "zstandard" - read the OP for how or when using FWUL use the latest FWUL nightly which comes with everything pre-installed.
    Summary changelog:
    • New (kdztools): KDZ extractions have been EXTREMELY enhanced. Means we can now even extract newer KDZ files up to the latest LG flagship (e.g. G7/V30).
      This has been fully achieved by runningnak3d ! it's always a pleasure to work with him ;)
    • Fix (kdztools): extraction failed when a KDZ had unallocated space (e.g. some H811 ones but also others)
    • Fix (SALT): python version for KDZ/DZ extraction
    • Fix (SALT): Browsing the mounted directory after using the Image mounter (advanced menu) will now use full permissions by default
    • New (SALT): mounting an image (advanced menu): previously when a user hasn't unmounted an image file he had to unmount it manually (terminal). now SALT offers a dialog to do so for the user instead.
    • New (SALT): from now on SALT can detect when a user tries to mount an image file from a vbox shared folder and denies mounting it
    • Fix (lglaf): Do not use "G4" as detected model (as there is no safe way to identify a model via the usb info)
    • Hint from a previous release: preparation for UFS devices (all newer LG models). Hint: you can use SALT now on newer devices but this requires a manual change in lglaf atm:
      Code:
      cd ~/programs/lglafng
      git checkout develop
      The above is NOT needed on non-UFS devices (like the G2,G3,G4, ...). If you are unsure open the advanced menu in SALT and check if the partition listing is working - if it is empty try the above otherwise you don't need to.
      The above handling and UFS detection will be done automatically in a future release of SALT!

    v3.20
    Released: 2018-11-30
    Full changelog (SALT): at github (this version compared with the previous release)
    Full changelog (lglaf): nothing has changed
    Summary changelog:
    • Fix (SALT): when the size of a backup cannot be calculated SALT continues with the free disk space check nevertheless
    • Fix (SALT): "direct flashing" message optimized
    • Fix (SALT): permissions on logfiles and all 3rd party paths
    • Fix (SALT): User detection was wrong (pkexec) and so the resulting program paths as well
      ATTENTION:
      You may get prompted to re-download lglaf, sdat2img and kdztools due to the corrected paths. Just do so and it will be fixed next time you start SALT.
    • New (SALT): Introducing the CUSTOM backup mode! Now you can not just choose from the predefined BASIC and FULL mode but also can choose CUSTOM. This CUSTOM mode allows to choose from your existing partitions. Plus: while backing up a beautiful multi-progress bar is showing the progress.
    • New (SALT): preparation for UFS devices (all newer LG models). Hint: you can use SALT now on newer devices but this requires a manual change in lglaf atm:
      Code:
      cd ~/programs/lglafng
      git checkout ufs-test
      The above is NOT needed on non-UFS devices (like the G2,G3,G4, ...). If you are unsure open the advanced menu in SALT and check if the partition listing is working - if it is empty try the above otherwise you don't need to.
      The above handling and UFS detection will be done automatically in a future release of SALT!

    v3.19
    Released: 2018-08-23
    Full changelog (SALT): at github (this version compared with the previous release)
    Full changelog (lglaf): nothing changed
    Summary changelog:
    • Fix (SALT): (G4 - UsU) fixed a bug where direct flashing was incorrectly shown regardless if it was possible or not
    • Fix (SALT): incorrectly shown laf download window
    • New (SALT): completely re-design of the installer (thx for the pkexec contribution ThePiGuy). all details for the new installer here: commit
    • New (SALT): prepare for multi model support in SALT (not G4 only anymore)
    • New (SALT): available SALT features and main window screen are now based on the detected LG model

    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)

    v3.17
    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

    v3.16
    Released: 2018-05-06
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): Improved backup / Free disk space check

    v3.15
    Released: 2018-04-25
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): Select/Deselect button when extracting a KDZ

    v3.14
    Released: 2018-04-17
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • Fix(SALT): SALT was unusable in rare cases


    v3.13
    Released: 2018-03-22
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): Mount button after extracting a KDZ added
    • Fix(SALT): remove flashing warning when user skips device connection
    • Fix(SALT): several issues when directories containing spaces (I recommend to still avoid spaces in dir and filenames)
    • Fix(kdztools): rare issues when extracting some KDZ files

    v3.12
    Released: 2018-03-21
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • Fix(SALT, kdzmgr): several issues for extracting KDZ files

    v3.11-0
    Released: 2018-03-16
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): extracting a KDZ will now detect and show the ARB !
    • Fix(SALT): extracting KDZ in a path with space or special chars failed (empty partition list on extract)

    v3.10-1
    Released: 2018-03-13
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • Fix(SALT): UsU hashes on some devices can't be set correctly (country related)
    • Fix(SALT): UsU check for ARB <=2 implemented to avoid damage

    v3.9-0
    Released: 2018-03-09
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): binary checker for fastboot on start
    • New(SALT): improved error handling for binary checks on start
    • Fix(SALT): UsU hashes on some devices can't be set correctly

    v3.8-2
    Released: 2018-03-07
    Full changelog (SALT): at github (this version compared with the previous release)

    v3.7-12
    Released: 2018-03-05
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): update checker for SALT on start
    • New(SALT): added a mount option for image files
    • NEW(SALT): checking LAF version and offering a compatible LAF if needed/recommended
    • NEW(SALT): complete re-design of UsU flashing verification using a hash table
    • NEW(SALT): added a fastboot flashing fallback on UsU flashing when partial success
    • Fix(SALT): a LOT of UsU stuff..
    • Fix(SALT): will not let open as much windows as before (e.g. closing advanced menu dialog on unlock click etc)
    • Fix(SALT): important UsU related fixes -> if you want to unlock by UsU do not use any previous version!
    • Fix(SALT): do not start UsU flashing on incompatible LAF versions

    v3.6-5
    Released: 2018-02-14
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): Upload/Paste your SALT logfile with a single click!
    • New(SALT): many important stuff related to UsU
    • Fix(SALT): SALT does not start in rare circumstances

    v3.5-7
    Released: 2018-02-05
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): Main GUI completely re-worked to fit on smaller screens
    • New(SALT): main screen now detect and display: LAF protocol, IMEI and serial (removed "Secure device" as its meaning is unknown anyways)
      HINT: IMEI and serial will never be written into the logfile!
    • New(SALT): added the feature to extract/convert/mount system.dat files (from LP up to Oreo 8.1) - requested by @kessaras
    • New(SALT): KDZ extract HEAVILY improved (details)
    • Fix(SALT): UsU related stuff
    • Fix(SALT): modemst info

    v3.1-1
    Released: 2018-01-09
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): adding a GPT compatibility info for UsU ROM flashing
    • Fix(SALT): garbage on UsU check in log

    v3.0-7
    Released: 2018-01-08
    Full changelog (SALT): at github (this version compared with the previous)
    Summary changelog:
    • New(SALT): Full UsU support
    • New(SALT): Full Nougat bootloader support
    • Fix(SALT): several .. read the full changelog

    v2.1-0
    Released: 2018-01-05
    Full changelog (SALT): at github (this version compared with the previous)
    Summary changelog:
    • New(SALT): Backup now uses $HOME/salt_backup as default backup path
    • New(SALT): If backup path does not exists it will be auto-created now
    • Fix(SALT): Verify backup was broken (thx @cowsngrass or the report)

    v2.0-7
    Released: 2018-01-03
    Full changelog (SALT): at github (this version compared with the previous)
    Full changelog (lglaf): at github (all commits up to release date)
    Full changelog (kdztools): at github (all commits up to release date)
    Summary changelog:
    • New(lglaf, SALT): Backup now shows a progress bar instead of that creepy log output
    • New(SALT): adding a Retry button on SALT startup
    • New(lglaf, SALT): replaced legacy auth method with new chall/response
    • New(SALT): adding support for mbn firmware files
    • New(SALT): adding UsU (Unofficial steadfasterX Unlock) detection
    • Fix(lglaf): Timeout issues on some devices resulting in no detection
    • Fix(lglaf): Some devices even when using an older LAF protocol version required challenge/response
    • Fix(SALT): md5 verify on some devices
    • Fix(kdztools): when on master (so STABLE) branch kdz extract was not possible
    • and many more (check github changelogs above)

    1.1-5
    Released: 2017-12-15
    Full changelog: at github (this version compared with the previous)
    Summary changelog:
    • New feature: MD5 verification of backup
      This feature may not be available on every device but SALT will check after a backup automatically if your device supports
      md5 verification and offers you an option to do so.
    • Fix: ARB detection was wrong on H811

    1.0-14
    Released: 2017-12-11
    Changelog:
    • first public release
    • Full changelog at github
    12
    New SALT release!

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

    v3.5-7
    Released: 2018-02-05
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): Main GUI completely re-worked to fit on smaller screens
    • New(SALT): main screen now detect and display: LAF protocol, IMEI and serial (removed "Secure device" as its meaning is unknown anyways).
      HINT: IMEI and serial will never be written into the logfile!
    • New(SALT): added the feature to extract/convert/mount system.dat files (from LP up to Oreo 8.1) - requested by @kessaras
    • New(SALT): KDZ extract HEAVILY improved (details)
    • Fix(SALT): UsU related stuff
    • Fix(SALT): modemst info
    12
    v3.6-5 released

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

    Released: 2018-02-14
    Full changelog (SALT): at github (this version compared with the previous release)
    Summary changelog:
    • New(SALT): Upload/Paste your SALT logfile with a single click!
    • New(SALT): many important stuff related to UsU
    • Fix(SALT): SALT does not start in rare circumstances
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone