Related to this: I have not tried Win10XPE, but Macrium's recovery media works fine (mounted as a CD-ROM again.) I have a nice collection of isos now so I'm going to stop
Related to this: I have not tried Win10XPE, but Macrium's recovery media works fine (mounted as a CD-ROM again.) I have a nice collection of isos now so I'm going to stop
im having this same issueI am on rooted android
I have created a blank image of 8GB in DriveDroid for Windows 10
But when i connect to my PC, it shows USB device not recognised.
Not showing in device manager or rufus. i tried read only, write as well as CD option
Can someone please Guide or advise here....
How to use it ?The app has not worked for me since pie however this script works for me on pie and q requires root... Assumes bash is installed in /system/xbin/bash change first line to #!/system/bin/sh if you get errors
Download the txt file and ensure it's in your /Download (internal storage) folder. Then download the app Termux from google play store, open the app, type su and the app will ask for superuser permission, grant the permission and type sh /sdcard/Download/mountr.txt
i tried running this and the terminal returnsDownload the txt file and ensure it's in your /Download (internal storage) folder. Then download the app Termux from google play store, open the app, type su and the app will ask for superuser permission, grant the permission and type sh /sdcard/Download/mountr.txt
Working for me on lake with Android 11.
/config/usb_gadget/g1/configs/b.1/f1: no such file or directory
/config/usb_gadget/g1/configs/b.1/f2: no such file or directory
Try typing "cd /" without quotes and then the command again.i tried running this and the terminal returns
im assuming my kernel is missing somethingCode:/config/usb_gadget/g1/configs/b.1/f1: no such file or directory /config/usb_gadget/g1/configs/b.1/f2: no such file or directory
output
rm: /config/usb_gadget/g1/configs/b.1/f1: no such file or directory
rm: /config/usb_gadget/g1/configs/b.1/f2: no such file or directory
ln: cannot create symbolic link from '/config/usb_gadget/g1/functions/mtp.gs0' to '/config/usb_gadget/g1/configs/b.1/f1/mtp.gs0': Operation not permitted
Same output for me After running once, just keep trying again till no errors output (except for the 'rm' ones). works great for me running linux images, i didn't test blank images tho. I have no idea about the 2 devices problem, i had that problem with another device despite the Android Version was compatible(8.1 and 9.0).output
Code:rm: /config/usb_gadget/g1/configs/b.1/f1: no such file or directory rm: /config/usb_gadget/g1/configs/b.1/f2: no such file or directory ln: cannot create symbolic link from '/config/usb_gadget/g1/functions/mtp.gs0' to '/config/usb_gadget/g1/configs/b.1/f1/mtp.gs0': Operation not permitted
doesnt seem to work at all now. really wish ums support wasn't such a mess. at least my lg g3 works perfectly for nowSame output for me After running once, just keep trying again till no errors output (except for the 'rm' ones). works great for me running linux images, i didn't test blank images tho. I have no idea about the 2 devices problem, i had that problem with another device despite the Android Version was compatible(8.1 and 9.0).
I dunno if this project is dead or not but I'm very interested in trying out your modThis project EOL?
I modified original app, working LOS18.1 external SD. If moderator allows, i upload publik stuff.
This disc contains a "UDF" file system and requires an operating system
that supports the ISO-13346 "UDF" file system specification.
2GB limitation kernel patch can be easily found at github , 2GB ISO image support is not a problem any more with a patched kernel .drivedroid is only usable for USB flashdrive emulation, CDROM however is kernel dependent, you may even need to patch your android kernel to accept 2gig ISOs for it to work properly. Not to mention of the kernel limitation of not being able to properly emulate a DVD drive which is basically essential on most ISO files now a days due to UFD extension (which majority of OS, specially Linux dont support in CDROM mode).
so with this limitations
- you cant mount any ISOs larger than 2GB in filesize
- you cant mount any ISOs that is using UFD extension
for the actual testing, yep there's a issue when mounting ISO files in UDF format and when you open it, allyou can see is a single text file containing
but you can actually just make it work if you do unplug/plug back the USB cable multiple times. dumb I know but that fixes it (sometimes), and even if you manage to make the Windows ISO boot from UEFI/BIOS, it will just complain with the drivers or something, which just means that the CDROM emulation went kaput again with the UDF limitation (the unplug/replug USB fix dont work here) so your basically SOL.
tl;dr, Vanilla Windows ISO dont work
but there's a workaround, all you have to do is convert the ISO file from UDF extension into Joliet, with this, the iso file will recognized as a CDROM supported filesystem. but there's a nasty limitation for this, which is the 4GB limit filesize. damn. but luckily install.wim files can be splitted into several parts (this is only a issue on windows 10 and later) and this workaround works just fine. Was able to boot the Windows ISO files (7,8.x,10,11) with a ISO converted from UDF to Joliet and installed the OS successfully.
tl;dr Joliet converted Windows ISO files works just fine
Yes, check whether the image has a partition table usually gives a very accurate indication that the disk is hybrid. To do this (under Linux) use the command:-is there any test i can do todo verify if a ISO file is compatible?
$ fdisk -l myimage.iso
For Linux distributions that are build on a recent version on syslinux you can use the tool 'isohybrid' like this:-what method por spp do you use todo make a compatible file from an ISO format not supported?
$ isohybrid myimage.iso
Ah, well, DriveDroid should show a CD icon next to the USB and locked-USB icons when selecting an image. At the moment only CyanogenMod nightly builds for the i9000 (kernel is named android_kernel_samsung_aries)
Thanks!
Question to all: if you have applied the patches on their kernel, please post it here so others can try it. As far as I know no-one has put such a kernel/rom online yet, except for CyanogenMod nightly for the Samsung Galaxy S.Does anyone know if any of the current Kernels for the Samsung Galaxy S3 have the required patches for the CD-rom support as I would also like to boot a couple of CD's from my phone.
Add "Disable ADB (Android Debugging)" to those instructions. It seems that's the final thing I need to add to DriveDroid to make it work for a lot of people. I've had several reports some Nexus devices stopped working because I fixed DriveDroid to allow ADB (previous versions just disabled ADB without consent). Some devices work with ADB running too (like my phone), but some just won't boot (although they do show up as USB devices on their OS).Got it working. Awesome work dev. Here's a small step by step instructions for those who were noobs like me.
Download slitaz from within the app
Select slitaz iso.
Select S3C1 and F Mass Storage 1
Also enable Usb storage.
Reboot system.
Do the thing with your boot procedure.
And voila, (I hope)![]()