[Q] HTC Desire S :/ ClockworkMod Recovery (Status 1) - HTC Desire S

Hello,
I'm having a problem with restoring my phone to life.
Since yesterday he stays in the white htc screen when power on.
I read many topics about that situation but non of them really solved it for me.
I have the phone S-OFF and rooted with Revolutionar.
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
I want to install CyanogenMod 7 for the HTC Desire S :: V7.1.0
So i press volume down / power into the -Revolutionary- screen.
Then RECOVERY, the phone then reboots in to clockworkmod recovery 5.0.2.0
I get the folowing messages:
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
I ignore the messenges en choose to wipe cache.
I takes a long time and then i get a message:
Cache wipe complete.
E: Can't mount /case/recovery/log
E: Can't open /case/recovery/log
E: Can't mount /case/recovery/last_log
E: Can't open /case/recovery/last_log
Now i choose to wipe data/factory reset.
Again i takes awile and then i get a message:
--Wiping data..
Formating /data..
Formating / cache..
Formating / sd-ext..
Formating / sdcard/.android_secure
Data whipe complete.
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
Now i choose advanced to wipe Dalvik Cache.
I don't get any message after this.
Now i choose to reboot recovery.
The phone reboots.
Now i choose to Wipe Data/Factory Reset once more.
Again the same messages as before - Data wipe complete.
I think the phone is empty by now.
So i choose instal zip from sdcard - choose zip from sd card.
i choose update-cm-7.1.0-DesireS-signed.zip
Confirm install - Yes install update-cm-7.1.0-DesireS-signed.zip
I get the message:
Finding update package...
opening update package...
Installing update...
E:Error in /sdcard/update-cm-7.1.0-DesireS-signed.zip
(Status 1)
Instalation aborted.
I get this message all the time even with diverent mods.
What does this meen? Please help me out of this mess

Had exactly the same issue today..
Read this if u want.. http://forum.xda-developers.com/showthread.php?t=1150917
I flashed custom recovery from here http://forum.xda-developers.com/showthread.php?t=1130004
And everyng is fine again!

pa3e said:
Had exactly the same issue today..
Read this if u want.. http://forum.xda-developers.com/showthread.php?t=1150917
I flashed custom recovery from here http://forum.xda-developers.com/showthread.php?t=1130004
And everyng is fine again!
Click to expand...
Click to collapse
I'm going to trie it in a few hours thanks for the tip!
I wil post if its works for me too.
It did not work, now i'm trying some other things see here:
[GUIDE] Read this before going for eMMC replacement.

If the beyond solution fails, take a look at this, it may help you.
http://forum.xda-developers.com/showthread.php?t=1284196
Swyped from my HTC Desire S

The answer to your problem:
Possible FIX for the infamous eMMC problem..

Just got a message from HTC Netherlands after sending my phone to them.
They say that the eMMc was fried by the s-off tool I had used. And thats why my warranty is now void. They tell me the replacement of the main board cost me €180,-
But if i dont want that and just want to get my phone back, i still need to pay them €30,- for the research of it. WTF!! next time i will microwave the freaking phone before i sent it to them. Now they just refurbish it and give it away....
I'm totaly done with this policy. thanks again for everybody's help.

spankranger said:
Just got a message from HTC Netherlands after sending my phone to them.
They say that the eMMc was fried by the s-off tool I had used. And thats why my warranty is now void. They tell me the replacement of the main board cost me €180,-
But if i dont want that and just want to get my phone back, i still need to pay them €30,- for the research of it. WTF!! next time i will microwave the freaking phone before i sent it to them. Now they just refurbish it and give it away....
I'm totaly done with this policy. thanks again for everybody's help.
Click to expand...
Click to collapse
Same thing happened to me.
In Italy they asked me € 201
I think tomorrow I'll bring back the phone.
I asked some of the forum and I think there is a solution for not spending all that money

kramegna said:
Same thing happened to me.
In Italy they asked me € 201
I think tomorrow I'll bring back the phone.
I asked some of the forum and I think there is a solution for not spending all that money
Click to expand...
Click to collapse
Im intressested, maybe we can mobilize some Desire S owners and claim a repair of this faulty chip.

Related

Need Help

I installed gummy 1.9.1 on my wifes charge a few weeks ago and she hasn't had any problems at all. Out of the blue her phone won't boot past the Samsumg logo screen. I can't get the phone recognized on odin and she doesn't have a backup from CWM. She didn't do anything to the phone to cause it. Anything I can do?
I was able to get into download mode and was able to get odin to recognize the phone. I reflashed gummy 1.9.1 through odin. Put battery back in phone and rebooted and the phone is still stuck on the samsung boot logo.
Try the instructions in this thread.
http://forum.xda-developers.com/showthread.php?t=1111486
If you want to go straight to EE4, use the PIT file from that thread, and download the stock EE4 rom from this thread.
http://forum.xda-developers.com/showthread.php?t=1116867
Have you wiped cache and data?
Sent from my SCH-I510
Yes I wiped. I'm trying the How To Fix Phone method and so far have no luck.
ercDROID said:
Yes I wiped. I'm trying the How To Fix Phone method and so far have no luck.
Click to expand...
Click to collapse
what is happening in odin when you use the ee4 stock and pit file?
you are following this right? Check the box for Re-partition (Odin will fail if you check this and don't use the PIT file) and un-check the boxes for Auto-Reset and F. Reset Time.
Everything goes through fine and it says that it passes. I reboot and the same error comes up and it boots into stock android recovery.
fitti28 said:
what is happening in odin when you use the ee4 stock and pit file?
you are following this right? Check the box for Re-partition (Odin will fail if you check this and don't use the PIT file) and un-check the boxes for Auto-Reset and F. Reset Time.
Click to expand...
Click to collapse
don't uncheck auto reset or f. reset time unless you want to bork whatever your flashing and have your data wiped on the first few reboots
blazing through on my 4G Droid Charge
ercDROID said:
Everything goes through fine and it says that it passes. I reboot and the same error comes up and it boots into stock android recovery.
Click to expand...
Click to collapse
blue android system recovery <3e>? If so i had that last night.
I had to odin FE1.9.1 to get me back in order
I tried that already. I tried the Samsung PST method going back to stock. All I get now is the samsung logo and then the charge boot animation and then it goes into a boot loop. I'm getting very tired and frustrated at this point. What would cause this to happen? My wife doesn't do any flashing or anything on her phone. I flashed this rom a month ago and she already had the OTA EE4 update. Would Verizon know what software is on the phone if i can't boot into the phone? At this point I don't know what software is on there.
This is the error I always get
--bootmode=7 from cmdline...
E:Can't mount /dev/block/mmcblk0p1
(No such file of directory)
-- Movi_check Start..!!
movinand open fail
Movinand Checksum Confirmation Fail
-- movi_checking done!...
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
Still not working. I tried the full odin of gummy 1.9.1 and the CWM did come over. I can't do anything inside of there though. I keep getting:
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I'm hoping that somebody can help me out. I'm lost at this point.
It does not seem like the PIT file works. I have tried so many things. If anyone is out there that can help please PM me and we can talk over the phone.
ercDROID said:
This is the error I always get
--bootmode=7 from cmdline...
E:Can't mount /dev/block/mmcblk0p1
(No such file of directory)
-- Movi_check Start..!!
movinand open fail
Movinand Checksum Confirmation Fail
-- movi_checking done!...
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p3
(No such file or directory)
Click to expand...
Click to collapse
damn, you know what you may need to pm Imnuts or Kejar for their help... I was trying to help another guy with this exact problem a few days ago and we got nowhere unfortunately, though that error is related to the /cache partition if it helps in your search
I contacted IMNUTS. Hopefully he gets back to me and helps me out. I have the phone going through the boot animation loop and after a few it goes to a black screen that shows my status bar(showing no connection), battery icon and time. Then it goes back to the boot animation loop.
Did you ever get this resolved? I'm having the same issue right now.
I was on GummyCharged GBE 2.1 and sometime last night it died out of no where. Wondering if it had to do with DST.
Anyhow...I've been unsucessful in getting anywhere, I've googled just about everything I can think of, and I've been working on this thing on and off for about 5hours.
Pretty new at this stuff too, so not sure if I messed it up somehow.
LinkinPrime said:
Did you ever get this resolved? I'm having the same issue right now.
I was on GummyCharged GBE 2.1 and sometime last night it died out of no where. Wondering if it had to do with DST.
Anyhow...I've been unsucessful in getting anywhere, I've googled just about everything I can think of, and I've been working on this thing on and off for about 5hours.
Pretty new at this stuff too, so not sure if I messed it up somehow.
Click to expand...
Click to collapse
through trying to guide others with this issue, troubleshooting, talking with devs, and attempting every kind of recovery I've learned that this /cache partition error (E:Can't mount /dev/block/mmcblk0p3) is a sort of perma-brick that is unrecoverable, or at least no one's been able to come up with a definite cause or fix yet... just try to Odin back to stock for whatever good it'll do and take it to verizon to get replaced
****I'll say it again for anyone who may get this error in the future: as of now there is no known cause or fix for this error, it seems to happen at random and cannot be recovered from. Please try and Odin back to stock for whatever good it'll do (at least so it looks like an accident) and see about having verizon replace it
That's what I feared. Mine's back on stock, and it just loops on the Droid Eye flash screen, I'll take my chances with Verizon.
Were you able to get your exchanged? If so, any tips on what you said?
LinkinPrime said:
That's what I feared. Mine's back on stock, and it just loops on the Droid Eye flash screen, I'll take my chances with Verizon.
Were you able to get your exchanged? If so, any tips on what you said?
Click to expand...
Click to collapse
I haven't had it happen to me but in another thread myself and others were trying to help about a half dozen people with the same issue and i believe those who reported back said they got it replaced no problem but didn't say how unfortunately
LinkinPrime said:
That's what I feared. Mine's back on stock, and it just loops on the Droid Eye flash screen, I'll take my chances with Verizon.
Were you able to get your exchanged? If so, any tips on what you said?
Click to expand...
Click to collapse
So did you get a replacement and did you have any issues in sending yours back?

[Q] CWM Can´t mount SDcard and Rom is broken

I have readed so many post, but haven´t found any help. So I dare to ask you some help.
I have S-OFF and rooted my HTC-Desire several days ago using Revolutionary. Everything went well and phone worked fine. Phone is 1 year old.
Then I did tried to install new ROM- leedroid, and it did started nicely, but after restarted few times, It didn´t start at all. Only showing that starting screen over and over again. And now it won´t do even that. I can´t flash new rom cos ClockworkMod recovery says can´t mount SDcard. SDs are working fine another phones, and I have formated them several times. I have all stuffs from that SD that was in phone, backups etc. Can´t do anything which uses sdcard. And otherwise it acts like there´s no ROM at all. When started it only flashes android text on blackscreen.
Error mounting /sdcard, E:Can´t mount /sdcard/ etc.
I also tried to connect it with computer, but it won´t connect properly. I thought that mayby that way using adb.. but not now how to and how to make connection right. It says E:Unable to write lunfile (No such file or directory) if you try to mount USB storage.
Is there anything else to do than go to do some phone shopping?
Please, if you have any ideas...
And I wish answers to be simple enough english to understand.. I´m not native english speaker.
And the only things that I can tell you about this piece of ****:
ClackworkMod Recovery v5.0.2.0
-Revolutionary-
Bravo Pvt3 Ship S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL -SYNW0101
RADIO-5.17.05.23
Aug 10 2010, 17.52:18
tristran said:
I have readed so many post, but haven´t found any help. So I dare to ask you some help.
I have S-OFF and rooted my HTC-Desire several days ago using Revolutionary. Everything went well and phone worked fine. Phone is 1 year old.
Then I did tried to install new ROM- leedroid, and it did started nicely, but after restarted few times, It didn´t start at all. Only showing that starting screen over and over again. And now it won´t do even that. I can´t flash new rom cos ClockworkMod recovery says can´t mount SDcard. SDs are working fine another phones, and I have formated them several times. I have all stuffs from that SD that was in phone, backups etc. Can´t do anything which uses sdcard. And otherwise it acts like there´s no ROM at all. When started it only flashes android text on blackscreen.
Error mounting /sdcard, E:Can´t mount /sdcard/ etc.
I also tried to connect it with computer, but it won´t connect properly. I thought that mayby that way using adb.. but not now how to and how to make connection right. It says E:Unable to write lunfile (No such file or directory) if you try to mount USB storage.
Is there anything else to do than go to do some phone shopping?
Please, if you have any ideas...
And I wish answers to be simple enough english to understand.. I´m not native english speaker.
And the only things that I can tell you about this piece of ****:
ClackworkMod Recovery v5.0.2.0
-Revolutionary-
Bravo Pvt3 Ship S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL -SYNW0101
RADIO-5.17.05.23
Aug 10 2010, 17.52:18
Click to expand...
Click to collapse
I know this thread is old, but I got exactly the same problem now ... and nobody did answer here yet.
A friend gave me his htc ace and I tried to repair it, since it's not booting anymore.
The bootloader is unlocked and I tried several recovery systems: CWM, modded CWM and TWRP.
The problem: I can't mount/format the storage/sdcard or /sdcard.
In CWM it says "Unable to write lunfile. Can't mount /sdcard",
In TWRP it shows 0 MB for the total/free size of the sdcard partition.
In modded CWM it says something like: Can't format/access non fvn(?)-format sdcard.
I can't access the phone via adb, since I just get "error: closed" (twice)
fastboot is working (so I could (re-)unlock the bootloader and flash custom recoveries) and so seems adb-sideload (it sends the new rom but doesn't do anything with it -> probably because it can't write to the sdcard).
Anyone might got an idea how to fix it? Maybe reformat the whole internal sdcard somehow?
Sewrizer said:
Full wipe or try to connect it to a flash drive with an OTG cable and use twrp to access it.
Click to expand...
Click to collapse
I already tried a full wipe, but every access to the sdcard just errors.
Even usb mount doesn't work, so I really couldn't find any way to access/format it yet

[Q] Stuck in CWM Recovery Mode

Hello all. I've been at it for a most of the day now and I am still stuck, and I feel like I am going in circles so it is time to ask for some help. I'm posting how I got to where I am, so you can skip the next two paragraphs if you can help me without them.
Yesterday I rooted my phone with Odin3 and CWM, and then I flashed CyanogenMod 7 to my phone. Before playing around too much with my new powers I realized that the texts I was sending were blank. I went looking for a fix, and found that if you flash your modem from EH09 back to EE19 the SMS sending should be fixed. I looked for EE19 for quite awhile, to no avail. Oh well - I decided to go back to FULL stock and say to hell with it (this paragraph represents about 15 hours of work haha).
I found this thread explaining how to get back to stock: http://forum.xda-developers.com/showthread.php?t=881064 Great! Well, they were Megaupload links. However on page 16 someone was nice enough to rehost the files I needed: http://cdn.kpsn.org/android/mesmerize/ I tried going back to stock with the EH09 rar file and the EE19 zip file as per the instructions on page 1 of the thread. In both instances, when I turned on my phone after running Odin3 CWM booted automatically in a different way than I had seen before. There was blue text as usual but there was also red text. This was the error: can't mount \dev\block\stl11.
Here is my current state:
If I try to turn my phone on by solely pressing the power button, I get booted into a normal version of CWM. Except I get several errors on boot:
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
When I choose the "reboot system now" option it just cycles back into CWM, and the "Samsung" logo never even shows up. I can give more details if necessary and if anyone is willing to help it is greatly appreciated!
I've been thinking about it and I think the files from the 2nd link above might be the problem, but I can't find any other files elsewhere.
SOLVED!! Funny I was stuck for 4-5 hours then I posted this thread and got it figured out shortly after. Oh well, glad I'm back to normal now with EH09. From the 2nd link in the OP download the file named Samsung_i500_Mesmerize_EH09.rar and follow the instructions in the first link from the OP. Cheers.
Thanks for this Thread !
I had done same thing and was also getting error message in recovery ...
Downloaded the MD5 file and fixed through odin !
I Love XDA !!!
wow thank you
hi there thanks for the great info , i was stuck in cwm recovery mode due to a rom i installed on my ace plus but i wiped cache and wiped all user dater tried a fresh rom to no avail the problem was i tried everything and was about to throw the towel in when i came across my old superuser.apk file for making stock rom a super user (sorry if i sound noobish its because i am ) lol) strange i know i opened odin 3 and re flashed in download mode with the md5 file and got back my stock operating system back (virgin media rom) which i was amazed that it worked lol big hands up to you guys and thanks for saving me a ins claim lol ) thank you will thank author in a mo

XT925 suddenly bricked

I was using my XT925 normally. Then it hanged for some time and I restarted it. Suddenly it wouldn't get past the circling cm boot. I tried to wipe cache to see if it solved the situation. Entered recovery mode, wiped cache, tried to restart again, now it won't even turn on.
Except when I use power + vol -, it goes to the bootloader unlocked screen and stops there.
Is there something I can do about it?
somehow got into recovery mode. Tried to wipe cache and this appeared:
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
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc
(I/O error)
Update 2:
Using rsdlite I got this error:
failed flashing process 1/19 flash sbl1 "sb1_signed" -> Phone returned FAIL
remove "get var"line from xml,then flash away
Thanks for the answer, but early today I went to a Motorola oficial store to see what they could do about it. They told me it was a hardware problem with the memory. I guess downgrading won't fix, if they're right.
It's really sad to have your phone not working anymore 1 month past the warranty limit. :/
There are ways... I ll check with you tomorrow man. It may still work
Wireless...
xusa said:
Thanks for the answer, but early today I went to a Motorola oficial store to see what they could do about it. They told me it was a hardware problem with the memory. I guess downgrading won't fix, if they're right.
It's really sad to have your phone not working anymore 1 month past the warranty limit. :/
Click to expand...
Click to collapse
Happy ? year
Ur phone working?
Wireless...
hbenz2008 said:
Happy ? year
Ur phone working?
Wireless...
Click to expand...
Click to collapse
Nah. I've decided to get a 2nd gen Moto G. I've expired all known troubleshoots and wasn't capable of solving this issue :/
weird man, what android were you running, you had cm ,right?
I would still try and flash gpt and tz if you still have it.
Anyway peace out man

[Q] Nexus 5 (32gb) Mobile Internal Memory Storage 0mb

Hello,
Today I woke up to my phone boot-looping after leaving it to charge overnight, despite it having run fine for close to a month (I have been running Cayanogen Mod ROM and TWRP 2.6.4.3 since I got my Nexus 5).
After a long wait at the Google and Nexus logos, there's a system popup of 'Cayanogen logo" present on the screen. However, right after completing the 'updating of apps', the system popup 'Media Storage has stopped working' appears and the phone immediately restarts again.
Upon booting into TWRP, it presents me with a password screen, which I have never encountered before. After pressing 'Cancel' though, I'm directed to the TWRP main menu.
Attempts to factory reset the phone resulted in:
Formatting cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Then i am using Nexus Root Toolkit and all are option i am going but nothing to do..
So please Watch this Video and Solved My Problem Please.. Please...
All are Process i am apply...Please developer help me......
Try locking your bootloader and rebooting. if it remains unlocked it's time for RMA/warranty cause you emmc is gone.
Niflheimer said:
Try locking your bootloader and rebooting. if it remains unlocked it's time for RMA/warranty cause you emmc is gone.
Click to expand...
Click to collapse
How to locking bootloader.. Please
apurbamajumder said:
How to locking bootloader.. Please
Click to expand...
Click to collapse
Install ADB/fastboot drivers . There's a thread in the stickies with the 10 seconds adb driver.
Press and hold volume down and power ( with the phone OFF ).
Connect phone to pc
open a command window .
change path to where you installed adb/fastboot ( e.g. if you installed in C:\ADB you would type cd c:\adb )
type fastboot devices . there should be a long string of numbers. If so , all is good. If not (and you get a message like waiting for devices) then you did something wrong. return to step 1
type fastboot oem lock . this will lock your bootloader.
Reboot the phone into bootmanager ( see step 2)
If it says bootloader locked all is good . Proceed to unlock it with the command fastboot oem unlock
If nothing changes ... it's time for warranty.
And stop using toolkits if you dont know what they do!
apurbamajumder said:
Hello,
Today I woke up to my phone boot-looping after leaving it to charge overnight, despite it having run fine for close to a month (I have been running Cayanogen Mod ROM and TWRP 2.6.4.3 since I got my Nexus 5).
After a long wait at the Google and Nexus logos, there's a system popup of 'Cayanogen logo" present on the screen. However, right after completing the 'updating of apps', the system popup 'Media Storage has stopped working' appears and the phone immediately restarts again.
Upon booting into TWRP, it presents me with a password screen, which I have never encountered before. After pressing 'Cancel' though, I'm directed to the TWRP main menu.
Attempts to factory reset the phone resulted in:
Formatting cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount storage.
Then i am using Nexus Root Toolkit and all are option i am going but nothing to do..
So please Watch this Video and Solved My Problem Please.. Please...
All are Process i am apply...Please developer help me......
Click to expand...
Click to collapse
Try to get into fastboot and flash a full factory image. Unlock bootloader in fastboot is by typing in cmd: fastboot oem unlock. BTW don`t use toolkits.
gee2012 said:
Try to get into fastboot and flash a full factory image. Unlock bootloader in fastboot is by typing in cmd: fastboot oem unlock. BTW don`t use toolkits.
Click to expand...
Click to collapse
This is the problem
Send it to LG/ Google - emmc is gone to greener pastures so your motherboard will need replacing.
Nexus 5 (32gb) Mobile Internal Memory Storage 0mb
Niflheimer said:
Send it to LG/ Google - emmc is gone to greener pastures so your motherboard will need replacing.
Click to expand...
Click to collapse
How to say? mymotherboard replace But my mobile is ON !!!!!
apurbamajumder said:
How to say? mymotherboard replace But my mobile is ON !!!!!
Click to expand...
Click to collapse
The internal memory got corrupted too bad to recover. Since you can't replace it alone ( at least in a cost effective way) the entire motherboard needs to be replaced.
Sure , LG/Google will probably just slap a new emmc on that board once it gets in their factory and put it up for the refurbished list but ... that doesn't mean you can do it.

Categories

Resources