Database Info

[Q] Major issues with my Desire S

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

[Q] CM7 to Mezmerize Stock issues

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.

[Q] NEXUS S Cache and Boot Loop problem

Ill start with what I was trying to do.
I wanted to port the new ICS on my Nexus S i9020, I got ClockWorkMod and Went through all the steps that were needed and then I had to boot the phone to see if it worked, but it stayed on the white Google sign.
I Pulled out the battery and put it back in more than 30 times and still didnt work. So now I cant access the phone itself only recovery mode.
When im in recovery all I get is cache failure, i get:
E: can't find misc
E: failed to find "cache" to mount at "/cache"
E:Can't mount cache/recovery/command.....etc.
Im new to this, Im not sure what I should do. Can anyone help?

I have had same problem as yours, try flash newer version of recovery via adb in bootloader and then flash rom
ics is not stable yet, flash 2.3.6,wait for another week for ics

qtwrk said:
I have had same problem as yours, try flash newer version of recovery via adb in bootloader and then flash rom
ics is not stable yet, flash 2.3.6,wait for another week for ics
Click to expand...
Click to collapse
Yeah thats what I think I need to do, but i really dont know how Im supposed to do that.. Can you help me out?

CWM Recovery Solution need help!

I posted in troubleshooting but hadn't received a reply and wasn't sure if I had posted in the wrong forum so here I go
Firstly I hope this is the right subforum for this post.
So I am pretty much stuck with a brick atm( can make calls / texts ) and I am not sure where I went wrong.
I went and unlocked my phone, unlocked the bootloader and installed CWM.
But when I went to flash a ROM and Gapps I encountered a problem
When I went to go and wipe data and cache I got these errors.
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 still proceeded to go ahead and try and flash Gapps and Liquidsmooth ROM.
When I selected to reboot after the flash my phone did nothing.
The screen was black and I was forced to reboot with Volume up/ Power.
Now I have found a thread in a sub forum of another phone but was hoping to find a Razr HD XT925 specific fix,
I will link the forums for reference but I am worried I may have bricked my phone.
When I do get it to boot it is practically the stock ROM but no Gapps, some buttons dont work.
reference links :
http://forum.xda-developers.com/show....php?t=1713419
http://forum.xda-developers.com/show....php?t=1492940
I hope someone can help me fix this issue
Thankyou in advance.
I also cant get my phone to recognise that it is in fact in USB debugging mode and I wasn't able to re run the Motopocalypse and Motochopper

Is my Nexus 5's storage corrupted?

Before this happened I was running CM11 on my Nexus just fine for a few weeks or so. It randomly rebooted, and then got stuck in a boot loop. Now, here's what's weird. When I booted into CWM, the only partitions I could mount were /system & /firmware. /data, /cache, & /persist all just give "Error mounting /partition!". Here's what I also get when navigating through CWM:
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
When I format the /cache partition it works just fine, but I still can't mount it and the issues above continue. When I try to wipe data/factory reset it just gives me an error mounting /data and skips it, along with /sdcard. This also means I can't install a zip from the device. I tried sideloading the stock ROM onto the device but it just prints this:
symlink: some symlinks failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Anyone who could point me in the right direction would be much appreciated. Flashing anything with fastboot doesn't seem to change anything either, by the way (including trying to change to TWRP) Thanks again.
Sent from my XT1034 using Tapatalk

I take it you've tried to flash the factory image with fastboot? Do you get anything if you type fastboot devices?

jd1639 said:
I take it you've tried to flash the factory image with fastboot? Do you get anything if you type fastboot devices?
Click to expand...
Click to collapse
I have indeed tried to flash the factory image. And the device status shows up in fastboot when I do fastboot devices.
Sent from my XT1034 using Tapatalk

try this
n1kolan said:
Before this happened I was running CM11 on my Nexus just fine for a few weeks or so. It randomly rebooted, and then got stuck in a boot loop. Now, here's what's weird. When I booted into CWM, the only partitions I could mount were /system & /firmware. /data, /cache, & /persist all just give "Error mounting /partition!". Here's what I also get when navigating through CWM:
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
When I format the /cache partition it works just fine, but I still can't mount it and the issues above continue. When I try to wipe data/factory reset it just gives me an error mounting /data and skips it, along with /sdcard. This also means I can't install a zip from the device. I tried sideloading the stock ROM onto the device but it just prints this:
symlink: some symlinks failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Anyone who could point me in the right direction would be much appreciated. Flashing anything with fastboot doesn't seem to change anything either, by the way (including trying to change to TWRP) Thanks again.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
I've had the same issue while using recovery mode with certain toms and I was also worried at first. It usually happens after a bootloop.
Try this:
1) If your device gets stuck during boots and it seems like its taking forever and just wont get past the boot phase then do this: boot up again and just wait for a while. Be more patient than last time let the process go on for five or so minutes THEN do a hard power off (gold down power button until it turns off). Then turn back on while holding volume to boot into recover. Now check to see if your partitions are back (THIS IS WHAT WORKED FIR ME). If still gone, try again but this time instead of waiting a while do the hard power off sooner in the boot process, maybe about 30s to a minute in or at about the time when it usually would have completed booting back when it was working. Boot back to recovery, check for partitions. If still not there repeat the steps a few more time doing the hard power off at different intervals (first try doing it almost immediately, then try waiting even longer than before, then try after 15s, ext...). My experience has been if u do the hard power off at the right point of timing during the bootloop you will have shut it off either before or after (not sure which) the point during the booting process where it is screwing up and making your partitions look like they are gone. They really are not and your data should still be there in SD area if u didn't delete it, cwm just isn't seeing the partition because of some error during boot process.
OR
2) If it continually resets try to time it then doing a hard power off (hold power button several seconds until your device shuts off) at the latest possible moment before when it normally resets. Then turn your device back on holding volume buttons to get to recovery mode and see if the partitions are back. If not, try a couple more times.
Anyway that's what worked for me. At first I was pissed and thought my data was gone to and I was gonna have to do full unbrick process but nope, after shutting off at the right point during the bootloop or indefinite boot process I found that when I went back into recovery mode cwm could see my partitions and all my data and all I had to do was reinstall a different kernel I had in the SD area of my memory and next time it booted right up. If installing or reinstalling a different kernel (one that worked before for u) doesn't fix it or isn't possible just while and reinstall any ROM or backup IMG u got stored in memory and install that then next boot will hopefully work fine.
If none of those steps restored your partitions or fixed it back so cwm or teamwin could see them then u will prolly have to USB to computer and go through unbrick process.
Hope this helps
---------- Post added at 10:32 PM ---------- Previous post was at 10:26 PM ----------
n1kolan said:
I have indeed tried to flash the factory image. And the device status shows up in fastboot when I do fastboot devices.[\QUOTE]
Depending on what u did it may be too late to try my suggestion I gave above but if u are still getting a bootloop and haven't figured it out yet then trying my above suggestion it is still worth a shot.
Click to expand...
Click to collapse

Thanks a ton for the help, but I'm afraid its too late. I've formatted the system & data partitions already. What's weird however is when I turn it on normally it still shows the CM splash screen.
Sent from my XT1034 using Tapatalk

Alright, I tried wiretaps suggestion but still nothing. I'm unable to mount anything except for system and firmware. Any other suggestions?
Sent from my XT1034 using Tapatalk

n1kolan said:
Alright, I tried wiretaps suggestion but still nothing. I'm unable to mount anything except for system and firmware. Any other suggestions?
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Flash twrp 2.6.3.4 and in wipe, format data.

jd1639 said:
Flash twrp 2.6.3.4 and in wipe, format data.
Click to expand...
Click to collapse
I've tried flashing TWRP, it sends and writes without an error. But when I boot into recovery CWM is still there :/

well if you've given up on recovering your partitions...
and all you want is to get your device working again you can always just follow the unbrick instructions. There us a guide posted on thus site somewhere I'm sure about how to do it using the android SDK but if you aren't very savvy with command line utilities there is an all in one program for windows with a darn good GUI (graphical interface) that works pretty damn well and will automate all the steps you need to return your Nexus 5 back to the way it came.
The software is called Nexus Root Toolkit and you can find it on Google or download it from this link: won't let me post just search for nexus root toolkit download on google
I have used it several times on my Nexus 4 and two different Nexus 5s without any problems or errors. Just install the application on a windows machine and follow instructions. Connect your device via USB and open it up. First it will either prompt u to download some files you will definitely need for it to work or it will ask you what device you are connecting then download all the necessary files. The windows drivers, factory images, android SDK ext. Everything u need, its completely automated all you gotta do is click yes read the instructions and follow the prompts.
Most people who download it do so because its an easy way to go through all the steps to unlock and root your nexus but it also has tons of other options including an option to completely "unbrick" your phone and return it to factory warranty condition just like the way it came. You will have to allow it to download the factory images for boot loader and the original OS but just follow the prompts it really is quite easy even for a newbie who is uninitiated with android development.
You might not need to do the full unroot relock process but if u just want to return the phone to factory condition then go for it. After you finish you can use the same app to unlockbit again and reroot it.
I'm sure there are plenty of Android developer SDK purists around here who would scoff at the idea of using the automated toolkit and say you should learn how to do it all by hand withe SDK command line way but u think that is over your head go on and use the toolkit there is no shame in it and it seems to work very well. I never encountered any problems with it.

1. DO NOT USE A TOOLKIT (as mentioned above)
2. Follow the factory reset thread to flash the factory image (you could try to leave out the userdata.img if you don't wanna lose your data)
3. Once confirmed working again, flash a recovery and a new ROM (and be careful in future )

EddyOS said:
1. DO NOT USE A TOOLKIT (as mentioned above)
2. Follow the factory reset thread to flash the factory image (you could try to leave out the userdata.img if you don't wanna lose your data)
3. Once confirmed working again, flash a recovery and a new ROM (and be careful in future )
Click to expand...
Click to collapse
+1.
And just to be picky, below the 3d link for factory reset:
http://forum.xda-developers.com/showthread.php?t=2513701
P.S. new to XDA, hi @ all

I've done it both ways. With the toolkit and without. Both ways worked fine. I really don't get all this anti-toolkit sentiment around here. Not everybody is as savvy at using SDKs and coomand line as many of you may be. For some people where the whole SDK command line instructions are truly over their abilities I see no reason why they shouldn't at least have the toolkit to use as a backup option.

wiretaps said:
I've done it both ways. With the toolkit and without. Both ways worked fine. I really don't get all this anti-toolkit sentiment around here. Not everybody is as savvy at using SDKs and coomand line as many of you may be. For some people where the whole SDK command line instructions are truly over their abilities I see no reason why they shouldn't at least have the toolkit to use as a backup option.
Click to expand...
Click to collapse
How can one command be over anyone's abilities. Fastboot flash will cover 90% of anything you need to do.

jd1639 said:
How can one command be over anyone's abilities. Fastboot flash will cover 90% of anything you need to do.
Click to expand...
Click to collapse
+1.
In Fastboot we trust!

n1kolan said:
I've tried flashing TWRP, it sends and writes without an error. But when I boot into recovery CWM is still there :/
Click to expand...
Click to collapse
hmmm... i smell a fried emmc.(hope not)
try to lock bootloader with fastboot, then reboot-bootloader and see if it still unlocked.
if yes so there is a hardware problem.... nothing will stick

samersh72 said:
hmmm... i smell a fried emmc.(hope not)
try to lock bootloader with fastboot, then reboot-bootloader and see if it still unlocked.
if yes so there is a hardware problem.... nothing will stick
Click to expand...
Click to collapse
uhm.. pretty logic.
nice information. Thanks you.

samersh72 said:
hmmm... i smell a fried emmc.(hope not)
try to lock bootloader with fastboot, then reboot-bootloader and see if it still unlocked.
if yes so there is a hardware problem.... nothing will stick
Click to expand...
Click to collapse
Will try this when I get home
Sent from my XT1034 using Tapatalk

Alright update: I tried what samersh72 said, and it said it was still unlocked. Looks like its a hardware problem... :/
Sent from my XT1034 using Tapatalk

jd1639 said:
How can one command be over anyone's abilities. Fastboot flash will cover 90% of anything you need to do.
Click to expand...
Click to collapse
You might be surprised. There are a lot of younguns out there who have never so much as even seen a command line. I'm sure your response will be that they have no business rooting or installing Roms on their phones in the first place but such is the way of the world.

n1kolan said:
Alright update: I tried what samersh72 said, and it said it was still unlocked. Looks like its a hardware problem... :/
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
I had the same problem, and couldn't find a solution. No partitions could mount, couldn't write to them, flashing and erasing recovery didn't do anything as it'd still boot to the one I had before, and to top it off fastboot OEM lock wouldn't stick. I had to rma it, and hope that whoever gets it is extremely tired from a long day and just passes it through without any checks.