Hello,
Suddenly, my HTC Desire HD crashed.
I can not format /cache nor /data partitions.
I couldn't install a rom nor a backuped rom.
I can boot into bootloader / recovery.
can I resize these partitions ? how ?
Thanks for help
TF85 said:
Hello,
Suddenly, my HTC Desire HD crashed.
I can not format /cache nor /data partitions.
I couldn't install a rom nor a backuped rom.
I can boot into bootloader / recovery.
can I resize these partitions ? how ?
Thanks for help
Click to expand...
Click to collapse
We need more information. What ROM? What bootloader status? What happened when it crashed? What error messages are showing up when you try to flash a ROM or recovery?
Hello,
The bootloader informations : Unlocked / S-ON / 4EXT_Recovery_Touch
The rom installed : DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00.zip
I can flash another recovery (TWR, ..)
In wiping partitions (one hour waiting :
E:Unable to mount /cache
E:Unable to mount /data
E:Unable to mount /system
E: Failed to wipe dalvik
When trying the same rom :
the message error :
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error n /sdcard/DHD...._nitr00.zip (status 7)
Installation aborted.
After the TWR recovery i returned to 4Ext recovery, I did in 2 steps
1 - a wipe for factory reset/cache/dalvik,
2 - shutdown 5 minutes later
3 - i did a wipe for data/system and boot.
without shutdowning, i had an error failed to ...
I installed the RandomRom (145 and 5.00)
Firstly RandomRom145.zip
shutdown 5 minutes
secondly RandomRom5.00
then I flashed th boot.img
The rom was installed without errors.
When I booted it, I have the first white screen then I had a black screen for 1 or 2 minutes then the recovery tool was loaded.
Finally, I think that ma DHD is really dead.
I spent a day to arrive to this !!
Thanx for helps
TF85 said:
Hello,
The bootloader informations : Unlocked / S-ON / 4EXT_Recovery_Touch
The rom installed : DHD_WWE_3.12.405.1_STOCK_rooted_by_nitr00.zip
I can flash another recovery (TWR, ..)
In wiping partitions (one hour waiting :
E:Unable to mount /cache
E:Unable to mount /data
E:Unable to mount /system
E: Failed to wipe dalvik
When trying the same rom :
the message error :
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error n /sdcard/DHD...._nitr00.zip (status 7)
Installation aborted.
After the TWR recovery i returned to 4Ext recovery, I did in 2 steps
1 - a wipe for factory reset/cache/dalvik,
2 - shutdown 5 minutes later
3 - i did a wipe for data/system and boot.
without shutdowning, i had an error failed to ...
I installed the RandomRom (145 and 5.00)
Firstly RandomRom145.zip
shutdown 5 minutes
secondly RandomRom5.00
then I flashed th boot.img
The rom was installed without errors.
When I booted it, I have the first white screen then I had a black screen for 1 or 2 minutes then the recovery tool was loaded.
Finally, I think that ma DHD is really dead.
I spent a day to arrive to this !!
Thanx for helps
Click to expand...
Click to collapse
First your DHD in continuously reboot, than You were unable to make a call and now this.
All this in period in one mouth?
I think you have corrupted eMMC.
No
I have 3 HTC Desire HD
First : in a continuous reboot,
Second : unable to make a call,
Third : the actual problem.
Best regards
Did you wipe everything after last ROM instalation (ROM + boot.img)?
Hello,
Yes I do everything (using 4ext Recovery Touch).
It takes a long long time to wipe : wipe data/factory reset; cache; cache+dalvik; dalvik cache; battry.
I had errors when formatting system and/or data, like :
formatting /data
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27
best regards
TF85 said:
Hello,
Yes I do everything (using 4ext Recovery Touch).
It takes a long long time to wipe : wipe data/factory reset; cache; cache+dalvik; dalvik cache; battry.
I had errors when formatting system and/or data, like :
formatting /data
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27
best regards
Click to expand...
Click to collapse
I think it would be great to first check and to be shure if it's eMMC problem or not.
How to check this (one of example):
Try to install some other Recovery.
If you pass without errors turn off phone and pull out battery for few minutes. (if you get errors in installation, try few times, or try with different recovery, but just be shure that you not installing the same you allready have)
Put battery back on and turn on phone in recovery. Check is it really there and installed.
If you succesfuly installed diffrent recovery your emmc is working and you can fix it.
If you don't get errors, install it, and after restart you see that you have your old recovery, it's probably problem with your emmc. We can try more things to be shure.
TF85 said:
Hello,
Yes I do everything (using 4ext Recovery Touch).
It takes a long long time to wipe : wipe data/factory reset; cache; cache+dalvik; dalvik cache; battry.
I had errors when formatting system and/or data, like :
formatting /data
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p26
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p27
best regards
Click to expand...
Click to collapse
Or you could try booting into bootloader and try using the erase and format options
like this
Code:
fastboot erase system
Code:
fastboot erase data
Code:
fastboot erase cache
Code:
fastboot erase boot
Same to the format
Code:
fastboot format system
Code:
fastboot format data
Code:
fastboot format cache
Code:
fastboot format boot
If these dont work, then am afraid your emmc is f*cked.
Hello,
Yes the emmc is out, I can't :
- erase or format system
- erase or format data
- erase or ormat cache
Thank you very much for your helps
A friend asked me to help unbricking his Nexus 7 (Wi-Fi, 2013 version) ("flo") (it's stuck on Google white logo screen that shows after boot-up), as I am the only person he knows who have some custom ROM installing/etc. experience, but I am hardly an expert. I tried my best, but after few hours I am stumped.
I found the guides at XDA and elsewhere, and they all suggest I need to start by unlocking his bootloader. I tried two (similar at core) methods: first, using the command prompt fastboot.exe from the ADK, and second, using the Nexus Rooting Toolkit. The device is detected through fastboot devices command, but after running fastboot oem unlock, fastboot terminal is stuck at (bootloader) erasing userdata... for many minutes (whereas the action should take no more than few seconds). NRT is also stuck; while the device is frozen on the confirmation of unlocking screen. I read somewhere that some USB ports are problematic (3.0?), so whereas I am not sure how to check (in Win 7) which USB ports I have, I tried 5-6 on 2 computers (laptops) I have at home; both provide exactly the same result. I may try a 3rd (work) computer tomorrow, but I wonder if the device is beyond help?
Now, I was able to enter the Stock Recovery mode, too, and it starts with several errors (yellow script at the bottom). I wonder if it means that the internal SD card is gone, or such?
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
same fir last_log and last_install
E:failed closing /dev/block... (I/O error)
Factory reset from stock recovery gives
-- Wiping data...
Formatting /data...
E:failed to mount /cache... and a bunch of can't mount/open followed by
Data wipe complete.
Then more failures to mount/open ending with the I/O error and a final failed to mount /cache (Invalid argument).
Any suggestions what can be tried, if anything, would be appreciated. Just please, if someone links me to a guide to unbricking that starts with "your device has to be unlocked", for pity's sake, remember I cannot unlock this damn contraption, so I need either a solution that bypasses unlocking, or suggestions on how to unlock this given my failure to do so on two computers.
hello guys
i have a galaxy note 8 that i didn't use for a month and when start it goes in boot loop. i didn't flash any ROM. i try to reset factory but ended with error. any one can help please.:crying:
I am in the exact same circumstance; and i've never rooted it. All of a sudden it began to boot loop. The thing is -- is that I have data on there that I really need to preserve. Is there any way that I can reach the data on the hard drive? I've done a wipe cache partition function.
I'm also receiving some of the following error messages (among others):
failed to mount /efs (Invalid argument)
E: failed to mount /data (Invalid argument)
can't mount '/data (Invalid argument)
Please advise if you're familiar.
Thanks!
Hi, a few months ago I installed Kingroot on my Samsung S4 mini DUOS (GT-i9192)... Idk if it has something to do with it, but after a while my phone suddenly starts to reset without reason at all. I tried to unroot but it didn't let me to unistall, delete or overwrite any kind of app, archive or folder. I can't even do a full wipe or install a custom recovery.
Here is the problem when I start the recovery...
Android system recovery <3e>
KOT49H.I9192XXUCOA1
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : CAC
did not match sized '/system/csc/common/system/csc/languaje.xml'(no data available)
And when I tried to do a full wipe/factory reset...
-- Wiping data...
Formating /data...
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata
Formating /cache...
E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/cache
Data wipe complete
Every help will be so appreciated... Thanks
PD: Sorry for my english is pretty basic...
Hello guys,
Long story short. Two days ago I tried to install lineageOS, managed to do it = no sim card error. Tried installing 15.1 same, did some wiping, erasing without knowledge or backups. Now installed latest [BALTIC] rom from sammobile, stuck on samsung logo during boot, in recovery mode it says some errors:
No support single-sku
E:Failed to mount /efs (Invalid argument) like 4x times
dm-verity verification failed...
E: Failed to clear BCB message: Failed to find /misc partition
I have no backups. Is it still possible to fix this phone? Or I screwed it up totally?
Thank you
Respectfully,
Tomas