EDIT: Ok, I've located where my problem is. Basically what happens is when I install the Custom ROM it replaces my 2ndInit bootmenu and CWM and it 'upgrades' them. But because it has 'upgraded' them I can no longer mount sd card. I have to reinstall 2ndInit to 'downgrade' CWM and then I can flash again.
Hi there,
A few weeks back I flashed Paranoid Android onto my phone (latest release), however now I have discovered that in recovery mode, my phone can't read or mount the sdcard, i.e. I can't apply updates.
Code:
If I select 'Install zip from sdcard > Choose zip from sdcard' I get:
E:Can't mount /sdcard/
And if I try 'Mounts and storage > mount /sdcard' I get:
Error mounting /sdcard!
I would really appreciate any help on this issue.
Note it was working previously (which is how I installed the ParanoidAndroid ROM) but now my phone can't read the sdcard in recovery. IT CAN READ IT ONCE THE PHONE HAS BOOTED UP.
Try running a chkdsk scan from a Windows machine to check if there's corruption in the filesystem
Sent from my MB526 using xda premium
thekguy said:
Try running a chkdsk scan from a Windows machine to check if there's corruption in the filesystem
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
will do and will post the results, but before I do, would that show anything because the sdcard works fine once the phone has booted up?
Not sure myself, it just eliminates any filesystem corruption as the cause. Also try using another build like quarx to check for this problem
Sent from my MB526 using xda premium
thekguy said:
Not sure myself, it just eliminates any filesystem corruption as the cause. Also try using another build like quarx to check for this problem
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
But I can't flash using recovery, so how would I test Quarx's build? Haven't had time to boot up my windows partition, but I will eventually.
EDIT: Ran fsck on fedora partition (forgot about the command). It came up with this
Code:
fsck from util-linux 2.21.2
e2fsck 1.42.3 (14-May-2012)
fsck.ext2: Is a directory while trying to open /media/CDF2-6BE2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
I've backed up my SDCard and am going to run e2fsck command (will post results) otherwise I'm going to have to reformat it
EDIT 2: Came up with same error. Should I reformat it? As ext3/ext4? What should I do?
My memory card was standard fat32
And I'm no Linux expert but I think you're trying to check for a wrong filesystem, what is your current sdcard format(filesystem)
And I think you should reformat as fat32
Sent from my MB526 using xda premium
thekguy said:
My memory card was standard fat32
And I'm no Linux expert but I think you're trying to check for a wrong filesystem, what is your current sdcard format(filesystem)
And I think you should reformat as fat32
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Code:
/dev/sdb vfat 7856128 1361952 6494176 18% /media/CDF2-6BE2
Now I've checked fsck again
Code:
fsck.vfat /media/CDF2-6BE2/
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
Read 512 bytes at 0:Is a directory
Can you try with Windows? And format to fat32
Sent from my MB526 using xda premium
thekguy said:
Can you try with Windows? And format to fat32
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
will do
EDIT:
Code:
The type of the file system is RAW.
CHKDSK is not available for RAW drives.
OK, Am backing up now. Will reformat as fat32
Ok... So now I've formatted as fat32, tried again, flashed full sbf, re-rooted phone, installed 2nd-init, flashed Quarx's latest build (before wi-fi experimentation builds) and still I have the problem
Sorry for the triple post
I've located where my problem is. Basically what happens is when I install the Custom ROM it replaces my 2ndInit bootmenu and CWM and it 'upgrades' them. But because it has 'upgraded' them I can no longer mount sd card. I have to reinstall 2ndInit to 'downgrade' CWM and then I can flash again.
Any suggestions on how I might be able to fix this?
Probably there isn't any fix, but you could make zip containing the working recovery, and flash it after every rom flash
Sent from my MB526 using xda premium
thekguy said:
Probably there isn't any fix, but you could make zip containing the working recovery, and flash it after every rom flash
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
If you could show me how to do that, I would so extremely grateful
Aparently there was a similar problem with the Defy running the 'official' CM and the wiki documented a fix here: http://oldwiki.cyanogenmod.org/wiki/Motorola_Defy:_FAQ#SD_Card
Do you think that could possibly work for the Defy+?
EDIT: However if I make a .zip file, would that put my phone in bootloop though? Because whenever I reinstall 2ndInit (v2.3) and it 'downgrades' my CWM/Bootmenu it causes a bootloop where I have to reflash everything. If I make a .zip that I flash after each install would it cause the same problem because it's 'downgrading' from the Bootmenu/CWM of the JB CM10 ROM.
I would've made you one, but unfortunately my computer is not working. I think it should be enough if the boot menu folder is replaced by your working set by a flash after every install
Sent from my MB526 using xda premium
thekguy said:
I would've made you one, but unfortunately my computer is not working. I think it should be enough if the boot menu folder is replaced by your working set by a flash after every install
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I really appreciate your help! I guess you could perhaps guide me in doing it, or I could wait till you've got a wroking computer.
So, computer just started working, and I made you a zip
Download the zip to your computer and extract the contents[META-INF and system) folders. Add your working bootmenu files inside the system/bootmenu folder you just extracted and delete the pre-existing text file there. Then add both META-INF and system to a zip(not rar!) and try flashing it. Make sure that the file consists of META-INF and system folders within itself. It should work
IF THERE'S A SIGNATURE VERIFICATION ERROR JUST TOGGLE SIGNATURE VERIFICATION WHICH IS PRESENT JUST BEFORE SELECTING THE ZIP FILE TO FLASH VIA RECOVERY
thekguy said:
So, computer just started working, and I made you a zip
Download the zip to your computer and extract the contents[META-INF and system) folders. Add your working bootmenu files inside the system/bootmenu folder you just extracted and delete the pre-existing text file there. Then add both META-INF and system to a zip(not rar!) and try flashing it. Make sure that the file consists of META-INF and system folders within itself. It should work
IF THERE'S A SIGNATURE VERIFICATION ERROR JUST TOGGLE SIGNATURE VERIFICATION WHICH IS PRESENT JUST BEFORE SELECTING THE ZIP FILE TO FLASH VIA RECOVERY
Click to expand...
Click to collapse
Thank you very much, I'll definitely try this out!
EDIT1: First attempt, didn't work
Trying something again...
EDIT2: Second attempt.... Put phone into bootloop :\
EDIT3: Third attempt... Seems like a bootloop again
So basically it changes the Recovery version (not the bootmenu) and puts it into bootloop :\ however I can flash via recovery.
Try copying only recovery folder from inside boot menu
I'll try to make a zip which first deletes the folder to avoid incompatibilities.
BTW can you enter the boot menu when there's boot loop?
And also try fixing permissions
Sent from my MB526 using xda premium
thekguy said:
Try copying only recovery folder from inside boot menu
I'll try to make a zip which first deletes the folder to avoid incompatibilities.
BTW can you enter the boot menu when there's boot loop?
And also try fixing permissions
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Yeah I can enter bootmenu during bootloop before it starts. I'll retry with the recovery folder only.
EDIT: Wow it worked! Thank you so much I hope you don't mind too much, but if you can modify the recovery slightly that it'd help out a lot and make everything perfect. But I can't thank you enough
I'll upload my working Patch.zip:
If you can do these, that would be amazing: (this is from the working CWM)
1) When I select 'Wipe data/factory reset' it says 'Formatting /data...' and then immediately says 'Formatting /cache...' and when the phone boots up, all my data is there. Now that isn't a problem as such but if I needed to do a clean install that may cause some issues.
2) This isn't a problem, but I was wondering if you could add a printed line whenever I execute the 'Wipe dalvik cache' because it wipes it very fast, but doesn't say anything in the console so I'm not sure if I clicked it or not. Nevertheless when I boot my phone up it says optimising apps which means that it worked.
But yeah only minor things.
Thank you so much
1)I can't modify the recovery, since I'm not really a dev but I can try to make you another zip to wipe data separately
2)Again, that is something coded in the recovery, which I don't know how to alter. Plus, my computer isn't working again(bad ram :banghead: ) so I'm limited to the phone
But are you able at all to wipe data from the custom recovery? Bootmenu? Are both not working?
Sent from my MB526 using xda premium
Related
I flashed http://forum.xda-developers.com/showthread.php?t=1434860 on my HD2 with the correct partitions and MAGDLR update. Now I'm basically sitting in a boot loop in which it doesn't load.
I tried to follow the video in the forum. I successfully apply the ICS zip file but when I try to apply the MAGDLR file afterwards it says:
Installing: /sdcard/update.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
I have tried renaming the zip files several different things, including "update," "update.zip," the original file name and all the like, but I still get the same message. Upon hard resetting and trying the whole process over again, it will occasionally display a different message about E://could not open blah blah. hahaha
Is there anyone that could provide some insight on this?
Try to raise partition size, maybe you have some bad NAND blocks.
Okay, I'm going to try that. I used 256M and 32M for my partitions using CWM. Let's see what happens when I use the next size up.
It didn't work with that size. I'm now trying 512M and 64M.
I didn't see anything mentioned in that post about renaming conventions or anything but could that have something to do with it? I know I'm supposed to delete .zip.
That didn't work either. That seems pretty big compared to the default partition size, should I keep trying larger partitions?
toiletpalms said:
That didn't work either. That seems pretty big compared to the default partition size, should I keep trying larger partitions?
Click to expand...
Click to collapse
You tried flashing a higher partition size clock work recovery?
Sent from my LG-P999 using xda premium
You are doing all wrong. Larger partitions will cause more boot loops because your /data partition will get smaller. Use 190MB for system and 5MB for cache and then see again.
Geek998 said:
You are doing all wrong. Larger partitions will cause more boot loops because your /data partition will get smaller. Use 190MB for system and 5MB for cache and then see again.
Click to expand...
Click to collapse
I used 400 cwm partition and every rom I flashed work and runs perfectly fine... but if it require higher the op would state that... I only left it high so I can go back and fourth between roms. That way I don't have to hook it back to my computer every time I switch rom
Sent from my LG-P999 using xda premium
I've tried every size available in CWM. I don't have the option to choose partitions at 195 and 2. It has presets both smaller and larger available, but not 195 and 2.
toiletpalms said:
I've tried every size available in CWM. I don't have the option to choose partitions at 195 and 2. It has presets both smaller and larger available, but not 195 and 2.
Click to expand...
Click to collapse
At a basketball game... I'll upload my cwm partition when I get home...
Go here and download 400mb http://forum.xda-developers.com/showthread.php?t=898913... after that do your normal wipe as you would install a fresh rom and don't forget to format your system.... flash the 400mb partition then your ics rom. Pm me if need further help...
Sent from my LG-P999 using xda premium
I tried the 400MB partition... the links are not responding? Only loads to like %15 percent and hangs there...
toiletpalms said:
I tried the 400MB partition... the links are not responding? Only loads to like %15 percent and hangs there...
Click to expand...
Click to collapse
Damn... let me check... cause its from multiupload- they been taken down... I'll find one and upload it through my dropbox
Here you go... http://db.tt/r4rgZfEj
Sent from my LG-P999 using xda premium
I'm assuming I need a PC to do that?
toiletpalms said:
I'm assuming I need a PC to do that?
Click to expand...
Click to collapse
yes... you need a higher cwm partition...
Sent from my LG-P999 using xda premium
toiletpalms said:
It didn't work with that size. I'm now trying 512M and 64M.
I didn't see anything mentioned in that post about renaming conventions or anything but could that have something to do with it? I know I'm supposed to delete .zip.
Click to expand...
Click to collapse
Not sure what files you're referring to, and can't see any install video, so can't see what you did there. Not aware of an update that needs to be installed after installing magldr ice. Or what you mean by deleting .zip
If the problem is the initial install, what you should be doing is applying the cwm image (you seem well versed in doing that now), copying the downloaded ics zip as it is to the sdcard, booting into ad recovery (CWM) from magldr, selecting install zip from SD card (I've never seen any need for install update.zip in CWM), scrolling to the ics zip you copied over and selecting it.
If your issue was something else then apologies, but it would help to know what files your working with.
HyT
Toiletpalm ... your confused about partition... what you are doing is partitioning your SD card with the current recovery... that is not going to fix your ice cream boot loop problem... the issue is your current cwm recovery size partition is too small... that is why I upload a higher(400mb) cwm recovery partition to work with ics. And yes what you have to do is unzip the file in your computer and locate the daf file... after locating it put your phone in magldr and select USB flasher... wait for phone to sync with the micro USB cable that is connected to the computer... "USB....USB" once you see that run the daf file and follow prompt.... when done... make sure you have your ics rom in your SD card.... reboot phone into magldr... select ad recovery... do a full wipe... including formatting your system... now install from SD... locate your ics rom and install... then when done... boot your phone normally... first boot will be longer... after that every reboot is quick... email me if you are confuse with any steps... [email protected]
Sent from my LG-P999 using xda premium
Hello
Currently I am using medroid 1.4.3 non hwa version & I want to flash qnd miui odexed version .
So what I do ...
Format data or format system partition or SD card ext 4
Sent from my Nexus One using xda premium
take a nandroid. and yea wipe/format everything atleast 3 times including sd ext. not necessary to format sd fat32 partition.
Sent from my Nexus One using Tapatalk
format system also---------
When i format SD ext & system ..
Any Lost for SD card data
& re partition SD card for app2sd
Sent from my Nexus One using xda premium
no sd card loss
read OP on how his a2sd works, shouldn't have to reformat sdcard itself, a2sd is probably built in, you may have to run scripts to move apps, not sure
Format data 3x,delvik chace format system, format sd-ext then trying to install qnd miui odex rom & getting error...
What should I do ....?
Sent from my Nexus One using xda premium
rugmankc said:
no sd card loss
read OP on how his a2sd works, shouldn't have to reformat sdcard itself, a2sd is probably built in, you may have to run scripts to move apps, not sure
Click to expand...
Click to collapse
Please help me...
Sent from my Nexus One using xda premium
1. doesn't help to not know your error
2. if you are on medroid assume you have blackrose hboot at 220/16/200, MIUI seems ok with that
3. did you read all of OP page and scan thread for tips etc
4. what recovery are you using
5. did you check md5 before flashing
6. if you are bootlooping, pull battery
7. otherwise, pull battery and hold down pwr/trackball and let it boot into bootloader. then boot into recovery, do your wipes again and restore your medroid nandroid
8. last resort--redo your sdcard by formatting with sdformatter (full erase on and size adj on) and repartition sdcard as 1gb 0 swap ext 4
9. back up before you do these things
10. i prefer amon_ra recovery over cwm--although if needed you can flash amon thru rom manager
11. if you are rooted with sdk installed you can fastboot it thru a command window
here is the xda wiki with good info--read/read/read on this stuff
http://forum.xda-developers.com/wiki/HTC_Nexus_One#Installing_a_Recovery_Image
you have enough posts to post in MIUI with SPECIFIC questions about your problem
hope you get it sorted
rugmankc said:
1. doesn't help to not know your error
2. if you are on medroid assume you have blackrose hboot at 220/16/200, MIUI seems ok with that
3. did you read all of OP page and scan thread for tips etc
4. what recovery are you using
5. did you check md5 before flashing
6. if you are bootlooping, pull battery
7. otherwise, pull battery and hold down pwr/trackball and let it boot into bootloader. then boot into recovery, do your wipes again and restore your medroid nandroid
8. last resort--redo your sdcard by formatting with sdformatter (full erase on and size adj on) and repartition sdcard as 1gb 0 swap ext 4
9. back up before you do these things
10. i prefer amon_ra recovery over cwm--although if needed you can flash amon thru rom manager
11. if you are rooted with sdk installed you can fastboot it thru a command window
here is the xda wiki with good info--read/read/read on this stuff
http://forum.xda-developers.com/wiki/HTC_Nexus_One#Installing_a_Recovery_Image
you have enough posts to post in MIUI with SPECIFIC questions about your problem
hope you get it sorted
Click to expand...
Click to collapse
getting error Bad installation
I using 4ext touch recovery
I have blackrose hboot at 220/16/200
Yes i have checked md5 before flashing.
Sent from my Nexus One using xda premium
Try reflashing
rugmankc said:
Try reflashing
Click to expand...
Click to collapse
Can I change recovery....
Which is the best for miui....?
Sent from my Nexus One using xda premium
pk301984 said:
Can I change recovery....
Which is the best for miui....?
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
changing recovery is not needed. and the one which you are using (4EXT) is currently the best out there now.
Sent from my Nexus One using Tapatalk
Heyyyy buddies
I was using ussrv5+kuro kernel 1+ akurodata2sd
Today I thought of uninstalling games and apps cause of 12th board, cet, aieee...
After uninstalling 32 apps...
I open cf3d and uninstalled it my phone rebooted with lots of force closes then it stuck on splash screen
I restored my latest backup
Same fate
Went to internet cafe downloaded DDLF2 odin pack (thanks to sir docky73)
Flashed it and phone booted..
After that restored my backup and wow it booted...
Bt kernel was stock one
My all apps were gone...
So I flashed kuro kernel and again it stucked at splash screen
So I flashed stock kernel
Now all my apps are gone..
They were in 2nd partition
So which kernel should I flash????
And worst thing
I heard a conversation in my cell
Stock Kernel to battery: Babes I am gonna eat you
Battery:noooooooo!!!!! Somebody plzzz save me
Sent from my GT-S5360 using xda premium
Use savies rev 73, the easiest to install and user-friendly kernel yet with very good performance imo..I had problems booting with kuro kernel for some ROMs (having custom kernels), but with savies kernel never had a problem
Merruk Dev 7 would be the best performing kernel out there, but a bit tricky to get it installed..
thats's akuro failure. the phone didn't boot because the data inside ext partition is different with the one used by system. you must delete /data folder inside your sdcard partition to boot up. after that you can copy /data/data into /system/sd/data as usual. if you don't know how to delete /data folder inside your sdcard, the easiest way is reformat your partition.
kurotsugi said:
thats's akuro failure. the phone didn't boot because the data inside ext partition is different with the one used by system. you must delete /data folder inside your sdcard partition to boot up. after that you can copy /data/data into /system/sd/data as usual. if you don't know how to delete /data folder inside your sdcard, the easiest way is reformat your partition.
Click to expand...
Click to collapse
What if I delete akuro script from init.d and make a complete wipe of 2nd partition...
Or
Which partition I should delete???
/sdcard/data or /data/data
P.s. I never moved my /data/data to /system/sd/data
Sent from my GT-S5360 using xda premium
for safety reason you can delete (or copy into somwhere else) all files in your init.d folder and wipe 2nd partition. after that you can move your tweaks into init.d again. this step might a lil bit inconvenient but in this way we could boot up the system succesfully and easily diagnose the problem source.
kurotsugi said:
for safety reason you can delete (or copy into somwhere else) all files in your init.d folder and wipe 2nd partition. after that you can move your tweaks into init.d again. this step might a lil bit inconvenient but in this way we could boot up the system succesfully and easily diagnose the problem source.
Click to expand...
Click to collapse
Going to try it
Edit: it booted yeppie yesss..
Two things sir kuro
1 thanx a lot
2 plzzz give me your brain
Sent from my GT-S5360 using xda premium
Problem2: how to get apps back
Erasing /data/data will work
Sent from my GT-S5360 using xda premium
if you have TBU you can use it to recover your backuped apps
I want to use my second partition so I think I shuld delete useless data in /data/data/
Sent from my GT-S5360 using xda premium
umm...you better don't touch any of them. you can copy /data/data to /system/sd/ to activate dt2sd function and prevent system to write your original /data partition but you'd better don't delete/modify them
kurotsugi said:
umm...you better don't touch any of them. you can copy /data/data to /system/sd/ to activate dt2sd function and prevent system to write your original /data partition but you'd better don't delete/modify them
Click to expand...
Click to collapse
I will try titanium backup to recover apps....
Thanks
Sent from my GT-S5360 using xda premium
Terminal command to wipe 2nd partition plzzz
Sent from my GT-S5360 using xda premium
Code:
su
mount -t extX -o nosuid,nodev /dev/block/mmcblk0p2 /system/sd
note:
1. extX - replace X with your type partition
2. its mmcblk[zero]p[two]
after executing these command you can go to /system/sd then delete all files there. if you don't have any app backup you can move the /app content to your sdcard. in this way you can reinstall all your app later.
Running cm10 night lies. My sdcard will become corrupt unexpectedly.
I just tried to download the latest nightly from 2013-01-27 and the file that is downloaded is 0kb even though it takes about a minute to download.
I can verify it's not the card holder on my nook because if I boot into recovery, I can adb and write a new file or push a file to it without issue. I can even used a recovery sdcard without issue.
I'm thinking this is a problem with cm10 because if I format the sdcard from within the storage menu, it works until my next reboot.
Any suggestions would be helpful
Sent from my NookColor using xda app-developers app
Hi everyone,
I am using CM on SD (latest nightly/latest CMW) and am having a problem with Cyandelta. It works sometimes but many times it bombs and erases the nightly about to be updated and ends with a no file found error.
The built in updater works well.
Anybody have any ideas?
Thanks,
V
volpo222 said:
Hi everyone,
I am using CM on SD (latest nightly/latest CMW) and am having a problem with Cyandelta. It works sometimes but many times it bombs and erases the nightly about to be updated and ends with a no file found error.
The built in updater works well.
Anybody have any ideas?
Thanks,
V
Click to expand...
Click to collapse
You use CWM and SD? I thought that the CWM for nightlies on SD was not working yet.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You use CWM and SD? I thought that the CWM for nightlies on SD was not working yet.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
On an SD card I have CWM 6.0.4.8 and the latest nightly. It runs fairly well on my NC. I'd love to figure out what is happening with Cyandelta. It does work sometimes.
I believe it's your image supporting the whole thing (generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8c.img).
V
leapinlar said:
You use CWM and SD? I thought that the CWM for nightlies on SD was not working yet.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
volpo222 said:
On an SD card I have CWM 6.0.4.8 and the latest nightly. It runs fairly well on my NC. I'd love to figure out what is happening with Cyandelta. It does work sometimes.
I believe it's your image supporting the whole thing (generic-sdcard-v1.3-CM7-9-10-10.1-10.2-11-largest-Rev8c.img).
Click to expand...
Click to collapse
I have been using CWM and the nightlies on SD since about 5/15 with no problems. It installs right from the Cyandelta directory directly. This is handy since leapinlar's sdboot mount trick doesn't seem to persist with an update anymore.
bowguy said:
This is handy since leapinlar's sdboot mount trick doesn't seem to persist with an update anymore.
Click to expand...
Click to collapse
The reason my sdboot trick stopped working for you is the use of CWM to install the updated ROM instead of the script installer. With the script installer the reason it stuck was the script installer does not wipe /system when it installs. It just copies the new /system files over the old /system files. That way any existing /system files that do not come with the new ROM stick. CWM wipes /system before copying the new /system files. That wipes my file that is put in /system/etc/init.d that creates sdboot.
Not that it matters since you successfully use cyandelta, but the solution is to put my 19mountsdboot file in /data/local/init.d and set its permissions to execute.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
The reason my sdboot trick stopped working for you is the use of CWM to install the updated ROM instead of the script installer. With the script installer the reason it stuck was the script installer does not wipe /system when it installs. It just copies the new /system files over the old /system files. That way any existing /system files that do not come with the new ROM stick. CWM wipes /system before copying the new /system files. That wipes my file that is put in /system/etc/init.d that creates sdboot.
Not that it matters since you successfully use cyandelta, but the solution is to put my 19mountsdboot file in /data/local/init.d and set its permissions to execute.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
/data/local/userinit.d ??
That works perfectly. Big thanks. This is really slick on dual boot setups. That directory is visible by both EMMC and SD operating systems.