Database Info

[GUIDE] Read this before going for eMMC replacement.

Code:
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
When you see this message in your recovery do not panic.
Setup adb/fastboot on your computer (there is a simple guide in my signature). Then connect your device to the PC, enter recovery, open cmd (command prompt) on the PC and type:
Code:
adb shell
dmesg | grep mmc0
If the output contains the following strings:
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
Than you internal memory (eMMC) is corrupted i.e. your chip is "fried". This is a hardware issue (reference here) and the chip has to be replaced. Sorry, no other solutions available.
If not - your chip is not fried!
This message results from a destroyed /cache partition - some relevant info here​
Some basic thing has to be done to solve this problem easily:
NEVER PULL THE BATTERY! Better have the patience to wait it to be completely drained
always keep a Backup of your current ROM and/or the Stock ROM, made from Recovery on your SDcard
enable USB Debugging in your Settings -> Applications -> Development and keep it that way
disable Fastboot in Settings -> Power to have total shutdown on power off
after unlocking (S-OFF) your device with Revolutionary flash an Engineering bootloader (e.g. 0.98.2000) to be able to overwrite it when needed
use 4EXT Recovery rather than ClockworkMod it has much better functionality
To restore one of the following has to be done:
restore the Nandroid backup if you have done it
or
restore the cache partition - wipe /cache from the Recovery (preferred - thanks forcefreak). If the size of the partition says <null> (when Printing partition info in 4EXT Recovery) connect your device to a PC, go into adb shell (look the link in my signature for adb setup) and type
Code:
mke2fs /dev/block/mmcblk0p27
do not pay attention to the busy partition message, then
Code:
reboot recovery
Note that this option will format your cache as ext2 or ext3 type. If you are using ext4 just use the 4EXT Recovery to reformat them as ext4
or
According to craigcharlie's post
selecting the Factory reset option in the HBOOT is also a way to boot to Recovery and then flash a custom ROM or restore a backup
or
if steps 1/ 2/ 3 are not working flash the relevant RUU (the same or higher version than your current and correct region/brand - you can find the available for Desire S here) when your phone is in FASTBOOT USB mode in bootloader (you may need to reinstall the HTC drivers) [credits go to dave303 and the guide in his blog.]
4.1 If you have a 6.98.1000 hboot
Change your hboot with this one
Download PG88IMG.zip, extract it and use Android Flasher to flash the extracted hboot.img
The hboot version now should be 0.98.2000
Search in this thread for the proper RUU and install it.
4.2 If you have a 6.98.1002 hboot
Change your hboot with this one
Download the hboot_0.98.0000.zip and extract it, boot your phone to Recovery, connect to PC, copy the hboot.img file to your SDcard, open command prompt and type:
Code:
adb devices [I](your device serial number should be displayed)[/I]
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes)[/I]
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18[I][/I]
if not working try to unmount/mount the SDcard:
Code:
adb devices [I](your device serial number should be displayed)[/I]
adb shell [I](there should be a command prompt with the # symbol in front if not type "su" without the quotes)[/I]
umount /sdcard [I](not a typo the command is umount, not u[B]N[/B]mount)[/I]
mount /sdcard
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18[I][/I]
Search in this thread for the proper RUU and install it.
NOTE: If you have a custom ROM and no info about your original software version the solution is as follows:
Connect the device, enter the bootloader and type the following command in the cmd:
Code:
fastboot getvar version-main
This is the number of your original software.
If this number is higher than the one of your RUU and you cannot flash it, change the number with the version of your RUU (be careful - use the correct RUU for your brand/region!) with misc_version that can be found here - post #1, link from step 1.
If you have problems with some of the above post in the Desire S General forum or in this thread to receive support. Some cases can be individual but there is always a chance to fix before going for a replacement

You should PM ben_pyett, he has full guides on this whole thing. Also so he could add it to the "index" thread ^.^

Wow.sick tutorial. this must get a place in the index in very very big, bold letters.
Sent from my HTC Desire S/S510e using XDA App

Other way to solve this problem?
Hi
I had the same error after installing a new RADIO version on my Desire S.
-> Market closes unexpected
-> Can't open cache... in recovery
I fixed the problem with CWM Recovery!
1. Restart phone to ClockworkMod Recovery
2. Choose "wipe cache partition"
3. "reboot system now"
DONE

Just checked my chip and luckily I'm not affected. Sympathy to l u guys who are. (
Sent from my HTC Desire S using xda premium

forcefreak said:
Hi
I had the same error after installing a new RADIO version on my Desire S.
-> Market closes unexpected
-> Can't open cache... in recovery
I fixed the problem with CWM Recovery!
1. Restart phone to ClockworkMod Recovery
2. Choose "wipe cache partition"
3. "reboot system now"
DONE
Click to expand...
Click to collapse
I have tried this as well but my partition size was null. Tried formatting as Ext3 and Ext4. Honestly haven't tried just to format...
Btw the command mk2fs (the 2nd method in my initial post) makes exactly the same as your solution but from the command prompt. Anyway yours is easier so thanks for the contribution! But keep in mind that in both ways the partirion will be restored as ext3 so you will have to use 4EXT Recovery later to convert if you want to use the advantages of ext4

Hello,
I've just one question: why this happens?
Every time I wipe the cache and the dalvik-cache through the Recovery, I get this error. Should be considered as normal hence?

fbcyborg said:
Hello,
I've just one question: why this happens?
Every time I wipe the cache and the dalvik-cache through the Recovery, I get this error. Should be considered as normal hence?
Click to expand...
Click to collapse
"Every time" is definately not NORMAL! Check your partiton type ext2/3/4. If not ext4 format it as such with 4EXT Recovery
And one piece of advice: change your bootloader version, in case you stuck. This cannot be overwritten so you will go straight to replacement (most probably paid by you)
Sent from my HTC Desire S using Tapatalk

How can I see which filesystem type is it?
Anyway, I use ClockworkMod now, and I don't think it is ext4.
---------- Post added at 05:00 PM ---------- Previous post was at 04:35 PM ----------
Checked: it is a ex2 partition.
I've just flashed the 4EXT Recovery.
So, you suggest to change the bootloader? Which version?
I didn't understand what could cause the stuck: the partition type change? What cannot be overwritten? Maybe it's not clear to me what is the risk.

fbcyborg said:
How can I see which filesystem type is it?
Anyway, I use ClockworkMod now, and I don't think it is ext4.
---------- Post added at 05:00 PM ---------- Previous post was at 04:35 PM ----------
Checked: it is a ex2 partition.
I've just flashed the 4EXT Recovery.
So, you suggest to change the bootloader? Which version?
I didn't understand what could cause the stuck: the partition type change? What cannot be overwritten? Maybe it's not clear to me what is the risk.
Click to expand...
Click to collapse
The best option IMO is the hboot from my signature: 0.98.2000 (2.0.2002 reduces your cache space and maybe will be useful in future, but for now it isn't)
The reason: Revolutionary/Alpharev is permanent, which means that it cannot be overwritten (I have an untested method that may unlock it but I cannot verify and definitely will not brick my device to try it out ), unlike the other ENG Bootloaders which provide the same functionality but can be easily replaced (by RUU for example) if necessary. Like if you flash some incompatible software that bricks your phone and you are not able (or just do not have) to restore a Nandroid backup there is nothing you can do except to go to a repair center, where they will see that your bootloader is 6.98.1002 and most probably you will pay the repair (the eMMC chip costs about 1/3 of the phone price). On other hand if you can restore the system or at least the bootloader with the Stock one (e.g. from RUU) you can always say that your phone just collapsed and you do not know anything about it. I hope now it will be more clear to you.
P.S.: 4EXT Recovery is the best choice!

Thanks a lot for the explanation. You was very clear now.
So, if I'm not wrong, and if I've really understood everything, you mean that my old ClockworkMod Recovery is still there, and the 4EXT (that is a modified CWM recovery), is a sort of upgrade of CWM.
Anyway, I have a doubt about the hBoot you mentioned: the 0.98.2000 which is reported as the original one in the related thread, but before S-Offing and rooting my phone with revolutionary, I had 0.98.0002. Is it not different?

fbcyborg said:
Thanks a lot for the explanation. You was very clear now.
So, if I'm not wrong, and if I've really understood everything, you mean that my old ClockworkMod Recovery is still there, and the 4EXT (that is a modified CWM recovery), is a sort of upgrade of CWM.
Anyway, I have a doubt about the hBoot you mentioned: the 0.98.2000 which is reported as the original one in the related thread, but before S-Offing and rooting my phone with revolutionary, I had 0.98.0002. Is it not different?
Click to expand...
Click to collapse
4EXT Recovery is based on ClockworkMod, but is has more functionality...now you can still use your backups from CWM, even to convert them to ext4 format (check the 4EXT thread in my signature all is described there.
Now, my explanation above was related to the bootloaders (hboot)
For the Desire S there are the following hboot versions:
0.98.0000, 0.98.0002 and 2.00.0002 - Stock. The latter currently cannot be unlocked by Revolutionary exploit
0.98.2000 - "old" Engineering bootloader that allows you to flash system stuff like custom Recovery, different Radio version, unsigned stuff, etc.
2.00.2002 - Engineering bootloader with the same functions as the "old" one but with different partition style (/cache is 150 MB smaller and /system has 150 MB more space), but currently supported only by the new OTA (Stock) ROM
6.98.1000 and 6.98.1002 - Revolutionary/Alpharev Engineering bootloader that is installed on your device after S-OFF, with the same functions and partition style as 0.98.2000, but cannot be directly overwritten by RUU if you get in trouble...

I've just put the 0.98.2000 ENG hBoot, but as regard the filesystem type: do you mean I have to convert all partitions to ext4 or only the cache partition?

fbcyborg said:
I've just put the 0.98.2000 ENG hBoot, but as regard the filesystem type: do you mean I have to convert all partitions to ext4 or only the cache partition?
Click to expand...
Click to collapse
system, data and cache. Then flash the new ROM. Of course you can use ext3 without any problems. Do some reading here and decide for yourself, but it is mentioned that:
The ext4 filesystem is backward compatible with ext3 and ext2, making it possible to mount ext3 and ext2 filesystems as ext4. This will slightly improve performance, because certain new features of ext4 can also be used with ext3 and ext2, such as the new block allocation algorithm.
Click to expand...
Click to collapse

I've followed your suggestions, and this time, with 4EXT and the cache wipe, I've not seen the messages I've reported when I used the CWM. Formatted all partitions (not the sdcard) to ext4 and all is OK!

fbcyborg said:
I've followed your suggestions, and this time, with 4EXT and the cache wipe, I've not seen the messages I've reported when I used the CWM. Formatted all partitions (not the sdcard) to ext4 and all is OK!
Click to expand...
Click to collapse
Glad to hear

Awesome post.
I have one extra problem right now and that is my phone will not power up?
I have the symptoms of fried eMMC chip, but since switching it off at one point it will not power up anymore. Tried battery in a different phone and it is nearly full.
Any Ideas?

clubbtraxx said:
Awesome post.
I have one extra problem right now and that is my phone will not power up?
I have the symptoms of fried eMMC chip, but since switching it off at one point it will not power up anymore. Tried battery in a different phone and it is nearly full.
Any Ideas?
Click to expand...
Click to collapse
is there any vibration when you turn it on or does the led light?
have you altered your device eg root or custom ROM etc?
If no return under warranty as sounds like hardware issue
Swyped from my Desire S using XDA Premium

Ben, right now nothing happens when I press the power button.
My saga was rooted through AlphaRev and I was trying few different ROMs
Somewhere along the way I changed my SD card and after powerup into recovery I noticed for the first time these errors in CWM.
After reading on here I tried few things and at one point shut it off and since can't power back on. My hboot and recovery were still working but as said can't power up anymore now.
When I attach the USB cable the led flashes on and off about every second or two. This stops when I press the power button but the phone doesn't power up.
Looks like bricked to me :-(

clubbtraxx said:
Ben, right now nothing happens when I press the power button.
My saga was rooted through AlphaRev and I was trying few different ROMs
Somewhere along the way I changed my SD card and after powerup into recovery I noticed for the first time these errors in CWM.
After reading on here I tried few things and at one point shut it off and since can't power back on. My hboot and recovery were still working but as said can't power up anymore now.
When I attach the USB cable the led flashes on and off about every second or two. This stops when I press the power button but the phone doesn't power up.
Looks like bricked to me :-(
Click to expand...
Click to collapse
Yes seem like a total brick...I think that you have flashed something that is not belonging to your phone (probably you are branded). Anyway try adb and fastboot, if any of these commands can detect the phone you can try to reboot to bootloader or recovery. If not go straight for a repair and do not mention the custom software part
P.S. curious what you did before this happened?

[Q] Accidentally Wiped /system, Can't Flash ROM

I was going to install a superuser.zip file to root my M4 but when I went to wipe the /cache the /system get wiped as well. I can boot into either CWM or TWRP and have full fastboot/adb, but when I try to boot into Android it just brings me back to the bootloader. When I try to install a stock ROM it just says it's flashing it but hangs at a certain point, I even had it run overnight and it still didn't install. When I try to flash a custom ROM suh as Cyanogenmod it either completes the flashing in about 2 seconds or greets me with an error. RUU and FUU don't seem to work. I'm 100% out of ideas now, and I'm open to anything to try.

legofan623 said:
I was going to install a superuser.zip file to root my M4 but when I went to wipe the /cache the /system get wiped as well. I can boot into either CWM or TWRP and have full fastboot/adb, but when I try to boot into Android it just brings me back to the bootloader. When I try to install a stock ROM it just says it's flashing it but hangs at a certain point, I even had it run overnight and it still didn't install. When I try to flash a custom ROM suh as Cyanogenmod it either completes the flashing in about 2 seconds or greets me with an error. RUU and FUU don't seem to work. I'm 100% out of ideas now, and I'm open to anything to try.
Click to expand...
Click to collapse
Andyt95 said:
Download Magio R4
reboot into recovery, type in cmd
Code:
adb devices
adb shell
mount data
exit
adb push /path/to/magioR4.zip /data/
[I](you should reboot here, in which case you'll
need to type[/I] "mount data" [I]again after adb shell,
but it's not really essential and should work anyway)[/I]
adb shell
mount /data /sdcard [I](creates a virtual sdcard)[/I]
flash your ROM in recovery just like you would normally (select .zip from sdcard) and boot up
run rumrunner, it should work, giving you S-OFF which will let you flash absolutely anything. If it doesn't, let me know and I'll come up with a workaround.
Click to expand...
Click to collapse
should work

Andyt95 said:
should work
Click to expand...
Click to collapse
Well first:
~ # ←[6nmount data
mount data
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
But instead I just used a USB OTG and flash drive so no big deal
And then Magio popped up with its installer and I went through that and then hit "reboot" to be greeted with the bootloader, so I hit "reboot" in the bootloader, but it still brings me back to the bootloader immediately after a black screen, so I thought "Oops, needed to flash the boot.img", so boot.img was then flashed. Now the green HTC logo is sitting there and isn't doing anything, probably frozen.

Code:
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
means /data is already mounted

I actually got it up and running from a nandroid restore, I tried it once before but the restore didnt finish so I thought it wouldnt work. Thanks for helping me out anyway though!

Internal memory corrupted ? unable to mount /data /cache

Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done​
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"​
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8​
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.​
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate

you are facing probably the same issue with others that faced with twrp
those partitions corrupted after using the wipe options
the only thing i can suggest you is to use this solution
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
best wishes

So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)

ni4rkx said:
So yeah, i've try so many things, and none of them is fixing my problem.
First i've installed 4ext recovery and i had still the same issue, not able to wipe cache or data or factory reset.
I've tried to install adb but it doesn't recognize my phone, even with SDK tools, i can't tell the program what my phone is.
now i've tried to install the RUU (dl the .exe, found the rom.zip, and put on my phone renamed it "PG58IMG.zip" now when i'm on the fastboot it loads the file and then it get stuck at the userdata part....
If i try to boot the normal way i get the black screen with the red triangle and exclamation mark ....
I'm going to keep looking but it's getting harder than expected
(still sorry for my english)
Click to expand...
Click to collapse
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.

hinxnz said:
I can't help with issue but userdata is not mmcblk0p8, it's mmcblk0p23 on our device.
Click to expand...
Click to collapse
Hmm thanks for this info, I will try to do again all this but on an other computer tomorrow maybe it will work... I hope!

So after hours of trying to repair it, it still doesn't work.
But i've found something that might be intersting.
In recovery 4ext but now I'm twrp so I don't have the exact information again but when I went in storage information, it was written that the internal storage was --mb, and --mb free, so I guess it means that my partition doesn't exist anymore.. Anyway I've found that I'm not the only one with this but I still didn't find any solution to fix it..

ni4rkx said:
Hi, first of all sorry for my english.
I'm S-off, rooted, using TWRP touch and android 5.0 (from ivanich).
I went out of memory on my internal storage, so I had a pop-up that says lower your storage (my sd card couldn't be mounted). Then i went in recovery to wipe cache and data for it would free some space, but I got theses issue:
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such device
unmount of /data failed; no such volume
script succeeded: result was [0,200000]
updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
...done​
I also tried by advanced wipe> wipe Data and I went stuck on this :
"Formatting Data using make_ext4fs function"​
If i try to reboot on the rom it's bootloop
I tried a few command in the terminal command that I've found here http://forum.xda-developers.com/showthread.php?t=2683787
mke2fs -T ext4 /dev/block/mmcblk0p8​
I get this :
filesystem too small for a journal
writing superblocks and lifesystem accounting information : done
This filesystem will be automatically checked every 37 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.​
So I have no idea how to fix this I never had this error before and I can't find anything about it, only Odin but correct me if I'm wrong but Odin doesn't work for Sensation ?
Thanks for any help I appreciate
Click to expand...
Click to collapse
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.

When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?

little_lerroyy said:
I decided to try TWRP yesterday and Im having a similar issue. However when i flash roms I have no issues at all. However i get stuck at the HTC logo forever when i try and boot. I have manually flashed boot.img so that isnt the issue. I even tried doing some mkfs.ext4 executions and i still have the same issue. Im going back to my E63 to see if i can still repair this. However looks like another device is looking likely.
Can anyone tell me if you can run some error logs for when the device is in the boot stage, and by that i mean when the HTC logo so showing? I dont think ADB will work in that mode.
Click to expand...
Click to collapse
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Sajito said:
When you try to mount data from recovery does it fail?
Can you tell me which twrp your using? I mean which r stands at the end of the filename?
Click to expand...
Click to collapse
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB

ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Where did you download that image?
That sounds like you just experienced the brick bug.

Sajito said:
Where did you download that image?
That sounds like you just experienced the brick bug.
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo

ni4rkx said:
http://techerrata.com/browse/twrp2/pyramid from http://teamw.in/project/twrp2/66 the recovery img method.
Well I'm not sure because It booted the rom (cm12 from ivanich) but yeah bootloop on the CM logo
Click to expand...
Click to collapse
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?

Sajito said:
I'm sorry to say, but that's definitely the brick bug. Only the link rzr86 posted might help you using your phone. Ivanich made twrp builds, which use his kernel and device trees, so we're pretty sure his twrp is not affected by that bug (that just as an info for anyone using the twrp from the official site. So if anyone reads this and is using twrp newer than 2.6 from official site, get ivanich's build).
The problem is that your data partition is corrupt, not the system partition. But you need the data partition, to use any rom, which is now not mountable anymore. So your able to flash roms and get until bootanimation, but without data partition working it won't boot.
@little_lerroyy did you use ivanich's twrp or the one from official site too?
Click to expand...
Click to collapse
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue

ni4rkx said:
So you're saying that TWRP didn't do their job good enough and bricked my phone ? =/ that's pretty sad
thanks for the info tho but maybe there is a way to re create the data partition, since I think I'm not the only one who has this issue
Click to expand...
Click to collapse
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.

Sajito said:
The problem is not caused by twrp, but the faulty device/kernel trees which were used for that image. Unfortunately nobody knows who built these images, nor do we know which sources were used.
I had that too, I know that sucks.
Click to expand...
Click to collapse
Alright then.... I have an old motorola defy yeahhhh :good:

ni4rkx said:
Alright then.... I have an old motorola defy yeahhhh :good:
Click to expand...
Click to collapse
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.

ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?

Sajito said:
You can still try to mount your sdcard as data partition, as explained in the link posted on page 1, it seems to work for some.
Click to expand...
Click to collapse
Hm I've take a look but it looks complicated :s
hinxnz said:
Connect phone to pc, boot into recovery, open terminal and type 'adb devices', your device should show.
To try mount data enter 'adb shell mount /data'.
To check structure enter 'adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p23'.
Maybe this could help?
Click to expand...
Click to collapse
Well I'll give it a try when I can work on an other computer because I also have an issue with windows 8.1, it doesn't recognize my phone, so I can't use adb to work with the phone. It worked on windows 7 on an other computer but I can't use it for now.. Thanks anyway I'll keep you in touch

ni4rkx said:
What do you mean "some mkfs.ext4 executions" ? I wanted to try that but I couldn't find how to do it, I tried in ADB it didn't work & terminal from twrp neither maybe I didn't type correctly.
I'll suggest you to re flash it, or wipe & flash. (but it's not the point of my thread tho ...)
Yes I can't mount it..
openrecovery-twrp-2.8.4.0-pyramid.img that i've flash by ADB
Click to expand...
Click to collapse
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.

little_lerroyy said:
Follow this link, the process is done in ADB
http://android-revolution-hd.blogspot.com.au/2013/10/fix-data-htc-one.html
Just make sure where it says "mmcblk0p37" in step number 10, you put in "mmcblk0p23" which is your data partition, but i doubt you will have much access doing this.
Click to expand...
Click to collapse
Thanks but as I said, I can't use ADB on my computer. I'll still try when I can use an other one !

[Solved]Help with root on 6039Y

Hello,
first of all my idol has locked bootloader.
I just resized /data partition to 16GB, and it is working no problem, but I can not root it ( install supersu.zip).
After installing supersu.zip, on the /system partition are su binaries and SuperSu apk etc. so the zip file is flashed right way but, after rebooting the device I can reach the device only via adb shell, and do whatever, but It is not booting
Is there any special supersu.zip package for our device? or Do I need bootloader unlocked?
Thanks for help )

howpathetic said:
Hello,
first of all my idol has locked bootloader.
I just resized /data partition to 16GB, and it is working no problem, but I can not root it ( install supersu.zip).
After installing supersu.zip, on the /system partition are su binaries and SuperSu apk etc. so the zip file is flashed right way but, after rebooting the device I can reach the device only via adb shell, and do whatever, but It is not booting
Is there any special supersu.zip package for our device? or Do I need bootloader unlocked?
Thanks for help )
Click to expand...
Click to collapse
What is the problem with the supersu from the recovery? Why you don't use it ? No additional .zip .bin or other files are needed to root your phone. I have described already here how the prompt for the supersu installation can be seen if it has been discarded once. The bootloader is not necessary to be unlocked.

petrov.0 said:
What is the problem with the supersu from the recovery? Why you don't use it ? No additional .zip .bin or other files are needed to root your phone. I have described already here how the prompt for the supersu installation can be seen if it has been discarded once. The bootloader is not necessary to be unlocked.
Click to expand...
Click to collapse
I forgot to write it, but I tried the TWRP supersu as well, and it did nothing I tried it now again, removed .twrps, allowed modifications on /system, pressed reboot, system then it asked for installing supersu, so I swiped for install. It intalled and rebooted, after reboot there is not root nor supersu apk.

howpathetic said:
I forgot to write it, but I tried the TWRP supersu as well, and it did nothing I tried it now again, removed .twrps, allowed modifications on /system, pressed reboot, system then it asked for installing supersu, so I swiped for install. It intalled and rebooted, after reboot there is not root nor supersu apk.
Click to expand...
Click to collapse
I fully unrooted my device, and then rooted it again, just to see that it works. After the installation of supersu from the recovery, root access is not available right away. In the applications menu you must have SuperSU installer. Start it, and choose Play. It will open the play store. Choose Update and that's all.

When i install twrp supersu and then reboot to the system I really do not have anything related to supersu installed.... It seems like it is not mounting my /system as readwrite but i have set twrp to mount it as rw
I will try to dig some logs from recorvery

The logs are in /cache/recovery. Which recovery you use by the way?

petrov.0 said:
The logs are in /cache/recovery. Which recovery you use by the way?
Click to expand...
Click to collapse
I am using this one -> Recovery

howpathetic said:
I am using this one -> Recovery
Click to expand...
Click to collapse
What the logs say ? Can I see one ?

petrov.0 said:
What the logs say ? Can I see one ?
Click to expand...
Click to collapse
http://pastebin.com/dDt8hss1
I installed the supersu via twrp but nothing in log -.-

howpathetic said:
http://pastebin.com/dDt8hss1
I installed the supersu via twrp but nothing in log -.-
Click to expand...
Click to collapse
This is not the log from the installation. There should be others.

petrov.0 said:
This is not the log from the installation. There should be others.
Click to expand...
Click to collapse
There is the second one http://pastebin.com/PpHZ0HsF
mount: mounting /dev/block/mmcblk0p25 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy

howpathetic said:
There is the second one http://pastebin.com/PpHZ0HsF
mount: mounting /dev/block/mmcblk0p25 on /system failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p37 on /data failed: Device or resource busy
Click to expand...
Click to collapse
These two lines are not a problem. The partitions are mounted already and that's why mount complains. After this, the script remounts them as rw (no complains from this, so the remount is successful). The rest looks OK, so the 'su' binary and the '.apk' should be installed. Can you list /system/xbin/ and /system/app/ through adb and also to execute cat /system/etc/install-recovery.sh

Sure,
http://pastebin.com/9xmQ8ppH
This script /system/etc/install-recovery.sh does not exist

howpathetic said:
Sure,
http://pastebin.com/9xmQ8ppH
This script /system/etc/install-recovery.sh does not exist
Click to expand...
Click to collapse
There is something unclean in your system path. These lines from your log
Code:
- Removing old files
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
indicate that you have either /system/etc/install-recovery.sh or /system/bin/install-recovery.sh, prior the start of the installation (there is no other way they to be shown). What else you've done with the phone ... except to resize the data partition ? Also you have saved settings and the recovery loads them at the start. Remove them all. Start with clean settings. But first check in which of these two paths is your install-recovery.sh and what's inside. If all this does not help, probably a manual installation can do it.
... and just before to send this I saw it ... what's wrong with your data partition ?!?
Code:
/data | /dev/block/mmcblk0p37 | Size: 12143MB Used: 2732MB Free: 4602MB Backup Size: 2732MB
mine looks like this resized
Code:
/data | /dev/block/mmcblk0p37 | Size: 12195MB Used: 2505MB Free: 9690MB Backup Size: 2505MB
So the main question is what exactly you did with the device ?

petrov.0 said:
There is something unclean in your system path. These lines from your log
Code:
- Removing old files
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
indicate that you have either /system/etc/install-recovery.sh or /system/bin/install-recovery.sh, prior the start of the installation (there is no other way they to be shown). What else you've done with the phone ... except to resize the data partition ? Also you have saved settings and the recovery loads them at the start. Remove them all. Start with clean settings. But first check in which of these two paths is your install-recovery.sh and what's inside. If all this does not help, probably a manual installation can do it.
... and just before to send this I saw it ... what's wrong with your data partition ?!?
Code:
/data | /dev/block/mmcblk0p37 | Size: 12143MB Used: 2732MB Free: 4602MB Backup Size: 2732MB
mine looks like this resized
Code:
/data | /dev/block/mmcblk0p37 | Size: 12195MB Used: 2505MB Free: 9690MB Backup Size: 2505MB
So the main question is what exactly you did with the device ?
Click to expand...
Click to collapse
I just resized the partition, tried to flash supersu from zip ( official ) and the twrp supersu thats all.
http://pastebin.com/6G75XVmQ
Should I remove it?
and I will check the data partition, I have everything backuped so I can revert, but I think i resized it well I will check.
EDIT:
I have it repartitioned good.
I printed list of partition and
37 5000400 30535546 12.2 GiB FFFF userdata
38 30535548 30535646 49.5 KiB 0700 userdatabak
Looks exactly same as you have in your topic.
It has to be false value read by twrp.
look
from mount command
/dev/block/mmcblk0p37 12435084 7722388 4696312 62% /sdcard

howpathetic said:
I just resized the partition, tried to flash supersu from zip ( official ) and the twrp supersu thats all.
http://pastebin.com/6G75XVmQ
Should I remove it?....
Click to expand...
Click to collapse
No, leave the file (for now). It will be moved by the install-supersu.sh script (obviously he doesn't do it for some reason at the moment). Let's assume that the repartitioning is okay. From where you have these /system/bin/install-recovery.sh and /system/recovery-from-boot.p ? You have some official update probably ? I don't have such files in my backup.

petrov.0 said:
No, leave the file (for now). It will be moved by the install-supersu.sh script (obviously he doesn't do it for some reason at the moment). Let's assume that the repartitioning is okay. From where you have these /system/bin/install-recovery.sh and /system/recovery-from-boot.p ? You have some official update probably ? I don't have such files in my backup.
Click to expand...
Click to collapse
I really do not know, I installed once update.. Now I have 5.0.2-010 02010 02 version. Btw. could you please help me on for example google hangouts? I will post solution here later.

Solved
We had to run e2fsck over /system partition.
/system partition was somehow corrupted

Stuck at YU logo

1) Accidentally wiped all data including Internal Storage
2) Twrp 3.0 is working, but can't able to install any rom, Getting E:failed to mount / cache (Invalid argument) etc etc..
3)Getting "NO OS Installed" message in TWRP &- Internal Storage size is 0 (TWRP)
4) Followed Steps to flash factory image (WINDOWS)
Download the factory image fastboot package
Extract the contents of the fastboot package into a folder.
Download this flashing tools package
Extract the contents of the flashing tools zip into the same folder
To make sure, check that system.img, boot.img etc files are in the same folder as flash-all.bat, fastboot.exe etc
Connect your phone in fastboot mode, steps for which are : -
a. Power off your phone
b. Press and hold the Volume Up key
c. With the Volume Up key, connect the phone to your PC/Laptop with USB cable
d. You can let go off the Volume Up key when Fastboot Mode is displayed on the screen
Run flash-all.bat by double clicking on it.
A command window will open and flashing procedure will start
DO NOT disconnect the device during flashing procedure
The command window will close after the flashing process is over.
Disconnect the USB cable, and boot the phone normally by long pressing the Power button
But getting this error while flashing: http://imgur.com/g3NozUJ
After reboot,phone is stuck at YU logo..

Yuphoria stuck at YU Logo.
I had got notification for the OTA Cyanogen 12.1 Update and I had updated it. But even after reboot, the same 12.1 Update-notification would still appear again.
Later, I switched off Yuphoria to take out the External-SD-Card for data-transfer. Then when I switched on the Yuphoria, this Yu-Logo Boot-Loop Problem has started.
Now, My Yuphoria is Stuck at Yu-Logo on boot... and showing 'cannot mount partitions' errors when I boot custom-recovery twrp.
I have unlocked the bootloader.
From what I read online, I guess the memory partition-tables have got corrupted.... Now how can we solve this corrupted memory problem ?
I read about fastboot-flashing database.rfs or dbdata.rfs in some xda-developers Threads.
-----------------------------------------
I tried flash-all.bat with latest Cyanogen Official 12.1 ROM signed-fastboot.zip file... but still stuck at Yu-Logo on boot....
I fastboot boot trwp 2.6 custom-recovery.img and installed Cyanogen 12.1 ROM signed.zip file from external-sd card. But trwp says cannot mount partitions '/data', '/system', '/cache' etc...
---------------------------------------
I ran the command e2fsck /dev/block/bootdevice/by-name/system in terminal.
Then this message came : 'superblock has an invalid journal (inode 8) ext4'
I entered yes for correction multiple times and the process completed....
But still stuck at YU Logo on reboot.... Please Help.
-----------------------------------
I erased persist, then flashed persist.img.
Then I booted into twrp recovery, and adb sideload cm-12.1-YPG4PAS8A8-lettuce-signed.zip
The sideload started and then stopped with error : failed to unmount /cache ; failed to unmount /data ;
-----------------------------------
I boot into twrp 2.8.7.2 from fastboot-mode using command : sudo fastboot -i 0x2a96 boot twrp.img
Selected Wipe → advanced wipe → selected data :
It shows :
Mount Point : /data , File system : ext4 , Present: Yes, Removable: No, Size:0MB, Used: 0MB, Free 0MB, Backup Size: 0MB
Then I tapped on change/repair file system → change file system → EXT4 → Swiped IT...
Error : Format Failed.
E: Unknown MTP message type: 1
Failed to unmount '/data' (Invalid argument)
Error changing file system.
Updating Partition details.......
Failed to unmount '/system', '/data', '/cache' (Invalid arguments)
....done
Unable to mount storage.
After 'Change File System' Failed, I tried 'Repair File System' and 'Resize File System' also... all Failed similarly....
Only TWRP 2.8.7.2 and lower versions boots successfully in my Yuphoria.
TWRP 3.0.0 will not boot successfully. The TWRP logo will appear and then show command errors, and the phone will restart.
Please help me reinstall OS in my softbricked Yuphoria.

Goodison14 said:
I had got notification for the OTA Cyanogen 12.1 Update and I had updated it. But even after reboot, the same 12.1 Update-notification would still appear again.
Later, I switched off Yuphoria to take out the External-SD-Card for data-transfer. Then when I switched on the Yuphoria, this Yu-Logo Boot-Loop Problem has started.
Now, My Yuphoria is Stuck at Yu-Logo on boot... and showing 'cannot mount partitions' errors when I boot custom-recovery twrp.
I have unlocked the bootloader.
From what I read online, I guess the memory partition-tables have got corrupted.... Now how can we solve this corrupted memory problem ?
I read about fastboot-flashing database.rfs or dbdata.rfs in some xda-developers Threads.
-----------------------------------------
I tried flash-all.bat with latest Cyanogen Official 12.1 ROM signed-fastboot.zip file... but still stuck at Yu-Logo on boot....
I fastboot boot trwp 2.6 custom-recovery.img and installed Cyanogen 12.1 ROM signed.zip file from external-sd card. But trwp says cannot mount partitions '/data', '/system', '/cache' etc...
---------------------------------------
I ran the command e2fsck /dev/block/bootdevice/by-name/system in terminal.
Then this message came : 'superblock has an invalid journal (inode 8) ext4'
I entered yes for correction multiple times and the process completed....
But still stuck at YU Logo on reboot.... Please Help.
-----------------------------------
I erased persist, then flashed persist.img.
Then I booted into twrp recovery, and adb sideload cm-12.1-YPG4PAS8A8-lettuce-signed.zip
The sideload started and then stopped with error : failed to unmount /cache ; failed to unmount /data ;
-----------------------------------
I boot into twrp 2.8.7.2 from fastboot-mode using command : sudo fastboot -i 0x2a96 boot twrp.img
Selected Wipe → advanced wipe → selected data :
It shows :
Mount Point : /data , File system : ext4 , Present: Yes, Removable: No, Size:0MB, Used: 0MB, Free 0MB, Backup Size: 0MB
Then I tapped on change/repair file system → change file system → EXT4 → Swiped IT...
Error : Format Failed.
E: Unknown MTP message type: 1
Failed to unmount '/data' (Invalid argument)
Error changing file system.
Updating Partition details.......
Failed to unmount '/system', '/data', '/cache' (Invalid arguments)
....done
Unable to mount storage.
After 'Change File System' Failed, I tried 'Repair File System' and 'Resize File System' also... all Failed similarly....
Only TWRP 2.8.7.2 and lower versions boots successfully in my Yuphoria.
TWRP 3.0.0 will not boot successfully. The TWRP logo will appear and then show command errors, and the phone will restart.
Please help me reinstall OS in my softbricked Yuphoria.
Click to expand...
Click to collapse
Exact same problem for me... someone please help..

I too have been stuck up with the same problem, but in Yu Yureka...Brothers, Don't we really have a solution for this issue?!?!?...Please do something dear nerds lot of thanks!!

same prblm
anyone got solution for this ??

Exact problem.........
I ve gave it micromax service center, they asked 400 and began their work. after some time the man came out and sad, this is a board problem, you have to change the board. My friend is an embedded service engineer. He is saying its just a soft brick and the device is perfectly working. Those knowledgeless idiots dont want to find solution for this, the simply trying to change the board. Friends the problem we have is 100% a software issue, pls dont fall in their trap............

Same issue
Guys anyone got the solution ? Please help ...

Anybody got solutions, please respond

Same here
I tried everything but nothing seems to work. Someone help....

Seems to be Soft-Brick Software issue....
TWRP Recovery is not able to mount the /system , /cache and /data partitions...
but inside TWRP Recovery FileManager , we can open and browse all partiton files and system folders/files in /dev directory....
Also the TWRP Terminal shell can be used to run e2fsck and mke2fs commands...
So I think the /system, /cache and /data , and other corrupted android partitions like /misc can be repaired and mounted again, using the right steps and procedures....
Then I believe TWRP Recovery will mount partitons again and work, and we will be able to install/flash new ROM... Phone will boot into OS again...
We need Somebody with enough technical know-how to run Terminal Shell commands and repair corrupted android partitions.
Please if someone can help, would be greatful...
I used my Yuphoria for 10 months... now lying useless for one year...
---------- Post added at 11:42 AM ---------- Previous post was at 11:05 AM ----------
This XDA-Developers Thread has people trying and finding solutions to our problem.... Some even claim to have found the solution.
[Soft Brick] [Flash Stock] [Recovery] [ADB Driver] Yuphoria [Solution] by EssArr , 119 replies.
https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Will try and find out a method there...

Got solved?
chattboyz said:
I ve gave it micromax service center, they asked 400 and began their work. after some time the man came out and sad, this is a board problem, you have to change the board. My friend is an embedded service engineer. He is saying its just a soft brick and the device is perfectly working. Those knowledgeless idiots dont want to find solution for this, the simply trying to change the board. Friends the problem we have is 100% a software issue, pls dont fall in their trap............
Click to expand...
Click to collapse
So did you get the soultion for it? If yes, what?

The post is of no help
Goodison14 said:
TWRP Recovery is not able to mount the /system , /cache and /data partitions...
but inside TWRP Recovery FileManager , we can open and browse all partiton files and system folders/files in /dev directory....
Also the TWRP Terminal shell can be used to run e2fsck and mke2fs commands...
So I think the /system, /cache and /data , and other corrupted android partitions like /misc can be repaired and mounted again, using the right steps and procedures....
Then I believe TWRP Recovery will mount partitons again and work, and we will be able to install/flash new ROM... Phone will boot into OS again...
We need Somebody with enough technical know-how to run Terminal Shell commands and repair corrupted android partitions.
Please if someone can help, would be greatful...
I used my Yuphoria for 10 months... now lying useless for one year...
---------- Post added at 11:42 AM ---------- Previous post was at 11:05 AM ----------
This XDA-Developers Thread has people trying and finding solutions to our problem.... Some even claim to have found the solution.
[Soft Brick] [Flash Stock] [Recovery] [ADB Driver] Yuphoria [Solution] by EssArr , 119 replies.
https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Will try and find out a method there...
Click to expand...
Click to collapse
This is of no help as partitions are not getting mounted.

stuck at yu logo
i accidentially wiped my yu yurekas internal storage and got stucked at yu logo
i approched about 3 local service centers bt they said
it cannot be repaired because of failed to connect with their software box
and atlast i reched another localservice center come sales shop and they also advoced tge same bt understanding my sady situation the service boy at the shop asked me that "may i check it for further options if you allow to took the device as DEAD CONDITION for servicing bcz it may completely dead after this"
i agreed it
after a day he contacted me and said the problem has fix thank god
now its working fine
if any one want to know more details
such as about service centre
feel free to contact me through
[email protected]
thankyou:good:

Have anyone try to Flash stock rom?

nischait said:
Have anyone try to Flash stock rom?
Click to expand...
Click to collapse
Same problem here !!
Tried to flash the ROM with QFIL but the port is not detected by the software.
Also tried with fastboot.exe method still the same sometimes it says write failed for Size too large of system.img and if I change the default size limit (with -S option) it says "Error : Write failed"

degrader said:
Same problem here !!
Tried to flash the ROM with QFIL but the port is not detected by the software.
Also tried with fastboot.exe method still the same sometimes it says write failed for Size too large of system.img and if I change the default size limit (with -S option) it says "Error : Write failed"
Click to expand...
Click to collapse
Try annabathina method

nischait said:
Try annabathina method
Click to expand...
Click to collapse
Hi, can you share the link please?

degrader said:
Hi, can you share the link please?
Click to expand...
Click to collapse
Your device model please

Device is not getting detected
Hi,
I want to flash my Yuphoria. But, when i connect my device in Fastboot mode, my LAP (Windows 7 32 bit) is showing "Unknown USB". How to solve this issue??? please help me.

shashankdatta1218 said:
Hi,
I want to flash my Yuphoria. But, when i connect my device in Fastboot mode, my LAP (Windows 7 32 bit) is showing "Unknown USB". How to solve this issue??? please help me.
Click to expand...
Click to collapse
Install adb and fastboot drivers first