yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] cowsngrass:
Operator error again?!

Wow, thanks.

Sooo, my ARB is version 2, and I just verified that SALT sees the partitions. I'll keep reading your posts and others on xde to see where to go from here.

I truly appreciate your help!
[Android Software/Hacking General [Developers Only]] steadfasterX:
New release!

In preparation of the unofficial unlock (UsU) and with many fixes and improvements I'm able to release v2.0 today:

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)

Summy 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)

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

Have fun

steadfasterX
[Android Software/Hacking General [Developers Only]] steadfasterX:
Supporting any Linux can be tricky sometimes (that's another reason why FWUL exists) but.. it looks like you have installed SALT to / ? if not the error indicates a path issue.

Best to find the issue is starting SALT from a terminal like this (after cd into the SALT install dir):

./salt (do not use sudo here. it will automatically switch to sudo if needed)

Then try it with sudo to see any difference:

sudo ./salt

Do you have any files in /tmp after taking the backup? Show me a

ls -la /tmp

SALT is not able to see your files and so can't verify them.

Keep in mind that taking a full backup requires 32 GB of free space.

Hint:

When pasting logs its important that I see everything from it. Do not cut

anything

here!

..and for any longer output then a few lines you better use one of the pastebin services like hastebin (click on save button on the top right and share the link)

thx for your report
[Android Software/Hacking General [Developers Only]] cowsngrass:
Do you have any files in /tmp after taking the backup? Show me a

ls -la /tmp

SALT is not able to see your files and so can't verify them.

Thanks. I'll try this in a few hours after returning from work.

In the meantime, here are the results from ls -la /tmp:

rob@rob-OptiPlex-755 ~ $ cd /

rob@rob-OptiPlex-755 / $ ls -la /tmp

total 104

drwxrwxrwt 16 root root 36864 Jan 4 03:39 .

drwxr-xr-x 23 root root 4096 Dec 9 14:48 ..

drwx------ 2 rob rob 4096 Jan 3 17:24 .com.google.Chrome.g1ezJ9

-rw------- 1 rob rob 0 Jan 3 17:21 config-err-3SMg1s

drwxrwxrwt 2 root root 4096 Jan 3 17:15 .font-unix

drwxrwxrwt 2 root root 4096 Jan 3 17:21 .ICE-unix

drwxrwxrwx 2 rob rob 4096 Jan 3 17:21 mintUpdate

drwx------ 2 rob rob 4096 Jan 3 17:22 .org.chromium.Chromium.zHnTol

drwx------ 3 rob rob 4096 Jan 3 17:22 skype-2825

drwx------ 2 rob rob 4096 Jan 3 17:22 skypeforlinux Crashes

drwx------ 2 rob rob 4096 Jan 3 17:21 ssh-QQyzxSeVCX8c

drwx------ 3 root root 4096 Jan 3 17:15 systemd-private-aa859c6cf7d94f9aa6ead66e714a4db4-colord.service-MUYgC6

drwx------ 3 root root 4096 Jan 3 17:21 systemd-private-aa859c6cf7d94f9aa6ead66e714a4db4-rtkit-daemon.service-FT10ik

drwx------ 3 root root 4096 Jan 3 17:15 systemd-private-aa859c6cf7d94f9aa6ead66e714a4db4-tor@default.service-JgKDHN

drwxrwxrwt 2 root root 4096 Jan 3 17:15 .Test-unix

-r--r--r-- 1 root root 11 Jan 3 17:15 .X0-lock

drwxrwxrwt 2 root root 4096 Jan 3 17:15 .X11-unix

-rw------- 1 rob rob 446 Jan 3 17:21 .xfsm-ICE-7WJ6BZ

drwxrwxrwt 2 root root 4096 Jan 3 17:15 .XIM-unix

rob@rob-OptiPlex-755 / $
[Android Software/Hacking General [Developers Only]] steadfasterX:
I need the output of the directory after you took a

backup

(assuming that you backup to /tmp as the debug log has shown)

.
[Android Software/Hacking General [Developers Only]] cowsngrass:
Results of opening SALT with ./salt:

Terminal after backup and verify: https://hastebin.com/emimugofef.http

1st part of Debug Log: https://hastebin.com/uqafesalov.http

2nd part of Debug Log: https://hastebin.com/migugogoso.php

Results of ls -la /tmp: https://hastebin.com/ataxiwugez.hs

Results of opening with sudo ./salt, backing up and verifying. Did not have to reboot computer:

Terminal after backup and verify: https://hastebin.com/utequwexat.vbs

Debug Log: https://hastebin.com/pomivuvopi.md

Results of ls -la /tmp: https://hastebin.com/ziyetilevi.hs

Closed SALT and tried to open with desktop icon and got this error:

"Failed to run /home/rob/SALT/salt as user root."

"Unable to copy the user's Xauthorization file."

If you want to pursue making this work on this Linux, I'm willing to keep testing. However I don't know enough about the whole unlocking thing to need Salt at this time. I'll keep studying and following your posts to learn more. If I get to the point where I want to try something, I'll go the FWUL route.

Again, I'm amazed at the knowledge displayed on these forums! Thanks to everyone. And thank you, steadfasterX for your kindness and patience with this nooby!
[Android Software/Hacking General [Developers Only]] AndreiGTR:
deleted
[Android Software/Hacking General [Developers Only]] steadfasterX:
SALT v2.1-0 released!

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

v2.1-0

Released: 2018-01-05

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

Summy 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

Thanks! your report is highly appreciated!

The backup verify is fixed in v2.1-0. pls upgrade.

Regarding the other error: check this: https://askubuntu.com/questions/40320/unable-to-copy-the-users-xauthorization-file#40324

.
[Android Software/Hacking General [Developers Only]] Jonotjie:
Installed Ubuntu 17.10 on a VM and managed to do a Basic Backup fine. Busy doing a Full backup now. :)

One question: What does the UsU mean? Mine is showing Unofficially_unlocked_by_UsU?

My phone is LG-H815P with stock MM, never did anything on it. Rollback is 0.
[Android Software/Hacking General [Developers Only]] steadfasterX:
UsU is the Unofficial secureboot-off/steadfasterX Unlock and what you see is a bug which get fixed in v3.0
[Android Software/Hacking General [Developers Only]] Jonotjie:
great! thanks for all your amazing efforts. :)
[Android Software/Hacking General [Developers Only]] cowsngrass:
Did the update and tweaked the desktop START icon properties. Everything seems to work!

Thanks.
[Android Software/Hacking General [Developers Only]] doop:
I have tried in vain to get salt to see my g4. Tried in VM and usb forgetful.

device recognised as:

Bus 002 Device 005: ID 1004:633a LG Electronics, Inc. Ultimate 2 Android Phone L41C

When I run lsub command.

The g4 is a H815 SEA running nougat v29a and ARB v0

any help getting it recognised appreciated.
[Android Software/Hacking General [Developers Only]] onotor:
Downgrade your phone to 6.0
[Android Software/Hacking General [Developers Only]] steadfasterX:
Get the debug log in the advanced menu and paste it to hastebin.com (save button top right and share the link)
[Android Software/Hacking General [Developers Only]] doop:
Thank you. I should of stated that I have also tried with a H810 running Lollipop and in the terminal window after running lsusb it`s recognised as

LG Electronics, Inc. G2/G3 Android Phone [MTP/PTP/Download mode]

but salt doesn`t detect that phone either?? have tried waiting for longer before running salt nothing seems to work.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Try another cable and also try a USB 2.0 port but anyways I need the log.
[Android Software/Hacking General [Developers Only]] doop:
Heres the log https://hastebin.com/hadofujepi.js

tried many leads (well 4) and am using usb 2.0 ports.

heres the result of lsusb LSUSB
[Android Software/Hacking General [Developers Only]] Pete_Mitchell:
How to access the bin file via salt?
[Android Software/Hacking General [Developers Only]] steadfasterX:
advanced menu --> Mount image
[Android Software/Hacking General [Developers Only]] Pete_Mitchell:
Sorry but I can't find advanced Menu with right click on it...
[Android Software/Hacking General [Developers Only]] steadfasterX:
Uhm.. Open SALT.. Click advanced menu..
[Android Software/Hacking General [Developers Only]] Pete_Mitchell:
Thanks SteadfasterX,

finally I managed to display the files, but I can' copy/cut and paste files...What can I do to do it?

Thanks in advance and kind regards
[Android Software/Hacking General [Developers Only]] steadfasterX:
Start SALT and open the advanced menu again. Choose debug log and click then upload button. Copy with right click the bpaste link or open it and copy it from the browser address bar and paste it here.

Consider to use the XDA thanks button on useful posts ;)
[Android Software/Hacking General [Developers Only]] dharakv:
I know this is a bit late but I finally got down to flashing MM KDZ and performing a partial SALT backup as you suggested. I took it one step ahead and performed it on the empty freshly-flashed device. Unfortunately the same thing is happening... it freezes on system partition (4GB) for hours on... (userdata is only 76MB so it worked) but then it skips to 100% and says its fully backed up, but looking at the partition sizes, I know it's nowhere near fully backed up. [MENTION=5545101]steadfasterX[/MENTION] mentioned previously that some firmwares cause timeouts....

But I'm baffled as to whether it has to do with the size of these partitions (maybe SALT is buggy and struggles with large sized partitions? maybe something CPU related?) or whether it's to do with corrupt flash memory. The phone was getting a bit slow (possibly due to heavy RAM usage), but besides that, I've had no other performance issues with the phone after 2.5 years, so I doubt it has to do with a corrupt flash memory... If the system partition was corrupt wouldn't there be a significant impact on performance of the OS?

Pls note I have tried this procedure on many different disks/flash drives, computers, hypervisors, USB cables, etc etc etc..

I just wanted to mention, the other partitions do backup without errors, but when I try to mount and open the bin files with PowerISO, I get the following message:

"The file format is invalid or unsupported"
[Android Software/Hacking General [Developers Only]] seadersn:
[MENTION=5545101]steadfasterX[/MENTION] i like your work :) pretty lightens a lot of tasks, very nice and well done! thanks and pls, continue like that :D ;)
[Android Software/Hacking General [Developers Only]] steadfasterX:
1) You really should learn how to provide the SALT log.. All these tests can get easily useless without it.

2) Anyways. Your firmware is may producing timeouts. SALT backups even userdata which is 23 GB but its slow ofc. it does NOT matter how much space is in use on the device as SALT clones the disk 1:1 so even unused data.

3) to prepare for UsU unlock its not needed to have a FULL backup. A BASIC one is enough and if you are using the latest SALT version (which is recommended anyways) you can also choose a CUSTOM backup and try to backup just a single partition like "system" or "userdata". Maybe that work out for your firmware

4) SALT is not buggy :P blame your phone OEM for creating buggy firmware instead

5) It is very unlikely that you have a corrupted partition while possible (1% chance for that. well if you are not using a bad custom ROM which you can't atm)

6) timeout issues can likely more occur when you run SALT in a virtualized environment (e.g. VirtualBox)

7) you should use SALT to mount an image (advanced menu) and no 3rd party tools which know nothing about android

8) just in case: if you have an encrypted device backing up "userdata" is useless

.-
[Android Software/Hacking General [Developers Only]] dharakv:
Thank you [MENTION=5545101]steadfasterX[/MENTION] for your prompt reply.

- UPDATE: I tried running a custom backup of system but it failed. Also, the filetype is img not bin.... Then I tried a full backup and the full 4GB backed up... Unforutunately I unplugged the phone right after the backup finished and didn't realize SALT had a verification feature. I will try a full backup again with the verification and post the results and logs later on.

-Clearly the userdata has failed but I don't think it's required for USU? I'm guessing the only partitions that won't be fully backed up with a partial backup are system and userdata?

- I have tried booting directly into FWUL without a hypervisor on 2 different computers, both giving the same result...

- Sorry, I forgot you can mount from within SALT itself. I will try to mount the image within SALT and if that doesn't work, again try the full backup as mentioned in the first point.

- I believe by default the storage data its unencrypted?
[Android Software/Hacking General [Developers Only]] steadfasterX:
regarding the file extension img | bin | ... read the SALT FAQ 11) I have a partition file with the extension: [ bin | image | img | mbn ]. How can I convert this?

as said: for UsU you only need the BASIC backup. I mentioned that here (point 3).

system partition can be easily extracted from a KDZ with SALT.

and you only need to backup "userdata" to avoid data loss of your internal storage (e.g. photos, vids etc) and that will only work when it is unencrypted (which is the default on stock MM)

.-
[Android Software/Hacking General [Developers Only]] dharakv:
2018-12-15 05:11:17: F_ADVMENU: main YAD_PID is 15383

2018-12-15 05:11:24: F_MOUNTPARTS: started

2018-12-15 05:11:50: returned: /media/sf_vbox_shared/carrier.bin|/mnt/salt_mnt|

2018-12-15 05:11:50: IMGFILE = /media/sf_vbox_shared/carrier.bin, MNTPNT = /mnt/salt_mnt

2018-12-15 05:11:50: F_MOUNTIMG: started with /media/sf_vbox_shared/carrier.bin

2018-12-15 05:11:50: F_MSGE: started

2018-12-15 05:11:57: ERROR: system image could not be mounted to /mnt/salt_mnt.

Check SALT logfile!

2018-12-15 05:11:57: 0

2018-12-15 05:11:57: F_MOUNTIMG ended

2018-12-15 05:11:58: F_MOUNTPARTS: started

2018-12-15 05:12:08: returned: /media/sf_vbox_shared/system.img|/mnt/salt_mnt|

2018-12-15 05:12:08: IMGFILE = /media/sf_vbox_shared/system.img, MNTPNT = /mnt/salt_mnt

2018-12-15 05:12:08: F_MOUNTIMG: started with /media/sf_vbox_shared/system.img

2018-12-15 05:12:08: F_MSGE: started

2018-12-15 05:12:12: ERROR: system image could not be mounted to /mnt/salt_mnt.

Check SALT logfile!

2018-12-15 05:12:12: 252

2018-12-15 05:12:12: F_MOUNTIMG ended

2018-12-15 05:12:17: F_MOUNTPARTS: started

2018-12-15 05:12:19: returned: /home/android/Desktop/LG/undef|/mnt/salt_mnt|

2018-12-15 05:12:19: IMGFILE = /home/android/Desktop/LG/undef, MNTPNT = /mnt/salt_mnt

2018-12-15 05:12:19: F_ERR: started

2018-12-15 05:12:19: ERROR: 3 occurred in F_MOUNTPARTS (expected 0, got 3)

2018-12-15 05:12:19: F_MSGE: started

2018-12-15 05:12:21: ERROR: /home/android/Desktop/LG/undef does not exists or is not readable!

2018-12-15 05:12:21: 0

2018-12-15 05:12:21: F_EXIT: started

2018-12-15 05:12:21: EXIT: F_MOUNTPARTS->F_ERR with code 4

2018-12-15 05:12:22: F_MOUNTPARTS: started

2018-12-15 05:12:34: returned: /media/sf_vbox_shared/ssd.bin|/mnt/salt_mnt|

2018-12-15 05:12:34: IMGFILE = /media/sf_vbox_shared/ssd.bin, MNTPNT = /mnt/salt_mnt

2018-12-15 05:12:34: F_MOUNTIMG: started with /media/sf_vbox_shared/ssd.bin

2018-12-15 05:12:34: F_MSGE: started

2018-12-15 05:12:36: ERROR: system image could not be mounted to /mnt/salt_mnt.

Check SALT logfile!

2018-12-15 05:12:36: 0

2018-12-15 05:12:36: F_MOUNTIMG ended

2018-12-15 05:12:39: CR setting: Auto =

2018-12-15 05:12:39: getlog script started
[Android Software/Hacking General [Developers Only]] steadfasterX:
Sharing logs like that is bad practice. First you cutted it which removes important information as you just selected a part which you think might be relevant. Second sharing logs directly in a post is nothing XDA itself and XDA readers like as it makes threads unreadable.

Read the SALT FAQ 1000 which even has a picture guide how to get and share the debug log correctly.

Regarding mounting:

When you use shared folders in VirtualBox you can't mount from these shares. That's a restriction of VirtualBox and another (of so many reasons) to use an USB stick to boot Linux e.g. FWUL. Either move the file you want to mount to your desktop or boot FWUL or your favorite Linux from an USB stick.
[Android Software/Hacking General [Developers Only]] dharakv:
Ok, so when i copied the system.bin image to FWUL's desktop and then mounted (Size is 3.2GB, 11397 items), it worked... but smaller partitions like sbl1, ssd, aboot don't mount..

Unfortunately i closed the SALT program after I got the logs of the failed mounts.. and it says I have to unmount the system partition first before I try again...
[Android Software/Hacking General [Developers Only]] steadfasterX:
Yes as said VirtualBox is not recommended and so you need to do it that way.

You can't mount EVERY partition. That's not how android works. The most partitions do not have a file system. but why you even WANT to mount e.g sbl1? It's part of the bootloader stack and nothing you ever wanna see or even touch.

The partitions which have a file system are just userdata, system, modem which are the most interesting ones. There are some others which can be mounted but those are nothing you ever need.
[Android Software/Hacking General [Developers Only]] dianxxyyzz:
Heya dear SteadfasterX ,

You know you cool , right? :) yes mayeb you remember me , we was trying in past to found a way to unlock all LG G4 . Any way , I come back to my "briked" lg Lg , that was converted to a LS with a ARB 2 . Now I send to the phone all partitions with ARB 4 posted he made backup with SALT . All looks better than before , phone show imei , but it is now I think in ARB 4 too . I send the partitions using fastboot .

Any way i did not send a system.img with fastboot because he said is too large . I can go into download mode and SALT gives me info about phone and all is ok . I just need a way to send the system image to the phone using SALT . Is this possible? Thank you very much !
[Android Software/Hacking General [Developers Only]] steadfasterX:
Hey dude. Sure I remember but read the first sentence of my signature so don't be mad with me if I do not remember every detail. ;)

It is may be possible but it depends. Share the debug.log while your phone is connected in download mode which is described in SALT FAQ 1000.
[Android Software/Hacking General [Developers Only]] dianxxyyzz:
I started your great tool SALT in experimental mode , and I flashed in about 2-3 hours a system img from MM 20g . I was trying to flash exactly what that guy with refurbished device and ARB 4 had . I just give a "Secure boot error .Error code 1009 .OFFICIAL." on screen top left message and reboots . I flashed also the recovery from kdz , but it dnt enter into it . It just bootloops . Is not a problem if I can not make this device work , I already acomodated with it to dnt work . But is strange , I flashed all partitions that guy posted as SALT backup and it still say that secure boot error . I used SALT to get a shell inside phone , I see system partition have the content that must be . I tried with boot.img of that guy , and also the one from kdz . Very strange . His phone was working full .
[Android Software/Hacking General [Developers Only]] steadfasterX:
Really I don't know what you're doing there or trying to achieve. Secure boot error message is clear as long as it has UsU flashed. I told you to send the debug log which you don't gave.
[Android Software/Hacking General [Developers Only]] Mariano 4002:
I tried to extract a kdz file for my g4 us991 but the program always gives me the same error: ARB_DETECT_ERROR

In FWUL sometimes it let me extract but the space disk isn't enough so i pass to ubuntu on a virtual machine but is the same.

Any solution?
[Android Software/Hacking General [Developers Only]] steadfasterX:
Yes for sure but you have to read and follow FAQ 1000 of this thread after trying to extract. This goes for both for Ubuntu and FWUL
[Android Software/Hacking General [Developers Only]] steadfasterX:
SALT v3.21 - fresh as a daisy

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.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 [MENTION=3167089]runningnak3d[/MENTION] ! 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:

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!
[Android Software/Hacking General [Developers Only]] seadersn:
it's a good day today :) thanks!!
[Android Software/Hacking General [Developers Only]] Pete_Mitchell:
A bit in late, but I have just done it now. Sorry...

So I managed to start the g4 disabling 2 big cores recovered everything almost, then I made the mistake to update it again.

The phone is stuck again and when in download mode if I try to flash a rom it stops at 12% rebooting Always. I think some partitions are messed up, do you suggest to erase partitions and reflash them from backupped ones? If yes which command?

I thank you in advance for your superb availability and kindness , you are a north pole for this community.