I just tried reverting back to stock 2.3.5 rom and after I flash it goes to stock recovery.
I get this:
--Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
E:format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Deleting Meta Data
Data wipe failed.
I just hit "reboot system now" and now i just get the Samsung logo bootloop. Tried reflashing it multiple times but end up with the same result.
What device is it?
Seems to be a 5.0 and may be the comon memory formating issue.
Did you flash something "wrong" before you try to revert to stock?
lolo9393 said:
What device is it?
Seems to be a 5.0 and may be the comon memory formating issue.
Did you flash something "wrong" before you try to revert to stock?
Click to expand...
Click to collapse
It's a 4.0 US
I think my files may be corrupted. They flashed in Odin and passed, but keep getting problems.
When I flash Steves kernel 3.0 I can access CWM. I then get no errors but can't load my system.
axvk97 said:
It's a 4.0 US
I think my files may be corrupted. They flashed in Odin and passed, but keep getting problems.
When I flash Steves kernel 3.0 I can access CWM. I then get no errors but can't load my system.
Click to expand...
Click to collapse
Never seen anybody asking for this issue on a 4.0, we were only a group of 5.0 GB70 owners having faced this before. I do not want to direct you to a wrong way, in mean time waiting for any other advise or remedy, take time to read the related korean GB70 memory problem.
http://forum.xda-developers.com/showthread.php?t=1716277
I got the errors to go away but I still cannot access the system. In CWM it says:
ClockworkMod Recovery v3.0.0.5
Checking for ext4 partitions...
Checking /system...
Checking /data...
Checking /datadata...
Checking /cache...
Done!
I have had this same thing happen before but was able to revert to stock firmware.
EDIT: Finally fixed it i just didn't go into recovery until after I flashed everything.
Hi everyone,
Let me present my situation.
After flashing a CM10-based rom (using cwm), I was able to use the phone for a few minutes. Then, the screen suddenly went black and I had to reboot it. Since then, my phone can no longer pass the phone logo (on stock rom) or cm9 boot screen. My attempts to flash stock GB & ICS (using Odin) were all successful but again it was not able to pass phone logo.
I suspect that my phone was bricked because of mmc_cap_erase bug (afaik, my phone model is vulnerable to this bug). However, emmc_find_brick_start script of hg42 was able to finish after ~23 hours of scanning . Furthermore, I can mount /efs /system /data /cache /emmc using cwm without problem. I can also browse these partitions using Aroma file manager easily.
So, I'm confused now. I'm not sure whether it's an effect of mmc_cap_erase bug or something else wrong with my phone. Any suggestion to tackle this problem is greatly appreciated.
As I'm still able to browse the mmc, let me know whatever file I should pull to assist with debugging.
Thanks
Alan
alansmith_xda said:
Hi everyone,
Let me present my situation.
After flashing a CM10-based rom (using cwm), I was able to use the phone for a few minutes. Then, the screen suddenly went black and I had to reboot it. Since then, my phone can no longer pass the phone logo (on stock rom) or cm9 boot screen. My attempts to flash stock GB & ICS (using Odin) were all successful but again it was not able to pass phone logo.
I suspect that my phone was bricked because of mmc_cap_erase bug (afaik, my phone model is vulnerable to this bug). However, emmc_find_brick_start script of hg42 was able to finish after ~23 hours of scanning . Furthermore, I can mount /efs /system /data /cache /emmc using cwm without problem. I can also browse these partitions using Aroma file manager easily.
So, I'm confused now. I'm not sure whether it's an effect of mmc_cap_erase bug or something else wrong with my phone. Any suggestion to tackle this problem is greatly appreciated.
As I'm still able to browse the mmc, let me know whatever file I should pull to assist with debugging.
Thanks
Alan
Click to expand...
Click to collapse
Do this now
-Boot to recovery mode
-Factory data reset
-Reboot phone
Swyped from my Samsung Galaxy SII
Jokesy said:
Do this now
-Boot to recovery mode
-Factory data reset
-Reboot phone
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Hi Jokesy
On trying to "factory data reset" I got
-- Wiping data...
Formating /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Formating /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
Formating /sd-ext...
Formating /sdcard/.android_secure...
Data wipe complete.
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
Thanks
Alan
alansmith_xda said:
Hi Jokesy
On trying to "factory data reset" I got
-- Wiping data...
Formating /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p25
Formating /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
Formating /sd-ext...
Formating /sdcard/.android_secure...
Data wipe complete.
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
Thanks
Alan
Click to expand...
Click to collapse
have you rebooted your phone yet? any news?
Jokesy said:
have you rebooted your phone yet? any news?
Click to expand...
Click to collapse
Hi Jokesy,
Yes, I already rebooted it (as I have to use key combo to enter cwm), but still cannot wipe.
It's getting late on my side now. I'll come back tomorrow instead.
Thanks for helping me out.
Alan
alansmith_xda said:
Hi Jokesy,
Yes, I already rebooted it (as I have to use key combo to enter cwm), but still cannot wipe.
It's getting late on my side now. I'll come back tomorrow instead.
Thanks for helping me out.
Alan
Click to expand...
Click to collapse
Reflashing via Odin can help...
Isn't it Jokesy?
Peace
Hit Thanks & It will Disappear
Sent from S II Running Official ICS 4.0.4 with Siyah 4.1 [/size]
Omaxe said:
Reflashing via Odin can help...
Isn't it Jokesy?
Peace
Hit Thanks & It will Disappear
Sent from S II Running Official ICS 4.0.4 with Siyah 4.1 [/size]
Click to expand...
Click to collapse
Sure, Odin will help.
I'm just waiting for him to come back before i post what's next for him
Swyped from my Samsung Galaxy SII
Hello,
So, now my current situation is
_I'm still able flash stock successfully using Odin (at least that was what Odin reported)
_Booting always stuck. On stock kernel, my phone shows 3 different splashes: Samsung logo, SHV-E120L logo with progress bar & distributor logo. Sometimes my phone stuck at SHV-E120L screen (with 100% progress) until I reboot it, sometimes it can reach distributor logo but it will automatically restart (just like a boot loop)
_Wipe data/factory reset always result in make_extf4fs failed on /data
Is there anything else I should provide to narrow down my problem?
Thanks
Alan
alansmith_xda said:
Hello,
So, now my current situation is
_I'm still able flash stock successfully using Odin (at least that was what Odin reported)
_Booting always stuck. On stock kernel, my phone shows 3 different splashes: Samsung logo, SHV-E120L logo with progress bar & distributor logo. Sometimes my phone stuck at SHV-E120L screen (with 100% progress) until I reboot it, sometimes it can reach distributor logo but it will automatically restart (just like a boot loop)
_Wipe data/factory reset always result in make_extf4fs failed on /data
Is there anything else I should provide to narrow down my problem?
Thanks
Alan
Click to expand...
Click to collapse
Don't seems like just Software/Firmware Problem.
Its more than that...
Is there any strange effect like overheating...
Edit: I really loved the way you post thread...
Peace
Hit Thanks & It will Disappear
Sent from S II Running Official ICS 4.0.4 with Siyah 4.1 [/size]
Omaxe said:
Don't seems like just Software/Firmware Problem.
Its more than that...
Is there any strange effect like overheating...
Edit: I really loved the way you post thread...
Click to expand...
Click to collapse
Glad that you like the way I posted
Except for being shutdown after upgrading to CM10, my phone hasn't shown any strange symptom. After couple attempts to wipe data/factory reset and re-flashing stock rom, CWM appears to stuck now
Thanks
Alan
alansmith_xda said:
Hi everyone,
Let me present my situation.
After flashing a CM10-based rom (using cwm), I was able to use the phone for a few minutes. Then, the screen suddenly went black and I had to reboot it. Since then, my phone can no longer pass the phone logo (on stock rom) or cm9 boot screen. My attempts to flash stock GB & ICS (using Odin) were all successful but again it was not able to pass phone logo.
I suspect that my phone was bricked because of mmc_cap_erase bug (afaik, my phone model is vulnerable to this bug). However, emmc_find_brick_start script of hg42 was able to finish after ~23 hours of scanning . Furthermore, I can mount /efs /system /data /cache /emmc using cwm without problem. I can also browse these partitions using Aroma file manager easily.
So, I'm confused now. I'm not sure whether it's an effect of mmc_cap_erase bug or something else wrong with my phone. Any suggestion to tackle this problem is greatly appreciated.
As I'm still able to browse the mmc, let me know whatever file I should pull to assist with debugging.
Thanks
Alan
Click to expand...
Click to collapse
Hi, I have exactly same problem as you. I didn´t try browsing these weird files you posted here but I have same symptoms as you.
My device work perfectly with flashed Rootbox ICS ROM but when I flash new ROM like PA JB or ressurection JB i´ll end up with bootloops.
Robotr0n said:
Hi, I have exactly same problem as you. I didn´t try browsing these weird files you posted here but I have same symptoms as you.
My device work perfectly with flashed Rootbox ICS ROM but when I flash new ROM like PA JB or ressurection JB i´ll end up with bootloops.
Click to expand...
Click to collapse
Hi Robotr0n,
Have you tried flashing any stock rom yet. In most case that should help. I heard that some custom JB rom have different partition layout and might introduce bootloop.
Mine is in more severe situation. One or more partitions are corrupted so I cannot wipe nor new rom cannot write data (even though Odin can successfully flash the new rom).
So, keep hoping for the best. I guess you still have chance to recover your phone :fingers-crossed:
In case a stock rom cannot help, I suggest making a backup of your /efs partition as soon as possible.
Thanks
Alan
alansmith_xda said:
Hi Robotr0n,
Have you tried flashing any stock rom yet. In most case that should help. I heard that some custom JB rom have different partition layout and might introduce bootloop.
Mine is in more severe situation. One or more partitions are corrupted so I cannot wipe nor new rom cannot write data (even though Odin can successfully flash the new rom).
So, keep hoping for the best. I guess you still have chance to recover your phone :fingers-crossed:
In case a stock rom cannot help, I suggest making a backup of your /efs partition as soon as possible.
Thanks
Alan
Click to expand...
Click to collapse
Hi alansmith_xda !
I´m hardly searching for solution of my problem.
I tried stock ROM but after installing stock ROM my problem persists. Only one thing helped me - flashing litening 6.1 ROM .tar via ODIN. Only after flashing this ROM I was able to flash ICS Rootbox ROM. But I wasn´t able to instal my desired ROM - Paranoid Android JB or Ressurection ROM - still have these f***n bootloops.
Now I´m running on Rootbox ICS ROM and I´m happy that atleast at this ROM is everything working perfectly, but you know, I still want PA ROM.
Anyway, check my thread where I´m tryin to solve my problem: http://forum.xda-developers.com/showthread.php?t=1870567
I have a simular problem. When i install a rom any rom my phone turns on the first time then after reboot it can't boot up.
I reseted the phone the it booted up but after i tryed to reboot it again i had the same problem. What to do?
Sorry for the bad english
I have a Galaxy Mini GT-S5570 running CM 10.1 which was installed about a month back. Yesterday my phone suddenly crashed and after rebooting it got stuck in the boot animation (cyanogenmod logo). I tried wiping the cache and data but when the CM recovery (v4.0.0.5) starts formatting /data it gets stuck. It displays formatting /data... and its their for forever.
P.S I was experiencing frequent reboots and hangs after I flashed the new badass kernel!
What i tried to did:
1. Updated CWM to latest available version but the problem exists.
2. Tried to restore my backup of cm 10.1 rom but it stucks at 'Restoring Data'.
3. Installed stock rom via odin. When Odin says Close serial port and wait until rebooting, the phone automatically boots into stock recovery
and it says:
" Installing update...
-- Applying Muti-CSC --
Multi_CSC : there are common apks
Multi_CSC : comm_so
Can't access to '/system/csc/ATL/system'.
Formatting /cache...
-- Applying Muti-CSC --
Multi_CSC : there are common apks
Multi_CSC : comm_so
Can't access to '/system/csc/ATL/system'. "
Odin says PASS but the phone is still stuck at stock recovery.
4. Wiped cache succesfully via stock recovery but it stucks at wiping data/reset (formatting /data...)
5. I then installed back CWM via odin. CWM displays the following message:
E:Can't mount /cache/recovery/command
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
Any help is surely appreciated.
Thanks.
cyanogenmod
azsrockz said:
I have a Galaxy Mini GT-S5570 running CM 10.1 which was installed about a month back. Yesterday my phone suddenly crashed and after rebooting it got stuck in the boot animation (cyanogenmod logo). I tried wiping the cache and data but when the CM recovery (v4.0.0.5) starts formatting /data it gets stuck. It displays formatting /data... and its their for forever.
P.S I was experiencing frequent reboots and hangs after I flashed the new badass kernel!
What i tried to did:
1. Updated CWM to latest available version but the problem exists.
2. Tried to restore my backup of cm 10.1 rom but it stucks at 'Restoring Data'.
3. Installed stock rom via odin. When Odin says Close serial port and wait until rebooting, the phone automatically boots into stock recovery
and it says:
" Installing update...
-- Applying Muti-CSC --
Multi_CSC : there are common apks
Multi_CSC : comm_so
Can't access to '/system/csc/ATL/system'.
Formatting /cache...
-- Applying Muti-CSC --
Multi_CSC : there are common apks
Multi_CSC : comm_so
Can't access to '/system/csc/ATL/system'. "
Odin says PASS but the phone is still stuck at stock recovery.
4. Wiped cache succesfully via stock recovery but it stucks at wiping data/reset (formatting /data...)
5. I then installed back CWM via odin. CWM displays the following message:
E:Can't mount /cache/recovery/command
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
Any help is surely appreciated.
Thanks.
Click to expand...
Click to collapse
the problem shoudl be with cm partitioning system, in my galaxy y i've installed cm7.2, it changes the format of the device partition, i guess it was "rfs" and it turned into "ext4", if this happened to your device it can be the problem
i will say some things but try one at once
if the problem was with me i would
try checking Re-partition at odin (be carefull, if you remove the usb or shut down your phone this can be the end)
try using "phone bootloader update" at odin (dangereous too)
try to use "phone efs clear" at odin (i dont know if this is dangereous)
try flashing stock kernel via cwm or odin (this one is)
if no one works re-flash cyanogenmod (but if the problems are partitions it wont work)
gkillershots said:
the problem shoudl be with cm partitioning system, in my galaxy y i've installed cm7.2, it changes the format of the device partition, i guess it was "rfs" and it turned into "ext4", if this happened to your device it can be the problem
i will say some things but try one at once
if the problem was with me i would
try checking Re-partition at odin (be carefull, if you remove the usb or shut down your phone this can be the end)
try using "phone bootloader update" at odin (dangereous too)
try to use "phone efs clear" at odin (i dont know if this is dangereous)
try flashing stock kernel via cwm or odin (this one is)
if no one works re-flash cyanogenmod (but if the problems are partitions it wont work)
Click to expand...
Click to collapse
thnks mate will surely try and tell the results
azsrockz said:
thnks mate will surely try and tell the results
Click to expand...
Click to collapse
did it worked?
the curiosity is killing me.
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..
Good Day.
I was trying to flash TWRP on my Samsung S5. Unfortunately, i bricked it due to wrong recovery. Had an ATT custom recovery issue
Tried flashing ROM, and i got stuck at Emergency firmware recovery issue, use kies to reload recovery and try again (something like that)... i tried flashing Kitkat stock ROM and the CP removed the error... but the phone hangs at samsung S5 logo screen.
Retrying to flash AP and CSC always give me E: failed to mount system, cache. ODIN always fails at cache for CSC flashing, the only flashable thing has been CP.
I can access stock recovery, but whenever i boot into recovery, it shows No command and below, i see
E: failed to mount /system (invalid argument)
# MANUAL MODE #
-- Appling Multi-CSC...
E: failed to mount /system (invalid argument)
can't mount '/system (invalid argument)
I've searched for all ways to mount system or something, got nothing. I've wiped cache and factory/data reset.
Please i need help...I was previously on Android 5.0 ROM, awkwardly being a G900F ROM...