Ok
I know i'm sorry if this has been posted quite a lot but i can't find a proper answer. I installed the leaked sense 3.0 rom and everything went fine. But suddenly the phone switched off and everytime i boot i get stuck on the white htc screen. i can get into recovery but when i do i get
E: can't find cache.... (will have to check error later properly)
Anyway i've tried factory reset, installing a new rom, installing recovery again and also running the RUU software. The RUU software was my last option and i'm getting stuck at rebooting to bootloader. Is this a faulty eMMC chip or do i still have other options. My device is S-OFF and rooted, so is there anyway to change it back for warranty purposes?
Any help will be appreciated a lot!!!!!
dan-fish said:
i can get into recovery but when i do i get
E: can't find cache.... (will have to check error later properly)
Click to expand...
Click to collapse
I'm afraid that it does sound very like the symptoms of the fried eMMC chip problem. Did you at any point pull the battery?
If you attempt to go into RECOVERY and try to format the CACHE partition what errors do you get?
Do you have any Full Nandroid backups on your SD card that you can attempt to restore?
i have taken the battery out many times to get into recovery when i have boot loops and what not. Also have done it a lot now to get into recovery
i didn't have a backup so i copied one over from my brothers desire s which i had hoped would still work. I'm not sure if it was because it was from my brother's phone or it was because everything refuses to work, but the restore didn't work.
also clockworkmod is just really slow.
when i wipe the cache it says
-- Wiping cache
Formatting /cache...
Cache wipe complete
Then shows the original error again which is
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
So the cache wiping is a success but does that help in any way. Is the eMMC chip still most likely fried?
I tried installing cm7 and it gave me the error
E:Error in /sdcard/update-cm-7.1.0-RC1-DesireS-Nexx-signed.zip
(Status 1)
Installation aborted
I know for a fact the rom is fine because my brother has the rom on his desire s.
dan-fish said:
i have taken the battery out many times to get into recovery when i have boot loops and what not. Also have done it a lot now to get into recovery
i didn't have a backup so i copied one over from my brothers desire s which i had hoped would still work. I'm not sure if it was because it was from my brother's phone or it was because everything refuses to work, but the restore didn't work.
also clockworkmod is just really slow.
when i wipe the cache it says
-- Wiping cache
Formatting /cache...
Cache wipe complete
Then shows the original error again which is
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
So the cache wiping is a success but does that help in any way. Is the eMMC chip still most likely fried?
I tried installing cm7 and it gave me the error
E:Error in /sdcard/update-cm-7.1.0-RC1-DesireS-Nexx-signed.zip
(Status 1)
Installation aborted
I know for a fact the rom is fine because my brother has the rom on his desire s.
Click to expand...
Click to collapse
I'm afraid that it does seem to be yet another fried eMMC chip...see this thread that I only answered yesterday that exhibits exactly the same problem and has a couple of linked threads in it. Although I'm by no means an expert, so dig around through the various related threads on this subject to confirm this for yourself. I have seen a thread a while back within this forum, although can't find it now that shows commands and then the results returned from a bricked (fried eMMC chip) device and a non bricked device that will enable you to confirm 100%.
Although, it does look like service centre will be your next stop, if you're lucky they may fail to notice the S-OFF state of the device.
so there is absolutely no way to go back to s-on? Is there at least a way to make sure they don't realise it's S-OFF?
dan-fish said:
so there is absolutely no way to go back to s-on? Is there at least a way to make sure they don't realise it's S-OFF?
Click to expand...
Click to collapse
I would also like to know this information incase it ever happened to me
daveys4 said:
I would also like to know this information incase it ever happened to me
Click to expand...
Click to collapse
Right now i would prefer it if my phone were actually bricked!
Can i just send them the phone without the battery or sd card?
Also how does fastboot work?
I want to try something like this http://forum.xda-developers.com/showthread.php?t=1231249
But when i type in fastboot oem lock in cmd nothing happens
dan-fish said:
so there is absolutely no way to go back to s-on? Is there at least a way to make sure they don't realise it's S-OFF?
Click to expand...
Click to collapse
I'll be honest I don't know.
Does adb recognise your device still? So question is does adb or fast boot function?
Now the post that I mentioned earlier may be of some use at this point.
I'm about to PM you something.
Swyped from HTC Desire S using XDA Premium
dan-fish said:
Right now i would prefer it if my phone were actually bricked!
Can i just send them the phone without the battery or sd card?
Also how does fastboot work?
I want to try something like this http://forum.xda-developers.com/showthread.php?t=1231249
But when i type in fastboot oem lock in cmd nothing happens
Click to expand...
Click to collapse
You need the adb and fast boot exe on your PC which you can get online, afraid that I'm away from a PC now so will have to add more tomorrow
I've send you a pm (a last resort)
Swyped from HTC Desire S using XDA Premium
i most likely will not have time today but tomorrow i'll try and get the hang of adb and fastboot. Explore my options with it. If nothing happens i'll just have to call htc.
I was thinking if i can't do anything else, i should just drain the battery by swapping the battery with my brother's desire s, drain the battery and then swap them back. Maybe that'll help?
dan-fish said:
i most likely will not have time today but tomorrow i'll try and get the hang of adb and fastboot. Explore my options with it. If nothing happens i'll just have to call htc.
I was thinking if i can't do anything else, i should just drain the battery by swapping the battery with my brother's desire s, drain the battery and then swap them back. Maybe that'll help?
Click to expand...
Click to collapse
You'll see in my Signature the links to get both ADB and FASTBOOT, you'll also need HTC drivers installed.
This is the usefull THREAD that I was talking about.....in determining whether you are indeed suffering from fried eMMC chip, even though at this stage we're reasonably confident.
ben_pyett said:
I'm afraid that it does seem to be yet another fried eMMC chip...see this thread that I only answered yesterday that exhibits exactly the same problem and has a couple of linked threads in it. Although I'm by no means an expert, so dig around through the various related threads on this subject to confirm this for yourself. I have seen a thread a while back within this forum, although can't find it now that shows commands and then the results returned from a bricked (fried eMMC chip) device and a non bricked device that will enable you to confirm 100%.
Although, it does look like service centre will be your next stop, if you're lucky they may fail to notice the S-OFF state of the device.
Click to expand...
Click to collapse
That is not a fried chip! If he can get into recovery and wipe cache it definately isn't a fried chip, i had this 2 days ago. I sorted it somehow..... been drinking tonight so don't expect an answer until late tomorrow
Malooga said:
That is not a fried chip! If he can get into recovery and wipe cache it definately isn't a fried chip, i had this 2 days ago. I sorted it somehow..... been drinking tonight so don't expect an answer until late tomorrow
Click to expand...
Click to collapse
@Malooga
It would obviously be quality if it's not and the device is recoverable from this position. Any clues how you sorted this out, using what approach?
@dan-fish
Do you have EXT4 recovery installed?
If you do great. If not then 1) download this FILE 2) copy it onto your SD card 3) enter recovery 4) flash the EXT4 ZIP file 5) then Reboot Recovery.
Using EXT4 recovery, look at what format the existing CACHE partition and the other partitions are in? this can be done using the EXT3 - 4EXT - 4EXT option of the EXt4 recovery main screen.
I'd also try to download a custom ROM WIPE script and then run this from recovery (reporting back any errors).
Then try to flash a custom ROM also again also from recovery having downloaded it to your SD card like LBC using the flash ZIP from SD card option in recovery.
Will try later today. Please do try and help malooga
Sent from my HTC Desire S using XDA Premium App
dan-fish said:
Will try later today. Please do try and help malooga
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
Although Malooga might be suffering today from the morning after (we've all been there)
I'll be online most of the day, as I'm currently off work sick...as I've somehow knackered my back - so XDA is keeping me sane
installing 4ext recovery
assert failed: write_raw_image (" /tmp/recovery.img" , "recovery"
E:Error in /sdcard/4EXTRecovery_v2.1.3RC2.zip
(Status 7)
Installation aborted.
Ran full wipe script:
E:Error in /sdcard/FULL_WIPE_1.5_EXT4-for-saga_.zip
(Status 1)
Installation aborted
Seriously running out of options.
I had this happen I just wiped data factory reset wipe cache wipe dalvik then go into mounts and format data format cache format system then flashed my backup the phone then booted up if u don't have a backup download a rom zip and flash that if you have tried the above then I'm all out of ideas good look
Sent from my HTC Desire S using xda premium
As you don't have any Backups.....we should attempt to move forward.
As we know that you can format/wipe partitions (eg CACHE appeared to work) you should try to manually format/wipe DATA, SYSTEM and CACHE.
Download a custom ROM to your SD card ie LBC like LBC v0.5.3
Then try to flash this Custom ROM from RECOVERY using the flash ZIP from SD card option.
Report back any errors and progress.
ok will try now and update in 10-15 mins.
also i haven't explored my options with fastboot mainly because i don't really understand it yet but if there are any options available through there (excluding the last resort which right now is looking like our only option) i will be happy to try
dan-fish said:
ok will try now and update in 10-15 mins.
also i haven't explored my options with fastboot mainly because i don't really understand it yet but if there are any options available through there (excluding the last resort which right now is looking like our only option) i will be happy to try
Click to expand...
Click to collapse
I'm by no means an expert either and fastboot is something that I've yet to master..so before you try that EVIL one.....lets try some other stuff and look for advice from others.......
I'm online tonight for next couple of hours, we'll until the England Football game kick offs anyway!
Im totally lost,today i flashed cwm recovery from this guide: http://forum.xda-developers.com/showthread.php?t=1632553
,everything was perfect untill i got the Wi-Fi error.But its ok since we got this:http://forum.xda-developers.com/showthread.php?t=1193063&page=2 ,but when i wipe dalvic and cache nothing happens .Any ideas ? HBoot is 1.27.0000.
PS:When i wipe data i get this E:format_volume: make_extf4fs failed on dev/block/mmcblk1p2
PS2:I used super wipe and i got this: E;Error in /sdcard/Android_Revolution_HD_Super_Wipe_Sensation.zip
(status 1)
Instalation aborted.
[email protected] said:
Im totally lost,today i flashed cwm recovery from this guide: http://forum.xda-developers.com/showthread.php?t=1632553
,everything was perfect untill i got the Wi-Fi error.But its ok since we got this:http://forum.xda-developers.com/showthread.php?t=1193063&page=2 ,but when i wipe dalvic and cache nothing happens .Any ideas ? HBoot is 1.27.0000.
PS:When i wipe data i get this E:format_volume: make_extf4fs failed on dev/block/mmcblk1p2
PS2:I used super wipe and i got this: E;Error in /sdcard/Android_Revolution_HD_Super_Wipe_Sensation.zip
(status 1)
Instalation aborted.
Click to expand...
Click to collapse
Use 4EXT recovery
It's much more compatible for sensation roms
Also superwipe runs on 4EXT.
To flash 4EXT step #2 (if SON follow step #3 too) from below guide
http://forum.xda-developers.com/showthread.php?p=25587345
Sent from my pyramid.. Through blazing fast sonic waves
EDIT: Everything is ok now i mback to stock RUU ,looks like i had problems with USB Cable,huge thank you ganeshp ,have a great day!
Hey guys, I know 4EXT works fine but would like to know why CWM is giving this error?
A while ago I was on CWM, until I suddenly came across the exact same error. I've read somewhere that this is related to a corrupted internal SD card, and while 4EXT works fine I'd still like to know if this is just an incompatibility with the CWM recovery or an actual corrupted internal SD card causing this?
I'm getting error while factory reset.
E:format_volume: rfs format failed on /dev/block/stl10
Please someone help me please.
[email protected] said:
I'm getting error while factory reset.
E:format_volume: rfs format failed on /dev/block/stl10
Please someone help me please.
Click to expand...
Click to collapse
try flashing using the latona.pit to have a correct repartition using the stock rom. you could use the search engine to find a guide how to flash back to a stock rom. or you could just google it.
Getting this error! Symlink: some symlink failed...(status 7) installation aborted
I've been trying to flash a new rom for a few days and have spent countless hours trying to figure out the issue. I'm trying to flash the KK-Beanstalk 4.4.215 - OC. I flashed an earlier release without an issue. I believe the error I'm getting has to do with the space on my system partition. I've tried all the basic troubleshooting; clean flash- factory reset, formatting system, re downloading the rom, used CWM 6.0.4.3 and Philz custom recovery. I've checked my system partition while running the rom and am using 435/588MB. I assume the wipe/factory reset and system format would take care of that but I'm not so sure.
I am stumped and haven't found this clearly answered on any other forum. I'm out of ideas on what I can try and would not prefer having to move to another rom. I apologize I would have posted this on that thread but I usually don't have to post, I can get away with reading and researching.
Thanks!
dirtycurty said:
Getting this error! Symlink: some symlink failed...(status 7) installation aborted
I've been trying to flash a new rom for a few days and have spent countless hours trying to figure out the issue. I'm trying to flash the KK-Beanstalk 4.4.215 - OC. I flashed an earlier release without an issue. I believe the error I'm getting has to do with the space on my system partition. I've tried all the basic troubleshooting; clean flash- factory reset, formatting system, re downloading the rom, used CWM 6.0.4.3 and Philz custom recovery. I've checked my system partition while running the rom and am using 435/588MB. I assume the wipe/factory reset and system format would take care of that but I'm not so sure.
I am stumped and haven't found this clearly answered on any other forum. I'm out of ideas on what I can try and would not prefer having to move to another rom. I apologize I would have posted this on that thread but I usually don't have to post, I can get away with reading and researching.
Thanks!
Click to expand...
Click to collapse
read this for a clean install http://forum.xda-developers.com/showthread.php?t=2176593
still fails, try cwm 6037 or even twrp 2.6.1.0
I'll try these steps today. I thought there might be something more specific with that error instead of the way I was flashing.
Today when I started a Wipe with TWRP for flash a previous release of Paranoid Android because the new one have many bugs the wipe froze so I decided to format with SD Formatter and I was unable to do anything, I ever have "E:Unable to mount '/cache', E:Unable to mount '/data', E:Unable to mount '/system'"
I can't flash Rom, do a wipe it's always on a loop.
Thanks in Advance.
Asindur said:
Today when I started a Wipe with TWRP for flash a previous release of Paranoid Android because the new one have many bugs the wipe froze so I decided to format with SD Formatter and I was unable to do anything, I ever have "E:Unable to mount '/cache', E:Unable to mount '/data', E:Unable to mount '/system'"
I can't flash Rom, do a wipe it's always on a loop.
Thanks in Advance.
Click to expand...
Click to collapse
did you try to change recovery?
if not do it and try to wipe again
rzr86 said:
did you try to change recovery?
if not do it and try to wipe again
Click to expand...
Click to collapse
I tried but with 4EXT when I wipe data, do a factory reset I have the error: "E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p23"
Asindur said:
I tried but with 4EXT when I wipe data, do a factory reset I have the error: "E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p23"
Click to expand...
Click to collapse
I assume you were using TWRP 2.7? Then I can't give you much hope, since no one figured out yet how to repair that or if it's repairable at all.
Sajito said:
I assume you were using TWRP 2.7? Then I can't give you much hope, since no one figured out yet how to repair that or if it's repairable at all.
Click to expand...
Click to collapse
I used the TWRP 2.7.0.0 (not the last 2.7.1.x version) since it is available for HTC Sensation without problem, flashing many roms and do many wipe without problem.
I'l follow the TWRP thread then if a solution is possible..
Thank you for trying to help me.
Asindur said:
I used the TWRP 2.7.0.0 (not the last 2.7.1.x version) since it is available for HTC Sensation without problem, flashing many roms and do many wipe without problem.
I'l follow the TWRP thread then if a solution is possible..
Thank you for trying to help me.
Click to expand...
Click to collapse
Even the 2.7.0.0 is not without problems. There seems to be something broken which breaks the emmc.