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!
I really got a big problem.
I came from HyperNonSense 1.5.1. After doing the SuperCID stuff with adb, I wiped all my data and formatted the system. Then I put the new Firmware and the Virtuous Inquisition Custom Rom on my sd-card. After flashing the new Firmware my Sensation didn't start (bootloop on the htc screen). I wasn't able to delete the PG58IMG.zip, because recovery isn't working as well...
Please... HELP :'((( what can I do now!?
recovery says:
can't mount cache/recovery/command
can't mount cache/recovery/log
can't open cache/recovery/log
can't mount cache/recovery/last_log
can't open cache/recovery/last_log
/closed
jentsch89 said:
/closed
Click to expand...
Click to collapse
Solved or brick confirmed ???
mathrania said:
Solved or brick confirmed ???
Click to expand...
Click to collapse
probably removed the SD card before going into recovery
I was having the same problem after flashing ICS firmware.
In clockworkmod, mounts & storage -> format /cache and rebooted recovery fixed this issue.
[Deleted]
johnfocker said:
Hey guys!
I've been trying to factory reset my tf700t to install a fresh CM10.1 but I had the (very) bad idea to try this ****ty encryption feature before and now everytime I try to factory reset or wipe /data, the recovery throws me an error like "Unable to mount /data".
Tried with TWRP as well as Clockworkmod, same result.
I don't want to mount it, it just want to get rid of it and start fresh.
Is there a way to do it?
Is there an official tool to flash a stock rom or am I stuck with those recoveries that can't work with encrypted partitions?
Cheers
Click to expand...
Click to collapse
As I recall there is a superwipe script somewhere the will completely remove and recreate the partitions. Don't recall where I found it though, but it will fix that.
johnfocker said:
I don't want to mount it, it just want to get rid of it and start fresh.
Is there a way to do it?
Click to expand...
Click to collapse
"Format /data" in TWRP should do it.
johnfocker said:
Hey guys!
I've been trying to factory reset my tf700t to install a fresh CM10.1 but I had the (very) bad idea to try this ****ty encryption feature before and now everytime I try to factory reset or wipe /data, the recovery throws me an error like "Unable to mount /data".
Tried with TWRP as well as Clockworkmod, same result.
Cheers
Click to expand...
Click to collapse
Did you try the Format Option in the TWRP? It wipes everything on your internal SD. I use it every time that I want a clean install.
Flash the TWRP recovery through fastboot mode and then u 'll be fine to wipe data/factory reset.
Sent from my ASUS Transformer Pad TF700T using xda premium
[Deleted]
johnfocker said:
I only just noticed I never replied to you guys...
So first of all, thank you for taking the time to answer me back then, if you ever read this
From what I can recall, I ended up doing a full format through CWM or TWRP. This takes a long time (because the nand is so slow I gues) and the first time I tried I thought the tablet was frozen, that's probably why I thought I was screwed...
So after I let the full format finish, I was able to sideload a fresh rom and it worked again
BTW just installed crombikk rom : AWESOME
I only wish I tried it earlier!
The encryption feature seems to be broken but... Who cares, my tablet as never been so fast (usable? Lol)
Click to expand...
Click to collapse
You got your first thanks
I like good news stories!!
Hi All
just tried to update to cm-11-20140606-Sultan-pyramid.zip from cm-11-20140511-Sultan-pyramid.zip and it fails with (status 0)
wiped data/factory reset
wiped cache partiton
wiped Dalvik cache too but still fails.....
anyone else having same issue?
Use latest 4ext recovery n try again.
Larest is v1.0.0.6 RC2
puyo78 said:
Hi All
just tried to update to cm-11-20140606-Sultan-pyramid.zip from cm-11-20140511-Sultan-pyramid.zip and it fails with (status 0)
wiped data/factory reset
wiped cache partiton
wiped Dalvik cache too but still fails.....
anyone else having same issue?
Click to expand...
Click to collapse
i suggest to update your recovery
what recovery do you have?
rzr86 said:
i suggest to update your recovery
what recovery do you have?
Click to expand...
Click to collapse
Hi
i'm currently using CLOCKWORKMOD Recovery V5.8.0.9
and never had this kinda issue before...
also tried download the ZIP file 3times already just for in case whether ZIP file were corrupted but made no difference...
puyo78 said:
Hi
i'm currently using CLOCKWORKMOD Recovery V5.8.0.9
and never had this kinda issue before...
also tried download the ZIP file 3times already just for in case whether ZIP file were corrupted but made no difference...
Click to expand...
Click to collapse
i suggest to change your recovery to 4ext recovery
rzr86 said:
i suggest to change your recovery to 4ext recovery
Click to expand...
Click to collapse
Hi rzr86
as advised, after changing to 4ext recovery, update was successful and working fine now
really appreciate for ur help & advise :fingers-crossed:
Hi guys,
Just looking for some advice - I have tried to read as much as I could before posting, and still don't really know what I'm doing wrong, so here goes:
I purchased an ATT branded A9, sim-unlocked it and am trying to convert it to the US unlocked version using the guide in this forum. I have managed to unlock bootloader, install TWRP 3.0.2, but when I try to decrypt storage by using the Format data optionthis is what I get:
Failed to decrypt data.
Unable to decrypt data with default password. You may need to perform a Format Data.
Updating partition details....
....done
Unable to mount storage
Full SELinux support is present.
Formatting Data using make_ext4fs...
You may need to reboot recovery to be able to use / data again.
Updating partition details...
...done
I have come close to bricking twice now - have managed to revive it both times, but am coming close to giving up and just dealing with the bloat and lack of 6.0.1 - any help would be greatly appreciated.
Make Wipe Data in Advanced Wipe before installing supersu.zip
romanch said:
Make Wipe Data in Advanced Wipe before installing supersu.zip
Click to expand...
Click to collapse
Its working?After that i can make backup from data woth TWRP?
krepsz said:
Its working?After that i can make backup from data woth TWRP?
Click to expand...
Click to collapse
If it works, obviously do before a general backup.
At the beginning I suffered with this, but no more
Thanks for replying, however I have already tried this and get the same result. I also tried doing a factory reset to remove encryption BEFORE installing TWRP and that didn't change anything, either.