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!

partitions seem to be locked, cant format

i had a recent soft brick in which for some reason, i couldnt decrypt, with this, i couldnt load anything on android besides twrp and fastboot.. when i try reformatting and wiping data, it seems to fail.. for example, i go to format with twrp and it hangs, if i try installing anything itll fail to load any data onto that partition.. if i could reformat that partition back to its useful state, without the encryption issue i could reinstall a rom and fix this issue
any ideas?
when i attempt to do anything in twrp.. i get this error
Updating partition details
E: error opening ' /data/media '
E: error: No such file or directory
just a test, i tried to create a new folder in /data, and it says its a read-only filesystem

jason41987 said:
i had a recent soft brick in which for some reason, i couldnt decrypt, with this, i couldnt load anything on android besides twrp and fastboot.. when i try reformatting and wiping data, it seems to fail.. for example, i go to format with twrp and it hangs, if i try installing anything itll fail to load any data onto that partition.. if i could reformat that partition back to its useful state, without the encryption issue i could reinstall a rom and fix this issue
any ideas?
when i attempt to do anything in twrp.. i get this error
Updating partition details
E: error opening ' /data/media '
E: error: No such file or directory
just a test, i tried to create a new folder in /data, and it says its a read-only filesystem
Click to expand...
Click to collapse
Your partition is probably encrypted. The only way to access to your data is to decrypt it before you can do anything. Do you have a password for it?

LetMeKnow said:
Your partition is probably encrypted. The only way to access to your data is to decrypt it before you can do anything. Do you have a password for it?
Click to expand...
Click to collapse
no, any way i can erase all the data, the partition and start fresh?

jason41987 said:
no, any way i can erase all the data, the partition and start fresh?
Click to expand...
Click to collapse
"Format data" should do this. In which way doesn't it work for you?

_that said:
"Format data" should do this. In which way doesn't it work for you?
Click to expand...
Click to collapse
when i attempt to format data, format fails, it will not let me touch the /data partition, when it does mount, it mounts as read-only.. the partition itself, possibly partition table or something is damaged because it cannot be formatted and nothing can be written to it
it would seem like the internal storage is screwed.. but the other partitions seem to work fine, even able to use command-line from twrp to check fstab and try to mount manually... im not sure how to completely delete and recreate a partition in fdisk, if possible on here

jason41987 said:
when i attempt to format data, format fails
Click to expand...
Click to collapse
No error message? No log file? Just "fails"?
You could try running "/sbin/make_ext4fs /dev/block/mmcblk0p8" manually from adb shell.
jason41987 said:
it would seem like the internal storage is screwed.. but the other partitions seem to work fine, even able to use command-line from twrp to check fstab and try to mount manually... im not sure how to completely delete and recreate a partition in fdisk, if possible on here
Click to expand...
Click to collapse
You can't use fdisk on the internal storage - it uses a combination of GPT and a proprietary partition table.

_that said:
No error message? No log file? Just "fails"?
You could try running "/sbin/make_ext4fs /dev/block/mmcblk0p8" manually from adb shell.
You can't use fdisk on the internal storage - it uses a combination of GPT and a proprietary partition table.
Click to expand...
Click to collapse
the errors i receive are above..trying different things ive received the error that the partition is write one... are there any tools for redoing the entire internal storage?

maybe this could work.. since the other partitions seem to work just fine, as they were not encrypted, what if i edited fstab to mount partitions on a MicroSD card pre-partitioned to act as /data and /cache, then install a rom... unless there are ROMs designed to utilize an external SD for installation?... either way if i can work around these two partitions i could get into a working android system where i can find more tools to assist in removing and recreating those broken partitions
ive considered trying to use fastboot to replace the twrp recovery with a stock asus recovery partition and try to fix the issue from that, but i doubt that would be of any use

jason41987 said:
ive considered trying to use fastboot to replace the twrp recovery with a stock asus recovery partition and try to fix the issue from that, but i doubt that would be of any use
Click to expand...
Click to collapse
Instead you should try it cause i'm pretty sure it will fix your partition.Just install the stock recovery and do a Wipe Data first. If all goes well you can go ahead and flash a stock rom from MicroSD or install the TWRP again and check if it's working.
Here you can find the latest stock recovery - - > http://forum.xda-developers.com/showthread.php?p=44280630

Pretoriano80 said:
Instead you should try it cause i'm pretty sure it will fix your partition.Just install the stock recovery and do a Wipe Data first. If all goes well you can go ahead and flash a stock rom from MicroSD or install the TWRP again and check if it's working.
Here you can find the latest stock recovery - - > http://forum.xda-developers.com/showthread.php?p=44280630
Click to expand...
Click to collapse
are you saying write over twrp with the stock recovery partition with fastboot, then boot into the recovery partition from the power + volume down menu and see if that recovery image will reset to factory defaults?... if so, where would i even get that recovery image?.. and if you mean just try installing a stock rom through TWRP, ive already been there, done that, and it hangs on formatting

jason41987 said:
are you saying write over twrp with the stock recovery partition with fastboot, then boot into the recovery partition from the power + volume down menu and see if that recovery image will reset to factory defaults?... if so, where would i even get that recovery image?.. and if you mean just try installing a stock rom through TWRP, ive already been there, done that, and it hangs on formatting
Click to expand...
Click to collapse
If you follow the link i posted previously you will find the stock recovery (from the latest asus firmware) as an attachment to that post.
After you flash it via Fastboot, do a Wipe Data from the bootloader menu (the one with the 3 icons) after that just follow "restore with stock recovery" procedure from my All in One Thread (it's a sticky post under General Forum).
That should fix your issue and get you to a new clean starting point.

Pretoriano80 said:
If you follow the link i posted previously you will find the stock recovery (from the latest asus firmware) as an attachment to that post.
After you flash it via Fastboot, do a Wipe Data from the bootloader menu (the one with the 3 icons) after that just follow "restore with stock recovery" procedure from my All in One Thread (it's a sticky post under General Forum).
That should fix your issue and get you to a new clean starting point.
Click to expand...
Click to collapse
well, ill try that as soon as i wake up.. if it doesnt work though i am prepared to install something thatll run those partitions of an external microsd though.. wonder why no roms exist specifically for that?... seems like an ultra-secure rom for the ultra-paranoid to be able to pop out their microsd and hide it with all user data stored on it

jason41987 said:
well, ill try that as soon as i wake up.. if it doesnt work though i am prepared to install something thatll run those partitions of an external microsd though.. wonder why no roms exist specifically for that?... seems like an ultra-secure rom for the ultra-paranoid to be able to pop out their microsd and hide it with all user data stored on it
Click to expand...
Click to collapse
Data2SD already exists.
Did you already try to format your data partition from adb shell?

data2sd seems to be something thats applied after a rom is successfully installed, not sure that would help me
anyway, i tried the stock recovery image and it just hangs on an android graphic with a rotating blue wireframe inside its chest and a blue progress bar, but it doesnt actually do anything else
edit: wait a minute.. i see how this goes with the data2sd... i download a data2sd kernal, since i install cleanrom i can add this to the installations list of kernals, the data2sd kernal will mount external SD cards as the /data, cache, and sdcard partitions, allowing me to bypass the issue im having completely and use a 64gb microsd card as my primary storage... very interesting indeed

aah, fantastic, cant even get into fastboot mode to put twrp back on for the data2sd method.. so it would seem now my tablet is COMPLETELY toast

jason41987 said:
aah, fantastic, cant even get into fastboot mode to put twrp back on
Click to expand...
Click to collapse
What happens when you try?

_that said:
What happens when you try?
Click to expand...
Click to collapse
when i hold power and volume down it goes straight to the robot with the blue spinning wireframe graphic,, i dont get an option to go to fastboot.. i can also use power and volume up to go into apx mode but no idea what thats even used for as i find very little reference to it online

jason41987 said:
when i hold power and volume down it goes straight to the robot with the blue spinning wireframe graphic,, i dont get an option to go to fastboot..
Click to expand...
Click to collapse
I see, that's forced boot to recovery because of "wipe data" selected from the bootloader menu.
I don't know how long wiping data takes, maybe you are just not patient enough to let it finish?

_that said:
I see, that's forced boot to recovery because of "wipe data" selected from the bootloader menu.
I don't know how long wiping data takes, maybe you are just not patient enough to let it finish?
Click to expand...
Click to collapse
no, it finished, then said it was booting the recovery image afterwards, then i let it sit for about 2 hours when i went to do something else and it hanged on that screen... no way to fix this from apx mode?

jason41987 said:
no way to fix this from apx mode?
Click to expand...
Click to collapse
APX mode is only useful if you have nvflash, the wheelie tool, and the blob file for your device, which you'd have needed to create with firmware 9.4.5.26 or earlier and the hacked bootloader from androidroot.mobi.

[Q] CWM cache wipe -> storage corruption?

So I was going to take a nandroid of my Nexus 5 in order to transfer to my RMA device. I have found that device swaps usually go over better using CWM for nandroid instead of TWRP. So I flashed the latest CWM from ROM Manager and booted into it.
I figured I would save space if I blanked the cache, so I initiated a cache wipe. The display become a broken-up Android picture, and the cache wipe did not complete in minutes. I long pressed power to boot into the OS and found that - uh oh - the entire sdcard folder was inaccessible. All app data appeared to be intact but no app could read or write the sd.
Did I just completely bork all my internal storage? Any possible rescue path?
EDIT: OK I flashed recovery over to TWRP and its file manager still shows all my files. So all is not lost. But something went wonky and the OS is confused now.
In TWRP when I try a cache wipe I get:
Updating partition details...
E:unable to mount '/cache'
E:unable to mount '/cache'
E:unable to mount '/cache'
Formatting Cache using make_ext4fs function.
And it sits there chugging the status bar. Been over a minute now.
Aha okay, it finished. Fingers crossed... Yeah OK it's fine now on another full boot.
Still a bit strange though. Normally on any other device I've owned, a cache wipe was a simple matter.

cmstlist said:
a cache wipe was a simple matter.
Click to expand...
Click to collapse
Its an issue on the nexus 5 for some reason, took 5-10 min on my phone before but i think it was fixed in the latest twrp.

peachpuff said:
Its an issue on the nexus 5 for some reason, took 5-10 min on my phone before but i think it was fixed in the latest twrp.
Click to expand...
Click to collapse
Yes, on TWRP 2.6.3.4 it took 5-10 minutes but fixed it. It would seem that there is a simple cache wipe versus fully formatting the partition. If the first fails to work, it proceeds to the full format.

[Q] Big problem PLEASE HELP

I properly installed CyanogenMod 10.2 at my Galaxy Tab 2 P5110. Tried to go to the Firmware Update at the settings and clicked Kit Kat. Everything was installing just fine, but suddenly it stopped. It said it had failed and I had to reboot the system and reroot or something like that. Accidentally clicking Go Back, the Tablet rebooted and kept going back to the recovery mode. I tried to Wipe Data/ Factory Reset and when it rebooted instead of the Samsung Galaxy Tab 2 boot image, a distorted image appeared and took me back to the recovery mode. I installed CyanogenMod again through External SD card, because the Internal SD card showed nothing. It started to install and everything worked normally, except that I had forgotten to install GApps. I went to the Browser and installed it and the Download folder at the internal sd card in theory, but when I got back to the recovery mode, nothing showed up there. I really don't know what happened with the Internal SD card, I just know I can't access it...

Might be you need to format the memory not wipe.
Sent from my SCH-I545 using xda app-developers app

pewds said:
Might be you need to format the memory not wipe.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
How do i do this?

matheusimmer said:
How do i do this?
Click to expand...
Click to collapse
you can found it in recovery > mount and storage if you're using cwm based recovery
do a format /system, format /data, format /cache, and format /data/media
carefully not to format /sdcard
then reflash rom and gapps, enjoy.

Error updating CM13, and others.

Hi, i have the next versions:
CyanogenMod: 13.0-20161004-NIGHTLY-osprey
Kernel: 3.10.49-MPI24.107-56-g09ff0d1
And when trying to install the 1009-NIGHTLY update i get an error without a log in the cianogenmod recovery. When I try to "Apply update" and then "Choose from emulated", it shows the next message:
"E:failed to mount /data (Invalid argument)
Installation aborted"
Then, i go to see the recovery logs, but it blanks and shows the main menu again.
Why do I want to update to the latest version, having 5 days of difference with the installed version?
Because I'm having repeatedly bugs with the Firefox browser, can't update Telegram, can't connect via Bluetooth to the most of the devices, can't update the binaries of SuperSU, and other minor errors.
Which could be the cause of some of this problems?
Sorry for my poor english, Saludos!

Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.

Henriquefeira said:
Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.
Click to expand...
Click to collapse
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?

Gonzon said:
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?
Click to expand...
Click to collapse
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you

Just as a side question, did anyone got AICP nightlies .zip stuck at extracting image to /system? I tried clean install (wipe /system, /data, /cache and dalvik) but its just stuck there. Tried multiple nightlies. Tried deleting Android and .android_secure folders in both external and internal storage. I haven't tried wiping internal storage yet (I will do it ASAP). Any tips will be great. Thanks
Broadcasted from Zeta Reticuli

Henriquefeira said:
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you
Click to expand...
Click to collapse
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Code:
[email protected]:~$ fastboot -p xxxxxxxxxx flash /data/media /home/imperial/Android2/cmupdater/cm-13.0-20161009-NIGHTLY-osprey.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 91972855 is not a multiple of the block size 4096
fastboot: /build/android-tools-hIu7Bj/android-tools-4.2.2+git20130529/core/libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Abortado
Do you know what it means?

Gonzon said:
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Do you know what it means?
Click to expand...
Click to collapse
You can't flash the zip of a ROM via fastboot, follow this tutorial >goo.gl/JfRzZu and on the next time avoid installing the CM bundled recovery

Solved.
I flashed vía fastboot a stable twrp, then after a lot of errors and strange things i was able to flash the ROM.
Thanks a lot for your help.
I was seeing a bricked phone already jajaja.