my Samsung galaxy tab 7.0 plus wifi us version GT-P6210ma 16gb is stuck on the samsung startup logo it started when my tab got lowbat then i recharged it for awhile when i opened it the issue happened. i already tried using odin and flashing my tab to its original firmware then wipe data/ factory reset then reboot but after reboot this problem showed up.
updating application
E:failed to mount /system (invalid argument)
E:install_application_for_customer:Cant mount /system
appling Multi-CSC
E:failed to mount /system (invalid argument)
E:multi_csc:cant mount /syste
i found P6210UEKL1, it passed on odin i didnt encounter any error on odin, but had error problems on the tab when its updating
Well I regret to inform you that you most likely have to send it in to Samsung. This happened to me before and I tried many different things with no good results.
If you haven't lost the ability to put the device into odin mode, I'd get the latest firmware LA3 using checkfus and use this to restore the device. Don't worry about wiping data or factory reset.
grahamtelly said:
my Samsung galaxy tab 7.0 plus wifi us version GT-P6210ma 16gb is stuck on the samsung startup logo it started when my tab got lowbat then i recharged it for awhile when i opened it the issue happened. i already tried using odin and flashing my tab to its original firmware then wipe data/ factory reset then reboot but after reboot this problem showed up.
updating application
E:failed to mount /system (invalid argument)
E:install_application_for_customer:Cant mount /system
appling Multi-CSC
E:failed to mount /system (invalid argument)
E:multi_csc:cant mount /syste
i found P6210UEKL1, it passed on odin i didnt encounter any error on odin, but had error problems on the tab when its updating
Click to expand...
Click to collapse
find pit file, and reflash using odin with 'repartition' checked.
Related
...Samsung galaxy s 4g.....Long story short i failed at flashing a custom ROM and bricked my phone (my phone kept boot looping..idk if it's considered bricked)...i searched up how to unbrick using odin and it worked. The guide told me to flash this rom to my phone:
http://forum.xda-developers.com/showthread.php?t=1063696
Everything went fine but when i go into the android system recovery <3e> i get this:
E: Can't Mount /dev/block/st1ll
(invalid argument)
E: Can't mount CACHE:recovery/command
#MANUAL MODE#
E:Can't mount /dev/block/st1ll
(invalid argument)
E: Can't mount Cache:log/recovery.log
E: can't open Cache:log/recovery.log
E: Can't mount /dev/block/st1ll
(invalid argument)
The phone starts up and everything but i cant do a factory reset anymore (i would like to revert to un-rooted stock firmware) and any application i try downloading from the market is unsuccessful.
Any fixes/suggestions. Your help will be appreciated.
i'd re-flash again. get 2.3.4 and make sure you wipe cache/factory reset afterwards. use odin 1.85
Can you give me some links reliable downloads? they would be appreciated.
what rom are you trying to flash?
You need to flash The pit file along with the PDA it will fix that
Sent from my SGH-T959V using XDA Premium App
I bricked my phone first time I tried to flash ROM after missing the mount/unmount section. I followed this guide and I was able to get phone back to stock.
http://forum.xda-developers.com/member.php?u=4132811
Thank you guys for all the help, my phones back to normal!
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
Alright so here's the breakdown, my Nexus 5 has recently run into a problem where it suddenly decided to get stuck in a bootloop. I figured I could just reflash the stock rom via the boot loader with the wugfresh root toolkit but that unfortunately didn't work. But by doing this I noticed that my bootloader was not staying unlocked when I try to unlock it. Every time I unlock the boot loader and it restarts the bootloader automatically re-locks. I then proceeded to try and manually flashing the stock rom files individually and unlocking the bootloader each time I flash a file which was really annoying. It still hasn't worked and I'm starting to get worried because I've also started to notice my recovery can't really factory reset or wipe the cache.
Instead I get this message at the bottom of the screen:
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/log
E:Can't open /ache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_log
E:Can't open /ache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_install
E:Can't open /ache/recovery/last_install
E:failed to mount /cache (Invalid argument)
....So now I'm completely stumped, could this be the end of my Nexus 5? Please if someone could help me out with a solution I would really really really appreciate it!:crying:
Try booting into fasboot and type "fastboot erase userdata" and then type "fastboot flash userdata userdata.img". These two commands will completely wipe your data. Then, immediately boot into recovery and perform a full wipe.
The img file is included with the stock Google ROM you are flashing to the phone.
Thanks for the suggestion, but I've tried that and still have had no success
Any other ideas?
If the bootloader is relocking itself after every reboot, the emmc is probably defective and the only solution would be a new motherboard.
ughhh thats not what I needed to hear....
Zenithity said:
ughhh thats not what I needed to hear....
Click to expand...
Click to collapse
Maybe help you
forum.xda-developers.com/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937
Hey, so I somehow bricked my Galaxy S6 SM-G920F. I wanted to root it, but then I got stuck in download mode (at this point I think I made a huge mistake, because I haven't done backup of my device before). So I flashed G920FXXU5DQA7_G920FBTU5DQA2_BTU with odin. It works just fine for me without any errors to get at least in recovery mode, because anthores I tried don't work. But when I flash it, blue screen with "installing system update" and loading android logo show up for a few seconds and then immediately recovery mode comes back, where at the bottom I get these errors:
Suported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity verification failed...
Tried to do emergency recovery with smart switch. It passes without any fails, but then I get stuck in recovery mode with same errors. When I try to reboot system, black screen shows up. Did I somehow lost my efs file? I'm not a pro at these situations, so I really need help.
Hi guys,
I wanted to upload new Odin software to my Samsung S8 + and I marked clear efs by mistake. Currently, the phone when switching on stops at the Samsung logo.
Download mode working, recovery mode working but:
E: failed to mount /efs (invalid argument)
E: failed to mount /efs (invalid argument)
E: failed to mount /efs (invalid argument)
dm-verity error
how to fix it?
soniqgsm said:
Hi guys,
I wanted to upload new Odin software to my Samsung S8 + and I marked clear efs by mistake. Currently, the phone when switching on stops at the Samsung logo.
Download mode working, recovery mode working but:
E: failed to mount /efs (invalid argument)
E: failed to mount /efs (invalid argument)
E: failed to mount /efs (invalid argument)
dm-verity error
how to fix it?
Click to expand...
Click to collapse
Hi mate
First some more info...
What firmware you had?
Was it working?
What firmware are you trying to flash?
What files did you use , odin settings?
Hey guy's,
I am having similar problems to OP. The "DM Verity error"
The other day my S8+ went into boot loop all of a sudden, I tried all the simple solutions, factory reset etc, nothing worked. The phone kept booting and wouldn't make it past the device model screen. I have tried multiple firmware for my region and have tried dropping down to Nougat.
At this point in time I am able to successfully flash with Odin, haven't had a failed flash yet. Once the flash completes, the device restarts, goes to device model screen and will either enter the "installing update" screen where the install will either crash straight away or at 25%(no more no less), then only sometimes will it take me to the recovery menu.
Down the bottom of the recovery menu is the "DM Verity error". I then proceed to wipe cache, factory reset then reboot device, only to be stuck in a boot loop or on the crashed install screen.
The device is still under warranty but due to dropping it (with glass prot and case on), a small mark has appeared on the LCD. I tried to return the phone to get the software issue fixed but will be charged $400 to replace the screen as Samsung will not send the phone back in an "un-warrantable" state.
I have been trying to solve this issue but i'm finally stumped.
Any help would be very much appreciated.
Thanks.
I wanted to change IMEI of my Samsung S8 + and I dont know at which step i did mistake. it is showing the Samsung logo and boot loop again and again .
Download mode working, recovery mode working but:
E: failed to mount /efs (invalid argument)
E: failed to mount /preloader (invalid argument)
phone did not starts