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.
...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
phone: moto g xt1032 16gb global gsm, converted to gpe 442
problem
i downloaded the 444 ota from MEGA, installed using an old version of philz, then phone bricked (can´t start the OS)
sure, i know how to restore to stock moto g or gpe via ADB FASTBOOT, and off course i did, but the same happens, stuck at google logo, nothing happens, with both roms
i guess the partition got corrupted, or something very wrong happened with the 444 files, corrupted bootloader or something
i wanted to sideload an update using latest philz, but pc does not detect the phone while in recovery, tried to install the driver but nop, can´t be detected in custom recovery
so........help?
BTE starting philz 6.47.7
shows
e: cant mount cache/ recovery/command
e: cant mount cache/ recovery/log
e: cant mount cache/ recovery/last log
e: cant mount cache/ recovery/ last install
e: cant open cache/ recovery/log
e: cant open cache/ recovery/last log
e: cant open cache/ recovery/last install
maurocds said:
hi
phone: moto g xt1032 16gb global gsm, converted to gpe 442
problem
i downloaded the 444 ota from MEGA, installed using an old version of philz, then phone bricked (can´t start the OS)
sure, i know how to restore to stock moto g or gpe via ADB FASTBOOT, and off course i did, but the same happens, stuck at google logo, nothing happens, with both roms
i guess the partition got corrupted, or something very wrong happened with the 444 files, corrupted bootloader or something
i wanted to sideload an update using latest philz, but pc does not detect the phone while in recovery, tried to install the driver but nop, can´t be detected in custom recovery
so........help?
BTE starting philz 6.47.7
shows
e: cant mount cache/ recovery/command
e: cant mount cache/ recovery/log
e: cant mount cache/ recovery/last log
e: cant mount cache/ recovery/ last install
e: cant open cache/ recovery/log
e: cant open cache/ recovery/last log
e: cant open cache/ recovery/last install
Click to expand...
Click to collapse
Try using this version of philz recovery. This is the version I used to update my converted xt1032.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon_gpe/philz_touch_6.13.9-falcon_gpe.zip
Sent from my XT1032 using XDA Premium 4 mobile app
maurocds said:
hi
phone: moto g xt1032 16gb global gsm, converted to gpe 442
problem
i downloaded the 444 ota from MEGA, installed using an old version of philz, then phone bricked (can´t start the OS)
sure, i know how to restore to stock moto g or gpe via ADB FASTBOOT, and off course i did, but the same happens, stuck at google logo, nothing happens, with both roms
i guess the partition got corrupted, or something very wrong happened with the 444 files, corrupted bootloader or something
i wanted to sideload an update using latest philz, but pc does not detect the phone while in recovery, tried to install the driver but nop, can´t be detected in custom recovery
so........help?
BTE starting philz 6.47.7
shows
e: cant mount cache/ recovery/command
e: cant mount cache/ recovery/log
e: cant mount cache/ recovery/last log
e: cant mount cache/ recovery/ last install
e: cant open cache/ recovery/log
e: cant open cache/ recovery/last log
e: cant open cache/ recovery/last install
Click to expand...
Click to collapse
Very similar problem here. I updated to 4.4.4 via official OTA, but I had the glorious idea of restoring it later to a stock image. Now I can only access fastboot and recovery (TWRP in my case). TWRP indicates that my system and data partitions are nonexistent, so my guess is that the OTA changed the partition table. The only solution I can think of is waiting for a 4.4.4 factory image, which will fix the problem since it would have the correct gpt.bin and motoboot.bin
Maybe you guys will know the answer to this:
I'm on 4.4.3 moto firmware right now on my XT1032, but I want to go 4.4.2 GPE. What do you think, will this conclude with a bricked phone or not?
ToastnButter said:
Maybe you guys will know the answer to this:
I'm on 4.4.3 moto firmware right now on my XT1032, but I want to go 4.4.2 GPE. What do you think, will this conclude with a bricked phone or not?
Click to expand...
Click to collapse
I would advise you to wait for a 4.4.4 GPE image.
That'd be a wise thing to do, but I didn't.
Everything went fine, and I've written all about it here: http://forum.xda-developers.com/showpost.php?p=53798598&postcount=666
still bricked
if only i could install the driver when the phone is in recovery, but i can´t
cannot be detected for some reason
fastboot drivers works fine, but not in recovery
maurocds said:
still bricked
if only i could install the driver when the phone is in recovery, but i can´t
cannot be detected for some reason
fastboot drivers works fine, but not in recovery
Click to expand...
Click to collapse
I made a method to recover your phone for use! Sadly, you will only be able to use custom ROMs (at least until there's a 4.4.4 image)
Check it in my thread
http://forum.xda-developers.com/moto-g/help/recover-4-4-4-downgrade-brick-temporal-t2801946
No working fix at the moment.
http://forum.xda-developers.com/mot...4-4-bricked-phone-fixed-t2803869/post53879298
well i tried everything and still bricked
used stock recovery, philz old and new, and twc? recovery,
flashed some partition file some guy posted
used sideload, push,
flashed stock moto room 442 and stock gpe 442
used paranoid android, cyanogen, and even i have a full nandroid backup from a working moto g gpe 444
but no matter what, there is no partition so there is no way to write anything on /DATA
the best i could managed was the booting logo of cyano and paranoid, nothing else
100% brick
i just hope gpe 444 images get out someday and they work
use it here
had the same problem
http://forum.xda-developers.com/moto-g/development/rom-4-4-4-gpe-using-philz-recovery-t2806546
The problem is that it seems impossible to get this backup in the right place. Cwm does not see the files.
Sent from my HUAWEI G700-U00 using XDA Premium 4 mobile app
Hey guys.
Today I wanted to downgrade my MG from 4.4.4 using a batch file with 4.4.2 files using fastboot.
Everything except gpt.bin and motoboot said Okay. These 2 failed :/
It didn't boot so I tried to flash TWRP and install a custom rom but every recovery says
E: cant mount system
E: cant mount data
E: cant mount cache
E: cant mount sdcard
In short, nothing mounts
When booting it up nothing more than the motorola logo shows up!
Did I **** up?
Yeah, u soft bricked your phone,but you van try wiping all partitions and flashing the stock ROM using the adb.