Hey
I already tried to install 3 different version of roms and all of them have the same issue. The problem is "Status 0" .
I have recovery ClockworkMod Recovery v3.2.0.0. When I'm tried to change recovery for 4EXTRecovery v2.1.3 RC2 I recieve error "Status 7".
I tried few guides but with no success.
I tried wipe reset(wipe factory reset) but nothing help me.
Any ideas?
Thanks
After a quick google for "status 7" it seems either the rom you have downloaded is damaged, or its incompatible with your phone.
What roms have you been trying, and are you sure they are compatible with Desire S?
andrey85 said:
Hey
I already tried to install 3 different version of roms and all of them have the same issue. The problem is "Status 0" .
I have recovery ClockworkMod Recovery v3.2.0.0. When I'm tried to change recovery for 4EXTRecovery v2.1.3 RC2 I recieve error "Status 7".
I tried few guides but with no success.
I tried wipe reset(wipe factory reset) but nothing help me.
Any ideas?
Thanks
Click to expand...
Click to collapse
Need more information....
Have you rooted you phone and how?
What does your HBOOT Screen?
How method did you use to get to S-OFF?
What ROM were you running?
What happened when you tried full factory reset from RECOVERY?
did you get any errors?
basse1978 said:
After a quick google for "status 7" it seems either the rom you have downloaded is damaged, or its incompatible with your phone.
What roms have you been trying, and are you sure they are compatible with Desire S?
Click to expand...
Click to collapse
I tried to install the rom that I already have. So it's 100% good and working.
ben_pyett said:
Need more information....
Have you rooted you phone and how?
yes
What does your HBOOT Screen?
HBOOT-6.98.1002
How method did you use to get to S-OFF?
AlphaRev
What ROM were you running?
Currently I don't have any rom but I use
CoreDroid_Desire_S_GB_2.3.3_v1.2_RV.zip before
What happened when you tried full factory reset from RECOVERY?
I have recovery ClockworkMod Recovery v3.0.2.6 on starting I have errors
E: can't mount /cache/recovery/comand
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
--Wiping Data...
Formating /data
Formating /cache
Formating /sd-ext
Formating /sdcard-.androind_secure
Data wipe complete
E: can't mount /cache/recovery/comand
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
did you get any errors?
After wipe reset and installing rom I get:
image:
img17.imageshack.us/img17/2641/20110905074200.th.jpg
Click to expand...
Click to collapse
E: can't mount /cache/recovery/comand
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
Click to expand...
Click to collapse
sounds like a fried eMMC chip to me.. there are plenty of threads about this. Did you at any point remove the battery while the phone was on?
basse1978 said:
sounds like a fried eMMC chip to me.. there are plenty of threads about this. Did you at any point remove the battery while the phone was on?
Click to expand...
Click to collapse
Yes I did remove the battery when the device stack.
andrey85 said:
Yes I did remove the battery when the device stack.
Click to expand...
Click to collapse
See my signature Fried eMMC Chip? for a link to a long thread which contains a series of commands that will determine whether you do indeed have fried eMMC chip or not.
From the numbers of users that are currently encountering this problem it does seem to me that you can get these errors without necessary having one, so don't panic just yet.
Although I'll be completely honest I haven't yet discovered how to resolve these errors...but am working on it.
EDIT: hadn't read properly.
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
Hi guys,
I'm afraid my emmc is fried.
I have tried to flash stock factory and it stuck in the last step "erasing cache".
I have tried stock recovery, CWM and TWRP to wipe,but none worked.
And it appears on the bottom.
E: Can't mount /cache/recovery/
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
ywt474000158 said:
Hi guys,
I'm afraid my emmc is fried.
I have tried to flash stock factory and it stuck in the last step "erasing cache".
I have tried stock recovery, CWM and TWRP to wipe,but none worked.
And it appears on the bottom.
E: Can't mount /cache/recovery/
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
Click to expand...
Click to collapse
tried flashing cache image via fastboot?
rootSU said:
tried flashing cache image via fastboot?
Click to expand...
Click to collapse
Yes,but in recovery ,cache partition still can't be mounted.
I'd go back to 100% stock and make sure the phone's working correctly. One running, flash a custom recovery and see how you get on
This happened to me and what i did was factory reset and then format data reboot and then everything fine
Sent from my Nexus 5 using Tapatalk
Hi folks,
I've gone and royally f-ed up my wife's phone and she's none too happy. . . . It started with a bad CM12 update and it's just gotten worse.
Somehow my partitions are all messed up. I can get fastboot and get to recovery (had to re-flash TWRP). However, when in recover, I get all sorts of errors like:
E: Unable to mount '/data'
E: Unable to recreate /data/media folder
E: Unable to mount internal storage.
E: Unable to mount /data/media during GUI startup
Click to expand...
Click to collapse
Does anyone have any thoughts? I'm guessing that the partitions got hosed somehow, but I have no clue how to create them. . . .
Thanks,
Chris
Have you tried flashing the stock firmware yet?
Flashing stock firmware will help
If u r on lollipop bootloader then don't flash 4.4.2 firmware
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