Fatal Error Missing Requirement yad Install Yad and Try Again

You are using an out of date browser. It may not brandish this or other websites correctly.
You lot should upgrade or employ an alternative browser.

• #821

Love steadfasterX,

I have no encrypted device, then I tried to switch to develop version of SALT, following your FAQ at point ten).

I've launched Common salt and washed the update (that seemed ok) and at the request to restart SALT I've obtained
a windows pop up saying "SALT 3.22.11 : TESTING – ERROR"
"ERROR: FATAL Mistake!! Missing requirement python cryptography module (Python3) Read the Salt thread for how to install and try again !"

After so It was impossible to start over again Table salt, so I have been constrained to flash once again FWUL (FWUL_v3.1_x86_64_8GB.nix)
over the USB pen-drive and I've tried again the same process , only plain the result was the same.

What did i get wrong?
Cheers for you lot support

you tin solve that by flashing mAid (fka equally FWUL) --> nightly. information technology has everything on lath already.
If you wanna do the same with FWUL three.1 pls do the following command in a terminal:
sudo pacman -Sy python-zstandard

but if the above does not solve the issue:
sudo pip3 install cryptography

if none of them solves the result, install the latest mAid nightly instead (see FWUL OP).

.-

• #822

Apathetic, bitten yet again by the LG G4 boot loop bug... This is the third time, yup... Though the outset 2 times taught me to backup regularly, I was a bit more than than 2 weeks out from my last backup on this newly failed G4 H811. And then I take now lost a series of important recordings, SMS text messages, and other information bits that accept accumulated over the last two weeks. Or take I? I am thinking of a scheme to potentially recover it before whatever physical intervention similar hot air reflowing, directed pressure level, or whatsoever. Here is my thought.

With the bootlooping G4 H811, I was able to get into Download mode, and backup all 56 partitions totaling well-nigh 29 GB total. And I have bachelor two more identical G4 H811s that are yet available and functioning (yep, what can I say--I am glutton for punishment...). So my idea was to write the 24 GB userdata partition that I salvaged from the now failed G4, and utilise TWRP to write it to the userdata partition of one of a functional G4.

If I were to do this, on booting the still functional G4, would I essentially exist able to grab the two weeks of important data I mentioned above?

I approximate I would besides clone over the arrangement sectionalization considering the G4s are running slightly different versions of steadfasterX's LOS16.

Any other salvaged partition images that I should clone over to the still functional G4 to make this all work?

Many thanks in advance for any guidance y'all might take!

• #823

With the bootlooping G4 H811, I was able to get into Download mode, and backup all 56 partitions totaling about 29 GB total. And I have bachelor 2 more identical G4 H811s that are yet available and functioning (yeah, what tin I say--I am glutton for penalization...). So my idea was to write the 24 GB userdata division that I salvaged from the at present failed G4, and utilize TWRP to write it to the userdata partition of one of a functional G4.

And so I've run across some hiccups in my potential strategy above, but I am hoping they are not insurmountable.

First issue was that my full userdata partition image made by Salt is nearly 24 GB in size as mentioned above. So information technology is as well large for a FAT32 filesystem on MicroSD or as mutual on most USB drives (which could exist accessed as OTG in TWRP). No problem, I simply prepared a spare MicroSD with an exFAT filesystem to deal with this. And so I went on my merry fashion to the still functional recipient G4 with this new MicroSD filled with boot, organization, and userdata images expecting to be able to flash them via TWRP. But alas, it seems TWRP simply allows flashing of boot and recovery partitions, not userdata. So even though I can access the 24 GB image under TWRP, in that location is no manner to flash it. I looked around TWRP for advanced options that might let me override this, but no luck.

Merely then it occurred to me I could just put the G4 into download/fastboot mode, and employ fastboot to wink over the 24 GB userdata partition. Seems logical--of form, I have used fastboot to wink smaller partition images like recovery on other systems, but I take never attempted to flash a huge, 24 GB like this. Any comments most this strategy earlier I give information technology a go?

BTW, I accept been able to mount the 24 GB userdata partition nether FWUL, and I can run into the whole contents no problem. So I could direct grab system-level data like SMS and my fitness tracker data (another important thing I forgot near!). I am not talking nigh ordinarily attainable user stuff nether the emulated IntSD user space storage like Downloads, DCIM, etc. Maybe this is a solution, but how would I restore this under a functional G4???

• #824

And then I've meet some hiccups in my potential strategy in a higher place, simply I am hoping they are not insurmountable.

First issue was that my full userdata division image made by Table salt is about 24 GB in size as mentioned above. So information technology is too large for a FAT32 filesystem on MicroSD or as mutual on most USB drives (which could be accessed as OTG in TWRP). No trouble, I just prepared a spare MicroSD with an exFAT filesystem to deal with this. And then I went on my merry way to the nevertheless functional recipient G4 with this new MicroSD filled with boot, system, and userdata images expecting to be able to flash them via TWRP. Simply alas, information technology seems TWRP only allows flashing of kick and recovery partitions, not userdata. So even though I can access the 24 GB image under TWRP, there is no style to flash it. I looked around TWRP for advanced options that might let me override this, but no luck.

Merely and then it occurred to me I could only put the G4 into download/fastboot style, and employ fastboot to flash over the 24 GB userdata partition. Seems logical--of form, I have used fastboot to flash smaller segmentation images similar recovery on other systems, just I have never attempted to flash a huge, 24 GB like this. Any comments nigh this strategy before I give it a go?

BTW, I have been able to mount the 24 GB userdata partitioning nether FWUL, and I tin see the whole contents no trouble. And then I could directly grab system-level data like SMS and my fitness tracker data (another of import thing I forgot well-nigh!). I am non talking near normally attainable user stuff under the emulated IntSD user space storage like Downloads, DCIM, etc. Maybe this is a solution, merely how would I restore this under a functional G4???

1. Right yous just need system, kick and userdata to "clone" your old device . Whatsoever other partition has the potential to brick your working phone

2. You Tin can use TWRP to do this merely you need a shell and use the dd command

3. fastboot is the easiest way and in that location is no size limit in pushing files at that place. Then give that a go for all the mentioned partitions of 1. Information technology should piece of work pretty fine.

Sent from my OnePlus 6T using XDA Labs

• #825

Thank you, steadfasterX, for the response!

I went into fastboot/bootloader fashion on the recipient G4, and using FWUL, attempted to flash these three partitions, merely ran into an error with each one at the end of each operation (run across beneath). The phone was definitely in the correct bootloader mode as it was recognized with the "fastboot devices" control as per below. I tried it with Windows version of fastboot after FWUL, but the same fault. And so close to potential victory, but non quite yet.

To brand the iii segmentation images with Common salt, I used the Backup pick which was pretty straightforward. And as mentioned previously, I was able to mountain the userdata partition image to browse information technology, and is contains seeming skillful data. Then I don't think the images are the trouble.

I must exist missing something...

                              [[email protected] ttt]$ fastboot devices 61b3114b	fastboot [[email protected] ttt]$ fastboot flash kicking kick.img target reported max download size of 536870912 bytes Sending 'boot' (40960 KB)... OKAY [  1.334s] Writing 'boot'... FAILED (remote: unknown control) Finished. Full time: 1.440s [[email protected] ttt]$ fastboot flash system system.img target reported max download size of 536870912 bytes Invalid sparse file format at header magic Erasing 'system'... FAILED (remote: unknown command) Finished. Total time: 4.809s [[e-mail protected] ttt]$ fastboot flash userdata userdata.img target reported max download size of 536870912 bytes Invalid sparse file format at header magic Erasing 'userdata'... FAILED (remote: unknown command) Finished. Full time: 26.277s [[e-mail protected] ttt]$                            

• #826

Thank you, steadfasterX, for the response!

I went into fastboot/bootloader manner on the recipient G4, and using FWUL, attempted to flash these three partitions, but ran into an error with each 1 at the end of each operation (meet below). The telephone was definitely in the correct bootloader mode equally information technology was recognized with the "fastboot devices" control as per below. I tried it with Windows version of fastboot after FWUL, but the aforementioned error. Then close to potential victory, but not quite still.

To make the iii partition images with SALT, I used the Backup option which was pretty straightforward. And equally mentioned previously, I was able to mount the userdata sectionalisation epitome to browse it, and is contains seeming good data. So I don't call up the images are the trouble.

I must be missing something...

Ok your fastboot mode is pretty limited , say thx to tmo. Anyways just switch to TWRP and so and assuming you have all 3 partitions directly on your external sdcard these are the cmds to flash them:

adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-proper noun/boot
sync
dd if=/external_sd/system.img of=/dev/block/bootdevice/past-proper name/system bs=512
sync
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-proper noun/userdata bs=1024
sync

Later on that reboot and it should be fine.

Sent from my OnePlus 6T using XDA Labs

• #827

Ok your fastboot mode is pretty limited , say thx to tmo. Anyways just switch to TWRP then and assuming you have all 3 partitions directly on your external sdcard these are the cmds to wink them:

Thanks then much for your help with this, steadfasterX! In the long run, I might not have to use it because I started some intensive freezer therapy with the wonky G4 last nighttime, and was able to fill-in the two critical things I wanted, and then restore them to the new surrogate G4. Whatever the case, I am pleased to see how flashing full partition images can be done directly with dd in TWRP since TMo seems to have bedridden fastboot mode on the H811 Indeed, given my luck with the G4, I tin can certainly see it coming in handy in the future.

By the way, thank you lot for the FWUL+SALT combo--it works great!

• #828

Trying to make my first backup. Running FWUL in virtualbox. I can ostend telephone is in Download Mode. Table salt is not detecting the phone, even if lsusb shows it. I besides updated Salt (it was on latest master already).
Here is the debug log from SALT: https://pastebin.com/PkvAFBSQ

I can't find the info nigh running FWUL into virtualbox, the link virtually "doing critical things in virtualbox" is cleaved. FWUL can meet the device in adb vanquish, USB filter for the VM matches everything from LG. (id 1004)

• #829

Trying to make my starting time backup. Running FWUL in virtualbox. I can confirm phone is in Download Mode. Table salt is non detecting the telephone, even if lsusb shows it. I likewise updated Common salt (it was on latest main already).
Here is the debug log from Common salt: https://pastebin.com/PkvAFBSQ

I can't find the info about running FWUL into virtualbox, the link about "doing disquisitional things in virtualbox" is broken. FWUL can run across the device in adb beat out, USB filter for the VM matches everything from LG. (id 1004)

Do you have USB 2 or 3 configured in VirtualBox ? Try switching to the other. When doing this you might need to ready the USB filter over again . This is (just) one reason why I recommend usb stick boot..
You can too attempt to put your phone into Download Mode first and so boot FWUL. for this you need yous accept Auto USB filtering enabled of course.

Sent from my OnePlus 6T using XDA Labs

• #830

Volition try, at least I know it should piece of work. Information technology would be a picayune of a problem to boot FWUL natively on my device as information technology has secure boot and bit locker enabled on the tpm, so I usually continue all live iso I would need to boot into a secure-kicking enabled USB drive with Grub, booting other alive ISO in plough. Also my device has no integrated keyboard, if something goes wrong in arch with the mobile keyboard or the touchscreen or the docking station interface it would exist quite annoying. AFAIK we have bear upon-capable bootloaders/recoveries for both windows and Android but non for Linux.

• #831

Will try, at least I know it should work. It would be a trivial of a problem to boot FWUL natively on my device as information technology has secure kick and scrap locker enabled on the tpm, then I usually proceed all alive iso I would need to kick into a secure-boot enabled USB drive with Grub, booting other live ISO in turn. Also my device has no integrated keyboard, if something goes wrong in arch with the mobile keyboard or the touchscreen or the docking station interface it would be quite annoying. AFAIK nosotros take touch-capable bootloaders/recoveries for both windows and Android simply non for Linux.

at least for secure boot at that place are good news if y'all are using the nightlies: they back up that
https://code.binbash.rocks:8443/mAid/build/wiki/Secure-Boot

.-

• #832

Rebooting the VM while device connected and in download way did the trick. Now backing upwards. ?

• #833

US991 to H811 to gain VoLTE capabilities?

This is probably a stupid question, but...

I have an LG G4 US991 that is facing obsolescence due to lack of VoLTE support. The H811 model does have VoLTE back up. Can I flash my US991 with an H811 ROM to gain VoLTE? Are in that location physical differences between the LG G4 models that would forestall such a ROM switch? Thanks.

• #834

This is probably a stupid question, but...

I accept an LG G4 US991 that is facing obsolescence due to lack of VoLTE support. The H811 model does take VoLTE back up. Can I flash my US991 with an H811 ROM to gain VoLTE? Are there physical differences between the LG G4 models that would prevent such a ROM switch? Thanks.

Is VoLTE worth it? Imho no just maybe that's a personal affair.
Anyways converting a device is EXTREMELY risky. Not because of hardware diffs (all g4 models are identical, ok besides the h818 which has a diff console) merely because of the PBL (master bootloader) which sits in a protected area and verifies the surface area which tin be flashed (i.e. what you wink by kdz). It'due south all well-nigh signatures (nosotros can leave out ARB for the moment) . The thing is without the PBL (which you can't pull) nobody else then the us991 OEM tin say if y'all tin can convert without a hard brick.

Y'all tin though (depends on your ARB): unlock with UsU, flash kick , modem and organization of a stock h811 (must match your current ARB!!!) and you might tin can get VoLTE ( your provider must support that as well, often needs then a transmission activation too). No guarantees hither every bit well but the adventure for a hard brick are at 1% if yous follow the guide . And as you lot accept a fusing model you could even revert UsU and so if that didn't worked and you wanna nevertheless run a risk a hard brick you could try a convert then (chance for a difficult brick are here 80:20).

You lot can recover from hard bricks past using qfil simply yous demand proper qfil files for your model and ARB (which could be a real event for your model )!!! Or by using a box simply those work commonly only upwardly to ARB ii.

Sent from my OnePlus 6T using XDA Labs

• #835

New Release

Checkout FAQ #ix for howto update to this make new release

Legend for the summary topics:
Fix/New (Common salt): Fixes & Enhancements of the Common salt primary application - what you lot see and work with
Gear up/New (lglaf): Fixes & Enhancements of the USB communication backend which Salt uses under the hood
Fix/New (kdztools): Fixes & Enhancements of the KDZ extraction backend which Salt uses nether the hood

v3.22
Released: 2020-03-09
Full changelog (SALT): at github (this version compared with the previous release)
Full changelog (lglaf): at github
Full changelog (kdztools): at github
Summary changelog:

• 
  ATTENTION FOR FWUL (v2.ten, v3.10) users:
  Upgrading to this Version Will BREAK Common salt without doing a FULL organisation upgrade (which tin can take hours, downloading multiple GB, may even break on low RAM systems)
  Instead information technology is highly recommended to apply the new mAid nightlies which are in RC phase already and so reasonable stable.
• Gear up (kdztools): some fixes for KDZ extractions
• Ready (Common salt): UsU and ARB detection in rare cases
• Fix (SALT): no output for several lglaf based operations
• Gear up (SALT): backup (custom) progress bars
• Set up (SALT): when a binder or filename independent a space SALT failed to parse and extract
• Fix (SALT): several things around ARB and ARB detection
• Gear up (SALT): screwed function listing
• Fix (Common salt): log upload
• New (SALT): added a pre-check after the user selected a directory: when the path exists and containing image files the user get prompted to either retry or proceed.

HINT:
Newer devices using UFS storage (e.one thousand. G5, G6, ..) nevertheless demand to switch to the DEVELOP/TESTING branch (see FAQ)

Last edited: Mar ten, 2020

• #836

LG g5 H820n11 att

i upgraded my lg g5 att H820n11 with lgup to oreo 8.0 with a tot file and after completion my phone turned off and and so it is dead. and in device manager at that place is com 18 lge androidnet usb serial port. what i do now...plzz help me.. thanks

• #837

Having Table salt issues while trying to do initial backup before trying UsU on my H815. 3 issues:

i. I tried the 15GB FWUL version of FWUL three.one and this worked fine to kicking via usb, merely SALT got "fatal mistake- missing phyton cryptography module" error on trying to update SALT.

2. Because of error one, wiped USB drive and installed latest mAid nightly mAid_v2020-04-07. Booting and the mAid Os are fine, SALT recognises device fine, merely Common salt gives fault on trying to do full fill-in, same fault as annotate 819, i'm backing upwardly to a 4TB NTFS bulldoze with about 3.9TB free on it.
---then followed steps from comment 819, backup of everything else works fine except for userdata.img, which always 'succeeds' but then fails md5 cheque. this happened on both

Table salt - three.22-12:STABLE. (all 3 branches stable per faq) and
SALT - 3.23-0:TESTING (all three branches develop per faq). Tried once again after manufactory reset H815 telephone (it'south yet unmodified) and with same results. Any ideas why userdata.img is always failing md5 check? Is userdata even important to backup, or is it simply photos and stuff which i've already deleted anyway from factory reset? If not important i'll merely skip userdata backup as i have everything else backed up via Table salt at present.

3. When i go to Salt > Avant-garde > debug log, i am unable to export the log to provide here, get "Error in module 'haste' while uploading logfile..." among others.

My device is H815 20e TWN, on MM fully stock (no modding at all yet) if it helps. I've really tried to follow all threads and FAQs and so deplorable if i've missed something.

Last edited: Apr fifteen, 2020

• #838

Having SALT issues while trying to do initial backup before trying UsU on my H815. 3 issues:

1. I tried the 15GB FWUL version of FWUL 3.one and this worked fine to boot via usb, but SALT got "fatal mistake- missing phyton cryptography module" error on trying to update Table salt.

2. Because of error ane, wiped USB drive and installed latest mAid nightly mAid_v2020-04-07. Booting and the mAid Bone are fine, SALT recognises device fine, but SALT gives fault on trying to do full backup, aforementioned error as comment 819, i'm backing up to a 4TB NTFS drive with about 3.9TB free on information technology.
---so followed steps from comment 819, backup of everything else works fine except for userdata.img, which always 'succeeds' but then fails md5 check. this happened on both

Salt - 3.22-12:STABLE. (all 3 branches stable per faq) and
Salt - 3.23-0:TESTING (all iii branches develop per faq). Tried again later mill reset H815 telephone (information technology's still unmodified) and with same results. Whatever ideas why userdata.img is ever declining md5 check? Is userdata even of import to backup, or is it just photos and stuff which i've already deleted anyway from factory reset? If not important i'll simply skip userdata backup as i have everything else backed up via Salt at present.

3. When i go to Table salt > Advanced > debug log, i am unable to export the log to provide here, get "Error in module 'haste' while uploading logfile..." among others.

My device is H815 20e TWN, on MM fully stock (no modding at all yet) if it helps. I've really tried to follow all threads and FAQs and so sorry if i've missed something.

userdata "just" contains your photos, apps etc. it is not a critical part when it comes to e.g. unbricking a device so if yous tin live with loosing your data (which you lot already have due to the factory reset) you tin can skip that. no without the log I cannot say why the md5 is failing here. will cheque why uploading declining.

.-

• #839

Reading betwixt the lines.

Ok your fastboot way is pretty limited , say thx to tmo. Anyways just switch to TWRP then and bold y'all have all 3 partitions direct on your external sdcard these are the cmds to flash them:

adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/past-name/boot
sync
dd if=/external_sd/arrangement.img of=/dev/block/bootdevice/past-proper name/organization bs=512
sync
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=1024
sync

After that reboot and it should exist fine.

Sent from my OnePlus 6T using XDA Labs

Let me simply say 1000 apologies for interrupting this thread. But I am in a tough spot.

TL/DR - Tin can I utilise TWRP to dd my one-time user information from a LGUP backup (from Nougat) into a fresh install of Lineage 17.ane? Just temporarily to recover some improperly backed up userdata? I am willing to downgrade or nearly annihilation to become in that location - just looking for elementary, condom and no risk to my newly unlocked bootloader .

Long version: Okay - once again - 1000 apologies. I hate when others bust into a thread... merely this stuff looks the closest to what I am imagining my solution to be.

I had -
LG V20 - AT&T version H910
Software version - H91010p
Android Security patch level: August 1, 2017
Kernel Version: 3.18.31
TWRP version 3.three.ane-0

Before doing anything - I did a full LGUP dump - INCLUDING MY USER Information
I likewise installed LG Switch and did a full fill-in.
Next - I followed this DirtySanta postal service to Unlock the bootloader etc.

I am now running LOS17.1 - an Android Q ROM
Android Security patch level = April v, 2020

And then - I am looking for a mode to become back some accidentally lost user data.
I tried LG switch and it only wants to backup my new install. Not sure how you get it to restore data...
I tried LGUP and no where does it say annihilation most restoring...
I am willing to try a dd fox in Linux (currently running Pop_OS and have Manjaro too) or Win 10 if demand be.
I am willing to fubar my current LOS17 install. I volition just reinstall after extracting my data.
I am willing to downgrade to Nougat or.... annihilation.
As long every bit I don't lose my root & unlocked boot loader, TWRP.

BTW - I tried just mounting the lgup file in linux and get some sort of bad superblock mistake.

I take the LGUP dump on the external at /LGUP...

And then in TWRP do I simply become to Avant-garde/Terminal and

dd if=/external_sd/LGUP/userdata.img of=/dev/cake/bootdevice/by-name/userdata bs=1024
sync

Do I need to restore anything else? I don't care if I go ForcedClose of some programs every bit long every bit FX File explorer works long enough to fetch my information? Oh and - will this work? My userdata is 52.2 GB...

Risks? Thinking of just trying it.

Is there another fashion?
Thanks in advance for whatever tips, tricks, breadcrumbs or best of all ANSWERS!!
Best Regards!!

---------- Post added at 04:50 PM ---------- Previous post was at 04:44 PM ----------

I might have already found a gotcha... /data/media on the phone shows 39 GB free of 51 GB... So fifty-fifty if I delete everything - not sure how to become 52.2 GB into that partition? Hopefully someone smarter than me will explain how...
Thanks.

• #840

Hold everything!!
I was able to recover my missing data.
I reverted back to Nougat and then LGSwitch was able to restore my information.
I grabbed it up onto a SD bill of fare and flashed forward to Pie.
Distressing for the break. It is notwithstanding a very interesting thought question.

Similar threads

fullertaight.blogspot.com

Source: https://forum.xda-developers.com/t/tool-locked-unlocked-salt-the-lg-up-revolution-begins.3717864/post-81896855

Share this post