yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] ThePiGuy:
I can't see anything wrong there...
[Android Software/Hacking General [Developers Only]] steadfasterX:
The best is to switch your base in SALT to develop and update. I greatly enhanced the installer today plus added the pkexec install by [MENTION=8699949]ThePiGuy[/MENTION] , too.

Details: https://github.com/steadfasterX/SALT/commit/307e61871e679c598193cd6b43b67cba95ffe3a7
[Android Software/Hacking General [Developers Only]] sdembiske:
Update hangs on the SALT Codebase at e562e85.5bbbaa1 - doesn't progress and green bar doesn't get to 100%

Salt Log:

2018-08-13 16:16:37: F_VCHK: newer SALT version found (319 / 3.19-0 vs. 318 / 3.18-0)

2018-08-13 16:16:37: F_MSGW: started

2018-08-13 16:16:44: New SALT version available!

You:	<b>3.18-0</b>

Online:	<b>3.19-0</b>

Do you want to update now?

2018-08-13 16:16:44: 99

2018-08-13 16:16:44: F_UPDATE: started

2018-08-13 16:16:51: F_UPDATE: updating /home/sxxx/SALT on branch develop ...

2018-08-13 16:16:52: Already on 'develop'

M	install-desktop.sh

Your branch is behind 'origin/develop' by 5 commits, and can be fast-forwarded.

(use "git pull" to update your local branch)

error: Your local changes to the following files would be overwritten by merge:

install-desktop.sh

Please commit your changes or stash them before you merge.

Aborting

Updating e562e85..5bbbaa1

2018-08-13 16:16:56: F_UPDATE: updating /root/programs/lglafng on branch g4-develop ...

2018-08-13 16:16:56: Already on 'g4-develop'

Your branch is up to date with 'origin/g4-develop'.

Already up to date.

2018-08-13 16:16:58: F_UPDATE: updating /root/programs/kdztools on branch develop ...

2018-08-13 16:16:58: Already on 'develop'

Your branch is up to date with 'origin/develop'.

Already up to date.

2018-08-13 16:18:24: F_MSGW: started

2018-08-13 16:18:29: You must restart SALT if you have updated or changed the <b>SALT</b> branch before the changes become active.

2018-08-13 16:18:29: 0

2018-08-13 16:18:30: F_UPDATE: ended

2018-08-13 16:18:30: F_MSGOK: started

2018-08-13 16:18:34: Will close SALT now due to the update taken!

Just re-open SALT afterwards.

2018-08-13 16:18:35: 0

2018-08-13 16:18:35: F_EXIT: started

2018-08-13 16:18:35: EXIT: After-Update-End with code 0

removed '/tmp/salt.lock'
[Android Software/Hacking General [Developers Only]] steadfasterX:
updating will work only with an unmodified codebase!

You can revert all your local changes by doing in the program folder of SALT :

git reset --hard

with this command all your local changes will be reverted and so you will have a clean code base again and so you will be able to use the update again
[Android Software/Hacking General [Developers Only]] sdembiske:
Thank you - all good now. As a reminder, as sudo pacman -Sy gksu is no longer required or works as it used to, it would be less confusing/problematical for those installing & using SALT now for the first time or re-installing in systems other than FWUL, to remove it from the OP.

Thanks again to [MENTION=8699949]ThePiGuy[/MENTION] and you for the help and for getting the issue dealt with for 1st time installers and users and re-installers wising to upgrade using the more secure polkit implementation vs using gksu.

Best, S.
[Android Software/Hacking General [Developers Only]] autorun:
Found it , Thanks.
[Android Software/Hacking General [Developers Only]] metropical:
pardon the stoopit q, but do I install Linux on VB or is SALT all thats needed? If Linux, is there a particular version?

My endgame is to update my rooted unlocked LG G4 to 20x. Haven't been able to make this happen with W7 and VB 5.1.38
[Android Software/Hacking General [Developers Only]] steadfasterX:
First thing: there is an upload button in SALT (advanced menu - debug log) which generates a link for the uploaded debug log. It's not good to paste big logs like that and its incomplete too. That's also written in the FAQ including a how-to.

Your issue is well known in some firmwares and especially when using SALT in a VM. Start FWUL from an USB stick and try again.

If that still does not work its the firmware so you may need to upgrade to 20p before.

Install FWUL on an USB stick like the OP recommends. Check the requirements. FWUL includes SALT and is the best way to go.

Keep in mind that only SALT v4 will allow flashing which is not released yet ( and that's nothing which will happen soon but who knows.. ).
[Android Software/Hacking General [Developers Only]] DopestKREW:
Sorry for posting the log with code but i'm a new user and I can't post links. I'm using VM with FWUL on my physical disk, i'll try with a USB. The problem is that i'm trying to get all the data back from the G4 because UI system keeps giving me error and i can't access the phone. It has the newest update that happend few months ago and as I understand, if you want to keep your files and don't brick the phone you can only update the firmware to a higher or equal version. Is 20p a higher version?
[Android Software/Hacking General [Developers Only]] metropical:
got it working with info from sdembiske post.

https://xdaforums.com/showpost.php?p=77338576&postcount=727

https://xdaforums.com/showpost.php?p=77338968&postcount=728

https://xdaforums.com/showpost.php?p=77341968&postcount=729

But can I extract a .zip from the .kdz and flash that with TWRP normally? Or not yet>?
[Android Software/Hacking General [Developers Only]] steadfasterX:
Firmware versions are alphabetical released (for the h81x models at least)

If you have no TWRP SALT is your best option yes. There are still another way but try to boot from USB stick and hope that it works.

You can extract the kdz and flash the bootloader stack and system partitions in fastboot or TWRP manually.
[Android Software/Hacking General [Developers Only]] metropical:
in dl mode but neither FWUL nor SALT see phone.

nor can I navigate to shared folder for .kdz extract.

http://bpaste.net/show/ac5837915cba LOG
[Android Software/Hacking General [Developers Only]] metropical:
Got dl mode to be seen by SALT (prolly fat fingers preventted it). But can't nav to shared folder to extract .kdz. Can't copy/paste. Tried a new folder, but it fails.
[Android Software/Hacking General [Developers Only]] sdembiske:
Virtualbox shared folders:

Pre-checks:

- confirm "virtualbox-guest-utils" is installed in FWUL - in a terminal type: sudo pacman -Qe

- make sure User, i.e., "your_user_name" is a member of the vboxsf group - in a terminal type: groups "your_user_name"

- if it is not, add it with this command: sudo gpasswd --add "your_user_name" vboxsf

note: it's two dashes with no spaces between ahead of 'add' in the command.

Edit the /etc/modules-load.d/virtualbox.conf file (I prefer nano for editing, finding it very user friendly - it can be installed with this terminal command: sudo pacman -Sy nano )

In a terminal enter this command: sudo nano /etc/modules-load.d/virtualbox.conf

add the following lines:

vboxguest

vboxsf

vboxvideo

- then, if using Nano, hit 'Ctrl x', 'y' to save and then 'enter' to add the lines in the file.

then (just in case), enter the following command in a terminal:

sudo systemctl enable vboxservice.service

Then, change the permissions on the shared folder with this terminal command:

sudo usermod -a -G vboxsf "your_user_name"

Then Reboot

See if that helps.
[Android Software/Hacking General [Developers Only]] metropical:
confirm "virtualbox-guest-utils" is installed in FWUL - in a terminal type: sudo pacman -Qe - thanks and Yes

[android@fwul ~]$ groups "android"

adm wheel audio optical storage log network floppy scanner power rfkill vboxsf users not sure?

I installed - nano.

n a terminal enter this command: sudo nano /etc/modules-load.d/virtualbox.conf

add the following lines:

vboxguest

vboxsf

vboxvideo

I think I got that right.

sudo systemctl enable vboxservice.service I think I got that as well.

sudo usermod -a -G vboxsf "android" I think I got that as well.

here we go
[Android Software/Hacking General [Developers Only]] metropical:
nope, can't leave the SALT directory.

see attachments
[Android Software/Hacking General [Developers Only]] SirenumDev:
Please help with backup

Hi I am failing to backup an LG-H910

Error:

Debug log: http://bpaste.net/show/45944bf6f4ac

I am using FWUL on Windows (guest additions + expansion pack installed).

[IMG="Calculated target size too small"]https://www.diigo.com/file/image/baaesbqozepqpderaozdodreqqr/Capture.jpg?k=e1c89a08a3619d02fdff6c4745e1adfb[/IMG]

I did read the instructions about 'no space'. I mounted a shared folder (with full read-write permissions) and modified SALT's working directory to the shared folder.

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.
[Android Software/Hacking General [Developers Only]] sdembiske:
re-read: I corrected 'android' to 'your_user_name'. ('android' was the user name for FWUL where I outlined this in that thread the first time).

Did you reboot your Manjaro, Arch Linux, Ubuntu or whatever system your running in Virtualbox after doing all the commands?

Did you select the kdz you downloaded from the location it downloaded to, then extract to your specifically named folder in your host shared folder? You should see your shared folder in the file system as something like sf_xxx - then select the specific folder you want to extract to in that folder.

Why are you highlighting the 'root' folder?
[Android Software/Hacking General [Developers Only]] metropical:
I used "android" as user name as I didn't change it.

rebooted arch.

I can't get to the kdz. Doh! I guess I have to dl .kdz from and to the SALT dir?

It was just a snap to show directory.

Might you have time for an IRC at some point?
[Android Software/Hacking General [Developers Only]] steadfasterX:
SALT is made for the LG G4 but should work for other LG models as well. I say "should" as I can't test other devices.

Your error is not a disk space issue but an issue with detection partitions on your model. Iirc the v20 uses UFS which is not compatible with the g4 way.

maybe its enough to switch the branch but I guess only [MENTION=3167089]runningnak3d[/MENTION] may can shed some light on this..

you just need to open the path where you stored the KDZ! There is no modification needed in FWUL to make shared folders work. It all works out of the box.

The error means: you haven't chosen a folder where a KDZ is.

if it is a shared folder just browse to /home then to android then to the shared folder name

.
[Android Software/Hacking General [Developers Only]] metropical:
I should clarify, I meant a shared folder from my Mac OS drive, which I added to the FWUL shared folder setting. In any case, dl'g the .kdz now within the FWUL OS.

And by extract, does that mean I would be able to extract a TWRP flashable .zip from the .kdz or am I missing something?
[Android Software/Hacking General [Developers Only]] runningnak3d:
[MENTION=5221250]SirenumDev[/MENTION] [MENTION=5545101]steadfasterX[/MENTION]

Yep, it is failing due to UFS. I have not implemented the parsing of all 7 LUNs to be compatible with SALT yet, so even changing the branch won't work.

I am adding full UFS detection, and signed writing so we can finally have a unified codebase, and be able to flash KDZs. There is just a little more I need to understand about INFO SPRO to make that happen, then we can finally say good riddance to LG UP on all LG phones.

-- Brian
[Android Software/Hacking General [Developers Only]] steadfasterX:
It doesnt matters if you use a MAC or AlienWare OS or whatever.. as long as its VirtualBox and you have shared folders enabled.

You just need to browse to your shared folder where you have stored the kdz thats all.

If you have the KDZ not yet downloaded in your Mac OS (and so its not in the shared folder) then yes downloading that to FWUL is another option.

As said Im online *usually* Mo-Fr on IRC if that helps (today only for 1 hour from now on..).

EDIT:

As stated here already: https://xdaforums.com/showpost.php?p=77343881&postcount=495

you will not extract a zip or create a zip with SALT. You will extract the KDZ which results in many image files and those can be flashed in fastboot (recommended) or manually in TWRP with the DD command. or wait for SALT v4 which will enable flashing (at least for fastboot).

thx for confirming. I had the hope that maybe switching the branch would be enough for taken a backup but for this we need to parse the partitions correctly first.

I cant test anything else then the G4 unfortunately so I cant help much on that lglaf part. When it comes to SALT I just need some example outputs and machine readable output like I implemented with https://github.com/steadfasterX/lglaf/blob/g4-stable/partitions.py#L312-L313

:)

.
[Android Software/Hacking General [Developers Only]] runningnak3d:
I believe I have fixed the ability to write with lglaf on MM again, but I haven't been able to test it.

If someone can check out the g4-develop branch, and let me know, it would be appreciated.

-- Brian
[Android Software/Hacking General [Developers Only]] steadfasterX:
Awesome! Will test hopefully next week but I guess no one else here is able to do so.

Thanks again for all your contributions!
[Android Software/Hacking General [Developers Only]] metropical:
LG G4 phone in dl mode isn't seen by SALT. Tried toggling dev mode. Tried starting SALT 1st. dl mode 1st.

but FWUL - Simple adb and fastboot both work.

Other G4, NP with SALT and dl mode.

If this is ARB 3 as the other phone is, could I skip the fastboot steps and move onto flashing the ROM?

Of course the dl mode issue has to be resolved 1st.
[Android Software/Hacking General [Developers Only]] metropical:
just found this: https://xdaforums.com/showpost.php?p=74827755&postcount=2

So moving on.
[Android Software/Hacking General [Developers Only]] steadfasterX:
I told you that you must manually select the USB device in the virtualbox settings once FWUL is running. It wasnt working automatically on your system so you have to go into the menu and select the USB device after starting FWUL.

no you can NOT skip the fastboot steps.

I gave you the fastboot commands within the correct directory on the last IRC session.

If you left without using the fastboot commands it wont work ofc as you must start that in the correct directory.

The command I gave you was working 100%.

tbh better wait for SALT v4 it will make flashing in fastboot very easy.

-
[Android Software/Hacking General [Developers Only]] metropical:
true, but one LG G4 is seen no problem in both FWUL (Simple adb) and SALT (download mode). The other doesn't. Both with manual toggle in VB USB setting.

I'll look at the IRC.

OK. AS we said, the earpiece issue is prolly physical so I'll get about replacing that. Though I'm starting to think, due to other issues, that phone is going.
[Android Software/Hacking General [Developers Only]] metropical:
here's the link to the non-co-operating G4 log - http://bpaste.net/show/bce6eb7244f7

and to the co-operating G4 - http://bpaste.net/show/df7ce9d1eaa3
[Android Software/Hacking General [Developers Only]] steadfasterX:
New version has been released

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

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 [MENTION=8699949]ThePiGuy[/MENTION]). 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
[Android Software/Hacking General [Developers Only]] Windows10Mobile:
If I do have a frankenstein device, can I use SALT to unlock my lg g4? It is a h815t actually but it's motherboard got replaced. They said, they flash the old imei to the new motherboard. In settings it shows H815TR, but with a H815T IMEI.
[Android Software/Hacking General [Developers Only]] steadfasterX:
identify your REAL model by opening the device (sounds harder then it is: https://ifixit.com/Teardown/LG+G4+Teardown/42705)

view at the FRONT of the mainboard where your real model is shown.

.
[Android Software/Hacking General [Developers Only]] Josh McGrath:
Thanks for all you've done for us LG guys, steadfasterX
[Android Software/Hacking General [Developers Only]] hamed_forum:
when connect g4 to windows in download mode windows cant detect and in device manger dont show anything

i use virtaul machine FWUL and SALt in download mode g4 dont detect device (i install new driver change cable...)

what must i do?
[Android Software/Hacking General [Developers Only]] sdembiske:
Refer to post # 529 in the FWUL thread. There are two USB settings in Virtualbox that have to be checked, one of which has to be done every time you connect your device.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Run FWUL from an USB stick and not in VirtualBox.
[Android Software/Hacking General [Developers Only]] Arctic Prodigy:
I like FWUL and what SALT can do.

I am wanting to flash kdz SALT for my LG V10, I assume reason why it says to choose extract+flash when I mouse over extract kdz and their is not another option to extract+flash kdz is because it isn't quite available to flash kdz for the V10 yet, hope it will be available soon, thanks.
[Android Software/Hacking General [Developers Only]] jerry_s87:
Any other suggestions or just wait for it to be compatible?

Greetings, for everyone here a warm greeting. Recognize that they are a true encyclopedia, the first option of consultation and reference to any inconvenience.

Tell them that I am with my H871 for about 6 months, I have activated the secure boot with password. Yesterday I rebooted my phone for the first time since I enabled the secure boot, now I do not remember the password, I do not want to delete it, so I have been investigating and I have come this far, I plan to use this method to make a full backup and then if Proceed to delete the phone and recover the data with the FWUL applications. If I am wrong, please tell me what I should do.

At the time of executing the copy I receive this message, I thought it was space to save the copy, but reading here I see that it is something related to the type of partition, I am correct and I must wait for a later update of SALT, or do you have any Another suggestion to not lose my data? I enclose the screenshot and the link of the SaltDebug log. Thanks in advance. Administrators / Moderators, apologize if the topic is wrong.

SALT Debug Log File = http //bpaste dot net/show/3fea7d8d9708 (I'm not allowed links yet.)
[Android Software/Hacking General [Developers Only]] hamed_forum:
use refuse i boot FWUL live on usb but when running salt not device conncet

only see download mode and dont go Firmware Update

FWUL in fastboot mode can detect device dont have any commnad going to Firmware Update? or can in fastboot mode in FWUL install tot?
[Android Software/Hacking General [Developers Only]] hamed_forum:
keep pressing Volume up until you see "Download mode"

if see Download mode relase up key or no?

i do anything but in Download mode dont change to Firmware Update
[Android Software/Hacking General [Developers Only]] steadfasterX:
Flashing is an experimental feature and not activated yet.

Connect your device, go into the advanced menu and select the partition list option.

Close it and while in advanced menu select debug log and upload it by pressing the button there (see the SALT FAQ 1000b which also have a screenshot guide for the howto).

share the link.

Then I can tell you if you have may can enable the option to flash or not..

Thanks for sharing the log (which most ppl dont). Your device is supported by lglaf (the underlying backend of SALT) but not yet in SALT.

Besides that: When you have your phone encrypted like you have done then it will not help to back it up. You would just backup the encrypted data which is useless so even when SALT is doing magic it can't hack encryption.

There is no fastboot command to go into download mode.

When you see just that small download mode pic and not the real download mode SALT will not detect your phone as SALT requires a full loaded dl mode.

Try LGup instead as that will even work sometimes when SALT does not (LGup uses a different way for detecting a device).

You can always consider to share the SALT debug log. words are nothing, logs and screenshots are everything.

You can skip the detection window in SALT and go to the advanced menu (see the SALT FAQ 1000b which also have a screenshot guide for the howto)

.
[Android Software/Hacking General [Developers Only]] jerry_s87:
Wow !, Bad news for me. But do you think that the copy can be made at some point (SALT update), even if it is an encrypted copy? I think I could keep it and maybe in the future they will come up with a tool to manipulate it and thus try without limits of attempts to try to remember what was the password that I placed and get my data back, it is a way to maintain the hopes.

Also if your experience comes up with an idea that can help me, it would be great, in fact the only thing that interests me is the pictures of my baby and of course, I know that if they were so important I should have backups, I know, but humans, Sometimes, we are heavy and we rely a lot on these devices ....

:confused: Although thinking well, I do not remember having marked the option to encrypt phone, I just marked the option that referred to "ask for password when restarting the device",

Secure Start-up

, I guess the password as with samsung is used to encrypt the fingerprint not the phone. Unfortunately, I had never modified any part of the phone (recovery, etc) so everything is in stock. You can evaluate my analysis, it will be that the device itself is not encrypted, yes that is a password before the complete boot and only serves to protect the fingerprint, because I never indicated that the entire smartphone was encrypted, hence my hope of being able to take out the copy of my data partition that maybe is not really encrypted.

What do you think?