My DInc NAND went bad, it became read-only and could not be written to. This is the 8GB NAND that houses /data, /cache, and /emmc partitions.
Tiny came out with a nice little patch for me, to patch custom ROMs in order to use partitions on the physical SD card as /data and /cache. That worked well for awhile, though with an occasional glitch where I'd get random factory resets. Anyway, I don't use the DInc anymore, thinking to fix it with a new motherboard from a cracked screen phone or something and selling it. Probably won't hardly go for anything, but it's not doing me much good sitting around. With that plan in mind, I decided to pull the bad NAND chip just to see how hard that is. Got a new SMD rework station and figured it's something I could goof off with on a boring Saturday morning. It came out without much fuss.
Anyhow, now the phone won't boot CM11 with the NAND chip missing. The phone does try to boot because /boot and /system are on a different NAND chip, but now it's not seeing /data or /cache on the physical SD card, at least that's my guess. I do plan to replace the motherboard, but mainly just curious why it no longer works. Is because of partition order? Because I lost 3 bad read-only partitions, the partition count is now off?
I knew it was possible I'd end up killing my DInc by pulling the bad NAND and I'm not too broken up about it. Mainly just curious why it no longer works, and kind of wondering if it's possible to fix.
Figured out some stuff.
With bad NAND chip removed, MicroSD takes its place as /dev/block/mmcblk0.
In a way, this is kind of good. If I make 3 partitions on MicroSD, I no longer need to use Tiny's patch or a custom recovery to map everything to mmcblk1. I can now use the same TWRP recovery everyone else uses and it recognizes mmcblk0p1 as /data, mmcblk0p2 as /cache, and mmcblk0p3 as /emmc.
Even CM11 and Evervolve 4.4.4 work without any patch and recognizes mmcblk0p1 as /data, mmcblk0p2 as /cache.
However, neither ROM maps mmcblk0p3 to anything. /sdcard, /emmc, /storage/sdcard0, /storage/sdcard1, none of those are mapped to mmcblk0p3.
UPDATE: Figured it out. Had to change /devices/platform/msm_sdcc.3/mmc_host/mmc2 to /devices/platform/msm_sdcc.2/mmc_host/mmc1 in fstab.inc.
just wondering, how are you determining that you have a bad nand chip? are you running any sort of test that can tell you definitely?
I have 3 dincs, 2 that I bought refurbished and used on eBay that seem to have been repaired(the water damage sticker has been tripped). I always assumed that the HTC Dinc was just a weak, limited and terrible phone due to bad 1st generation design. My phones had been prone to rebooting and errors due to the small system app partition. But they have worked reasonably well for me the last 3-4 years.
I upgraded all 3 to the latest evervolv 4.0 version with TWRP 2.6.3 and 2 of the 3 seem to have taken the upgrade well. have the 3rd one constantly reboots when trying to access anything via the play store. The internal 8 gig EMMC card had disappeared from it and also at times, the wifi controller disappears. I down graded it all the way back to Tiny 5-16(which it had run for the last 2 years) and it stabilized for the most part with the EMMC being seen again. Do you think the missing EMMC partition is a sure indicator that the memory on the phone is bad?
Here is the full thread:
http://forum.xda-developers.com/showthread.php?t=2175346
But long story short, I couldn't write to the eMMC chip at all. Not only my /emmc partition was read-only like some people had happen and could fix with fsck_msdos, but my entire eMMC chip, which means /data, /cache, and /emmc were read-only. RUU couldn't fix it, fsck couldn't fix it, and even attempting to remove and rebuild partitions using parted couldn't fix it.
I'm not sure if losing the /emmc partition by itself means the chip is bad. The chip also has the /data and /cache partitions. I'd think if either of those go offline, all your apps will start to FC. Although you did say it constantly reboots, and I think that's possible when /data and /cache go offline. I think mine actually did reboot an awful lot on its own before the eMMC chip went completely bad. You might try running e2fsck -c to check for bad blocks.
Related
Here's the story, Please read. I don't think anything like this has happened to anybody else...
Running CM6.02, unrevoked forever (s-off)
Using my 8GB SDHC card from my old phone (It's about 2.5 yrs old)
Over the past few weeks the SD card will randomly go corrupt, I can't recover data and must format it.
SD card went corrupt again 2 days ago. This time it refuses to format. I tried formatting it in the phone, and 2 laptops, no go.
I ordered a new SDHC (class 6) from newegg and it's in the mail. I don't have any other SDHC cards to use.
In the meantime, today the phone was acting weird so I decided to reboot it. The phone gets to the CM6 boot animation andd gets 2/3 through it and then it loops over and over, never getting into android OS.
Did a battery pull, removed SDHC card completely and it still won't get past the CM6 boot animation.
OK... so I go into bootloader and perform a "CLEAR MEMORY" in hopes to get the phone to boot into CM6.
NOW the phone doesn't get past the lock screen, it just sits there forever.
Another battery pull.
Getting desperate and I go into clockworkmod and hit "clear data/cache" and it pops up lots of errors that it can't mount the internal volumes!!!
Is this a very bad sign, wtf have I done and is there anything I can do to get it to work without a SDHC card??
I have seen something like this before. Here is a useful link
I wouldn't be to worried about it at the moment. You might have a brick till you get a new sdcard, but once your new one comes in the mail you should be all set. If your still having issues after you get a new sdcard then you might have problems.
Is it possible to install any rom or the RUU without a SD card? I won't have that SD card for days......
For whatever reason now instead of showing the Dinc splash screen it goes straight to FASTBOOT. It looks like bootloader but has options:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
wth?
A friend let me borrow his SD card. I flashed a new rom on my phone through clockworkmod. Everything appeared to go fine, no errors. Reboot phone and it is still stuck on the HTC splash screen.
How do I rebuild the internal partitions through ADB using parted?
I was able to format 2 of the partitions and now I can atleast wipe data/factory reset without errors. When I wipe dalvik cache though I get an error:
Code:
E:Can't mount /dev/block/mmcblk1p2
(file exists)
Dalvik cache wiped.
Loaded a rom (ruby) and it still doesn't get past the splash screen.
parted shows 3 partitions, I only formatted the first 2
Code:
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary
2 797MB 1007MB 210MB primary
3 1007MB 8095MB 7088MB primary fat32 lba
(parted)
Should I try formatting the third?
I fixed it, phones working now.
wouldn't you think it might be potentially useful to tell people what the problem was and how you fixed it, should somebody else run into the same issue?
just sayin...
cosmicjoke said:
wouldn't you think it might be potentially useful to tell people what the problem was and how you fixed it, should somebody else run into the same issue?
just sayin...
Click to expand...
Click to collapse
yea but it seemed like a one sided conversation in here so obviously not too many ppl cared
I was glad to see that the Cyanogenmod link helped you.
Funny enough
Long time "researcher" here on xda, keeping up with trends and techniques. Took the plunge and tried some roms this week after deciding to root it and go figure I get stuck unable to mount that 3rd partition.
Would have been nice to know what you did to get it to work. Guess I'll continue the search of google. It's funny that most people have issues with the first two storage mounts - teacher's always said I took the path less traveled. Damn!
Are there any roms or other easy ways to increase the size of the partition /data/data on the Droid Incredible? To this day, all I really find are ways to save space in there. That's been covered - everything from Cachemate to not using certain apps. I want to know if there are any roms out there that use space from internal or other areas and reroute them so that /data/data shows more space. Any help would be appreciated.
+1
I've run into this a lot lately. Even my Eris never had this problem.
enigmatl said:
Are there any roms or other easy ways to increase the size of the partition /data/data on the Droid Incredible? To this day, all I really find are ways to save space in there. That's been covered - everything from Cachemate to not using certain apps. I want to know if there are any roms out there that use space from internal or other areas and reroute them so that /data/data shows more space. Any help would be appreciated.
Click to expand...
Click to collapse
No roms do it currently. But its probably doable.
Sent from my ADR6300 using Tapatalk
There is an app on the market called Notenoughspace. I have never used it, but it is supposed to take stuff out of your data/data, and insert it somewhere else. I here it is tricky, so be careful if you use it. I really don't know much about it. The first couple of times I ran into this problem it drove me crazy. Have you read all of the threads for what causes this? Stay away from Facebook. If you sync contacts in Facebook it can cause this. I am a crackflasher, so I rarely run into the problem. I don't think that a Rom can fix this, but I am a newb myself. Really just wanted TP help since I saw your disgruntled post in the developers section....good luck
Thanks for the reply. But here's the thing. Please let's not go into the likes of notenoughspace and cachemate and whiping out facebook. This is what people say in EVERY thread on this from the beginning of the droid incredible.
I'm not looking for a solution that at best can let an extra app or 2 get installed on the droid incredible. I'm looking for a way to INCREASE the size of the /data/data partition by way of taking some unused space from other areas like system or cache or better yet, from that pointless internal storage (for all the SD card users).
There is a lot of extra space on these phones. Thus it is nonsensical to have a measly 150mb to use in that area.
AS this phone is for a friend (and I generally do the upgrading or fixing), I do not experience this on my photon nor do I experience it on my Iconia tab. There was a limit for /data/data on my evo but it was about twice the Droid Incredible I believe.
So this most likely has to be a partition issue. Is there really no fix for it? Since it's not a hardware limit, I'm surprised as I've seen some out of this world ROMs for the device (like Skyraider's which I hoped would make it to the Evo when I had that).
enigmatl said:
Thanks for the reply. But here's the thing. Please let's not go into the likes of notenoughspace and cachemate and whiping out facebook. This is what people say in EVERY thread on this from the beginning of the droid incredible.
I'm not looking for a solution that at best can let an extra app or 2 get installed on the droid incredible. I'm looking for a way to INCREASE the size of the /data/data partition by way of taking some unused space from other areas like system or cache or better yet, from that pointless internal storage (for all the SD card users).
There is a lot of extra space on these phones. Thus it is nonsensical to have a measly 150mb to use in that area.
AS this phone is for a friend (and I generally do the upgrading or fixing), I do not experience this on my photon nor do I experience it on my Iconia tab. There was a limit for /data/data on my evo but it was about twice the Droid Incredible I believe.
So this most likely has to be a partition issue. Is there really no fix for it? Since it's not a hardware limit, I'm surprised as I've seen some out of this world ROMs for the device (like Skyraider's which I hoped would make it to the Evo when I had that).
Click to expand...
Click to collapse
I have had the same problem, and I haven't seen any roms that come close to solving it. And there is no quick and easy solution.
The best work around I could find was to mod the stock rom and add Dark Tremor's APP2SD, and use notenoughspace.
With dtapps2sd you have to partiton the SD card so that you have a ext3 partition on it that can be mounted and apps can be ran from it. It does this for /data/app and a couple of other folders.
Notenoughspace will let you move folders in /data/data to the sd partition that dtapps2sd has mounted, and that survive through a reboot. The extra partition option is what you would use, not the NES partition.
Using this work around I have about 300 apps on my phone, and about 70mb free in /data/data.
My Android version is GB 2.3.4 (build 4.06.605.3).
enigmatl said:
Are there any roms or other easy ways to increase the size of the partition /data/data on the Droid Incredible? To this day, all I really find are ways to save space in there. That's been covered - everything from Cachemate to not using certain apps. I want to know if there are any roms out there that use space from internal or other areas and reroute them so that /data/data shows more space. Any help would be appreciated.
Click to expand...
Click to collapse
Bootmanager will install the whole rom on /sdcard or emmc storage and as an added bonus, /data and /data/data are all in one image so you have shared space. By default you have 950 MB to share for apps and app data. As an added bonus you have the ability to boot multiple roms and have them all loaded at once. It's available on the market and the devs who made it are awesome. However it costs a few dollars.
If you don't want to go that route then it's possible to create an image on the sdcard or emmc and symlink it to /data/data and you could set the size of the file. Then the ramdisk would need to be modified and maybe a couple of things done on the rom. You asked for an easy way and this is one but not easy though. Bootmanager is pretty easy though and no coding changes need to be done to the roms and it will leave your original rom intact.
I've been wondering about this as well.
I've tried a couple different approaches, and ended up sticking with one: it takes some setup overhead for every ROM I install, but it helps a lot.
I ended up deleting the datadata mount from init.inc.rc in boot.img (get ROM, unpack, edit init.inc.rc, repack, flash), and booting in recovery mode to move the data from ([email protected])/ over to (mmcblk0p1)/data (which is now just a subdir on the 768MB /data partition.)
Initial tests repartitioning mmcblk0 (houses /data, /cache, and /emmc) to make /data larger for this purpose didn't work out well: the bootloader rewrites the MBR/partition table when it finds that they don't match metrics it likes. /emmc can not really be reformatted because the bootloader updates some bits that it expects to be FAT32 on boot time as well, corrupting other filesystems.
Why on earth HTC would ship a phone in this day and age with such a crippled storage layout is beyond me.
DHowett said:
I've been wondering about this as well.
I've tried a couple different approaches, and ended up sticking with one: it takes some setup overhead for every ROM I install, but it helps a lot.
I ended up deleting the datadata mount from init.inc.rc in boot.img (get ROM, unpack, edit init.inc.rc, repack, flash), and booting in recovery mode to move the data from ([email protected])/ over to (mmcblk0p1)/data (which is now just a subdir on the 768MB /data partition.)
Initial tests repartitioning mmcblk0 (houses /data, /cache, and /emmc) to make /data larger for this purpose didn't work out well: the bootloader rewrites the MBR/partition table when it finds that they don't match metrics it likes. /emmc can not really be reformatted because the bootloader updates some bits that it expects to be FAT32 on boot time as well, corrupting other filesystems.
Why on earth HTC would ship a phone in this day and age with such a crippled storage layout is beyond me.
Click to expand...
Click to collapse
That doesn't sound too difficult (i moved CM7 from emmc img to the actual phone partitions so that should be pretty simple). The only downside is you do lose space for apps (easily solved with apps2sd). I haven't seen you around since you posted your idea for multiboot. Been busy?
Well, the emmc method would be a loopback image which would not touch the fat32 filesystem.
Or if you're doing nightlies for instance once you mod the boot.img just add it to each new nightly.
Would Conap's dual boot work the same way? I am comfortable with this, and all the coding is intimidating for this newb. Would one of you smarter members put out a small guide as to exactly how to do this. I know it is time consuming, but it would really be worth it to us low lifes. Thanks
How can you do this?
DHowett said:
I've been wondering about this as well.
I've tried a couple different approaches, and ended up sticking with one: it takes some setup overhead for every ROM I install, but it helps a lot.
I ended up deleting the datadata mount from init.inc.rc in boot.img (get ROM, unpack, edit init.inc.rc, repack, flash), and booting in recovery mode to move the data from ([email protected])/ over to (mmcblk0p1)/data (which is now just a subdir on the 768MB /data partition.)
Initial tests repartitioning mmcblk0 (houses /data, /cache, and /emmc) to make /data larger for this purpose didn't work out well: the bootloader rewrites the MBR/partition table when it finds that they don't match metrics it likes. /emmc can not really be reformatted because the bootloader updates some bits that it expects to be FAT32 on boot time as well, corrupting other filesystems.
Why on earth HTC would ship a phone in this day and age with such a crippled storage layout is beyond me.
Click to expand...
Click to collapse
Wow, that sounds like a great idea. Like the above poster, can I also ask if someone who knows how would write up some instructions on how to to this? It certainly would be appreciated by many! With Gingerbread, there's not much Incredible users can do about the tiny /data size. Thanks!
I'm encountering this issue with 384MB of phone storage free and nearly 4GB of SD free. When I checked, I only had 14.5MB free in /data/data. 150MB for this is ridiculous! I would appreciate any fix, preferably one I can set and forget (don't want to have to constantly move or create symlinks for ever new app I install).
possible fix
You should check out jermaine151's Stock+ version 2.1. http://forum.xda-developers.com/show....php?t=1260994. I can't personally vouch for it as he just released it and it's a little late to start reinstalling everything, but it looks promising.
I recently have been reading about the EMMC corruption encountered when flashing ROMs with an ICS based kernels. I've been flashing the different leaked ICS ROMs since they started being leaked and have never paid any attention to the EMMC corruption issue. I've never had any trouble flashing the different leaked ROMs and my phone has always worked fine. However, after reading about this issue I decided to see if I was affected. Problem is I have no idea how to tell for sure if I am. My phone shows the following total capacities:
System storage: 1.92GB
USB storage: 11.50GB
SD card 29.71GB
What I don't quite understand is that my phone has a total of 16GB built-in storage capacity. I'm assuming that System storage accounts for 2GB. That would leave 14GB left for USB storage? Concern is that there is only 11.50GB of storage which means that there is 2.50GB of storage missing and/or has been effected by EMMC corruption???
OR
USB storage is only 12GB instead of 14GB and the remaining 2GB that appears to be missing isn't really missing but rather some sort of reserved system storage that the system uses and I can't touch? If this is the case then I presume that I've probably been very very lucky and somehow not fallen victim to the EMMC corruption that others have?
Does anyone know the answer to my concern?
Not another of thesr threads. Use custom kernels by agat or chris41g and you will mot brick. Simple as that!
Sent from my SPH-D710 using xda premium
There is an entire thread (or two) here about the eMMC issue. And another sticky about how not to brick your device. Take the time to read them.
Chainfire has an application which can tell you if your firmware is susceptible here http://forum.xda-developers.com/showpost.php?p=27014974&postcount=1 I will bet it is.
SO if you are going to flash anything use the latest safe kernel from Agat and Chris41g. They have removed the offending code from the newly relesed kernel source.
Goog luck.
StoverA said:
Does anyone know the answer to my concern?
Click to expand...
Click to collapse
You don't have the issue. Your 16GB is being used as internal SD, /data partition, /system partition, /cache partition
Also when you format, you lose capacity for the filesystem metastructures.
You will know quite easily if you have the problem. If you factory reset, it will start hanging and if you try and flash a full rom it will hang on data.img or factoryfs.img.
BTW it isn't corruption in the sense that the filesystem locks out bad sectors. It is corruption in the sense that whenever the bad sectors are accessed, even just to scan for bad sectors, the phone completely locks up.
Thank you Sfhub.
sfhub said:
You don't have the issue. Your 16GB is being used as internal SD, /data partition, /system partition, /cache partition
Also when you format, you lose capacity for the filesystem metastructures.
You will know quite easily if you have the problem. If you factory reset, it will start hanging and if you try and flash a full rom it will hang on data.img or factoryfs.img.
BTW it isn't corruption in the sense that the filesystem locks out bad sectors. It is corruption in the sense that whenever the bad sectors are accessed, even just to scan for bad sectors, the phone completely locks up.
Click to expand...
Click to collapse
Thank you for answering my question. I could not account for the missing 2GB of storage and now I know where it is. Until yesterday I had not bothered to read anything about the EMMC issue. Then I spent most the evening reading about the issue and have concluded that I have been extremely fortunate. I think I have flashed every ICS leaked build that has been leaked.
I was however not careless. For starters, I used only sfhub's leaked ICS stock rooted builds. And I've used only Agat and Chris41g based kernels. Additionally I used a specific process each time I installed a new leaked ICS build.
Thank you Sfhub for all the work that you do. I am a big fan of yours and appreciate you. Additionally, I want to also Thank Agat and Chris41g for their work as well. These three are a huge asset to the Epic 4G Touch community!
I know I'm late to the party and this was probably already discussed, but I couldn't find it with search. Has anyone considered converting the inc to a data media device (http://www.xda-developers.com/android/what-is-a-data-media-device/)? I've seen this done with other devices (e.g. hp touchpad). I'd be nice to be able to use the EMMC partition for storage and data. I know there is ext4all but I still seem to run out of space quickly since dalvik-cache is half of /data.
Not sure if hboot will let you combine partitions to do what you want; however, lvm can probably accomplish what you're hoping to achieve but it takes quite a bit of effort to setup.
Sent from my One using Tapatalk
I wasn't necessarily thinking we need to combine any partitions. Just don't mount the existing /data and /data/data partitions, and mount the EMMC partition as /data with an emulated sdcard at /data/media. I think this is how the Samsung phones work; you have both "internal" and "external" sdcards. Seems like it should just be some config changes and maybe a recovery that is datamedia aware so you don't erase the emulated sdcard when wiping data.
Smells like a project. I'll see if I will get around to this but this sounds doable.
No promises but my Inc could get bricked and I wouldn't cry over it so I can take a few risks.
Sent from my One using Tapatalk
I've only done a little research so far, but it seems like you'd only need to change a few configuration files. I don't think you could truly brick your Inc, could you? I'm tempted to try and get it working myself but I can't risk bricking my dd.
Sent from my ADR6300 using Tapatalk
ive got 2 incs so I dont mind messing with it, I have a touchpad tho and from what I know (I am decent friends with invisiblek and he does work on the touchpad) the only real difference, is re-partitioning your internal and setting the device tree to mount data as data/media instead of for say /data or /data/data
I have a TouchPad too. Finally made the leap to kk and datamedia there which is what got me thinking about the Inc. The repartioning done for the TouchPad was too make the data partition larger since it now holds both apps and sdcard data. We shouldn't have to do that for the Inc since we already have a partition with 6.6 gig available. Nothing is mounted at /data/media, it's just another directory on the main /data partition. That's why you need a special recovery that "wipes" data instead of formatting...
I've been looking at the changes milaq made. I assume invisiblek did something similar if not the same.
Sent from my ADR6300 using Tapatalk
natediggity said:
I have a TouchPad too. Finally made the leap to kk and datamedia there which is what got me thinking about the Inc. The repartioning done for the TouchPad was too make the data partition larger since it now holds both apps and sdcard data. We shouldn't have to do that for the Inc since we already have a partition with 6.6 gig available. Nothing is mounted at /data/media, it's just another directory on the main /data partition. That's why you need a special recovery that "wipes" data instead of formatting...
I've been looking at the changes milaq made. I assume invisiblek did something similar if not the same.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
A fancy flashable script to convert your boot.img to use /data/media should be possible. So far I told it to switch to mmcblk03 from 01 for /data so it's 6.6GB. The other part is relocating fuse to use /data/media for the internal storage instead of /emmc. That should be somewhat easy to change but a bit harder to script.
/data/media was designed for devices that don't have an sdcard slot which the Inc does have so this is more of a proof of concept idea for me than actual utility.
Ok, the last part is recovery and the current recovery images appear to be large enough to make the recovery build part fail. I'm not sure the actual recovery partition size on the inc but the images come to be about 4.5 MB and fail.
zachf714 said:
ive got 2 incs so I dont mind messing with it, I have a touchpad tho and from what I know (I am decent friends with invisiblek and he does work on the touchpad) the only real difference, is re-partitioning your internal and setting the device tree to mount data as data/media instead of for say /data or /data/data
Click to expand...
Click to collapse
/data/media uses fuse on an existing ext4 partition so the recovery as nate said has to be told to wipe /data instead of format (in other words, using an rm command and excluding /data/media).
This makes filesystem corruption harder to fix since the partition can't be wiped from recovery normally unless it's a format which TWRP does have an option to format /data.
tiny4579 said:
A fancy flashable script to convert your boot.img to use /data/media should be possible. So far I told it to switch to mmcblk03 from 01 for /data so it's 6.6GB. The other part is relocating fuse to use /data/media for the internal storage instead of /emmc. That should be somewhat easy to change but a bit harder to script.
/data/media was designed for devices that don't have an sdcard slot which the Inc does have so this is more of a proof of concept idea for me than actual utility.
Ok, the last part is recovery and the current recovery images appear to be large enough to make the recovery build part fail. I'm not sure the actual recovery partition size on the inc but the images come to be about 4.5 MB and fail.
Click to expand...
Click to collapse
Check my device tree, I have a commit on omni that compresses recovery a bit more and I use it to build
Sent from my SCH-I535 using Tapatalk
tiny4579 said:
A fancy flashable script to convert your boot.img to use /data/media should be possible. So far I told it to switch to mmcblk03 from 01 for /data so it's 6.6GB. The other part is relocating fuse to use /data/media for the internal storage instead of /emmc. That should be somewhat easy to change but a bit harder to script.
Click to expand...
Click to collapse
I don't need a flashable script unless it's required. Personally, I'm fine just building a new system image and flashing that.
tiny4579 said:
/data/media was designed for devices that don't have an sdcard slot which the Inc does have so this is more of a proof of concept idea for me than actual utility.
Click to expand...
Click to collapse
datamedia can be used in conjunction with sdcards. This is what the new samsung phones do. I thought the HTC One did as well, but I just remembered it doesn't have a sdcard slot. If you haven't already, check out this page: https://source.android.com/devices/tech/storage/config-example.html. Our config would be similar to the Xoom's.
It is happened just now. I've a maguro with a fresh UA 7.1, no-gapps, magisk, and f2fs-formatted /cache and /data. Also, few days ago I've replaced ducatti.bin with one from official stable firmware. Now my Nexus worked flawlessly for 5 days after flashing and I was enjoyng the relatively lag-free experience, playing videos and no need for reboot. Eventually I forgot to test the camera (which was always a pain). I've launched the camera, and all was ok until I tapped a shutter button, and my phone rebooted. When it has finished loading I have noticed that all my apps have lost their data and starting like a first time (though all apps present). Furthermore I discovered that all files from /sdcard are gone. I mean, root directories like DCIM is still there, but empty. All settings were reset, but wifi survived and auto-connected to my AP after boot.
Oh ok, I thought, it's the f2fs that is unstable, my emmc is old and this is possible, though I've no such experience until now.
But how it's even possible? /sdcard partition was damaged and wiped by fsck? But /sdcard is mounted inside /data, and placed on the same emmc partition. If that partition has been broken, why all apps still present and running?
Any ideas and advice are appreciated. Should I reformat back to ext4?