yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] steadfasterX:
Yeah many thx for that hint :) makes totally sense this way and hopefully helps others.
[Android Software/Hacking General [Developers Only]] spainter:
Try disabling the fast start in advanced power options in Windows. When starting cold it uses a hibernate file to speed up the boot but doesn't kick in during a restart.
[Android Software/Hacking General [Developers Only]] nufrankz:
How can I mount any usb plugged into the computer? Doesn't seems to recognize no one usb, even if its a memory stick or my android phone. Thank you!
[Android Software/Hacking General [Developers Only]] Koncrete:
:D

TYVM for trying to help me... But I already fixed that by readding the correct headers and redo'ing the permissions and installing virtualbox tools. It runs pretty straight now but I ran into one small issue that I haven't really tried to fix because of time... A program I am trying to use wants to access the phone as a com/serial port... So i figured out how to add my phone as a comm/serial port and can see it but I don't have permissions to "read" it... Working on that tomorrow probably... I've completely butchered your build and I've probably gone about it the hardest way possible but I only knew how to do the commands /cd and /ls when I started... 2 weeks later and I have destroyed and rebuilt fwul as well as creating my own version of arch linux on a separate vm next I am dual booting my laptop so I can have a dedicated linux environment although I can't figure out what build to use... I want to use it to work on phones as well as host a minecraft server :D I may have caught the *nix bug lol
[Android Software/Hacking General [Developers Only]] UKLonghorn:
I am trying to reflash my Xiaomi Redmi Note 3 (MediaTek / hennessey). Space was tight on the phone so I decide to wipe the phone and was going to reinstall my prefered ROM. All was good but TWRP got overwritten so I have a device with no OS and no recovery.

I think I should still be able to flash TWRP via adb and fastboot and from there I can reinstall my ROM?

The issue is I cannot get adb to see my device on Windows 7 so I am using FWUL. I am familar with Linux as I run an unRAID server at home. But I am seeing the same issue - I cannot get adb on FWUL to see my device. I have booted and attached the phone in fastboot mode (power+volume down) and recovery (power+volume up). The device then appears on the dektop but adb cannot access it.

The phone previously had debuuging enabled but perhaps this got wiped with everything else?

If I can get adb to see the device, I will be fine - any pointers would be appreciated - Thanks!

Dave
[Android Software/Hacking General [Developers Only]] piskor:
You can access your phone using adb only when you have working recovery or system

In your case you need to flash recovery using fastboot commands and boot to recovery:

fastboot flash recovery here-put-your-twrp-recovery-img-name.img

fastboot boot here-put-your-twrp-recovery-img-name.img
[Android Software/Hacking General [Developers Only]] UKLonghorn:
[MENTION=3037460]piskor[/MENTION] - many thanks! Will give that a go later this weekend and update here. Thanks!
[Android Software/Hacking General [Developers Only]] steadfasterX:
Oh I just realized...

Happy Birthday FWUL

:highfive:

yesterday FWUL has been reached the first year of (public) existence :)

on the 28th of December in 2016 I released the first public beta and wow the time goes by fast, right :)
[Android Software/Hacking General [Developers Only]] Raj.S:
How can I make a bootable USB in Linux of FWUL?

will dd work fine?

Plz help. [MENTION=5545101]steadfasterX[/MENTION]
[Android Software/Hacking General [Developers Only]] steadfasterX:
Sure a dd should work just fine.

Either use dd or if you are as lazy as I am... install a GUI tool like the SUSE imagewriter (pacman -S imagewriter on arch Linux or within FWUL :) ) or any of the others like:

https://www.fossmint.com/3-best-gui-enabled-usb-image-writer-tools-on-linux/

Hint: do not use the image tool named multiboot. It has issues and FWUL wouldnt boot.
[Android Software/Hacking General [Developers Only]] Raj.S:
Thanks for replying me.

I tried dd, unetbootin and Rufus all didn't work for me:(

I am on kali Linux btw.

Will try again with SUSE.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Thanks for your post and detailed explanations so far. I try to make FWUL a good user experience for those coming from windows so you input is highly appreciated.

Could you do me a favor and test the latest nightly v2.5(!) from yesterday? The nightlies link is in the OP and you will find the 2.5 when you scroll down a bit.

2.5 isn't released yet so its not linked on the main download servers. I will add several more stuff to 2.5 and need to do more testing on it before releasing it but it should work fine for you already.

I hope that one works better for you when it comes to usb auto detection. Let me know your results.

Your issues when it comes to installing and or upgrading something are strange. Here it works fine but without the error messages I can't help here ofc.. Keep in mind that when *not* using a persistent type of FWUL the RAM is used and so may needs to be increased. So share the complete errors and the output of:

df -h

in FWUL.

IRC will be auto configured in a future release (see roadmap) until then the web link in the OP should work fine. Keep in mind that the whole project is managed and done by ONE single person (with thx clicks as my motivation ;) ) and I may live in a different timezone so I may cannot respond on IRC directly. Besides that its end of the year and I'm on vacation until next Tuesday so don't expect any answer until then on IRC ;)
[Android Software/Hacking General [Developers Only]] steadfasterX:
Didn't work means what? What happens when booting? Do you have setup your bios to boot from USB? Do you have secure boot enabled on bios (see FAQ)? Do really have a 64 bit pc?
[Android Software/Hacking General [Developers Only]] Raj.S:
I can boot other os like kali and windows installation also Hiren's boot CD but in case of FWUL when i select my flash drive in boot menu it won't boot and goes directly to grub menu of my dual boot kali and windows 10. It's like normal booting when i boot without any selection .

Ps:- I think there something wrong with my download iso. After dd this is how my partition size of flash drive looks like.......

My flash drive is of 4gb.

Check the first red circle Its only of 64 mb partition should be about 853 mb!!

I think i should re-download the iso again.

Sorry for bothering you....

I like your work.:fingers-crossed:
[Android Software/Hacking General [Developers Only]] steadfasterX:
If you find an 8 GB stick you could use the persistent img instead...

A 4 GB stick could held only the forgetful ISO!

If you have to redownload you could also try the v2.5 nightly build on the nightlies dl server mentioned..

And pls verify always the md5!
[Android Software/Hacking General [Developers Only]] Raj.S:
Hell yeah finally.... After downloading again:o:D:victory::laugh:
[Android Software/Hacking General [Developers Only]] HTCDevil:
No, Xiaomi like all other brand use Mtk and Snapdragon principally

Inviato dal mio Redmi 5 Plus utilizzando Tapatalk
[Android Software/Hacking General [Developers Only]] google99:
Below are the error i have connecting my LG G4 (H815 with this ROM : [ROM][H850] H-ROM V30 FULL V1.0 [BETA][UX6+][v20s][v10g] normally for LG G5) !

Can you please help me to resolve it ?
[Android Software/Hacking General [Developers Only]] TechnoTew:
Any way to compile my own 4GB persistent version?
[Android Software/Hacking General [Developers Only]] steadfasterX:
Sure. Read github readme.
[Android Software/Hacking General [Developers Only]] TechnoTew:
How would I do it? I'm a noob at this and I am a student so...

My thumbdrive only has 4GB of space and it works with forgetful mode, how to create persistence for the remaining 3GB ++ of space?

I changed USBSIZEMB to 2048 and tried to run the command to compile but this is the output(Mac Terminal):

readlink: illegal option -- f

usage: readlink [-n] [file ...]

Please help
[Android Software/Hacking General [Developers Only]] steadfasterX:
Before you really go further: there is a reason why no 4GB version exists. It makes usually not much sense. Ok when you do not want to install something then.. But then you wouldn't need a persistent.. Well ok if you just want to save your personal settings like language and wallpaper whatever.. Then yes it would make sense. But when you begin to install software you will reach the limit very fast.

If you really want to go on read the README again! You can build FWUL only on Arch Linux.
[Android Software/Hacking General [Developers Only]] TechnoTew:
Thx for the reply. I guess I cant do it then since I don't have a arch linux device.

Otherwise, great job making this forgetful version
[Android Software/Hacking General [Developers Only]] Laugh2:
Hi SteadfasterX,

I've just burnt the latest nightly "FWUL_v2018-01-25_22-04_x86_64_persistent.img" (which took quite a while) and booted it then entered the command "adb devices" in a terminal. So far, I can confirm that FWUL puts an icon for a USB Flashdrive onto the desktop. That will make transferring files much easier. :)

I try a few more of those niggles mentioned over the next few days. Thank you again for your work!
[Android Software/Hacking General [Developers Only]] TechnoTew:
I mean, i still want a 3GB persistence version but its too much of a hassle for me to find a thumbdrive that is suitable to install arch linux on my 1 and only 4GB thumbdrive and compiling it. I'm a noob so its too hard for me.

The main reason why I want it is for installing just tools for samsung such as JOdin and stuff
[Android Software/Hacking General [Developers Only]] steadfasterX:
Grabbing a 8GB stick and just use the 8GB FWUL version is your best option and highly recommended..

Otherwise you have to use the forgetful one.
[Android Software/Hacking General [Developers Only]] Laugh2:
Hi SteadfasterX,

Further to yesterday's trial post about trialling a USB-Stick installation, today I made a VirtualBox VM using "FWUL_v2018-01-25_21-53_x86_64_forgetful.iso" and entered the command "adb devices" in a terminal. It now works i.e. the USB Stick has an icon on the desktop and files can be transferred. Thanks.

:)

I've now to work out how to use Heimdall with the ROMs I have, which are all TAR.MD5 ROMS, so I'll have to find a Linux utility to handle them. Any suggestions, anyone? (Perhaps a utility for this could also be a candidate for inclusion in the FWUL project?)
[Android Software/Hacking General [Developers Only]] steadfasterX:
open the folder Samsung on your desktop.

Use Heimdall if you want to use it or JOdin which is a replacement for Odin on windows

https://xdaforums.com/showpost.php?p=70272684&postcount=3

-> scroll down for what is included in FWUL and how to use it

-
[Android Software/Hacking General [Developers Only]] David_#27:
Please, create a 32bit image! I need it so desparately! It's unfair that 64bit users can enjoy it and we, 32bit users can't!
[Android Software/Hacking General [Developers Only]] Laugh2:
... yes, I'd found and tried both JOdin and Heimdall for my earlier posts. Both find attached devices if they are in Download mode, so that's great. The difficulty is that although JOdin recognises TAR.MD5 files and seems to start flashing them, it makes no progress and no blue bar appears on the mobile.

Heimdall performs better and will create PIT files successfully. Unfortunately Heimdall doesn't accept TAR.MD5 files - which is what I almost always usually have. They need to be unpacked first, which I don't seem to be able to do in Linux.

Currently I've toyed with 7Zip in a Windows VM to unpack the TAR.MD5 files, which seems to work. I haven't yet been bold enough to try flashing these unpacked files using Hemidall. That may be my next trial. I'm sort of hoping I get better infos next time I search the internet, or better still perhaps someone can point me in the right direction for an unpacker for TAR.MD5 files on Linux.
[Android Software/Hacking General [Developers Only]] steadfasterX:
Pls read this: https://github.com/Carbon-Fusion/build_fwul/issues/25#issuecomment-361854881 . It's not that I do not want to but keep in mind that I do this project completely alone. No one wanted to help on that 32bit topic and the effort is extremely high as 32bit gets abandoned on the base FWUL uses.

Thanks for writing this down!

Highly appreciated and added to FAQ #4

.
[Android Software/Hacking General [Developers Only]] sdembiske:
Deprecated* ...How to add your VirtualBox (Host) Shared Folder to FWUL - Updated

* "Deprecated" i.e., rendered obsolete - From version 2.5 + this method is no longer required as steadfasterX has incorporated the general method.

--------------------------------------------------------------------------------------------------------------------------------------------

After some trial and error, again, finally got the correct method to get your VirtualBox (Host) Shared Folders on FWUL(persistent) - allowing one to greatly expand the usability of FWUL given the inherent drive sizes ... the problem is that the automount function in VirtualBox puts the shared folder in the /media directory which is accessible only by root, so permission is denied to access it whatsoever.

in the VirtualBox settings for FWUL add your (Host) shared folder in Shared Folders and do put a check mark in the Auto-mount box and, if you desire, one in the Make Permanent box.

Pre-checks:

- confirm "virtualbox-guest-utils" is installed in FWUL - in a terminal type: sudo pacman -Qe

- make sure User "android" is a member of the vboxsf group - in a terminal type: groups android

- if it is not, add it with this command: sudo gpasswd --add android vboxsf

note

: it's

two

dashes with no spaces between ahead of 'add' in the command.

Edit the /etc/modules-load.d/virtualbox.conf file (I prefer nano for editing finding it very user friendly - it can be installed with this terminal command: sudo pacman -Sy nano )

In a terminal enter this command: sudo nano /etc/modules-load.d/virtualbox.conf

add the following lines:

vboxguest

vboxsf

vboxvideo

- then, if using Nano, hit 'Ctrl x', 'y' to save and then 'enter' to add the lines in the file.

then (just in case), enter the following command in a terminal:

sudo systemctl enable vboxservice.service

Then, change the permissions on the shared folder with this terminal command:

sudo usermod -a -G vboxsf android

Now (the real nuts and bolts), in a terminal use the following command

:

sudo VBoxControl guestproperty set /VirtualBox/GuestAdd/SharedFolders/MountDir /home/android/Desktop/

-

note

: if you don't want it on the Desktop, just leave that off and it will install to your Home directory.

-

NOTE

: The command will

NOT

work in the latest Nightly version (at this point in time) as the 'home' folder is owned by root and does not allow permission changes.

Confirm that it's done by typing in a terminal:

sudo VBoxControl guestproperty get /VirtualBox/GuestAdd/SharedFolders/MountDir

and see what's listed in "Value" in the output.

Next, type in a terminal: reboot

- the shared folder should be loaded and fully accessible after the reboot.

Enjoy your expanded FWUL capability for backup purposes etc. - example, SALT full backups are up to 32 Gigs- you can save the backup to your VBox shared folder (provided of course, you have enough disk space available on your Host hard drive).
[Android Software/Hacking General [Developers Only]] Laugh2:
I had one last device to flash: an old Samsung Galaxy Y GT-S5360, which has been unusable for a year or more. The TAR.MD5 ROMs for it could not be expanded by 7zip, presumably because it's so old. I needed to extract the CSC and MODEM files from the old ROMs to use with Custom ROMs. Fortunately Odinatrix can unpack the old stock ROMs and worked first time (but takes a while). It can be found at:

https://xdaforums.com/showthread.php?t=1892529

After getting the various files together i.e. CSC, modem, and Custom ROM, I tried to flash them with Heimdall on FWUL but presumably due to unfamiliarity with Hemdall it failed (and perhaps because my file names needed "translation" to know which to use where). Since I very soon have a very busy phase at work now I ended up flashing using Odin on a VM, which revived the old device to better-than-new condition and working like a charm. I really look forward to further development of this project, especially a persistent version in a VirtualBox VM of the recent nightly version which fixed the USB-Stick issue. Thank you for work to date.

:)
[Android Software/Hacking General [Developers Only]] steadfasterX:
Persistent in VirtualBox? Already there. Read the FAQ ;)

Btw remove the md5 file ending and double click the tar file to extract ;)

Cheers
[Android Software/Hacking General [Developers Only]] Laugh2:
Sorry, I should have been more specific. I meant of course a persistent version of the nightly edition I'd trialled and which didn't have the bug regarding USB-Sticks. (I had been using the persistent Live USB version on bare metal and was pleased with that version but would prefer your VirtualBox VM.)

:)
[Android Software/Hacking General [Developers Only]] sdembiske:
How to add and use your USB Flash Drive in FWUL persistent in (Windows) VirtualBox

In your (Windows) Host machine, right click on the USB Flash Drive that you've inserted and highlight the give access to line and click on Advanced Sharing when it comes up. Then, click on the Advanced Sharing menu bar and put a check mark in Share this folder when it pops up. Next, click on the Permissions menu and put a check mark in Full Control in Permissions for Everyone in the box below.

Then, open your Settings menu in Virtual Box for your FWUL persistent guest os and click on Shared Folders, When it pops up, add your flash drive (+), selecting the Flash Drive you've inserted and shared, then put a check mark in both the Auto-mount and Make Permanent boxes. The Auto-Mount box alone will do if the Make Permanent box doesn't show.

[Start your Fwul persistent guest os and when it's loaded, if you haven't done so already, refer to post # 486 and follow the directions there to add your VirtualBox (Host) Shared Folder(s) to FWUL.

Note

: If you previously added all the commands for a shared folder, you do not have to do it again - it only has to be done once] - From version 2.5 + this is no longer required as steadfasterX has incorporated it.

When you've completed entering

all

the listed terminal commands in that post, reboot FWUL and enjoy full permissions access to your Flash Drive on the FWUL Desktop.

Note

: Unless you have the same Drive letter for every USB Flash Drive you have, the process will have to be repeated for each different Flash Drive. Solution (?): re-name your Flash Drives to all the same Drive Letter, e.g. 'Z' (?)
[Android Software/Hacking General [Developers Only]] steadfasterX:
one word:

awesome

.

Really that information and solution is really appreciated and helpful stuff! Good findings especially the direct display on the desktop ;)

based on the above I will include all necessary changes in v2.5 (with slightly modifications as not all of the above is needed)

Thanks for your contribution!

steadfasterX

EDIT:

newest v2.5 nightly has the above included ;)

feel free to test and report back

ty
[Android Software/Hacking General [Developers Only]] steadfasterX:
FWUL_2.5_x86-64 released!

Released: 2018-02-15

Download: Go to the Download section in the OP

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

Full

Changelog: on Github

Summary

Changelog:

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

Versions of the main FWUL components:

Kernel -> version: 4.14-1

ADB and fastboot: android-tools -> version: 8.1.0_r7-1

simple-adb GUI -> version: update6

SALT -> version: 3.6-6

heimdall-git -> version: 1.4.2.r5.g5377b62-1

xfwm4 -> version: 4.12.4-1

lightdm -> version: 1:1.24.0-3

xorg-server -> version: 1.19.6+13+gd0d1a694f-1

virtualbox-guest-utils -> version: 5.2.6-2

firefox -> version: 58.0.1-1

hexchat -> version: 2.12.4-7
​

new: Added the awesome LG tool SALT ;)

new: replaces LTS kernel with the latest (better hardware support for many cpus, network/wifi cards etc)

new: added tmate as a TeamViewer alternative when no GUI is needed (no install needed)

new: full support for VirtualBox share folders (big thx to [MENTION=6302635]sdembiske[/MENTION] who brought up the idea!)

fix: desktop takes a long time to load after login

fix: /media was not writable

there are more fixes/news: follow the above full changelog/milestone link!
[Android Software/Hacking General [Developers Only]] sdembiske:
Thank you for your comments.

2 things

:

- the first VirtualBox image conversion command (VBoxManage internalcommands createrawvmdk -rawdisk FWUL_v2.5_x86_64.img -filename FWUL_v2.5_x86_64.vdi), you have recommended in the OP, simply does not work - it appears to do the conversion but on trying to install it indicates the verr_ file is missing. No amount of repositioning of files helps - I would delete the command entirely from your OP as I don't believe it will work as it is in any version of VirtualBox anymore. The second command works just fine and should be the only one recommended currently.

- The SALT desktop icon is not automatically installed to the desktop - no big deal (but thought you should know, just in case), as opening a terminal command in the SALT folder and adding the command: bash install-desktop.sh solves easily.

The Shared Folders desktop link is a nice addition and particularly so when doing a full backup of one's phone (up to 32G) with SALT and being able to now save the backup to the Host hard drive. Appreciate you doing it.

Best and thanks for all you do for all us XDA members ...

S.
[Android Software/Hacking General [Developers Only]] steadfasterX:
The first command for converting works but not on all VirtualBox versions.

SALT icon is installed ;) but where it belongs to: folder LG in the desktop. FWUL is meant for all android lovers not only LG users :)
[Android Software/Hacking General [Developers Only]] sdembiske:
The first command dates to at least 2013 or earlier - so it would be helpful to your FWUL/VBox users to know that it is a "legacy" command, so they do not waste time trying it first on any later versions of VBox. Putting the second command first would also help.

Using that logic re: the SALT icon, all android users are Samsung, Sony or Mediatek owners ... ? ;)

Question: on v2.5 can it be updated now with the sudo pacman -Syu command or will it still run the risk of breaking it?

Thanks,

Steve
[Android Software/Hacking General [Developers Only]] steadfasterX:
Hm 2013.. Really? Ok will change the FAQ accordingly asap. I'm always open to valid suggestions ;)

EDIT:

nope VBoxManage internalcommands converttoraw is still valid here on VirtualBox 5.2.6 (runnin on Linux) but I nevertheless swapped the both first ones.

You can upgrade even older FWUL releases as long as you do not upgrade the kernel. If you put the kernel to pacman.conf ignore list you can upgrade without breaking the system as a workaround.

Could you pls open an issue on github for that (upgrading kernel breaks system boot)?
[Android Software/Hacking General [Developers Only]] Vishnuisgod:
I hate asking silly questions but;

how do I remove the FWUL from my usb to get it back to normal.

I put it on an 8gb stick, but I want to move it to a 32gb stick, I cant seem to find any programs thatll see it in windows to reformat it....

thanx steadfastX

youre a hero the world needs (head shaking, who the phuck locks a phone???). I can wait for th G4 PoC release!
[Android Software/Hacking General [Developers Only]] Kurt Krummbein:
You just have one USB-port on your PC? Boot from you 8gb stick, copy it over to the 32gb stick, boot from the 32gb stick, format your 8gb stick, done :).

Gtz

Kurt
[Android Software/Hacking General [Developers Only]] wiliamminke:
Remove Log in Page

can i remove the log in page ?

How to?