Related
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.
Okay,
So I played with linux literally once or twice in my life and I never really dig into any deeper than that...
However I am aware / have made bootable Linux OS's in the past on just a normal USB, this was a few years back following some guides.
I have a Galaxy S and I know my computer tries to run the USB driver at boot because if my phone is plugged in the PC stalls at the Lenovo splash screen.
therefore it must be possible for it to run as a normal USB Boot so long as the right image in on the SD card in the phone.
My question is, how?
Any help greatly appreciated, going to start researching but any one with any quick ideas please let me know.
regards,
EDIT, I guess I will need to partition the SD Card, can I do this and not affect the Android OS? I presume it would have to be an external one too?
I guess that you could do it as long as your samsung mounts your SD when you boot your PC.
You could use a tool called UNETBOOTIN to create a USB-bootable version of any linux distro.
I would do this as follow:
- back up EVERYTHING in my SD card to a folder on PC
- run UNETBOOTIN and create a bootable linux on a usb stick
- copy everything from the usb stick to the root of your SD
- restore the files you have backed up earlier
If your Galaxy S mounts the SD card right at the boot of your PC then everything should work.
FYI you will not be able to see what is inside your SD, afaik, since linux will stay in a compressed filesystem image. So you won't be able to access your files on your phone, neither use it via ADB or fastboot.
Hope this has been helpful
Based on that last statement does that mean you cannot save anything on your USB boot versions of linux, since they are image files?
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
This was the 6th post in the thread. I swapped it with the original first, because this one contains the instructions on how to get dualbooting to work.
@brewmeister:
Thanks, I've got it working, since Graiden05 added the support for it. ^^
@f69m:
I'm stalking your thread, ready to pounce once sd cards and linux are supported. If you see a shadow in the corner of your eye, while writing a post in your thread, then that's most likely me.
@Trigger911 and everyone else interested:
It's quite easy now. But takes a while, if you're doing it for the first time. Note that I'm talking about the MicroSD card slot in the tablet. This won't work with the slot in the Dock. Also you need to have your tablet unlocked, a 4.2 Bootloader and a custom recovery, like TWRP 2.5.0.0-42. See the Cromi-X thread in the developer forum:
forum.xda-developers.com/showthread.php?t=2425390
The rootfs is a bit dated. It's xubuntu 13.04. There are instructions on how to create your own roots in the 2nd post of the xubuntu thread in the dev forum. We'll just use the dated one.
Also webdoctors wrote a nice post about just installing xubuntu. There are links to the rootfs, installer script v2.2.9 and the modules needed:
forum.xda-developers.com/showpost.php?p=48947306&postcount=342
Download the installer script and Cromi-X to the internal storage of your tablet.
To get both Cromi-X and xubuntu booting from the sdcard you need to partition it:
Create four patitions on your card. The order is important and don't forget to make a backup! All data on the card will be lost during the process:
1st: vfat (any size you want, there was a technical reason, that the first partition needs to be vfat, but I can't remember)
2nd: ext4 (will be the data partition for your apps and stuff, as big as possible)
3rd: ext4 (system, for cromi-x, 1GiB, more would be a waste of space)
4th: ext4 (rootfs, for xubuntu, at least 4GiB, made mine 10GiB, on a 64GiB card)
Detailed Instructions on how to partition a sd card can be found at the end of the 2nd post of sdbags' Cromi-X thread.
Installing Cromi-X:
Get Cromi-X 5.4 and flash it with the ROM2SD Option selected. Instructions on how to install Cromi-X are in the 1st post.
Cromi-X will use the 2nd and 3rd Partition.
Once the installation is done, reboot and check if it is working. During the boot you will see Penguins and some text below. If at the end of it there's something like "setting up for Rom2SD", then it's working and booting from the card.
Installing xubuntu:
For the next steps I use Ubuntud. It might work on a rooted phone/tablet too, if you use a terminal app, like Terminal IDE or Terminal Emulator. But you might need to use su instead of sudo and use another folder than /media.
Follow these instructions and enter the commands in a terminal. If you want to learn more about what a command is doing type "man" followed by the command, e.g. "man sudo" or "man mkdir":
1. Create mountpoints for the rootfs-partition and the downloaded rootfs-image:
sudo mkdir /media/xubuntu
sudo mkdir /media/rootimage
2. Determining the path of your sd card under Linux. Don't play with this! fdisk you can wreak havoc to your harddisk. The -l option tells fdisk to show you a list of all partitions of storage mediums connected to your pc:
sudo fdisk -l
3. Mount the rootfs partition of the sdcard. Assuming the path to the sd card is /dev/sdd, then the 4th partition is adressed as /dev/sdd4. Change it accordingly:
sudo mount -t ext4 /dev/sdd4 /media/xubuntu
4. Download the rootfs. Use the link in webdoctors post.
5. Extract the image from the file.
6. Mount the image, so you can copy it's content to the rootfs partition on the card. You need to change the path to match your situation. Here I simply downloaded it to my Downloads folder and extracted it there:
sudo mount -o loop /home/<username>/Downloads/xubuntu_13.04.img /media/rootimage
8. Now we can copy the files in the image to our root partition. We use the options -pr, which will (p)reserve access rights, owner, group, etc. and copy (r)ecursivly the contents of all directories in the image:
sudo cp -pr /media/rootimage/* /media/xubuntu/
9. Wait till it's done copying, then unmount both the image and root partition:
sudo umount /media/xubuntu
sudo umount /media/rootimage
10. Put the SD card in the tablet and boot to recovery: Press Volume Down and keep holding it. Press Power for a second and release it, while keeping Volume Down pressed. Once you see three icons, with RCK blinking, release Volume Down and Press Volume Up.
11. Now it's time to flash the installer script. Doing this will enable us to boot xubuntu, but we will loose wifi in Android. We will fix this afterwards. In TWRP chose install, locate the V2.2.9.zip and flash it. The tablet will reboot, show a blue bar and reboot again.
12. You will be greeted by a new bootmenu. Waiting for 10 seconds or hitting 1 will boot xubuntu, pressing Volume Down or 2 will boot Cromi-X. For now we want to boot to xubuntu.
13. On the login screen just hit login.
Fixing WiFi in Android
Now we need the mod_update.zip from Graiden05.
1. Get it from: forum.xda-developers.com/showpost.php?p=47990253&postcount=311
2. Unzip it and open the mod_update.sh file in an editor.
3. The script assumes, that we've installed Android to the internal storage, which we did not. So we need to change a line and point it at the right direction.
In the 3rd line we need to change "/dev/mmcblk0p1" to "/dev/mmcblk1p3". Now the script will mount the system partition of the sd card and not the one from internal storage.
Save and quit.
4. Open a terminal and navigate to the folder containing the script.
5. Run the script by typing:
sudo sh ./mod_update.sh
6. Done! Sit back, relax and enjoy dualbooting your TF300T!
Add swap to xubuntu:
Stop relaxing and get back to work! We ain't done yet. *cracks a whip*
We're gonna add a swap file for xubuntu to use because: "If you don't setup a swap space, programs will randomly get killed when you run out of RAM, which is kinda annoying if you want a stable and fast system." (shamelessly stolen from webdoctors' post)
And because we already got four primary partitions on the card, we can't add another one. We could try using extended/logical partitions, but I'm not sure if those are supported on a card and haven't tried it. The only disadvantage will be, that we can't use the swapfile while running Cromi-X... Or can we? Hmmm, mount the xubuntu partition and simply use the swapfile? Got to think about/try it.
Anyways, a good description on how to setup swap is here: http://www.thegeekstuff.com/2010/08/how-to-add-swap-space/ (again shamelessly stolen from webdoctors' post).
Use the second method and don't forget to add "sudo" to the beginning of every line. Also change the value for count in the dd command according to your needs, e.g. count=512 instead of count=1024 to use 512MiB of swap instead of 1GiB.
Ok, it is possible to use the swapfile on the xubuntu partition while running Cromi-X. I don't know how to make these changes permanently yet, so you'll have to mount the partition (step 3) and activate the swapfile (step 4) on every boot to Cromi-X. Also note that using the card for swap will increase it's wear.
With that said, let's get it on! *dingding*
1. Start a terminal app and get root right. In Terminal Emulator just type "su" and hit enter.
2. Create a directory to mount to:
mkdir /sdcard/xubuntu
3. Mount the xubuntu partition:
mount -t ext4 /dev/block/mmcblk1p4 /sdcard/xubuntu
4. Activate swap. If you didn't follow the guide and created it in another directory or under another name, then you have to change the path accordingly:
swapon /sdcard/xubuntu/root/myswapfile
5. Check that it's working. The first number after swap should be anything but 0:
free -k
6. Done! Stop working and get back to relaxing! *cracks a whip*
Things to note:
Suspend is not working. Don't use or you'll have to hard power down the tablet (pressing power for 7? 10? seconds). This is bad and you don't want do that. Always shut the tablet down, when you're done. Booting to xubuntu only takes about a minute.
Doing a distribution upgrade in xubuntu is not working. I tried and had to use a backup for the rootfs.
I'm not sure if this is related to making the tablet dualboot. But sometimes, when I used Android and put the tablet to sleep for some hours, it won't wake up and the battery in the dock took quite a hit. The cause for this could be anything; The modules used, kernel, a badly programmed app, bug in Cromi-X, corrupted partition, cosmic rays blasting my tablet or the tablet's just like me and doesn't like being woken early.
I can try to build GRIMLOCK based kernel which should make it possible. But there is one problem left to solve - choosing partition to boot certain OS.
Really hope to see this happen can only find solutions for 4.1
try v2.2.9
Try the updated kernel and rootfs from xubuntu thread, if i remember right, data2sd was implemented in v2.2.6 kernel, latest kernel is 2.2.9.
Look at the 2nd or 3rd thread(I think?) on pg 35 of xubuntu thread. Also consider setting up a linux swap partition at the end of your sd card.
Hope you get it working, good luck.
The official MultiROM has quite flexible support for dual-booting different Linux systems, but that is disabled in my early TF300T port due to lack of time. I am currently concentrating on Ubuntu Touch.
If someone is willing to try, I am happy to provide experimental MultiROM builds and some support. All I am asking in return are some howto docs to include in the MultiROM thread.
Sent from my TF300T using Tapatalk
This was originally the 1st post.
Hi,
I am trying to get dualboot to work with Xubuntu and Chromix 5.2a from an external SD-Card.
Since I can't post in the Dev-forum yet, I have to do it here instead of the corresponding thread.
Hardware/Software infos:
My Tablet is an Asus TF300T with 4.2 Bootloader (Asus Firmware WW 10.6.1.27.5 -> Chromix 5.2a Deodexed), TWRP 2.5.0.0, Nvflash enabled, ADB and fastboot access.
There is Chromix 5.2a with _that-v6 Kernel installed to both internal memory and SD-Card (Rom2SD). The Xubuntu rootfs is on the card too.
The card is a Samsung MB-MGCGBEU Class 10 microSDXC Pro 64GB and got these partitions:
/dev/mmcblk1p1 8GB vfat
/dev/mmcblk1p2 40GB ext4, data partition
/dev/mmcblk1p3 1GB ext4, system partition
/dev/mmcblk1p4 10GB ext4, rootfs for xubuntu
Journaling is disabled for the ext4 partitions, to keep the wear down for the card.
Rom2SD requires the first three partitions.
Goal and Problem:
What I am trying to do is being able to boot both Android and Xubuntu from the external SD-Card.
Also I want to keep Chromix on the internal memory as a fallback, in case the card gets damaged/lost/stolen by aliens and misused in weird experiments.
Right now I can only access either Android or Xubuntu from the card, but not the other:
When I flash Chromix 5.2a via TWRP, I can boot to Android from the card but have no access to Xubuntu.
Flashing Graiden05's testV2.2.4.zip from http://forum.xda-developers.com/showpost.php?p=47649660&postcount=265&nocache=1&z=7287232739506702 I can boot to Android from internal memory and Xubuntu form the card.
I know that the installers don't know anything about each other and hope it's only a matter of modifying them or some boot scripts.
Maybe change the installers so they use their own partition and don't overwrite each other. And then extend _that's dualboot method (http://forum.xda-developers.com/showthread.php?t=2501129) to multiple OS on an external sdcard.
Something like: (Note: I've only got some vague ideas about what's going on during installation or booting)
1. Add a 5th partition to the sdcard.
2. Install Chromix with Rom2SD.
3. Change the testV2.2.4.zip to do it's xubuntu magic on the 5th partition and not overwrite the Rom2SD stuff
4. Modify _that's dualboot method to include xubuntu and wait for VolUp or VolDown to select what to boot.
5. ???
6. Profit!
7. ???
8. World domination!
I hope someone can help me with this problem. It would really rock to be able to boot this baby with multiple OS from a fast SD-Card!
nice
glad your up and running and thanks for the details. this would be a good post to reference for those wanting to try this (along with web doctors post in the xubuntu thread) - I would however set up a fifth partition for linux swap and set it up as detailed in the link in webdrs thread. How is cromi running with rom2sd? right now i've got mine set up with cromi on data2sd and xubuntu on internal. all I have is a 16 gb micro and i'm thinking of switching my setup once i get a bigger card. does cromi run any better from the card? anyways thanks again and a huge thanks to all those that have made this possible (graiden, join the realms, fm69, shrdlu and anyone else that i may have missed)
also got to give a huge thanks to sbdags for his awesome cromix rom
brewmeister said:
glad your up and running and thanks for the details. this would be a good post to reference for those wanting to try this (along with web doctors post in the xubuntu thread) - I would however set up a fifth partition for linux swap and set it up as detailed in the link in webdrs thread. How is cromi running with rom2sd? right now i've got mine set up with cromi on data2sd and xubuntu on internal. all I have is a 16 gb micro and i'm thinking of switching my setup once i get a bigger card. does cromi run any better from the card? anyways thanks again and a huge thanks to all those that have made this possible (graiden, join the realms, fm69, shrdlu and anyone else that i may have missed)
also got to give a huge thanks to sbdags for his awesome cromix rom
Click to expand...
Click to collapse
Ah yes right, I forgot about the swap part. Gonna add it.
Performancewise I'm happy with running Cromi-X from card. To be honest, I haven't booted from internal memory for some months now. Then again, it all depends on the card. If you've got a fast one, I'd say give it a try. If it's not fast enough for you, you can just power down, remove the card and the bootloader from the v2.2.9 script will simply boot from your internal memory.
Can somebody help me a little? Because after mod update (on rootfs 12.10 tried also files from installer.tar.gz) I can't start xubuntu
Currently I have latest kernel 2.2.9 from dev thread and CROMi-X. Tried also rootfs for 13.04 but i won't start anyway. Using 12.10 I can at least login to the system.
I partially figured it out. My problem was caused because of wireless kernel modules. I can again run xubuntu but without wi-fi. Unfortunately modules from dev thread doesn't work for me
Does 3G work on tf300TG while in Xubuntu?
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.