yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] pocepoke:
result :

sudo: lshw: command not found

icant use persistent mode ..... always ending in command prompt and i dont know what to do next

im traying using another way but still tought by u

https://xdaforums.com/g4/help/tutorial-backup-download-mode-t3659223

result :

git clone https://github.com/steadfasterX/lglaf.git

Cloning into 'lglaf'...

remote: Counting objects: 501, done.

remote: Compressing objects: 100% (6/6), done.

remote: Total 501 (delta 4), reused 7 (delta 3), pack-reused 492

Receiving objects: 100% (501/501), 159.22 KiB | 308.00 KiB/s, done.

Resolving deltas: 100% (297/297), done.

[android@fwul ~]$ cd lglaf

[android@fwul lglaf]$ sudo python2 auth.py

[sudo] password for android:

Challenge: 67:45:8b:6b

Response: f7:ee:f3:01:bd:0a:2d:1d:93:98:93:47:75:cf:88:ea

Traceback (most recent call last):

File "auth.py", line 73, in <module>

main()

File "auth.py", line 66, in main

do_challenge_response(comm)

File "auth.py", line 57, in do_challenge_response

metr_header, metr_response = comm.call(request_kilo_metr)

File "/home/android/lglaf/lglaf.py", line 269, in call

raise RuntimeError('Command failed with error code %#x (%s)' % (errCode, msg))

RuntimeError: Command failed with error code 0x80000001 (LAF_ERROR_INVALID_PARAMETER)

but still go run backup and stuck again in

2018-05-04 09:54:42,404 extract-partitions: INFO: Dumping partition /dev/mmcblk0p53 (system) to /run/media/android/Win/G4/ori/full/system.bin (4747952128 bytes)

[ 39 % ] (1814523 / 4636672 KB)

same partition that stuck when using SALT

...... back to windows again and mybe if i read more of your guide i will find some clue :D
[Android Software/Hacking General [Developers Only]] steadfasterX:
sorry my fault:

lspci | grep -i vga
[Android Software/Hacking General [Developers Only]] Dr. Bubbler:
More SALTy problems
[Android Software/Hacking General [Developers Only]] pocepoke:
i think my vga is geforce GTX680 .....

this command is for showing vga card yes? and detect it as gf gtx680

with last install FWUL on usbdisk 32gb the persisitent mode running fine

i update the SALT, same stuck at downloading mmclbk53 (system)

so i tried update all on FWUL, after finish and restart my keybord and mouse cannot use ...... (its fine on windows or before update FWUL) and i had to build usbdisk FWUL again

right know im trying use short (15cm) usb cable ...... mybe that will minimize data lost

last night when update FWUL it takes a very long time mybe an hour or more .......

start again ...... mybe my disk as ide will finish the backup all the last using ahci

couple hours after im trying ....

i install FWUL persistent on 128gb ssd try to update but to slow .... more 3hours only got 60mb file from 500mb all (my internet speed unlock speed variatve depend load on my country the limited is my mikrotik 100Mbps port

so i cancel it and update only SALT, still doent work always stuck at same point partition mmcblk0p53 (system) same backup stuck at 1.9gb file

even using development mode still same,

is the mmcblk0p53 can i bypass backup (mybe using another from stock file)

becouse i want to use usu to unlock and have TWRP / ROOT, is it still save to flash TWRP ?

i forget to mention it the firmware is LOLIPOP (LP) (5.1) mybe becose of that system.img cant be backup by SALT ?

thxs
[Android Software/Hacking General [Developers Only]] steadfasterX:
according to your paste (https://bpaste.net/show/33d281632352) the problem is that you have not enough space left on the device

OSError: [Errno 28] No space left on device

Best is to mount your Windows drive as described here:

FAQ #5) How can I access my Windows drives/partitions in FWUL?

After you mounted your windows drive you need to select that windows folder as the target folder.

Glad the latest nightly is working for you! Yes that command was to find out the graphic card.

as mentioned multiple times:

SHARE THE LOG

. The FAQ 1000 tells you how - even with a picture guide

But for a regular backup: use BASIC mode which is mentioned in the UsU thread as "enough". You dont need the system backup and the userdata is even bigger which you better backup otherwise (e.g. with Titanium backup or any other backup app)

The reasons for stalled backups are

1) not enough space on the target folder

2) timeouts which you cannot solve as they are related to the firmware

I can't say what of the above is the reason for you as you dont share the log.

Doing a basic backup should always work.

.
[Android Software/Hacking General [Developers Only]] pocepoke:
sorry im forgetfull :silly:

here is the log on attachment

so i need to MM for USU to get TWRP right?

sorry to ask again, is any best choice to get safest ROM update to MM .... becouse the diffrent board original is 810 but rom using 811 make me scare to upgrade :D
[Android Software/Hacking General [Developers Only]] pocepoke:
update:

aleast i got guts to using UsU and it success now my G4 is unlock

and i can install any roms that suitable

thx's alot for the great SALT and FWUL ...... big thanks for [MENTION=5545101]steadfasterX[/MENTION] :good:
[Android Software/Hacking General [Developers Only]] steadfasterX:
SALT update

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

Due to the recurring amount of stalled backups I added the long awaited (by me) pre-check of free disk space.

When the choosen target folder has not enough free disk space SALT will now show an error and ask for a different one.

v3.16

Released: 2018-05-06

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

Summary changelog:

New(SALT): Improved backup / Free disk space check
[Android Software/Hacking General [Developers Only]] fil3s:
Did you manage to solve the corrupted install that we spoke about (possibly caused by my flashing usu with wrong FWUL version) ?

Sorry, had to ask. Thx!
[Android Software/Hacking General [Developers Only]] steadfasterX:
Can't remember your issue but I guess that was long time ago.

.. and SALT had a lot of fixes regarding flashing issues so I guess yes.
[Android Software/Hacking General [Developers Only]] pocepoke:
yes, after this update i know that the salt backup needs around same size with MMC of your device

thats way i always failed on system.img

[MENTION=5545101]steadfasterX[/MENTION] big thanks for the help, u save me the hazzle :victory:

i fastboot flash again aboot raw_resources laf original from backup of my devices becouse lgflashtool refuse to flash if had UsU root twrrp

and i flash using lgflashtool image at&t LGH810AT-00-V10o-ATT-US-SEP-10-2015-ARB02+0_User_Secure.tot

now working fine and i UsU again to get twrp ,root and Xposed

i wanna use your rom but still confuse what to chose is H810 or H811 roms the partition table is H811

my be some other time i got time to flash again ..... its my daily phone

:highfive:
[Android Software/Hacking General [Developers Only]] sdembiske:
Refer to post # 947 in the UsU thread, in particular: How to remove the Assert line - see if that helps.

Removing the assert line is recommended in the OP in the UsU thread when installing custom roms not designed for your specific model version, as long as the GPT compatability is a match.
[Android Software/Hacking General [Developers Only]] steadfasterX:
when u flash the 30 GB persistent FWUL version on a 100000 GB disk you will just have 30 GB available in FWUL.

Thats the way it works.
[Android Software/Hacking General [Developers Only]] pocepoke:
same like xiomi, sometime in their roms (zip) they forget to edit the assert code.

so get error 7 in twrp

u never know if there no space left until SALT latest update until then just stuck at backup process

i mount ssd 128gb still stuck, after update i know that free space only 24gb

the backup is mean to FULL bacup BASIC only 4-5gb

but remember SALT FULL backup size around size of your MMC mine is 32gb
[Android Software/Hacking General [Developers Only]] kim12355:
can h818p can unlock?

it still have touch issue?
[Android Software/Hacking General [Developers Only]] Dr. Bubbler:
OK. The FWUL home folder properties say 0 bytes of 12.5 GB free. Where is the rest if the space and can I access it to save my backup?
[Android Software/Hacking General [Developers Only]] fil3s:
This might be a stupid question, but how do I restore a back up?
[Android Software/Hacking General [Developers Only]] steadfasterX:
You would need to repartition the disk after flashing FWUL..

fastboot for unlocked devices. (officially or by UsU)

Waiting for SALT v4 for locked ones.
[Android Software/Hacking General [Developers Only]] fil3s:
What command do I run? Thx

Edit, ahh i gotcha. U mean "officially unlocked devices". ;) :highfive:

Thx for clarification. Cheers! ?
[Android Software/Hacking General [Developers Only]] steadfasterX:
Nope for official unlocked and UsU'd fastboot will do.

Just check the faq in the UsU thread to find examples how to use and flash fastboot.
[Android Software/Hacking General [Developers Only]] fil3s:
I see.. Did not see SALT related restore method - BUT - I did notice fastboot commands. :D many thanks to you and giving us years more use out of our G4's !! :D

Lg gave me two system updates

**** that! :D :good:
[Android Software/Hacking General [Developers Only]] nummer:
I have came across a problem...

It appears that gksu has been removed from ubuntu repos and i can't use it anymore, therefore i cant use SALT... What can i do??? [MENTION=5545101]steadfasterX[/MENTION]
[Android Software/Hacking General [Developers Only]] grantdb:
sudo ~/SALT/salt
[Android Software/Hacking General [Developers Only]] steadfasterX:
Actually you even do not need sudo before. :)

You can just start

./salt

After changing into the SALT install dir. It will auto sudo ;)

[MENTION=7673578]NummerEinsNerd[/MENTION]

I will add a more general solution in a future SALT release as gksu has been completely removed everywhere without a proper replacement unfortunately.

You can also edit the desktop shortcut:

Set terminal=true

Replace "gksu" with"sudo"

This will open a terminal when double click the desktop icon where you type the pass to start SALT. The terminal will stay open afterwards so it's not a very beautiful solution just a workaround.
[Android Software/Hacking General [Developers Only]] rojanor:
just a few questions about salt backup

Hi, i have just done a full backup with salt, does this mean that i can reverse whatever i do to my untouched phone from now on by restoring the full backup i just made?

I noticed that the partition userdata.bin is rather large, is it ok to delete this partition from my backup, or would i at some point later regret i did it you think? (on a factory reset phone..)

After doing the backup i got a bunch of files.bin, do i have to do something to make them restorable, or do i just flash them one by one as they are with fastboot or twrp?

Awesome work, btw :)
[Android Software/Hacking General [Developers Only]] Rosostolato:
Missing fastboot

What is this fastboot? I didn't see anything about it on tutorials

[IMG="Error"]https://imageshack.com/a/img921/8475/5ZjlJW.png[/IMG]
[Android Software/Hacking General [Developers Only]] grantdb:
It says right in that screen capture, check UsU thread for example of usage.
[Android Software/Hacking General [Developers Only]] Rosostolato:
Does FWUL come ready to use? I just want to use SALT to unlock my lg g4
[Android Software/Hacking General [Developers Only]] grantdb:
Read the OP again bro
[Android Software/Hacking General [Developers Only]] steadfasterX:
The backups are raw disk images. Nothing is needed to restore them. Just flash in fastboot or TWRP or wait for SALT v4.

Userdata contains all your internal storage. TWRP excluded the internal storage so if you really want to have a 1:1 copy of your current phone SALT is the best option. If you delete userdata from your backup it would be like a factory reset on android so if that is ok for you delete it. You can also consider to compress all backup files with 7zip which decreases the size a lot btw.
[Android Software/Hacking General [Developers Only]] dharakv:
Full backup stuck?

I've been running the full backup for 8 hours and for over the past hour, it has been stuck on /dev/mmcblk0p55 (userdata) even though the progress bar is fully green..

Should I maybe force close it and check, or would that risk losing some of my data?

Logs:

http://bpaste.net/show/d875784eda05

Update: Appears to be stuck at the same point.... I tried to mount the userdata partition but it failed. Here's the log for that:

<a href="http://bpaste.net/show/d875784eda05">http://bpaste.net/show/d875784eda05</a>

2018-05-27 12:45:59: 0

2018-05-27 13:36:39: F_ADVMENU: started

2018-05-27 13:36:43: F_MOUNTPARTS: started

2018-05-27 13:37:26: returned: /run/media/android/72C9-FE71/userdata.bin|/mnt/salt_mnt|

2018-05-27 13:37:26: IMGFILE = /run/media/android/72C9-FE71/userdata.bin, MNTPNT = /mnt/salt_mnt

2018-05-27 13:37:26: F_MOUNTIMG: started with /run/media/android/72C9-FE71/userdata.bin

2018-05-27 13:37:26: F_MOUNTIMG: mountpoint /mnt/salt_mnt does not exits.. will be created now!

2018-05-27 13:37:32: F_MSGE: started

2018-05-27 13:37:39: ERROR: system image could not be mounted to /mnt/salt_mnt.

Check SALT logfile!

2018-05-27 13:37:39: 0

2018-05-27 13:37:39: F_MOUNTIMG ended

2018-05-27 13:37:41: getlog script started

2018-05-27 13:41:02: getlog script started
[Android Software/Hacking General [Developers Only]] sdembiske:
Refer to post # 1587 in the Canadian H812 guide - suspect that's the issue you may have run into.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Unfortunately some firmware versions produces timeouts when backing up large partitions and that happens to you.
[Android Software/Hacking General [Developers Only]] dharakv:
[MENTION=6302635]sdembiske[/MENTION] [MENTION=5545101]steadfasterX[/MENTION]

First off, I thank you for all your support. If it wasn't for you, I'd be lost here..

I went forth with the Virtual Box installation outlined from sdembiske's guide(https://xdaforums.com/showpost.php?p=75389990&postcount=483). FWUL installed beautifully, detected all peripherals. However, SALT on the other hand, does not detect the phone specifically, even with VirtualBox USB driver, LG Universal Driver, and VirtualBox Extension Pack installed.

I'm thinking of repeating the same process within VMware, however I cannot find a way to convert an img file to .vmdk format... Is there a persistant 30GB iso file for FWUL? I went ahead and created a forgetful VM in VMware, and SALT can detect the phone...

If not, I have an Ubuntu VMware VM, I'll install SALT there and try it.
[Android Software/Hacking General [Developers Only]] sdembiske:
Hold off on VMware install - it's not supported and won't be troubleshooted by steadfasterX.

Instead ...

Refer to post # 529 in the FWUL thread - it's a bit of a checklist I have to run through sometimes myself when I'm having trouble connecting. See if it helps.
[Android Software/Hacking General [Developers Only]] dharakv:
Thanks. SALT detected it and a backup's running :good:

Update: SALT froze and crashed, again back to square one... not detecting the USB...

For some reason, when I set the destination as the shared folder, the progress bar just skips to 100%. Same thing happens when I try to backup to a 1TB external HDD.....

I formatted my 128GB flash drive, and when I set that as the backup destination, it always seems to crash when in the userdata partition..
[Android Software/Hacking General [Developers Only]] dharakv:
Ok. Is there anyway to overcome it? I noticed the timeout is different depending on what I backup to. Timeout is very early when I backup to my HDD or external HDD
[Android Software/Hacking General [Developers Only]] sdembiske:
You have to make a specific folder for the backup, for example, salt_backup_full (no spaces, using underscrore instead) in your shared folder (making sure it is shared, of course) and direct your backup to it. Ensure you have at least 33GB free on your hard drive for the full backup.

You can also, if you prefer, make your flash drive shared (refer to post # 490) and create the specific backup folder there. Double check your USB setting and make sure it is checked for your LG device again - that one has to be done every time, not the usb 3.0 setting as it should carry forward once it is set once.
[Android Software/Hacking General [Developers Only]] steadfasterX:
A too fast run indicates another issue. Share the log again. Always share logs when having issues.
[Android Software/Hacking General [Developers Only]] Ceezar:
Still no method of unlocking a nougat bootloader?
[Android Software/Hacking General [Developers Only]] dharakv:
Thanks. I forgot about that part. I made a folder inside the shared folder and tried it. First time it got stuck on System partition, second time it went through perfectly. Now let's hope it goes through userdata without issues :)

One thing I noticed was: if your backup fails, you can just re run the backup into the same folder. SALT won't overwrite the previously backed up partitions, it will just continue onwards from the partition it failed...
[Android Software/Hacking General [Developers Only]] dharakv:
http://bpaste.net/show/b6cef0556ce5.

It froze and crashed at the 4.5GB mark of the userdata partition.
[Android Software/Hacking General [Developers Only]] sdembiske:
I may be off base here, but one thing I would think to try would be to disable your internet connection and virus protection on your PC/laptop while the backup is running and not do anything else on the PC/laptop while the backup is running - I'm thinking something is slowing the PC/laptop down or freezing it and/or interfering with it while the backup is running ... if it happens again, see what task manager shows what other processes may be interfering/taking up too much CPU.
[Android Software/Hacking General [Developers Only]] dharakv:
Well, I ran it prior to reading this and I had some major luck on my side. The backup completed! Userdata partition image is about 24.9GB and I got the message "All finished".

I normally have low CPU usage and very minimal number of services runnig on idle. My CPU usage is around 1% on idle. Having run VMs in the past.. ive learned the hard way the importance of closing RAM intensive applications (including Chrome).

Thanks ! Now lets see if I can mount the bin file and access my data (Right now I'm making copies of the userdata.bin just in case). Do you normally mount the bin file within SALT or do you use PowerISO ?

Update: Can't seem to mount it in either...

Also, the size of it in Windows is only 23.2GB...
[Android Software/Hacking General [Developers Only]] steadfasterX:
Mount it in SALT. Advanced menu.

If it doesn't mount share the log.
[Android Software/Hacking General [Developers Only]] dharakv:
Mounting Logs: https://bpaste.net/show/3e6a2662e487

Also, could the userdata.bin be corrupted because it shows 2 different sizes in Windows and FWUL...

Thanks a ton.
[Android Software/Hacking General [Developers Only]] steadfasterX:
it looks like being corrupted yes.

try this in FWUL:

sudo mkdir /mnt/data
file /media/sf_vbox_shared/salt/userdata.bin
sudo fsck.ext4 -f -p /media/sf_vbox_shared/salt/userdata.bin
sudo mount -t ext4 /media/sf_vbox_shared/salt/userdata.bin /mnt/data

paste all the output of the above (here when not more then a couple of lines else to http://bpaste.net )
[Android Software/Hacking General [Developers Only]] dharakv:
Thanks, I will do it when I get home.. If the file is corrupted, is there a way to correct it rather tham running the backup again?
[Android Software/Hacking General [Developers Only]] steadfasterX:
thats what the fsck.ext4 command tries to do..
[Android Software/Hacking General [Developers Only]] dharakv:
Ah ok.. didnt see that command there.. sorry about that. I'll update you in maybe 8hours or so.

Have a good day.
[Android Software/Hacking General [Developers Only]] dharakv:
https://bpaste.net/show/9621c4fda8b7

There was also some lines that say IGNORED instead of FIXED. Unfortunately, the terminal emulator doesnt give all the lines... some got overwrote...
[Android Software/Hacking General [Developers Only]] steadfasterX:
Ok so unfortunately the backup is broken and can't be fixed easily..

Best would be to do the backup of userdata again. Fastest way is to rename/move the current userdata file in the backup folder and when doing the backup again pointing to that same directory of your previous backup.

This way only userdata will be backuped as SALT skip partitions when they can be found in the target folder.

There is a way to recover the data from corrupted image files but it's easier to re-do the backup tbh..

EDIT:

I forgot one thing which is quite new in FWUL. Depending on what you want to recover there is a new easier way:

If you use the latest nightly from my leech server there is a tool named photorec pre-installed (you should find it on the desktop or in the menu). This is a GUI tool for recovering several types of files (not just photos) from e.g. a corrupted image like yours.

Give that a go! Just select the userdata image file as the source and choose the types you wanna recover. Can take a long time ofc but if something can be recovered from that corrupt userdata this tool will find it.
[Android Software/Hacking General [Developers Only]] dharakv:
[MENTION=5545101]steadfasterX[/MENTION] [MENTION=6302635]sdembiske[/MENTION]

So what I ended up doing was re-flashing the phone with LG FLASH TOOL 2014 in Normal Mode. It only wrote the System partition so my data and apps were still there. All I lost was root. I learned my lesson the hard way.. always backup before making any root-level changes to the phone... and have a custom recovery.

I thank you both for all your help and support. Canadian LG G4 users are lucky to have hardworking and dedicated developers such as you both.

Just out of curiosity, I tried to mount the other bin files as well using both SALT and PowerISO, but they all failed except for modem(only mounted in PowerISO). I'm going to root again, and install TWRP-IN-FISH just in case I screw up something bigger later on. I'm sure there's other partitions which when tampered, can really screw the phone up. I won't be bootloader unlocking anytime soon because SALT hates my phone :(

Of course the bootloader unlock and actual TWRP would be the better option, however, aside from flashing custom ROMs, all the other functionality of TWRP can be done with TWRP-IN-FISH, right?
[Android Software/Hacking General [Developers Only]] sdembiske:
Glad you got recovered. You should still try and run a SALT backup in my opinion on your recovered phone now to see if it goes through fully. The problem is that you may still have a corrupted data partition and should find out where the problem is - perhaps it was reflecting a system corruption ...

In addition to TWRP-IN-FiSH, install Titanium and back up your apps and system data. Don't use it to restore your apps, just to restore your data to your apps. ALSO, copy your SD card fully over to your PC/Laptop.

IMO, by choosing not to UsU unlock you are potentially compromising your phone down the road even more with not getting the latest android updates, leaving yourself open to even more potential corruption, security vulnerabilities, etc.
[Android Software/Hacking General [Developers Only]] dharakv:
So suppose some other partition becomes corrupt (modem for example)... can I simply flash the modem bin file from SALT through TWRP-IN-FISH?

I will definitely attempt another SALT backup just to see how it goes.
[Android Software/Hacking General [Developers Only]] sdembiske:
The latest TWRP has the ability to back-up one's Carrier and it looks like the ability has been incorporated in TWRP-in-FiSH as of the v5 (5.0) version dated 2017-12-19, so you could simply restore a clean prior backup of that partition.

IMO, you should seriously consider going the UsU unlock route at some point if you plan to continue using your LG G4 - your "stagefright" and other security vulnerability patches are way out of date currently ...