Hi all,
first of all I would like to point out that although I Googled well this topic, I'm finding mixed replies which confused me rather than helped me - and seeing that this device has screwed itself up pretty badly, I do not wish to experiment haphazardly.
So, for the problem:
Around 2 weeks ago, I had S-OFFed and rooted my Desire S by using Revolution. This worked well. I kept my original unbranded firmware, and had no intention of changing nor flashing any different firmware - all I wanted was root access for some apps. No, I haven't taken any backups.
No problems so far, however since my phone was over loaded with apps, I found it easier yesterday to simply do a factory reset (from the menu) and start from scratch than uninstalling each and every app one by one. Nothing illegal a simple factory reset which anyone can do.
I thought it went well, however I started having frequent crashes and infinite reboots. The only way out of the infinite reboot was to remove the battery and restart the phone.
Today however, after the Nth time that this happened, my phone stayed loading on the white HTC screen forever. Eventually, seeing tthat his was getting hopeless I opened the bootloader and I got the following error messages:
Code:
Revolutionary CWM v4.0.1.4
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
I tried wiping and formatting the /cache partition from recovery mode. Wiping succeeded however errors remained. Formatting failed.
As it is the phone is just stuck at loading. What do you suggest is the best solution?
Code:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3005.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
Is it possible to go back to stock BL and go back to S-ON?
Oh, and the battery is currently around ~18% and I cannot find a way of recharging it (and I don't know anyone else with a Desire S nor do I have a wall charger).
What do you think the best option is? I'm currently extremely annoyed at this phone as my only offence was of performing a factory reset from the main menu! I bought it new from eBay last May!
Thank you all and sorry for writing so long!
6.98.2003
Click to expand...
Click to collapse
interesting bootloader version. never seen before
try to flash 4Ext Recovery and format the partitions with it...
http://forum.xda-developers.com/showthread.php?t=1284196 < main
http://forum.xda-developers.com/showthread.php?t=1307543
http://forum.xda-developers.com/showthread.php?t=1307233
http://forum.xda-developers.com/showthread.php?t=1305950
http://forum.xda-developers.com/showthread.php?t=1226849
Hi
I dont know about this issue...
I dont have a Desire S... (but i have a Desire)
But i might be able to help you out
Fastboot has functions to flash or erase any partition on the phone...
See this page: hxxp://wiki.cyanogenmod.com/wiki/Fastboot
My opinion is to try erasing the cache partition from fastboot...
Also see these links... might be something to do with a fried eMMC chip
hxxp://forum.xda-developers.com/showthread.php?t=1284196
hxxp://forum.xda-developers.com/showthread.php?t=1150917
Tell us on what you did and how it went...
amidabuddha said:
interesting bootloader version. nver seen before
try to flash 4Ext Recovery and format the partitions with it...
Click to expand...
Click to collapse
Sorry, HBOOT-6.98.1002 (updated post)
I must've made a typo hehe
Thanks all for the replies. As soon as I get home I'll take a look into everything you mentioned. I also want to check whether the warranty is still valid (rooted) since I found online that the Desire can be rooted and warranty remains valid - maybe this is the same. If that's the case, I'll just take it to an authorised HTC dealer and leave it up to them.
Thank you all!
Code:
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
I have already received the above errors numerous times when flashing my phone. Also noticed if received these errors, my CACHE is not recognized by recovery..
I don't know if we have the same problem..
My method of fixing this:
1. remove the battery for 30secs to 1 minute and putting it back in
2. boot directly to your bootloader, then go to recovery
3. If you haven't received the errors, your cache will be formatted to EXT3, try formatting it to ext4 if need be
4. I wipe everything (all partitions) including dalvik cache and battery stat
5. flash your rom again, cross your fingers and hope for the best..
check my sig for more info..
Skanob said:
Code:
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
I have already received the above errors numerous times when flashing my phone. Also noticed if received these errors, my CACHE is not recognized by recovery..
I don't know if we have the same problem..
My method of fixing this:
1. remove the battery for 30secs to 1 minute and putting it back in
2. boot directly to your bootloader, then go to recovery
3. If you haven't received the errors, your cache will be formatted to EXT3, try formatting it to ext4 if need be
4. I wipe everything (all partitions) including dalvik cache and battery stat
5. flash your rom again, cross your fingers and hope for the best..
check my sig for more info..
Click to expand...
Click to collapse
You are lucky (or smart enough) to have 4EXT Recovery. With ClockworkMod is not that easy But the solution is the same with one additional step (it is described in the guide in my signature)
I have also faced this kind of errors, except I couldn't even get to the recovery.
I manage to resolve it this way http://forum.xda-developers.com/showpost.php?p=18622540&postcount=4 but I can't really help you with getting it back to S-ON.
You should be able to change your recovery without any problem if your s-off or unlocked 2.xx.xx hboot s-on.
1. Get 4ext recovery.img
2. connect phone on fastboot
3. In cmd use these command to push the recovery image:
Fastboot flash recovery D::\recovery.img (<- should be directory of 4ext recovery image)
Fastboot reboot-bootloader
Now you should have 4ext recovery.
P.s.
Cmd code may need to be corrected, as using my phone right now. Hope memories serves me right.
Sent from my HTC Desire S using XDA App
Skanob said:
You should be able to change your recovery without any problem if your s-off or unlocked 2.xx.xx hboot s-on.
Click to expand...
Click to collapse
I do not think that you can use fastboot flash whatewer without an engineering bootloader (requires s-off) or push images with adb without su (requires rooting). This is the point of all the guides and tutorials around here...
i'm also got this error many time.
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
Click to expand...
Click to collapse
but full data/cache wipe solve the problem.
amidabuddha said:
I do not think that you can use fastboot flash whatewer without an engineering bootloader (requires s-off) or push images with adb without su (requires rooting). This is the point of all the guides and tutorials around here...
Click to expand...
Click to collapse
You actually can.. Check my sig.. I have already flashed a stock recovery then back to 4EXT many times.. I am on OFFICIAL HBOOT from the 2.10.401.4 update..
flashing OFFICIAL RUUs prior to latest hboot didn't work for me as the HBOOT seems to be un-writable to old HBOOTs. I haven't tried revolutionary's 6.xx.xx HBOOT though..
I am on unrooted STOCK RUU when I tried to flash the update forcefully. HBOOT and RECOVERY got updated so got me stock on HTC logo (without the "quietly brilliant") means ROM is not booting.
That is the method I used to revive my phone.
Edit:
"Unlocking" my S-ON could've helped me..
Skanob said:
You actually can.. Check my sig.. I have already flashed a stock recovery then back to 4EXT many times.. I am on OFFICIAL HBOOT from the 2.10.401.4 update..
flashing OFFICIAL RUUs prior to latest hboot didn't work for me as the HBOOT seems to be un-writable to old HBOOTs. I haven't tried revolutionary's 6.xx.xx HBOOT though..
I am on unrooted STOCK RUU when I tried to flash the update forcefully. HBOOT and RECOVERY got updated so got me stock on HTC logo (without the "quietly brilliant") means ROM is not booting.
That is the method I used to revive my phone.
Edit:
"Unlocking" my S-ON could've helped me..
Click to expand...
Click to collapse
Ok taking my words back And how do you did this? You flashed the Stock 2.10.401.4 ROM over you bricked phone and it worked? (overwritted the revolutionary hboot or which version was it before?).
To make the long story short:
I stupidly get the firmware.zip file inside the ota file. That file had the latest hboot, recovery, and others. I renamed it to the correct pgxxximg.zip (cant remember the correct filename, currently drinking ) to flash it from bootloader.
Everything went well. Everything inside the file updated the corresponding file/partition/image to my phone. Hence letting me be stock to the "locked" hboot 2.xx.xx s-on. ROM wouldnt boot as I said.
Being on the "locked" state wouldn't allow me to flash anything on the phone as far as i can remember. While writing, it will say has its unsuccessful.
But "unlocking" the hboot let me flash the recovery.
Sent from my HTC Desire S using XDA App
I just realised I never left an answer as to how I resolved this problem (around a year ago!).
The flash chip itself was fried and it apparently was a problem with a good number of Desire S phones.
Took the device for warranty and it got replaced with a brand new mainboard.
Happy ending
Sent from my HTC Sensation using Tapatalk 2
So I flashed CM7 to my phone a while back. It worked. Fantastic.
There were some drawbacks to having a pre-nightly rom so I wanted out. I looked at the dev forums and saw the instructions to flash the full stock rom to the phone. A genuine factory reset. I followed the instructions, hoping it would work (and before anyone asks, yes, I did turn off the lagfix in voodoo).
Odin continually fails to flash the stock rom onto my phone and now I can only get to the bootloader on my phone. I can't mount USB storage, I can't get anything onto my phone to flash with CWM, and I now have a phone I cannot use until I get this fixed.
Obviously I did something wrong, but I'm having trouble retracing my steps to find out what that wrong move was. If anyone knows what I did wrong just by reading this, awesome, please help me out.
Also, when I try to mount usb storage from CWM, I get an error saying
E:Unable to open ums lunfile (No such file or directory)
Click to expand...
Click to collapse
and on loading the bootloader I get
ClockworkMod Recovery v4.0.1.0
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
Click to expand...
Click to collapse
Don't know if you're still having an issue, but flash ec10 or ee19 through Odin, and make sure to check re-partition. You can either stay there or go to the gingerbread based EH09, which is the official firmware. Before you flash that in Odin, uncheck re-partition. It might say that it failed. If it does, disconnect the phone, put the battery back in and power it up. If it works, and it should, you're golden. Hope this helped
Sent from my SCH-I500 using XDA App
I had the same scenario w/ my Showcase. I did everything "correctly", and I never could get GB to load back on there after loading CM7.1. I tried multiple versions of 2.2 through Odin, I constantly got FC's. Then I tried reloading GB, I got stuck in boot loop. I had to send it in to Samsung... under warranty.
Okay so I really need some help. I was installing CWM 10 and decided to try another one when the home key didn't work, and tried to go with Slim Bean. The phone has been stuck in boot loop ever since. I can however get into recovery but no luck there. None of the backup zips will flash and I am in CWM 5.0.2.7. I normally will just flash back to stock in an instance like this but now Odin wont even come up with a COM when i plug it in. I also have tried Heimdall to no avail. All it says under Recovery is
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/reovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any ideas, I am willing to try anything
cwm 5.x is CM9.
CM10/JB has cmw 6.x
it's hard to tell how you got from jb cmw 6 to ics cmw 5 .
it's possible your partitions are also messed up.
you may need to start over with a return to stock package via Odin or Heimdall.
qkster said:
cwm 5.x is CM9.
CM10/JB has cmw 6.x
it's hard to tell how you got from jb cmw 6 to ics cmw 5 .
it's possible your partitions are also messed up.
you may need to start over with a return to stock package via Odin or Heimdall.
Click to expand...
Click to collapse
I read somewhere about trying a jig since I can't get into download mode, I just ordered one online, hopefully that will help me to return to stock. Thank you!
valcat22 said:
I read somewhere about trying a jig since I can't get into download mode, I just ordered one online, hopefully that will help me to return to stock. Thank you!
Click to expand...
Click to collapse
np..if you are stuck in a constant samsung boot loop and cant get into download mode, it may be your power button.
look in the q/a threads if you think it may be your pwer button.
without power button issue, you should be able to get to DL mode..
getting
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/reovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
though i can get back to stock via odin to 2.3 and it boots fine.
really confused ????
Previously, i tried to update my Sensations Firmware to 3.3.2 (TMOUS) and it failed and gave a CID error (Something like that)
After that it wont boot up, i get a bit of the boot image from the installed rom and it gets cut short and the phone restarts. (Stuck in boot loop)
Ive tried to change the ROM but Clockwork mod touch recovery keeps giving me an error, ive tried every rom possible. (Error 1)
I have tried wiping the phone and everything ans still nothing works.
When i boot into recovery (CM v5.8.0.9) it said:
E: Cant open /cache/recovery/log
E: Cant open /cache/recovery/log
E: Cant open /cache/recovery/last_log
E: Cant open /cache/recovery/last_log
Any help?
Connor1744 said:
Previously, i tried to update my Sensations Firmware to 3.3.2 (TMOUS) and it failed and gave a CID error (Something like that)
After that it wont boot up, i get a bit of the boot image from the installed rom and it gets cut short and the phone restarts. (Stuck in boot loop)
Ive tried to change the ROM but Clockwork mod touch recovery keeps giving me an error, ive tried every rom possible. (Error 1)
I have tried wiping the phone and everything ans still nothing works.
When i boot into recovery (CM v5.8.0.9) it said:
E: Cant open /cache/recovery/log
E: Cant open /cache/recovery/log
E: Cant open /cache/recovery/last_log
E: Cant open /cache/recovery/last_log
Any help?
Click to expand...
Click to collapse
I have also tried to restore the phone to a back-up i made before but it still does not work :/
Honestly I recommend you to use standard cwm recovery... Touch version sometimes it fail to install rom and script, tested it on my device a months ago
Sent from my HTC Sensation using XDA Premium 4 mobile app
post the output from this command
fastboot getvar all
I did something stupid and installed rom manager, it corrupted my recovery. I restored to stock rom i found online using odin but it says you need to wipe factory settings to make it boot. The recovery is now the stock one but it displays error messages and when I choosed a command it does nothing. What should I do?
EDIT: I flashed another stock rom this time i could boot into the phone. Some of my apps went missing and superuser went missing. It was a little weird. The recovery still shows errors and no command. It says
"can't access to '/system/csc/VAU/system". I don't think I can root it again and install a custom rom. I dont know what is the right thing to do now. I just want to root it and install a rom
EDIT2: I installed another recovery called Amon-RA recovery and I still get errors. I am thinking maybe the recovery partition is corrupted. I get these errors.
E: Can't mount CACHE:recovery/command
E: Can't mount /dev/block/stl14
(invalid argument)
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
E: Can't mount /dev/block/stl14
(invalid argument)
turntaker said:
I did something stupid and installed rom manager, it corrupted my recovery. I restored to stock rom i found online using odin but it says you need to wipe factory settings to make it boot. The recovery is now the stock one but it displays error messages and when I choosed a command it does nothing. What should I do?
EDIT: I flashed another stock rom this time i could boot into the phone. Some of my apps went missing and superuser went missing. It was a little weird. The recovery still shows errors and no command. It says
"can't access to '/system/csc/VAU/system". I don't think I can root it again and install a custom rom. I dont know what is the right thing to do now. I just want to root it and install a rom
EDIT2: I installed another recovery called Amon-RA recovery and I still get errors. I am thinking maybe the recovery partition is corrupted. I get these errors.
could you please download below files and install with odin.also you need samsung usb driver
S5670XWKTI_S5670DBTKT1_DBT
Odin_GT-S5670 (odin 4.38)
Click to expand...
Click to collapse
I downloaded it and flashed it..AND I REALIZED THAT I WAS STUPID....
YOU DONT PRESS THE POWER BUTTON TO SELECT YOU PRESS HOME BUTTON.... LOL