Database Info

When i reboot my phone it wipe all that i saved

Hey guys, i didn't found my problem in other topics, so i opened a new .
So here is the deal, i have the Kisadworx ROM installed now in my Samsung galaxy 3 i5800, and already tried the Kyrillos and both of them have this same issue. When the phone shutdown for low battery, i put it to recharge and when i boot it, it wiped all i have saved. Apps, configs, widgets....just everything. i have no clue why...some one have faced this issue before?
Note: when i enter in recovery mode and try to wipe data/factory reset it shows a message:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/ log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
I don't know if this error is related but ok ....
Plz someone could help me?

I had this issue days ago, and it happened to me while I simply only turned off and on my phone.
This is probably caused by bad data and cache(?) partition or by bad (wrong) filesystem used. Try re-flashing STOCK rom eg. XXJPQ and over it custom rom of your choice. If the problem persists, try flashing custom kernel (g3mod) and convert file systems like this:
stl6 - ext4
stl7 - ext4
stl8 - ext2
I never had any issues with g3mod kernel's recovery with theese filesystems.
In gingerbread ROMs I had never issues with data or recovery.

bielmontes said:
Hey guys, i didn't found my problem in other topics, so i opened a new .
So here is the deal, i have the Kisadworx ROM installed now in my Samsung galaxy 3 i5800, and already tried the Kyrillos and both of them have this same issue. When the phone shutdown for low battery, i put it to recharge and when i boot it, it wiped all i have saved. Apps, configs, widgets....just everything. i have no clue why...some one have faced this issue before?
Note: when i enter in recovery mode and try to wipe data/factory reset it shows a message:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/ log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
I don't know if this error is related but ok ....
Plz someone could help me?
Click to expand...
Click to collapse
Do you have an ext partition on your phone?
I got into similar problems with the scripts related to ext partition long ago
I too get the recovery error and it is not of any problem to us . This is solved by using g3mod kernel

hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys

bielmontes said:
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
Click to expand...
Click to collapse
If u checked ur available memory when u had the problem, u probably had 0.00kb available. Just saying.
Sent from my GT-I9003 using xda app-developers app

bielmontes said:
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
Click to expand...
Click to collapse
If youre going from ROM that uses other filesystems than stock samsung's RFS filesystem such as ext2, ext4, so by flashing the stock ROM causes the bootloop WILL be there. (because the stock kernel doesn't support other filesystems than RFS) You need after flashing stock ROM pull the battery, reinsert it, reboot into recovery by pressing 3-keys combo and then "wipe data - factory reset" in recovery and then "wipe cache partition".
After this, the /data and /cache partition gets either mounted again or reformatted (not sure) with the rfs filesystem and the system will be able to boot.
BTW/little hint: You can see for couple of seconds after flashing the stock rom the phone boots into recovery, shows a couple of lines and there are 2 lines that are RED and say something like
DATA: blablabla... !
CACHE: blablabla... !
This process applies to the ROMs such as Purumod, Kyrillos and maybe others what have other filesystems used than the one used by the stock ROM (RFS).
Thats the description of the "bootloop" problem.
BTW... glad we could help and this has been fixed!

Unable to mount /data

I've managed to get that awful Rom (Destroyer) Manager off of my TF101G and have got Rogue on via PERI and now I'm trying to flash the stock ASUS ICS Rom but can't delete the Dalvik Cache because I'm unable to mount /data
Code:
- - Wiping all user data - -
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure
Cache wipe complete.
Formatting /cache...
Cache wipe complete.
Wiping dalvik-cache...
Error mounting /data!
I'm assuming that /data is stuck on read only?
Manually fixing permissions and then mounting /data also shows the same error.
HELP :crying:

I have the same problem. I know what lead me to it.
Its an Asus SL101
I have cyanogenmod correctly installed. In order to install a megatron rom I downloaded their app called megatron apps. Trying to download a rom from them I got validation error at end of download and I make the stupidity of change the download dir from /mnt/sdcard to /sdcard and then when I restart again it doesn´t load and CWM recovery give me the same errors (unable to mount /data or unable to mount /sdcard when cleaning cache or trying to restore a backup ).
The only thing I have been able to do its to install Rogue XM Recovery 1.5.0 instead of CWM 6.x ) but the problem to apply an update or restore a backup persists.
Any idea ?

Aaargh.
After a year and a half of heavy CWM and TWRP usage, this has suddenly happened to me too, possibly after flashing the updated TWRP blob from Goo Manager (although that's conjecture at best). My ROM (RaymanFX' CM10 v6) is fine in everyday use - no problems whatsoever, but now I want to update, and my recovery won't let me.
In the hope that something simply went wrong during recovery blob flash, I successfully deleted TWRP and flashed a different recovery (latest CWM) from ROM Manager, but the new recovery can't mount anything either - neither sd card, data, or cache. The error messages are more or less identical to TWRP's errors. My system MAY be readable, but I can't backup or restore or flash anything anyway, so I don't dare format it.
I don't have a Windows PC, so I haven't tried Easy Flasher. I could try it on my work computer if there's no way around it and if neither OSX or Ubuntu can help.
Any suggestions?

(SOLVED) [Q] [HELP] Motorola NOOB! Mount point information for XT925?

Hi there, I seem to have messed up my mounting partitions while trying to deodex Stock JB Central Europe. I basically used xultimate to pull the files and deodex then tried using adb shell to mount the system partition and copy them over. After I rebooted the phone, it would get stuck on unlocked bootloader warning or on the motorola logo. I hard reset into recovery and restored a nandroid backup and once booted into android found so many folders under the Storage folder such as "asec", "obb", rfs0" and so on. Now, when I try to wipe dalvik-cache in recovery, i get the following error: "E: unknown volume for path [/sd-ext]". Also, when i try flashing custom rom's and reboot, it gets stuck on the unlocked bootloader warning and wont load - while in recovery after flashing, i also get another error something like this: "E: cant load /cache/recovery.log" or similar. I also sometimes have issues mounting system, cache partitions, data and internal storage, all depending on which custom recovery i am using. I read on another site that downgrading to ics might solve mounting problems so I forced a downgrade to ics but that didnt work either and am still on ics.
Is there a way to restore the partitions correctly or are they stuck this way? Would mounting and remounting solve this problem? Any help would be much appreciated and would very much appreciate it if someone could upload their mount point info so i could use to try and fix it.
Many thanks in advance.
EDIT: Managed to flash Slim Bean 4.3 Official using OUDHS recovery without wiping cache and dalvik-cache at first. After reboot, it would bootloop so went to recovery and wiped cache and dalvik-cache then it worked. Still no sd-ext and some apps can't write or backup to external memory such as Go Backup & Restore Pro so what remains is to mount/unmount the partitions correctly.

Unique problem with flashing namely lollipop!

Hello, I faced unique problem. Device Nexus 5 D820. I've read a lot of topics on how to flash stock dactory image, clean, and did everything the same as described there.
Problem is that I am not able to flash lollipop (Android 5+) factory images. I mean everything goes fine, but when it comes to final start of the system it stucks on flying dots (dots are moving) over 12-24 hours and won't open. However the KitKat (Android 4+) factory images flashes properly, the system loads in 10 minutes. I also tried to update from Android 4.4.4 by google update (Android 5+) notification, but it also gets stuck on the same flying dots. The problem began when my device running Android 5.1 several months suddenly rebooted and system asked me to enter password (I do not use any passwords on phone), I entered my google account password, then it stated that the data was corrupted and needed factory reset. In order to avoid this I just turned it off and on and it stucked in flying dots. When I tried to wipe cache first the following errors appeared:
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
Then, after several flash things these errors do not appear already, but problem still remains. I already delete all data, so no need to bother keeping data. Any Ideas what causes this problem?

When I boot from TWRP and do operations the following string appears during operations (wipe cache, etc.):
Updating partition details...
E: Unable to mount '/persist'

I had a similar problem.
Make sure you wipe dalvik and cache in recovery before rebooting.
Finally, nothing worked until I did a factory reset after flashing.
Be sure to first backup photos, documents, etc. in addition to nandroid and titanium backup.

Update: problem SOLVED
maybeme2 said:
I had a similar problem.
Make sure you wipe dalvik and cache in recovery before rebooting.
Finally, nothing worked until I did a factory reset after flashing.
Be sure to first backup photos, documents, etc. in addition to nandroid and titanium backup.
Click to expand...
Click to collapse
Thank you mate. But my problem is apparently more specific.
I find a solution which is exactly suits for my problem. Greatest thanks to @bitdomo :good::good::good::good::good::good::highfive:highfive:
Here is his topic
[GUIDE][FIX] Boot loop on Lollipop 5.0 and above (fix persist partition)

[A510] Can't mount /data on any recovery

Hi,
I wanted to reset my 510 to a fresh 4.4.4 install. So I decided to "restore to factory settings" within the android system settings menu.
kitkat CM12 4.4.4 by shreps was working fine before, I just wanted to get rid of the data in order to give the tablet away.
now I'm stuck with a soft bricked device, it seems:
- when starting the tablet, the CM screen shows, but freezes after a while
- flashing any CM version in CWM 6..0.5 by shreps shows a "error: can't mount /data"
- wipe cache / data shows the same error
- wipe dalvik cache doesn't seem to respond in any way
- I reflashed CWM 6.0.5 using fastboot flash recovery, but to no success..
what options do I have now? can I format and remount the /data partition via ADB? do I need to go to stock?if, so, how?
Thanks for your ideas!

ok, via
fastboot -w -v
i could reformat the data partition somehow.
I still got an
E:unknown volume for path [/sd-ext]
error, but it continued and works for now.

huedrant said:
ok, via
fastboot -w -v
i could reformat the data partition somehow.
I still got an
E:unknown volume for path [/sd-ext]
error, but it continued and works for now.
Click to expand...
Click to collapse
Glad you dot it going.
I just pulled my 701 out of retirement (broke my Sony z2 screen trying to change my battery) so taking a look in here.
The data format has always been a bit twitchy, but I run the latest version of TWRP for KK. I remember bricking my original Data partition wiping it because some bozo used the wrong partition info making the original recovery for JB. Exchanged the tab.
I recall the bootloader version had to match what version of the ROM you installed (JB, KK, etc), and maybe the recovery also (can't remember). Latest TWRP for KK seems to work for me as I installed Pac Rom before I retired it. TWRP Ver 2.7.1.0
As with the "Path to ext SD", that's always been there if I recall. Just means you have to install a ROM from internal memory. Although my TWRP seems to mount it fine.
But I will say, feels like I've entered the dark ages again.