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?
Related
So I have been playing with android builds for some time now.
I had successfully ran cupcake and donut builds using the HaRET on sdcard method.
(not every time was perfect but worked more times than not)
eclair has been very troublesome. with the introduction of the new installation method.
I have had limited success even getting it to install.
sometimes it would install without a hitch.
other times it wouldn't even get to the install screen.
SO HERE ARE MY FINDINGS.
while installing the latest polymod2.1g eclair build (actually with any version) I was watching the screen messages.
I know they are fast scrolling, but I can usually pic out errors.
I noticed almost every time I installed there were at least a few I/O errors of some kind.
and the times that I tried and didn't get any errors, the build would often install OK.
I obviously have either a crappy sdcard OR the phone is having problems writing to the sdcard.
either way is a problem, being that the new version of installing creates(writes to the sdcard) the system.img
with the installer program ON THE PHONE.
when using the previous android versions (cupcake & donut), the builds came with a system.img that was already built.
only the data.img was needed to be built on the phone.
that lead to fewer if any bad installs.
Now that there is more to write on the phone, its almost impossible to get a stable eclair build.
SO HERE IS WHAT I DID. (being that I am too stubborn to go buy another card yet...)
I first decided to go the route of partitioning the sdcard. (assuming there might be "bad" sectors on the card)
(1) fat32 followed by (2) ext2.
I then tried installing with the new 'install to partitions' options in the installer.
I was still getting I/O errors...
I tried again putting data on partition and system as an img.
still errors...
then data as img and system as partition.
still errors (but it worked)...
I reformatted the ext2 partitions and ran a check. (NO PROBLEMS)
at this point I got a crazy Idea....
ON MY COMPUTER I EXTRACTED THE ANDROIDINSTALL.TGZ AND PUT THE CONTENTS FROM THE SYSTEM FOLDER TO THE SYSTEM PARTITION ON THE SDCARD.
THEN I PUT THE CONTENTS OF THE DATA FOLDER TO THE DATA PARTITION OF THE SDCARD.
still having the andboot folder on the fat32 partition I confirmed the files: HaRET.exe, initrd.gz, zImage-eclair, and startup.txt.
Ran HaRET...
skipped installer...
NO ERRORS>>> INSTALLED>>>>> WORKS!!!!!!!
EDIT: OK, I did have a problem.
I couldn't install any apks. just got message that application was not installed.
first I reboot to installer and tried to fix permissions.
still couldn't install anything...
then I tried installing from market. got error message that there was no room left to install.
then I uninstalled an application and tried to install something else...
still no install...
it Had to be a permission issue. there is more than 50% free space on all partitions.
WENT BACK TO COMPUTER CHANGED PERMISSIONS ON ALL FOLDERS ON THE DATA PARTITION TO RW.(not sure if this is bad???)
and now everything works GREAT!!!!
the only problems are sometimes with the newly installed apps (probably due to I/O errors)
and I just re-install the app and it works.
*********I guess it is time for a new sdcard*******
but for now it is a nice work around.
however, it still doesn't rule out either the installer or the phone itself as the problem.
I will report back if I ever get a new sdcard.
mnjm9b said:
#1
Click to expand...
Click to collapse
This is an interesting approach, copying the files manually instead of using the installer script for that.
I have to say, I have tested with several micro sd cards (class 2,4,6) and I never had any problems with the installer (replimenu 0.9) using ext2 partitions and booting from haret
However, NAND is giving me massive problems still after flashing dzo's or vilord's nbh
After a cold boot, it's extremely slow and getting stuck at several places during the loading process
So I stick with Haret at the moment.
Using class 6 SD memory, the whole process from power on to Android just takes me only 45 seconds, which is working much faster for me than NAND. Another advantage is that the /system and /data mount points are only limited by the size (of the created partitions) of the sd card. I use a 8GB card.
Using Kaiser's internal memory for NAND only gives you 50-80MiB free space left for /data
Update...
I broke my data, which was to be expected.
after I installed a bunch of apps and had problems with many of them.
it finally crapped out on me.
Luckily I backed up my data partition using partimage on linux
so after I re-formated and restored the data partition
everything worked smooth again.
the system partition seemed to be unaffected....NICE!!!
although this time I manually added the apks that I wanted
to the data partition before I put it back in the phone.
they all work great now.
this is way to damn easy...
THANK YOU
every time i go to wipe the dalvik cache this error comes up. its still able to wipe tho. i had aokp flashed and was dling a game when i decided to cancel the download and my phone stopped working. so i restarted it and it bootlooped. so i pulled the battery restarted it and saw this error for the first time. finally got back to my phone, rebooted, still saw it and my phone was acting slow so i restored it using cwm. then i decided to just wipe the phone clean and reflash everything from stock. i still see this error tho. what does it mean?
i would love to know this also, happens to me every time i wipe dalvik.
posted this on reddit and got this answer:
"It's nothing worth getting worried over, and no, you can't fix it. It's a carry-over from older devices (G1 and such) which had insufficient space on /data, so part of their sdcard was formatted using EXT. That space was then mounted as /sd-ext and apps could be installed there, though it was incredibly unstable and not recommended. Newer devices don't need this because they have large /data partitions, and can install apps onto the SD card with Android 2.2 and higher, natively. The /sd-ext wiping is just old code from those days that still exists in ClockworkMod Recovery and its derivatives.
tl;dr, don't worry about it, you can't do anything, it's just old crap from old phones."
so i think its ok, still worried about my phone freezing tho. oh well everythings working fine now if a little slow. but that may be all in my worried, first time flashing head.
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.
Hello Again, I have found a few threads with the same issue but something in the middle is different, this has happened on my Nexus 5 before, and it pissed me off because i never got it resolved.
I want to convert my HTC One M8 ATT to GPE later today, but first i'm on sense with NvROM.
The ROM isn't the issue since it's been working fine for a 2 weeks now, here is the story.
What i did-
Recovery (Wanted to try out CarbonROM)
Flashed LiquidSmooths kernel ontop of Carbon, got "Unfortunately phone has stopped".
Went to recovery again to attempt to flash liquidsmooth only.
E: Unable to mount /data
E: Unable to mount /system
E: Unable to mount /cache
E: Unable to mount /sdcard
E: Wiping /data /system /cache failed!
Now, i rebooted and those errors are non existent i can flash again.
But on LiquidSmooth , The Gallery can not find my Pictures.
The Music app can not find the music anymore.
Whenever i use a File Manager , magically my files are still there.
Anybody got ideas on this one? Thanks.
>Pics related<
Try to connect the phone to a PC, and use Device Manager to format the internal memory. Backup any personal data first, if needed (and if possible).
I've heard that , that causes the eMMc or internal storage to go into Read Only mode?
anyone correct me when i`m totally wrong here.
hasn't this something to do with the so called fused location of your sd-card ?
On my phone the locations of the sdcard is shown different then when i locate them trough recovery or shell.
In android the location is something like: /root/storage/sdcard (internal memory)
the real location in my case was shown in recovery as: /root/storage/emulated/0/
And i think because i had previously installed a cm11 based rom and kernel.
And when i completely wiped my phone for a newly rom, afterwards i still had all my data on my phone, because it didn't wipe the /emulated/0 location.
so all the files are still found with a file manager because the two location i mentioned before are fused. But your apps still has the old location in his settings somewhere..
You can try to do a media rescan so your phone search for new media.... But i believe that is also done when you reboot your phone.
I had that happen to me and I was able to fix it by using the "Format" option in TWRP recovery. That, of course, wipes everything on the device but everything will be mounted correctly and properly again.
Guys, I ended up fixing it.
TWRP format fixes it but i needed a backup. Also first attempt at formatting it on TWRP had issues. E:Can't format , E: Data isn't mounted.
Ended up just going ahead and doing the Google Play Edition Conversion and that fixed the whole issue, Thanks for your time!
@TarekElsakka @djmarkd @redpoint73
i4GS said:
Guys, I ended up fixing it.
TWRP format fixes it but i needed a backup. Also first attempt at formatting it on TWRP had issues. E:Can't format , E: Data isn't mounted.
Ended up just going ahead and doing the Google Play Edition Conversion and that fixed the whole issue, Thanks for your time!
@TarekElsakka @djmarkd @redpoint73
Click to expand...
Click to collapse
so wait, aren't you going to tell us what you mean by it fixed the whole issue? were you able to back up the data first?
I'm having a slightly different (maybe similar) issue.. my at&T m8 was working fine on insertcoin (previously viper/venom) and i decided to try a very stock AT&T debloated rom.
forgot to flash the firmware first, so booted into fastboot, and was going to do that.. but it wouldn't work, gave me an error..
booted back into recovery (TWRP 2.7.0.2) and my internal storage WILL NOT MOUNT. hence, nothing works... I can see microSD files, I can attempt to flash things ,but, due to the internal "sd" (not my microsd, just using old fashioned android terminology) not mounting, every operation fails. interestingly, I can mount / (root partition) and it has the correct structure, and even some vestiges of my files.. when i say mount, i mean in recovery on the device.. not on a computer via USB.
any ideas? i'm stuck
I know i can probably format the /media/data blahblah partition (the internal storage) but I have very important photographs of my best friend's wedding and my children's recent visit to their grandparents'.. so i really really want to restore those files.. I do this kind of thing (file forensics) on OSX, windows, and some linux drives, all the time at work.. I just don't know how to access the storage on an android phone, in order to run the forensics scans etc.
thanks!!
sneef said:
so wait, aren't you going to tell us what you mean by it fixed the whole issue? were you able to back up the data first?
I'm having a slightly different (maybe similar) issue.. my at&T m8 was working fine on insertcoin (previously viper/venom) and i decided to try a very stock AT&T debloated rom.
forgot to flash the firmware first, so booted into fastboot, and was going to do that.. but it wouldn't work, gave me an error..
booted back into recovery (TWRP 2.7.0.2) and my internal storage WILL NOT MOUNT. hence, nothing works... I can see microSD files, I can attempt to flash things ,but, due to the internal "sd" (not my microsd, just using old fashioned android terminology) not mounting, every operation fails. interestingly, I can mount / (root partition) and it has the correct structure, and even some vestiges of my files.. when i say mount, i mean in recovery on the device.. not on a computer via USB.
any ideas? i'm stuck
I know i can probably format the /media/data blahblah partition (the internal storage) but I have very important photographs of my best friend's wedding and my children's recent visit to their grandparents'.. so i really really want to restore those files.. I do this kind of thing (file forensics) on OSX, windows, and some linux drives, all the time at work.. I just don't know how to access the storage on an android phone, in order to run the forensics scans etc.
thanks!!
Click to expand...
Click to collapse
Sorry, but what i did was different, and MIGHT factory reset your internal storage, i can't verify 100%.
You can do two things,
Either flash the RUU
for 4.4.3 STOCK HTC [ATT]
or Flash Google Play edition RUU and revert back to sense which will fix it too.
SENSE: http://forum.xda-developers.com/showthread.php?t=2733523
GPE: http://forum.xda-developers.com/showthread.php?t=2708589
I think I have just screwed up big time.
Here is what happened:
Had CrDroid 8 installed (Android 12) with encrypted storage
Wanted to upgrade to next version; following the guide, simply did a wipe (without any advanced options) in TWRP and then installed the zip
Realized after rebooting that the phone has been completely reset and internal storage shows as empty
I know that this is related to a problem with decryption by TWRP with A12.
My question is, is there any chance that I would be able to recover my lost files? I mean where did they go? What could have happened? Did TWRP just not understand the encrypted data so it threw it away and recreated it, overwriting these files?
Is there any chance that the previous data partition (my internal storage, all my photos, etc) are still somewhere to be found within the storage and I could locate this partition and decrypt it using my passphrase? I am desperate at this point. I am stupid and did not make backups. I thought this would be a regular upgrade, wipe, install ZIP, like I've done dozens of times... Couldn't I perhaps scan the raw disk devices for some magic string or anything that would mark the start of the encrypted partition?
Sorry about the frantic writing, I am devastated and literally begging for any kind of help with this. Thank you.
Sorry for the noise, I was desperate I gave up since then, I just don't think this is possible. As far as I understand the encrpytion keys have been flushed (which are kept in the TEE anyway?). I still don't fully understand why TWRP just decides to wipe /data/media as well as /data in this case, but what is done is done. Back up your data guys. Same old story.