yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] sdembiske:
I was able to complete both full and partial SALT backups on H81210n - the important thing to keep in mind I think is that many more issues/problems have presented later after unlocking on LP than with MM, particularly as it relates to later flashing custom N and O roms. steadfasterX is now suggesting that for the H812, the bootstack version should be H81220x or higher for the H812 UsU LineageOS O version - refer to the listed Requirements in the [ROM][UNOFFICIAL][O][UsU] LineageOS 15.1 [H812] thread.
[Android Software/Hacking General [Developers Only]] windozeanti:
I am not able to run a basic or full backup in SALT. The following is the log:

https://bpaste.net/show/4f96dfa5e7b4

What am I doing wrong? Please advise.
[Android Software/Hacking General [Developers Only]] sdembiske:
Refer to post # 341 and see if that helps.
[Android Software/Hacking General [Developers Only]] tim455:
EDIT: saw the previous message and am trying with a shared drive......

Hi,

sorry if this is not in the correct forum, but I am trying to use SALT to backup user data from a LGG4 H811 that I've been given

from what I understand, this is the way to do it now, using SALT.

I'm using SALT via oracle vm virtual box using "FWUL_v2.6_x86_64_30GB.zip"

selecting FULL backup (which i understand has the user partition) says it will require 30GB and that I only have 3GB usable. (see attached)

The end goal would be to install UsU on the device once I've got anything I can off the device first. I'm not sure if I meet the requirements with this device, but that's something to figure out later perhaps...
[Android Software/Hacking General [Developers Only]] steadfasterX:
hi

1) SALT is not "the new way for backup" its meant as a replacement for LGup plus many more features like backup. TWRP (requires unlock) and/or FlashFire (requires root) is still the best way to backup your device.

so.. here some ideas when and how to use SALT for backup:

backup all important partitions (even those not covered by TWRP)

= use SALT basic backup - this is recommended at least once to ensure your device can be recovered one day

no TWRP installed but root

= use FlashFire (FF) + SALT basic backup

TWRP is installed

= use TWRP (will not backup userdata though) + root the device and use FlashFire or any other backup tool like Titanium Backup + SALT basic backup

no TWRP and no root possible (and you do *NOT* care about your data/pics/apps)

= use SALT basic backup

no TWRP and no root possible (and you do not want to loose your data/pics/apps)

= use SALT full backup

2) you need to point to a folder with enough disk space. read and follow FAQ #12

3) as you have a h811 there is no need to UsU'ing your device. Read the h811 unlock thread. its just a simple command in fastboot and just to be clear you have ARB 3 so UsU wouldn't work for you anyways.
[Android Software/Hacking General [Developers Only]] tim455:
Thanks steadfasterX :)

You're always amazing.

The phone is not rooted and is suffering from bootloop (it's not mine, I'm just trying to fix it).

Using the FULL backup option to do this.

Yes, I saw that too late before posting. Sorry about that. I tried to make an edit, but apparently you are too fast and you had already started trying to help. We don't deserve you <3

Oh, that should be easy enough then. I'll try getting the data this way, then try an unlock and maybe flash one of the 4core fixes I found on XDA. (I also dont know what version of android it is on). Cheers for the info

Thanks steadfasterX. You are amazing.
[Android Software/Hacking General [Developers Only]] tim455:
managed to do a FULL backup and ended up with a 29gb user partition... took a while.

tried mounting it with SALT but get an error saying that it could not be mounted, check the log. The log only shows:

0

F_MOUNTING ended

I have restarted my VM between uses (if that makes any difference) and it doesnt appear to be in persistent mode. (using vga failsafe mode 1 as it's the only option allowing it to actually boot)
[Android Software/Hacking General [Developers Only]] kudlinux:
Hi Steadfaster, I have toshiba laptop. The wifi shows its there, but it disconnects. Please help
[Android Software/Hacking General [Developers Only]] steadfasterX:
Share the log after trying to mount. Advanced menu. Debug log. Click the upload button. It can't be easier ;)

Yes VGA modes are never persistent. They are meant as fallback only.

Boot to vga fallback and open a terminal

sudo pacman -Sy xnxi

xnxi -b

Paste the whole output of the last command to http://bpaste.net

Exact laptop model? Post the answer in the correct thread then! This is about SALT and not about FWUL.
[Android Software/Hacking General [Developers Only]] kudlinux:
PSL- 48E. Please help. I
[Android Software/Hacking General [Developers Only]] kudlinux:
its Realtek 8197 manufacturer Wifi . Please help
[Android Software/Hacking General [Developers Only]] kudlinux:
I need SALT to download and install . Since the WIFI in FWUL is not working. Can i just manually download from windows and get that installed in FWUL?

Please Any specific commands to install? I'm new to Linux
[Android Software/Hacking General [Developers Only]] steadfasterX:
hm ok try this in a terminal

file /home/android/Desktop/sf_FWUL/userdata.bin
stat /home/android/Desktop/sf_FWUL/userdata.bin
fsck.ext4 -f -p /home/android/Desktop/sf_FWUL/userdata.bin

--> if that last one gives errors which cant be fixed automatically you have a problem with the backup file itself
[Android Software/Hacking General [Developers Only]] tim455:
[android@fwul ~]$ file /home/android/Desktop/sf_FWUL/userdata.bin
/home/android/Desktop/sf_FWUL/userdata.bin: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (needs journal recovery) (extents) (large files)
[android@fwul ~]$ stat /home/android/Desktop/sf_FWUL/userdata.bin
File: /home/android/Desktop/sf_FWUL/userdata.bin
Size: 24935137280	Blocks: 48701440 IO Block: 4096 regular file
Device: 2ch/44d	Inode: 59 Links: 1
Access: (0770/-rwxrwx---) Uid: ( 0/ root) Gid: ( 109/ vboxsf)
Access: 2018-07-02 14:12:28.241806000 +0000
Modify: 2018-07-02 16:32:10.162174800 +0000
Change: 2018-07-02 16:32:10.162174800 +0000
Birth: -
[android@fwul ~]$ fsck.ext4 -f -p /home/android/Desktop/sf_FWUL/userdata.bin
/home/android/Desktop/sf_FWUL/userdata.bin: recovering journal
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 66417 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 66852 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 74355 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 75133 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 91606 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 123394 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 180493 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 188909 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 197369 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 230104 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 540985 extent tree (at level 1) could be shorter. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 1310768 extent tree (at level 1) could be narrower. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: Inode 1311441 extent tree (at level 1) could be narrower. IGNORED.
/home/android/Desktop/sf_FWUL/userdata.bin: 136204/1523712 files (7.1% non-contiguous), 4283541/6087680 blocks
[android@fwul ~]$

I'm not sure what I'm looking for here...
[Android Software/Hacking General [Developers Only]] steadfasterX:
great. now try again to mount it in SALT

EDIT

just for info: the above run will be included in one of the next SALT releases: https://github.com/steadfasterX/SALT/issues/18
[Android Software/Hacking General [Developers Only]] steadfasterX:
yea USB in VMs is sometimes error prone..

ok but before: I would like to see the error.

in a terminal:

sudo mkdir /mnt/mydata
sudo mount /home/android/Desktop/sf_FWUL/userdata.bin /mnt/mydata
dmesg | tail -n 20
[Android Software/Hacking General [Developers Only]] tim455:
[android@fwul ~]$ sudo mkdir /mnt/mydata
[sudo] password for android:
[android@fwul ~]$ sudo mount /home/android/Desktop/sf_FWUL/userdata.bin /mnt/mydata
mount: /mnt/mydata: can't read superblock on /dev/loop1.
[android@fwul ~]$ dmesg | tail -n 20
[ 5549.632304] Buffer I/O error on dev loop1, logical block 24350659, async page read
[ 5866.014078] usb 1-2: reset high-speed USB device number 8 using ehci-pci
[ 5941.791902] usb 1-2: reset high-speed USB device number 8 using ehci-pci
[ 5972.795951] print_req_error: I/O error, dev loop1, sector 48701312
[ 5972.795971] print_req_error: I/O error, dev loop1, sector 48701312
[ 5972.795973] Buffer I/O error on dev loop1, logical block 6087664, async page read
[ 5972.796100] print_req_error: I/O error, dev loop1, sector 64
[ 5972.796105] isofs_fill_super: bread failed, dev=loop1, iso_blknum=16, block=32
[ 5972.796148] print_req_error: I/O error, dev loop1, sector 48701312
[ 5972.796166] print_req_error: I/O error, dev loop1, sector 0
[ 5972.796170] SQUASHFS error: squashfs_read_data failed to read block 0x0
[ 5972.796171] squashfs: SQUASHFS error: unable to read squashfs_super_block
[ 5972.800283] print_req_error: I/O error, dev loop1, sector 48701312
[ 5972.800288] Buffer I/O error on dev loop1, logical block 24350656, async page read
[ 5972.800292] print_req_error: I/O error, dev loop1, sector 48701314
[ 5972.800293] Buffer I/O error on dev loop1, logical block 24350657, async page read
[ 5972.800295] print_req_error: I/O error, dev loop1, sector 48701316
[ 5972.800296] Buffer I/O error on dev loop1, logical block 24350658, async page read
[ 5972.800297] print_req_error: I/O error, dev loop1, sector 48701318
[ 5972.800299] Buffer I/O error on dev loop1, logical block 24350659, async page read
[android@fwul ~]$

originally i did it via a shared network drive from my windows SSD C drive (via VirtualBox), didnt verify the first time.

This time ill try via usb and verify after too.

Upon entering these last 3 commands, i just started doing another backup to usb.

thanks for the ongoing help
[Android Software/Hacking General [Developers Only]] steadfasterX:
ooh.. yea.. that is Virtualbox shared folders related! we cant't mount the file from there..

if you would put that userdata file e.g. on another USB stick (or like you have done before via a shared network drive from the windows SSD) and mount that in FWUL then SALT should be able to mount it.

The reason why it had not worked before and now should? the filecheck we have done (fsck.ext4 above)

.
[Android Software/Hacking General [Developers Only]] uweork:
first...salt ist already installed.

second...no you cant upgrade salt trough windows

third...Wifi in fwul is ok only search ssid and passwort and it should connect (beware The keys are USA not Europe so y and z are switsched...)
[Android Software/Hacking General [Developers Only]] kudlinux:
Hi Steadfaster,

I just burned the image of 2.37 release to USB. you saying Salt is already there in it? The wifit cannot just connect, it disconnects. I dont know what wrong I'm doing . Please help.

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

I have SSID, but its not connecting. I put password and keeps disconnecting, not connecting at all.

---------- Post added at 11:57 AM ---------- Previous post was at 11:56 AM ----------
[Android Software/Hacking General [Developers Only]] kudlinux:
Hi Steadfasterx,

When SALT is already installed, my working on WIFI is baseless. I just want to unlock G4( H810). Do i still need WIFI?

How should i start the SALT which is already installed.

I mean to say , how should i start the SALT from terminal or GUI. I have gone through whole of description of the page, but i cannot understand how to start the SALT.

Once i know the command to start the salt, i shall go from there to unlock . Please help. I dont know anything about LINUX.

Also i'm entering correct password, it is not just connecting the SSID.

you are of great help.
[Android Software/Hacking General [Developers Only]] steadfasterX:
uhm.. on the desktop..

.. there is a folder named

LG

( I guess you have one ).

FWUL is made to make things easy for Windows users you dont need to know anything about Linux.
[Android Software/Hacking General [Developers Only]] kudlinux:
Hi SteadfasterX,

Thank you. Is the ICON LG LAF (auth) ?
[Android Software/Hacking General [Developers Only]] steadfasterX:
you are NOT running FWUL 2.7 !

This is from the FWUL OP:

stop using an outdated FWUL release and use the newest one.

and consider to use the thanks button from time to time .. :p
[Android Software/Hacking General [Developers Only]] kudlinux:
Thank you.
[Android Software/Hacking General [Developers Only]] steadfasterX:
not saying (only) - clicking.. there is a thanks button on each post.. :eek:
[Android Software/Hacking General [Developers Only]] steadfasterX:
this is the last warning. This is NOT the FWUL thread.

THIS is the FWUL thread:

https://xdaforums.com/android/software-hacking/live-iso-adb-fastboot-driver-issues-t3526755
[Android Software/Hacking General [Developers Only]] tim455:
Hello again,

I've moved my userdata.bin backup to an external usb and am now able to mount it, but I am not sure of my next step.

I would have thought that most of my data would be in the /media folder, however, it shows a broken folder (or something) and states

"error opening directory '/mnt/salt/mnt/
media': permission denied

i've attached an image of what the root of the userdata image shows

cheers

EDIT: saw the "inxi" mention in the FWUL thread. not sure if needed anymore but here's the output

[android@fwul backup_usb]$ inxi -b
System: Host: fwul Kernel: 4.14.20-1-rt17-MANJARO x86_64 bits: 64 Desktop: N/A
Distro: Manjaro Linux 17.1.6 Hakoila
Machine: Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial: <root required>
Mobo: Oracle model: VirtualBox v: 1.2 serial: <root required> BIOS: innotek v: VirtualBox
date: 12/01/2006
CPU: Single Core: Intel Core i5-3570K type: MCP speed: 3400 MHz
Graphics: Card-1: InnoTek Systemberatung VirtualBox Graphics Adapter driver: vboxvideo v: 5.2.8 r120774
Display: x11 server: N/A driver: modesetting unloaded: fbdev,vboxvideo,vesa
resolution: <xdpyinfo missing>
Message: Unable to show advanced data. Required tool glxinfo missing.
Network: Card-1: Intel 82540EM Gigabit Ethernet driver: e1000
Card-2: Intel 82371AB/EB/MB PIIX4 ACPI driver: piix4_smbus
Drives: HDD Total Size: 741.12 GiB used: 231.88 GiB (31.3%)
Info: Processes: 143 Uptime: 1d 9h 24m Memory: 4.81 GiB used: 968.1 MiB (19.7%) Shell: bash inxi: 3.0.12
[Android Software/Hacking General [Developers Only]] steadfasterX:
Do you had mounted the image file with SALT or manually?

SALT takes care about the permissions so after mounting it offers you to browse the mounted file. That should avoid the permission error.

The inxi is regarding FWUL and so related to the FWUL thread (that's why I posted it there). You said you can't boot persistent but you are using VirtualBox. So I recommend to read the FWUL faq regarding persistent mode and how to enable it in VirtualBox. Any further discussion in the fwul thread please!
[Android Software/Hacking General [Developers Only]] tim455:
I am using the inbuilt SALT mounting. Perhaps it's my dump... I'm not sure.
[Android Software/Hacking General [Developers Only]] tim455:
i've tried dumping again and hit similar error. (dumping via virtual box and shared network for saving the dumps)

EDIT: uploading log...

EDIT2: file is quite large. wont upload to http://bpaste.net

EDIT3:

https://gitlab.com/gimmiedat/test_proj/raw/master/error.log

sorry, i've uploaded them to gitlab, which requires a signup... its all i had at the time. if not ok ill try something else.
[Android Software/Hacking General [Developers Only]] steadfasterX:
I cant access your log...

maybe just zip it and attach it here..

and again.. running FWUL within VirtualBox should work but is not recommended for such operations.. (checkout https://github.com/Carbon-Fusion/build_fwul/issues/76 )
[Android Software/Hacking General [Developers Only]] tim455:
Now I just feel silly. From 40mb to 4mb when zipped.

I didn't realise that this was the case. I'll try getting a USB going again

Thanks
[Android Software/Hacking General [Developers Only]] steadfasterX:
looks good mostly. The error on userdata is due to a timeout (common issue on several firmwares - there is no easy fix for that other then trying several firmwares).

The other errors are strange. Do you have rebooted the phone between taking the backup and before verifying??

I still strongly recommend to not use VirtualBox for these kind of operations. Next FWUL release will give a warning popup on login when running in a VM.

USB emulation is not 100% stable on

no

Virtualization software.. (refer to https://github.com/Carbon-Fusion/build_fwul/issues/76 )

.
[Android Software/Hacking General [Developers Only]] whitewolf1608:
Hello, Dear steadfasterX user :)

I downloaded your SALT app from this link>

https://xdaforums.com/android/software-hacking/live-iso-adb-fastboot-driver-issues-t3526755

>

https://androidfilehost.com/?w=files&flid=214529

>

https://androidfilehost.com/?fid=11050483647474833357

I downloaded this downloaded image. Img on PenDrive

Please send me instructions on how to run the SALT application on the system

Windows OS?

Dear User SteadfasterX, I am asking you with a very sincere request asking how to start from this SALT app - with PenDrive on USB 3.0 it will work?

Dear User SteadfasterX I have PenDrive USB 3.0. I am asking you for support or this PenDrive - will it work? On Windows 7 I downloaded Rufus applications to create bootable PenDrives. I have recorded this image in the USB 2.0 port but I have a problem - visible on the screen>

https://drive.google.com/file/d/1JpBxKcu_twiWu8snfp2CCYE5mbEs4P5D/view?usp=drivesdk
[Android Software/Hacking General [Developers Only]] jd.21:
[MENTION=5545101]steadfasterX[/MENTION]

is it possible to reflash the backed-up partitions on non-rooted devices with the latest release salt 3.16?
[Android Software/Hacking General [Developers Only]] steadfasterX:
Yes but it is still an experimental feature and it will not work on nougat.

If you can't wait for v4 write me a PM.
[Android Software/Hacking General [Developers Only]] smzubair:
Can't Take a Backup

I'm trying to take a basic or full backup from SALT on Lg G4 H810 after UsU. After start it already finished 100%. After clicking close(wait until you see all finished) it throws an error

Backup incomplete! check the log. After that it offers to verify the backup, clicked verify, again error "does not exist!"

This is the log: http://bpaste.net/show/6e1d43442cf4

Seeing the log file this line suspects to me

"failed to change ownership of '/home/android/salt_backup' to android" I needs an advice what is the problem and how to solve?:crying:
[Android Software/Hacking General [Developers Only]] steadfasterX:
The problem is

"backup size: 0"

Which means SALT is not able to extract the partition sizes and so the rest is failing.

How to solve:

Wait for a fix in SALT.

There is nothing you can do atm.
[Android Software/Hacking General [Developers Only]] tim455:
Tried puting the latest FWUL (v2.7) on a usb and booting from my PC. Ran into a strange issue where it stopped after a while... possibly due to going into sleep mode (or something)

Managed to do a full dump, however, upon verify, it stopped/hung right at the end, ultimately not verifying the userdata partition, which is the only one I wanted :\

<< I then restarted into Win7 and booted my VM to try to read from the user partition >>

However, I am able to mount the image and search around and can confirm that there are files in the /media/ folder. HOWEVER, they appear to be locked or something. (actually, various folders including /media appear to be locked)

Trying to access the folders via terminal gives a PERMISSION DENIED message.

I may try rebooting and trying from FWUL again, or perhaps taking another dump and testing straight away.

Didnt manage to get any logs. Also, from v2.6 the logs no longer appear to be kept in ~/ anymore...

EDIT: added screenshot
[Android Software/Hacking General [Developers Only]] steadfasterX:
You must use the "Browse Image" button after mounting the image with SALT.

This will start a file browser with root perms allowing to access all data.

If you do not want a file explorer and instead want to use a terminal use sudo -s before changing in the mount directory.

-
[Android Software/Hacking General [Developers Only]] steadfasterX:
please change SALT to the TESTING channel (see this thread FAQ #10) and try again. It should still fail but now give a meaningful error and more important generates some log lines I need.

So choose a basic backup.

Then if it fails or not go in the advanced menu and share the debug log
[Android Software/Hacking General [Developers Only]] tim455:
Hi,

I am/was using SALT to browse and mount the image, in fact, when mounting from salt the image appears and very quickly disappears from the file browser, so it would be impossible otherwise to view the files.

Used 8gb usb and the FWUL v2.7 8gb image (and RUFUS method). saved to a separate exFAT usb.

Furthermore, I guess there's something wrong with this device because I've attempted to dump it again but come up with the same issue.

I've attached the log and a similar verify mismatch.

I guess this is the end of my journey.....?

NOTE: I can view pictures from the userdata image/partition, but i can not copy the jpg/png/etc from the image/partition to anywhere else, as it still says permission denied.

EDIT2: turns out that I can use the terminal and sudo -s to open the /media folder and then copy its contents out onto my USB... this might actually work....

EDIT3: looks like its working :) will update with more information later.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Ok sorry I just realized that I start the file explorer with the regular user permissions.

Please switch to the TESTING channel (see FAQ #10) and after mounting you will see a new button named "Browse Image (root)".

Choose that one and it will work.
[Android Software/Hacking General [Developers Only]] tim455:
No, no, don't be sorry. Just glad I can help test this for you. It in turn helps others down the line. You're the real MVP here :)

I tried the development/testing branch like FAQ10 says, but it still didnt work for whatever reason. (tried the oringal browse image and browse image root. Both do not work.)

It seem the terminal work-around will suffice for now (for me at least)

Happy to help test anything if you want :)

thanks again.
[Android Software/Hacking General [Developers Only]] steadfasterX:
hmm the root one must work.. could you mount it again while using the Browse Image(root) button and then while leaving that file browser window open type this in a terminal :

ps aux | grep xdg

paste the output here pls
[Android Software/Hacking General [Developers Only]] lowtiertrash:
repost

https://bpaste.net/show/a64c36c2cff7

Results are the same. It saves to /root/salt_backup. However when I go to extract it, nothing is there.
[Android Software/Hacking General [Developers Only]] steadfasterX:
So the log shows that you are backing up to /root/salt_backup and as there are backup files already in there it skips most of them.

This log does not show any tries of extracting a KDZ.

I dont understand that "When I try to extract a kdz from backup". That makes no sense. You can either do a backup or extract a KDZ file. Totally different things..

.