yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] akenis:
Ok...working in Perstant mode.

Had to select Y to install downgrade (confusing)

Had to select y to IgnorePkg question

Thanks. Learning a lot here.

So in reference to previous question about my xfce install on Chromebook:. can I use pacman to install Android tools?
[Android Software/Hacking General [Developers Only]] steadfasterX:
Thanks for your kind words ;) its not easy to do all this stuff alone..

glad it works now.

xfce is just a desktop environment not a linux distribution itself but regarding your question if you can install Android tools with pacman: yes.

adb and fastboot are both included in the package android-tools which you downgraded to fix the authenticate issue.

sfX
[Android Software/Hacking General [Developers Only]] shinobisoft:
Trust me, I know!!! You deserve the recognition!!!
[Android Software/Hacking General [Developers Only]] akenis:
All good! Looks like my install is Ubuntu Xenial WITH Xfce environment. No Pacman. But I did use apt-get to install 2 packages:

android-sdk-platform-tools-common

android-sdk-platform-tools

Works here too! Version 1.0.32 though......

I should be able to flash anything now!!!

1. PC Windows native

2. PC boot FWUL

3. Chromebook shell

4 Chromebook development console

5. Chromebook boot FWUL

6. Chromebook Crouton Ubuntu/Xfce, Open terminal from dowlnloaded tools folder

7. Chromebook Crouton Ubuntu/Xfce native

All I really wanted to do was lock a bootloader with fastboot. How we are easily distracted......

Only thing left is to use one Android to adb/fastboot with a client Android??????!!!! Anyway, maybe I should start a thread: How to use a Chromebook to fastboot/adb.....the FWUL companion!
[Android Software/Hacking General [Developers Only]] SonderTech:
Help
[Android Software/Hacking General [Developers Only]] steadfasterX:
sudo pacman --noconfirm -Sy downgrade
[Android Software/Hacking General [Developers Only]] SonderTech:
It works!
[Android Software/Hacking General [Developers Only]] akenis:
FWUL

What's the F stand for? haha.

Think I'll call my guide FWUC

..use Chromebook.

Seem to be missing a K.
[Android Software/Hacking General [Developers Only]] shinobisoft:
The "F" is actually for "Forget". Forget Windows Use Linux.

We do appreciate the other possibility for "F" however, it's inappropriate for this forum. ;)
[Android Software/Hacking General [Developers Only]] steadfasterX:
Announcement: FWUL LivePatcher available!

Ok so ... after 24 hours nonstop coding I'm able to proudly introduce you the absolutely awesome FWUL LivePatcher ! (Details)

The idea:

having a way to hotfix issues after a major release within a persistent installation (forgetful can be applied as well but here you have to re-do it on every boot..).

What this is not:

Providing all future enhancements or adding new features.

FWUL LivePatcher should be just an easy way to solve smaller bugs without the need to reinstall the whole IMG.

So don't expect to update an existing v2 to a new v3! Major releases will require a full re-flash This is just for hotfixing known issues

Installation (already included since v2.3!):

I will release a new v2.2 version asap which will have the FWUL LivePatcher included but until now and if you have a persistent install and do not want to re-flash follow this guide:

In FWUL download the FWUL LivePatcher package:

(click)

Open the file explorer and double click on the downloaded package (e.g. fwulpatch-2.2.2-1-any.pkg.tar.xz)

Confirm the following after being prompted for your FWUL login password:

These warning messages can be ignored (see issue #58)

Just close this dialog and the next one and you are fine

You will see a new icon appearing on the Desktop: FWUL LivePatcher

Doubleclick FWUL LivePatcher icon

Check for new updates:

Click Start LivePatcher

Doubleclick the Welcome icon to see if the version got increased

Re-Start FWUL LivePatcher and click again on Start LivePatcher

You should see a message that there's no need to patch anymore

Current available hotfixes in FWUL LivePatcher

Checkout the patch names listed here: (click) - every patch is named as an issue so you can easily find them on the FWUL issue tracker

especially issue 56 is therefore (hot)fixed after running the FWUL LivePatcher !

Have fun

sfX
[Android Software/Hacking General [Developers Only]] YuriRM:
Unfortunately, FWUL does not run in my Windows 10 PC. I selected the UEFi Partition 1 of the JetFlashTranscend. It is blocked at Asus BIOS level by a red banner Secure Boot Violation. This also happens with some Linux distributions that I tried before. Only a few like Maui Linux and Deepin booted successfully.

Flashed it to an USB stick with Etcher.

Update: Rufus has failed too!
[Android Software/Hacking General [Developers Only]] steadfasterX:
Do you have read and tried FAQ #1:

https://xdaforums.com/showpost.php?p=70272692&postcount=4

sfX
[Android Software/Hacking General [Developers Only]] SonderTech:
I have windows 10 and its able to boot. Granted I booted it through my flash drive but it shouldn't make a difference and try choosing the jetflash transcend instead of the uefi partition 1 of the jetflash transcend.
[Android Software/Hacking General [Developers Only]] YuriRM:
Thanks a lot for your suggestion! FWUL has now booted successfully.
[Android Software/Hacking General [Developers Only]] SonderTech:
I'm glad to hear, when booting another OS using a flash drive, I think, just to be safe, choose the non uefi partition option of the flash drive.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Announcement: FWUL_2.3_x86-64

Released: 2017-09-23

Versions of the main FWUL components:

ADB and fastboot: android-tools -> version: 7.1.2_r27-1

simple-adb GUI -> version: update4

heimdall-git -> version: 1.4.2.r3.g9bcc42d-1

xfwm4 -> version: 4.12.4-1

lightdm -> version: 1:1.22.0-1

xorg-server -> version: 1.19.3-3

virtualbox-guest-utils -> version: 5.1.28-1

firefox -> version: 55.0.3-1

hexchat -> version: 2.12.4-6
​

Fixed an issue with adb

Fixed an issue with directory permissions

Added FWUL LivePatcher --> details and issue
[Android Software/Hacking General [Developers Only]] rizkhan999:
Problem Using the builtin LG LAF tool

I have to use the LG LAF tool for my LG Nexus 5. I burnt FWUL_v2.3_x86_64_15GB.zip IMG using DD mode in Rufus (on Windows). And booted in persistant mode. The desktop folder named LG contains 03 x programs: LG LAF (auth), LG LAF - ng, LG LAF (no auth). The first and the third, crash as soon as I double click on them, while only the second one can be used. In that, I tried commands like "python lglaf.py" and "python partitions.py --list" as mentioned in the LGLAF readme or elsewhere but I got the error saying "PyUSB is not installed".

From the PyUSB guide I came to know that I needed to have python, libusb and pip installed. Python is pre-installed in this FWUL image, however I installed the remaining 02 x packages using the following commands:

$ sudo pacman -S multilib/lib32-libusb

$ sudo pacman -S extra/python-pip

Then, I installed "pyusb" using the following command as mentioned in that PyUSB guide:

$ sudo pip install pyusb --pre

Everything was successfully installed till that point. However, now when I run the above mentioned commands again i.e. "python lglaf.py" and "python partitions.py --list", it gives the RuntimeError that "USB device not found".

My Nexus is in Bootloader/Download mode and connected to my laptop and is also detectable with the "fastboot devices" command (correct serial number also shows up in the output of that commands). Does anyone have the idea what can be the problem?
[Android Software/Hacking General [Developers Only]] steadfasterX:
you have to use

sudo

python2 lglaf.py

all python2 dependencies coming completely pre-installed with FWUL. There is no need to install anything but you have to use explicitly python2 in your commands.

The tools you have installed are those for python3.

Both lglaf shells (auth and no-auth) are connecting directly to a device in download mode (with python2). Sorry for not pointing that python2 hint better atm.

sfX
[Android Software/Hacking General [Developers Only]] rizkhan999:
Thanks. But I am getting the same error whether using python2 or python. I am pasting both commands and both the errors below:

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

Traceback (most recent call last):

File "lglaf.py", line 404, in <module>

main()

File "lglaf.py", line 382, in main

comm = autodetect_device()

File "lglaf.py", line 318, in autodetect_device

return USBCommunication()

File "lglaf.py", line 206, in __init__

raise RuntimeError("USB device not found")

RuntimeError: USB device not found

[android@fwul lglafng]$ sudo python2 partitions.py --list

Traceback (most recent call last):

File "partitions.py", line 276, in <module>

main()

File "partitions.py", line 248, in main

comm = lglaf.autodetect_device()

File "/home/android/programs/lglafng/lglaf.py", line 318, in autodetect_device

return USBCommunication()

File "/home/android/programs/lglafng/lglaf.py", line 206, in __init__

raise RuntimeError("USB device not found")

RuntimeError: USB device not found

While the device is properly detected by fastboot as below:

[android@fwul lglafng]$ fastboot devices

0317318b09399c0c	fastboot

The Download mode in my phone is looking like what I have attached herewith.
[Android Software/Hacking General [Developers Only]] steadfasterX:
are you sure that the device is in download mode?

when you can do fastboot devices it seems that you are in the bootloader and not in download mode

sfX
[Android Software/Hacking General [Developers Only]] shinobisoft:
You're in recovery mode, NOT download mode.

Edit: My bad, it's fastboot mode. Still not download mode. Have you zeroed out the laf partition by chance?

If you can boot the device normally, and are rooted, you can use the follow in a terminal emulator on the device to see if the laf partition has been zeroed out.

su
echo $(dd if=/dev/block/platform/*/by-name/laf bs=1 count=8)

If the last line output is NOT "ANDROID!", without the quotes, your laf partition has been modified or zeroed out.

That's the only reason I can figure you're booting to fastboot mode, other than user error. No offense meant.

EDIT: Updated code snippet to use a slightly different path. If that doesn't work, substitute the device path for your own.
[Android Software/Hacking General [Developers Only]] rizkhan999:
Yes my phone is rooted. The output of the suggested echo command executed as su gives:

dd: /dev/block/bootdevice/by-name/laf: No such file or directory

By the way I don't have the "bootdevice" directory in the "/dev/block" directory!

And the df command also doesn't show any partition named laf:

root@hammerhead:/ # df

df

Filesystem Size Used Free Blksize

/dev 928.2M 84.0K 928.1M 4096

/realdata 26.8G 25.4G 1.4G 4096

/system 26.8G 25.4G 1.4G 4096

/data 26.8G 25.4G 1.4G 4096

/cache 26.8G 25.4G 1.4G 4096

/data/media 26.8G 25.4G 1.4G 4096

/dev 928.2M 84.0K 928.1M 4096

/sys/fs/cgroup 928.2M 12.0K 928.2M 4096

/mnt 928.2M 0.0K 928.2M 4096

/persist 15.7M 4.2M 11.6M 4096

/firmware 64.0M 44.4M 19.6M 16384

/storage 928.2M 0.0K 928.2M 4096

/mnt/runtime/default/emulated 26.8G 25.4G 1.4G 4096

/storage/emulated 26.8G 25.4G 1.4G 4096

/mnt/runtime/read/emulated 26.8G 25.4G 1.4G 4096/mnt/runtime/write/emulated 26.8G 25.4G 1.4G 4096

And yes the mode that I were at (in the attached screenshot of my previous post) is th3 bootloader mode. I can't get into the Download mode.

For more information, I have multirom recovery installed and have 5 to 6 OSs installed as secondary roms besides the stock MM rom.

Can i recover the laf partition without affecting my multirom setup?

Update: Just felt it important to inform the partitions related output of "fastboot getvar all" command while phone in bootloader mode:

(bootloader) partition-size:aboot: 80000

(bootloader) partition-type:aboot: emmc

(bootloader) partition-size:boot: 1600000

(bootloader) partition-type:boot: emmc

(bootloader) partition-size:recovery: 1600000

(bootloader) partition-type:recovery: emmc

(bootloader) partition-size:system: 40000000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:userdata: 6ce9fa800

(bootloader) partition-type:userdata: ext4

(bootloader) partition-size:cache: 2bc00000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:persist: 1000000

(bootloader) partition-type:persist: ext4
[Android Software/Hacking General [Developers Only]] shinobisoft:
[MENTION=8423206]rizkhan999[/MENTION]

It seems your laf partition is missing. I found a pic of your device in download mode and a link to an article describing how he got to that mode.

Here's the URL... https://plus.google.com/+AdamOutler/posts/Pr4UphvQLEd

This may or may not help...
[Android Software/Hacking General [Developers Only]] rizkhan999:
Its talking about the wireless charger. I dont have that. But thanks for the help :)
[Android Software/Hacking General [Developers Only]] richie16171:
Just hold the volume + button(up) while phone is in off position and connect the USB cable to the computer to get into the download mode. Hope it helps.
[Android Software/Hacking General [Developers Only]] shinobisoft:
Sound advice, if he had a LAF partition. Somehow his isn't being detected or it's been written over/removed. Without the LAF partition there is no Download mode, just fastboot.
[Android Software/Hacking General [Developers Only]] YuriRM:
I own a Takee 1 Holographic 3D Smartphone.

The best update for now is 20151109. And the BOOT from 20151010 flashed upon it with SP Flash Tool. Almost everyting works fine.

This switch of boot image enables perfect GSM calls. Unfortunately, it does not solve the bug in VoIP calls.

The October 2015 ROM has a Proximity Sensor bug, turning off the microphone when the screen goes off. The conversation stops because the other person cannot ear me.

The November 2015 ROM has another Proximity Sensor bug, introducing disturbing clicking noises when the screen is off, but keeps the microphone on. The conversation goes on.

These two ROMs are buggy on both GSM calls and VoIP calls. Why does the switch of the boot image file (November to October) enable perfect GSM calls on the November 2015 firmware? Is it possible to enable perfect VoIP calls by editing the boot image file?

I would like to use FWUL for editing the boot image file of the October and November 2015 ROMs.

A comparison of the source-codes of these two image files is needed. Is it possible to highlight their differences automatically?

I have no experience in Smartphone programming languages. I did a small bit of FORTRAN programming a long time ago.

Can you help me, please?

The boot image files may be extracted from the October and November 2015 ROMs

Takee-1_151010_151026-212141_root-mod-deodeXposed

Takee-1_151109_151114-172130_root-mod-deodeXposed

EDIT - I have got an hybrid phone now.

Notice that Kernel Version is Saturday, October 10 and Build Number is November 09 (2015.11.09)

EDIT - Inside the boot image, there is the kernel and ramdisk. The kernel is compiled and the source code is unavailable. Therefore, my request is not feasible.
[Android Software/Hacking General [Developers Only]] rizkhan999:
Yes I had finally figured out that there was no Download Mode in my LG Nexus 5. Thanks for all the support.

---------- Post added at 09:22 AM ---------- Previous post was at 09:08 AM ----------

I know have LG G4 H815 (International variant) with unlocked bootloader and a custom nougat 7.0 rom but not rooted. And I am in the Download Mode now and connected to my laptop.

However, in FWUL v2.3 15GB (persistant mode) when I open LG LAF (auth) or LG LAF (no auth), and then enter any command (e.g. pwd etc.), I get the message Hello, I am LAF. Nice to meet you., as reproduced below:

LGLAF.py by Peter Wu (https://lekensteyn.nl/lglaf)

Type a shell command to execute or "exit" to leave.

# pwd

Hello, I am LAF. Nice to meet you.#

Similarly, when I open LG LAF - ng and execute command sudo python2 lglaf.py, and then execute any command (e.g. uname -a etc.), I get the same message Hello, I am LAF. Nice to meet you., as shown below:

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

[sudo] password for android:

LGLAF.py by Peter Wu (https://lekensteyn.nl/lglaf)

Type a shell command to execute or "exit" to leave.

# uname -a

Hello, I am LAF. Nice to meet you.#

Finally, when in LG LAF - ng I execute the command sudo python2 partitions.py --list, I get the following message:

[android@fwul lglafng]$ sudo python2 partitions.py --list

Traceback (most recent call last):

File "partitions.py", line 276, in <module>

main()

File "partitions.py", line 253, in main

list_partitions(comm, args.partition)

File "partitions.py", line 124, in list_partitions

partitions = get_partitions(comm)

File "partitions.py", line 41, in get_partitions

assert arrow == '->', "Expected arrow in ls output"

AssertionError: Expected arrow in ls output

Does any one know what can possibly be the problem?
[Android Software/Hacking General [Developers Only]] steadfasterX:
Yes your device firmware is not supported.. You can go into the main lglaf thread and ask for support or try to flash other firmware versions.
[Android Software/Hacking General [Developers Only]] nortish:
Hi guys. Im having some problems boot FWUL in Virtualbox. The ISO fires up to the boot screen but then it just loops. I can see the "Automatic boot in X seconds..." but when the time runs out its just loops back to 3 seconds. Not sure whats going on. Any tips?
[Android Software/Hacking General [Developers Only]] steadfasterX:
ensure that you select a 64 bit Linux in virtualbox VM settings

sfX
[Android Software/Hacking General [Developers Only]] nortish:
Ahh, silly me. Missed that one. Always nice with the easy solutions thou. Thanks!
[Android Software/Hacking General [Developers Only]] rizkhan999:
Dear developer!

I am using FWUL 15GB. The partitions.py --list command works flawlessly however its other switches i.e. wipe, dump and restore also get the job done but also generate an error in the end, reproduced below:

$ sudo python2 /home/android/programs/lglaf/partitions.py --dump recovery_bak.bin recovery

[COLOR="Navy"][B]2017-11-08 17:16:13,903 partitions: INFO: Wrote 41943040 bytes to recovery_bak.bin[/B]
Traceback (most recent call last):
File "/home/android/programs/lglaf/partitions.py", line 277, in <module>
main()
File "/home/android/programs/lglaf/partitions.py", line 273, in main
wipe_partition(comm, disk_fd, part_offset, part_size)
File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
self.gen.next()
File "/home/android/programs/lglaf/partitions.py", line 79, in laf_open_disk
comm.call(close_cmd)
File "/home/android/programs/lglaf/lglaf.py", line 177, in call
raise RuntimeError('Command failed with error code %#x' % errCode)
RuntimeError: Command failed with error code 0x8000010a
[/COLOR]

Similary extract-partitions.py also does its job but also gives out an error at the end. I am reproducing only the error in this case:

[COLOR="navy"]Traceback (most recent call last):
File "/home/android/programs/lglaf/extract-partitions.py", line 63, in <module>
main()
File "/home/android/programs/lglaf/extract-partitions.py", line 60, in main
dump_partitions(comm, disk_fd, args.outdir, args.max_size * 1024)
File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__
self.gen.next()
File "/home/android/programs/lglaf/partitions.py", line 79, in laf_open_disk
comm.call(close_cmd)
File "/home/android/programs/lglaf/lglaf.py", line 177, in call
raise RuntimeError('Command failed with error code %#x' % errCode)
RuntimeError: Command failed with error code 0x8000010a
[/COLOR]

Any idea what could be the problem? And would it effect the outputs or not?
[Android Software/Hacking General [Developers Only]] steadfasterX:
Hi ;)

Better place the DLM backup questions to the DLM backup thread especially as there you will find your answer in FAQ #3 https://xdaforums.com/g4/help/tutorial-backup-download-mode-t3659223/post73485387

Thx for choosing my "products" :)
[Android Software/Hacking General [Developers Only]] Koncrete:
[android@fwul ~]$ sudo ntfs-config

Traceback (most recent call last):

File "/usr/lib/python2.7/site-packages/NtfsConfig/NtfsConfig.py", line 247, in on_external_toggled

self.set_external_ntfs_policy("rw")

File "/usr/lib/python2.7/site-packages/NtfsConfig/NtfsConfig.py", line 210, in set_external_ntfs_policy

os.symlink(NTFS_WRITE, TARGET_NTFS_WRITE)

OSError: [Errno 20] Not a directory

Traceback (most recent call last):

File "/usr/lib/python2.7/site-packages/NtfsConfig/NtfsConfig.py", line 249, in on_external_toggled

self.set_external_ntfs_policy("ro")

File "/usr/lib/python2.7/site-packages/NtfsConfig/NtfsConfig.py", line 215, in set_external_ntfs_policy

os.symlink(NTFS_READ, TARGET_NTFS_READ)

OSError: [Errno 20] Not a directory

Traceback (most recent call last):

File "/usr/lib/python2.7/site-packages/NtfsConfig/NtfsConfig.py", line 247, in on_external_toggled

self.set_external_ntfs_policy("rw")

File "/usr/lib/python2.7/site-packages/NtfsConfig/NtfsConfig.py", line 210, in set_external_ntfs_policy

os.symlink(NTFS_WRITE, TARGET_NTFS_WRITE)

OSError: [Errno 20] Not a directory

Traceback (most recent call last):

File "/usr/lib/python2.7/site-packages/NtfsConfig/NtfsConfig.py", line 295, in on_close_clicked

self.disk.shutdown()

File "/usr/lib/python2.7/site-packages/NtfsConfig/Fstab/FstabHandler.py", line 199, in shutdown

list_created_path("clean")

File "/usr/lib/python2.7/site-packages/NtfsConfig/Fstab/Fstab.py", line 510, in list_created_path

created_file = open(CREATED_PATH_FILE, "a+")

IOError: [Errno 2] No such file or directory: '/media/.created_by_python-fstab'

I get nothing but screens full of header errors using this and then the tool errors out and leaves the img jacked up with no drive access lol I've went through 17 vm installs now trying to patch together a set of working headers but I am done guessing at this mess lol... Time to ask for help :D
[Android Software/Hacking General [Developers Only]] steadfasterX:
Which exact FWUL release?
[Android Software/Hacking General [Developers Only]] Koncrete:
FWUL_v2.3_x86_64_persistent

---------- Post added at 03:52 AM ---------- Previous post was at 03:35 AM ----------

Hmm... Maybe?
[Android Software/Hacking General [Developers Only]] steadfasterX:
Well the ntfs-config thing is just a workaround and I dont like it much (thats why it isnt in FWUL)

could u try this?

sudo mkdir -p /etc/hal/fdi/policy

sudo ntfs-config

The problem with NTFS drives is that starting from WIndows 8 the system will not REALLY powerdown by default when you select powerdown in the start menu. that automatic powersafe energy-safer whatever option is enabled by default in windows.

Win 8 and higher will put the system into a very deep sleep like hibernating (but it isnt hibernate). The result is: when you mount Win8 or higher disks in Linux as RW / ALLOW-WRITE this may destroy things in Windows (not sure as I do not use Windows and cant test).

So ensure that you do not enable write mode of the Windows disks to be sure. Readonly is totally safe though.

EDIT:

oh and this one here may work as well: https://askubuntu.com/questions/271516/is-there-a-program-to-mount-all-of-my-drives-automatically

in FWUL its not exactly the same then the above and should be here: Settings > Disks

or what should work for sure and u can follow the above guide is:

sudo pacman -S gnome-disk-utility

EDIT2:

To make gnome disk utility work this is required as well:

sudo pacman -S mdadm

Cheers
[Android Software/Hacking General [Developers Only]] ExquisiteArcaneAstralMystic:
Simple solution for not shutting down windows is .....

Simply everytime choose restart instead of shutdown (I do it all the time and this way everything works ) if u choose shutdown u cannot mount because there is error saying that disk was unproperly unmounted in windows
[Android Software/Hacking General [Developers Only]] infixremix:
When will the feature install be avalible I wonna use as main os