[App]DriveDroid - HTC Pico (Explorer)

DriveDroid allows you to boot your PC from ISO/IMG files stored on your phone. This is ideal for trying Linux distributions or always having a rescue-system on the go... without the need to burn different CDs or USB pendrives. The paid version of DriveDroid does not include ads and helps the developer.
DriveDroid also includes a convenient download menu where you can download USB-images of a number of operating systems from your phone.
You can also create USB-images which allows you to have a blank USB-drive where you can store files in. Another possibility is to use tools on your PC to make a bootable USB-drive out of the blank image that DriveDroid created.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How do you make this work?
* Connect your phone to your PC using an USB cable
* Download an image file (.iso or .img) or create one
* Select the image file in DriveDroid to let your phone 'host' the file over USB
* (Re)start your PC and make sure the correct boot priority is set in the bios
* The image should now be booted on your PC
Recommendations:
To quickly try DriveDroid download SliTaz from the download menu. It is an operating system of only 35MB, so it should be easily downloaded.
You can also create a 100MB FAT image through the 'Create blank image...'-menu. It should show up as a normal empty USB-drive on your PC.
Requirements:
* Root
* USB cable (from phone to PC)
* USB Mass Storage (UMS) should be enabled on your ROM (being able to mount SD card)
Some devices have trouble with UMS and ADB. Please set the USB-mode to 'Mass Storage' though DriveDroids preferences. If that does not work, send me a support email, also through the preferences.
USB Mass Storage (UMS)
DriveDroid relies on the kernel of Android, in particular the USB Mass Storage (UMS) feature. It allows your phone to act as an USB-drive and have a device (SDcard) or file (ISO/IMG) be used as the content for that emulated drive.
Different Android devices implement this feature differently. Most modern devices do not have UMS enabled by default, but it is supported by the kernel. I've added a option to DriveDroid to change the USB-mode for devices that do not support UMS by default, but no guarantees. I'm getting very mixed reports of devices working and not.
I need all the help I can get to fix this problem. Hopefully we can figure out some method to enable UMS in a stable way.
Hybrid-ISOs
Since most phones only support emulating USB-drives, DriveDroid will not act as an CD-drive. This means that not all ISO files will work, only hybrid-ISOs and IMG files. Hybrid-ISOs are specially crafted ISOs that is used on many modern Linux-distributions. DriveDroids downloadlist contains most of the distributions I've found that do have hybrid-ISOs.
This is just to notify you that you have to convert non-hybrid ISOs by writing the ISO to the emulated USB-drive. You can get a blank emulated USB-drive by creating a blank image through DriveDroids + menu.
True CD-ROM emulation
True CD-rom emulation is possible. It should allow you to run any ISO on your PC. With some help of others I've found a way to get CD-rom support, but it requires patching the kernel. For most users this isn't an option, however if you're interested: I've applied patches to the kernel of CyanogenMods Nightly builds for the Samsung Galaxy S (my device). The patches are accepted, so the more recent nightlies should work. I think the patches can be merged easily to other kernels (for other devices) as well, but I need people to try this for themselves. We can see whether we can get the patches into the nightly builds of CyanogenMod of more devices when it's well-tested.
DrivrDroid Free
Drivedroid Paid

Related

[APP] AL Mass Storage Manager | Beta 3 | 29/11(Nov)/2011 | Mount multiple USB devices

AL Mass Storage Manager - Beta 3 is a tool that allows you to mount multiple devices connected to your Android tablet or mobile phone with USB host capabilities.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Pre-requisites:
Rooted device
Busybox 1.19+
Features
Runs on tables or mobile phones, specialized layouts
Mount any block device that is detected by Android kernel
It doesn't interferre on the native mounting capabilities
Allows to cleanup mounting points for wrongly unmounted devices
Testing devices
Until now it's has been only tested on an Asus Transformer TF101, tested with the USB ports on the keyboard and the external USB adapter, it works smooth.
Usage
The application is free to use(with ads). Please, send me any feedback you consider necessary, comments, bug reports, enhancements are welcomed.
Download
Market link: You can find this applications searching the keyword antulabs in the Market
APK link: View attachment MassStorageManager.apk
help i just install this app and somehow tweak some of the sd file directory(deleted sd file properties) and now my phone shows 0 available space.
jcesar085 said:
help i just install this app and somehow tweak some of the sd file directory(deleted sd file properties) and now my phone shows 0 available space.
Click to expand...
Click to collapse
Please, give me more details to be able to help you, a snapshot will be useful too.
Hi! Does it can enable the USB Mass Storage connection for honeycomb device such as TF101 ?
I do have big problem to make TF101 can be mounted as USB Mass Storage, so I can recover 1000+ photos storaged in internal memory ( /sdcard ), which have been formatted days ago, by unexpected operating.
aigeek said:
Hi! Does it can enable the USB Mass Storage connection for honeycomb device such as TF101 ?
I do have big problem to make TF101 can be mounted as USB Mass Storage, so I can recover 1000+ photos storaged in internal memory ( /sdcard ), which have been formatted days ago, by unexpected operating.
Click to expand...
Click to collapse
I'm sorry, AL Mass Storage Manager only provides a mechanism to mount external USB devices that are not mounted automatically or not recognized directly by your device, nothing about setting the device itself as a USB mass storage to be used in a Desktop machine.
antulabs said:
I'm sorry, AL Mass Storage Manager only provides a mechanism to mount external USB devices that are not mounted automatically or not recognized directly by your device, nothing about setting the device itself as a USB mass storage to be used in a Desktop machine.
Click to expand...
Click to collapse
Thanks for reply.
About setting the honeycomb device as a USB mass storage ( but MTP ) , is it impossible?

[Resolved] Lands of Lore 2 + DosBox Turbo, how?

I have installed using GOG installer Lands of Lore 2 on my PC. It installs 2 folders, one is DosBox, the other one is Lands of Lore 2.
I also have my own DosBox on the PC that I use separately from this GOG installer. The only way to start the game on PC which it does via dosbox and that's the idea, is not just to run DosBOX installed by GOG which has its own configuration - running it from that is like running the regular DosBox, it does not start gives:
Unable to Load Language File from CD-ROM disc #1
BUT from a shortcut of the dosbox set to use exactly the CONF file that I attached:
"E:\Legacy Games\Lands of Lore Guardians of Destiny\DOSBOX\DOSBox.exe" -conf dosboxLOL2.conf -noconsole -c "exit"
On ANDROID, (Smartphone etc) with DosBox Turbo:
Copying the LoLG folder and running straight from it gives the same CD-ROM Load Language error you see above.
Also DosBox Turbo does not use the CONF file seen here, even the PC's original DOSBOX does not use that conf file and I wonder how to make the DosBox Turbo run with such settings that game?
Anyone knows?
At home wasted hours and didn't find how to do it - while I am at work posting this (I suspected the solution may be easy and I don't do it right), all I did was mount:
mount d storage/emulator/0/Other/LLore2 -t cdrom
This mounts the installed folder game files on D: drive as a CD-ROM, I do not have ISO to do 'imgmount' but mb you didn't understand.
Previously I entered D: and started game from it - ofc it doesn't have enough free space there. But all I needed to do is mount D as a CD-ROM so it reads the game files from a CD-ROM to not give me 'Unable to Load Language File from CD-ROM disc #1'. Then I go to C: drive, no need to mount, as I already see the game on my hard disk - then load the game from there, then it reads the files it wants to read from the virtual CD-ROM, while I start the game from the C drive (i.e storage/emulator/0/Other/LLore2).
Thanks to Jorpho for helping
Resolution
If you need to enter Setup to configure some things, you can still use this command:
- If you use DosBox (PC):
mount d E:\LegacyGames\LoLG -t cdrom
- If you use DosBox Turbo (Android):
mount d /storage/emulator/0/LegacyGames/LoLG
You get the message: MSDEX: Mounted subdirectory. Limited Support Drive D: is mounted as CDRom E:\LegacyGames\LoLG\
Mind your Folder names - if the game is on which drive and folder name, especially on Android, which is your root folder name! Too long names get shortened to Name~1 Name~2 and these names should be used to get the folder path correctly. Sometimes when mounting Name~1 and such do not get recognized at all as their original name is not so, only display name on DosBox. Best is to name folders under 7 (or 6) characters, so that DOS doesn't have to change them and you can get your path correct.
Then enter your game folder (LegacyGames\LoLG\) from C: if you haven't mounted that already on DosBox (mount c E:\LegacyGames\LoLG\ OR mount c E:\) or on DosBox Turbo it is already added in the dosbox.conf to mount C as your local Android phone/tablet drive (for me it was /storage/emulator/0/)
From the game folder run Setup.exe, this will run the setup but then it will ask for a CD,
Please insert any LOL:G CD into your CD-rom drive.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is for Setup, as it won't load further, you just set your settings here.
How to actually start the game and without getting a screen asking for CD?
- No need to mount CDROM at all, just enter your game folder from your already mounted C drive and type any of the two:
lolg -CD .
lolg.exe -CD .
Yes, CASE SENSITIVE, [dash][CD] in caps or -"cd" will give you 'No CD path!', then [space] then [dot/period]
Now the GOG version of the game should start, and you will be in main menu, then you can navigate and set Options further!
Same methods worked both for DosBox and DosBox Turbo on Android, as they are the same.
I would still like to use setup, to set proper sound card..

USB connection works only sometimes on SAMSUNG S4 ValueEdition (lineage-18.1-20210717-nightly-jfvelte-signed.zip)

Hi,
I have installed the last LineageOS 18.1 (Android 11) on a SAMSUNG S4 Value Edition.
I got almost everything working, but the USB connection.
Settings-System-Advanced-Developer Options-Default USB Configuration = File Transfer
Now, if I go in System-Connected Devices and the USB cable is plugged in it should appear OTHER DEVICES - USB connection but it doesn't !!! It actually does appear but only very very rarely and randomly !!!
Please offer feedback, many thanks !
Regards
You set USB-mode to File Transfer ( AKA MTP ): File transfer will change your phone to USB mass storage, allowing you move files between the phone and the other device (such as your computer). To access phone in this USB-mode requires another driver.
Many thanks for the quick reply.
But that was the idea! I want to be able to access the S4 jfvelte internal memory (pictures, docs, etc) from a PC.
My expectation was that when I connect the phone to the PC (Win10) via USB cable I can access the phone from WinExplorer but this is NOT so... only very rarely the phone is shown in Explorer.
Contrariwise when I connect another (real) S4 with the official Android 5 I can always access the phone from the PC.
jwoegerbauer said:
To access phone in this USB-mode requires another driver.
Click to expand...
Click to collapse
Does it mean that one should update the jfvelte USB driver first ?
If YES how can I do this ?
Where can I find the right USB driver ?
On windows PC install the MTPdrive 4.1 app - a trial version - what is attached:
MTPdrive is intended to map devices to a drive letter. It works with all devices that operate in MTP (Media Transfer Protocol) mode.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jwoegerbauer said:
On windows PC install the MTPdrive 4.1 app
Click to expand...
Click to collapse
Done. However I cannot notice any change.
The phone is still not visible in Explorer.
If I start the MTPdrive.exe there is no device detected:
I have just installed the last UBS drivers from SAMSUNG (Samsung-USB-Driver-v1_7_43_0.zip) on the Win10 PC.
The Samsung S4 phone (jfvelte - Lineage 18.1) behaves in the same way, namely the phone is most of the time not accessible from the PC via the USB cable. This looks to be a LineageOS 18.1 jfvelte bug. Any idea if there is a way to talk with the LineageOS developers, eventually to report such an issue ?
Hi,
The topic is solved: it was because the phone screen was locked ! as soon as one connects the USB cable to the phone AFTER unlocking the phone screen it works as expected, meaning one can access the files/pictures etc which are being stored on the phone !!!
Many thanks for all !!!

[Linux] [Plasma Desktop - alpine] pmOS Latest Edge

Important : This is only a test release and should be treated as such. Use this modification at your own risk.
This package was built using pmbootstrap : https://wiki.postmarketos.org/wiki/Installation_guide
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot from the A205F Model. Won't be providing any more.
Check https://kde.org/ for more information about KDE.​
Know before you go -
- Bold text might contain crucial information, so read carefully.
- This DE runs on Alpine Linux.
- It has a partially working KDE Plasma Desktop.
- Working in Linux gives you endless possibilities. You might be able to make those things work that I couldn't.
- You need to have a basic knowledge of Linux Troubleshooting.
What works -
- OTG works, meaning it supports storage devices, mouse and keyboard. Ethernet works with some tweaks.
- SD Card
- Basic programs included in the distro run fine.
- Touchscreen
- Power Button. (Brings up the power menu)
What doesn't work -
- Screen Rotation is broken. So Portrait mode is the only option.
- Every sensor is broken. Including WiFi, Bluetooth, NFC, Camera, etc.. Sound is not supported.
- Volume buttons.
- Any type of SIM & Calling Support is off limits. It is never going to work on this phone, the kernel development is dead.
- Firefox crashes on opening heavy websites.
- Installing themes might break the UI.
---------------------
Requirements -
- A custom recovery, preferably TWRP.
- An SD Card with at least 1 GB of free space.
- A keyboard. Proper On Screen Keyboard isn't included.
Installation Instructions
--------
(only tested on A205F) (might or might not work for others)
--------------------------------
1. Download zip from the link below.
Download Here
(Google Drive)
​2. Take a backup of the BOOT & DATA partition. Internal Storage is going to be erased.
3. Copy the file you downloaded to your SD Card.
4. Boot into recovery and unmount everything except the SD Card.
5. Flash the file like you normally would. Ignore any mount errors.
Default Password :
Username - admin
(if prompts)
Password - 123456
The system partition on your phone stays untouched. But you already know the risks. I won't be providing any troubleshooting help.
Disclaimer -
I didn't code anything in this whole project. It was simply built with the utilities that were available, instructions to build are in the second line of this thread. I was inspired to look into Linux for A20 by this thread. I won't be accepting any criticism since I'm not involved in the development of this project.
And finally, English Is not even my third language. I won't be taking responsibility for a Headache or Eye trauma.
Credits & Sources- @arpio
Kernel Source - https://gitlab.com/arpio/kernel_samsung_a20/-/tree/pmos
PostmarketOS - https://gitlab.com/postmarketOS

[DEV] Thor Flash Utility - The new Samsung flash tool

Thor Flash Utility​This is a flash utility for Samsung devices, made from scratch in C#.
To run this, you must have .NET 7 runtime installed on your computer.
Latest release can be found on GitHub - https://github.com/Samsung-Loki/Thor
This tool was tested and works flawlessly, I'm open for any bug reports.
List of platforms​1) Linux (USB DevFS method)
2) Windows (not implemented)
3) Mac OS (not implemented)
How's it different from Heimdall?​Fun fact: Official Odin for Linux works using DevFS, and people report it working when Heimdall didn't.
1) Is able to do NAND Erase All (aka erase userdata) and erase any partition, given the length.
2) Ability to shutdown and reboot into Odin mode (not supported on every device)
3) Not using a USB transfer library and doing it natively for best results
4) Extended the PIT parser with new information being discovered
5) Can flash directly from an Odin .tar / .tar.md5 archive
6) Works with .lz4 files directly without manual extraction
7) Implemented EFS Clear and Bootloader Update options in Odin
8) Is able to change the sales code of the device
Support me​If you would like to support me and my team, donate here.
We're a team of teens (at age of 14-15) making random projects for fun.
Current list of commands​The up-to-date list of commands can be found here.
Usage guide​A comprehensive usage guide can be found here.
What devices were tested?​1) SM-M205FN/DS from 2019 0x00030000 (Unknown1: 0, Unknown2: 0, Version: 3)
2) SM-G355H/DS from 2014 0x00020000 (Unknown1: 0, Unknown2: 0, Version: 2)
Frequently Asked Questions​1) A fatal error occurred. The required library something could not be found.
This is a Linux Package Mixup, use this as reference.
2) What happened to original Thor (or Hreidmar)
This is a rewrite of Thor written from scratch, so I could implement the native USB communication.
Also, the old codebase was severely flawed in my opinion. I archived it here.
Credits​TheAirBlow for Thor Flash Utility
Benjamin-Dobell for documenting much of the Odin protocol
[reserved]
real
Bro finally revived good old Thor/Hreidmar
@TheAirBlow Thx.
Didn't test it yet but just a hint:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link leeds to wrong version acc to your post #1, or doesn't it?
bmwdroid said:
@TheAirBlow Thx.
Didn't test it yet but just a hint:
View attachment 5938745
Link leeds to wrong version acc to your post #1, or doesn't it?
Click to expand...
Click to collapse
Yeah, that was an accident. It is indeed .NET 7
hello, please help me flash and revive the Samsung a12 (125FN) device.
the fact is that I don 't have a pc (
I only have an arm7 phone )
Heimdall-frontend does not work in Linux Deploy in my device, it cannot flash the super partition.. tell me what else can be done in my situation!??)
ilshatiko1988 said:
hello, please help me flash and revive the Samsung a12 (125FN) device.
the fact is that I don 't have a pc (
I only have an arm7 phone )
Heimdall-frontend does not work in Linux Deploy in my device, it cannot flash the super partition.. tell me what else can be done in my situation!??)
Click to expand...
Click to collapse
This tool could probably be used in Termux or in a root shell if you somehow could install .NET 7 Runtime. But, it does require the phone to be rooted for Thor to be able to access the USB devices connected. And additionally, you need a (first phones USB) to (second phone's USB) cable to connect, or have some adapter to make it work.

Categories

Resources