yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Almighty1:
Thanks steadfasterX as I thought the /sdcard was unmounted as I did a df using the Open a shell in the advanced menu and couldn't find the /sdcard mounted which was why I was asking about the Full Backup if it did include the internal sdcard or not. I was also looking at the Show Partitions and couldn't figure out which one was the internal sdcard storage. I just hope the battery at 100% charge will have enough capacity to do the Full Backup since the phone doesn't work anyways as of now, 6 hours isn't really a problem as long as the data is available and I can just extract or copy the sdcard's contents and everything below it without doing each file or folder individually.
[Android Software/Hacking General [Developers Only]] steadfasterX:
internal storage = userdata in SALT or in Android /data/media or /sdcard

you may be able to mount it in the shell like this:

mount /data

.
[Android Software/Hacking General [Developers Only]] Almighty1:
Thanks, I forgot about the /data/media bit since the phone isn't working and it's been a long day, still haven't slept yet. Where would /data/apps in Android be under SALT?

I noticed in the shell, the cd command is not changing the directory as it seems to be stuck in / and I'm trying to do ls |more or ls |less except it says permission denied.

I tried mount /data and it didn't work:

#mount /data

as it responds with the usage line.
[Android Software/Hacking General [Developers Only]] steadfasterX:
no cd will not work there. only commands and which ones are limited by the firmware (unless you fully unlock your device ofc)

ah sorry about that you need to:

mount -t ext4 /dev/block/bootdevice/by-name/userdata /data

(there is a thx button beyond each post ;) )
[Android Software/Hacking General [Developers Only]] Almighty1:
Haven't slept so not thinking well as /data is already mounted so the challenge is how do I get more/less working since ls will list everything except anything that doesn't fit the screen cannot be seen. cd worked fine from the terminal on the phone as well as busybox.
[Android Software/Hacking General [Developers Only]] steadfasterX:
cd and many others like using less/more will not work in download mode! Its very limited. only simple commands nothing else.

better take a couple of sleep or just start the full backup before going to sleep ;)

EDIT: you can see if /data is mounted by just typing:

mount
[Android Software/Hacking General [Developers Only]] steadfasterX:
NEW SALT RELEASE

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

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
[Android Software/Hacking General [Developers Only]] Leg0V0geL:
Restore?

It all works after I have flashed the file and I made my backups. By the way thanks for making this awesome software!

Now I have all the files but how can I restore them?
[Android Software/Hacking General [Developers Only]] steadfasterX:
you can restore them with SALT v4.0

or by flashing them in fastboot / TWRP ...

.
[Android Software/Hacking General [Developers Only]] Almighty1:
I know what you meant about it being limited, just never knew even cd doesn't work correctly. Is there any other way to really see the entire list of files other than doing a "ls -al > filename" so it logs the output to a file since other than a Full Backup, I'm trying to find files in the normal /sdcard to delete to free up some space to fix the phone from booting up and I know a majority of it is in /sdcard/Tencent as that's where the WeChat cache is and also, clearing the data for Google Play Services usually will fix the problem except not sure what I need to delete exactly for that to happen.

Also, how long is backing up system supposed to take in Full Backup as I started the backup at 5:00AM (GMT -800) which was 8 hours and 23 minutes ago and it is still doing the system backup with the last timestamp at 5:16AM for system.bin which was 8 hours and 8 minutes ago and the phone already did the low battery warning sound about 5 minutes ago.
[Android Software/Hacking General [Developers Only]] අධිරාජ (Adhirāja):
Who said we have to use Virtualbox or live boot???

Hi steadfasterx:

I know you said previously only to run FWUL on Oracle VirtualBox or burn to Flash drive. But guess what? I created an FWUL Virtual Machine using VMWare Workstation, and connected the phone, and started SALT just to test it. And you know what?? It detected everything PERFECTLY.

Please see attached images as proof.

So why do we HAVE to use virtualbox or live boot?? It worked perfectly with me so everyone reading this, you can boot FWUL on any hypervisor.
[Android Software/Hacking General [Developers Only]] steadfasterX:
This sounds like you ran out of space.

I hope you choosen a place where you have enough ( 33 GB ) free space available.

Yes you can exec for example with lglaf.py an EXEC and then pipe that output locally. Look at the lglaf repo to see an example. Lglaf is installed on your system in /root/programs

FWUL run in any hypervisor.

Use VirtualBox, KVM, XEN, ESX, Hyper-V or VMware workstation or put it into docker or LXC.

All will work. Every of these have its own issues. Especially when it comes to shared folders or USB itself.

Support only for VirtualBox!

Use whatever you want but don't expect any support if you encounter issues. I can't support any possible hypervisor.

Btw the wrong place to complain about FWUL. This is about SALT.
[Android Software/Hacking General [Developers Only]] අධිරාජ (Adhirāja):
Ok thank you. I'll burn FWUL to a flashdrive or a DVD-RW before I do the SALT backup. Also one more question sir, I was looking at the partition table provided by SALT, and noticed it is different to that found in /proc/partitions file. Here is the contents of /proc/partitions :

<code>

major minor #blocks name

253 0 715332 zram0

179 0 30535680 mmcblk0

179 1 88064 mmcblk0p1

179 2 512 mmcblk0p2

179 3 1024 mmcblk0p3

179 4 1024 mmcblk0p4

179 5 512 mmcblk0p5

179 6 512 mmcblk0p6

179 7 512 mmcblk0p7

179 8 2048 mmcblk0p8

179 9 1024 mmcblk0p9

179 10 512 mmcblk0p10

179 11 1024 mmcblk0p11

179 12 512 mmcblk0p12

179 13 512 mmcblk0p13

179 14 2048 mmcblk0p14

179 15 512 mmcblk0p15

179 16 512 mmcblk0p16

179 17 512 mmcblk0p17

179 18 512 mmcblk0p18

179 19 512 mmcblk0p19

179 20 512 mmcblk0p20

179 21 1536 mmcblk0p21

179 22 16384 mmcblk0p22

179 23 32768 mmcblk0p23

179 24 1536 mmcblk0p24

179 25 1536 mmcblk0p25

179 26 1536 mmcblk0p26

179 27 512 mmcblk0p27

179 28 512 mmcblk0p28

179 29 512 mmcblk0p29

179 30 2048 mmcblk0p30

179 31 512 mmcblk0p31

259 0 512 mmcblk0p32

259 1 512 mmcblk0p33

259 2 512 mmcblk0p34

259 3 2048 mmcblk0p35

259 4 4096 mmcblk0p36

259 5 49152 mmcblk0p37

259 6 40960 mmcblk0p38

259 7 40960 mmcblk0p39

259 8 8192 mmcblk0p40

259 9 8192 mmcblk0p41

259 10 32768 mmcblk0p42

259 11 8192 mmcblk0p43

259 12 4096 mmcblk0p44

259 13 4096 mmcblk0p45

259 14 16384 mmcblk0p46

259 15 40960 mmcblk0p47

259 16 8192 mmcblk0p48

259 17 47104 mmcblk0p49

259 18 2048 mmcblk0p50

259 19 10240 mmcblk0p51

259 20 6144 mmcblk0p52

259 21 4386816 mmcblk0p53

259 22 1261568 mmcblk0p54

259 23 24350720 mmcblk0p55

259 24 12271 mmcblk0p56

179 32 4096 mmcblk0rpmb

</code>

As you can see there is no modem or aboot or bootloader partitions according to this output. Could you please tell me why there is such a difference? Thanks:D
[Android Software/Hacking General [Developers Only]] ziomus684:
Hello everybady, i have big problem after encryting in kessaras room AOSP oreo, becouse now i can't enter system, recovery and download mode(all time after few secounds rebooting). Bootloader ok. I am very green, how i can run SALT. I'm in command line:

C:\Users\Mateusz>cd "C:\Users\Mateusz\Desktop\SALT-master"

C:\Users\Mateusz\Desktop\SALT-master>

end i don't know what i have to do? "bash install-desktop.sh" How?? Please write me commend, wchich i should enter in commandline. Very thanks!

----------------------------------------------------------

I burn FWUL_v2.6_x86_64_forgetful.iso on pendrive and opened salt, but it's working only bootloader mode. i think i must flash bootloader by faastboot, but i can't make this by "simple-ADB".

[fastboot erase data]

erasing 'data'...

FAILED (remote: cannot erase this partition in unlocked state)

finished. total time: 0.020s

===================

[fastboot flash bootloader /home/android/Downloads/LG-H815_v29A_bootloaderonly.zip]

target reported max download size of 536870912 bytes

sending 'bootloader' (232513 KB)...

OKAY [ 7.545s]

writing 'bootloader'...

FAILED (remote: cannot flash this partition in unlocked state)

finished. total time: 7.561s

===================
[Android Software/Hacking General [Developers Only]] steadfasterX:
You do not provide the salt log when the issue occurs. Log files are there so I don't need to guess. There is even a simple upload button to make that as easy as possible!

Just use this cmd to backup only userdata:

sudo python3 partitions.py --dump /media/sf_FWUL_Backup/userdata.img userdata

(and ofc there is planned to backup custom partitions I can't do everything the same time. Check the issues on SALT github)

But jfi: you have a strange issue and doing this from the command line will NOT fix it. Also pls use USB 3 if possible and another USB cable.

Regarding the exec stuff i told you to look at the lglaf repo not in a thread https://github.com/Lekensteyn/lglaf/blob/master/README.md

Ok so even if this thread here is about SALT and NOT(!) about lglaf (you found the lglaf thread already) here is an example :

sudo python3 ./lglaf.py --debug -c '!EXEC find /data/media\0' | less

or

sudo python3 ./lglaf.py --debug -c '!EXEC ls -la /data/media\0' | less

What do you want with SALT then? Read the OP. SALT does not run on windows.
[Android Software/Hacking General [Developers Only]] ziomus684:
I burn FWUL_v2.6_x86_64_forgetful.iso on pendrive and opened salt, but it's working only bootloader mode. i think i must flash bootloader by faastboot, but i can't make this by "simple-ADB".

[fastboot erase data]

erasing 'data'...

FAILED (remote: cannot erase this partition in unlocked state)

finished. total time: 0.020s

===================

[fastboot flash bootloader /home/android/Downloads/LG-H815_v29A_bootloaderonly.zip]

target reported max download size of 536870912 bytes

sending 'bootloader' (232513 KB)...

OKAY [ 7.545s]

writing 'bootloader'...

FAILED (remote: cannot flash this partition in unlocked state)

finished. total time: 7.561s

===================[/QUOTE]

meaby i should relock phone command- fastboot oem lock end again flash bootloader?
[Android Software/Hacking General [Developers Only]] steadfasterX:
This thread is about SALT not about FWUL.

Besides that I don't understand your issue.

If you want to erase your complete internal storage:

use TWRP not fastboot.

If you want to flash the bootloader zip:

use TWRP not fastboot.

Open an own thread in help section if you need help on a non specific issue.
[Android Software/Hacking General [Developers Only]] ziomus684:
I can't enter recovery. when i entering recovery redirects to download mode. Download mode always after few secounds rebooting. When i try boot recovey i get this:

C:\Users\Mateusz\Desktop\platform-tools>fastboot boot lgg4-twrp.img

downloading 'boot.img'...

OKAY [ 0.715s]

booting...

FAILED (remote: unknown command)

finished. total time: 0.736s
[Android Software/Hacking General [Developers Only]] steadfasterX:
Learn to read really. It's all written it's all known. You can't use fastboot boot on nougat bootloader stack!!!!!

I said open an own thread if your are too lazy to use the XDA search or read e.g. the OP of this thread. Maybe you have luck and someone answers regardless of that..
[Android Software/Hacking General [Developers Only]] Almighty1:
I couldn't provide the SALT log because the last two times it happened, one of the times, the host machine ended up in a BSOD while the most recent time, FWUL was no longer responded and Oracle VirtualBox terminated in the host machine with some memory read error after the FWUL was no longer responsive. So with both of those two, I would assume the SALT logs would have been gone since the FWUL and SALT is starting from a cold start.

In any case, before you responded, I figured out how to do the backing up of userdata and the log is at:

https://bpaste.net/show/c3e7507d290e

What is interesting is generally for flashing, people recommend the OEM cable and to only use USB2.0 ports and never USB3.0 ports as USB3.0 is the one that usually will fail except I have tried both USB2.0 and USB3.0 under SALT and USB3.0 in this instance with the LG OEM cable which is the most reliable cable. I'll try another cable and see what happens and will post the results. I don't know if the issue is with the LG G4 or is it with the host machine since in SALT, it seems like the process has hanged but in lglaf, it seems like there is some sort of USB timeout. As for the lglaf example, I actually read that already and had trouble understanding exactly the syntax of the command. I know this is the SALT thread which is why I try not to ask FWUL questions as I didn't realize you were the author of both SALT and FWUL but not the author of lglaf but lglaf comes with both FWUL and SALT and obviously you have to know about using lglaf to it's full capacity to be able to put out SALT which was the reason I was asking.

In any case, it seems that even though the phone has been in download mode for the last 48 hours, the battery is still 100% when I connected it to the charger and tapped the power button and the same 100% is reported when SALT starts. I have tried a different USB cable that is OEM Motorola that is known to be reliable and it seems like there is still a hang backing up /system except it happens earlier as I noticed both the USB and Storage lights are no longer shown on the bottom of the Oracle VirtualBox, this time I am using the forgetful mode and updated SALT to 3.9-0 Stable.

This is the log:

http://bpaste.net/show/6ebea978fcc8
[Android Software/Hacking General [Developers Only]] අධිරාජ (Adhirāja):
Sir pls refer to post #206 thanks.
[Android Software/Hacking General [Developers Only]] steadfasterX:
could you do me a favor? write shorter sentences. you concatenate several sentences with either a "but" or an "and" and its incredible hard to read. just before you use a BUT or AND ensure it is really needed ;)

thanks

USB 3 is pretty fine and working good. In terms of Virtualbox its even recommended to use USB 3. Yes there is a timeout coming from LAF/lglaf and so it stops.

you can try to do the dump command with --debug to find out more but I guess it will be not that much helpful.

There is already an issue opened for the timeout thing btw https://github.com/steadfasterX/SALT/issues/11 but it might be not enough to just increase the timeout.

So my suggestion is:

try USB 3 as it is more reliable

use --debug

and disable the timeout: https://github.com/steadfasterX/lglaf/blob/g4-stable/lglaf.py#L291 (set this to 0)

test with the above and provide the output

.
[Android Software/Hacking General [Developers Only]] steadfasterX:
mmcblkXXX is the block device.

modem, aboot etc are just names and linked to these block devices. For any further questions use google.

.
[Android Software/Hacking General [Developers Only]] steadfasterX:
New Release

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

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
[Android Software/Hacking General [Developers Only]] David X:
Thank you very much for creating these tools. I have a G4 H812 and just try to root it. I have copy UsU files to phone internal storage, but I don't know how to do next step 'start SALT'. I have struggled many hours trying to find way to install/start SALT, but no success. Can you please explain the steps to install SALT or show me a link to do that? Thanks again.

update: finally I found the ways to do that, sorry for above questions.
[Android Software/Hacking General [Developers Only]] fil3s:
I can't update salt in 2.6 persistent how do I manually update it?
[Android Software/Hacking General [Developers Only]] steadfasterX:
provide the log after updating.

.
[Android Software/Hacking General [Developers Only]] fil3s:
My 64gb USB drive crapped itself. Won't format, won't show up in device manager . Looks like I'll have to get a new one

---------- Post added at 11:58 AM ---------- Previous post was at 11:52 AM ----------

I left fwul running all night lol. Fell asleep.
[Android Software/Hacking General [Developers Only]] fil3s:
I updated to 3.10.1 ok by a 8GB USB ,took a basic backup, verified it but after that it won't let me into advanced menu. I restarted FWUL and got a crash on booting it. The same happened on previous FWUL :confused:

Also after the backup it wouldn't reboot the device out of DL mode
[Android Software/Hacking General [Developers Only]] steadfasterX:
where do you store the backups you made in SALT?

I guess in /home and so you are limited in free space.

If so keep in mind that when you ran out of space the things you mention here can happen.

Always choose e.g. a windows mount or another storage.

.
[Android Software/Hacking General [Developers Only]] fil3s:
Yeah thanks. Might give VB another shot.

Jk. :good:

---------- Post added at 01:28 PM ---------- Previous post was at 01:26 PM ----------
[Android Software/Hacking General [Developers Only]] steadfasterX:
New Release

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

v3.11-1

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 spaces or special chars failed (empty partition list on extract)
[Android Software/Hacking General [Developers Only]] steadfasterX:
Update again (should be on 3.11-1 now instead of 3.11-0)

try again pls
[Android Software/Hacking General [Developers Only]] mwahahaa:
Still not working for me on 3.11.1: http://bpaste.net/show/a56c870cc823
[Android Software/Hacking General [Developers Only]] steadfasterX:
ok for now pls do not use spaces in the target directory. you have defined the dir "/home/android/Desktop/MM bootstack" so pls use something like "/home/android/Desktop/MM_bootstack" instead

.
[Android Software/Hacking General [Developers Only]] mwahahaa:
Changed it, but says "missing required file to check for ARB (checked for: )! http://bpaste.net/show/0aa5d66a1f2b
[Android Software/Hacking General [Developers Only]] steadfasterX:
no log no cookies.
[Android Software/Hacking General [Developers Only]] mwahahaa:
There is a log edited in but you must have responded before I included it. Thanks. http://bpaste.net/show/0aa5d66a1f2b
[Android Software/Hacking General [Developers Only]] izzle47:
Hello, I'm getting an issue here with my devices being detected in Salt, am on FWUL with the latest version 3.11-1, I boot into download mode and connect the device but salt doesn't recognize it

The devices are lg h810 running h81010o kdz and lg vs986 running vs98610b LP

Ps. When I connect a h815 in download mode it gets detected in Salt
[Android Software/Hacking General [Developers Only]] steadfasterX:
Im not a magician ;)

connect device in download mode to your PC, start SALT, when the device gets not connected: wait at least 2 minutes and retry several times afterwards

if it still fails reboot the PC while the device is connected in dl mode (it must be connected before the PC boots) and try again

most important at all: grab the logfile before rebooting or closing SALT (advanced menu -> debug log -> upload button -> share the link)
[Android Software/Hacking General [Developers Only]] steadfasterX:
something bad happened with your SALT installation. It cannot start anymore..

try to re-install SALT if possible
[Android Software/Hacking General [Developers Only]] izzle47:
Here is the log file https://bpaste.net/show/5f694185775d

I tried all the above still not getting detected as it should am running salt in FWUL in a virtual machine don't know if that really makes any difference. Thanks.
[Android Software/Hacking General [Developers Only]] steadfasterX:
nice a complete different vendor model id?! :eek: LG is doing crap everywhere..

Yes it totally makes a difference. Best is always to use an USB stick/sdcard/DVD to boot FWUL especially when having issues regarding USB connections.

You can still try to set to USB 3 in Virtualbox settings and see if that helps.

.
[Android Software/Hacking General [Developers Only]] izzle47:
So I used a USB stick to boot FWUL and salt now recognizes the device. Thanks alot. :o:o:good:
[Android Software/Hacking General [Developers Only]] Bcoates84:
request

requesting, salts to work with lg v20 h915

tnx
[Android Software/Hacking General [Developers Only]] steadfasterX:
New release

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

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
[Android Software/Hacking General [Developers Only]] fates13:
Hey steadfaster, I've been trying to extract a couple KDZ's I downloaded off https://lg-firmwares.com and I keep getting an "arb-detect-error". When it gets to the point where I want to select a particular partition, they're all blank. Wondering if they've modified the KDZ or something. Other KDZ's I've downloaded from XDA extract fine.

http://bpaste.net/show/9250f138fc66
[Android Software/Hacking General [Developers Only]] Ceezar:
Can someone make a video on how to use this.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Hm the error is

Error: extraneous data found IN pad

So the underlying extract software cannot extract . I I will look into this later and thanks for providing both the links to the files you have used and the log
[Android Software/Hacking General [Developers Only]] adam_s_459_:
It's not hard to figure out you just open salt and there are a bunch of feilds with different info just click around (without your phone connected just in case) and figure it out yourself.
[Android Software/Hacking General [Developers Only]] fates13:
Here's the one I'm really trying to extract which I know for a fact throws that error: https://lg-firmwares.com/download-file/?fileId=9735
[Android Software/Hacking General [Developers Only]] steadfasterX:
New Release

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

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
[Android Software/Hacking General [Developers Only]] sdembiske:
Thank you for your work on this: Successful extraction now on H81220X kdz with arb version determined correctly!

Very much appreciated.

S.
[Android Software/Hacking General [Developers Only]] fil3s:
[MENTION=5545101]steadfasterX[/MENTION] .

I hope u enjoyed the donation. I'm out of this thread. Thanks :svetius:

Edit: sfx helped on irc and salt is working flawless. :highfive: