FORUMS
Remove All Ads from XDA

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

4,452 posts
Thanks Meter: 10,976
 
By steadfasterX, Recognized Developer on 11th December 2017, 03:34 PM
Post Reply Email Thread
21st December 2017, 12:47 PM |#21  
Junior Member
Thanks Meter: 5
 
More
MD5 verification on v29a
Hi,

I did backup yesterday when on ROM v20G..SALT detected that device is MD5 capable. I run verification there was only one error on userdata partition, and 8 warnings. today I'm on v29a and i did backup again and MD5 verification and i got 51 errors. there is something strange in log as well see bellow

2017-12-21 13:31:37: F_VERIFYBAK: vfilerem: fota, REMFILE: Hello,
2017-12-21 13:31:37: F_VERIFYBAK: #fota.bin verify ERROR ((f1c9645dbc14efddc7d8a322685f26eb != Hello,))!

I've assume that backup should be OK. "HELLO" do not look like MD5. Is it correct assumption ?

Bodziak
The Following User Says Thank You to bodziak For This Useful Post: [ View ] Gift bodziak Ad-Free
 
 
21st December 2017, 01:49 PM |#22  
steadfasterX's Avatar
OP Recognized Developer
Thanks Meter: 10,976
 
Donate to Me
More
Quote:
Originally Posted by bodziak

Hi,

I did backup yesterday when on ROM v20G..SALT detected that device is MD5 capable. I run verification there was only one error on userdata partition, and 8 warnings. today I'm on v29a and i did backup again and MD5 verification and i got 51 errors. there is something strange in log as well see bellow

2017-12-21 13:31:37: F_VERIFYBAK: vfilerem: fota, REMFILE: Hello,
2017-12-21 13:31:37: F_VERIFYBAK: #fota.bin verify ERROR ((f1c9645dbc14efddc7d8a322685f26eb != Hello,))!

I've assume that backup should be OK. "HELLO" do not look like MD5. Is it correct assumption ?

Bodziak

Ah yes. fixed. Unfortunately v29 seems to not support the md5sum cmd anymore ...
Please update SALT and try again. you should get no offer regarding verification now. Can you confirm this for v1.2-4 ?

thx
23rd December 2017, 03:44 PM |#23  
Senior Member
Thanks Meter: 1,037
 
More
Rooted, locked H812 with 5.1 not connecting in download mode (confirmed) in SALT in FWUL (forgetful), either in VM or direct boot from USB.

I know the H812 has presented problems connecting in download mode (as discussed in [! DISCONTINUED !] [TUTORIAL][LOCKED][UNLOCKED][ANY G4] DLM Backup with ReeS86 in post #23 proving to be very restrictive.

Is there any workaround in SALT available? Any suggestions appreciated, steadfasterX.

Thanks,
S.
23rd December 2017, 06:13 PM |#24  
ReeS86's Avatar
Senior Member
Flag Kitchener ON
Thanks Meter: 92
 
More
I can give it a shot later today when I can escape from some last minute Xmas shopping to see if I experience the same issues
The Following 2 Users Say Thank You to ReeS86 For This Useful Post: [ View ] Gift ReeS86 Ad-Free
23rd December 2017, 07:29 PM |#25  
Junior Member
Thanks Meter: 0
 
More
Hello,
I have a couple of questions.
First, how can I backup my /data/ partition on an unrooted device? I don't see it listed in the partitions.
Secondly, how can I wipe the dalvik cache with the shell?
Many thanks in advance!
23rd December 2017, 08:52 PM |#26  
steadfasterX's Avatar
OP Recognized Developer
Thanks Meter: 10,976
 
Donate to Me
More
Quote:
Originally Posted by sdembiske

Rooted, locked H812 with 5.1 not connecting in download mode (confirmed) in SALT in FWUL (forgetful), either in VM or direct boot from USB.

I know the H812 has presented problems connecting in download mode (as discussed in [! DISCONTINUED !] [TUTORIAL][LOCKED][UNLOCKED][ANY G4] DLM Backup with ReeS86 in post #23 proving to be very restrictive.

Is there any workaround in SALT available? Any suggestions appreciated, steadfasterX.

Thanks,
S.

Hm this should have been fixed already..

Connect device download mode in FWUL and open a terminal. gimme the output of

lsusb

Then also start SALT from within a terminal and copy and paste the output from the terminal plus: in SALT open the advanced menu and there the debug log. Paste the output from here as well.



Quote:
Originally Posted by ReeS86

I can give it a shot later today when I can escape from some last minute Xmas shopping to see if I experience the same issues

Pls do the same as written above for sdembiske then.

Quote:
Originally Posted by satiricon22

Hello,
I have a couple of questions.
First, how can I backup my /data/ partition on an unrooted device? I don't see it listed in the partitions.
Secondly, how can I wipe the dalvik cache with the shell?
Many thanks in advance!

Click backup. Choose FULL.

what's the output of

ls -la /data ?

Usually just selecting the text in the shell will copy automatically.




Sent from my LG-H815 using XDA Labs
The Following 2 Users Say Thank You to steadfasterX For This Useful Post: [ View ]
23rd December 2017, 11:44 PM |#27  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by steadfasterX

Hm this should have been fixed already..

Connect device download mode in FWUL and open a terminal. gimme the output of

lsusb

Then also start SALT from within a terminal and copy and paste the output from the terminal plus: in SALT open the advanced menu and there the debug log. Paste the output from here as well.





Pls do the same as written above for sdembiske then.



Click backup. Choose FULL.

what's the output of

ls -la /data ?

Usually just selecting the text in the shell will copy automatically.




Sent from my LG-H815 using XDA Labs

I'll try a full backup overnight, but I worry that /data won't be there since it's not listed.

When I type ls -la /data I get:
drwxrwx--- system system 2015-01-01 00:00 fota

Thanks for your help!
24th December 2017, 12:51 AM |#28  
Senior Member
Thanks Meter: 1,037
 
More
Quote:
Originally Posted by steadfasterX

Hm this should have been fixed already..

Connect device download mode in FWUL and open a terminal. gimme the output of

lsusb

Then also start SALT from within a terminal and copy and paste the output from the terminal plus: in SALT open the advanced menu and there the debug log. Paste the output from here as well.

Sent from my LG-H815 using XDA Labs

lsusb output in DLM in FWUL:

[[email protected] Desktop]$ lsusb
Bus 001 Device 009: ID 1004:633e LG Electronics, Inc. G2/G3 Android Phone [MTP/PTP/Download mode]
Bus 001 Device 006: ID 05dc:a815 Lexar Media, Inc. JumpDrive V10
Bus 001 Device 004: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 413c:2010 Dell Computer Corp. Keyboard
Bus 004 Device 002: ID 413c:1003 Dell Computer Corp. Keyboard Hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[[email protected] Desktop]$

lsusb in SALT:

[[email protected] SALT]$ lsusb
Bus 001 Device 009: ID 1004:633e LG Electronics, Inc. G2/G3 Android Phone [MTP/PTP/Download mode]
Bus 001 Device 006: ID 05dc:a815 Lexar Media, Inc. JumpDrive V10
Bus 001 Device 004: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 413c:2010 Dell Computer Corp. Keyboard
Bus 004 Device 002: ID 413c:1003 Dell Computer Corp. Keyboard Hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[[email protected] SALT]$

SALT debug log:

2017-12-23 16:47:49: Starting SALT v1.1-5:STABLE!
************************************************** **

2017-12-23 16:47:49: F_EGO: started
2017-12-23 16:47:49: F_EGO: /tmp/salt.lock created
2017-12-23 16:47:49: First start of SALT? Expected LG LAF NG here: /root/programs/lglafng
2017-12-23 16:47:49: F_MSG: started
2017-12-23 16:47:54:
First start of SALT?

Expected <b><u>lglaf</u></b> here:
/root/programs/lglafng

but it is missing..

Should I download it for you now?
2017-12-23 16:47:54: F_MSG: ended
2017-12-23 16:47:59: First start of SALT? Expected kdztools here: /root/programs/kdztools
2017-12-23 16:47:59: F_MSG: started
2017-12-23 16:48:02:
First start of SALT?

Expected <b><u>kdztools</u></b> here:
/root/programs/kdztools

but it is missing..

Should I download it for you now?
2017-12-23 16:48:02: F_MSG: ended
2017-12-23 16:48:05: DEVCON before: 99
2017-12-23 16:48:05: F_CHKDEVCON: started
2017-12-23 16:48:05: F_MSG: started
2017-12-23 16:48:15: NO DEVICE CONNECTED?
If you have connected your device ensure that it is in DOWNLOAD mode
(<u>not</u> fastboot, <u>not</u> recovery, <u>not</u> booted Android)
2017-12-23 16:48:15: F_MSG: ended
2017-12-23 16:48:15: F_CHKDEVCON: msge result = 0
2017-12-23 16:48:15: RET: 0
2017-12-23 16:48:15: DEVCON after: 0
2017-12-23 16:48:15: F_GETINFO: started
2017-12-23 16:48:15: F_CDARB: started
2017-12-23 16:48:16: EMPTY ARB DETECTED:

2017-12-23 16:48:16: Please send this log and the SBL1 dump in /tmp/sbl1.err
2017-12-23 16:48:16: F_CDARB:
2017-12-23 16:48:16: F_CDARB: DEVARB=0, DEVARBEMPTY=1
2017-12-23 16:48:16: F_CDARB: ended
2017-12-23 16:48:16: F_GETINFO: ended
2017-12-23 16:48:16: parsing arb:0:1
2017-12-23 16:48:40: F_ADVMENU: started
2017-12-23 16:48:43: getlog script started

Thanks,
S.
The Following User Says Thank You to sdembiske For This Useful Post: [ View ] Gift sdembiske Ad-Free
24th December 2017, 08:17 AM |#29  
steadfasterX's Avatar
OP Recognized Developer
Thanks Meter: 10,976
 
Donate to Me
More
Quote:
Originally Posted by satiricon22

I'll try a full backup overnight, but I worry that /data won't be there since it's not listed.

When I type ls -la /data I get:
drwxrwx--- system system 2015-01-01 00:00 fota

Thanks for your help!

there is no "data" partition. The partition is named userdata and gets mounted to the directory /data. I think that's why you get confused.
The full backup will contain userdata partition which is what you need.

In the SALT shell type:
mount -t ext4 /dev/block/bootdevice/by-name/userdata /data
and:
ls -la /data
rm -rf /data/dalvik-cache
ls -la /data



Quote:
Originally Posted by sdembiske

lsusb output in DLM in FWUL:
.......
Thanks,
S.

Thx but one thing is missing:

Start SALT from the terminal in FWUL by:

sudo ./salt

I need the output from the terminal (only that)



Sent from my LG-H815 using XDA Labs
24th December 2017, 02:35 PM |#30  
Senior Member
Thanks Meter: 1,037
 
More
Quote:
Originally Posted by steadfasterX


Thx but one thing is missing:

Start SALT from the terminal in FWUL by:

sudo ./salt

I need the output from the terminal (only that)

Sent from my LG-H815 using XDA Labs

Here you go:

[[email protected] SALT]$ sudo ./salt
[sudo] password for android:

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:24:64: Using one color stop with linear-gradient() is deprecated.

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:58:64: Using one color stop with linear-gradient() is deprecated.

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:2523:75: Using one color stop with linear-gradient() is deprecated.

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:2882:24: '0' is not a valid color name

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3602:8: Junk at end of value for background-image

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3711:68: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3727:74: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3743:74: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3759:80: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3775:80: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3791:80: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3806:64: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3821:70: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3836:70: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3851:76: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3866:76: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3881:76: Expected ')' at end of '-gtk-scaled'

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:4729:73: Using one color stop with linear-gradient() is deprecated.

(yad:1865): Gtk-WARNING **: Theme parsing error: gtk-contained.css:4741:87: Using one color stop with linear-gradient() is deprecated.

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:24:64: Using one color stop with linear-gradient() is deprecated.

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:58:64: Using one color stop with linear-gradient() is deprecated.

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:2523:75: Using one color stop with linear-gradient() is deprecated.

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:2882:24: '0' is not a valid color name

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3602:8: Junk at end of value for background-image

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3711:68: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3727:74: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3743:74: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3759:80: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3775:80: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3791:80: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3806:64: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3821:70: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3836:70: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3851:76: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3866:76: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3881:76: Expected ')' at end of '-gtk-scaled'

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:4729:73: Using one color stop with linear-gradient() is deprecated.

(yad:1910): Gtk-WARNING **: Theme parsing error: gtk-contained.css:4741:87: Using one color stop with linear-gradient() is deprecated.
2017-12-24 06:55:30,217 partitions: INFO: Wrote 1048576 bytes to -
2017-12-24 06:55:31: parsing arb:0:0
2017-12-24 06:55:31: parsing battery_level:89
2017-12-24 06:55:31: parsing device_sw_version:H81210n
2017-12-24 06:55:31: parsing secure_device:S
2017-12-24 06:55:31: parsing device_factory_version:LGH812AT-01-V10n-302-720-DEC-04-2015+0
2017-12-24 06:55:31: parsing model_name:LG-H812
2017-12-24 06:55:31: parsing target_country:CA

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:24:64: Using one color stop with linear-gradient() is deprecated.

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:58:64: Using one color stop with linear-gradient() is deprecated.

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:2523:75: Using one color stop with linear-gradient() is deprecated.

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:2882:24: '0' is not a valid color name

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3602:8: Junk at end of value for background-image

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3711:68: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3727:74: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3743:74: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3759:80: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3775:80: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3791:80: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3806:64: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3821:70: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3836:70: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3851:76: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3866:76: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:3881:76: Expected ')' at end of '-gtk-scaled'

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:4729:73: Using one color stop with linear-gradient() is deprecated.

(yad:1969): Gtk-WARNING **: Theme parsing error: gtk-contained.css:4741:87: Using one color stop with linear-gradient() is deprecated.
2017-12-24 06:55:58: EXIT: main->end with code 0
[[email protected] SALT]$ lsusb
Bus 001 Device 009: ID 1004:633e LG Electronics, Inc. G2/G3 Android Phone [MTP/PTP/Download mode]
Bus 001 Device 006: ID 05dc:a815 Lexar Media, Inc. JumpDrive V10
Bus 001 Device 004: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 413c:2010 Dell Computer Corp. Keyboard
Bus 004 Device 002: ID 413c:1003 Dell Computer Corp. Keyboard Hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[[email protected] SALT]$

Thanks again,
S

Addendum:

This time it seemed to work, using the terminal command sudo ./salt within the desktop SALT folder. When I realized this, I right clicked on the SALT icon in the desktop SALT folder and it brought up the menu with the device info listed and no connection error. Starting a full backup now ...

Thanks,
S.
The Following User Says Thank You to sdembiske For This Useful Post: [ View ] Gift sdembiske Ad-Free
24th December 2017, 03:52 PM |#31  
steadfasterX's Avatar
OP Recognized Developer
Thanks Meter: 10,976
 
Donate to Me
More
Quote:
Originally Posted by sdembiske

Here you go:

[[email protected] SALT]$ sudo ./salt
[sudo] password for android:

....

Addendum:

This time it seemed to work, using the terminal command sudo ./salt within the desktop SALT folder. When I realized this, I right clicked on the SALT icon in the desktop SALT folder and it brought up the menu with the device info listed and no connection error. Starting a full backup now ...

Thanks,
Steve

Well. Sometimes the download mode needs some time to be fully loaded. Give it at least 30 sec after you see the cycling arrow screen and if it does not work on the first try just try it again after another 30 sec.

I'm glad it works for you now. Restricted download modes should be no prob anymore for SALT - at least not for the backup part.



Sent from my LG-H815 using XDA Labs
The Following User Says Thank You to steadfasterX For This Useful Post: [ View ]
Post Reply Subscribe to Thread

Tags
backup, kdz, lglaf, lgup, restore

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes