I flash with odin and make mistakes.
Flashed:
CSC in PDA
PDA in CSC
Click to expand...
Click to collapse
So everytime I entered recovery I get this kind of messages
E:failed to mount /data (No such file or directory)
E: failed to mount /sdcard (File exists)
E: copy_cache _media: Can't mount /sdcard
your storage not prepared yet,p lese use UI menu for format and reboot actions
E:failed to mount data (Invalid Argument)
Click to expand...
Click to collapse
And I get Bootlop on samsung logo (the second one)
Don't know why, none Roms managed to boot EXCEPT THIS ONE (CM7) http://forum.xda-developers.com/showthread.php?t=1527359
BUT I'm facing this bugs:
#No internal storage at all (It says 0 and can't install google play apps because it says that I have no free space)
#Reboot erase all config and apps installed. It takes the phone like it recently flashed the rom.
#EFS is missing (Have backup, restored, but the problem above makes all difficult)
I'm thinking that the /device files might be corrrupted. But I don't know how to solve this.
try flashing pit file
mehran 92 said:
try flashing pit file
Click to expand...
Click to collapse
Done it 3493493414 times.
jutopa said:
Code:
E:failed to mount /data (No such file or directory)
E: failed to mount /sdcard (File exists)
E: copy_cache _media: Can't mount /sdcard
your storage not prepared yet,p lese use UI menu for format and reboot actions
E:failed to mount data (Invalid Argument)
Click to expand...
Click to collapse
It looks like that the eMMC is not working, /sdcard and /data are on it.
I don't think the problem is due to the fact that you wrongly flashed the files. As long as you don't mess with bootloaders, things can most of the time be fixed.
It looks like an hardware failure, but I could be wrong. I've no ways to determine it.
Anyway, the eMMC is not the most important memory in our device, you can replace it with the external SD. There are several ways to do it, some users posted their solution here in the forum, this for example.
loSconosciuto said:
It looks like that the eMMC is not working, /sdcard and /data are on it.
I don't think the problem is due to the fact that you wrongly flashed the files. As long as you don't mess with bootloaders, things can most of the time be fixed.
It looks like an hardware failure, but I could be wrong. I've no ways to determine it.
Anyway, the eMMC is not the most important memory in our device, you can replace it with the external SD. There are several ways to do it, some users posted their solution here in the forum, this for example.
Click to expand...
Click to collapse
Yeah, I'm starting to think that.
I will try to swap SDs.
But I have a question. My main problem is that most of ROMS don't boot. Don't know why, but the only ROMs I managed to boot are CM7 and MIUI 2.3 also. Why this? If I try a different rom it gets stuck in bootloop or doesn't even install it at all.
If a swap sd would this limitation of roms will be solved? I mean, this swapping is permanent or it goes away every time I flash a new build????
jutopa said:
Yeah, I'm starting to think that.
I will try to swap SDs.
But I have a question. My main problem is that most of ROMS don't boot. Don't know why, but the only ROMs I managed to boot are CM7 and MIUI 2.3 also. Why this? If I try a different rom it gets stuck in bootloop or doesn't even install it at all.
If a swap sd would this limitation of roms will be solved? I mean, this swapping is permanent or it goes away every time I flash a new build????
Click to expand...
Click to collapse
I can't explain why CM7 is working, there could be several reasons (/cache is inside the OneNAND, it's using your SD card for /data etc...).
The changes for the swap are usually in the kernel ramdisk or /system and both of them are entirerly wiped during ROM updates, so you should do them on every ROM update.
Related
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Eisken said:
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Click to expand...
Click to collapse
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
ben_pyett said:
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
Click to expand...
Click to collapse
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Eisken said:
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Click to expand...
Click to collapse
Sorry, I'm afraid that I must be the bearer of bad news ....I believe that by pulling out the battery you have ruined the eMMC chip in the device, this appears to be a flaw or defect with a selection of recent HTC devices.
I believe that the only thing you can do is to return the device for warranty or to attempt to get the chip replaced.
Here are a selection of similar threads, within this forum which also cover this problem and I believe that you should be able to find others......
http://forum.xda-developers.com/showthread.php?t=1165304
http://forum.xda-developers.com/showthread.php?t=1150917
http://forum.xda-developers.com/showthread.php?t=1226849
Thanks for your reply!
Too bad there is nothing to do about it. I'll just send it in for repair then.
having the same problem.. so should i try to wipe the cache and see what happens?
I fixed that by going into recovery and wiping the cache. It still says that it is unable to mount but re-flashing the ROM fixed all that.
I've tried that quite a few times, but it always failed to flash the rom. Did you get errors when flashing the rom?
What errors do you get when you're installing the ROM?
If you are still able to go into recovery then....
Do you have EXT4 recovery installed?
If not 1) Download this FILE which is EXT4 recovery 2) then copy it onto your SD card 3) enter recovery and flash the EXT4 ZIP file 4) Reboot Recovery
Then look at what format the existing CACHE partition is in?
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
EbiEre said:
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
Click to expand...
Click to collapse
The good news here is that you recovered from this problem and also that you didn't pull battery, so we can rule that out as being the cause in your case.
Between the Installation/flashing of the second ROM did you perform the necessary WIPES?
You may well have done, but, just in case, I'd always recommend that you take a full Nandroid backup of an existing system ROM before moving and flashing another (just to have a fall back position in case)?
@ EbiEre
I got scared after reading those lines too. Nothing to worry about. Just keep flashing roms as usual . Just a cache error. If you didnt pull out the battery, and if the rom booted, then everything is ok.
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
EbiEre said:
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
Click to expand...
Click to collapse
Can only echo the comments of @.sh4d0w.
We all take a minor risk of bricking our devices with the majority of commands and flashes that we do.....but we still do them because that's half the fun...
Did you ever examine the format types ie EXT3/EXT4 of each partition using the EXT4 recovery?
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!
I was running scotts newest build 2/3/13 JB however my internal sd card kept failing.. i read going back to stock would fix the problem.. i have gone all the way back to gingerbread before and i got odin to work for me in doing this, ( it says it successfully passes, however when the setup shows up on my phone it says
"E: failed to mount /dbdata (File exist)
E: copy_dbdata_media: Can't mount /dbdata
your storage not prepared yet. please use UI menu for format and reboot options."
. I really need help i feel really dumb for trying this. I should also mention that i formatted my internal sd card before doing this
Ok so i was able to get it working i used a different tar file that was linked to me. i completly forgot how GB looked like did not miss it at all
Hello!
Recently I recevied "Encryption Unseccesful" message on my phone. I tried to restore backup, but twrp says: "failed to mount /data". So, internal storage is dead. Found this. But cant find "repartition" menu in the cwm.
Questions is:
1. Do I need older versions of cwm to repartition sdcard? (If you have one, please share )
2. Is there any ways of recovering phone?
Thanks in advance!
no, just go to TWRP, Wipe, Format internal sdcard
sandpox said:
no, just go to TWRP, Wipe, Format internal sdcard
Click to expand...
Click to collapse
tried this, but I think internal storage is corrupted. Is there a way to use sdcard as internal storage?
you can use sd card for apps and other stuff, but as I knoe cannot be used for system files
I made 2 partitions on sd:
4gb fat32
4gb ext4
But I cant bind /data to this ext4 partition. Can you help, please?
What i did:
With TWRP's terminal:
Code:
mount -t ext4 /dev/block/mmcblk1p2 /data
- Invalid argument (dunno why)
Code:
ln -s /dev/block/mmcblk1p2 /data
- but on phone boot i receive same "encryption unsuccesful" screen.
Edited /etc/fstab - same result.
Files and mount after reboot turn back to its previous condition.
Also installed stock ROM - same message screen.
[/QUOTE]
I got advice that i must do this things with init.d scripts. How can I do this? Already tried "xda's app2sd scripts" but they works if phone completely boots in OS.
remosam said:
you can use sd card for apps and other stuff, but as I knoe cannot be used for system files
Click to expand...
Click to collapse
Why not? I want only mount /data on sd without booting in OS. Other partitions like /system surprisingly work right, because i can flash ROM (stock, CM), but always receive - "cant mount /data"
blind_aquila said:
Why not? I want only mount /data on sd without booting in OS. Other partitions like /system surprisingly work right, because i can flash ROM (stock, CM), but always receive - "cant mount /data"
Click to expand...
Click to collapse
asked sostk or noname
@blind_aquila
try to flash stock rom with odin
Hi All,
I am trying to root Samsung S7 Oreo 8.0 with TWRP & Magisk. But, when ever I log into TWRP it's saying "Inernal Memory 0MB)
I've followed below steps :
Installed TWRP and no-verity-opt-encrypt zip, it worked until I reboot to system
After reboot again the internal memory showing as 0MB (may be re-encrypted)
Is there any way that I can remove the encryption permanently?
Error :
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present
Unable to mount /data/media/TWRP/.twrps
PS : I've gone through the forum to find different solutions, but nothing working to remove the encryption permanently.
yes, it is possible. is use it all the time with my stock android. give me some time to write it...or maybe someone other can tell u. u already used the search in this forum?
an other question, u really need an unencrytped internal memory?
snowfirewall said:
Hi All,
I am trying to root Samsung S7 Oreo 8.0 with TWRP & Magisk. But, when ever I log into TWRP it's saying "Inernal Memory 0MB)
I've followed below steps :
Installed TWRP and no-verity-opt-encrypt zip, it worked until I reboot to system
After reboot again the internal memory showing as 0MB (may be re-encrypted)
Is there any way that I can remove the encryption permanently?
Error :
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present
Unable to mount /data/media/TWRP/.twrps
PS : I've gone through the forum to find different solutions, but nothing working to remove the encryption permanently.
Click to expand...
Click to collapse
Thank you.. Am not exactly looking for unencrypted partition. Am just confused whether it's expected to format data and no variety everytime or is it just one time for root?
Also I gone through the threads to find fix for this issue. But most of the people are suggesting to format data.
Any other better ways? Can we take backup of existing ROM from TWRP without root?
Roberto W. said:
yes, it is possible. is use it all the time with my stock android. give me some time to write it...or maybe someone other can tell u. u already used the search in this forum?
an other question, u really need an unencrytped internal memory?
Click to expand...
Click to collapse
i am using a stock firmware by telekom, it installs some features after first flash and first reboot (maybe ur firmware does not need step 3, so my second reboot is ur first reboot into download mode)
1. flash stock firmware
2. first reboot
3. install for provider reasons and then
4. second reboot (important: into download mode)
5. flash twrp
6. third reboot (important: into twrp)
7. flash zip-file (attached to this post)
8. reboot and wait....
now u should have an unencrypted system. the only thing is, u need to repeat these steps on firmware updates.
snowfirewall said:
Thank you.. Am not exactly looking for unencrypted partition. Am just confused whether it's expected to format data and no variety everytime or is it just one time for root?
Also I gone through the threads to find fix for this issue. But most of the people are suggesting to format data.
Any other better ways? Can we take backup of existing ROM from TWRP without root?
Click to expand...
Click to collapse