Hello!! This is my first post and I was hoping someone will help me. I have a GT-i9100M locked to bell that wont boot. It gets stuck on the SAMSUNG splash screen. I am able to boot into recovery and download mode. But every time i boot into recovery mode i get the following error
#MANUAL MODE #
--Applying Multi-CSC...
E: failed to mount /system (invalid Argument)
can't mount '/system' (invalid Argument)
E: failed to mount /system (Invalid argument)
Im assuming my /system partition got corrupted. After doing lots of research, I have have tried to wipe data/factory reset, wipe cache partition, and re-install the firmware through Odin but didnt have any luck. One thing i should mention, is that Odin doesnt show me that my device is connected. Should i attempt to reinstall a new ROM with a bootloader? Im completely lost. If anyone got any idea what i could do to revive my phone. Ill greatly appreciated.
bmesta said:
Hello!! This is my first post and I was hoping someone will help me. I have a GT-i9100M locked to bell that wont boot. It gets stuck on the SAMSUNG splash screen. I am able to boot into recovery and download mode. But every time i boot into recovery mode i get the following error
#MANUAL MODE #
--Applying Multi-CSC...
E: failed to mount /system (invalid Argument)
can't mount '/system' (invalid Argument)
E: failed to mount /system (Invalid argument)
Im assuming my /system partition got corrupted. After doing lots of research, I have have tried to wipe data/factory reset, wipe cache partition, and re-install the firmware through Odin but didnt have any luck. One thing i should mention, is that Odin doesnt show me that my device is connected. Should i attempt to reinstall a new ROM with a bootloader? Im completely lost. If anyone got any idea what i could do to revive my phone. Ill greatly appreciated.
Click to expand...
Click to collapse
can anyone help me or suggest something? Ill appreciate it a lot
Hey man the screebshot shows that u dont have cwm
Flash it via odin first
Then try
sent by typing by my fingers
[email protected] said:
Hey man the screebshot shows that u dont have cwm
Flash it via odin first
Then try
sent by typing by my fingers
Click to expand...
Click to collapse
hey amit!! thanks for your quick response man. I dont have CWM install i only got the bell stock recovery. Will I be able to install CWM if odin is not recognizing my phone? I have attempted to falsh the stock firmware through odin but no luck. im thinking of flashing the stock firmware through a SD card. i dunno if thats a good idea.
First u have to install cwm via odin
Install ur phone drivers via kies
Then install a custom rom
sent by typing by my fingers
Having some phone issues - Samsung Galaxy S II LTE (Skyrocket). I've Googled and searched these forums, I've tried every "fix" I could but haven't found anything that specifically matches my issue here. A few months ago I did have the sticky power button issue but I don't think this is the issue here given I am not getting multiple vibrations on the reboots.
I had CM 10.2 installed and running, did a factory reset/wipe dalvik & cache/wipe system and installed AOKP 4.3. Phone was stuck in a boot loop. Restored CM backup and phone still stuck in boot loop. Used ODIN to revert to factory stock image and phone is still stuck in a boot loop. Tried clearing cache and factory reset in stock recovery and phone is still stuck in boot loop.
As far as this boot loop it flashes at the SGS II LTE "S" logo for a couple of minutes, vibrates once then reboots. As well, as soon as I insert the battery, the phone turns on, holding the power button down to turn the phone off just reboots the phone.
Also in stock recovery, I see this:
-- Verifying internal MMC block --
E:failed to mount /efs (invalid argument)
E:Mount fail : EFS partition
Not need checksum confirmation
already executed!!...
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : unknown
Successfully applied multi-CSC.
Any thoughts/ideas/possible fixes?
pixelens said:
Having some phone issues - Samsung Galaxy S II LTE (Skyrocket). I've Googled and searched these forums, I've tried every "fix" I could but haven't found anything that specifically matches my issue here. A few months ago I did have the sticky power button issue but I don't think this is the issue here given I am not getting multiple vibrations on the reboots.
I had CM 10.2 installed and running, did a factory reset/wipe dalvik & cache/wipe system and installed AOKP 4.3. Phone was stuck in a boot loop. Restored CM backup and phone still stuck in boot loop. Used ODIN to revert to factory stock image and phone is still stuck in a boot loop. Tried clearing cache and factory reset in stock recovery and phone is still stuck in boot loop.
As far as this boot loop it flashes at the SGS II LTE "S" logo for a couple of minutes, vibrates once then reboots. As well, as soon as I insert the battery, the phone turns on, holding the power button down to turn the phone off just reboots the phone.
Also in stock recovery, I see this:
-- Verifying internal MMC block --
E:failed to mount /efs (invalid argument)
E:Mount fail : EFS partition
Not need checksum confirmation
already executed!!...
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : unknown
Successfully applied multi-CSC.
Any thoughts/ideas/possible fixes?
Click to expand...
Click to collapse
READ THIS B4 POSTING | THE MOST Common Questions Answered HERE goto the general section for sticky power button
inserting battery turns on phone is symptom of sticky power button.
your error message idk, could be because phone wont/cant stay on long enough to mount partitions
vincom said:
READ THIS B4 POSTING | THE MOST Common Questions Answered HERE goto the general section for sticky power button
inserting battery turns on phone is symptom of sticky power button.
your error message idk, could be because phone wont/cant stay on long enough to mount partitions
Click to expand...
Click to collapse
As I mentioned, I had the sticky power button issue about 3 months ago and I resolved it then, I just mentioned it because I was unsure if my current issue might be related. I read the rest of that post before I posted here and didn't see anything regarding the EFS issue.
pixelens said:
As I mentioned, I had the sticky power button issue about 3 months ago and I resolved it then, I just mentioned it because I was unsure if my current issue might be related. I read the rest of that post before I posted here and didn't see anything regarding the EFS issue.
Click to expand...
Click to collapse
if it starts as soon as you put the battery in the power button is the prob, afaik no one ever had the phone boot up reinserting the battery no matter what the state the phone was in, I even wiped the phone then pulled/reinserted the battery and the phone did not boot up.
next prob is you probably had a bad flash, why you had a bad flash idk, maybe a bad emmc, the only way to tell is to reflash stock, but u need to get to odin mode to do that but you cant get to odin because of the bootloop, reason behind bootloop is the sticky power button.
it could be dumb luck that both things happened at the same time. try to get into odin mode by either mashing the power button or cleaning it out to solve the bootloop
I can get into download mode and Odin. I've flashed stock and it still bootloops.
TL;DR:
1. Bootloop started with fresh AOKP 4.3 install
2. Bootloop continued with CWM restore to CM 10.2
3. Bootloop continued with CM 10.2 fresh install (everything wiped, even factory reset)
4. Bootloop continued with Stock install via ODIN
5. Factory reset and wiped cache in stock recovery and bootloop continues.
I think the power button is a separate issue from the bootloop - but I did try the fixes in the power button section just in case and no change.
Please share the steps to resolve bootloop
pixelens said:
I can get into download mode and Odin. I've flashed stock and it still bootloops.
TL;DR:
1. Bootloop started with fresh AOKP 4.3 install
2. Bootloop continued with CWM restore to CM 10.2
3. Bootloop continued with CM 10.2 fresh install (everything wiped, even factory reset)
4. Bootloop continued with Stock install via ODIN
5. Factory reset and wiped cache in stock recovery and bootloop continues.
I think the power button is a separate issue from the bootloop - but I did try the fixes in the power button section just in case and no change.
Click to expand...
Click to collapse
I too have the same problem. Have you resolved it. I have tried all the steps like get into ownload mode and Odin. I've flashed stock and it still bootloop. Please share the steps if you resolved. I don't know what to do
Thanks, KamaL
kingkamal said:
I too have the same problem. Have you resolved it. I have tried all the steps like get into ownload mode and Odin. I've flashed stock and it still bootloop. Please share the steps if you resolved. I don't know what to do
Thanks, KamaL
Click to expand...
Click to collapse
Do a factory reset in recovery
Hi . I have a samsung galaxy next turbo (GT-S5570L) which was originally Gingerbread. I have succesfully upgraded it to jellybean plus. However when trying to upgrade to kitkat something went wrong and I think I bricked my phone. On recovery mode when I tried wipe data/factory reset a message displays
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
Moreover, when pressing install zip from sd card, it says installation complete, but when pressing apply update from sd card, it says installation aborted. On rebooting the device it won't load. Any suggestions on how to solve this problem? Thanks.
il-gawc said:
Hi . I have a samsung galaxy next turbo (GT-S5570L) which was originally Gingerbread. I have succesfully upgraded it to jellybean plus. However when trying to upgrade to kitkat something went wrong and I think I bricked my phone. On recovery mode when I tried wipe data/factory reset a message displays
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
Moreover, when pressing install zip from sd card, it says installation complete, but when pressing apply update from sd card, it says installation aborted. On rebooting the device it won't load. Any suggestions on how to solve this problem? Thanks.
Click to expand...
Click to collapse
Greetings and welcome to assist. It sounds like your pit file is corrupt, try using kies/smartswitch emergency firmware recovery and it should fix it
Good Luck
Sawdoctor
Hello all. I have a oneplus one. My phone was turned on working fine as it was charging. Then out of nowhere it went into a bootloop. The system would not boot and just stayed on the cyanogenmod boot up screen. At the time I was on cm13. I can access fastboot and twrp. While in twrp the storage will not mount. I get numerous errors when trying to format, wipe etc.. What's also strange is that in some of the instances, I get errors but at the very top it says wipe or format was successful. Any help will be much appreciated. Thanks in advance.
The errors I get:
Failed to mount data(invalid argument)
Unable to mount storage
Unable to repair system
Hey all. First post and I need your help.
S8 randomly restarted and was stuck on the "SAMSUNG" logo screen. Restarted it and it said "applying update" but then "no command" screen with dead robot.
I've tried to factory reset it but "unable to mount drive" appears. I've tried reflashing with Odin. Seeing if I could boot with adb and wipe from there, nothing.
Corrupt drive pops up on occasion and it tries to wipe itself but this message comes up after it fails.
wiping data
formatting /data
E: /sbin/mke2fs_static failed with status 37
E: format _volume: failed to make ext4 on /dev/block/bootdevice/by-name/userdata
no such file or directory
Any help would be appreciated. I dont want to have to pay for a new one.
I was able to reload everything after a NAND erase