yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] steadfasterX:
New Major Release

FWUL_v3.0_x86-64

Released: 2019-01-02

Reason: Feature & Maintenance release

Download: Go to the Download section in the OP

All closed issues for this release: see the Milestone tracking on my gitlab

Full

Changelog (this version VS. previous): gitlab commits

Summary

Changelog:

FWUL got an own HOMEPAGE :)

You may notice that I moved all code to an own gitlab server. The repositories on github.com will stay but are archived, read-only and

outdated

.

Fresh Manjaro Arch Linux base from the day of release (means all OS packages are top current)

Versions of the main FWUL components for this release:

Kernel -> version: 4.19.13-1 (major upgrade)

ADB and fastboot: android-tools -> version: 9.0.0_r18-1 (major upgrade)

simple-adb GUI -> version: update6

SALT -> version: 3.21-4

ROME -> version: 1.0-1 (newly added)

TeamViewer (req user install) -> version: 14.0 (major upgrade)

bootimgtool-git -> version: 20150607.g9ccd962-1

heimdall-git -> version: 1.4.2.r7.ga2cfdaa-1

xfwm4 -> version: 4.12.5-1

lightdm -> version: 1:1.28.0-1

xorg-server -> version: 1.20.3-1

virtualbox-guest-utils -> version: 6.0.0-1 (major upgrade)

firefox -> version: 64.0-1

hexchat -> version: 2.14.2-1

testdisk-wip -> version: 7.1-1

tmate -> version: 2.2.1-2
​

new: added MiFlash for Xiaomi devices - read the short summary in FWUL included tools & installers

new: finally pre-configured hexchat

new: added two android boot image manipulating tools

new: added an even more clear Virtualization warning in the welcome screen

new: added [ROM][E] an extract tool for ROMs - read the short summary in FWUL included tools & installers

new: polished up wallpaper

fix: from now on FWUL supports (partly) system upgrades (see issue #63)! This means:

- you CAN update FWUL (using the desktop icon for adding/removing software or within a terminal: trizen -Syu --noconfirm)

- you will NOT be able to update the kernel, virtualbox guest utils or any other kernel related module(s) (they are excluded automatically so just for info)

- you will NOT be able to update to newer FWUL releases. This will ALWAYS require a re-install as changing that would require an incredible amount of work and resources, update servers etc.

there are more fixes/changes: follow the above full changelog/milestone link!
[Android Software/Hacking General [Developers Only]] Zander_Sig:
Thank You!!

Awesome! Thanks [MENTION=5545101]steadfasterX[/MENTION] !!!
[Android Software/Hacking General [Developers Only]] fil3s:
Thanks chief! :svetius:
[Android Software/Hacking General [Developers Only]] KokkoM:
Working fine on my ASUS Chromebook C223, booted via legacy boot mode :)
[Android Software/Hacking General [Developers Only]] sansara_2001:
Hello! Tell me what's the problem, if at the start of the virtual machine, the reverse timer appears 3,2,1 and after that the countdown again 3,2,1. and so it counts endlessly in a circle. Where is the error in configuring the virtual machine or what?
[Android Software/Hacking General [Developers Only]] steadfasterX:
1) There is no reverse counter on VirtualBox afaik so it seems you use an unsupported hypervisor . If you use VirtualBox: The most common issue is to not configuring the VM as 64bit .

2) did you read this from the OP ?

keep in mind

: Even running in a VM is supported you will have best performance and best user experience when running from

DVD/USB-Stick

instead.

To be more clear: It is HIGHLY recommended to

not

do critical operations from within VirtualBox as this can be a risk (see information here)
[Android Software/Hacking General [Developers Only]] sdembiske:
Refer to post # 483 in this thread and read and follow it thoroughly & exactly. If done correctly all the way through you should not run into any issues such as you have. VirtualBox is the only virtual machine supported.

The main advantage in using VirtualBox IMO, is the ability to expand your storage beyond the limitations imposed by the size of the USB flash drive/DVD (max. 30GB) that is used to run FWUL directly as well as being able to transfer/copy projects/files etc., directly to one's Windows OS. This is particularly important for LG users using the SALT full backup provision, for example, as it can be up to 32 GB.

---------- Post added at 08:27 PM ---------- Previous post was at 08:18 PM ----------

@steadfasterX

Thank you for the new version.

A couple of quick notes

:

- The default language is German when first booted up and must be changed on the login screen initially. Once changed & logged-in, it requires a reboot to effect the language change on the right-click menus, for example.

- When a dark desktop background is chosen, the icon descriptions below each icon become unreadable as the default font is black it seems. It would be helpful to have an option to select a white font colour when dark backgrounds in particular are selected.

Thank you again,

S.
[Android Software/Hacking General [Developers Only]] sansara_2001:
I figured it out.

it was necessary to choose Linux 2.4 (64-bit)
[Android Software/Hacking General [Developers Only]] steadfasterX:
The text color of the icons cannot be changed easily as I had to hardcode it for FWUL. I will not make it changeable but thx for your feedback anyways. You can though change the complete theme itself which includes also the text icon color in the settings .

Well the German default is interesting .. I remember that I had recognized it but thought it was maybe due to newer vbox guest utils.. Hmm I'll check that later .. It you like open an issue on my gitlab ..
[Android Software/Hacking General [Developers Only]] sdembiske:
The icon text colour is no deal-breaker whatsoever. Just chose a lighter background colour.

With respect to the default language, I only tested the 30GB persistent version - solve was easy enough, just thought I'd mention it in case you weren't aware and it was an oversight as all the prior versions defaulted to English,.
[Android Software/Hacking General [Developers Only]] AlwaysLucky:
I got this error too. I used Rufus and followed the OP guide. However the newer Rufus version (v3.4.1430) doesn't look the same. The 2 differences I found is that Rufus asks to download 2 files to flash it (ldlinux.sys & ldlinux.bss). The other difference is that it asks to use DD *after* you click start; which I selected.

Any help?

Update 1: Using USBwriter has exact same result.

Update 2: Worked perfectly on 6 yo laptop I got out of the closet and dusted off. Must be an issue with newer hardware?
[Android Software/Hacking General [Developers Only]] steadfasterX:
well when rufus will add these files it will destroy things I guess. I will take a look and report back once tested.

EDIT

so.. it seems to be still possible to use rufus.. but only in UEFI mode: you have to switch MBR to GPT and then select DD write when asked.

The issue with that is not all PCs support UEFI and so I would prefer to switch to another tool.

[MENTION=6061535]AlwaysLucky[/MENTION] could you please try that one here?

https://www.balena.io/etcher/

It is VERY simple to use and does exactly what we need..

.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Recommended Flasher on Windows (since 2018-01-15)

This one is super easy to use, includes even a flashing verification and is available on all platforms:

Etcher: https://www.balena.io/etcher/

Works on: Windows, Mac OS (10.9 and later), Linux

Select the FWUL image:

Ensure you choose the correct USB drive by clicking on

Change

below "USB device" :

Click the Flash button and wait until it has finished:

By default Etcher will verify the flashed image (you can abort that one but it is highly recommended to let the verification finish):

Once all has finished reboot, ensure your PC booting from your USB (check your BIOS if not) and enjoy FWUL from your USB stick :)

Alternative Flasher on Windows (since 2018-01-15) - (slower, no verify)

Use this one ONLY when the recommended flasher does

not

work for you!

HDDRawCopy: http://hddguru.com/software/HDD-Raw-Copy-Tool/

Works on: Windows XP, Vista, 7, 8, Server 2003, 2008, 2008R2

Select the source by double-click in the "FILE" row:

Select the target by clicking on the "USB" row (and ensure it is

really

the correct one!):

Click start to begin the flashing:

Check the warning pop-up: that's your last chance to abort before destroying a wrong drive..:

Wait until the flashing finishes:

Once all has finished reboot, ensure your PC booting from your USB (check your BIOS if not) and enjoy FWUL from your USB stick :)

legacy methods (unsupported but may still work)
[Android Software/Hacking General [Developers Only]] fil3s:
:eek: this is driving me nuts now which display resolution is recommended for VirtualBox ? If I choose the wrong res the whole VM freezes up

My native resolution is 1920x1080 any ideas?
[Android Software/Hacking General [Developers Only]] AlwaysLucky:
Very cool, thanks for the attention into this.

It turns out it it just doesn't like my main custom desktop PC. Rufus and USBwriter both worked great on an older laptop I had and a newer laptop my gf has. I tested both UEFI and non-UEFI. On the laptops it all worked perfectly.

I used my desktop to flash two different flash drives with your linux install. They were flashed using a Win 10 system using the following configs:

RUFUS: flashed onto 16gb flash drive, allowing it to use the downloaded files. Used MBR, not GPT. Selected DD option after clicking start. No errors were encountered during flashing. Booted successfully on both laptops.

USBwriter: flashed onto 16gb flash drive. No errors were encountered during flashing. Booted successfully on both laptops.

If I get a chance I will try the flashing tool you mentioned and report back. I will also try RUFUS with GPT selected. However, I don't think this is a flashing issue. I think this particular problem has to do with my desktop hardware. My desktop is a newer custom build with newer BIOS features as well. Would a list of my desktop hardware be useful to you to try to narrow down the cause, or are you sure it's a flashing issue?

Either way, thanks so much for your work on this! It's very handy to have a lightweight Linux with phone drivers baked in. It also helped to root my LG V20. I'll go click all your thanks buttons. :good::cowboy::victory:
[Android Software/Hacking General [Developers Only]] whitewolf1608:
Hello, dear steadfast user, X-ranked Recognized Developer, how can I change language from German to Polish Linux, which I downloaded on PenDrive from this link.

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

https://photos.app.goo.gl/JqphqkNV11dznWPd9

https://photos.app.goo.gl/F93p8Pe1ktojhNV18

https://photos.app.goo.gl/znJyNzvpwgbVMcKFA
[Android Software/Hacking General [Developers Only]] fordry:
deleted
[Android Software/Hacking General [Developers Only]] ExquisiteArcaneAstralMystic:
[MENTION=5545101]steadfasterX[/MENTION]

Not sure if u still remember me but i hope u do not because I'm really not full of sh1t as u may think (in case u remember my nick)

Gimme ur private email (the one u use all the time) i will continue there (u won't regret that)
[Android Software/Hacking General [Developers Only]] whitewolf1608:
Hello, but what is deleted?

---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------

Hello, but what is deleted?
[Android Software/Hacking General [Developers Only]] jovanv:
It would help some poor souls like mine if the FWUL comes in English, instead of German: xfce in FWUL_v3.0_x86_64_15GB.zip is in German, it took me some time to figure out how to change it to English.
[Android Software/Hacking General [Developers Only]] steadfasterX:
that's a bug in the current release and only happens on persistent mode.

See

https://code.binbash.it:8443/FWUL/build_fwul/issues/87

and

https://code.binbash.it:8443/FWUL/build_fwul/issues/88
[Android Software/Hacking General [Developers Only]] jovanv:
Solved it by 1) changing the keyboard to us_US before login (upper right on login screen) and then 2) editing the file .dmrc and changing de_DE to us_US and then logout and login.

If you don't know German it will be quite difficult to find which xfce configuration to open and where to change it. So, the above should be OK. Also not that if you don't change the keyboard before login then you have to know the German keyboard layout, it took me some time to figure out how to exit vim (:wq) after editing the .dmrc file :D
[Android Software/Hacking General [Developers Only]] steadfasterX:
Well that works for you but is way to hard as a workaround ;)

As described in the linked issue #88 it's much easier:

select language, login, reboot

The issue is that the greeter (or lightdm I am not sure atm) does not actually write the .dmrc file unless you reboot or restart the lightdm service.

There are several things in FWUL included to make sure the language and keyboard is set properly after logging in but everything depends on .dmrc . I call it a bug as the file has to be changed after logging in (like it does in all earlier FWUL versions) but it doesn't .

That happens only in persistent builds so when you boot the forgetful mode and change the language before login the change takes place immediately .

The above workaround works fine though and I work hard on a real solution.
[Android Software/Hacking General [Developers Only]] fil3s:
Got ignored and it gets on my nerves. I don't use lg g4 anyway Gonna give it to my mother

Hopefully she uses it because i don't
[Android Software/Hacking General [Developers Only]] shinobisoft:
I'm quite sure you didn't get ignored. Bear in mind, we ALL contribute voluntarily and we ALL have lives outside of XDA. [MENTION=5545101]steadfasterX[/MENTION] is great about answering questions when HIS time allows. Have patience!!!
[Android Software/Hacking General [Developers Only]] fil3s:
He did in fact ignore the question and thanked you for responding to my blowup about it, what u said makes no sense.. but I realise it was a stupid question now so it's all good :angel:
[Android Software/Hacking General [Developers Only]] steadfasterX:
uhm .. ok you created your post on the 12th January at

5:02

and deleted it on the same day just half an hour later and you say I

ignore

you?

If you're expecting

live

support here, I'm afraid I have to disappoint you..

I have a RL as well btw. (yea it often doesn't look like but..)

Sometimes I can answer quickly sometimes it needs even

days

but I try to answer all questions if I can .

.-
[Android Software/Hacking General [Developers Only]] steadfasterX:
FWUL_v3.0.2_x86-64 - PERSISTENT ONLY

A patch has been released for FWUL

persistent

builds.

Patching a persistent build is handled by the FWUL LivePatcher which can be found on the desktop.

Due to many under-the-hood changes of the LivePatcher (mainly the repo URL path changed and that required adjusting several files) the following procedure is needed to upgrade correctly to the latest release:

double-click "FWUL LivePatcher"

click "Check & Download Patches" button!

once finished click "Start LivePatcher" and wait until it finishes

you will be prompted to re-open the LivePatcher as there was an update for the LivePatcher itself

you should be informed that your FWUL version is now 3.0.1

close the LivePatcher and re-open it

click again on "Check & Download Patches" button!

once finished click "Start LivePatcher" and wait until it finishes

you should be informed that your FWUL version is now 3.0.2

if something goes wrong do this in a terminal:

tar cvzf flu.tgz /var/log/fwul

and attach the resulting flu.tgz file in your post.

Changelog

Released: 2019-01-15

Reason: Maintenance release, ONLY for persistent builds

Summary

Changelog:

changed repository patch for FWUL LivePatcher to gitlab

workaround for issue #88
[Android Software/Hacking General [Developers Only]] fil3s:
[MENTION=5545101]steadfasterX[/MENTION] you mean this question? I don't see it deleted :confused: .. Ive unsubbed from you're threads now. Have a nice day
[Android Software/Hacking General [Developers Only]] steadfasterX:
Well I am a human only so sometimes even

I

overlook something.

that happens maybe because of your VirtualBox version!? Try to upgrade that one first.

The display resolution is set automatically when you set to auto-adjust it (which works fine for me after logging in):

If that still fails.. yea I have to say I am not a VirtualBox supporter. This has nothing to do with FWUL itself so try to post your issue in the Vbox forum to get proper help.

.-
[Android Software/Hacking General [Developers Only]] fil3s:
? I am only a begginer at forums . Didn't mean it.

Edit: by the way, I downloaded the Latest version. Forget it.
[Android Software/Hacking General [Developers Only]] xdamember143:
cant seem to format my usb stick after flashing any help?
[Android Software/Hacking General [Developers Only]] steadfasterX:
https://www.pendrivelinux.com/restoring-your-usb-key-partition/
[Android Software/Hacking General [Developers Only]] xdamember143:
Also cant read german how do u change language
[Android Software/Hacking General [Developers Only]] steadfasterX:
I assuming you are using a persistent build?!

Read and follow this:

https://xdaforums.com/showpost.php?p=78678680&postcount=870

then change the language before login (the background pic is pretty clear WHERE) and then you will be prompted to apply the changes
[Android Software/Hacking General [Developers Only]] fil3s:
Autoresize guest display is greyed out so my res ended being 1400x1050.
[Android Software/Hacking General [Developers Only]] steadfasterX:
you won't change anything within FWUL. This will be handled full automatic!

Look again at the screenshot in my post https://xdaforums.com/showpost.php?p=78679026&postcount=872

This setting is taken in the VirtualBox windows - not in FWUL ! When you set this and just resize the whole VM window the FWUL desktop will be auto-resized magically.

.-
[Android Software/Hacking General [Developers Only]] fil3s:
I realise this isn't the VirtualBox thread so I won't continue my nonsense talk anymore. I googled for an answer but couldn't figure it out Anyway It's working now and my G4 is even being recognised in DL mode ;)
[Android Software/Hacking General [Developers Only]] Ablutions:
Usage feedback: love the FWUL bundle thanks for your work. Of course I had to tinker with Salt and it bricked my phone. I was I forgetful mode and have no logs, live off a USB stick, 8gb version. Sp320(10h), 7.1, no ARB, (adb debugging and OEM unlock enabled) was recognized and everything seemed to work, read all my partitions but many were labeled unknown. Completed a full back up, 14gb or so. Despite the multiple warnings I stubbornly, foolishly, wiped the cache partition tagged "unneeded" containing 1gb. Clicked on reboot which it did and it hung on the boost logo. Powered off with the keys after 30 and immediately tried to get into recovery, saw the words for 5 secs but it flickered off and "supported API 3" pops up in a loop. No key combo for DL or recovery, vol down+ power turn it off but it won't stay off. It charges. LGUP and Bridge recognize it for a split sec it won't enter any sustained mode. Had it replaced but still have it and would like to get my data off it. Unrecognized by adb in both Fwul and win 7. That's all I know, I apologize for not being able to provide logs.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Download mode is needed for SALT to work. Adb needs running recovery or android.

You said you wiped the cache partition. How? With SALT ?

Are you able to boot into fastboot ! Unlocked or locked bootloader?
[Android Software/Hacking General [Developers Only]] Ablutions:
I was just reading about UsU. The BL is locked and how to get into fastboot? It seems to still retain some functionality but only for a split second. I can see "unknown" briefly with LGUP but it won't stick. This model has an internal battery. I had it doing an intermittent pulse vibrate at one point after mashing key combos

*yes with SALT. I have the bricked phone still pending to send it back plus I have an identical working model. Only difference is the old one was on 32010h 7.1, the replacements on 32010e 7.1.1. I think... In fact the new phones prompting me to install a 648 mb security update but I held off. Thanks for your response.
[Android Software/Hacking General [Developers Only]] steadfasterX:
I don't know your model but anyways this is more a SALT topic or tbh an own one.

could you boot your working device into download mode and start SALT , then go in the advanced menu and click show partitions button. Close it and while still in the advanced menu share the debug log link you get after click on the debug log + upload button. Share that link in the SALT thread though ( https://bit.do/SALTatXDA ). This will help to make SALT better for your model..

I asked regarding fastboot because wiping a partition wipes it. Wiping is different from formatting and you did that for the cache partition which needs a formatted file system on it to work properly. The solution for this is quite easy: fastboot format cache but that requires an unlocked device . Another option is to get download mode working and using SALT to open a cmd shell or flashing a cache partition from a kdz .

Open an own thread for this in your device forum and mention my nickname or share the link to your post by PM.

UsU is available for the g4 only.
[Android Software/Hacking General [Developers Only]] Ablutions:
Yes I see what you mean: wipe is not synonymous with clear in this case. I knew that in retrospect but was set on establishing my model was compatible. What could possibly go wrong emptying the cache, lol. Sorry to clutter your thread, ill move it else where and get that log to you.
[Android Software/Hacking General [Developers Only]] Teknouser:
Hi everybody,

What is the SALT version number in this FWUL 3.02? I have read in one of other post saying that

"

2a) So I can't flash any KDZ/TOT anymore?

2b) So I can't upgrade my STOCK ROM with the LG updater anymore?

Have you really read the limitations topic? I guess no.

You can't! At least for the KDZ flashing part: not yet.

SALT will allow flashing of KDZ files with the upcoming version 4.0 but until then do not flash with lgup and do not use the LG Android internal updater --> You WILL 100% brick your device.

Why? Read the above FAQ.

"

Is it now possible to flash a stock MM rom in case of I brick my LG G4 H815P phone during rooting attempt?

I have almost lost all my hope that LG will give an update the current MM firmware. So, I think to root and ınstall a custom recovery then a custom rom accordingly. But I am still not sure whether it could be possible to install stock rom in any case for a bricked H815P?

Thanks
[Android Software/Hacking General [Developers Only]] smurf_1:
Hey,

I have flashed the latest persistant FWUL image (3.0).

I am getting a mount error for "fwulforever" on startup. It gives me a shell, if I enter "exit" it loads fine, but it's not saving my data (not persistant).

I am running ubuntu and I flashed it with Etcher.

Laptop is Dell XPS 13 (9343)

Any ideas?

Thanks!
[Android Software/Hacking General [Developers Only]] steadfasterX:
100% an issue with flashing. Either the stick has errors or the flashing was not correct.

The etcher verify after flashing went fine? Or do you skipped that?

Try another usb stick or the alternative method
[Android Software/Hacking General [Developers Only]] steadfasterX:
Uhm REALLY????? you had still hope for any update for the g4? Sorry... but LOL.. That will never come! 110%.

Ask SALT questions in the SALT thread. If you wanna know what's included FWUL read the changelog on the first site of this topic