Related
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 having a problem when i try to format via Cwm i keep getting E:format_volume: rfs format failed on /dev/block/mmcblk0p2,also when i try to flash a rom it will get stuck on a bootloop...I can restore back to ARHD 3.6.1 and it will boot up and work fine but when i try to flash a new rom i always get the error message and get stuck can someone please help me...
RUU back to stock and start again
Anyone else with this problem?? Im on ARHD 3.6.1
EddyOS said:
RUU back to stock and start again
Click to expand...
Click to collapse
if i RUU back to stock do i have to Re-root and super CID all over? And how do i go back to stock RUU im on a T-mobile usa sensation 4g..sorry im a newbie and thanks for the help
HigherSensation said:
if i RUU back to stock do i have to Re-root and super CID all over? And how do i go back to stock RUU im on a T-mobile usa sensation 4g..sorry im a newbie and thanks for the help
Click to expand...
Click to collapse
If you have done super CID already, then all you would need to do is run the RUU of your choice (WWE would do nicely), then re-flash the recovery, and then flash any ROM you want.
pakraider said:
If you have done super CID already, then all you would need to do is run the RUU of your choice (WWE would do nicely), then re-flash the recovery, and then flash any ROM you want.
Click to expand...
Click to collapse
if i ruu back i will still have s-off correct? and all ill need to do is flash recovery and SU
Thanks for the help guys I Ruu back to stock and im still having the same problem any ideas?
fixed**
3. Open Rom Manager
4. Choose to Partition your sdcard, sdext 512, swap 0
5. Reinstall Recovery through Rom Manager
6. Reboot into Recovery
7. Wipe
HigherSensation said:
fixed**
3. Open Rom Manager
4. Choose to Partition your sdcard, sdext 512, swap 0
5. Reinstall Recovery through Rom Manager
6. Reboot into Recovery
7. Wipe
Click to expand...
Click to collapse
Hello, I am a noob. This looks useful. Could you perhaps explain it a little further..??
oh man ... whho can help me on this.. im really newbie on androi phone.
HigherSensation said:
fixed**
3. Open Rom Manager
4. Choose to Partition your sdcard, sdext 512, swap 0
5. Reinstall Recovery through Rom Manager
6. Reboot into Recovery
7. Wipe
Click to expand...
Click to collapse
What if I do not have Rom Manager installed and teh market is not working anymore?
Hello all !
I have an issue after trying to change ROM : I had "icon stretching" issue with Source, something apparently no one had seen before. I wanted to switch to Maximus, so I flashed it apparently with no problems. But then the phone only booted to Recovery (TWRP)...
So I tried to flash firmware again, the one given in tuto for Maximus but same problem.
And this is when it got tricky, not only I couldn't boot to Android, but I couldn't mount USB either, the option just disappeared ! Along with issue to mount "/cache" apparently. I tried factory reset, then full wipe, no result.
I tried a more recent version of TWRP than the one given with Maximus' tutorial, with it I have the option to mount USB but only for a 48 MB space ! Again, factory reset and full wipe don't help.
I'm not too worried since I can access bootloader and Recovery fine but I feel out of options... I flashed 2.16 firmware like a dozen times (is it any point in doing that ?), I wonder just how I can get a recovery that can mount USB, or a stock ROM to start fresh.
Anybody to help me ? Thanks in advance !
stick on TWRP 2.3.3.0 which (iirc) is the last one that allows you to mount storage. slap another rom across, flash, fastboot boot.img, get the rom up and running and then consider changing recoveries.
Thanks for your reply
I flashed this version but I can only mount a 48MB storage . I didn't reflash the firmware, should I downgrade to 2.15 ?
i've got no experience with 2.16 firmware so i can't really help you as far as it goes with the best recovery on that... all i can say is the last version of TWRP that allows sd mount is 2.3.3.0. have you tried the latest CWM that works with kitkat roms? that might be worth a shot.
djiock said:
Thanks for your reply
I flashed this version but I can only mount a 48MB storage . I didn't reflash the firmware, should I downgrade to 2.15 ?
Click to expand...
Click to collapse
Maybe you should use recovery from maximus thread, it can be specialized for hboot 2.16. AFAIK 2.16 hboot has a different partition system, that could be the problem. Try to wipe your sd with op recomended recovery. You should flash the firmware twice by the way(second one when got the error), i think you already know that
Sent from my One S using xda app-developers app
djiock said:
Hello all !
I have an issue after trying to change ROM : I had "icon stretching" issue with Source, something apparently no one had seen before. I wanted to switch to Maximus, so I flashed it apparently with no problems. But then the phone only booted to Recovery (TWRP)...
So I tried to flash firmware again, the one given in tuto for Maximus but same problem.
And this is when it got tricky, not only I couldn't boot to Android, but I couldn't mount USB either, the option just disappeared ! Along with issue to mount "/cache" apparently. I tried factory reset, then full wipe, no result.
I tried a more recent version of TWRP than the one given with Maximus' tutorial, with it I have the option to mount USB but only for a 48 MB space ! Again, factory reset and full wipe don't help.
I'm not too worried since I can access bootloader and Recovery fine but I feel out of options... I flashed 2.16 firmware like a dozen times (is it any point in doing that ?), I wonder just how I can get a recovery that can mount USB, or a stock ROM to start fresh.
Anybody to help me ? Thanks in advance !
Click to expand...
Click to collapse
Look at this thread, might help you:
http://forum.xda-developers.com/showthread.php?t=2584297
---------- Post added at 03:17 PM ---------- Previous post was at 03:11 PM ----------
djiock said:
Thanks for your reply
I flashed this version but I can only mount a 48MB storage . I didn't reflash the firmware, should I downgrade to 2.15 ?
Click to expand...
Click to collapse
I can mount sdcard with TWRP 2.6.3.0 for hboot 2.15 from this thread: http://forum.xda-developers.com/showthread.php?t=2528113
YYYYYEEEEEESSSS !
Finally ! That was the right way to do it, downgrade to Hboot 2.15 with help of http://forum.xda-developers.com/showthread.php?t=2322755 but the recovery wasn't booting, just reflashing TWRP offered in http://forum.xda-developers.com/showthread.php?t=2528113 did the trick.
And then I was able to mount my SD card and follow the steps to flash Maximus.
What a relief. Thank you all for your help ! I'm just surprised not many people seem to have had the same issue... But maybe they manage to resolve it by themselves !
Hello,
Just had issue with my Samsung galaxy S3.
A lot of sudden death and device freezes.
I installed the "[ROM][364MB][NB7]Revolutionary S5 V2 - Like your new Galaxy S5? [23RD MAR][FLYING][AVAILABLE]"
rom and since then i cannot boot my device.
After the installation was finished and just click the reboot option and its stucked on the boot screen(Samsung Galaxy s3 image)
Is it what's called a brick?
Is there any way to fix that issue?
I know i can get into recovery.
I'm having trouble with the sd card, I guess it's related cause it was working well before having issue with the device.
Any suggestion from you guys?
chenazran said:
Hello,
Just had issue with my Samsung galaxy S3.
A lot of sudden death and device freezes.
I installed the "[ROM][364MB][NB7]Revolutionary S5 V2 - Like your new Galaxy S5? [23RD MAR][FLYING][AVAILABLE]"
rom and since then i cannot boot my device.
After the installation was finished and just click the reboot option and its stucked on the boot screen(Samsung Galaxy s3 image)
Is it what's called a brick?
Is there any way to fix that issue?
I know i can get into recovery.
I'm having trouble with the sd card, I guess it's related cause it was working well before having issue with the device.
Any suggestion from you guys?
Click to expand...
Click to collapse
Recovery + downloa mode working ??
LS.xD said:
Recovery + downloa mode working ??
Click to expand...
Click to collapse
Yes sir.
I'm just trying to play with the adb tool and install a different rom, no result yet.
Do you know another way?
chenazran said:
Yes sir.
I'm just trying to play with the adb tool and install a different rom, no result yet.
Do you know another way?
Click to expand...
Click to collapse
Sure. You don't need adb for installing a rom!
Perform a wipe
copy CUSTOMROM.zip* to your sdcard
install it via recovery
be happy again
*you can choose any custom rom compatible to your device.
The sd card is curropted for some reason.
I try the ADB but get the error attached.
Any reason what's wrong?
Or how can I fix this issue?
chenazran said:
The sd card is curropted for some reason.
I try the ADB but get the error attached.
Any reason what's wrong?
Or how can I fix this issue?
Click to expand...
Click to collapse
Don't use adb sideload pls. Just go to recovery --> format sd-card --> mount sd to computer --> copy rom.zip to sdcard manually. You dont need adb sideload
I format the external_sd
I mount the external_sd but can get the drive in my local machine.
do you i need to do something in addition to get the drive in my pc?
What Recovery Version do you use actually?
]Do You have the SIII gt-i9300?
If you have unbranded SIII GT-i9300 --> This is the best recovery avaiable PhilZ advanced cwm 6.19.3 . You can flash it using Odin 3.07
Latest usb drivers --> Samsung USB drivers
Your solution is good.
I installed this recovery and managed to mount my sd card and then install a different rom.
Thing I still have the sudden death issue.
I understood that any rom with version of 4.1.2 and above has that relevant fixes but its just didn't solve my issue.
Any suggestion about that?
chenazran said:
Your solution is good.
I installed this recovery and managed to mount my sd card and then install a different rom.
Thing I still have the sudden death issue.
I understood that any rom with version of 4.1.2 and above has that relevant fixes but its just didn't solve my issue.
Any suggestion about that?
Click to expand...
Click to collapse
Have you flashed full stock firmware once you're sd card is fine again?
I installed a custom ROM(Archdroid v2.4) and in the installation i chose the stock kernel.
Is that enough?
Model: GT-I9300
Android version: 4.4.2
XXELLA
chenazran said:
Hello,
Just had issue with my Samsung galaxy S3.
A lot of sudden death and device freezes.
I installed the "[ROM][364MB][NB7]Revolutionary S5 V2 - Like your new Galaxy S5? [23RD MAR][FLYING][AVAILABLE]"
rom and since then i cannot boot my device.
After the installation was finished and just click the reboot option and its stucked on the boot screen(Samsung Galaxy s3 image)
Is it what's called a brick?
Is there any way to fix that issue?
I know i can get into recovery.
I'm having trouble with the sd card, I guess it's related cause it was working well before having issue with the device.
Any suggestion from you guys?
Click to expand...
Click to collapse
Do you have custom recovery ? if you have so then do a complete wipe (cache,factory data, dalvik) and try, if the device doesnt boot then flash your backup or stock rom in recovery
I installed a custom ROM based on stock and it reduced the freezes and sudden death big time but didn't solve it.
since the installation one day ago i had a couple of sudden deaths.
I did all wipes the recovery have to offer but I still see picture and old data I had.
No way to format the entire phone and then install a ROM from recovery?
Any other suggestion how to fix?
chenazran said:
I installed a custom ROM based on stock and it reduced the freezes and sudden death big time but didn't solve it.
since the installation one day ago i had a couple of sudden deaths.
I did all wipes the recovery have to offer but I still see picture and old data I had.
No way to format the entire phone and then install a ROM from recovery?
Any other suggestion how to fix?
Click to expand...
Click to collapse
You can format everything using PhilZ recovery:
-->Mounts&Storage
Format /system /cache /data /storage/sdcard0 /storage/sdcard1
Then copy the rom to your sdcard and install it again. If that does not work you will have to flash the stock firmware once using odin before you can use a custom rom again.
Keep in mind that a custom kernel can cause system instability and errors.
LS.xD said:
You can format everything using PhilZ recovery:
-->Mounts&Storage
Format /system /cache /data /storage/sdcard0 /storage/sdcard1
Then copy the rom to your sdcard and install it again. If that does not work you will have to flash the stock firmware once using odin before you can use a custom rom again.
Keep in mind that a custom kernel can cause system instability and errors.
Click to expand...
Click to collapse
"stock firmware once using odin"
I want to try that.
Format the whole phone and install stock firmware.
Where can I download that?
chenazran said:
"stock firmware once using odin"
I want to try that.
Format the whole phone and install stock firmware.
Where can I download that?
Click to expand...
Click to collapse
XXELLA = T-Mobile Austria
If that is correct you will need this Firmware
Keep in mind that its Android 4.12 so please perform a EFS backup using KTool
chenazran said:
Hello,
Just had issue with my Samsung galaxy S3.
A lot of sudden death and device freezes.
I installed the "[ROM][364MB][NB7]Revolutionary S5 V2 - Like your new Galaxy S5? [23RD MAR][FLYING][AVAILABLE]"
rom and since then i cannot boot my device.
After the installation was finished and just click the reboot option and its stucked on the boot screen(Samsung Galaxy s3 image)
Is it what's called a brick?
Is there any way to fix that issue?
I know i can get into recovery.
I'm having trouble with the sd card, I guess it's related cause it was working well before having issue with the device.
Any suggestion from you guys?
Click to expand...
Click to collapse
I think you havent cleared data/factory reset your phone from cwm or twrp or else..
u need to do that + clear dalvik cache before flashing the zip..
But about the ROM u mentioned, is it really made for Samsung S3 ? :/
Vaibhav4166 said:
I think you havent cleared data/factory reset your phone from cwm or twrp or else..
u need to do that + clear dalvik cache before flashing the zip..
But about the ROM u mentioned, is it really made for Samsung S3 ? :/
Click to expand...
Click to collapse
Yes its a rom for SIII GT-i9300 LOL
LS.xD said:
XXELLA = T-Mobile Austria
If that is correct you will need this Firmware
Keep in mind that its Android 4.12 so please perform a EFS backup using KTool
Click to expand...
Click to collapse
"XXELLA = T-Mobile Austria"
Didnt know that one.
I will download what's relevant for my country according to the site you provided and install.
It's only a KERNEL stock, right?
I can leave my current custom rom and just flash the official stock kernel ?
chenazran said:
I installed a custom ROM(Archdroid v2.4) and in the installation i chose the stock kernel.
Is that enough?
Model: GT-I9300
Android version: 4.4.2
XXELLA
Click to expand...
Click to collapse
You posted XXELLA before...
Its a FULL FIRMWARE. Will setup complete phone. !!! Backup personal data if you need something!!!
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.