hi
after trying to flash "cm-9.0.0-nozomi.zip" with CWM, my xperia s get stucked in a boot loop. after that i tried to restore my backup with CWM but it couldn't restore /data partition , and i couldn't mount it too. the error is "can't mount /data (invalid argument)" or something like that.
now i can boot to ics but because of not having a mounted /data i can't save anything , and when i reset my phone, it get factory reset-ed.
and i'm using advanced ics kernel 11.
if anyone can help me, it would be very nice.
i flashed a new rom using flashtool and everything seems to be fine.
the CWM in the CM9 is a bit broken
best ist: flash another (any, exept the newest xsx, his CWM is also broken... all another Kernel have a working recovery) Kernel via Fastboot and then work with the recovery from this kernel..
Related
Hi All,
i think i just softbricked my S3. i was running Omega rom 33.2 and found the phone was unstable. Hence i wiped data, factory reset, clear dalvik cache and etc. after flashing the rom, it got stucked at samsung boot screen.
i even tried to reflash the rom but still failed to boot up. after that i decided to flash stock rom using Odin (I9300ZSDLK2). it managed to boot in but then it got stucked at recovery (failed to mount /system (Invalid argument). i thought it could be something wrong with the /system, i then flash CWM to format /system. obvious i wont be asking for help if that step succeeded. i basically got pawned because i am not able to mount /system. anybody can help me?
Hello.
This problem has appeared after i flashed the latest Dorimanx kernel (Kernel_Dorimanx-V9.43-[12-16]-[24-10]-JB-SGII-PWR-CORE). Today, after i flashed the latest ressurection remix ROM, i wanted to flash a kernel too. So i booted into recovery, flashed Dorimanx's kernel with no problems, rebooted, and noticed that my keyboard was lagging. So i decided to restore a previous backup from before i flashed the kernel, but when i got into recovery, and select to instal zip from sdcard, i got the following error: E: can't mount /sdcard. The thing is, when i restart my phone, i can acces my files with no problems (music, photos etc), but when i try to do it from recovery, i will not load the sdcard. Other than that, phone is working fine. No bootloops, no lag, just the mounting problem of the sdcard. I feel i should mention that i get an error even when trying to mount it directly from the recovery tab "mounts and storage". I hope you can get back to me and this soon, because this problem will prevent me from flashing any future roms/kernels or doing backups/restores.
cosminpislariu said:
Hello.
This problem has appeared after i flashed the latest Dorimanx kernel (Kernel_Dorimanx-V9.43-[12-16]-[24-10]-JB-SGII-PWR-CORE). Today, after i flashed the latest ressurection remix ROM, i wanted to flash a kernel too. So i booted into recovery, flashed Dorimanx's kernel with no problems, rebooted, and noticed that my keyboard was lagging. So i decided to restore a previous backup from before i flashed the kernel, but when i got into recovery, and select to instal zip from sdcard, i got the following error: E: can't mount /sdcard. The thing is, when i restart my phone, i can acces my files with no problems (music, photos etc), but when i try to do it from recovery, i will not load the sdcard. Other than that, phone is working fine. No bootloops, no lag, just the mounting problem of the sdcard. I feel i should mention that i get an error even when trying to mount it directly from the recovery tab "mounts and storage". I hope you can get back to me and this soon, because this problem will prevent me from flashing any future roms/kernels or doing backups/restores.
Click to expand...
Click to collapse
Put philz kernel into your internal sd card or the kernel which you were using previously and flash it from recovery then reboot to recovery again. Now try to restore your nandroid backup.
Hope it helps.
Good luck :thumbup:
Hey there
I'm in need of some help!
Phone: I9300 international 16gb
ROM: PA 4.2 beta 2/4
Kernel: stock PA/Devil v2.3.2/Googy-Max2 v2.1.8/2.2.0/2.2.1 final
Recovery: CWM 6.0.4.6 / Philz touch 6.25.0 / latest devil recovery
Problem:
I came from AOSPA 4.2 beta 1 or 2 (think it was 2) and wanted to try devil kernel with f2fs.
So I downloaded the devil recovery found here:
http://forum.xda-developers.com/show...postcount=1116
and downloaded latest PA (4.2 beta 4 04/09/2014) along with day-0 gapps minimal package.
Also I saved devil kernel to my ext sdcard. Ready to go I thought.
Rebooted to recovery...
Flashed devil recovery...
Rebooted recovery...
Did nandroid backup to ext sdcard...
formated /system /data + /datamedia & /cache as f2fs
Flashed latest PA 4.2 beta4...
Flashed gapps...
Flashed devil kernel...
Wiped data & /cache just to be sure
Rebooted...
After the first boot i got
com.android.phone forceclosing over and over again. As soon as I press the OK button the message reappears, giving me no time at all to sort things out while android is running. Next I rebooted to recovery, formated again (f2fs) did a clean reflash, rebooted and got the same problem.
So I wanted to switch back to my working rom, rebooted to recovery, formated everything back to ext4 and restored my backup.
Just to be sure I wiped /cache & dalvik-cache before i rebooted to my old rom (PA 4.2 beta 2 with googy-max2 v2.2.1).
Boot succeeded but I got the same forceclose. This was the first time I realized something just isn't right. Reboot to recovery, restored AGAIN, flashed devil kernel on top -> bootloop. Tried clean installing PA 4.2 beta 4 without custom kernel -> bootloop, switched recovery to CWM v4.0.4.6 and tried restoring my backup from there -> bootloop.
Thought I messed up my partitions, found an Odin package with CWM 6.0.4.4 included, flashed it together with 16gb .pit file and re-partition checked.
As I had 13 partitions before I can confirm via ADB that it did indeed repartition my sdcard.
Restored my backup -> bootloop, for test purposes I tried latest NeatROM light.
Booted & working like a charm. No hickups.
Updated recovery to latest Philz touch (v6.25 somewhat).
Restoring my backup or flashing PA results in bootloops no matter how eager I format /system /cache /data + /data/media before.
/efs is accessible and seems fine. /preload not so much. I noticed it just after flashing Philz touch recovery that whenever I try to format /preload it failes. Can't even mount it (not in recovery menu, nor via adb).
Could /preload (/dev/block/mmcblk0p10) not being able to mount cause these bootloops? Why would NeatROM run just fine then (Sammy based ROM)? Is the /preload partition supposed to behave like that and if not, what could I do to get things going again?.
I'm pretty desperate for help. Thanks in advance for reading that whole text!
//Edit: I hope this is not considered spam, I posted the same text in another thread!
So i was playing around with different roms yesterday (tried cm7/9/11) and i must have messed up something when flashing cm11 nightly. After i was unable to flash any rom with any recovery (flashed ok, but then stopped at samsung logo) i tried odin with stock firmware found here http://forum.xda-developers.com/showthread.php?t=1822109
Odin flash went ok but immediatly when phone rebotted, i got errors on /data (fail to mount /data invalid argument) . Now stock rom bootloops and if i flash anything custom, i get stuck on samsung logo.
Also if i try to format /data from stock recovery, i get "E:format_volume: rfs format failed on /dev/stl11)
Any ideas what to do ? It seems that /data partrition is somehow messed up or something..
Hello,
I'm trying to flash an old Samsung Galaxy Ace GT-S5830i with Cyanogenmod. Installing a new Recovery (CWM, tried several versions for the S5830i) works as expected. But unfortunately I'm unable to access (mount, format) the /system partition from any of those CWM recoveries.
If I go to 'mounts and storage' and try to 'mount /system', CWM says:
Code:
Error mounting /system!
If I try to 'format /system', it says:
Code:
Formatting /system...
E:format_volume: make_ext4fs failed on /dev/block/stl9
Error formatting /system!
I searched this forum and the web for answers, but so far were unable to find a sufficient one. Is this a known problem?
I tried to flash CM 9.1 unofficial port from http://forum.xda-developers.com/showthread.php?t=2118645 nevertheless. The installation seems to succeed (no obvious error messages), but afterwards the phone hangs at the 'Samsung Galaxy Ace GT-S5830i' splash screen in boot process forever. I guess that this is related to the unaccessable /system partition, right? If the partition is not accessible, then flashing the new ROM must have failed to write data to it as well.
Thanks in advance for any help.
Seems like the phone was bricked. I managed to fix it by flashing the stock ROM using Odin. Afterwards flashing CM 9.1 worked like a charm.