[Guide][Android-x86] Mount Internal Windows Partition (NTFS) in Android-x86 - Android General

Mount Internal Windows Partition (NTFS) in Android-x86.
Android-x86 project is one of the new and exciting offshoot of Android platform solely developed by the community. Our Android community has contributed very heavily for the development of Android as one of the most loved platform for both users and the development community as a whole. Custom ROMs such as CyanogenMod, OmniROM, SlimRom, AOKP, Paranoid Android and many more community developed ROM's rock our beloved devices, including latest flagships to aged Legends such as HTC HD2, Motorola Defy(+). One such community developed Android ROM is the Android-x86 Project.
Android-x86 project aims porting the android experience as whole to the x86 architecture platform. This includes our laptops, desktops and x86 based tablets. Although android is a mobile platform specifically developed for phones, tablets and newly introduced wearable devices such as smart watches and Google Glass eyewear, google has not introduced the android as an operating system into the desktop-laptop segment. Google is sticking with its Chrome OS for desktops and is now trying to introduce android app to the Chrome OS. Android-x86 project patches that gap for us.
Android-x86 is like an elixer for our old desktops and laptops wiith lower capability processors and rams, such as pentium and atoms by introducing a modern OS with a lower requirement. It gives those devices a new life. But it is also not perfect yet and has many drawbacks. One such drawback is that it can't mount the internal NTFS partitions of the HDD, in case of the Multibooting Android-x86 with Windows Operating Systems. Many has tried it before but failed. Recently I came upon a chinese website which depicted a process of mounting internal ntfs partitions using a library named mount_nfsd_fuse.
Steps :
1. Download the mount_nfsd_fuse file from the download link provided below or here
2. Place the the downloaded file in the /system/xbin/ folder using a root enabled file manaager, eg. ES File Explorer, Root Explorer and and change to approriate permission.
3. Open Terminal ( If no terminal app installed, download one from Google Play), and obtain Su permission.
4. Mount the NTFS partitions using the code for example :
mkdir /storage/D
mount_nfsd_fuse /dev/block/sda2 /storage/D
format : mount_nfsd_fuse /dev/block/(partition) /(mount point)
5. (Optional) You can automate the process of mounting on boot by adding these lines to the /etc/init.sh file.
6. You can make a Windows style My Computer Icon using ES explorer widget pointing to the mounting folder such as in my example /Storage use it as a my computer alternative for android.
NOTE : All internal HDD partitions are stored at /dev/block/ folder. And so far I have failed mounting C drive , sda1, and sda10 partitions. Feel free to poke around.
Disclaimer : I'm note the developer of this tool and i take no responsibility for any damages caused.
Download : http://www.jemshi101.tk/tools/android-x86/mount_nfsd_fuse.zip
Ref : http://tieba.baidu.com/p/2094586835

[Guide][Android-x86] Mount entire Hard Disk Space using Gparted in Android-x86
The best way to install Android-x86 on any PC is using Gparted. You can download Gparted ISO from it's official site and then write the iso into a USB drive. Now boot from USb drive and then format the newly created partition to ext4. I have found a post related to this on a site called Techposts, you can search this site on google.
Once the partition is formatted to ext4, you can write Android-x86 ISO to USB drive and then follow the installation. The installation on ext4 is differtent so follow the guide to understand how to do it. This way you can get rid of error 17 and also you get the entire partitioned disk space and use it to store files while using Android OS on PC. Below are the screenshots of installtion using GParted!!
All the Best!!:good:

/sys/kernel/debug/ i believe is d...
§Glass<^>Rain§2

checknmater said:
The best way to install Android-x86 on any PC is using Gparted. You can download Gparted ISO from it's official site and then write the iso into a USB drive. Now boot from USb drive and then format the newly created partition to ext4. I have found a post related to this on a site called Techposts, you can search this site on google.
Once the partition is formatted to ext4, you can write Android-x86 ISO to USB drive and then follow the installation. The installation on ext4 is differtent so follow the guide to understand how to do it. This way you can get rid of error 17 and also you get the entire partitioned disk space and use it to store files while using Android OS on PC. Below are the screenshots of installtion using GParted!!
All the Best!!:good:
Click to expand...
Click to collapse
This doesnt mount the entire Hard disk, just the partition in which you have installed the OS

Sparshkr said:
Can you explain Step 4 in detail please? "D" stands for what in step 4? and how to determine in which partition windows is installed?
Click to expand...
Click to collapse
Here the D stands for a custom folder in /storage to mount the corresponding partition in the hard disk.

I've Managed to mount the partition. but the media files inside cant be played for some reason while copying them to android's storage makes them play. any ideas?

checknmater said:
The best way to install Android-x86 on any PC is using Gparted. You can download Gparted ISO from it's official site and then write the iso into a USB drive. Now boot from USb drive and then format the newly created partition to ext4. I have found a post related to this on a site called Techposts, you can search this site on google.
Once the partition is formatted to ext4, you can write Android-x86 ISO to USB drive and then follow the installation. The installation on ext4 is differtent so follow the guide to understand how to do it. This way you can get rid of error 17 and also you get the entire partitioned disk space and use it to store files while using Android OS on PC. Below are the screenshots of installtion using GParted!!
All the Best!!:good:
Click to expand...
Click to collapse
This article was not to share how to make a bootable or infact install the Android-x86 on any PC. It was meant to share the knowledge how to mount an internal NTFS drive after installing Android-x86 using the terminal or any other methods available.

Sparshkr said:
Can you explain Step 4 in detail please? "D" stands for what in step 4? and how to determine in which partition windows is installed?
Click to expand...
Click to collapse
This article was not to share how to make a bootable or infact install the Android-x86 on any PC. It was meant to share the knowledge how to mount an internal NTFS drive after installing Android-x86 using the terminal or any other methods available.
Here D stands for D Drive, It depends on which drives you have. It can be D, E or any other Drives

Help
Hi . My screen started to flicker after i mount the partition . I have tried to change the hdd but it still flickers . It seems to me like the problem isn't from the hdd which i install the android x86 . Any suggestion on how to fix this ? Cant even boot to windows . Blue screen appear if i want to boot to windows .

As of androidx86 ver 6, you do not need a tool as one is now built in.
With su permissions, you can do the following to mount a ntfs partition,
ntfs-3g /dev/block/{partition you want mounted, use sda1 style format} {filepath to mount to, must already be created}
This works for me. There is a single space between the source partition and the destination folder paths.
However, to note, I upgraded to android ver 8, and this works for the terminal emulator, but my file explorer apps read the mounted drive as empty. Additionally, creating a folder in that directory "works" in the file explorer, but doesn't show up in the terminal emulator.
Conclusion, android 6 for x86 works fine without additional tools, though 8 still has problems I haven't solved yet.

tnx bro.
it,s really good work bliss os 9. thank u?

Thanks man for sharing the steps. Works on Bliss OS 11.13. Saves a lot of time from having to switch between OSes just to transfer something from the Android partition and the Windows partition.

Related

"Stale NFS file handle"

Hi all
I have all my apps and data moved to the sdcard a while back but my phone crashed and I decided to move only the apps to the sdcard.
I'm trying remove the /system/sd/data folder on the sdcard and keeps getting that error message. How to fix it?
Thanks
This should only happen if an NFS export is mounted to a linux box of some sort, and that export has changed or otherwise become inaccessible.
any idea how to fix it?
i have this problem, i'm not able to delete the data folder beacause of that error. :/
your ext2 partition is corrupted. this happens quite a lot if data is moved to the sdcard. boot up linux and run fsck on the sdcard and that should fix it.
cool. I'll give that a try.
Thanks
I'm having this problem too. Can you provide some basic instructions for how to mount and fix under linux? I have an ubuntu vmware image I can boot to on my windows pc and a usb card reader. Will that suffice?
When you plug the card into an ubuntu box it should automatically mount it as the next available drive. You'll have to figure out what device node the card shows up as, unmount it (umount /dev/<insert device name here>), and then run a filesystem check (fsck /dev/<insert device name here>) on the unmounted card. The utility will report various problems about "inodes" which you will want to say yes to fix. Once it has run through the file system should be in a consistent state and ready for use again.
You run the risk of losing stuff written to the card (which is probably corrupt anyways) when you run the fsck so you may want to take a copy of the data first.
On a side note: I am not sure what the default mount options are listed for moving the stuff onto the sd card in the faqs but I suspect it may help prevent corruption to mount the card on android with the sync option. Though, this will definitely slow writes to the card. It would definitely be a bad idea to remove the card while your G1 is running either way.
equid0x said:
On a side note: I am not sure what the default mount options are listed for moving the stuff onto the sd card in the faqs but I suspect it may help prevent corruption to mount the card on android with the sync option. Though, this will definitely slow writes to the card. It would definitely be a bad idea to remove the card while your G1 is running either way.
Click to expand...
Click to collapse
I was thinking of using the sync option, but then I read this at http://linux.die.net/man/8/mount:
sync
All I/O to the file system should be done synchronously. In case of media with limited number of write cycles (e.g. some flash drives) "sync" may cause life-cycle shortening.
Click to expand...
Click to collapse
Busybox seems to have an fsck command built in, but I don't think all the supporting stuff is there. I'd like to have a way to fsck my ext2 partition while on the go and not near my linux box.
I know that you can't fsck without unmounting the partition and of course it would be bad to unmount the partition with apps on it while the phone is running, but I was thinking it would be nice to be able to boot into the recovery console.
I tried this and attempted to do a fsck on /dev/mmcblk0p2 with the fsck in busybox as follows:
Code:
busybox fsck -t ext2 /dev/mmcblk0p2
But the error I got was that fsck.ext2, which is the actual executable that should be used, isn't there.
What would it take to get this onto the system so that I could boot into recovery and do a quick fsck and then reboot back into phone mode?
I was thinking of using the sync option, but then I read this at http://linux.die.net/man/8/mount:
Click to expand...
Click to collapse
Where flash lifetime is concerned... I agree, this will certainly have some impact. However, the amount of wear concerned really depends on the number of write cycles the particular flash you are writing to can handle, and how good any wear leveling in the memory controller is. Modern flash memory will likely last on the order of years even with tons of writing going on. If all you are moving to the card are the apps, that data will likely be written once (or maybe a few times over the life of an app) and only re-read from that point forward. The caching will eventually commit any data in the buffer to "disk" regardless of how much is actually there. The idea is to line up all the writes so they can be done efficiently. Where ext3 is concerned, the commit interval is 5 seconds by default, I am not sure what it was in ext2 but I imagine it is similar. Ext2 is not really a flash optimized filesystem, but it is readily available on basically any linux distro, and is supported on Android. A better fs for flash drives where write cycles are an issue might be something like jffs2 or yaffs.
At any rate, sd cards are cheap. Why not just throw it away when it starts to die?
But the error I got was that fsck.ext2, which is the actual executable that should be used, isn't there.
What would it take to get this onto the system so that I could boot into recovery and do a quick fsck and then reboot back into phone mode?
Click to expand...
Click to collapse
You would have to compile an ARM6 compatible version of fsck and get it onto the recovery partition so you could run it.
just turn off your phone, pull out the sdcard, boot on a linux os and
then in console type :
fsck -p /dev/your_ext2_partition
Is there any way to clear this error message on a windows xp computer?
Maybe use pargon partion manager, but where do I go to fix it in pargon?
equid0x said:
Ext2 is not really a flash optimized filesystem, but it is readily available on basically any linux distro, and is supported on Android. A better fs for flash drives where write cycles are an issue might be something like jffs2 or yaffs.
Click to expand...
Click to collapse
Hmm... Well, we know that yaffs is supported on Android because that's what the onboard storage uses. So I wonder why the tutorial for apps-on-sdcard suggests creating an ext2 partition? Couldn't we create a yaffs partition on the sdcard and use that instead?
Maybe because yaffs isn't as commonly supported in non-Android partitioning tools (which you would have to use to set up the card initially)?
In any case, if there's no real downside to having the partition be yaffs, how can I go about formatting it as such? I don't recall seeing such an option on gParted or anything, but then again I didn't look that carefully.
So can anyone clue me into how I might add yaffs/yaffs2 support to my desktop linux box? I'd like to try using a yaffs2 partition rather than ext2 to see if I get better reliability, but I need to add support for that filesystem first. Can't seem to figure out how to do that quite yet...
You will likely need to create the partition from the terminal using something like fdisk or cfdisk which will allow you to select the proper filesystem ID. The command for creating the filesystem is mkyaffs. The fstab in android will need to be modified to enable mount of this file system at boot. You will need to install all of the yaffs support tools on a linux desktop to get access to the mkyaffs command.
Yaffs is designed to be used directly on NAND or NOR flash memory (not abstracted through the controller built into an SD card) but it may work anyways. I am not very familiar with the specifics of this particular FS. Most of these flash filesystems are designed to provide a bootable root filesystem for an embedded device.
Yaffs kernel support can be built into a custom kernel with the instructions here:
http://yaffs.net/howto-incorporate-yaffs
Its not likely you will find pre-made packages for any of this in a common distro like Ubuntu. So, you will need to know how to compile it all by hand. A good starting point for a lot of linux info is The Linux Documentation Project at:
http://www.tldp.org/
FWIW I have built homebrew linux based routers for dual ISPs, IPSEC VPN and the like using a lightly modified version of CentOS and 4GB CF cards plugged into an ATA adapter. I used EXT2 on these and they were in production use at a small 13 server farm for a couple of years before being replaced with newer equipment without any failures whatsoever.
I have also used CF cards in small 200Mhz cube PCs as basic web kiosks for extended periods of time without any failures as well.
Under normal usage patterns on a mobile device probably does not require a large amount of writes in the grand scheme of things. I'd say it is fairly likely that your card will outlive the device you are using it in regardless of the filesystem in use.
If you are seeing lots of corruption I would suspect a flakey/failing SD card or some other hardware related problem. It definitely pays to buy high quality flash media. I would also suggest not allowing the phone to constantly run dead if you know things are being written to the SD card, since random power failures during a write to flash can permanently damage the media.

Help: Partition data recovery

I have a 160 gb hard disk on my desktop with windows 7 and puppy linux installed today I wanted to extend the size of my c volume where both were installed, by mistake I converted my c partition to dynamic the os' s weren't booting up - boot mgr was missing, then I inserted my windows xp disc and when I was in the partition part I deleted one partition of 40 gb then it showed me 157gb unallocated space I have not installed windows now as I thought I have formatted my whole hard disk now please anyone suggest a way to recover the data on all other drives
Sent from my A52 using xda premium
prajyotsingh said:
I have a 160 gb hard disk on my desktop with windows 7 and puppy linux installed today I wanted to extend the size of my c volume where both were installed, by mistake I converted my c partition to dynamic the os' s weren't booting up - boot mgr was missing, then I inserted my windows xp disc and when I was in the partition part I deleted one partition of 40 gb then it showed me 157gb unallocated space I have not installed windows now as I thought I have formatted my whole hard disk now please anyone suggest a way to recover the data on all other drives
Sent from my A52 using xda premium
Click to expand...
Click to collapse
Check with google
Backtrack or Kali Linux distributions will boot from USB or CD and come with tools for 'data recovery' that maybe able to help. If the data that you want to recover has been written over by other data; then things can be a little tougher. The best stuff for doing what I think you want to do is going to run in a terminal window not a GUI, so hopefully you're comfortable with the command line
Let me know if I need to be more specific and I'll see about adding better instructions, otherwise, google up some 'forensic data or drive recovery or imaging' software for one of the above suggested distributions and you should be able to recover the important stuff.
Sent from either my SPH-D700 or myTouch3Gs
Debian Kit Install guide for all android devices that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
Or
https://docs.google.com/document/d/1ssVeIhdBuuy8CtpBP1lWgUkG6fR6oHxP20ToYPPw6zI/edit?usp=drive_web
Try loading any linux from usb and download testdisk recovery tool its a cross platform supported program that saved me many times. Google for testdisk and how to use it.Hope this helps.
Sent from my GT-I9505 using xda app-developers app
I'm back from helping someone else with something similar. Had an sdcard go out, saying "damaged sd" and here is how they recovered nearly all the data...
From Backtrack Linux...
dd was able to make a forensic image of the SD card, and testdisk was able to show and save unlinked files from the image file, so we were able to get all her photos and videos back!
http://www.cgsecurity.org/wiki/TestDisk
Click to expand...
Click to collapse
The "unlinked" files when scrolling through should have the first two characters or letters messed up, and the link provided should have directions on how to recover lost data. The thing to do is "dd" as this will make a full copy of everything to another drive, this will alow you to try different methods of recovery on the copy without risking the original drive.
Hope you get it all back
Sent from either my SPH-D700 or myTouch3Gs
Debian Kit/QEMU Linux Install guide for all android devices that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
Now have working Installers for ARM Java 7 JDK + Maptools + jMonkey
In windows , there are many tools
In windows , there are many tools,but in linux ,I dont know much

[Q] Linux Deploy fails at mounting partition

Hey everyone! I'm completely new at both Linux and Android. So this is probably a terrible question, but I can't seem to find a direct answer anywhere on the forum.
I have Linux Deploy on my Droid 2. When I start the setup for a distro (so far it has happened with every one I've tried), it finishes making a file system (ext3), and moves on to mounting partitions, where it fails.
Do I need to partition my sd card somehow? I'm not really even sure what questions to ask or how to proceed.
Try booting a linux live cd with gparted such as the Ubuntu installer.
You should be able to see if the filesystem was created successfully and if the install files were copied over.

Install CyanogenMod 14 x86 on PC Hard-Drive | Android N 7.0 | Dual-Boot

1. Download CyanogenMod 14 x86 ISO file[Developed by Android x86].
2. Download Rufus win App to Create Bootable/Live USB.
3. Insert USB with Minimum 4GB. Below My Rufus Configurations::
# Device : Inserted USB.
# Partition Scheme and Target System type: MBR Partition scheme for BIOS or UEFI.
# File System: (Default).
# Cluster Size : (Default).
# New Volume Label : XXX.
# Format Options:
-> Except "Check devices for bad blocks" Make Tick mark to all.
# 1 Pass
Select ISO Image and then select downloaded CM 14 ISO file.
Finally Click start.
4. After Finishing, Create New/ Separate Partition in PC for CM 14 to be Installed with Minimum of 16GB Disk Size and Format it as FAT32.
5. After formatting, Reboot PC.
6. Boot PC from USB. (To boot Press F10 or Esc. It depends upon your PC).
7. Select Install android X86 to HDD. ( If you don't want to install, just select Run & skip the below all steps).
8. Now In blue-screen Select the Separate FAT32 formatted Partition to Install.
9. Do not Format.( I didn't formatted and it works fine else select ext4).
10. Install Boot Loader GRUB.( It will replaces default Windows Boot-loader).
12. Next it shows up that your are having Windows Partition and asked to create boot item for windows. Select Yes for that else you won't be able to boot into Windows next time.
13. Next Select Skip for EFI GRUB2.(I Skipped and worked for me, I think because I'm having Legacy PC).
14. Then Select Yes to Create Read/Write enabled system directory.
15. Now To create data.img, select yes and then Enter the Size you need for Internal Memory in MBs (1GB-1024MB).
(Note: If you formatted your Drive with FAT32 probably you can't enter more than 2048(2GB). If you want more than 2GB internal, you must format it with NTFS while in Windows Environment).
16. Now Accept Reboot and then Boot Android from GRUB Menu.
17. Thats all . You have Successfully installed CyanogenMod 14 (Android N) in your PC Hard-disk.
Also I Made Video Tutorial in YouTube for Better Understanding. You can Checkout if you don't understand or if any error pops.
https://www.youtube.com/watch?v=mQVzQhqb6N4(TechGeekShan).
Note : If you accidentally deleted the CM 14 Partition, then you can't boot into Windows as because your Boot menu is saved in that partition. It will show
"GRUB Loading.. Please Wait-Error-17" error.
But your Windows & its files are in Safe. To Overcome this problem, you need to Create Live/Bootable USB drive with Windows OS, then repair and then your Windows will be back with No Data Loss.
Watch this Video, If you had experienced this issue
https://www.youtube.com/watch?v=DoXCSrUHWYg
Follow Me
http://facebook.com/techgeekshan
http://twitter.com/techgeekshan
https://www.reddit.com/r/TechGeekShan/
http://instagram.com/techgeekshan/
http://www.techgeekshan.in/
But with fat 32 highest i can go is 4 gb, how to make it go till 32 gb?
Can i use Windows boot loader with EasyBCD to add Cyanogenmod boot entry?
using External graphic card + some errors
I can't boot If I use external graphics card (GTX960/4GB/OC)
It works after I removed graphics card but do you have any solution for this?
computer specs:
I7-6600K
GTX960
Z170 Extreme 4
...
..
.
Also, Many applications stopped after I boot
Lastly, I couldn't use LAN(not WIFI).
Ayan Uchiha Choudhury said:
But with fat 32 highest i can go is 4 gb, how to make it go till 32 gb?
Click to expand...
Click to collapse
Use ntfs with Android x86 to use more than 4 gb.
is an emulator important to installe cynogenmod on PC?
________________________________________________________________________________
iphone 6 plus http://iphon6.fr/
Whats the best way to get google services up on the system after install?
any info about a LAOS 14.1 port?
Error msg data.img
If you can help just tell me what i can do!
msg error: "failed to create data.img"
thx for ever thing!:good:
Keyboard and mouse are not working in the second menu, where I have to select the partition where I want to install Android X86.
Tried with Logitech K400r and wired microsoft mouse.
Hi
...hi,thanks for the awesome tutorial. Please does this particular iso work with 32bit laptops...?!?...and if it doesn't, please, which one does...?!?
I installed this rebooted it a couple of times but i have tried opening the browser app, it froze and 5 min. later i came back seeing my pc turned off.
Tried booting again but at the end of the boot animation i can see the wallpaper for a split second but then it goes back to the boot animation, it does this every 10 seconds. Is my data.img corrupt?
how can i use GAPPS in this rom??
how can i use GAPPS in this rom??
Using NTFS, still space issue
Sands207 said:
Use ntfs with Android x86 to use more than 4 gb.
Click to expand...
Click to collapse
I have 231 GB separate drive space that I am installing CM formatted on Windows to NTFS, however after installing CM, I only have 130 mb free space, when I boot on Windows to check the property of this drive on Windows (on separate partition), it shows up at 230 gb, and my CM partition always complains of low space. Can anyone advise please?

SD Card Mounting error after reboot in Oreo Roms fix

So guys, this is my first time making a thread and so it may not be that perfect so bear with me. In oreo roms, i was constantly having an error of my mount point of sd card changing after every reboot. so i found a fix which is formatting. This post is NOT for the following people :-
1. Who wants to do it without deleting data
2. Who are pros, this is for the 0.1% who can't.
here i am using a pendrive to demonstrate the functions of the usb and it does not include mac os here. only linux and windows.
before reading this kindly copy your data to your computer.
I checked a lil bit with my sd card's and found that the main error for this is more of the fact that current Oreo roms can't properly support exfat and you need to remount them after every reboot. so what do you do, you format it to the some other format.
Prerequisites -
1. sd card
2. card reader
I have personally tested with exFAT, NTFS, FAT32. however i did not try to use ext4 but it should theoritically work. these were the results of my observations which i gave in a table like format. Now how to do this i will tell you in clear steps
FOR LINUX :-
1. install gparted.
Steps for installing are
1.0. open terminal by pressing CTRL+ALT+T
for debian it is :-
1.1 sudo apt-get update && sudo apt-get install gparted
for fedora it is :-
1.1 sudo dnf update && sudo yum install gparted
p.s if it asks for password give it and press enter even if password is not visible
2. Follow the images according to their timings on right hand side corner should work.
In linux exFat cannot be formatted so you MUST shift to windows or mac
FOR WINDOWS :-
Here you cannot READ ext4 pendrive natively, so if your device is windows i would not recommend using ext4.. Again steps are given in the images below just follow them according to their time.
If you want to format your sd card in fat32 but your sd card is above 32 gb, then you can't natively format it. you would need a 3rd party software. i am posting a link to it you can google search it if you want to choose another.
https://fat32-format.en.softonic.com/download
A very poorly made thread. but i hope it helped.
You might want to install exfat-utils and exfat-fuse on debian based systems before you can mount exfat drives :good:
tywinlannister7 said:
You might want to install exfat-utils and exfat-fuse on debian based systems before you can mount exfat drives :good:
Click to expand...
Click to collapse
OH yes yes yes I forgot absolutely.

Categories

Resources